Summary: | gnome-base/gdm-3.8: suspend doesn't work | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mark R. Pariente <markpariente> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | azpegath, poncho, systemd |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugzilla.gnome.org/show_bug.cgi?id=704599 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 463242 |
Description
Mark R. Pariente
2013-05-05 18:21:42 UTC
Upgraded to systemd-203 (was using 202) and now suspend doesn't work neither in gdm nor in the user menu from within the session. Suspending with pm-suspend works fine, and with GNOME 3.6 both gdm and the user menu suspend worked. (In reply to comment #1) > Upgraded to systemd-203 (was using 202) and now suspend doesn't work neither > in gdm nor in the user menu from within the session. Suspending with > pm-suspend works fine, and with GNOME 3.6 both gdm and the user menu suspend > worked. No idea if something changed in 203 causing that regression :( (In reply to comment #1) > Upgraded to systemd-203 (was using 202) and now suspend doesn't work neither > in gdm nor in the user menu from within the session. probably bug 468998 So, upgrading to systemd-203-r1 did fix the suspend issue from the user menu, but even with 203-r1 suspend from gdm doesn't work. I noticed that upower has a "deprecated" use flag that was set in my case which makes it use pm-utils instead of systemd for suspending, so I emerged upower with -deprecated hoping that would solve my issue. Unfortunately it doesn't seem to matter, I still can't suspend the system from gdm by clicking the top right power icon and then selecting suspend. Power off / restart works though. Any pointers on how to go about debugging what is going on? Upgraded to gdm-3.8.1.1 to see if upstream fixed anything but still no dice, can't suspend stuff from gdm. I think the problem might be with upower. I'm trying to get upower suspend stuff working from the cmdline with dbus-send and I'm having trouble. Let me see if I can figure out what is going on here. It looks like this might be the same issue as bug 462476. So the weird thing is, manually triggering a suspend into upower works: # dbus-send --print-reply --system --dest=org.freedesktop.UPower /org/freedesktop/UPower org.freedesktop.UPower.Suspend (system is suspended) So it looks like the issue is NOT upower related, but somehow related to the way gdm is using upower. (In reply to comment #7) > So the weird thing is, manually triggering a suspend into upower works: > > # dbus-send --print-reply --system --dest=org.freedesktop.UPower > /org/freedesktop/UPower org.freedesktop.UPower.Suspend > > (system is suspended) > > So it looks like the issue is NOT upower related, but somehow related to the > way gdm is using upower. The issue with systemd-203 is fixed in systemd-204 according to upstream private mail. They added a new configuration file to control what "suspend" "hybrid-sleep" and "hibernate" would do, but defaulted to doing nothing if that file didn't exist. Upgraded to systemd-204 and gnome 3.8.2 but still can't suspend from GDM. I'm guessing this is a gdm issue (not fixed as of 3.8.1.1). BTW, this has been fixed, suspecting gdm-3.8.4 upgrade fixed it. (In reply to Mark R. Pariente from comment #10) > BTW, this has been fixed, suspecting gdm-3.8.4 upgrade fixed it. Good to hear. |