shotwell SIGABRT, database_table_prepare_update_by_id assertion assertion failed: (res == Sqlite.OK)

[Vague Entertainment]

Happened when I was just searching through my pictures

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: shotwell 0.14.1-3ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic x86_64
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Jul 16 21:21:36 2013
ExecutablePath: /usr/bin/shotwell
InstallationDate: Installed on 2013-07-05 (12 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: shotwell
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: shotwell
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: shotwell crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to saucy on 2013-07-10 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastien Bacher (seb128)]

Thank you for your bug report.

That seems the most reported shotwell error on errors.ubuntu.com for Ubuntu 13.10:
https://errors.ubuntu.com/problem/bfb9523f2ef0663cb1b4475b41709dd3418a389b

the assert message seems to be "database_table_prepare_update_by_id assertion failed: (res == Sqlite.OK)"

[Jim Nelson (yorba-jim)]

Sebastien, I don't have access to that report on errors.ubuntu.com. Can you point me to other reports of it on Launchpad? We had one come in upstream but couldn't reproduce it or discover the problem behind it.

[Jim Nelson (yorba-jim)]

I did find bug #856970. Are there others?

The upstream ticket I was referring to is http://redmine.yorba.org/issues/7659 I found a related ticket (with a different stack trace) at http://redmine.yorba.org/issues/5071 (which is referred to in bug #856970).

[Sebastien Bacher (seb128)]

@Jim: the duplicates are listed on the right of the launchpad page, e.g bug #1235359 is the most recent one.

errors.ubuntu.com is nice because it gives an idea of what issue is frequent or not, it doesn't include user descriptions though so it doesn't provide more informations than the backtrace and the other details you have on this launchpad bug report...

[Jim Nelson (yorba-jim)]

I was able to reproduce this. The steps I took were:

* Add a lot of videos to my Shotwell library
* Delete all the Shotwell thumbnails (~/.cache/shotwell/thumbs)
* In the photo.db, I did "UPDATE VideoTable SET is_interpretable=0"

(Note: We never recommend users modify their Shotwell database file directly. I only did this to repro the problem.)

When I ran Shotwell, I got the error seen above.

We'll be releasing a Shotwell 0.15.1 soon. I think this fix will be a part of it.

[Sebastien Bacher (seb128)]

Thanks Jim!

[Launchpad Janitor (janitor)]

This bug was fixed in the package shotwell - 0.15.1-0ubuntu1

---------------
shotwell (0.15.1-0ubuntu1) trusty; urgency=low

  * New upstream version:
    - should fix assertions in the database code (lp: #1202049)
 -- Sebastien Bacher <email address hidden> Wed, 20 Nov 2013 11:10:21 +0100