settings not being saved/written

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install gnome-mplayer
2. Change any of the interface settings
3. Restart gnome-mplayer
4. Recheck if your settings got saved.

What is the expected output? What do you see instead?
Mplayer settings are saved normally but settings for Gnome-mplayer itself are 
not. In fact the gnome-mplayer.conf file is non-existant.

What version of the product are you using? On what operating system?
Gnome-mplayer svn 2108 on Arch Linux

Original issue reported on code.google.com by 31337H4c...@gmail.com on 25 May 2011 at 7:01

[GoogleCodeExporter]

Are you sure that the settings are not being stored in dconf?

gnome-mplayer.conf is only used when gconf is not found or disabled. With gtk 
2.26 or higher gsettings is used for storing settings and that is typically 
stored in dconf.

As of this moment I cannot duplicate your issue. Can you please post the output 
of gnome-mplayer -v 

Original comment by kdeko...@gmail.com on 25 May 2011 at 7:26

[GoogleCodeExporter]

Here is my output:

~ $ gnome-mplayer -v
GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not 
be saved or shared with other applications.
GNOME MPlayer v1.0.4beta
read mplayer config values: vo = gl2
Running with GIO support
Using audio device: 
The volume on 'Default' is 1.000000
Using match: type='signal',interface='com.gnome.mplayer'
Using match: type='signal',interface='org.gnome.SettingsDaemon'
Using match: type='signal',interface='org.gnome.SettingsDaemon.MediaKeys'
Proxy connections and Command connected

Original comment by 31337H4c...@gmail.com on 25 May 2011 at 8:03

[GoogleCodeExporter]

Well there is your problem.... looks like your Gsettings isn't configured to 
use any type of permanent storage. You can force it to use gconf with

./configure --enable-gconf

If you need me to make a option to force the keystore I can do that, but I was 
hoping to depreciate that storage method.

Original comment by kdeko...@gmail.com on 25 May 2011 at 8:20

[GoogleCodeExporter]

How would I change gsettings to use permenent storage? I am using awesomewm btw.

Also why use dconf/gconf instead of a simple config file?

Original comment by 31337H4c...@gmail.com on 25 May 2011 at 8:30

[GoogleCodeExporter]

gsettings is built into gtk/glib so it is probably the way you built it.

Why use dconf/gconf, well because that is the recommended way of storing 
settings in GTK. 

AwesomeWM has nothing to do with this problem.

Original comment by kdeko...@gmail.com on 25 May 2011 at 8:40

[GoogleCodeExporter]

Well I realized the problem is that I did not have dconf installed. Now my 
settings are saved, so thanks for the help.

Original comment by 31337H4c...@gmail.com on 25 May 2011 at 9:11

[GoogleCodeExporter]

Closing as client issue...

Original comment by kdeko...@gmail.com on 25 May 2011 at 9:15

• Changed state: Done

[GoogleCodeExporter]

Issue 525 has been merged into this issue.

Original comment by kdeko...@gmail.com on 17 Jun 2011 at 11:54

[GoogleCodeExporter]

Sorry, I looked for this problem before post issue 525 but I did not find. I 
should have looked better.

Well, I installed the package "dconf-gsettings-backend" and now the preferences 
are being saved.

I use Debian, but it should work too with ubuntu.

Thanks

Original comment by gilberto...@gmail.com on 17 Jun 2011 at 2:54

[GoogleCodeExporter]

is not related to gnome-mplayer, an alternative to using dconf would be
to defined
GSETTINGS_BACKEND=gconf
in your environment

Original comment by wileyh...@gmail.com on 15 Apr 2014 at 10:49