apps using the mono bindings fail to load
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Application Indicators |
Fix Released
|
High
|
Unassigned | ||
indicator-application (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
tomboy (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: indicator-
Tomboy built against libappindicator
Unhandled Exception: System.
at (wrapper managed-to-native) AppIndicator.
at AppIndicator.
at GtkSharp.
at AppIndicator.
--- End of inner exception stack trace ---
at Tomboy.
at Tomboy.
at Tomboy.Tomboy.Main (System.String[] args) [0x00000]
This is caused by the use of appindicator-0.0 instead of appindicator-0.1 at some places and by the move of the library files to a different directory in the source code, making them unfindable for the GAPI parser. Two branches are associated with this bug that fix those two issues.
Related branches
- David Barth: Approve
-
Diff: 18 lines (+4/-4)1 file modifiedbindings/mono/app-indicator.sources.xml (+4/-4)
- Ken VanDine: Pending requested
-
Diff: 229 lines (+78/-14)5 files modifiedChangeLog (+24/-0)
configure (+10/-10)
configure.ac (+2/-2)
debian/changelog (+7/-0)
src/application-service-appstore.c (+35/-2)
Changed in indicator-application: | |
importance: | Undecided → High |
description: | updated |
Changed in indicator-application: | |
status: | Triaged → Fix Committed |
Changed in tomboy (Ubuntu): | |
status: | New → Invalid |
Changed in indicator-application: | |
milestone: | none → 0.2.1 |
Changed in indicator-application: | |
status: | Fix Committed → Fix Released |
This is probably related to the fact that it seems that the libappindicator 0.1-cil package seems to be putting everything in directories called 'appindicator- sharp-0. 0' whereas the Makefiles and the .pc file points to 'appindicator- sharp-0. 1'.
The packaging and the source code seem to have diverged a bit when the packaging was fixed in order to comply to the Debian CLI Policy. I'm not sure what would be the best way to fix it -- presumably something in the packaging needs to be changed -- but the best people to ask this would probably be Jo Shields or Chow Loong Jin.