Bug 489033 - bottom bar in the updates page doesn't change size when maximizing/unmaximizing
Summary: bottom bar in the updates page doesn't change size when maximizing/unmaximizing
Status: RESOLVED DUPLICATE of bug 479782
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 6.1.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-23 10:45 UTC by kevindu52defargoth
Modified: 2024-06-25 21:41 UTC (History)
3 users (show)

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


Attachments
when the bar is longer than the window (84.20 KB, image/jpeg)
2024-06-23 10:45 UTC, kevindu52defargoth
Details
the bar is shorter than the window (100.78 KB, image/jpeg)
2024-06-23 10:46 UTC, kevindu52defargoth
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kevindu52defargoth 2024-06-23 10:45:32 UTC
Created attachment 170852 [details]
when the bar is longer than the window

SUMMARY
There is a bottom bar in the update page that read something like "Select all Select None  Total size : 500MiB".
It adapts its  size when resizing the window, but not when maximizing it.


STEPS TO REPRODUCE
1. Open discover and go to Updates.
2. Notice the bottom bar (you may have to hit refresh).
2. Unmaximize the window and resize it. THe bar adapts.
4. Maximize the window.

OBSERVED RESULT
Now the bar is too short (see attachment).

EXPECTED RESULT
The width of the bar should adapt.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-41-generic (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
You can also make the bar too long, in which case some part of it are not visible.
Comment 1 kevindu52defargoth 2024-06-23 10:46:04 UTC
Created attachment 170853 [details]
the bar is shorter than the window
Comment 2 Nate Graham 2024-06-25 21:41:52 UTC
Same root cause as Bug 479782.

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