GNOME Bugzilla – Bug 582234
gnome-terminal doesn't launch after gconf update
Last modified: 2018-08-17 13:57:10 UTC
Steps to reproduce: 1. Updated gconf from 2.26.0 to 2.26.1 2. gnome-terminal 2.26.1 doesn't launch anymore. I get this error if I try to start it from xterm: ** ERROR:terminal-app.c:1769:terminal_app_handle_options: assertion failed: (profile) Cancelled Stack trace: Other information: It worked fine with gconf 2.26.0 and it works if I go back to gconf 2.26.1. Actually I'm not sure if this is a bug with gnome-terminal or gconf. I don't know what other info to provide, if you need anything more, please ask.
Oops, sorry, I meant to write: "It worked fine with gconf 2.26.0 and it works if I go back to gconf 2.26.0"
Is there any difference in the output of this command: gconftool-2 -R /apps/gnome-terminal when run against gconf 2.26.0 and .1 ? Make sure the gconf daemon is killed beforehand so it's really running against the expected version.
No, the output is exactly the same for both 2.26.0 and 2.26.1.
Hmm. Did you also ascertain whether the gconftool-2 from 2.26.0 / .1 was used, and was linking against the .0 / .1 version of libgconf ?
Yes. gconftool-2 and libgconf are compiled and installed at the same time as gconfd anyway from the gconf sources.
Updated gconf to 2.26.2 and still have the same problem. Confirmed with multiple PCs too, so it's not only my system.
Could you clone gconf from git://git.gnome.org/gconf and bisect the changes between the "GCONF_2_26_0" and "2.26.1" tags to see which one exactly causes this problem?
Got it, it's 5a18e7925b73d0a5b7e84b42513e4e84bc2b14ff. Is this a gconf problem after all?
Let's try moving this to gconf... http://git.gnome.org/cgit/gconf/commit/?id=5a18e7925b73d0a5b7e84b42513e4e84bc2b14ff
CC'ing Behdad since he commited the change that apparently causes this (comment 8).
Doesn't make sense, that commit only adds or removes debugging lines. Something wrong with your bisect. Were you doing "make install" and test? If yes, that's broken, since apps link to the highest version installed. So you should remove the old installs...
Of course I was removing the old installs...
Anyway, that would be a heisenbug if that commit really causes the failure.
GConf has been deprecated since 2011. GConf is not under active development anymore. Its codebase has been archived: https://gitlab.gnome.org/Archive/gconf/commits/master dconf and gsettings are its successors. See https://developer.gnome.org/gio/stable/ch34.html and https://developer.gnome.org/GSettings/ for porting info. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of dconf/gsettings. Thanks!