<![CDATA[Dev1 Galaxy Forum / Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?id=4944 Wed, 23 Mar 2022 17:41:31 +0000 FluxBB <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35356#p35356 Thanks for your suggestions: unhappily I followed them and things stay as before.

I think that the grub error may just mean that no saved state was found in the swap area.

As to the permissions to use pm-suspend and others, this was probably already solved because the options for suspending and hibernating are now available in the logout actions that slim presents. Moreover I have also been trying to suspend as root and the result is the same.

Just for the record I made an apt-get update and dist-upgrade as it could be there were some new things missing but nothing came of it,

]]> Wed, 23 Mar 2022 17:41:31 +0000 https://dev1galaxy.org/viewtopic.php?pid=35356#p35356 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35351#p35351 Try this line instead in /etc/default/grub (and of course then run update-grub).

GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=UUID=7ade7026-f504-4f6e-a768-105e4a93b05e"

This is how I specify a swap partition for hibernation.

The change to your error message when you tried to do this with incorrect syntax confirms that your PC is attempting to hibernate not suspend.
It's unclear why this is happening (doesn't happen on mine unless I ask for hibernation).

Have already tried 

sudo /usr/sbin/pm-suspend

to get suspend?

On my PC I have put /usr/sbin/pm-suspend, /usr/sbin/pm-hibernate in /etc/sudoers.d/Suspend to allow me to run it passwordless.

username   ALL = NOPASSWD: /usr/sbin/pm-hibernate
username   ALL = NOPASSWD: /usr/sbin/pm-suspend

I then have these as options, along with Quit, Restart, Logout and Screenlock in a panel applet 'Shutdown Menu with Icons'. However this is under Cinnamon not XFCE.

]]> Wed, 23 Mar 2022 13:49:35 +0000 https://dev1galaxy.org/viewtopic.php?pid=35351#p35351 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35349#p35349 By using blkid --fs I found out that the swap uuid, then edited  /etc/default/grub to change the GRUB_CMDLINE_LINUX_DEFAULT:

GRUB_CMDLINE_LINUX_DEFAULT="resume=7ade7026-f504-4f6e-a768-105e4a93b05e quiet"

After a suspend and hard reset, GRUB complained "Invalid resume device". A new suspend behaved as before,

I found out this Gentoo page https://wiki.gentoo.org/wiki/Suspend_and_hibernate but I am not sure if anything there is what is needed in Devuan. I tried

cat /sys/power/state
 freeze mem disk

I don't know if this output is the one to be expected.

]]> Wed, 23 Mar 2022 10:34:44 +0000 https://dev1galaxy.org/viewtopic.php?pid=35349#p35349 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35347#p35347

fsmithred wrote:
I ran fsck from another system on the same machine and it fixed some orphaned inodes.

...

Have you tried running loginctl suspend to see if it acts differently?

The hard resets I have made after suspends being blocked led to disk journals being recovered but no other problems. So I thought there was no need for
fsck's: am I wrong?

I tried loginctl suspend and the behaviour is the same of using the other methods.

Marjorie wrote:
Have you specified the swap partition where you are saving the hibernation image?

If the system is hibernating and you really just want it to suspend then you need to track down where PM is making the 'wrong' call.

My grub.cfg has no such field (neither before nor after the upgrade). I will try and add one tomorrow morning first thing and will report.

In fact the syslog has a lot of entries about hibernation but I am sure I am asking for a suspend not a hibernation. As I wrote in a previous post this
behaviour happens also with the command pm-suspend.

]]> Tue, 22 Mar 2022 21:20:36 +0000 https://dev1galaxy.org/viewtopic.php?pid=35347#p35347 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35336#p35336 migf, your last syslog listing relates to hibernating (to disk), not suspending to memory.

Have you specified the swap partition where you are saving the hibernation image?

On the linux /boot/vmlinuz-5.10.0-12-amd64 line in your /boot/grub/grub-cfg you need an entry such as resume=UUID=1e9fb381-0966-401f-b649-7958a6df7307. Obviously the UUID for the swap area you use will be different on your PC to the one I use on mine.

[edit] If the system is hibernating and you really just want it to suspend then you need to track down where PM is making the 'wrong' call.

]]> Mon, 21 Mar 2022 21:15:48 +0000 https://dev1galaxy.org/viewtopic.php?pid=35336#p35336 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35335#p35335 My syslog looks like #2. It seems that a lot of my entries for going into sleep have the same timestamp as the entries coming out of sleep. Not sure what to make of that. Or of your #3 paste.

During my testing, I did have occasion to not wake up from sleep. I had other problems after reboot, like not being able to drop to console with ctrl-alt-F2. I ran fsck from another system on the same machine and it fixed some orphaned inodes. That's probably not your problem, but might be worth trying fsck from a live-usb.

Have you tried running loginctl suspend to see if it acts differently? On mine it does the same as pm-suspend.

]]> Mon, 21 Mar 2022 18:52:05 +0000 https://dev1galaxy.org/viewtopic.php?pid=35335#p35335 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35331#p35331 I was replying and was logged out... So I will restart and will be brief.

Ok to staying in this thread.

This is a desktop, I used the keyboard to awake a suspend.

I had saved pm-suspend.logs from before and after the upgrade. The main difference between them is that the 2nd entry below is now missing (the error in the 3rd appears in both) and there is no awake:

Running hook /usr/lib/pm-utils/sleep.d/50unload_alx suspend suspend:
/usr/lib/pm-utils/sleep.d/50unload_alx suspend suspend: success.

Running hook /usr/lib/pm-utils/sleep.d/55wicd suspend suspend:
/usr/lib/pm-utils/sleep.d/55wicd suspend suspend: success.

Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend:
Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory
/usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend: success.

What appears after the PM entries in the syslogs are completely different and I cannot make out what the problem is. So I post them below.

Before the upgrade:

Mar 14 14:06:13 khashkol kernel: [15740.516318] PM: suspend entry (deep)
Mar 14 14:37:52 khashkol rtkit-daemon[3171]: The canary thread is apparently starving. Taking action.
Mar 14 14:37:52 khashkol rtkit-daemon[3171]: Demoting known real-time threads.
Mar 14 14:37:52 khashkol kernel: [15740.516321] PM: Syncing filesystems ... done.
Mar 14 14:37:52 khashkol kernel: [15740.741424] Freezing user space processes ... (elapsed 0.001 seconds) done.
Mar 14 14:37:52 khashkol kernel: [15740.742981] OOM killer disabled.
Mar 14 14:37:52 khashkol kernel: [15740.742982] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Mar 14 14:37:52 khashkol kernel: [15740.744216] Suspending console(s) (use no_console_suspend to debug)
Mar 14 14:37:52 khashkol kernel: [15740.764435] sd 1:0:0:0: [sda] Synchronizing SCSI cache
Mar 14 14:37:52 khashkol kernel: [15740.764446] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
Mar 14 14:37:52 khashkol kernel: [15740.764450] sd 5:0:0:0: [sdc] Synchronizing SCSI cache
Mar 14 14:37:52 khashkol kernel: [15740.764556] sd 3:0:0:0: [sdb] Stopping disk
Mar 14 14:37:52 khashkol kernel: [15740.764600] sd 5:0:0:0: [sdc] Stopping disk
Mar 14 14:37:52 khashkol kernel: [15740.764602] sd 1:0:0:0: [sda] Stopping disk
Mar 14 14:37:52 khashkol kernel: [15745.596679] ACPI: Preparing to enter system sleep state S3
Mar 14 14:37:52 khashkol kernel: [15745.597589] PM: Saving platform NVS memory
Mar 14 14:37:52 khashkol kernel: [15745.597751] Disabling non-boot CPUs ...
Mar 14 14:37:52 khashkol kernel: [15745.613549] smpboot: CPU 1 is now offline
Mar 14 14:37:52 khashkol kernel: [15745.630250] smpboot: CPU 2 is now offline
Mar 14 14:37:52 khashkol kernel: [15745.645691] smpboot: CPU 3 is now offline
Mar 14 14:37:52 khashkol kernel: [15745.646907] ACPI: Low-level resume complete
Mar 14 14:37:52 khashkol kernel: [15745.646924] PM: Restoring platform NVS memory
Mar 14 14:37:52 khashkol kernel: [15745.647317] Enabling non-boot CPUs ...
Mar 14 14:37:52 khashkol kernel: [15745.647366] x86: Booting SMP configuration:
Mar 14 14:37:52 khashkol kernel: [15745.647366] smpboot: Booting Node 0 Processor 1 APIC 0x4
Mar 14 14:37:52 khashkol kernel: [15745.649739]  cache: parent cpu1 should not be sleeping
Mar 14 14:37:52 khashkol kernel: [15745.650057] CPU1 is up
Mar 14 14:37:52 khashkol kernel: [15745.650086] smpboot: Booting Node 0 Processor 2 APIC 0x1
Mar 14 14:37:52 khashkol kernel: [15745.652417]  cache: parent cpu2 should not be sleeping
Mar 14 14:37:52 khashkol kernel: [15745.652843] CPU2 is up
Mar 14 14:37:52 khashkol kernel: [15745.652871] smpboot: Booting Node 0 Processor 3 APIC 0x5
Mar 14 14:37:52 khashkol kernel: [15745.655205]  cache: parent cpu3 should not be sleeping
Mar 14 14:37:52 khashkol kernel: [15745.655521] CPU3 is up
Mar 14 14:37:52 khashkol kernel: [15745.657544] ACPI: Waking up from system sleep state S3

After

Mar 17 13:48:32 khashkol kernel: [  284.573893] PM: suspend entry (deep)
Mar 17 13:50:38 khashkol kernel: [    0.000000] Linux version 5.10.0-12-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.103-1 (2022-03-07)
Mar 17 13:50:38 khashkol kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-12-amd64 root=UUID=6e72fa3d-e9d3-4047-ace8-baec24ee7478 ro quiet
Mar 17 13:50:38 khashkol kernel: [    0.000000] x86/fpu: x87 FPU will use FXSAVE
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-provided physical RAM map:
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000094bff] usable
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x0000000000094c00-0x000000000009ffff] reserved
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e4000-0x00000000000fffff] reserved
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bf77ffff] usable
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000bf780000-0x00000000bf78dfff] ACPI data
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000bf78e000-0x00000000bf7cffff] ACPI NVS
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000bf7d0000-0x00000000bf7dffff] reserved
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000bf7ed000-0x00000000bfffffff] reserved
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x00000000ffb00000-0x00000000ffffffff] reserved
Mar 17 13:50:38 khashkol kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000013bffffff] usable
Mar 17 13:50:38 khashkol kernel: [    0.000000] NX (Execute Disable) protection: active
Mar 17 13:50:38 khashkol kernel: [    0.000000] SMBIOS 2.6 present.
Mar 17 13:50:38 khashkol kernel: [    0.000000] DMI: Acer Aspire M3910/Aspire M3910, BIOS P01-A3         05/17/2010
Mar 17 13:50:38 khashkol kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Mar 17 13:50:38 khashkol kernel: [    0.000000] tsc: Detected 3191.791 MHz processor
Mar 17 13:50:38 khashkol kernel: [    0.003235] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Mar 17 13:50:38 khashkol kernel: [    0.003238] e820: remove [mem 0x000a0000-0x000fffff] usable
Mar 17 13:50:38 khashkol kernel: [    0.003244] last_pfn = 0x13c000 max_arch_pfn = 0x400000000
Mar 17 13:50:38 khashkol kernel: [    0.003248] MTRR default type: uncachable
Mar 17 13:50:38 khashkol kernel: [    0.003249] MTRR fixed ranges enabled:
Mar 17 13:50:38 khashkol kernel: [    0.003251]   00000-9FFFF write-back
Mar 17 13:50:38 khashkol kernel: [    0.003252]   A0000-BFFFF uncachable
Mar 17 13:50:38 khashkol kernel: [    0.003253]   C0000-CFFFF write-protect
Mar 17 13:50:38 khashkol kernel: [    0.003254]   D0000-DFFFF uncachable
Mar 17 13:50:38 khashkol kernel: [    0.003254]   E0000-E7FFF write-through
Mar 17 13:50:38 khashkol kernel: [    0.003255]   E8000-FFFFF write-protect
Mar 17 13:50:38 khashkol kernel: [    0.003256] MTRR variable ranges enabled:
Mar 17 13:50:38 khashkol kernel: [    0.003258]   0 base 13C000000 mask FFC000000 uncachable
Mar 17 13:50:38 khashkol kernel: [    0.003259]   1 base 000000000 mask F00000000 write-back
Mar 17 13:50:38 khashkol kernel: [    0.003260]   2 base 100000000 mask FC0000000 write-back
Mar 17 13:50:38 khashkol kernel: [    0.003261]   3 base 0C0000000 mask FC0000000 uncachable
Mar 17 13:50:38 khashkol kernel: [    0.003262]   4 disabled
Mar 17 13:50:38 khashkol kernel: [    0.003263]   5 disabled
Mar 17 13:50:38 khashkol kernel: [    0.003263]   6 disabled
Mar 17 13:50:38 khashkol kernel: [    0.003264]   7 disabled
Mar 17 13:50:38 khashkol kernel: [    0.004161] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Mar 17 13:50:38 khashkol kernel: [    0.004469] e820: update [mem 0xc0000000-0xffffffff] usable ==> reserved
Mar 17 13:50:38 khashkol kernel: [    0.004476] last_pfn = 0xbf780 max_arch_pfn = 0x400000000
Mar 17 13:50:38 khashkol kernel: [    0.013458] found SMP MP-table at [mem 0x000ff780-0x000ff78f]
Mar 17 13:50:38 khashkol kernel: [    0.017237] RAMDISK: [mem 0x349dd000-0x364e5fff]
Mar 17 13:50:38 khashkol kernel: [    0.017241] ACPI: Early table checksum verification disabled
Mar 17 13:50:38 khashkol kernel: [    0.017245] ACPI: RSDP 0x00000000000FA3E0 000014 (v00 ACPIAM)
Mar 17 13:50:38 khashkol kernel: [    0.017250] ACPI: RSDT 0x00000000BF780000 000048 (v01 ACRSYS ACRPRDCT 20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017256] ACPI: FACP 0x00000000BF780200 000084 (v01 ACRSYS FACP1139 20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017262] ACPI: DSDT 0x00000000BF7805E0 0068E4 (v01 1AEIP  1AEIP012 00000012 INTL 20051117)
Mar 17 13:50:38 khashkol kernel: [    0.017266] ACPI: FACS 0x00000000BF78E000 000040
Mar 17 13:50:38 khashkol kernel: [    0.017269] ACPI: APIC 0x00000000BF780390 00008C (v01 ACRSYS APIC1139 20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017273] ACPI: MCFG 0x00000000BF780420 00003C (v01 ACRSYS OEMMCFG  20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017277] ACPI: SLIC 0x00000000BF780460 000176 (v01 ACRSYS ACRPRDCT 20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017281] ACPI: OEMB 0x00000000BF78E040 000079 (v01 ACRSYS OEMB1139 20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017285] ACPI: HPET 0x00000000BF78A5E0 000038 (v01 ACRSYS OEMHPET  20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017288] ACPI: ASF! 0x00000000BF78A620 000099 (v32 LEGEND I865PASF 00000001 INTL 20051117)
Mar 17 13:50:38 khashkol kernel: [    0.017293] ACPI: AWMI 0x00000000BF78E0C0 00004E (v01 ACRSYS OEMB1139 20100517 MSFT 00000097)
Mar 17 13:50:38 khashkol kernel: [    0.017296] ACPI: SSDT 0x00000000BF78FB60 000363 (v01 DpgPmm CpuPm    00000012 INTL 20051117)
Mar 17 13:50:38 khashkol kernel: [    0.017300] ACPI: Reserving FACP table memory at [mem 0xbf780200-0xbf780283]
Mar 17 13:50:38 khashkol kernel: [    0.017301] ACPI: Reserving DSDT table memory at [mem 0xbf7805e0-0xbf786ec3]
Mar 17 13:50:38 khashkol kernel: [    0.017302] ACPI: Reserving FACS table memory at [mem 0xbf78e000-0xbf78e03f]
Mar 17 13:50:38 khashkol kernel: [    0.017303] ACPI: Reserving APIC table memory at [mem 0xbf780390-0xbf78041b]
Mar 17 13:50:38 khashkol kernel: [    0.017304] ACPI: Reserving MCFG table memory at [mem 0xbf780420-0xbf78045b]
Mar 17 13:50:38 khashkol kernel: [    0.017305] ACPI: Reserving SLIC table memory at [mem 0xbf780460-0xbf7805d5]
Mar 17 13:50:38 khashkol kernel: [    0.017306] ACPI: Reserving OEMB table memory at [mem 0xbf78e040-0xbf78e0b8]
Mar 17 13:50:38 khashkol kernel: [    0.017307] ACPI: Reserving HPET table memory at [mem 0xbf78a5e0-0xbf78a617]
Mar 17 13:50:38 khashkol kernel: [    0.017308] ACPI: Reserving ASF! table memory at [mem 0xbf78a620-0xbf78a6b8]
Mar 17 13:50:38 khashkol kernel: [    0.017309] ACPI: Reserving AWMI table memory at [mem 0xbf78e0c0-0xbf78e10d]
Mar 17 13:50:38 khashkol kernel: [    0.017310] ACPI: Reserving SSDT table memory at [mem 0xbf78fb60-0xbf78fec2]
Mar 17 13:50:38 khashkol kernel: [    0.017319] ACPI: Local APIC address 0xfee00000
Mar 17 13:50:38 khashkol kernel: [    0.017365] No NUMA configuration found
Mar 17 13:50:38 khashkol kernel: [    0.017366] Faking a node at [mem 0x0000000000000000-0x000000013bffffff]
Mar 17 13:50:38 khashkol kernel: [    0.017379] NODE_DATA(0) allocated [mem 0x13bfd3000-0x13bffcfff]
Mar 17 13:50:38 khashkol kernel: [    0.017870] Zone ranges:
Mar 17 13:50:38 khashkol kernel: [    0.017871]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
Mar 17 13:50:38 khashkol kernel: [    0.017873]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
Mar 17 13:50:38 khashkol kernel: [    0.017875]   Normal   [mem 0x0000000100000000-0x000000013bffffff]
Mar 17 13:50:38 khashkol kernel: [    0.017876]   Device   empty
Mar 17 13:50:38 khashkol kernel: [    0.017878] Movable zone start for each node
Mar 17 13:50:38 khashkol kernel: [    0.017880] Early memory node ranges
Mar 17 13:50:38 khashkol kernel: [    0.017881]   node   0: [mem 0x0000000000001000-0x0000000000093fff]
Mar 17 13:50:38 khashkol kernel: [    0.017883]   node   0: [mem 0x0000000000100000-0x00000000bf77ffff]
Mar 17 13:50:38 khashkol kernel: [    0.017884]   node   0: [mem 0x0000000100000000-0x000000013bffffff]
Mar 17 13:50:38 khashkol kernel: [    0.017886] Initmem setup node 0 [mem 0x0000000000001000-0x000000013bffffff]
Mar 17 13:50:38 khashkol kernel: [    0.017888] On node 0 totalpages: 1029907
Mar 17 13:50:38 khashkol kernel: [    0.017889]   DMA zone: 64 pages used for memmap
Mar 17 13:50:38 khashkol kernel: [    0.017890]   DMA zone: 21 pages reserved
Mar 17 13:50:38 khashkol kernel: [    0.017891]   DMA zone: 3987 pages, LIFO batch:0
Mar 17 13:50:38 khashkol kernel: [    0.017893]   DMA32 zone: 12190 pages used for memmap
Mar 17 13:50:38 khashkol kernel: [    0.017894]   DMA32 zone: 780160 pages, LIFO batch:63
Mar 17 13:50:38 khashkol kernel: [    0.017895]   Normal zone: 3840 pages used for memmap
Mar 17 13:50:38 khashkol kernel: [    0.017896]   Normal zone: 245760 pages, LIFO batch:63
Mar 17 13:50:38 khashkol kernel: [    0.017900] On node 0, zone DMA: 1 pages in unavailable ranges
Mar 17 13:50:38 khashkol kernel: [    0.017945] On node 0, zone DMA: 108 pages in unavailable ranges
Mar 17 13:50:38 khashkol kernel: [    0.027509] On node 0, zone Normal: 2176 pages in unavailable ranges
Mar 17 13:50:38 khashkol kernel: [    0.027789] On node 0, zone Normal: 16384 pages in unavailable ranges
Mar 17 13:50:38 khashkol kernel: [    0.027910] ACPI: PM-Timer IO Port: 0x808
Mar 17 13:50:38 khashkol kernel: [    0.027913] ACPI: Local APIC address 0xfee00000
Mar 17 13:50:38 khashkol kernel: [    0.027930] IOAPIC[0]: apic_id 6, version 32, address 0xfec00000, GSI 0-23
Mar 17 13:50:38 khashkol kernel: [    0.027932] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Mar 17 13:50:38 khashkol kernel: [    0.027935] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Mar 17 13:50:38 khashkol kernel: [    0.027936] ACPI: IRQ0 used by override.
Mar 17 13:50:38 khashkol kernel: [    0.027937] ACPI: IRQ9 used by override.
Mar 17 13:50:38 khashkol kernel: [    0.027940] Using ACPI (MADT) for SMP configuration information
Mar 17 13:50:38 khashkol kernel: [    0.027942] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Mar 17 13:50:38 khashkol kernel: [    0.027948] smpboot: Allowing 8 CPUs, 4 hotplug CPUs
Mar 17 13:50:38 khashkol kernel: [    0.027966] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Mar 17 13:50:38 khashkol kernel: [    0.027968] PM: hibernation: Registered nosave memory: [mem 0x00094000-0x00094fff]
Mar 17 13:50:38 khashkol kernel: [    0.027968] PM: hibernation: Registered nosave memory: [mem 0x00095000-0x0009ffff]
Mar 17 13:50:38 khashkol kernel: [    0.027969] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000e3fff]
Mar 17 13:50:38 khashkol kernel: [    0.027970] PM: hibernation: Registered nosave memory: [mem 0x000e4000-0x000fffff]
Mar 17 13:50:38 khashkol kernel: [    0.027972] PM: hibernation: Registered nosave memory: [mem 0xbf780000-0xbf78dfff]
Mar 17 13:50:38 khashkol kernel: [    0.027973] PM: hibernation: Registered nosave memory: [mem 0xbf78e000-0xbf7cffff]
Mar 17 13:50:38 khashkol kernel: [    0.027974] PM: hibernation: Registered nosave memory: [mem 0xbf7d0000-0xbf7dffff]
Mar 17 13:50:38 khashkol kernel: [    0.027974] PM: hibernation: Registered nosave memory: [mem 0xbf7e0000-0xbf7ecfff]
Mar 17 13:50:38 khashkol kernel: [    0.027975] PM: hibernation: Registered nosave memory: [mem 0xbf7ed000-0xbfffffff]
Mar 17 13:50:38 khashkol kernel: [    0.027976] PM: hibernation: Registered nosave memory: [mem 0xc0000000-0xfedfffff]
Mar 17 13:50:38 khashkol kernel: [    0.027977] PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Mar 17 13:50:38 khashkol kernel: [    0.027978] PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xffafffff]
Mar 17 13:50:38 khashkol kernel: [    0.027978] PM: hibernation: Registered nosave memory: [mem 0xffb00000-0xffffffff]
Mar 17 13:50:38 khashkol kernel: [    0.027981] [mem 0xc0000000-0xfedfffff] available for PCI devices
Mar 17 13:50:38 khashkol kernel: [    0.027982] Booting paravirtualized kernel on bare hardware
Mar 17 13:50:38 khashkol kernel: [    0.027985] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Mar 17 13:50:38 khashkol kernel: [    0.032311] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
Mar 17 13:50:38 khashkol kernel: [    0.032697] percpu: Embedded 58 pages/cpu s200536 r8192 d28840 u262144
Mar 17 13:50:38 khashkol kernel: [    0.032706] pcpu-alloc: s200536 r8192 d28840 u262144 alloc=1*2097152
Mar 17 13:50:38 khashkol kernel: [    0.032708] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
Mar 17 13:50:38 khashkol kernel: [    0.032748] Built 1 zonelists, mobility grouping on.  Total pages: 1013792
Mar 17 13:50:38 khashkol kernel: [    0.032749] Policy zone: Normal
Mar 17 13:50:38 khashkol kernel: [    0.032751] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-12-amd64 root=UUID=6e72fa3d-e9d3-4047-ace8-baec24ee7478 ro quiet
]]> Mon, 21 Mar 2022 14:02:27 +0000 https://dev1galaxy.org/viewtopic.php?pid=35331#p35331 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35286#p35286 I vote for staying in this thread. These things may all be related, and someone else might run into similar problems.

Is it a laptop? (Do we need to deal with lid switch and power-manager?)

Look in /var/log/pm-suspend.log to see information related to entering and leaving suspend state.
Look in /var/log/syslog for info about leaving suspend state. Find where it says PM: suspend entry (deep) to see what's happening when you leave suspend. I could not find anytihing in syslog to show when it went into suspend. (And I started with an empty syslog, so there's no way I missed it.)

]]> Sat, 19 Mar 2022 13:02:21 +0000 https://dev1galaxy.org/viewtopic.php?pid=35286#p35286 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35276#p35276 Thank you for all your recent posts!

alexkemp wrote:

sudo apt install libpam-elogind

In fact this package was already installed, so I installed 

libpolkit-gobject-elogind-1-0

and the two console-kit related packages were removed as fsmithred mentioned.

fsmithred wrote:
If you're still having trouble with suspend after you get the packages all straightened out, you might take a look at this page: https://wiki.ubuntu.com/DebuggingKernelSuspend

I read it and some stuiff linked from it but I couldn't do anything: they say one should trace what happens at the kernel level assuming the file 

/sys/power/pm-trace

exists what is not the case here.

I also found some pages that mentioned changes that could be made on 

/proc/acpi/awake

that here has 

Device  S-state   Status   Sysfs node
P0P1      S4    *disabled  pci:0000:00:01.0
P0P3      S4    *disabled
P0P4      S4    *disabled
P0P5      S4    *disabled
P0P6      S4    *disabled
BR1E      S4    *disabled  pci:0000:00:1e.0
PS2K      S4    *enabled   pnp:00:02
                *disabled  serio:serio0
PS2M      S4    *disabled  pnp:00:03
BR20      S4    *disabled  pci:0000:00:1c.0
BR21      S4    *disabled
BR22      S4    *disabled  pci:0000:00:1c.2
BR23      S4    *disabled
BR24      S4    *disabled
BR25      S4    *disabled
BR26      S4    *disabled
BR27      S4    *disabled
EUSB      S3    *enabled   pci:0000:00:1d.0
USB0      S3    *disabled
USB1      S3    *disabled
USB2      S3    *disabled
USB3      S3    *disabled
USBE      S3    *enabled   pci:0000:00:1a.0
USB4      S3    *disabled
USB5      S3    *disabled
USB6      S3    *disabled
GBE       S4    *disabled
SLPB      S4    *disabled

It may happen that EUSB stands for the keyboard but I don't know how to check that.

Should I start a new thread on this and mark the current thread as solved?

]]> Fri, 18 Mar 2022 18:04:21 +0000 https://dev1galaxy.org/viewtopic.php?pid=35276#p35276 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35269#p35269 If you're still having trouble with suspend after you get the packages all straightened out, you might take a look at this page: https://wiki.ubuntu.com/DebuggingKernelSuspend

Someone in IRC gave me the link. I haven't had a chance to read it, and I will be busy with other things today.

]]> Fri, 18 Mar 2022 11:54:00 +0000 https://dev1galaxy.org/viewtopic.php?pid=35269#p35269 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35267#p35267 migf wrote:

Do you think I should change to your configuration by installing libpolkit-gobject-elogind-1-0?

Short answer: yes (but see bottom).

Long Answer: read this thread (also with a Summary of the whole process)

tl;dr: sudo apt install libpam-elogind then restart multiple times until the sun shines again.

]]> Fri, 18 Mar 2022 08:59:26 +0000 https://dev1galaxy.org/viewtopic.php?pid=35267#p35267 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35251#p35251 consolekit and libpolkit-gobject-consolekit-1-0 should get removed when you install elogind and libpam-elogind. And libpolkit-gobject-elogind-1-0 will be installed automatically.

]]> Thu, 17 Mar 2022 21:27:46 +0000 https://dev1galaxy.org/viewtopic.php?pid=35251#p35251 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35250#p35250

alexkemp wrote:
Something else for you to look at.

Thanks! I compared with my list here and there is a difference here: I have consolekit and libpolkit-gobject-consolekit-1-0 instead of libpolkit-gobject-elogind-1-0. Do you think I should change to your configuration by installing libpolkit-gobject-elogind-1-0?

]]> Thu, 17 Mar 2022 21:18:42 +0000 https://dev1galaxy.org/viewtopic.php?pid=35250#p35250 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35249#p35249 migf wrote:

I tried to find in the syslog something about this but to no avail. Can this be a problem with the new linux kernel (5.10.0-12)?

Most likely not.

]]> Thu, 17 Mar 2022 20:50:00 +0000 https://dev1galaxy.org/viewtopic.php?pid=35249#p35249 <![CDATA[Re: Chimaera: xfce4 and changing to another window manager]]> https://dev1galaxy.org/viewtopic.php?pid=35246#p35246 migf wrote:

Can this be a problem with the new linux kernel (5.10.0-12)?

You also state that you are running Chimaera. Hmm. This is from my fully-updated system just now:

$ uname -r
5.16.0-0.bpo.3-amd64

$ cat /etc/apt/sources.list
deb http://deb.devuan.org/merged chimaera main non-free contrib
deb http://deb.devuan.org/merged chimaera-security main non-free contrib
deb http://deb.devuan.org/merged chimaera-updates main non-free contrib
deb http://deb.devuan.org/devuan chimaera-proposed-updates main non-free contrib
deb http://deb.devuan.org/merged chimaera-backports main non-free contrib

$ dpkg -l | egrep "logind|consolekit|libpam|policykit|polkit|upower"
rc  consolekit                            1.2.1-8                                amd64        framework for defining and tracking users, sessions and seats
ii  elogind                               246.10-2                               amd64        user, seat and session management daemon
ii  gir1.2-polkit-1.0                     0.105-31+devuan2                       amd64        GObject introspection data for PolicyKit
ii  libelogind0:amd64                     246.10-2                               amd64        user, seat and session management library
ii  libpam-cap:amd64                      1:2.44-1                               amd64        POSIX 1003.1e capabilities (PAM module)
ii  libpam-elogind:amd64                  246.10-2                               amd64        elogind PAM module
ii  libpam-gnome-keyring:amd64            3.36.0-1                               amd64        PAM module to unlock the GNOME keyring upon login
ii  libpam-modules:amd64                  1.4.0-9+deb11u1                        amd64        Pluggable Authentication Modules for PAM
ii  libpam-modules-bin                    1.4.0-9+deb11u1                        amd64        Pluggable Authentication Modules for PAM - helper binaries
ii  libpam-runtime                        1.4.0-9+deb11u1                        all          Runtime support for the PAM library
ii  libpam0g:amd64                        1.4.0-9+deb11u1                        amd64        Pluggable Authentication Modules library
ii  libpolkit-agent-1-0:amd64             0.105-31+devuan2                       amd64        PolicyKit Authentication Agent API
ii  libpolkit-gobject-1-0                 0.105-31+devuan2                       all          PolicyKit Authorization API
ii  libpolkit-gobject-elogind-1-0:amd64   0.105-31+devuan2                       amd64        PolicyKit Authorization API
ii  libpolkit-qt5-1-1:amd64               0.113.0-1                              amd64        PolicyKit-qt5-1 library
ii  libupower-glib1:amd64                 1:0.9.23-2+devuan1.3                   amd64        abstraction for power management - shared library
ii  libupower-glib3:amd64                 0.99.11-2                              amd64        abstraction for power management - shared library
ii  policykit-1                           0.105-31+devuan2                       amd64        framework for managing administrative policies and privileges
ii  policykit-1-gnome                     0.105-7                                amd64        authentication agent for PolicyKit
ii  upower                                1:0.9.23-2+devuan1.3                   amd64        abstraction for power management

Something else for you to look at.

]]> Thu, 17 Mar 2022 19:06:49 +0000 https://dev1galaxy.org/viewtopic.php?pid=35246#p35246