KDE

5294 readers

93 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago

MODERATORS

[email protected]

Debian KDE - login broken after trying to fix volume keys (lemmy.nz)

submitted 4 months ago by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

(initially posted on /r/KDE but stoked to see there's a community here!)

I have a fairly new Debian KDE install - I've been tweaking and fixing things for the past week quite happily.

Was trying to fix the volume keys not working this evening. Logged into TTY2 and ran showkey --scancodes and showkey --keycodes per a forum post in an attempt to diagnose and fix. When I hit ctrl+alt+F7 to get back to my session, it was back at the login screen, as if I'd typed my password (ie dots entered for password and greyed out as if I'd then hit enter)

And there it stayed.

Reboot brings me to login, type password (fingerprint reader no longer registers) and there it hangs again.

I can log in just fine through the console (incidentally, the fingerprint reader works just fine there). startx will then happily run a gui from there with full access to my files. I've also created a new user via console and I can log in graphically just fine via that one too.

But my main user login remains stubbornly broken. Any ideas on what's happened?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 4 months ago* (last edited 4 months ago) (1 children)

Another thought: Is it possible that your original user account (which hangs) is trying to log in to an X session while the new one (which works) is using a Wayland session, or vice-versa? That might explain the difference in behavior if only one of the two session types is broken.

Good luck!

[–] [email protected] 1 points 4 months ago

Yes, I'd considered that too. Alas, not the case