Bug 412632 - discover crash on start
Summary: discover crash on start
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.15.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
: 416408 420142 432266 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-10-05 11:12 UTC by jm-ejC9o
Modified: 2021-02-02 01:10 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
stacktrace (17.80 KB, text/plain)
2019-10-05 11:12 UTC, jm-ejC9o
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jm-ejC9o 2019-10-05 11:12:57 UTC
Created attachment 123032 [details]
stacktrace

SUMMARY
Discover crashes on startup

STEPS TO REPRODUCE
1. Start discover

OBSERVED RESULT
Discover crashes

EXPECTED RESULT
Discover not crashing

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.4

ADDITIONAL INFORMATION

Possible caused by proxy settings changes, I'm on another network than usual and have to disable going through the proxy. 

A toast appears briefly before the crash and says:
"cannot update repo 'updates-modular': Cannot prepare internal mirrorlist: Curl error (5): Couldn't resolveproxy name for " and it goes on a little bit then finishes by "[Could not resolve proxy: myredactedproxyname]".
Comment 1 Aleix Pol 2019-10-09 11:41:35 UTC
On which distribution do you get this? Is there any chance you can upgrade to the stable Plasma 5.16?
Comment 2 jm-ejC9o 2019-10-14 10:33:19 UTC
I'm on "Fedora release 30 (Thirty)" and I'd rather not risk a manual upgrade of plasma.
Comment 3 Christoph Feck 2019-10-22 01:09:02 UTC
Requested information was added with comment #2; changing status.

Relevant part of the backtrace:
Thread 1 (Thread 0x7fcc9412a800 (LWP 14964)):
[KCrash Handler]
#6  0x00005645051ec200 in ?? ()
#7  0x00007fcc97c9cdca in QObjectPrivate::connectImpl (sender=0x5645047b5d60, signal_index=0, receiver=0x5645083303c0, slot=<optimized out>, slotObj=<optimized out>, type=<optimized out>, types=<optimized out>, senderMetaObject=<optimized out>) at kernel/qobject.cpp:4883
#8  0x00007fcc97c9d052 in QObject::connectImpl (sender=sender@entry=0x5645047b5d60, signal=signal@entry=0x7ffd54a3a9b0, receiver=receiver@entry=0x5645083303c0, slot=slot@entry=0x0, slotObj=0x564507888270, type=Qt::AutoConnection, types=0x0, senderMetaObject=<optimized out>) at kernel/qobject.cpp:4841
#9  0x00007fcc99cdbfc5 in QObject::connect<void (QObject::*)(QObject*), AggregatedResultsStream::addResults(const QVector<AbstractResource*>&)::<lambda()> > (type=Qt::AutoConnection, slot=..., context=0x5645083303c0, signal=(void (QObject::*)(class QObject * const, class QObject *)) 0x7fcc97c984c0 <QObject::destroyed(QObject*)>, sender=0x5645047b5d60) at /usr/include/c++/9/bits/move.h:99
#10 AggregatedResultsStream::addResults (this=0x5645083303c0, res=...) at /usr/src/debug/plasma-discover-5.15.5-1.fc30.x86_64/libdiscover/resources/ResourcesModel.cpp:308
#11 0x00007fcc97c97ec0 in QtPrivate::QSlotObjectBase::call (a=0x7ffd54a3aaf0, r=0x5645083303c0, this=0x5645058ebba0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#12 QMetaObject::activate (sender=0x564505840e20, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3781
#13 0x00007fcc99cb8506 in ResultsStream::resourcesFound (this=<optimized out>, _t1=...) at /usr/src/debug/plasma-discover-5.15.5-1.fc30.x86_64/x86_64-redhat-linux-gnu/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResourcesBackend.cpp:157
#14 0x00007fcc99cec9b9 in ResultsStream::<lambda()>::operator() (__closure=0x564504cc0d60) at /usr/src/debug/plasma-discover-5.15.5-1.fc30.x86_64/libdiscover/resources/AbstractResourcesBackend.cpp:52
#15 QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, ResultsStream::ResultsStream(const QString&, const QVector<AbstractResource*>&)::<lambda()> >::call (arg=<optimized out>, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#16 QtPrivate::Functor<ResultsStream::ResultsStream(const QString&, const QVector<AbstractResource*>&)::<lambda()>, 0>::call<QtPrivate::List<>, void> (arg=<optimized out>, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#17 QtPrivate::QFunctorSlotObject<ResultsStream::ResultsStream(const QString&, const QVector<AbstractResource*>&)::<lambda()>, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=<optimized out>, this_=0x564504cc0d50, r=<optimized out>, a=<optimized out>, ret=<optimized out>) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:439
#18 0x00007fcc97ca4596 in QtPrivate::QSlotObjectBase::call (a=0x7ffd54a3ab30, r=<optimized out>, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
#19 QSingleShotTimer::timerEvent (this=0x564504cc0d80) at kernel/qtimer.cpp:318
Comment 4 spmorton 2019-11-19 15:10:54 UTC
try these commands:
plasma-discover --listbackends
Available backends:
 * kns-backend
 * packagekit-backend
to be sure the packagekit-backend is  installed then issue the command:
plasma-discover --backends packagekit-backend

This should fix it
Comment 5 Christoph Feck 2020-05-06 20:59:06 UTC
*** Bug 420142 has been marked as a duplicate of this bug. ***
Comment 6 Aleix Pol 2020-06-21 01:45:30 UTC
Git commit 1616e8b84a649913f4d9e1664e632d0a9c747491 by Aleix Pol.
Committed on 21/06/2020 at 01:44.
Pushed by apol into branch 'master'.

safety

Try not to keep objects that might get destroyed in memory unless necessary

M  +8    -5    libdiscover/resources/ResourcesModel.cpp
M  +2    -1    libdiscover/resources/ResourcesModel.h

https://invent.kde.org/plasma/discover/commit/1616e8b84a649913f4d9e1664e632d0a9c747491
Comment 7 Nate Graham 2021-01-29 15:16:20 UTC
*** Bug 416408 has been marked as a duplicate of this bug. ***
Comment 8 Nate Graham 2021-01-29 15:16:28 UTC
*** Bug 432266 has been marked as a duplicate of this bug. ***
Comment 9 Aleix Pol 2021-02-02 01:10:43 UTC
I can't find any crash since Plasma 5.16. Please reopen if you can reproduce in a maintained version of the software.