Thunar assert failure: thunar-vfs:ERROR:thunar-vfs-path.c:1201:_thunar_vfs_path_shutdown: assertion failed: (home_components[n]->ref_count == 1)

[valerio]

Binary package hint: thunar

Started Thunar from GNOME terminal as normal user, then used it without issues.
I closed the window, and in the terminal the process was still running, with this output:

**
thunar-vfs:ERROR:thunar-vfs-path.c:1201:_thunar_vfs_path_shutdown: assertion failed: (home_components[n]->ref_count == 1)

**

ProblemType: Crash
Architecture: amd64
AssertionMessage: thunar-vfs:ERROR:thunar-vfs-path.c:1201:_thunar_vfs_path_shutdown: assertion failed: (home_components[n]->ref_count == 1)
CrashCounter: 1
Date: Sat Sep 12 00:56:22 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/Thunar
NonfreeKernelModules: nvidia
Package: thunar 1.0.1-1ubuntu1
ProcCmdline: thunar
ProcEnviron:
 SHELL=/bin/bash
 LANG=it_IT.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
Signal: 6
SourcePackage: thunar
Stacktrace:
 #0 0x00007f37a83b44b5 in raise () from /lib/libc.so.6
 No symbol table info available.
 Cannot access memory at address 0x7fffc9542f58
StacktraceTop: raise () from /lib/libc.so.6
Title: Thunar assert failure: thunar-vfs:ERROR:thunar-vfs-path.c:1201:_thunar_vfs_path_shutdown: assertion failed: (home_components[n]->ref_count == 1)
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin audio cdrom dialout fuse lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:*__GI_raise (sig=<value optimized out>)

[Charlie Kravetz (cjkgeek)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 444163, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

My mistake in marking it confirmed when I really wanted to mark it a duplicate.