GNOME Bugzilla – Bug 502860
crash in File Browser: I downloaded and install...
Last modified: 2007-12-10 16:11:41 UTC
Version: 2.20.0 What were you doing when the application crashed? I downloaded and installed the new release OpenOffice2.3.1 (deb packages) and I have filled the form related to the survey on line. 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: Tango Memory status: size: 80855040 vsize: 80855040 resident: 27389952 share: 16310272 rss: 27389952 rss_rlim: 4294967295 CPU usage: start_time: 1197294926 rtime: 844 utime: 779 stime: 65 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 0xb6c416c0 (LWP 3827)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 181446
Thread 1 (Thread 0xb6c416c0 (LWP 3827))
----------- .xsession-errors (6 sec old) --------------------- at org.gudy.azureus2.ui.common.Main.directLaunch(Main.java:228) at org.gudy.azureus2.ui.common.Main.main(Main.java:131) shell.open took 352ms processStartupDMS took 5ms psDMS 14ms (SWT:4550): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width 250 and height -1 (SWT:4550): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width 250 and height -1 (nautilus:3827): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `VALID_ITER (iter, tree_model_sort)' failed ** ERROR **: file fm-tree-model.c: line 1527 (fm_tree_model_unref_node): assertion failed: (parent->dummy_child_ref_count > 0) 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 440988 ***