GNOME Bugzilla – Bug 535541
crash in Home Folder: Ich habe auf einen netzw...
Last modified: 2008-05-30 11:23:09 UTC
What were you doing when the application crashed? Ich habe auf einen netzwerkorder unter win vista zugeriffen, wo nur bilder drin waren (jpg) Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 93687808 vsize: 93687808 resident: 37953536 share: 16326656 rss: 37953536 rss_rlim: 4294967295 CPU usage: start_time: 1212088744 rtime: 386 utime: 360 stime: 26 cutime:5 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 0xb6b4e720 (LWP 2892)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199026
Thread 1 (Thread 0xb6b4e720 (LWP 2892))
----------- .xsession-errors (31 sec old) --------------------- SndSys_Init: using the ALSA module SndSys_Init: PCM device is "default" Sound format: 48000Hz, 2 channels, 16 bits per sample Initial CD volume: 1 CD Audio Initialized Client using an automatically assigned port Client opened a socket on address local:2 Client opened a socket on address 0.0.0.0:56334 Fake CD track 1 playing... ERROR: Failed to parse the following modeline of display device 0x00000001 'CRT-0' connected to GPU-0 'GeForce 7800 GS': source=xserver :: "nvidia-auto-select" 194.020 1024 1108 1220 1416 768 768 770 806 DoubleScan -HSync +VSync --------------------------------------------------
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 522534 ***