[04:40] <xu-irc41w> hmm it looks like most of the chicago95 install process is just changing configs
[04:40] <xu-irc41w> that's a REALLY versatile system
[04:40] <xu-irc41w> wow
[04:41] <xu-irc41w> i don't understand why grassmunk hasn't produced a series of automated scripts for these different options
[04:41] <xu-irc41w> i mean he had time to make the theme after all
[17:04] <xu-help97w> Hello there
[17:05] <xu-help97w> Can anyone tell me why I get weird symbols when I start my laptop
[19:09] <indigo_kirisame> weh
=== tomreyn_ is now known as tomreyn
[20:06] <xu-irc69w> anyone around?
[20:48] <acollign> hi everyone ;-), I a looking for hel. I am facin a lock screen issue with a fresh install of xubuntu 23.10. After some idle time, the desktop becomes unresponsive only the mouse can move. I've disabled the lock feature in the screensaver much which seems to have temporarly solved the problem. Anyone facing the same issue?
[20:52] <acollign> there is this old bug which was marked as solved in 2019 https://bugzilla.xfce.org/show_bug.cgi?id=15325
[20:54] <tomreyn> acollign: usually such issues are related to one or more of: suspend/resume and buggy bios, buggy bios (by other means), nvidia graphics with hardware-incompatible proprietary driver series, more recent nvidia graphics with nouveau open source drivers
[20:55] <tomreyn> journalctl -p4 -b     may hint on what's going wrong.
[20:56] <acollign> thanks tomreyn. I am actually using an old macbook pro from 2013... so I am guessing that is all wrong in terms of supported hardware. I don't have the issue with gnome and its locking feature (with gdm) though.
[20:58] <tomreyn> this (not happening on gnome) doesn't have to mean much - screen locking works quite a bit differently there.
[20:58] <acollign> that is what I was assuming, thanks for the confirmation.
[21:01] <tomreyn> you're welcome 
[21:03] <tomreyn> if i had to guess, i'd say it has to do with the mac-ness of this system, i.e. no attempts made to make an OS agnostic bios. but that's pure speculation, the logs might help you analyze this further.
[21:04] <acollign> yep, I just reproduce the issue. I am looking into the logs now
[21:08] <acollign> nothing to report unfortunately.
[21:10] <tomreyn> you can keep a    journalctl -f    running and lock then unlock the screen, hoping it will hint on an error but not break your screen output.
[21:11] <tomreyn> or run it in an ssh shell from another computer, if you can
[21:42] <acollign> thanks for the help so far tomreyn. I will need to dig into this another day. cheers
[21:42] <tomreyn> see you, good luck