crash when browsing over the pictures

[Anmar Oueja]

Binary package hint: f-spot

I was sifting through pictures (editing mode) and when I hit a special picture, it crash. Here are the details:

An unhandled exception was thrown: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

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

Assembly Version Information:

System.Configuration (2.0.0.0)
FSpot.Widgets (0.0.0.0)
System.Xml (2.0.0.0)
NDesk.DBus.Proxies (0.0.0.0)
gconf-sharp (2.24.0.0)
System.Data (2.0.0.0)
Mono.Data.SqliteClient (2.0.0.0)
FSpot.Query (0.0.0.0)
gdk-sharp (2.12.0.0)
gnome-vfs-sharp (2.24.0.0)
NDesk.DBus.GLib (1.0.0.0)
NDesk.DBus (1.0.0.0)
Cms (0.0.0.0)
Mono.Posix (2.0.0.0)
System (2.0.0.0)
FSpot.Utils (0.0.0.0)
FSpot.Core (0.0.0.0)
atk-sharp (2.12.0.0)
gtk-sharp (2.12.0.0)
Mono.Addins (0.4.0.0)
Mono.Addins.Setup (0.4.0.0)
glib-sharp (2.12.0.0)
gnome-sharp (2.24.0.0)
f-spot (0.5.0.3)
mscorlib (2.0.0.0)

Platform Information: Linux 2.6.28-13-generic i686 unknown GNU/Linux

Distribution Information:

[/etc/debian_version]
5.0

[/etc/lsb-release]
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.04
DISTRIB_CODENAME=jaunty
DISTRIB_DESCRIPTION="Ubuntu 9.04"

I can send much more data if you need it.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: f-spot 0.5.0.3-1ubuntu6
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: f-spot
Uname: Linux 2.6.28-13-generic i686

[Anmar Oueja (anmar)]

The file is in the grid view, but when I drag and drop it, it says: Error stating file '/home/anmar/img_1510.jpg': No such file or directory

Hmm.. but the file is in the grid however, nothing shows up in the edit view. I see why the crash is happening but if you don't have the file on the Disk due to somebody moving it somehwere you shouldn't crash and you should simply mark the image with an X or move it to a different category of images that can't be located on the drive.

[Pedro Villavicencio (pedro)]

that seems to be another issue, could you please run f-spot as: f-spot --debug &> f-spot.txt reproduce the issue and attach that resulting file to the report? thanks.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don\'t hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.