GNOME Bugzilla – Bug 426123
crash in Archive Manager: Extracting an archive to...
Last modified: 2007-06-23 20:07:10 UTC
Version: 2.16.3 What were you doing when the application crashed? Extracting an archive to a location over the samba network. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 11:38:26 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 156012544 vsize: 0 resident: 156012544 share: 0 rss: 17580032 rss_rlim: 0 CPU usage: start_time: 1175661468 rtime: 0 utime: 278 stime: 0 cutime:224 cstime: 0 timeout: 54 it_real_value: 0 frequency: 94 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 -1208277296 (LWP 21221)] (no debugging symbols found) 0x0024c402 in __kernel_vsyscall ()
+ Trace 124844
Thread 1 (Thread -1208277296 (LWP 21221))
----------- .xsession-errors --------------------- Autoselected keyboard map en-us WARNING: Remote desktop does not support colour depth 24; falling back to 16 X Error of failed request: BadAtom (invalid Atom parameter) Major opcode of failed request: 23 (X_GetSelectionOwner) Atom id in failed request: 0x0 Serial number of failed request: 1045 Current serial number in output stream: 1045 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4600003 (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 0x4800003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** (bug-buddy:21242): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 427499 has been marked as a duplicate of this bug. ***
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 366580 ***