Hi Ben, When checkbox starts, it tries to launch a backend process which runs as root and takes care of executing a few superuser jobs. That's why you get asked for your password. Due to some limitations of the mechanism we use to launch this process, checkbox has no way of positively confirming whether it was started, or the reason why it may have failed to start. Also, previously, gksudo had a bug where it would only ask for the password once, and if it was wrong it would just fail, thus giving the user no chance to correct a wrong password entry.
Thus the only solution we could implement was having checkbox wait ~30 seconds, try to contact the backend, and if it's not present, it tries to respawn it again (which again asks the user for the password; this is what you're seeing). If after 3 tries it's unable to start the backend, it gives up and continues without superuser privileges. This behavior is by design so it's not something we will fix in checkbox. We're looking at alternate mechanisms for running superuser jobs, we'll probably implement this in the future but for now, I apologize since the only option I can offer, if you don't want to enter your password, is to click "cancel" 3 times (a 30 second wait between tries is normal). ** Changed in: checkbox (Ubuntu) Status: New => Confirmed ** Changed in: checkbox (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157433 Title: checkbox ask for user password even after closing if not provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/1157433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs