F-Spot refused to close, force quit used

[Red Baron]

Binary package hint: f-spot

F-Spot would not quit voluntarily.
Force quit was needed.

I loaded a photo collection (~800), viewed a few in full screen slide show mode, returned the the regular view, scrolled through the photos, and then tried to quit. F-Spot then hung. I then killed it. It only misbehaved by refusing to quit.

user@host:~$ lsb_release -rd
Description: Ubuntu hardy (development branch)
Release: 8.04
user@host:~$ apt-cache policy f-spot
f-spot:
  Installed: 0.4.2-1ubuntu1
  Candidate: 0.4.2-1ubuntu1
  Version table:
 *** 0.4.2-1ubuntu1 0
        500 http://us.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
Date: Thu Apr 3 23:38:28 2008
Disassembly: 0xb6b6b478:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/f-spot/f-spot.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: nvidia
Package: f-spot 0.4.2-1ubuntu1
PackageArchitecture: i386
ProcCmdline: f-spot /usr/lib/f-spot/f-spot.exe
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: f-spot
Stacktrace: #0 0xb6b6b478 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: f-spot.exe crashed with SIGSEGV
Uname: Linux 2.6.24-14-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Pedro Villavicencio (pedro)]

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

[Claudiu Vlad (claudiu-vlad)]

i can confirm this behaviour too. there is no output in stderr so i can't tell why f-spot hangs on close

[Claudiu Vlad (claudiu-vlad)]

I would be more than happy to submit any debugging logs for this particular bug, as it is extremely annoying. I upgraded to hardy with no problems, and i found out that f-spot can't do a clean exit EVERY TIME. I would like to know how can I submit any useful logs , as the bug is reproducible here any time. So pls suggest the commands for debugging.

[Claudiu Vlad (claudiu-vlad)]

[16:07][claudiu:/>~]$ f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
Starting new FSpot server
Reloading
item changed
cleanup context

(f-spot:5755): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference.
Killed

[Joel Montes de Oca (joelmontes01)]

Here is a video of the bug...

[Saeid Zebardast (saeidzebardast)]

Confirmed.
Ubuntu: 8.04
Package: f-spot 0.4.2-1ubuntu3

[Pedro Villavicencio (pedro)]

can you run f-spot as: f-spot --debug &> f-spot-debug.txt and attach that file to the report? which version of f-spot are you using? are you running f-spot on an AMD64 system?

[Joel Montes de Oca (joelmontes01)]

Ubuntu 4.08
Fspot 0.4.3.1

[Joel Montes de Oca (joelmontes01)]

Can the status of this bug report be changed to confirmed?

[Claudiu Vlad (claudiu-vlad)]

This is the result of
 f-spot --debug &> f-spot-debug.txt

[Claudiu Vlad (claudiu-vlad)]

This is the result of
 f-spot --debug &> f-spot-debug.txt

[Saeid Zebardast (saeidzebardast)]

debug result:
f-spot 0.4.3.1-0ubuntu1 0

[Rob Frohne (frohro)]

Here is the result from the debug command for f-spot. I just started it, and then clicked the close button. It responded with a dialog box claiming f-spot was not responding and suggesting "Force Quit." I have tried using f-spot on another user who doesn't have any photos, on the same machine and had no problem quitting. I tried it on another Hardy install, and it worked okay with a user with some photos, but not 2500 as this user has. Unfortunately the ones with the large libraries are the ones that use f-spot a lot. The problem is that changes cannot be saved the way it is, because changes are lost with Force Quit.

frohba@frohba-600m:~$ f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
Starting new FSpot server
Reloading
item changed
Killed
frohba@frohba-600m:~$

[Rob Frohne (frohro)]

I backed up the .gnome2/f-spot/ directory and then moved it, and started f-spot, and then closed the import window without importing anything, and then closed f-spot. It required "Force Quit" again. This seemed a little surprising to me, especially when another user could close f-spot just fine.

Rob

[Rob Frohne (frohro)]

I compiled f-spot from source version 0.4.4, and it has the same problem.

Rob

[Pedro Villavicencio (pedro)]

May someone experiencing the issue send this upstream? for forwarding instructions please have a look to https://wiki.ubuntu.com/Bugs/Upstream/GNOME ; thanks.

[Rob Frohne (frohro)]

I compiled from the SVN trunk and the bug still exists for me. I forwarded the bug upstream as well.
<http://bugzilla.gnome.org/show_bug.cgi?id=537057>

Rob

[Rob Frohne (frohro)]

I did run f-spot --debug from the terminal, and it said nothing about the problem. The offending computer is at home and I'm at the office, but I can supply the output from there.

Rob

[Rob Frohne (frohro)]

Here is the result I promised:

Rob

frohba@frohba-600m:~$ f-spot --debug
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 20:23:22.185] Initializing DBus
[Debug 20:23:22.473] DBusInitialization took 0.266062s
[Info 20:23:22.474] Initializing Mono.Addins
[Debug 20:23:23.287] Mono.Addins Initialization took 0.813547s
[Info 20:23:23.299] Starting new FSpot server
[Debug 20:23:24.368] Db Initialization took 0.807601s
[Debug 20:23:24.957] Query: SELECT photos.id, photos.time, photos.uri, photos.description, photos.roll_id, photos.default_version_id, photos.rating FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY photos.time
[Debug 20:23:26.986] Query took 2.028789s
[Debug 20:23:27.031] Query: SELECT photos.id, photos.time, photos.uri, photos.description, photos.roll_id, photos.default_version_id, photos.rating FROM photos WHERE photos.id NOT IN (SELECT photo_id FROM photo_tags WHERE tag_id = 2) ORDER BY photos.time
[Debug 20:23:28.181] Query took 1.149079s
[Info 20:23:30.073] Starting BeagleService
[Debug 20:23:30.075] BeagleService startup took 2E-05s
Killed
frohba@frohba-600m:~$

[Pedro Villavicencio (pedro)]

Questions from upstream:

"- what's your architecture ? x86 ? x86-64 ?
 - if your processor is 64bits, are you running a 32 or 64 bit distro ?
 - do you have a multi-core cpu ?
 - does it happens with the LiveCD, or with the default hardy install ? or did
you installed/upgraded stuffs ?
 - can you run f-spot --gdb and paste the result of the "bt full" command ?
"

May someone ask them? here or in the upstream report, thanks in advance.

[Saeid Zebardast (saeidzebardast)]

result of the "bt full" (f-spot --gdb)

[Claudiu Vlad (claudiu-vlad)]

I am using Harfy Heron 32 bit, upgraded from Gutsy. I didn't try the LiveCD,
I have a Pentium IV 3000mhz with HT enabled.
"processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Pentium(R) 4 CPU 3.00GHz
stepping : 10
cpu MHz : 2400.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm
bogomips : 6000.64
clflush size : 64
"

[Claudiu Vlad (claudiu-vlad)]

The bug seems related to some configuration files. I moved all the * and .* files away in a "tmp" folder from my home directory and f-spot ran perfectly. As I was moving the configuration settings back one by one, f-spot went back to the old behaviour - not responding when required to close. I suspect it is something related to .evolution or .mozilla .

[Claudiu Vlad (claudiu-vlad)]

This bug disappeared in Jaunty beta. F-spot works ok now.

[Felipe Figueiredo (philsf)]

I think I found out how to work around this issue. Since an empty test account didn't show the behaviour, I decided moving my dirs and files out of ~ until I got f-spot to work. After a while of some trial and error, I nailed it down to ~/.gnupg.

After that, I kept trying until I pinpointed the problem (at least for me) to gpg.conf. Since it was a nearly empty file (only three options, including default key and keyserver), I finally got to the offending option:

use-agent

Commenting this option was sufficient to make F-Spot close as expected.

Could others affected see if this helps you as well?

[Claudiu Vlad (claudiu-vlad)]

Excellent news, if they confirm this.

Cheers,

On Tue, Apr 14, 2009 at 12:14 PM, Felipe Figueiredo <email address hidden>wrote:

> I think I found out how to work around this issue. Since an empty test
> account didn't show the behaviour, I decided moving my dirs and files
> out of ~ until I got f-spot to work. After a while of some trial and
> error, I nailed it down to ~/.gnupg.
>
> After that, I kept trying until I pinpointed the problem (at least for
> me) to gpg.conf. Since it was a nearly empty file (only three options,
> including default key and keyserver), I finally got to the offending
> option:
>
> use-agent
>
> Commenting this option was sufficient to make F-Spot close as expected.
>
> Could others affected see if this helps you as well?
>
> --
> F-Spot refused to close, force quit used
> https://bugs.launchpad.net/bugs/211692
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Ryan Cresawn (jrcresawn)]

On Wed, Apr 15, 2009 at 9:16 AM, Claudiu Vlad <email address hidden>wrote:

> Excellent news, if they confirm this.

I have no ability to test at this time.

Sorry,
Ryan

[Pedro Villavicencio (pedro)]

setting back to confirmed seems to be an Ubuntu only issue.

[Claudiu Vlad (claudiu-vlad)]

In case someone missed it, I'll put it here again: This bug dissapeared
after upgrading to Jaunty 904.

Have a nice weekend, everyone!

On Thu, May 14, 2009 at 5:19 PM, Pedro Villavicencio <email address hidden>wrote:

> setting back to confirmed seems to be an Ubuntu only issue.
>
> ** Changed in: f-spot (Ubuntu)
> Status: Triaged => Confirmed
>
> --
> F-Spot refused to close, force quit used
> https://bugs.launchpad.net/bugs/211692
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Pedro Villavicencio (pedro)]

good, closing the report then, thanks you.