Bug 480900 - Digital clock render error
Summary: Digital clock render error
Status: RESOLVED DUPLICATE of bug 365716
Alias: None
Product: plasmashell
Classification: Plasma
Component: Global Menu (show other bugs)
Version: 5.93.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-02-05 14:19 UTC by hovgaard
Modified: 2024-02-05 21:07 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Digitalclock render error after screen save event (36.45 KB, image/jpeg)
2024-02-05 14:19 UTC, hovgaard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description hovgaard 2024-02-05 14:19:01 UTC
Created attachment 165567 [details]
Digitalclock render error after screen save event

The digital clock in menubar is bonkers after waking from screen energy save.
After an energy save event under wayland my screen resolution bums down to 1024x768 resoltion.
I then run kscreen-doctor to get back to 1920x1080 resolution.
And the desktop is restored and all of the statmenu look fine and works fine except for the digital clock which does a weird errornous rerender and only some part of the clock i displayed (see attached screen shot)


Operating System: Arch Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.3-arch1-2 (64-bit)
Graphics Platform: Wayland
Processors: 32 × 13th Gen Intel® Core™ i9-13900HX
Memory: 62.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4070 Laptop GPU/PCIe/SSE2
Manufacturer: LENOVO
Product Name: 82WK
System Version: Legion Pro 5 16IRX8
nvidia-smi 
Mon Feb  5 15:17:00 2024       
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 545.29.06              Driver Version: 545.29.06    CUDA Version: 12.3     |
|-----------------------------------------+----------------------+----------------------+
Comment 1 Nate Graham 2024-02-05 21:07:12 UTC
Looks like Bug 365716 is back!

*** This bug has been marked as a duplicate of bug 365716 ***