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 463968 - file-roller crashed with SIGSEGV in g_closure_invoke()
file-roller crashed with SIGSEGV in g_closure_invoke()
Status: RESOLVED FIXED
Product: file-roller
Classification: Applications
Component: general
2.19.x
Other Linux
: Normal critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2007-08-06 11:20 UTC by Sebastien Bacher
Modified: 2007-09-09 09:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Sebastien Bacher 2007-08-06 11:20:29 UTC 
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/126788

"Binary package hint: file-roller

Using the 'extract archive here' option from the right click dialogue menu on a rar archive when the libraries to support the rar format are not installed.
...
Package: file-roller 2.19.3-0ubuntu1
...

+ Trace 153175

  • #0 action_performed
    at fr-window.c line 2773
  • #1 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.13.6/gobject/gclosure.c line 490
  • #2 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.13.6/gobject/gsignal.c line 2440
  • #3 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.13.6/gobject/gsignal.c line 2199
  • #4 IA__g_signal_emit
    at /build/buildd/glib2.0-2.13.6/gobject/gsignal.c line 2243
  • #5 copy_remote_file_cb
    at fr-archive.c line 1401
  • #6 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.13.6/glib/gmain.c line 2061
  • #7 g_main_context_iterate
    at /build/buildd/glib2.0-2.13.6/glib/gmain.c line 2694
  • #8 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.13.6/glib/gmain.c line 2898
  • #9 IA__gtk_main
    at /build/buildd/gtk+2.0-2.11.5/gtk/gtkmain.c line 1144
  • #10 main
    at main.c line 239 






Comment 1


Paolo Bacchilega





          2007-09-09 09:17:02 UTC
        



This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.