GNOME Bugzilla – Bug 552825
crash in Home Folder: double clicked on the up...
Last modified: 2008-09-18 23:59:17 UTC
What were you doing when the application crashed? double clicked on the upper folder in the bar, which is listing the folders down to the path which is shown at the moment. example: i was just navigating /home/josi/foo/bar and then clicked on /home/josi/foo in bar. happened the first time Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Thu Aug 28 12:00:54 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 119865344 vsize: 119865344 resident: 58675200 share: 17469440 rss: 58675200 rss_rlim: 4294967295 CPU usage: start_time: 1221750948 rtime: 11228 utime: 10673 stime: 555 cutime:772 cstime: 42 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb6a82710 (LWP 3818)] [New Thread 0xb10bcb90 (LWP 13202)] 0xb7eea424 in __kernel_vsyscall ()
+ Trace 206955
Thread 1 (Thread 0xb6a82710 (LWP 3818))
----------- .xsession-errors (8 sec old) --------------------- OggS-SEEK: at 704 want 47096 got 23104 (diff-requested 46392) OggS-SEEK: at 47040 want 1032 got 0 (diff-requested -46008) ICE default IO error handler doing an exit(), pid = 13391, errno = 11 ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** ** ERROR:(fm-tree-model.c:1531):fm_tree_model_unref_node: assertion failed: (node->ref_count > 0) --------------------------------------------------
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 512040 ***