After installing kde-plasma/plasma-workspace-6.0.90 and all the dependencies on the llvm profile. Starting kde on wayland and get the follwing result: 1 - Kwin start with a black screen 2 - After opening a app that trigger kwallet-pam, for exemple chromium, (also kwallet autounlock is broken requires password), plasmashell starts 3 - After a few seconds kde-plasma crashes with the following error: I have a Lenovo Legion 5 15ACH6H and this error can be reproduce both using the amd igpu or the nvidia dgpu (in dgpu mode) ```bash org.kde.startup: "kdeinit5_shutdown" QList() exited with code 255 startplasma-wayland: Shutting down... startplasmacompositor: Shutting down... startplasmacompositor: Done. ``` Launching of X11 even with SDDM on wayland mode (with kwin) everything works great.
Created attachment 894624 [details] emerge --info
Please always mention if you are using libcxx which is far from a stable or even standard configuration. There are major known issues with that already and I would consider it completely unsupported at this point.
(In reply to Andreas Sturmlechner from comment #2) > Please always mention if you are using libcxx which is far from a stable or > even standard configuration. > > There are major known issues with that already and I would consider it > completely unsupported at this point. Well but at least until version 6.0.5 was usable, the only problem with plasma wayland was the right click. Now plasmashell is complete broken. It possible for you to re add the 6.0.5 ebuilds, just to have a "stable" version to fallback to?
No, they were always under package.mask, by definition not anywhere near stable, and the existing issue is enough to consider it unusable.
Please continue working with upstream on that issue, thanks.
(In reply to Andreas Sturmlechner from comment #4) > No, they were always under package.mask, by definition not anywhere near > stable, and the existing issue is enough to consider it unusable. I understand my ideia is if would be possible to still have both 6.0.90 (6.1 beta) and 6.0.5 in the tree, until 6.1 full releases. (In reply to Andreas Sturmlechner from comment #5) > Please continue working with upstream on that issue, thanks. Ok I might update this bug when the bug upstream get resolved.
I decided to make some extensive testing and this was what I found. When using `MYCMAKEARGS="-DLIBCXX_TYPEINFO_COMPARISON_IMPLEMENTATION=2"` in `sys-libs/libcxx` and `kde-plasma/plasma-workspace` like is was done in BUG 923292, and didn't solve my problems. Today the BUG 933120 can be solved by the used of a patch send it by Sam (https://bugs.gentoo.org/933120#c9) and notice that my problem with plasma-workspace on kde was complety solved (also the broken kwallet autounlock). To be sure I recompiled `sys-libs/libcxx` and `kde-plasma/plasma-workspace` with the `MYCMAKEARGS="-DLIBCXX_TYPEINFO_COMPARISON_IMPLEMENTATION=2"` env and yes the issues is complety gone when using Sam patch. So this bug only happen if kwin is compiled without systemd support! *** This bug has been marked as a duplicate of bug 933120 ***
Gonna also report my findings to upstream
(In reply to Gonçalo Negrier Duarte from comment #7) > To be sure I recompiled `sys-libs/libcxx` and `kde-plasma/plasma-workspace` > with the `MYCMAKEARGS="-DLIBCXX_TYPEINFO_COMPARISON_IMPLEMENTATION=2"` env > and yes the issues is complety gone when using Sam patch. Small typo: without the `MYCMAKEARGS="-DLIBCXX_TYPEINFO_COMPARISON_IMPLEMENTATION=2"`...
