for a while now (a dozen or more updates) discover will crash “unexpectedly” when i close the window after an update (the updates seem to complete without error).
if i switch the view off the updates page (applications, etc) and then close the window it does not crash.
tried several times to file a bug report following the dialog the pops up but it always fails to generate the necessary logs so the report won’t allow me to submit.
any idea what, if anything, i should try to do differently?
I sometimes use Discover to shop through the apps to find things like extensions or themes, but I leave all my updating to my package management system. So far, Discover has not been able to handle every scenario for every distribution. On openSUSE, I handle most things from the command line with zypper and only use YAST for repositories and searching for packages and their dependencies and looking at what dependencies come from which repos. In fact, I don’t remember the last time I opened Discover. It’s been quite a while.
Will it work one day in the future, maybe.
The only other thing I might suggest is perhaps trying to launch Discover from a terminal, then trigger the issue so you can at least see what (if anything) is printed to stdout when the crash happens?
Also, if I saw correctly in your post history, you’re running Kubuntu 22.04? Do you have the Backports PPA enabled, and/or have you used any other update mechanisms to update Discover/other KDE components? I’m just assuming that everything that shipped with 22.04 is pretty old by this point, and the issue you’re seeing might already be solved in a more recent version?
it was working before this, and it’s not like it chokes on certain updates…
it crashes EVERY time i don’t switch away from the update page before closing the app, but ONLY if i don’t switch away.
i’ve been tempted to let the backports updates flow thru, but haven’t done it yet.
i’ll try the command line for any other hints first and then probably just let massive update plow thru from backports.
should i also turn on /extras or is that a bridge too far?
Is it updating properly from Apt? If so, at least you know that part works. Separating it all out will help the troubleshooting.
If you have packages installed from /extras, then they do need to keep as up to date as the rest of the system, or they will start failing.
If you don’t have packages installed from /extras, then wait till you get it all working again before turning that repo on.
Explain?
What specific backports are you talking about?
If you added a PPA or something, you can use ppa-purge to roll back to stock plasma packages.
If you are purposefully NOT updating some things, this would clearly cause odd sorts of bugs like what you see, from a mix of new and old components not working with each other properly.
typing “discover” at the command line gives me “command not found”, so that’s a bust.
i’ve installed
https://ppa.launchpadcontent.net/kubuntu-ppa/backports/ubuntu/
but it is currently not checked so updates do not pull from there
thinking about also installing
https://ppa.launchpadcontent.net/kubuntu-ppa/backports-extra/ubuntu/
for access to the latest plasma
i checked (made active) the first one only long enough to download kalendar and a couple of other pim libraries that were needed to integrate with the clock/calendar widget in the taskbar panel, but that has been acting up lately as well.
so what you are saying is that it’s whole hog or nothing, not a good idea to pick and choose.
so i should just turn both of these on an let the updates fly?
the updates from discover work fine, it’s just that when they are finished and i go to close the window that the crash happens… i should have been more clear.
so apt and discover are both in sync and both work to install/update packages, i’m just getting this giltch in the GUI app when i try to close it.
The program you need to run is plasma-discover %F
Anytime you need to know a program name that a gui uses, just right-click a shortcut to it in the kick off and open “Edit Application”.
If your kde/discover version is still supported you can file a bug report. There is a kde guide on how to create useful crash reports.
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Also you can look at or post your journald logs for more information.
thanks that’s helpful
there’s not currently anything that needs updating so i’ll probably have to try this trick till later when something shows up.
rather do that then run 417 updates thru my machine and hope for the best from backports
will update this thread when i get more info.
ah, yes it was the backtrace that was failing… so i could not submit the bug report
i’ll try running the gdb tool next time i have updates
Correct.
This will be an even larger set of updates, just to let you know 
You should in theory be able to enable the kubuntu-backports-extra without re-enabling the kubuntu-backports PPA, and is what I would attempt, personally. I do like to take chances, though.
But it may be wiser to re-enable kubuntu-backports and fully update, to get a complete set of packages from there, in case you decide to ppa-purge the -extras PPA.
Backups/snapshots of course are highly suggested.
ok got a couple of updates this morning and ran discover using gdb to get this output
everything seemed to go fine right up until the last line which shows a SIGSEGV
the only difference is i didn’t get a crash report notice on my desktop this time.
i’ve also included the output of the bt command as well
and i’ll work on filing a bug report with this info as well
(gdb) run
Starting program: /usr/bin/plasma-discover
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff018c640 (LWP 28917)]
[New Thread 0x7fffef1b3640 (LWP 28918)]
[New Thread 0x7fffed63a640 (LWP 28919)]
qrc:/qml/DiscoverWindow.qml:116:19: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ <key> ]' to bind to all of them.
[New Thread 0x7fffdd5ff640 (LWP 28920)]
[New Thread 0x7fffdcdfe640 (LWP 28921)]
[New Thread 0x7fffd7fff640 (LWP 28922)]
[New Thread 0x7fffd77fe640 (LWP 28923)]
qrc:/qml/DiscoverPage.qml:42:37: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:85:25: QML ScrollBar: Binding loop detected for property "visible"
adding empty sources model QStandardItemModel(0x5555560c3f50)
[New Thread 0x7fffd6ffd640 (LWP 28924)]
[New Thread 0x7fffd49ff640 (LWP 28925)]
[New Thread 0x7fffbbfff640 (LWP 28926)]
[New Thread 0x7fffba1ff640 (LWP 28927)]
[New Thread 0x7fffb99fe640 (LWP 28928)]
[New Thread 0x7fffb91fd640 (LWP 28929)]
[New Thread 0x7fffb89fc640 (LWP 28930)]
[Detaching after fork from child process 28931]
org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:75:5: QML Binding: Binding loop detected for property "value"
[New Thread 0x7fffa3fff640 (LWP 28933)]
[New Thread 0x7fffa36fe640 (LWP 28934)]
[New Thread 0x7fffa19fc640 (LWP 28940)]
[New Thread 0x7fffa0bff640 (LWP 28942)]
[New Thread 0x7fff8bfff640 (LWP 28945)]
[New Thread 0x7fff8b7fe640 (LWP 28946)]
[Thread 0x7fff8b7fe640 (LWP 28946) exited]
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight"
Fwupd Error 10 no metadata URIs for vendor-directory
qml: message: no metadata URIs for vendor-directory
[New Thread 0x7fff8b7fe640 (LWP 28947)]
[Thread 0x7fffb91fd640 (LWP 28929) exited]
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed
qrc:/qml/DiscoverPage.qml:42:37: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:85:25: QML ScrollBar: Binding loop detected for property "visible"
[Thread 0x7fff8bfff640 (LWP 28945) exited]
[Thread 0x7fffdcdfe640 (LWP 28921) exited]
[Thread 0x7fffd77fe640 (LWP 28923) exited]
[Thread 0x7fffdd5ff640 (LWP 28920) exited]
[Thread 0x7fffd7fff640 (LWP 28922) exited]
[Thread 0x7fffd49ff640 (LWP 28925) exited]
[Thread 0x7fffd6ffd640 (LWP 28924) exited]
[Thread 0x7fffbbfff640 (LWP 28926) exited]
[Thread 0x7fffa3fff640 (LWP 28933) exited]
[Thread 0x7fffed63a640 (LWP 28919) exited]
Thread 1 "plasma-discover" received signal SIGSEGV, Segmentation fault.
0x00007ffff7a7d275 in QQuickWindow::mouseGrabberItem() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
(gdb)
(gdb) bt
#0 0x00007ffff7a7d275 in QQuickWindow::mouseGrabberItem() const () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#1 0x00007ffff7a7faef in QQuickWindowPrivate::removeGrabber(QQuickItem*, bool, bool) ()
at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#2 0x00007ffff7a67195 in QQuickItemPrivate::derefWindow() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#3 0x00007ffff7a67d58 in QQuickItem::setParentItem(QQuickItem*) () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#4 0x00007ffff7a6803c in QQuickItem::~QQuickItem() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5 0x00007ffff7be9859 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6 0x00007ffff5ce4a6e in QObjectPrivate::deleteChildren() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007ffff5cef924 in QObject::~QObject() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007ffff7be9859 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#9 0x00007ffff5ce4a6e in QObjectPrivate::deleteChildren() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ffff5cef924 in QObject::~QObject() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007ffff7bea789 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x00007ffff5ce4a6e in QObjectPrivate::deleteChildren() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007ffff5cef924 in QObject::~QObject() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007fffec056609 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so
#15 0x00007ffff68af463 in QV4::MemoryManager::sweep(bool, void (*)(char const*)) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#16 0x00007ffff68af5a9 in QV4::MemoryManager::~MemoryManager() () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#17 0x00007ffff692c0e4 in QV4::ExecutionEngine::~ExecutionEngine() () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#18 0x00007ffff69167e2 in QJSEngine::~QJSEngine() () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#19 0x00007ffff6af4a3d in QQmlApplicationEngine::~QQmlApplicationEngine() () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#20 0x000055555556e411 in ()
#21 0x000055555556e43d in ()
#22 0x00007ffff5ce71c3 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007ffff6f6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x00007ffff5cb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007ffff5cbcf27 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007ffff5cc0d0c in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x000055555556c838 in ()
#28 0x00007ffff5229d90 in __libc_start_call_main
(main=main@entry=0x55555556bf40, argc=argc@entry=1, argv=argv@entry=0x7fffffffddf8) at ../sysdeps/nptl/libc_start_call_main.h:58
#29 0x00007ffff5229e40 in __libc_start_main_impl
(main=0x55555556bf40, argc=1, argv=0x7fffffffddf8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdde8) at ../csu/libc-start.c:392
#30 0x000055555556d275 in ()
(gdb)
I found this. Not sure if it will help.
i can remember seeing some firmware updates go by in discover, so i’m not really sure when this package got broken (or if it is broken) but i’ve found 3 installed packages with fwupd in the name marked them all for re-installation, just in case that makes any difference.
also looked a the recommends and re-installed python3 because there was some audio playback packages i installed and then deleted and some of those had ties to python3 and may have impacted it.
Not sure if the error output about fwupd is related to the crash, but IANAD(eveloper).
You might try disabling all the firmware update options in Discover’s settings, and see if it still crashes.
Which distro are you running? I thought all major ones are already on 5.27?
not unless they have enabled backports and backports/extras
which i have yet to do.