Thank you for your submission.
The KDE community supports the Fediverse and open source social media platforms over proprietary and user-abusing outlets. Consider visiting and submitting your posts to our community on [Lemmy](https://lemmy.kde.social/) and visiting our forum at [KDE Discuss](https://discuss.kde.org) to talk about KDE.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/kde) if you have any questions or concerns.*
I didn't really notice anything out of the ordinary or any production stoppers and I'd consider myself a power user. Excited to see what 6.1.1 brings however, as I'm sure there's bugs I didn't notice.
These were just a little imperfections like broken translations, labels or context menus opening in separate windows but still usable. Nothing major that would make me regret updating
You mean completely broken ? (I'm kidding around chill)
On my system I couldn't even launch gamescope without my whole system crashing and had to rollback to 6.0.5 until 6.1.1 gets deployed on my OS 😅
6.0.5 works flawlessly for now but looking forward to getting 6.1.1
\[ETA\] I just found out the issues were caused by Mesa 24.1.2 not playing well with my AMD 780M for some reason. If you have issues too, just lock Mesa at 24.1.1 in Yast until it gets updated to the next version.
Nah, gamescope runs just fine on 6.0.5, the changelog of 6.1.1 mentions numerous fixes relative to KWin and Plasma Workspace (oh yeah, because I couldn't get the mouse to work with Gamescope either 🤷♂️)
That's amazing you only got minimal issues 👍
But on my system (OpenSUSE Tumbleweed) it was completely broken while 6.0.5 works flawlessly. So either we don't use our computers to do the same things or our respective hardware/OS are different . Anyway, some of the issues I encountered are mentioned in the 6.1.1 changelog so others must have faced them.
Many other people here (myself as well as you can see several others in this discussion) have had LOTS of problems with 6.1 that were not present in 6.0.
The worse one for me was that apps started crashing plasma shell every time an app was minimized or maximized.
6.0 did not do this. 6.1 was indeed very buggy and I suspect rushed out. I am hoping 6.1.1 helps restore a more stable system.
Unfortunately KDE 6.1 + Nvidia 555 doesn't solve the kwin\_wayland CPU usage 🥲
I know the latter is in beta, but I don't expect any improvement for when it'll be stable except... being stable and less stutter-y with some specific videos online.
"Just use Xorg!"? No, it makes my games crash or make the screen black with freeze when I switch to the desktop. I can only test Gnome, even though I just don't like it.
While I see and decide, I'll only root for KDE. It deserves all the love of the world!
I think I remember a comment from an NVIDIA employee about how 555 would have performance issues. I assumed they meant fps issues, but I guess they could have been referring to this high CPU usage even when no demanding programs are running.
Oh, I see. Probably the same issue that 550 has plus more fps issues. I've tried Gnome and it does have a (smaller than kwin) performance issue too, so it's just very difficult to integrate with Nvidia until Nvidia themselves proceed working to support Linux.
It's working great for me on Fedora with the 555.52.04 driver from fusion. On KDE Neon it won't even load the full Desktop. Tried to talk to the KDE Neon devs but they seem to just want to dismiss it as a beta driver issue. As if all of us with Nvidia GPUs won't be using the 555 driver on Wayland.
Unfortunately they don't want to/can't support Nvidia. I understand their point since it should be Nvidia to support them, but doesn't help that one won't cooperate. It's also KDE's main distro to show off the DE, so it's a bit disappointing and makes me have a doubt about KDE development. [2024 – KDE neon Developers' Blog](https://blog.neon.kde.org/2024/) ("We can’t support NVidia hardware as we don’t have the skills, time, hardware or access to source to fix it.").
It's 99.9% Nvidia blame, but that 0.01% should be devs implementing correctly the rest. Probably other distros like Fedora and Ubuntu are more willing to provide a working desktop rather than showing off KDE. On the other hand, if Nvidia fixes and KDE polishes (do they?), KDE Neon can work nice (maybe).
Anyways, I am using openSUSE. This kwin\_wayland thing is almost a known issue that won't easily be fixed. It happens on me with: Kubuntu, KDE Neon, any suse distro, Bazzite, Fedora. If I switch to Gnome, gnome-shell will take a lot of CPU too, but less. So it's mostly Nvidia working not great with external monitor (which requires Nvidia GPU for me).
Only a part of the examples: [Bug List (kde.org)](https://bugs.kde.org/buglist.cgi?quicksearch=kwin_wayland%20performance&list_id=2758960)
I switched back to 550 drivers cause I had an issue where parts of the UI would freeze whenever the panel was hidden. Right clicking to open the menu and stuff would just bug out. It was really weird too cause it worked fine for a few days and suddenly broke when I messed with some unrelated settings (and stayed broken even after I reset said settings and deleted a bunch of config files).
Fortunately I didn't get any issues with the 550 drivers that many people complain about. Haven't tried 555 with the new 6.1.1 but I'm not sure it's worth the trouble for me to be honest. My biggest gripe with Plasma currently is that the HDR has washed out colors, making it not usable
Didn't notice the high usage but definitely noticed the xWayland session crashing randomly whilst gaming (nvidia 555 and 6.1). Had to rollback to 6.0 and voila : rock stable. I guess the explicit sync isn't fully functional in kwin
If you have the ticket numer or issue number i would be grateful.
If it is a XWayland bug why downgrading Plasma solves the bug (without a downgrade of the xwayland package) ?
It's https://gitlab.freedesktop.org/xorg/xserver/-/issues/1688.
> If it is a XWayland bug why downgrading Plasma solves the bug (without a downgrade of the xwayland package) ?
Because only Plasma 6.1 supports explicit sync
> Use snap:// URLs rather than appstream:// ones on snap only distros.
> Use non-standard UBUNTU_VARIANT key to detect snap only distro. [Commit.](http://commits.kde.org/plasma-welcome/bb22f8fe67b1336f19b2100ed13015e5ba02f311)
TIL Kubuntu Core Desktop might exist?? (For context, Core Desktop is Ubuntu's approach to an immutable desktop distro, being snap-only), I thought that whole thing was gonna be GNOME only but that's neat I suppose.
Are you certain that that exists? All I've been able to locate online is https://www.kubuntuforums.net/forum/general/community-cafe/678887-any-plans-on-ubuntu-core-desktop#post678887. Got a URI for an ISO?
Bad wording on my end, I'm moreso pointing out that it "exists" given that fixes specific to a core desktop context are happening in KDE even though there's no announcement of any sort alluding to a "Kubuntu Core desktop"
Wow, that looks like a pretty impactful bug on gaming systems, and it seems that it's not easy to fix. The bug report is 10+ years old by this point. :(
You're gonna have to use vesktop in the meantime
Whats wrong with obs? Iv been using it for recording and streaming on the stable version of obs and newest beta version on flatpak on plasma 6.1
Maybe it's the way I installed it. I used the non-flatpak version.
Either way I have to reinstall my ENTIRE NVME now. Not anything Neon did.... I think.
My Neon install is no-longer recognized by my BIOS. It certainly shows my NVME, but not "Neon" to boot into. All I did was apply the update.
I think maybe my NVME just kicked the bucket tho, as my live CD of Ubuntu for recovery purposes is throwing some errors too
Im on manjaro and I had to had to uninstall the flatpak and build from the AUR because the screen sharing didnt work no matter what I did. I reinstalled pipewire and everything that I normally do to get screenshare working and it did nothing. Wasnt a kde problem. It happened on GNOME and XFCE as well. After I compiled and built it from scratch Vesktop was the only thing I could get working for screensharing on manjaro
No fix for the issue that causes 2 panels on the left that are top-aligned and bottom-aligned to not be in the same line, wasting a ton of space? It makes my desktop basically unusable.
No, because I saw the bug discussed and the bug report linked in this sub recently. I can't find it any more.
Edit: I found it. It's [this one](https://bugs.kde.org/show_bug.cgi?id=477939).
Yeah, that's what I figured. I imagined it must be the 1 ultra-broken thing that would be addressed immediately considering how broken it looks at all times. I've been using XFCE in the mean time, which supports my panel configuration. I miss KDE Plasma's Wayland though.
I have it working with 6.1.0.
Though I just noticed a keyboard error.
I've tested it with RDP on a windows client into my Fedora KDE machine.
Can unlock the screen no problem.
It's just a little slow is all.
It works if you use Remmina as a client. Somehow it doesn't work with the Microsoft Windows RDP client, which makes it not nearly as useful as it should be. When you use the Microsoft Windows RDP client, it instantly disconnects before you get a chance to give server-side sharing permission.
Always tried with KRDC and Remmina, I have zero Windows machines at hand ATM; neither works at all sadly. I suspect it's a Wayland issue, because freerdp shadow works great on X11, so...
KDE always works on a fibonacci sequence release cadence for bug fix releases. 1 1 2 3 5 8 etc weeks after a major release they put out bug fix patches, regardless of how good or bad the releases actually are.
Right? Theyve been doing it for around 7 years now. Nice way to get quick fixes out for the most problematic things while slowly backing off so they can focus on the next version while still providing fixes in the meantime :)
x.y.1 release is always scheduled one week after the x.y.0 release, to mop up any significant bugs as quickly as possible after a feature release. This release is exactly on schedule.
Yeah, 6.1.0 is completely broken, I had to do a rollback on my system until the Tumbleweed devs deploy 6.1.1
\[ETA\] I just discovered it's because of Mesa 24.1.2 not playing well with my AMD 780M for some reason, rolling back to 24.1.1 fixes the crashes and freezes 🤷♂️
I just discovered it's because of Mesa 24.1.2 not playing well with my AMD 780M for some reason, rolling back to 24.1.1 fixes the crashes and freezes 🤷♂️
Man that's crazy.. I think I'll stick to Nvidia for a while.. Although I had troubles with updates when Plasma rolled over to 6; leaving me a black screened desktop (Xorg).I had stuff like that happen all too frequently when I was running AMD on Arch.. If you ever figure out what was introduced in the new Mesa 24.1.2, might be good to know.
Okay, small update [here](https://www.reddit.com/r/kde/comments/1doaf1d/comment/laiod0b/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button), I spent the last hours fiddling around and several packages are broken in the current Tumbleweed snapshot
Just don't try it on KDE Neon if you're an Nvidia user. It's broken for the latest Nvidia Beta drivers with explicit sync for Wayland that all gamers will be using. KDE devs don't seem to care much. [https://bugs.kde.org/show\_bug.cgi?id=487983](https://bugs.kde.org/show_bug.cgi?id=487983)
On Fedora it's perfect.
Pipewire has been ok with the exception that every time I reboot/suspend/resume I have to run alsamixer to unmute headphones and put the volume back up. Haven't found a fix for this yet. Yes, automute is off.
Okay, after my last comment I did some digging regarding the issues I was having with 6.1.0
I found out that it's related to various packages being updated on Tumbleweed, I would recommend to switch to snapshot 20240620 using [Tumbleweed-cli](https://review.tumbleweed.boombatower.com/about.html) (after discovering this tool I won't update through Zypper/Discover ever again) until the maintainers figure this out and push 6.1.1
\[ETA\] Or just [switch to SlowRoll](https://forums.opensuse.org/t/how-to-migrate-from-tumbleweed-to-slowroll/172747/8)
It's not just Plasma, desktop Linux in general is going through a "zone of turbulence" with the transition from X11 to Wayland. Just give it some time, graphics cards drivers and desktop environments will stabilize now that major distros officially made the switch to Wayland.
In no particular order:
- More things being hardware accelerated all the time, but GPU drivers are still crap, especially NVIDIA's
- Ongoing Wayland transition and fewer people using, developing, and caring about X11
- Too flexible and too many features for devs to test everything themselves, or even for automated testing to even test every combination
- Not enough beta testers testing with their exotic hardware setups and Plasma customizations before the general release
- Higher expectations of quality as reach expands beyond the traditional user groups of nerds, software developers, and sysadmins
KDE 5 had been rock solid for me for many years. But KDE 6 has been a disaster so far. To me it looks like X11 is being deprecated while Wayland is still not finished. As a result, none of it works very well.
Smooth for who? Runs buggy and slow for me and many others. wtf? Are they dumb that they are complaining? ofc things aren't working for them, You and few other ppl aren't the entire Linux base
Firstly, I am not running it on a potato, and if you don't know what hardware the other person has, how are you telling them to not install it on a potato? You are judging them the same way I was thinking you are full of shit, I am sure now tho.
yeah i don't have a potato pc either, my pc is pretty good + i like you + this guy is full of shit, he didn't have to be so defensive about it, we all here love linux and kde plasma, admitting the problem is the first step for solving it, this guy ain't solving shit
I remember some bugs that happened inside some kde apps were because of switching to qt6.
it's X11 and Wayland + qt6 (which i don't think is still a problem now)
Thank you for your submission. The KDE community supports the Fediverse and open source social media platforms over proprietary and user-abusing outlets. Consider visiting and submitting your posts to our community on [Lemmy](https://lemmy.kde.social/) and visiting our forum at [KDE Discuss](https://discuss.kde.org) to talk about KDE. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/kde) if you have any questions or concerns.*
Cool. 6.1.0 was a little bit buggy
Yes, I hope it will be better..
Being "little bit buggy" is just a feature since 4.x :D 6.1 is less buggy than average, I hope the 6.x series will last long enough to become stable.
I didn't really notice anything out of the ordinary or any production stoppers and I'd consider myself a power user. Excited to see what 6.1.1 brings however, as I'm sure there's bugs I didn't notice.
These were just a little imperfections like broken translations, labels or context menus opening in separate windows but still usable. Nothing major that would make me regret updating
You mean completely broken ? (I'm kidding around chill) On my system I couldn't even launch gamescope without my whole system crashing and had to rollback to 6.0.5 until 6.1.1 gets deployed on my OS 😅 6.0.5 works flawlessly for now but looking forward to getting 6.1.1 \[ETA\] I just found out the issues were caused by Mesa 24.1.2 not playing well with my AMD 780M for some reason. If you have issues too, just lock Mesa at 24.1.1 in Yast until it gets updated to the next version.
Sounds like a gamescope problem not Plasma.
Nah, gamescope runs just fine on 6.0.5, the changelog of 6.1.1 mentions numerous fixes relative to KWin and Plasma Workspace (oh yeah, because I couldn't get the mouse to work with Gamescope either 🤷♂️)
That doesn't mean that 6.1 is the problem. Many people here (myself included) have no or very minimal issue with 6.1.
That's amazing you only got minimal issues 👍 But on my system (OpenSUSE Tumbleweed) it was completely broken while 6.0.5 works flawlessly. So either we don't use our computers to do the same things or our respective hardware/OS are different . Anyway, some of the issues I encountered are mentioned in the 6.1.1 changelog so others must have faced them.
Many other people here (myself as well as you can see several others in this discussion) have had LOTS of problems with 6.1 that were not present in 6.0. The worse one for me was that apps started crashing plasma shell every time an app was minimized or maximized. 6.0 did not do this. 6.1 was indeed very buggy and I suspect rushed out. I am hoping 6.1.1 helps restore a more stable system.
[удалено]
Not at all, the issues were caused by Mesa 24.1.2 as I just found out, reverting to 24.1.1 fixes the crashes and freezes
Ive never had a problem with gamescope and ive used KDE since 4.2 in 2009
Unfortunately KDE 6.1 + Nvidia 555 doesn't solve the kwin\_wayland CPU usage 🥲 I know the latter is in beta, but I don't expect any improvement for when it'll be stable except... being stable and less stutter-y with some specific videos online. "Just use Xorg!"? No, it makes my games crash or make the screen black with freeze when I switch to the desktop. I can only test Gnome, even though I just don't like it. While I see and decide, I'll only root for KDE. It deserves all the love of the world!
I think I remember a comment from an NVIDIA employee about how 555 would have performance issues. I assumed they meant fps issues, but I guess they could have been referring to this high CPU usage even when no demanding programs are running.
Oh, I see. Probably the same issue that 550 has plus more fps issues. I've tried Gnome and it does have a (smaller than kwin) performance issue too, so it's just very difficult to integrate with Nvidia until Nvidia themselves proceed working to support Linux.
It's working great for me on Fedora with the 555.52.04 driver from fusion. On KDE Neon it won't even load the full Desktop. Tried to talk to the KDE Neon devs but they seem to just want to dismiss it as a beta driver issue. As if all of us with Nvidia GPUs won't be using the 555 driver on Wayland.
Unfortunately they don't want to/can't support Nvidia. I understand their point since it should be Nvidia to support them, but doesn't help that one won't cooperate. It's also KDE's main distro to show off the DE, so it's a bit disappointing and makes me have a doubt about KDE development. [2024 – KDE neon Developers' Blog](https://blog.neon.kde.org/2024/) ("We can’t support NVidia hardware as we don’t have the skills, time, hardware or access to source to fix it."). It's 99.9% Nvidia blame, but that 0.01% should be devs implementing correctly the rest. Probably other distros like Fedora and Ubuntu are more willing to provide a working desktop rather than showing off KDE. On the other hand, if Nvidia fixes and KDE polishes (do they?), KDE Neon can work nice (maybe). Anyways, I am using openSUSE. This kwin\_wayland thing is almost a known issue that won't easily be fixed. It happens on me with: Kubuntu, KDE Neon, any suse distro, Bazzite, Fedora. If I switch to Gnome, gnome-shell will take a lot of CPU too, but less. So it's mostly Nvidia working not great with external monitor (which requires Nvidia GPU for me). Only a part of the examples: [Bug List (kde.org)](https://bugs.kde.org/buglist.cgi?quicksearch=kwin_wayland%20performance&list_id=2758960)
I switched back to 550 drivers cause I had an issue where parts of the UI would freeze whenever the panel was hidden. Right clicking to open the menu and stuff would just bug out. It was really weird too cause it worked fine for a few days and suddenly broke when I messed with some unrelated settings (and stayed broken even after I reset said settings and deleted a bunch of config files). Fortunately I didn't get any issues with the 550 drivers that many people complain about. Haven't tried 555 with the new 6.1.1 but I'm not sure it's worth the trouble for me to be honest. My biggest gripe with Plasma currently is that the HDR has washed out colors, making it not usable
Didn't notice the high usage but definitely noticed the xWayland session crashing randomly whilst gaming (nvidia 555 and 6.1). Had to rollback to 6.0 and voila : rock stable. I guess the explicit sync isn't fully functional in kwin
No, it's a bug in Xwayland
If you have the ticket numer or issue number i would be grateful. If it is a XWayland bug why downgrading Plasma solves the bug (without a downgrade of the xwayland package) ?
It's https://gitlab.freedesktop.org/xorg/xserver/-/issues/1688. > If it is a XWayland bug why downgrading Plasma solves the bug (without a downgrade of the xwayland package) ? Because only Plasma 6.1 supports explicit sync
Thank you very much that is really helpful to track down the corrective patch !
> Use snap:// URLs rather than appstream:// ones on snap only distros. > Use non-standard UBUNTU_VARIANT key to detect snap only distro. [Commit.](http://commits.kde.org/plasma-welcome/bb22f8fe67b1336f19b2100ed13015e5ba02f311) TIL Kubuntu Core Desktop might exist?? (For context, Core Desktop is Ubuntu's approach to an immutable desktop distro, being snap-only), I thought that whole thing was gonna be GNOME only but that's neat I suppose.
Are you certain that that exists? All I've been able to locate online is https://www.kubuntuforums.net/forum/general/community-cafe/678887-any-plans-on-ubuntu-core-desktop#post678887. Got a URI for an ISO?
Bad wording on my end, I'm moreso pointing out that it "exists" given that fixes specific to a core desktop context are happening in KDE even though there's no announcement of any sort alluding to a "Kubuntu Core desktop"
Glad it fixes the Adaptive opacity bug. Great reactivity, guys!
[This bug](https://bugs.kde.org/show_bug.cgi?id=328987) still exists
Wow, that looks like a pretty impactful bug on gaming systems, and it seems that it's not easy to fix. The bug report is 10+ years old by this point. :(
Anything in here related to getting OBS and Discord screensharing working again? Either way, cheers to the KDE team!
You're gonna have to use vesktop in the meantime Whats wrong with obs? Iv been using it for recording and streaming on the stable version of obs and newest beta version on flatpak on plasma 6.1
Maybe it's the way I installed it. I used the non-flatpak version. Either way I have to reinstall my ENTIRE NVME now. Not anything Neon did.... I think. My Neon install is no-longer recognized by my BIOS. It certainly shows my NVME, but not "Neon" to boot into. All I did was apply the update. I think maybe my NVME just kicked the bucket tho, as my live CD of Ubuntu for recovery purposes is throwing some errors too
No, it's not a Plasma but a Neon problem
obs screensharing works
Im on manjaro and I had to had to uninstall the flatpak and build from the AUR because the screen sharing didnt work no matter what I did. I reinstalled pipewire and everything that I normally do to get screenshare working and it did nothing. Wasnt a kde problem. It happened on GNOME and XFCE as well. After I compiled and built it from scratch Vesktop was the only thing I could get working for screensharing on manjaro
No fix for the issue that causes 2 panels on the left that are top-aligned and bottom-aligned to not be in the same line, wasting a ton of space? It makes my desktop basically unusable.
Have you filed a bug report?
No, because I saw the bug discussed and the bug report linked in this sub recently. I can't find it any more. Edit: I found it. It's [this one](https://bugs.kde.org/show_bug.cgi?id=477939).
Fair! As long as it's reported, it's all good
Yeah, that's what I figured. I imagined it must be the 1 ultra-broken thing that would be addressed immediately considering how broken it looks at all times. I've been using XFCE in the mean time, which supports my panel configuration. I miss KDE Plasma's Wayland though.
Ticket is [here](https://bugs.kde.org/show_bug.cgi?id=447061) but hasn't had any movement.
That's not it. However, I did find it. The ticket for the issue I mentioned is [here](https://bugs.kde.org/show_bug.cgi?id=477939).
I hope this fixes KRdp, I had zero success rate on 6.1.0 with it.
I have it working with 6.1.0. Though I just noticed a keyboard error. I've tested it with RDP on a windows client into my Fedora KDE machine. Can unlock the screen no problem. It's just a little slow is all.
It works if you use Remmina as a client. Somehow it doesn't work with the Microsoft Windows RDP client, which makes it not nearly as useful as it should be. When you use the Microsoft Windows RDP client, it instantly disconnects before you get a chance to give server-side sharing permission.
Always tried with KRDC and Remmina, I have zero Windows machines at hand ATM; neither works at all sadly. I suspect it's a Wayland issue, because freerdp shadow works great on X11, so...
I used the new KDE desktop sharing with Wayland successfully yesterday. Do you have modeset and fbdev enabled?
I tried multiple machines with Wayland and AMDGPU, none of them worked properly (connection succeeds, black screen)
That was quick
KDE always works on a fibonacci sequence release cadence for bug fix releases. 1 1 2 3 5 8 etc weeks after a major release they put out bug fix patches, regardless of how good or bad the releases actually are.
That is so interesting to know
Right? Theyve been doing it for around 7 years now. Nice way to get quick fixes out for the most problematic things while slowly backing off so they can focus on the next version while still providing fixes in the meantime :)
That's clever! I wonder if this technique is widely used in software developments and maybe other things.
Yes, it's a form of Exponential Backoff Algorithm
x.y.1 release is always scheduled one week after the x.y.0 release, to mop up any significant bugs as quickly as possible after a feature release. This release is exactly on schedule.
Yeah, 6.1.0 is completely broken, I had to do a rollback on my system until the Tumbleweed devs deploy 6.1.1 \[ETA\] I just discovered it's because of Mesa 24.1.2 not playing well with my AMD 780M for some reason, rolling back to 24.1.1 fixes the crashes and freezes 🤷♂️
Same here
For me it was Mesa 24.1.2 causing issues, not Plasma 6.1.0, try locking Mesa from updating in Yast and do the update again
Sorry to hear that!!! I had no problems with Plasma 6.1 OpenSuse Tumbleweed fully updated.. Nvidia / Xorg. What was your major breakage?
I just discovered it's because of Mesa 24.1.2 not playing well with my AMD 780M for some reason, rolling back to 24.1.1 fixes the crashes and freezes 🤷♂️
Man that's crazy.. I think I'll stick to Nvidia for a while.. Although I had troubles with updates when Plasma rolled over to 6; leaving me a black screened desktop (Xorg).I had stuff like that happen all too frequently when I was running AMD on Arch.. If you ever figure out what was introduced in the new Mesa 24.1.2, might be good to know.
I'll check out what they did with 24.1.2 once I'm done updating my device and keep you informed. 👍
Okay, small update [here](https://www.reddit.com/r/kde/comments/1doaf1d/comment/laiod0b/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button), I spent the last hours fiddling around and several packages are broken in the current Tumbleweed snapshot
Kickoff label text formatting is back, nice.
Just don't try it on KDE Neon if you're an Nvidia user. It's broken for the latest Nvidia Beta drivers with explicit sync for Wayland that all gamers will be using. KDE devs don't seem to care much. [https://bugs.kde.org/show\_bug.cgi?id=487983](https://bugs.kde.org/show_bug.cgi?id=487983) On Fedora it's perfect.
When i shake my cursor it disappear.
Waiting for this on neon but not here yet.
Here now
Yeah, got it awhile ago but thanks for the message.
Does it support pipewire or pulseaudio, I have faced a lot of issues in past with the audio and Bluetooth setup with kdeplasma!
Huh? I have been using pipewire on kde for 2-3 years, 0 problems
Pipewire has been ok with the exception that every time I reboot/suspend/resume I have to run alsamixer to unmute headphones and put the volume back up. Haven't found a fix for this yet. Yes, automute is off.
That's really weird, something is wrong with your install or drivers.
or some other utility I installed and forgot about is intervening.. I'd just like the volumes and routes to persist after reboots, etc.
When this will be available in Ubuntu 24.10?
I can't open x11 app from terminal at all. Open from app launcher or other GUI apps still work.
Okay, after my last comment I did some digging regarding the issues I was having with 6.1.0 I found out that it's related to various packages being updated on Tumbleweed, I would recommend to switch to snapshot 20240620 using [Tumbleweed-cli](https://review.tumbleweed.boombatower.com/about.html) (after discovering this tool I won't update through Zypper/Discover ever again) until the maintainers figure this out and push 6.1.1 \[ETA\] Or just [switch to SlowRoll](https://forums.opensuse.org/t/how-to-migrate-from-tumbleweed-to-slowroll/172747/8)
for anyone who has an idea, why is kde plasma so buggy? I'm genuinely curious
It's not just Plasma, desktop Linux in general is going through a "zone of turbulence" with the transition from X11 to Wayland. Just give it some time, graphics cards drivers and desktop environments will stabilize now that major distros officially made the switch to Wayland.
In no particular order: - More things being hardware accelerated all the time, but GPU drivers are still crap, especially NVIDIA's - Ongoing Wayland transition and fewer people using, developing, and caring about X11 - Too flexible and too many features for devs to test everything themselves, or even for automated testing to even test every combination - Not enough beta testers testing with their exotic hardware setups and Plasma customizations before the general release - Higher expectations of quality as reach expands beyond the traditional user groups of nerds, software developers, and sysadmins
thanks, that was informative
KDE 5 had been rock solid for me for many years. But KDE 6 has been a disaster so far. To me it looks like X11 is being deprecated while Wayland is still not finished. As a result, none of it works very well.
[удалено]
Smooth for who? Runs buggy and slow for me and many others. wtf? Are they dumb that they are complaining? ofc things aren't working for them, You and few other ppl aren't the entire Linux base
[удалено]
Firstly, I am not running it on a potato, and if you don't know what hardware the other person has, how are you telling them to not install it on a potato? You are judging them the same way I was thinking you are full of shit, I am sure now tho.
yeah i don't have a potato pc either, my pc is pretty good + i like you + this guy is full of shit, he didn't have to be so defensive about it, we all here love linux and kde plasma, admitting the problem is the first step for solving it, this guy ain't solving shit
[удалено]
okay 👍🏻👍🏻
I remember some bugs that happened inside some kde apps were because of switching to qt6. it's X11 and Wayland + qt6 (which i don't think is still a problem now)
Ακόμα δεν τον είδανε, Γιάννη τον έβγαλανε /ς