Summary: | Since updating to 5.100 kded segfaults in Packagekit (likely during update check) | ||
---|---|---|---|
Product: | [Applications] apper | Reporter: | Claudius <claudius+kde> |
Component: | general | Assignee: | Daniel Nicoletti <dantti12> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | bernhardu, kdelibs-bugs, navarrums, nicolas.fella, smitha, tysontanx, ybx332 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Apper causes KDED to crash after login |
Description
Claudius
2022-12-06 13:26:58 UTC
The crash is in packagekit-qt and unrelated to kded, please report it upstream at https://github.com/PackageKit/PackageKit-Qt Could also be a problem with appear, but either way, not a bug in the kded framework I tried to bring this to the attention of packagekit-qt developers in this bug report: https://github.com/PackageKit/PackageKit-Qt/issues/42 (In reply to Bernhard Übelacker from comment #3) > I tried to bring this to the attention of packagekit-qt Thank you! I didn't have the time to report it to upstream yet. It also doesn't seem to happen every time. It might be some sort of race condition. Created attachment 155131 [details] Apper causes KDED to crash after login I've reported my information to https://github.com/PackageKit/PackageKit-Qt/issues/42 But just in case, I will post those info here, as well. This also happens to me but it's on Archlinux. Apper causes kded5 to crash at login. This bug began to happen since KDE Plasma 5.26.3 or .4, KDE Framework 5.100.0. It happens at every login, on multiple machines, all of them ArchLinux. The crash would happen a few seconds after I logged in to KDE Plasma Desktop. The whole desktop would appears to freeze for a few seconds. KDE Crash Handler would then notify me about kded5 crashed. But when I click the button to see Developer Information, the Crash Handler would also crash. KDED would not restart automatically after that. I thought it could have been Apper/packagekit-qt's automatic update checker not compatible with the newer KDE components, but I could not stop KDED from crashing even after I disabled every automatic update function in Apper. The only way was to uninstall Apper from the system (I didn't need to uninstall packagekit or packagekit-qt5). BTW, all my machines has a Intel CPU. So I don't think this is Zen4 specific? Following is the crash information from DrKonqi. *** Bug 463576 has been marked as a duplicate of this bug. *** (In reply to Tyson Tan from comment #5) > Created attachment 155131 [details] > Apper causes KDED to crash after login > > I've reported my information to > https://github.com/PackageKit/PackageKit-Qt/issues/42 > > But just in case, I will post those info here, as well. > > This also happens to me but it's on Archlinux. Apper causes kded5 to crash > at login. This bug began to happen since KDE Plasma 5.26.3 or .4, KDE > Framework 5.100.0. It happens at every login, on multiple machines, all of > them ArchLinux. > > The crash would happen a few seconds after I logged in to KDE Plasma > Desktop. The whole desktop would appears to freeze for a few seconds. KDE > Crash Handler would then notify me about kded5 crashed. But when I click the > button to see Developer Information, the Crash Handler would also crash. > KDED would not restart automatically after that. > > I thought it could have been Apper/packagekit-qt's automatic update checker > not compatible with the newer KDE components, but I could not stop KDED from > crashing even after I disabled every automatic update function in Apper. The > only way was to uninstall Apper from the system (I didn't need to uninstall > packagekit or packagekit-qt5). > > BTW, all my machines has a Intel CPU. So I don't think this is Zen4 specific? > > Following is the crash information from DrKonqi. Same here on Arch Linux and was wondering what's the problem, thanks! I'll uninstall Apper and let's hope this will fix it. *** Bug 464934 has been marked as a duplicate of this bug. *** |