Bug 175205

Summary:	Marble widget crashed and caused the signal 11 (SIGSEGV).
Product:	[Applications] marble	Reporter:	Still <nlcampos>
Component:	general	Assignee:	Torsten Rahn <rahn>
Status:	CLOSED DUPLICATE
Severity:	crash	CC:	andresbajotierra, caulier.gilles
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:	0.10.0
Sentry Crash Report:
Attachments:	Crash report

Description Still 2008-11-15 12:08:54 UTC

Version:            (using KDE 4.1.3)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Debian testing/unstable Packages

When digikam starts, it ask me about the path to the alguns and after I informe it, it tries to make a DB with the photos and after a while it crashes.
Here is some information about my system:

Debian SID/Experimental AMD64
gcc 4.3.2
kde 4.1.3
Photos 7.4Gb

Backtrace:
Application: digiKam (digikam), signal SIGSEGV
(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 0x7f47d1c60750 (LWP 31220)]
[New Thread 0x448d6950 (LWP 31264)]
[New Thread 0x440d5950 (LWP 31263)]
[New Thread 0x438d4950 (LWP 31262)]
[New Thread 0x430d3950 (LWP 31261)]
[New Thread 0x428d2950 (LWP 31258)]
[New Thread 0x418d0950 (LWP 31257)]
[New Thread 0x420d1950 (LWP 31256)]
[New Thread 0x410cf950 (LWP 31224)]
(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  0x00007f47ca50ad00 in GeoSceneDocument::head ()
   from /usr/lib/libmarblewidget.so.4
#6  0x00007f47ca5c1b7e in ?? () from /usr/lib/libmarblewidget.so.4
#7  0x00007f47ca53b304 in MarbleModel::MarbleModel ()
   from /usr/lib/libmarblewidget.so.4
#8  0x00007f47ca542c0e in MarbleMap::MarbleMap ()
   from /usr/lib/libmarblewidget.so.4
#9  0x00007f47ca538799 in MarbleWidget::MarbleWidget ()
   from /usr/lib/libmarblewidget.so.4
#10 0x00000000004a066a in Digikam::WorldMapWidget::WorldMapWidget ()
#11 0x0000000000482272 in Digikam::ImagePropertiesGPSTab::ImagePropertiesGPSTab ()
#12 0x00007f47d15b7c37 in Digikam::ImagePropertiesSideBar::ImagePropertiesSideBar () from /usr/lib/libdigikam.so.1
#13 0x000000000048631d in Digikam::ImagePropertiesSideBarDB::ImagePropertiesSideBarDB ()
#14 0x0000000000625921 in ?? ()
#15 0x0000000000611264 in Digikam::DigikamApp::setupView ()
#16 0x000000000061bdca in Digikam::DigikamApp::DigikamApp ()
#17 0x000000000064c340 in ?? ()
#18 0x00007f47c99c7466 in __libc_start_main () from /lib/libc.so.6
#19 0x0000000000471f19 in _start ()
#0  0x00007f47c9a47a91 in nanosleep () from /lib/libc.so.6


Kind regards,

Still

Comment 1 Still 2008-11-15 12:10:55 UTC

One bit of additional information:
nlcampos@leah-linux:~$ dpkg -l | grep digikam
ii  digikam                              2:0.10.0~beta2-1                 digital photo management application for KDE

Still

Comment 2 caulier.gilles 2008-11-15 12:13:54 UTC

Another report have been done about that. It's relevant of Marble widget component used in digiKam

Gilles Caulier

Comment 3 Andi Clemens 2008-12-01 23:26:09 UTC

Shouldn't we assign this to marble or close it completely?

Andi

Comment 4 caulier.gilles 2008-12-02 08:48:40 UTC

Right Andi. Re assigned...

Gilles

Comment 5 Dario Andres 2008-12-05 01:52:57 UTC

Is "marble-data" installed in your system? If not, this may be a duplicate of bug 172830

Comment 6 Dario Andres 2009-01-19 22:25:31 UTC

The reporter sent me an email:
--------

I have downgraded digikam and it works again. After I saw your e-mail, I have upgraded it again and the error now is quite different. When I start the digikam, it crash and there is no output debug.

I have the libmarble4 installed in my system.

Comment 7 caulier.gilles 2009-01-19 22:34:20 UTC

Dario,

Compile digiKam with full debug and post here the backtrace

Gilles Caulier

Comment 8 Dario Andres 2009-01-19 22:40:50 UTC

@Gilles: I hope Still reads your message... (I'm not the one experiencing the crash, I only posted the mail the original reporter (Still) sent me about his situation)

Comment 9 Still 2009-01-20 10:50:31 UTC

Daríos and Gilles;

  I'll try to compile digikam, but I must to clarify that I'm using the one pre pakaged by Debian team.
  I'm going to try it tonight (here is 07h50 am).

Regards,

Still

Comment 10 Still 2009-02-03 22:35:58 UTC

Created attachment 30934 [details]
Crash report

Comment 11 Still 2009-02-03 22:39:50 UTC

Hi guys;

  I have attached a crash report after I had upgraded my system:

ii  libmarble4                           4:4.2.0-1                        Marble globe widget library
ii  marble-data                          4:4.2.0-1                        data files for Marble
ii  digikam                              2:0.10.0~rc1-1                   digital photo management application for KDE

[]'s,

Still

Comment 12 Torsten Rahn 2009-02-03 23:06:31 UTC

The package that you need to install to work around the stupid packaging in ubuntu/debian is called "marble".

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

Comment 13 Still 2009-02-03 23:56:54 UTC

Hi Rahn;

  Ok. It's fixed. I'm closing this bug.
  Thanks!

[]'s,

Still