This is a screen shot of the message I am getting. I can get back in but this happens every day. oh dear my screen is pretty dirty but the only way to get a screen shot was to use the camera on my phone. Any way I have included some other info that I hope will help.
First reboot and check again (the last updates included a lot of KDE stuff).
If there are still issues after that, then set everything to default in the System Settings under Screen Locking → Configure Appearance (button in the top right corner).
Tried the reboot, no change
tried setting the screen locking to default
testing so far so good but will see what happens when I leave it over night as it seems to be an issue when it is left over night.
Also thank you for the fast reply.
Well looks like that did not work. The message was on the screen this morning. The same one I posted above. If it helps it has been doing this from the day I installed this distro.
I thought about switching to a different distro. This computer did come with pop OS but I didn’t really like that. So had Tuxedo os on it for a long time but when a new version of your distro came out and it worked great on my home computer I thought I would put it on this one. However this issue exists on this one but not the home one. What I like about Garuda linux is how easy it is to get docker working. Oh my goodness getting that to work on tuxedo OS was a nightmare. The same with most other distros I have tried. So in my opinion Garuda linux is the best because of how easy docker is to install.
loginctl -h
loginctl [OPTIONS...] COMMAND ...
Send control commands to or query the login manager.
Session Commands:
list-sessions List sessions
session-status [ID...] Show session status
show-session [ID...] Show properties of sessions or the manager
activate [ID] Activate a session
lock-session [ID...] Screen lock one or more sessions
unlock-session [ID...] Screen unlock one or more sessions
lock-sessions Screen lock all current sessions
unlock-sessions Screen unlock all current sessions
terminate-session ID... Terminate one or more sessions
kill-session ID... Send signal to processes of a session
User Commands:
list-users List users
user-status [USER...] Show user status
show-user [USER...] Show properties of users or the manager
enable-linger [USER...] Enable linger state of one or more users
disable-linger [USER...] Disable linger state of one or more users
terminate-user USER... Terminate all sessions of one or more users
kill-user USER... Send signal to processes of a user
Seat Commands:
list-seats List seats
seat-status [NAME...] Show seat status
show-seat [NAME...] Show properties of seats or the manager
attach NAME DEVICE... Attach one or more devices to a seat
flush-devices Flush all device associations
terminate-seat NAME... Terminate all sessions on one or more seats
Options:
-h --help Show this help
--version Show package version
--no-pager Do not pipe output into a pager
--no-legend Do not show the headers and footers
--no-ask-password Don't prompt for password
-H --host=[USER@]HOST Operate on remote host
-M --machine=CONTAINER Operate on local container
-p --property=NAME Show only properties by this name
-P NAME Equivalent to --value --property=NAME
-a --all Show all properties, including empty ones
--value When showing properties, only print the value
-l --full Do not ellipsize output
--kill-whom=WHOM Whom to send signal to
-s --signal=SIGNAL Which signal to send
-n --lines=INTEGER Number of journal entries to show
--json=MODE Generate JSON output for list-sessions/users/seats
(takes one of pretty, short, or off)
-j Same as --json=pretty on tty, --json=short otherwise
-o --output=MODE Change journal output mode (short, short-precise,
short-iso, short-iso-precise, short-full,
short-monotonic, short-unix, short-delta,
json, json-pretty, json-sse, json-seq, cat,
verbose, export, with-unit)
See the loginctl(1) man page for details.
Try X11 from login page and test.
Do not leave it on overnight or simply unlock the session
Do you need the lock?
Would like to see the output of some things sudo dmesg | tb – the output will be long, the added |tb will give a link you can post journalctl -p 3 -xb – this shows errors in a pager you scroll through. Post anything of interest around the time of the crash
This will trigger a test lock, use it and give output. Try a few times to see if you can get the crash to be reproduced.
Just found out something important when looking upstream. There’s about to be a huge update. New version was just tagged yesterday with many changes. This may resolve itself shortly
I just checked that termbin link, I don’t see any problem. Just to confirm, you are doing this after the problem occurs, right?
Next time it happens, follow the steps on screen to unlock, and then get the logs. Would still like to see the output of /usr/lib/kscreenlocker_greet --testing regardless of the crash state.
╰─λ /usr/lib/kscreenlocker_greet --testing
kf.svg: The theme "We10XOS-dark" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.svg: The theme "We10XOS-dark" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.plasma.core: The theme "We10XOS-dark" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.plasma.core: The theme "We10XOS-dark" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
Locked at 1747413475
kf.svg: The theme "We10XOS-dark" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
Unlocked
Unlocked
Unlocked
Unlocked
I was trying to figure out if the theme I was using had anything to do with it so set it back to one of the Garuda themes. Not sure if that did anything but no longer getting the messages in my last post. Also as I want to get this tested with out waiting over night I set the power management to 10 minutes for the display turning off as running the locker test commend you had me run didn’t trigger the error but then again neither did that. So as another test I changed the theme back and ran the test command and waiting the 10 minutes for the screen to turn off and still no error. Now I am confused why it no longer shows the error. Maybe need to wait longer.
Needing more time could be the case, but I’m beginning to suspect it was an invalid portion of a past theme. Especially because changing the theme seems to stop it being reproduced. Need reproduction to be certain though.
What do you know of this theme? Do you know when and where you got it? Those errors are very curious.
From those errors, I am assuming you are using a Global Theme?
Looks like the theme had an update 5 days ago. Was the theme kept up to date? If it was up to date, maybe the new version is buggy. Could also be a bad port to Plasma 6 for that theme.
(KDE Global themes can do harm to system as they contain scripts and whatnot. Even if they were not intentionally malicious, they can still do harm.
&
I still remember this bit of news last year. Looks like your issue is hopefully just a bad porting issue though.)
I make sure to keep everything up today and yes In noticed and installed the update. Also the error message was back this morning and I tried to follow the instructions but when I did the Alt + Control + f2 all I got was a screen with the cursor on it. I waited to see if it would do anything and even went to the rest room and came back still same cursor on the screen. So just ended up rebooting.
I might try something though. I may try a total reinstall a garuda and this time leaving the theme alone.
EDIT I thought I installed the theme almost right way.
Interesting, a fresh clean install with no changes had no issues leaving it locked over night. So I am going to call this solved and not use that theme again. I may leave the theme, I do prefer bright themes and not dark themes. Light themes are just easier on the eyes.
Anyway thanks for all the help and you guys are great keep up the good work.
