Bug 107034

Summary: random kicker crashes in 3.4.1
Product: [Unmaintained] kicker Reporter: Gilles Schintgen <gschintgen>
Component: generalAssignee: Aaron J. Seigo <aseigo>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Gilles Schintgen 2005-06-08 14:37:36 UTC
Version:            (using KDE KDE 3.4.1)
Installed from:    Gentoo Packages
OS:                Linux

Hi. Kicker keeps crashing randomly in KDE 3.4.1 (about once a day). (Just as in 3.4.0.) I'm not doing anything special, not even interacting with kicker, and then it simply disappears. A few seconds later, the crash handler comes up. Well it's probably a duplicate of some other backtrace, but you're the expert...

Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1220458832 (LWP 13627)]
[KCrash handler]
#4  0x42994c6c in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#5  0x42994e0c in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#6  0xb75964f5 in KApplication::notify (this=0xbffff090, receiver=0x835f7a8, 
    event=0xbfffeb20) at kapplication.cpp:549
#7  0x4292f7e2 in QETWidget::translateMouseEvent ()
   from /usr/qt/3/lib/libqt-mt.so.3
#8  0x4292e0c1 in QApplication::x11ProcessEvent ()
   from /usr/qt/3/lib/libqt-mt.so.3
#9  0x42941846 in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#10 0x429ab250 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#11 0x429ab1a6 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#12 0x42993e1f in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#13 0xb7f88371 in kdemain (argc=7012388, argv=0xbffff2f4) at main.cpp:136
#14 0x0804872e in main (argc=7012388, argv=0x6b0024) at kicker.la.cpp:2
Comment 1 Aaron J. Seigo 2005-06-08 16:28:46 UTC

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