[Konsole-devel] Bug#39510: marked as done (if started from menu/kicker, konsole does not accept keyboard input, crashes on exit) by Stephan Binner <binner at kde.org>

Tue Mar 19 17:48:07 UTC 2002

Your message with subj: Always do "make clean" before reporting bug to Konsole...

has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 18 Mar 2002 17:32:52 +0000
Received: (qmail 30937 invoked by uid 33); 18 Mar 2002 17:32:52 -0000
Date: 18 Mar 2002 17:32:52 -0000
Message-ID: <20020318173252.30936.qmail at mail.kde.org>
To: submit at bugs.kde.org
Subject: if started from menu/kicker, konsole does not accept keyboard input, crashes on exit
From: jharris at 30doradus.org
X-KDE-Received: -130.167.235.40

Package:           konsole
Version:           konsole 1.1; KDE 2.9.9 (CVS20020317); Qt 3.0.2 (20020126) (using KDE 2.9.2 CVS/CVSup/Snapshot)
Severity:          normal
Installed from:    Compiled sources
Compiler:          gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)
OS:                Linux
OS/Compiler notes: Not Specified

When konsole is launched from the kicker, or from the K menu, it does not accept keyboard input.  The same thing is true for konsoles launched automatically on startup.  In the latter case, however, I also get junk characters printed before and after the regular console prompt. The konsole does accept mouse events, however. 

Konsoles launched using Alt+F2 are *not* frozen, they are behaving normally.  In case it helps, this is with yesterday's CVS (17 March); my previous CVS was from 5 March, and konsoles worked fine there.  Also, I noticed the autoconf warning while compiling the packages.  I am still using ac-2.13...don't know if that matters for this problem.

(I wasn't sure about filing this under konsole, since not all konsoles are frozen, so the bug could be elsewhere.  However, all other apps seem to be functioning properly.)

The frozen konsoles crash on exit; the backtrace is:

[New Thread 1024 (LWP 3565)]
0x412be669 in __wait4 () from /lib/i686/libc.so.6
#0  0x412be669 in __wait4 () from /lib/i686/libc.so.6
#1  0x4133a154 in __DTOR_END__ () from /lib/i686/libc.so.6
#2  0x4116d523 in waitpid (pid=3717, stat_loc=0x0, options=0)
    at wrapsyscall.c:172
#3  0x406b88dd in KCrash::defaultCrashHandler () at eval.c:41
#4  0x4116b8d5 in pthread_sighandler (signo=11, ctx=
      {gs = 7, __gsh = 0, fs = 0, __fsh = 0, es = 43, __esh = 0, ds = 43, __dsh = 0, edi = 0, esi = 135276664, ebp = 3221217672, esp = 3221217660, ebx = 1097799176, edx = 0, ecx = 4294967295, eax = 0, trapno = 14, err = 4, eip = 1097715223, cs = 35, __csh = 0, eflags = 66118, esp_at_signal = 3221217660, ss = 43, __ssh = 0, fpstate = 0xbfffdf00, oldmask = 2147483648, cr2 = 0}) at signals.c:97
#5  <signal handler called>
#6  0x416dce17 in TEmuVt102::sendString () from /opt/kde3/lib/libkonsolepart.so
#7  0x416d2d6c in TESession::setConnect () from /opt/kde3/lib/libkonsolepart.so
#8  0x41696b57 in Konsole::doneSession () from /opt/kde3/lib/konsole.so
#9  0x4169b740 in Konsole::qt_invoke () from /opt/kde3/lib/konsole.so
#10 0x40a7a60a in QObject::activate_signal () at eval.c:41
#11 0x416d33c4 in TESession::done () from /opt/kde3/lib/libkonsolepart.so
#12 0x416d2dc7 in TESession::done () from /opt/kde3/lib/libkonsolepart.so
#13 0x416d366c in TESession::qt_invoke () from /opt/kde3/lib/libkonsolepart.so
#14 0x40a7a60a in QObject::activate_signal () at eval.c:41
#15 0x40a7a764 in QObject::activate_signal () at eval.c:41
#16 0x416c08e3 in TEPty::done () from /opt/kde3/lib/libkonsolepart.so
#17 0x416c0de9 in TEPty::donePty () from /opt/kde3/lib/libkonsolepart.so
#18 0x416c0a3d in TEPty::qt_invoke () from /opt/kde3/lib/libkonsolepart.so
#19 0x40a7a60a in QObject::activate_signal () at eval.c:41
#20 0x40651eb3 in KProcess::processExited () at eval.c:41
#21 0x4065081e in KProcess::processHasExited () at eval.c:41
#22 0x406533ad in KProcessController::slotDoHousekeeping () at eval.c:41
#23 0x4065392f in KProcessController::qt_invoke () at eval.c:41
#24 0x40a7a60a in QObject::activate_signal () at eval.c:41
#25 0x40a7a764 in QObject::activate_signal () at eval.c:41
#26 0x40df021b in QSocketNotifier::activated () at eval.c:41
#27 0x40a94f66 in QSocketNotifier::event () at eval.c:41
#28 0x40a0f650 in QApplication::internalNotify () at eval.c:41
#29 0x40a0f3a3 in QApplication::notify () at eval.c:41
#30 0x4061077a in KApplication::notify () at eval.c:41
#31 0x409aa994 in sn_activate () at eval.c:41
#32 0x409ab211 in QApplication::processNextEvent () at eval.c:41
#33 0x40a10f48 in QApplication::enter_loop () at eval.c:41
#34 0x409aaa60 in QApplication::exec () at eval.c:41
#35 0x41688d69 in main () from /opt/kde3/lib/konsole.so
#36 0x0804ccb4 in launch () at eval.c:41
#37 0x0804d927 in handle_launcher_request () at eval.c:41
#38 0x0804ddd6 in handle_requests () at eval.c:41
#39 0x0804f27a in main () at eval.c:41
#40 0x41220507 in __libc_start_main (main=0x804ebf4 <main>, argc=3, 
    ubp_av=0xbffffc04, init=0x804a318 <_init>, fini=0x804f6e8 <_fini>, 
    rtld_fini=0x4000dc14 <_dl_fini>, stack_end=0xbffffbfc)
    at ../sysdeps/generic/libc-start.c:129

thanks,
Jason

(Submitted via bugs.kde.org)