policykit is not responding

Bug #623819 reported by Harry
634
This bug affects 143 people
Affects Status Importance Assigned to Milestone
PolicyKit GNOME
Invalid
Undecided
Unassigned
policykit-1-gnome (Ubuntu)
Fix Released
Medium
Michael Vogt

Bug Description

Binary package hint: policykit-1-gnome

In a fully updated maverick_amd64 the newest policykit-1-gnome_0.96-2ubuntu3
does not let me reboot nor shutdown. This is a recent update.

After I have pressed the reboot or shutdown button from the user menu, a small window opens with an error text:
"policykit is not responding".
If I then press the button "shutdown anyway", the computer reboots or shuts down within 10 seconds, but not immediately.

This has something to do with user rights, because if I command in terminal:
sudo reboot or
sudo halt (sudo poweroff)
the combuter responds immediately without any errors.

Also, if I downgrade the policykit-1-gnome and libpolkit-gtk-1-0 packages to the version 0.96-2ubuntu2, the issue is gone
and the user menu works as it should.

Revision history for this message
Harry (harry33) wrote :

This seems not to be an authorization error, more like policykit "hanging" and thus not responding.
Bug #499937 does not seem to bear much resemblance to this, even if it has been named to be solved with this 0.96-2ubuntu3 update.

plun (plun)
Changed in policykit-1-gnome (Ubuntu):
status: New → Confirmed
Revision history for this message
vmc (vmclark) wrote :

Harry, your right on Bug# 499937 and all its duplicates. I went through them all and this one doesn't reflect there issues. Its Mavericks recent iso only.

Revision history for this message
dino99 (9d9) wrote :

same issue here, ive removed quiet splash on the boot line to be able to see comments when i shutdown:
- at end of shutdown process, " / (root) is busy" is shown, then system stop, but on next reboot, it fail, need a cold boot to restart.

Revision history for this message
Harry (harry33) wrote :

Actually how much new code has been applied to the 0.96-2ubuntu3 version?
There was absolutely no problem with the former 0.96-2ubuntu2 version as far as shutdown/rebooting issues are concerned.
This much has been publiced in launchpad about this update:

" debian/patches/04-autorestart.patch:
    - add autorestart support (LP: #499937)"

And then this is built to depend on two new packages:
- libdbus-glib-1-2 (>= 0.78)
- libgdk-pixbuf2.0-0 (>= 2.21.6)

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

The issue is that the agent needs to repond to the session-end signals now it registers with the session manager

Changed in policykit-1-gnome (Ubuntu):
assignee: nobody → Michael Vogt (mvo)
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
Bilal Akhtar (bilalakhtar) wrote :

Okay, I am also facing this problem, on a fresh install of maverick i386 august 25 daily build.

Revision history for this message
Zorglub (jean-frm) wrote :

Same here, after an upgrade from lucid to maverick (amd64) on a Toshiba Satellite.

Revision history for this message
subbu (skbhat03) wrote :

I am also facing the same problem and i am on maverick 32bit

Revision history for this message
Stephan Muhs (stephan-dinoco) wrote :

Same issue here on Maverick amd64 with kernels 2.6.35-18 and 2.6.35-19

Revision history for this message
John Webster (civil-bigpond) wrote :

Same problem - Maverick i386 with 2.6.35-19 kernel (26 August build)

Revision history for this message
DeadlyWolf (deadlywolf051) wrote :

Same issue here on Maverick amd64 with kernels 2.6.35-18 and 2.6.35-19

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Could people please stop adding "me too's" here. We already understand what the issue is, we don't need people to keep telling us they're affected. There is a button you can press at the top of the page if you're affected, please use that instead

Revision history for this message
liamdawe (liamdawe) wrote :

Seems like we hit a nerve!

Revision history for this message
dino99 (9d9) wrote :

details logged into xsession-errors when i shutdown and see the policykit warning:

Exiting...
gnome-session[3206]: WARNING: Client '/org/gnome/SessionManager/Client4' failed to reply before timeout

Avertissement du gestionnaire de fenêtres : CurrentTime used to choose focus window; focus window may not be correct.
Avertissement du gestionnaire de fenêtres : Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
** Message: applet now removed from the notification area
Shutting down nautilus-ideviceinfo extension
Shutting down nautilus-gdu extension

--- Hash table keys for warning below:
--> root
--> inode/directory
--> l2069
--> oem
--> l2083
--> x-directory/normal

(nautilus:3278): Eel-WARNING **: "unique eel_ref_str" hash table still has 6 elements at quit time (keys above)

(nautilus:3278): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 22 elements at quit time
gnome-settings-daemon: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
polkit-gnome-authentication-agent-1: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
nm-applet: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
update-notifier: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
gdu-notification-daemon: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"

      after 80246 requests (80245 known processed) with 0 events remaining.

applet.py: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.
padevchooser: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.0.

Revision history for this message
dino99 (9d9) wrote :

might be due the second login (same as first) as i need to log twice: first login seem normal but when i want to do something else like using firefox or run update-manager or else, i immediatly fall down to the loging screen, then no trouble, except when shuting down, policykit complaint (see post above)

Revision history for this message
IdleOne (idleone) wrote :

screenshot of the error

Revision history for this message
Wei-Yee Chan (chanweiyee) wrote :

2.6.35-19-generic #26-Ubuntu SMP Thu Aug 26 19:13:04 UTC 2010 x86_64 GNU/Linux
AMD Athlon(tm) 64 X2 Dual Core Processor 3600+

Gary M (garym)
tags: added: maverick
Michael Vogt (mvo)
Changed in policykit-1-gnome (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Michael Vogt (mvo) wrote :

Uploaded into maverick (in the review queue currently).

Changed in policykit-1-gnome (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
riccardo de palo (riccardo-depalo-gmail) wrote :

I confirm the bug, with x86 Maverick install on two machines: asus t101mt and Sony Vgn Fz21M

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package policykit-1-gnome - 0.96-2ubuntu4

---------------
policykit-1-gnome (0.96-2ubuntu4) maverick; urgency=low

  * debian/patches/04-autorestart.patch:
    - updated to implement the full gnome-session API to prevent
      "authentication agent is not responding" message on logout
      (LP: #623819)
 -- Michael Vogt <email address hidden> Mon, 30 Aug 2010 09:59:29 +0200

Changed in policykit-1-gnome (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Harry (harry33) wrote :

I can confirm the fix works.
Problem solved.

Revision history for this message
Halvor Lyche Strandvoll (halvors) wrote :

When will the fix be avaliable in the Update Manager?

Revision history for this message
G0B1!N5486 (godthegoblin) wrote :

I have installed this latest update but I am still getting this "authentication agent is not responding" message on logout

Revision history for this message
Bilal Akhtar (bilalakhtar) wrote : Re: [Bug 623819] Re: [Maverick] policykit is not responding

On Tue, 2010-08-31 at 13:04 +0000, G0B1!N5486 wrote:
> I have installed this latest update but I am still getting this
> "authentication agent is not responding" message on logout

Did you reboot after the update? In the first shutdown, the message
appears, but not in consecutive shutdowns.

Revision history for this message
NoOp (glgxg) wrote :

On 08/31/2010 06:20 AM, Bilal Akhtar wrote:
> On Tue, 2010-08-31 at 13:04 +0000, G0B1!N5486 wrote:
>> I have installed this latest update but I am still getting this
>> "authentication agent is not responding" message on logout
>
> Did you reboot after the update? In the first shutdown, the message
> appears, but not in consecutive shutdowns.
>

Works for me after today's update. Thanks for the fix!

Revision history for this message
Jimmy Pinto Stelzer (jimmy-stelzer) wrote : Re: [Maverick] policykit is not responding

the upgrade works for me.

Revision history for this message
Illogic_Gate (illogicgate) wrote :

Recent updates resolved the problem for all three of my various ubuntu machines. Thanks!

Revision history for this message
Martin Pitt (pitti) wrote :

Michael, did you send this upstream anywhere? I can't find it.

Revision history for this message
Peter Schoenborn (nogaroc4) wrote : Re: [Bug 623819] Re: [Maverick] policykit is not responding

Yesm but ist OK now. No Problems now.

Thank you

Greatings
Peter

Am 04.11.2010 22:23, schrieb Martin Pitt:
> Michael, did you send this upstream anywhere? I can't find it.
>

Revision history for this message
Michael Vogt (mvo) wrote : Re: [Maverick] policykit is not responding

Hey Martin, thanks for the reminder. I send it upstream as https://bugzilla.gnome.org/show_bug.cgi?id=634502

Changed in policykit-1-gnome:
importance: Unknown → Wishlist
status: Unknown → New
Revision history for this message
andypiper (andypiperuk) wrote :

I have policykit-1-gnome 0.96-2ubuntu4 on Maverick i386 and see this same error on selecting Restart from the session menu.

dino99 (9d9)
tags: removed: maverick
summary: - [Maverick] policykit is not responding
+ policykit is not responding
Revision history for this message
dino99 (9d9) wrote :

This has been fixed on the way; so closing that report.

Changed in policykit-1-gnome:
importance: Wishlist → Undecided
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.