Description of problem: Since updating to mageia 2, nautilus does not save changes in the configuration. During the update, it did not transfer the previous configuration, instead using a global default. Sometimes certain changes will be applied, such as configuration of the desktop via nautilus menu:edit:preferences. But in all cases, if one exits and re-enters the configuration, the settings are reverted to the initial default. The settings can be accessed via - nautilus menu:edit:preferences -- changes made here are not saved, and usually not respected. - mageia main menu:tools:system_tools:dconf_editor:org:gnome:nautilus -- changes made here are generally saved, but seem to be never respected. It seems to be referring to 2 different files, since the values set often do not correspond. Version-Release number of selected component (if applicable): nautilus-3.4.1-1.mga2 (same as source rpm) How reproducible: Always, for a particular setting via the same point of access. Steps to Reproduce: 1. Change a setting to see if it changes the behavior of nautilus. Usually it has no effect, depending on which setting was changed. 2. Change a setting via the nautilus menu, then exit and re-enter. The change was not saved. Settings of particular interest are : - default folder view (always icon view) - display hidden and backup files (not displayed) - zoom level for icon/compact/list views (always 100% except list = 50%) - date display format (always traditional unix) - columns displayed in list view, and order - display text in icons, thumbnail images Interestingly, if a particular folder is set via nautilus menu:display, the configuration of the folder in question is correctly applied, even though the configuration shown at this point is not saved. (It always reverts to the original nautilus default.) But the changes apply to no other folder, unless displayed as a subfolder in the same window. The configuration of the specific folder persists after reboot. But it is a bit onerous to reconfigure many thousands of folders one at a time. Note that this only applies to part of the problem.
Assignee: bugsquad => olav
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD
Still a problem in Mageia 3
Status: RESOLVED => REOPENEDVersion: 2 => 3Resolution: OLD => (none)
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: REOPENED => RESOLVEDResolution: (none) => OLD