Description of problem: Made changes to the repos through the app, refreshed the cache and then clicked "update" app then crashed before compleation. No changes were made. Version-Release number of selected component: apper-1.0.0-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/apper crash_function: QHash<QString, PackageModel::InternalPackage>::erase executable: /usr/bin/apper journald_cursor: s=3083ef2bfb4f4086b8866210849b4509;i=5d79c;b=c269b0eecb7e44a99f26c4899aa7793b;m=8d28cd80;t=57306f24bd7c2;x=bf24e0ee9eec6e89 kernel: 4.17.11-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QHash<QString, PackageModel::InternalPackage>::erase at /usr/include/qt5/QtCore/qrefcount.h:73 #2 PackageModel::clearSelectedNotPresent at /usr/src/debug/apper-1.0.0-1.fc28.x86_64/libapper/PackageModel.cpp:494 #3 Updater::getUpdatesFinished at /usr/src/debug/apper-1.0.0-1.fc28.x86_64/Apper/Updater/Updater.cpp:268 #4 QtPrivate::QSlotObjectBase::call at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378 #5 QMetaObject::activate(QObject*, int, int, void**) at kernel/qobject.cpp:3750 #6 QMetaObject::activate at kernel/qobject.cpp:3629 #7 PackageKit::Transaction::finished at /usr/src/debug/PackageKit-Qt-1.0.1-1.fc28.x86_64/x86_64-redhat-linux-gnu/src/packagekitqt5_autogen/include/moc_transaction.cpp:1655 #8 PackageKit::TransactionPrivate::finished at /usr/src/debug/PackageKit-Qt-1.0.1-1.fc28.x86_64/src/transactionprivate.cpp:235 #9 PackageKit::TransactionPrivate::daemonQuit() at /usr/src/debug/PackageKit-Qt-1.0.1-1.fc28.x86_64/src/transactionprivate.cpp:263 #10 PackageKit::Transaction::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) at /usr/src/debug/PackageKit-Qt-1.0.1-1.fc28.x86_64/src/transaction.h:850
Created attachment 1474822 [details] File: backtrace
Created attachment 1474823 [details] File: cgroup
Created attachment 1474824 [details] File: core_backtrace
Created attachment 1474825 [details] File: cpuinfo
Created attachment 1474826 [details] File: dso_list
Created attachment 1474827 [details] File: environ
Created attachment 1474828 [details] File: exploitable
Created attachment 1474829 [details] File: limits
Created attachment 1474830 [details] File: maps
Created attachment 1474831 [details] File: mountinfo
Created attachment 1474832 [details] File: open_fds
Created attachment 1474833 [details] File: proc_pid_status
Created attachment 1474834 [details] File: var_log_messages
*** Bug 1639435 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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' of '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.