https://bugs.kde.org/show_bug.cgi?id=455648
Hans Meine <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Resolution|DOWNSTREAM |--- Ever confirmed|0 |1 Status|RESOLVED |REOPENED --- Comment #2 from Hans Meine <[email protected]> --- I have the same problem, and I only found out when debugging why Plasma does not work properly since I upgraded Kubuntu to 22.04. (My original problem is that I do not get a dock or desktop background; krunner works.) The problem seems to be related to the proprietary NVidia driver (which I need for work); if I switch to Nouveau, Plasma works. Now I found some reports online that suggested this could be due to a broken multi-monitor setup – I guess if Plasma believed there was more than one screen, that could explain what I am seeing. Hence, I was trying to look into the configuration and found a suspiciously uninteresting display configuration control panel (that only allows to set a zoom scale). When I try running `kcmshell5 kscreen`, I am getting kf.coreaddons: "Could not load plugin from kcm_kscreen: The shared library was not found." kf.kirigami: Warning: Theme implementations should use Kirigami.BasicThemeDefinition for its root item kf.kirigami: Failed to find a Kirigami platform plugin file:///usr/share/kpackage/kcms/kcm_kscreen/contents/ui/Screen.qml:39: TypeError: Value is null and could not be converted to an object qt.qpa.xcb: QXcbConnection: XCB error: 148 (Unknown), sequence: 190, resource id: 0, major code: 140 (Unknown), minor code: 20 Just running `ldd` on kcm_kscreen.so, though, does not reveal any problems. What's more, running strace on the above command shows that it does seem to load the DLL *after* giving the error message? statx(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kscreen", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffcb3c5b4e0) = -1 ENOENT (No such file or directory) statx(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kscreen.so", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffcb3c5b4e0) = -1 ENOENT (No such file or directory) statx(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/qt5/plugins/libkcm_kscreen", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffcb3c5b4e0) = -1 ENOENT (No such file or directory) statx(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/qt5/plugins/libkcm_kscreen.so", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffcb3c5b4e0) = -1 ENOENT (No such file or directory) statx(AT_FDCWD, "/usr/bin/kcm_kscreen", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffcb3c5b4e0) = -1 ENOENT (No such file or directory) statx(AT_FDCWD, "/usr/bin/kcm_kscreen.so", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffcb3c5b4e0) = -1 ENOENT (No such file or directory) statx(AT_FDCWD, "/usr/bin/libkcm_kscreen", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffcb3c5b4e0) = -1 ENOENT (No such file or directory) statx(AT_FDCWD, "/usr/bin/libkcm_kscreen.so", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffcb3c5b4e0) = -1 ENOENT (No such file or directory) write(2, "kf.coreaddons: \"Could not load p"..., 91kf.coreaddons: "Could not load plugin from kcm_kscreen: The shared library was not found." ) = 91 statx(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcms/kcm_kscreen", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffcb3c5b4d0) = -1 ENOENT (No such file or directory) statx(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcms/kcm_kscreen.so", AT_STATX_SYNC_AS_STAT, STATX_ALL, {stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0644, stx_size=213464, ...}) = 0 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcms/kcm_kscreen.so", O_RDONLY|O_CLOEXEC) = 27 statx(27, "", AT_STATX_SYNC_AS_STAT|AT_EMPTY_PATH, STATX_ALL, {stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0644, stx_size=213464, ...}) = 0 statx(27, "", AT_STATX_SYNC_AS_STAT|AT_EMPTY_PATH, STATX_ALL, {stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0644, stx_size=213464, ...}) = 0 I admit that this might not be the right place to report this, but I decided to reopen the issue in the hope that people can either help debugging this directly here or point me (and others who might have the same problem) to a better location. -- You are receiving this mail because: You are watching all bug changes.
