dbus error: F-Spot not launching on a fresh install of Kubuntu Gutsy

Bug #139050 reported by martalli
This bug report is a duplicate of:  Bug #89832: Missing dependency: dbus-x11. Edit Remove
4
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Incomplete
Medium
Maia Everett

Bug Description

Binary package hint: f-spot

I just did a fresh install of Kubuntu gutsy, and then did a full upgrade through adept. Since I have been managing my photos on this machine, I did an install of f-spot. Now, upon opening f-spot, I get an error re: dbus.

F-Spot cannot find the Dbus session bus. Make sure dbus is configured properly or start a new session for f-spot "dbus-launch f-spot"

and then the following error details are included:

An unhandled exception was thrown: F-Spot cannot find the Dbus session bus. Make sure dbus is configured properly or start a new session for f-spot using "dbus-launch f-spot"

  at FSpot.Driver.Main (System.String[] args) [0x00000]
.NET Version: 2.0.50727.42

Assembly Version Information:

gdk-sharp (2.10.0.0)
gnome-vfs-sharp (2.16.0.0)
Mono.Addins (0.2.0.0)
NDesk.DBus.GLib (1.0.0.0)
NDesk.DBus (1.0.0.0)
System (2.0.0.0)
Mono.Posix (2.0.0.0)
atk-sharp (2.10.0.0)
gtk-sharp (2.10.0.0)
Mono.Addins.Setup (0.2.0.0)
glib-sharp (2.10.0.0)
gnome-sharp (2.16.0.0)
f-spot (0.4.0.0)
Mono.GetOptions (2.0.0.0)
mscorlib (2.0.0.0)

Platform Information: Linux 2.6.22-11-generic i686 unknown GNU/Linux

Distribution Information:

[/etc/debian_version]
lenny/sid

[/etc/lsb-release]
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu gutsy (development branch)"

I tried running dbus-launch f-spot, but only got errors. I also tried reinstalling dbus and f-spot through adept, but that did not change anything (not that I really expected that to work, but hey).

Now, I previously had f-spot on this computer, so the original files are all still there in my home partition. Could this have caused the problem? I wouldn't have thought so...

Thanks, Bryan

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your comments. This does not appear to be a bug report as such. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. http://launchpad.net/support ; Looks like your dbus service is not running. not a f-spot problem.

Changed in f-spot:
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
e (0x0065) wrote :

This error occurs on my gentoo system with dbus running as a service and all other apps using dbus without reporting any problem...
...probably an f-spot problem.

erik@0x0065 ~ $ f-spot
System.ApplicationException: F-Spot cannot find the Dbus session bus. Make sure dbus is configured properly or start a new session for f-spot using "dbus-launch f-spot" ---> System.Exception: Unable to open the session message bus. ---> System.ArgumentNullException: Argument cannot be null.
Parameter name: address
  at NDesk.DBus.Bus.Open (System.String address) [0x00000]
  at NDesk.DBus.Bus.get_Session () [0x00000] --- End of inner exception stack trace ---

  at NDesk.DBus.Bus.get_Session () [0x00000]
  at NDesk.DBus.BusG.Init () [0x00000]
  at FSpot.Driver.Main (System.String[] args) [0x00000] --- End of inner exception stack trace ---

  at FSpot.Driver.Main (System.String[] args) [0x00000]

erik@0x0065 ~ $ su
Password:
0x0065 erik # /etc/init.d/dbus start
 * WARNING: dbus has already been started.
0x0065 erik # ps -A | grep dbus
 5227 ? 00:00:00 dbus-daemon
 5464 ? 00:00:00 dbus-launch
 5465 ? 00:00:00 dbus-daemon
0x0065 erik # exit
erik@0x0065 ~ $ f-spot
System.ApplicationException: F-Spot cannot find the Dbus session bus. Make sure dbus is configured properly or start a new session for f-spot using "dbus-launch f-spot" ---> System.Exception: Unable to open the session message bus. ---> System.ArgumentNullException: Argument cannot be null.
Parameter name: address
  at NDesk.DBus.Bus.Open (System.String address) [0x00000]
  at NDesk.DBus.Bus.get_Session () [0x00000] --- End of inner exception stack trace ---

  at NDesk.DBus.Bus.get_Session () [0x00000]
  at NDesk.DBus.BusG.Init () [0x00000]
  at FSpot.Driver.Main (System.String[] args) [0x00000] --- End of inner exception stack trace ---

  at FSpot.Driver.Main (System.String[] args) [0x00000]

erik@0x0065 ~ $ dbus-launch f-spot
Initializing Mono.Addins
Starting new FSpot server

...again, nothing else is complaining...

Changed in f-spot:
status: Invalid → Confirmed
Revision history for this message
e (0x0065) wrote :

   try {
    NDesk.DBus.BusG.Init();
   } catch (Exception e) {
    throw new ApplicationException ("F-Spot cannot find the Dbus session bus. Make sure dbus is configured properly or start a new session for f-spot using \"dbus-launch f-spot\"", e);
   }
   /*
    * FIXME we need to inialize gobject before making the dbus calls, we'll go
    * ahead and do it like this for now.
    */
   program = new Program (Defines.PACKAGE,
            Defines.VERSION,
            Modules.UI, args);

   Console.WriteLine ("Initializing Mono.Addins");
   AddinManager.Initialize (FSpot.Global.BaseDirectory);
   AddinManager.Registry.Update (null);
   SetupService setupService = new SetupService (AddinManager.Registry);
   setupService.Repositories.RegisterRepository (null, "http://addins.f-spot.org", false);

Revision history for this message
Maia Everett (linneris) wrote :

Does installing the dbus-x11 package solve the problem?

Changed in f-spot:
assignee: nobody → sikon
status: Confirmed → Incomplete
Revision history for this message
foxy123 (foxy) wrote :

I've got the same problem. Can launch F-Spot with 'dbus launch f-spot' but trying just 'f-spot' gives me the same error

Revision history for this message
Natan (nvivo) wrote :

I have the same problem using Kubuntu 8.04 amd64.

Installed Kubuntu yesterday, then installed "f-spot" package. It gives the exact same error when I launch.

Tried "sudo /etc/init.d/dbus start", it gives me:
 * system message bus already started; not starting.

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.