[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Changed in: dbus Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/328575 Title: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal- emulator) because of gconf error To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/328575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Changed in: gconf Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/328575 Title: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal- emulator) because of gconf error To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/328575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Changed in: dbus Status: Fix Released = Confirmed ** Changed in: dbus Importance: Critical = Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/328575 Title: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal- emulator) because of gconf error To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/328575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Changed in: dbus Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/328575 Title: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal- emulator) because of gconf error To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/328575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Changed in: gnome-terminal Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/328575 Title: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal- emulator) because of gconf error To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/328575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Changed in: dbus Importance: Unknown = Critical -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/328575 Title: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal- emulator) because of gconf error -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Changed in: dbus Importance: Critical = Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/328575 Title: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal- emulator) because of gconf error -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Changed in: gnome-terminal Importance: Unknown = Wishlist -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Changed in: gconf Importance: Unknown = Medium -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
I had the same problem as Brian Murrell in post #74. I have fixed the bug for the past two releases by commenting out the broken code in terminal.c. The test for gconf using gconf_ping_daemon() failed if the program was being called over an ssh connection. When I tried to compile the 2.29.6 source from the Ubuntu source the make command failed didn't compile. The error message was: gnome-terminal-2.29.6/src/terminal-window.c:3330: undefined reference to `GTK_WIDGET_REALIZED' collect2: ld returned 1 exit status I am puzzled about the failure to build. It appears that the binaries for gnome-terminal in 10.4 may have been built against a different release. The solution was to download the 2.29.92 release,and build it. The comment at line 451 of src/terminal.c describes the fix that was made in this release. Here are the steps required to build and install this release: Download the gnome-terminal-2.29.92.tar.gz from https://launchpad.net /gnome-terminal/main/2.29.92: wget http://launchpad.net/gnome-terminal/main/2.29.92/+download /gnome-terminal-2.29.92.tar.gz Get tools for building deb packages: sudo apt-get install autotools-dev fakeroot dh-make build-essential checkinstall unpack tarball and enter the source directory: tar -xzf gnome-terminal-2.29.92.tar.gz cd gnome-terminal-2.29.92/ build, and install the deb: ./configure make sudo checkinstall The new gnome-terminal will be installed in /usr/local/bin. -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
This bug still exists on Lucid: karmic-pc $ ssh lucid-pc gnome-terminal Failed to get the session bus: Failed to connect to socket /tmp/dbus-B95HmT1Dsv: Connection refused Falling back to non-factory mode. Failed to summon the GConf demon; exiting. Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-B95HmT1Dsv: Connection refused) This is what, 3 releases in a row now that this bug has persisted? $ apt-cache policy gnome-terminal gnome-terminal: Installed: 2.29.6-0ubuntu5 Candidate: 2.29.6-0ubuntu5 Version table: *** 2.29.6-0ubuntu5 0 500 http://apt.interlinx.bc.ca/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Branch linked: lp:ubuntu/jaunty-proposed/gnome-terminal -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
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 * Backport f41c3d14 from upstream to try to start gconf before assuming it's not there (LP: #328575) -- Evan Broder bro...@mit.edu Sat, 22 Aug 2009 13:00:55 -0400 ** Changed in: gnome-terminal (Ubuntu Jaunty) Status: Fix Committed = Fix Released -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
I too loaded the jaunty-proposed package last week and it fixed my problems. Many thanks to the team for tracking this down and creating a fix. I once again have my root terminal with a different color font, launched from a toolbar button. :) Regards, Jim Evans -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Tags added: verification-done ** Tags removed: verification-needed -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
Update manager downloaded and installed the fix this morning. Everything works fine now. Lotsa thanks! -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
According to the bug description this problem is fixed in Karmic. ** Also affects: gconf2 (Ubuntu Jaunty) Importance: Undecided Status: New ** Also affects: gnome-terminal (Ubuntu Jaunty) Importance: Undecided Status: New ** Changed in: gnome-terminal (Ubuntu) Status: Triaged = Fix Released -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
Seems this isn't a bug in gconf, just a problem in how g-terminal uses gconf. ** Changed in: gconf2 (Ubuntu) Status: Triaged = Invalid ** Changed in: gconf2 (Ubuntu Jaunty) Status: New = Invalid -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
Accepted gnome-terminal into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: gnome-terminal (Ubuntu Jaunty) Status: New = Fix Committed ** Tags added: verification-needed -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Changed in: debian Status: Unknown = Fix Released -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
I'm not sure if this is important or not, but thought I'd add just in case... I just discovered the problem in Ubuntu Jaunty running Root Terminal, something I rarely do. I installed the jaunty-proposed package as described by Martin, and at first, it gave me a blank screen. Then, I noticed that if I resized the window, it would redraw and be OK. This only happens with the root terminal, run gksu; it seems as if using sudo from a terminal works OK, and using gksu from a terminal sometimes worked, I believe (when it didn't re-prompt for the password). But, I remembered I had tried out a Window Rule using a Compiz Window Management plugin that resized gnome terminal windows. After disabling this rule, the Gnome terminal worked normally at all times. -- [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Summary changed: - Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error + [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error ** Description changed: + Binary package hint: gnome-terminal + + IMPACT: gnome-terminal will fail to launch under any circumstance where + gconfd isn't already running. This can include `sudo gnome-terminal` + (since no gconfd is running for root), or starting gnome-terminal under + a non-GNOME window manager. + + DEVELOPMENT: The Debian maintainer added 02_let_gconf_autostart.patch in + 2.26.2-2 to solve this issue (debbugs #531734). That version has been + merged into Karmic. + + PATCH: Patch available at http://launchpadlibrarian.net/30671489/gnome- + terminal_2.26.0-0ubuntu2.1.debdiff, with test builds in + https://launchpad.net/~broder/+archive/ubuntu-tests. The upstream gnome- + terminal maintainer rejected the patch used for + 02_let_gconf_autostart.patch, because it reintroduced gnome-bugs + #561663. The attached patch instead cherry-picks the commit the + maintainer added to fix this bug upstream. + + INSTRUCTIONS: Attempt to run `sudo gnome-terminal`. It will exit with + Failed to contact the GConf daemon; exiting. + + REGRESSION: Seems limited - this is a cherry-pick of an upstream change + that only changes a handful of lines. + + + Original bug description: + I cannot start gnome-terminal. If I open an xterm and start gnome- terminal from the command line, here is what I get: $ sudo gnome-terminal Failed to contact the GConf daemon; exiting. (original report didn't have sudo in this command, but a later comment by the submitter amended this.) $ ps ax | grep gconf 3956 pts/0R+ 0:00 grep gconf 6643 ?S 0:00 /usr/lib/pulseaudio/pulse/gconf-helper 6647 ?S 0:06 /usr/lib/libgconf2-4/gconfd-2 This is in Jaunty Alpha 4 with all updates current as of 12 Feb. This bug is now understood. Read all the comments (or at least try some text searches) before adding your own, because a lot of things have already been covered. summary of some stuff posted in comments: gnome-terminal on purpose refuses to start if it can't connect to gconfd to get its config settings. gconf clients now find the server using DBUS. Starting gnome-terminal as root doesn't work even when you have all the gnome bits and pieces running under your account, because DBUS is per-user. executive of summary: We know what is going on. Everything that doesn't work is a consequence of the design. Everything is working as designed, although obviously there are problems with this design. Discussion about the design probably belongs on freedesktop-bugs #17970 (link in the remote bug sidebar). Workarounds to use until the bugs are fixed: for the gconfd-not-running case: start gconfd. e.g. add /usr/bin/gnome-settings-daemon to your X session startup script, ahead of any gnome-terminal commands. This applies whatever window manager you happen to be using. (except if you're using Ubuntu's default GNOME desktop, which already starts gconfd itself.) multiple tabs over ssh: use screen(1) $ sudo aptitude install screen screen-profiles # if you don't have it already The default config has unhelpful keybindings. I'm used to ^t as the command key, and F11/F12 as next/previous tab (screen calls them windows). I set up my own .screenrc before screen-profiles was packaged, so I don't know if its examples and samples are good or not. If you insist on displaying a GUI over X11 over ssh, there are other terminal emulators with tabs, e.g. the lighter-weight mrxvt. (be careful, though: it doesn't support UTF-8.) You might also investigate ssh -M for connection sharing. As I understand it, this lets you tunnel multiple sessions over one SSH connection, so only one password prompt... You could presumably get a local gnome-terminal going with ssh connections in each tab. root shells: You can use sudo inside a gnome terminal that's running under your own account. sudo -s, sudo -i, sudo su, and sudo bash are all variations on getting a shell running as root. If you don't know which to pick, use sudo -s. Or, better, don't start a root shell, and simply use sudo or gksudo on the one or two commands that need it. This bug is partly that gconf requires DBUS, which breaks some remote- GUI situations, and partly that gnome-terminal just refuses to start without gconf, even though some people have found that it actually works if they comment out that part. Armed with this knowledge, this bug shouldn't be more than a minor inconvenience, esp. if you're not dealing with ssh. (GNU screen takes some time to get used to...) I hope it's ok that I turned this bug's description into a guide on how to deal with it. Please correct any inaccuracies. --
