Created attachment 177884 [details] Screen recording of the bug SUMMARY Opening properties of a file / folder for the first time in dolphin under X11 messes up window management badly. The dolphin window is hidden for a short time, then re-appears at a different position, along with the properties dialogue. STEPS TO REPRODUCE 1. Open a fresh instance of dolphin in X11 (maybe also Wayland, untested) 2. Right click a folder or file 3. Click on properties OBSERVED RESULT Dolphin window unaffected, dialogue window opens EXPECTED RESULT A whole lot of mess (see attached video) SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.12.11-200.fc41.x86_64 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7700X 8-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7D70 System Version: 1.0 ADDITIONAL INFORMATION Unfortunately the whole thing happens way too fast so I couldn't get any decent x properties info or the likes. Neither kwin nor dolphin give any helpful output on stdout or stderr (except some potentially unrelated qml warnings). Window manager is kwin, mostly default settings, no window rules for dolphin as far as I can spot. Reproducible on my laptop (same software versions) with an Intel GPU, thus unrelated to graphics stack or drivers.
Thanks for the bug report. I'm not able to reproduce this using Dolphin built from git-master, on Plasma also built from git-master I also tried with Plasma 6.2.5 on Fedora, and on Neon Testing (X11 sessions) but was unable to replicate there either. Can you please create a new user and see if you can replicate the bug with it? Thanks.
Created attachment 177976 [details] Same bug, fresh user, vanilla config hi, yes.
Thanks for following up. I'll leave it to the more experienced Dolphin maintainers to take it from here.
Hi - merging this in with the existing bug for this topic, thanks! *** This bug has been marked as a duplicate of bug 494627 ***