You are not logged in.
Yeah, I see now that might be the best option.
Offline
For me systemsettings is now running (thank you for the hint to disable qml caching). All other issues are minor issues - all applications I use are running...
Offline
For me systemsettings is now running (thank you for the hint to disable qml caching). All other issues are minor issues - all applications I use are running...
Yes that helped a lot for me too. But there are problems with other QT based software. For instance yuzu is not starting and the KDE settings are rendered in a wrong way. Some of the settings are still not accessible because there rendered outside of the window.
I understand the reasoning behind trying to test Qt 6.7 while also testing Plasma 6, but in practice, it's made it impossible to test Plasma 6 and I've reverted to Plasma 5 after being on 6 since the Alpha. The system settings modules being borked is definitely a problem, but I'm also seeing hangs in the window switcher and mouse events being offset by a certain amount in some applications. My assumption is that those are Qt, but who can tell.
It would seem to make a lot more sense to either stick on Qt 6.6 until Qt 6.7 stabilizes (at the very least until they fix whatever broke systemsettings) or maybe provide another set of Plasma packages that depends on Qt 6.7. Two betas at once is a lot of instability.
That would be my recommendation too.
It would be better to recompile everything with QT 6.6. In that situation lots of the people who already tested the beta 1 will go back to plasma 5... And they will stop reporting plasma 6 bugs.
Last edited by modnoob (2023-12-23 09:05:46)
Offline
Anybody else having trouble logging in after locking the session? When I put my laptop to sleep and wake it up again, instead of lockscreen I get a blank screen with just the mouse cursor. I have to hop to another tty and use loginctl to unlock the session. All was fine in Beta 1.
My Beta 1 experience was overall much better than Beta 2. I guess that a lot of it can be attributed to problems with Qt 6.7 beta.
Offline
Anybody else having trouble logging in after locking the session? When I put my laptop to sleep and wake it up again, instead of lockscreen I get a blank screen with just the mouse cursor. I have to hop to another tty and use loginctl to unlock the session. All was fine in Beta 1.
My Beta 1 experience was overall much better than Beta 2. I guess that a lot of it can be attributed to problems with Qt 6.7 beta.
Same for me....
The same problem for the lockscreen as with the logout screen. (eveything blank with cursor)
Offline
I can confirm here, too. It looks like a QT issue.
Offline
Anybody else having trouble logging in after locking the session? When I put my laptop to sleep and wake it up again, instead of lockscreen I get a blank screen with just the mouse cursor. I have to hop to another tty and use loginctl to unlock the session. All was fine in Beta 1.
My Beta 1 experience was overall much better than Beta 2. I guess that a lot of it can be attributed to problems with Qt 6.7 beta.
I assume you have an nvidia gpu. Known issue. I disabled the lockscreen as a not ideal workaround.
Offline
lock screen is fixed with plasma-integration 5.91.0-2
Offline
MadCat_X wrote:Anybody else having trouble logging in after locking the session? When I put my laptop to sleep and wake it up again, instead of lockscreen I get a blank screen with just the mouse cursor. I have to hop to another tty and use loginctl to unlock the session. All was fine in Beta 1.
My Beta 1 experience was overall much better than Beta 2. I guess that a lot of it can be attributed to problems with Qt 6.7 beta.
I assume you have an nvidia gpu. Known issue. I disabled the lockscreen as a not ideal workaround.
No, Intel HD4000.
Offline
Same for me....
The same problem for the lockscreen as with the logout screen. (eveything blank with cursor)
Here too with RX6900XT amdgpu
I will test tomorrow plasma-integration 5.91.0-2 and report back
edit: after reading the whole thread I saw there was posted a new thread and fixes are live
Last edited by ManuVice (2023-12-24 15:47:18)
Offline
The noise is a reminder of Neon_6 early days.
System Settings remains an issue and we Timeshifted twice for that reason. As of today, logout, restart and shutdown are working now. They were ending in a dead gray screen with no tty. Lock is ok (amd).
Our guess account (hostsblock_git) has an impressive amount of distortion, including Dolphin with the konsole at bottom.
We are back down the hill to KF5 for the first time.
Offline
Thanks for the backports. A lot of the pressing problems are now gone.
I do prefer the Qt6 wayland engine over the Qt5 wayland engine, a few bugs here and there have been fixed.
Here's hoping for about two weeks time when the next Qt beta drops.
Last edited by cmdrkotori2 (2023-12-24 03:07:28)
Offline
I used libreoffice on Saturday and noticed that there is a visual regression between beta 1 and beta 2.
This is present in both libreoffice fresh and still. fwiw I have never logged into gnome on either system.
Offline
I just installed LibreOffice 7.6.4.1 (libreoffice-fresh) via Pacman, not getting that issue.
Offline
My plasma-shell doesn't start.
plasma-plasmashell.service logs say this:
kde.plasmashell: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
kde.plasmashell: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
and then it crashes.
plasma-kactivitymanagerd on the other hand just crashes instantly on start without any other log messages.
KCrash: Application 'kactivitymanagerd' crashing... crashRecursionCounter = 2
Process 2974 (kactivitymanage) of user 1000 dumped core.
Stack trace of thread 6585:
#0 0x00007f2ca9cac83c n/a (libc.so.6 + 0x8e83c)
#1 0x00007f2ca9c5c668 raise (libc.so.6 + 0x3e668)
#2 0x00007f2cab13645f _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x645f)
#3 0x00007f2ca9c5c710 n/a (libc.so.6 + 0x3e710)
#4 0x00007f2ca4171fc5 _ZN5fcitx14FcitxQtWatcher5watchEv (libFcitx5Qt6DBusAddons.so.1 + 0x31fc5)
#5 0x00007f2ca629fd0e n/a (libfcitx5platforminputcontextplugin.so + 0x27d0e)
#6 0x00007f2ca97afc74 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x1afc74)
#7 0x00007f2caa97bf4b _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x17bf4b)
#8 0x00007f2ca9765488 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x165488)
#9 0x00007f2ca9765814 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x165814)
#10 0x00007f2ca99ad734 n/a (libQt6Core.so.6 + 0x3ad734)
#11 0x00007f2ca9020f69 n/a (libglib-2.0.so.0 + 0x59f69)
#12 0x00007f2ca907f367 n/a (libglib-2.0.so.0 + 0xb8367)
#13 0x00007f2ca901f162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#14 0x00007f2ca99ab164 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3ab164)
#15 0x00007f2ca976d67e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16d67e)
#16 0x00007f2ca97690b8 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x1690b8)
#17 0x0000561479c99367 n/a (kactivitymanagerd + 0xa367)
#18 0x00007f2ca9c45cd0 n/a (libc.so.6 + 0x27cd0)
#19 0x00007f2ca9c45d8a __libc_start_main (libc.so.6 + 0x27d8a)
#20 0x0000561479c99455 n/a (kactivitymanagerd + 0xa455)
Stack trace of thread 6589:
#0 0x00007f2ca9d20f6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007f2ca907f2b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2 0x00007f2ca901f162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3 0x00007f2ca99ab164 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3ab164)
#4 0x00007f2ca976d67e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16d67e)
#5 0x00007f2ca9853a3f _ZN7QThread4execEv (libQt6Core.so.6 + 0x253a3f)
#6 0x00007f2caa77613f n/a (libQt6DBus.so.6 + 0x3113f)
#7 0x00007f2ca98d4ae3 n/a (libQt6Core.so.6 + 0x2d4ae3)
#8 0x00007f2ca9caa9eb n/a (libc.so.6 + 0x8c9eb)
#9 0x00007f2ca9d2e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 6590:
#0 0x00007f2ca9d20f6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007f2ca6334a68 n/a (libQt6WaylandClient.so.6 + 0x70a68)
#2 0x00007f2ca98d4ae3 n/a (libQt6Core.so.6 + 0x2d4ae3)
#3 0x00007f2ca9caa9eb n/a (libc.so.6 + 0x8c9eb)
#4 0x00007f2ca9d2e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 6603:
#0 0x00007f2ca9ca74ae n/a (libc.so.6 + 0x894ae)
#1 0x00007f2ca9ca9d40 pthread_cond_wait (libc.so.6 + 0x8bd40)
#2 0x00007f2c90d1385c n/a (radeonsi_dri.so + 0x11385c)
#3 0x00007f2c90d0ab8c n/a (radeonsi_dri.so + 0x10ab8c)
#4 0x00007f2ca9caa9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007f2ca9d2e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 6602:
#0 0x00007f2ca9ca74ae n/a (libc.so.6 + 0x894ae)
#1 0x00007f2ca9ca9d40 pthread_cond_wait (libc.so.6 + 0x8bd40)
#2 0x00007f2c90d1385c n/a (radeonsi_dri.so + 0x11385c)
#3 0x00007f2c90d0ab8c n/a (radeonsi_dri.so + 0x10ab8c)
#4 0x00007f2ca9caa9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007f2ca9d2e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 6601:
#0 0x00007f2ca9ca74ae n/a (libc.so.6 + 0x894ae)
#1 0x00007f2ca9ca9d40 pthread_cond_wait (libc.so.6 + 0x8bd40)
#2 0x00007f2c90d1385c n/a (radeonsi_dri.so + 0x11385c)
#3 0x00007f2c90d0ab8c n/a (radeonsi_dri.so + 0x10ab8c)
#4 0x00007f2ca9caa9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007f2ca9d2e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 6614:
#0 0x00007f2ca9d20f6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007f2ca907f2b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2 0x00007f2ca901f162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3 0x00007f2ca99ab164 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3ab164)
#4 0x00007f2ca976d67e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16d67e)
#5 0x00007f2ca9853a3f _ZN7QThread4execEv (libQt6Core.so.6 + 0x253a3f)
#6 0x0000561479c9b684 n/a (kactivitymanagerd + 0xc684)
#7 0x00007f2ca98d4ae3 n/a (libQt6Core.so.6 + 0x2d4ae3)
#8 0x00007f2ca9caa9eb n/a (libc.so.6 + 0x8c9eb)
#9 0x00007f2ca9d2e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 6600:
#0 0x00007f2ca9ca74ae n/a (libc.so.6 + 0x894ae)
#1 0x00007f2ca9ca9d40 pthread_cond_wait (libc.so.6 + 0x8bd40)
#2 0x00007f2c90d1385c n/a (radeonsi_dri.so + 0x11385c)
#3 0x00007f2c90d0ab8c n/a (radeonsi_dri.so + 0x10ab8c)
#4 0x00007f2ca9caa9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007f2ca9d2e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 6616:
#0 0x00007f2ca9d20f6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007f2ca907f2b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2 0x00007f2ca901f162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3 0x00007f2ca99ab164 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3ab164)
#4 0x00007f2ca976d67e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16d67e)
#5 0x00007f2ca9853a3f _ZN7QThread4execEv (libQt6Core.so.6 + 0x253a3f)
#6 0x0000561479c9fab4 n/a (kactivitymanagerd + 0x10ab4)
#7 0x00007f2ca98d4ae3 n/a (libQt6Core.so.6 + 0x2d4ae3)
#8 0x00007f2ca9caa9eb n/a (libc.so.6 + 0x8c9eb)
#9 0x00007f2ca9d2e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 6591:
#0 0x00007f2ca9d20f6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007f2ca6334a68 n/a (libQt6WaylandClient.so.6 + 0x70a68)
#2 0x00007f2ca98d4ae3 n/a (libQt6Core.so.6 + 0x2d4ae3)
#3 0x00007f2ca9caa9eb n/a (libc.so.6 + 0x8c9eb)
#4 0x00007f2ca9d2e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 6617:
#0 0x00007f2ca9d20f6f __poll (libc.so.6 + 0x102f6f)
#1 0x00007f2ca907f2b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2 0x00007f2ca901f162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3 0x00007f2ca99ab164 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3ab164)
#4 0x00007f2ca976d67e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x16d67e)
#5 0x00007f2ca9853a3f _ZN7QThread4execEv (libQt6Core.so.6 + 0x253a3f)
#6 0x0000561479c99cdf n/a (kactivitymanagerd + 0xacdf)
#7 0x00007f2ca98d4ae3 n/a (libQt6Core.so.6 + 0x2d4ae3)
#8 0x00007f2ca9caa9eb n/a (libc.so.6 + 0x8c9eb)
#9 0x00007f2ca9d2e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 6605:
#0 0x00007f2ca9ca74ae n/a (libc.so.6 + 0x894ae)
#1 0x00007f2ca9ca9d40 pthread_cond_wait (libc.so.6 + 0x8bd40)
#2 0x00007f2c90d1385c n/a (radeonsi_dri.so + 0x11385c)
#3 0x00007f2c90d0ab8c n/a (radeonsi_dri.so + 0x10ab8c)
#4 0x00007f2ca9caa9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007f2ca9d2e7cc n/a (libc.so.6 + 0x1107cc)
Stack trace of thread 6604:
#0 0x00007f2ca9ca74ae n/a (libc.so.6 + 0x894ae)
#1 0x00007f2ca9ca9d40 pthread_cond_wait (libc.so.6 + 0x8bd40)
#2 0x00007f2c90d1385c n/a (radeonsi_dri.so + 0x11385c)
#3 0x00007f2c90d0ab8c n/a (radeonsi_dri.so + 0x10ab8c)
#4 0x00007f2ca9caa9eb n/a (libc.so.6 + 0x8c9eb)
#5 0x00007f2ca9d2e7cc n/a (libc.so.6 + 0x1107cc)
ELF object binary architecture: AMD x86-64
I didn't have this issue on beta1. I have kactivitymanagerd 5.91.0-2 installed from kde-unstable.
Last edited by Firecatmon (2023-12-26 02:26:30)
Offline
We did not pay attention to the given solution on post# 98 , but tweaking home.conf fixes the systemsettings module's issue. Thanks.
Few minor issues remain. Libreoffice-fresh is ok here too. BTW, Fedora 40 did not switch to beta 2, they stick to beta one.
Operating System: Arch Linux
KDE Plasma Version: 5.91.0
KDE Frameworks Version: 5.247.0
Qt Version: 6.7.0
Kernel Version: 6.7.0-rc7-1-mainline (64-bit)
Graphics Platform: Wayland
Offline
I just installed LibreOffice 7.6.4.1 (libreoffice-fresh) via Pacman, not getting that issue.
Right, I had GTK_USE_PORTAL=1 in my environment. Removing it fixed libreoffice.
Sorry for the false alarm.
Offline
I didn't have this issue on beta1. I have kactivitymanagerd 5.91.0-2 installed from kde-unstable.
You have to rebuild fcitx5-qt yourself against Qt 6.7
Offline
Firecatmon wrote:I didn't have this issue on beta1. I have kactivitymanagerd 5.91.0-2 installed from kde-unstable.
You have to rebuild fcitx5-qt yourself against Qt 6.7
Or you can unset QT_IM_MODULE, select fcitx5 as the virtual keyboard (i.e. Wayland IME) in systemsettings, and mask /etc/xdg/autostart/org.fcitx.Fcitx5.desktop.
https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland
Last edited by genericity (2023-12-27 03:15:53)
Offline
So for now, it seems my biggest issue is with the desktops disappearing - like, the background containment. The wallpaper turns black and I can no longer get a right-click menu from the desktop. Cursor is fine, windows and panels themselves are fine. It happens when resuming from sleep, or power settings turning off the displays for inactivity.
Offline
Not trying to blame anyone, but I still want to throw my opinion into the ring that I think it was a bad decision to roll out Qt 6.7 beta and Plasma 6.0 beta 2 at the same time.
Especially as, at least at the time of writing, Qt 6.7 (proposed release date: 2024/03/24)is supposed to be released half a month after Plasma 6 (proposed release date: 2024/02/28).
So what's the plan here? Release Plasma 6 without proper testing?
(Proper testing would be to test it against Qt 6.6, as that is what will very likely be in the main repo at the time of release)
Offline
I was able to get around the QML modules acting up by making the following change until the bug with Qt 6.7.0b1 is fixed:
❯ cat ~/.config/environment.d/envvars.conf QML_DISABLE_DISK_CACHE=1
\
Thanks for this tip! My 6.0 Beta 2 is mostly operational now that I can actually use the system settings.
Offline
@foxcm2000 Thanks for that quote. It worked. While the content strangely aligned (looks like the top was cut), at least I can see the settings pages.
Offline
Not trying to blame anyone, but I still want to throw my opinion into the ring that I think it was a bad decision to roll out Qt 6.7 beta and Plasma 6.0 beta 2 at the same time.
Especially as, at least at the time of writing, Qt 6.7 (proposed release date: 2024/03/24)is supposed to be released half a month after Plasma 6 (proposed release date: 2024/02/28).
So what's the plan here? Release Plasma 6 without proper testing?
(Proper testing would be to test it against Qt 6.6, as that is what will very likely be in the main repo at the time of release)
Qt6.6 is a short term support release ending soon. Qt6.7 is the next LTS and there will be no plasma 6 LTS without it. We do respect their decision, because it has to be tested.
For the rest, Qt 6.7 is responsablible for the majority of issues. Fedora Rawhide got beta 2 with Qt 6.6.1 and there is no bug at all on both accounts even with Linux-next as the default kernel. We are glad to see that the given solution for systemsettings helped everyone.
Operating System: Fedora Linux 40
KDE Plasma Version: 5.91.0
KDE Frameworks Version: 5.247.0
Qt Version: 6.6.1
Kernel Version: 6.7.0-0.rc7.20231226gitfbafc3e621c3.56.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Offline
One additional bug at my system: I cannot add applications to favorites. Right click on the menue item has no member "add to favorites". Is that only at my system?
Offline