I know it’s called plasma, and I don’t know if it’s actually plasmas fault, don’t judge me, it’s for the meme
Found the Nvidia user
Some people have KDE problems because they use Nvidia. I have KDE problems because I switched from Nvidia to amd but there’s no way to uninstall Nvidia drivers in arch without a os reinstall and I’m too lazy for that (games still work, but many of my KDE bugs are probably caused by Nvidia drivers still being present). We are not the same.
You literally just have to uninstall the Nvidia packages
pacman -Rs nvidia nvidia-tools
i kinda did the same today, but my machine was headless.
can you give me more info on why is impossible to uninstall Nvidia drivers?
Just switched from 2080 super to 7900xt last week on Endeavour. Install amdgpu, vulkan and mesa, reboot and install, uninstall nvidia stuff.
How do you like this setup? I’m on the same thing, using nixos. It’s great, but Nvidia is clearly a buggy mess when I compare to my steam deck (I know not apples to apples)
I am loving it. Most recent builds have been absolutely smooth. My only complaint, a minor one, is I’m lazy and would like to see Discover added and populated with flatpak and appimage support more easily.
It was good with the 2080. It’s great with the 7900. Everything I throw at it, maxed out 4k, streamed via Sunshine (max detail/quality all) to an nvidia Shield or Steamdeck running moonlight, is so closely synced that audio is pretty much matched.
And since getting rid of nvidia, no more waking up in the mornings to find the thing had crashed and rebooted to maintenance mode during some sort of unattended update or process.
Wat
sudo pacman -Rnsc nvidia-utils lib32-nvidia-utils
Unless you went to the NVIDIA website and ran the .bin, you’re not supposed to do that on any distro unless you want problems.
Although it still shouldn’t use an inactive driver.
When I last had an Nvidia GPU (secondhand PC), I discovered that the drivers came with altered versions of a lot of the 3D rendering libs. Those drivers are a cancer.
I didn’t know that, but when I changed to AMD I didn’t think twice before reinstall everything so I never reached this knowledge.
;-;
I feel your pain, I was there once my friend, just hold on plasma 6 is coming.
just hold on plasma 6 is coming.
It’s only a matter of time until Nvidia will fuck up compatibility again. Waiting for workarounds to Nvidia problems is not the solution.
I really wish Linux hardware companies would stop selling Nvidia, and that Linux users would stop buying Nvidia. They don’t care about us.
EDIT: Yes I know people with Nvidia switch to Linux with existing hardware. That’s not what I’m getting at and I hope those people choose their next GPU wisely.
They don’t care about us.
Nvidia only cares about CUDA and users don’t even need to use the Nvidia hardware to output graphics for that. Pretty sure Nvidia barely tests non-headless use of their hardware on Linux.
You’re probably right, but it definitely seems like the majority of Linux users are still buying Nvidia.
No sympathy then.
Or AMD, apparently. The bug report for this issue was explicitly renamed to say “Non Intel GPUs” - even though it seemed to be more likely(?) to happen to Nvidia users.
What’s the matter?
I’ve had laptop with Nvidia GPU, and the only thing was that for some reason the driver only worked with Linux 5.4. Other than that, it was fine.You were using nvidia with KDE on wayland? Maybe it was Nouveau driver but Nvidia official driver freezes KDE on wayland all the time, X11 is ok tho.
Nope. That laptop is dead, sadly, so I can’t try anymore. X11 with cinnamon (I briefly tried Plasma too). Nouveau at least worked with all kernels I tried, but it wouldn’t resume from sleep.
I just have “plasmashell --replace” mapped to meta + del.
I totally just stole that one
No need to steal, I’m giving it away for free :)
deleted by creator
Do you know the whats the difference by any chance? Would be interested
They are both doing the exact same thing. In your case it’s just stopping and starting the service with separate commands instead of restarting with a single command.
I’ve had to have such a shortcut for… 4+ years now.
It gets used too often
You know what’s funny… I use Windows still for gaming and I have KDE connect installed to control stuff from my phone, and I have a “Refresh KDE connect” shortcut because the connection sometimes bugs out.
If you disable previews on hover, it seems to make the issue go away. At least it did for me. The bug report I’ve submitted months ago is still unsolved, but it’s better than having to restart the compositor every time
Maybe your bug report didn’t get collected into the other bug report, but it’ll be resolved for Plasma 6 thankfully!
i mostly use kde apps like krita and kdenlive, although when i did use plasma i didn’t have these issues. i use sway now because i wanted fully functional tiling (both polonium and bismuth were weird/buggy)
There’s a new one I think. Sorry but I can’t find it right now, but I believe it’s in the get new KWin scripts menu.
by the way i think you mean the kde store
Thanks, didn’t know they have a web version!
I eventually want to return to GNU/Linux, but I just don’t see a DE that has no drawbacks. The most reasonable choice I think is to just return to MATE, even though it looks dated and doesn’t feel to innovate.
I really want to try KDE out but it looks like a cluster fuck for me.
Plasma is fine. This buggy reputation is from a decade ago.
removed by mod
I can just recommend trying it out. If you’re not stupid like me and use the wayland session with nvidia drivers it is anything but a clusterfuck
Linux mint cinnamon?
Tested last week. Games with proton crash every 20 minutes… O am so sad to be forced to go back to windaub
Try gnome, it’s really good!
Use a WM, now you’ll only have yourself to blame. But GNOME should work well
ah a fellow Waterfox user, flatpak or appimage?
AUR waterfox-bin, btw (¬‿¬") I’m almost glad to have made the mistake to install Arch because through AUR I don’t have to get involved in these flatpack/snap/appimage wars xD (also because I have no clue what I am doing, but don’t tell anyone)
ahah lol that’s fair, i maintain the flatpak so whenever i see someone with Waterfox on Linux I get curious. Love the AUR but I’m mostly on immutable distros so I don’t get to use it qwq
I actually used the flatpak on my mint install a while ago, had no problems. So great work for a great browser I’d say xD thanks o7
lol thanks, it’s more of a side project atm as I’m juggling school and running IT for my dad’s business but I’m glad to hear it worked for you!
Distrobox says hi! I used the AUR occasionally when I was on Silverblue and there weren’t any alternatives short of compiling the software myself. Or rarely if I needed a newer version of something.
This is unrelated but what’s the appeal toward immutable distros to you?
I don’t mean this in a hostile way I’m genuinely curious to know. I usually consider the ability to change anything about Linux as quite a big selling point so these distros seem kinda counterproductive to me.
I usually consider the ability to change anything about Linux as quite a big selling point so these distros seem kinda counterproductive to me.
Immutable distros are actually easier to customize and tinker with than traditional distros, while being safer. Example: Universal Blue
Interesting
Basically what IverCoder said, but also sometimes I like not having to tinker with my desktop at all. I’m running through an Arch Install on my Thinkpad right now just for the fun of it and I do love this kind of thing, but I’ll admit the concept of plugging in a USB stick, installing a distro in one click, downloading my apps through Flatpak and not having to mess with the CLI a whole bunch is very appealing. Yes you can do that with Ubuntu or whatever but (at least in my workflow) you still have to mess with the CLI a bit.
Basically, I like messing with Linux sometimes but other times I just want a, I suppose Windows-like experience while still having Linux under the hood.
Just curious, what makes Waterfox different from Firefox?
Waterfox is an independent fork of Firefox developed by Alex Kontos. It has several added features such as tracking protection, built in container tab support (eg private browsing in the same window, very neat feature), and Mozilla’s telemetry is disabled too. It’s a lovely little browser in general, I don’t know why I love it so much tho, you could achieve the Waterfox experience with Firefox and some addons probably. Perhaps it’s just the appeal of a (more or less) independent project to me, I don’t know. It has some history too like I think it supported x64 on Windows before Firefox did but I’m not a long time user so that might be wrong. I’d give the website a once-over if you’re interested.
Ahh nice, thanks for that. I like giving smaller and independent projects some love so I’ll give it a solid go 👌
Similar to an official cinnamon feature that automatically reloads cinnamon if it’s memory usage becomes too high
I see someone else is also using waterfox
yeah, that browser that was bought by an ad company :)
It’s apparently independent again - announced in July 2023. here’s the announcement
Still don’t understand the purpose of wayland besides cleaner code and easier updates for kernel level stuff.
X11 has been fairly updated with all the features people wanted and needed anyway. Just because no one uses all of its niche and antiquated plugins and extra stuff, doesn’t mean its inherently an outdated program.
I’m pretty sure that recent X.Org server development has been driven by XWayland for the most part, the tags on repo certainly look that way
I’ve literally never need to do that.
Which version of kde is that, I can’t tell. 🙄
Looks like Windows to me /s
Never been an issue on Gnome
You mean the gnome that had a memory leak for the first 8-10 years because every frame non-deterministically allocated memory that may not be freed before the heat death of the universe which they solved by by running the GC every frame because they couldn’t fix their bad design?
The one where the only way many people’s computer wouldn’t fall over is if they restarted their computer or gnome…
Then they switched to Wayland and it was impossible restart the compositor without losing your apps.
The one where common features in other environments are only available via JavaScript extensions that break every release where if even one of those teeny tiny JavaScript extensions crashes your entire gnome session crashes taking out all unsaved data and all your apps?
That gnome?
Someone’s very upset over gnome it looks like. Never had a memory leak on my machine, been using it for years. Gnome is fully complete, the only “common features” it’s missing are things you subjectively prefer. Like restarting a Wayland compositer is what really bugs you? What an incredible obscure problem that you’re crying about. The actually polished DE that isn’t a buggy bloated mess, that Gnome.
Gnome3 had a pretty big issue from inception in 2011 and continuing for 8 years without recognition. It’s not my fault you are young and just installed it last year. Some of us have been here a while. Some users continued to have issues all the way though 2021 and the fix is just as stupid as described.
Now the problem is not restarting it. It’s that you can’t restart it in place without losing your apps. This means if your shell crashes you lose everything. This would be less of an issue if the entire desktop weren’t written in javascript, if it actually had an addon api, or if it didn’t load all extensions into the same javascript context as the shell.
Compare and contrast to other systems which can survive graphic drivers crashing without dropping a session or X11 which can survive a component crash.
It suffers from the EXACT problem that the old firefox addon ecosystem suffered from only gnome learned nothing from mozilla and its pervasively used. 83% of users use extensions despite the fact that they are so unstable all extension devs have to opt into every minor release with every extension because there is is no way to verify that the any given addon works with the new version.
https://yoric.github.io/post/why-did-mozilla-remove-xul-addons/