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 382229 - file roller crashes on ISO file
file roller crashes on ISO file
Status: RESOLVED DUPLICATE of bug 376848
Product: file-roller
Classification: Applications
Component: general
2.16.x
Other All
: Normal critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on: 382227
Blocks:
 
 
Reported: 2006-12-04 12:05 UTC by bjohnson
Modified: 2006-12-19 23:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description bjohnson 2006-12-04 12:05:25 UTC 
Steps to reproduce:
1. download http://mirror.switch.ch/ftp/mirror/eldk/eldk/3.1.1-2005-06-07/ppc-linux-x86/iso/ppc-2005-06-07-src.iso
2. right click on it -> extract here
3. 


Stack trace:
The application file-roller has crashed.

However you don't have installed bug-buddy, the GNOME crash report tool.  If you want to help us to make GNOME better, please, install it

I installed bug buddy, but I can't get a stack trace because of bug #382227.

Other information:
Comment 1 André Klapper 2006-12-05 23:10:27 UTC 
hi,
thanks for taking the time to report this.

if your distribution provides any debug packages for file-roller, glib and gtk, can you please install them?
*if* you're a bit familiar with using the terminal/shell, can you get us a stacktrace by using "gdb"? see http://live.gnome.org/GettingTraces/Details, section "Obtaining a stack trace using GDB" for more information. thanks. :-)
Comment 2 bjohnson 2006-12-10 09:26:49 UTC 
I don't know if the "(CRC mismatch)" is important below so I included those lines as well.

I started file-roller, clicked "Open" and navigated to the directory with my .iso files.  Then I selected the one I mentioned above and clicked "Open"


(gdb) run
Starting program: /usr/bin/file-roller 
warning: the debug information found in "/usr/lib/debug//usr/lib/libgtk-x11-2.0.so.0.1000.4.debug" does not match "/usr/lib/libgtk-x11-2.0.so.0" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug//usr/lib/libgdk-x11-2.0.so.0.1000.4.debug" does not match "/usr/lib/libgdk-x11-2.0.so.0" (CRC mismatch).

warning: the debug information found in "/usr/lib/debug//usr/lib/libgdk_pixbuf-2.0.so.0.1000.4.debug" does not match "/usr/lib/libgdk_pixbuf-2.0.so.0" (CRC mismatch).

[Thread debugging using libthread_db enabled]
[New Thread -1208142128 (LWP 18621)]
[New Thread -1233855600 (LWP 18628)]
[New Thread -1244345456 (LWP 18629)]
[New Thread -1254835312 (LWP 18630)]
[Thread -1244345456 (LWP 18629) exited]
[Thread -1233855600 (LWP 18628) exited]
[Thread -1254835312 (LWP 18630) exited]
Couldn't get registers: No such process.
(gdb) thread apply all bt

+ Trace 92976

Thread 1 (Thread -1208142128 (LWP 18621))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 fork
    from /lib/libc.so.6
  • #2 fork
    from /lib/libpthread.so.0
  • #3 fork_exec_with_pipes
    at gspawn.c line 1083
  • #4 IA__g_spawn_async_with_pipes
    at gspawn.c line 584
  • #5 start_current_command
    at fr-process.c line 628
  • #6 fr_archive_load
    at fr-archive.c line 776
  • #7 window_archive_open
    at window.c line 4375
  • #8 open_file_response_cb
    at actions.c line 468
  • #9 IA__g_cclosure_marshal_VOID__INT
    at gmarshal.c line 216
  • #10 IA__g_closure_invoke
    at gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #13 IA__g_signal_emit
    at gsignal.c line 2241
  • #14 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #17 IA__g_closure_invoke
    at gclosure.c line 490
  • #18 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #19 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #20 IA__g_signal_emit
    at gsignal.c line 2241
  • #21 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_button_set_alignment
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #24 g_type_class_meta_marshal
    at gclosure.c line 567
  • #25 IA__g_closure_invoke
    at gclosure.c line 490
  • #26 signal_emit_unlocked_R
    at gsignal.c line 2368
  • #27 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #28 IA__g_signal_emit
    at gsignal.c line 2241
  • #29 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 g_type_class_meta_marshal
    at gclosure.c line 567
  • #33 IA__g_closure_invoke
    at gclosure.c line 490
  • #34 signal_emit_unlocked_R
    at gsignal.c line 2476
  • #35 IA__g_signal_emit_valist
    at gsignal.c line 2207
  • #36 IA__g_signal_emit
    at gsignal.c line 2241
  • #37 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #41 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #42 g_main_context_iterate
    at gmain.c line 2677
  • #43 IA__g_main_loop_run
    at gmain.c line 2881
  • #44 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 main
    at main.c line 228
  • #46 __libc_start_main
    from /lib/libc.so.6
  • #47 _start 






Comment 3


Paolo Bacchilega





          2006-12-19 23:07:00 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 376848 ***