Clementine and sudpend to ram

Everything about X, Gnome, KDE, ... and everything running on it

Clementine and sudpend to ram

Postby pythagorasmk » 2020-01-02 09:48

I have set my computer to go in sleep mode after 25 min. But when Clementine is playing songs I don't want my computer to go in sleep mode. I don't see any option in Clementine to prevent sleep mode. How can I solve this issue?
pythagorasmk
 
Posts: 83
Joined: 2015-01-18 03:40


Re: Clementine and sudpend to ram

Postby pythagorasmk » 2020-01-03 01:38

I need more guidelines here. I have used "systemd-inhibit clementine" to start clementine but sleep mode is not prohibited. I think that the setting of the KDE takes precedence, but I am not sure. What should I try next?
pythagorasmk
 
Posts: 83
Joined: 2015-01-18 03:40

Re: Clementine and sudpend to ram

Postby Head_on_a_Stick » 2020-01-03 09:49

pythagorasmk wrote:What should I try next?

Run the command without arguments to see the locks applied by the Plasma desktop then read systemd-inhibit(1) to find out how to use the command.

Post back if you can't figure it out.
User avatar
Head_on_a_Stick
 
Posts: 12140
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Clementine and sudpend to ram

Postby pythagorasmk » 2020-01-04 04:45

Head_on_a_Stick wrote:Post back if you can't figure it out.

Output of the systend-inhibit without any arguments is:
Code: Select all
HO                          UID  USER   PID   COMM            WHAT               
ModemManager                 0    root   600   ModemManager    sleep               
NetworkManager               0    root   615   NetworkManager  sleep               
UPower                       0    root   1216  upowerd         sleep               
Unattended Upgrades Shutdown 0    root   674   unattended-upgr shutdown           
PowerDevil                   1001 barney 1295  org_kde_powerde handle-power-key:han
clementine                   1001 barney 28705 systemd-inhibit shutdown:sleep:idle

6 inhibitors listed.
pythagorasmk
 
Posts: 83
Joined: 2015-01-18 03:40

Re: Clementine and sudpend to ram

Postby Head_on_a_Stick » 2020-01-04 10:11

pythagorasmk wrote:
Code: Select all
clementine                   1001 barney 28705 systemd-inhibit shutdown:sleep:idle

Looks like the lock is already applied, not sure why it isn't working for you. Are there any clues in the systemd journal or X.Org log?
User avatar
Head_on_a_Stick
 
Posts: 12140
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Clementine and sudpend to ram

Postby Dai_trying » 2020-01-04 10:46

I really don't know much about this but would it be possible for a root process (maybe upowerd?) to over-ride a user process (clementine), just a thought... :?:
Dai_trying
 
Posts: 925
Joined: 2016-01-07 12:25

Re: Clementine and sudpend to ram

Postby pythagorasmk » 2020-01-06 17:42

Head_on_a_Stick wrote: Are there any clues in the systemd journal or X.Org log?

I had a short visit to journal and X.Org log, but there is nothing suspicious. No error messages, no warnings about clementine. I don't know what should I look for.
pythagorasmk
 
Posts: 83
Joined: 2015-01-18 03:40

Re: Clementine and sudpend to ram

Postby Head_on_a_Stick » 2020-01-07 16:30

pythagorasmk wrote:I don't know what should I look for.

Use the -f option for journalctl to "follow" new journal entries as they are made then play some music and wait for it to suspend and check for any new entries upon the resume.
User avatar
Head_on_a_Stick
 
Posts: 12140
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Clementine and sudpend to ram

Postby pythagorasmk » 2020-01-07 21:53

Head_on_a_Stick wrote:Use the -f option for journalctl to "follow" new journal entries as they are made then play some music and wait for it to suspend and check for any new entries upon the resume.

I have started journalctl -f, then started clementine with systemd-inhibit clementine, and waited for output from journalctl. Here is the result:
Code: Select all
-- Logs begin at Tue 2020-01-07 03:12:30 CET. --
Jan 07 22:30:01 living-room CRON[6274]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Jan 07 22:30:01 living-room CRON[6273]: pam_unix(cron:session): session closed for user root
Jan 07 22:34:31 living-room systemd[1]: Started Run anacron jobs.
Jan 07 22:34:31 living-room anacron[6290]: Anacron 2.3 started on 2020-01-07
Jan 07 22:34:31 living-room anacron[6290]: Normal exit (0 jobs run)
Jan 07 22:34:31 living-room systemd[1]: anacron.service: Succeeded.
Jan 07 22:44:09 living-room kernel: usb 2-1.6: USB disconnect, device number 4
Jan 07 22:44:09 living-room kernel: usblp2: removed
Jan 07 23:10:19 living-room sudo[6570]:   barney : TTY=pts/1 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/journalctl -f
Jan 07 23:10:19 living-room sudo[6570]: pam_unix(sudo:session): session opened for user root by barney(uid=0)
Jan 07 23:17:01 living-room CRON[6632]: pam_unix(cron:session): session opened for user root by (uid=0)
Jan 07 23:17:01 living-room CRON[6633]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jan 07 23:17:01 living-room CRON[6632]: pam_unix(cron:session): session closed for user root
Jan 07 23:30:01 living-room CRON[6659]: pam_unix(cron:session): session opened for user root by (uid=0)
Jan 07 23:30:01 living-room CRON[6660]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Jan 07 23:30:01 living-room CRON[6659]: pam_unix(cron:session): session closed for user root
Jan 07 23:30:31 living-room systemd[1]: Started Run anacron jobs.
Jan 07 23:30:31 living-room anacron[6662]: Anacron 2.3 started on 2020-01-07
Jan 07 23:30:31 living-room anacron[6662]: Normal exit (0 jobs run)
Jan 07 23:30:31 living-room systemd[1]: anacron.service: Succeeded.
Jan 07 23:36:54 living-room NetworkManager[569]: <info>  [1578436614.1357] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 07 23:36:54 living-room NetworkManager[569]: <info>  [1578436614.1358] manager: NetworkManager state is now ASLEEP
Jan 07 23:36:54 living-room systemd[1]: Reached target Sleep.
Jan 07 23:36:54 living-room systemd[1]: Starting Suspend...
Jan 07 23:36:54 living-room systemd-sleep[6670]: Suspending system...
Jan 07 23:36:54 living-room kernel: PM: suspend entry (deep)
Jan 07 23:37:09 living-room kernel: PM: Syncing filesystems ... done.
Jan 07 23:37:09 living-room kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Jan 07 23:37:09 living-room kernel: OOM killer disabled.
Jan 07 23:37:09 living-room kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jan 07 23:37:09 living-room kernel: Suspending console(s) (use no_console_suspend to debug)
Jan 07 23:37:09 living-room kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jan 07 23:37:09 living-room kernel: sd 0:0:0:0: [sda] Stopping disk
Jan 07 23:37:09 living-room kernel: ACPI: Preparing to enter system sleep state S3
Jan 07 23:37:09 living-room kernel: PM: Saving platform NVS memory
Jan 07 23:37:09 living-room kernel: Disabling non-boot CPUs ...
Jan 07 23:37:09 living-room kernel: smpboot: CPU 1 is now offline
Jan 07 23:37:09 living-room kernel: smpboot: CPU 2 is now offline
Jan 07 23:37:09 living-room kernel: smpboot: CPU 3 is now offline
Jan 07 23:37:09 living-room kernel: ACPI: Low-level resume complete
Jan 07 23:37:09 living-room kernel: PM: Restoring platform NVS memory
Jan 07 23:37:09 living-room kernel: Enabling non-boot CPUs ...
Jan 07 23:37:09 living-room kernel: x86: Booting SMP configuration:
Jan 07 23:37:09 living-room kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jan 07 23:37:09 living-room kernel:  cache: parent cpu1 should not be sleeping
Jan 07 23:37:09 living-room kernel: CPU1 is up
Jan 07 23:37:09 living-room kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
Jan 07 23:37:09 living-room kernel:  cache: parent cpu2 should not be sleeping
Jan 07 23:37:09 living-room kernel: CPU2 is up
Jan 07 23:37:09 living-room kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Jan 07 23:37:09 living-room kernel:  cache: parent cpu3 should not be sleeping
Jan 07 23:37:09 living-room kernel: CPU3 is up
Jan 07 23:37:09 living-room kernel: ACPI: Waking up from system sleep state S3
Jan 07 23:37:09 living-room kernel: usb usb1: root hub lost power or was reset
Jan 07 23:37:09 living-room kernel: usb usb2: root hub lost power or was reset
Jan 07 23:37:09 living-room kernel: ehci-pci 0000:00:1a.0: cache line size of 4 is not supported
Jan 07 23:37:09 living-room kernel: ehci-pci 0000:00:1d.0: cache line size of 4 is not supported
Jan 07 23:37:09 living-room kernel: sd 0:0:0:0: [sda] Starting disk
Jan 07 23:37:09 living-room kernel: usb 1-1: reset high-speed USB device number 2 using ehci-pci
Jan 07 23:37:09 living-room kernel: ata2: SATA link down (SStatus 0 SControl 300)
Jan 07 23:37:09 living-room kernel: ata5: SATA link down (SStatus 0 SControl 300)
Jan 07 23:37:09 living-room kernel: usb 2-1: reset high-speed USB device number 2 using ehci-pci
Jan 07 23:37:09 living-room kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jan 07 23:37:09 living-room kernel: ata6.00: configured for UDMA/133
Jan 07 23:37:09 living-room kernel: usb 2-1.2: reset high-speed USB device number 3 using ehci-pci
Jan 07 23:37:09 living-room kernel: usb 1-1.3: reset low-speed USB device number 8 using ehci-pci
Jan 07 23:37:09 living-room kernel: r8169 0000:07:00.0 enp7s0: Link is Down
Jan 07 23:37:09 living-room kernel: usb 1-1.4: reset full-speed USB device number 4 using ehci-pci
Jan 07 23:37:09 living-room kernel: OOM killer enabled.
Jan 07 23:37:09 living-room kernel: Restarting tasks ... done.
Jan 07 23:37:09 living-room kernel: PM: suspend exit
Jan 07 23:37:09 living-room rtkit-daemon[1286]: The canary thread is apparently starving. Taking action.
Jan 07 23:37:09 living-room systemd-sleep[6670]: System resumed.
Jan 07 23:37:09 living-room rtkit-daemon[1286]: Demoting known real-time threads.
Jan 07 23:37:09 living-room rtkit-daemon[1286]: Successfully demoted thread 1391 of process 1266 (n/a).
Jan 07 23:37:09 living-room rtkit-daemon[1286]: Successfully demoted thread 1388 of process 1266 (n/a).
Jan 07 23:37:09 living-room rtkit-daemon[1286]: Successfully demoted thread 1387 of process 1266 (n/a).
Jan 07 23:37:09 living-room rtkit-daemon[1286]: Successfully demoted thread 1383 of process 1266 (n/a).
Jan 07 23:37:09 living-room rtkit-daemon[1286]: Successfully demoted thread 1266 of process 1266 (n/a).
Jan 07 23:37:09 living-room rtkit-daemon[1286]: Demoted 5 threads.
Jan 07 23:37:11 living-room NetworkManager[569]: <info>  [1578436631.3781] device (enp7s0): carrier: link connected
Jan 07 23:37:11 living-room kernel: r8169 0000:07:00.0 enp7s0: Link is Up - 1Gbps/Full - flow control rx/tx
Jan 07 23:37:15 living-room kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 07 23:37:15 living-room kernel: ata1.00: configured for UDMA/133
Jan 07 23:37:15 living-room systemd-sleep[6670]: /dev/sda:
Jan 07 23:37:15 living-room systemd-sleep[6670]:  setting Advanced Power Management level to 0xfe (254)
Jan 07 23:37:15 living-room systemd-sleep[6670]:  APM_level        = off
Jan 07 23:37:15 living-room systemd[1]: systemd-suspend.service: Succeeded.
Jan 07 23:37:15 living-room systemd[1]: Started Suspend.
Jan 07 23:37:15 living-room systemd[1]: Stopped target Sleep.
Jan 07 23:37:15 living-room systemd[1]: Reached target Suspend.
Jan 07 23:37:15 living-room systemd[1]: Stopped target Suspend.
Jan 07 23:37:15 living-room systemd-logind[565]: Operation 'sleep' finished.
Jan 07 23:37:15 living-room NetworkManager[569]: <info>  [1578436635.3977] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jan 07 23:37:15 living-room NetworkManager[569]: <info>  [1578436635.3978] device (enp7s0): state change: activated -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 07 23:37:15 living-room avahi-daemon[561]: Withdrawing address record for 192.168.0.2 on enp7s0.
Jan 07 23:37:15 living-room avahi-daemon[561]: Leaving mDNS multicast group on interface enp7s0.IPv4 with address 192.168.0.2.
Jan 07 23:37:15 living-room avahi-daemon[561]: Interface enp7s0.IPv4 no longer relevant for mDNS.
Jan 07 23:37:15 living-room avahi-daemon[561]: Withdrawing address record for fe80::52e5:49ff:fe50:58bf on enp7s0.
Jan 07 23:37:15 living-room avahi-daemon[561]: Leaving mDNS multicast group on interface enp7s0.IPv6 with address fe80::52e5:49ff:fe50:58bf.
Jan 07 23:37:15 living-room avahi-daemon[561]: Interface enp7s0.IPv6 no longer relevant for mDNS.
Jan 07 23:37:15 living-room NetworkManager[569]: <info>  [1578436635.4601] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 07 23:37:15 living-room NetworkManager[569]: <info>  [1578436635.4795] manager: NetworkManager state is now DISCONNECTED
Jan 07 23:37:15 living-room NetworkManager[569]: <info>  [1578436635.5201] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Jan 07 23:37:15 living-room kernel: IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
Jan 07 23:37:15 living-room kernel: RTL8211E Gigabit Ethernet r8169-700:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=r8169-700:00, irq=IGNORE)
Jan 07 23:37:15 living-room dbus-daemon[567]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=569 comm="/usr/sbin/NetworkManager --no-daemon ")
Jan 07 23:37:15 living-room systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 07 23:37:15 living-room dbus-daemon[567]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 07 23:37:15 living-room systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 07 23:37:15 living-room nm-dispatcher[6878]: req:1 'down' [enp7s0]: new request (1 scripts)
Jan 07 23:37:15 living-room nm-dispatcher[6878]: req:1 'down' [enp7s0]: start running ordered scripts...
Jan 07 23:37:15 living-room nm-dispatcher[6878]: req:2 'connectivity-change': new request (1 scripts)
Jan 07 23:37:15 living-room nm-dispatcher[6878]: req:2 'connectivity-change': start running ordered scripts...
Jan 07 23:37:15 living-room kernel: IPv6: ADDRCONF(NETDEV_UP): enp7s0: link is not ready
Jan 07 23:37:17 living-room ModemManager[553]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.5/0000:07:00.0': not supported by any plugin
Jan 07 23:37:19 living-room kernel: r8169 0000:07:00.0 enp7s0: Link is Up - 1Gbps/Full - flow control rx/tx
Jan 07 23:37:19 living-room kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp7s0: link becomes ready
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2174] device (enp7s0): carrier: link connected
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2178] device (enp7s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2192] policy: auto-activating connection 'Wired connection 1' (6416c2a4-1f2a-4627-8d0f-f7025784df8e)
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2203] device (enp7s0): Activation: starting connection 'Wired connection 1' (6416c2a4-1f2a-4627-8d0f-f7025784df8e)
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2206] device (enp7s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2215] manager: NetworkManager state is now CONNECTING
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2220] device (enp7s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2230] device (enp7s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 07 23:37:19 living-room avahi-daemon[561]: Joining mDNS multicast group on interface enp7s0.IPv6 with address fe80::52e5:49ff:fe50:58bf.
Jan 07 23:37:19 living-room avahi-daemon[561]: New relevant interface enp7s0.IPv6 for mDNS.
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2266] device (enp7s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 07 23:37:19 living-room avahi-daemon[561]: Registering new address record for fe80::52e5:49ff:fe50:58bf on enp7s0.*.
Jan 07 23:37:19 living-room avahi-daemon[561]: Joining mDNS multicast group on interface enp7s0.IPv4 with address 192.168.0.2.
Jan 07 23:37:19 living-room avahi-daemon[561]: New relevant interface enp7s0.IPv4 for mDNS.
Jan 07 23:37:19 living-room avahi-daemon[561]: Registering new address record for 192.168.0.2 on enp7s0.IPv4.
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2282] device (enp7s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2285] device (enp7s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2290] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2716] manager: NetworkManager state is now CONNECTED_SITE
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.2717] policy: set 'Wired connection 1' (enp7s0) as default for IPv4 routing and DNS
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.3135] device (enp7s0): Activation: successful, device activated.
Jan 07 23:37:19 living-room NetworkManager[569]: <info>  [1578436639.3149] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 07 23:37:19 living-room nm-dispatcher[6878]: req:3 'up' [enp7s0]: new request (1 scripts)
Jan 07 23:37:19 living-room nm-dispatcher[6878]: req:3 'up' [enp7s0]: start running ordered scripts...
Jan 07 23:37:19 living-room nm-dispatcher[6878]: req:4 'connectivity-change': new request (1 scripts)
Jan 07 23:37:19 living-room nm-dispatcher[6878]: req:4 'connectivity-change': start running ordered scripts...
Jan 07 23:37:29 living-room systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan 07 23:37:42 living-room systemd[1]: Starting Daily apt download activities...
Jan 07 23:37:43 living-room systemd[1]: apt-daily.service: Succeeded.
Jan 07 23:37:43 living-room systemd[1]: Started Daily apt download activities.
pythagorasmk
 
Posts: 83
Joined: 2015-01-18 03:40


Return to Desktop & Multimedia

Who is online

Users browsing this forum: No registered users and 11 guests

fashionable