[Digikam-devel] [digikam] [Bug 351639] New: crash on start up. Complaint: GStreamer-CRITICAL **: gstsystemclock: write control failed in wakeup_async: 9:Bad file descriptor
Brian J Hoskins
brianjhoskins at gmail.com
Sun Aug 23 11:20:32 BST 2015
https://bugs.kde.org/show_bug.cgi?id=351639
Bug ID: 351639
Summary: crash on start up. Complaint: GStreamer-CRITICAL **:
gstsystemclock: write control failed in wakeup_async:
9:Bad file descriptor
Product: digikam
Version: 4.12.0
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: digikam-devel at kde.org
Reporter: brianjhoskins at gmail.com
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.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Digikam-devel
mailing list