Bug 66611 - GUI freeze.... no action receive, except HOTKEY
Summary: GUI freeze.... no action receive, except HOTKEY
Status: RESOLVED NOT A BUG
Alias: None
Product: kate
Classification: Applications
Component: part (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-26 02:40 UTC by Mathieu Jobin
Modified: 2003-10-27 09:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Jobin 2003-10-26 02:40:33 UTC
Version:           unknown (using KDE 3.1.92 (CVS >= 20031019), compiled sources)
Compiler:          gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk)
OS:          Linux (i686) release 2.4.21-0.13mdk

#kdevelop : created Sun Aug  3 16:02:34 2003
<somekool> just to let you know !!! saving under kdevelop 3 is the UNSAFEST move I ever made, ever.
<somekool> right now ! kdevelop does not react  to any of my keypress, mouse click.
<somekool> the window refresh perfectly. when I mouseover something, over a separator widget for example, my mouse cursor change.
<somekool> but i can't do anything.... and I have a few unnsaved files
<somekool> what am I suppose to do ?
<Crissi> hm
<somekool> so the GUI update does not seems to be done, like when im going over a button, nothing change. but the refresh GUI is done. the window is not all gray
<somekool> OH NICE !!!
<somekool> HOTKEY still work,... I just did a CTRL-Q to quit ;) yahoo, I've been able to save file.
<somekool> but the gui was really frozen.
<somekool> I think I'll fill a bugreport.

cvs updated and compiled on ....

-rwxr-xr-x    1 root     root       578937 Oct  3 20:51 /usr/local/kde/bin/kdevelop*

as usual, it crash on exit();

[New Thread 16384 (LWP 29343)]
[New Thread 32769 (LWP 29382)]
0x41a596ba in waitpid () from /lib/i686/libpthread.so.0
#0  0x41a596ba in waitpid () from /lib/i686/libpthread.so.0
#1  0x40ef7f2d in KCrash::defaultCrashHandler(int) (sig=11) at kcrash.cpp:242
#2  0x41a585ce in __pthread_sighandler () from /lib/i686/libpthread.so.0
#3  0x41bc53b8 in __libc_sigaction () from /lib/i686/libc.so.6
#4  0x42a88a3e in KateDocument::save() (this=0x90e7e10)
    at katedocument.cpp:2478
#5  0x42ab9443 in KateView::save() (this=0x884a498) at kateview.cpp:846
#6  0x42ab20cb in KateView::qt_invoke(int, QUObject*) (this=0x884a498, 
    _id=120, _o=0xbfffed40) at kateview.moc:587
#7  0x4134e533 in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x881fd20, clist=0x86eaa28, o=0xbfffed40) at kernel/qobject.cpp:2333
#8  0x4134e3d2 in QObject::activate_signal(int) (this=0x881fd20, signal=2)
    at kernel/qobject.cpp:2302
#9  0x40c0259e in KAction::activated() (this=0x881fd20) at kaction.moc:157
#10 0x40c01f78 in KAction::slotActivated() (this=0x881fd20) at kaction.cpp:1054
#11 0x40c028a2 in KAction::qt_invoke(int, QUObject*) (this=0x881fd20, _id=14, 
    _o=0xbfffee60) at kaction.moc:181
#12 0x4134e533 in QObject::activate_signal(QConnectionList*, QUObject*) (
    this=0x92bd1f8, clist=0x8a65a48, o=0xbfffee60) at kernel/qobject.cpp:2333
#13 0x4134e3d2 in QObject::activate_signal(int) (this=0x92bd1f8, signal=2)
    at kernel/qobject.cpp:2302
#14 0x40eed6cc in KAccelPrivate::menuItemActivated() (this=0x92bd1f8)
    at kaccelprivate.moc:110
#15 0x40eebb8a in KAccelPrivate::eventFilter(QObject*, QEvent*) (
    this=0x92bd1f8, pEvent=0xbffff210) at kaccel.cpp:318
#16 0x4134c11c in QObject::activate_filters(QEvent*) (this=0x81a5a80, 
    e=0xbffff210) at kernel/qobject.cpp:902
#17 0x4134bf8e in QObject::event(QEvent*) (this=0x81a5a80, e=0xbffff210)
    at kernel/qobject.cpp:735
#18 0x4138581d in QWidget::event(QEvent*) (this=0x81a5a80, e=0xbffff210)
    at kernel/qwidget.cpp:4401
#19 0x4144bcbb in QMainWindow::event(QEvent*) (this=0x81a5a80, e=0xbffff210)
    at widgets/qmainwindow.cpp:1669
#20 0x412ebd21 in QApplication::internalNotify(QObject*, QEvent*) (
    this=0xbffff6b0, receiver=0x81a5a80, e=0xbffff210)
    at kernel/qapplication.cpp:2582
#21 0x412eb33c in QApplication::notify(QObject*, QEvent*) (this=0xbffff6b0, 
    receiver=0x8619e28, e=0xbffff210) at kernel/qapplication.cpp:2339
#22 0x40e69ad8 in KApplication::notify(QObject*, QEvent*) (this=0xbffff6b0, 
    receiver=0x8619e28, event=0xbffff210) at kapplication.cpp:509
#23 0x4016c4b5 in QApplication::sendEvent(QObject*, QEvent*) (
    receiver=0x8619e28, event=0xbffff210)
    at /usr/local/qt/include/qapplication.h:490
#24 0x40eea876 in KAccelEventHandler::x11Event(_XEvent*) (this=0x81d88c0, 
    pEvent=0xbffff530) at kaccel.cpp:108
#25 0x40e7975f in KAppX11HackWidget::publicx11Event(_XEvent*) (this=0x81d88c0, 
    e=0xbffff530) at kapplication.cpp:1528
#26 0x40e6e160 in KApplication::x11EventFilter(_XEvent*) (this=0xbffff6b0, 
    _event=0xbffff530) at kapplication.cpp:1583
#27 0x41270ffb in qt_x11EventFilter (ev=0xbffff530)
    at kernel/qapplication_x11.cpp:378
#28 0x41279b38 in QApplication::x11ProcessEvent(_XEvent*) (this=0xbffff6b0, 
    event=0xbffff530) at kernel/qapplication_x11.cpp:3270
#29 0x41293fe2 in QEventLoop::processEvents(unsigned) (this=0x8151028, flags=4)
    at kernel/qeventloop_x11.cpp:192
#30 0x4130161e in QEventLoop::enterLoop() (this=0x8151028)
    at kernel/qeventloop.cpp:198
#31 0x4130153a in QEventLoop::exec() (this=0x8151028)
    at kernel/qeventloop.cpp:145
#32 0x412ebea5 in QApplication::exec() (this=0xbffff6b0)
    at kernel/qapplication.cpp:2705
#33 0x08067869 in main ()
#34 0x41bb27f7 in __libc_start_main () from /lib/i686/libc.so.6
Comment 1 Thiago Macieira 2003-10-26 02:48:25 UTC
Apparently KatePart's fault, not KDevelop.
Comment 2 Christoph Cullmann 2003-10-27 09:22:21 UTC
and no visible reason in bt, therefor will close it, have never got such crash on end of kate, if that happens often in gideon there could be some prob with how they handle closing the docs on shutdown