Sort setting change does effect only after restart Dolphin Reproducible: Always Steps to Reproduce: 1. Open Dolphin and open its settings dialog 2. On left site select "General", change "Sorter mode" and apply the change Actual Results: Previous setting is still working until Dolphin is restarted Expected Results: New setting works immediately
Confirmed.
There is no need to restart. It is enough to close and open again the settings dialog. But the bug is still valid. For developers: According to GammaRay, dolphin has two objects GeneralSettings (but it should be a singleton!), one created in: return QUrl::fromUserInput(GeneralSettings::homeUrl(), QString(), QUrl::AssumeLocalFile); in dolphin/src/global.cpp (47) and the other created in: mainWindow->openDirectories(urls, splitView); in dolphin/src/main.cpp (151) ... loadSortingSettings(); in src/kitemviews/kfileitemmodel.cpp (60)
*** Bug 407078 has been marked as a duplicate of this bug. ***
it's still reproducible with Dolphin 19.08 RC on Arch Linux. 1. open Dolphin 2. press ctrl+shift+, to open Dolphin preferences 3.. change "Sorting mode" in "General" section 4. click 'OK" button Actual Results: Previous sorting mode is still working until Dolphin is restarted Expected Results: New sorting mode works immediately Operating System: Arch Linux KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0
Looking into this, and it seems like the issue is that the GeneralSettings object is not emitting the sortingChoiceChanged signal when the sorting choice is actually changed. It does emit the sortingChoiceChanged signal when the dialog is opened, which is why reopening the settings dialog applies the sorting. This is connected to the KFileItemModel slot slotSortingChoiceChanged. The GeneralSettings class is generated by the dolphin_generalsettings.kcfg file, so it seems weird that it isn't emitting signals correctly. That should be automatic? Jamie Torres's comment above suggests that there are two instances of the GeneralSettings singleton, so perhaps they're both emitting the signal at different times, and the one that is emitting it when the dialog is opened but not when the setting is changed is the one that is being connected to the KFileItemModel?
*** Bug 420555 has been marked as a duplicate of this bug. ***