issue digikam startup

[Marco]

Binary package hint: digikam

digikam crashes at startup

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: showfoto 2:1.5.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.37-8.21-generic 2.6.37-rc4
Uname: Linux 2.6.37-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Dec 12 18:31:09 2010
ProcEnviron:
 LANGUAGE=it_IT
 LANG=it_IT.utf8
 SHELL=/bin/bash
SourcePackage: digikam

[Biasquez (biasquez)]

Application: showfoto (1.5.0)
KDE Platform Version: 4.5.85 (4.6 Beta2)
Qt Version: 4.7.1
Operating System: Linux 2.6.37-8-generic x86_64
Distribution: Ubuntu natty (development branch)

-- Information about the crash:
- What I was doing when the application crashed:

i had this crash opening file .jpg clicking on "Open with showPhoto"

The crash can be reproduced every time.

-- Backtrace:
Application: showFoto (showfoto), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f0e538ed800 (LWP 10029))]

Thread 3 (Thread 0x7f0e373f6710 (LWP 10030)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1 0x00007f0e4f7b00eb in wait (this=<value optimized out>, mutex=0xa38d58, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2 QWaitCondition::wait (this=<value optimized out>, mutex=0xa38d58, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3 0x00007f0e5315e2d9 in Digikam::ParkingThread::run (this=0xa38d40) at /build/buildd/digikam-1.5.0/libs/threads/threadmanager.cpp:101
#4 0x00007f0e4f7afa2e in QThreadPrivate::start (arg=0xa38d40) at thread/qthread_unix.cpp:285
#5 0x00007f0e4c761971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#6 0x00007f0e4ed0194d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f0e36b25710 (LWP 10031)):
#0 0x00007f0e4ecf5203 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1 0x00007f0e4b713030 in g_main_context_poll (context=0xd85130, block=<value optimized out>, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.27.4/glib/gmain.c:3400
#2 g_main_context_iterate (context=0xd85130, block=<value optimized out>, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.27.4/glib/gmain.c:3082
#3 0x00007f0e4b713559 in g_main_context_iteration (context=0xd85130, may_block=1) at /build/buildd/glib2.0-2.27.4/glib/gmain.c:3150
#4 0x00007f0e4f8c1f26 in QEventDispatcherGlib::processEvents (this=0xd7ca20, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#5 0x00007f0e4f896362 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6 0x00007f0e4f89659c in QEventLoop::exec (this=0x7f0e36b24d20, flags=...) at kernel/qeventloop.cpp:201
#7 0x00007f0e4f7ad274 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#8 0x00007f0e4f87882f in QInotifyFileSystemWatcherEngine::run (this=0xd7a9f0) at io/qfilesystemwatcher_inotify.cpp:248
#9 0x00007f0e4f7afa2e in QThreadPrivate::start (arg=0xd7a9f0) at thread/qthread_unix.cpp:285
#10 0x00007f0e4c761971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#11 0x00007f0e4ed0194d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f0e538ed800 (LWP 10029)):
[KCrash Handler]
#6 0x00007f0e4c1f7b4c in Marble::MarbleModel::addDownloadPolicies(Marble::GeoSceneDocument*) () from /usr/lib/libmarblewidget.so.10
#7 0x00007f0e4c1f9498 in Marble::MarbleModel::setMapTheme(Marble::G...

[Dario Andres (andresbajotierra)]

[Comment from a bug triager]
- Is the Marble application properly installed and updated ?
As bug 247420 and other reports, this could be caused by some old Marble installation conflicting with the new one.
Thanks

[Biasquez (biasquez)]

ii libmarblewidget10 4:4.5.3-0ubuntu1 Marble globe widget library
ii libmarblewidget11 4:4.5.85-0ubuntu1 Marble globe widget library
ii marble 4:4.5.85-0ubuntu1 globe and map widget
ii marble-data 4:4.5.85-0ubuntu1 data files for Marble
ii marble-plugins 4:4.5.85-0ubuntu1 plugins for Marble

[Dario Andres (andresbajotierra)]

[Comment from a bug triager]
If "libmarblewidget10" is installed, try uninstalling it (and reinstalling "libmarblewidget11 ")

[Biasquez (biasquez)]

uninstalling libmarblewidget10, system removes dikikam too.maybe there is an error with dependency in kubuntu (digikam 1.5.0)

[Johannes Wienke (languitar)]

Where did you get version 11 from? It is not from the standard package sources in maverick.

[Biasquez (biasquez)]

(In reply to comment #5)
> Where did you get version 11 from? It is not from the standard package sources
> in maverick.

i'm using natty

[Johannes Wienke (languitar)]

Then there must be a packaging error. If version 11 is the natty one, then digikam must also be built against this one. having two versions of marblewidget installed is strange.

[Nienhueser (nienhueser)]

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

[Rohan Garg (rohangarg)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 689337 and any other logs that are relevant for this particular issue.

[Caulier-gilles-9 (caulier-gilles-9)]

Not reproducible with 6.0.0