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 649691 - Wrong behavior when comming back from suspending
Wrong behavior when comming back from suspending
Status: RESOLVED DUPLICATE of bug 651874
Product: gnome-shell
Classification: Core
Component: general
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-05-07 20:37 UTC by Yichao Yu
Modified: 2011-06-05 11:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.91/3.0


Attachments
x log (39.57 KB, text/x-log)
2011-05-07 21:31 UTC, Yichao Yu
Details

Description Yichao Yu 2011-05-07 20:37:03 UTC
First, the screen isn't locked after suspending and I cannot find anywhere to configure it (this might not be a bug).
Even though it sometimes is locked, it shows my previous desktop first(although I cannot do anything because the screen is locked) and then turn into the input password screen.
I don't think it is a good idea to show the screen when it is still locked
Comment 1 Milan Bouchet-Valat 2011-05-07 20:48:12 UTC

*** This bug has been marked as a duplicate of bug 649690 ***
Comment 2 Milan Bouchet-Valat 2011-05-07 20:50:59 UTC
Hm, I messed up with bug numbers, sorry.

You can change when to lock the screen in System settings->Screen. The second problem is a bug, probably in gnome-screensaver, but I'll leave the developers decide. Could you give the version of the Shell you are using, and your graphics card model, drivers version and distribution?
Comment 3 Yichao Yu 2011-05-07 21:00:40 UTC
Yeah, that is exactly what I have done. (System settings->Screen) and it doesn't work at all if I use suspend button on my laptop to suspend, and appears as what I have said when I use the button in the menu.

The way it behave is so different when using menu button or keyboard button to suspend. I think Bug 646750 doesn't mention this one which is also included in my  bug 649690. Do I need to report a new bug for this one?

upload my system info soon.
Comment 4 Yichao Yu 2011-05-07 21:08:38 UTC
Thinkpad W500 4063-RC1

Archlinux
linux-2.6.38
gnome-shell 3.0.1-3

00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller])
	Subsystem: Lenovo Device 2115
	Flags: bus master, fast devsel, latency 0, IRQ 50
	Memory at f4400000 (64-bit, non-prefetchable) [size=4M]
	Memory at d0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at 1800 [size=8]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915


01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3650 (prog-if 00 [VGA controller])
	Subsystem: Lenovo Device 2126
	Flags: bus master, fast devsel, latency 0, IRQ 51
	Memory at c0000000 (32-bit, prefetchable) [size=256M]
	I/O ports at 2000 [size=256]
	Memory at bfff0000 (32-bit, non-prefetchable) [size=64K]
	[virtual] Expansion ROM at bff00000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: radeon
	Kernel modules: radeon


Are these enough?
Thank you.
Comment 5 Yichao Yu 2011-05-07 21:10:04 UTC
sorry miss one
Archlinux x86_64
Comment 6 Milan Bouchet-Valat 2011-05-07 21:13:30 UTC
Ah, yes, when you suspend manually it doesn't lock, that's another bug, but I
can't find the report.

Yes, I think the different behavior when you press the suspend button is a bug
(probably in the gnome-power-manager<->Shell interaction). Note there are
reasons why the fade shouldn't happen (Bug 590865), but anyway it should be
consistent, so you can file a bug.


About the video card:
- Do you know which of the cards you're using? Have you tried with both?
- Can you give the version of the drivers, which are probably called something like xf86-video-intel and xf86-video-ati or xf86-video-nouveau (tell us which one is used too).
Comment 7 Yichao Yu 2011-05-07 21:25:56 UTC
Actually, I simply installed all the x video drivers and I haven't configured to use a particular card and I just let X to detect.

Really sorry about that, but I don't know how to find out~~~~~. I am still learning all these things and not yet an expert.
Comment 8 Milan Bouchet-Valat 2011-05-07 21:27:07 UTC
You can attach /var/log/Xorg.0.log, it will say it all.
Comment 9 Yichao Yu 2011-05-07 21:31:08 UTC
Created attachment 187436 [details]
x log
Comment 10 Milan Bouchet-Valat 2011-05-07 21:38:42 UTC
OK, so you're using the Intel card, and in Arch the driver seems to be 2.15.0-1.
Comment 11 Yichao Yu 2011-05-07 21:40:00 UTC
Thanks
Comment 12 Rui Matos 2011-06-05 11:22:56 UTC
Please don't report more than one issue in a single bug report.

The first issue is bug 650464.

The second issue is described clearly by bug 651874 so I'm marking this as duplicate.

*** This bug has been marked as a duplicate of bug 651874 ***