[Bug 21404] Re: Show updates with no password fails

2011-01-14 Thread Robbie Williamson
** Changed in: gksu (Ubuntu) Assignee: Michael Vogt (mvo) => (unassigned) ** Changed in: gksu (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/21404 Ti

[Bug 21404] Re: Show updates with no password fails

2010-06-29 Thread Martin Pool
Within gksu itself, you now get a message on stderr if the wrong password is entered, but that typically won't be visible when it's started by some other program. So this bug could be considered fixed in update-manager, but arguably still open in gksu, depending on whether it's considered to be gk

Re: [Bug 21404] Re: Show updates with no password fails

2010-06-29 Thread Martin Pool
This seems to be fixed in current Maverick, where it's apparently using polkit rather than gksudo(?) You get "authentication failed" in the password dialog and can either try again or cancel. -- Show updates with no password fails https://bugs.launchpad.net/bugs/21404 You received this bug notif

[Bug 21404] Re: Show updates with no password fails

2010-06-29 Thread Martin Brook
The issue reported in #5 is occurring for me in 10.04. -- Show updates with no password fails https://bugs.launchpad.net/bugs/21404 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 21404] Re: Show updates with no password fails

2009-11-19 Thread Martin Pool
I can still reproduce the behaviour of comment #5 in karmic. -- Show updates with no password fails https://bugs.launchpad.net/bugs/21404 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubunt

[Bug 21404] Re: Show updates with no password fails

2009-11-19 Thread faultygearbox
Martin, is this still a problem for you? It seems to work (now). -- Show updates with no password fails https://bugs.launchpad.net/bugs/21404 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.

[Bug 21404] Re: Show updates with no password fails

2009-06-10 Thread Martin Pool
I get similar behaviour when mistyping my password to install updates. -- Show updates with no password fails https://bugs.launchpad.net/bugs/21404 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@l

[Bug 21404] Re: Show updates with no password fails

2009-06-10 Thread Martin Pool
This seems to be still broken for me in Karmic: 0. Run 'sudo -k' 1. Start update-manager 2. Click 'check' 3. Dialog asking for my password 4. Enter something that's not my password, press enter 5. Update-manager displays a little progress dialog while reloading the package list There's no error

[Bug 21404] Re: Show updates with no password fails

2009-06-09 Thread Michael Vogt
This particular problem is now fixed in ubuntu. update-manager runs as the normal user (just the backend runs as root) and when gksu gets a wrong passowrd it will display that in the UI and offer a second attempt. @Martin: its true that it does not show a error anymore if a empty passowrd is give

[Bug 21404] Re: Show updates with no password fails

2008-09-25 Thread Martin Pool
In Intrepid, if you enter the wrong password, there's no error message at all. -- Show updates with no password fails https://bugs.launchpad.net/bugs/21404 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubunt

[Bug 21404] Re: Show updates with no password fails

2007-06-07 Thread Marco Rodrigues
Still present on Feisty... ** Changed in: gksu (Ubuntu) Status: Unconfirmed => Confirmed -- Show updates with no password fails https://bugs.launchpad.net/bugs/21404 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs