I can create new ones, or do mean edit existing ones? I’ll try it out now
1 Like
I can reassign existing ones to overwrite the old ones but can’t edit those ones directly
1 Like
That’s interesting. I reassigned a kwin command to open Dolphin. Worked flawlessly. Then I tried reassigning my terminal launch to open Dolphin, and that failed.
I’m on an other distro currently so the info might or might not be relevant, but reassigning existing shortcuts does seem a bit stubborn/buggy.
I was trying to reassign PrtScn to Spectacle’s Rectangular Region. It either completely ignored the new assignment, or did both actions (open rectangular, then on Esc open Spectacle default view as well). Then after trying again and again, it suddenly “just worked”.
Just in case… make sure you hit “Apply” on bottom right corner once you are done with assigning shortcuts.
Other issues I’ve had in case someone has also encountered them or solved them:
- Spectacle’s screenshots appear to be blurry
- Trying to set env variables for applications (through: RightClick > Edit Application > Application > Environment Variables) doesn’t seem to work
1 Like
Custom shortcuts are saved in a file, but not what they do/run. I guess they are in some dbus settings.
grep -C1 _launch $HOME/.config/kglobalshortcutsrcActually, the behavior I’ve seen, and has been consistent across distros, is different.
When I have set my shortcuts (in 5), Plasma will “remember” my last change (or last few), and “forget” the first ones. I have had to hit Apply after every change to make sure it sticks.
Is anyone here having any issues with the Plasma panel locking up and becoming unresponsive in Wayland + NVIDIA?
I’ve had that happen to me the first day of usage, not on Nvidia though (intel integrated).
I just restarted the plasma-shell and it hasn’t happened again:
( systemctl --user restart plasma-plasmashell )
Btw, as someone who absolutely adores KDE Plasma, I have to say… it’s definitely not there (at ready state) yet…
I’m having all kinds of issues and I’m not even on N0-vidia.
Spectacle is straight up unusable, flameshot is a tiny bit better but still has issues.
Scaling of all kinds of apps is all over the place.
Small lags and bugs here and there (eg the thing with shortcuts I mentioned above).
And from a quick glance on 6.0.3 change-log I didn’t see any of those addressed (could have missed it though, didn’t thoroughly read it all)
I have nvidia/KDE and I can tell you that the current state is so bad for me right now that I would have quit Linux and went back to windows had this been my first impression.
Yes I know I can log off and go to x11.
Definitely not a Wayland issue!
I’ve been using wayland for years, Plasma 5 wasn’t even close to that bad under wayland.
I just hope we don’t have to wait till Plasma 6.27 to get a stable environement 
Thanks! I didn’t notice that the procedure for restarting the plasmashell had changed! I was wondering why it wasn’t working anymore…
Anyway, I’ve been holding off on criticizing the Plasma 6 release for several reasons:
-
I’ve been using Plasma 6 on two of my computers. The first is a fresh install of EndeavourOS with Plasma 6 on a Surface Pro 8 tablet, which only has Intel integrated graphics. The second was a 2 1/2 year old install of EndeavourOS on an ASUS gaming laptop with an NVIDIA GTX 1060 GPU that I updated from Plasma 5.27 to Plasma 6. I’ve only had a few random Plasma shell crashes on the Intel tablet. I’ve had nothing but issues on the NVIDIA gaming laptop, which might be contributed to the fact that:
-
I finally saw the writing on the wall and decided to switch to Wayland on the NVIDIA gaming laptop; I’ve been using Wayland on the Intel tablet since Plasma 5.22. I’ve tried Wayland on NVIDIA several times in the past, but would always run back to Xorg when I ran into problems. This time I’m forcing myself to stick with it. I suspect that most of my issues are NVIDIA + Wayland specific, as I have had little to no problems on the Intel tablet.
-
The NVIDIA gaming laptop had over 2 1/2 years worth of Plasma 5 tweaks and related add-ons. I removed as many as I could remember before installing Plasma 6, but I kept on finding new ones after the fact. I also had a full GNOME desktop, plus configuration files left over from testing Cinnamon, XFCE, DDE, and Cosmic Alpha. Any of this stuff could have caused issues with Plasma 6 (or any other desktop…). So, I decided today to back up my personal data and do a clean install of EndeavourOS/Plasma 6 before making any further judgements.
-
I was around during the last major KDE transition, which was KDE 3.x to KDE 4.0 (KDE 4.0 to Plasma 5.0 was a minor transition). I was also around for the GNOME 2.x to GNOME 3.0 transition. The transition from Plasma 5.x to Plasma 6 has been the smoothest that I’ve seen!
I think there has been too many complaints from people who didn’t properly prepare their system for the update (by not removing Plasma 5 add-ons and tweaks), by people who were expecting Plasma 5 add-ons to still work on day one without a port, and by weird people who were expecting dead projects like Bismuth and Latte Dock to continue working on Plasma 6. I’m not one of those people…
1 Like
For the only machine(s), the Intel GPU based Surface Pro 4 and 8, that I used Plasma + Wayland religiously on since Plasma 5.22, and did a clean install of Plasma 6, I have had only minor stability issues. To me, Plasma 6 on that machine has been a rock solid release. Plasma 6 on NVIDIA + Wayland has been just as much as a PITA as Plasma 5 on NVIDIA + Wayland has been, and as GNOME 3/40 though 46 on NVIDIA + Wayland has been.
I can’t argue with that, I just don’t have the information you do.
I’ve only used Plasma since/after 5 (it’s been a decade btw… Damn, time flies!)
Before that I was using XFCE for a couple of years, before which was my long gone Windows days.
Again, I do really love KDE Plasma!
I’m just sad of not being able to bash Gnome in all conscience with Plasma in that state 
I actually tried gnome because I was tired of KDE’s issues.
Once I loaded up the desktop I had this sudden urge to throw up.
So now I am back on my broken KDE.
I know what you mean. On my work VM I just upgraded to Fedora 39 (we’re a RH shop, so RHEL or Fedora only on workstations, RHEL only on servers), and I am not a fan. Luckily I only need it once in a while, and mostly work on the servers that are 99% headless and CLI only.
Plasma 6.0.3 did not land yet in the EOS repo. I heard that the maintainer is on time-off.
Do we have an expected time of arrival for the .03 release?
I’ll give Plasma some time to stabilize a bit and then give it a look. I was pretty impressed with how lightweight you could set up on Plasma 5. It wound up becoming my default choice for older or lower resource computers.
It’s in testing now.
1 Like
I didn’t want to dismiss or diminish the issues you’re having. I just wanted to point out that I was not in the same boat. I also wanted to point out that, as far as major desktop releases are concerned, the Plasma 6 transition has been relatively (major) problem free. I think most of the issues that we are all having with Plasma 6 at the moment are just growing pains.
I also wanted to point out that the grass is not greener on the other side. GNOME is pretty, but it is a mess in its own right, especially when it comes to missing features and unsupported extensions. Windows 10 and 11 are just too invasive and are a pain to maintain, with each program having its own update mechanism instead of a having a centralized update repository. Using both GNOME and Windows in the past few days has made me appreciate the beauty and simplicity of KDE Plasma a lot more.
I completed my reinstall of EndeavourOS with Plasma 6 on my NVIDIA gaming laptop last night. I applied some NVIDIA + Wayland based kernel variables, environment variables, and systemd services, as outlined in the Arch NVIDIA wiki. The reinstall wiped away all of the old Plasma 5, GNOME, and other desktop related stuff. I also did a fresh install of Steam, some of my Steam games, and Warzone 2100. I’ve been playing with the Plasma 6 desktop and playing games all night using the Wayland session. I’m happy to say that my NVIDIA + Wayland session is a lot more stable! I also didn’t get any annoying flickering with any of the games tested so far.
The beauty of GNOME takes some getting used to. It’s kinda got a Tonka Toy/Lego Duplo block look and feel to it that seems to be appealing to GUI designers, but not very practical for day to day use. It definitely requires a lot of tweaks/extensions to make it palatable to the eyes and more usable. However, it seems that the GNOME development team/community are against tweaks, since the developers keep breaking them on every release and the community keeps bragging about how useful (yucky!) “vanilla” GNOME is.
I hate spending a lot of time tweaking my desktop and display manager only to have all of my work erased on the next minor release, which is why I gave up on GNOME. At least with Plasma 5, my tweaks/add-ons lasted for years! If the developers of the add-ons had moved a little quicker with porting to Plasma 6, I probably wouldn’t have had any issues with Plasma 6 either. I’m not complaining… at least it didn’t take months for the developers to port the add-ons I normal use to Plasma 6. All of them are available now, unlike what I had to go through with Dash to Dock on GNOME 40-46.
1 Like