Hi! Muon-Discover reproducibly crashes when installing an application using the PackageKit backend. I am using the Tanglu packages at time: http://packages.tanglu.org/chromodoris/muon-discover I would fix this, but I don't understand the backend well enough yet to determine the correct solution for this crash, although its origin is quite simple (see the gdb trace). Cheers, Matthias Reproducible: Always GDB Backtrace: #0 QString (other=..., this=0x7fffffffd000) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:812 No locals. #1 PackageKitResource::installedPackageId (this=this@entry=0x14fe9b0) at ../../../../libmuon/backends/PackageKitBackend/PackageKitResource.cpp:68 No locals. #2 0x00007fffca245b60 in PKTransaction::progressChanged (this=0x3d92010, id=..., status=PackageKit::Transaction::StatusUnknown, percentage=<optimized out>) at ../../../../libmuon/backends/PackageKitBackend/PKTransaction.cpp:74 No locals. #3 0x00007fffca24bb35 in PKTransaction::qt_static_metacall (_o=0x7fffffffcfc0, _c=4294954944, _id=0, _a=0x381f9d0) at moc_PKTransaction.cpp:119 No locals. #4 0x00007ffff57e7719 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 No symbol table info available. #5 0x00007fffca009414 in PackageKit::Transaction::itemProgress(QString const&, PackageKit::Transaction::Status, unsigned int) () from /usr/lib/x86_64-linux-gnu/libpackagekitqt5.so.0 No symbol table info available. #6 0x00007fffca00bb29 in ?? () from /usr/lib/x86_64-linux-gnu/libpackagekitqt5.so.0 No symbol table info available. #7 0x00007ffff57e7719 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 No symbol table info available.
Git commit eac54c6f314f24a085dbaa12a0b1e3d00fd934d8 by Aleix Pol. Committed on 26/05/2015 at 15:24. Pushed by apol into branch 'Plasma/5.3'. Make sure that the backends aren't unavailable when we decide to install M +1 -0 discover/qml/InstallApplicationButton.qml M +4 -0 libmuon/resources/ResourcesModel.cpp M +1 -1 libmuon/resources/ResourcesModel.h http://commits.kde.org/muon/eac54c6f314f24a085dbaa12a0b1e3d00fd934d8
Hi Matthias, Thanks for the bug report. I haven't been able to reproduce your crash, I managed to reproduce another one above, can you try and see if it's related? Otherwise I'll need more information to be able to understand the patch.
Thanks for your reply! From the GDB trace, it appears like m_packages[PackageKit::Transaction::InfoInstalled] holds no value instead of a QStringList, which means resource() is not set properly in this transaction. Since this crash is triggered by a sanity check: if (id != res->availablePackageId() || id != res->installedPackageId()) I would probably catch this case and ignore it, but this would highly likely cover another bug in this case. To reproduce this issue, you can use the tanglu-kde ISO images from here: http://yofel.net/tanglu/cdimage/daily-live/current/ Or alternatively take the older images (e.g. http://yofel.net/tanglu/cdimage/daily-live/20150525/ ) and run apt update && apt full-upgrade in order to get the latest Muon packages. The crash can be reproduced in VirtualBox perfectly well here. (for debugging symbols, use the muon-dbg package) Cheers, Matthias
Follow up: I need to test your patch, as this crash might be related, since I immediately switched views in Muon Discover after hitting the "Install" button.
I tested the patch you committed, but the issue still remains...
Hm, knowing how to reproduce it would help, there's little I can do otherwise...
Can somebody maybe run this patch and tell me what's the output? It will help to understand what's going on. To get the output run "plasmawindowed org.kde.muonnotifier" diff --git a/libmuon/backends/ApplicationBackend/ApplicationNotifier.cpp b/libmuon/backends/ApplicationBackend/ApplicationNotifier.cpp index 967e22f..673328b 100644 --- a/libmuon/backends/ApplicationBackend/ApplicationNotifier.cpp +++ b/libmuon/backends/ApplicationBackend/ApplicationNotifier.cpp @@ -138,6 +138,7 @@ void ApplicationNotifier::parseUpdateInfo() QByteArray securityString = line.right(line.size() - eqpos - 1); int securityUpdates = securityString.toInt(); + QDebug() << "updates!" << line << updatesString << securityString; setUpdates(updatesString.toInt() - m_securityUpdates, securityUpdates); }
You can easily reproduce this bug by using the current Tanglu live-cd, which has Muon preinstalled. You can get the image from here: http://yofel.net/tanglu/cdimage/daily-live/current/tanglu-chromodoris-kde-live-amd64.hybrid.iso (See http://yofel.net/tanglu/cdimage/daily-live/current/ for a list of ISOs) In order to get debug information installed, run "sudo apt install muon-dbg". The crash appears when you install an application in Muon discover and, while it is being installed, switch back to the main overview and click on other UI elements. I can apply your patch and test with it, but I don't think it's related to this issue... (unless the installation somehow also triggers an update check)
With the latest refactoring done in Muon, this issue appears much less often - in fact, I only had it once, unfortunately without GDB running. I will attach a backtrace in case I experience it again.
Don't you get the backtrace on drkonqi?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!