GNOME Bugzilla – Bug 485308
crash in Computer: Je cliquais.
Last modified: 2007-10-10 23:16:29 UTC
Version: 2.18.1 What were you doing when the application crashed? Je cliquais. Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18-4-xen-686 #1 SMP Mon Mar 26 21:49:04 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Dietlooks Icon Theme: Buuf Memory status: size: 73891840 vsize: 73891840 resident: 24367104 share: 15728640 rss: 24367104 rss_rlim: 4294967295 CPU usage: start_time: 1192001906 rtime: 199 utime: 173 stime: 26 cutime:0 cstime: 1 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/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226938704 (LWP 16978)] [New Thread -1261655152 (LWP 17406)] [New Thread -1327273072 (LWP 17405)] (no debugging symbols found) 0xb7f90402 in __kernel_vsyscall ()
+ Trace 169198
----------- .xsession-errors --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 Avertissement du gestionnaire de fenêtres : L'écran 1 sur le visuel « :0.0 » a déjà un gestionnaire de fenêtres Avertissement du gestionnaire de fenêtres : L'écran 1 sur le visuel « :0.0 » a déjà un gestionnaire de fenêtres ** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers)) aborting... --------------------------------------------------
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 459221 ***