[Bug 532511] Re: terminal settings messed up after upgrade due to forced profile change

2010-03-26 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-terminal - 2.29.6-0ubuntu5 --- gnome-terminal (2.29.6-0ubuntu5) lucid; urgency=low * Revert the previous changes to add a new profile, as changing the default profile on upgrade is suboptimal, and there are better ways to implement

[Bug 532511] Re: terminal settings messed up after upgrade due to forced profile change

2010-03-25 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/gnome-terminal/ubuntu -- terminal settings messed up after upgrade due to forced profile change https://bugs.launchpad.net/bugs/532511 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in

[Bug 532511] Re: terminal settings messed up after upgrade due to forced profile change

2010-03-25 Thread Chris Coulson
** Changed in: gnome-terminal (Ubuntu Lucid) Status: In Progress = Fix Committed -- terminal settings messed up after upgrade due to forced profile change https://bugs.launchpad.net/bugs/532511 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 532511] Re: terminal settings messed up after upgrade due to forced profile change

2010-03-23 Thread Chris Coulson
I'm taking a slightly different route with this now. I'm going to drop all the changes to the profile, and instead make it possible to control the visual appearance of the terminal from the GTK theme. It's already possible to control the background / text colours from the GTK theme, but

[Bug 532511] Re: terminal settings messed up after upgrade due to forced profile change

2010-03-05 Thread Martin Pitt
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/40234695/Dependencies.txt ** Changed in: gnome-terminal (Ubuntu) Assignee: (unassigned) = Chris Coulson (chrisccoulson) ** Tags added: regression-potential ** Also affects: gnome-terminal (Ubuntu Lucid) Importance:

[Bug 532511] Re: terminal settings messed up after upgrade due to forced profile change

2010-03-05 Thread Martin Pitt
Oh, before filing this bug report I manually flipped the default profile back to Default (the /apps/gnome-terminal/global/default_profile key). I'm pretty sure it was Ambience after the upgrade (at least that's what the terminal Profiles.. dialog showed). If necessary I can dig out my older gconf

[Bug 532511] Re: terminal settings messed up after upgrade due to forced profile change

2010-03-05 Thread Chris Coulson
** Changed in: gnome-terminal (Ubuntu Lucid) Importance: Undecided = High ** Changed in: gnome-terminal (Ubuntu Lucid) Status: New = Triaged -- terminal settings messed up after upgrade due to forced profile change https://bugs.launchpad.net/bugs/532511 You received this bug

[Bug 532511] Re: terminal settings messed up after upgrade due to forced profile change

2010-03-05 Thread Martin Pitt
Those are my gconf settings (snippet from ~/.gconf/%gconf-tree.xml) from yesterday's backup. ** Attachment added: original gconf settings http://launchpadlibrarian.net/40235420/gnome-terminal.gconf-original.xml -- terminal settings messed up after upgrade due to forced profile change

[Bug 532511] Re: terminal settings messed up after upgrade due to forced profile change

2010-03-05 Thread Martin Pitt
My gconf tree only has changes for Default, but it doesn't have a custom gconf key for /apps/gnome-terminal/global/default_profile. So I assume I got the new default Ambience from the schema? -- terminal settings messed up after upgrade due to forced profile change

[Bug 532511] Re: terminal settings messed up after upgrade due to forced profile change

2010-03-05 Thread Oliver Grawert
confirming, i see the same after the theme upgrade -- terminal settings messed up after upgrade due to forced profile change https://bugs.launchpad.net/bugs/532511 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu.

[Bug 532511] Re: terminal settings messed up after upgrade due to forced profile change

2010-03-05 Thread Martin Pitt
Instead of creating a new profile and switching users to it, can we change the default profile in the schema instead? For that to work, we need to * fix g-t to not set user-specific keys unless you change them (it does right now) * change the migration patches to unset user specific keys if