Bug 132036 - kicker SIGSEGV (occured when printing from KWord)
Summary: kicker SIGSEGV (occured when printing from KWord)
Status: RESOLVED DUPLICATE of bug 123869
Alias: None
Product: kicker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Aaron J. Seigo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-08 01:27 UTC by Timothée Lecomte
Modified: 2006-08-08 07:06 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 Timothée Lecomte 2006-08-08 01:27:13 UTC
Version:            (using KDE KDE 3.5.4)
Installed from:    Compiled From Sources
Compiler:          gcc 4.0.3 Distribution selected (sourcemage)
OS:                Linux

As I was printing from KWord (a couple of windows appear successively to display the status), kicker crashed, I got the bracktrace reproduced below, and kicker reappeared automatically.

Backtrace :

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' 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)
[KCrash handler]
#6  0x6e702e6e in ?? ()
#7  0xb63dc7ba in TaskBar::filteredContainers () from /usr/lib/libtaskbar.so.1
#8  0xb63ddbcb in TaskBar::reLayout () from /usr/lib/libtaskbar.so.1
#9  0xb63de459 in TaskBar::qt_invoke () from /usr/lib/libtaskbar.so.1
#10 0xb74a00ce in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb74a0518 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb785e6af in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#13 0xb74c6a4a in QTimer::event () from /usr/lib/libqt-mt.so.3
#14 0xb7432b71 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#15 0xb74335b8 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#16 0xb7b4298d in KApplication::notify () from /usr/lib/libkdecore.so.4
#17 0xb742677c in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#18 0xb73ce65f in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#19 0xb744c1e2 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#20 0xb744c106 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#21 0xb7432609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#22 0xb6728abb in kdemain () from /usr/lib/libkdeinit_kicker.so
#23 0xb72104f6 in kdeinitmain () from /usr/lib/kde3/kicker.so
#24 0x0804de60 in kdeinit_x_errhandler ()
#25 0x0804e42d in kdeinit_x_errhandler ()
#26 0x0804e853 in kdeinit_x_errhandler ()
#27 0x0804f5cb in kdeinit_x_errhandler ()
#28 0xb6f66015 in __libc_start_main () from /lib/libc.so.6
#29 0x0804c2f1 in ?? ()

(I must add that I experienced a couple of crashes with kicker in kde 3.5.3, but I didn't get the backtrace as today, and I was losing the position of the panel at each crash. Mine is placed on the upper edge of my screen, and it used to reappear at the bottom. With kde 3.5.4, it reappears on the top where it is supposed to be)

I'll be glad to give more information if needed. I'm not sure it's reproducable (ie *deterministic) though.
Comment 1 Andreas Kling 2006-08-08 07:06:02 UTC

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