Yeah the icon in task manager is just the wayland w. I think this is a wayland protocol problem.
Pretty sure it is related to this issue https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/269.
It comes with X11, but defaults to Wayland.
Just updated my media PC to Plasma 6 and no issuesā¦well log in screen was messed up but tat was my fault for not change login screen theme to default.
Will there be a new iso ? Iām guessing with the current iso, if you install KDE, and in livecd, there will be a massive update to download?
(I asked in another Plasma thread too, sorry, but Iām looking to do a fresh install and wondering if I should wait)
Yes, notably better-inline-clock and all of the network/netspeed applets are not working at the moment. However, many of the native Plasma applets are noticeably improved.
@seija @d-air1 Thatās a long standing problem on wayland. From what I understand it has to do with app naming and a mismatch.
The easiest way to fix it is the following:
Right click the title bar of the app showing the wayland icon > select more actions > then select configure special application settings. On the popup, click add property and search for desktop file name. From there add the name of the .desktop file that wayland uses to launch that app. However, do not include the .desktop part of the file name. Click apply and close the app, then relaunch and it is usually fixed.
Itās a bit of a faff, but it usually works and the easiest thing to do until it gets fixed.
As already mentioned here, this is it:
But I took the test here, he wasnāt the culprit. I removed it and used it for a good few hours without it and even so, it reached 10.5 GB of use with almost nothing open.
The culprit was apparently the Wayland session itself. I logged into the X11 session and it was as it was on Plasma 5, usage didnāt exceed 3.3 GB, even with about 10 tabs open in Brave, Kate, Dolphin and Audacious also opened.
I donāt know if anyone has issues with this. I am experiencing blank/black login screens that appear to be related to display refresh rate with two displays connected.
With one display set to 120hz (LG C2) and the other set to 60hz (AVR, used only for 5.1 sound), I get a blank screen after logging into a Wayland session. With only the LG C2 connected at 120hz or with both connected and at 60hz, the login works. There were occasions where I got through the login, but all of the display configurations were reset to default. If I log in with only the LG C2 connected, I can then plug in the AVR and it will remember my settings and function as intended.
Thanks for the link. Exactly what I was looking for,
J.
I didnāt notice anything untoward on my Wayland laptop, but my X.org desktop had some issues
-
session switched to Wayland, breaking software. Not really a problem, just switch session back
-
custom shortcuts were broken. They were visible, but half missing, and didnāt work, had to delete them all and reimplement using ācustom commandsā instead.
-
ddcutil does not work anymore, without doing something to solve, various options presented here:
Thank you!
And tiling is shot to hell. Hooray.
Having switched to Wayland completely a while ago, switched all appearance settings to breeze defaults and upgradedā¦ man what a smooth experienceā¦ not a single thing is broken for meā¦ yay! 
Havenāt updated since nov 2023 but updating yesterday went smoothly. No major issues 
I have noticed the issue 2. as well (except that the shortcuts are still working in a X11 session).
So, how are we supposed to redefine our custom shortcuts now?
I had one break. I just defined it again as usual, and it works fine.
Well, I donāt know the commands I have bound to these shortcuts by heart. Hmmā¦ it seems I can find them in the .config/khotkeysrc file. Thatās weird I cannot access / edit them anymore through settings.
i dont know if itās just me but since the update to plasma 6 i noticed firefox and librewolf easily crashing on my end (i dont remember seeing them crashing back to plasma5), so i been using ungoogled chromium for now which apparently seems to be somewhat more stable, could be something related perhaps to nvidia and hardware acceleration ??
Iām using nvidia and have forced hardware acceleration in firefox, but havenāt had it crash yet.
I think Iāll give up on Plasma for a while. I donāt want to abandon Arch, so Iām going to go back to using Gnome or take a chance on the TWM that Iāve been putting off for so long.
Some other annoying bugs I identified:
-
Plasmashell gives random crashes, even without any application open. I didnāt observe anything unusual, just the Crashed Process Overview opening suddenly informing that there was a crash. Haruna Media Player was also crashing with a video, as this video opened in VLC, the problem was not with the video. It was a mere MP4 downloaded from Twitter.
-
I went for a walk, left the PC on. The sleep mode was off, only the screen off mode was activated. When I returned, I only had the mouse pointer, everything else on the desktop was gone, black screen. I had to restart the PC.
-
Dolphin doesnāt keep the panel displaying, every time I open it I have to press F9 to display the panel.
-
Notifications were appearing in the middle of the screen, instead of the right corner, as usual. This returned to normal after an update today.
-
There was an update to Plasmaās integration with the browser and it disappeared with some browser extensions! WTF!? In this case, it was an extension that had been installed manually (TWP - Translate Web Pages).