Application: digikam (1.2.0) KDE Platform Version: 4.4.5 (KDE 4.4.5) Qt Version: 4.6.3 Operating System: Linux 2.6.33.3-85.fc13.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: After updating from Fedora 12 to Fedora 13, the first time I started digikam it asked me to be configured. When I used the button to select my library path, digikam crashed. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [KCrash Handler] #5 0x00000033c4fde2e3 in KFileDialog::getExistingDirectory(KUrl const&, QWidget*, QString const&) () from /usr/lib64/libkio.so.5 #6 0x00000033c501034b in KUrlRequester::KUrlRequesterPrivate::_k_slotOpenDialog() () from /usr/lib64/libkio.so.5 #7 0x00000033c5010ba9 in KUrlRequester::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5 #8 0x00000033c2b66a36 in QMetaObject::activate (sender=0x1d9d650, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff433b5ad0) at kernel/qobject.cpp:3295 #9 0x00000033cc5e2e12 in QAbstractButton::clicked (this=<value optimized out>, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:206 #10 0x00000033cc3310ab in QAbstractButtonPrivate::emitClicked (this=<value optimized out>) at widgets/qabstractbutton.cpp:546 #11 0x00000033cc33242b in QAbstractButtonPrivate::click (this=0x1d9ee50) at widgets/qabstractbutton.cpp:539 #12 0x00000033cc33269c in QAbstractButton::mouseReleaseEvent (this=0x1d9d650, e=0x7fff433b6420) at widgets/qabstractbutton.cpp:1121 #13 0x00000033cbff648a in QWidget::event (this=0x1d9d650, event=0x7fff433b6420) at kernel/qwidget.cpp:8044 #14 0x00000033cbfab39c in QApplicationPrivate::notify_helper (this=0x1934d10, receiver=0x1d9d650, e=0x7fff433b6420) at kernel/qapplication.cpp:4306 #15 0x00000033cbfb1e2d in QApplication::notify (this=<value optimized out>, receiver=0x1d9d650, e=0x7fff433b6420) at kernel/qapplication.cpp:3871 #16 0x00000033c4007016 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #17 0x00000033c2b53ddc in QCoreApplication::notifyInternal (this=0x7fff433b7160, receiver=0x1d9d650, event=0x7fff433b6420) at kernel/qcoreapplication.cpp:726 #18 0x00000033cbfb101e in sendEvent (receiver=0x1d9d650, event=0x7fff433b6420, alienWidget=0x1d9d650, nativeWidget=0x7fff433b7120, buttonDown=0x33cca2f088, lastMouseReceiver=..., spontaneous=true) at ../../src/corelib/kernel/qcoreapplication.h:215 #19 QApplicationPrivate::sendMouseEvent (receiver=0x1d9d650, event=0x7fff433b6420, alienWidget=0x1d9d650, nativeWidget=0x7fff433b7120, buttonDown=0x33cca2f088, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2971 #20 0x00000033cc023155 in QETWidget::translateMouseEvent (this=0x7fff433b7120, event=<value optimized out>) at kernel/qapplication_x11.cpp:4380 #21 0x00000033cc021acc in QApplication::x11ProcessEvent (this=0x7fff433b7160, event=0x7fff433b6d40) at kernel/qapplication_x11.cpp:3513 #22 0x00000033cc04ab92 in x11EventSourceDispatch (s=0x1938a30, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #23 0x00000033bd23bd02 in g_main_dispatch (context=0x1937920) at gmain.c:1960 #24 IA__g_main_context_dispatch (context=0x1937920) at gmain.c:2513 #25 0x00000033bd23fae8 in g_main_context_iterate (context=0x1937920, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2591 #26 0x00000033bd23fc9c in IA__g_main_context_iteration (context=0x1937920, may_block=1) at gmain.c:2654 #27 0x00000033c2b79863 in QEventDispatcherGlib::processEvents (this=0x18fa2a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412 #28 0x00000033cc04a84e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #29 0x00000033c2b52822 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #30 0x00000033c2b52aec in QEventLoop::exec (this=0x7fff433b7070, flags=...) at kernel/qeventloop.cpp:201 #31 0x00000033cc42d97e in QDialog::exec (this=0x7fff433b7120) at dialogs/qdialog.cpp:546 #32 0x0000000000700c07 in ?? () #33 0x00000033bba1ec5d in __libc_start_main (main=0x6fe9d0, argc=3, ubp_av=0x7fff433b8018, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff433b8008) at libc-start.c:226 #34 0x000000000046f369 in _start () Possible duplicates by query: bug 170391. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 170391 ***
I am not sure about this being a duplicate of #170391 as #170391 is itself a duplicate of #156869 and both were bugs in 4.1 and marked as resolved in a later version of KDE 4.1. This bug is happening with KDE 4.4. Or is there a regression and should #156869 be reopened?
This can be some sort of binary incompatibility, broken packages, packages from different versions etc, my guess is a downstream issue. In any case t's happening in kdeui (KUrlRequester) libraries.
*** Bug 254544 has been marked as a duplicate of this bug. ***
I know, this has nothing to do about the crash above, but bugs.kde.org unfortunately bugs.kde.org is so "optimized" against filing new bugs that this seems to be the only option left: Application: digikam (3.5.0) KDE Platform Version: 4.13.3 Qt Version: 4.8.6 Operating System: Linux 3.13.0-62-generic x86_64 Distribution: Ubuntu 14.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: I was just starting digikam. The splash screen shows for about a minute, then it segfaults This started happening after I upgraded from 12.04 to 14.04 The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f64b4da5ac0 (LWP 17174))] Thread 5 (Thread 0x7f648e7b2700 (LWP 17176)): #0 0x00007f64ae7c512d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f6493580248 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x00007f64a9a55182 in start_thread (arg=0x7f648e7b2700) at pthread_create.c:312 #3 0x00007f64ae7d247d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f647c265700 (LWP 17177)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f64af5b3816 in wait (time=18446744073709551615, this=0x2216940) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x2216850, mutex=mutex@entry=0x2216848, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x00000000005d5ede in Digikam::ScanController::run (this=0x21510d0) at /build/buildd/digikam-3.5.0/core/digikam/database/scancontroller.cpp:725 #4 0x00007f64af5b332f in QThreadPrivate::start (arg=0x21510d0) at thread/qthread_unix.cpp:349 #5 0x00007f64a9a55182 in start_thread (arg=0x7f647c265700) at pthread_create.c:312 #6 0x00007f64ae7d247d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f646ffff700 (LWP 17178)): #0 0x00007f64a72be61a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007f64a72be9a9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f64a727c680 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f64a727cf03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f64a727d0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f64af6e27be in QEventDispatcherGlib::processEvents (this=0x7f64640008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x00007f64af6b40af in QEventLoop::processEvents (this=this@entry=0x7f646fffeae0, flags=...) at kernel/qeventloop.cpp:149 #7 0x00007f64af6b43a5 in QEventLoop::exec (this=this@entry=0x7f646fffeae0, flags=...) at kernel/qeventloop.cpp:204 #8 0x00007f64af5b0c5f in QThread::exec (this=this@entry=0x21baf70) at thread/qthread.cpp:537 #9 0x00007f64af695823 in QInotifyFileSystemWatcherEngine::run (this=0x21baf70) at io/qfilesystemwatcher_inotify.cpp:265 #10 0x00007f64af5b332f in QThreadPrivate::start (arg=0x21baf70) at thread/qthread_unix.cpp:349 #11 0x00007f64a9a55182 in start_thread (arg=0x7f646ffff700) at pthread_create.c:312 #12 0x00007f64ae7d247d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f6463fff700 (LWP 17195)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f64af5b3816 in wait (time=18446744073709551615, this=0x222c720) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x24f02a0, mutex=mutex@entry=0x24f0298, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x00007f64b242c79a in Digikam::ParkingThread::run (this=0x24f0280) at /build/buildd/digikam-3.5.0/core/libs/threads/threadmanager.cpp:119 #4 0x00007f64af5b332f in QThreadPrivate::start (arg=0x24f0280) at thread/qthread_unix.cpp:349 #5 0x00007f64a9a55182 in start_thread (arg=0x7f6463fff700) at pthread_create.c:312 #6 0x00007f64ae7d247d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f64b4da5ac0 (LWP 17174)): [KCrash Handler] #6 data (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135 #7 qGetPtrHelper<QScopedPointer<QObjectData> > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2467 #8 d_func (this=0x0) at widgets/qabstractbutton.h:171 #9 QAbstractButton::setChecked (this=0x0, checked=checked@entry=true) at widgets/qabstractbutton.cpp:738 #10 0x00007f64b24a4988 in Digikam::MetadataWidget::setMode (this=0x2c7ee70, mode=2) at /build/buildd/digikam-3.5.0/core/libs/widgets/metadata/metadatawidget.cpp:465 #11 0x00007f64b24cb2f0 in Digikam::ImagePropertiesColorsTab::readSettings (this=0x2c3bc00, group=...) at /build/buildd/digikam-3.5.0/core/libs/imageproperties/imagepropertiescolorstab.cpp:337 #12 0x00007f64b24bfbd9 in Digikam::ImagePropertiesSideBar::doLoadState (this=this@entry=0x2b99150) at /build/buildd/digikam-3.5.0/core/libs/imageproperties/imagepropertiessidebar.cpp:357 #13 0x00000000004a7782 in Digikam::ImagePropertiesSideBarDB::doLoadState (this=0x2b99150) at /build/buildd/digikam-3.5.0/core/libs/imageproperties/imagepropertiessidebardb.cpp:643 #14 0x00007f64b2454efa in Digikam::StateSavingObject::loadState (this=0x2b99180) at /build/buildd/digikam-3.5.0/core/libs/widgets/common/statesavingobject.cpp:183 #15 0x0000000000660a36 in Digikam::DigikamView::loadViewState (this=this@entry=0x261f620) at /build/buildd/digikam-3.5.0/core/digikam/views/digikamview.cpp:692 #16 0x0000000000660c89 in Digikam::DigikamView::slotAllAlbumsLoaded (this=0x261f620) at /build/buildd/digikam-3.5.0/core/digikam/views/digikamview.cpp:844 #17 0x0000000000661fba in Digikam::DigikamView::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at /build/buildd/digikam-3.5.0/obj-x86_64-linux-gnu/core/digikam/digikamview.moc:332 #18 0x00007f64af6c987a in QMetaObject::activate (sender=sender@entry=0x2216800, m=m@entry=0x844e60 <Digikam::AlbumManager::staticMetaObject>, local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x0) at kernel/qobject.cpp:3539 #19 0x00000000005af9bb in signalAllAlbumsLoaded (this=0x2216800) at /build/buildd/digikam-3.5.0/obj-x86_64-linux-gnu/core/digikam/albummanager.moc:273 #20 Digikam::AlbumManager::startScan (this=0x2216800) at /build/buildd/digikam-3.5.0/core/digikam/album/albummanager.cpp:1114 #21 0x00000000005984c1 in Digikam::DigikamApp::DigikamApp (this=0x2407cb0, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /build/buildd/digikam-3.5.0/core/digikam/main/digikamapp.cpp:287 #22 0x0000000000491cfa in main (argc=<optimized out>, argv=<optimized out>) at /build/buildd/digikam-3.5.0/core/digikam/main/main.cpp:189 Report to https://bugs.kde.org/
Alain, bugs.kde.org refused to accept your crash report, because it is from a very old version of digikam. Instead of posting it to an unrelated bug, you could update your digikam version.
This is the version that is currently included in the current stable Kubuntu... Another alternative, I could just switch back to the Gimp instead :-)
And, btw, how am I supposed to know? Indeed, the system didn't say anywhere *why* it was refusing this bug report... Maybe it would help here to be a little bit more explicit in the error messages? Not all users are IQ 80 ex-Windows users, some of us can _understand_ messages when they are actually displayed...
Are you still able to reproduce the problem with digiKam 5.0.0-Beta7 ? Please try to build fresh digiKam, maybe you're missing a library or package.
The original backtrace report a binary compatibility problem with KFileDialog With since 5.0.0, we do not use KFileDialog in favor of pure Qt5 API, to limit BC side effects. You can test the current development AppImage bundle here : https://files.kde.org/digikam/ Gilles Caulier