I'm seeing what sounds like exactly the same thing as Ovidiu. Run "Root Terminal" from the GNOME Shell menu. It pops up a box asking for my password, then launches GNOME Terminal fine.
If I then exit this terminal subsequent attempts pop up the password dialog then once that's entered seem to do nothing. "su"ing to root from a terminal and running "gnome-terminal" manually I get: root@mixian:~# gnome-terminal Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 1 An xterm fires up fine. If I manually run gnome-terminal-server then it works: root@mixian:~# /usr/lib/gnome-terminal/gnome-terminal-server & [1] 16893 root@mixian:~# gnome-terminal root@mixian:~# The discussions about D-BUS made me take a closer look at that. It turned out in ~root/.dbus/session-bus/ I had 2 files; one which was a few months old and one of which was created yesterday. Both had the same hex basename but the older ended -1 and the newer -0. I killed the "dbus-launch --autolaunch=<hexbase>" daemon running as root and cleaned out both those files and tried to launch the terminal from GNOME Shell again. That worked fine. Additionally quitting the terminal and trying again also worked fine. As a result I'm currently led to believe the issue was caused by crud lying around from an old root DBUS session. I will follow up to this bus if I see the issue again having done this cleanup. J. -- Web [ 101 things you can't have too much of : 12 - Volume. ] site: http:// [ ] Made by www.earth.li/~noodles/ [ ] HuggieTag 0.0.24
signature.asc
Description: Digital signature
