GNOME Bugzilla – Bug 514476
crash in Open Folder: viewing properties of fi...
Last modified: 2008-02-05 10:17:14 UTC
Version: 2.18.3 What were you doing when the application crashed? viewing properties of files, which are in USB disk Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy P Icon Theme: Industrial Memory status: size: 74170368 vsize: 74170368 resident: 24510464 share: 15171584 rss: 24510464 rss_rlim: 4294967295 CPU usage: start_time: 1202201273 rtime: 330 utime: 303 stime: 27 cutime:206 cstime: 18 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6e086b0 (LWP 14035)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 188137
Thread 1 (Thread 0xb6e086b0 (LWP 14035))
----------- .xsession-errors (9266 sec old) --------------------- GCJ PLUGIN: thread 0x8156380: NP_GetValue GCJ PLUGIN: thread 0x8156380: NP_GetValue: returning plugin description. GCJ PLUGIN: thread 0x8156380: NP_GetValue return GCJ PLUGIN: thread 0x8156380: NP_GetMIMEDescription GCJ PLUGIN: thread 0x8156380: NP_GetMIMEDescription return GCJ PLUGIN: thread 0x8156380: NP_GetValue GCJ PLUGIN: thread 0x8156380: NP_GetValue: returning plugin name. GCJ PLUGIN: thread 0x8156380: NP_GetValue return GCJ PLUGIN: thread 0x8156380: NP_GetValue GCJ PLUGIN: thread 0x8156380: NP_GetValue: returning plugin description. GCJ PLUGIN: thread 0x8156380: NP_GetValue return ** Message: drive = 0 ** Message: volume = 0 ...Too much output, ignoring rest... --------------------------------------------------
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 355018 ***