Bug 449558

Summary:	dolphin starts very weirdly under wayland
Product:	[Applications] dolphin	Reporter:	Martin Tlustos <martin.tlustos>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	kfm-devel
Priority:	NOR
Version:	21.12.1
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Martin Tlustos 2022-02-03 13:43:35 UTC

SUMMARY
When starting dolphin under wayland, the window pops up in the right lower center of the screen. I cannot maximize it (clicking doesn't do anything). When closing and starting again, dolphin appears in the left top middle of the screen, and then I can maximize it. Next time I close and open dolphin, the cycle repeats. Any way how to solve or debug it?
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. start kwin wayland
2. open dolphin (opens in a weird place, but only if I closed it maximized)
3. click on the maximize/restore button
4. close it
5. reopen it (it opens in another place and now I can maximize it)

No other program shows this behaviour, and it only shows under wayland.

Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.3
Kernel Version: 5.13.0-27-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD RENOIR

Comment 1 Martin Tlustos 2022-02-08 05:14:11 UTC

So I just realized there are two parts to it. 
1) Even discover and kate will open at a weird place (so last opened place and status is not remembered)
2) only dolphin will refuse to get maximized, the other two programs will get maximized without any problem.

I have tried to get a screen capture for documentation, but couldn't find a program that works under wayland (yet).

Comment 2 Martin Tlustos 2022-02-10 13:40:14 UTC

Fixed with version 5.24.0 (at least for me ;-)