I was guessing that was the subject at hand, however there is no “fix around the corner” regarding those warnings so I just wanted to clarify.
Those two things are not related. Phil was replying to Frede’s post above that regarding pacman, not linux-firmware:
Oh, okay then. Guess I missed that one then.
I’ll get mi coat…
No worries. See why I was trying to clarify? 
1 Like
i fixed the missing manjaro settings manager icon by installing manjaro-settings-manager-knotifier (claims to be for plasma 5 but seems to work just fine on plasma 6) instead of manjaro-settings-manager-notifier
1 Like
Hmm, after updating to the newest KDE Plasma release, plasmashell seems to no longer open. (Edit 2!: Switching back to Manjaro testing temporarily fixed this issue for me.)
I can’t seem to find any bug reports for my issue on the KDE bugtracker, possibly this is a Manjaro issue?
(EDIT: Added, KDE Bug ID 505670 )
https://bugs.kde.org/show_bug.cgi?id=505670
Shortened KDE Backtrace, for those searching;
Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault.
0x00007ffff6a9dda2 in QSGSoftwareRenderableNode::update (this=0x55555928f170) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/scenegraph/adaptations/software/qsgsoftwarerenderablenode.cpp:151
151 if (!m_handle.simpleImageNode->texture()->hasAlphaChannel())
(gdb) backtrace
#0 0x00007ffff6a9dda2 in QSGSoftwareRenderableNode::update (this=0x55555928f170) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/scenegraph/adaptations/software/qsgsoftwarerenderablenode.cpp:151
#1 0x00007ffff6aad820 in QSGSoftwareRenderableNode::setTransform (this=0x55555928f170, transform=...) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/scenegraph/adaptations/software/qsgsoftwarerenderablenode.cpp:332
#2 QSGSoftwareRenderableNode::setTransform (this=0x55555928f170, transform=...) at /usr/src/debug/qt6-declarative/qtdeclarative/src/quick/scenegraph/adaptations/software/qsgsoftwarerenderablenode.cpp:327
mod edit to directly link to mentioned kde bug
Well, they suggested to run kcmshell6 qtquicksettings and put it back to automatic since for some reason your system runs on software render. Also upstream claims to have fixed the issue in Qt 6.3.1 for qtwebengine. KDE might need to adopt the same fix for plasma on software render. So I will suggest to bump the bug report once more to see what KDE developers might do to solve it.
2 Likes
Yup, that worked like a charm. I had no idea that setting was even hiding in there, and no clue how it happened. Thanks!
On Plasma 6.4 the wayland session will be the only one installed when the users does not manually specify kwin-x11.
With the recent split of kwin into kwin-wayland and kwin-x11, users running the old X11 session needs to manually install plasma-x11-session, or they will not be able to login.
Currently pacman is not able to figure out your personal setup, and it wouldn’t be ok to install plasma-x11-session and kwin-x11 for every one using Plasma.
5 Likes
Better make that a blockbuster of a chapter in the next Testing Updates and Stable Updates announcement threads.
But of course, it’s not going to stop the 100 or so new threads in the 24 hours after the update from people who can’t log into Plasma anymore because they couldn’t be bothered reading the announcements. 
4 Likes
Well, we will see what will happen when we only offer Wayland Only ISOs with Manjaro 25.1 series …
2 Likes
but manjaro-system can !
grep "DisplayServer" /etc/sddm.conf
DisplayServer=x11-user
1 Like
That may not work if one has the display server specified in a separate file under /etc/sddm.conf.d/.
grep -R "^DisplayServer.*x11" /etc/sddm.conf.d/
/etc/sddm.conf.d/user.conf:DisplayServer=x11
1 Like
Better still…
grep -R "^DisplayServer.*x11" /etc/sddm.conf*
This will check both /etc/sddm.conf and any file under /etc/sddm.conf.d/.
separate is best ?
- conf.d/*
- if not found, test etc/sddm.conf
RE-EDIT
if i have wayland in .conf.d/*.conf and x11 in et/sddm.conf(before .pacnew?) i use wayland and not x11
If the grep command is used as the polling mechanism, then we only need to test whether it has output or not. If yes, then it’s an X11 system, and if no, then it’s a Wayland system. 
Edit: I just saw your ninja edit.
Okay, then maybe test /etc/sddm.conf.d/* first, and then /etc/sddm.conf.
little confusion, do we need to install both plasma-x11-session and kwin-x11 to use X11 session going forward or would plasma-x11-session alone be good enough
kwin-x11 is a dependency of plasma-x11-session.
2 Likes