>>109453535
Why doesn't it do it by itself?

>>109453638
Isn't that a little too user friendly?

>>109453535
>Fucking.
>WHY.
Wayland.
We told you, don't use gnome, don't use wayland, don't use systemd.

>>109453535
I literally have no idea what this is and I have not ever seen this before
>doesn't post anything about details
100% certain this is bullshit

use case for a screen locker? turn the goddamned thing off ffs

>>109453679
>100% certain this is bullshit
Unfortunately no it isn't. Plasma's Wayland compositor does this when its screen locking software crashes.

>>109453535
I got a kernel panic on a the most basic fedora distro after auto-updating a few months ago. Restoring did not help. Hard to roll a brand new install on top from a live usb. Would be an absolute nightmare for a casual user.

>>109453701
Your disk is dying, back your files up.

>>109453696
the computer machine stops working when it crashes? this is unprecedented.

that's an awesome error message, how do you even get that?

XFCE has never crashed on me

>>109453734
Screensavers haven't been able to kill your whole desktop session since the 90s. It's a huge regression due to a lot of mental illness.

>>109453761
they kinda have, that's why i disabled logonui.exe on Windows XP

>>109453683
shut it off like every 15 minutes?

>>109453696
They should've named it... nowayland heh gottem

>>109453696
>it was KrashDE all along
Maybe use something that isn't in permanent beta status.

>>109453535
What is this? I'm using GNOME and KDE daily on 2 machines. Fedora and Debian. I never saw this (I started 2022)

>>109453535
If the program knows how to solve the problem why doesn't the program solve it?

Windows doesn't need me to ask permission to access my files and folders every time I open the file explorer. Windows doesn't ask me permission to run an antivirus scan. Windows just does things that I want it to just do.

Why doesn't linux? Why can't linux just reboot the screensaver without me doing it manually? Why do I have a computer that requires manual inputs from me all the time like it's a little baby

I want a grown up adult computer, not a little baby computer I have to look after constantly or it breaks itself

can linux just like, grow up?

File: puffy-861007297.gif (69 KB, 800x689)

69 KB GIF

>wake up/roll over
>see another 'linux has a problem thread'
>go back to sleep

File: hyprlock-error-when-enabl(...).png (437 KB, 1920x1078)

437 KB PNG

Here's the hyprland one. I used to see it all the time but ever since a reinstall I haven't seen it. Been about 4 months.

>>109453932
So why is this a thing to begin with? It's such a surface-level thing to occur, and normal updates should not fucking cause this.
At least Linus had the luck of being told that his update/installation of Steam would break something.
Simple updating (and none of that "do you wish to replace 'faggot' with '/extra/faggot'" shit that I always second guess is gonna break something) should not to do shit like this.

>>109453995
I don't know what caused it but I'm willing to admit it was probably something I did, which is why a reinstall fixed it. I fuck around with shit I shouldn't touch all the time and problems from that can sometimes take a long time to show up.

>>109453535
>This is why Linux will never be ready for prime time.
why, exactly?
>windows installation is corrupted, can't load libraries because they're just fucked or nonexistant hence login screen doesn't react to input
No debug information, nothing. Good luck googling how to fix this shit (you can't, reinstall is needed)
>linux installation is corrupted
BUHUU LINUX IS SO BAD BECAUSE IT PRECISELY TOLD ME WHAT TO DO, NOOOOOOOO, WINDOWS IS BETTER BECAUSE I SAID SO
You need psych evaluation, OP.

>Linux has a problem
Yeah the users being too retarded to work shit out.
Even if something breaks "randomly" it's normally not that hard to fix it as long as you aren't some aspie windows licker.

>>109453535
That's because you're not on mint
>It just werks

>>109453995
This doesn't happen on X11 with Xscreensaver.

>>109454026
I literally just ran updates that it told me were available.
I shouldn't have to scour the internet and research every update to find out if it's good or not. That might be fun for a hobbyist OS where one would like to research and troubleshoot, but not when you just want to fart around after a long day and have things just werk.
Truer words have never been spoken, linux really is made for those who do not value their time.

>>109453696
Good to know, using Gentoo testing with KDE Plasma and haven't yet seen that.

>>109454070
bingo

>>109453638
Because that would unlock the screen.

I have been using computers since 2009, when I was 8 yo, never have I ever come across this sort of error on windows.

>The screen locker is broken and unlocking is not possible anymore.
How does this happen?

>>109453676
Do you think a windows refugee knows what any od those things are?

I've been using many many Linux distros as my only OS for like 10+ years, maybe 15 I forgot. I've never had this error and I often fuck up my linux distros installing random stuff or doing random stuff and then spend hours or even days trying to fix it, which I find fun BTW. But in all my Linux time and huge amount of time I've trashed my OS I've never had this happen. KEK, how retarded are you? Every time I update Linux I just run updates via the terminal and never once had an issue, not once, ever.

This even a kernel issue anymore. It's now between getting spoonfed everyday or taking a real DIY approach.
You're going to have to be comfortable with no longer getting spoonfed in the future.

>>109453535
Galyland problems lmoa, use cinnamon with X11 (the default)

>>109453535
kys
>>109453676
This have nothing to do with wayland

>>109453535
Holy based Linux.
On Windows or macOS you'd just be forced to reboot.

File: tenor.gif (101 KB, 498x451)

101 KB GIF

>>109453535
Literally never happened with slock + dwm + X11

I love Linux but
>>109453535
>>109453638
>>109453822
>>109453995
>>109454338
Yeah this is nonsense. It should just restart the screen locker. It knows what user is logged in. A fallback screenlock is better than this shitty message.

these threads always seem so weird to me, i switched to linux like a year ago and have had literally zero issues that weren't resolved after a quick search. What in the fuck kind of usecases or hardware are you guys running to have constant issues?

>>109453535
Skill issue. Use debian

>>109455752
-random Wi-Fi adapters are a common issue
-anons are repeating stories about what happened to their Linux installations decades ago
-having a "minimal" system often leads to bugs due to missing software components

File: 1707888530367950.png (784 KB, 1440x1440)

784 KB PNG

>>109453822
>I want a grown up adult computer, not a little baby computer I have to look after constantly or it breaks itself
>
>can linux just like, grow up?
it did

ot, but i always wonder - i ran windows from 95 to 10, on linux since 1,5 years and I never managed to brick my system. Not with windows updates that suposedly delete my files or bricked my pc, to linux where everything is supposed to break on update. I just set up my system and click update every weekend. Assuming you're not le hacker writing your own components or using literally who meme distros or (((debloat))) windows scripts - how tf do you actually manage to brick your system everyday like i read here, regardless of windows/linux

>>109453701
Fedora was always super crashy. Redhat's entire suite is broken by design, partly so they can sell support contracts and partly because they're just evil and incompetent (see: lennart).

>>109453995
See tpbp: >>109453676

>>109453535
s/linux/gnome/

funny, i've never had slock crash
https://tools.suckless.org/slock/

everyone blames linux for using shit software on linux, this'd be like if i blamed windows every time solidworks crashed

>>109453707
Broken drive won't cause kernel panics.
>>109453701
What module was it?

>>109453638
Something something Stallman.

>>109453868
This
I honestly don't even know how these people get half of these issues. I'm not smart and I've been fine with fucking Arch of all things.

>>109453535
>This is why Linux will never be ready for prime time.
I've been using Linux for over a decade and literally never seen anything like that. I didn't even knew Linux came with a screen locker, I thought it's just a kernel.
You probably should contact your Linux supplier.

>>109453535
Cinnamon, Gnome and xfce dont have this problem

>>109453676
>>109456271
>gnome
>SDDM error

>>109453535
Linux is just a colonel, and I've never seen this issue on Gentoo with openrc and LXQt
In conclusion, install Gentoo

>>109453535
>MS Windows just throws a BSOD. You silly person.

>>109453535
i smell a bait. never happened to me and shit just works on my machine.

>>109453535
Your fault for being so Windows slop pilled that you cannot understand how to use Linux.

Gnome grashes when renaming files on online drives.

File: 1783790919718540.png (217 KB, 532x550)

217 KB PNG

>>109454156

>>109453535
On Windows, you will never see a message like this and yet I absolutely HAVE had it lock up with a black screen when trying to login or switch users. There's no way out in that case except a power cycle.

This is the difference between the two. Given a similar situation, Windows just gives up while (this distro of) Linux gives you instructions for a possible solution. If you aren't able to follow the instructions then you just treat it like Windows and power cycle instead, no harm done.

>>109453535
massive skill issue as usual

>>109453535
If something happens with windows I just hold the power button and loss all unsaved work instead.

>>109453868
pufferfish wit da big ass lip

>>109453535
>This is at least the 7th time this has happened to me and all I did was update.
There's your problem. Serious distros like Fedora do offline updates so this doesn't happen because you can't swap out the screenlocker or Qt framework live from underneath it.

>>109453535
I installed Fedora kde to try since I don't want to upgrade to W11 and after installing Steam it crashes because some 32 bit something is missing. It was the second thing I installed in a fresh OS install, and it crashed.

>>109456291
Yes it will. It messes up the virtual memory subsystem (yes, even if you're not using swap. The kernel demand pages binaries.)

>>109456966
This isn't a problem on X with Xscreensaver.

>>109453535
I mean sure but I can also follow instructions so it's not my problem

>>109463462
XScreensaver would simply leave you with a blackscreen and unable to login. At least the desktops screenlocker fails gracefully and still allows you to log back in.

>>109453535
I've seen this too.
But the stupidest shit happened to me was when I left my computer for twenty minutes. When I came back, the clock on the taskbar was frozen, and I only noticed it an hour later. Instead of showing a message, freezing the entire system, or bsoding, it just froze the clock like nothing happened. That's basic computer function, so unreliable. I've never experienced that on windows in almost 30 years of using it.

>>109453535
i agree linux will never be ready for prime time
but you should just use the tried and true xfce

>>109453707
Brand new laptop, slop apologist.

File: 1768262488252626.jpg (84 KB, 736x978)

84 KB JPG

I don't understand why you faggots are always obsessed with other people using Linux. I've been using Linux since around 2016 and I have never once bitched about other people not wanting to use it.

>>109464226
Heh. I had a brand new SSD die after a couple months this year. It happens.

>>109453535
>Both updating every week or once every 6 months. Across different flavors.
using a rolling release obv. you arent resetting services as the binaries update. rolling release linux distros dont do this for you. opensuse kinda tells you what needs to be restarted. if you dont read what you update, might as well just reboot after every update.

>>109464269
>I don't understand why you faggots are always obsessed with other people using Linux.
IMO other people using it actually makes it worse. Some of us can't stop it though. We find something good and have to tell everyone about it until it's unpleasantly popular.

>>109453676
Pretty sure this was a QT issue

>>109453535
User error.

>>109453535
are you on debian xfce? kinda makes your point moot if you're not.

>>109453535
I'll assume KWin/KDE, yeah? Got this shit two years ago on OpenSUSE Leap after a broken update. Glad to see this is still a possibility...

>>109453995
Linux software isn't that great with regression testing. They are always breaking API/ABIs or something. That's why "dinosaur" stable distros like Debian & Rocky are popular on servers, they slowly update their packages!

>>109460090
That's the thing...Windows (10) generally doesn't fail in the first place, especially for a fucking lock-screen.

>>109463292
False, and fedora breaks more than any other distro in existence because that is redhat's entire business model.

>>109453638
it's made by code monkeys, what do you expect.
same as with ceos, they don't understand what user wants and needs.

>>109454127
gentoo uses elogind, doesn't it? I just login to root and run startx. no need for faggy systemd shite.

>>109466929
I'm using Gentoo with Systemd :^)

>>109453745
This

>>109463436
You need to manually add and install the 32bit libraries that were missing. The Steam client and many older games are 32bit so they won't work without it. Linux was never meant to be used like this which is why there are so many nonsense issues that come up when using it like a normal desktop.

>>109454127
>using Gentoo testing with KDE Plasma
if you upgrade plasma then, without reloading plasma, lock the screen it will happen.
Honestly retards believe the "you don't have to restart linux ever" claim too much.

>>109453535
I haven't seen this screen in ages. Which distros did you see this on, anon?
> Both updating every week or once every 6 months.
Updating once a week isn't frequent enough on rolling release distros. Updating every six months isn't frequent enough on any distro. Sorry to break that to you.

>>109465517
Fedora is fucking shit and I'm tired of people memeing it. Bazzite is the only good flavor of Fedora, and even then it relies on btrfs, which is also shit.

>>109467900
>Updating once a week isn't frequent enough on rolling release distros.
>arch users really think this

>>109453701
Saying Linux is at fault? How long before someone says it's your hardware at fault?
>>109453707
70 seconds.

>>109464226
That won't stop them from claiming it's your hardware. Had the same shit happen with me on a brand new system I put together. Everyone here on /g/ swore up and down it was my hardware dying, the brand new hardware. Wiped Linux, put Win10 on here, zero issues since, because the new hardware is actually flawless and Linux just couldn't do shit right. Even posted some pictures of the hardware tests showing the SSD was brand new and flawless. "YOUR SSD MUST BE DYING AND THE TESTS ARE WRONG, LINUX CAN'T BE AT FAULT!" Linux fags are incapable of accepting the fact Linux isn't perfect, and usually flawed. They aren't power-users, they're a cult.

>>109467929
Linux is a colonel.

>>109467918
It's true though. Don't want to update daily? Don't use a rolling release.

>>109467955
I update security packages every 2 weeks and userland packages just whenever.

>>109467869
you don't.. IF you understand how to do it. most new users don't, which ia why some newbie friendly distros like fedora have introduced offline updates.

just because someone hears you don't need to, doesn't mean there aren't things to consider or do after updating, they just assume there isn't, and assumptions is how you get into trouble. This is also why only new users have problems like this, they don't know how to use linux properly

File: 3506e2df-268a-4afd-b228-4(...).png (2.49 MB, 1536x1024)

2.49 MB PNG

>>109453535
The problem is not that "linux" is broken. Obviously some desktop environments work just fine. The problem is that linux is a free-for-all and you have the choice of using terrible broken software that crashes all the time (OP's choice) or decent software that just works. Normalfags switching to linux can't help themselves but install the latest meme shit like arch and goofy flashy kde nonsense. If OP really wanted a "just works" linux he could have it, but the temptation to fuck around is just too strong for most. I remember being like this too way back in the day.

>>109467955
Tell that to my tumbleweed laptop that I update every 3 months.

>>109467900
>>109467955
dumbass
nothing changes if you don't update for a longer time
nothing magically corrupts if you don't update for a longer time
the only real thing that can happen is if you modify system configs, don't update until a breaking config change, then don't merge .pacnews (at least on arch)

>>109465517
Fedora's offline updates would literally have prevented this entire issue though. Screenlocker only breaks after an update because you have a mismatch in the running libraries (in memory) and the libraries on disk.

The solution is to reboot after a major update or to not fucking upend your system like that and install the updates offline.

>>109467869
I'm kind of lazy to restart anything but hasn't happened so far.

>>109468668
It happens to me from time to time, but its because I have power management set to suspend the system after 15 minutes combined with

alias emerge='systemd-inhibit --what=sleep --why='\''Preforming System upgrade'\'' emerge '

so if emerge completes while i'm asleep or away, it suspends then I get the black screen on wakeup

windows doesn't let you update a running program because they know their users can't handle it. the more popular linux gets, the more dumb stuff like this will show up

>>109469054
>

alias emerge='systemd-inhibit --what=sleep --why='\''Preforming System upgrade'\'' emerge '

@Grok how do I do this in OpenRC?

Stop using an old stable distro like a retard.

>>109453638
Your time is worthless if you're using Linux

>>109470470
Use elogind-inhibit?

>>109470482
>Stop using an old stable distro like a retard.
/g/urus what did it mean by this?

>>109470671
Debian, ushito, etc.

>>109453535
Its not just not ready, its going backwards.

>>109468228
>nothing changes if you don't update for a longer time
>nothing magically corrupts if you don't update for a longer time
Almost correct. Nothing breaks if you don't update for a long time UNTIL YOU UPDATE.

>>109470870
wroooong

If you had used NixOS you could just easily roll back

>>109453535
I've had this a few times on my thinkpad
Sometimes it happened when it locked for inactivity and I reacted as soon as it happened, sometimes it happened when I closed the lid, really weird
It happened a single time on my desktop, but I switched back to x11 (for unrelated reasons) and it has never happened since
Both of them are stock debian stables

>already gives you the fix, saving you from a google
Is this luxury? I'm used to just getting a blue screen of fuck you

>>109470870
i've updated an arch computer rarely use twice with about 2 years between each one without breaking it. also recently updated my friends' gentoo server with over 170 days since the last update without issue

>>109455774
This issue only happens on Debian and Arch because of APT and Pacman, the issue happens because you upgraded SDDM and APT and Pacman don't know how to handle live updates so you end up with a combination of old and new libraries and configurations which causes this problem, the recommendation from KDE devs is to stop using retarded distros like Debian and Arch or activate offline upgrades using Discover.
I'm not trolling by the way this is the real problem and solution, genuinely trying to help you here.

>>109476089
All false. Stop asking the gay eye.