Description of problem: The package gtk+-1:1.2.10-82.fc24.x86_64 is leaking of a dependency to dconf. Without dconf some functions of the GtkFileChooser won't work. Version-Release number of selected component (if applicable): 1.2.10 / f24 How reproducible: 100% Actual results: The command "dnf install gtk+" does not install dconf. Expected results: The command "dnf install gtk+" should install dconf too. Additional info: See: https://bugzilla.gnome.org/show_bug.cgi?id=768180
The https://bugzilla.gnome.org/show_bug.cgi?id=768180 ticket appears to be discussing gtk3 behavior, not gtk+ (gtk1). Is that what you meant? In Fedora 24, dconf is pulled in as a dependency by gnome-session amongst other things. Which desktop are you using? I could see an argument for gtk3 recommending (rather than requiring) dconf.
Which Fedora package is providing the GtkFileChooser chooser? Pleas discuss this with the Gnome team. (In reply to Paul Howarth from comment #1) > The https://bugzilla.gnome.org/show_bug.cgi?id=768180 ticket appears to be > discussing gtk3 behavior, not gtk+ (gtk1). Is that what you meant? I thought the gtk+ package is providing the GtkFileChooser. Is it an other package? > > In Fedora 24, dconf is pulled in as a dependency by gnome-session amongst > other things. Which desktop are you using? I use KDE/plasmashell and I'm not interested in installing to much of Gnome. But Firefox or GIMP depends on Gtk. > > I could see an argument for gtk3 recommending (rather than requiring) dconf. Fact is, since I've installed the missing dconf package, the file GtkFileChooser is remaindering it's settings. And beehives as it should while searching! Pleas discuss with the Gnome team, why dconf is needed.
triaging to gtk3 component
What will you do to fix the problems with the GtkFileChooser in the KDE-Spin?
I don't think gtk is the right place for a dependency. Providing a working backend for gsettings is really a responsibility of the overall desktop.
Re: comment #5 what is the recommended/preferred gsettings backend? Any objection to at least adding a Recommends: for it then?
(In reply to Rex Dieter from comment #6) > Re: comment #5 > > what is the recommended/preferred gsettings backend? > > Any objection to at least adding a Recommends: for it then? I don't think that is really a great direction to take. If we keep going that way, we end up with a Recommends: gnome in gtk3.
So... you expect all non-desktop/non-gnome DE's to know this (that a gsettings backend is needed) and choose one? How is that any better?
To put another way, you don't want to enforce via dependencies that gtk3 has a gsettings backend? What backends are available? What are the pros/cons of each?
(In reply to Rex Dieter from comment #9) > To put another way, you don't want to enforce via dependencies that gtk3 has > a gsettings backend? The question is inaccurate, but I'll answer it anyway: No, I don't.
We had a long (and heated! :) discussion about this on #fedora-workstation and ended up adding 'Recommends: dconf' in http://pkgs.fedoraproject.org/cgit/rpms/gtk3.git/commit/?id=b66fa3258228d5a8563c1d54990590d6cb9d5e86
How ever, fact is, fedora delivers a broken gkt-file-chooser if you execute "dnf install firefox" on the KDE-spin. I think a properly working file open and save dialogue is very essential for many desktops application. The dependency of gtk+ to dconf was just the way, the issue was fixed on our systems: By installing the dconf package. May there are better ways to fix it. But a not working file open and save dialogue in many very popular applications is a "no go". Really.