Hola Michael Banck! El 29/03/2007 a las 11:43 escribiste: > can you guys maybe try the following gamin_0.1.8-2 package, and see > whether it fixes your problems? > http://people.debian.org/~mbanck/unstable/gamin_0.1.8-2_i386.deb > http://people.debian.org/~mbanck/unstable/libgamin0_0.1.8-2_i386.deb > or "deb http://people.debian.org/~mbanck/unstable/ ./" > I pulled one patch from upstream which I thought fixed things for me > when I was able to reproduce the problem; but as 0.1.8-1 is mostly > working again for me now with thunar and pcmanfm for some reason, I am > not sure it's the right fix, but worth a try. > I'm continueing trying to reproduce this.
The patched version does not fix the problem. But continuing tests gave me more info, the previous info I've sent were based on tests made mainly in an amd64 and only confirmed with a i386 desktop, as the source of the patch is not provided I could not test the amd64, also the i386 machine had a little different behaviour I did not see before, as I was focusing on the amd64 machine. Starting thunar on a i386 does start a gam_server, but not in an amd64. (speaking of version 0.1.8, of course). In two different i386 computers I have reproduced the problem that thunar is not getting notified of the changes, neither with the -1 nor the -2 versions. In a third i386 (upgraded to sid), thunar does get the notifications. In this computer I also noticed, that, if you do the sequence: 1 - Start nautilus (it starts a gam_server), 2 - start thunar (it connects to the gam_server), 3 - close thunar. As a result the gam_server that was started by nautilus is closed. Anyway nautilus doesn't seem to be using the gam_server, so this might not be a bug after all. As a conclusion, I suspect that the problem is not in gamin itself, but in a dependancy. -- " Documentation is like sex: when it is good, it is very, very good; and when it is bad, it is better than nothing. " -- (Dick Brandon) Saludos /\/\ /\ >< `/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
