Is TELNET broken in Fedora 43 KDE?

Ask Fedora
1

I upgraded my Fedora systems from FW 42 KDE to FW 43 KDE. TELNET appears to be messed up in FW 43. When I log in, I get this:

Kernel 6.17.7-300.fc43.x86_64 on x86_64 (0)
powerbxx login: tim
Password:
3008;start=9043ca18-a053-4692-bae4-e5cb389d9aad;user=tim;hostname=powerbxx;machineid=f5cbe162a1b44eb9afac17468e09588e;bootid=9d88c74c-d056-4ceb-b461-d29a6037d076;pid=8567;type=shell;cwd=/home/tim/home/tim>

This causes the telnet client on my windows machine to wait forever. It still works fine on FW 42 KDE. Any suggestions?

2

See:

The post I’ve linked to suggests a workaround by editing a systemd config file.

3

Another “workaround” might be using SSH. It’s 2025, let’s give poor old Telnet a rest. :wink:

2 Likes
4

Thank You P G pg-tips, I’ll give it a try.

5

Lars l-c-g, I regularly use XRDP to access the machines; I use NETTERM for quick changes or updates. Yes TELNET is old, but still installs and runs (quicker that XRDP or SSH). There are times when it is necessary to use the built-in ZMODEM file transfer. All the machines running Fedora Workstation also support SAMBA. When I need to hit, command, and quit it is a perfect case for TELNET. The TELNET Server on the box is somehow broken.

6

SUPPLEMENTAL: The problem encountered has nothing to do with TELNET server on FEDORA. Both NETTERM (v 5.6.2.0) and the native TELNET client on Windows 10 have this problem. Using the TELNET client on FEDORA (FW 42 and FW 4.3) work just fine.