When I change my screen resolution because I add an external screen to my laptop the digital clock time gets tangled with the date, such that none of them can be read. I will attach screenshot. The positions are not reset before I right click it -> Digital clock settings -> add or remove bold/italic/shadow and click apply. This was actually happening with KDE 4.8 as well. Reproducible: Always
Created attachment 72600 [details] screenshot
I can confirm with 4.9
Still in 4.9.2 takes 20 seconds extra of changing when having started up with external screen.
Created attachment 76290 [details] "proof" snapshot I just noticed the same problem! But for me I did not change the screen resolution at all. Not sure when exactly it happened, I first noticed it when my notebook last woke up from standby. I attached a screenshot. Please let me know if there is anything I can do ! Of course I will add more information if I get them. And btw: KDE is unbelievably great - a few small glitches, but exceptionally flexible!!
Created attachment 76291 [details] Digital Clock Settings - Appearance Sorry for the big png :/ I just went into the Digital Clock Settings - unchecked "Bold", clicked "Apply" and then it got fixed. I attached another screenshot with my appearance settings. Please let me know, thanks! Tormen.
Created attachment 76292 [details] "proof" snapshot - small version
... and I forgot to mention, I am using: 4.9.5
This also happens in 4.10 RC3
Also happens in 4.10.1 This is driving me crazy. The worst thing is that when I go to "Digital clock settings" -> check a box AND uncheck it again (thus changing nothing) -> click apply. Then the clock is untangled. It seems that it just doesn't initialize correctly upon startup.
It stopped happening after I started using kscreen in the new kubuntu (same KDE version, just with kscreen). I don't think it's fixed, but I don't get the symptoms any more.
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham