GNOME Bugzilla – Bug 495450
crash in Open Folder: I tried to view the prop...
Last modified: 2007-11-11 16:49:57 UTC
Version: 2.18.3 What were you doing when the application crashed? I tried to view the properties of a *.wmv file located on my desktop. fc7, thinkpad X61tablet, usual gnome install + livna for vlc and a few other things. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 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: 89198592 vsize: 89198592 resident: 23867392 share: 17133568 rss: 23867392 rss_rlim: 4294967295 CPU usage: start_time: 1194650846 rtime: 68 utime: 61 stime: 7 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208580384 (LWP 3036)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 176684
Thread 1 (Thread -1208580384 (LWP 3036))
----------- .xsession-errors --------------------- localuser:rodney being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2916 Initializing nautilus-search-tool extension Initializing nautilus-open-terminal extension ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: livna. Please verify its path and try again ** Message: <info> You are now connected to the wireless network 'smeghead'. Gtk-ERROR **: file 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 been fixed already. Please update. *** This bug has been marked as a duplicate of 440988 ***