GNOME Bugzilla – Bug 485690
crash in Home Folder: nach einer datei gesucht
Last modified: 2007-10-19 01:50:44 UTC
What were you doing when the application crashed? nach einer datei gesucht Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-09-24 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22.9 #4 SMP PREEMPT Fri Oct 5 13:01:54 CEST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: E17-GTK-GREEN Icon Theme: LeopardX-Beta2 Memory status: size: 295034880 vsize: 295034880 resident: 39444480 share: 24027136 rss: 39444480 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192008868 rtime: 10042 utime: 8953 stime: 1089 cutime:1287 cstime: 193 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 47560046204368 (LWP 17038)] [New Thread 1140889920 (LWP 6711)] 0x00002b416e888816 in poll () from /lib/libc.so.6
+ Trace 169468
Thread 2 (Thread 1140889920 (LWP 6711))
----------- .xsession-errors (86952 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ALSA lib conf.c:3939:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:910:(snd_ctl_open_noupdate) Invalid CTL default:0 ALSA lib pcm_softvol.c:889:(_snd_pcm_softvol_open) Unknown field max_dB fixme:wave:ALSA_AddCaptureDevice Add support for DSCapture fixme:advapi:SetSecurityInfo stub fixme:system:SystemParametersInfoW Unimplemented action: 112 (SPI_GETMOUSESPEED) fixme:powrprof:DllMain (0x7cd00000, 1, (nil)) not fully implemented ...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 ***