bamfdaemon links to libunity_webapps.so but the library is named libunity-webapps.so

Bug #1053688 reported by Thomi Richards on 2012-09-20
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
BAMF
Critical
Unassigned
WebApps: libunity-webapps
Undecided
Unassigned
bamf (Ubuntu)
Undecided
Unassigned

Bug Description

In Quantal, with the staging PPA enabled, bamfdaemon refuses to start:

/usr/lib/bamf/bamfdaemon: error while loading shared libraries: libunity_webapps.so.0: cannot open shared object file: No such file or directory

The libunity-webapps0 package installs this library as:

/usr/lib/i386-linux-gnu/libunity-webapps.so.0

Thomi Richards (thomir) wrote :

This can be fixed by symlinking libunity-webapps.so.0 to libunity_webapps.so.0

Tim Penhey (thumper) on 2012-09-20
Changed in bamf:
status: Confirmed → Triaged
importance: Undecided → Critical
Robert Carr (robertcarr) wrote :

bamfdaemon just needs a rebuild, -lunity-webapps is in the pkgconfig file now (and has been for a while). Shouldn't have been renamed so late.

Thomi Richards (thomir) on 2012-09-20
summary: - bamfdaemon links to libunity-webapps.so but the library is named
- libunity_webapps.so
+ bamfdaemon links to libunity_webapps.so but the library is named
+ libunity-webapps.so
Will Cooke (willcooke) on 2012-09-28
Changed in libunity-webapps:
status: New → Invalid
Changed in bamf (Ubuntu):
status: New → Confirmed
Changed in bamf:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers