GNOME Bugzilla – Bug 460285
crash in Open Folder: searching a windows shar...
Last modified: 2007-09-05 15:38:29 UTC
Version: 2.18.3 What were you doing when the application crashed? searching a windows share via a wireless network Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 90234880 vsize: 90234880 resident: 33357824 share: 22048768 rss: 33357824 rss_rlim: 4294967295 CPU usage: start_time: 1185376234 rtime: 4315 utime: 3936 stime: 379 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (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 -1208568096 (LWP 3128)] [New Thread -1238377584 (LWP 4272)] (no debugging symbols found) 0x005e4402 in __kernel_vsyscall ()
+ Trace 150476
Thread 2 (Thread -1238377584 (LWP 4272))
----------- .xsession-errors (16 sec old) --------------------- Major opcode: 20 Minor opcode: 0 Resource id: 0x500000a sh: mpg123: command not found QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * ) ICE default IO error handler doing an exit(), pid = 3854, errno = 0 --- Hash table keys for warning below: --> file:///home/peter (nautilus:4049): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:3128): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x2fdcb)! --------------------------------------------------
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 and reopen this bug or report a new one. Thanks in advance!
*** Bug 460282 has been marked as a duplicate of this bug. ***
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!
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 454799 ***