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 702070 - Settings migration from 3.4 to 3.8 incomplete
Settings migration from 3.4 to 3.8 incomplete
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: Profiles
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-06-12 10:24 UTC by Laurent Bigonville
Modified: 2013-06-21 08:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
GConf dump (1.49 KB, text/plain)
2013-06-12 12:09 UTC, Laurent Bigonville
Details
dconf dump (591 bytes, text/plain)
2013-06-12 12:15 UTC, Laurent Bigonville
Details
Gconf dump from 2nd machine (2.57 KB, text/plain)
2013-06-12 19:33 UTC, Laurent Bigonville
Details

Description Laurent Bigonville 2013-06-12 10:24:24 UTC
Hi,

Yesterday I've upgraded gnome-terminal (on debian unstable) from 3.4.1.1 to 3.8.2 and today when I booted my machine again and opened gnome-terminal, part of my profile settings were restored to the defaults.

The "Use system theme color" checkbox was checked again. The value in the "Predefined color" dropmenu was still good, so it only was a matter of unticking the checkbox again.

Also, the name of the profile is now "Unamed" instead of "Default" but this is probably minor.
Comment 1 Christian Persch 2013-06-12 12:00:38 UTC
Can you please attach a dump of the dconf and gconf settings?

$ gconftool-2 --dump /apps/gnome-terminal
$ dconf dump /org/gnome/terminal/
Comment 2 Laurent Bigonville 2013-06-12 12:09:03 UTC
Created attachment 246618 [details]
GConf dump
Comment 3 Laurent Bigonville 2013-06-12 12:15:17 UTC
Created attachment 246620 [details]
dconf dump

I'm not sure this is relevant as I changed things in it afterward
Comment 4 Laurent Bigonville 2013-06-12 12:33:08 UTC
OK I've reset the dconf config (dconf reset -f /org/gnome/terminal/) and then ran the /usr/lib/gnome-terminal/gnome-terminal-migration tool again.

"dconf dump /org/gnome/terminal/" is now giving me

[legacy]
schema-version=uint32 3
Comment 5 Christian Persch 2013-06-12 13:59:51 UTC
Is that dconf dump in comment 3 from the fresh migration?
Comment 6 Christian Persch 2013-06-12 15:30:32 UTC
Also, do these commands return both 'false' ?

$ gconftool-2 --get /apps/gnome-terminal/profiles/Default/use_theme_colors
$ gconftool-2 --get --ignore-schema-defaults /apps/gnome-terminal/profiles/Default/use_theme_colors
Comment 7 Laurent Bigonville 2013-06-12 15:45:01 UTC
Yes both are returning false

About comment 5, as said this was not directly after the migration
Comment 8 Christian Persch 2013-06-12 15:57:08 UTC
Then I don't see any way that the use_theme_colors dconf pref could have ended up anything but 'false'.

As for "Unnamed", that might happen if 

$ gconftool-2 --get --ignore-schema-defaults /apps/gnome-terminal/profiles/Default/visible_name

returned unset. I guess in that case could use "Default" instead of "Unnamed" for the default profile's name, but that's a string change and can't be done for 3.8 only 3.10.
Comment 9 Laurent Bigonville 2013-06-12 16:23:40 UTC
> gconftool-2 --get --ignore-schema-defaults /apps/gnome-terminal/profiles/Default/visible_name

Is returning "Par défaut"
Comment 10 Laurent Bigonville 2013-06-12 19:33:33 UTC
Created attachment 246667 [details]
Gconf dump from 2nd machine

Alright, on my computer at home it's working as expected
Comment 11 Christian Persch 2013-06-20 19:53:47 UTC
Using "Default" for default profile name (if unset) on master now.

Looking at the code, the other problem (system colours) shouldn't be happening, so no idea what went wrong. If you see it again (unlikely), please re-open.
Comment 12 Laurent Bigonville 2013-06-20 22:15:11 UTC
Well the most noticeable difference between the gconf config that was successfully migrated and the one that didn't is the lack of: 


    <entry>
      <key>global/profile_list</key>
      <value>
        <list type="string">
            <value>
              <string>Default</string>
            </value>
        </list>
      </value>
    </entry>


Couldn't this be related?
Comment 13 Christian Persch 2013-06-21 08:48:17 UTC
Don't think so. The migration code uses gconf_client_get() which consults the gconf schema if there's no explicit value set, and the schema has that key as ["Default"].