Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

messes up with dconf settings even when the user didn't change anything #732

Open
GoogleCodeExporter opened this issue Sep 20, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
  0) start dconf-editor
  1) reset all gnome-mplayer/gecko-mediaplayer preferences to their defaults
  2) quit dconf-editor
  3) start gnome-mplayer
  4) enter its preferences dialog window and just take a look around
     (without changing anything)
  5) exit from the dialog window
  6) quit gnome-mplayer
  7) start dconf-editor

What is the expected output? What do you see instead?
 many settings are again marked as manually-changed (in boldface font),
 even though almost all of these are actually equal to their default
 value; some values are indeed non-default (such as audio-lang, for
 instance).
 I do not experience this awkward behavior, if I skip steps 4 and 5.

What version of the product are you using? On what operating system?
 Debian Jessie - gnome-mplayer version: 1.0.8-1

Please provide any additional information below.
 Debian Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711118

 gnome-mplayer internal configuration dialog
 window does something strange to ~/.config/dconf/user ...
 I don't think it should save anything to the configuration file, if I
 haven't changed any setting at all! In other words, the configuration
 file should stay absolutely untouched, unless I actually changed
 something.

 And anyway, it should not mark settings as manually-changed, if I
 haven't changed them manually.

 Finally, it should not set some options to non-default values (such as
 audio-lang, for instance), if I haven't done anything to them.

Original issue reported on code.google.com by rossgamm...@gmail.com on 10 May 2015 at 6:26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant