[Bug 902712] New: Digikam 4.3.0 crashes
http://bugzilla.opensuse.org/show_bug.cgi?id=902712 Bug ID: 902712 Summary: Digikam 4.3.0 crashes Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: jonte1@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Digikam 4.3.0 (Builddate 17 September 2014) crashes when I browse in certain directories. It seems to be the same problem already fixed in 13.1 with a newer build. A example: digikam(3391)/KEXIV2: Cannot load metadata from file (Error # 11 : /home/****/*/vol2/My Pictures/England 2002-10/MOV01235.MPG: The file contains data of an unknown image type digikam(3391)/KEXIV2: Cannot load metadata using Exiv2 (Error # 11 : /home/*****/vol2/My Pictures/England 2002-10/MOV01235.MPG: The file contains data of an unknown image type KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/home/*****/.kde4/socket-jodotpc/kdeinit4__0 QSocketNotifier: Invalid socket 15 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... QSocketNotifier: Invalid socket 21 and type 'Read', disabling... QSocketNotifier: Invalid socket 71 and type 'Read', disabling... QSocketNotifier: Invalid socket 78 and type 'Read', disabling... digikam: Fatal IO error: client killed (digikam:3391): GStreamer-CRITICAL **: gstsystemclock: write control failed in wakeup_async: 9:Bad file descriptor -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=902712 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |wbauer@tmo.at Resolution|--- |FIXED --- Comment #1 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Johan Dot from comment #0)
Digikam 4.3.0 (Builddate 17 September 2014) crashes when I browse in certain directories. It seems to be the same problem already fixed in 13.1 with a newer build.
Those fixes from KDE:Extra are already in 13.2 as well. But they have been added on Sept. 24th (for 13.1 too), so are not yet in a package with build date Sept. 17th obviously. IOW, the fixes are not in 13.2 RC1 yet, but they should be in 13.2 final then. Please reopen if not. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=902712 --- Comment #2 from Johan Dot <jonte1@gmail.com> --- Ok. I 'm satisfied with the answer. About dates and versions I hope that final 13.2 will include the newer version but can understand if it not does (=low prio). I will ring the bell again then. Dont worry for me, I will find a way, I allready installed digikam-4.2.0-2.1.2.x86_64.rpm from factory that I saved a while ago in connection the problem in 13.1. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=902712 --- Comment #3 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Johan Dot from comment #2)
About dates and versions I hope that final 13.2 will include the newer version but can understand if it not does (=low prio).
You mean 4.4.0? As that is in Factory since 10 days already, I think it won't be added to the 13.2 release. Otherwise it would be in the 13.2 repo on OBS already I suppose. But you can always get the latest one from the KDE:Extra repo of course. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=902712 --- Comment #4 from Wolfgang Bauer <wbauer@tmo.at> --- PS: I just noticed that KDE:Extra (with digikam 4.4.0) is even available for 13.2 already. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=902712 --- Comment #5 from Johan Dot <jonte1@gmail.com> --- I sugget that the tread/bug is closed. The owner of the bug at bugzilla has delivered. Both in 13.1 and later in 13.2 I cant other then say thank you, regards -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com