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 499243 - crash in Archive Manager: I have tried to open tar...
crash in Archive Manager: I have tried to open tar...
Status: RESOLVED DUPLICATE of bug 488564
Product: file-roller
Classification: Applications
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2007-11-23 20:15 UTC by igorr74
Modified: 2007-11-23 23:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description igorr74 2007-11-23 20:15:04 UTC 
Version: 2.20.1

What were you doing when the application crashed?
I have tried to open tar.bz2 archive


Distribution:                    Solaris Express Community Edition snv_77 X86
Gnome Release: 2.20.1 2007-10-22 (Sun Microsystems, Inc.)
BugBuddy Version: 2.20.1

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: my-theme
Icon Theme: nimbus

Memory status: size: 145817600 vsize: 145817600 resident: 21102592 share: 2142208 rss: 21102592 rss_rlim: 0
CPU usage: start_time: 0 rtime: 63 utime: 562764 stime: 73119 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/file-roller'

(no debugging symbols found)
sol-thread active.
Retry #1:
Retry #2:
Retry #3:
Retry #4:
[New LWP    1        ]
[New Thread 1 (LWP 1)]

+ Trace 179398

Thread 1 (LWP 1)

  • #0 _waitid
    from /lib/libc.so.1
  • #1 _waitpid
    from /lib/libc.so.1
  • #2 waitpid_cancel
    from /lib/libc.so.1
  • #3 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #5 __1cNrun_bug_buddy6Fpkclp0_b_
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 __1cMcheck_if_gdb6Fpv_b_
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 _ex_text0
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 __sighndlr
    from /lib/libc.so.1
  • #9 call_user_handler
    from /lib/libc.so.1
  • #10 <signal handler called>
  • #11 countbytes
    from /lib/libc.so.1
  • #12 _ndoprnt
    from /lib/libc.so.1
  • #13 vsnprintf
    from /lib/libc.so.1
  • #14 g_printf_string_upper_bound
    from /usr/lib/libglib-2.0.so.0
  • #15 g_vasprintf
    from /usr/lib/libglib-2.0.so.0
  • #16 g_strdup_vprintf
    from /usr/lib/libglib-2.0.so.0
  • #17 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #18 g_log
    from /usr/lib/libglib-2.0.so.0
  • #19 g_type_check_instance_cast
    from /usr/lib/libgobject-2.0.so.0
  • #20 fr_window_stop_activity_mode
  • #21 fr_window_free_private_data
  • #22 fr_window_finalize
  • #23 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_object_run_dispose
    from /usr/lib/libgobject-2.0.so.0
  • #25 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 close__step2
  • #28 g_idle_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #30 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #31 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #32 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #33 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 main 

Thread 1 (LWP    1        ):
#-1 0xcfef4075 in _waitid () from /lib/libc.so.1
No symbol table info available.
#-1 0xcfef4075 in _waitid () from /lib/libc.so.1


----------- .xsession-errors (7427 sec old) ---------------------
/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/dt/config/Xsession.jds
--------------------------------------------------
Comment 1 Susana 2007-11-23 23:26:02 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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