The first instance of this crash happened while I was adding video file content to a directory which digikam manages as an album. Digikam was running at the time. The crash now occurs every time I launch digikam. I have removed all the recently added video files, but the crash still occurs. I queried the database file and found that there are still entries for the media I removed, so I deleted those records. But the crash still occurs. *** CRASH DETAILS *** *** Error in `digikam': free(): invalid next size (fast): 0x00007f8d94322a80 *** KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/brian/.kde/socket-hoskins/kdeinit4__0 QSocketNotifier: Invalid socket 16 and type 'Read', disabling... QSocketNotifier: Invalid socket 19 and type 'Read', disabling... QSocketNotifier: Invalid socket 22 and type 'Read', disabling... QSocketNotifier: Invalid socket 81 and type 'Read', disabling... QSocketNotifier: Invalid socket 84 and type 'Read', disabling... QSocketNotifier: Invalid socket 89 and type 'Read', disabling... QSocketNotifier: Invalid socket 87 and type 'Read', disabling... QSocketNotifier: Invalid socket 80 and type 'Read', disabling... digikam: Fatal IO error: client killed (digikam:5198): GStreamer-CRITICAL **: gstsystemclock: write control failed in wakeup_async: 9:Bad file descriptor Reproducible: Always Steps to reproduce are unknown, since it is not clear to me what has caused the crash to occur. If it was the adding of a "bad file", I cannot be certain which file it was that triggered the problem. Removing all files added that day does not resolve.
digiKam do not use GSTream. Only Phonon components from KDE (used by digiKam to play video) use GStreamer. Gilles Caulier
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!