PCMan-FM QT Devices list started to contain “Volume” entry that appears for a fraction of second then disappears again. It is quite annoying.
To actually read text I needed to record it with Peek at frame rate increased to 60 fps and step frame by frame with VLS.
Relevant System Information:
I detached all drives (except internal SSD), it keeps happening
Noticing it happened on the same day as installing podman but may be a spurious correlation
dmesg repeatedly lists loop9: detected capacity change from 0 to 8
losetup does not have loop9 (though maybe it appears for this fraction of second?)
systemctl status udisks2 has
mar 12 05:20:42 grisznak udisksd[1227]: Error getting 'loop9' information: Failed to get backing file of the device loop9: Failed to read from file “/sys/class/block/loop9>
mar 12 05:20:43 grisznak udisksd[1227]: Error getting 'loop9' information: Failed to get backing file of the device loop9: Failed to open file “/sys/class/block/loop9/loop>
mar 12 05:23:22 grisznak udisksd[1227]: Error getting 'loop9' information: Failed to get backing file of the device loop9: Failed to open file “/sys/class/block/loop9/loop>
mar 12 05:27:31 grisznak udisksd[1227]: Error getting 'loop9' information: Failed to get backing file of the device loop9: Failed to open file “/sys/class/block/loop9/loop>
mar 12 05:30:31 grisznak udisksd[1227]: Error getting 'loop9' information: Failed to get backing file of the device loop9: Failed to read from file “/sys/class/block/loop9>
mar 12 05:31:14 grisznak udisksd[1227]: Error getting 'loop9' information: Failed to get backing file of the device loop9: Failed to read from file “/sys/class/block/loop9>
mar 12 05:36:22 grisznak udisksd[1227]: Error getting 'loop9' information: Failed to get backing file of the device loop9: Failed to open file “/sys/class/block/loop9/loop>
mar 12 05:38:31 grisznak udisksd[1227]: Error getting 'loop9' information: Failed to get backing file of the device loop9: Failed to read from file “/sys/class/block/loop9>
mar 12 05:47:47 grisznak udisksd[1227]: Error getting 'loop9' information: Failed to get backing file of the device loop9: Failed to read from file “/sys/class/block/loop9>
mar 12 05:48:25 grisznak udisksd[1227]: Error getting 'loop9' information: Failed to get backing file of the device loop9: Failed to open file “/sys/class/block/loop9/loop>
and I see quite a lot of snap spam there, repeated in loop:
mar 12 05:53:02 grisznak systemd[1]: Started snapd.service - Snap Daemon.
mar 12 05:53:02 grisznak systemd[1]: snapd.failure.service: Deactivated successfully.
mar 12 05:53:02 grisznak systemd[1]: Finished snapd.failure.service - Failure handling of the snapd snap.
mar 12 05:53:03 grisznak systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
mar 12 05:53:03 grisznak systemd[1]: Cannot find unit for notify message of PID 702948, ignoring.
mar 12 05:53:03 grisznak snapd[702878]: handlers.go:4682: PANIC Re-refresh task has 3 tasks waiting for it.
mar 12 05:53:03 grisznak snapd[702878]: panic: Re-refresh task has 3 tasks waiting for it.
mar 12 05:53:03 grisznak snapd[702878]: goroutine 98 [running]:
mar 12 05:53:03 grisznak snapd[702878]: github.com/snapcore/snapd/logger.Panicf({0x59204d7aac12?, 0x0?}, {0xc000229cb0?, 0x0?, 0x0?})
mar 12 05:53:03 grisznak snapd[702878]: /build/snapd/parts/snapd/build/logger/logger.go:73 +0xe9
mar 12 05:53:03 grisznak snapd[702878]: github.com/snapcore/snapd/overlord/snapstate.(*SnapManager).doCheckReRefresh(0x0?, 0xc0000eb040, 0x59204cdca6b7?)
mar 12 05:53:03 grisznak snapd[702878]: /build/snapd/parts/snapd/build/overlord/snapstate/handlers.go:4682 +0x12b
mar 12 05:53:03 grisznak snapd[702878]: github.com/snapcore/snapd/overlord/state.(*TaskRunner).run.func1()
mar 12 05:53:03 grisznak snapd[702878]: /build/snapd/parts/snapd/build/overlord/state/taskrunner.go:220 +0xb4
mar 12 05:53:03 grisznak snapd[702878]: gopkg.in/tomb%2ev2.(*Tomb).run(0xc00097b900, 0x0?)
mar 12 05:53:03 grisznak snapd[702878]: /build/snapd/parts/snapd/build/vendor/gopkg.in/tomb.v2/tomb.go:163 +0x36
mar 12 05:53:03 grisznak snapd[702878]: created by gopkg.in/tomb%2ev2.(*Tomb).Go
mar 12 05:53:03 grisznak snapd[702878]: /build/snapd/parts/snapd/build/vendor/gopkg.in/tomb.v2/tomb.go:159 +0xee
mar 12 05:53:03 grisznak systemd[1]: snapd.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
mar 12 05:53:03 grisznak systemd[1]: snapd.service: Failed with result 'exit-code'.
mar 12 05:53:03 grisznak systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.
mar 12 05:53:03 grisznak systemd[1]: Starting snapd.service - Snap Daemon...
mar 12 05:53:03 grisznak snapd[702952]: overlord.go:274: Acquiring state lock file
mar 12 05:53:03 grisznak snapd[702952]: overlord.go:279: Acquired state lock file
mar 12 05:53:03 grisznak snapd[702952]: daemon.go:250: started snapd/2.67 (series 16; classic) ubuntu/24.04 (amd64) linux/6.8.0-55-generic.
mar 12 05:53:03 grisznak kernel: loop9: detected capacity change from 0 to 8
mar 12 05:53:03 grisznak snapd[702952]: daemon.go:353: adjusting startup timeout by 1m5s (pessimistic estimate of 30s plus 5s per snap)
mar 12 05:53:03 grisznak systemd[1]: tmp-syscheck\x2dmountpoint\x2d1337510807.mount: Deactivated successfully.
mar 12 05:53:03 grisznak snapd[702952]: backends.go:58: AppArmor status: apparmor is enabled and all features are available (using snapd provided apparmor_parser)
mar 12 05:53:03 grisznak systemd[1]: Cannot find unit for notify message of PID 703012, ignoring.
mar 12 05:53:03 grisznak systemd[1]: Started snapd.service - Snap Daemon.
