Application: plasma-discover (6.1.2) Qt Version: 6.7.0 Frameworks Version: 6.3.0 Operating System: Linux 6.5.0-41-generic x86_64 Windowing System: Wayland Distribution: KDE neon 6.0 DrKonqi: 6.1.2 [CoredumpBackend] -- Information about the crash: After Plasma update to 6.1 and this issue discussed here: https://discuss.kde.org/t/no-start-menu-or-menu-bar-after-update-to-plasma-6-1/17758/3 I tried to update using Discover. I got the message : Replacement Available: "runtime/org.freedesctop.Platform/x86_64/21.08" is no longer receiving updates. Replace it with the supported version provided by ""? At this time updates continued running in the background and at some point they stopped waiting for my action. When I clicked on Proceed, Discover crashed. The crash can be reproduced every time. -- Backtrace (Reduced): #6 0x00007d8ee7fd4f54 in QByteArrayView::QByteArrayView<char const*, true> (data=<optimized out>, this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qbytearrayview.h:152 #7 FlatpakTransactionThread::fail (this=0x58004c83a210, refName=0x7d8d05d425c0 "runtime/org.freedesktop.Platform/x86_64/21.08", error=0x0) at ./libdiscover/backends/FlatpakBackend/FlatpakTransactionThread.cpp:384 #8 0x00007d8ee7fd517b in FlatpakTransactionThread::end_of_lifed_with_rebase (reason=<optimized out>, previous_ids=0x7d8d05d428f0, rebased_to_ref=<optimized out>, ref=<optimized out>, remote=0x7d8d05d428d0 "flathub", this=0x58004c83a210) at ./libdiscover/backends/FlatpakBackend/FlatpakTransactionThread.cpp:425 #9 Callbacks::end_of_lifed_with_rebase (transaction=<optimized out>, remote=0x7d8d05d428d0 "flathub", ref=<optimized out>, reason=<optimized out>, rebased_to_ref=<optimized out>, previous_ids=0x7d8d05d428f0, user_data=0x58004c83a210) at ./libdiscover/backends/FlatpakBackend/FlatpakTransactionThread.cpp:153 [...] #12 0x00007d8ef91c569a in g_cclosure_marshal_generic_va () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Reported using DrKonqi
Created attachment 171693 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Created attachment 171694 [details] Message caused Discover crash
Running the update again no more updates ware available in Discover. I was prompted to reboot. I choose Install updates and reboot. On reboot I got the message: Failed to start NVIDIA Persistence Daemon. See systemctl status nvidia-persistenced.service for details After the update finished the GUI launched correctly this time with taskbar all menus I run systemctl and gave me: angel@angel-pc:~$ systemctl status nvidia-persistenced.service × nvidia-persistenced.service - NVIDIA Persistence Daemon Loaded: loaded (/lib/systemd/system/nvidia-persistenced.service; static) Active: failed (Result: exit-code) since Tue 2024-07-16 00:11:39 CEST; 4min 50s ago Process: 2830 ExecStart=/usr/bin/nvidia-persistenced --user nvidia-persistenced --no-persistence-mode --verbose (code=e> Process: 2854 ExecStopPost=/bin/rm -rf /var/run/nvidia-persistenced (code=exited, status=0/SUCCESS) CPU: 4ms Jul 16 00:11:39 angel-pc systemd[1]: Starting NVIDIA Persistence Daemon... Jul 16 00:11:39 angel-pc nvidia-persistenced[2830]: ERROR: Failed to find user ID of user 'nvidia-persistenced': Success Jul 16 00:11:39 angel-pc systemd[1]: nvidia-persistenced.service: Control process exited, code=exited, status=1/FAILURE Jul 16 00:11:39 angel-pc systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'. Jul 16 00:11:39 angel-pc systemd[1]: Failed to start NVIDIA Persistence Daemon.
*** Bug 490352 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 487526 ***