Root Terminal crashes and weird behaviour

[wedgetail]

Have a very simple test system: pclos2010.07 + fully updated + Opera + Kate basically nothing installed yet (no OOO)

I thought all was well, I never had any of "blakbird's topic" problems, only a small problem with konsole giving odd result, after last update but I have problem.

1.. Root terminal does not work. I can bring up login screen, for example using krunner (alt+F2) and gksu /usr/bin/xvt or any other way.
     As soon as I enter the password, my display shimmers unstable like towards the right and downward, not fatal just annoying.
     No terminal anywhere to be seen.

2.. The rest of the terminals can not open a kwrite session when in su mode.  Trying comes up with following result

Code: [Select]

[gert@localhost ~]$ kwrite
[gert@localhost ~]$ kwrite .bashrc
kwrite(10247)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing  "/usr/share/mime/magic"
kwrite(10247)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing  "/home/gert/.local/share/mime/magic"
[gert@localhost ~]$ su
Password:
[root@localhost gert]# kwrite .bashrc
kwrite(10321): Session bus not found

KCrash: Application 'kwrite' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/root/.kde4/socket-localhost.localdomain/kdeinit4__0

[1]+  Stopped                 kwrite .bashrc
[root@localhost gert]#

In normal mode I believe all terminals will open kwrite sessions.

I thought I had just discovered a new terminal mode, it looked like Xterm with white background but nicer presentation basically because of bigger fonts. Xterm has an annoying shimmer in the left side which was absent. This mode worked fine in su mode and brought up a bashrc file which automatically had some lines entered I could scream as this seems to be the only screen I did not document. I should have noted the extra in bashrc. Tried in vain to recreate condition.

Sequence: old-polack had kindly supplied some terminal color settings http://www.pclinuxos.com/forum/index.php/topic,77878.msg642675.html#msg642675 and instructions to open .bashrc:

Code: [Select]

[root@localhost gert]# kwrite .bashrc
Note that I happened to be in su mode, the reason I found out.

Then found there was no problem opening in in normal konsole mode, entered old-polacks data, this worked fine
 
John Bee came up with an addition for some modernisation of the terminal, I thought well I will stick this in as well and activate (one line at the time).

His did not work, but I had made a mistake an extra character had slipped in at the end of a ver very long line well off the screen.

After this I started checking every konsole/terminal  and found the su mode would not open kwrite the error is:

Executable: kwrite PID: 10321 Signal: 6 (Aborted)

Content of my bashrc is now:

Code: [Select]

# .bashrc

# User specific aliases and functions

# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi

#PS1="\[\e[0;1;36m\][\u@\h \[\e[0;1;33m\]\W\[\e[0;1;36m\]]$\[\e[0;1m\] $RESET"        # light blue

#PS1="\[\e[0;1;32m\][\u@\h \[\e[0;1;33m\]\W\[\e[0;1;32m\]]$\[\e[0;1m\] $RESET"         # green

#PS1="\[\e[0;1;35m\][\u@\h \[\e[0;1;33m\]\W\[\e[0;1;35m\]]$\[\e[0;1m\] $RESET"        # lavender

PS1="\[\e[0;1;34m\][\u@\h \[\e[0;1;33m\]\W\[\e[0;1;34m\]]$\[\e[0;1m\] $RESET"        # dark blue

#PS1="\[\e[0;1;31m\][\u@\h \[\e[0;1;33m\]\W\[\e[0;1;31m\]]$\[\e[0;1m\] $RESET"        # red

#PS1="\[\e[0;1;33m\][\u@\h \[\e[0;1;32m\]\W\[\e[0;1;33m\]]$\[\e[0;1m\] $RESET"        # yellow  - green pwd

# end of old-polack's entries

#PS1="\n\[\033[1;35m\]\$(/bin/date +%a\ %b\ %e\ %r\ %Z\ %Y)\n\[\033[0;36m\]\w\n\[\033[1;32m\]\u@\h: \[\033[1;34m\] \[\033[1;36m\]\$(/bin/ls -1 | /usr/bin/wc -l | /bin/sed 's: ::g') items \[\033[1;33m\]\$(/bin/ls -lah | /bin/grep -m 1 total | /bin/sed 's/total //')b\[\033[0m\] -> \[\033[0m\]"
Oh dear, oh dear that was not what my test system was ment for. 

[Old-Polack]

Have a very simple test system: pclos2010.07 + fully updated + Opera + Kate basically nothing installed yet (no OOO)

I thought all was well, I never had any of "blakbird's topic" problems, only a small problem with konsole giving odd result, after last update but I have problem.

1.. Root terminal does not work. I can bring up login screen, for example using krunner (alt+F2) and gksu /usr/bin/xvt or any other way.
     As soon as I enter the password, my display shimmers unstable like towards the right and downward, not fatal just annoying.
     No terminal anywhere to be seen.

2.. The rest of the terminals can not open a kwrite session when in su mode.  Trying comes up with following result

Code: [Select]

[gert@localhost ~]$ kwrite
[gert@localhost ~]$ kwrite .bashrc
kwrite(10247)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing  "/usr/share/mime/magic"
kwrite(10247)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing  "/home/gert/.local/share/mime/magic"
[gert@localhost ~]$ su
Password:
[root@localhost gert]# kwrite .bashrc
kwrite(10321): Session bus not found

KCrash: Application 'kwrite' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/root/.kde4/socket-localhost.localdomain/kdeinit4__0

[1]+  Stopped                 kwrite .bashrc
[root@localhost gert]#

In normal mode I believe all terminals will open kwrite sessions.

I thought I had just discovered a new terminal mode, it looked like Xterm with white background but nicer presentation basically because of bigger fonts. Xterm has an annoying shimmer in the left side which was absent. This mode worked fine in su mode and brought up a bashrc file which automatically had some lines entered I could scream as this seems to be the only screen I did not document. I should have noted the extra in bashrc. Tried in vain to recreate condition.

Sequence: old-polack had kindly supplied some terminal color settings http://www.pclinuxos.com/forum/index.php/topic,77878.msg642675.html#msg642675 and instructions to open .bashrc:

Code: [Select]

[root@localhost gert]# kwrite .bashrc
Note that I happened to be in su mode, the reason I found out.

Then found there was no problem opening in in normal konsole mode, entered old-polacks data, this worked fine
 
John Bee came up with an addition for some modernisation of the terminal, I thought well I will stick this in as well and activate (one line at the time).

His did not work, but I had made a mistake an extra character had slipped in at the end of a ver very long line well off the screen.

After this I started checking every konsole/terminal  and found the su mode would not open kwrite the error is:

Executable: kwrite PID: 10321 Signal: 6 (Aborted)

Content of my bashrc is now:

Code: [Select]

# .bashrc

# User specific aliases and functions

# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi

#PS1="\[\e[0;1;36m\][\u@\h \[\e[0;1;33m\]\W\[\e[0;1;36m\]]$\[\e[0;1m\] $RESET"        # light blue

#PS1="\[\e[0;1;32m\][\u@\h \[\e[0;1;33m\]\W\[\e[0;1;32m\]]$\[\e[0;1m\] $RESET"         # green

#PS1="\[\e[0;1;35m\][\u@\h \[\e[0;1;33m\]\W\[\e[0;1;35m\]]$\[\e[0;1m\] $RESET"        # lavender

PS1="\[\e[0;1;34m\][\u@\h \[\e[0;1;33m\]\W\[\e[0;1;34m\]]$\[\e[0;1m\] $RESET"        # dark blue

#PS1="\[\e[0;1;31m\][\u@\h \[\e[0;1;33m\]\W\[\e[0;1;31m\]]$\[\e[0;1m\] $RESET"        # red

#PS1="\[\e[0;1;33m\][\u@\h \[\e[0;1;32m\]\W\[\e[0;1;33m\]]$\[\e[0;1m\] $RESET"        # yellow  - green pwd

# end of old-polack's entries

#PS1="\n\[\033[1;35m\]\$(/bin/date +%a\ %b\ %e\ %r\ %Z\ %Y)\n\[\033[0;36m\]\w\n\[\033[1;32m\]\u@\h: \[\033[1;34m\] \[\033[1;36m\]\$(/bin/ls -1 | /usr/bin/wc -l | /bin/sed 's: ::g') items \[\033[1;33m\]\$(/bin/ls -lah | /bin/grep -m 1 total | /bin/sed 's/total //')b\[\033[0m\] -> \[\033[0m\]"
Oh dear, oh dear that was not what my test system was ment for.  

Try su - instead of su. Kwrite will then open just fine. but the .bashrc you will be opening will be that of root, not your normal user. If you want to open kwrite while using just su, the command would be dbus-launch kwrite.

[wedgetail]

old-polack
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 - and dbus-launch came up, I was not happy about the su - or dbus-launch  however the problem disappeared after the next update a few days later.

Thank you, su - and dbus-launch 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 window:

----------------------------
# .bashrc

PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/lib/kde4/libexec
ENV=$HOME/.bashrc
USERNAME="root"
export USERNAME ENV PATH

# Source global definitions
if [ -f /etc/bashrc ]; then
   . /etc/bashrc
fi

# This line was appended by KDE
# Make sure our customised gtkrc file is loaded.
export GTK2_RC_FILES=$HOME/.gtkrc-2.0
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.

Code: [Select]

[gert@localhost ~]$ gksu /usr/bin/xvt
/usr/bin/konsole
QMetaObject::invokeMethod: No such method Konsole::Application::loadCommandLineOptionsForNewInstance()
[gert@localhost ~]$

Now that was mild response, I tried in su mode (not su -)

Code: [Select]

[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.)
/usr/bin/konsole
<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.

[wedgetail]

Minor update done few minutes ago to my simple test system (pclos2010.07 LiveCD plus upgrade 16th August + opera + Kate:

In konsoles, I forgot to mention that "clear scrollback" is now gone when using right click and selection nothing  happens.

Can still be cleared by "clear" command  

[Old-Polack]

wedgeling:

Maybe this will help.

http://www.pclinuxos.com/forum/index.php/topic,71397.msg591547.html#msg591547

Read the thread, starting from this reply, as there is more later. In KDE 4.5 there has been a change in where the two konsole version choices are shown, but the functionality remains the same. Just poke around a bit to find them. I'm back on the non upgraded KDE desktop at the moment so I can't check and give a screen shot.

[wedgetail]

old-polack
Thank you, a ripper post again.    I got to bed even later I had to scan, I shall have some fun with that.  

[RebelTiger]

Found a simple solution...
Change:
gksu /usr/bin/xvt
to:
kdesu /usr/bin/xvt
all will work well again!

[wedgetail]

RebelTiger
I notice that it is exactly 1 year today since I posted in this thread. Welcome to Forum and may you have lots of fun searching and experimenting with PCLOS.

Since it is a long time since I have experimented with my konsoles I am not sure where I presently stand, I am not doing much updating either but I am aware of a lot has happened in the last 12 months.  Some of my systems have had upgrades and if I come accross this problem again I will hopefully find this thread again.