You are not logged in.
I just installed the latest KF6 updates and things immediately exploded like a nuke. Wayland appears to be completely broken. To get SDDM to start, I had to revert to X11 in its config. The same goes for an attempt to start KDE Wayland session - I get a few seconds of a black screen and then get dropped back to SDDM. X11 session, is, unfortunately, broken too. There are no window decorations and a notification about KWin having crashed multiple times. NetworkManager Plasma Widget also reports an error, complaining about a missing symbol somewhere. Yakuake displays an error message instead of console.
RC1 isn't fully updated yet in kde-testing, that's why your system is broken.
Offline
MadCat_X wrote:I just installed the latest KF6 updates and things immediately exploded like a nuke. Wayland appears to be completely broken. To get SDDM to start, I had to revert to X11 in its config. The same goes for an attempt to start KDE Wayland session - I get a few seconds of a black screen and then get dropped back to SDDM. X11 session, is, unfortunately, broken too. There are no window decorations and a notification about KWin having crashed multiple times. NetworkManager Plasma Widget also reports an error, complaining about a missing symbol somewhere. Yakuake displays an error message instead of console.
RC1 isn't fully updated yet in kde-testing, that's why your system is broken.
RC1 does not seem to be in KDE-Unstable at all. What is available is the latest update of KF6 libraries. With Plasma 5 it was possible to update KF5 and Plasma 5 independently as long as minimum requirements were met. That's why I'm surprised that things broke so catastrophically.
Offline
That's why I'm surprised that things broke so catastrophically.
You can downgrade back to yesterday's packages by pointing to yesterday's date of package archives right before "Include mirrorlist" line for kde-unstable and running pacman -Syuu
[kde-unstable]
Server = https://archive.archlinux.org/repos/2024/01/09/$repo/os/$arch
Include = /etc/pacman.d/mirrorlist
Last edited by MacTavishAO (2024-01-10 22:17:04)
Offline
It looks like the latest KF6 introduced some kind of binary incompatibility and everything needs to get rebuilt against it, including the KDE Apps suite. Hopefully this will get sorted out in a few hours.
Offline
I have updated just now, and it seems to be at least usable, i.e., sddm works, and I can boot just fine into KDE plasma.
however, a few things I have noticed personally are:
1. applications look weird (systemsettings, discover, etc.)
2. systemsettings still doesn't work, without disabling qml disk cache (and even that has weird alignment issues)
3. a lot of symbol lookup crashes with applications including konsole and dolphin, i.e., basically unusable
4. KDE connect daemon crashes and does not seem to work, and its tray entry is not supported for plasma 6
5. cannot set wallpaper, empty settings page (even after using the workaround)
Last edited by kj (2024-01-11 09:09:16)
Offline
The next batch of updates fixed the SDDM Wayland mode and I can log. I guess we now have to wait until all the KDE Apps get rebuilt.
Offline
I have no idea if this is connected to this particular issue, or if I should make a new thread, but seeing as the Qt bugs are being discussed here as well, I thought it better to try here rather than opening a new thread right away.
Ever since update to the kde-unstable repo, Calibre is not working - symbol lookup issue with Qt. Please let me know if I should make this into a separate thread, or if this is indeed related.
$ calibre
Failed to import PyQt module: PyQt6.QtWidgets with error: /usr/lib/python3.11/site-packages/PyQt6/QtGui.abi3.so: undefined symbol: _ZN5QFont11tagToStringEj, version Qt_6
Traceback (most recent call last):
File "/usr/bin/calibre", line 21, in <module>
sys.exit(calibre())
^^^^^^^^^
File "/usr/lib/calibre/calibre/gui_launch.py", line 72, in calibre
from calibre.gui2.main import main
File "/usr/lib/calibre/calibre/gui2/__init__.py", line 13, in <module>
from qt.core import (
ImportError: cannot import name 'QApplication' from 'qt.core' (/usr/lib/calibre/qt/core.py)
Offline
Better. Konsole (and a bunch of other apps) still need a rebuild. But Konsole is a blocker for me.
Offline
Better. Konsole (and a bunch of other apps) still need a rebuild. But Konsole is a blocker for me.
You can always login to a tty and install another terminal for now such as xterm or terminator.
Offline
I have no idea if this is connected to this particular issue, or if I should make a new thread, but seeing as the Qt bugs are being discussed here as well, I thought it better to try here rather than opening a new thread right away.
Ever since update to the kde-unstable repo, Calibre is not working - symbol lookup issue with Qt. Please let me know if I should make this into a separate thread, or if this is indeed related.
$ calibre Failed to import PyQt module: PyQt6.QtWidgets with error: /usr/lib/python3.11/site-packages/PyQt6/QtGui.abi3.so: undefined symbol: _ZN5QFont11tagToStringEj, version Qt_6 Traceback (most recent call last): File "/usr/bin/calibre", line 21, in <module> sys.exit(calibre()) ^^^^^^^^^ File "/usr/lib/calibre/calibre/gui_launch.py", line 72, in calibre from calibre.gui2.main import main File "/usr/lib/calibre/calibre/gui2/__init__.py", line 13, in <module> from qt.core import ( ImportError: cannot import name 'QApplication' from 'qt.core' (/usr/lib/calibre/qt/core.py)
PyQt most likely needs a rebuild against Qt 6.7 which you get from KDE-Unstable. Since KDE-Unstable doesn't ship PyQt, you're stuck with the version from extra which is built against Qt 6.6.1. There are many more applications that are broken in a similar fashion, qt6ct being the most annoying one for me.
QT 6.7 Beta 2 is due for release today, hopefully they'll at least fix the QML issues.
Offline
Better. Konsole (and a bunch of other apps) still need a rebuild. But Konsole is a blocker for me.
Rebuilding Konsole was, fortunately, quite trivial for me.
You can grab the repo source from here https://gitlab.archlinux.org/archlinux/ … onsole.git, switch branch to kde-unstable and just run "makepkg -cf".
Offline
DebauchedSloth wrote:Better. Konsole (and a bunch of other apps) still need a rebuild. But Konsole is a blocker for me.
Rebuilding Konsole was, fortunately, quite trivial for me.
You can grab the repo source from here https://gitlab.archlinux.org/archlinux/ … onsole.git, switch branch to kde-unstable and just run "makepkg -cf".
Lovely! That worked like a charm. Thanks!
Offline
The one application I cannot get to work even after a rebuild from chroot is Okular. It attempts to start but quickly bails with "kf.coreaddons: "Could not find plugin okularpart" error message in the console. The "okularpart.so" lbrary does exist, it seems to be in the right place and linked against the correct libraries (all KF6, Qt6). Any ideas?
Offline
I can confirm
Offline
The reason for this behavior seems to be this:
KPluginMetadataPrivate from KCoreAddons has a static method "pluginLoaderForPath()". When Okular shell attempts to load the "okularpart" plugin, it creates KPlugínMetadata object by passing "okularpart" string literal to the constructor. This eventually leads to the "pluginLoaderForPath()" method to get called. The method sees the "okularpart" input as a relative path and converts it to an absolute path by prepending the output of "QCoreApplication::applicationDirPath()". This happens to be "/usr/bin" so the loader looks for "okularpart" on path "/usr/bin/okularpart.so". That is the wrong path, the correct path should be "/usr/lib/qt6/plugins/kf6/parts/okularpart.so". That is the immediate reason for Okular not working. A better question is why is the plugin loader using an incorrect path.
EDIT:
FWIW, this highly suspicious patch works around the problem and I can launch Okular again
diff --git a/shell/shell.cpp b/shell/shell.cpp
index 0a006d5ca..cf0d57177 100644
--- a/shell/shell.cpp
+++ b/shell/shell.cpp
@@ -183,6 +183,25 @@ private:
QWidget *m_dumbTitleWidget = nullptr;
};
+static KPluginFactory::Result<KPluginFactory> findOkularPart()
+{
+ auto result = KPluginFactory::loadFactory(KPluginMetaData(QStringLiteral("okularpart")));
+ if (result) {
+ return result;
+ } else {
+ auto metadatas = KPluginMetaData::findPlugins(
+ QStringLiteral("kf6/parts"),
+ [](const auto &md) { return md.name() == QStringLiteral("Okular"); }
+ );
+
+ if (metadatas.isEmpty()) {
+ return result;
+ }
+
+ return KPluginFactory::loadFactory(metadatas.at(0));
+ }
+}
+
Shell::Shell(const QString &serializedOptions)
: KParts::MainWindow()
, m_menuBarWasShown(true)
@@ -201,7 +220,7 @@ Shell::Shell(const QString &serializedOptions)
// name which is a bad idea usually.. but it's alright in this
// case since our Part is made for this Shell
- const auto result = KPluginFactory::loadFactory(KPluginMetaData(QStringLiteral("okularpart")));
+ const auto result = findOkularPart();
if (!result) {
// if we couldn't find our Part, we exit since the Shell by
Last edited by MadCat_X (2024-01-11 21:23:25)
Offline
Having patched Okular I noticed another major issue. I cannot see the mouse cursor when my external screen is attached. I can still move the mouse and see things like bouncing launch notifications but not the cursor itself. When I disconnect the external screen (DP), the mouse cursor reappears.
Offline
EDITED:
My quick and dirty solution is to put a symlink to /usr/lib/qt6/plugins/kf6/parts/okularpart.so in /usr/bin/. So no new build is needed.
EDITEDIT:
No longer neccessary - okular is updated and working now.
I already have a text file where such temporary fixings are noted so that I can remove them by time.
Last edited by df8oe (2024-01-12 11:47:16)
Offline
Having patched Okular I noticed another major issue. I cannot see the mouse cursor when my external screen is attached. I can still move the mouse and see things like bouncing launch notifications but not the cursor itself. When I disconnect the external screen (DP), the mouse cursor reappears.
Switching to x11 worked for me.
Another idea: https://bugs.kde.org/show_bug.cgi?id=479583#c12
Offline
MadCat_X wrote:Having patched Okular I noticed another major issue. I cannot see the mouse cursor when my external screen is attached. I can still move the mouse and see things like bouncing launch notifications but not the cursor itself. When I disconnect the external screen (DP), the mouse cursor reappears.
Switching to x11 worked for me.
Another idea: https://bugs.kde.org/show_bug.cgi?id=479583#c12
The suggested patch fixes the problem but a trivial backport is needed for it to apply cleanly on KWin 5.92.0. https://pastebin.com/ykhzZZdB
Offline
I've been using RC1 for a few hours on Wayland and I have to say that beyond a couple of small crashes and some inconsistency, the desktop and applications look very solid for the moment. The memory consumption is a bit higher than in Plasma 5, but otherwise just the experience has been really good.
The only problems I've encountered have nothing to do with Plasma, and have to do with some programs I use regularly running on Wayland, such as shortcuts in OBS not working, SMPlayer not running natively yet, and problems in applications that capture the desktop as SimpleScreenRecorder doesn't work unfortunately. I think for the time being I will keep using X11 session.
Excuse my poor English.
Offline
mparillo wrote:MadCat_X wrote:I cannot see the mouse cursor when my external screen is attached. I can still move the mouse and see things like bouncing launch notifications but not the cursor itself. When I disconnect the external screen (DP), the mouse cursor reappears.
Switching to x11 worked for me.
Another idea: https://bugs.kde.org/show_bug.cgi?id=479583#c12The suggested patch fixes the problem but a trivial backport is needed for it to apply cleanly on KWin 5.92.0. https://pastebin.com/ykhzZZdB
A patch would be really nice. Not having the mouse visible - on all Intel GPUs as it seems - is a complete showstopper and the bug catches a lot of duplicates on the tracker too.
Alas the bug was introduced one day before the RC1 freeze and the fix just missed it.
Last edited by Schlaefer01 (2024-01-12 17:44:27)
Online
MadCat_X wrote:mparillo wrote:Switching to x11 worked for me.
Another idea: https://bugs.kde.org/show_bug.cgi?id=479583#c12The suggested patch fixes the problem but a trivial backport is needed for it to apply cleanly on KWin 5.92.0. https://pastebin.com/ykhzZZdB
A patch would be really nice. Not having the mouse visible - on all Intel GPUs as it seems - is a complete showstopper and the bug catches a lot of duplicates on the tracker too.
Alas the bug was introduced one day before the RC1 freeze and the fix just missed it.
If you know how to build Arch Packages, you can grab the patch on pasebin I linked and rebuild KWin with it. That should fix the problem.
Offline
If you know how to build Arch Packages, you can grab the patch on pasebin I linked and rebuild KWin with it. That should fix the problem.
I tried but something wasn't working (on my end?). I ran into compile errors even building the unpatched KWin version. ... oooh, just while I'm writing this I realize I probably forgot to checkout kde-unstable *slaps forehead*. Yeah, let me give that another run.
[edit]
Yep, forgot to check out the kde-unstable branch. Used the patch you provided: Works - Thanks. Nonetheless having an official, updated build for the broader public would probably be beneficial.
Last edited by Schlaefer01 (2024-01-12 19:23:35)
Online
Has anyone noticed "Find in page" (Ctrl-F) no longer appearing in KHelpCenter?
Offline
I recompiled every package in kde-unstable repo against QT 6.6 instead of QT 6.7 Beta. This way QML_DISABLE_DISK_CACHE is unneeded to have somewhat functioning system. Building against QT6.6 fixes System Settings entirely, dolphin and konsole plugins respect your customisations, window previews work as expected and applications can be added to favourites and application launcher can be resized. There are probably more things it fixes as a result but these bugs were only ones grinding my gears. If you want to use Plasma 6 beta with QT6.6 add code block below to pacman.conf before kde-unstable:
[kde-unstable-qt6-6]
Server = https://github.com/MacTavishAO/arch-kde-unstable-qt6.6/raw/main
SigLevel = PackageOptional
Use "pacman -Sl kde-unstable | awk '/installed/ {print $2}' | sudo pacman -Syu -" to reinstall all packages installed from kde-unstable. Since QT6.6 repo is before kde-unstable, it should download and install those packages from QT6.6 rebuild repo. Having done that, disable or comment out real kde-unstable from pacman.conf and use "pacman -Qq | grep ^qt6- | sudo pacman -Syu" so you downgrade qt6-* packages back to 6.6 found in extra repo.
Last edited by MacTavishAO (2024-01-12 22:45:56)
Offline