[hardy] X crashes when I start f-spot with "dbus-launch f-spot"

Bug #191100 reported by Alexander Rødseth
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wacom-tools (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xorg

Steps to reproduce:
- Type this at the commandline:
dbus-launcher f-spot

X just disappears here, every time I try. First I tried just starting "f-spot", but then I was told to use "dbus-launcher f-spot" instead, by the commandline output from "f-spot".

Revision history for this message
Jorge Castro (jorge) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Hardy Heron. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at [WWW] http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

I cannot reproduce this on Hardy Alpha4.

Changed in xorg:
status: New → Incomplete
Revision history for this message
Alexander Rødseth (alexanro) wrote :

I'm already using the very latest version of Hardy. Are there any commands I can run to further investigate this?

Revision history for this message
Alexander Rødseth (alexanro) wrote :

When I start f-spot from the commandline, here is the output I get:

~% 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]

---

Then a "fatal error" window pops up, with this text:

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:

NDesk.DBus.Proxies (0.0.0.0)
gdk-sharp (2.10.0.0)
gnome-vfs-sharp (2.16.0.0)
Mono.Addins (0.3.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.3.0.0)
glib-sharp (2.10.0.0)
gnome-sharp (2.16.0.0)
f-spot (0.4.1.0)
Mono.GetOptions (2.0.0.0)
mscorlib (2.0.0.0)

Platform Information: Linux 2.6.24-7-generic i686 unknown GNU/Linux

Distribution Information:

[/etc/debian_version]
lenny/sid

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

---

Here is the suggestion of the "fatal error"-window: Make sure dbus is configured properly or start a new session for f-spot using "dbus-launch f-spot"

When I try "dbus-launch f-spot", X just crashes and disappears.

Revision history for this message
Alexander Rødseth (alexanro) wrote :

Do I have to demonstrate this bug on a live CD for this to be a valid issue?

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Please attach /var/log/Xorg.0.log.old which should contain a backtrace from the crash.

Revision history for this message
Alexander Rødseth (alexanro) wrote :

I suspect that my Xorg.0.log.old does not contain the backtrace, but I'll attach it anways.
If I find the time, I'll try running the command again and attach the backtrace. I would rather not restart X right now.

Thanks for the response.

Revision history for this message
Alexander Rødseth (alexanro) wrote :

I tried starting F-spot again (with "dbus-launch f-spot") First time, it started up seemingly fine. I selected File->Import and added a directory with about 400 pictures.
During the import, I noticed that f-spot would copy all the images to ~/Photos. I didn't want this, so I clicked "Cancel" and tried pressing ESC, but got no response.
F-spot, X and all my other applications started going slower and slower, and I think I got an "OutOfMemory" error on the console before everything went to a crawl.
After several minutes, I barely managed to press Ctrl+Alt+F1, log in and kill f-spot.

But, I still had faith in being able to reproduce the crash, so I tried again. I started f-spot (still with "dbus-launch f-spot"). This time, I had better luck and X crashed after a short while.
I even managed to get hold of the Xorg.0.log.old, which I am attaching right now.

Looking at the log, it seems like the wacom-driver is to blame, but no other application makes X crash but f-spot, and my wacom tablet works perfectly fine in other applications, so I'm having a hard time believing that. However, it might be combination of f-spot and the wacom-drivers. I'm using the lastest version of the linuxwacom drivers, which I need to in order to get my Bamboo1 tablet to work: http://linuxwacom.sourceforge.net/

Hope it helps.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

There's a new version of the driver uploaded recently, does it still crash?

Revision history for this message
Alexander Rødseth (alexanro) wrote :

F-spot seems to work fine now, but I've also switched to Intrepid.

Revision history for this message
Pablo Castellano (pablocastellano) wrote :

Closing this bug. It seems to be fixed (previous comments).

Changed in wacom-tools:
status: Incomplete → Fix Released
Revision history for this message
Marko Martinović (marko-martinovic-deactivatedaccount) wrote :

I am having this bug in Lucid with wacom Bamboo One. F-Spot, Shotwell i Rythmbox are crashing X to login when started, and light on my Wacom Bamboo One blinks when that happens and tablet stops working until restart. Please reopen, thanks.

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.