Bug 160719 - kicker crashed with signal 11 SIGSEV, i presume it crashed due to the fact I was using f-spot (i have problem using kubuntu and f-spot since hardy)
Summary: kicker crashed with signal 11 SIGSEV, i presume it crashed due to the fact I ...
Status: RESOLVED DUPLICATE of bug 133386
Alias: None
Product: kicker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Aaron J. Seigo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-11 18:14 UTC by marc
Modified: 2008-04-11 18:23 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 marc 2008-04-11 18:14:44 UTC
Version:            (using KDE 3.5.9)
Installed from:    Ubuntu Packages
OS:                Linux

kubuntu hardy amd64 version refused to let me using f-spot, I had to make dbus modification to be abble to run it (see launchpad 2 bugs report : https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/207157 --  dbus and f-spot not does not start f-spot https://bugs.launchpad.net/bugs/185752)
once dbus launch modified in xsession, i have to delete f-psot data base on my home and relaunch it : it agree to launch the app this time, it calculates database but refuse me to quit the application..... and finally I guess it drive me to get kicker to crash, trace is here below :I wish I could get a solution to get digital camera picture sorted according to exif, iptc and xmp  datas ... that's the why of using f-spot

(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)
(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)
[Thread debugging using libthread_db enabled]
[New Thread 0x7ff5c089a6f0 (LWP 8669)]
(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)
(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]
#5  0x00007ff5b67f3508 in TaskContainer::updateKickerTip ()
   from /usr/lib/libtaskbar.so.1
#6  0x00007ff5b7e0f7ca in KickerTip::display ()
   from /usr/lib/libkickermain.so.1
#7  0x00007ff5b7e0fc88 in KickerTip::qt_invoke ()
   from /usr/lib/libkickermain.so.1
#8  0x00007ff5be6a3fd0 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#9  0x00007ff5be6a4b4e in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#10 0x00007ff5bea1e496 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#11 0x00007ff5be6c9d83 in QTimer::event () from /usr/lib/libqt-mt.so.3
#12 0x00007ff5be63c33a in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#13 0x00007ff5be63e093 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#14 0x00007ff5bf0a940d in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#15 0x00007ff5be5cd20e in QApplication::sendEvent ()
   from /usr/lib/libqt-mt.so.3
#16 0x00007ff5be62fabc in QEventLoop::activateTimers ()
   from /usr/lib/libqt-mt.so.3
#17 0x00007ff5be5e2107 in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#18 0x00007ff5be6565bf in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#19 0x00007ff5be6562ab in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#20 0x00007ff5be63de00 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#21 0x00007ff5b8561a01 in kdemain () from /usr/lib/libkdeinit_kicker.so
#22 0x0000000000408018 in ?? ()
#23 0x00000000004087b1 in ?? ()
#24 0x0000000000408ce9 in ?? ()
#25 0x0000000000409652 in ?? ()
#26 0x00007ff5bf9721c4 in __libc_start_main () from /lib/libc.so.6
#27 0x0000000000404e39 in ?? ()
#28 0x00007fffc88c6358 in ?? ()
#29 0x0000000000000000 in ?? ()
Comment 1 Pino Toscano 2008-04-11 18:23:10 UTC

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