[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]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/dbus/dbus/issues/7. -- 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: Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
I've confirmed that installing Evan's package addresses this issue (i.e., that gnome-terminal starts with this patch applied, and doesn't produce any GTK warnings or other ill effects). -- 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. --
[Bug 328575] Re: Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Changed in: gnome-terminal (Ubuntu) Importance: Undecided = Low ** Changed in: gnome-terminal (Ubuntu) Status: New = Triaged ** Changed in: gnome-terminal (Ubuntu) Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs) -- 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: Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
Here's a patch that cherry-picks an upstream commit to fix this problem for Jaunty. ** Attachment added: gnome-terminal_2.26.0-0ubuntu2.1.debdiff http://launchpadlibrarian.net/30671489/gnome-terminal_2.26.0-0ubuntu2.1.debdiff -- 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: Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Bug watch added: GNOME Bug Tracker #564649 http://bugzilla.gnome.org/show_bug.cgi?id=564649 ** Also affects: gnome-terminal via http://bugzilla.gnome.org/show_bug.cgi?id=564649 Importance: Unknown Status: Unknown -- 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: Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Changed in: gnome-terminal Status: Unknown = Confirmed -- 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: Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- 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: Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Bug watch added: Debian Bug tracker #531734 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531734 ** Changed in: debian Importance: Undecided = Unknown ** Changed in: debian Status: New = Unknown ** Changed in: debian Remote watch: None = Debian Bug tracker #531734 -- 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: Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error
** Summary changed: - Cannot start gnome-terminal because of gconf error + Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error ** Tags added: gconf terminal -- 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: Cannot start gnome-terminal because of gconf error
It's not explictly stated here, but this also occurs for other users than root
(it's implict in the doesn't work over
ssh case).
For me, I run Ubuntu on my home PC with one user name, and have a
separate user for my work environment, which I generally access with `su
- other_user`. I was a bit flabbergasted when I couldn't launch a work
user terminal because of this issue, as I done this with gnome-terminal
on one of those other linux distributions in the past. I adapted the
dbus workaround shown above. I'm posting in case someone with the same
need but less shell scripting experience (not that this takes much)
finds it useful until this is fixed.
#!/bin/sh
eval `dbus-launch --sh-syntax --exit-with-session`
/usr/lib/libgconf2-4/gconfd-2
if [ -z $DISPLAY ]; then
DISPLAY=:0
export DISPLAY
fi
title=`whoa...@`uname -n`
cmd=gnome-terminal --disable-factory --sm-client-disable --window --title
\$title\
# open six tabs
tab_count=5
i=0
while [ $i -lt $tab_count ]
do
i=`expr $i + 1`
cmd=${cmd} --tab --title \${title}\
done
eval $cmd /dev/null /dev/null 21
--
Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
I just noticed this behavior in an update to Jaunty from Intrepid. If it is not a bug then it is a feature and should be in a change log somewhere. I liked being able to click on a root terminal icon, give it my password and be presented with a root terminal. I guess I can just as easily su to root. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
franik4ever - have you got the link to the Debian bug report so it can be tracked here, seeing as you added the Debian task? -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
** Also affects: debian Importance: Undecided Status: New -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
What is 'interesting' is that I don't see any gnome program except gnome-terminal that needs that workaround Not 100% convinced about this. I've had lots of gksu nautilus commands mysteriously failing lately (from ALT-F2). Exact same behaviourrequests password and then nothing. The annoying thing is that it happens randomly I can't duplicate it right now. :( Might just be a co-incidence...but its been annoying me for some time now. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
Thank you, whoever added the workaround guide to the bug description. It was concise and extremely helpful. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
I've tried to make it more clear that this should be considered a bug. I am very pleased: I didn't expect a positive/constructive reaction. This is great work, now it's up to gnome/gconf developers. Isn't it just providing settings that were configured when you still used GNOME? I never used GNOME on this installation =) If you had an empty ~/.gnome* and ~/.gconf*, wouldn't you get the same defaults as when gconfd isn't running at all? (try moving those directories aside before deleting them). I had .gnome2 and .gnome2_private directories in ~/, which I renamed before running gnome-settings-daemon. Didn't change anything, gnome-settings-daemon is still taking over. Moreover, my custom Openbox key bindings for XF86AudioPrev, XF86AudioNext, etc. don't work anymore once gnome-settings-daemon has been launched (even after g-s-d is killed). I guess really you just need gconfd, which is started by gnome-settings-daemon. Does running /usr/lib/libgconf2-4/gconfd-2 change your themes and fonts? Or only g-s-d? If it's ok, then you could update the workaround to suggest just that, instead of g-s-d. Running this doesn't change anything, and, in fact, it exits immediately : -- tsubaka ~ # /usr/libexec/gconfd-2 [1] 12114 tsubaka ~ # (press enter) [1]+ Exit 1 /usr/libexec/gconfd-2 tsubaka ~ # -- Olivier Sessink provided a working way to launch gconfd-2 and then gnome-terminal, as root ( https://bugs.launchpad.net/ubuntu/+source/gconf2/+bug/328575/comments/42 ): The problem is that there is no session-dbus. The following lines of shell code start a session dbus, start gconfd and start the gnome-terminal #!/bin/sh eval 'dbus-launch --sh-syntax --exit-with-session' /usr/lib/libgconf2-4/gconfd-2 gnome-terminal add it to a script, and start the script. So in my case, it's a no-go for gnome-terminal, and I'm off using xfce's terminal emulator, which is just fine, and lightweight too =) -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
Huh.. no it's not okay to turn it into a guide.. People have been using gnome-terminal as root for years. Lecturing them on the dangerousity of their ways is just an excuse not to fix the bug. I do not mean to attack you personally, but I just hate it when people say why do you do that anyway? or it's much better if you do it the other way when there is a real bug. While I understand Ubuntu is targeted at the general public (including very, very dumb users), well not only dumb users use it, I guess. Those should have the freedom to launch gnome-terminal as root, knowing and accepting the risk. As for me, I have turned to x11-terms/terminal (gentoo package terminology), which is the xfce terminal emulator. It has nearly all features from gnome-terminal, without the wont-launch-as-root bug. But I seriously hope this bug is fixed upstream in gnome-terminal. Additionally, running gnome-settings-daemon is not always an acceptable workaround, since it messes up with gtk+ themes, desktop background, etc. Gnome is a trustworthy partner, but an invasive ex. (ie. when you just want to stay friends = just run gnome applications) As a conclusion, well, I guess a guide is better than nothing. Thanks for that effort already. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
** Description changed: 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: + 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: - 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 on the one or two commands that need it. e.g. - $ ls - $ less foo.conf - $ sudo editor foo.conf - (or gksudo editor foo.conf, if your editor of choice is opens it's own window instead of running inside the terminal) - $ ls .. - $ sudo mv foo bar - $ sudo # error permission denied - $ echo 10 | sudo tee /proc/sys/vm/swappiness # sudo tee is a way to accomplish echo 10 file with the file-open happening as root. - - Root is dangerous: a typo could break things much more easily than - without sudo. The fewer things running as root, the better. It's not - usually necessary to run a terminal emulator as root, just things that - use that terminal. Even when you're doing a sysadmin thing, you - probably run lots of info-gathering commands that don't need root. Save - sudo for the commands that need it. + 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. -- Cannot start gnome-terminal 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
[Bug 328575] Re: Cannot start gnome-terminal because of gconf error
BlueSky wrote: Lecturing them on the dangerousity of their ways is just an excuse not to fix the bug. I do not mean to attack you personally, but I just hate it when people say why do you do that anyway? or it's much better if you do it the other way when there is a real bug. Thanks for the comments. You're right, I went way overboard with the lectures against running too much as root, when all that was called for in that space was workarounds that would let people do the things they wanted to. I see how that would give the impression that it's actually the user's fault, not a bug (which is not the case.) I've tried to make it more clear that this should be considered a bug. e.g. Workarounds: - Workarounds to use until the bugs are fixed:. Although I did already try to make it clear that this is still a bug, not just simply the new way that GNOME works. OTOH, unless gnome-terminal will just work without gconf, this bug will probably take a long time to get fixed, since it's the result of the design, not just a problem implementing it correctly. That's what I was trying to make clear, and prepare people for a long wait. It's true that my workarounds for root and remote usage cases are what I do anyway, and I do in fact consider them better than actually running gnome-terminal as root, or remote-displaying it. That's what makes them such great workarounds... (esp. since I'm a command line guy, and I always have gnome-terminal open, and usually have a shell already cd'ed to whatever directory I want to do something in... This is not the case for everybody, e.g. the people who want to start a shell from nautilus. That's fine, use your computer however you want, as long as it's not a security disaster that's going to have your computer infected and trying to crack mine and relaying spam.) Without the big lecture, I'm probably less likely to put people off actually trying anything I suggested. running gnome-settings-daemon is not always an acceptable workaround, since it messes up with gtk+ themes, desktop background, etc Isn't it just providing settings that were configured when you still used GNOME? If you had an empty ~/.gnome* and ~/.gconf*, wouldn't you get the same defaults as when gconfd isn't running at all? (try moving those directories aside before deleting them). I guess really you just need gconfd, which is started by gnome-settings-daemon. Does running /usr/lib/libgconf2-4/gconfd-2 change your themes and fonts? Or only g-s-d? If it's ok, then you could update the workaround to suggest just that, instead of g-s-d. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
I'm having this gconf error from a regular account. I use fluxbox. Here's the command throwing the error. x-terminal-emulator -T Bash -e /bin/bash --login This issue seems to resolve itself after some usage. I suspect gphpedit fires up the gonf daemon properly. I like to fire up my terminals immediately after login though, and dropping to a text terminal (ctrl- alt-F1) to fire up a terminal is really annoying. I'm not knowledgeable about EUIDs or some of the other crazy stuff above, but I think they are related to the root user, which is not what I'm trying to use. I just want to open a terminal! And I'd rather not change the terminal I'm used to. The main purpose of this message is to point out that this is NOT just a su issue. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
The main purpose of this message is to point out that this is NOT just a su issue. Right, it's an X11-without-gconf issue. See my post, above, for my workaround for fluxbox. Like you, I use fluxbox and gnome-terminal. It's a simple matter of getting gconf running. I do it by running gnome-settings-daemon in my .fluxbox/startup. (startx does start DBUS, so gnome stuff can find itself once started.) BTW, ctrl-alt-f1 is not the simplest way. There are other viable terminal emulators you can start from the menu: Applications-Terminal Emulators-anything but gnome terminal. If you don't have any others installed, aptitude install xterm It's not very nice, but it works well as a failsafe. Or start any other GUI program that lets you run shell commands. e.g. emacs, and M-x shell. (and start gnome-settings-daemon that way.) -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
** Description changed: I cannot start gnome-terminal. If I open an xterm and start gnome- terminal from the command line, here is what I get: - $ gnome-terminal + $ 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: + 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: + 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 on the one or two commands that need it. e.g. + $ ls + $ less foo.conf + $ sudo editor foo.conf + (or gksudo editor foo.conf, if your editor of choice is opens it's own window instead of running inside the terminal) + $ ls .. + $ sudo mv foo bar + $ sudo # error permission denied + $ echo 10 | sudo tee /proc/sys/vm/swappiness # sudo tee is a way to accomplish echo 10 file with the file-open happening as root. + + Root is dangerous: a typo could break things much more easily than + without sudo. The fewer things running as root, the better. It's not + usually necessary to run a terminal emulator as root, just things that + use that terminal. Even when you're doing a sysadmin thing, you + probably run lots of info-gathering commands that don't need root. Save + sudo for the 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. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
Still happening here with 9.04 and all the updates. I can confirm that it only keeps me from running a new gnome-terminal from the root account, users can. I can run other graphical shells like konsole or xterm with no trouble. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
I have the same problem after upgrade from Intrepid to Jaunty. I don't know of this is information is useful, but i experience this issue problem trying to start gnome-terminal from /etc/gdm/PostSession/Default. This script is run when the user logs out of the system. In Intrepid, a terminal pops out in front of the user, but it does nothing in Jaunty. The terminal does not start, and I get this very same error. What I don't understand is that the very same command works perfectly when started from /etc/gdm/PostLogin/Default. This script is run right after user logon. And when i try to run it between logon and logoff, manually from terminal, it also works. I tried the suggested workaround which seems to solve the problem when executed from /etc/gdm/PostSession/Default -- Cannot start gnome-terminal 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
Re: [Bug 328575] Re: Cannot start gnome-terminal because of gconf error
Let me be more accurate here. Gnome-terminal works fine, *ONLY* root terminal fails (gksu /usr/bin/x-terminal-emulator fails to execute). Hence, GConf may be error-free in this case. Quoting Maxim Levitsky maximlevit...@gmail.com: Thus I still thing gnome-terminal should work without gconf -- Cannot start gnome-terminal because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a direct subscriber of a duplicate bug. This message was sent using IMP, the Webmail Program of Haifa University -- Cannot start gnome-terminal 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
Re: [Bug 328575] Re: Cannot start gnome-terminal because of gconf error
Let me be more accurate here. Gnome-terminal works fine, *ONLY* root terminal fails (gksu /usr/bin/x-terminal-emulator fails to execute). Hence, GConf may be error-free in this case. Quoting Alwin Roosen i...@alwinroosen.be: I have the same problem after upgrade from Intrepid to Jaunty. I don't know of this is information is useful, but i experience this issue problem trying to start gnome-terminal from /etc/gdm/PostSession/Default. This script is run when the user logs out of the system. In Intrepid, a terminal pops out in front of the user, but it does nothing in Jaunty. The terminal does not start, and I get this very same error. What I don't understand is that the very same command works perfectly when started from /etc/gdm/PostLogin/Default. This script is run right after user logon. And when i try to run it between logon and logoff, manually from terminal, it also works. I tried the suggested workaround which seems to solve the problem when executed from /etc/gdm/PostSession/Default -- Cannot start gnome-terminal because of gconf error https://bugs.launchpad.net/bugs/328575 You received this bug notification because you are a direct subscriber of a duplicate bug. This message was sent using IMP, the Webmail Program of Haifa University -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
Aviv here is some clarification: $ ls -l /usr/bin/x-terminal-emulator lrwxrwxrwx 1 root root 37 2009-04-27 14:01 /usr/bin/x-terminal-emulator - /etc/alternatives/x-terminal-emulator $ ls -l /etc/alternatives/x-terminal-emulator lrwxrwxrwx 1 root root 31 2009-04-27 14:00 /etc/alternatives/x-terminal-emulator - /usr/bin/gnome-terminal.wrapper -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
I'm just re-confirming the same problem with today's latest updates (May 6, 2009). I only run *UBUNTUs now. I'm curious if this bug has cropped up on other distributions, eg RedHat, Suse, etc., or is it just in the UBUNTU family? If it isn't general then maybe its a *UBUNTU configuration quirk. Heya, just got there from Google, I report that I have the same problem under Gentoo, from updates today. I am aware it's not the place to report Gentoo bugs, just letting you know you're not the only ones having the bug. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
I'm just re-confirming the same problem with today's latest updates (May 6, 2009). I only run *UBUNTUs now. I'm curious if this bug has cropped up on other distributions, eg RedHat, Suse, etc., or is it just in the UBUNTU family? If it isn't general then maybe its a *UBUNTU configuration quirk. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
The problem is that there is no session-dbus. The following lines of shell code start a session dbus, start gconfd and start the gnome- terminal #!/bin/sh eval 'dbus-launch --sh-syntax --exit-with-session' /usr/lib/libgconf2-4/gconfd-2 gnome-terminal add it to a script, and start the script. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
I didn't work, until I caught on the typo (ticks instead of backticks). Here is the corrected script: #!/bin/sh eval `dbus-launch --sh-syntax --exit-with-session` /usr/lib/libgconf2-4/gconfd-2 gnome-terminal Now it does indeed work. I can gksudo this script and can also invoke it remotely. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
Indeed. as a workaround one can create /usr/local/bin/gnome-terminal with the above code: #!/bin/bash if [ $EUID = 0 ] ; then eval `dbus-launch --sh-syntax --exit-with-session` /usr/lib/libgconf2-4/gconfd-2 fi exec /usr/bin/gnome-terminal $* -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
Thus I still thing gnome-terminal should work without gconf -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
What is 'interesting' is that I don't see any gnome program except gnome-terminal that needs that workaround -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
What is 'interesting' is that I don't see any gnome program except gnome-terminal that needs that workaround In case of running programs over ssh, every gnome program that I tried is affected by this bug. For example nautilus: $ nautilus (nautilus:8367): Eel-WARNING **: GConf error: 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-SmPGlbnjCX: Connection refused) (nautilus:8367): Eel-WARNING **: GConf error: 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-68o2xY0A4a: Connection refused) GConf warning: failure listing pairs in `/apps/nautilus/preferences': 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-653EukrRMz: Connection refused)GConf warning: failure listing pairs in `/desktop/gnome/file_views': 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-7PdDqACLDB: Connection refused)GConf warning: failure listing pairs in `/apps/nautilus/desktop': 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-v4zT60f1OD: Connection refused)GConf warning: failure listing pairs in `/apps/nautilus/icon_view': 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-W31BvrdFGB: Connection refused) [etc... and crash] $ gnome-calculator GConf Error: 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-XL6x5ZWna8: Connection refused) [etc... and crash] I remeber that i tested also epiphany and update-manager, neither of them works without the above workaround. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
Sebastien, your comment seems to imply that Launchpad bug reports are a waste of time. Is this really what you meant? I had been under the impression that Launchpad was intended to be a gateway/portal for bug reporting. If Launchpad reports do not get forwarded upstream automatically once triaged then what purpose does it have? -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
For some sense that seems to be true, I often find out that reporting bugs upstream is better. Yet, this also usually doesn't help, bugs just remain in bugzilla, and nobody fixes them. Thus the only way to fix the bugs is just grok the code, and fix them up myself. (No matter how hard that is) This bug is an exception, as the 'real' fix for it might involve some big changes in way root applications are handled There is nothing wrong with the above, linux just has few users and developers, and I feel that majority of linux users, just use it because they have to for one or another reason, and will thus use it as little as possible (eg run in VM, try cygwin, bring own laptop with windows, as a backup, etc...) This is sad. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
your comment seems to imply that Launchpad bug reports are a waste of time. Is this really what you meant? I had been under the impression that Launchpad was intended to be a gateway/portal for bug reporting. If Launchpad reports do not get forwarded upstream automatically once triaged then what purpose does it have? No, the issue is just that the number of bug reports and issues is just high for the team working on those so it might take some time to get issues triaged, confirmed, sent upstream etc. If you know what you are doing you are welcome to speed the process by sending the bug upstream too rather than waiting on overworked triagers to pick it for you -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
Having just upgraded to Jaunty from Intrepid, I have arrived at this cannot do 'gksu gnome-terminal' bug. How did this happen? What change was made Intrepid - Jaunty that broke this oft used (even if some people consider it the wrong thing to do) feature? I really am not looking for workarounds, I am looking for this not to have been broken in the first place. This problem has clearly been known about since the beginning of this year and still Jaunty was released with the bug for us unsuspecting people to get hit by. This really does need to be considered as a security bug and fixed asap: the whole point of using this idiom is that it requires the password and it gives a new type of terminal so that it can be coloured differently from other terminals to show it is a dangerous terminal. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
This bug affects more applications. please fix it asap. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
I just upgraded to Ubuntu 9.10 on two machines and both exhibit the same problem when attempting to open a root terminal via the built in gksu command. The suggestion to use: gnome-terminal -e sudo -i is not sufficient for me, as I defined a different default profile for the root user which has a different text color (to visually differentiate a normal terminal from a su terminal) and the root profile is not loaded using this workaround. Very annoying that a built in option like Root terminal was broken by the 9.10 upgrade -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
** Tags added: regression-release -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
@ Adam Yao: could you please be more specific? Are you meaning that you've found some applications other than the root terminal which undergo this GConf's issue, or that the fact the terminal is unusable affects other activities of yours? Or maybe referring to something you read on other pages about this same bug? Just to know. Thanks :) -- Cannot start gnome-terminal 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
Re: [Bug 328575] Re: Cannot start gnome-terminal because of gconf error
On Wed, 2009-04-29 at 13:39 +, Pibo wrote: @ Adam Yao: could you please be more specific? Are you meaning that you've found some applications other than the root terminal which undergo this GConf's issue, or that the fact the terminal is unusable affects other activities of yours? Or maybe referring to something you read on other pages about this same bug? Just to know. The problem is that this affects way more than just gksu gnome-terminal. It also makes it impossible to do: $ ssh -Y jaunty_system gnome-terminal As you can see, where I may launch 12 other terminals or tabs (i.e. from the New Terminal/Tab menu options) from that one gnome-terminal, using 12 or more ssh -Y commands is simply an unacceptable work-around. I want the functionality of the gnome-terminal on the remote machine, not on my local machine. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
Been following these comments -- all the while finding myself more and more dumbfounded. This bug is over two months old. Never mind the new notification system -- people want to get some serious work done and here's some essential functionality that, well. isn't functioning. There's another bug there: how could a much anticipated release make it out the door, even with this fundamental breakage already having been reported? bjd -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
While I agree with most of stuff said here, lets not turn this bug into
a flame war.
I want to repeat myself, that commenting out this:
in terminal.c:
/* If the gconf daemon isn't available (e.g. because there's no dbus
* session bus running), we'd crash later on. Tell the user about it
* now, and exit. See bug #561663.
*/
if (!gconf_ping_daemon ())
{
g_printerr (Failed to contact the GConf daemon; exiting.\n);
exit (1);
}
made it work for me
--
Cannot start gnome-terminal 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
Re: [Bug 328575] Re: Cannot start gnome-terminal because of gconf error
I do not see how commenting that out is a good idea if that comment is correct. Instead, it appears to me to be a bug in the gconf_ping_daemon. If the gnome-terminal can run just fine under sudo, then the gconf_ping_daemon should be using the actual user ID, not the effective user ID to try to get the running gconf process. Since I know for a fact that I am running X and GConf is accessible, then this function does not appear to be detecting the daemon correctly. -- Cannot start gnome-terminal 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
Re: [Bug 328575] Re: Cannot start gnome-terminal because of gconf error
On Wed, 2009-04-29 at 17:44 +, bjd wrote: Been following these comments -- all the while finding myself more and more dumbfounded. This bug is over two months old. More and more bugs lately seem to befall this fate sadly, of just lingering on and on and nothing being done. There's another bug there: how could a much anticipated release make it out the door, even with this fundamental breakage already having been reported? Because it was time. Sadly, in this day and age, releases are made based on squares on a calendar, not on suitability of release. To be sure, much work is put into trying to make the release stable by the time that square on the calendar comes up but it doesn't always happen. The square comes and the release has to be made. While this does not seem to have been a problem in the past, the past couple of releases of both Ubuntu and evolution seem to have fallen victim to it's time and not it's ready. Hopefully this changes in that the release date is allowed to slip or more hands are put into getting it ready by that release date or less ambitious are set for releases. It's one of those old pick two songs. In this case the three choices are on time, feature packed, stable. Pick two. b. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
the best way to get that bug worked would be to opened a bug against the concerned software to the software writters on bugzilla.gnome.org, ubuntu only distribute it, the quality comments are not useful, the usecase described there is just not the most common one and technical users having the issue should be able to help and send that to GNOME early -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
With all due respect Sebastien -- I can hardly believe that I'm reading this: ubuntu only distribute it. (why even have a bug reporting system in the first place, one wonders, btw.). -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
I also have this problem: gksu /usr/bin/x-terminal-emulator ...does not work, displays Failed to contact the GConf daemon /usr/bin/x-terminal-emulator ...works ok gksu gedit ...works ok -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
Aw crap! Now I'm going to have to go back to Intrepid. Not being able to open a gnome-terminal over an ssh connection is a show stopper for me! ~sigh~ It's been too long now since I have been able to do a Ubuntu upgrade and everything just works as well as it did before the upgrade. Please fix this ASAP. -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
** Bug watch added: freedesktop.org Bugzilla #17970 https://bugs.freedesktop.org/show_bug.cgi?id=17970 ** Also affects: dbus via https://bugs.freedesktop.org/show_bug.cgi?id=17970 Importance: Unknown Status: Unknown -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
** Changed in: dbus Status: Unknown = In Progress -- Cannot start gnome-terminal 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: Cannot start gnome-terminal because of gconf error
Same problem, gksu gnome-terminal and sudo gnome-terminal not start the Terminal! gnome-terminal is ready for use the Terminal! Fix this Bug Please!!! -- Cannot start gnome-terminal 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: Cannot start gnome-terminal bcause of gconf error
gnome-settings-daemon doesn't help: I do: # sudo -i $ gnome-settings-daemon $ gnome-terminal and it still fails with same message It did work fine in 8.10 Now I can't open it nether from root nautilus or from remote share and can't open like I said above -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
Copy of my posting in Bug #326158 in Ubuntu: As far as I 'm concerned it's not a big issue, a (temporary?) solution is simple. Add a starter to the taskbar (or your menu) with: gnome-terminal -e sudo -i and the terminal starts immediately asking for your password. As long as you keep that terminal open you will have root-permissions in it. Gr, Jim -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
@Jim, this isn't what makes it fail. The problem is that if I launch nautilus as root, I can't open terminal from it. I strongly suspect this bug prevents above from working -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
I did some brief look, and discovered a workaround, or maybe even a fix:
The message you see comes from gnome-terminal, but it can work fine
without gconf, or maybe check for it is broken:
in terminal.c:
/* If the gconf daemon isn't available (e.g. because there's no dbus
* session bus running), we'd crash later on. Tell the user about it
* now, and exit. See bug #561663.
*/
if (!gconf_ping_daemon ())
{
g_printerr (Failed to contact the GConf daemon; exiting.\n);
exit (1);
}
If I comment out this condition block, then it works just fine
--
Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
Maxim Levitsky wrote: QUOTE: @Jim, this isn't what makes it fail. The problem is that if I launch nautilus as root, I can't open terminal from it. Do'nt understand that, opening a terminal from within nautilus? But OK, I do understand that the real problem must be some bug in the gconf deamon so we will wait for the solution of that I suppose. Gr, Jim -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal because of gconf error
** Summary changed: - Cannot start gnome-terminal bcause of gconf error + Cannot start gnome-terminal because of gconf error -- Cannot start gnome-terminal 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: Cannot start gnome-terminal bcause of gconf error
I'm having the same error. I'm running Ubuntu 9.04 final. $ sudo gnome-terminal Failed to contact the GConf daemon; exiting. -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
Thanks to everyone for confirming that this happens under normal circumstances. No further confirmation is required. Just subscribe to the bug without making a post, unless you have anything new to add. (Correct me if I'm overstepping here, Ubuntu maintainers.) Further posts on this thread should be about what to do about this, or ideas for how the relevant programs and libraries should behave so gnome-terminal can start when gnome-settings-daemon isn't already running. I've always found it kind of messy the way KDE programs start daemons that clutter your terminal with log messages even after the first KDE program (that started them) has exitted. If it wasn't for the messages on stdout or stderr, it wouldn't be so bad. Obviously, you don't want to hide the messages either, so I don't really see any good solution. I guess it's something you get used to as a user, though. I start most of my long-lived GUI stuff from one screen(1) window, so only one window will get clogged with messages if any of them feel like spewing. So it would probably work to start any required daemons when they're needed. I don't see any obvious solution, if there's no way around requiring a daemon. Hmm, possibly if there's no daemon, read settings from a file yourself? Using the same code (in a library) that the daemon uses to get the settings? This might have to be read-only to avoid danger in case the daemon does start while gnome-terminal is running... -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
Hello Folks, I just encountered this problem during LiveCD Building with Ubuntu Customization Kit. I used Xubuntu CD image as base so far, always worked well - now with 9.04 rc / Ubuntu Edition this problem comes when selecting 'run console'. If unsolved, LiveCD building with UCK is jeopardized, unless the scripts get patched with a workaround as mentioned above. Will dive deeper now, just fyi. Regards, Daniel -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
Can put somebody this bug as medium-importance? It's a very nerving bug! Thx -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
Jaunty beta. affects me too, both if I run it with sudo and if I run it remotely with ssh: $ sudo gnome-terminal [sudo] password for paolo: Failed to contact the GConf daemon; exiting. $ ssh -Yf paolo gnome-terminal pa...@paolo's password: pa...@parroco:~$ Failed to contact the GConf daemon; exiting. Notably the issue is only with gnome-terminal. All other applications run well in both situations. Also when local pc = intrepid, remote = jaunty : running gnome-terminal with ssh = the same error -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
Affects me too. Jaunty with all updates -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
I noticed this problem because my .fluxbox/startup wasn't starting my gnome-terminal anymore. (that's a shell script run by startfluxbox that runs some X clients then execs /usr/bin/fluxbox. I put some of my startup stuff in it.) If I run /usr/bin/gnome-settings-daemon before gnome-terminal, then it works. If I leave that commented out, gnome-terminal refuses to start, with the Failed to contact the GConf daemon; exiting. error message everyone's reporting. Obviously when gnome-terminal is run as root, there's no root-owned gconf daemon for it to talk to. (BTW, why would you want to do that? sudo -s not good enough?) I already had /usr/bin/gnome-settings-daemon in my fluxbox startup, but I used to run it as gnome-terminal --geometry=132x30 --tab-with-profile=default --tab-with-profile=default --tab-with-profile=default (sleep 1 setxkbmap -option ctrl:nocaps xset r rate 195 60 /usr/bin/gnome-settings-daemon ) I use sleep to spread out the disk I/O load of starting X a bit. gnome-terminal used to load, then after gnome-settings-daemon loaded, the font would switch to my configured font. But now my desktop was coming up with no terminal. gnome-terminal would work later, since by then gnome-settings-daemon would be started. So now I do /usr/bin/gnome-settings-daemon (sleep 1 gnome-terminal --geometry=132x30 --tab-with-profile=default --tab-with-profile=default --tab-with-profile=default ) (sleep 1 setxkbmap -option ctrl:nocaps xset r rate 195 60 ) and my X startup script should start everything nicely. If gnome stuff is going to require daemons, they should start them automatically if they're not running. KDE stuff does that. If GNOME can come up with a convincing reason why this is a bad idea, then this is not a bug. Although it had better be documented, and the error message should suggest starting gnome-settings-daemon. So IMHO something has to change before this bug can be closed. -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
forgot to say that this is maybe not gconf2's bug, but rather a bug in things that use it. (esp. if the fix is a more useful error message.) -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
I confirm this bug with todays updates. It affects probably most of other GNOME programs. I tried epiphany, gnome-terminal, and update- manager and all of them fail, which makes them unusable over ssh. Is there some way to start the gconf manually? -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
Hi! Same for me on jaunty beta, can't open gnome terminal as root error message: Failed to contact the GConf daemon; exiting. -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
Have this issue also - anyone has an idea how to resolve it? Obviously gnome-terminal needs something from gconf, or expects it to run (in a special manner perhaps?)...hmm -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
** Bug watch added: GNOME Bug Tracker #555745 http://bugzilla.gnome.org/show_bug.cgi?id=555745 ** Changed in: gconf Status: New = Unknown ** Changed in: gconf Bugwatch: GNOME Bug Tracker #576346 = GNOME Bug Tracker #555745 -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
** Changed in: gconf Status: Unknown = New -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
I also have this bug.UbuntuJauty,all last updates Temporary solution $ gnome-terminal -e sudo -i -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: http://bugzilla.gnome.org/show_bug.cgi?id=576346 ** Changed in: gconf2 (Ubuntu) Status: Incomplete = Triaged ** Also affects: gconf via http://bugzilla.gnome.org/show_bug.cgi?id=576346 Importance: Unknown Status: Unknown -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
** Changed in: gconf Status: Unknown = New -- Cannot start gnome-terminal bcause 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: Cannot start gnome-terminal bcause of gconf error
does not work for me too # gksudo gnome-terminal Failed to contact the GConf daemon; exiting. # gksudo synaptic or # gksudo nautilus working. wanna have the root-terminal menu-entry enabled, but does'n work any solution? -- Cannot start gnome-terminal bcause 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
