After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 691347 - gnome-terminal doesn't start in jhbuild 3.8 session
gnome-terminal doesn't start in jhbuild 3.8 session
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: Profiles
git master
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-01-08 15:21 UTC by Volker Sobek (weld)
Modified: 2013-01-14 17:02 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Volker Sobek (weld) 2013-01-08 15:21:48 UTC
When I try to start gnome-terminal from gnome-shell in a 3.8 jhbuild session, it won't start.

Trying from another tty in a jhbuild shell I get:
 $ DISPLAY=:2 gnome-terminal
 Error creating terminal: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs:
 Profile "b1dcc9dd-5262-4d8d-a863-c897e6d979b9"

 $ gsettings get org.gnome.Terminal.Settings legacy-profiles
 ['5d0df8e9-feae-4e5a-a2f2-b4051bced6d8']

 $ gsettings get org.gnome.Terminal.Settings legacy-default-profile
 <some id that was different from the 5d0df8e9-feae-4e5a-a2f2-b4051bced6d8>

setting the org.gnome.Terminal.Settings schema version back to 0 and running the gnome terminal profile migrator from libexec had the same results (different IDs).

on IRC, chpe suggested to try the following change:
diff --git a/src/migration.c b/src/migration.c
index 686280a..670e79f 100644
--- a/src/migration.c
+++ b/src/migration.c
@@ -443,7 +443,7 @@ migrate_profiles (GError **error)
 
   profile_uuids = g_ptr_array_new_with_free_func ((GDestroyNotify) g_free);
 
-  dvalue = gconf_client_get_without_default (client, GCONF_GLOBAL_PREFIX "/default_profile", NULL);
+  dvalue = gconf_client_get (client, GCONF_GLOBAL_PREFIX "/default_profile", NULL);
   if (dvalue != NULL &&
       dvalue->type == GCONF_VALUE_STRING)
     default_profile = gconf_value_get_string (dvalue);

followed by resetting the schema version to 0 again and running the migrator again. This led to:

 $ gsettings get org.gnome.Terminal.Settings legacy-default-profile
 '221ae85b-fab2-4c1b-9c86-9789fc3f4249'
 $ gsettings get org.gnome.Terminal.Settings legacy-profiles
 ['221ae85b-fab2-4c1b-9c86-9789fc3f4249']

And now I'm able to start gnome-terminal form tty in a jhbuild shell:
 $ DISPLAY=:2 gnome-terminal

but it still doesn't start when I try to launch it from the dash in the jhbuild session.
Comment 1 Volker Sobek (weld) 2013-01-08 15:30:07 UTC
Not sure, but this is might just be some dbus issue with my jhbuild setup.
Comment 2 Christian Persch 2013-01-08 16:39:59 UTC
That last issue looks more like a jhbuild/dbus setup problem, yes. Since g-t is now using a client/server model, maybe it's just not finding the .service file?
Comment 3 Christian Persch 2013-01-08 22:24:49 UTC
The migration issue should be fixed on git master; please check.