[dolphin] [Bug 477662] New: Saved display style differ for a shared folder and symlink

Ivan Korytov bugzilla_noreply at kde.org
Tue Nov 28 09:24:47 GMT 2023


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

            Bug ID: 477662
           Summary: Saved display style differ for a shared folder and
                    symlink
    Classification: Applications
           Product: dolphin
           Version: 23.04.3
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: view-engine: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: boot.efi at yandex.ru
                CC: kfm-devel at kde.org
  Target Milestone: ---

STEPS TO REPRODUCE
1. Set option "View" to "Remember display style" in Dolphin configuration
2. Get in to a shared folder (e.g. /mnt/shares/Public), set view option to
Compact
3. Create symlink to that folder somewhere else (e.g.
/home/user/Desktop/Public)
4. Get in to a folder using symlink

OBSERVED RESULT
Display style in symlink (/home/user/Desktop/Public) is not the same as in
folder itself (/mnt/shares/Public).

EXPECTED RESULT
Display style in symlink is the same as in folder itself, because they are the
same folder, only path differs.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ALT Linux Workstation K 10.2 x86_64
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Dolphin creates a structure to hold .directory files for shared folders in
~/.local/share/dolphin/view_properties and it confirms that it differentiates
between folder and symlink by storing separate settings for them.

For other directories, e.g. ~/Downloads, there is no such behavior, because
.directory file created in the directory itslef, not in "view_properties". For
shared folders, keeping the .directory files separate should be more
convenient, because user doesn't always have access to write in the root of the
shared folder.

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


More information about the kfm-devel mailing list