[Bug 49139] crash when pressing Ctrl+W to close a file

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=49139     
[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From [email protected]  2002-10-15 10:03 -------
Subject: Re:  New: crash when pressing Ctrl+W to close a file

Am Monday 14 October 2002 20:05 schrieb Felix Seeger:
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
>
> http://bugs.kde.org/show_bug.cgi?id=49139
>            Summary: crash when pressing Ctrl+W to close a file
>            Product: kate
>            Version: 2.1
>           Platform: Compiled Sources
>         OS/Version: Linux
>             Status: UNCONFIRMED
>           Severity: crash
>           Priority: NOR
>          Component: general
>         AssignedTo: [email protected]
>         ReportedBy: [email protected]
>
>
> Version:           2.1 (using KDE 3.0.8 (KDE 3.1 beta2))
> Installed from:    compiled sources
> Compiler:          gcc version 2.95.4 20011002 (Debian prerelease)
> OS:          Linux (i686) release 2.4.19
>
> Pressing Ctrl+w to close the last file from five crashes kate.
> qt-copy is uptodate, closing with the button works.
>
> Here is the backtrace:
>
> 0x40f42609 in wait4 () from /lib/libc.so.6
> #0  0x40f42609 in wait4 () from /lib/libc.so.6
> #1  0x40fb7dd0 in __check_rhosts_file () from /lib/libc.so.6
> #2  0x40dedeeb in waitpid () from /lib/libpthread.so.0
> #3  0x4062bfaa in KCrash::defaultCrashHandler ()
>    from /opt/kde31/lib/libkdecore.so.4
> #4  0x40deba44 in pthread_sighandler () from /lib/libpthread.so.0
> #5  0x40ecb518 in sigaction () from /lib/libc.so.6
> #6  0x405ab87e in KApplication::notify () from
> /opt/kde31/lib/libkdecore.so.4 #7  0x4088d903 in
> QETWidget::translateKeyEvent ()
>    from /opt/qt-copy/lib/libqt-mt.so.3
> #8  0x4088a228 in QApplication::x11ProcessEvent ()
>    from /opt/qt-copy/lib/libqt-mt.so.3
> #9  0x4089b2b0 in QEventLoop::processEvents ()
>    from /opt/qt-copy/lib/libqt-mt.so.3
> #10 0x408e6b25 in QEventLoop::enterLoop () from
> /opt/qt-copy/lib/libqt-mt.so.3 #11 0x408e6a9f in QEventLoop::exec () from
> /opt/qt-copy/lib/libqt-mt.so.3 #12 0x408d573e in QApplication::exec () from
> /opt/qt-copy/lib/libqt-mt.so.3 #13 0x415c164b in main () from
> /opt/kde31/lib/libkateinterfaces.so #14 0x0804cdd7 in launch ()
> #15 0x0804dcc8 in handle_launcher_request ()
> #16 0x0804e27b in handle_requests ()
> #17 0x0804f16f in main ()
> #18 0x40ebb0bf in __libc_start_main () from /lib/libc.so.6
>
That's the same Qt bug as reported quite some times on kde-devel

Greetings, Stephan