GNOME Bugzilla – Bug 537057
F-Spot will Not Close, must Force Quit
Last modified: 2009-04-28 08:27:26 UTC
Please describe the problem: When you try to close f-spot, a dialog appears saying f-spot is not responding, and you can force quit or cancel. Force quitting claims that it will lose your data. I haven't checked to make sure, that always happens, but losing data is serious. Steps to reproduce: 1. Open f-spot. 2. Close f-spot 3. Actual results: hen you try to close f-spot, a dialog appears saying f-spot is not responding, and you can force quit or cancel. Force quitting claims that it will lose your data. I haven't checked to make sure, that always happens, but losing data is serious. Expected results: I expect f-spot to close without loss of data. Does this happen every time? Yes, kind of. It happens everytime on one account (with a lot of photos) and never in an account with none. I moved the database files in and the behavior is the same. (mv ~/.gnome2/fspot) ~ and run f-spot and it still won't quit. Other information: See "[Bug 211692] Re: F-Spot refused to close, force quit used" on Ubuntu.
f-spot version? from source or package? can you try running f-spot --debug from command line and post here some lines of what happens on console after you try to quit?
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:~$
I think this occurred after I killed f-spot. (f-spot:10597): 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
probably related to this: https://bugzilla.novell.com/show_bug.cgi?id=322163 Rob: you mean this bug, right ? https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/211692
Rob: - 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 ?
Hi Stephane, I am using a Dell 600m (x86, 32 bit Celeron) laptop. I did the --gdb, but there are no debugging symbols found. I'll see if I can get those set up, and get back with you with the results. Thanks! Rob
Ok, I give up. I can't figure out how to compile with debug symbols. What arguments do I give to configure or make to get debugging symbols installed? Thanks, Rob
it's a mono crash so you need the mono debug symbols, probably from the mono-dbg package - does it happens with the LiveCD, or with the default hardy install ? or did you installed/upgraded stuffs ?
This install was an upgrade from Gutsy. I'll try again on the debugging symbols. Rob
I installed mono-dbg package, but I still get no debugging symbols. I also installed monodevelop, and found a solution file in svn and tried to build F-spot, but it croaked on a makefile problem. Is there a good way to compile with debug symbols from the command line, or is there a solution file that is more up to date? Rob
Here is the problem I get compiling from svn. It is the same from command line as it was from monodevelop. *** Compiling FSpot.Widgets.dll gmcs -debug -target:library -out:FSpot.Widgets.dll -d:TEST_METADATA -d:BROKEN_RSVG -d:GTKHTML_3_14 -d:GIO_2_16 -d:GTK_2_10 -d:GTK_2_10_3 -d:GTK_2_11 -d:MONO_1_2_5 -d:CAIRO_1_2_5 -d:GCONF_SHARP_2_18 ./Widgets/ComplexMenuItem.cs ./Widgets/CustomPrintWidget.cs ./Widgets/HighlightedBox.cs ./Widgets/MenuButton.cs ./Widgets/Rating.cs ./Widgets/SaneTreeView.cs ./Widgets/ScrolledView.cs ./Widgets/Sidebar.cs ./Widgets/TagView.cs -pkg:gtk-sharp-2.0 -pkg:gnome-sharp-2.0 -r:Mono.Posix -r:FSpot.Core.dll -r:FSpot.Utils.dll ./Widgets/TagView.cs(21,9): warning CS0612: `Gtk.Tooltips' is obsolete ./Widgets/TagView.cs(29,25): warning CS0612: `Gtk.Tooltips' is obsolete ./Widgets/TagView.cs(100,37): warning CS0612: `Gtk.Tooltips' is obsolete Compilation succeeded - 3 warning(s) Makefile:654: *** insufficient number of arguments (1) to function `foreach'. Stop. make[2]: Leaving directory `/home/frohba/Desktop/trunk/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/frohba/Desktop/trunk' make: *** [all] Error 2 I also did the following: frohba@frohba-600m:~/Desktop$ svn co http://svn.gnome.org/svn/f-spot/trunk U trunk/src/Widgets/InfoBox.cs U trunk/extensions/ChangeLog U trunk/extensions/FolderExport/FolderExport.cs U trunk/extensions/FolderExport/FolderExport.addin.xml U trunk/po/es.po U trunk/po/ChangeLog U trunk/po/de.po Fetching external item into 'trunk/gio-sharp' Checked out external at revision 103197. Checked out revision 4056. frohba@frohba-600m:~/Desktop$ sudo apt-get install mono-gmcs libmono-sqlite2.0-cil libmono-cairo2.0-cil intltool subversion [sudo] password for frohba: E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable) E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? frohba@frohba-600m:~/Desktop$ sudo apt-get install mono-gmcs libmono-sqlite2.0-cil libmono-cairo2.0-cil intltool subversion Reading package lists... Done Building dependency tree Reading state information... Done mono-gmcs is already the newest version. libmono-sqlite2.0-cil is already the newest version. libmono-cairo2.0-cil is already the newest version. intltool is already the newest version. subversion is already the newest version. The following packages were automatically installed and are no longer required: libglitz-glx1 libmono-mozilla0.1-cil linux-headers-2.6.24-17-generic libglitz1 linux-headers-2.6.24-17 Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. frohba@frohba-600m:~/Desktop$ Maybe I'll learn some good stuff in the process of getting you a gdb output with symbols. Thanks, Rob
first, the monodevelop solution file is out-of-date second, this is a mono issue, having debugging symbols in f-spot won't help
if you can't compile from svn, it's because mondevelop messed with your Makefiles. get a fresh co if you want, but that won't automagically solve his isue
School is finally out, and now I have some time to try and fix this for my wife again. So I did a little more testing. I checked out f-spot anew from svn, and built it. Then I ran it with without installing it using: ./f-spot --uninstalled --basedir /tmp --photodir /tmp I found the same problem, when I clicked the close button. I found that when I choose quit from the file menu, it doesn't bring up the same force quit box, but f-spot stops responding, and is grayed out for me. I also found that f-spot seems to save photos imported, despite the claim from the force quit box. I suspect that the force quit box, which you can get even if you select the File->Quit option by clicking the close gadget on the window, is a higher level thing and that the warning is generic. This has only been tested once, but it worked. Perhaps this bug isn't as critical as I thought. I am not done trying things, and so if anyone has any ideas on how to further debug this, I'd be happy to try them. Best regards, Rob
it's nice your running svn. can you try this and report the output ? ./f-spot --uninstalled --basedir /tmp --photodir /tmp --trace=N:Dingus this won't fix your problem, but might give me a clue...
Here is your clue. I hope it is a good one. :-) frohba@frohba-600m:~/trunk/src$ ./f-spot --uninstalled --basedir /tmp --photodir /tmp --trace=N:Dingus *** Running uninstalled f-spot *** ** Running Mono with --trace=N:Dingus ** [Info 08:29:03.360] BaseDirectory is now /tmp [Info 08:29:03.373] PhotoDirectory is now /tmp [Info 08:29:03.374] Initializing DBus [Info 08:29:03.612] Initializing Mono.Addins EXCEPTION handling: Exception [Info 08:29:04.228] Starting new FSpot server EXCEPTION handling: NoSuchKeyException EXCEPTION handling: NoSuchKeyException EXCEPTION handling: ArgumentException EXCEPTION handling: ArgumentException EXCEPTION handling: NoSuchKeyException EXCEPTION handling: NoSuchKeyException EXCEPTION handling: ArgumentException (f-spot:20282): 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 frohba@frohba-600m:~/trunk/src$ I simply started f-spot with your command, and then I clicked the close gadget. When the box saying f-spot was not responding came up, I force quit it. I think the best clue I had before this, was that it happens on this account and not on another on the same computer. I plan to move the .gnome2 and other such preference files one by one to find out which one is causing the trouble, but that won't be until I am done with my meetings today. Thanks for your attention to this bug! Rob
no, it doesn't help :( but the fact that it only happen on 1 account is new, and could drive us in the right way
I have this issue, with an empty ~/Pictures dir (never used f-spot before). I'm also using Ubuntu 8.04, package 0.4.3.1-0ubuntu1, so it must not be related to library size. Please tell me what information I can provide to help debugging this issue.
I also have this issue. Even upgrading to F-Spot 0.5.0 didn't help.
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? Can any developer confirm that this gpg option is the cause of the issue?
this is an ubuntu only bug, and no longer happens in latest version (of U). There's nothing we can do here. keep discussing this on launchpad. closing.