Welcome!
Important information
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.1 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

[Solved] Xfce Power Manager asking for password when unattended suspend times-out

Help for Current Versions of MX
Post Reply
User avatar
m_pav
Forum Guide
Forum Guide
Posts: 2707
Joined: Sun Aug 06, 2006 3:02 pm

[Solved] Xfce Power Manager asking for password when unattended suspend times-out

#1

Post by m_pav » Fri Mar 15, 2019 12:22 am

I've seen this twice in the last few days now so wondering if it's specific to my laptop or have others been experiencing it too. if you have, please chime in.

Events leading up to the issue:
Leave laptop running, walk away and do something else for an hour or so, come back to laptop, screen appears to be in PM, tap power button to wake, type password to unlock, message on screen saying pm-suspend requires root password to enter suspend and another message indicating request timed out (root password) and the process failed. I tried to snapshot the screen but the screenshooter refused to open, only path forward was to respond to the messages.
/var/log/messages relevant content below.

Code: Select all

Mar 15 16:55:51 mikepav kernel: [21202.839885] PM: suspend entry (deep)
Mar 15 16:55:51 mikepav kernel: [21202.839888] PM: Syncing filesystems ... done.
Mar 15 16:56:01 mikepav kernel: [21202.846792] (NULL device *): firmware: direct-loading firmware i915/skl_dmc_ver1_27.bin
Mar 15 16:56:01 mikepav kernel: [21202.846909] (NULL device *): firmware: direct-loading firmware intel/ibt-11-5.ddc
Mar 15 16:56:01 mikepav kernel: [21202.847204] (NULL device *): firmware: direct-loading firmware intel/ibt-11-5.sfi
Mar 15 16:56:01 mikepav kernel: [21202.847277] Freezing user space processes ... (elapsed 0.003 seconds) done.
Mar 15 16:56:01 mikepav kernel: [21202.850445] OOM killer disabled.
Mar 15 16:56:01 mikepav kernel: [21202.850447] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Mar 15 16:56:01 mikepav kernel: [21202.851666] Suspending console(s) (use no_console_suspend to debug)
Mar 15 16:56:01 mikepav kernel: [21203.010571] sd 1:0:0:0: [sda] Synchronizing SCSI cache
Mar 15 16:56:01 mikepav kernel: [21203.024282] sd 1:0:0:0: [sda] Stopping disk
Mar 15 16:56:01 mikepav kernel: [21203.059415] e1000e: EEE TX LPI TIMER: 00000011
Mar 15 16:56:01 mikepav kernel: [21203.670086] ACPI: EC: interrupt blocked
Mar 15 16:56:01 mikepav kernel: [21203.695913] ACPI: Preparing to enter system sleep state S3
Mar 15 16:56:01 mikepav kernel: [21203.701614] ACPI: EC: event blocked
Mar 15 16:56:01 mikepav kernel: [21203.701614] ACPI: EC: EC stopped
Mar 15 16:56:01 mikepav kernel: [21203.701615] PM: Saving platform NVS memory
Mar 15 16:56:01 mikepav kernel: [21203.701619] Disabling non-boot CPUs ...
Mar 15 16:56:01 mikepav kernel: [21203.708921] smpboot: CPU 1 is now offline
Mar 15 16:56:01 mikepav kernel: [21203.717047] smpboot: CPU 2 is now offline
Mar 15 16:56:01 mikepav kernel: [21203.726660] smpboot: CPU 3 is now offline
Mar 15 16:56:01 mikepav kernel: [21203.729982] ACPI: Low-level resume complete
Mar 15 16:56:01 mikepav kernel: [21203.730058] ACPI: EC: EC started
Mar 15 16:56:01 mikepav kernel: [21203.730059] PM: Restoring platform NVS memory
Mar 15 16:56:01 mikepav kernel: [21203.731960] Enabling non-boot CPUs ...
Mar 15 16:56:01 mikepav kernel: [21203.731995] x86: Booting SMP configuration:
Mar 15 16:56:01 mikepav kernel: [21203.731996] smpboot: Booting Node 0 Processor 1 APIC 0x2
Mar 15 16:56:01 mikepav kernel: [21203.733682]  cache: parent cpu1 should not be sleeping
Mar 15 16:56:01 mikepav kernel: [21203.733822] CPU1 is up
Mar 15 16:56:01 mikepav kernel: [21203.733843] smpboot: Booting Node 0 Processor 2 APIC 0x1
Mar 15 16:56:01 mikepav kernel: [21203.734315]  cache: parent cpu2 should not be sleeping
Mar 15 16:56:01 mikepav kernel: [21203.734469] CPU2 is up
Mar 15 16:56:01 mikepav kernel: [21203.734491] smpboot: Booting Node 0 Processor 3 APIC 0x3
Mar 15 16:56:01 mikepav kernel: [21203.734937]  cache: parent cpu3 should not be sleeping
Mar 15 16:56:01 mikepav kernel: [21203.735106] CPU3 is up
Mar 15 16:56:01 mikepav kernel: [21203.738336] ACPI: Waking up from system sleep state S3
Mar 15 16:56:01 mikepav kernel: [21203.747412] ACPI: EC: interrupt unblocked
Mar 15 16:56:01 mikepav kernel: [21203.779194] ACPI: button: The lid device is not compliant to SW_LID.
Mar 15 16:56:01 mikepav kernel: [21203.779204] ACPI: EC: event unblocked
Mar 15 16:56:01 mikepav kernel: [21203.780825] sd 1:0:0:0: [sda] Starting disk
Mar 15 16:56:01 mikepav kernel: [21204.048098] usb 1-8: reset high-speed USB device number 6 using xhci_hcd
Mar 15 16:56:01 mikepav kernel: [21204.091848] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 15 16:56:01 mikepav kernel: [21204.109951] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Mar 15 16:56:01 mikepav kernel: [21204.109955] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Mar 15 16:56:01 mikepav kernel: [21204.176723] ata2.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Mar 15 16:56:01 mikepav kernel: [21204.176727] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Mar 15 16:56:01 mikepav kernel: [21204.212744] ata2.00: configured for UDMA/133
Mar 15 16:56:01 mikepav kernel: [21204.289073] usb 1-7: reset full-speed USB device number 5 using xhci_hcd
Mar 15 16:56:01 mikepav kernel: [21204.524783] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758]
Mar 15 16:56:01 mikepav kernel: [21204.529083] usb 1-5: reset full-speed USB device number 4 using xhci_hcd
Mar 15 16:56:01 mikepav kernel: [21204.557506] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..]
Mar 15 16:56:01 mikepav kernel: [21204.771081] usb 1-9: reset full-speed USB device number 7 using xhci_hcd
Mar 15 16:56:01 mikepav kernel: [21206.137778] OOM killer enabled.
Mar 15 16:56:01 mikepav kernel: [21206.137780] Restarting tasks ... 
Mar 15 16:56:01 mikepav kernel: [21206.137898] usb 1-2: USB disconnect, device number 2
Mar 15 16:56:01 mikepav kernel: [21206.140543] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
Mar 15 16:56:01 mikepav kernel: [21206.143363] cdc_ether 1-2:2.0 wwan0: unregister 'cdc_ether' usb-0000:00:14.0-2, Mobile Broadband Network Device
Mar 15 16:56:01 mikepav kernel: [21206.147799] Bluetooth: hci0: Device revision is 5
Mar 15 16:56:01 mikepav kernel: [21206.147800] Bluetooth: hci0: Secure boot is enabled
Mar 15 16:56:01 mikepav kernel: [21206.147801] Bluetooth: hci0: OTP lock is enabled
Mar 15 16:56:01 mikepav kernel: [21206.147802] Bluetooth: hci0: API lock is enabled
Mar 15 16:56:01 mikepav kernel: [21206.147803] Bluetooth: hci0: Debug lock is disabled
Mar 15 16:56:01 mikepav kernel: [21206.147804] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Mar 15 16:56:01 mikepav kernel: [21206.147808] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
Mar 15 16:56:01 mikepav kernel: [21206.148784] done.
Mar 15 16:56:01 mikepav kernel: [21206.150898] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Mar 15 16:56:01 mikepav kernel: [21206.150914] option 1-2:2.2: device disconnected
Mar 15 16:56:01 mikepav kernel: [21206.151217] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Mar 15 16:56:01 mikepav kernel: [21206.151230] option 1-2:2.3: device disconnected
Mar 15 16:56:01 mikepav kernel: [21206.151364] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Mar 15 16:56:01 mikepav kernel: [21206.151376] option 1-2:2.4: device disconnected
Mar 15 16:56:01 mikepav kernel: [21206.151573] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
Mar 15 16:56:01 mikepav kernel: [21206.151585] option 1-2:2.5: device disconnected
Mar 15 16:56:01 mikepav kernel: [21206.151797] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
Mar 15 16:56:01 mikepav kernel: [21206.151810] option 1-2:2.6: device disconnected
Mar 15 16:56:01 mikepav kernel: [21206.193862] PM: suspend exit
Last edited by m_pav on Mon Mar 18, 2019 4:07 am, edited 2 times in total.
Mike P

Regd Linux User #472293
(Mine)Lenovo T560, i7-6600U, 16GB, 2.0TB SSHD, MX17 64-bit
(Wifes) Asus M4A88TD-M, AMD Phenom II x4 955 CPU, nVidia GF610, 6Gb, 500GB+320GB, MX17 + KDE
(Kids) Intel NUC, J1900, 4GB, 64GB SSD, MX17

User avatar
m_pav
Forum Guide
Forum Guide
Posts: 2707
Joined: Sun Aug 06, 2006 3:02 pm

Re: pm-suspend asking for root password

#2

Post by m_pav » Fri Mar 15, 2019 3:16 pm

It happened again, but this time I was ready for it. Turns out screenshooter was working, but hidden under the authentication message.

Suspend works just fine when initiated through the MX shutdown menu, but fails when called through a countdown timed power management event. I set the Power management to suspend the laptop after 15 minutes and rebooted to ensure nothing was interfering with the process.
pm-suspend.png
You do not have the required permissions to view the files attached to this post.
Mike P

Regd Linux User #472293
(Mine)Lenovo T560, i7-6600U, 16GB, 2.0TB SSHD, MX17 64-bit
(Wifes) Asus M4A88TD-M, AMD Phenom II x4 955 CPU, nVidia GF610, 6Gb, 500GB+320GB, MX17 + KDE
(Kids) Intel NUC, J1900, 4GB, 64GB SSD, MX17

User avatar
Adrian
Forum Veteran
Forum Veteran
Posts: 9593
Joined: Wed Jul 12, 2006 1:42 am

Re: pm-suspend asking for root password

#3

Post by Adrian » Fri Mar 15, 2019 4:48 pm

I've seen that once on one of my respins MX-KDE,I thought it was because I mucked up with the packages... not sure what's going on.

User avatar
fehlix
Forum Veteran
Forum Veteran
Posts: 3111
Joined: Wed Apr 11, 2018 5:09 pm

Re: pm-suspend asking for root password

#4

Post by fehlix » Fri Mar 15, 2019 6:53 pm

IIRC, when I played around with pm-suspend, I made intentionally pm-suspend password-less, actually in order to bind it to a key. Not sure whether this would have anything to do with it.

Code: Select all

# /etc/sudoers.d/suspend 
# sudoers file for system-suspend 
 
%users ALL=(root) NOPASSWD: /usr/sbin/pm-suspend
:puppy:
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
m_pav
Forum Guide
Forum Guide
Posts: 2707
Joined: Sun Aug 06, 2006 3:02 pm

Re: pm-suspend asking for root password

#5

Post by m_pav » Mon Mar 18, 2019 4:05 am

Two more of my systems fell prey to the same behaviour after installing updates and others running Debian based systems have reported it too.

Turns out the setting that cures the issue is in the Security tab of the Xfce Power Manager for the heading Light Locker.
Change the option for Automatically Lock the Session from "When the screensaver is activated" to "When the screensaver is deactivated" and the issue disappears, everything returns to normal.
Screenshot-3.png
Changing the title and marking this issue as solved.
You do not have the required permissions to view the files attached to this post.
Mike P

Regd Linux User #472293
(Mine)Lenovo T560, i7-6600U, 16GB, 2.0TB SSHD, MX17 64-bit
(Wifes) Asus M4A88TD-M, AMD Phenom II x4 955 CPU, nVidia GF610, 6Gb, 500GB+320GB, MX17 + KDE
(Kids) Intel NUC, J1900, 4GB, 64GB SSD, MX17

Post Reply

Return to “MX Help”