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 365696 - f-spot-import crash
f-spot-import crash
Status: RESOLVED FIXED
Product: f-spot
Classification: Other
Component: Import
0.2.2
Other All
: Normal critical
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-27 11:11 UTC by Víctor Enríquez
Modified: 2006-12-02 16:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Víctor Enríquez 2006-10-27 11:11:07 UTC
Steps to reproduce:
1. f-spot-import /path/to/ or calling import from f-spot.
2. 
3. 


Stack trace:
gosth@DarkSun ~ $ f-spot-import 
4582: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 797.
This is normally a bug in some application using the D-BUS library.
libhal.c 995 : Couldn't allocate D-BUS message
error: libhal_device_get_property_type: (null): (null)
4583: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 797.
This is normally a bug in some application using the D-BUS library.
libhal.c 995 : Couldn't allocate D-BUS message
error: libhal_device_get_property_type: (null): (null)
4584: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 797.
This is normally a bug in some application using the D-BUS library.
libhal.c 995 : Couldn't allocate D-BUS message
error: libhal_device_get_property_type: (null): (null)
gphoto2:usb:000,000
*** WARNING *** The programme 'mono' uses the Apple Bonjour compatiblity layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=mono>
f-spot: compat.c:465: sdref_unref: La declaración `sdref->n_ref >= 1' no se cumple.

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

Stacktrace:

  at (wrapper managed-to-native) LibGPhoto2.PortInfoList.gp_port_info_list_load (System.Runtime.InteropServices.HandleRef) <0x00004>
  at (wrapper managed-to-native) LibGPhoto2.PortInfoList.gp_port_info_list_load (System.Runtime.InteropServices.HandleRef) <0xffffffff>
  at LibGPhoto2.PortInfoList.Load () <0x0002c>
  at GPhotoCamera..ctor () <0x00045>
  at MainWindow.ImportCamera (string) <0x0005f>
  at ImportCommand.Execute () <0x0003a>
  at FSpot.Core.Import (string) <0x0003e>
  at FSpot.Driver.Main (string[]) <0x00694>
  at (wrapper runtime-invoke) System.Object.runtime_invoke_void_string[] (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

        f-spot [0x81556d9]
        [0xb7ef9440]
        /lib/libc.so.6(abort+0x101) [0xb7d0b671]
        /lib/libc.so.6(__assert_fail+0xfd) [0xb7d03d29]
        /usr/lib/libdns_sd.so.1 [0xb535a6fd]
        [0xbf007069]

Debug info from gdb:

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1211234608 (LWP 4586)]
[New Thread -1257247856 (LWP 4591)]
[New Thread -1256195184 (LWP 4590)]
[New Thread -1221207152 (LWP 4588)]
[New Thread -1221190768 (LWP 4587)]
0xb7ef9410 in __kernel_vsyscall ()
  5 Thread -1221190768 (LWP 4587)  0xb7ef9410 in __kernel_vsyscall ()
  4 Thread -1221207152 (LWP 4588)  0xb7ef9410 in __kernel_vsyscall ()
  3 Thread -1256195184 (LWP 4590)  0xb7ef9410 in __kernel_vsyscall ()
  2 Thread -1257247856 (LWP 4591)  0xb7ef9410 in __kernel_vsyscall ()
  1 Thread -1211234608 (LWP 4586)  0xb7ef9410 in __kernel_vsyscall ()

Thread 4 (Thread -1221207152 (LWP 4588))

  • #0 __kernel_vsyscall
  • #1 pthread_cond_wait
    from /lib/libpthread.so.0
  • #2 mono_pthread_key_for_tls
  • #3 mono_pthread_key_for_tls
  • #4 mono_pthread_key_for_tls
  • #5 mono_pthread_key_for_tls
  • #6 mono_gc_is_finalizer_thread
  • #7 mono_thread_get_abort_signal
  • #8 mono_pthread_key_for_tls
  • #9 GC_start_blocking
  • #10 start_thread
    from /lib/libpthread.so.0
  • #11 clone
    from /lib/libc.so.6

/usr/bin/f-spot-import: line 20:  4586 Abortado                f-spot --import "$uri"


Other information:
Im using Gentoo Linux ~x86 other info related to this bug is on this page http://bugs.gentoo.org/show_bug.cgi?id=152954
Comment 1 Larry Ewing 2006-11-01 21:39:36 UTC
This looks like you are using libgphoto2 complied with unstable hal support.  Does  rebuilding libbgphoto2 with the hal support disabled fix the problem?
Comment 2 Víctor Enríquez 2006-11-02 00:14:23 UTC
Hi Larry thanks for your support!.

rebuilding libgphoto2 with USE=-hal and then rebuilding f-spot doesn't work like you expected i'm having the same crash. I will try rebuilding all the packages depending on libgphoto2 and then rebuilding f-spot and i'll tell you about. 

This are my settings in this try:

emerge -vp libgphoto2 f-spot

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] media-libs/libgphoto2-2.2.1-r1  USE="-exif -hal nls -usb -doc" 0 kB 
[ebuild   R   ] media-gfx/f-spot-0.2.2  USE="-debug" 0 kB 

And the crash is:

1560: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 797.
This is normally a bug in some application using the D-BUS library.
libhal.c 995 : Couldn't allocate D-BUS message
error: libhal_device_get_property_type: (null): (null)
1561: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 797.
This is normally a bug in some application using the D-BUS library.
libhal.c 995 : Couldn't allocate D-BUS message
error: libhal_device_get_property_type: (null): (null)
1562: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 797.
This is normally a bug in some application using the D-BUS library.
libhal.c 995 : Couldn't allocate D-BUS message
error: libhal_device_get_property_type: (null): (null)
gphoto2:usb:000,000
*** WARNING *** The programme 'mono' uses the Apple Bonjour compatiblity layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=mono>
f-spot: compat.c:465: sdref_unref: La declaración `sdref->n_ref >= 1' no se cumple.

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

Stacktrace:

  at (wrapper managed-to-native) LibGPhoto2.PortInfoList.gp_port_info_list_load (System.Runtime.InteropServices.HandleRef) <0x00004>
  at (wrapper managed-to-native) LibGPhoto2.PortInfoList.gp_port_info_list_load (System.Runtime.InteropServices.HandleRef) <0xffffffff>
  at LibGPhoto2.PortInfoList.Load () <0x0002c>
  at GPhotoCamera..ctor () <0x00045>
  at MainWindow.ImportCamera (string) <0x0005f>
  at ImportCommand.Execute () <0x0003a>
  at FSpot.Core.Import (string) <0x0003e>
  at FSpot.Driver.Main (string[]) <0x00694>
  at (wrapper runtime-invoke) System.Object.runtime_invoke_void_string[] (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

        f-spot [0x81556d9]
        [0xb7f90440]
        /lib/libc.so.6(abort+0x101) [0xb7da2671]
        /lib/libc.so.6(__assert_fail+0xfd) [0xb7d9ad29]
        /usr/lib/libdns_sd.so.1 [0xb50716fd]
        [0xbf007069]

Debug info from gdb:

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1210616112 (LWP 1564)]
[New Thread -1255765104 (LWP 1568)]
[New Thread -1254712432 (LWP 1567)]
[New Thread -1220588656 (LWP 1566)]
[New Thread -1220572272 (LWP 1565)]
0xb7f90410 in __kernel_vsyscall ()
  5 Thread -1220572272 (LWP 1565)  0xb7f90410 in __kernel_vsyscall ()
  4 Thread -1220588656 (LWP 1566)  0xb7f90410 in __kernel_vsyscall ()
  3 Thread -1254712432 (LWP 1567)  0xb7f90410 in __kernel_vsyscall ()
  2 Thread -1255765104 (LWP 1568)  0xb7f90410 in __kernel_vsyscall ()
  1 Thread -1210616112 (LWP 1564)  0xb7f90410 in __kernel_vsyscall ()

Thread 4 (Thread -1220588656 (LWP 1566))

  • #0 __kernel_vsyscall
  • #1 pthread_cond_wait
    from /lib/libpthread.so.0
  • #2 mono_pthread_key_for_tls
  • #3 mono_pthread_key_for_tls
  • #4 mono_pthread_key_for_tls
  • #5 mono_pthread_key_for_tls
  • #6 mono_gc_is_finalizer_thread
  • #7 mono_thread_get_abort_signal
  • #8 mono_pthread_key_for_tls
  • #9 GC_start_blocking
  • #10 start_thread
    from /lib/libpthread.so.0
  • #11 clone
    from /lib/libc.so.6

/usr/bin/f-spot-import: line 20:  1564 Abortado                f-spot --import "$uri"

If you want more info tell me please.



Comment 3 Larry Ewing 2006-12-01 23:58:46 UTC
what distribution are you using?
Comment 4 Víctor Enríquez 2006-12-02 16:11:28 UTC
Like i said in comment 0, i'm using Gentoo.
This bug is finally solved, after upgrading, mono, gtkmm and other packages, seems like libgphoto2 was fine and was not the cause of the bug.

In any case the bug is solved now, thanks for your support.