Shotwell cannot resolve gexiv2_initialize symbol

Bug #971828 reported by Bruno Girin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shotwell (Ubuntu)
New
Undecided
Unassigned

Bug Description

Following the upgrade to Shotwell 0.12.1 last night on Precise amd64, Shotwell doesn't start anymore. When starting from the command line it complains about a missing gexiv2 symbol:

$ shotwell
shotwell: symbol lookup error: shotwell: undefined symbol: gexiv2_initialize

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: shotwell 0.12.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic x86_64
ApportVersion: 2.0-0ubuntu2
Architecture: amd64
Date: Mon Apr 2 20:21:58 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: shotwell
UpgradeStatus: Upgraded to precise on 2012-02-11 (51 days ago)

Revision history for this message
Bruno Girin (brunogirin) wrote :
Revision history for this message
Bruno Girin (brunogirin) wrote :

I realised after filing this bug that I probably had a locally compiled version of gexiv2 so I removed the locally compiled library and tried to run Shotwell again, at which point I got this error:

$ shotwell
shotwell: error while loading shared libraries: libgexiv2.so.0: cannot open shared object file: No such file or directory

And indeed, if I check the libraries installed on the machine, here is what I get:

$ ls /usr/lib | grep gexiv
libgexiv2.a
libgexiv2.so
libgexiv2.so.1
libgexiv2.so.1.0.0

Revision history for this message
Lucas Beeler (lucas-yorba) wrote : Re: [Bug 971828] Re: Shotwell cannot resolve gexiv2_initialize symbol

Bruno,

Since you're a pro user, I'd recommend checking out the latest gexiv2
source from git://git.yorba.org/gexiv2, building from source, and
doing a sudo make install. I noticed that on my dev machine I had
several versions of gexiv2 in /usr/lib and /usr/local/lib. But
compiling and installing from source ensures that the latest version
of the so will be placed in /usr/local/lib, which, given the
LD_LIBRARY_PATH on Ubuntu, should be searched first.

Lucas

On Mon, Apr 2, 2012 at 12:30 PM, Bruno Girin <email address hidden> wrote:
> I realised after filing this bug that I probably had a locally compiled
> version of gexiv2 so I removed the locally compiled library and tried to
> run Shotwell again, at which point I got this error:
>
> $ shotwell
> shotwell: error while loading shared libraries: libgexiv2.so.0: cannot open shared object file: No such file or directory
>
> And indeed, if I check the libraries installed on the machine, here is
> what I get:
>
> $ ls /usr/lib | grep gexiv
> libgexiv2.a
> libgexiv2.so
> libgexiv2.so.1
> libgexiv2.so.1.0.0
>
> --
> You received this bug notification because you are subscribed to
> shotwell in Ubuntu.
> https://bugs.launchpad.net/bugs/971828
>
> Title:
>  Shotwell cannot resolve gexiv2_initialize symbol
>
> Status in “shotwell” package in Ubuntu:
>  New
>
> Bug description:
>  Following the upgrade to Shotwell 0.12.1 last night on Precise amd64,
>  Shotwell doesn't start anymore. When starting from the command line it
>  complains about a missing gexiv2 symbol:
>
>  $ shotwell
>  shotwell: symbol lookup error: shotwell: undefined symbol: gexiv2_initialize
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 12.04
>  Package: shotwell 0.12.1-0ubuntu1
>  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
>  Uname: Linux 3.2.0-21-generic x86_64
>  ApportVersion: 2.0-0ubuntu2
>  Architecture: amd64
>  Date: Mon Apr  2 20:21:58 2012
>  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
>  ProcEnviron:
>   LANGUAGE=en_GB:en
>   TERM=xterm
>   LANG=en_GB.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: shotwell
>  UpgradeStatus: Upgraded to precise on 2012-02-11 (51 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/971828/+subscriptions

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.