Application: systemsettings (6.5.5) ApplicationNotResponding [ANR]: true Qt Version: 6.10.1 Frameworks Version: 6.22.0 Operating System: Linux 6.18.9-200.fc43.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora Linux 43 (KDE Plasma Desktop Edition)" DrKonqi: 6.5.5 [CoredumpBackend] -- Information about the crash: Last boot, I updated https://github.com/luisbocanegra/plasma-smart-video-wallpaper-reborn, acquired via plasma-discover-6.5.5-1.fc43.x86_64. Upon successful `qdbus-qt6 org.kde.LogoutPrompt /LogoutPrompt promptReboot`, when SDDM was automatically bypassed, as I've configured its KCM to do, I observed that PlasmaShell was not visible. Invoking it via BaSH didn't remediate this. To demonstrate, `time strace -Ttr qdbus-qt6 org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.activateLauncherMenu` fails, and returns: > ~~~ > 00:49:27 (+ 0.000027) futex(0x560ff83d3ad8, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, FUTEX_BITSET_MATCH_ANY) = 0 <24.986885> > 00:49:52 (+ 24.986928) futex(0x560ff83d3a90, FUTEX_WAKE_PRIVATE, 1) = 0 <0.000010> > 00:49:52 (+ 0.000042) fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(0x88, 0x2), ...}) = 0 <0.000011> > 00:49:52 (+ 0.000045) write(1, "Error: org.freedesktop.DBus.Erro"..., 42Error: org.freedesktop.DBus.Error.NoReply > ) = 42 <0.000013> > 00:49:52 (+ 0.000035) write(1, "Did not receive a reply. Possibl"..., 211Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. > ) = 211 <0.000010> > 00:49:52 (+ 0.000034) write(4, "\1\0\0\0\0\0\0\0", 8) = 8 <0.000009> > 00:49:52 (+ 0.000028) futex(0x7ffc29885570, FUTEX_WAIT_PRIVATE, 0, NULL) = 0 <0.000019> > 00:49:52 (+ 0.000050) write(4, "\1\0\0\0\0\0\0\0", 8) = 8 <0.000008> > 00:49:52 (+ 0.000026) futex(0x560ff83d0648, FUTEX_WAKE_PRIVATE, 1) = 1 <0.000008> > 00:49:52 (+ 0.000025) futex(0x7f12543ff990, FUTEX_WAIT_BITSET, 20630, NULL, FUTEX_BITSET_MATCH_ANY) = 0 <0.000032> > 00:49:52 (+ 0.000151) exit_group(2) = ? > 00:49:52 (+ 0.000488) +++ exited with 2 +++ > > real 0m49.541s > user 0m0.005s > sys 0m0.009s > ~~~ Consequently, I attempted to change wallapers, via the relevant KCM. However, doing so reproducibly causes this ANR. Additional diagnostic information may be available at https://bugzilla.redhat.com/show_bug.cgi?id=2411805#c13. The crash can be reproduced every time. -- Backtrace (Reduced): #5 __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:52 #6 0x00007fbd6107bc3c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=a5@entry=0, a6=a6@entry=4294967295, nr=202) at cancellation.c:49 #7 0x00007fbd6107c2ac in __futex_abstimed_wait_common64 (private=0, futex_word=0x55a7e24c57d8, expected=<optimized out>, op=<optimized out>, abstime=0x0, cancel=true) at futex-internal.c:57 #8 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55a7e24c57d8, expected=<optimized out>, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #9 0x00007fbd6107c30f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55a7e24c57d8, expected=<optimized out>, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #10 0x00007fbd6107e97e in __pthread_cond_wait_common (cond=0x55a7e24c57b8, mutex=0x55a7e24c5790, clockid=0, abstime=0x0) at pthread_cond_wait.c:421 #11 ___pthread_cond_wait (cond=0x55a7e24c57b8, mutex=0x55a7e24c5790) at pthread_cond_wait.c:453 #12 0x00007fbd618da234 in QWaitConditionPrivate::wait (this=0x55a7e24c5790, deadline=...) at /usr/src/debug/qt6-qtbase-6.10.1-3.fc43.x86_64/src/corelib/thread/qwaitcondition_unix.cpp:68 #13 QWaitCondition::wait (this=this@entry=0x55a7dfc3de70, mutex=mutex@entry=0x55a7dfc3de68, deadline=...) at /usr/src/debug/qt6-qtbase-6.10.1-3.fc43.x86_64/src/corelib/thread/qwaitcondition_unix.cpp:146 #14 0x00007fbd615a96b5 in QDBusPendingCallPrivate::waitForFinished (this=this@entry=0x55a7dfc3de20) at /usr/src/debug/qt6-qtbase-6.10.1-3.fc43.x86_64/src/dbus/qdbuspendingcall.cpp:207 #15 0x00007fbd6155c127 in QDBusConnectionPrivate::sendWithReply (this=this@entry=0x7fbd480016e0, message=..., mode=mode@entry=QDBus::Block, timeout=timeout@entry=-1) at /usr/src/debug/qt6-qtbase-6.10.1-3.fc43.x86_64/src/dbus/qdbusintegrator.cpp:2073 #16 0x00007fbd6155c418 in QDBusConnectionPrivate::findMetaObject (this=0x7fbd480016e0, service=..., path=..., interface=..., error=...) at /usr/src/debug/qt6-qtbase-6.10.1-3.fc43.x86_64/src/dbus/qdbusintegrator.cpp:2634 #17 0x00007fbd6157066c in QDBusInterfacePrivate::QDBusInterfacePrivate (serv=<optimized out>, p=<optimized out>, iface=<optimized out>, con=<optimized out>, this=0x55a7e0d112b0) at /usr/src/debug/qt6-qtbase-6.10.1-3.fc43.x86_64/src/dbus/qdbusinterface.cpp:123 #18 QDBusInterfacePrivate::QDBusInterfacePrivate (this=0x55a7e0d112b0, serv=<optimized out>, p=<optimized out>, iface=<optimized out>, con=<optimized out>) at /usr/src/debug/qt6-qtbase-6.10.1-3.fc43.x86_64/src/dbus/qdbusinterface.cpp:117 #19 0x00007fbd615707fc in QDBusInterface::QDBusInterface (this=this@entry=0x55a7e01934c0, service=..., path=..., interface=..., connection=..., parent=parent@entry=0x55a7e20b47d0) at /usr/src/debug/qt6-qtbase-6.10.1-3.fc43.x86_64/src/dbus/qdbusinterface.cpp:187 #20 0x00007fbd2aa13390 in WallpaperModule::save (this=0x55a7e20b47d0) at /usr/include/qt6/QtCore/qarraydatapointer.h:452 Reported using DrKonqi
Created attachment 189633 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
I have reproduced this at https://bugzilla.redhat.com/show_bug.cgi?id=2440117#c0, too.
This also affects Qt's DBusViewer, per https://bugzilla.redhat.com/show_bug.cgi?id=2440118#c0.
Does the issue go away if you change back to 1st party wallpaper plugin (like default picture wallpaper) instead of using 3rd party video wallpaper plugin?
(In reply to Akseli Lahtinen from comment #4) > Does the issue go away if you change back to 1st party wallpaper plugin > (like default picture wallpaper) instead of using 3rd party video wallpaper > plugin? Attempting to change to a default wallpaper is what caused this. It was already set as PSVWB, so I couldn't switch off it, to Plain Colour. However, this problem remediated itself the next time I logged-out.