Bug 433163 - 'configure digital clock' resizes kickoff
Summary: 'configure digital clock' resizes kickoff
Status: RESOLVED DUPLICATE of bug 433083
Alias: None
Product: plasmashell
Classification: Plasma
Component: Digital Clock widget (other bugs)
Version First Reported In: 5.21.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-18 12:13 UTC by roger truong
Modified: 2021-02-18 15:08 UTC (History)
2 users (show)

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


Attachments
kickoff vs clock interaction (629.35 KB, video/x-matroska)
2021-02-18 12:13 UTC, roger truong
Details

Note You need to log in before you can comment on or make changes to this bug.
Description roger truong 2021-02-18 12:13:35 UTC
Created attachment 135843 [details]
kickoff vs clock interaction

SUMMARY
When the new kickoff menu is open, and 'configure digital clock' is selected through the widget, it sometimes causes the kickoff menu to resize itself so that the next becomes unreadable. This sometimes takes a few tries to reproduce, but I can get it to happen pretty consistently on a fresh user profile. So far this seems to only affect the clock and not other widgets (still not sure if this bug should be filed under kickoff or clock so feel free the change).

STEPS TO REPRODUCE
1. open new kickoff and keep it open
2. right click digital clock widget
3. select 'configure digital clock'

OBSERVED RESULT
The applications list shrinks in width to make the text unreadable
[see attachment]

EXPECTED RESULT
Kickoff closes as the new systems window is open and comes into focus

SOFTWARE/OS VERSIONS
Linux: 5.10.16
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
unsure what logs i can attach for this
Comment 1 roger truong 2021-02-18 13:07:49 UTC
ive only been able to reproduce this bug in x11. wayland seems to be fine
Comment 2 Nate Graham 2021-02-18 15:08:17 UTC
Same root cause as Bug 433083.

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