After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 390314 - crash in F-Spot Photo Manager: Trying to import a direc...
crash in F-Spot Photo Manager: Trying to import a direc...
Status: RESOLVED INCOMPLETE
Product: f-spot
Classification: Other
Component: General
0.3.0
Other All
: Normal major
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-28 11:15 UTC by Hans de Graaff
Modified: 2008-07-16 22:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Hans de Graaff 2006-12-28 11:15:33 UTC
What were you doing when the application crashed?
Trying to import a directory of images. Since the import file browser did not show my home directory or my Desktop directory I manually entered my home directory, getting this crash.


Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.2 2006-11-20 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 216633344 vsize: 216633344 resident: 56045568 share: 18780160 rss: 56045568 rss_rlim: -1
CPU usage: start_time: 1167304523 rtime: 875 utime: 833 stime: 42 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/f-spot'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47160069567488 (LWP 16564)]
[New Thread 1083406672 (LWP 16569)]
[New Thread 1080977744 (LWP 16568)]
[New Thread 1078876496 (LWP 16567)]
[New Thread 1075988816 (LWP 16566)]
[New Thread 1073822032 (LWP 16565)]
0x00002ae44ed8692f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47160069567488 (LWP 16564))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib/libglib-2.0.so.0
  • #7 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #8 gtk_file_chooser_button_new
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #9 gtk_file_chooser_dialog_new
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #11 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #15 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #18 gtk_button_set_alignment
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #19 gtk_marshal_BOOLEAN__VOID
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #21 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #24 gtk_widget_get_default_style
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #25 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #26 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #27 gdk_add_client_message_filter
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #28 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #31 gtk_dialog_run
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
  • #38 ??
  • #39 ??
  • #40 ??
  • #41 ??
  • #0 waitpid
    from /lib/libpthread.so.0

Comment 1 Thomas Van Machelen 2006-12-28 11:53:24 UTC
Thanks for taking the time to report this bug.

Unfortunately there isn't much we can do with the current stacktrace.  Can you reproduce the error after you executed f-spot from a console?  The produced stacktrace should give us more information.

Comment 2 Hans de Graaff 2006-12-28 12:01:01 UTC
When starting f-spot from the shell I still get a crash that is filtered through bug buddy, but I did get the following assertion:

Gtk-ERROR **: file gtkfilechooserdefault.c: line 7772 (gtk_file_chooser_default_should_respond): assertion failed: (path != NULL)
aborting...


In addition the real problem seems to occur earlier, because my file chooser doesn't show me the Desktop and Home directory items that are there normally. The same file chooser in Evolution does show these items and works as expected.

Comment 3 Hans de Graaff 2006-12-30 10:02:04 UTC
Some more information that might be helpful. When I reported the bug I was still using the 2.8.2 bindings for GTK+ and GNOME. I am currently in the process of updating them, and I found that updating the gnome-sharp bindings to 2.16.0 did give me the Home and Desktop directory entries back, but no files appear in the right-hand area and f-spot seems to have gone in an endless loop. Trying this a second time actually did get me the files. However, subsequent attempts return me to the empty file browser without Home and Desktop entries, and I'm back where I started.

So in the end my conclusion is that this is not related to the version of the bindings.

Most likely candidate seems to be either an initialization issue or a race conditions. If there are suggestions on how to debug this further I'd be happy to have another look.
Comment 4 Hans de Graaff 2006-12-30 16:01:01 UTC
Two more data points:

The endless loop I mentioned in my previous comment isn't actually an endless loop. Instead it seems to be a problem with event handling. When I cover the window and then uncover it the files in the currently selected directory suddenly appear. By doing this repeatedly I can navigate around and actually import the files. Note that the import dialog (where the to be imported files are previewed and tags can be selected) also suffers from the same issue.

After looking around in src/CompatFileChooser.cs I decided to change the #if false on line 233 to #if true. Now I don't have the additional drives anymore that f-spot seems to populate the file chooser with, but I can navigate around again without issues. That solves my problems since I don't care about the extra drives in the menu. 

Now if only it was so easy to import and tag and comment on all my old photos... :-)
Comment 5 Stephane Delcroix 2007-01-02 13:33:41 UTC
Hi hans,

Do you really have a '#if false' on line 233 in src/CompatFileChooser.cs ?

And secondly, f-spot doesn't say anything on the console at all ??? in that case, it's more than probably an mono issue :(

Anyway, with an updated system (*-sharp, mono and gnome) it should be better...
Comment 6 Hans de Graaff 2007-01-04 14:09:41 UTC
Actually the '#if false' line is on line 151 of src/CompatFileChooser.cs.

I have now updated mono from version 1.1.13.8.1 to 1.2.2.1, reverted my change to src/CompatFileChooser.cs, and recompiled f-spot. Things seem to work again as expected. So I agree that this is most likely an issue with mono.

Perhaps f-spot should require a sufficiently new version to avoid bugs like these?

Comment 7 Hans de Graaff 2007-01-14 16:23:19 UTC
Bad news, I'm seeing this bug again with f-spot compiled with mono 1.2.2.1. It happened today after importing a number of directories, one at a time. Perhaps the problem is related to the number of times the import file chooser is shown or used?
Comment 8 Larry Ewing 2007-02-05 16:24:27 UTC
what version of gtk do you have?
Comment 9 Hans de Graaff 2007-02-05 17:18:17 UTC
I've been using gtk+ 2.10.6 until Jan 19th, then switched to 2.10.7 and back again to 2.10.6 on Jan 20th. Since Jan 26th I'm using 2.10.9.

I haven't seen the problem yet since installing 2.10.9, but I have also not had a need to import several times in a row, so I can't tell if 2.10.9 fixes the bug.
Comment 10 Bengt Thuree 2007-11-21 21:02:38 UTC
Is this problem still occurring, and if so which versions are you using now?
Comment 11 André Klapper 2008-07-16 22:06:04 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!