| Summary: | Digikam crashes on termination if an audio file played | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Jonathan Ryshpan <jonrysh> |
| Component: | Preview-Video | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.4.0 | |
| Sentry Crash Report: | |||
Your backtrace is not suitable. Please compile digiKam unsing .configure --enable-debug=full Thanks in advance Gilles Caulier I didn't think the backtrace was worth much. This is the digikam from the FC7 repository; is there any way to get a version that will produce a useful backtrace from a repository so as to eliminate the need to recompile a "debug" repository or whatever? Also, I've just noticed that the crash prevents rotated versions of images from being stored, but not comments. Thanks - jon Take a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports . There's lots of info about getting useful backtraces there. Thanks to Philip Rodrigues, here is a more useful backtrace:
Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496430016 (LWP 8958)]
[KCrash handler]
#5 0x0000003bb4a08229 in pthread_mutex_lock () from /lib64/libpthread.so.0
#6 0x0000003bb464f5e3 in XrmDestroyDatabase (db=0x656590) at Xrm.c:2651
#7 0x0000003bb4636c92 in _XFreeDisplayStructure (dpy=0x657e30)
at OpenDis.c:768
#8 0x0000003bb4621cab in XCloseDisplay (dpy=0x657e30) at ClDisplay.c:74
#9 0x0000003c61e92c46 in qt_cleanup () at kernel/qapplication_x11.cpp:2456
#10 0x0000003c61f05c8f in ~QApplication (this=0x7fff20cf3dc0)
at kernel/qapplication.cpp:1084
#11 0x0000000000402cee in main (argc=1, argv=0x7fff20cf4068) at main.cpp:322
Jonathan, No more. The crash is outside digiKam, into multithreading system library Are you more fresh info to report ? Gilles Caulier No more info to report. Any particular questions you would like answered? Jonathan, I just would said than the backtrace do not give us more informations... Gilles What should be done about this crash? Is there anything which could be done on digikam's side here? Arnd, Audio preview in digiKAm is delegate to audio KParts player. We just start and embbed it in preview area. That all. If KPart crash, digiKam will crash too... Gilles If kaffeine is default player for wav-files, then I'd check that it's linked against xcb-library. If not, then it's known kaffeine bug (which is fixed, bug #114198) ldd `which kaffeine` |grep xcb This command tell if kaffeine is linked against libxcb or not. Tommi, thanks a lot! Jonathan, any update on this problem? As far as i can say it should be a kaffeine problem Have a look at: http://bugs.kde.org/show_bug.cgi?id=121921 Angelo Jonathan, Can you test with last stable digiKam 0.9.3 + last kaffeine release to check if problem still exist ? Thanks in advance Gilles Caulier Closing this bug now. This does not mean it is invalid by itself, but without updated information (with full debug gdb backtrace) using the current 0.9.3 version (or current svn) it is not possible to find the root of the problem. Please feel free to re-open if there is any new information. Thanks a lot for your understanding, Arnd digiKam 5.4.0 bundles will use QtAV framework instead Qt5Multimedia to thumb and play video. The Slideshow tool will also support video/audio as well. QtAV use ffmpeg codecs. It's multi-platform and will always available in OSX, Windows and Linux bundles that digiKam team provide. For Linux packagers, you will need to turn on video support at compilation time and solve QtAV dependencies... See screenshots here : https://www.flickr.com/photos/digikam/30886133553 https://www.flickr.com/photos/digikam/31679362466 https://www.flickr.com/photos/digikam/31572654722 https://www.flickr.com/photos/digikam/31726086736 Bundles have been recompiled are posted to GDrive for testing : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM |
Version: 0.9.2-final (using KDE KDE 3.5.7) Installed from: Fedora RPMs OS: Linux I have an album with both jpeg images and wav audio files. If I play any of the audio files, digikam will crash when it is terminated. 27 ordinary plugins and 20 Kipi plugins are loaded. Here is a backtrace: (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (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 46912505773424 (LWP 7224)] [KCrash handler] #5 0x0000003bb4a08229 in pthread_mutex_lock () from /lib64/libpthread.so.0 #6 0x0000003bb464f5e3 in XrmDestroyDatabase (db=0x620590) at Xrm.c:2651 #7 0x0000003bb4636c92 in _XFreeDisplayStructure (dpy=0x621e30) at OpenDis.c:768 #8 0x0000003bb4621cab in XCloseDisplay (dpy=0x621e30) at ClDisplay.c:74 #9 0x0000003c61e92c46 in qt_cleanup () from /usr/lib64/qt-3.3/lib/libqt-mt.so.3 #10 0x0000003c61f05c8f in QApplication::~QApplication$base () from /usr/lib64/qt-3.3/lib/libqt-mt.so.3 #11 0x0000000000402cee in main () BTW: How do I attach things to the bug report?