Bug 438512 - Since the 5.22 update, the event and timezone view always shows a (glitched) horizontal scrollbar
Summary: Since the 5.22 update, the event and timezone view always shows a (glitched) ...
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: Digital Clock widget (show other bugs)
Version: 5.22.0
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL: https://bugreports.qt.io/browse/QTBUG...
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-12 16:20 UTC by Christian (Fuchs)
Modified: 2021-06-15 23:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
screenshot of the issue (148.28 KB, image/png)
2021-06-12 16:20 UTC, Christian (Fuchs) 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christian (Fuchs) 2021-06-12 16:20:28 UTC 
Created attachment 139260 [details]
screenshot of the issue

SUMMARY

Since I updated to 5.22, both the PIM events and timezone views (left hand in the popup) of the digital clock show a glitched horizontal scrollbar, see the attached screenshot.


STEPS TO REPRODUCE
1. Update to Plasma 5.22
2. Have a digital clock applet with support for timezones and PIM events
3. Open the popup

OBSERVED RESULT

Layout broken

EXPECTED RESULT

Layout normal

SOFTWARE/OS VERSIONS

Operating System: Fedora 34
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.12.9-300.fc34.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2
Comment 1 Nate Graham 2021-06-15 23:10:02 UTC 
This is caused by an upstream Qt bug: https://bugreports.qt.io/browse/QTBUG-83890

We ported to use a component that's affected by this bug, unfortunately. We can't port back without losing some of the features that the new UI added. So we just need to be patient and wait for the bug to be fixed. FWIW a KDE contributor submitted a patch to fix it; it simply needs to be reviewed, merged, and backported to the KDE patch collection.