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
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
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
Bugs, whi
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
>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 annoy
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
Bugs, which is subscribed
> 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 us
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.
Tha
** 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 b
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?" o
** 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, bu
> 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-se
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
im
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.l
> 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 config
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-termi
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 have the same problem after upgrade from Intrepid to Jaunty.
>
> I don't know of this i
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 :
> Thus I still thing gnome-terminal should work without gconf
>
> --
> Cannot start gnome
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
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.
> 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
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
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
Bugs, which is subscribed
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-termin
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.
-
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.
--
> 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
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)
T
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 triage
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
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 issu
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 anoth
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
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
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 anothe
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?
>
@ 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 a
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
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
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
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 workaroun
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 th
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 f
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 becaus
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
** 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://bu
** 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
Bugs, wh
47 matches
Mail list logo
