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

[BananasGoMoo]

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

--- Comment #63 from BananasGoMoo <gdtcompwiz at aol.com> ---
(In reply to Méven from comment #62)
> To shed some light, affected people could you run and report the results of
> commands :
> 
> getfattr -d ~/Documents
> 
> And generally the folder concerned, after you have set non-default settings,
> and after you load the folder and reproduce the issue.
> The command may return nothing and that would be informative.

Prior to and after setting *just* the view setting to Icons, the output is
nothing.

if I also set "sort by -> modified" in addition to Icons view I get the
following:
getfattr: Removing leading '/' from absolute path names
# file: home/bananasgomoo/Documents
user.kde.fm.viewproperties#1="[Dolphin]\012SortRole=modificationtime\012Timestamp=2025,2,6,18,20,16.384\012Version=4\012ViewMode=1\012"

after resetting the sort by back to "name" (my default setting), the command
once again returns nothing.
so it is actively removing the attributes if only the view mode is changed.

> And
> 
> getfattr -d ~/.local/share/dolphin/view_properties/global
> cat ~/.local/share/dolphin/view_properties/global/.directory
> 
> When you have changed the default settings (that's where they are stored).
> The .directory file isn't supposed to be present.

getfattr -d ~/.local/share/dolphin/view_properties/global outputs the
following:
getfattr: Removing leading '/' from absolute path names
# file: home/bananasgomoo/.local/share/dolphin/view_properties/global
user.kde.fm.viewproperties#1="[Dolphin]\012Timestamp=2024,12,27,16,53,28.468\012Version=4\012ViewMode=1\012"

as expected, the .directory does not exist:
cat: /home/bananasgomoo/.local/share/dolphin/view_properties/global/.directory:
No such file or directory

> I will probably add verbose traces to dolphin, so that after a future
> release we will have more to work with.

that would be great. i feel like things are failing that arent being reported
in the current debug. or maybe branches not being triggered.

> > I'm a little concerned how this issue is so hard to reproduce, as I am using essentially stock KDE with stock Dolphin. I have done nothing special whatsoever and I have only modified the settings listed in this issue. All other settings are default
> 
> Don't be, as you have seen this requires some unknown conditions for the bug
> to manifest. The fact that you have a fresh install and most people aren't
> has probably to do with it or at least partly.
> Be patient please and diligent please, I am very much frustrated be assured.

reminds me of that recent issue with fonts of GTK apps where the change in
cache variables caused text to not display on people who's cache wasnt updated
recently lol

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