Version: 2:0.10.0~rc2-1 (using KDE 4.2.0) Compiler: gcc (Debian 4.3.2-1.1) 4.3.2 OS: Linux Installed from: Debian testing/unstable Packages Application: digiKam (digikam), signal SIGSEGV [Current thread is 0 (LWP 8865)] Thread 5 (Thread 0xb33b5b90 (LWP 8866)): #0 0xb7fa3424 in __kernel_vsyscall () #1 0xb5211025 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb56097fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6 #3 0xb57ee542 in QWaitCondition::wait (this=0x89f84d0, mutex=0x89f84cc, time=4294967295) at thread/qwaitcondition_unix.cpp:82 #4 0x0828e879 in Digikam::ScanController::run (this=0x89fa330) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/digikam/scancontroller.cpp:412 #5 0xb57ed52e in QThreadPrivate::start (arg=0x89fa330) at thread/qthread_unix.cpp:185 #6 0xb520d4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb55fb6de in clone () from /lib/i686/cmov/libc.so.6 Thread 4 (Thread 0xb206bb90 (LWP 8871)): #0 0xb7fa3424 in __kernel_vsyscall () #1 0xb5211025 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb56097fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6 #3 0xb57ee542 in QWaitCondition::wait (this=0x8d00a28, mutex=0x8d00a24, time=4294967295) at thread/qwaitcondition_unix.cpp:82 #4 0xb71eabda in Digikam::LoadSaveThread::run (this=0x8d00a18) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/libs/threadimageio/loadsavethread.cpp:131 #5 0xb57ed52e in QThreadPrivate::start (arg=0x8d00a18) at thread/qthread_unix.cpp:185 #6 0xb520d4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb55fb6de in clone () from /lib/i686/cmov/libc.so.6 Thread 3 (Thread 0xb286cb90 (LWP 8872)): #0 0xb7fa3424 in __kernel_vsyscall () #1 0xb5211025 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb56097fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6 #3 0xb57ee542 in QWaitCondition::wait (this=0x8d15610, mutex=0x8d1560c, time=4294967295) at thread/qwaitcondition_unix.cpp:82 #4 0xb71eabda in Digikam::LoadSaveThread::run (this=0x8d15600) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/libs/threadimageio/loadsavethread.cpp:131 #5 0xb57ed52e in QThreadPrivate::start (arg=0x8d15600) at thread/qthread_unix.cpp:185 #6 0xb520d4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb55fb6de in clone () from /lib/i686/cmov/libc.so.6 Thread 2 (Thread 0xafc61b90 (LWP 8874)): #0 0xb7fa3424 in __kernel_vsyscall () #1 0xb5211025 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb56097fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6 #3 0xafdd565f in ?? () from /usr/lib/libjack.so.0 #4 0xafde46e0 in ?? () from /usr/lib/libjack.so.0 #5 0xafde46c4 in ?? () from /usr/lib/libjack.so.0 #6 0xafde46e0 in ?? () from /usr/lib/libjack.so.0 #7 0xb521cff4 in ?? () from /lib/i686/cmov/libpthread.so.0 #8 0x00000000 in ?? () Thread 1 (Thread 0xb49706f0 (LWP 8865)): [KCrash Handler] #5 0xb6e80146 in Marble::PluginManager::loadPlugins () from /usr/lib/libmarblewidget.so.4 #6 0xb6e80bfe in Marble::PluginManager::PluginManager () from /usr/lib/libmarblewidget.so.4 #7 0xb6e7e5d1 in Marble::LayerManager::LayerManager () from /usr/lib/libmarblewidget.so.4 #8 0xb6e3dcc1 in Marble::MarbleModel::MarbleModel () from /usr/lib/libmarblewidget.so.4 #9 0xb6e47c06 in Marble::MarbleMap::MarbleMap () from /usr/lib/libmarblewidget.so.4 #10 0xb6e3a1f0 in Marble::MarbleWidget::MarbleWidget () from /usr/lib/libmarblewidget.so.4 #11 0xb72b6c1b in WorldMapWidget (this=0x8fc1390, w=256, h=256, parent=0x8f845f0) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/libs/imageproperties/worldmapwidget.cpp:77 #12 0xb72b2f5f in ImagePropertiesGPSTab (this=0x8f845f0, parent=0x8c9ba58) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/libs/imageproperties/imagepropertiesgpstab.cpp:96 #13 0xb7299a02 in ImagePropertiesSideBar (this=0x8ec2770, parent=0x8c9ba58, splitter=0x8c40798, side=KMultiTabBar::Right, mimimizedDefault=<value optimized out>) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/libs/imageproperties/imagepropertiessidebar.cpp:82 #14 0x0809ed51 in ImagePropertiesSideBarDB (this=0x8ec2770, parent=0x8c9ba58, splitter=0x8c40798, side=KMultiTabBar::Right, mimimizedDefault=<value optimized out>) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/libs/imageproperties/imagepropertiessidebardb.cpp:89 #15 0x0825d72c in DigikamView (this=0x8c9ba58, parent=0x8ad1aa8) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/digikam/digikamview.cpp:201 #16 0x08245e53 in Digikam::DigikamApp::setupView (this=0x8ad1aa8) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/digikam/digikamapp.cpp:422 #17 0x0825195b in DigikamApp (this=0x8ad1aa8) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/digikam/digikamapp.cpp:195 #18 0x082b3f44 in main (argc=1, argv=0xbf8be334) at /home/mark/src/kde-extras/build-area/digikam-0.10.0~rc2/digikam/main.cpp:167
This is a duplicate of 172830. It's a packaging bug. Please ask your distributor to do packaging properly.
*** This bug has been marked as a duplicate of bug 172830 ***
(In reply to comment #1) > This is a duplicate of 172830. > > It's a packaging bug. > Please ask your distributor to do packaging properly. tackat, I am the packager, what is the issue? debian digikam/0.10.0~rc2 does depend on marble-data so I doubt this is a duplicate of #172830. Mark
The debug output seems to indicate to me that you are packaging the Marble plugins as part of the marble package instead of putting them into the libmarble package (at least that was identified to be the bug for ubuntu/kubuntu with the same debug output).
Thanks tackat, it is indeed a dependency of digikam to have the marble plugins, which are currently shipped in the marble package. I'll make marble a dependency of the digikam package and things should be good. Mark
Sorry, but this is a really bad solution: This will just mean that all other applications which would use the library would need to depend on the marble package as well (then the point of having a separation between the marble and the libmarble package becomes really moot ...). If you already package the library as a separate entity (which was completely a debian choice right from the start) then you should at least make sure that it works as such (and this of course includes testing whether this works at all which didn't happen obviously). So the proper solution would be to include the plugins with the library (They aren't application specific anyways but meant for wide use).