If the username contains control chars , for example from backspacing to correct an error during originally entering the password , r9 displays the password in its normal form as a prompt but stores an empty string in /etc/ppp/pap-secrets Connection then is then bound to fail. This is doubly confusing since each time adls-setup will show the correct username to the user and the previously stored username with cntl-chars will work as a log-on. Reproducible: Always Steps to Reproduce: 1. user adsl-setup from r7 to enter a username and backspace to retype one or more chars. 2. connect to confirm it works 3. emerge rp-pppoe (r9 is current the ONLY version in portage despite being buggy) 4. adls-setup ; accept username as it is shown - it reads correctly - finish up 5. cat /etc/ppp/pap-secrets Actual Results: adsl-connect fails. Nothing in log files to indicate invalid username or auth failure. No simple way to revert to previous version of rp-pppoe that DID work since all else has been pulled out of portage. Expected Results: adsl-connect that works without hours of debugging effort rp-pppoe that stores the same thing as it displays as a prompt Upgrades that are compatible with earlier versions. Please do not pull all earlier versions of packages until a replacement has been fully tested by the userbase. There should always be some fall-back when an issue comes up. This is a recurrent problem since begining of 2005. Gentoo is becoming evermore demanding in maintainance effort.
indeed, there is a problem regarding password saving, but it has nothing to do with what you described. the problem is that adsl-setup edit chap-secrets with typed username and password. workaround: re-enter username every time you run adsl-setup
Indeed you are right, I've just checked. So rp-pppoe is going to break everyone's connect after the first use. So if it is as fundementally broken as that why is r9 not hard masked? This cost me a lot of time and about 3days without a working connection. Less experienced users will be completely lost. This is supposed to be the current "stable " version isn't it?
because main functionality isn't broken and most users don't use adsl-setup anyway. what would you do if I'd mask the rp-pppoe? I will fix it in r10, but I am waiting input in other 2 bugs related to rp-pppoe. please don't change status of this bug
Well a util to help set up an adsl connection that causes a working connection to no longer connect . You dont get much more broken than that. There's no indication this is a once only tool . So major functionality not only fails to work but actually does dammage to a working system. >>most users don't use adsl-setup Those that do probably can't connect anymore , so that conclusion may be ill-founded. I would have thought the severity of this bug would warrent and immediate fix -it would not seem to be a big issue technically. This is the ONLY version still in portage. It is broken and not fully tested. I had a working setup with r7 (apparently r2 worked as well). The r7 ebuild was pulled without a working replacement. If r10 is not available earlier versions should be put back in the tree a.s.a.p to prevent more systems going off line due this careless bug. This is exactly the type of situation that makes Gentoo unreliable and a headache to maintain. The lack of will to rectify only adds to the level and extent of user frustrations. Sorry to sound off, but I have wasted far too much time with kind of problem on Gentoo. It is completely unnecessary.
fixed in r10.
Thanks for the fix in r10. I see you've marked it as fixed. Does that mean you have released r10? Is that scheduled for immediate release or is it necessary to open a bug against portage that currently only has one , broken copy of this package?
synchronize your portage tree by issuing "emerge --sync"
I'll take that as " affirmative captain" ;) I did that just proir to posting but it obviously had not propagated to the mirror I got. I'll re-sync if it's not too early. Thanks for the speedy response on this , hopefully it will avoid others falling into the same trap I did. Cheers.
