After a new installation of 11.2, I found I could not use YAST (or SAX2) as
the root password would not be accepted. I tried the same password in a
terminal window and “su” was happy with it. I can also log on as Root with
the password. Both user sessions on this system are similarly affected.
I’ve made other installations of 11.2 and not had this problem before so the
glitch seems unrelated to 11.2 - just one of those things. How can I fix it?
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
It’s a kernel bug. Kernel 2.6.31 is in the Factory repos now. Bug is already being worked on.
Weird thing is: if I persist in clicking OK, I do get the root access…
I didn’t put it there because I didn’t think it was 11.2-related as I’d
already made several installs without this problem showing up. I assumed it
was just the luck of the draw - one of these daft things that happen from
time to time. It seemed to me that the problem was likely to have shown up
before with other releases and the cure, assuming there was one, would be
similarly general.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
>
> It’s a kernel bug. Kernel 2.6.31 is in the Factory repos now. Bug is
> already being worked on.
> Weird thing is: if I persist in clicking OK, I do get the root
> access…
>
>
Odd. I was sure this problem showed up from the start, i.e. before I updated
the kernel. I might try a few more experiments.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
> sorry, it was not my intention to say you had done wrong, rather it
> was a HINT to a moderator to move it…so other testers have the
> benefit…
>
No problem. I’ve done an update on another machine and found the same
problem, so Knuroht was correct in saying it was a kernel bug - I’d made a
mistake in recognising when the problem had happened during installation.
So, yes, I now agree that the thread would be better located in “prerelease-
beta”. Of course, if all the correspondence had occurred on NNTP, all the
relevant info would probably be in one posting and I could do it myself.
Sorry, couldn’t resist jumping onto the nearest soapbox.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
>
> It’s a kernel bug. Kernel 2.6.31 is in the Factory repos now. Bug is
> already being worked on.
> Weird thing is: if I persist in clicking OK, I do get the root
> access…
>
Latest update has fixed the problem.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
Not SOLVED !! First time after reboot it looks OK, weird behaviour stays. I just keep clicking OK, until ‘it lets me in’. Kdesu states it cannot contact su…
>
> Not SOLVED !! First time after reboot it looks OK, weird behaviour
> stays. I just keep clicking OK, until ‘it lets me in’. Kdesu states it
> cannot contact su…
>
>
Apologies, you are right, it’s not fully functional. However, it is a lot
better - for me at least.
I had tried my normal userid on two machines and the password was accepted
by YAST first time. However, on seeing your posting, I tried another user
and got a failure but it worked the second time. On another machine I tried
two more users - one a brand new one - and had no failures on either.
Before the update, on both machines, I’d repeated typing the password in 3
or 4 times without any success.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
> Knurpht wrote:
>
>>
>> Not SOLVED !! First time after reboot it looks OK, weird behaviour
>> stays. I just keep clicking OK, until ‘it lets me in’. Kdesu states it
>> cannot contact su…
>>
>>
>
> Apologies, you are right, it’s not fully functional. However, it is a lot
> better - for me at least.
>
> I had tried my normal userid on two machines and the password was accepted
> by YAST first time. However, on seeing your posting, I tried another user
> and got a failure but it worked the second time. On another machine I
> tried two more users - one a brand new one - and had no failures on
> either.
>
> Before the update, on both machines, I’d repeated typing the password in 3
> or 4 times without any success.
>
Serves me right for showing off! Now it won’t accept the password however
many times I try.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
