Bug 106912 - Random crash, possibly from an icon update?
Summary: Random crash, possibly from an icon update?
Status: RESOLVED DUPLICATE of bug 105679
Alias: None
Product: kicker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Aaron J. Seigo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-06 18:17 UTC by Dustin Souers
Modified: 2005-06-06 19:47 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 Dustin Souers 2005-06-06 18:17:48 UTC
Version:           the one bundled with 3.4.1 Level "a" (using KDE KDE 3.4.1)
Installed from:    SuSE RPMs

I was surfing in Konqueror, I assume it might have been caused by either kopete or kmail, when it updates the icon.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(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 1095896608 (LWP 4585)]
(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)
(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)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#7  0x407b4dd6 in QETWidget::translateMouseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0x407b4116 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0x407c4b08 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0x4082fb41 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x4082f986 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0x4081963f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0x417ca1b1 in kdemain () from /opt/kde3/lib/libkdeinit_kicker.so
#14 0x40018584 in kdeinitmain () from /opt/kde3/lib/kde3/kicker.so
#15 0x0804e725 in launch ()
#16 0x0804ee3c in handle_launcher_request ()
#17 0x0804f3f9 in handle_requests ()
#18 0x0804fbca in main ()
Comment 1 Dustin Souers 2005-06-06 18:18:40 UTC
It caused a SIGSEGV. I forgot to add that.
Comment 2 Aaron J. Seigo 2005-06-06 19:47:31 UTC

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