Description of problem:
I have gnome-power-manager configured to display a logout dialog when pressing
the power button of my laptop. Effectively it's the same as `gnome-session-save
--kill --gui`. The dialog gets displayed, but is completely unresponsive. On my
desktop with FC5 the background fades out after running that command. That's not
the case on my laptop with up to date Rawhide.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Login to GNOME
2. Open a terminal window
3. Run `gnome-session-save --kill --gui`
Logout/shutdown dialog gets drawn, but no actions can be performed. The only
option to get out of this is to kill gnome-session.
Possibility to do something inside the dialog, and actually log out.
With Compiz enabled, I get a blank window without controls.
The system is a PowerBook G4 with Radeon Mobility 9700.
In longer term it would be nice to sync the appearance of this dialog with the
gnome-panel dialog (accessible from the main menu).
Turns out, this happens only if a11y is enabled. Without a11y it works.
adding to FC7Target
Sees to work fine here with current rawhide. Do you still see this problem ?
(In reply to comment #3)
> Sees to work fine here with current rawhide. Do you still see this problem ?
Yes, it's still not working. The only difference is that now no widget gets
drawn inside the dialog, even without Compiz. It's just a grey square.
But a11y support needs to be enabled in your personal preferences to reproduce this.
gnome-session-save --kill --gui
works fine for me with a11y turned on, too.
Created attachment 152830 [details]
Output of attached strace to gnome-session process. Attached before pressing
the power button.
Created attachment 152831 [details]
Output of gdb attached after pressing the power button.
If there are other things I can provide, please say so.
can you attach your ~/.gnome2/session ?
Created attachment 152980 [details]
(In reply to comment #8)
> can you attach your ~/.gnome2/session ?
Sure. Here it is.
Just updated from 2.18.0-3 to 2.18.0-5, and what should I say... it works.
Maybe the fix of bug 229912 did the trick.