Bug 1212052 - KDE clock widgets not working
Summary: KDE clock widgets not working
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma) (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-Mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-06 11:39 UTC by Miguel Rozsas
Modified: 2023-06-10 21:04 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miguel Rozsas 2023-06-06 11:39:22 UTC
The several kde clocks are not working on snapshot 2023-06-04.
The analog one shows a fixed time.
The digital and approximate shows nothing (an empty space).
No matter if the widget is placed on the desktop or in taskbar.

Reverting to snapshot 2023-06-01, the clocks was showed ok again.

There is no indication of problem on date/time when issuing the command date.
The file /etc/localtime is a symbolic link to /usr/share/zoneinfo/America/Sao_Paulo

There is no KDE component/library/framework updated between 2023-06-1 and 2023-06-01 neither a kernel update. Very confusing....

On tumbleweed 2023-06-04 I have created a new test user with a empty home and loaded KDE for the first time for this new user. By default, a digital clock should be on taskbar. All I see is an empty space. If I hover the mouse pointer over the digital clock area I see an empty box where it should display the date/time in long format.

Operating System: openSUSE Tumbleweed 20230604
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.4-1-default (64-bit)
Graphics Platform: offscreen
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600
Comment 1 Miguel Rozsas 2023-06-10 21:03:22 UTC
Fixed on 20230605.
No additional work is needed, just updating to 20230605 fixed the issue.
Comment 2 Miguel Rozsas 2023-06-10 21:04:27 UTC
Fixed on 20230605.
No additional work is needed, just updating to 20230605 fixed the issue.