Bug 444995 - [Wayland] Non-Kirigami KDE apps stuck unmaximized or maximized
Summary: [Wayland] Non-Kirigami KDE apps stuck unmaximized or maximized
Status: RESOLVED FIXED
Alias: None
Product: frameworks-kxmlgui
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.87.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords: usability, wayland
Depends on:
Blocks:
 
Reported: 2021-11-05 05:35 UTC by Samuel Reddy
Modified: 2023-12-12 16:44 UTC (History)
1 user (show)

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


Attachments
Video of the bug (2.64 MB, video/x-matroska)
2021-11-05 05:35 UTC, Samuel Reddy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Samuel Reddy 2021-11-05 05:35:33 UTC
Created attachment 143226 [details]
Video of the bug

SUMMARY
If a KDE app starts up maximized, then you unmaximize the window, then you try to maximize the window, it won't let you maximize it( or if you unmaximize, maximize, then try to unmaximize) This does not apply to kirigami apps like discover.

STEPS TO REPRODUCE
1. Open an KDE app(like gwenview) that starts maximized(not kirigami apps though)
2. Unmaximize the KDE app
3. Try to maximize the KDE app
4. The KDE app will not maximize
5. If you can maximize the app, try unmaximizing it
6. Does not unmaximize

OBSERVED RESULT
The KDE app refuses to maximize or unmaximize

EXPECTED RESULT
They maximize and unmaximize normally 

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.14-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 5 3450U with Radeon Vega Mobile Gfx
Memory: 5.7 GiB of RAM
Graphics Processor: AMD Radeon™ Vega 8 Graphics

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2021-11-08 20:17:32 UTC

*** This bug has been marked as a duplicate of bug 437089 ***
Comment 2 Nate Graham 2023-12-12 16:44:27 UTC
Unfortunately I mis-triaged this bug report, and it's not that at all. It is however already fixed!