Application: plasma-discover (5.27.8) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.0-41-lowlatency x86_64 Windowing System: X11 Distribution: Ubuntu 23.10 DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: [Steps performed, Also steps for reproduction.] 1. Updates are available notice displays 2. Click on [Update] or [OK] 3. Discover opens, displayes list of apps to be updated. 4. Click [Update] 5. "sudo" verify dialogue displays 6. Enter password 7. Appears to start updating apps. 8. Discover disapears from screen and System monitor list. 9. Click on Discover launcher. Steps 3 through 8 repeated twice at this point. 10. Repeated steps 4 through 8. 11. Dr Konqi KDE Crash Handler appeared. 12. [I did not know I would be able to compare the back trace with other back traces, so regretably did not display the backtrace. I will open the backtrace for making comparisons in the future.] 13. Found two similar [one closed, one closed waiting for info] bug reports but for other distros or for Operating System versions Earlier Than: Ubuntu Studio 23.10 or KDE Plasma Version: 5.27.8 The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x00007ed917fa9bdc in ??? () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #5 0x00007ed917fa9c40 in PackageKitBackend::resolvePackages(QStringList const&) () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #6 0x00007ed917faaa16 in ??? () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #7 0x00007ed917fb9225 in ??? () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #8 0x00007ed924af99a0 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x00007ed92656bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x00007ed924acc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x00007ed924acfeb1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x00007ed924b286f7 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x00007ed923313b2c in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x00007ed92336f46f in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x00007ed923311d20 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x00007ed924b27daa in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007ed924acb15b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x00007ed924ad3904 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x00006208a5b58c0f in ??? () #20 0x00007ed924028150 in __libc_start_call_main (main=main@entry=0x6208a5b58320, argc=argc@entry=1, argv=argv@entry=0x7ffd30959f18) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x00007ed924028209 in __libc_start_main_impl (main=0x6208a5b58320, argc=1, argv=0x7ffd30959f18, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd30959f08) at ../csu/libc-start.c:360 #22 0x00006208a5b595e5 in ??? () [Inferior 1 (process 10368) detached] The reporter indicates this bug may be a duplicate of or related to bug 482259, bug 487165, bug 481838, bug 482073, bug 482095, bug 482369, bug 482492, bug 483177, bug 483499, bug 483708, bug 483871, bug 483890, bug 484035, bug 484424, bug 484658, bug 484714, bug 484730, bug 485003, bug 486362, bug 485598, bug 486057, bug 487442, bug 488041, bug 489305, bug 489433. Reported using DrKonqi
5.27.8 is no longer supported. Please file a bug with your distribution.
(In reply to Harald Sitter from comment #1) > 5.27.8 is no longer supported. Please file a bug with your distribution. Am finally upgraded Ubuntu Studio 24.04 LTS and Discover 5.27.11 After the upgrade there were 90 some odd updates for Discover to handle. I split Discover update process in thirds so only tested it handling about 33 at a time. I am very impressed with the display of each load and update. It completed the updates as expected. I am closing this bug.