[dolphin] [Bug 430969] New: Dolphin doesn't remember places panel width

David Abreu bugzilla_noreply at kde.org
Wed Dec 30 07:06:53 GMT 2020


https://bugs.kde.org/show_bug.cgi?id=430969

            Bug ID: 430969
           Summary: Dolphin doesn't remember places panel width
           Product: dolphin
           Version: 20.12.0
          Platform: Neon Packages
                OS: Linux
            Status: REPORTED
          Severity: grave
          Priority: NOR
         Component: panels: places
          Assignee: dolphin-bugs-null at kde.org
          Reporter: adabreug94 at gmail.com
                CC: kfm-devel at kde.org
  Target Milestone: ---

Created attachment 134394
  --> https://bugs.kde.org/attachment.cgi?id=134394&action=edit
Case1

Dolphin doesn't remember places panel width in several situations.

1. Open Dolphin, set a width for the places panel. Open another instance of the
app, note that the width of the places panel has been reset.

2. Open Dolphin, set a width for the places panel. Close Dolphin. Once is
opened again the width of the places panel has been reset.

3. Open Dolphin, put it in Maximized mode. Open Dolphin once again (a new
window), resize the app to fit the space from the right or left edge of the
screen to half the width of the screen, or maybe from bottom or top edge to
half height of thee screen. Resize back to Maximized, it has loosen the panel
width.  

Only case when dolphin preserve its places panel width is when opening a
window, set the width, open a new window (which doesn't inherits the places
panel width) , close the first one, keeping the second one open, open a third
one, this one does inherit the places panel width set in the first one (already
closed).

EXPECTED RESULT
I would expect dolphin to remember the width of places panel, at least for
common windows sizes as the maximized state of the app.

SOFTWARE/OS VERSIONS

Sistema operativo: KDE neon 5.20
Versión de KDE Plasma: 5.20.4
Versión de KDE Frameworks: 5.77.0
Versión de Qt: 5.15.2

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list