Xfce Forum

Sub domains
 

You are not logged in.

#1 2021-11-07 01:47:30

chakkerz
Member
Registered: 2021-11-07
Posts: 4

Difference between Power Manager lid vs other hibernate

Hello there

I've been trying to enable hibernate on my Linux Mint 20.2 XFCE install. I guess when i custom partitioned that went out the window ... ANYWAY:

i added the bits to grub, updated systemd, updated polkit, powermanager says its authorised etc and shows all the options, but:
It works fine when i run `sudo systemctl hibernate`; it works fine if i go into the whiskers menu and click the power button (configured to hibernate). And then resume by pressing the powerbutton again.
It does not work if i just close the lid, and open it again after the fans have stopped.

The difference is that in the first instance i can see the system do the snapshot on screen, and in the second, because this Dell Inspiron 7590 turns on when the lid is lifted i don't press the button. As far as i can tell, everything works the system seems to resume but XFCE does not. I can CTRL+ALT+F1 and log in and see there was some issue:

Nov 07 11:15:02 nebula kernel: xfce4-session[5421]: segfault at 2c ip 000055b670179404 sp 00007ffed62bd368 error 4 in xfce4-session[55b6701620>
Nov 07 11:15:02 nebula kernel: Code: 48 83 c4 08 4c 89 e7 5d 41 5c e9 17 bb fe ff 0f 1f 80 00 00 00 00 48 83 c4 08 5d 41 5c c3 0f 1f 84 00 00 >
Nov 07 11:15:02 nebula systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Nov 07 11:15:02 nebula systemd[1]: Started Process Core Dump (PID 5505/UID 0).
Nov 07 11:15:02 nebula systemd-coredump[5506]: Process 5421 (xfce4-session) of user 1000 dumped core.
                                               
                                               Stack trace of thread 5421:
                                               #0  0x000055b670179404 xfsm_manager_get_shutdown_type (xfce4-session + 0x29404)
                                               #1  0x000055b67016ca5e n/a (xfce4-session + 0x1ca5e)
                                               #2  0x00007f0ab20a2c67 n/a (libgio-2.0.so.0 + 0x118c67)
                                               #3  0x00007f0ab20a2ed8 n/a (libgio-2.0.so.0 + 0x118ed8)
                                               #4  0x00007f0ab203ef49 n/a (libgio-2.0.so.0 + 0xb4f49)
                                               #5  0x00007f0ab203fb3d n/a (libgio-2.0.so.0 + 0xb5b3d)
                                               #6  0x00007f0ab209a3ef n/a (libgio-2.0.so.0 + 0x1103ef)
                                               #7  0x00007f0ab203ef49 n/a (libgio-2.0.so.0 + 0xb4f49)
                                               #8  0x00007f0ab203ef8d n/a (libgio-2.0.so.0 + 0xb4f8d)
                                               #9  0x00007f0ab1e5304e g_main_context_dispatch (libglib-2.0.so.0 + 0x5204e)
                                               #10 0x00007f0ab1e53400 n/a (libglib-2.0.so.0 + 0x52400)
                                               #11 0x00007f0ab1e536f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3)
                                               #12 0x00007f0ab26c237d gtk_main (libgtk-3.so.0 + 0x24e37d)
                                               #13 0x000055b670166461 main (xfce4-session + 0x16461)
                                               #14 0x00007f0ab1c110b3 __libc_start_main (libc.so.6 + 0x270b3)
                                               #15 0x000055b6701666fe _start (xfce4-session + 0x166fe)
                                               
                                               Stack trace of thread 5489:
                                               #0  0x00007f0ab1dec376 futex_wait_cancelable (libpthread.so.0 + 0x10376)
                                               #1  0x00007f0aae73fe7b n/a (iris_dri.so + 0x147e7b)
                                               #2  0x00007f0aae73fa7b n/a (iris_dri.so + 0x147a7b)
                                               #3  0x00007f0ab1de5609 start_thread (libpthread.so.0 + 0x9609)
                                               #4  0x00007f0ab1d0c293 __clone (libc.so.6 + 0x122293)
                                               
                                               Stack trace of thread 5495:
                                               #0  0x00007f0ab1d0589d syscall (libc.so.6 + 0x11b89d)
                                               #1  0x00007f0ab1ea0746 g_cond_wait_until (libglib-2.0.so.0 + 0x9f746)
                                               #2  0x00007f0ab1e23581 n/a (libglib-2.0.so.0 + 0x22581)
                                               #3  0x00007f0ab1e7d4ca n/a (libglib-2.0.so.0 + 0x7c4ca)
                                               #4  0x00007f0ab1e7cad1 n/a (libglib-2.0.so.0 + 0x7bad1)
                                               #5  0x00007f0ab1de5609 start_thread (libpthread.so.0 + 0x9609)
                                               #6  0x00007f0ab1d0c293 __clone (libc.so.6 + 0x122293)
                                               
                                               Stack trace of thread 5490:
                                               #0  0x00007f0ab1dec376 futex_wait_cancelable (libpthread.so.0 + 0x10376)
                                               #1  0x00007f0aae73fe7b n/a (iris_dri.so + 0x147e7b)
                                               #2  0x00007f0aae73fa7b n/a (iris_dri.so + 0x147a7b)
                                               #3  0x00007f0ab1de5609 start_thread (libpthread.so.0 + 0x9609)
                                               #4  0x00007f0ab1d0c293 __clone (libc.so.6 + 0x122293)
                                               
                                               Stack trace of thread 5492:
                                               #0  0x00007f0ab1dec376 futex_wait_cancelable (libpthread.so.0 + 0x10376)
                                               #1  0x00007f0aae73fe7b n/a (iris_dri.so + 0x147e7b)
                                               #2  0x00007f0aae73fa7b n/a (iris_dri.so + 0x147a7b)
                                               #3  0x00007f0ab1de5609 start_thread (libpthread.so.0 + 0x9609)
                                               #4  0x00007f0ab1d0c293 __clone (libc.so.6 + 0x122293)
                                               
                                               Stack trace of thread 5494:
                                               #0  0x00007f0ab1cffaff __GI___poll (libc.so.6 + 0x115aff)
                                               #1  0x00007f0ab1e5336e n/a (libglib-2.0.so.0 + 0x5236e)
                                               #2  0x00007f0ab1e536f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3)
                                               #3  0x00007f0ab20a8f8a n/a (libgio-2.0.so.0 + 0x11ef8a)
                                               #4  0x00007f0ab1e7cad1 n/a (libglib-2.0.so.0 + 0x7bad1)
                                               #5  0x00007f0ab1de5609 start_thread (libpthread.so.0 + 0x9609)
                                               #6  0x00007f0ab1d0c293 __clone (libc.so.6 + 0x122293)
                                               
                                               Stack trace of thread 5491:
                                               #0  0x00007f0ab1dec376 futex_wait_cancelable (libpthread.so.0 + 0x10376)
                                               #1  0x00007f0aae73fe7b n/a (iris_dri.so + 0x147e7b)
                                               #2  0x00007f0aae73fa7b n/a (iris_dri.so + 0x147a7b)
                                               #3  0x00007f0ab1de5609 start_thread (libpthread.so.0 + 0x9609)
                                               #4  0x00007f0ab1d0c293 __clone (libc.so.6 + 0x122293)
                                               
                                               Stack trace of thread 5493:
                                               #0  0x00007f0ab1cffaff __GI___poll (libc.so.6 + 0x115aff)
                                               #1  0x00007f0ab1e5336e n/a (libglib-2.0.so.0 + 0x5236e)
                                               #2  0x00007f0ab1e534a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3)
                                               #3  0x00007f0ab1e534f1 n/a (libglib-2.0.so.0 + 0x524f1)
                                               #4  0x00007f0ab1e7cad1 n/a (libglib-2.0.so.0 + 0x7bad1)
                                               #5  0x00007f0ab1de5609 start_thread (libpthread.so.0 + 0x9609)
                                               #6  0x00007f0ab1d0c293 __clone (libc.so.6 + 0x122293)
Nov 07 11:15:02 nebula systemd[1]: systemd-coredump@0-5505-0.service: Succeeded.
Nov 07 11:15:09 nebula acpid[802]: client 5384[1000:1000] has disconnected

I'm on Linux Mint 20.2 fully up 2 date, with:
Linux nebula 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Given this works three different ways and fails on the lid open close scenario, is there a chance to adjust power-manager to run the same command (say as the whisker's menu `xfce4-session-logout --hibernate`)?

Offline

#2 2021-11-07 10:54:47

ToZ
Moderator
From: Canada
Registered: 2011-06-02
Posts: 8,506

Re: Difference between Power Manager lid vs other hibernate

chakkerz wrote:

It works fine when i run `sudo systemctl hibernate`; it works fine if i go into the whiskers menu and click the power button (configured to hibernate). And then resume by pressing the powerbutton again.

By default, the xfce4-power-manager inhibits systemd/logind. See https://docs.xfce.org/xfce/xfce4-power- … er-manager. First, try running this command:

xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-hibernate-key -n -t bool -s true

...and then trying again.

It does not work if i just close the lid, and open it again after the fans have stopped.

Secondly, you might want to also try:

xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch -n -t bool -s true

...and also make sure that /etc/systemd/logind.conf has the correct action assigned to the HandleLidSwitch* parameters.

Nov 07 11:15:02 nebula kernel: xfce4-session[5421]: segfault at 2c ip 000055b670179404 sp 00007ffed62bd368 error 4 in xfce4-session[55b6701620>

See https://gitlab.xfce.org/xfce/xfce4-session/-/issues/54

Offline

#3 2021-11-08 21:05:37

chakkerz
Member
Registered: 2021-11-07
Posts: 4

Re: Difference between Power Manager lid vs other hibernate

Hmm, that (logind.conf) wasn't set up and i'll need to take more of a look at that, i added this:
chakkerz@nebula:~$ grep -v ^# /etc/systemd/logind.conf

[Login]
HandleLidSwitch=hibernate
HandleLidSwitchExternalPower=ignore
chakkerz@nebula:~$

but that didn't take care of it, there are more things commented out obviously so i need to take a look at that when i get a moment.

And ... i added a lock screen back since posting that, and now if i click hibernate in the whiskers menu i get a second unlock screen where my keyboard doesn't work (had selected screensaver to have its own lock screen ... oops, fixed)...

Eitherway, no joy just yet, but let me have more of a dig into logind.conf on the weekend.
Thanks for the pointer!

Last edited by chakkerz (2021-11-08 21:10:31)

Offline

#4 2022-01-10 22:08:42

chakkerz
Member
Registered: 2021-11-07
Posts: 4

Re: Difference between Power Manager lid vs other hibernate

Hey ToZ - thanks for that, Finally looked at it and found that i don't really want hibernate, but it appears i got suspend working. Nine times out of ten i'll just shut the laptop down anyway, but good to have that option smile.

ended up being:
HandleLidSwitch=suspend
HandleLidSwitchExternalPower=ignore
in /etc/systemd/logind.conf

And configuring power management.
Hibernate keeps misbehaving if triggered by closing the lid, but reading the man page for logind.conf would help me sort that out, seeing as i never used it cause it's too slow and a bit moronic to start back up i didn't bothe taking that to the nth degree.

Eitherway, thanks for your pointer!
chakkerz

Offline

Board footer

Powered by FluxBB