Q: What are the known issues for Debathena?
Answer
- Some packages (Zephyr, from, mailusage, and mailquota) will not work behind a NAT device or home router. Consider using tzc in place of Zephyr. See Why doesn't Debathena work correctly behind a NAT device or home router?.
- Upgrading between Ubuntu releases may cause you to lose Debathena functionality until you re-enable it. See [archive:Why did Debathena stop working when I upgraded Ubuntu?].
- An existing local account with the same name as your Athena account may cause problems for debathena-login, debathena-login-graphical, and debathena-workstation users. A workaround is available at Why don't I get my AFS home directory when logging in to a Debathena workstation?.
- When upgrading from Ubuntu Intrepid from Jaunty, you may see a message about /etc/services that indicates that three Athena-specific lines are about to be removed. You should select “Yes” / “Install the package maintainer's version”; the Athena lines will be re-added later in the upgrade process.
- Upgrades of the libhesiod0 package may cause an OMINOUS WARNING error. See [archive:Why did I get an OMINOUS WARNING about debathena-hesiod-config during an upgrade?].
- Pine’s “bounce” feature sends messages to the original recipient instead of the specified one. See Why doesn't pine's "bounce" feature work correctly in Debathena?.
- Some legacy applications that ignore nsswitch or attempt to enumerate the passwd database will behave incorrectly and not notice Hesiod users. For example, finger without the -m option will attempt to walk the passwd file and ignore Hesiod. (This specific example has been worked around in Debathena.)
Listed below is a list of known issues: