Summary: | Crash when loggin in after having logged out previously | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Clemens Eisserer <linuxhippy> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | linuxhippy, nate, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.20.5 | ||
Target Milestone: | 1.0 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Clemens Eisserer
2021-05-29 06:23:51 UTC
This should have been fixed a while ago; can you upgrade to Fedora 34 and see of it still happens? 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 mark the bug 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! When logging out & in again, I see all kinds of weird behaviour, sometimes crashes on login, sometimes wifi does not work anymore - and sometimes everything works as expected. I'll give the usb live system a try, F34 changed quite a bit and to be honest I am a bit reluctant to see my production desktop broken again (wayland) or without audio (pipewire) ;) what I find interesting - most of the time, those bugs are catched by the system-wide bug reporting utility (ABRT), only on rare occuasions the kde bug reporter is able to catch a crash. This seems to be a sad thing, because the bugs filed at redHat usually are not noticed by anybody and every 6 months I get about 20 emails regarding bugs that will be auto-closed because their reported release is approacing EOL. Created attachment 139731 [details]
New crash information added by DrKonqi
plasmashell (5.20.5) using Qt 5.15.2
- What I was doing when the application crashed:
logged out and in again, which sometimes works - sometimes results in various crashes.
-- Backtrace (Reduced):
#6 0x00007f5d87523db6 in _dbus_abort.cold () from /lib64/libdbus-1.so.3
#7 0x00007f5d87549310 in _dbus_warn_check_failed () from /lib64/libdbus-1.so.3
#8 0x00007f5d89044059 in QDBusConnectionPrivate::getNameOwnerNoCache(QString const&) () from /lib64/libQt5DBus.so.5
#9 0x00007f5d89046051 in QDBusConnectionPrivate::addSignalHook(QString const&, QDBusConnectionPrivate::SignalHook const&) () from /lib64/libQt5DBus.so.5
#10 0x00007f5d890476c5 in QtPrivate::QSlotObject<bool (QDBusConnectionPrivate::*)(QString const&, QDBusConnectionPrivate::SignalHook const&), QtPrivate::List<QString const&, QDBusConnectionPrivate::SignalHook const&>, bool>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libQt5DBus.so.5
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 mark the bug 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! 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! |