Bug 452469 - Discover will not run updates. Crashes every time I try to use it to update the system.
Summary: Discover will not run updates. Crashes every time I try to use it to update t...
Status: RESOLVED DUPLICATE of bug 443745
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.24.3
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-10 12:57 UTC by nashtr@gmail.comn
Modified: 2022-04-12 02:12 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nashtr@gmail.comn 2022-04-10 12:57:34 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Discover notifier starts at login, crashes while fetching updates
2. Running discover manually and clicking updates after opening causes it to crash.
3. Bug reporter says it can't generate a backtrace.

OBSERVED RESULT
Crashes every time I try to check for updates.

EXPECTED RESULT
Updates are successfully installed

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  Fedora Linux 35
(available in About System)
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-04-11 18:38:56 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. If the crash reporter wizard can't generate one, it's possible that you can use the command-line `coredumpctl` tool to get one manually. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Can you please attach a backtrace of the crash? Thanks!
Comment 2 nashtr@gmail.comn 2022-04-11 22:08:46 UTC
Thank you for the quick response here are the results of gdb and backtrace. If you need any more info, please let me know. Thanks in advance.

gdb:
Starting program: /usr/bin/plasma-discover 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffe35ef640 (LWP 4841)]
[New Thread 0x7fffe2dee640 (LWP 4842)]
[New Thread 0x7fffe2552640 (LWP 4843)]
[New Thread 0x7fffe0f8d640 (LWP 4844)]
[New Thread 0x7fffc7fff640 (LWP 4845)]
[New Thread 0x7fffc77fe640 (LWP 4846)]
[Thread 0x7fffc7fff640 (LWP 4845) exited]
[Thread 0x7fffc77fe640 (LWP 4846) exited]
[New Thread 0x7fffc77fe640 (LWP 4847)]
Invalid cast.
warning: Probes-based dynamic linker interface failed.
Reverting to original interface.
Downloading separate debug info for /usr/lib64/gio/modules/libgsettingsgconfbackend.so...
Downloading separate debug info for /home/fnord79/.cache/debuginfod_client/a103dfe6b545dfa26205e744dc0bf0d108e3a97e/debuginfo...
Downloading separate debug info for /lib64/libgconf-2.so.4...
Downloading separate debug info for /lib64/libdbus-glib-1.so.2...
Downloading separate debug info for /home/fnord79/.cache/debuginfod_client/6a0fc8765d53e60df12f887aa8a4feeda211bae7/debuginfo...
[New Thread 0x7fffc7fff640 (LWP 4851)]
[New Thread 0x7fffc635d640 (LWP 4852)]
[New Thread 0x7fffc5b25640 (LWP 4853)]
[New Thread 0x7fffc5324640 (LWP 4854)]
[New Thread 0x7fffaffff640 (LWP 4856)]
[New Thread 0x7fffaf7fe640 (LWP 4857)]
[New Thread 0x7fffaeffd640 (LWP 4858)]
[New Thread 0x7fffae7fc640 (LWP 4859)]
[New Thread 0x7fffaddfa640 (LWP 4860)]
adding empty sources model QStandardItemModel(0x555556285c60)
[New Thread 0x7fffad5f9640 (LWP 4861)]
[Detaching after fork from child process 4862]
org.kde.plasma.libdiscover: Couldn't find a category for  "fwupd-backend"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5: QML Binding: Binding loop detected for property "value"
[New Thread 0x7fffacdf8640 (LWP 4872)]
[New Thread 0x7fff87fff640 (LWP 4873)]
[Thread 0x7fffacdf8640 (LWP 4872) exited]
[Thread 0x7fff87fff640 (LWP 4873) exited]
[New Thread 0x7fff87fff640 (LWP 4875)]
[New Thread 0x7fffacdf8640 (LWP 4877)]
[New Thread 0x7fff84ffd640 (LWP 4878)]
[Thread 0x7fffae7fc640 (LWP 4859) exited]
[New Thread 0x7fffae7fc640 (LWP 4886)]
[New Thread 0x7fff86703640 (LWP 4887)]
[New Thread 0x7fff85f00640 (LWP 4889)]
[New Thread 0x7fff7ffff640 (LWP 4890)]
kf.newstuff.core: Could not find category "Calligra Flow Stencil"
KNS error in "Calligra_stencils" : KNSCore::ConfigFileError "All categories are missing" QVariant(Invalid)
invalid kns backend! "/etc/xdg/calligra_stencils.knsrc" because: "Invalid Calligra_stencils backend, contact your distributor."
org.kde.plasma.libdiscover: Discarding invalid backend "calligra_stencils.knsrc"
kns error "/etc/xdg/calligra_stencils.knsrc" "Invalid Calligra_stencils backend, contact your distributor."
org.kde.plasma.libdiscover: Couldn't find a category for  "fwupd-backend"
[Thread 0x7fff7ffff640 (LWP 4890) exited]
[Thread 0x7fffc5b25640 (LWP 4853) exited]
[Thread 0x7fff85f00640 (LWP 4889) exited]
[Thread 0x7fffaeffd640 (LWP 4858) exited]
[Thread 0x7fffad5f9640 (LWP 4861) exited]
[Thread 0x7fff86703640 (LWP 4887) exited]
[New Thread 0x7fff86703640 (LWP 4949)]
[New Thread 0x7fffad5f9640 (LWP 5081)]

Thread 1 "plasma-discover" received signal SIGSEGV, Segmentation fault.
FlatpakBackend::findSource (origin=..., installation=0x7fffbc02ee40, this=0x555555f49d40) at /usr/src/debug/plasma-discover-5.24.3-1.fc35.x86_64/libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:114
Downloading source file /usr/src/debug/plasma-discover-5.24.3-1.fc35.x86_64/libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp...
114             return m_installation;

And backtrace:
(gdb) backtrace
#0  FlatpakBackend::findSource (origin=..., installation=0x7fffbc02ee40, this=0x555555f49d40)
    at /usr/src/debug/plasma-discover-5.24.3-1.fc35.x86_64/libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:114
#1  FlatpakBackend::getAppForInstalledRef (this=0x555555f49d40, installation=0x7fffbc02ee40, ref=0x55555731e260, 
    freshResource=0x7fffffffd417)
    at /usr/src/debug/plasma-discover-5.24.3-1.fc35.x86_64/libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:357
#2  0x00007fffc46d7a3e in operator() (__closure=0x55555735e0c0)
    at /usr/src/debug/plasma-discover-5.24.3-1.fc35.x86_64/libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:1296
#3  QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, FlatpakBackend::search(const AbstractResourcesBackend::Filters&)::<lambda()>::<lambda()> >::call (arg=<optimized out>, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#4  QtPrivate::Functor<FlatpakBackend::search(const AbstractResourcesBackend::Filters&)::<lambda()>::<lambda()>, 0>::call<QtPrivate::List<>, void> (arg=<optimized out>, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#5  QtPrivate::QFunctorSlotObject<FlatpakBackend::search(const AbstractResourcesBackend::Filters&)::<lambda()>::<lambda()>, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=<optimized out>, 
    this_=0x55555735e0b0, r=<optimized out>, a=<optimized out>, ret=<optimized out>)
    at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#6  0x00007ffff614f3e9 in QtPrivate::QSlotObjectBase::call (a=0x7fffffffd500, r=<optimized out>, this=0x55555735e0b0)
    at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#7  doActivate<false> (sender=0x5555573c4400, signal_index=4, argv=0x7fffffffd500) at kernel/qobject.cpp:3886
#8  0x00007ffff614a367 in QMetaObject::activate (sender=<optimized out>, m=<optimized out>, 
    local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3946
#9  0x00007ffff5f68315 in QFutureWatcherBase::event (this=<optimized out>, event=0x7fff485d2b80)
    at thread/qfuturewatcher.cpp:334
#10 0x00007ffff721c443 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x5555573c4400, e=0x7fff485d2b80)
    at kernel/qapplication.cpp:3632
#11 0x00007ffff611b7d8 in QCoreApplication::notifyInternal2 (receiver=0x5555573c4400, event=0x7fff485d2b80)
    at kernel/qcoreapplication.cpp:1064
#12 0x00007ffff611ed46 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5555555c6db0)
    at kernel/qcoreapplication.cpp:1821
#13 0x00007ffff616d117 in postEventSourceDispatch (s=0x5555555f24c0) at kernel/qeventdispatcher_glib.cpp:277
#14 0x00007ffff4a800af in g_main_dispatch (context=0x5555555d45c0) at ../glib/gmain.c:3381
#15 g_main_context_dispatch (context=0x5555555d45c0) at ../glib/gmain.c:4099
#16 0x00007ffff4ad5308 in g_main_context_iterate.constprop.0 (context=context@entry=0x5555555d45c0, block=block@entry=1, 
    dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4175
--Type <RET> for more, q to quit, c to continue without paging--c
#17 0x00007ffff4a7d8a3 in g_main_context_iteration (context=0x5555555d45c0, may_block=1) at ../glib/gmain.c:4240
#18 0x00007ffff616cbb8 in QEventDispatcherGlib::processEvents (this=0x5555555ef360, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#19 0x00007ffff611a1e2 in QEventLoop::exec (this=this@entry=0x7fffffffd930, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#20 0x00007ffff6122724 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#21 0x000055555556b688 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/plasma-discover-5.24.3-1.fc35.x86_64/discover/main.cpp:217
(gdb) Quit
Comment 3 Nate Graham 2022-04-12 02:12:06 UTC
Aha, it is the infamous Bug 443745. Thankfully that was just fixed today!

*** This bug has been marked as a duplicate of bug 443745 ***