Ticket #342 (closed defect: fixed)

Opened 15 years ago

Last modified 15 years ago

Non-GNOME sessions' terminals are broken in Jaunty

Reported by: geofft Owned by: broder
Priority: normal Milestone: Fall 2009 Release
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:  LP:328575  GNOME:564649  DebianBug:531734


Essentially all non-GNOME sessions want you to start off with a terminal, which Debian makes sure is x-terminal-emulator, which is gnome-terminal. At some point between Intrepid and Jaunty, gnome-terminal started failing to launch if gnome-settings-daemon isn't running, rather than just launching with vaguely ugly default settings. This is pretty poor for the usability

We should figure out what's going on here, and work around it somehow, e.g.:

  • Figure out if there's a setting or environment variable to make the lack of gnome-settings-daemon noncritical, or to make it spawn if needed.
  • Start gnome-settings-daemon in every session.
  • Make the non-GNOME sessions use xterm instead.

Change History

comment:1 Changed 15 years ago by jdreed

If this means that, e.g. the Failsafe Terminal session doesn't work, we should also report that upstream.

comment:2 Changed 15 years ago by quentin

This only happens if gnome-terminal is the very first GNOME app you launch in your session; it explicitly checks whether a gconfd is running and bails if it isn't. Other apps just use gconf without checking, and it obliges them by spawning a new gconfd. This is upstream at  https://bugs.launchpad.net/ubuntu/+source/gconf2/+bug/328575

The maintainer of gnome-terminal says this is fixed in 2.27.91; maybe we can prod Ubuntu into doing a backport and/or cherrypick the patch?

comment:3 Changed 15 years ago by broder

Is there some ultra-secret source repo for gnome-terminal that I don't know about?

All I can find is  http://git.gnome.org/cgit/gnome-terminal/refs/. The most recent version it lists is; I can't find a 2.27.91 anywhere, and that seems entirely out of style with the other tags.

comment:4 Changed 15 years ago by geofft

The ultra-secret sources for 2.27.91 are at

comment:5 Changed 15 years ago by broder

  • Upstream bug set to LP:328575 GNOME:564649 DebianBug:531734

Ok, figured it out.

2.27 is active development, which actually corresponds to master in the git repo. The commit in question that fixes this is  f41c3d14bdfd533109d7d75bdbb2e2a0ab59b60c f41c3d14.

However, the Debian gnome-terminal maintainer added the distinctly less clever patch 02_let_gconf_autostart.patch in 2.26.2-2, which has now been merged into Karmic, fixing the bug (which was also tracked as  DebianBug:531734). This is basically equivalent to  GNOME:564649#c5 on the upstream bug.

I'm not sure whether to backport the Debian fix or the upstream fix for an SRU. I'd also kind of like to cherry-pick the upstream fix into Ubuntu since it's less dumb. And Debian, for that matter.

comment:6 Changed 15 years ago by broder

Err...Trac ate the commit. That's  f41c3d14

comment:8 Changed 15 years ago by jdreed

  • Status changed from new to assigned
  • Owner set to broder

comment:9 Changed 15 years ago by broder

  • Status changed from assigned to closed
  • Resolution set to fixed
This bug was fixed in the package gnome-terminal - 2.26.0-0ubuntu2.1

gnome-terminal (2.26.0-0ubuntu2.1) jaunty-proposed; urgency=low

Just went into jaunty-updates today, so this should be fixed.

Note: See TracTickets for help on using tickets.