And here is an example of what happens to the underlying system when one sector of the dev community does not listen to or consider the needs of others when changing or removing legacy(their words not mine) functionality. In customising and stripping away "unnecessary" stuff Ubuntu has determined the way it will be in all linux (at least all who use gnome or kde, or udev/udisk) in the example below. They have removed features that are not considered useful to Ubuntu without considering the many outside Ubuntu consquently affecting the many who have customised it to suit their own cases (supposedly one of the key benefits of OSS) and now have had their systems broken by this update. He sums it up nicely (and without bitterness) at end of his message: "I guess the people who care about this type of correctness are using BSD or Arch and have less say or gentoo and can just recompile" It doesn't come down to knowledge or experience anymore, it is numbers that call the shots in that dev world. It is no wonder there are so many fundamental problems, they are chasing their tails just like MS and Apple do :) Ubuntu has definitely fallen into that trap, just hope it doesn't take linux with it :D On 04/12/11 05:44, Kevin Chadwick wrote: > On Sat, 03 Dec 2011 12:03:37 +0800 > pomhg wrote: > >> Hi,I've got same problem here. I'm using xfce with udiskie and rox instead >> of thunar for automounting. >> With 'rox copy' or 'cp', it just immediately ended. From iotop I can see >> that 'flush' is still active. >> So my solution is writing a shell script for rox custom menu, in which I >> put 'sync && udiskie-umount "$@"'. >> I hope there is a better way to solve this. >> >> I tried the solution mentioned by Timothy Redaelli about the udev rules, >> but didn't help. > > Forgot the link sorry. > > "https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/880965" > > I opened a bug a few weeks ago about not being able to change the > default options that udev/udisks has introduced. In my case it was > showexec to noexec. > > You can track that bug here, but I'm not too hopeful of it's acceptance > due to "pushback" especially without someone finding the time and > providing diffs to make those changes. I'm surprised when migrating from > older automounters that this functionality was allowed to slip away. I > would have thought it would be part of the specification and > testing/requirements to replace. > > I guess the people who care about this type of correctness are using > BSD or Arch and have less say or gentoo and can just recompile. > > Kc >