GNOME Bugzilla – Bug 485392
crash in File Browser: Searching for .exe files...
Last modified: 2007-10-19 01:50:40 UTC
Version: 2.18.3 What were you doing when the application crashed? Searching for .exe files in my USB Memory Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-08-31 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-gentoo-r2 #1 SMP Sat Aug 18 01:47:10 PET 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human2 Memory status: size: 297758720 vsize: 297758720 resident: 46706688 share: 27332608 rss: 46706688 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192023327 rtime: 1142 utime: 921 stime: 221 cutime:58 cstime: 10 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 47464043945616 (LWP 6823)] [New Thread 1090660672 (LWP 8961)] 0x00002b2b151ff626 in poll () from /lib/libc.so.6
+ Trace 169256
Thread 2 (Thread 1090660672 (LWP 8961))
----------- .xsession-errors (934 sec old) --------------------- CSS Error (http://mail.google.com/mail/?ui=1&ik=70da238c5a&view=cv&search=inbox&th=11585f9e4d910c95&ww=1280&cvap=7&qt=&zx=nh22bk-yz5fgl :0.8): Error al leer el valor para la propiedad 'width'. Declar CSS Error (http://mail.google.com/mail/?ui=1&ik=70da238c5a&view=cv&search=inbox&th=11585f9e4d910c95&ww=1280&cvap=7&qt=&zx=nh22bk-yz5fgl :0.0): Se esperaba ':', pero se encontró 'none'. Declaración CSS Error (http://mail.google.com/mail/?ui=1&ik=70da238c5a&view=cv&search=inbox&th=11585f9e4d910c95&ww=1280&cvap=7&qt=&zx=nh22bk-yz5fgl :0.13): Error al leer el valor para la propiedad 'padding-left'. CSS Error (http://mail.google.com/mail/?ui=1&ik=70da238c5a&view=cv&search=inbox&th=11585f9e4d910c95&ww=1280&cvap=7&qt=&zx=nh22bk-yz5fgl :0.10): Error al leer el valor para la propiedad 'display'. Dec CSS Error (http://mail.google.com/mail/?ui=1&ik=70da238c5a&view=cv&search=inbox&th=11585f9e4d910c95&ww=1280&cvap=7&qt=&zx=nh22bk-yz5fgl :0.8): Error al leer el valor para la propiedad 'width'. Declar CSS Error (http://mail.google.com/mail/?ui=1&ik=70da238c5a&view=cv&search=inbox&th=11585f9e4d910c95&ww=1280&cvap=7&qt=&zx=nh22bk-yz5fgl :0.0): Se esperaba ':', pero se encontró 'none'. Declaración CSS Error (http://mail.google.com/mail/?ui=1&ik=70da238c5a&view=cv&search=inbox&th=11585f9e4d910c95&ww=1280&cvap=7&qt=&zx=nh22bk-yz5fgl :0.13): Error al leer el valor para la propiedad 'padding-left'. CSS Error (http://mail.google.com/mail/?ui=1&ik=70da238c5a&view=cv&search=inbox&th=11585f9e4d910c95&ww=1280&cvap=7&qt=&zx=nh22bk-yz5fgl :0.10): Error al leer el valor para la propiedad 'display'. Dec CSS Error (http://mail.google.com/mail/?ui=1&ik=70da238c5a&view=cv&search=inbox&th=11585f9e4d910c95&ww=1280&cvap=7&qt=&zx=nh22bk-yz5fgl :0.8): Error al leer el valor para la propiedad 'width'. Declar CSS Error (http://mail.google.com/mail/?ui=1&ik=70da238c5a&view=cv&search=inbox&th=11585f9e4d910c95&ww=1280&cvap=7&qt=&zx=nh22bk-yz5fgl :0.0): Se esperaba ':', pero se encontró 'none'. Declaración CSS Error (http://mail.google.com/mail/?ui=1&ik=70da238c5a&view=cv&search=inbox&th=11585f9e4d910c95&ww=1280&cvap=7&qt=&zx=nh22bk-yz5fgl :0.13): Error al leer el valor para la propiedad 'padding-left'. CSS Error (http://mail.google.com/mail/?ui=1&ik=70da238c5a&view=cv&search=inbox&th=11585f9e4d910c95&ww=1280&cvap=7&qt=&zx=nh22bk-yz5fgl :0.10): Error al leer el valor para la propiedad 'display'. Dec CSS Error (http://mail.google.com/mail/?ui=1&ik=70da238c5a&view=cv&search=inbox&th=11585f9e4d910c95&ww=1280&cvap=7&qt=&zx=nh22bk-yz5fgl :0.8): Error al leer el valor para la propiedad 'width'. Declar ...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 454799 ***