Created attachment 187449 [details] Two photos are zipped. One is before the logging in and the other is after the logging in. SUMMARY When a multi-screen PC resumed from the suspend state, the login window on each screen showed the time in a different time zone. After logging in, only the primary monitor showed the desktop while the other was left in the login state. STEPS TO REPRODUCE 1. Put the multi-screen PC into suspend state by closing the lid. 2. After 1 hr, open the lid to resume. 3. Then, the time in different time zones is shown. OBSERVED RESULT Please see the attached photo(before-loggging-in.jpg). The internal ( primary ) screen and external screen show the time in UTC and local time(UTC+9), respectively. When I logged in, only the primary screens showed the desktop(after-logging-in.jpg). The secondary screen was left in the log-in state. This was solved when I logged off and logged in again. EXPECTED RESULT Both screen shows time in the local time zone. And both screens showed the desktop after logging in. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Linux 2025-12-06 KDE Plasma Version: 6.5.80 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 ADDITIONAL INFORMATION NOTE: I saw this problem this morning. This is the first time I saw and I could not reproduce it.
This is the lock screen and not the login screen, right? And to confirm, you're reporting that with a multi-screen setup, after you unlock, the lock screen disappears only on one screen, and it remains visible on the other screen? And that the whole time, the times shown on each screen differed? Were you able to move the pointer to the other screen and unlock it too? This is all very strange.
Created attachment 187471 [details] attachment-3583719-0.html Seiichi HORIE <a6m1zero@gmail.com> 5:56 (2 分前) To *bug-control* You are right. This is the lock screen after resuming from suspend. > after you unlock, the lock screen disappears only on one screen, and it remains visible on the other screen? Yes. > And that the whole time, the times shown on each screen differed? Yes. > Were you able to move the pointer to the other screen and unlock it too? No, it was. The pointer was able to move only on the desktop screen. 2025年12月10日(水) 1:53 Nate Graham <bugzilla_noreply@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=513115 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > CC| |nate@kde.org > Status|REPORTED |NEEDSINFO > Assignee|kwin-bugs-null@kde.org |plasma-bugs-null@kde.org > Product|kwin |plasmashell > Component|multi-screen |Screen locking > Target Milestone|--- |1.0 > Version First|git-stable-Plasma/6.2 |6.5.80 > Reported In| | > > --- Comment #1 from Nate Graham <nate@kde.org> --- > This is the lock screen and not the login screen, right? > > And to confirm, you're reporting that with a multi-screen setup, after you > unlock, the lock screen disappears only on one screen, and it remains > visible > on the other screen? > > And that the whole time, the times shown on each screen differed? > > Were you able to move the pointer to the other screen and unlock it too? > > This is all very strange. > > -- > You are receiving this mail because: > You reported the bug.
Thanks. Based on the symptoms, it would appear to be the same issue as Bug 512028. *** This bug has been marked as a duplicate of bug 512028 ***
Created attachment 187826 [details] Log of the jounalctl and system information in 2025 Dec 21 This is the journalctl output when this issue reproduced on my PC.
I don't think this is a duplication of Bug #512028 . According to the symptom, Bug #512028 is the problem, such as "Cannot log in until typing ENTER twice". But this issue eventually allows log-in only on one screen (Please see the after-logging-in.jpg ) in the first attachment (zip). While one desktop is ready to work, the other is left as a lock screen. Today, I have met the same problem. I could log in to only one of the two screens. The other was still locked (I didn't see the time in either window). Please find the third attachment, log-202251221.tar.gz, as : - Journalctl output. - Information about my system.
Created attachment 192077 [details] Photo before and after minute change Suffer the same as found in attachment 187449 [details] - before logging in image, not after logging in image SUMMARY Lock screen after waking from sleep, one monitor shows UTC instead of local time until next minute tick STEPS TO REPRODUCE 1. Put computer to sleep/suspend to RAM 2. Wake computer from sleep OBSERVED RESULT One monitor shows correct time (UTC+10) and other monitor shows incorrect time (UTC) (see PXL_20260506_115540130.jpg). After 1 minute passes, both displays update and show the correct time (see PXL_20260506_115602439.jpg). EXPECTED RESULT After waking from sleep, both displays should show the correct time from the outset SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 44 KDE KDE Plasma Version: 6.6.4 KDE Frameworks Version: 6.25.0 Qt Version: 6.10.3 ADDITIONAL INFORMATION Should it be relevant, display specifications Left: 1440p 170Hz no rotation running at 110% scale Right: 1080p 165Hz 90deg counterclockwise at 100% scale
Based on the description of the symptoms, I think it's actually Bug 516479, which will be fixed in the upcoming Plasma 6.6.5 release. *** This bug has been marked as a duplicate of bug 516479 ***