Bug 1260271
Summary: | Bad report :-( plasmashell freezes or kactivitymanaged? | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Martin Kho <rh-bugzilla> |
Component: | plasma-workspace | Assignee: | KDE SIG <kde-sig> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | dhgutteridge, erecio, jgrulich, kde-sig, kevin, ltinkl, rdieter, than |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-12-20 14:35:06 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Martin Kho
2015-09-05 12:25:16 UTC
Hi, This issue started happening after the big kf5-* update from Thursday, August 27. HTH Martin Kho Hi, 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. HTH Martin Kho I've also encountered this issue recently, soon (but not immediately) after upgrading from kf5 5.17 to 5.18: [67608.045320] kactivitymanage[2099]: 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' of '23'. 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed. |