Bug 215314 - if initialized the program crashes
Summary: if initialized the program crashes
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Searches-Map (show other bugs)
Version: 1.0.0
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-19 20:33 UTC by siggi
Modified: 2012-06-27 11:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 1.0.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description siggi 2009-11-19 20:33:59 UTC
Application that crashed: digikam
Version of the application: 1.0.0-beta5
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.31.5-desktop-1mnb x86_64
Distribution: "Mandriva Linux 2010.0"

What I was doing when the application crashed:
Program starts up and displays the dialog to select the media folder. I coose a local folder. If I choos a folder with pictures, pictures are indexed and the db is created. after finishing indexing the program crashes. If I delete the config and the folder dialg appears again, vene selecting an empty folder crashes the program

 -- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f8705a27710 (LWP 30172))]

Thread 9 (Thread 0x7f86f3e86910 (LWP 30173)):
#0  0x00007f86ff142e59 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f87002f4d5b in QWaitCondition::wait () from /usr/lib64/libQtCore.so.4
#2  0x00000000006c2ea3 in Digikam::ScanController::run (this=0x1e3bf10) at /usr/src/debug/digikam-1.0.0-beta5/digikam/scancontroller.cpp:499
#3  0x00007f87002f3ca5 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x00007f86ff13e7cd in start_thread () from /lib64/libpthread.so.0
#5  0x00007f86ff87037d in clone () from /lib64/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 8 (Thread 0x7f86f0139910 (LWP 30174)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f86f0138da0 in ?? ()
#2  0x00007fff007ff782 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 7 (Thread 0x7f86ef938910 (LWP 30175)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f86ef937da0 in ?? ()
#2  0x00007fff007ff782 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 6 (Thread 0x7f86ef137910 (LWP 30176)):
#0  0x00007f86ff142e59 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f87002f4d5b in QWaitCondition::wait () from /usr/lib64/libQtCore.so.4
#2  0x00007f87031939e2 in Digikam::LoadSaveThread::run (this=0x1f233b0) at /usr/src/debug/digikam-1.0.0-beta5/libs/threadimageio/loadsavethread.cpp:136
#3  0x00007f87002f3ca5 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x00007f86ff13e7cd in start_thread () from /lib64/libpthread.so.0
#5  0x00007f86ff87037d in clone () from /lib64/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7f86ee936910 (LWP 30177)):
#0  0x00007f86fa4d374e in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0
#1  0x00007f86fa4d3a91 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f86fa4d3fc0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f8700401cc6 in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4
#4  0x00007f87003d7fe2 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4
#5  0x00007f87003d83b4 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#6  0x00007f87002f0f2b in QThread::exec () from /usr/lib64/libQtCore.so.4
#7  0x00007f87002f3ca5 in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007f86ff13e7cd in start_thread () from /lib64/libpthread.so.0
#9  0x00007f86ff87037d in clone () from /lib64/libc.so.6
#10 0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f86ee135910 (LWP 30178)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f86ee134da0 in ?? ()
#2  0x00007fff007ff782 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0x7f86ed934910 (LWP 30179)):
#0  0x00007f86ff142e59 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f87002f4d5b in QWaitCondition::wait () from /usr/lib64/libQtCore.so.4
#2  0x00007f87031939e2 in Digikam::LoadSaveThread::run (this=0x1e8b690) at /usr/src/debug/digikam-1.0.0-beta5/libs/threadimageio/loadsavethread.cpp:136
#3  0x00007f87002f3ca5 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x00007f86ff13e7cd in start_thread () from /lib64/libpthread.so.0
#5  0x00007f86ff87037d in clone () from /lib64/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f86e57fe910 (LWP 30192)):
#0  0x00007f86ff8667f3 in poll () from /lib64/libc.so.6
#1  0x00007f86ff5845df in ?? () from /usr/lib64/libpulse.so.0
#2  0x00007f86ff574bf6 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0
#3  0x00007f86ff575fd9 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0
#4  0x00007f86ff576090 in pa_mainloop_run () from /usr/lib64/libpulse.so.0
#5  0x00007f86ff5844fb in ?? () from /usr/lib64/libpulse.so.0
#6  0x00007f86f95ed900 in ?? () from /usr/lib64/libpulsecommon-0.9.19.so
#7  0x00007f86ff13e7cd in start_thread () from /lib64/libpthread.so.0
#8  0x00007f86ff87037d in clone () from /lib64/libc.so.6
#9  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f8705a27710 (LWP 30172)):
[KCrash Handler]
#5  0x00007f87003ed907 in operator<< () from /usr/lib64/libQtCore.so.4
#6  0x00007f8702760864 in Marble::PluginManager::loadPlugins () from /usr/lib64/libmarblewidget.so.4
#7  0x00007f8702761654 in Marble::PluginManager::PluginManager () from /usr/lib64/libmarblewidget.so.4
#8  0x00007f870275e089 in Marble::LayerManager::LayerManager () from /usr/lib64/libmarblewidget.so.4
#9  0x00007f87027231df in Marble::MarbleModel::MarbleModel () from /usr/lib64/libmarblewidget.so.4
#10 0x00007f870272c02a in Marble::MarbleMap::MarbleMap () from /usr/lib64/libmarblewidget.so.4
#11 0x00007f8702720559 in Marble::MarbleWidget::MarbleWidget () from /usr/lib64/libmarblewidget.so.4
#12 0x00007f870326ffdf in WorldMapWidget (this=0x26dd470, w=<value optimized out>, h=256, parent=<value optimized out>)
    at /usr/src/debug/digikam-1.0.0-beta5/libs/imageproperties/markerclusterholder.h:443
#13 0x00007f870326cb1b in ImagePropertiesGPSTab (this=0x26c2e40, parent=<value optimized out>) at /usr/src/debug/digikam-1.0.0-beta5/libs/imageproperties/imagepropertiesgpstab.cpp:106
#14 0x00007f8703255d97 in ImagePropertiesSideBar (this=0x25cd9e0, parent=0x1e90fa0, splitter=<value optimized out>, side=<value optimized out>, mimimizedDefault=<value optimized out>)
    at /usr/src/debug/digikam-1.0.0-beta5/libs/imageproperties/imagepropertiessidebar.cpp:82
#15 0x000000000047979d in ImagePropertiesSideBarDB (this=0x7f870267d7f8, parent=0x7fff007d39f0, splitter=0x7f870267d7f8, side=40857346, mimimizedDefault=<value optimized out>)
    at /usr/src/debug/digikam-1.0.0-beta5/libs/imageproperties/imagepropertiessidebardb.cpp:89
#16 0x000000000066e428 in DigikamView (this=0x1e90fa0, parent=0x1ed0c80) at /usr/src/debug/digikam-1.0.0-beta5/digikam/digikamview.cpp:220
#17 0x00000000006549c2 in Digikam::DigikamApp::setupView (this=0x1ed0c80) at /usr/src/debug/digikam-1.0.0-beta5/digikam/digikamapp.cpp:470
#18 0x00000000006637c5 in DigikamApp (this=0x1ed0c80) at /usr/src/debug/digikam-1.0.0-beta5/digikam/digikamapp.cpp:209
#19 0x0000000000759c75 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/digikam-1.0.0-beta5/digikam/main.cpp:163

Reported using DrKonqi
Comment 1 Michael G. Hansen 2009-11-19 22:19:17 UTC
Could you try to move the following file to another location (to /root/, for example) and see if the problem still occurs:

/usr/lib/kde4/plugins/marble/ExternalDraw.so

If that file did not exist, it is probably stored in another location on Mandriva. Try finding it using 
cd /usr ; find | grep ExternalDraw
and then move it somewhere else.

If you still get a crash, can you check whether you get a crash when you start Marble on its own?

Michael
Comment 2 siggi 2009-11-20 00:12:57 UTC
Hello,

thanks for the fast response.
Moved the file away
mv /usr/lib64/./kde4/plugins/marble/ExternalDraw.so .
Crashes with the same symtoms.
I'm not shure what you mean. I have installed the marble globus app, now.
It crashes if I try to start it.
marble: symbol lookup error: marble: undefined symbol: 
_ZN6Marble18AbstractDataPlugin16staticMetaObjectE

Gruß
siggi
Michael G. Hansen wrote:
> https://bugs.kde.org/show_bug.cgi?id=215314
>
>
> Michael G. Hansen <mike@mghansen.de> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |mike@mghansen.de
>           Component|general                     |Map Searches
>             Version|unspecified                 |1.0.0-beta5
>
>
>
>
> --- Comment #1 from Michael G. Hansen <mike mghansen de>  2009-11-19 22:19:17 ---
> Could you try to move the following file to another location (to /root/, for
> example) and see if the problem still occurs:
>
> /usr/lib/kde4/plugins/marble/ExternalDraw.so
>
> If that file did not exist, it is probably stored in another location on
> Mandriva. Try finding it using 
> cd /usr ; find | grep ExternalDraw
> and then move it somewhere else.
>
> If you still get a crash, can you check whether you get a crash when you start
> Marble on its own?
>
> Michael
>
>
Comment 3 caulier.gilles 2009-11-20 06:14:01 UTC
and also, try beta6...

Gilles Caulier
Comment 4 siggi 2009-11-20 20:16:41 UTC
Sorry, can not try beta6 at the moment, because not provided by mandriva at the moment and ti is a companys laptop. To compile it from the scratch, if to change to much things. maybe I can try on a differen PC I have, but can't promise. sorry.

Siggi
Comment 5 Michael G. Hansen 2009-11-20 20:58:06 UTC
Siggi,

thanks for trying our suggestions. Since Marble is also crashing, and Digikam depends on Marble, you might want to try to find out why Marble is crashing on its own. Try un-installing all Marble packages (libmarble, marble, marble-data) and re-installing them, there might be a version conflict there. Or check the Mandriva pages for Marble problems.

If you decide to compile Digikam, you can simply uninstall libmarble before running CMake, this way Digikam will be built without Marble, hence hopefully avoiding the crash.

Michael
Comment 6 siggi 2009-11-20 21:38:52 UTC
In this moment if got new marble libs from mandriva. 4.3.2 instead of 4.2.x before. Now everything works fine.
You can close this bug. It seems to be a problem with the marble lib version.
Thank you for your support.
Best
Siggi