This appears to be a side effect of trying to enforce tty_tickets properly: back in lucid for commands invoked from the menus the sudo timestamp was written under the name 'unknown'; now it does not get written at all - hence the timeout is not honored.
With tty_tickets turned off, you can be prompted for password once and then any login under that id is not prompted for @timeout@ period, including ones that may be under different controlling terminal, such as a remote ssh login. But this seems to be a better workaround, than having to type in a password every 5 minutes for running synaptic. With lucid behavior, you could actually get prompted once, and then reboot the machine and not get prompted again, if the terminal name happened to match. What we really want is for timeout to be shared in a user session - a desktop session, a screen/byobu session, etc. Of course there are nested sessions: screen running in a xterm... And related ones, such as ones on the local ttys :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692391 Title: no timestamp timeout in latest sudo except for current instance -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
