That meme used to be true 4 years ago but I just used it for a whole evening with no bugs
Only weird thing is there's no way to turn the screen off faster once you lock the screen, other than that it's almost perfect
I can tell you a 15 minute bug that has been present since the first release of 5.27.
Import several images into the wallpaper changer dialog and they will be imported with some missing, others displaying the wrong thumbnail and others displaying a black thumbnail.
This worked alright for years.
This is bait isn't it?
Plasma 5.27 is literally the current version of plasma you stupid mongoloid, the issue has been present since the first release.
Hey, pretty sure this will be added as an option soon as i recall searching for the bug, yet as i didn't want to wait for them to fix it i did it myself easily:
Go to notifications -> Scroll down to almost the bottom and search for screen saver (Trust me, the event you want is in there) at the bottom click on Configure events.
You should see the screen lock and unlock events, put a run command on both of them pointing to different sh files.
Lock.sh
#!/bin/bash
sleep 1
if [ "`qdbus org.freedesktop.ScreenSaver /org/freedesktop/ScreenSaver GetActive`" = "true" ]; then
kwriteconfig5 --file $HOME/.config/powermanagementprofilesrc --group AC --group DPMSControl --key idleTime --type int 25
qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement org.kde.Solid.PowerManagement.refreshStatus
fi
LockReset.sh (for unlock event):
#!/bin/bash
sleep 1
if [ "`qdbus org.freedesktop.ScreenSaver /org/freedesktop/ScreenSaver GetActive`" = "false" ]; then
kwriteconfig5 --file $HOME/.config/powermanagementprofilesrc --group AC --group DPMSControl --key idleTime --type int 600
qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement org.kde.Solid.PowerManagement.refreshStatus
fi
Change the int 600 for whatever you usually use to turn off monitor when inactive (in seconds)
Been using it myself for ~ 2 months without troubles, yet they'll add a preference for that soon so you can configure different times when the screen is locked, the issue says it's fixed but i'm not sure when it'll land.
https://bugs.kde.org/show_bug.cgi?id=348529
I've made myself a simple shortcut to turn off the screen to save on electricity, but it doesn't work now for some reason.
It turns the screen off and then turns it back on, if you want to have a look then picrel
also, it's late and i'm going to sleep so you probably wont hear from me again :c
3 weeks ago
Anonymous
>but it doesn't work now for some reason. >It turns the screen off and then turns it back on
You might have something running that's preventing it, for example Steam does this. If you add a timer with sleep like 30 secs it might work better.
2 weeks ago
Anonymous
Maybe it's the keypress itself waking up the monitors. Try:
sleep 1 && xset dpms force off
Hey, probably it's just what this anon here suggested [...]
But i'd recommend toggling the idleTime so it doesn't turn on and stay that way in case something accidentally disturbed your mouse
Thank you all for responses! I've made screenshots and I will make changes at the weekend. I also want to learn dbus integration and make some plugins for kde. I may publish them for others. For now have a good day and please take care of yourselves anons! <3
3 weeks ago
Anonymous
Maybe it's the keypress itself waking up the monitors. Try:
sleep 1 && xset dpms force off
3 weeks ago
Anonymous
Hey, probably it's just what this anon here suggested
Maybe it's the keypress itself waking up the monitors. Try:
sleep 1 && xset dpms force off
But i'd recommend toggling the idleTime so it doesn't turn on and stay that way in case something accidentally disturbed your mouse
no, see the problem is kde users can't like their own DE without shitting on GNOME. they just can't shut the fuck up about it and just enjoy their lives, but have to shit on GNOME constantly. so GNOME users respond in kind.
i don't think most GNOME users give a fuck about KDE. many of them might not have a real opinion on KDE cause of no experience of using it.
i have experience of daily driving KDE, and yes it's shit. it looks nice but it's so buggy and glitchy i just can't stomach it.
>the problem is kde users can't like their own DE without shitting on GNOME >i don't think most GNOME users give a fuck about KDE >i have experience of daily driving KDE, and yes it's shit.
goddamn what's it like being a walking contradiction?
that was in response to the constant shitting on GNOME by KDE users that i've witnessed on this board for years now.
it's like you're so fucking brain dead you can't like something without also hating everything else at the same time. just shut up about GNOME if you're not a GNOME user and instead talk about what makes your DE of choice great.
OP said nothing about gnome, you are the retard who brought it up.
3 weeks ago
Anonymous
he doesn't need to bring it up. it's brought up daily in multiple threads on LULZ regardless. eat shit
3 weeks ago
Anonymous
the only one eating shit here is you. every pro KDE Plasma thread that exists >muh krashes
I haven't had Plasma crash on me in 8 years anon. What drugs are you on? I normally filter out gnome threads because most gnome users are shit flinging low iq naggers.
3 weeks ago
Anonymous
i'm surprised you managed to type that whole post without plasma krashing
srsly though. why do you think that meme exists if there was nothing to substantiate it?
3 weeks ago
Anonymous
because gnome users are shit flinging low iq naggers who can't wrap their smooth brains around desktop icons. there's nothing to substantiate because every single "crash" that has been brought up is due to a few factors
1) they ran it in a VM instead of metal and they used VMWare or Virtual Box. It ran fine in Boxes.
2) They probably ran it on nvidia or were missing nvidia drivers or the nvidia drivers were shit and to blame.
3) The issues they did post were overblown way out of proportion as if it were some gotcha, when the issue they posted were beta versions of plasma.
You came into a pro KDE thread to spout off gnome nonsense and start flamewars WHEN NOBODY THE FUCK ASKED YOUR LYING nagger ASS!
3 weeks ago
Anonymous
son, i've used linux daily since 2005. do you really think i don't know how to install graphics drivers or set my system up properly?
it's a fact that each time i've tried to use kde since v4 (v3 was fine iirc), it has been a krashy mess. and i really tried to enjoy it. stuck with it for months each time.
i've tried many DEs over the years and none have been as krashy as KDE is. or plasma or whatever the hell you want to call it. maybe you're a zoomer. most people know it by 'KDE', not plasma.
3 weeks ago
Anonymous
I used Plasma 5 exclusively for years and it sucked balls. AMD GPU and obviously running on bare metal and krashes were real. Shit was so annoying it made me move to Gnome. Now I have the newest Plasma on Steam Deck and stability seems to have improved. It’s still an ugly shitshow of random options and buttons but at least it kinda works.
3 weeks ago
Anonymous
I doubt you actually used it. You probably applied some broken theme made for an earlier version of plasma that broke it and you act like a total fucking homosexual about it.
While we are on the topic of themes, look for a theme that suits you better thats made for your specific version of plasma.
It would help if y'all all didn't lie so much.
3 weeks ago
Anonymous
Fuck off nagger.
3 weeks ago
Anonymous
weird, in the last year i got 3 crashes, and one of those three was trying to replicate it. on X, i didn't let wayland time enough to crash as last time i tried there was some weirdness that made my jump back to X on the first minute, i'll try wayland again on kde 6.
3 weeks ago
Anonymous
wayland is buggy on nvidia hardware
this is not the fault of plasma
3 weeks ago
Anonymous
I was using amd, and now i'm usually 90% of the time on the intel igpu.
3 weeks ago
Anonymous
Wayland was a mistake. I really liked Mir and wish Canonical would have continued development of Mir. Because its popular to hate everything Canonical it died.
3 weeks ago
Anonymous
Can't really argument about it as i haven't really have a deep understanding of mir, wayland otoh made some decisions that doesn't seem to align correctly with the needs of a full fledged desktop computer.
But I hate snaps.
3 weeks ago
Anonymous
Snaps are getting better now that they made them totally open source again. They did it in response to the whole IBM/RedHat fiasco. Give Snaps a few years and you won't care.
3 weeks ago
Anonymous
snap being FOSS doesn't make it not shit, it's fundamentally stupidly designed
3 weeks ago
Anonymous
as are appimages and flatpaks tbh but we dont have a good way of distributing software on Linux. Windows does it right IMHO. I just wish Microsoft weren't evil as fuck.
3 weeks ago
Anonymous
>Windows does it right IMHO.
spoken like a non-admin, i'll gladly take freetard bloat over VC++ redists and the absolute hell of windows server mass deployment. there's a reason even azure customers mostly use linux VMs.
3 weeks ago
Anonymous
I remember the firefox snap sent me back to the mechanical hdd era of start times, then realized that with 4-5 snaps the whole computer started several seconds slower and a quick systemd-analyze told me it was cause snaps too, i ran away and i'm not sitting on arch + kde and it's being quite comfy.
3 weeks ago
Anonymous
>wayland otoh made some decisions that doesn't seem to align correctly with the needs of a full fledged desktop computer
you fucking retard. the reason wayland was even conceived was because X.org doesn't align correctly with the graphical desktop needs of today.
stop reposting half-baked memes you found online and start reading facts instead.
nobody likes wayland, gnagger. We didn't support Mir either. Eat a bag of cocks and go back to sniffing glue and robbing inner city walmarts.
wayland has worked perfectly in GNOME for years. that was the point of my post you fucking idiot. if KDE had fixed their shit, you would have a different opinion on wayland.
3 weeks ago
Anonymous
>you fucking retard. the reason wayland was even conceived was because X.org doesn't align correctly with the graphical desktop needs of today.
I looked at some of the tickets that were stopping me to make some stuff, and that they didn't want to implement as they can be abused, and at least now there's a draft for a portal so it seems that at some point in the future it'll work.
Lot of the security bullshit was in the way to be of use on a full fledged desktop, i don't care what you say. The easy fix would have been a proper permission system to ask the user, (one of the few things macOS does right, BEWARE: the rest of mac is a pita as it lacks basic functionality)
It seems they're more open to discuss this issues and implement the most than needed features now, ie: proper global shortcuts weren't possible till 1-2 years ago on wayland.
But there's still a lot of work remaining, ie:
https://github.com/flatpak/xdg-desktop-portal/issues/1046
So, yeah wayland is soooo great, lets just use wayland, everything works....
but somehow, there's still lot of things that are needed for things to work, so i'll wait till those things are in place instead of deluding myself.
3 weeks ago
Anonymous
if the bug tickets were on the side of KDE why the fuck do you think it's a wayland problem? seems it's aan issue with their implementation and not the protocol itself. wayland is just a protocol. it's the KDE team that's in charge of immplementing it, same as every other DE or WM.
did you even know that basic fact about wayland? of course not, you don't know anything about anything just like all the other fags who whine about wayland.
it's because of this basic misunderstanding about who's in charge of the code that makes retards on this board think wayland is broken.
3 weeks ago
Anonymous
Are you retarded?
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/56
3 weeks ago
Anonymous
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues
There's lot of missing pieces in wayland protocols, you delude yourself and then demean others to avoid further debate.
3 weeks ago
Anonymous
And the same happens on xdg.
2 weeks ago
Anonymous
Wouldn't it make more sense to create wayland compositor for blind people? This way the UX could be much more optimized for people who do not see.
3 weeks ago
Anonymous
it's literally the fault of plasma.
why do you think this page exists?
https://community.kde.org/Plasma/Wayland_Showstoppers
it's a fact that the KDE dev team has been *extremely* lazy about implementing wayland, and fixing bugs. it's my impression that while GNOME was working hard on their wayland implementation, the KDE team just laid back and silently wished wayland would disappear.
now they realize wayland is here to stay so at the *last* fucking minute they decide to try fixing their wayland implementation.
KDE is the reason why people think wayland is not ready. they are the reason why smoothbrained mongoloids on this board have been whining about wayland for years. none of this would've happened if those lazy KDE dev FUCKS would've just worked on their wayland shit like GNOME did.
3 weeks ago
Anonymous
>the KDE team just laid back and silently wished wayland would disappear.
can't really blame them
3 weeks ago
Anonymous
nobody likes wayland, gnagger. We didn't support Mir either. Eat a bag of cocks and go back to sniffing glue and robbing inner city walmarts.
3 weeks ago
Anonymous
I think gnome users are perpetually retarded.
picrel is a Windows 11 theme I am working on for Plasma 6 running on Plasma 6 beta. I dont recommend running Plasma 6 until it's done but even in beta it is really stable.
3 weeks ago
Anonymous
tbh the only times i managed for it to crash was on edit mode, while using the search bar to filter widgets, and that was fixed quite fast.
3 weeks ago
Anonymous
Nice legs.
2 weeks ago
Anonymous
Plasma 6 shows a banner in the bottom right...
That's Windows 11.
3 weeks ago
Anonymous
Can you just fucking shut up
3 weeks ago
Anonymous
Can you gnaggers stop lying in every thread about KDE Plasma?
>it looks nice but it's so buggy and glitchy i just can't stomach it.
lies, tell me princess have you tried using Plasma (its not called KDE, that would be like calling Windows, Xbox)
go be a retard somewhere else please.
i think MATE is cool cause GNOME 2 is the era when i first got into Linux. but it's gonna have a hard time keeping up with the ever-changing GTK toolkit. i feel like DEs like MATE and Xfce are going to be perpetually behind. and they don't have a lot of manpower so it's difficult for them to implement wayland support.
i constantly use it for sharing files and clipboard contents between devices. especially useful if you have a password manager. it's also great to use your phone as a remote during presentations, ring your phone if you lost it somewhere around the house, etc. depends on you and your usecase, but i get daily use out of it.
I put kconnect on my gnome
never tried that (i dislike gnome but you do you) - does it integrate well? like adding "share to [device name]" entries to the right-click context menu inside the file browser?
kde has been a buggy glitchy mess ever since v4. try using it for longer than an evening and you'll notice. plasma 6 will default to wayland, and i have no idea how they'll pull that off considering kde's wayland session has always been a complete clusterfuck.
it's like they're not even trying.
ironically, most apps for qt / kde are better than kde itself.
it was on fedora. i've been running fedora exclusively for years. i try kde every now and again and stick with it for a few months each time, but it's always glitchy. it's not immediately apparent but it's minor shit that adds up in the end.
last time i tried kde was around a year ago i think.
Every DE is gonna have an assortment of minor issues so fuck it. I'm sticking with KDE because the file manager feels awesome and responsive with huge media directories and has thumbnails on folder icons.
>kde has been a buggy glitchy mess ever since v4. try using it for longer than an evening and you'll notice
using it for 5 years and i didn't notice that, what does "glitchy" even mean in the context of a DE?
well, parts of the screen would get stuck. parts of application windows would stop updating, and / or flicker from black to normal. that would happen only after i've had a session going for a while, more than 1 day. the solution was to log out and in again.
see [...]
I bet you're trying to use it with an Nvidia or something.
on my old build it was intel graphics. their drivers are open source and high quality so you can't blame that. now i have amd graphics but haven't tried kde on this build yet.
I reinstalled Kubuntu 22.04 LTS with KDE 5.25 and now I cant get GPU sensor values in widgets. nvidia-smi has no problem reporting. Halp! What's the backend that's missing?
https://invent.kde.org/olib/thermalmonitor
I have this installed and it tells you what it requires. Whatever you use there might be a similar page for you to check from.
Probably fixed in later KDE Plasma, the Nvidia GPU reporting stuff has been fixed a few times in recent versions.
https://invent.kde.org/olib/thermalmonitor
I have this installed and it tells you what it requires. Whatever you use there might be a similar page for you to check from.
This uses the same backend as System Monitor and its widgets.
>BAAHHHHHHHHH NOT THE KOOL DE OHNONONO NOT THE KDE!!!
Kek. I bet you're a r/gnome regular. You people can't seem to shut the fuck up about how bad and buggy KDE is when GNOME cannot even fix their fucking calendar on the top bar.
The absolute state of GNOMEfags. Cannot fix their own shit so better start spreading FUD and lies about other projects that are simply better.
Only problem I still have with KDE is that on multiple monitors, it never seems to go into sleep right. It never times out, and never takes the settings into account.
The seeth itt by GNOME cucks is what happens when we don't have an ebassie thread in the catalog.
Some people were saying that ebassie threads got stale.
They don't understand that we create them to keep the GNOME devs contained (who spend their time shilling on LULZ rather than developing their DE).
Every post a GNOME cuck makes in a dedicated ebassie thread, is a post that he doesn't make anywhere else.
Those threads protect us from their bad takes, ebassie posters are massively improving the quality of LULZ.
No matter how much time I invest on KDE, it always looks and somewhat behaves like dogshit
Yeah, it's very convenient and has features other DEs don't. But half the time I'm having to wait for shit to just open, for it to let me save a fucking file because the file picker is just so good that it has to take a year to load shit. I have to use these things, Kvantum, QtCurve, it's all a goddamn mess. Window decorations make everything so sluggish opening a new dolphin window makes my cursor stutter, what is this nonsense. Shitty defaults or bust I guess.
openSUSE
Have a folder with thousands of files, try to save something there from the filepicker.
Try installing some random window decoration, maximizing and minimizing windows, opening them up.
I'm using sweet, with kvantum, i tried saving an image with the file picker in a folder with 1.247 files and it opened in 1/5 of a second, probably faster, it's hard to measure as it's quite fast, i don't have bigger folders in this pc as i have to access the same folder with a mac from time to time and mac explorer (finder) tends to crash if there's too many files in the same folder (macOS is a joke)
>1/5 of a second
I wish
I have to save files on the same folder and everytime I have to wait for 4-5 seconds. I can press the save button, that window is not going to disappear until then.
Is a 3600 + 6600xt with 32gb of RAM not enough for KDE plasma now?
At this point just throw away your PC and buy a Mac, obviously you are unable to operate it. A Chromebook would be another option.
3 weeks ago
Anonymous
What is this cultist like reaction? Christ. I'll use XFCE I guess.
3 weeks ago
Anonymous
There is no cultist reaction.
First you say that you save everything in one folder like a phone tard. Then you say that loading it is slow and people say that they are just fine to watch folders with 40k files. Then you say that saving takes apparently 5s? Something that absolutely nobody can recreate and that was never an issue in more than a decade?
Obviously the issue is on you. Either you are lying or computers simply aren't for you.
Buy a Chromebook, they perfected the "don't use the filesystem" workflow from Android.
3 weeks ago
Anonymous
Do I really need to make a .webm of this shit? You karpies are something. Just footfags with a different hood, I swear to god. Your beloved filepicker doesn't even have a search function past the folder you're in, so don't be bitching now about putting everything on one folder.
3 weeks ago
Anonymous
If you would be interested in telling us about your problem or finding a solution, you would tell us what you saved from what applications and not do a generalized: "Saving takes 5 seconds".
Because guess what filepicker your firefox browser or chromium are using?
If you are using the gtk default, you will have the exact same experience on XFCE. Because it's the same thing. If you use the xdg-desktop-portal, you probably should point that out because RedHat would want to fix that very fast. They need it to shill for flatpak.
3 weeks ago
Anonymous
An example is it takes me nearly 5 seconds to save an attached document on an email from thunderbird, using the KDE file picker.
openSUSE has firefox patched builds to use the KDE filepicker, but if that wasn't the case I already know how to use that specifically. Yes it is the filepicker that doesn't need to previously generate a thumbnail cache to show thumbnails and it is the filepicker that has a little button on top that shows and hides these previews. I don't know what else to say here.
3 weeks ago
Anonymous
Thunderbird is the same thing as firefox and must use the desktop portal to see the kde filepicker. A feature we got from flatpaks that has corporate funding.
If you report it, an army of RedHat devs will gladly help you.
But why do you even use the desktop portal? >openSUSE has firefox patched builds to use the KDE filepicker
No such thing exists. You either use GTK dialog or xdg-portal.
3 weeks ago
Anonymous
>I don't know what else to say here.
Then I will say it for you anon... Gnome is fucking garbage. KDE is fucking based.
3 weeks ago
Anonymous
>An example is it takes me nearly 5 seconds to save an attached document on an email from thunderbird, using the KDE file picker. >OpenSUSE
many such cases
I have a shortcut on my desktop to quickly change theme and color scheme by running things like plasma-apply-colorscheme.
I siwtch multiple times per day. Never did i experience any issue. And my meme folder had 40k images and worked just fine, till i got annoyed at having to type for search and sorted them into subfolders.
I've daily driven KDE for years and have only experienced like 2 or 3 crashes in the past couple of years. Anecdotal but you'll never convince me that current KDE is constantly crashing. Also Gnome deserves to be shit on.
I'm using it right now because is the only DE that push to talk works on Wayland, it's way snappier than gnome, but it's ugly as fuck they need to hire a designer, also most apps are made using GTK so they don't look as good on plasma
I like video thumbnails it even show different frames on mouse hover, but yes, baloo sucks ass, i tried very hard to have it working and most of my problems with search got resolved once disabled it.
It's pretty good so far, Plasma has come a long way since 2008. I do wish it could support shadows under CSD windows like GNOME Shell does though, helps integrate things better.
>The GNOME foundation started paying jannies to censor anything negative to GNOME
Kek that just confirms that GNOME devs post here all the time. A few threads were all it took break their minds.
nice conspiracy theory. it's the other way around dipshit. if you say anything positive about GNOME on LULZ you will get ddosed by some random pissy jannie who thinks the healthy competition between DEs is some sort of spiritual war between good and evil.
i wish those retards would go leave and stop involving politics with software.
>NOOOO IT'S THE OTHER WAY AROUND >GO leave BUHUHUHU
Holy shit you're seething, lmao. It's a well known fact that GNOME devs talk about politics everyday. Literal troons and naggers make out the GNOME foundation who want "diversity" and "ethical" software.
https://weirder.earth/@sophie
https://gitlab.gnome.org/BrainBlasted
There's also the pajeet dev who goes by blackcain on Reddit. You're probably a trannie too. That's why you're so fucking mad right now, kek. About to pop a vein probably lol.
you're a fucking moron trying to fight fire with fire.
yes, the way to battle blue-haired feminists and troons is to say 'fuck the israelites', and 'heil hitler you fucking cuck', read the bible and vote for trump.
you think you're any better than the GNOME devs? what's the fucking difference?
you're like a retarded teenager lashing out at their christian parents by reading the satanic bible and wearing goth clothes. you're not fighting anything but shadows in your mind.
you're just a reactionary little cockroach who can't judge things based on their technical merits, but have to involve unrelated shit like politics.
>hurrr durrrr trumpp
lmao fuck off moron I don't give a shit about your murican politics and I ain't reading all your troon schizo babble
what a fucking seething loser hahaha
3 weeks ago
Anonymous
well, you probably can't read full sentences anyway. you strike me as someone with the IQ of an amoeba
KDE pushed Wayland into adopting fractional scaling. Something that wayland and GNOME developers considered as "not needed".
Similar to how Valve pushed wayland into adopting the tearing protocol, allowing vsync to be turned off.
The wayland purists, who think that you should never use a higher resolution than 1080p, must be pretty mad about that.
But those people only exist as corporate paid developers who try to castrate things to make their work easier... which tells you a lot about those posters here.
that's because it's literally true. do you even know what wayland is you stupid shit? it's a protocol.
gnome has already implemented it, successfully. kde devs have been dragging their feet, doing a shitty job. that's why mongoloids like you think wayland is shit.
because you use kde and they didn't do a good job.
The problems people have with wayland aren't related to the KDE showstoppers, you coping troon. Your shitty protocol literally does not have feature parity with what it's supposed to be replacing.
what features? network transparency? have you ever actually used it or are you just whining about it for no reason like everyone else? sending 4K pixmaps over network for every frame. yeah good luck homosexual.
or what about the ability of X.org to let any fucking process in the system listen in on keystrokes and know what's displayed on the screen? yeah, great feature.
the fact that kde has done such a lazy shitty job of implementing wayland is the reason why it's garnered so much hate. smoothbrains like you just fire up a kde wayland session and see it's completely b0rked, hence wayland is bad.
when actually, it's just a piss poor implementation.
>kde has done such a lazy shitty job of implementing waylandd
Wayland gathered hate because GNOME started to recommend it as default while it was still completely unusable. They changed at a time when pipewire was still not widly distributed, meaning that they cucked their users out of screenrecordings, screenshare or even screenshots.
They also didn't (afaik they still don't) let you choose if you want xwayland applications to get scaled by the system or to trust them to scale themselves. Meaning that if you had a scale of 150%, they would render at 1:1, then scale up to 200% and then get scaled down to 150%. DPI settings wouldn't help you out here either. They look ridiculously washed out.
GNOME also STILL doesn't support native fractional scaling on wayland and. GNOME also shipped wayland with the fucking cursor lag under load.
Canonical noticed it and they ship GNOME still with xorg per default. Fedora followed the official recommendation and defaults to an unusable GNOME wayland for years now. Which is also the reason why they were the first to make the pipewire switch.
KDE doesn't have most of those problems in their current version and they will have none of those problems in Plasma 6 (fractional scaling is supported by every Qt6 application, they just have to port KDE Gear to it).
And guess what:
KDE NEVER recommended you to use wayland because they knew that people use monitors that are larger than 1080p and they knew that a laggy cursor under load is completely unacceptable.
The official recommendation to use wayland on KDE will be with Plasma 6. Not earlier. Even thought that it is in a much better state that GNOME wayland, they STILL don't tell you to use it.
GNOME 45 has been patched to run keyboard / mouse input in its own thread so there will not be lag anymore. That had nothing to do with Wayland but was a limitation of GNOME itself.
I haven't heard about KDE having input lag problems. So it's literally not a problem with Wayland, it's just a problem with your brain.
Let's hope Plasma 6 fucking fixes the Wayland session, since it will be the default.
3 weeks ago
Anonymous
>since it will be the default
Pretty sure this is decided by distributions and not Plasma 6.
3 weeks ago
Anonymous
>in the future there will be no cursor lag
There will be less. It won't be gone, only less. You can't fix the cause, because the cause is in atomic modesetting and would require massive DRI kernel patches, involving all GPU drivers. And yes, this is a wayland problem that is in every single wayland compositor.
By doing their own thread stuff to prioritize the cursor as an improvement, they copied what KDE did.
And on KDE i could additionally always disable atomic modesetting and have a smooth cursor that way. Then i wouldn't have a strict standard wayland session, but it's at least usable.
And this is 2.5 years after wayland became the official recommendation and default for GNOME.
If you follow the recommendation of GNOME developers, you end up with an unusable system with blurred windows, cursor lag and broken screen recording.
If you follow the recommendation of KDE developers, you will never experience a single one of the listed bugs, because they are all already fixed and we just wait for the Qt6 ports to get Plasma 6, which will recommend wayland as default.
3 weeks ago
Anonymous
alright. i still don't understand why it's surprising that the cursor lags when the computer is under full load. if you're using 100% of your CPU at any given moment, you're not going to be able to do anything. the desktop is not going to be responsive cause there's literally no CPU cycles left to deal with your input.
3 weeks ago
Anonymous
Maybe you should think about the concept of prioritization and what the nice command does and ask yourself why this was never an issue with xorg. Or with windows. Or with mac.
Maybe you once played a game that doesn't have vsync on and is calculating as many frames as the system will allow and would run with 200 FPS, despite the monitor having only 60 Hz and those frames being useless?
Or maybe you did some rendering once, which uses whatever resources are available.
The mindest: "It has to be that way"
...is the reason why people using GNOME in the default configuration the past two years experienced a crappy shitty and unusable system, if they used any hardware younger than 10 years or any game or rendering.
Maybe read this if you want to know more about what's going on with the cursor:
https://zamundaaa.github.io/wayland/2023/08/29/getting-rid-of-cursor-stutter.html
3 weeks ago
Anonymous
it is a problem in all those systems though. if you're under full load, that's it. there's no getting around it. just like there's no getting around if your RAM has reached 100% use. if that happens the system will lock until resources are freed up.
but that's specifically under full load. if it's just normal load, then yeah, the cursor should not lag. i will try GNOME 45 as soon as it becomes available in the fedora repos and stress test the wayland session to see how the cursor responds.
that might be a while though, as i don't know if that package will become available for fedora 38. they might just wait for fedora 39, which is just around the corner.
3 weeks ago
Anonymous
Preemptive multitasking is a thing since 1984.
GNOME and wayland devs might not know that, but we got the solution 39 years ago.
3 weeks ago
Anonymous
pre-emptive multitasking is not going to do anything if your CPU is under 100% use and your RAM is 100% full.
>or what about the ability of X.org to let any fucking process in the system listen in on keystrokes and know what's displayed on the screen? yeah, great feature.
Name a single OS where this isn't the case.
Hard mode: No phone shit.
idk if you know that, but the Unix permissions are based on users and groups and if you run an application as a user, it has the permissions of that user.
This is by design.
If you want to get out of that, you just create a different user. i.e. every webserver runs as its own user.
Putting a gorillion layers on top of that won't help you much and just has the danger of false security.
An application that doesn't keylog you could steal your credentials by watching browser cookies just fine.
gnome hasn't even implemented server side decorations whi h breaks many applications including vscode which either crashes or has no way to move or resize it. It also doesn't implement suspension pause which means watching videos doesn't work properly as it can go to sleep if you don't move the cursor. This is why mpv devs hate gnome.
nice conspiracy theory. i think most wayland devs and users are happy about those patches.
the motto of wayland is "every frame is perfect", and they refused to add an option in the protocol to disable it since they were arguing that disabling it has no benefits. They only changed that because valve paid a wayland dev to change that.
Doesn't this have temeletry that can't be turned off?
https://community.kde.org/Telemetry_Use
Most sections have the "Opt-In" keyword, but the very top section under "Plasma" does not. Is this suspicious, or can some anon point out why this is not the case?
>Source?
running lsof -Pni seeing kioslave5 or something and checking the ip addresses
It is not a constant connection, only every so often. Might be completely benign but I don't know why it does it.
kioslave are network shares and stuff like that, it's also what makes the google drive connections if you have them setup.
If it tries to connect without you ever using that, it's weird and suspicious.
btw. you can remove the "kio-gdrive" package to remove that capability completely.
They have it written in their privacy politcy that telemetry will always be Opt-In and disabled by default >Some software produced by the KDE Community may include telemetry components, which provides details on the device it's running on to us. Where this functionality exists, it will always operate on an opt-in basis and be disabled by default, with the ability to change your preferences at any time.
https://kde.org/privacypolicy-apps/
linux desktop only works if you have standard-dpi monitors and open source drivers.
the moment you either have high-dpi or nvidia drivers its game over.
Most people itt are retarded gorilla naggers. Literately nobody cares if you use Kde, Gnome, Xfce or some other thing. Most DE's are solid and it really depends on personal preference so you cannot say that one thing is better than the other.
are you joking? someone that use something shitty have to be mocked for you? that change nothing to other life if you use ubuntu+gnome (shitty) or you use arch with some other popular ultra giga nigga nerd edition, it change NOTHING someone hase the liberty to use something bad/shitty or other without being mocked and bullyed for that
Used to use Openbox religiously to avoid ((GNOME)). KDE sucked back in the day so I avoided it. Tried KDE Plasma on my Steamdeck and now I use it on my new builds. It's pretty great and comfy and customizable. First DE I've used that doesn't make me miss any features from Openbox.
>anons suck kde's Kock on the daily >decide to try it >claustrophobic mess of settings >multiple fonts are being rendered incorrectly on 4k monitor >dislike that it's bloated with stuff like KDEwallet >feels like I'm being watched (not sure if schizo) >sudo apt purge *kde*
only the rat and the fucking foot have treated me nicely
I guess ymmv, and it all depends on the hardware you're running, meaning everyone has a different experience
to the lurker, use whatever you like and what works for you, threads like these never produce any productive or useful discussions
It never happened to me in Gnome. On KDE, this happened whenever I suspended my PC. If I didn't restart the PC, I would have annoying bugs, like images not wanting to open in threads here in LULZ.
kwin is so mighty that when your gpu driver doesn't wake-up (that's what that error means and if you didn't see such an error on GNOME, it means that gnome simply doesn't use the GPU), it stops your network from loading images?
About the images, I don't know how to explain, I left my computer suspended and when I came back, the images didn't work. I saw in the KDE notifications that the desktop effects had restarted. Then I restarted the PC and the images opened normally on LULZ again.
Oh yes... GNOME which took 15 years to enable thumbnails on the filepicker and then still didn't manage to get it working right, is soo well developer.
Eat a bullet, ebussy.
>GNOME is sluggish and laggy as fuck. >check out what's the cause >it isn't buffering right >theres a Merge Request waiting for more than two years now >GNOME developers simply don't merge it, because FUCK YOU >some distributions apply it downstream, but most don't
so if your GNOME is working or extremely laggy, is a gamble based on the distro.... nice
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441
KDE is Kool because it started with every single fuck you feature ever conceived, and then took 20 years to make it work without Krashing. I'm never EVER going back to gnome specially after gnome 3 and the latest libadwaita drama. It's all going to become irrelevant once all pajeets move to flutter and every corporate app becomes just a mobile app compiled for x64, so libadwaita is basically just a waste of everyone's time.
It's blocked because it breaks multi-monitor setups.
So GNOME is either super laggy, or it doesn't work with multiple monitors.
Choose your poison. And this for two+ years now.
I like KDE.
The ONLY complaint Ive is that, sometimes, for some reason, I cant open settings after changing a theme... Its random and doesnt actually bothers me.
+ its prob theme creators fault idk
+ prob fixes in newer builds (I run Kubuntu)
Whenever someone recommends KDE the GNOME dev runs in and yells "krashes!" to water it down. People have said it many times but it doesn't stick.
That meme used to be true 4 years ago but I just used it for a whole evening with no bugs
Only weird thing is there's no way to turn the screen off faster once you lock the screen, other than that it's almost perfect
I can tell you a 15 minute bug that has been present since the first release of 5.27.
Import several images into the wallpaper changer dialog and they will be imported with some missing, others displaying the wrong thumbnail and others displaying a black thumbnail.
This worked alright for years.
>using old versions of plasma
>not updating to the fixed version
>proceeding to bitch about it as if it were a gotcha
take your goddamn meds.
This is bait isn't it?
Plasma 5.27 is literally the current version of plasma you stupid mongoloid, the issue has been present since the first release.
5.27.7 is the current version
now take that cock out of your mouth and apologize for being such a homosexual
The bug still persist you fucking mouthbreathing negroid.
Hey, pretty sure this will be added as an option soon as i recall searching for the bug, yet as i didn't want to wait for them to fix it i did it myself easily:
Go to notifications -> Scroll down to almost the bottom and search for screen saver (Trust me, the event you want is in there) at the bottom click on Configure events.
You should see the screen lock and unlock events, put a run command on both of them pointing to different sh files.
Lock.sh
#!/bin/bash
sleep 1
if [ "`qdbus org.freedesktop.ScreenSaver /org/freedesktop/ScreenSaver GetActive`" = "true" ]; then
kwriteconfig5 --file $HOME/.config/powermanagementprofilesrc --group AC --group DPMSControl --key idleTime --type int 25
qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement org.kde.Solid.PowerManagement.refreshStatus
fi
LockReset.sh (for unlock event):
#!/bin/bash
sleep 1
if [ "`qdbus org.freedesktop.ScreenSaver /org/freedesktop/ScreenSaver GetActive`" = "false" ]; then
kwriteconfig5 --file $HOME/.config/powermanagementprofilesrc --group AC --group DPMSControl --key idleTime --type int 600
qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement org.kde.Solid.PowerManagement.refreshStatus
fi
Change the int 600 for whatever you usually use to turn off monitor when inactive (in seconds)
not the first guy, but i will take it, thanks!
Been using it myself for ~ 2 months without troubles, yet they'll add a preference for that soon so you can configure different times when the screen is locked, the issue says it's fixed but i'm not sure when it'll land.
https://bugs.kde.org/show_bug.cgi?id=348529
I've made myself a simple shortcut to turn off the screen to save on electricity, but it doesn't work now for some reason.
It turns the screen off and then turns it back on, if you want to have a look then picrel
also, it's late and i'm going to sleep so you probably wont hear from me again :c
>but it doesn't work now for some reason.
>It turns the screen off and then turns it back on
You might have something running that's preventing it, for example Steam does this. If you add a timer with sleep like 30 secs it might work better.
Thank you all for responses! I've made screenshots and I will make changes at the weekend. I also want to learn dbus integration and make some plugins for kde. I may publish them for others. For now have a good day and please take care of yourselves anons! <3
Maybe it's the keypress itself waking up the monitors. Try:
sleep 1 && xset dpms force off
Hey, probably it's just what this anon here suggested
But i'd recommend toggling the idleTime so it doesn't turn on and stay that way in case something accidentally disturbed your mouse
Nice, thanks
I don't suppose you also have a fix for spectacle's rectangular selection not working with fractional scaling?
>a whole evening
heh
It Krashes a lot on arch, tested KDE on debian just werks
Simply press ESC.
I hate GNOME shitters so much.
Rather than developing their own DE, they seeth about others.
no, see the problem is kde users can't like their own DE without shitting on GNOME. they just can't shut the fuck up about it and just enjoy their lives, but have to shit on GNOME constantly. so GNOME users respond in kind.
i don't think most GNOME users give a fuck about KDE. many of them might not have a real opinion on KDE cause of no experience of using it.
i have experience of daily driving KDE, and yes it's shit. it looks nice but it's so buggy and glitchy i just can't stomach it.
>the problem is kde users can't like their own DE without shitting on GNOME
>i don't think most GNOME users give a fuck about KDE
>i have experience of daily driving KDE, and yes it's shit.
goddamn what's it like being a walking contradiction?
that was in response to the constant shitting on GNOME by KDE users that i've witnessed on this board for years now.
it's like you're so fucking brain dead you can't like something without also hating everything else at the same time. just shut up about GNOME if you're not a GNOME user and instead talk about what makes your DE of choice great.
OP said nothing about gnome, you are the retard who brought it up.
he doesn't need to bring it up. it's brought up daily in multiple threads on LULZ regardless. eat shit
the only one eating shit here is you. every pro KDE Plasma thread that exists
>muh krashes
I haven't had Plasma crash on me in 8 years anon. What drugs are you on? I normally filter out gnome threads because most gnome users are shit flinging low iq naggers.
i'm surprised you managed to type that whole post without plasma krashing
srsly though. why do you think that meme exists if there was nothing to substantiate it?
because gnome users are shit flinging low iq naggers who can't wrap their smooth brains around desktop icons. there's nothing to substantiate because every single "crash" that has been brought up is due to a few factors
1) they ran it in a VM instead of metal and they used VMWare or Virtual Box. It ran fine in Boxes.
2) They probably ran it on nvidia or were missing nvidia drivers or the nvidia drivers were shit and to blame.
3) The issues they did post were overblown way out of proportion as if it were some gotcha, when the issue they posted were beta versions of plasma.
You came into a pro KDE thread to spout off gnome nonsense and start flamewars WHEN NOBODY THE FUCK ASKED YOUR LYING nagger ASS!
son, i've used linux daily since 2005. do you really think i don't know how to install graphics drivers or set my system up properly?
it's a fact that each time i've tried to use kde since v4 (v3 was fine iirc), it has been a krashy mess. and i really tried to enjoy it. stuck with it for months each time.
i've tried many DEs over the years and none have been as krashy as KDE is. or plasma or whatever the hell you want to call it. maybe you're a zoomer. most people know it by 'KDE', not plasma.
I used Plasma 5 exclusively for years and it sucked balls. AMD GPU and obviously running on bare metal and krashes were real. Shit was so annoying it made me move to Gnome. Now I have the newest Plasma on Steam Deck and stability seems to have improved. It’s still an ugly shitshow of random options and buttons but at least it kinda works.
I doubt you actually used it. You probably applied some broken theme made for an earlier version of plasma that broke it and you act like a total fucking homosexual about it.
While we are on the topic of themes, look for a theme that suits you better thats made for your specific version of plasma.
It would help if y'all all didn't lie so much.
Fuck off nagger.
weird, in the last year i got 3 crashes, and one of those three was trying to replicate it. on X, i didn't let wayland time enough to crash as last time i tried there was some weirdness that made my jump back to X on the first minute, i'll try wayland again on kde 6.
wayland is buggy on nvidia hardware
this is not the fault of plasma
I was using amd, and now i'm usually 90% of the time on the intel igpu.
Wayland was a mistake. I really liked Mir and wish Canonical would have continued development of Mir. Because its popular to hate everything Canonical it died.
Can't really argument about it as i haven't really have a deep understanding of mir, wayland otoh made some decisions that doesn't seem to align correctly with the needs of a full fledged desktop computer.
But I hate snaps.
Snaps are getting better now that they made them totally open source again. They did it in response to the whole IBM/RedHat fiasco. Give Snaps a few years and you won't care.
snap being FOSS doesn't make it not shit, it's fundamentally stupidly designed
as are appimages and flatpaks tbh but we dont have a good way of distributing software on Linux. Windows does it right IMHO. I just wish Microsoft weren't evil as fuck.
>Windows does it right IMHO.
spoken like a non-admin, i'll gladly take freetard bloat over VC++ redists and the absolute hell of windows server mass deployment. there's a reason even azure customers mostly use linux VMs.
I remember the firefox snap sent me back to the mechanical hdd era of start times, then realized that with 4-5 snaps the whole computer started several seconds slower and a quick systemd-analyze told me it was cause snaps too, i ran away and i'm not sitting on arch + kde and it's being quite comfy.
>wayland otoh made some decisions that doesn't seem to align correctly with the needs of a full fledged desktop computer
you fucking retard. the reason wayland was even conceived was because X.org doesn't align correctly with the graphical desktop needs of today.
stop reposting half-baked memes you found online and start reading facts instead.
wayland has worked perfectly in GNOME for years. that was the point of my post you fucking idiot. if KDE had fixed their shit, you would have a different opinion on wayland.
>you fucking retard. the reason wayland was even conceived was because X.org doesn't align correctly with the graphical desktop needs of today.
I looked at some of the tickets that were stopping me to make some stuff, and that they didn't want to implement as they can be abused, and at least now there's a draft for a portal so it seems that at some point in the future it'll work.
Lot of the security bullshit was in the way to be of use on a full fledged desktop, i don't care what you say. The easy fix would have been a proper permission system to ask the user, (one of the few things macOS does right, BEWARE: the rest of mac is a pita as it lacks basic functionality)
It seems they're more open to discuss this issues and implement the most than needed features now, ie: proper global shortcuts weren't possible till 1-2 years ago on wayland.
But there's still a lot of work remaining, ie:
https://github.com/flatpak/xdg-desktop-portal/issues/1046
So, yeah wayland is soooo great, lets just use wayland, everything works....
but somehow, there's still lot of things that are needed for things to work, so i'll wait till those things are in place instead of deluding myself.
if the bug tickets were on the side of KDE why the fuck do you think it's a wayland problem? seems it's aan issue with their implementation and not the protocol itself. wayland is just a protocol. it's the KDE team that's in charge of immplementing it, same as every other DE or WM.
did you even know that basic fact about wayland? of course not, you don't know anything about anything just like all the other fags who whine about wayland.
it's because of this basic misunderstanding about who's in charge of the code that makes retards on this board think wayland is broken.
Are you retarded?
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/56
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues
There's lot of missing pieces in wayland protocols, you delude yourself and then demean others to avoid further debate.
And the same happens on xdg.
Wouldn't it make more sense to create wayland compositor for blind people? This way the UX could be much more optimized for people who do not see.
it's literally the fault of plasma.
why do you think this page exists?
https://community.kde.org/Plasma/Wayland_Showstoppers
it's a fact that the KDE dev team has been *extremely* lazy about implementing wayland, and fixing bugs. it's my impression that while GNOME was working hard on their wayland implementation, the KDE team just laid back and silently wished wayland would disappear.
now they realize wayland is here to stay so at the *last* fucking minute they decide to try fixing their wayland implementation.
KDE is the reason why people think wayland is not ready. they are the reason why smoothbrained mongoloids on this board have been whining about wayland for years. none of this would've happened if those lazy KDE dev FUCKS would've just worked on their wayland shit like GNOME did.
>the KDE team just laid back and silently wished wayland would disappear.
can't really blame them
nobody likes wayland, gnagger. We didn't support Mir either. Eat a bag of cocks and go back to sniffing glue and robbing inner city walmarts.
I think gnome users are perpetually retarded.
picrel is a Windows 11 theme I am working on for Plasma 6 running on Plasma 6 beta. I dont recommend running Plasma 6 until it's done but even in beta it is really stable.
tbh the only times i managed for it to crash was on edit mode, while using the search bar to filter widgets, and that was fixed quite fast.
Nice legs.
Plasma 6 shows a banner in the bottom right...
That's Windows 11.
Can you just fucking shut up
Can you gnaggers stop lying in every thread about KDE Plasma?
>it looks nice but it's so buggy and glitchy i just can't stomach it.
lies, tell me princess have you tried using Plasma (its not called KDE, that would be like calling Windows, Xbox)
go be a retard somewhere else please.
>NNNOOOO DON'T CALL ME OUT ON MY BULLSHIT!
>YES I SAY *KRASHES* EVERY TIME SOMEONE MENTIONS KDE BUT THAT'S BECAUSE YOU WERE SO MEAN TO ME FIRST!
Why do you think krashing is a metric for how good software is?
Gnome is the worst DE of all but KDE isn't much better. Linux DEs are an abomination across the board, the only reasonably decent one is MATE.
i think MATE is cool cause GNOME 2 is the era when i first got into Linux. but it's gonna have a hard time keeping up with the ever-changing GTK toolkit. i feel like DEs like MATE and Xfce are going to be perpetually behind. and they don't have a lot of manpower so it's difficult for them to implement wayland support.
Let me guess, you also hate Wayland and think screen tearing is good?
fpbp
Isn't MATE literally just a fork of Gnome?
yes, MATE is a fork of GNOME (2.x). it's cool and all, but outdated as fuck, and is in an eternal race to catch up to changes in the GTK toolkit.
I wish Trinity got that kind of attention.
All I ask is hidpi support and maybe a bit of modernization
just wait until you discover KDE Connect. can't live without that shit anymore, it's so convenient.
what is that?
like airdrop for oople devices.
just tried that out for the first time
pretty sweet
I put kconnect on my gnome
Use GSConnect on Gnome, anon.
Idk last time I used it I didn't find it very useful. That was like 3 years ago. What's convenient about it now?
i constantly use it for sharing files and clipboard contents between devices. especially useful if you have a password manager. it's also great to use your phone as a remote during presentations, ring your phone if you lost it somewhere around the house, etc. depends on you and your usecase, but i get daily use out of it.
never tried that (i dislike gnome but you do you) - does it integrate well? like adding "share to [device name]" entries to the right-click context menu inside the file browser?
i use it as a remote when i'm in bed watching videos
Broken piece of shit that can't handle large file transfers
>now
Only KDE 4 was bad.
kde has been a buggy glitchy mess ever since v4. try using it for longer than an evening and you'll notice. plasma 6 will default to wayland, and i have no idea how they'll pull that off considering kde's wayland session has always been a complete clusterfuck.
it's like they're not even trying.
ironically, most apps for qt / kde are better than kde itself.
I am using KDE on Wayland for over a year now and it is more stable than xorg lol
What distro did you test?
it was on fedora. i've been running fedora exclusively for years. i try kde every now and again and stick with it for a few months each time, but it's always glitchy. it's not immediately apparent but it's minor shit that adds up in the end.
last time i tried kde was around a year ago i think.
Every DE is gonna have an assortment of minor issues so fuck it. I'm sticking with KDE because the file manager feels awesome and responsive with huge media directories and has thumbnails on folder icons.
>kde has been a buggy glitchy mess ever since v4. try using it for longer than an evening and you'll notice
using it for 5 years and i didn't notice that, what does "glitchy" even mean in the context of a DE?
well, parts of the screen would get stuck. parts of application windows would stop updating, and / or flicker from black to normal. that would happen only after i've had a session going for a while, more than 1 day. the solution was to log out and in again.
on my old build it was intel graphics. their drivers are open source and high quality so you can't blame that. now i have amd graphics but haven't tried kde on this build yet.
see
I bet you're trying to use it with an Nvidia or something.
I miss KDE 3.5.10 so much bros.
yeah, i kinda miss it too. i miss how it looks, but i guess you can make modern KDE look like that too.
bloat
I reinstalled Kubuntu 22.04 LTS with KDE 5.25 and now I cant get GPU sensor values in widgets. nvidia-smi has no problem reporting. Halp! What's the backend that's missing?
https://invent.kde.org/olib/thermalmonitor
I have this installed and it tells you what it requires. Whatever you use there might be a similar page for you to check from.
Probably fixed in later KDE Plasma, the Nvidia GPU reporting stuff has been fixed a few times in recent versions.
This uses the same backend as System Monitor and its widgets.
it's garbage compared to gnome
>Ubuntu
>Gnome
is it even possible to be more reddit than this
FILE
PICKER
THUMBNAILS
they are here anon
not to mention
>1366x768
>hp
Only krashes 2 times a week now!
ive literally been shilling this shit for free for months
Valve told you with the steamdeck. I now like it even over xfce. Also never listen to gaynometards.
because people who use kde just use their computers and dont talk about kde
t. never had any issues (even on gayland) since 2022
It's good anon. Much better than Gnome. Fuck Gnome and epussi.
KDE master race!
Because every "it's good" here is met by "">krashes"". What's the point. Not gatekeeping but it's on you now to discover it.
i don't really hate kde. just tired of the never-ending psychotic whining about GNOME. to each their own
The real battle should be kde vs xfce
Gnome is trash. Shut the fuck up.
>BAAHHHHHHHHH NOT THE KOOL DE OHNONONO NOT THE KDE!!!
Kek. I bet you're a r/gnome regular. You people can't seem to shut the fuck up about how bad and buggy KDE is when GNOME cannot even fix their fucking calendar on the top bar.
The absolute state of GNOMEfags. Cannot fix their own shit so better start spreading FUD and lies about other projects that are simply better.
The reason why GNOMEtards think KDE is buggier is because whenever something stops working in GNOME the devs just pretend it was an intended feature.
Kek sounds about right, Gnome is fucking useless.
>2023
>Krashes
Sounds like a you problem.
Everybody told you but you wouldn't listen
X11 Plasma just works.
Only problem I still have with KDE is that on multiple monitors, it never seems to go into sleep right. It never times out, and never takes the settings into account.
The seeth itt by GNOME cucks is what happens when we don't have an ebassie thread in the catalog.
Some people were saying that ebassie threads got stale.
They don't understand that we create them to keep the GNOME devs contained (who spend their time shilling on LULZ rather than developing their DE).
Every post a GNOME cuck makes in a dedicated ebassie thread, is a post that he doesn't make anywhere else.
Those threads protect us from their bad takes, ebassie posters are massively improving the quality of LULZ.
Gnome is for stable distros, kde is for rolling release distros
why?
Because on stable distros you have to live with the same bugs for a lot longer time
And on unstable ones you get new bugs
cuz you only care and listen to GNOME troons clearly
Anyone with a functional brain immediately knows KDE was always superior to GNOME
No matter how much time I invest on KDE, it always looks and somewhat behaves like dogshit
Yeah, it's very convenient and has features other DEs don't. But half the time I'm having to wait for shit to just open, for it to let me save a fucking file because the file picker is just so good that it has to take a year to load shit. I have to use these things, Kvantum, QtCurve, it's all a goddamn mess. Window decorations make everything so sluggish opening a new dolphin window makes my cursor stutter, what is this nonsense. Shitty defaults or bust I guess.
Tried every single thing you stated, no slow picker no cursor stutter, nothing, what distro and when did those thing happened?
openSUSE
Have a folder with thousands of files, try to save something there from the filepicker.
Try installing some random window decoration, maximizing and minimizing windows, opening them up.
I'm using sweet, with kvantum, i tried saving an image with the file picker in a folder with 1.247 files and it opened in 1/5 of a second, probably faster, it's hard to measure as it's quite fast, i don't have bigger folders in this pc as i have to access the same folder with a mac from time to time and mac explorer (finder) tends to crash if there's too many files in the same folder (macOS is a joke)
>1/5 of a second
I wish
I have to save files on the same folder and everytime I have to wait for 4-5 seconds. I can press the save button, that window is not going to disappear until then.
>4-5 seconds
I didn't even have this issue back when KDE sucked. Either your distro is fucked or you need to buy a new machine.
Is a 3600 + 6600xt with 32gb of RAM not enough for KDE plasma now?
Then the former. I'm on a discount Ideapad that I only haven't replaced out of laziness, and the file picker in KDE is perfectly fine for me.
At this point just throw away your PC and buy a Mac, obviously you are unable to operate it. A Chromebook would be another option.
What is this cultist like reaction? Christ. I'll use XFCE I guess.
There is no cultist reaction.
First you say that you save everything in one folder like a phone tard. Then you say that loading it is slow and people say that they are just fine to watch folders with 40k files. Then you say that saving takes apparently 5s? Something that absolutely nobody can recreate and that was never an issue in more than a decade?
Obviously the issue is on you. Either you are lying or computers simply aren't for you.
Buy a Chromebook, they perfected the "don't use the filesystem" workflow from Android.
Do I really need to make a .webm of this shit? You karpies are something. Just footfags with a different hood, I swear to god. Your beloved filepicker doesn't even have a search function past the folder you're in, so don't be bitching now about putting everything on one folder.
If you would be interested in telling us about your problem or finding a solution, you would tell us what you saved from what applications and not do a generalized: "Saving takes 5 seconds".
Because guess what filepicker your firefox browser or chromium are using?
If you are using the gtk default, you will have the exact same experience on XFCE. Because it's the same thing. If you use the xdg-desktop-portal, you probably should point that out because RedHat would want to fix that very fast. They need it to shill for flatpak.
An example is it takes me nearly 5 seconds to save an attached document on an email from thunderbird, using the KDE file picker.
openSUSE has firefox patched builds to use the KDE filepicker, but if that wasn't the case I already know how to use that specifically. Yes it is the filepicker that doesn't need to previously generate a thumbnail cache to show thumbnails and it is the filepicker that has a little button on top that shows and hides these previews. I don't know what else to say here.
Thunderbird is the same thing as firefox and must use the desktop portal to see the kde filepicker. A feature we got from flatpaks that has corporate funding.
If you report it, an army of RedHat devs will gladly help you.
But why do you even use the desktop portal?
>openSUSE has firefox patched builds to use the KDE filepicker
No such thing exists. You either use GTK dialog or xdg-portal.
>I don't know what else to say here.
Then I will say it for you anon... Gnome is fucking garbage. KDE is fucking based.
>An example is it takes me nearly 5 seconds to save an attached document on an email from thunderbird, using the KDE file picker.
>OpenSUSE
many such cases
funny, i had exactly that problem with GNOME
>GNOMED
I'm using openSUSE and the file picker works instantly with zero lag. Your computer is just broken or you made it up.
I have a shortcut on my desktop to quickly change theme and color scheme by running things like plasma-apply-colorscheme.
I siwtch multiple times per day. Never did i experience any issue. And my meme folder had 40k images and worked just fine, till i got annoyed at having to type for search and sorted them into subfolders.
What's it like living in 2014?
Because it isn't.
I've daily driven KDE for years and have only experienced like 2 or 3 crashes in the past couple of years. Anecdotal but you'll never convince me that current KDE is constantly crashing. Also Gnome deserves to be shit on.
Same. "Krashes" is an old meme that has no relevance today. And I agree Gnome is absolute garbage.
>Why did nobody tell me this is good now?
why would we lie to you?
I've been using it for 2 years and it's great and only been getting better, even on Wayland.
I use Plasma with an Arc A770 and it's good
5.27 has been way more stable than the past few releases
I'm using it right now because is the only DE that push to talk works on Wayland, it's way snappier than gnome, but it's ugly as fuck they need to hire a designer, also most apps are made using GTK so they don't look as good on plasma
Steam deck uses KDE
no it uses plasma, calling plasma "kde" is like calling Windows explorer or your PC the modem, you should probably kill yourself.
nta but google "gnome or plasma" and send a screenshot of the results
you missed the point retard
Problems I have woth kde:
Baloo sucks ass
Search sucks ass
Thumbnails for videos suck ass
I like video thumbnails it even show different frames on mouse hover, but yes, baloo sucks ass, i tried very hard to have it working and most of my problems with search got resolved once disabled it.
Works fine for me. Looks like you're too retarded to use a desktop environment.
It's pretty good so far, Plasma has come a long way since 2008. I do wish it could support shadows under CSD windows like GNOME Shell does though, helps integrate things better.
Been using KDE for years now and I haven't found it to be buggy at all.
It's gotta be PICNIC errors with these people who have problems with KDE.
>Installed KDE manually
>Running old as fuck version
>Citing experiences from 5+ years ago as if relevant today
>Other weirdness
These are the fat autistic man children that would have run into problems with any desktop environment.
brace yourself, the current ebassie thread got deleted by jannies, the GNOME devs will come to this thread again
>The GNOME foundation started paying jannies to censor anything negative to GNOME
Kek that just confirms that GNOME devs post here all the time. A few threads were all it took break their minds.
nice conspiracy theory. it's the other way around dipshit. if you say anything positive about GNOME on LULZ you will get ddosed by some random pissy jannie who thinks the healthy competition between DEs is some sort of spiritual war between good and evil.
i wish those retards would go leave and stop involving politics with software.
>NOOOO IT'S THE OTHER WAY AROUND
>GO leave BUHUHUHU
Holy shit you're seething, lmao. It's a well known fact that GNOME devs talk about politics everyday. Literal troons and naggers make out the GNOME foundation who want "diversity" and "ethical" software.
https://weirder.earth/@sophie
https://gitlab.gnome.org/BrainBlasted
There's also the pajeet dev who goes by blackcain on Reddit. You're probably a trannie too. That's why you're so fucking mad right now, kek. About to pop a vein probably lol.
you're a fucking moron trying to fight fire with fire.
yes, the way to battle blue-haired feminists and troons is to say 'fuck the israelites', and 'heil hitler you fucking cuck', read the bible and vote for trump.
you think you're any better than the GNOME devs? what's the fucking difference?
you're like a retarded teenager lashing out at their christian parents by reading the satanic bible and wearing goth clothes. you're not fighting anything but shadows in your mind.
you're just a reactionary little cockroach who can't judge things based on their technical merits, but have to involve unrelated shit like politics.
>hurrr durrrr trumpp
lmao fuck off moron I don't give a shit about your murican politics and I ain't reading all your troon schizo babble
what a fucking seething loser hahaha
well, you probably can't read full sentences anyway. you strike me as someone with the IQ of an amoeba
Gotta say I don't think I've seen Wayland fags cope by blaming KDE for Wayland being shit before this thread.
KDE pushed Wayland into adopting fractional scaling. Something that wayland and GNOME developers considered as "not needed".
Similar to how Valve pushed wayland into adopting the tearing protocol, allowing vsync to be turned off.
The wayland purists, who think that you should never use a higher resolution than 1080p, must be pretty mad about that.
But those people only exist as corporate paid developers who try to castrate things to make their work easier... which tells you a lot about those posters here.
nice conspiracy theory. i think most wayland devs and users are happy about those patches.
that's because it's literally true. do you even know what wayland is you stupid shit? it's a protocol.
gnome has already implemented it, successfully. kde devs have been dragging their feet, doing a shitty job. that's why mongoloids like you think wayland is shit.
because you use kde and they didn't do a good job.
The problems people have with wayland aren't related to the KDE showstoppers, you coping troon. Your shitty protocol literally does not have feature parity with what it's supposed to be replacing.
>muh feature parity
what features? network transparency? have you ever actually used it or are you just whining about it for no reason like everyone else? sending 4K pixmaps over network for every frame. yeah good luck homosexual.
or what about the ability of X.org to let any fucking process in the system listen in on keystrokes and know what's displayed on the screen? yeah, great feature.
the fact that kde has done such a lazy shitty job of implementing wayland is the reason why it's garnered so much hate. smoothbrains like you just fire up a kde wayland session and see it's completely b0rked, hence wayland is bad.
when actually, it's just a piss poor implementation.
>kde has done such a lazy shitty job of implementing waylandd
Wayland gathered hate because GNOME started to recommend it as default while it was still completely unusable. They changed at a time when pipewire was still not widly distributed, meaning that they cucked their users out of screenrecordings, screenshare or even screenshots.
They also didn't (afaik they still don't) let you choose if you want xwayland applications to get scaled by the system or to trust them to scale themselves. Meaning that if you had a scale of 150%, they would render at 1:1, then scale up to 200% and then get scaled down to 150%. DPI settings wouldn't help you out here either. They look ridiculously washed out.
GNOME also STILL doesn't support native fractional scaling on wayland and. GNOME also shipped wayland with the fucking cursor lag under load.
Canonical noticed it and they ship GNOME still with xorg per default. Fedora followed the official recommendation and defaults to an unusable GNOME wayland for years now. Which is also the reason why they were the first to make the pipewire switch.
KDE doesn't have most of those problems in their current version and they will have none of those problems in Plasma 6 (fractional scaling is supported by every Qt6 application, they just have to port KDE Gear to it).
And guess what:
KDE NEVER recommended you to use wayland because they knew that people use monitors that are larger than 1080p and they knew that a laggy cursor under load is completely unacceptable.
The official recommendation to use wayland on KDE will be with Plasma 6. Not earlier. Even thought that it is in a much better state that GNOME wayland, they STILL don't tell you to use it.
GNOME 45 has been patched to run keyboard / mouse input in its own thread so there will not be lag anymore. That had nothing to do with Wayland but was a limitation of GNOME itself.
I haven't heard about KDE having input lag problems. So it's literally not a problem with Wayland, it's just a problem with your brain.
Let's hope Plasma 6 fucking fixes the Wayland session, since it will be the default.
>since it will be the default
Pretty sure this is decided by distributions and not Plasma 6.
>in the future there will be no cursor lag
There will be less. It won't be gone, only less. You can't fix the cause, because the cause is in atomic modesetting and would require massive DRI kernel patches, involving all GPU drivers. And yes, this is a wayland problem that is in every single wayland compositor.
By doing their own thread stuff to prioritize the cursor as an improvement, they copied what KDE did.
And on KDE i could additionally always disable atomic modesetting and have a smooth cursor that way. Then i wouldn't have a strict standard wayland session, but it's at least usable.
And this is 2.5 years after wayland became the official recommendation and default for GNOME.
If you follow the recommendation of GNOME developers, you end up with an unusable system with blurred windows, cursor lag and broken screen recording.
If you follow the recommendation of KDE developers, you will never experience a single one of the listed bugs, because they are all already fixed and we just wait for the Qt6 ports to get Plasma 6, which will recommend wayland as default.
alright. i still don't understand why it's surprising that the cursor lags when the computer is under full load. if you're using 100% of your CPU at any given moment, you're not going to be able to do anything. the desktop is not going to be responsive cause there's literally no CPU cycles left to deal with your input.
Maybe you should think about the concept of prioritization and what the nice command does and ask yourself why this was never an issue with xorg. Or with windows. Or with mac.
Maybe you once played a game that doesn't have vsync on and is calculating as many frames as the system will allow and would run with 200 FPS, despite the monitor having only 60 Hz and those frames being useless?
Or maybe you did some rendering once, which uses whatever resources are available.
The mindest: "It has to be that way"
...is the reason why people using GNOME in the default configuration the past two years experienced a crappy shitty and unusable system, if they used any hardware younger than 10 years or any game or rendering.
Maybe read this if you want to know more about what's going on with the cursor:
https://zamundaaa.github.io/wayland/2023/08/29/getting-rid-of-cursor-stutter.html
it is a problem in all those systems though. if you're under full load, that's it. there's no getting around it. just like there's no getting around if your RAM has reached 100% use. if that happens the system will lock until resources are freed up.
but that's specifically under full load. if it's just normal load, then yeah, the cursor should not lag. i will try GNOME 45 as soon as it becomes available in the fedora repos and stress test the wayland session to see how the cursor responds.
that might be a while though, as i don't know if that package will become available for fedora 38. they might just wait for fedora 39, which is just around the corner.
Preemptive multitasking is a thing since 1984.
GNOME and wayland devs might not know that, but we got the solution 39 years ago.
pre-emptive multitasking is not going to do anything if your CPU is under 100% use and your RAM is 100% full.
>or what about the ability of X.org to let any fucking process in the system listen in on keystrokes and know what's displayed on the screen? yeah, great feature.
Name a single OS where this isn't the case.
Hard mode: No phone shit.
It's not the case in Wayland. I know that much.
idk if you know that, but the Unix permissions are based on users and groups and if you run an application as a user, it has the permissions of that user.
This is by design.
If you want to get out of that, you just create a different user. i.e. every webserver runs as its own user.
Putting a gorillion layers on top of that won't help you much and just has the danger of false security.
An application that doesn't keylog you could steal your credentials by watching browser cookies just fine.
gnome hasn't even implemented server side decorations whi h breaks many applications including vscode which either crashes or has no way to move or resize it. It also doesn't implement suspension pause which means watching videos doesn't work properly as it can go to sleep if you don't move the cursor. This is why mpv devs hate gnome.
the motto of wayland is "every frame is perfect", and they refused to add an option in the protocol to disable it since they were arguing that disabling it has no benefits. They only changed that because valve paid a wayland dev to change that.
>They only changed that because valve paid a wayland dev to change that.
Why don't we pay GNOME developers to go develop something else?
Why don't we pay someone to stop GNOME developers from ever developing anything ever again?
I'm on Wayland and use KDE. Works fine.
It has always been good
It's been good for a while now, it's old news
KDE is based.
Gnome is cringe.
Everything else is meh.
>he's still seething
Kek this GNOME trannie is so fucking desperate for attention lmao. No (You) for you this time, Sophie.
>he's STILL seething
>now deleting and making multiple posts
Holy shit I broke this trannie's mind hahahaha. The absolute state of GNOME devs lmao.
Steam Deck uses KDE.
German engineering wins again.
Latte is an unbelievably buggy piece of shit lately and supposedly dumped since the main guy isn't working on it anymore.
Whats a good alternative?
Doesn't this have temeletry that can't be turned off?
https://community.kde.org/Telemetry_Use
Most sections have the "Opt-In" keyword, but the very top section under "Plasma" does not. Is this suspicious, or can some anon point out why this is not the case?
kde connects to google, cloudflare and other servers all the time
this is without google drive integration and no telemetry opted into
Source?
Never found anything in wireshark.
>Source?
running lsof -Pni seeing kioslave5 or something and checking the ip addresses
It is not a constant connection, only every so often. Might be completely benign but I don't know why it does it.
kioslave are network shares and stuff like that, it's also what makes the google drive connections if you have them setup.
If it tries to connect without you ever using that, it's weird and suspicious.
btw. you can remove the "kio-gdrive" package to remove that capability completely.
I don't have kio-gdrive and never have, it still connects to google.
Wireshark shows nothing.
They have it written in their privacy politcy that telemetry will always be Opt-In and disabled by default
>Some software produced by the KDE Community may include telemetry components, which provides details on the device it's running on to us. Where this functionality exists, it will always operate on an opt-in basis and be disabled by default, with the ability to change your preferences at any time.
https://kde.org/privacypolicy-apps/
Why even care about telemetry?
linux desktop only works if you have standard-dpi monitors and open source drivers.
the moment you either have high-dpi or nvidia drivers its game over.
nvidia doesn't work this isn't a problem with linus' unix
Gnome for laptop, Plasma for desktop. That's it.
Most people itt are retarded gorilla naggers. Literately nobody cares if you use Kde, Gnome, Xfce or some other thing. Most DE's are solid and it really depends on personal preference so you cannot say that one thing is better than the other.
WRONG.
Gnome is fucking shit and if you use/like it you are a certifiable idiot.
if you use plain GNOME without any extensions you objectively deserve mockery
are you joking? someone that use something shitty have to be mocked for you? that change nothing to other life if you use ubuntu+gnome (shitty) or you use arch with some other popular ultra giga nigga nerd edition, it change NOTHING someone hase the liberty to use something bad/shitty or other without being mocked and bullyed for that
good night sir
prepare to be mocked
thanks sir, i say that but it's for just sayng that mocke the newbies is bad but i use debian11+xfce
Try Intel ARC. I know it sounds like shilling but I've never had a more stable system before in my fucking life.
Used to use Openbox religiously to avoid ((GNOME)). KDE sucked back in the day so I avoided it. Tried KDE Plasma on my Steamdeck and now I use it on my new builds. It's pretty great and comfy and customizable. First DE I've used that doesn't make me miss any features from Openbox.
>anons suck kde's Kock on the daily
>decide to try it
>claustrophobic mess of settings
>multiple fonts are being rendered incorrectly on 4k monitor
>dislike that it's bloated with stuff like KDEwallet
>feels like I'm being watched (not sure if schizo)
>sudo apt purge *kde*
only the rat and the fucking foot have treated me nicely
I guess ymmv, and it all depends on the hardware you're running, meaning everyone has a different experience
to the lurker, use whatever you like and what works for you, threads like these never produce any productive or useful discussions
Using Plasma makes me feel like I'm using Windows in many ways
The sluggishness specially
GNOME been crashing on me every time I lock the computer. Seriously considering trying KDE now.
It never happened to me in Gnome. On KDE, this happened whenever I suspended my PC. If I didn't restart the PC, I would have annoying bugs, like images not wanting to open in threads here in LULZ.
kwin is so mighty that when your gpu driver doesn't wake-up (that's what that error means and if you didn't see such an error on GNOME, it means that gnome simply doesn't use the GPU), it stops your network from loading images?
I believe Gnome handles Nvidia GPUs better.
About the images, I don't know how to explain, I left my computer suspended and when I came back, the images didn't work. I saw in the KDE notifications that the desktop effects had restarted. Then I restarted the PC and the images opened normally on LULZ again.
Well fuck. From the trash to the gutter. This is super annoyig.
considering plasma has more features and less contributors, you'll only be getting more bugs.
Oh yes... GNOME which took 15 years to enable thumbnails on the filepicker and then still didn't manage to get it working right, is soo well developer.
Eat a bullet, ebussy.
>GNOME is sluggish and laggy as fuck.
>check out what's the cause
>it isn't buffering right
>theres a Merge Request waiting for more than two years now
>GNOME developers simply don't merge it, because FUCK YOU
>some distributions apply it downstream, but most don't
so if your GNOME is working or extremely laggy, is a gamble based on the distro.... nice
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441
KDE is Kool because it started with every single fuck you feature ever conceived, and then took 20 years to make it work without Krashing. I'm never EVER going back to gnome specially after gnome 3 and the latest libadwaita drama. It's all going to become irrelevant once all pajeets move to flutter and every corporate app becomes just a mobile app compiled for x64, so libadwaita is basically just a waste of everyone's time.
It's blocked because it breaks multi-monitor setups.
So GNOME is either super laggy, or it doesn't work with multiple monitors.
Choose your poison. And this for two+ years now.
I like KDE.
The ONLY complaint Ive is that, sometimes, for some reason, I cant open settings after changing a theme... Its random and doesnt actually bothers me.
+ its prob theme creators fault idk
+ prob fixes in newer builds (I run Kubuntu)
Kubuntu is based, is the working man's distro, no tranny shit, no autismo "muh systemd sucks!!", just load it and it fucking works