GNOME Bugzilla – Bug 562800
crash in Home Folder: I wanted to open a folde...
Last modified: 2008-11-30 21:14:43 UTC
What were you doing when the application crashed? I wanted to open a folder with nautilus in debian lenny. Nautilus crashed. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Sat Nov 8 19:00:26 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 126930944 vsize: 126930944 resident: 48529408 share: 24514560 rss: 48529408 rss_rlim: 4294967295 CPU usage: start_time: 1228070062 rtime: 3300 utime: 3097 stime: 203 cutime:77 cstime: 20 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb69ab710 (LWP 16380)] [New Thread 0xb268eb90 (LWP 4783)] 0xb7f75424 in __kernel_vsyscall ()
+ Trace 210357
Thread 1 (Thread 0xb69ab710 (LWP 16380))
----------- .xsession-errors (2045 sec old) --------------------- path to watch: "/usr/share/kde4/apps/marble/data/maps/earth/srtm" path to watch: "/usr/share/kde4/apps/marble/data/maps/earth/srtm/srtm.dgml" path to watch: "/usr/share/kde4/apps/marble/data/maps/earth/temp-dec" path to watch: "/usr/share/kde4/apps/marble/data/maps/earth/temp-dec/temp-dec.dgml" path to watch: "/usr/share/kde4/apps/marble/data/maps/earth/temp-july" path to watch: "/usr/share/kde4/apps/marble/data/maps/earth/temp-july/temp-july.dgml" Entered selectTheme MapThemeId "earth/openstreetmap/openstreetmap.dgml" loadMapTheme "earth/openstreetmap/openstreetmap.dgml" level zero columns x rows: 1 x 1 Succesfully parsed file! DGML2 Name : "OpenStreetMap" ...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 512040 ***