Mono_path issue: crash when starting f-spot

[Psykotik]

Binary package hint: f-spot

I just upgraded to Ubuntu Hardy 8.04. And I have been able to run once f-spot; but since then, not anymore.

Here is the console log:

----
$ f-spot

** (/usr/lib/f-spot/f-spot.exe:14735): WARNING **: The following assembly referenced from /usr/lib/f-spot/f-spot.exe could not be loaded:
     Assembly: NDesk.DBus (assemblyref_index=8)
     Version: 1.0.0.0
     Public Key: f6716e4f9b2ed099
The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/f-spot).

** (/usr/lib/f-spot/f-spot.exe:14735): WARNING **: Could not load file or assembly 'NDesk.DBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f6716e4f9b2ed099' or one of its dependencies.

Unhandled Exception: System.TypeLoadException: A type load exception has occurred.
----

[Psykotik (linux-ikiru)]

This issue seems to be identical to this one: https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/133337

I don't understand what's about, but I also tried to launch the command "dbus-launch f-spot", but no change at all.

[Psykotik (linux-ikiru)]

Found a workaround.

I uninstalled libmono2.0-cil, which uninstalled also libndesk-dbus-glib1.0-cil and libndesk-dbus1.0-cil. Note the latter gave this apt message (from file /var/log/apt/term.log):

Suppression de libndesk-dbus1.0-cil ...

Removing libndesk-dbus1.0-cil from Mono

W: removing assembly: NDesk.DBus, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f6716e4f9b2ed099 failed!

I installed again these files (including f-spot and tomboy, which have also been uninstalled when uninstalling libmono2.0-cil), and everything work flawlessly.

Seems to be related to the upgrade, and to the libndesk-dbus1.0-cil library.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

[Psykotik (linux-ikiru)]

As I wrote, re-installing some libraries did the trick.

[Pedro Villavicencio (pedro)]

closing the bug then, thanks.