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 582471 - file-roller crashed with SIGSEGV in IA__g_object_ref()
file-roller crashed with SIGSEGV in IA__g_object_ref()
Status: RESOLVED INCOMPLETE
Product: file-roller
Classification: Applications
Component: general
2.26.x
Other Linux
: Normal critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2009-05-13 14:35 UTC by Pedro Villavicencio
Modified: 2011-01-27 03:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Pedro Villavicencio 2009-05-13 14:35:26 UTC 
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/file-roller/+bug/375474

"I opened a TAR archive in file-roller and tried to drag&drop a file to a nautilus window that displayed a remote directory with SFTP. The file was not copied therefore I insisted several times and file-roller ended-up crashing."

".

+ Trace 215412

Thread 1 (process 7553)

  • #0 IA__g_object_ref
    at /build/buildd/glib2.0-2.20.1/gobject/gobject.c line 2339
  • #1 IA__g_simple_async_result_run_in_thread
    at /build/buildd/glib2.0-2.20.1/gio/gsimpleasyncresult.c line 695
  • #2 g_file_real_enumerate_children_async
    at /build/buildd/glib2.0-2.20.1/gio/gfile.c line 4207
  • #3 IA__g_file_enumerate_children_async
    at /build/buildd/glib2.0-2.20.1/gio/gfile.c line 870
  • #4 for_each_child_start_current
    at gio-utils.c line 374
  • #5 action_performed
    at fr-archive.c line 870
  • #6 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c line 767
  • #7 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 3247
  • #8 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 2980
  • #9 IA__g_signal_emit
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 3037
  • #10 fr_command_done
    at fr-command.c line 231
  • #11 IA__g_cclosure_marshal_VOID__VOID
    at /build/buildd/glib2.0-2.20.1/gobject/gmarshal.c line 77
  • #12 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.20.1/gobject/gclosure.c line 767
  • #13 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 3247
  • #14 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 2980
  • #15 IA__g_signal_emit
    at /build/buildd/glib2.0-2.20.1/gobject/gsignal.c line 3037
  • #16 check_child
    at fr-process.c line 912
  • #17 g_timeout_dispatch
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c line 3253
  • #18 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c line 1814
  • #19 g_main_context_iterate
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c line 2448
  • #20 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c line 2656
  • #21 IA__gtk_main
    at /build/buildd/gtk+2.0-2.16.1/gtk/gtkmain.c line 1205
  • #22 main
    at main.c line 309 






Comment 1


Tomas Bzatek





          2010-05-18 13:43:23 UTC
        



I believe this is fixed in master by the following commit:

commit 33c21fc3647af32de5a9c9d49e33765a526910f5
Author: Tomas Bzatek <tbzatek@redhat.com>
Date:   Wed May 12 13:54:29 2010 +0200

    Bring back support for file caching when gvfs-fuse-daemon is not available
    
    The commit 73fa5d77a60861cd35c6f3425d27c88061af081c introduced trouble
    when user was trying to work with archives on remote GIO mounts and
    not having the fuse daemon running. This led to segfaults and error messages.
    
    Please see bug #617769 for details.

Please check the changes and close this bugreport if it resolves the issue.






Comment 2


Akhil Laddha





          2010-12-15 10:23:34 UTC
        



Moving to needinfo as per comment#1






Comment 3


Akhil Laddha





          2011-01-27 03:48:14 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!