Please don't bother installing Jaunty - if that's failing in Karmic,
that's enough for me. So to sum up, it seems that both PolicyKit and
gksu authentications fail. Does a simple "sudo echo test" works? I guess
not, but I'd like to be sure. A log that you could also post here is
/var/log/auth.log (
On Thu, 03 Dec 2009 21:15:54 -
Milan Bouchet-Valat wrote:
> Yeah, that's bug 484559. But does changing your password from the
> console using 'passwd' bring the same bug as the present report
> describes? If that's the case, that's a bug in PAM or sudo, and we
> should move it if we want it t
Yeah, that's bug 484559. But does changing your password from the
console using 'passwd' bring the same bug as the present report
describes? If that's the case, that's a bug in PAM or sudo, and we
should move it if we want it to be fixed some day.
--
Changing your password does not take effect be
On Thu, 03 Dec 2009 13:20:51 -
Milan Bouchet-Valat wrote:
> Do you have any idea of were this problem comes from? Are you able to
> reproduce it in Karmic? I'm not able to reproduce the problem here, so
> I'd need somebody to answer these questions. In particular, whether this
> also happens
Do you have any idea of were this problem comes from? Are you able to
reproduce it in Karmic? I'm not able to reproduce the problem here, so
I'd need somebody to answer these questions. In particular, whether this
also happens when changing password using 'passwd', rather than using
users-admin. El
On Thu, 03 Dec 2009 10:22:33 -
Milan Bouchet-Valat wrote:
> So thanks for providing the details now. This bug was not Triaged, it
> was merely Confirmed. Sure, you had in mind the details, but nobody else
> did. So, what was not mentioned in the report or the comments is:
> changing your pass
So thanks for providing the details now. This bug was not Triaged, it
was merely Confirmed. Sure, you had in mind the details, but nobody else
did. So, what was not mentioned in the report or the comments is:
changing your password does not allow you to authenticate via sudo.
You're really not hel
Details to reproduce it were to install Xubuntu 8.10, go to Add Users,
change your password, exit Add Users. At that point, you can not use
sudo for anything because you must log out and log back in. As I already
said, this bug was reported against Xubuntu, triaged against Xubuntu,
you changed thin
Thanks for attempting to reproduce the problem, Milan. When you tried
that, were you using Jaunty or Karmic? The dup I submitted (418337) was
for Jaunty.
Also, did you try to reproduce the symptom I reported in that bug, which
was different from the one reported here?
--
Changing your password
Charlie Kravetz: You said you were able to reproduce the bug. Could you
give me details on that? I can keep it open indefinitely, but that won't
help, while cluttering my TODO list. I don't think your policy is to
keep reports open disregarding the fact that we can't reproduce them.
There have been
Xubuntu has a policy of not closing a bug report simply to get rid of
it. This was triaged in January 2009. There is no need for further
follow-ups unless it becomes fixed. Lack of feedback is not a valid
reason to close a triaged bug. Please insure the fix is valid before
closing.
** Changed in:
wierdlmate: You're not the original reporter, are you? The problem you
describe seems to be linked with bug 490093. Please comment on that bug,
not here - are you able to change your password from the console using
'passwd'?
Closing this report by lack of feedback since august. Please reopen if
yo
No, what I see is this (maybe different bug): I open users-admin, I
unlock, select the current user, and click on properties. When I try to
change the password---so I enter the new password and press "Change
password", the tool just waits indefinitely. I cannot say it hangs,
because I can click o
If I understand correctly the problem, you can only hit that bug when
trying to get admin rights without having restarted your session. Is
that the case? If so, I'm not able to reproduce that. Anyway, I'd see
that more as a PAM/PolicyKit issue. Warning users is a mere workaround,
since changes shou
14 matches
Mail list logo