Activity log for bug #43233
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2006-05-06 14:28:47 | kko | bug | added bug | ||
| 2006-05-06 18:42:04 | Dennis Kaarsemaker | sudo: status | Unconfirmed | Confirmed | |
| 2006-05-06 18:42:04 | Dennis Kaarsemaker | sudo: severity | Normal | Wishlist | |
| 2006-05-08 07:41:00 | kko | title | "sudo -k" fails when timestamp is in the future, "sudo" too | "sudo -k" fails when timestamp is in the future | |
| 2007-02-15 09:27:29 | Martin Pitt | sudo: status | Confirmed | Needs Info | |
| 2007-02-15 09:27:29 | Martin Pitt | sudo: statusexplanation | I still need a *detailled* recipe how to reproduce this -- I tried various combinations for half an hour without success. | ||
| 2007-02-15 10:32:25 | kko | bug | added attachment 'sudoers' (I changed the file ownership to be able to submit it.) | ||
| 2007-02-19 16:43:27 | Martin Pitt | sudo: status | Needs Info | Confirmed | |
| 2007-02-19 16:43:27 | Martin Pitt | sudo: importance | Wishlist | Medium | |
| 2007-02-19 16:43:27 | Martin Pitt | sudo: statusexplanation | I still need a *detailled* recipe how to reproduce this -- I tried various combinations for half an hour without success. | Indeed, using kko's recipe I could *sometimes* reproduce it on Dapper, and not at all on Feisty. But since Feisty does not have any changes wrt. ticket handling compared to dapper and because I cannot reliably reproduce it in Dapper either I guess it still affects Feisty in some way. However, I could log into a different console/pty without any problem in every case, so it never locked me out completely. Did that happen to anyone? | |
| 2007-11-01 21:49:21 | Martin Pitt | sudo: assignee | pitti | ||
| 2007-11-14 13:30:09 | Martin Pitt | sudo: status | Confirmed | Fix Released | |
| 2009-06-28 10:40:21 | Launchpad Janitor | branch linked | lp:ubuntu/karmic/sudo |
