Only sudo ajaxterm rather than default /etc/init.d allows logins
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ajaxterm (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ajaxterm
First things first, the full title of this bug is:
ajaxterm 0.9-2 only allows logins if invoked by "sudo ajaxterm" (root) rather than through "[sudo] /etc/init.
However, launchpad.net kept getting internal server errors and/or timing out on trying to submit this one for days with all sorts of browsers (Firefox 2.0.0.3 through Konqueror all the way back to lynx and w3m) until I realised it has an issue with summaries longer than a few words - latest OOPS-502A512 for those with an account on the launchpad-users mailing list... (if the server can't handle this an input http://
But back the bug (found using Ubuntu 7.04 "Feisty Fawn"):
The default installation of ajaxterm starts it via "/etc/init.
While "Login: " may look promising, for a functional ajaxterm on a given machine (assuming "penguin" for the purposes of this report) the real login prompt actually permitting a user to authenticate would be "penguin login: " rather than the former.
When issuing "/etc/init.
This might be an issue with Ubuntu's notorious aversion to "root" (or even patches to avoid this user), or simply any other distribution-
Changed in ajaxterm: | |
status: | New → Invalid |
Moreover, in spite of a manual "unset LANG" (as recommended specifically for Ubuntu) prior to invocation of "sudo ajaxterm", important keys/characters such as @ and \ are not working e.g. from Windows Internet Explorer clients, and accented letters (e.g. with diacritics like German "Umlaute") are missing from the output displayed by the ajaxterm (which would not work anyway for the reason in the previous post) as installed by Ubuntu's package manager.