You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run dconf-editor and set the "excluded-uris" setting in org.mate.disk-usage-analyzer.preferences to some directory. I placed 'file:///home/monsta/Dropbox' there (note the single quotes and the uri format).
Open the preferences window in mate-disk-usage-analyzer. Actually, you can open it before changing anything in dconf-editor - it doesn't matter.
Close the preferences window.
See the "excluded-uris" setting in dconf-editor resetting to the default (empty).
Reproduced in Debian Jessie with MATE 1.9 (from git master).
Note: this is not related to that GLib 2.43 issue - it's reproducible with GLib 2.42 just fine.
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9470194-mate-disk-usage-analyzer-closing-prefs-window-resets-the-excluded-uris-setting-to-the-default-empty?utm_campaign=plugin&utm_content=tracker%2F1509859&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1509859&utm_medium=issues&utm_source=github).
The text was updated successfully, but these errors were encountered:
monsta
changed the title
mate-disk-usage-analyzer
mate-disk-usage-analyzer: closing prefs window resets the "excluded-uris" setting to the default (empty)
Mar 12, 2015
Steps to reproduce:
'file:///home/monsta/Dropbox'
there (note the single quotes and the uri format).Reproduced in Debian Jessie with MATE 1.9 (from git master).
Note: this is not related to that GLib 2.43 issue - it's reproducible with GLib 2.42 just fine.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9470194-mate-disk-usage-analyzer-closing-prefs-window-resets-the-excluded-uris-setting-to-the-default-empty?utm_campaign=plugin&utm_content=tracker%2F1509859&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1509859&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: