Bug 274863

Summary: Digikam crashes on close of application
Product: [Applications] digikam Reporter: Russ Fineman <upscope>
Component: Portability-RuntimeAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: caulier.gilles, upscope
Priority: NOR    
Version: 2.0.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In: 5.1.0
Sentry Crash Report:

Description Russ Fineman 2011-06-03 20:41:13 UTC 
Application: digikam (2.0.0-beta5)
KDE Platform Version: 4.6.3 (4.6.3) "release 4"
Qt Version: 4.7.3
Operating System: Linux 2.6.37.6-0.5-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Was trying to create database on localhost. Failed.

Then clicked close application.

Got error and box to submit report.

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Aborted
[Current thread is 1 (Thread 0x7fd141db7860 (LWP 31431))]

Thread 4 (Thread 0x7fd121a7d700 (LWP 31450)):
#0  0x00007fd13927a503 in poll () from /lib64/libc.so.6
#1  0x00007fd1333fd114 in ?? () from /lib64/libglib-2.0.so.0
#2  0x00007fd1333fd650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#3  0x00007fd13b1af286 in QEventDispatcherGlib::processEvents (this=0xd28bb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007fd13b1838d2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fd13b183ae5 in QEventLoop::exec (this=0x7fd121a7cce0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007fd13b0987a4 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:492
#7  0x00007fd13b165008 in QInotifyFileSystemWatcherEngine::run (this=0xeec860) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fd13b09b095 in QThreadPrivate::start (arg=0xeec860) at thread/qthread_unix.cpp:320
#9  0x00007fd13ae0aa3f in start_thread () from /lib64/libpthread.so.0
#10 0x00007fd13928367d in clone () from /lib64/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7fd12117b700 (LWP 31481)):
#0  0x00007fd13ae0f38c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fd13b09b77b in wait (this=<value optimized out>, mutex=0x1047e18, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x1047e18, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x00000000005c9e68 in _start ()

Thread 2 (Thread 0x7fd12097a700 (LWP 31486)):
#0  0x00007fd13ae0f38c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fd13b09b77b in wait (this=<value optimized out>, mutex=0x208b658, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x208b658, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x00007fd13e8d4f07 in ?? () from /usr/lib64/libdigikamcore.so.2
#4  0x00007fd13b09b095 in QThreadPrivate::start (arg=0x208b640) at thread/qthread_unix.cpp:320
#5  0x00007fd13ae0aa3f in start_thread () from /lib64/libpthread.so.0
#6  0x00007fd13928367d in clone () from /lib64/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fd141db7860 (LWP 31431)):
[KCrash Handler]
#6  0x00007fd1391e2ab5 in raise () from /lib64/libc.so.6
#7  0x00007fd1391e3fb6 in abort () from /lib64/libc.so.6
#8  0x00007fd13921ddd3 in __libc_message () from /lib64/libc.so.6
#9  0x00007fd1392233b6 in malloc_printerr () from /lib64/libc.so.6
#10 0x00007fd139225b32 in _int_malloc () from /lib64/libc.so.6
#11 0x00007fd139227d99 in malloc () from /lib64/libc.so.6
#12 0x00007fd13b09d2cd in QByteArray::resize (this=0x7fff25c942d0, size=132) at tools/qbytearray.cpp:1386
#13 0x00007fd13b568f11 in KConfigIniBackend::stringToPrintable (aString=..., type=KConfigIniBackend::KeyString) at /usr/src/debug/kdelibs-4.6.3/kdecore/config/kconfigini.cpp:605
#14 0x00007fd13b569434 in KConfigIniBackend::writeEntries (this=<value optimized out>, locale=..., file=..., map=<value optimized out>, defaultGroup=false, firstEntry=@0x7fff25c9444f) at /usr/src/debug/kdelibs-4.6.3/kdecore/config/kconfigini.cpp:326
#15 0x00007fd13b5696b8 in KConfigIniBackend::writeEntries (this=0xba5f00, locale=..., file=..., map=...) at /usr/src/debug/kdelibs-4.6.3/kdecore/config/kconfigini.cpp:362
#16 0x00007fd13b648332 in KConfigIniBackend::writeConfig (this=0xba5f00, locale=..., entryMap=<value optimized out>, options=<value optimized out>, data=...) at /usr/src/debug/kdelibs-4.6.3/kdecore/config/kconfigini.cpp:441
#17 0x00007fd13b5e6983 in KConfig::sync (this=0xba5bf0) at /usr/src/debug/kdelibs-4.6.3/kdecore/config/kconfig.cpp:379
#18 0x00007fd13e90b8cb in Digikam::SearchTextBar::doSaveState() () from /usr/lib64/libdigikamcore.so.2
#19 0x00007fd13e91043a in Digikam::StateSavingObject::saveState() () from /usr/lib64/libdigikamcore.so.2
#20 0x00007fd13e90b590 in Digikam::SearchTextBar::~SearchTextBar() () from /usr/lib64/libdigikamcore.so.2
#21 0x00007fd13e90b6c9 in Digikam::SearchTextBar::~SearchTextBar() () from /usr/lib64/libdigikamcore.so.2
#22 0x00007fd13b196a34 in QObjectPrivate::deleteChildren (this=0x2b14f20) at kernel/qobject.cpp:1955
#23 0x00007fd13a103ee0 in QWidget::~QWidget (this=0x2b14c40, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1631
#24 0x00000000005ed469 in _start ()

Reported using DrKonqi
Comment 1 caulier.gilles 2011-06-05 21:15:25 UTC 
Not reproducible. 2.0.0-beta6 is out. Please try with it...

Gilles Caulier
Comment 2 Marcel Wiesweg 2011-06-11 16:25:46 UTC 
What exactly does this mean:
"Was trying to create database on localhost. Failed."

Probably memory corruption, crash inside frequently used Qt code. Less probable, a kdelibs problem.
Comment 3 Russ Fineman 2011-06-11 20:40:08 UTC 
(In reply to comment #2)
> What exactly does this mean:
> "Was trying to create database on localhost. Failed."
I created the two data bases Digikam needs, then went to digikam as changed the configuration to use the MySQl database I created (Just like kmymoney and amarok). failed to connect to localhost where database resides. Error message said application failed. I click close and got the wizzard to do a back trace.
> 
> Probably memory corruption, crash inside frequently used Qt code. Less
> probable, a kdelibs problem.
Since my other data bases work and I can manually login to the digikam databases from the command line(No tables have been created I thought this was like amarok, where you create datbase, grant permissions etc, then when the application first accessed the database, it created the tables), I do not think its MySQl.

Internal MySQl database works but trying to migrate, gives error that it cannot log in to external (localhost database. I'm using the socket method, no external access to my system accepted).

Let what other information I can provide.

Thanks for your response.
Comment 4 Marcel Wiesweg 2011-06-11 22:57:14 UTC 
Ok I see, MySQL. Seems to be some invalid behavior in error handling secondary to a failed connection to the database.
Comment 5 caulier.gilles 2011-07-02 10:02:22 UTC 
digiKam 2.0.0 RC is out. Please check if crash is reproducible with this version.

Thanks in advance

Gilles Caulier
Comment 6 caulier.gilles 2011-11-03 12:42:25 UTC 
digiKam 2.2.0 is out since few weeks. Crash still valid with this version ?

Gilles Caulier
Comment 7 caulier.gilles 2015-06-27 13:44:41 UTC 
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles caulier
Comment 8 caulier.gilles 2015-08-22 06:38:58 UTC 
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.
Comment 9 caulier.gilles 2016-07-09 16:12:51 UTC 
This problem is not reproducible with last 5.0.0.
I close this file now. Don't hesitate to re-open it if necessary.
Gilles Caulier