OK, I spent some time on nailing this one... It made the plasmashell process enter an infinite loop. Logging out then logging or rebooting does not solve this since the bug conditions are reproduced as soon as the session restarts. The only way I could find out is to remove the file : ~/.config/plasma-org.kde.plasma.desktop-appletsrc Onto the bug description now : Reproducible: Always Steps to Reproduce: 1. If you don't have it yet, add an "Analog clock" widget on the horizontal panel 2. Configure it to display the date 3. Move the panel to left or right screen edge (I also tested this sequence in the order 3->1->2 with the same consequence) Actual Results: Plasmashell freezes, CPU jumps to 100%.
I experienced pretty much the same but without analogue clock. I'm not 100% certain it's the same bug, therefore I reported it as well as bug 351479. Btw you don't need to delete plasma-org.kde.plasma.desktop-appletsrc. Kill plasmashell, open the file in a text editor, look for the line plugin=org.kde.panel and in the same section change formfactor to 2 and location to 4.
Can anyone of you please get a backtrace?
@Kai, since Drkonqui is not popping up (plasmashell is not crashing, just freezing), I am unsure on how to get a backtrace... How do I get one ?
Hi, I'm affected by this as well. In my case it is caused by enabling option "Show date" in the digital clock applet. After this, plasmashell freeze at start. But when I removed the line " showDate=true" from the plasma-org.kde.plasma.desktop-appletsrc file, plasmashell started again. But when I enabled the "Show Date" options again, and restarted the plasmashell application, it worked as well. So maybe there is one more condition. Maybe: date is to wide and is printed outside of panel. In .xsession-errors file I have a lot of messages: QPainter::end: Painter ended with 2 saved states I'm just recompiling qt and kde5 packages with debug symbols and I'll try to provide backtrace.
Are we sure we mean analogue clock? That doesn't have a show date function.
@David, yes you're right, I meant digital clock of course... :) I changed the title.
thanks *** This bug has been marked as a duplicate of bug 351479 ***