GNOME Bugzilla – Bug 505936
crash in Home Folder: Trying to access a file ...
Last modified: 2007-12-27 18:29:33 UTC
What were you doing when the application crashed? Trying to access a file properties. 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: dlg-etiquette Memory status: size: 98054144 vsize: 98054144 resident: 31997952 share: 14192640 rss: 31997952 rss_rlim: 4294967295 CPU usage: start_time: 1198752059 rtime: 8140 utime: 7592 stime: 548 cutime:176 cstime: 75 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 0xb6cf66b0 (LWP 4537)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 183242
Thread 1 (Thread 0xb6cf66b0 (LWP 4537))
----------- .xsession-errors (20694 sec old) --------------------- Clearing tracks cache new thread created with Bossanova Pixies cover thread started /home/wiltave/.exaile/covers/3cd0f84473d731e642e636776b9e8ad8.jpg updated plays 1, rating 1 Attempting to submit track Cecilia Ann from Bossanova by Pixies to last.fm -AUDIOSCROBBLER- i[0]=2007-12-27%2012%3A11%3A12&b[0]=Bossanova&a[0]=Pixies&s=e9382d54a14ee95ddee57a78c13b7fa7&u=wiltave&m[0]=&t[0]=Cecilia%20Ann&l[0]=126 2007-12-27 12:11:13: Uploaded 1 tracks successfully next track was reported as Rock Music from Bossanova by Pixies Aborted cover thread Playing queued track "Rock Music from Bossanova by Pixies" updated plays 1, rating 1 Attempting to submit track Rock Music from Bossanova by Pixies to last.fm -AUDIOSCROBBLER- i[0]=2007-12-27%2012%3A13%3A12&b[0]=Bossanova&a[0]=Pixies&s=e9382d54a14ee95ddee57a78c13 ...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 485526 ***