Oh no, dbus-launch back again, a week or two back I posted on similar problem, I forgot what I posted about then but su -
came up, I was not happy about the su -
however the problem disappeared after the next update a few days later.
Thank you, su -
does work and on top I found it was indeed root .bashrc
that I accidentally got and could never find again. Content of root .bashrc
I recognised the 'export' lines at the bottom and the 'nice' panel must have been small kwrite
export USERNAME ENV PATH
# Source global definitions
if [ -f /etc/bashrc ]; then
# This line was appended by KDE
# Make sure our customised gtkrc file is loaded.
export PS1='\[\033[01;31m\][\u@\h \W]\$\[\033[00m\] '
Now I think I can reconstruct how I got it too, I was going through all the terminals to check the response and one of them I may have worked in su mode it seems, when applying kwrite, I was randomly using 'kwrite' or 'kwrite .bashrc' well in the past now.
Trying to recreate how I could have used su - I have tested various combinations of starting konsole/terminals:
Root Terminal is an option in menu I checked that command was: gksu /usr/bin/xvt I could not help testing this in normal terminal which did not like that.
[gert@localhost ~]$ gksu /usr/bin/xvt
QMetaObject::invokeMethod: No such method Konsole::Application::loadCommandLineOptionsForNewInstance()
Now that was mild response, I tried in su mode (not su -)
[root@localhost gert]# gksu /usr/bin/xvt
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: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
<unknown program name>(10772)/: KUniqueApplication: Cannot find the D-Bus session server: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
<unknown program name>(10765)/: KUniqueApplication: Pipe closed unexpectedly.
I have removed 2 of the GConf Errors I received. Is that verbose for "use su-" or "dbus-launch"
Yes the command works in a su - session. Perhaps I will be convinced that an alias for su may be more time saving that insisting on minimal tweaks, the problem I see next upgrade I will forget these tweaks.