gnome-mplayer-1.0.3 either migrates the gsettings-based configuration, or creates a new one in gconf: apps/gnome-mplayer/preferences/%gconf.xml (didn't dig too deep into this), although gconf is supposed to be disabled according to bug #364513. In case this is not easily reproducible: I ran gnome-mplayer, played a movie, viewed the settings (but didn't change any), then exited.
Do you have dconf installed ? If not, install it and login again (so that /etc/profile is sourced and proper value for GSETTINGS_BACKEND is set).
Maybe I used incorrect terminology - I don't mind gnome-mplayer using gconf (vs. installing another configuration backend, that is). I was just surprised that gnome-mplayer-1.0.0 seemed to use XDG_CONFIG_HOME/gnome-mplayer/gnome-mplayer.conf, and 1.0.3 uses gconf backend (via GSettings, apparently). If it's the correct behavior, then please close this bug.
+ 27 Sep 2011; Samuli Suominen <ssuominen@gentoo.org> + gnome-mplayer-1.0.4.ebuild: + Fix missing gnome-base/dconf RDEPEND wrt #383729 by "Faustus"
Hi, did you add an unconditional dconf dependency? I think it's wrong, since choosing a GSettings backend is up to the end-user. It's probably not a bug, but a confusion on my side wrt. how GSettings works.
(In reply to comment #4) > Hi, did you add an unconditional dconf dependency? I think it's wrong, since > choosing a GSettings backend is up to the end-user. It's probably not a bug, > but a confusion on my side wrt. how GSettings works. Yes I did. With gconf being deprecated, what else there is than dconf? I'm not in business of providing broken packages to users, so unless you have another backend in mind... this is fixed
Gconf is deprecated? I don't get it. My understanding is that it's up to the user which backend to use. Which package depends on dconf? E.g., gedit-2.30.4 - depends on gconf, gedit-3.0.6 - doesn't depend on gconf or dconf. From dconf's site: "dconf is a low-level configuration system. Its main purpose is to provide a backend to GSettings on platforms that don't already have configuration storage systems".
Moreover, depending on dconf changes the behavior of the whole system. This doesn't make any sense. I suggest reverting the change and closing as notabug.
I'm getting tired of this bug reopening... stop doing that. Quoting gecko-mediaplayer/gnome-mplayer upstreama from bug 366695, comment #12 "My recommendation is you are seeing problems, use the --without-gconf option when configuring gecko-mediaplayer and gnome-mplayer. If you have GTK 2.26 or higher, ensure you have dconf installed as gecko-mediaplayers settings may not be saved otherwise." I've asked you to present another non-deprecated configuration backend, than dconf, and none was provided so the dep stays.
I am reopening the bug because you ignore what I'm saying, and refuse to clarify what you are saying, treating me as a nuisance. Moreover, I think that you are wrong about GConf vs GSettings and dconf. 1. Comment #12 doesn't say that gconf can't be the backend, it says that GSettings should be used, and that dconf should be probably installed for settings to be saved. But what I observed is that settings are saved just fine in GConf DB, *via* GSettings. There is no evidence that having GConf as the underlying configuration backend to GSettings triggers the aforementioned bug. Using GConf backend via GSetting is not the same as configuring with --with-gconf. 2. The bug is in Chromium, not in gecko-mediaplayer, or in gnome-mplayer. Now, I don't use gecko-mplayer in Chromium, so why should I be forced to install dconf? That doesn't make any sense. At most, the dconf dependency should be configured by a USE-flag, same USE-flag should be present in gecko-mplayer, and Chromium should depend on that USE-flag in gecko-mediaplayer. That's if my understanding of the issue is correct after reading the numerous bug reports, and *assuming* that you are right about the equivalence of --with-gconf and using GConf via GSettings, which I think you are not. 3. Gentoo is supposed to be about choice. You are deciding, without thinking twice, that a bug in Chromium w.r.t. gecko-mediaplayer integration means that gnome-mplayer should unconditionally pull in dconf, changing the behavior of the *whole* system. Again, that doesn't make any sense.
No, I'm making the decision based on that gconf is obsolete and shouldn't be used anymore where possible, leaving us with one singular, non-obsolete backend, which is dconf.
So why don't other packages that have been ported to GSettings don't depend on dconf directly?
(In reply to comment #11) > So why don't other packages that have been ported to GSettings don't depend on > dconf directly? Based on resolution of bug 375101 propably by mistake as gnome, gnome-light and gnome-settings-daemon are keeping it installed for Gentoo GNOME developers and users.
Ok, I see, thanks.
*** Bug 387351 has been marked as a duplicate of this bug. ***
Created attachment 292237 [details] gnome-mplayer-1.0.4-r1.ebuild Why not use the ~/.config/gnome-mplayer/gnome-mplayer.conf file As it is possible (see attached ebuild) why privating users of this ?
