| View previous topic :: View next topic |
| Author |
Message |
nabla
n00b
Joined: 30 Oct 2002
Posts: 69
Location: Zurich, Switzerland
|
 Posted: Mon Nov 25, 2002 10:17 pm Post subject: HELP: konsole crashes in KDE |
 |
|
Hello,
please help:
I just emerged KDE and everything seams to be OK, BUT it's not possible to open a kosonle! After calling the konsole the KDE crash handler comes up.
This is the short description: "The applivation Konsole (konsole) crashed and caused the signal 11 (SIGSEGV)."
This is the backtrace:
no debugging symbols found)...0x410ca4b9 in wait4 () from /lib/libc.so.6
#0 0x410ca4b9 in wait4 () from /lib/libc.so.6
#1 0x4114dc18 in __DTOR_END__ () from /lib/libc.so.6
#2 0x40fcfea3 in waitpid () from /lib/libpthread.so.0
#3 0x406b7d97 in KCrash::defaultCrashHandler(int) ()
from /usr/kde/3/lib/libkdecore.so.4
#4 0x40fcdcd2 in pthread_sighandler () from /lib/libpthread.so.0
#5 <signal handler called>
#6 0x40a8f367 in QObject::inherits(char const*) const ()
from /usr/qt/3/lib/libqt-mt.so.3
#7 0x417d3032 in Konsole::makeGUI() () from /usr/kde/3/lib/konsole.so
#8 0x417d8169 in Konsole::activateSession(TESession*) ()
from /usr/kde/3/lib/konsole.so
#9 0x417d7dfe in Konsole::activateSession() () from /usr/kde/3/lib/konsole.so
#10 0x417d9610 in Konsole::newSession(KSimpleConfig*, QString, QStrList const&, QString const&, QString const&, QString const&) ()
from /usr/kde/3/lib/konsole.so
#11 0x417cde16 in Konsole::Konsole(char const*, QString const&, QStrList&, int, bool, bool, bool, bool, QString const&, QString const&, QCString, QString const&, bool) () from /usr/kde/3/lib/konsole.so
#12 0x417cb328 in main () from /usr/kde/3/lib/konsole.so
#13 0x0804d33e in strcpy ()
#14 0x0804ed6e in strcpy ()
#15 0x0804de7a in strcpy ()
#16 0x0804bed2 in strcpy ()
#17 0x41043142 in __libc_start_main () from /lib/libc.so.6
Many thanks for help, what is Linux without konsole?
nabla |
|
| Back to top |
|
 |
chicklove
n00b
Joined: 26 Nov 2002
Posts: 5
|
| Posted: Tue Nov 26, 2002 1:43 am Post subject: |
|
|
I'm seeing the same thing on one machine, but not the other.
| Quote: | # /usr/kde/3/bin/konsole
DCOPServer up and running.
Conflict in /usr/kde/3/lib/kde3/plugins/styles/highcolor.so:
Plugin uses incompatible Qt library!
expected build key "i586 Linux g++-2.95.* full-config", got "g++-2.95.* full-config".
Conflict in /usr/kde/3/lib/kde3/plugins/styles/light.so:
Plugin uses incompatible Qt library!
expected build key "i586 Linux g++-2.95.* full-config", got "g++-2.95.* full-config".
Conflict in /usr/kde/3/lib/kde3/plugins/styles/dotnet.so:
Plugin uses incompatible Qt library!
expected build key "i586 Linux g++-2.95.* full-config", got "g++-2.95.* full-config".
Conflict in /usr/kde/3/lib/kde3/plugins/styles/kthemestyle.so:
Plugin uses incompatible Qt library!
expected build key "i586 Linux g++-2.95.* full-config", got "g++-2.95.* full-config".
KCrash: crashing.... crashRecursionCounter = 2
KCrash: Application Name = konsole path = <unknown> pid = 6777
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
Mutex destroy failure: Device or resource busy
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
|
This is going from one machine to another. I see the same thing going back (different errors, tho, complains about missing GLX), but not within the same machine.
Hope this helps...
_________________
Open mind, open heart |
|
| Back to top |
|
|
nabla
n00b
Joined: 30 Oct 2002
Posts: 69
Location: Zurich, Switzerland
|
| Posted: Tue Nov 26, 2002 4:48 pm Post subject: thanks |
|
|
Thank you for the hints.
I think I will update my qt-library. Have you any other ideas?
cu
nabla |
|
| Back to top |
|
|
chicklove
n00b
Joined: 26 Nov 2002
Posts: 5
|
| Posted: Tue Nov 26, 2002 5:59 pm Post subject: |
|
|
Well, now I'm finding it just doesn't work at all. I had open konsoles that were started by the session manager, but when I try to start a new one, I get just the crash, no other messages.
Time to file a bug report....
_________________
Open mind, open heart |
|
| Back to top |
|
|
chicklove
n00b
Joined: 26 Nov 2002
Posts: 5
|
|
| Back to top |
|
|
vert
Apprentice
Joined: 07 May 2002
Posts: 214
Location: Delft, The Netherlands
|
| Posted: Mon Dec 09, 2002 8:43 pm Post subject: |
|
|
| The thread is kinda old, but I seem to have exactly the same problem. The konsole crashes every time I try to start it with a "The applivation Konsole (konsole) crashed and caused the signal 11 (SIGSEGV)." I emerged 3.1.0-r1 a while ago. It might be since then. Anybody got an idea how to solve this? I run kde 3.0.4. |
|
| Back to top |
|
|
guero61
l33t
Joined: 14 Oct 2002
Posts: 811
Location: Behind you
|
| Posted: Mon Dec 09, 2002 9:01 pm Post subject: |
|
|
I know the "go elsewhere" posts may not be so helpful, but...
I've never understood the value of konsole or any of those other prettified "terminals" over a simple, good xterm. They don't do what I want them to do, and the xterms are so configurable! Here -- let me give you my terminal scripts, and see if you like them. Put them in ~/bin.
This is ~/bin/terminal
| Code: |
case $0 in
*term) cterm black darkgray
;;
*terms) cterm lightgray black
cterm lightgreen black
cterm lightblue black
cterm cyan black
;;
*termsr) cterm black lightgray
cterm black lightgreen
cterm black lightblue
cterm black tan
;;
esac
|
This is ~/bin/cterm
| Code: |
/usr/X11R6/bin/xterm -ls -fg $1 -bg $2 -geometry 100x24 -fn 6x13 -fb 6x13boldb -sk -sl 2048 &
|
What I do then, is just make soft links from ~/bin/terminal to ~/bin/term, ~/bin/terms, and ~/bin/termsr. Now I have an extensible, easily modifiable set of terminals in just about any color I want. It can also be extended by changing one character to use aterm, the terminal with transparency! Also, I have this little thing that helps immensely --
~/bin/vix
| Code: |
case $0 in
*vix) xterm -fg black -bg darkgray -geometry ${COLUMNS}x${LINES} -fn 6x13 -fb 6x13boldb -sk -sl 2048 -e vim ~/bin/$1
chmod 755 ~/bin/$1
;;
*vh) xterm -fg black -bg darkgray -geometry ${COLUMNS}x${LINES} -fn 6x13 -fb 6x13boldb -sk -sl 2048 -e vim ~/$1
;;
esac
|
This script allows me to lay down a new script in ~/bin any time I want, wherever I am, with a simple command. It pops up a new window of the same size with either the script or a blank document, then makes it executable. The vh derivative (made by a soft link from ~/bin/vix to ~/bin/vh) opens files relative to my home directory. That way I don't have to do "vi /home/<username>/...". I'm all about shortcuts. I even have KDE pointing toward ~/bin/term as my default console program, not konsole. Just me, just my preference.
Anyway, sorry this is so long and not at all what you were looking for, just thought I'd try to help "expand your paradigm".  |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
