This has in fact been fixed as I indicated with the above-mentioned nautilus
update.
On 9/19/06, Sebastien Bacher [EMAIL PROTECTED] wrote:
do you still have that issue? could you try to strace -p $(pidof
nautilus) and note what it's doing when that happens? What the
backtrace get with thread
Le mardi 19 septembre 2006 à 20:03 +, saads a écrit :
I apologise. I replied earlier when it was fixed via email and it
apparently did not appear here on launchpad. I sent a reply dated
September 4th with the following:
It appears as though this has been fixed with the latest update to
Here it is:
Thread 1 (Thread -1225976144 (LWP 30638)):
#0 0xe410 in __kernel_vsyscall ()
#1 0xb749ee86 in *__GI_time () from /lib/tls/i686/cmov/libc.so.6
#2 0xb790f7ef in actually_dispatch_callback (data=0x87c3878) at
gnome-vfs-monitor.c:235
#3 0xb7695b11 in g_source_is_destroyed () from
