Bug 65917

Summary:	crash when using ssh
Product:	[Applications] konsole	Reporter:	Jacek K. Blaszkowski <rainman>
Component:	general	Assignee:	Konsole Bugs <konsole-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jacek K. Blaszkowski 2003-10-12 12:50:09 UTC

Version:           unknown (using KDE 3.1.4)
Installed from:    compiled sources
Compiler:          gcc version 3.2.3
OS:          Linux (i686) release 2.4.22jkb

Trying to connect via ssh to my account at kastor.ds.pg.gda.pl
1. Konsole starts normally (from KPanel)
2. jkb@decadence$ ssh kastor.ds.pg.gda.pl -l <mylogin>
3. Konsole crashes ALWAYS just after I type my password.

The backtrace:
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 891)]

0x40f515c9 in waitpid () from /lib/libpthread.so.0
#0  0x40f515c9 in waitpid () from /lib/libpthread.so.0
#1  0x4063f9ed in KCrash::defaultCrashHandler(int) ()
   from /opt/kde/lib/libkdecore.so.4
#2  0x40f4fc45 in __pthread_sighandler () from /lib/libpthread.so.0
#3  <signal handler called>
#4  0x0020007d in ?? ()
#5  0x409418c5 in QPainter::drawTextItem(int, int, QTextItem const&, int) ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#6  0x409415e5 in QPainter::drawText(int, int, QString const&, int, int, QPainter::TextDirection) () from /usr/lib/qt/lib/libqt-mt.so.3
#7  0x4094120a in QPainter::drawText(int, int, QString const&, int, QPainter::TextDirection) () from /usr/lib/qt/lib/libqt-mt.so.3
#8  0x419a5172 in TEWidget::drawAttrStr(QPainter&, QRect, QString&, ca const*, bool, bool) () from /opt/kde/lib/konsole.so
#9  0x419a605e in TEWidget::setImage(ca const*, int, int) ()
   from /opt/kde/lib/konsole.so
#10 0x419b4da9 in TEmulation::showBulk() () from /opt/kde/lib/konsole.so
#11 0x419b3626 in TEmulation::qt_invoke(int, QUObject*) ()
   from /opt/kde/lib/konsole.so
#12 0x419ac894 in TEmuVt102::qt_invoke(int, QUObject*) ()
   from /opt/kde/lib/konsole.so
#13 0x409d7e50 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#14 0x409d7c84 in QObject::activate_signal(int) ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#15 0x40cf1a3b in QTimer::timeout() () from /usr/lib/qt/lib/libqt-mt.so.3
#16 0x409f9242 in QTimer::event(QEvent*) () from /usr/lib/qt/lib/libqt-mt.so.3
#17 0x4097d035 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#18 0x4097c6eb in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#19 0x405c2c89 in KApplication::notify(QObject*, QEvent*) ()
   from /opt/kde/lib/libkdecore.so.4
#20 0x4096ca6b in QEventLoop::activateTimers() ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#21 0x4092abb4 in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#22 0x40990276 in QEventLoop::enterLoop() () from /usr/lib/qt/lib/libqt-mt.so.3
#23 0x40990118 in QEventLoop::exec() () from /usr/lib/qt/lib/libqt-mt.so.3
#24 0x4097d281 in QApplication::exec() () from /usr/lib/qt/lib/libqt-mt.so.3
#25 0x4197fcf2 in main () from /opt/kde/lib/konsole.so
#26 0x0804cbe1 in strcpy ()
#27 0x0804da09 in strcpy ()
#28 0x0804de8c in strcpy ()
#29 0x0804ec3a in strcpy ()
#30 0x4109fd06 in __libc_start_main () from /lib/libc.so.6

Comment 1 Stephan Binner 2003-10-12 20:17:03 UTC

Doesn't crash here - until I get rejected by that host. ;-) Some special escape 
sequences in your login shell initialization scripts or alike? Try with a 
minimal version.

Comment 2 Jacek K. Blaszkowski 2003-10-13 17:18:31 UTC

Hello,
the remote host is so configured that it greets an user logging in with a rather
complicated MOTD, including characters from Polish aplphabet (encoded in
iso8859-2 or unicode, AFAIR). After a long, long googling I realized changing
Konsole font to "Unicode" mode prevents it from crash. It still crashes
inevitably when using "Linux" font setting.

Comment 3 Thiago Macieira 2003-10-28 23:17:12 UTC

Same backtrace as #65127.

*** This bug has been marked as a duplicate of 65127 ***