Doesn't start: libgexiv2.so.0 => not found

[Christophe]

Hey,

Shotwell doesn't start since the latest libgexiv2 update.

dpkg --list | grep -E "(libgexiv2-0|shotwell)"
ii libgexiv2-0 0.4.1-0ubuntu1
ii shotwell 0.12.1-0ubuntu1

ldd `which shotwell` | grep libgexiv2
 libgexiv2.so.0 => not found

ls -l /usr/lib/libgexiv2.so*
lrwxrwxrwx 1 root root 18 Apr 2 08:02 /usr/lib/libgexiv2.so.1 -> libgexiv2.so.1.0.0
-rw-r--r-- 1 root root 126200 Apr 2 08:02 /usr/lib/libgexiv2.so.1.0.0

[Launchpad Janitor (janitor)]

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

[Sebastien Bacher (seb128)]

Thank you for your bug report, seems like the gexiv2 soname changed and Robert didn't rename the binary

[Launchpad Janitor (janitor)]

This bug was fixed in the package gexiv2 - 0.4.1-1build1

---------------
gexiv2 (0.4.1-1build1) precise; urgency=low

  * Resynchronize on Debian, including correct binary naming for the
    new soname (lp: #971468)
  * debian/control:
    - have libgexiv2-1 Replaces libgexiv2-0 to avoid upgrade issues

gexiv2 (0.4.1-1) experimental; urgency=low

  * Team upload.
  * New upstream release.
  * debian/patches/soname.patch:
    - Removed, already implemented upstream.
  * debian/compat:
    - Bump compatibility level to 9.
  * debian/copyright:
    - Convert to DEP5 format.
 -- Sebastien Bacher <email address hidden> Mon, 02 Apr 2012 15:19:29 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package shotwell - 0.12.1-0ubuntu2

---------------
shotwell (0.12.1-0ubuntu2) precise; urgency=low

  * debian/control:
    - build with current gexiv2 to pick the current soname (lp: #971468)
 -- Sebastien Bacher <email address hidden> Mon, 02 Apr 2012 15:35:03 +0200

[macstevejb (macstevejb)]

Bug may be fixed but still not in repos and shotwell therefore unusable. Hope the update appears soon :)

[Jim Nelson (yorba-jim)]

You should be able to upgrade Shotwell again and see the fix. Or, uninstall Shotwell and reinstall again.