GNOME Bugzilla – Bug 509407
crash in Open Folder: I checked properties on ...
Last modified: 2008-01-14 23:50:02 UTC
Version: 2.18.3 What were you doing when the application crashed? I checked properties on my Ipod icon located on the desktop. 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: Clearlooks Icon Theme: Tango Memory status: size: 72880128 vsize: 72880128 resident: 22106112 share: 14852096 rss: 22106112 rss_rlim: 4294967295 CPU usage: start_time: 1200326421 rtime: 152 utime: 136 stime: 16 cutime:0 cstime: 0 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 0xb6dae6b0 (LWP 3405)] [New Thread 0xb5cecb90 (LWP 10718)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 185302
Thread 1 (Thread 0xb6dae6b0 (LWP 3405))
----------- .xsession-errors (37 sec old) --------------------- BEGIN checking gmail account jgranqvist ... END checking gmail account jgranqvist ... BEGIN checking gmail account jgranqvist ... END checking gmail account jgranqvist ... BEGIN checking gmail account jgranqvist ... END checking gmail account jgranqvist ... BEGIN checking gmail account jgranqvist ... END checking gmail account jgranqvist ... BEGIN checking gmail account jgranqvist ... END checking gmail account jgranqv (gecko:3786): Pango-WARNING **: failed to create cairo scaled font, expect ugly output. the offending font is 'Arial 0' (gecko:3786): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Arial 0', text=' ' (gecko:3786): Pango-WARNING **: pango_font_get_glyph_extents called with null font argument, expect ugly output --------------------------------------------------
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 ***