| Summary: | digikam import crashes when you select video files | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Jim Shipman <JimShip> |
| Component: | Import-Settings | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, JimShip, tpr |
| Priority: | NOR | ||
| Version: | 4.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 6.0.0 | |
| Sentry Crash Report: | |||
|
Description
Jim Shipman
2012-07-09 00:26:10 UTC
digiKam 3.5.0 is out. Can you give a fresh feedback about your report ? Crash still reproducible ? Thanks in advance Gilles Caulier This crash happens on multiple systems, including a fresh fedora 19 install. The following is the output of the message log during the crash. This has been going on for a long time and is reproducible on both my systems (including a fresh install). Nov 3 13:41:56 laurie gnome-session[2558]: digikam: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Nov 2 13:41:56 laurie gnome-session[2558]: QSocketNotifier: Invalid socket 19 and type 'Read', disabling... Nov 2 13:41:56 laurie gnome-session[2558]: digikam: Fatal IO error 9 (Bad file descriptor) on X server :0. Nov 2 13:41:56 laurie gnome-session[2558]: KCrash: Application 'digikam' crashing... Nov 2 13:41:56 laurie gnome-session[2558]: KCrash: Attempting to start /usr/libexec/kde4/drkonqi from kdeinit Nov 2 13:41:56 laurie gnome-session[2558]: Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. Nov 2 13:41:56 laurie gnome-session[2558]: sock_file=/home/shipman/.kde/socket-laurie.family.net/kdeinit4__0 Nov 2 13:41:56 laurie gnome-session[2558]: drkonqi(2334): The specified process does not exist. Actually the crash you're talking about is a different one. The given codepath does not exist at all in recent version of digiKam because the filtering is commented out in import ui and that FilterCombobox is not used elsewhere at all. That doesn't mean that there's no crash inside that code, but it'll need to be debugged when the filtering is restored. Filtering is now re-enabled, please test if you can still reproduce this. digiKam 4.0.0 is out : http://www.digikam.org/node/713 Please check if this entry still valid with this new version. Thanks in advance Gilles Caulier This crash now happens after import while digikam is scanning for metadata in the background. Exiv2 crashes whenever it runs into a file that it doesn't understand and this brings digikam down with it. I reported this to the exiv2 bug tracker and they said that M2TS (MTS) video files were not suppoted by exiv2 and digikam should not have called exiv2 for unsupported file types. They put my bug in as a "feature request" with low priority. Right now I can't run digikam because right after it starts (idle to me, but scanning metadata in the background) it crashes because of exiv2. digikam would be much more robust if it would trap these kind of exceptions and recover instead of simply crashing. You will always be vulnerable to crashes by your dependencies unless you trap them and handle them yourself. Jim Shipman digikam would be much more robust if it would trap these kind of exceptions and recover instead of simply crashing ==> crash must be handle properly in low level interface (Exiv2). After all, Exiv2 know better which files can be managed or not... I close it as UPSTREAM (relevant of Exiv2) Gilles Caulier Fixed with next 6.0.0 release which integrate a nex video metadata parser based on FFMPEg instead Exiv2. Gilles Caulier |