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 507405 - crash in Archive Manager: downloading unzipping
crash in Archive Manager: downloading unzipping
Status: RESOLVED DUPLICATE of bug 452880
Product: file-roller
Classification: Applications
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2008-01-05 02:00 UTC by sakaldeo.sinha
Modified: 2008-05-04 23:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description sakaldeo.sinha 2008-01-05 02:00:24 UTC 
Version: 2.18.4

What were you doing when the application crashed?
downloading  unzipping



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 36675584 vsize: 36675584 resident: 19955712 share: 16154624 rss: 19955712 rss_rlim: 4294967295
CPU usage: start_time: 1199498271 rtime: 169 utime: 143 stime: 26 cutime:5 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208801568 (LWP 4274)]
(no debugging symbols found)
0x0015f402 in __kernel_vsyscall ()

+ Trace 184119

Thread 1 (Thread -1208801568 (LWP 4274))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_type_check_instance_cast
    from /lib/libgobject-2.0.so.0
  • #5 ??
  • #6 ??
  • #7 window_update_file_list
  • #8 ??
  • #9 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #10 g_cclosure_marshal_VOID__BOOLEAN
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #13 ??
  • #14 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #15 g_cclosure_marshal_VOID__BOOLEAN
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #18 ??
  • #19 g_cclosure_marshal_VOID__POINTER
    from /lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #21 g_cclosure_marshal_VOID__BOOLEAN
    from /lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #24 ??
  • #25 g_cclosure_marshal_VOID__BOOLEAN
    from /lib/libglib-2.0.so.0
  • #26 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #27 g_cclosure_marshal_VOID__BOOLEAN
    from /lib/libglib-2.0.so.0
  • #28 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #29 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (2753 sec old) ---------------------
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800048 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-04 23:26:43 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 452880 ***