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 646750 - Suspend fade out is out of sync
Suspend fade out is out of sync
Status: RESOLVED DUPLICATE of bug 655924
Product: gnome-shell
Classification: Core
Component: general
2.91.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
: 649690 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-04-04 21:52 UTC by Cosimo Cecchi
Modified: 2011-08-25 20:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Cosimo Cecchi 2011-04-04 21:52:43 UTC 
When I select "Suspend" from the shell user menu, I get the following:

1 a fade to black animation starts
2 it fades to black
3 when it reaches black, it flashes back to my desktop for a couple of seconds
4 flashes back to black again
5 laptop is actually suspended

3 and 4 should not happen
Comment 1 Kane 2011-04-16 19:54:19 UTC 
I can confirm this happens on both a laptop and desktop system.
Comment 2 HyperBaton 2011-04-17 00:57:47 UTC 
Same here, on a desktop with Radeon HD 3200 and ati-xf86-ati driver.
Comment 3 Finnbarr P. Murphy 2011-04-19 13:34:18 UTC 
Same here. On 64-bit UEFi system with Nvidia card, nouveau driver.
Comment 4 Ulrich Keller 2011-05-04 18:42:45 UTC 
Same here, Gnome 3.0.1 i686 on Arch Linux, Intel 945, xf86-video-intel driver.
Comment 5 Milan Bouchet-Valat 2011-05-07 20:51:33 UTC 
*** Bug 649690 has been marked as a duplicate of this bug. ***
Comment 6 Rui Matos 2011-06-05 11:17:49 UTC 
Does this still happen? I can't reproduce on an updated Fedora 15.
Comment 7 Yichao Yu 2011-06-05 15:37:58 UTC 
yes still on mine
Comment 8 Matthias Clasen 2011-08-25 20:49:36 UTC 
*** Bug 651874 has been marked as a duplicate of this bug. ***
Comment 9 Matthias Clasen 2011-08-25 20:56:12 UTC 
*** This bug has been marked as a duplicate of bug 655924 ***