Does anyone have a work-around handy, for disabling this entire "security" "feature"?
In my web searches, I find nothing about how to turn it off. What I do see, are instances of the same error message reported in numerous forums. The problem is normally misinterpreted by the local geeks and gurus in these forums, as an application level problem or (most commonly), a missing filesystem permission on an executable file. The real bug looks and sounds too much like deliberate sabotage to seem possible. I certainly don't need it, it's nothing but an annoyance to anyone who pays attention to where the files on his or her system came from. This "feature" adds nothing but extra time and motion to the simplest and most frequently used task on the desktop. I am seriously thinking about the time/effort tradeoff in switching from Gnome to KDE on account of it. Clueless newbies also don't need it, unless someone thinks it's a good idea to protect them from hypothetical hostile content by disabling the only file-open method they know about. (Insert famous quote about unplugged computer encased in a cube of concrete here.) :o/ Steve -- nautilus's clever anti-hax0r detection is really dumb https://launchpad.net/bugs/19101 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
