I use latte dock, kvantum manager and different plasma widgets. I’m pretty sure they will be broken.
1 Like
Well sure … anything, like lattedock, that is abandoned/discontinued or simply incompatible with the new libraries due to a current lack of updates et al … will be broken.
Thats known and technically true for any software on your system.
( and has virtually nothing to do with wayland )
I suppose you can wait as long as hermitly possible to see if any of those things you ‘need’ get revitalized. But thats not exactly advisable either.
How sure are you that you actually ‘need’ any of those things?
In whatever case … such discussions are not for this thread.
3 Likes
7 posts were split to a new topic: Did something happen to the microsoft-office-web-jak
-
latte-dockis broken, although work is on the way to port it to Plasma 6. -
kvantumhas been upgraded toqt6, and all yourkvantumthemes will work just fine. You may however have to additionally installkvantum-qt5to getkvantumtheme support inqt5applications. -
Third-party widgets will most likely be broken, although some of them may in the meantime have been ported to Plasma 6. Best is to check their respective home page at store.kde.org.
2 Likes
The can also be found by right-clicking on the desktop or a panel, selecting “Add widgets”, then “Get new widgets”, then “Download new plasma widgets”. Once you’re upgraded to Plasma 6, only compatible widgets will show here.
2 Likes
KDE, X11.
Update mostly went well besides smaller annoyances like I don’t seem to be able to change default setting on log out screen and I can’t get rid of System Tray applet “Peek at Desktop”.
However, after update there were no input/output sources shown in volume applet, sound still worked, just no sources shown, and Pamac GUI was back to light theme even though Pamac-GTK3 is still installed.
While working on the audio sources my laptop decided to crash and restart. Upon restart input/output sources are back and Pamac GUI have dark theme.
Still have to look in to the log out settings and the Peek at desktop applet but that is not urgent.
That’s not a system tray entry; that’s a widget on your panel. You have to enter “Edit Mode” in order to remove that.
Thanks, I was going to say I tried that to, which I have. But now giving it a last attempt I found the delete button. It was just too easy, just hover over the widget.
1 Like
Got this warning upgrading from the 2023-10-15 iso:
[ALPM-SCRIPTLET] WARNING: The 'plymouth-encrypt' and 'sd-plymouth' hooks are depreciated. You should replace them with 'encrypt' and 'plymouth' hooks in your 'mkinitcpio.conf'. The 'lxdm-plymouth.service', 'lightdm-plymouth.service' and 'sddm-plymouth.service' systemd service files are no longer recommended. You should enable 'lxdm.service', 'lightdm.service' or 'sddm.service' instead.
As all went apparently fine, I can ignore it?
I also installed all LTS kernels:
[ALPM-SCRIPTLET] ==> WARNING: Deprecated option 'ALL_microcode' found. Update '/etc/mkinitcpio.d/linux510.preset' to use the 'microcode' hook instead.
Same for 4.19, 5.15 and 5.4, 6.1, and 6.6. and 6.9
edit ALL_microcode to: microcode ?
No.
You should remove the old hooks (and use new ones?) from /etc/mkinitcpio.conf (and/or /etc/mkinitcpio.conf.d/*.conf)
You should also get rid of any of the *dm-plymouth services and use the regular service.
No.
You should remove the ALL_microcode from those preset files.
The microcode hook should go in the mkinitcpio.conf like the ones removed above.
Thank you. I will try these options. Should I do that before or after updating from the 23-10-15 install? (I did not I manage to get up-to-date and running nvidia-390 from later installs. )
After you update to the max. The hook is in the newest mkinit version, older ones does know what to do with it. And you are currently 7 month behind.
1 Like
Tyvm. After, I run mkinitcpio -P ?
After you change hooks, yes.
I think I am back on track.
Default value on logout screen - Turns out Plasma 6 has a section ‘Session management’ in shortcuts where you can assign shortcuts for different defaults.
Then Breeze theme has problem with black screen on lock screen, might be fixed or there may be a corresponding Plasma 6 theme.
Is anyone else having issues now with podman? Since the last update I’m getting the following error message when trying to run any container: (Even a simple test container like:
podman run --rm fedora:latest
The error I’m getting is
Error: pasta failed with exit code 1:
Couldn’t set IPv6 route(s) in guest: No route to host
This seems like it was an issue a couple months ago that is similar:
Basically if I create the pod using the --net=pasta:-4 argument it seems to work (I took that from that closed issue). I’m going ahead and opening a ticket with podman as it looks like maybe the latest version once again has an incompatibility with pasta. I’ve been running these pods for almost 2 years now and this was the first time they have had an issue.
Just curious if anyone is experiencing similar issues with podman.
Fixed (workarounded?) in Some QT applications (okular, qucs-s) segfaulting under Wayland + GNOME 46 - #14 by medmedin
19 posts were merged into an existing topic: [Stable Update] 2024-05-29 - Kernels, Plasma 6.0.5, GNOME 46.2, Mesa