Created attachment 112489 [details] PopUp1 My calendar popup is 1 day off. "date," KDE's "Adjust date and time," and even the calender hover pop-up show the correct date. However, the grid is exactly 1 day off. I'm running plasma 5.12.5, kde-frameworks 5.45.0, and Qt 5.11.0beta4.
Created attachment 112490 [details] Popup2
Maybe related to the start weekday (it is Monday here).
Not sure if it's helpful, but it's still 1 day off here (my timezone, American/Detroit, has changed to Tuesday, and the pop-up displays Monday). I haven't changed any settings, and can't seem to locate "week starts with weekday" to try toggling. None of the settings changes make it jump forward a day, and hovering, the systemsettings "Date and Time" module, etc. all show Tuesday correctly.
I have the same problem. The date seems to be correct everywhere except the digital/analog clock popup. My calendar weekday starts on Sunday and I couldn't find a place to change it. If I change the date to June 1st, the popup calendar switches to June, but the highlighted day is still incorrect (May 31). I have only noticed this after the recent qt5 and frameworks packages updates (2018-05-25). plasma: 5.12.5 frameworks: 5.46.0 qt: 5.11.0 system: 4.16.11-1-ARCH x86_64
It's still an issue for me on 5.12.90 as well. Could this be related to Qt 5.11? I'm not sure how to provide more information for troubleshooting. I have the issue with a fresh KDE instance (new config) with the following: [andrew@thinkpad]$ pacman -Q plasma-desktop qt5-base plasma-desktop 5.12.90.1-1 qt5-base 5.11.0-1 [andrew@thinkpad]$ ls -l /etc/localtime lrwxrwxrwx 1 root root 37 May 19 22:16 /etc/localtime -> ../usr/share/zoneinfo/America/Detroit
Same issue for me also on on Arch Linux running: plasma-desktop 5.12.5 qt5-base 5.11.0 I'm running KDE Neon User Edition on my laptop and do not have the issue. Digital Clock version on Neon is: 4.5.12.5-0neon+16.04+xenial+build121 Still trying to locate the Digital Clock widget version on Arch, but have yet to find it.
*** Bug 394978 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 394423 ***