Crash on opening with corrupted picture
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glib2.0 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
# Context
Due to some problem I don't understand now, Shotwell crashes while updating pictures metadata, resulting in empty or corrupted files.
[But that's not the point of this report. I may open a new ticket when I understand the root cause.]
# What happens
it's that Shotwell now refuses to start, and report following error:
joel@
L 2835 2015-12-25 20:14:36 [CRT] PhotoMonitor.
**
GLib-
Abandon (core dumped)
Please find the corrupted file attached (even if it's 0B long).
# What I would expect to happen
Shotwell should detect that the file is corrupted, and ignore it / raise an alert / tag it as missing or corrupted.
# Versions description
Shotwell package version: 0.22.0-0ubuntu5
Xubuntu version : 15.10
affects: | shotwell (Ubuntu) → glib2.0 (Ubuntu) |
Complementary information: if I remove the identified 0B-long picture, shotwell goes further in starting but still crashes, only with the already-quoted Glib-IO error. This was likely due to another picture earlierly-corrupted by shotwell, that is attached here.