Red Hat Bugzilla – Bug 1260271
Bad report :-( plasmashell freezes or kactivitymanaged?
Last modified: 2016-12-20 09:35:06 EST
Description of problem:
This is a really bad report because I have no idea what causes plasmashell to freeze. Is it actually plasmashell or is it kactivitymanaged. In dmesg I see:
kactivitymanage: segfault at 7f8c6c3217d0 ip 00007f8c6c56a731 sp 00007ffea9810608 error 4 in libQt5Sql.so.5.5.0[7f8c6c556000+3f000]
But I doubt this has anything to do with the freezes I experience. The segfault happens even when plasmashell starts okay.
I've found a way to trigger the freezes and how to 'solve' them (mostly). See below.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2. open Regional Settings (systemssettings) - Formats
3. select Detailed Settings
4. change all settings ( country doen't matter)
5. logout as requested and login
6. plasmashell/panel/desktop right click menu (?) are 'frozen'
To restore a working desktop
2. open a virtual terminal (e.g. Ctrl-Alt-F2)
3. remove from ~/.config/plasma-localerc all localization settings (except the LANG setting)
4. do the same for ~/.config/plasma-locale-settings.sh
5. return to the login screen (Ctrl-Alt-F1) and login.
Note: I've seen this failing :-(
Changing regional setting leads to the desktop to freeze.
Desktop does not freeze after changing regional settings
As I said this is a bad report. Not only because I have no idea what componant can be the culprit, but also I couldn't find any useful information in log files (.xsession-errors, journalctl, /var/log/Xorg.0.conf).
Btw. Is there a way I can disable/remove kactivitymanaged, so that I can better isolate this issue?
This issue started happening after the big kf5-* update from Thursday, August 27.
Found the right component. It's - again - the digital clock who is to blame. e.g change Digital Clock Settings -> Use 24-hour Clock (default is with am/pm) to 24-hour w/o am/pm, logout/login and bingo. Btw. it makes plasmashell very unhappy cpu usage raises to 100%. Changing the setting back to it's default - edit in file plasma-org.kde.plasma.desktop-appletsrc variable use24hFormat= 2 -> 1- solves the issue.
I've also encountered this issue recently, soon (but not immediately) after upgrading from kf5 5.17 to 5.18:
[67608.045320] kactivitymanage: segfault at 7f08b84ad7d0 ip 00007f08b84c3731 sp 00007fffefdc2c88 error 4 in libQt5Sql.so.5.5.1[7f08b84af000+3f000]
When it happens to me, it crashes my whole Plasma desktop and kicks me back to the GDM login screen.
I don't have any particular insights to add here. Apparently this has been reported a number of times upstream to KDE, but because no one's ever provided a backtrace, they've typically closed all the tickets (e.g. https://bugs.kde.org/show_bug.cgi?id=336079). Information elsewhere suggests that this is sometimes related to an interaction with data found under the user's .cache directory, and clearing that may resolve the issue. (One reference for this being https://bugs.launchpad.net/ubuntu/+source/kactivities-kf5/+bug/1450660.)
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.