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 681766 - segfaults in fr_command_handle_process_error()
segfaults in fr_command_handle_process_error()
Status: RESOLVED FIXED
Product: file-roller
Classification: Applications
Component: general
3.5.x
Other Linux
: Normal normal
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2012-08-13 14:32 UTC by Sebastien Bacher
Modified: 2012-08-13 14:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastien Bacher 2012-08-13 14:32:12 UTC 
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1034531

The issue has been reported against 3.5.4 but git still seems to have the bug

"file-roller http://download.opensuse.org/repositories/isv:/ownCloud:/community/xUbuntu_12.04/csync_0.50.8-1.diff.gz

+ Trace 230664

  • #0 ??
  • #1 fr_command_handle_process_error
    at fr-command.c line 438
  • #2 load_local_archive_list_ready_cb
    at fr-command.c line 721
  • #3 g_simple_async_result_complete
    at /build/buildd/glib2.0-2.33.8/./gio/gsimpleasyncresult.c line 775
  • #4 complete_in_idle_cb
    at /build/buildd/glib2.0-2.33.8/./gio/gsimpleasyncresult.c line 787
  • #5 g_main_dispatch
    at /build/buildd/glib2.0-2.33.8/./glib/gmain.c line 2707
  • #6 g_main_context_dispatch
    at /build/buildd/glib2.0-2.33.8/./glib/gmain.c line 3211
  • #7 g_main_context_iterate
    at /build/buildd/glib2.0-2.33.8/./glib/gmain.c line 3282
  • #8 g_main_context_iteration
    at /build/buildd/glib2.0-2.33.8/./glib/gmain.c line 3343
  • #9 g_application_run
    at /build/buildd/glib2.0-2.33.8/./gio/gapplication.c line 1607
  • #10 main
    at main.c line 931 






Comment 1


Paolo Bacchilega





          2012-08-13 14:57:13 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.