Bug#491458: digikam doesn't start-up

[Luc Castermans-2]

Package: digikam
Version: 2:0.10.0~rc2-1
Followup-For: Bug #491458

herewith the dump:

Application: digiKam (digikam), signal SIGSEGV
[Current thread is 1 (Thread 0xb47c06f0 (LWP 3534))]

Thread 4 (Thread 0xb3176b90 (LWP 3537)):
#0  0xb7f55424 in __kernel_vsyscall ()
#1  0xb50a0025 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb54977fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb567d852 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#4  0x0828e879 in ?? ()
#5  0xb567c83e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb509c4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb54896de in clone () from /lib/i686/cmov/libc.so.6

Thread 3 (Thread 0xb1e2db90 (LWP 3544)):
#0  0xb7f55424 in __kernel_vsyscall ()
#1  0xb50a0025 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb54977fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb567d852 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#4  0xb719cbda in Digikam::LoadSaveThread::run() () from /usr/lib/libdigikamcore.so.1
#5  0xb567c83e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb509c4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb54896de in clone () from /lib/i686/cmov/libc.so.6

Thread 2 (Thread 0xb262eb90 (LWP 3545)):
#0  0xb7f55424 in __kernel_vsyscall ()
#1  0xb50a0025 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb54977fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb567d852 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#4  0xb719cbda in Digikam::LoadSaveThread::run() () from /usr/lib/libdigikamcore.so.1
#5  0xb567c83e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb509c4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb54896de in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb47c06f0 (LWP 3534)):
#0  0xb7f55424 in __kernel_vsyscall ()
#1  0xb5444ef6 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb5444d0f in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb68d9128 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000000 in ?? ()



-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages digikam depends on:
ii  kde-icons-oxygen       4:4.2.0-1         Oxygen icon theme for KDE 4
ii  kdebase-runtime        4:4.2.0-1         runtime components from the offici
ii  kdelibs5               4:4.2.0-3         core libraries for all KDE 4 appli
ii  kdepimlibs5            4:4.2.0-1         core libraries for KDE PIM 4 appli
ii  libc6                  2.7-18            GNU C Library: Shared libraries
ii  libgcc1                1:4.3.3-4         GCC support library
ii  libgphoto2-2           2.4.1-3           gphoto2 digital camera library
ii  libgphoto2-port0       2.4.1-3           gphoto2 digital camera port librar
ii  libjasper1             1.900.1-5.1       The JasPer JPEG-2000 runtime libra
ii  libjpeg62              6b-14             The Independent JPEG Group's JPEG
ii  libkdcraw7             4:4.2.0-1         Raw picture decoding C++ library (
ii  libkexiv2-7            4:4.2.0-1         Qt like interface for the libexiv2
ii  libkipi6               4:4.2.0-1         library for apps that want to use
ii  liblcms1               1.17.dfsg-1       Color management library
ii  libmarble4             4:4.2.0-1         Marble globe widget library
ii  libphonon4             4:4.3.0-2         Phonon multimedia framework for Qt
ii  libpng12-0             1.2.33-2          PNG library - runtime
ii  libqt4-dbus            4.5.0~rc1-2       Qt 4 D-Bus module
ii  libqt4-network         4.5.0~rc1-2       Qt 4 network module
ii  libqt4-qt3support      4.5.0~rc1-2       Qt 3 compatibility library for Qt
ii  libqt4-sql             4.5.0~rc1-2       Qt 4 SQL module
ii  libqt4-sql-sqlite      4.5.0~rc1-2       Qt 4 SQLite 3 database driver
ii  libqt4-svg             4.5.0~rc1-2       Qt 4 SVG module
ii  libqt4-xml             4.5.0~rc1-2       Qt 4 XML module
ii  libqtcore4             4.5.0~rc1-2       Qt 4 core module
ii  libqtgui4              4.5.0~rc1-2       Qt 4 GUI module
ii  libstdc++6             4.3.3-4           The GNU Standard C++ Library v3
ii  libtiff4               3.8.2-11          Tag Image File Format (TIFF) libra
ii  phonon                 4:4.3.0-2         metapackage for Phonon multimedia
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages digikam recommends:
ii  konqueror                     4:4.2.0-1  KDE 4's advanced file manager, web

Versions of packages digikam suggests:
ii  digikam-doc                   0.9.5-1    handbook for digikam and showfoto

-- no debconf information



_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Mark Purcell]

On Tuesday 24 February 2009 18:20:11 Luc Castermans wrote:
> Application: digiKam (digikam), signal SIGSEGV

Thanks Luc, Martial,

Could I ask do you have gpsd installed?

I can crash digikam if my gpsd is running and isn't locked in.

If I stop gpsd `/etc/init.d/gpsd stop`

digikam starts fine.

Mark

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[babatoko]

Hi there,

I'm not running that package on both following platform i386 and X86_64.
On both platform, digikam crashs.

Let me know if I can do something else to help.

Martial
On Tue, 24 Feb 2009 21:13:23 Mark Purcell wrote:

> On Tuesday 24 February 2009 18:20:11 Luc Castermans wrote:
> > Application: digiKam (digikam), signal SIGSEGV
>
> Thanks Luc, Martial,
>
> Could I ask do you have gpsd installed?
>
> I can crash digikam if my gpsd is running and isn't locked in.
>
> If I stop gpsd `/etc/init.d/gpsd stop`
>
> digikam starts fine.
>
> Mark

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Luc Castermans-2]

Mark Purcell schreef:
> On Tuesday 24 February 2009 18:20:11 Luc Castermans wrote:
>  
>> Application: digiKam (digikam), signal SIGSEGV
>>    
>
> Thanks Luc, Martial,
>
> Could I ask do you have gpsd installed?
>  
No, it is not even installed.

I did a fresh KDE 4.2 install, on top of Lenny on a Dell L400 laptop
(Pentium III, only 128MB RAM).  It did create the digikam4.db file after
scanning the tree. It´s size is about 5x the digikam3 file. Is that normal?

luc@mestreech:/home/filmpje/fotos$ ls -l --si digikam*
-rw-rw-r-- 1 filmpje users 677k feb 22 11:52 digikam3.db
-rw-rw-r-- 1 luc     users 3,2M feb 24 14:06 digikam4.db

When I start it, it crashes when it builds the mainpage, so when I read
the subsequent messages in the splash screen, it crashes shortly
after displaying message 3 below:

1. Scan albums
2. Search for images in individual albums
3. Preparing main-page

Hope this helps!
> I can crash digikam if my gpsd is running and isn't locked in.
>
> If I stop gpsd `/etc/init.d/gpsd stop`
>
> digikam starts fine.
>
> Mark
>  


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Mark Purcell]

On Tuesday 24 February 2009 20:42:44 Martial Paupe wrote:
> Let me know if I can do something else to help.

Can you start without any pictures in your album path?

Mark

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[babatoko]

On Wed, 25 Feb 2009 07:29:13 Mark Purcell wrote:
> On Tuesday 24 February 2009 20:42:44 Martial Paupe wrote:
> > Let me know if I can do something else to help.
>
> Can you start without any pictures in your album path?
I've tried on a fresh install (i386) and without album tree and DB at begining. The other one was on x86_64 and was not a fresh install with an album tree and DB already there. It was update from kde 3.5 to 4.2.0 and Digikam was updated at that time as well.

Both figures crash at the start up.

Martial

>
> Mark

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel