F-Spot crashes immediately after start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
f-spot (Ubuntu) |
Incomplete
|
Medium
|
Unassigned |
Bug Description
Binary package hint: f-spot
This bug is similar to other "F-Spot Crash" event logged already. However, I tried running F-Spot from console, and found errors I have been receiving are different than given in support forums. Complete removal and re-install did not help either.
Here is message after issuing command f-spot from console
-------
(/usr/lib/
[Info 15:59:09.892] Initializing DBus
[Info 15:59:10.034] Initializing Mono.Addins
[Info 15:59:10.239] Starting new FSpot server (f-spot 0.6.1.5)
** (/usr/lib/
** (/usr/lib/
** (/usr/lib/
** (/usr/lib/
** (/usr/lib/
[Info 15:59:11.157] Starting BeagleService
[Info 15:59:11.187] Hack for gnome-settings-
(/usr/lib/
The program '/usr/lib/
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 2904 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
-------
Here is message after issuing command gksudo f-spot from console:
-------
** No session dbus found. Starting one **
[Info 16:00:25.323] Initializing DBus
[Info 16:00:25.499] Initializing Mono.Addins
[Info 16:00:25.703] Starting new FSpot server (f-spot 0.6.1.5)
** (/usr/lib/
** (/usr/lib/
** (/usr/lib/
** (/usr/lib/
** (/usr/lib/
[Info 16:00:26.736] Starting BeagleService
[Info 16:00:26.756] Hack for gnome-settings-
(/usr/lib/
The program '/usr/lib/
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 2942 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
-------
ProblemType: Bug
Architecture: i386
Date: Mon Mar 1 15:56:42 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: f-spot 0.6.1.5-0ubuntu1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: f-spot
Uname: Linux 2.6.31-19-generic i686
Thank you for your bug report, what gtk theme do you use?