After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 619451 - "gnome-session-save --shutdown-dialog" persists as blank after resuming from suspend
"gnome-session-save --shutdown-dialog" persists as blank after resuming from ...
Status: RESOLVED NOTGNOME
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-manager
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-05-23 18:45 UTC by mmonaco27
Modified: 2010-09-17 01:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description mmonaco27 2010-05-23 18:45:41 UTC 
When I suspend my computer via gnome-session-save, the dialog window remains after I resume as a blank window. It takes ~10 seconds to disappear. I'm pretty sure this _started_ with 2.30.
Comment 1 Hussam Al-Tayeb 2010-05-23 19:11:44 UTC 
I can confirm this too. It happens after resuming from hibernate too. 
gnome-session 2.30.0 
pm-utils 2.30.0
dbus 1.2.24
upower 0.9.4
Comment 2 Francisco J. Vazquez 2010-06-11 14:22:47 UTC 
Just another "me too". Gentoo and gnome 2.30 with:

dbus-1.2.24 
gnome-session-2.30.0-r1 
pm-utils-1.3.0-r3
Comment 3 Vincent Untz 2010-06-22 02:04:21 UTC 
That's actually a bug in upower. See discussion in https://bugzilla.novell.com/show_bug.cgi?id=615646

I'll open a bug against upower after discussing this with Richard.
Comment 4 mmonaco27 2010-09-16 01:45:37 UTC 
I just ran org.gnome.ScreenSaver.Lock() using d-feet. I noticed the same behavior when I unlocked the screen. A lot of the windows were blank, and took a few seconds to come back.
Comment 5 mmonaco27 2010-09-17 01:02:56 UTC 
Oops, I didn't see Vincent's comment about upower already.