| Summary: | Desktop UI (panels, icons) are not responding to any action | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Pawel Smolinski <pawel> |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | bhush94, info, kde, maldela, notmart, peter, polyakov84 |
| Priority: | NOR | ||
| Version: | 5.2.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Slackware | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
plasmashell frozen process GDB backtrace
Last 200 lines of ~/.xsession-errors file errors in ~/.xsession-errors file errors in ~/.xsession-errors file next episode |
||
|
Description
Pawel Smolinski
2015-02-24 22:58:44 UTC
Created attachment 91279 [details]
plasmashell frozen process GDB backtrace
Created attachment 91280 [details]
Last 200 lines of ~/.xsession-errors file
>#8 0x00007f43908546a3 in KToolInvocation::startServiceInternal(char const*, QString const&, QStringList const&, QString*, QString*, int*, QByteArray const&, bool, QString const&) () from /usr/lib64/libKF5Service.so.5
What app did you just launch?
Update status I've tried to launch Konsole app. I'm seeing something that sounds similar, but my .xsession-errors doesn't have any "Not implemented reached in virtual" ..., and my bug doesn't happen by itself. I'll report a new bug. (https://bugs.kde.org/show_bug.cgi?id=346379). Mark it as a dup if appropriate. was konsole actually launched? this may be the old problem of desktop files with the wrong dbus name that freeze the caller in krun until the invoken application is closed? I had same problems three times today. I couldn't to get error log file. But I'll try to get it next time. My plasmashell version is 5.3. Created attachment 92462 [details]
errors in ~/.xsession-errors file
Created attachment 92492 [details]
errors in ~/.xsession-errors file next episode
Maybe it helps to resolve.
Maybe problem is in system tray and thunderbird or another gtk program.
*** Bug 346379 has been marked as a duplicate of this bug. *** My plasmashell (desktop and panel[s]) also consistently freezes/is unresponsive to clicks after my session locks and a few minutes elapse. I have to kill and re-launch plasmashell (now bound to a hotkey for "convenience") to regain usability. Side note, CPU,Memory, and Network widgets in panel are all vertically compressed& overlapping thus unreadable. Date and Time widget does not appear to adhere to selected locale - previously en_DK allowed 24hr ISO date/time I'm also having plasmashell freeze on me quite regularly. My system is Fedora 22 running plasma-workspace-5.3.2-2.fc22.x86_64. It most frequently happens when switching activities using the Menu-Tab keyboard combination. It usually happens the first few times I switch activities after I have logged in. When the freeze occurs this is what happens (right after hitting Menu-Tab): - The switch to the next activity seems to have worked partially, because the open windows get switched successfully. If the start activity had firefox open and the activity I'm moving to a konsole window, these are changed (that is, firefox is no longer visible, konsole appears) - The taskbar however continues to show the open windows from the former activity (firefox in my example) - The following elements become completely unresponsive to left or right clicks: taskbar, "start" menu (I'm not sure what the proper name is), desktop itself, and the workspace menu in the top-left corner - Hitting Menu-Tab won't continue to switch to the next activity. I have to kill and restart plasmashell before I can continue. - Krunner on the other hand continues to work and can still be activated using Alt-F2. I often use this to launch a console to kill and restart plasma shell. Often I have to repeat the process several times in a row: switch activity - plasmashell freezes - restart plasmashell - switch activity - plasmashell freezes again - restart plamsashell again - ... I have 5 activities. It has happened several times I had to restart plasmashell at least 4 times before I managed to reach the last one. (I know I could also cycle backwards. I'm mostly illustrating how frequently this happens). Just to get this bugfix reported I had to switch to a separate activity to check my workspace version in a konsole: 2 restarts were required... Configuring a hotkey to restart plasmashell is a good tip that will save me quite a bit of frustration. Upgraded to plasma-workspace 5.4.1 and at first sight my freezes seem to be mostly resolved. I'm not sure if I still had them since (because of other complications around me). I'll keep an eye on it and report in the near future again. marking as resolved for now then. It was probably a wrong dbus name in a desktop file that got solved with a package update |