Bug 114142

Summary: kicker crashes all the time
Product: [Unmaintained] kicker Reporter: Bradley Pierson <bpierson>
Component: generalAssignee: Aaron J. Seigo <aseigo>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Mandriva RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Bradley Pierson 2005-10-09 21:32:19 UTC
Version:            (using KDE KDE 3.4.2)
Installed from:    Mandriva RPMs
OS:                Linux

Kicker crases and gives me this message every time it is started:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1233069696 (LWP 4073)]
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#4  0xffffe410 in __kernel_vsyscall ()
#5  0xb7d19ef1 in raise () from /lib/tls/libc.so.6
#6  0xb7d1b83b in abort () from /lib/tls/libc.so.6
#7  0xb6c3bf81 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#8  0xb6c398a5 in __gxx_personality_v0 () from /usr/lib/libstdc++.so.6
#9  0xb6c398e2 in std::terminate () from /usr/lib/libstdc++.so.6
#10 0xb6c39a4a in __cxa_throw () from /usr/lib/libstdc++.so.6
#11 0xb6c39eb1 in operator new () from /usr/lib/libstdc++.so.6
#12 0xb6c39f7d in operator new[] () from /usr/lib/libstdc++.so.6
#13 0xb72a93a5 in QString::setLength () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x40000000 in ?? ()
#15 0x00000000 in ?? ()
Comment 1 Maksim Orlovich 2005-10-09 21:50:02 UTC
Please see bug #109161 for a workaround

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