On 02/07/2015 12:54 PM, Yamaban wrote:
On Sat, 7 Feb 2015 21:34, John Andersen
wrote: On 02/07/2015 12:01 PM, Yamaban wrote:
yOn Sat, 7 Feb 2015 20:44, John Andersen
wrote: On 02/07/2015 08:51 AM, Freek de Kruijf wrote:
Op zaterdag 7 februari 2015 16:33:16 schreef Aaron Digulla:
Hi,
I installed a bunch of patches and updated packages yesterday. I could hibernate yesterday evening but couldn't resume (Linux would just boot normally).
When I now try to hibernate, nothing happens.
I tried (as root):
# /usr/bin/powersave --suspend-to-disk Error org.freedesktop.DBus.Error.UnknownMethod: Method "Hibernate" with signature "" on interface "org.freedesktop.UPower" doesn't exist
I also tried (as root)
# /usr/sbin/pm-hibernate
which doesn't do anything anymore. That worked yesterday.
Did you look at: # systemctl status dbus-org.freedesktop.login1.services It should show: active (running)
Hmmm, out of curiosity I decided to check mine:
poulsbo:~ # systemctl status dbus-org.freedesktop.login1.services dbus-org.freedesktop.login1.services.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
And yet suspend/resume works just fine. (I tried it again just before posting this). So not only can I NOT see the original problem, I can't even see the supposed fix! Feeling left out over here guys.... ;-)
13.2.
Was there a kernel-update or an other cause to rebuild the initrd? That would cause pm-hibernate to abort, because there would be no working wakeup environment.
If this problem still exists after a normal (full) reboot, then there is a real cause to investigate.
- Yamaban.
Fedora lists suggest this is caused by glibc patches. https://bugzilla.redhat.com/show_bug.cgi?id=1085846
Yet as you suggest, zypper ps shows some things running that have been deleted, although none of them look like they are involved. so I am going to reboot and see if that solves the problem of no running dbus-org.freedesktop.login1.services
At my system, the file /usr/lib/systemd/system/dbus-org.freedesktop.login1.service is just a symlink to systemd-logind.service
So if "systemctl status dbus-org.freedesktop.login1.service" says no-good, check that first, and if it is a link at your system, too, try "systemctl status systemd-logind.service" at my system this gives back an "ok, working".
And, FYI, a change / update of glibc breaks hibernate until the next full reboot, at minimum.
- Yamaban.
After a reboot, the link did exist. and the systemctl command worked, but I never see the "ok working". Rather I see the following spew, which I translate as "ok working"
sa@poulsbo:~> systemctl status systemd-logind.service systemd-logind.service - Login Service Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static) Active: active (running) since Sat 2015-02-07 13:47:41 PST; 6min ago Docs: man:systemd-logind.service(8) man:logind.conf(5) http://www.freedesktop.org/wiki/Software/systemd/logind http://www.freedesktop.org/wiki/Software/systemd/multiseat Main PID: 877 (systemd-logind) Status: "Processing requests..." CGroup: /system.slice/systemd-logind.service └─877 /usr/lib/systemd/systemd-logind
And sure enough # /usr/sbin/pm-hibernate works now to hibernate and shut down. (And, suspend (lid close) still works too, as does And Lid open (resume) after suspend). However power on (after hibernate) goes through a couple of quick lines on the console, then quickly goes to black screen, and I am totally screwed at that point because it just hangs, all disk activity ceases, the machine is running but I have no idea what it wants me to do. Does it want mu login password, does it want my encrypted home directory password? I have no clue because screen is totally black. Power off (is my only option, and the hibernated session is lost). -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org