GNOME Bugzilla – Bug 497939
crash in File Browser: Wchodzenie we właściwośc...
Last modified: 2007-11-18 16:53:18 UTC
Version: 2.18.3 What were you doing when the application crashed? Wchodzenie we właściwości klipu, to samo w przypadku paczki deb Viewing properties of movie file, the same happens in the deb packages (sorry for my english, i am beginner). At now better is usind nautilus from Sid repo' or uprage to sid Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 76496896 vsize: 76496896 resident: 26923008 share: 15810560 rss: 26923008 rss_rlim: 4294967295 CPU usage: start_time: 1194802438 rtime: 278 utime: 266 stime: 12 cutime:0 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 0xb6d4c6b0 (LWP 4945)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 178536
Thread 1 (Thread 0xb6d4c6b0 (LWP 4945))
----------- .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 ** Message: drive = 0 ** Message: volume = 0 Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store)) aborting... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 440988 ***