Fedora Linux

2464 readers

6 users here now

All about Fedora Linux

founded 6 years ago

MODERATORS

CAP_NAME_NOW_UPVOTE@lemmy.ml

Has any of you gotten this before? (lemmy.ml)

submitted 1 month ago by lemmy@programming.dev to c/fedora@lemmy.ml

9 comments fedilink hide all child comments

I am using a laptop. I fixed it by turning it off and on.

top 9 comments

sorted by: hot top controversial new old

[–] that_leaflet@lemmy.world 6 points 1 month ago

You probably ran an update before this and updated the screen locker. Then the OS was in a mismatched that caused the screen locker to break.

[–] MummifiedClient5000@feddit.dk 5 points 1 month ago* (last edited 1 month ago)

Yes, I get this regularly on my piece of shit work HP laptop running Ubuntu. It doesn't handle my USB dock well.

Try to do as it says, although it sometimes gets the session number wrong and maybe the F-key too.

[–] salmoura@lemmy.eco.br 5 points 1 month ago

Once, in a Debian work machine. Did as it said, worked flawlessly afterwards.

[–] HiddenLayer555@lemmy.ml 5 points 1 month ago* (last edited 1 month ago) (1 children)

Getting it all the time on Fedora KDE. And Ctrl+alt+F1 (or any other F key) doesn't get me to a terminal and even SSHing into the computer and entering the command doesn't get rid of it (update: I tried the SSH method again and it worked). Been just turning the computer off and on again whenever it shows up.

I think an update broke something and am hoping it gets fixed soon.

[–] mcmxci@mimiclem.me 2 points 3 days ago* (last edited 3 days ago)

Depending on your setup F1 might be occupied. (GDM takes it up on mine) You can try F3-F6 as iirc most distros have 6 ttys

[–] snowfalldreamland@lemmy.ml 3 points 1 month ago

I was able to fix it on my machine by switching from the fedora to the breeze theme

[–] Showroom7561@lemmy.ca 3 points 1 month ago

I'm on Aurora (which is based on Fedora silverblue) and after updating, I started getting that error (yesterday).

Followed the instructions and got back in, but earlier today when I manually locked the PC, I didn't get the error screen, just a mouse and black screen. Followed the same instructions to get back into my desktop.

It's already been reported as a bug, and I think a new update should fix it really soon.

[–] weirdo_from_space@sh.itjust.works 1 points 1 month ago

I got it for the first time today, fixed it rebooting the machine. I hope it doesn't become a common occurence.

[–] whiskers165@lemmy.ml 1 points 1 month ago

Happened once yesterday while setting up and updating Fedora KDE on a 2012 MacBook Pro 9,2. Haven't had it happen since then so I hope it was just a hiccup while I was getting it all up to date