Occasionally, a crash occurs if certain corrupted video files are imported from a camera.
Submitted by cli..@..ba.org
Assigned to Lucas Beeler
Link to original bug (#718289)
Description
---- Reported by clinton@yorba.org 2011-09-23 12:37:00 -0700 ----
Original Redmine bug id: 4172
Original URL: http://redmine.yorba.org/issues/4172
Searchable id: yorba-bug-4172
Original author: Clinton Rogers
Original description:
Steps to reproduce:
With certain low-end point-and-shoots, record at least one video successfully.
With the same device, begin recording a second video and deliberately disconnect power from the device while recording.
With the same device, connect it to Shotwell, attempt importing the files together and observe the results.
Notice that, occasionally Shotwell aborts and the following error appears on the console:
ERROR:meh/Dialogs.c:2810:import_ui_get_media_specific_string: code should not be reached
The problem has been seen with both a Concord 3045 and a Jazz HDV141. Both of them shoot motion-JPEG .avi files.
Related issues:
- related to shotwell - 4098: Import hangs (Invalid)
- duplicated by shotwell - 4234: Bug: shotwell import digital camera "Canon" (Duplicate)
- duplicated by shotwell - 4211: Shotwell 0.11.2 crashes after import (Duplicate)
- duplicated by shotwell - 4561: USB import from SDcard causes Shotwell to crash (Duplicate)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:38:00 -0700 ----
History
Comment 1
Updated by Jim Nelson about 2 years ago
- Category set to 4
- Priority changed from High to Urgent
This sounds like we have problems decoding partial or corrupted video files. I'm marking as Urgent because it's a crasher. If we evaluate and see it's a real corner case, we can reduce the priority.
Comment 2
Updated by Jim Nelson about 2 years ago
- Description updated (diff)
This has been reported downstream: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/860657
Comment 3
Updated by Clinton Rogers about 2 years ago
What appears to be a related crash when someone is attempting to import images can happen as well, and at least two users have encountered it in the wild; please see https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/862347 as well as the link Jim posted below.
This user has been asked for a sample image file in hopes of getting the assert_not_reached() to happen reliably.
Comment 4
Updated by Paulo Matos about 2 years ago
I reproduced this and reported as duplicate (sorry) in #4211 (closed) using a Nikon D5000. It has some videos but I haven't disconnected the device while recording so unsure if there's anything corrupt in there.
Actually the whole import process seems to be going pretty well and the crash happens at the end of the import process.
Comment 5
Updated by Lucas Beeler about 2 years ago
- Assignee set to Lucas Beeler
- Resolution set to fixed
Fixed in 95878514
Comment 6
Updated by Lucas Beeler about 2 years ago
- Status changed from Open to 5
Comment 7
Updated by Lucas Beeler about 2 years ago
- Target version changed from 0.12 to 0.11.3
Comment 8
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:56 UTC ---
This bug was previously known as bug 4172 at http://redmine.yorba.org/show_bug.cgi?id=4172
Unknown Component Using default product and component set in Parameters Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.11.3
Resolution: RESOLVED FIXED