| Summary: | Maximized window shrinks at the bottom when opening or closing search bar | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | joseteluisete <josete> |
| Component: | bars: filter | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | cfeck, john.kizer, kfm-devel |
| Priority: | NOR | Keywords: | X11-only |
| Version First Reported In: | 24.12.2 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
joseteluisete
2025-03-03 15:46:43 UTC
Hi - I can't reproduce on my Fedora KDE 41 device, or a KDE Neon VM. Could you please specify the Dolphin version that you experienced this on, and if the issue occurs on the most recent 24.12.3 version? And just to double-check, does the same issue occur on a Wayland session? Thanks! My Dolphin version is 24.12.2. Manjaro has not yet released anything new in Plasma. I keep my system always updated. I've seen this problem for many months. Today I have tried Wayland for the very first time. It does not happen with Wayland. But I've found that some applications I have don't scale correctly so I guess I won't use it for now. I have looked a lot for this error and I've found nothing. Nobody else is complaining about this. I don't know what to do. Thanks a lot! Thanks! Updating the title to reflect that closing also impacts it, the version it was found in, and the X11 vs. Wayland factor. Do you happen to have multiple virtual desktops in use? If you run dolphin from a terminal, are any message printed to that terminal when the window shrinks? I have seen that it happens not only when the window is maximized but in all cases. I have also seen that it happens not only with the Search pane but also with the Filters pane. Launching Dolphin from terminal I have seen many errors all related to the icon set used. I have tried to change it (La Capitaine, Mojave-CT, Oxygen, Breeze). With the standard ones (Oxygen, Breeze) there are no error messages. But in no case the terminal shows errors opening and closing the panels that make Dolphin shrink. Thanks! I forgot, sorry ... I don't use virtual desktops. I have only one. Thanks - and just to double-check, does the issue reproduce on your system within a newly-created user account? (Trying to rule out any possible customization influence!) Could be bug 477700. Great point - joseteluisete, can you also let us know if you're using fractional scaling, and if the issue still reproduces at 100% scale? (In reply to Christoph Feck from comment #7) > Could be bug 477700. It seems to describe the same problem but with Dolphin instead of Konsole (In reply to John Kizer from comment #6) > Thanks - and just to double-check, does the issue reproduce on your system > within a newly-created user account? (Trying to rule out any possible > customization influence!) Great! It doesn't happen with a new user. What can I do to restart it? I have looked for more information. My username is knight. I think my configuration file is /home/knight/.config/dolphinrc Should I delete the contents of this text file? Or maybe delete the file? Thanks! (In reply to John Kizer from comment #8) > Great point - joseteluisete, can you also let us know if you're using > fractional scaling, and if the issue still reproduces at 100% scale? I'm using Global scale = 175% I've changed to 100% > Restarted > The problem disappeared When I've set again 175% the problem appeared again I'm going to try some other percentages Thanks! Global scale = 100%, 200% ... everything OK! Global scale = 150%, 175% ... the problem comes back I'll keep 200%. It's too big for me but I think I'll get used to it. Do you want me to try something else? Thanks a lot to everybody! That's perfect - I think that at least establishes then that what you're experiencing here is the same core issue as in bug 477700, manifesting in Dolphin (that bug already shows versions of the issue impacting Konsole, KDevelop and elsewhere). Thanks! *** This bug has been marked as a duplicate of bug 477700 *** |