173995 – Digikam crashes on loading main view

Bug 173995 - Digikam crashes on loading main view

Summary: Digikam crashes on loading main view

Status:	RESOLVED FIXED

Alias:	None

Product:	digikam
Classification:	Applications
Component:	Preview-Image (show other bugs)
Version:	unspecified
Platform:	Compiled Sources Linux

Importance:	NOR crash
Target Milestone:	---
Assignee:	Digikam Developers

URL:
Keywords:

Depends on:
Blocks:

Reported:	2008-10-31 21:06 UTC by Luca Giambonini
Modified:	2017-07-23 08:07 UTC (History)
CC List:	2 users (show)

See Also:
Latest Commit:
Version Fixed In:	5.7.0

Attachments
backtrace digikam (2.08 KB, text/plain) 2008-11-01 00:27 UTC, Luca Giambonini	Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description Luca Giambonini 2008-10-31 21:06:13 UTC

Version:           0.10.0-beta6 (rev.: 877980) (using Devel)
OS:                Linux
Installed from:    Compiled sources

Qt: 4.4.1
KDE: 4.1.71 (KDE 4.1.71 (KDE 4.2 >= 20081023))
digiKam: 0.10.0-beta6 (rev.: 877980)

compiled using kdesvn-build with cmake-options: - DCMAKE_BUILD_TYPE=debugfull - DKDE4_BUILD_TESTS:BOOL=OFF  
  
(sorry in advance for my English)
I don't know exactly from which revision the problem has started, but I'm sure that 3 weeks ago the crashes didn't happen.  
  
How to reproduce:  
when digikam start I can seen the spash screen and as last writing that can be read in the splash screen is "initialisation main view" ("inizializzazione vista principale" in Italian).  Then the contours of the principal window of digikam are seen as a flash and then the segmentation fault.
  
I have tried to cancel all the configurations files in ~/.kde4 but the problem persist.  
  
I have done a "strace digikam" and does hang 1.5MB can help? (i will attach later if request)

is it perhaps related to this? http://bugs.kde.org/show_bug.cgi?id=173645

------------
digikam(4125)/digikam (core) main: Root Album Path:  "/home/luca/test"
digikam(4125)/digikam (core) main: Database Path:  "/home/luca/"
digikam(4125)/digikam (core) Digikam::SchemaUpdater::update: SchemaUpdater update
digikam(4125)/digikam (core) Digikam::SchemaUpdater::startUpdates: Have a database structure version  "5"
digikam(4125)/digikam (core) Digikam::SchemaUpdater::makeUpdates: makeUpdates  5  to  5
digikam(4125)/digikam (core) Digikam::CollectionManagerPrivate::actuallyListVolumes: listFromType
digikam(4125)/digikam (core) Digikam::CollectionManagerPrivate::actuallyListVolumes: got listFromType
digikam(4125)/digikam (core) Digikam::AlbumRootLocation::AlbumRootLocation: Creating new Location  "/luca/test"  uuid  "volumeid:?uuid=9bc7f896-5910-4c9c-9247-4741b06eecb2"
digikam(4125)/digikam (core) Digikam::CollectionManager::updateLocations: location for  "/home/luca/test" is available  true
Segmentation fault

Comment 1 caulier.gilles 2008-11-01 00:01:24 UTC

Please attach a gdb backtrace like it's explained at this url:  
http://www.digikam.org/drupal/contrib

Thanks in advance

Gilles Caulier

Comment 2 Luca Giambonini 2008-11-01 00:27:14 UTC

Created attachment 28258 [details]
backtrace digikam

Do I have to activate the debug of the QT for a better backtrace? (installing on ubuntu the package libqt4-dbg?)
Thanks for this amazing program.

Comment 3 caulier.gilles 2008-11-01 00:34:08 UTC

you need to install the debug packages for digiKam, kipi-plugins and other shared libraries used...

Gilles Caulier

Comment 4 Luca Giambonini 2008-11-02 00:17:17 UTC

I have resolved updating ubuntu from the version 8.04 to the 8.10. I don't have idea of what has been updated, maybe are the QT library or others libraies, but now all work great.  
  
I apologize if I have opened this bug that at the end doesn't result inherent to digikam. For me can be closed. (invalid)
Thanks for the patience.
Luca

Comment 5 caulier.gilles 2008-11-02 01:34:17 UTC

Thanks Luca for the report. I close this file now...

Gilles Caulier

Comment 6 Jay Ambee 2009-01-30 12:34:48 UTC

Bug seems not to be resolved in Opensuses 11.1 actual KDE 4.2 versions (dating from 30.01.08. DigiKam still crashes on startup after splash screen with the following info (backtrace obviously does not work):

Eine korrekte Rückverfolgung ist nicht möglich.
Wahrscheinlich sind die Dateien Ihres Systems in einer Weise erstellt worden, die eine solche Rückverfolgung (Backtrace) nicht erlaubt. Oder der so genannte „Stack Frame“ für das Programm wurde durch den Absturz unbrauchbar gemacht.

[?1034h(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 0xb23b7b90 (LWP 8400)]
[New Thread 0xb1b89b90 (LWP 8399)]
[New Thread 0xb2f8ab90 (LWP 8396)]
(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)
(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)
(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)
(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)
0xffffe430 in __kernel_vsyscall ()
[Current thread is 1 (Thread 0xb4676700 (LWP 8395))]

Thread 4 (Thread 0xb2f8ab90 (LWP 8396)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb577ac35 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb57da872 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#3  0x0827e599 in ?? ()
#4  0xb57d985e in ?? () from /usr/lib/libQtCore.so.4
#5  0xb57771b5 in start_thread () from /lib/libpthread.so.0
#6  0xb55ba38e in clone () from /lib/libc.so.6

Thread 3 (Thread 0xb1b89b90 (LWP 8399)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb577ac35 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb57da872 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#3  0xb720262a in Digikam::LoadSaveThread::run() () from /usr/lib/libdigikamcore.so.1
#4  0xb57d985e in ?? () from /usr/lib/libQtCore.so.4
#5  0xb57771b5 in start_thread () from /lib/libpthread.so.0
#6  0xb55ba38e in clone () from /lib/libc.so.6

Thread 2 (Thread 0xb23b7b90 (LWP 8400)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb577ac35 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb57da872 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#3  0xb720262a in Digikam::LoadSaveThread::run() () from /usr/lib/libdigikamcore.so.1
#4  0xb57d985e in ?? () from /usr/lib/libQtCore.so.4
#5  0xb57771b5 in start_thread () from /lib/libpthread.so.0
#6  0xb55ba38e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb4676700 (LWP 8395)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb5582e96 in nanosleep () from /lib/libc.so.6
#2  0xb5582c7e in sleep () from /lib/libc.so.6
#3  0xb6904ada in ?? () from /usr/lib/libkdeui.so.5
#4  0xb690550c in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb58df317 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#7  0xb7f44553 in ?? () from /usr/lib/libphonon.so.4
#8  0xb7f2fd89 in ?? () from /usr/lib/libphonon.so.4
#9  0xb7f31d52 in ?? () from /usr/lib/libphonon.so.4
#10 0xb7f30735 in ?? () from /usr/lib/libphonon.so.4
#11 0xb7f3df35 in ?? () from /usr/lib/libphonon.so.4
#12 0xb7f3e220 in Phonon::VideoPlayer::VideoPlayer(Phonon::Category, QWidget*) () from /usr/lib/libphonon.so.4
#13 0x08271707 in ?? ()
#14 0x082243b3 in ?? ()
#15 0x0824afaa in ?? ()
#16 0x08236293 in ?? ()
#17 0x08241533 in ?? ()
#18 0x082a12e4 in ?? ()
#19 0xb54ff705 in __libc_start_main () from /lib/libc.so.6
#20 0x0808d521 in _start ()

Since I have quite some pictures to edit, a  resolution would be greatly appreciated! ;-)

Thanks a lot
Jay

Comment 7 caulier.gilles 2009-01-30 12:46:03 UTC

#12 0xb7f3e220 in Phonon::VideoPlayer::VideoPlayer(Phonon::Category, QWidget*) () from /usr/lib/libphonon.so.4

It's Phonon + libXine issue, not digiKam...

Gilles Caulier

Comment 8 Jay Ambee 2009-01-30 13:37:12 UTC

Okay ... nice to know, but doesn't help me much for now ...
Do you want me to file the bug again to the phonon / libxine group?

And sorry, but if there is an interaction of phonon/libXine with digiKam,
shouldn't that be of interest to you too?? ... In the end this causes digiKam ANY time to crash ... most times without that handy bugreport ...

Sorry for me insisting ...
Jay

Comment 9 Andi Clemens 2009-01-30 13:44:12 UTC

Seems to be a packaging problem, because none of us devs (or other users) have this problem.
What distro are you using? Which libraries (phonon, kdelibs, qt, xine)?

Andi

Comment 10 Andi Clemens 2009-01-30 13:45:49 UTC

Oh just read it: OpenSuse 11.1

> Eine korrekte Rückverfolgung ist nicht möglich. 
Klingt ja wie ein Zitat der deutschenn Post :-)

Comment 11 caulier.gilles 2009-01-30 13:46:36 UTC

This one is a wonderfull example :

http://bugs.kde.org/show_bug.cgi?id=180701

Look like the crash is duing of a bad translation file.

anyway, digiKam has not in charge all crashes which depand of separated components used, as Phonon, or Marble...

Gilles Caulier

Comment 12 Jay Ambee 2009-01-30 14:20:54 UTC

(In reply to comment #10)
> Oh just read it: OpenSuse 11.1
> 
> > Eine korrekte Rückverfolgung ist nicht möglich. 
> Klingt ja wie ein Zitat der deutschenn Post :-)
> 
hmmm ... also wenn ich mich recht entsinne ist das der Text im 
Dialog ... wer den wohl geschrieben hat ... ;-)

... aber ich kann mich auch täuschen ...

Comment 13 Matthias Welwarsky 2009-01-30 14:22:44 UTC

(In reply to comment #11)
> anyway, digiKam has not in charge all crashes which depand of separated
> components used, as Phonon, or Marble...

Of course. But "Upstream" should still be notified about that problem. Better for overall user experience. Not solving a problem because it "worksforme" often hides latent problems in own code.

> 
> Gilles Caulier
>

Comment 14 Jay Ambee 2009-01-30 14:26:14 UTC

(In reply to comment #11)
> This one is a wonderfull example :
> 
> http://bugs.kde.org/show_bug.cgi?id=180701
> 
> Look like the crash is duing of a bad translation file.
> 
> anyway, digiKam has not in charge all crashes which depand of separated
> components used, as Phonon, or Marble...
> 
> Gilles Caulier
> 

I know you are not, nor the program ... but who else should I ask for a solution??

Comment 15 Jay Ambee 2009-01-30 14:29:44 UTC

(In reply to comment #9)
> Seems to be a packaging problem, because none of us devs (or other users) have
> this problem.
> What distro are you using? Which libraries (phonon, kdelibs, qt, xine)?
> 
> Andi
> 

I'm using Opensuse 11.1, with the fresh DE 4.2 packages from this morning ... ;-)
Not sure whether libXine has been updated during that run ... but problem existed already before with earlier versions

Comment 16 Andi Clemens 2009-01-30 14:42:41 UTC

And what libxine version are you using?
Mine is 1.1.16.1

and phonon: 4.3.0

Andi

Comment 17 caulier.gilles 2009-01-30 14:43:41 UTC

When crash appear in Phonon + libXine, report a file in Phonon component from KDE bugzilla.

Gilles Caulier

Comment 18 Jay Ambee 2009-01-30 14:54:01 UTC

(In reply to comment #16)
> And what libxine version are you using?
> Mine is 1.1.16.1
> 
> and phonon: 4.3.0
> 
> Andi
> 

The versions that were installed are: (on Opensuse 11.1)

libXine 1.1.16.1-0.pm.1

phonon 4.3.0-26.8

Comment 19 caulier.gilles 2017-07-23 08:07:41 UTC

This problem is relevant of digiKam video preview using Phonon which have been moved to QtAV/ffmpeg since 5.2.0. It will never reproducible.