File copy/cut/paste interactions & insufficient privileges

It would be very nice to give the user an opportunity to enter his/her password at this point.

Adding an emblem on folders you don't have sufficient permission to alter files and having a notification bar (like the firefox "remember password" bar) when browsing inside those folders would warn the user before he/she tries to make such an action, saving the user time.

Even better, there could be a button on the notification bar allowing the user to authorize himself (using policykit?) to make such actions.

Even if this isn't a paper cut, it would be a great feature to have.

David Siegel wrote: "It would be very nice to give the user an opportunity to enter his/her password at this point."

This would be the greatest thing ever. I often have trouble with missing privileges using samba or a removable device etc.
I made a mocup, how it could look like!

This bug seems to be a subset of issues discussed in Bug #12154

In my opinion there are two good ways to fix this annoying bug:
1) Use Policykit to ask for the users password when he tries to perfom an action like creating a new folder, deleting a file, renaming a file or drag and drop a file or directory into a directory he doesn't have any previleges;
2) Use the solution of jango. I have to say I really like that mock up. The moment the user opens this directory he sees he doesn't have enough previleges, he can click the button, enter his password and he can do what he wants to do. Very good mock up, jango.

To make it clear:
I thought, that the "no privileges"-bar only appears, if someone tries to paste something in there, or tries to make any changes.
Otherwise it would be too persisting - there a lot of system-folders, where you have no privileges.
And we do not want to destroy something with our action, so the user should not see the button the whole time - this is too alluring to click on it.

This would be excellent to fix, but does not appear trivial enough to fix to be considered a paper cut.

What a shame... this bug used to plague me all the time. In order to get around this gui bug it requires a lot of knowledge for a typical user to learn. The three most obivous assumptions of knowledge is that the user will:

1). Learn that Nautilus is the default file-browser in Ubuntu (as it's not clearly indicated much of anywhere except the "Help-> About" section)
2). Know how to use the CLI.
3). Learn that you can give nautilus root privileges by calling it with "sudo" in front on the CLI.

I remember this error always providing a brick wall for me when I was first learning Ubuntu. I hope it does eventually get onto someone's to-do list for a fix.