Red Hat Bugzilla – Bug 1274167
[abrt] muon-discover: QtPrivate::RefCount::ref(): muon-discover killed by SIGSEGV
Last modified: 2016-12-20 10:05:59 EST
Description of problem:
I started installing yakuake, then after seeing it not progressing I pressed install again.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 QtPrivate::RefCount::ref at /usr/include/qt5/QtCore/qrefcount.h:54
#1 QString::QString at /usr/include/qt5/QtCore/qstring.h:878
#2 PackageKitResource::installedPackageId at ../../../../libmuon/backends/PackageKitBackend/PackageKitResource.cpp:68
#3 PackageKitResource::availablePackageId at ../../../../libmuon/backends/PackageKitBackend/PackageKitResource.cpp:63
#4 PKTransaction::start at ../../../../libmuon/backends/PackageKitBackend/PKTransaction.cpp:46
#5 ResourcesModel::qt_static_metacall at moc_ResourcesModel.cpp:157
#6 ResourcesModel::qt_metacall at moc_ResourcesModel.cpp:264
#7 QQmlObjectOrGadget::metacall at /usr/src/debug/qtdeclarative-opensource-src-5.5.0/src/qml/qml/qqmlpropertycache.cpp:1689
#8 CallMethod at /usr/src/debug/qtdeclarative-opensource-src-5.5.0/src/qml/jsruntime/qv4qobjectwrapper.cpp:1160
#9 CallPrecise at /usr/src/debug/qtdeclarative-opensource-src-5.5.0/src/qml/jsruntime/qv4qobjectwrapper.cpp:1409
Created attachment 1085423 [details]
Created attachment 1085424 [details]
Created attachment 1085425 [details]
Created attachment 1085426 [details]
Created attachment 1085427 [details]
Created attachment 1085428 [details]
Created attachment 1085429 [details]
Created attachment 1085430 [details]
Created attachment 1085431 [details]
Created attachment 1085432 [details]
Created attachment 1085433 [details]
Created attachment 1085434 [details]
tried to install thunderbird in fully updated f23 RC-3 live KDE x86_64 install. with muon install failed Had previous install of xchat work on same session.
Another user experienced a similar problem:
Hit this two ways in muon-discover:
1. Install F23 KDE Live i686. Open muon. Search for Kate, click 'Install'. It seems to do something, then returns to showing Kate with an 'Install' button. Click the 'Install' button again. Crash.
2. After the crash, run muon again. See that Kate is shown as installed. Click 'Remove'. Enter admin credential. Removal fails ('operation not supported'), then shows Kate with a 'Remove' button again. Click the 'Remove' button. Crash.
reason: muon-discover killed by SIGSEGV
runlevel: N 5
I reported it on kde bugzilla
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.