Media playback stops working after waking from sleep

DaforLynx · Yesterday 00:44:35

I've been using Arch for a little over a year now, and this entire time, sleep has been a constant problem. For like the entirety of 2025, it straight up didn't work and would wake up my computer automatically into an undead state with no screen output. Then that got fixed and it woke up normally, or so I thought. But YouTube videos wouldn't play, just loading perpetually. Neither would audio files in any application I tried. I pushed it out of my mind and forgot about it until today when I tried sleeping again, not remembering why I didn't do it in the first place, experienced disappointment, and finally decided to ask here for answers.
The reason I post in this forum section is because I don't believe it's a kernel bug; it seems to be affecting software specifically. But it's hard to know.

My desktop environment is KDE Plasma; this is the output of kinfo:

Operating System: Arch Linux 
KDE Plasma Version: 6.6.4
KDE Frameworks Version: 6.25.0
Qt Version: 6.11.0
Kernel Version: 6.14.0-rt3-arch1-7-rt (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: AMD Radeon RX 6650 XT

I use pipewire as the audio backend. It outputs all applications into a default sink before outputting to my Behringer UMC204HD interface. I don't think there are any problems with pipewire when the bugged state happens.

I have examined the journal output when waking from sleep and not found anything particularly exciting or incriminating. No errors are output into the journal when trying to play a file while in the bugged state - the playback simply doesn't work, either outputting no audio or even refusing to tick the seekbar forward (this could be a hint as to what's happening). I have also taken a look at the systemd services and not found anything promising, though I don't really know what I'm looking for.

If further info or experimentation is required, I'd be happy to do it tomorrow. Hopefully we can figure it out and it's just a user skill issue. I should probably get some diagnostics about services and stuff from before and after sleeping but I will post that later if needed.

V1del · Yesterday 10:54:33

What are you using an RT kernel for? I'm. not sure why it's in such a maintenance limbo especially seeing that the relevant RT patches should only be a kernel config away on current kernels, but you're essentially running a more than a year old kernel. And especially stuff like trying to sleep and the like which interact with HW state that the RT kernel aims to keep in certain guarantees is likely to be more wonky there than with a normal kernel.

So first of all I'd test this on the normal linux kernel, if you still have issues how exactly does this manifest, does pipewire still hold the device (

sudo fuser -v /dev/snd/*

, does ceasing all playback and restarting it work again? Behringer also tend to have quite a few specific quirks, could also be an issue with how they resume from the suspended state, does replugging it after going into this state restore the audio? does disabling usb autosuspend help? What's in your journal after running into this?

sudo journalctl -b | curl -F 'file=@-'  https://paste.c-net.org/

after reproducing?

Last edited by V1del (Yesterday 11:00:53)

DaforLynx · Yesterday 23:06:00

I use the rt linux kernel because I produce music on this machine, and it helped with latency. At least, it did, but using the most recent kernel now and it's not showing the latency penalty it once did.

Nevertheless, switching off the rt kernel did not help the issue. But I figured out something. I unplugged and replugged the interface back in, reset my pipewire, and it worked. Restarting the interface is necessary, because if I just restart pipewire, it still doesn't work (although the interface still shows up in qpwgraph). This makes it seem like there's an issue with the interface.

So when running the fuser command after waking from sleep, I get:

                     USER        PID ACCESS COMMAND
/dev/snd/controlC0:  d          5790 F.... wireplumber
/dev/snd/controlC2:  d          5790 F.... wireplumber
/dev/snd/controlC3:  d          5790 F.... wireplumber
/dev/snd/controlC4:  d          5788 F.... pipewire
                     d          5790 F.... wireplumber
/dev/snd/controlC5:  d          5790 F.... wireplumber
/dev/snd/pcmC4D0p:   d          5788 F...m pipewire
/dev/snd/pcmC5D0c:   d          5788 F...m pipewire
/dev/snd/pcmC5D0p:   d          5788 F...m pipewire
/dev/snd/seq:        d          1595 F.... qpwgraph
                     d          5788 F.... pipewire

And here's the working state:

                     USER        PID ACCESS COMMAND
/dev/snd/controlC0:  d          6366 F.... wireplumber
/dev/snd/controlC2:  d          6366 F.... wireplumber
/dev/snd/controlC3:  d          6366 F.... wireplumber
/dev/snd/controlC4:  d          6364 F.... pipewire
                     d          6366 F.... wireplumber
/dev/snd/controlC5:  d          6366 F.... wireplumber
/dev/snd/pcmC4D0p:   d          6364 F...m pipewire
/dev/snd/pcmC5D0c:   d          6364 F...m pipewire
/dev/snd/pcmC5D0p:   d          6364 F...m pipewire
/dev/snd/seq:        d          1595 F.... qpwgraph
                     d          6364 F.... pipewire

Doesn't seem to be any difference.

I'll restart again and get the other info.

DaforLynx · Yesterday 23:09:55

Here's the entire journal output when starting the PC, sleeping, then waking up (and doing nothing else).

https://paste.c-net.org/OraclesOblivion

I tried to make sure there's no personal information contained.

DaforLynx · Yesterday 23:47:15

Doing more testing, I found the following:

When waking from sleep, all sound stops working including through the motherboard. Unplugging the interface causes something to happen and the motherboard audio starts working again.

So it seems like this could be an issue with pipewire? I don't know. Here's the journal output from the moment I unplug to the moment I plug it back in. You can probably skip past the journal spam from the system trying to send audio to the nonexistent device. https://paste.c-net.org/AcceptFever
As you can see, nothing new really happens. Maybe up until it says "spa.alsa: hw:5,0p: close failed: No such device". But the music plays just fine (and fooyin having to reinitialize its pipewire backend doesn't have anything to do with the problem, that's just something that happens when it plays music at a new samplerate).

seth · Today 06:40:52

Apr 29 16:07:19 d-arch kernel: usb 1-5: clock source 41 is not valid, cannot use
Apr 29 16:07:19 d-arch kernel: usb 1-5: clock source 41 is not valid, cannot use
Apr 29 16:07:19 d-arch kernel: usb 1-5: clock source 41 is not valid, cannot use
Apr 29 16:07:19 d-arch kernel: usb 1-5: clock source 41 is not valid, cannot use
Apr 29 16:07:19 d-arch kernel: usb 1-5: clock source 41 is not valid, cannot use
Apr 29 16:07:19 d-arch wireplumber[1162]: spa.alsa: Path UMC204HD 192k Output is not a volume or mute control
Apr 29 16:07:19 d-arch systemd[1]: Starting Locale Service...
Apr 29 16:07:19 d-arch kernel: usb 5-1: 3:1: cannot get freq at ep 0x84
Apr 29 16:07:19 d-arch kernel: usb 5-1: 3:1: cannot get freq at ep 0x84
Apr 29 16:07:19 d-arch wireplumber[1162]: spa.bluez5: BlueZ system service is not available
Apr 29 16:07:19 d-arch wireplumber[1162]: wp-device: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
Apr 29 16:07:19 d-arch wireplumber[1162]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.
Apr 29 16:07:19 d-arch systemd[1]: Started Locale Service.
Apr 29 16:07:19 d-arch systemd[1094]: Reload requested from client PID 1172 ('startplasma-way')...
Apr 29 16:07:19 d-arch systemd[1094]: Reloading...
Apr 29 16:07:19 d-arch systemd-xdg-autostart-generator[1210]: Exec binary '/opt/paloaltonetworks/globalprotect/PanGPUI' does not exist: No such file or directory
Apr 29 16:07:19 d-arch systemd-xdg-autostart-generator[1210]: /etc/xdg/autostart/PanGPUI.desktop: not generating unit, executable specified in Exec= does not exist.
Apr 29 16:07:19 d-arch systemd[1094]: Reloading finished in 148 ms.
Apr 29 16:07:19 d-arch systemd[1094]: Created slice Slice /app/dbus-:1.1-org.kde.KSplash.
Apr 29 16:07:19 d-arch systemd[1094]: Started dbus-:1.1-org.kde.KSplash@0.service.
Apr 29 16:07:19 d-arch systemd[1094]: Created slice User Background Tasks Slice.
Apr 29 16:07:19 d-arch systemd[1094]: Submitting pending crash events skipped, unmet condition check ConditionPathExistsGlob=/home/d/.cache/drkonqi/sentry-envelopes/*
Apr 29 16:07:19 d-arch systemd[1094]: Starting KDE Global Shortcuts Server...
Apr 29 16:07:19 d-arch systemd[1094]: Starting KDE Wayland Compositor...
Apr 29 16:07:19 d-arch systemd[1094]: Starting User folders update...
Apr 29 16:07:19 d-arch systemd[1094]: Starting Baloo File Indexer Daemon...
Apr 29 16:07:19 d-arch systemd[1094]: Finished User folders update.
Apr 29 16:07:19 d-arch systemd[1094]: Reached target Session services which should run early before the graphical session is brought up.
Apr 29 16:07:19 d-arch systemd[1094]: Started KDE Wayland Compositor.
Apr 29 16:07:19 d-arch systemd[1094]: Starting KDE Config Module Initialization...
Apr 29 16:07:19 d-arch systemd[1094]: Starting Splash screen shown during boot...
Apr 29 16:07:19 d-arch systemd[1094]: Started KDE Global Shortcuts Server.
Apr 29 16:07:19 d-arch systemd[1094]: Started Baloo File Indexer Daemon.
Apr 29 16:07:19 d-arch systemd[1094]: Starting Portal service...
Apr 29 16:07:19 d-arch systemd[1]: Starting Disk Manager...
Apr 29 16:07:19 d-arch systemd[1094]: Starting sandboxed app permission store...
Apr 29 16:07:19 d-arch systemd[1094]: Started sandboxed app permission store.
Apr 29 16:07:19 d-arch systemd[1094]: Starting flatpak document portal service...
Apr 29 16:07:19 d-arch systemd[1094]: Started flatpak document portal service.
Apr 29 16:07:19 d-arch /usr/lib/xdg-desktop-portal[1228]: Choosing gtk.portal for org.freedesktop.impl.portal.Lockdown as a last-resort fallback
Apr 29 16:07:19 d-arch kernel: nvme nvme0: using unchecked data buffer
Apr 29 16:07:19 d-arch kernel: block nvme0n1: No UUID available providing old NGUID
Apr 29 16:07:19 d-arch kwin_wayland[1220]: No backend specified, automatically choosing drm
Apr 29 16:07:19 d-arch systemd[1]: Started Disk Manager.
Apr 29 16:07:19 d-arch systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Apr 29 16:07:20 d-arch kwin_wayland[1220]: could not create a component for  "org.gnome.Calculator.desktop"
Apr 29 16:07:20 d-arch systemd[1094]: Starting KDE Night Time Service...
Apr 29 16:07:20 d-arch systemd[1094]: Started KDE Night Time Service.
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1366]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1366]: > Warning:          Multiple symbols for level 1/group 1 on key <FK23>
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1366]: >                   Using F23, ignoring XF86TouchpadOff
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1366]: > Warning:          Symbol map for key <FK23> redefined
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1366]: >                   Using last definition for conflicting fields
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1366]: > Warning:          Symbol map for key <FK24> redefined
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1366]: >                   Using last definition for conflicting fields
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1366]: Errors from xkbcomp are not fatal to the X server
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1372]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1372]: > Warning:          Unsupported maximum keycode 709, clipping.
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1372]: >                   X11 cannot support keycodes above 255.
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1372]: > Warning:          Virtual modifier Hyper multiply defined
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1372]: >                   Using 0, ignoring 0
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1372]: > Warning:          Virtual modifier ScrollLock multiply defined
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1372]: >                   Using 0, ignoring 0
Apr 29 16:07:20 d-arch systemd[1094]: Starting Accessibility services bus...
Apr 29 16:07:20 d-arch kwin_wayland_wrapper[1372]: Errors from xkbcomp are not fatal to the X server
Apr 29 16:07:20 d-arch systemd[1094]: Started Accessibility services bus.
Apr 29 16:07:20 d-arch dbus-broker-launch[1385]: Ready
Apr 29 16:07:21 d-arch systemd[1094]: Started KDE Config Module Initialization.
Apr 29 16:07:21 d-arch systemd[1094]: Starting KDE Session Management Server...
Apr 29 16:07:21 d-arch systemd[1094]: Started Unlock kwallet from pam credentials.
Apr 29 16:07:21 d-arch systemd[1094]: Starting KDE Daemon 6...
Apr 29 16:07:21 d-arch pam_kwallet_init[1398]: 2026/04/29 16:07:21 socat[1398] W address is opened in read-write mode but only supports read-only
Apr 29 16:07:21 d-arch systemd[1094]: Started KDE Session Management Server.
Apr 29 16:07:21 d-arch systemd[1094]: Starting KDE Plasma Workspace...
Apr 29 16:07:21 d-arch systemd[1094]: Created slice Slice /app/dbus-:1.20-org.a11y.atspi.Registry.
Apr 29 16:07:21 d-arch systemd[1094]: Started dbus-:1.20-org.a11y.atspi.Registry@0.service.
Apr 29 16:07:21 d-arch systemd[1094]: Started KDE Daemon 6.
Apr 29 16:07:21 d-arch systemd[1094]: Starting KDE Configuration Module Initialization (Phase 1)...
Apr 29 16:07:21 d-arch at-spi2-registryd[1444]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Apr 29 16:07:21 d-arch systemd[1094]: Finished KDE Configuration Module Initialization (Phase 1).
Apr 29 16:07:21 d-arch systemd[1094]: Starting User preferences database...
Apr 29 16:07:21 d-arch systemd[1094]: Starting KActivityManager Activity manager Service...
Apr 29 16:07:21 d-arch kded6[1396]: QDBusObjectPath: invalid path "/modules/oom-notifier"
Apr 29 16:07:21 d-arch kded6[1396]: The kded module name "oom-notifier" is invalid!
Apr 29 16:07:21 d-arch systemd[1094]: Started User preferences database.
Apr 29 16:07:21 d-arch kded6[1396]: QDBusObjectPath: invalid path "/modules/plasma-session-shortcuts"
Apr 29 16:07:21 d-arch kded6[1396]: The kded module name "plasma-session-shortcuts" is invalid!
Apr 29 16:07:21 d-arch systemd[1094]: Started KDE Plasma Workspace.
Apr 29 16:07:21 d-arch systemd[1094]: Reached target KDE Plasma Workspace Core.
Apr 29 16:07:21 d-arch systemd[1094]: Started Consume pending crashes using DrKonqi.
Apr 29 16:07:21 d-arch systemd[1094]: Started Proxies GTK DBus menus to a Plasma readable format.
Apr 29 16:07:21 d-arch systemd[1094]: Started KAccess.
Apr 29 16:07:21 d-arch systemd[1094]: Starting KDE PolicyKit Authentication Agent...
Apr 29 16:07:21 d-arch systemd[1094]: Starting Powerdevil...
Apr 29 16:07:21 d-arch systemd[1094]: Started Handle legacy xembed system tray icons.
Apr 29 16:07:21 d-arch kaccess[1483]: Xlib XKB extension major= 1  minor= 0
Apr 29 16:07:21 d-arch org_kde_powerdevil[1485]: Starting libddcutil. library built Not set at Not set. stdout_stderr_redirected=true
Apr 29 16:07:21 d-arch NetworkManager[788]: <info>  [1777504041.4284] agent-manager: agent[dddc7c04881198a8,:1.30/org.kde.plasma.networkmanagement/1000]: agent registered
Apr 29 16:07:21 d-arch systemd[1094]: Started KDE PolicyKit Authentication Agent.
Apr 29 16:07:21 d-arch org_kde_powerdevil[1485]: Starting. library built Not set at Not set, library_initialized=false, libopts=|(null)|
Apr 29 16:07:21 d-arch polkit-kde-authentication-agent-1[1484]: New PolkitAgentListener  0x5ae18ab17a90
Apr 29 16:07:21 d-arch org_kde_powerdevil[1485]: Initializing libddcutil.  ddcutil version: 2.2.6, shared library: /usr/lib/libddcutil.so.5.5.0
Apr 29 16:07:21 d-arch polkit-kde-authentication-agent-1[1484]: Adding new listener  PolkitQt1::Agent::Listener(0x5ae18ab176e0) for  0x5ae18ab17a90
Apr 29 16:07:21 d-arch org_kde_powerdevil[1485]:                           library built Not set at Not set. stdout_stderr_redirected=true
Apr 29 16:07:21 d-arch polkit-kde-authentication-agent-1[1484]: Listener online
Apr 29 16:07:21 d-arch org_kde_powerdevil[1485]: [  1485] Options passed from client:
Apr 29 16:07:21 d-arch kaccess[1483]: X server XKB extension major= 1  minor= 0
Apr 29 16:07:21 d-arch org_kde_powerdevil[1485]: [  1485] Applying combined libddcutil options:
Apr 29 16:07:21 d-arch polkit-kde-authentication-agent-1[1484]: Authentication agent result: true
Apr 29 16:07:21 d-arch org_kde_powerdevil[1485]: [  1485] (i2c_detect_x37) Extra x37 sleep: Sleeping for 400 milliseconds
Apr 29 16:07:21 d-arch kded6[1396]: Failed to connect to Bolt manager DBus interface: 
Apr 29 16:07:21 d-arch kded6[1396]: Couldn't connect to Bolt DBus daemon
Apr 29 16:07:21 d-arch kded6[1396]: QDBusObjectPath: invalid path "/modules/wpad-detector"
Apr 29 16:07:21 d-arch kded6[1396]: The kded module name "wpad-detector" is invalid!
Apr 29 16:07:21 d-arch kconf_update[1587]: /usr/share/kconf_update/filepicker.upd defined Version=5 but Version=6 was expected
Apr 29 16:07:21 d-arch dbus-broker-launch[784]: Activation request for 'org.freedesktop.ModemManager1' failed: The systemd unit 'dbus-org.freedesktop.ModemManager1.service' could not be found.
Apr 29 16:07:21 d-arch kded6[1396]: Failed enumerating MM objects: "org.freedesktop.DBus.Error.NameHasNoOwner" 
                                     "Could not activate remote peer 'org.freedesktop.ModemManager1': activation request failed: unknown unit"
Apr 29 16:07:21 d-arch dbus-broker-launch[784]: Activation request for 'org.bluez' failed: The systemd unit 'dbus-org.bluez.service' could not be found.
Apr 29 16:07:21 d-arch kded6[1594]: xsettingsd: Loaded 17 settings from /home/d/.config/xsettingsd/xsettingsd.conf
Apr 29 16:07:21 d-arch kded6[1594]: xsettingsd: Created window 0xe00001 on screen 0 with timestamp 27112
Apr 29 16:07:21 d-arch kded6[1594]: xsettingsd: Selection _XSETTINGS_S0 is owned by 0x0
Apr 29 16:07:21 d-arch kded6[1594]: xsettingsd: Took ownership of selection _XSETTINGS_S0
Apr 29 16:07:21 d-arch systemd[1]: Created slice Slice /system/dbus-:1.2-org.kde.kded.smart.
Apr 29 16:07:21 d-arch systemd[1]: Started dbus-:1.2-org.kde.kded.smart@0.service.
Apr 29 16:07:21 d-arch kded6[1396]: PendingCall Error: "The name is not activatable"
Apr 29 16:07:21 d-arch kded6[1396]: PendingCall Error: "Could not activate remote peer 'org.bluez': activation request failed: unknown unit"
Apr 29 16:07:22 d-arch org_kde_powerdevil[1485]: [  1485] (i2c_detect_x37) Extra x37 sleep: Sleeping for 400 milliseconds
Apr 29 16:07:22 d-arch systemd[1094]: Started KActivityManager Activity manager Service.
Apr 29 16:07:22 d-arch kded6[1396]: Known activities: QList("ee67455c-a98f-4c48-9491-e00bb4a63bf7")
Apr 29 16:07:22 d-arch kded6[1396]: Known activities: QList("ee67455c-a98f-4c48-9491-e00bb4a63bf7")
Apr 29 16:07:22 d-arch systemd[1094]: Starting Track hardware statistics...
Apr 29 16:07:22 d-arch plasmashell[1443]: Could not find required file "mainscript" for package "/usr/share/plasma/plasmoids/org.kde.plasma.icontasks/" should be QList("ui/main.qml")
Apr 29 16:07:22 d-arch plasmashell[1443]: Could not find required file "mainscript" for package "/usr/share/plasma/plasmoids/org.kde.plasma.minimizeall/" should be QList("ui/main.qml")
Apr 29 16:07:22 d-arch plasmashell[1443]: Could not find required file "mainscript" for package "/usr/share/plasma/plasmoids/org.kde.plasma.icontasks/" should be QList("ui/main.qml")
Apr 29 16:07:22 d-arch plasmashell[1443]: Could not find required file "mainscript" for package "/usr/share/plasma/plasmoids/org.kde.plasma.minimizeall/" should be QList("ui/main.qml")
Apr 29 16:07:22 d-arch NetworkManager[788]: <info>  [1777504042.4196] audit: op="statistics" interface="enp6s0" ifindex=2 args="500" pid=1613 uid=1000 result="success"
Apr 29 16:07:22 d-arch systemd[1094]: Started Track hardware statistics.
Apr 29 16:07:22 d-arch NetworkManager[788]: <info>  [1777504042.4246] audit: op="statistics" interface="wlan0" ifindex=4 args="500" pid=1613 uid=1000 result="success"
Apr 29 16:07:22 d-arch NetworkManager[788]: <info>  [1777504042.4364] audit: op="statistics" interface="wlan0" ifindex=4 args="500" pid=1613 uid=1000 result="success"
Apr 29 16:07:22 d-arch plasmashell[1443]: Member visible of the object PlasmaQuick::Dialog overrides a member of the base object. Consider renaming it or adding final or override specifier
Apr 29 16:07:22 d-arch org_kde_powerdevil[1485]: [  1485] (i2c_detect_x37) Extra x37 sleep: Sleeping for 400 milliseconds
Apr 29 16:07:22 d-arch plasmashell[1443]: Member enabled of the object DeclarativeDropArea overrides a member of the base object. Consider renaming it or adding final or override specifier
Apr 29 16:07:22 d-arch systemd[1094]: Finished Splash screen shown during boot.
Apr 29 16:07:22 d-arch org_kde_powerdevil[1485]: [  1485] (i2c_detect_x37) Extra x37 sleep: Sleeping for 400 milliseconds
Apr 29 16:07:23 d-arch org_kde_powerdevil[1485]: [  1485] (i2c_detect_x37) Extra x37 sleep: Sleeping for 400 milliseconds
Apr 29 16:07:23 d-arch systemd[1094]: Created slice Slice /app/dbus-:1.1-org.kde.kdeconnect.
Apr 29 16:07:23 d-arch systemd[1094]: Started dbus-:1.1-org.kde.kdeconnect@0.service.
Apr 29 16:07:23 d-arch kernel: warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
Apr 29 16:07:23 d-arch kdeconnectd[1669]: Cannot find a compatible running Bluez. Please check the Bluez installation. QtBluetooth requires at least BlueZ version 5.
Apr 29 16:07:23 d-arch kdeconnectd[1669]: No local bluetooth adapter found
Apr 29 16:07:23 d-arch org_kde_powerdevil[1485]: [  1485] (i2c_detect_x37) Extra x37 sleep: Sleeping for 400 milliseconds
Apr 29 16:07:24 d-arch kdeconnectd[1669]: new capabilities for  "Pixel 9"
Apr 29 16:07:24 d-arch kdeconnectd[1669]: Clearing existing entries 0
Apr 29 16:07:24 d-arch kdeconnectd[1669]: No Primary Battery detected on this system. This may be a bug.
Apr 29 16:07:24 d-arch kdeconnectd[1669]: Total quantity of batteries found:  0
Apr 29 16:07:24 d-arch kdeconnectd[1669]: Primary Battery seems to have been removed. Suspending packets until it is reconnected.
Apr 29 16:07:24 d-arch kdeconnectd[1669]: Failed enumerating MM objects: "org.freedesktop.DBus.Error.NameHasNoOwner" 
                                           "Could not activate remote peer 'org.freedesktop.ModemManager1': activation request failed: unknown unit"
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: Library initialization complete.
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: [  1485] (ddci_init) Done.  Returning 0
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: [  1485] Starting ddca_start_watch_displays()
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: Watching for DPMS state changes unimplemented
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: [  1485] Watching for DPMS state changes unimplemented
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: [  1485] Watching for display connection changes, resolved watch mode = Watch_Mode_Udev, poll loop interval = 500 millisec
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: [  1485]                                          extra_stabilization_millisec: 0,  stabilization_poll_millisec: 100
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: [  1485] libddcutil recheck thread 0x608986ceae70 started
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: [  1703] (dw_recheck_displays_func) Recheck interval: Sleeping for 200 milliseconds
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: [  1485] libddcutil watch thread 0x608986d53390 started
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: [  1485] Done     ddca_start_watch_displays returning OK - OK(0): success
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: [  1485] (ddca_get_display_refs) Returned DDCA_Display_Ref list:
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: [  1485] (ddca_get_display_refs)    DDCA_Display_Ref Display_Ref[1:bus /dev/i2c-3 @0x608986d84a20]
Apr 29 16:07:24 d-arch systemd[1]: Created slice Slice /system/dbus-:1.2-org.kde.powerdevil.discretegpuhelper.
Apr 29 16:07:24 d-arch systemd[1]: Started dbus-:1.2-org.kde.powerdevil.discretegpuhelper@0.service.
Apr 29 16:07:24 d-arch systemd[1]: Created slice Slice /system/dbus-:1.2-org.kde.powerdevil.chargethresholdhelper.
Apr 29 16:07:24 d-arch systemd[1]: Started dbus-:1.2-org.kde.powerdevil.chargethresholdhelper@0.service.
Apr 29 16:07:24 d-arch systemd[1]: Created slice Slice /system/dbus-:1.2-org.kde.powerdevil.backlighthelper.
Apr 29 16:07:24 d-arch systemd[1]: Started dbus-:1.2-org.kde.powerdevil.backlighthelper@0.service.
Apr 29 16:07:24 d-arch backlighthelper[1722]: no kernel backlight interface found
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: org.kde.powerdevil.backlighthelper.brightness failed
Apr 29 16:07:24 d-arch systemd[1094]: Started Powerdevil.
Apr 29 16:07:24 d-arch systemd[1094]: Reached target KDE Plasma Workspace.
Apr 29 16:07:24 d-arch systemd[1094]: Reached target Current graphical user session.
Apr 29 16:07:24 d-arch systemd[1094]: Reached target plasma-workspace-wayland.target.
Apr 29 16:07:24 d-arch systemd[1094]: Starting Blueman Applet...
Apr 29 16:07:24 d-arch systemd[1094]: Starting Geoclue Demo agent...
Apr 29 16:07:24 d-arch systemd[1094]: Starting KAlarm...
Apr 29 16:07:24 d-arch systemd[1094]: Starting NetworkManager Applet...
Apr 29 16:07:24 d-arch systemd[1094]: Starting gnome-disk-utility notification plugin for GNOME Settings Daemon...
Apr 29 16:07:24 d-arch systemd[1094]: Starting Pika Backup Monitor...
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: Handle button events action could not check for screen configuration
Apr 29 16:07:24 d-arch systemd[1094]: Starting Discover...
Apr 29 16:07:24 d-arch systemd[1094]: Starting KDE Connect...
Apr 29 16:07:24 d-arch systemd[1094]: Starting Plasma Session Restore...
Apr 29 16:07:24 d-arch systemd[1094]: Starting Yakuake...
Apr 29 16:07:24 d-arch systemd[1094]: Starting qpwgraph...
Apr 29 16:07:24 d-arch systemd[1094]: Starting Print Queue Applet...
Apr 29 16:07:24 d-arch systemd[1094]: Starting start_wineserver.sh...
Apr 29 16:07:24 d-arch systemd[1094]: Starting stereo_output.sh...
Apr 29 16:07:24 d-arch systemd[1094]: Starting surfshark...
Apr 29 16:07:24 d-arch systemd[1094]: Starting KDE Session Restoration...
Apr 29 16:07:24 d-arch systemd[1094]: Starting Portal service (GTK/GNOME implementation)...
Apr 29 16:07:24 d-arch org_kde_powerdevil[1485]: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Apr 29 16:07:24 d-arch stereo_output.sh[1773]: Restarting pipewire...
Apr 29 16:07:24 d-arch systemd[1094]: Started start_wineserver.sh.
Apr 29 16:07:24 d-arch systemd[1094]: Started qpwgraph.
Apr 29 16:07:24 d-arch systemd[1094]: Started KDE Connect.
Apr 29 16:07:24 d-arch systemd[1094]: Started Yakuake.
Apr 29 16:07:24 d-arch systemd[1094]: Started Blueman Applet.
Apr 29 16:07:24 d-arch systemd[1094]: Started stereo_output.sh.
Apr 29 16:07:24 d-arch systemd[1094]: Started Pika Backup Monitor.
Apr 29 16:07:24 d-arch systemd[1094]: app-nm\x2dapplet@autostart.service: Skipped due to 'exec-condition'.
Apr 29 16:07:24 d-arch systemd[1094]: Condition check resulted in NetworkManager Applet being skipped.
Apr 29 16:07:24 d-arch systemd[1094]: Started surfshark.
Apr 29 16:07:24 d-arch systemd[1094]: app-org.gnome.SettingsDaemon.DiskUtilityNotify@autostart.service: Skipped due to 'exec-condition'.
Apr 29 16:07:24 d-arch systemd[1094]: Condition check resulted in gnome-disk-utility notification plugin for GNOME Settings Daemon being skipped.
Apr 29 16:07:24 d-arch systemd[1094]: app-print\x2dapplet@autostart.service: Skipped due to 'exec-condition'.
Apr 29 16:07:24 d-arch systemd[1094]: Condition check resulted in Print Queue Applet being skipped.
Apr 29 16:07:24 d-arch systemd[1094]: Finished KDE Session Restoration.
Apr 29 16:07:24 d-arch systemd[1094]: Started Geoclue Demo agent.
Apr 29 16:07:24 d-arch systemd[1094]: Started KAlarm.
Apr 29 16:07:24 d-arch systemd[1094]: Stopping PipeWire PulseAudio...
Apr 29 16:07:24 d-arch kded6[1396]: context kaput
Apr 29 16:07:24 d-arch kded6[1396]: No object for name "alsa_output.usb-BEHRINGER_UMC204HD_192k-00.pro-output-0"
Apr 29 16:07:24 d-arch kded6[1396]: No object for name "alsa_output.usb-BEHRINGER_UMC204HD_192k-00.pro-output-0"
Apr 29 16:07:24 d-arch kded6[1396]: No object for name "alsa_input.usb-BEHRINGER_UMC204HD_192k-00.pro-input-0"
Apr 29 16:07:24 d-arch kdeconnectd[1669]: context kaput
Apr 29 16:07:24 d-arch kdeconnectd[1669]: No object for name "alsa_output.usb-BEHRINGER_UMC204HD_192k-00.pro-output-0"
Apr 29 16:07:24 d-arch kdeconnectd[1669]: No object for name "alsa_output.usb-BEHRINGER_UMC204HD_192k-00.pro-output-0"
Apr 29 16:07:24 d-arch kdeconnectd[1669]: No object for name "alsa_input.usb-BEHRINGER_UMC204HD_192k-00.pro-input-0"
Apr 29 16:07:24 d-arch systemd[1094]: Stopped PipeWire PulseAudio.
Apr 29 16:07:24 d-arch systemd[1094]: Stopping Multimedia Service Session Manager...
Apr 29 16:07:24 d-arch systemd[1094]: Started Plasma Session Restore.
Apr 29 16:07:24 d-arch systemd[1094]: Started Discover.
Apr 29 16:07:24 d-arch wireplumber[1162]: pw.core: 0x601c67629fc0: leaked proxy 0x601c677a0f20 id:3
Apr 29 16:07:24 d-arch systemd[1094]: Reached target Startup of XDG autostart applications.
Apr 29 16:07:24 d-arch wireplumber[1162]: pw.core: 0x601c67629fc0: leaked proxy 0x601c676bd080 id:4
Apr 29 16:07:24 d-arch wireplumber[1162]: pw.core: 0x601c67629fc0: leaked proxy 0x601c67821e00 id:5
Apr 29 16:07:24 d-arch wireplumber[1162]: pw.core: 0x601c67629fc0: leaked proxy 0x601c677b5370 id:6
Apr 29 16:07:24 d-arch wireplumber[1162]: pw.core: 0x601c67629fc0: leaked proxy 0x601c67731e60 id:7
Apr 29 16:07:24 d-arch wireplumber[1162]: pw.core: 0x601c67629fc0: leaked proxy 0x601c6772b970 id:9
Apr 29 16:07:24 d-arch wireplumber[1162]: pw.core: 0x601c67629fc0: leaked proxy 0x601c67939880 id:13
Apr 29 16:07:24 d-arch wireplumber[1162]: pw.core: 0x601c67629fc0: leaked proxy 0x601c67776900 id:14
Apr 29 16:07:24 d-arch systemd[1]: Starting Accounts Service...
Apr 29 16:07:24 d-arch pika-backup-monitor[1763]: 2026-04-29T23:07:24.580827Z  INFO pika_backup_monitor::init:27: Starting monitor v0.8.2
Apr 29 16:07:24 d-arch systemd[1094]: Starting Virtual filesystem service...
Apr 29 16:07:24 d-arch systemd[1094]: Stopped Multimedia Service Session Manager.
Apr 29 16:07:24 d-arch systemd[1094]: Stopping PipeWire Multimedia Service...
Apr 29 16:07:24 d-arch kwin_wayland[1220]: PipeWire remote error:  connection error
Apr 29 16:07:24 d-arch systemd[1094]: Stopped PipeWire Multimedia Service.
Apr 29 16:07:24 d-arch systemd[1094]: Started PipeWire Multimedia Service.
Apr 29 16:07:24 d-arch systemd[1094]: Started Multimedia Service Session Manager.
Apr 29 16:07:24 d-arch systemd[1094]: Started PipeWire PulseAudio.
Apr 29 16:07:24 d-arch systemd[1094]: Started Virtual filesystem service.
Apr 29 16:07:24 d-arch pika-backup-monitor[1763]: 2026-04-29T23:07:24.627797Z  INFO pika_backup_common::config::loadable:106: Initial load for "/home/d/.config/pika-backup/history.json"
Apr 29 16:07:24 d-arch pika-backup-monitor[1763]: 2026-04-29T23:07:24.627825Z  INFO pika_backup_common::config::loadable:16: Loading file "/home/d/.config/pika-backup/history.json"
Apr 29 16:07:24 d-arch kded6[1396]: No object for name "alsa_output.usb-BEHRINGER_UMC204HD_192k-00.pro-output-0"
Apr 29 16:07:24 d-arch kdeconnectd[1669]: No object for name "alsa_output.usb-BEHRINGER_UMC204HD_192k-00.pro-output-0"
Apr 29 16:07:24 d-arch kdeconnectd[1669]: No object for name "alsa_input.usb-BEHRINGER_UMC204HD_192k-00.pro-input-0"
Apr 29 16:07:24 d-arch kded6[1396]: No object for name "alsa_input.usb-BEHRINGER_UMC204HD_192k-00.pro-input-0"
Apr 29 16:07:24 d-arch kded6[1396]: No object for name "@DEFAULT_SINK@"
Apr 29 16:07:24 d-arch kded6[1396]: No object for name "@DEFAULT_SOURCE@"
Apr 29 16:07:24 d-arch kdeconnectd[1669]: No object for name "@DEFAULT_SINK@"
Apr 29 16:07:24 d-arch pika-backup-monitor[1763]: 2026-04-29T23:07:24.648658Z  INFO pika_backup_common::config::loadable:106: Initial load for "/home/d/.config/pika-backup/backup.json"
Apr 29 16:07:24 d-arch pika-backup-monitor[1763]: 2026-04-29T23:07:24.648677Z  INFO pika_backup_common::config::loadable:16: Loading file "/home/d/.config/pika-backup/backup.json"
Apr 29 16:07:24 d-arch kdeconnectd[1669]: No object for name "@DEFAULT_SOURCE@"
Apr 29 16:07:24 d-arch systemd[1094]: Starting Virtual filesystem service - disk device monitor...
Apr 29 16:07:24 d-arch kdeconnectd[1765]: QThreadStorage: entry 2 destroyed before end of thread 0x5fbed5c62870
Apr 29 16:07:24 d-arch kdeconnectd[1765]: QThreadStorage: entry 1 destroyed before end of thread 0x5fbed5c62870
Apr 29 16:07:24 d-arch kded6[1396]: No object for name "@DEFAULT_SOURCE@"
Apr 29 16:07:24 d-arch kdeconnectd[1669]: No object for name "@DEFAULT_SOURCE@"
Apr 29 16:07:24 d-arch systemd[1094]: Started Cavasik.
Apr 29 16:07:24 d-arch DiscoverNotifier[1788]: couldn't load "/usr/lib/qt6/plugins/discover-notifier/DiscoverPackageKitNotifier.so" because "Cannot load library /usr/lib/qt6/plugins/discover-notifier/DiscoverPackageKitNotifier.so: libpackagekitqt6.so.2: cannot open shared object file: No such file or directory"
Apr 29 16:07:24 d-arch pika-backup-monitor[1763]: 2026-04-29T23:07:24.717817Z  INFO pika_backup_common::config::loadable:16: Loading file "/home/d/.config/pika-backup/schedule_status.json"
Apr 29 16:07:24 d-arch kded6[1396]: Registering ":1.55/StatusNotifierItem" to system tray
Apr 29 16:07:24 d-arch systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Apr 29 16:07:24 d-arch systemd[1094]: Started Portal service (GTK/GNOME implementation).
Apr 29 16:07:24 d-arch systemd[1094]: Started Virtual filesystem service - disk device monitor.
Apr 29 16:07:24 d-arch plasmashell[1443]: PipeWire remote error:  -32 connection error
Apr 29 16:07:24 d-arch wireplumber[1816]: spa.alsa: Path UMC204HD 192k Output is not a volume or mute control
Apr 29 16:07:24 d-arch systemd[1]: Started RealtimeKit Scheduling Policy Service.
Apr 29 16:07:24 d-arch rtkit-daemon[1940]: Handling system-suspend using logind.
Apr 29 16:07:24 d-arch accounts-daemon[1801]: Unable to open /etc/tcb: No such file or directory
Apr 29 16:07:24 d-arch systemd[1094]: Starting Xdg Desktop Portal For KDE...
Apr 29 16:07:24 d-arch accounts-daemon[1801]: couldn't list homed users: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.freedesktop.home1': activation request failed: unknown unit
Apr 29 16:07:24 d-arch plasmashell[1443]: context kaput
Apr 29 16:07:25 d-arch accounts-daemon[1801]: started daemon version 26.13.0
Apr 29 16:07:25 d-arch systemd[1]: Started Accounts Service.
Apr 29 16:07:25 d-arch systemd[1094]: Started Xdg Desktop Portal For KDE.
Apr 29 16:07:25 d-arch systemd[1094]: Starting flatpak session helper...
Apr 29 16:07:25 d-arch systemd[1094]: Started Portal service.
Apr 29 16:07:25 d-arch kwin_wayland[1220]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/1220/root")
Apr 29 16:07:25 d-arch systemd[1094]: Started flatpak session helper.
Apr 29 16:07:25 d-arch ksmserver[1394]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.ksmserver'")
Apr 29 16:07:25 d-arch xembedsniproxy[1486]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.xembedsniproxy'")
Apr 29 16:07:25 d-arch gmenudbusmenuproxy[1482]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.gmenudbusmenuproxy'")
Apr 29 16:07:25 d-arch polkit-kde-authentication-agent-1[1484]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/1484/root")
Apr 29 16:07:25 d-arch kded6[1396]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.kded6'")
Apr 29 16:07:25 d-arch kactivitymanagerd[1476]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.ActivityManager'")
Apr 29 16:07:25 d-arch org_kde_powerdevil[1485]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.org_kde_powerdevil'")
Apr 29 16:07:25 d-arch kded6[1396]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.kded6'")
Apr 29 16:07:25 d-arch ksecretd[1171]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Apr 29 16:07:25 d-arch kwin_wayland[1220]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/1220/root")
Apr 29 16:07:25 d-arch kaccess[1483]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Apr 29 16:07:25 d-arch kactivitymanagerd[1476]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.ActivityManager'")
Apr 29 16:07:25 d-arch ksmserver[1394]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.ksmserver'")
Apr 29 16:07:25 d-arch plasmashell[1443]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Apr 29 16:07:25 d-arch gmenudbusmenuproxy[1482]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.gmenudbusmenuproxy'")
Apr 29 16:07:25 d-arch kdeconnectd[1669]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Apr 29 16:07:25 d-arch org_kde_powerdevil[1485]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Apr 29 16:07:25 d-arch xembedsniproxy[1486]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.xembedsniproxy'")
Apr 29 16:07:25 d-arch polkit-kde-authentication-agent-1[1484]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/1484/root")
Apr 29 16:07:25 d-arch xdg-desktop-portal-kde[1973]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Apr 29 16:07:25 d-arch DiscoverNotifier[1788]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Apr 29 16:07:25 d-arch qpwgraph[1768]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Apr 29 16:07:25 d-arch wireplumber[1816]: spa.bluez5: BlueZ system service is not available
Apr 29 16:07:25 d-arch pika-backup-monitor[1763]: 2026-04-29T23:07:25.195104Z  INFO pika_backup_common::config::loadable:16: Loading file "/home/d/.config/pika-backup/history.json"
Apr 29 16:07:25 d-arch systemd[1094]: Started app-flatpak-org.kde.yakuake-3631197238.scope.
Apr 29 16:07:25 d-arch kded6[1396]: No object for name "auto_null"
Apr 29 16:07:25 d-arch kdeconnectd[1669]: No object for name "auto_null"
Apr 29 16:07:25 d-arch kded6[1396]: No object for name "@DEFAULT_SOURCE@"
Apr 29 16:07:25 d-arch kdeconnectd[1669]: No object for name "@DEFAULT_SOURCE@"
Apr 29 16:07:25 d-arch kded6[1396]: No object for name "@DEFAULT_SINK@"
Apr 29 16:07:25 d-arch kded6[1396]: No object for name "@DEFAULT_SOURCE@"
Apr 29 16:07:25 d-arch kdeconnectd[1669]: No object for name "@DEFAULT_SINK@"
Apr 29 16:07:25 d-arch kdeconnectd[1669]: No object for name "@DEFAULT_SOURCE@"
Apr 29 16:07:25 d-arch kdeconnectd[1669]: No object for name "@DEFAULT_SINK@"
Apr 29 16:07:25 d-arch kded6[1396]: No object for name "@DEFAULT_SINK@"
Apr 29 16:07:25 d-arch kded6[1396]: No object for name "@DEFAULT_SOURCE@"
Apr 29 16:07:25 d-arch kdeconnectd[1669]: No object for name "@DEFAULT_SOURCE@"
Apr 29 16:07:25 d-arch kded6[1396]: No object for name "alsa_input.usb-BEHRINGER_UMC204HD_192k-00.pro-input-0"
Apr 29 16:07:25 d-arch kdeconnectd[1669]: No object for name "alsa_input.usb-BEHRINGER_UMC204HD_192k-00.pro-input-0"
Apr 29 16:07:25 d-arch wireplumber[1816]: wp-device: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
Apr 29 16:07:25 d-arch wireplumber[1816]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.
Apr 29 16:07:25 d-arch blueman-applet[1756]: blueman-applet 16.07.25 WARNING  PluginManager:93 load_plugin: Failed to start plugin GameControllerWakelock: Only X11 platform is supported
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:3977:3-22: No property named "-gtk-outline-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4094:3-29: No property named "-GtkWidget-window-dragging"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4108:9-37: No property named "-gtk-outline-top-left-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4110:9-38: No property named "-gtk-outline-top-right-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4113:9-40: No property named "-gtk-outline-bottom-left-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4115:9-41: No property named "-gtk-outline-bottom-right-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4118:5-33: No property named "-gtk-outline-top-left-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4120:5-34: No property named "-gtk-outline-top-right-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4123:5-36: No property named "-gtk-outline-bottom-left-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4125:5-37: No property named "-gtk-outline-bottom-right-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4131:7-36: No property named "-gtk-outline-top-right-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4133:7-39: No property named "-gtk-outline-bottom-right-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4136:7-35: No property named "-gtk-outline-top-left-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4138:7-38: No property named "-gtk-outline-bottom-left-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4212:23-37: Not a valid image
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4251:3-31: No property named "-gtk-outline-top-left-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4253:3-32: No property named "-gtk-outline-top-right-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4260:3-34: No property named "-gtk-outline-bottom-left-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4262:3-35: No property named "-gtk-outline-bottom-right-radius"
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4930:12-17: "shade" is not a valid color name.
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:4990:12-17: "shade" is not a valid color name.
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:5017:12-15: "mix" is not a valid color name.
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:5021:12-15: "mix" is not a valid color name.
Apr 29 16:07:25 d-arch python3[1924]: Theme parser warning: gtk-dark.css:5222:3-5223:1: Expected ';' at end of block
Apr 29 16:07:25 d-arch python3[1924]: Theme parser error: gtk-dark.css:5253:3-19: No property named "-gtk-icon-effect"
Apr 29 16:07:25 d-arch blueman-applet[1756]: blueman-applet 16.07.25 WARNING  PluginManager:153 __load_plugin: Not loading DhcpClient because its conflict has higher priority
Apr 29 16:07:25 d-arch blueman-applet[1756]: blueman-applet 16.07.25 WARNING  PluginManager:153 __load_plugin: Not loading PPPSupport because its conflict has higher priority
Apr 29 16:07:25 d-arch blueman-applet[1756]: blueman-applet 16.07.25 WARNING  DiscvManager:122 update_menuitems: warning: Adapter is None
Apr 29 16:07:25 d-arch python3[1924]: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
Apr 29 16:07:25 d-arch systemd[1094]: Reload requested from client PID 2080 ('systemctl') (unit app-surfshark@autostart.service)...
Apr 29 16:07:25 d-arch systemd[1094]: Reloading...
Apr 29 16:07:25 d-arch systemd-xdg-autostart-generator[2102]: Exec binary '/opt/paloaltonetworks/globalprotect/PanGPUI' does not exist: No such file or directory
Apr 29 16:07:25 d-arch systemd-xdg-autostart-generator[2102]: /etc/xdg/autostart/PanGPUI.desktop: not generating unit, executable specified in Exec= does not exist.
Apr 29 16:07:25 d-arch kded6[1396]: Registering ":1.70/StatusNotifierItem" to system tray
Apr 29 16:07:25 d-arch systemd[1094]: Reloading finished in 201 ms.
Apr 29 16:07:26 d-arch systemd[1094]: surfsharkd.service: unit configures an IP firewall, but not running as root.
Apr 29 16:07:26 d-arch systemd[1094]: surfsharkd.service: (This warning is only shown for the first unit using IP firewalling.)
Apr 29 16:07:26 d-arch systemd[1094]: Started Surfshark Daemon.
Apr 29 16:07:26 d-arch stereo_output.sh[1773]: Adding empty stereo-output sink
Apr 29 16:07:26 d-arch stereo_output.sh[2179]: 536870916
Apr 29 16:07:26 d-arch stereo_output.sh[1773]: Setting default sink to stereo-output
Apr 29 16:07:26 d-arch stereo_output.sh[1773]: Setting stereo-output volume to 0.33
Apr 29 16:07:26 d-arch gjs[2149]: JS LOG: [SHUTDOWN-MONITOR] Log file is: /home/d/.local/state/Surfshark/logs/shutdown.log
Apr 29 16:07:26 d-arch gjs[2149]: JS LOG: [SHUTDOWN-MONITOR] Successfully subscribed to PrepareForShutdown signal (ID: 16)
Apr 29 16:07:26 d-arch stereo_output.sh[1773]: Changing buffer size to 512 and samplerate to 48khz
Apr 29 16:07:26 d-arch gjs[2149]: JS LOG: current connection: {"id":"ABELBAKER","type":"802-11-wireless","uuid":"1d764134-0c0a-40de-9d71-fc99b9b47082","wireless_security":{"key_mgmt":"wpa-psk"},"internal_networks":[{"gateway":"192.168.1.1","protocol":"ipv4","address":"192.168.1.153","family":24,"_noncompliant":false}],"interface_name":null,"_noncompliant":false}
Apr 29 16:07:26 d-arch stereo_output.sh[2192]: Found "settings" metadata 31
Apr 29 16:07:26 d-arch stereo_output.sh[2192]: set property: id:0 key:clock.force-quantum value:512 type:(null)
Apr 29 16:07:26 d-arch stereo_output.sh[2193]: Found "settings" metadata 31
Apr 29 16:07:26 d-arch stereo_output.sh[2193]: set property: id:0 key:clock.force-rate value:48000 type:(null)
Apr 29 16:07:26 d-arch stereo_output.sh[1773]: Linking stereo-output to interface
Apr 29 16:07:26 d-arch stereo_output.sh[1773]: Linking stereo-output to speakers
Apr 29 16:07:26 d-arch stereo_output.sh[1773]: Linking stereo-output to cavasik
Apr 29 16:07:26 d-arch stereo_output.sh[2216]: failed to link ports: File exists
Apr 29 16:07:26 d-arch stereo_output.sh[2226]: failed to link ports: File exists
Apr 29 16:07:26 d-arch systemd[1094]: app-stereo_output.sh@autostart.service: Main process exited, code=exited, status=255/EXCEPTION
Apr 29 16:07:26 d-arch systemd[1094]: app-stereo_output.sh@autostart.service: Failed with result 'exit-code'.
Apr 29 16:07:26 d-arch kded6[1396]: Registering ":1.73/StatusNotifierItem" to system tray
Apr 29 16:07:26 d-arch gjs[2149]: JS LOG: [SHUTDOWN-MONITOR] Shutdown inhibit handle acquired 13
Apr 29 16:07:26 d-arch gjs[2149]: JS LOG: Handle ipc method version
Apr 29 16:07:26 d-arch gjs[2149]: JS LOG: Handle ipc method onNetStateChange
Apr 29 16:07:26 d-arch gjs[2149]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
                                  fB/</<@/opt/Surfshark/resources/dist/resources/surfsharkd.js:2:404273
                                  @/opt/Surfshark/resources/dist/resources/surfsharkd.js:2:559708
                                  @/opt/Surfshark/resources/dist/resources/surfsharkd.js:2:559713
                                  @/opt/Surfshark/resources/dist/resources/surfsharkd.js:2:559719
Apr 29 16:07:26 d-arch gjs[2149]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
                                  fB/</<@/opt/Surfshark/resources/dist/resources/surfsharkd.js:2:404273
                                  @/opt/Surfshark/resources/dist/resources/surfsharkd.js:2:559708
                                  @/opt/Surfshark/resources/dist/resources/surfsharkd.js:2:559713
                                  @/opt/Surfshark/resources/dist/resources/surfsharkd.js:2:559719
Apr 29 16:07:26 d-arch gjs[2149]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
                                  fA/</<@/opt/Surfshark/resources/dist/resources/surfsharkd.js:2:403938
                                  @/opt/Surfshark/resources/dist/resources/surfsharkd.js:2:559708
                                  @/opt/Surfshark/resources/dist/resources/surfsharkd.js:2:559713
                                  @/opt/Surfshark/resources/dist/resources/surfsharkd.js:2:559719
Apr 29 16:07:26 d-arch gjs[2149]: JS LOG: Handle ipc method getState
Apr 29 16:07:27 d-arch gjs[2149]: JS LOG: Handle ipc method getLastShutdownTs
Apr 29 16:07:27 d-arch gjs[2149]: JS LOG: Handle ipc method logInfo
Apr 29 16:07:27 d-arch gjs[2149]: JS LOG: #### VPN session Ended
Apr 29 16:07:27 d-arch gjs[2149]: JS LOG: Handle ipc method clearLastShutdownTs
Apr 29 16:07:27 d-arch plasmashell[1443]: QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/modules/kdeconnect/devices/8e1b8831b12d4b84a462109f49a7b225/notifications'")
Apr 29 16:07:27 d-arch plasmashell[1443]: QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/modules/kdeconnect/devices/8e1b8831b12d4b84a462109f49a7b225/notifications'")
Apr 29 16:07:27 d-arch gjs[2149]: JS LOG: Handle ipc method getState
Apr 29 16:07:27 d-arch gjs[2149]: JS LOG: Handle ipc method removeConnection
Apr 29 16:07:27 d-arch gjs[2149]: JS LOG: Handle ipc method removeConnection
Apr 29 16:07:28 d-arch systemd[1]: Stopping User Manager for UID 967...
Apr 29 16:07:28 d-arch systemd[975]: Activating special unit Exit the Session...
Apr 29 16:07:28 d-arch systemd[975]: Stopped target Main User Target.
Apr 29 16:07:28 d-arch systemd[975]: Stopped target Basic System.
Apr 29 16:07:28 d-arch systemd[975]: Stopped target Paths.
Apr 29 16:07:28 d-arch systemd[975]: Stopped Submitting pending crash events (file monitor).
Apr 29 16:07:28 d-arch systemd[975]: Stopped target Sockets.
Apr 29 16:07:28 d-arch systemd[975]: Stopped target Sound Card.
Apr 29 16:07:28 d-arch systemd[975]: Stopped target Timers.
Apr 29 16:07:28 d-arch systemd[975]: Closed GnuPG network certificate management daemon.
Apr 29 16:07:28 d-arch systemd[975]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 29 16:07:28 d-arch systemd[975]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 29 16:07:28 d-arch systemd[975]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 29 16:07:28 d-arch systemd[975]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 29 16:07:28 d-arch systemd[975]: Closed GnuPG public key management service.
Apr 29 16:07:28 d-arch systemd[975]: Closed p11-kit server.
Apr 29 16:07:28 d-arch systemd[975]: Closed PipeWire PulseAudio.
Apr 29 16:07:28 d-arch systemd[975]: Closed PipeWire Multimedia System Sockets.
Apr 29 16:07:28 d-arch systemd[975]: Closed Query the User Interactively for a Password.
Apr 29 16:07:28 d-arch systemd[975]: Closed Disk Image Download Service Socket.
Apr 29 16:07:28 d-arch systemd[975]: Closed Journal Log Access Socket.
Apr 29 16:07:28 d-arch systemd[975]: Closed Virtual Machine and Container Registration Service Socket.
Apr 29 16:07:28 d-arch dbus-broker[993]: Dispatched 307 messages @ 1(±2)μs / message.
Apr 29 16:07:28 d-arch systemd[975]: Stopping D-Bus User Message Bus...
Apr 29 16:07:28 d-arch systemd[975]: Stopped D-Bus User Message Bus.
Apr 29 16:07:28 d-arch systemd[975]: Removed slice User Core Session Slice.
Apr 29 16:07:28 d-arch systemd[975]: Closed D-Bus User Message Bus Socket.
Apr 29 16:07:28 d-arch systemd[975]: Removed slice User Application Slice.
Apr 29 16:07:28 d-arch systemd[975]: Reached target Shutdown.
Apr 29 16:07:28 d-arch systemd[975]: Finished Exit the Session.
Apr 29 16:07:28 d-arch systemd[975]: Reached target Exit the Session.
Apr 29 16:07:28 d-arch systemd-logind[791]: Removed session 1.
Apr 29 16:07:28 d-arch (sd-pam)[977]: pam_unix(systemd-user:session): session closed for user sddm
Apr 29 16:07:28 d-arch systemd[1]: user@967.service: Deactivated successfully.
Apr 29 16:07:28 d-arch systemd[1]: Stopped User Manager for UID 967.
Apr 29 16:07:28 d-arch systemd[1]: Stopping User Runtime Directory /run/user/967...
Apr 29 16:07:28 d-arch systemd[1]: run-user-967.mount: Deactivated successfully.
Apr 29 16:07:28 d-arch systemd[1]: user-runtime-dir@967.service: Deactivated successfully.
Apr 29 16:07:28 d-arch systemd[1]: Stopped User Runtime Directory /run/user/967.
Apr 29 16:07:28 d-arch systemd[1]: Removed slice User Slice of UID 967.
Apr 29 16:07:28 d-arch systemd[1]: user-967.slice: Consumed 1.265s CPU time over 16.948s wall clock time, 366.1M memory peak.
Apr 29 16:07:29 d-arch gjs[2149]: JS LOG: Handle ipc method getState
Apr 29 16:07:29 d-arch kded6[1396]: Registering ":1.81/StatusNotifierItem" to system tray
Apr 29 16:07:31 d-arch systemd[1]: dbus-:1.2-org.kde.kded.smart@0.service: Deactivated successfully.
Apr 29 16:07:34 d-arch systemd[1]: dbus-:1.2-org.kde.powerdevil.discretegpuhelper@0.service: Deactivated successfully.
Apr 29 16:07:34 d-arch systemd[1]: dbus-:1.2-org.kde.powerdevil.chargethresholdhelper@0.service: Deactivated successfully.
Apr 29 16:07:34 d-arch systemd[1]: dbus-:1.2-org.kde.powerdevil.backlighthelper@0.service: Deactivated successfully.
Apr 29 16:07:39 d-arch systemd-timesyncd[596]: Contacted time server [2602:81c:1000:2::199]:123 (2.arch.pool.ntp.org).
Apr 29 16:07:39 d-arch systemd-timesyncd[596]: Initial clock synchronization to Wed 2026-04-29 16:07:39.435291 PDT.
Apr 29 16:07:43 d-arch systemd-logind[791]: The system will suspend now!
Apr 29 16:07:43 d-arch rtkit-daemon[1940]: Demoting known real-time threads.
Apr 29 16:07:43 d-arch rtkit-daemon[1940]: Demoted 0 threads.
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.6583] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.6584] device (enp6s0): state change: unavailable -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 29 16:07:43 d-arch kwin_wayland[1220]: Failed to delay sleep: The operation inhibition has been requested for is already running
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.6922] device (/net/connman/iwd/0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.6924] manager: NetworkManager state is now DISABLED (ASLEEP)
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.6926] device (wlan0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Apr 29 16:07:43 d-arch systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 29 16:07:43 d-arch systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 29 16:07:43 d-arch iwd[789]: event: state, old: connected, new: disconnecting
Apr 29 16:07:43 d-arch kernel: wlan0: deauthenticating from 38:88:71:4a:22:18 by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 29 16:07:43 d-arch iwd[789]: event: state, old: disconnecting, new: disconnected
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.8752] device (wlan0): new IWD device state is disconnecting
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.8754] device (wlan0): new IWD device state is disconnected
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.8755] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.8772] dhcp4 (wlan0): canceled DHCP transaction
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.8772] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.8772] dhcp4 (wlan0): state changed no lease
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.8773] dhcp6 (wlan0): canceled DHCP transaction
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.8773] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.8774] dhcp6 (wlan0): state changed no lease
Apr 29 16:07:43 d-arch NetworkManager[788]: <info>  [1777504063.9361] device (wlan0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 29 16:07:43 d-arch gjs[2149]: JS LOG: current connection: null
Apr 29 16:07:44 d-arch systemd[1]: Reached target Sleep.
Apr 29 16:07:44 d-arch systemd[1]: Starting System Suspend...
Apr 29 16:07:44 d-arch kscreenlocker_greet[2343]: Data set on unsupported clipboard mode. QMimeData object will be deleted.
Apr 29 16:07:44 d-arch systemd[1]: session-2.scope: Unit now frozen-by-parent.
Apr 29 16:07:44 d-arch systemd[1]: user.slice: Unit now frozen.
Apr 29 16:07:44 d-arch systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Apr 29 16:07:44 d-arch systemd-sleep[2405]: Successfully froze unit 'user.slice'.
Apr 29 16:07:44 d-arch systemd[1]: user@1000.service: Unit now frozen-by-parent.
Apr 29 16:07:44 d-arch systemd-sleep[2405]: Performing sleep operation 'suspend'...
Apr 29 16:07:44 d-arch kernel: PM: suspend entry (deep)
Apr 29 16:07:44 d-arch kernel: Filesystems sync: 0.041 seconds
Apr 29 16:07:55 d-arch kernel: Freezing user space processes
Apr 29 16:07:55 d-arch kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Apr 29 16:07:55 d-arch kernel: OOM killer disabled.
Apr 29 16:07:55 d-arch kernel: Freezing remaining freezable tasks
Apr 29 16:07:55 d-arch kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Apr 29 16:07:55 d-arch kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 29 16:07:55 d-arch kernel: serial 00:04: disabled
Apr 29 16:07:55 d-arch kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Apr 29 16:07:55 d-arch systemd-sleep[2405]: System returned from sleep operation 'suspend'.
Apr 29 16:07:55 d-arch kernel: ata1.00: Entering standby power mode
Apr 29 16:07:55 d-arch kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache
Apr 29 16:07:55 d-arch kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Apr 29 16:07:55 d-arch kernel: ata3.00: Entering standby power mode
Apr 29 16:07:55 d-arch kernel: ata2.00: Entering standby power mode
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
Apr 29 16:07:55 d-arch kernel: ACPI: PM: Preparing to enter system sleep state S3
Apr 29 16:07:55 d-arch kernel: ACPI: PM: Saving platform NVS memory
Apr 29 16:07:55 d-arch kernel: Disabling non-boot CPUs ...
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 15 is now offline
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 14 is now offline
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 13 is now offline
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 12 is now offline
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 11 is now offline
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 10 is now offline
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 9 is now offline
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 8 is now offline
Apr 29 16:07:55 d-arch kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 7 is now offline
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 6 is now offline
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 5 is now offline
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 4 is now offline
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 3 is now offline
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 2 is now offline
Apr 29 16:07:55 d-arch kernel: smpboot: CPU 1 is now offline
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: microcode: reload revision: 0x0a50000c
Apr 29 16:07:55 d-arch kernel: ACPI: PM: Low-level resume complete
Apr 29 16:07:55 d-arch kernel: ACPI: PM: Restoring platform NVS memory
Apr 29 16:07:55 d-arch kernel: AMD-Vi: Virtual APIC enabled
Apr 29 16:07:55 d-arch kernel: AMD-Vi: Virtual APIC enabled
Apr 29 16:07:55 d-arch kernel: LVT offset 0 assigned for vector 0x400
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: Enabling non-boot CPUs ...
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU1 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU2 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU3 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU4 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU5 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 6 APIC 0xc
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU6 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 7 APIC 0xe
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU7 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 8 APIC 0x1
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Apr 29 16:07:55 d-arch kernel: CPU8 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 9 APIC 0x3
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU9 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 10 APIC 0x5
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU10 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 11 APIC 0x7
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU11 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 12 APIC 0x9
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU12 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 13 APIC 0xb
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU13 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 14 APIC 0xd
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU14 is up
Apr 29 16:07:55 d-arch kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf
Apr 29 16:07:55 d-arch kernel: microcode: No sha256 digest for patch ID: 0xa500012 found
Apr 29 16:07:55 d-arch kernel: CPU15 is up
Apr 29 16:07:55 d-arch kernel: ACPI: PM: Waking up from system sleep state S3
Apr 29 16:07:55 d-arch kernel: xhci_hcd 0000:04:00.0: xHC error in resume, USBSTS 0x401, Reinit
Apr 29 16:07:55 d-arch kernel: usb usb1: root hub lost power or was reset
Apr 29 16:07:55 d-arch kwin_wayland[1220]: Libinput: event0  - Power Button: client bug: event processing lagging behind by 3339ms, your system is too slow
Apr 29 16:07:55 d-arch kernel: usb usb2: root hub lost power or was reset
Apr 29 16:07:55 d-arch kwin_wayland[1220]: Libinput: event1  - Power Button: client bug: event processing lagging behind by 3339ms, your system is too slow
Apr 29 16:07:55 d-arch rtkit-daemon[1940]: Resuming known real-time threads.
Apr 29 16:07:55 d-arch kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000800000).
Apr 29 16:07:55 d-arch kwin_wayland[1220]: Libinput: event3  - SONiX USB DEVICE: client bug: event processing lagging behind by 3283ms, your system is too slow
Apr 29 16:07:55 d-arch rtkit-daemon[1940]: Resumed scheduling 0 threads.
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: PSP is resuming...
Apr 29 16:07:55 d-arch systemd[1]: session-2.scope: Unit now thawed.
Apr 29 16:07:55 d-arch kernel: serial 00:04: activated
Apr 29 16:07:55 d-arch systemd[1]: user@1000.service: Unit now thawed.
Apr 29 16:07:55 d-arch kernel: nvme nvme0: 16/0/0 default/read/poll queues
Apr 29 16:07:55 d-arch systemd[1]: user-1000.slice: Unit now thawed.
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: reserve 0xa00000 from 0x81fd000000 for PSP TMR
Apr 29 16:07:55 d-arch systemd[1]: user.slice: Unit now thawed.
Apr 29 16:07:55 d-arch kernel: usb 1-2: WARN: invalid context state for evaluate context command.
Apr 29 16:07:55 d-arch systemd-sleep[2405]: Successfully thawed unit 'user.slice'.
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available
Apr 29 16:07:55 d-arch systemd[1]: systemd-suspend.service: Deactivated successfully.
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Apr 29 16:07:55 d-arch systemd[1]: Finished System Suspend.
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
Apr 29 16:07:55 d-arch systemd[1]: Stopped target Sleep.
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b3200 (59.50.0)
Apr 29 16:07:55 d-arch systemd[1]: Reached target Suspend.
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
Apr 29 16:07:55 d-arch systemd-logind[791]: Operation 'suspend' finished.
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable
Apr 29 16:07:55 d-arch NetworkManager[788]: <info>  [1777504075.6730] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
Apr 29 16:07:55 d-arch NetworkManager[788]: <info>  [1777504075.6731] device (enp6s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Apr 29 16:07:55 d-arch kernel: [drm] kiq ring mec 2 pipe 1 q 0
Apr 29 16:07:55 d-arch systemd[1]: Starting Load/Save RF Kill Switch Status...
Apr 29 16:07:55 d-arch kernel: [drm] DMUB hardware initialized: version=0x02020021
Apr 29 16:07:55 d-arch systemd[1]: Stopped target Suspend.
Apr 29 16:07:55 d-arch kernel: ata4: SATA link down (SStatus 0 SControl 300)
Apr 29 16:07:55 d-arch kdeconnectd[1669]: No local bluetooth adapter found
Apr 29 16:07:55 d-arch kernel: ata5: SATA link down (SStatus 0 SControl 330)
Apr 29 16:07:55 d-arch kdeconnectd[1669]: No local bluetooth adapter found
Apr 29 16:07:55 d-arch kernel: usb 1-2: reset full-speed USB device number 2 using xhci_hcd
Apr 29 16:07:55 d-arch kscreenlocker_greet[2343]: Data set on unsupported clipboard mode. QMimeData object will be deleted.
Apr 29 16:07:55 d-arch kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr 29 16:07:55 d-arch kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr 29 16:07:55 d-arch kernel: sd 2:0:0:0: [sdc] Starting disk
Apr 29 16:07:55 d-arch kernel: ata3.00: configured for UDMA/133
Apr 29 16:07:55 d-arch kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr 29 16:07:55 d-arch kernel: sd 1:0:0:0: [sdb] Starting disk
Apr 29 16:07:55 d-arch kernel: sd 0:0:0:0: [sda] Starting disk
Apr 29 16:07:55 d-arch kernel: ata2.00: configured for UDMA/133
Apr 29 16:07:55 d-arch kernel: ata1.00: configured for UDMA/133
Apr 29 16:07:55 d-arch kernel: ahci 0000:04:00.1: port does not support device sleep
Apr 29 16:07:55 d-arch kernel: ahci 0000:04:00.1: port does not support device sleep
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 14 on hub 0
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Apr 29 16:07:55 d-arch kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
Apr 29 16:07:55 d-arch kernel: usb 1-5: reset high-speed USB device number 3 using xhci_hcd
Apr 29 16:07:55 d-arch kernel: usb 1-6: WARN: invalid context state for evaluate context command.
Apr 29 16:07:55 d-arch kernel: ata6: failed to resume link (SControl 0)
Apr 29 16:07:55 d-arch kernel: ata6: SATA link down (SStatus 0 SControl 0)
Apr 29 16:07:55 d-arch kernel: usb 1-6: reset full-speed USB device number 4 using xhci_hcd
Apr 29 16:07:55 d-arch kernel: usb 1-10: WARN: invalid context state for evaluate context command.
Apr 29 16:07:55 d-arch org_kde_powerdevil[1485]: [  1704] Udev event detected
Apr 29 16:07:55 d-arch kernel: usb 1-10: reset full-speed USB device number 6 using xhci_hcd
Apr 29 16:07:55 d-arch kernel: usb 1-8: reset high-speed USB device number 5 using xhci_hcd
Apr 29 16:07:55 d-arch kernel: usb 2-4: reset SuperSpeed USB device number 2 using xhci_hcd
Apr 29 16:07:55 d-arch kernel: usb 1-8.1: WARN: invalid context state for evaluate context command.
Apr 29 16:07:55 d-arch kernel: usb 1-8.1: reset full-speed USB device number 7 using xhci_hcd
Apr 29 16:07:55 d-arch kernel: usb 1-8.1: device descriptor read/64, error -32

1-5 is the Behringer, how does the system behave if you never attach that and exclusively use the ALC897 or HDMI sound?

DaforLynx · Today 09:12:34

(For reference, stereo-output is the null sink which I connect the interface and motherboard outputs to simulatneously, through which all audio is routed by default.)

Some new discoveries about what I'm calling the "broken sound" state:
- Sound refuses to output UNLESS the pipewire link between stereo-output and the Behringer is broken, at which point it'll work fine out of the remaining output.
- Sound inputs (microphones) do not work either.
- While in the broken sound state, if I disconnect the link to the interface, play music from my music player, and reconnect it while it's playing (even just one channel!), it loops the same half-second bit of audio over and over even if I press pause. The track timestamp keeps ticking forward, though. But if I disconnect it again, the timestamp jumps back to the bit it was repeating after pressing pause/play again. This is some of the most bizarre behavior I've ever seen.
- Restarting pipewire with

systemctl --user restart pipewire

does NOT fix the issue.

seth wrote:

1-5 is the Behringer, how does the system behave if you never attach that and exclusively use the ALC897 or HDMI sound?

Ok, now here's how things go when I do different sequences of unplugging stuff and sleeping:
- Plugged in with interface connected to stereo-output -> sleep -> wake: sound is broken
- Plugged in with interface connected to stereo-output -> sleep -> unplug interface -> wake: sound is fine out of remaining output
- Plugged in with interface connected to stereo-output -> sleep -> unplug interface -> wake -> replug and reconnect: sound is fine
- Plugged in with interface connected to stereo-output -> sleep -> unplug interface -> replug interface -> wake (interface is still connected to stereo-output): sound is broken
- Plugged in with interface disconnected from stereo-output -> sleep -> wake: sound is fine out of remaining output
- Plugged in with interface disconnected from stereo-output -> sleep -> wake -> reconnect: sound is broken
- Unplug interface -> sleep -> wake: sound is fine out of remaining output
- Unplug interface -> sleep -> wake -> replug interface and reconnect wires: sound is fine
- Unplug interface -> sleep -> replug interface -> wake (wires have been connected automatically for some reason): sound is fine

The commonality behind all the broken states is that the interface is physically plugged in while the computer goes to sleep, and is physically plugged in while the computer wakes. This suggests that sleeping "breaks" the representation of the interface in the kernel, or something, and that representation can only be fixed by reseting it specifically by unplugging and replugging it. That borked representation also silently breaks pipewire and media decoding libraries. Do I have to, like, dig into the driver code to figure this out??? I really hope not.

And another thing - the sleep bug I was talking about in the OP, where it fails to sleep (or maybe successfully sleeps for a split second) and remains turned on with a permanently nonfunctioning monitor output, has returned, and happens roughly 25% of the time at random. This is the journal output when that happens:

Apr 30 01:46:00 d-arch systemd-logind[675]: The system will suspend now!
Apr 30 01:46:00 d-arch rtkit-daemon[1801]: Demoting known real-time threads.
Apr 30 01:46:00 d-arch rtkit-daemon[1801]: Demoted 0 threads.
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.7073] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.7073] device (enp6s0): state change: unavailable -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.7135] device (/net/connman/iwd/0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.7137] manager: NetworkManager state is now DISABLED (ASLEEP)
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.7138] device (wlan0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Apr 30 01:46:00 d-arch kwin_wayland[1060]: Failed to delay sleep: The operation inhibition has been requested for is already running
Apr 30 01:46:00 d-arch systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 30 01:46:00 d-arch systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 30 01:46:00 d-arch iwd[673]: event: state, old: connected, new: disconnecting
Apr 30 01:46:00 d-arch kernel: wlan0: deauthenticating from 38:88:71:4a:22:18 by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 30 01:46:00 d-arch iwd[673]: event: state, old: disconnecting, new: disconnected
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.8388] device (wlan0): new IWD device state is disconnecting
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.8389] device (wlan0): new IWD device state is disconnected
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.8389] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.8406] dhcp4 (wlan0): canceled DHCP transaction
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.8406] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.8406] dhcp4 (wlan0): state changed no lease
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.8407] dhcp6 (wlan0): canceled DHCP transaction
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.8407] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.8407] dhcp6 (wlan0): state changed no lease
Apr 30 01:46:00 d-arch NetworkManager[672]: <info>  [1777538760.8824] device (wlan0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 30 01:46:00 d-arch gjs[2014]: JS LOG: current connection: null
Apr 30 01:46:01 d-arch systemd[1]: Reached target Sleep.
Apr 30 01:46:01 d-arch systemd[1]: Starting System Suspend...
Apr 30 01:46:01 d-arch systemd[1]: session-2.scope: Unit now frozen-by-parent.
Apr 30 01:46:01 d-arch systemd[1]: user@1000.service: Unit now frozen-by-parent.
Apr 30 01:46:01 d-arch systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Apr 30 01:46:01 d-arch systemd[1]: user.slice: Unit now frozen.
Apr 30 01:46:01 d-arch systemd-sleep[3986]: Successfully froze unit 'user.slice'.
Apr 30 01:46:01 d-arch systemd-sleep[3986]: Performing sleep operation 'suspend'...
Apr 30 01:46:01 d-arch kernel: PM: suspend entry (deep)

Again, I don't see any issues at first glance. It seems related to the video card in this case, since unplugging and replugging the monitors doesn't do anything.
But then just now, I tried it, and it DID go to sleep successfully. But when I tried to wake it, my computer entered an undead state where not only did the video card not output anything, but the reset button and even holding the power button to force shut-down didn't work! I had to turn the power supply off and on! Here's the journal output from that:

Apr 30 02:00:24 d-arch systemd-logind[675]: The system will suspend now!
Apr 30 02:00:24 d-arch rtkit-daemon[1808]: Demoting known real-time threads.
Apr 30 02:00:24 d-arch rtkit-daemon[1808]: Demoted 0 threads.
Apr 30 02:00:24 d-arch NetworkManager[672]: <info>  [1777539624.4868] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Apr 30 02:00:24 d-arch NetworkManager[672]: <info>  [1777539624.4869] device (enp6s0): state change: unavailable -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 30 02:00:24 d-arch NetworkManager[672]: <info>  [1777539624.4925] device (/net/connman/iwd/0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 30 02:00:24 d-arch NetworkManager[672]: <info>  [1777539624.4927] device (wlan0): state change: disconnected -> unmanaged (reason 'unmanaged-nm-disabled', managed-type: 'full')
Apr 30 02:00:24 d-arch kwin_wayland[1063]: Failed to delay sleep: The operation inhibition has been requested for is already running
Apr 30 02:00:24 d-arch NetworkManager[672]: <info>  [1777539624.5102] manager: NetworkManager state is now DISABLED (ASLEEP)
Apr 30 02:00:24 d-arch systemd[1]: Reached target Sleep.
Apr 30 02:00:24 d-arch systemd[1]: Starting System Suspend...
Apr 30 02:00:24 d-arch systemd[1]: session-2.scope: Unit now frozen-by-parent.
Apr 30 02:00:24 d-arch systemd[1]: user.slice: Unit now frozen.
Apr 30 02:00:24 d-arch systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Apr 30 02:00:24 d-arch systemd-sleep[4056]: Successfully froze unit 'user.slice'.
Apr 30 02:00:24 d-arch systemd[1]: user@1000.service: Unit now frozen-by-parent.
Apr 30 02:00:24 d-arch systemd-sleep[4056]: Performing sleep operation 'suspend'...
Apr 30 02:00:24 d-arch kernel: PM: suspend entry (deep)

Again...seems like no help. I think my motherboard is cursed.

seth · Today 12:36:03

Since

Apr 29 16:07:07 d-arch kernel: usb 1-8.1: device descriptor read/64, error -32
Apr 29 16:07:07 d-arch kernel: usb 1-8.1: New USB device found, idVendor=0b05, idProduct=190e, bcdDevice= 2.00
Apr 29 16:07:07 d-arch kernel: usb 1-8.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 29 16:07:07 d-arch kernel: usb 1-8.1: Product: ASUS USB-BT500
Apr 29 16:07:07 d-arch kernel: usb 1-8.1: Manufacturer: Realtek
Apr 29 16:07:07 d-arch kernel: usb 1-8.1: SerialNumber: 00E04C239987

is acting up, can you try to attach the DAC to some other usb hub (so it shows up as usb 2-x or usb 3-x ?

If not, is it sufficient to de-authorize the device before and re-authorize it after the sleep?

https://wiki.archlinux.org/title/Power_ … leep_hooks
https://www.kernel.org/doc/Documentatio … zation.txt

You can eg.

grep 1397 -r /sys/bus/usb/devices/*/idVendor

or

grep 0508 -r /sys/bus/usb/devices/*/idVendor

to find the device (in a script)

I had to turn the power supply off and on! Here's the journal output from that:

will render any journal useless.
If there was an incident between the sleep at 1:46 and the (fatal?) sleep at 2:00, that journal segment would be the most interesting bit.

Arch Linux

#1 Yesterday 00:44:35

Media playback stops working after waking from sleep

#2 Yesterday 10:54:33

Re: Media playback stops working after waking from sleep

#3 Yesterday 23:06:00

Re: Media playback stops working after waking from sleep

#4 Yesterday 23:09:55

Re: Media playback stops working after waking from sleep

#5 Yesterday 23:47:15

Re: Media playback stops working after waking from sleep

#6 Today 06:40:52

Re: Media playback stops working after waking from sleep

#7 Today 09:12:34

Re: Media playback stops working after waking from sleep

#8 Today 12:36:03

Re: Media playback stops working after waking from sleep

Board footer