[dolphin] [Bug 495878] New: Customizing the default view settings doesn't work anymore

Jan Rathmann bugzilla_noreply at kde.org
Wed Nov 6 14:57:08 GMT 2024


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

            Bug ID: 495878
           Summary: Customizing the default view settings doesn't work
                    anymore
    Classification: Applications
           Product: dolphin
           Version: git-master
          Platform: Other
                OS: Linux
            Status: REPORTED
          Keywords: regression
          Severity: normal
          Priority: NOR
         Component: view-engine: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: jan.rathmann at gmx.de
                CC: kfm-devel at kde.org
  Target Milestone: ---

SUMMARY
Configuring the default view settings for folders that have no individual view
settings doesn't work anymore currently, custom settings for the default view
seem to be just getting ignored by Dolphin.

STEPS TO REPRODUCE
1. Open Dolphin (build from master, or e.g. boot live image of openSUSE
Krypton).
2. Default view mode is "Symbols".
3. Create a fresh test folder, and fill it with content (an empty file is
sufficient).
4. Go to the folder above your test folder.
5. Enable menu bar (Ctrl+M)
6. Enable "Settings -> Configure Dolphin -> View -> Remember display style for
each folder"
7. Open "View -> Adjust View Display Style..."
8. Set "View mode" to "Details" and check "Use as default view settings", click
OK.
9. Go to the test folder.

OBSERVED RESULT
View mode of test folder is still set to "Symbols", despite "Details" was
configured in the steps before.

EXPECTED RESULT
View mode of test folder should be "Details", respecting the default view
settings made before.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.2.80
KDE Frameworks Version: 6.9.0 
Qt Version: 6.8.0

ADDITIONAL INFORMATION
Reproduced with:
* Dolphin build from master with kdesrc-build
* Dolphin from openSuse Krypton current live image running in a VM.

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


More information about the kfm-devel mailing list