Maybe ;)… it seems that they also report in bug #1650835 a problem of
timing but did not make mistakes typing the password the first time.
Maybe not a duplicate… but obviously it seems that the problems might be
linked
--
You received this bug notification because you are a member of Desktop
Public bug reported:
Hi,
We install ubuntu/mint to numerous people and we got multiple
reports that the wifi password was not taken into account. We managed to
reproduce it by
1 - Select your wifi network
2 - Enter a fake password (Just to simulate a user error not entering well his
wifi
*** This bug is a duplicate of bug 661272 ***
https://bugs.launchpad.net/bugs/661272
** This bug has been marked a duplicate of bug 661272
changing user password causes hang in users-admin
--
You received this bug notification because you are a member of Desktop
Packages, which is
Hi,
here a patch of src/users/run-passwd.c that allows me to do
multiples mistakes when trying to change my password.
** Patch added: "patch for src/users/run-passwd.c"
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/661272/+attachment/4619463/+files/run-passwd.c.patch
so it seems for my case that we are stuck in "case PASSWD_STATE_NEW" of
io_watch_stdout, because of an error of "Authentication token
manipulation error".
If i force the state to go to PASSWD_STATE_RETYPE by adding
else if(is_string_complete (str->str, "token", NULL)) {
On Ubuntu 16.06 (daily build 23/02/2016), the interface is not the same as in
gnome-system-tools, but one can see that
the filesrc/users/run-passwd.c present in
gnome-system-tools
was reused inpanels/user-accounts/run-passwd.c in ubuntu-control-center
with some
some infos :
Test :
fill current password
fill new password with current password
fill confirmation with current password
click ok
get the error message that new password is the same
fill new password with a new password
fill confirmation with a new password ( without error ! )
Here two case
Hi,
bug append also in Xubuntu 14.04.03.
It is a very annoying bug for people who install distros with a generic
password. Once the pc is delivered, the first thing to do is to change
the password and a lot of time the user make a "fatal" mistake…
Some informations i gathered for now :
Update to Phil Wright solution, for a more general context
1 - Create a udev rules file '/etc/udev/rules.d/61-sr-change.rules' and
add the line :
KERNEL==sr*, ACTION==change, RUN+=/usr/local/bin/sr_change.sh %n
2 - And create the script '/usr/local/bin/sr_change.sh' :
#!/bin/sh
if [ $# -eq 1
9 matches
Mail list logo
