Bug 240688

Summary: power button (set to "ask" in gnome-power-manager) doesn't ask, instead locks X
Product: [Fedora] Fedora Reporter: Leszek Matok <lam>
Component: gnome-sessionAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-29 19:06:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Leszek Matok 2007-05-20 12:13:52 UTC
For few days now, pressing the power button of my Thinkpad T30, instead of
asking whether I want to shutdown or restart the machine, gradually darkens the
screen a little, then stops darkening and hangs in this state forever. No window
is shown, no keys work, no visible (behind the "dark glass", but visible)
windows show any updates. I can move the mouse cursor, though.

In this state, all I can do is kill X using alt-ctrl-backspace. I can also
switch to tty1 and kill gnome-session, or switch back to vt 7, where I see some
screen corruption at the top, which doesn't refresh to proper screen content.

On tty1 I checked if some program is looping taking whole CPU, but nothing like
that takes place.

I also checked for some messages in Xorg.0.log (suspecting "radeon" driver bug),
but it doesn't change between before and after pushing the button.

If I set the button function to suspend, it suspends without problem. Only
"asking" locks my session for good.

Everything used to work in FC7t4, but stopped with some of this week's updates
(which included gnome-power-manager, gnome-session and xorg-x11-server-Xorg,
every one of them is suspected). Now it's reproducible every time, so I can
provide every information you need.

Comment 1 Leszek Matok 2007-05-27 16:12:44 UTC
I've found an hour to test it and I confirm that the problem is in gnome-session.

In gnome-session-2.18.0-5.fc7 it works.

In gnome-session-2.18.0-7.fc7 it doesn't work.

Can't anyone reproduce it?

Comment 2 Ray Strode [halfline] 2007-05-29 19:06:49 UTC
ah this should be fixed in 2.18.0-8.fc7