I'm getting it when trying to hibernate, on a new computer of mine. The claimed source of the bug is xfsm-shutdown-h: ``` Nov 09 21:40:53 vn971zivver audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@1-1735-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? a> Nov 09 21:40:54 vn971zivver systemd-coredump[1736]: Process 1731 (xfsm-shutdown-h) of user 0 dumped core. Stack trace of thread 1731: #0 0x00006774b2ba5f41 __libc_free (libc.so.6) #1 0x00006774b2d619e3 g_error_free (libglib-2.0.so.0) #2 0x00000d70ec4e2dd9 n/a (xfsm-shutdown-helper) #3 0x00000d70ec4e2bc8 n/a (xfsm-shutdown-helper) #4 0x00006774b2b44223 __libc_start_main (libc.so.6) #5 0x00000d70ec4e2caa n/a (xfsm-shutdown-helper) ``` I was not able to compile a debug build yet because there's some unknown issue preventing me from doing it, but that's probably a separate story. Note: the actual version specified by ArchLinux is 4.12.1, which isn't on this list. I've used "4.12.0" as a number that feels the closest. Any ideas on where it might come from or how to fix it? Maybe I should raise the issue of "not compiling" first?
As was explained in the IRC, version "4.12.1" is fine. The core dump crash question still holds.
Same backtrace from https://bugzilla.xfce.org/show_bug.cgi?id=13699 . Run: $ gdbus call --system --dest org.freedesktop.login1 --object-path /org/freedesktop/login1 --method org.freedesktop.login1.Manager.CanHibernate What is returned? Possible solution in https://bugzilla.xfce.org/show_bug.cgi?id=14707 .
@Marcos, I get this when I run the DBUS command: ('na',) Does this sound like relevant?
Yes. logind says hibernation is not supported on your system. xfce4-session should not offer the "Hibernate" button at all. Duplicate of bug #13699 . If your machine used to hibernate before, you are probably being hit by https://github.com/systemd/systemd/issues/10613 .
Marcos, thanks. // I wonder why I don't have hibernate working though. I have the GRUB "resume" entry for it, and the "resume" hook in mkinitcpio.conf. But I guess this is totally offtopic to the issue raised here. Thanks again.
Marcos, ah, though you've just linked the issue that could be relevant. Indeed it probably is. I've first got my hands on the new notebook about 5 days ago, so I can't tell if it's broken around those dates or not though.
Closing as dup *** This bug has been marked as a duplicate of bug 13699 ***