© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
We're mixing jaunty and karmic here; under karmic we now have mono 2.4 which seems to work fine without OABI_COMPAT (as reported by ogra who's running the vendor's kernel) and f-spot can be launched. Both the SIGILL and SEGV are gone.
Under jaunty, you confirmed that OABI_COMPAT fixes the SIGILL and allows you to move on to the SEGV. This seemed to be a known bug in mono < 2.4. We could probably provide PPA packages for mono if you care to demo f-spot and the like on a jaunty base, but we can't include mono 2.4 in jaunty. We could consider adding a non-intrusive patch to mono in jaunty.
Dave, I think you wanted to check whether OABI_COMPAT has a performance penalty; if it doesn't, could you please file a bug to request setting this config on armel kernel configs in karmic? Thanks!