[01:43] <semitones_rex> arraybolt3: is lubuntu+1 liveISO supposed to have paplay installed, or aplay, or both?
[01:43] <semitones_rex> mine has aplay, but it plays garbled playback
[01:46] <arraybolt3> a play should be there, not sure about paplay
[01:46] <arraybolt3> What are you trying to play?
[01:46] <arraybolt3> aplay only supports .WAV files as far as I know.
[01:47] <arraybolt3> Also how does it behave if you try playing some audio from YouTube or Pixabay or some such?
[01:48] <semitones_rex> ah ok. Youtube works as expected, so does VLC. I did 'aplay /usr/share/sounds/freedesktop/stereo/complete.oga'
[01:49] <arraybolt3> oh yeah that won't work
[01:50] <arraybolt3> try `aplay /usr/share/sounds/alsa/Front_Center.wav`
[01:50] <arraybolt3> That should sound normal.
[01:51] <semitones_rex> yup that works, sounds great.
[01:53] <semitones_rex> thanks :)
[01:55] <arraybolt3> Happy to help!
[02:01] <sem> arraybolt3: this is a problem... Xscreensaver crashed the system, and I was taking my notes in noblenote
[02:01] <arraybolt3> Crashed the system? How badly?
[02:01] <arraybolt3> X server crash? Kernel panic?
[02:02] <sem> The mouse moved slowly and then stopped moving. I see the desktop but it's unresponsive
[02:03] <sem> This happened when I checked "ok" for "Warning: the Xscreensaver daemon doesn't seem to be running on display ":0". Launch it now?"
[02:04] <sem> I don't seem to be able to access a virtual terminal with ctrl-alt-f1, etc
[02:07] <sem> Do you have any suggestions for how to recover any of this? The contents of noblenote are all I care about
[02:08] <sem> I could also just reboot and write what I can remember
[02:09] <arraybolt3> sem: sounds like you ran out of RAM
[02:09] <sem> oom-killer strikes again
[02:09] <arraybolt3> All those symptoms are characteristic of "thrashing".
[02:09] <sem> I have 6 GB ram
[02:10] <arraybolt3> Best hope is to wait and hope something kicks in and kills whatever is overloading things, otherwise force-reboot.
[02:10] <arraybolt3> How many apps and browser tabs were you using?
[02:11] <arraybolt3> Slow mouse movement transitioning to stop, and inability to switch to TTY, is what thrashing generally does.
[02:11] <sem> Noble note, quassel, file manager, terminal, firmware-updater (hung) 1 tab in Firefox, configuration center, and xscreensaver 
[02:11] <sem> Thanks for teaching me some new vocab
[02:12] <sem> I also tried to start discover twice and that didn't work, but I didn't see it in top 
[02:12] <sem> VLC was giving me some errors about private memory, but I was closing it each time
[02:13] <sem> Oh, also open in notifications bar: nm-applet, clipper, redshift, pavucontrol...
[02:13] <sem> *qclippr
[02:22] <arraybolt3> hmm
[02:22] <arraybolt3> Doesn't sound like that much, that's weird.
[02:26] <sem> Would you recommend I file this "thrashing" bug against xscreensaver since that was the trigger? Or xorg-nouveau since it seems to be display related
[02:35] <arraybolt3> I don't think it was either really.
[02:35] <arraybolt3> Without seeing what program was eating RAM, there's no way to know.
[02:36] <arraybolt3> The program that tipped it into thrashing could be entirely unrelated.
[02:36] <arraybolt3> if for instance the X server suddenly ate up almost all your RAM, you might not thrash yet, but then open another app (like the screensaver) and boom, thrashing
[02:38] <sem> arraybolt3, sounds like i could try to reproduce it, maybe while writing a log to a USB drive so there's something persistent
[02:39] <arraybolt3> Do that, and also open htop and sort by memory used to see if you can spot the top offender.
[02:39] <arraybolt3> (to be clear, open htop, then try to trigger the bug)
[02:45] <sem> gotcha
[02:46] <sem> i'm going to give it some time to see if something in the system recovers enough to kill whatever is misbehaving so I can get my notes back
[02:47] <lotuspsychje> on my NUC i have this xscreensaver bug it consumes 99% cpu
[02:47] <lotuspsychje> but didnt test it on noble yet
[02:48] <lotuspsychje> i got xscreensaver running on my new 24.04 laptop on ubuntu-desktop without issues on wayland
[02:48] <sem> i use xscreensaver extensively on lubuntu 20.04, but I think it is X11
[02:49] <lotuspsychje> never had a crash on lubuntu before
[02:49] <lotuspsychje> i would go the arraybolt3 road, memory and cpu going high on xscreensaver and killing your desk?
[02:49] <sem> this was in the liveISO environment. What you describe sounds likely to me
[02:50] <lotuspsychje> but on the other hand, my nuc is an i7 with intel 650 uhd, should be able to handle a matrix screensaver like a charm
[02:50] <lotuspsychje> so im not sure how this works yet
[02:51] <sem> what does 'nuc' mean in this context? My pc is an antique at this point :) built in 2007
[02:51] <lotuspsychje> bug #1862150
[02:51] -ubottu:#ubuntu-next- Bug 1862150 in xscreensaver (Ubuntu) "Xscreensaver produces high cpu and fan on 18.04" [Undecided, New] https://launchpad.net/bugs/1862150
[02:51] <lotuspsychje> intel NUC
[02:52] <lotuspsychje> what are your specs like sem
[02:53] <sem> AMD athlon 64 x2, 6 gb ram
[02:54] <lotuspsychje> i ran xscreensaver for long on an amd 3200
[02:54] <lotuspsychje> with 2gb
[02:56] <sem> yeah, xscreensaver seems to have no problem on my 20.04 install on the same machine. The main difference is that install uses the nvidia drivers; this one is using nouveau
[02:56] <lotuspsychje> so we can assume this is machine related
[02:56] <lotuspsychje> but we have to prove, why it happens on decent hardware?
[02:57] <sem> yeah; i guess we have to first see if it is indeed the same bug
[02:58] <sem> it probably is though
[02:58] <lotuspsychje> problem with xscreensaver is the moment you move, cpu load goes down and you cant see it anymore
[02:58] <lotuspsychje> so you need to log cpu
=== guiverc2 is now known as guiverc