Apologies ahead of time for the length of this due to inclusion of troubleshooting details. Also, I did not yet go back and try this with earlier versions however this is what I see using QtSM .71 and QtT .73 on linux x86 both 32 and 64bit.
On system "A" (WA3WLH-6) start a fresh instance of QtSM configured for AX25 300B listening on AGW port 8001. Then start a fresh instance of QtT with Listen enabled on default port 8015, AGW Setup configured with both interface and monitor enabled, with Ports (between Interval and Message in the setup dialogue) set to 1, and "TNC Setup" as host 127.0.0.1 port 8001. System "A" is now idle and listening and has not yet had any incoming connects nor has it initiated any outbound connects.
On system "B" (WA3WLH-7) issue an AX25 connect to system "A". The system B monitor shows:
?1:Fm WA3WLH-7 To WA3WLH-6 <SABM P=1 >[10:42:35]
?1:Fm WA3WLH-6 To WA3WLH-7 <UA F=1 >[10:42:37]
The system A monitor shows:
?1:Fm WA3WLH-7 To WA3WLH-6 <SABM P>[15:42:35]
?1:Fm WA3WLH-6 To WA3WLH-7 <UA F >[15:42:36]
So it looks like a good connect at both ends and B indicates connected with A... but system A does not indicate an incoming connect from B. In addition the QtT menu bar on A still shows the Connect button as available and the Disconnect button remains greyed out...
Next on system B sending keyboard text "test" shows the following in the system B monitor:
?1:Fm WA3WLH-7 To WA3WLH-6 <I S0 R0 pid=F0 Len=5 P=0 >[10:56:31]
test
?1:Fm WA3WLH-6 To WA3WLH-7 <RR R1 F=0 >[10:56:33]
And system A monitor shows:
?1:Fm WA3WLH-7 To WA3WLH-6 <I R0 S0 pid=F0 Len=5 >[15:56:31]
test
?1:Fm WA3WLH-6 To WA3WLH-7 <RR R1>[15:56:32]
The text "test" appears in the system A monitor so they both hear and ACK each other yet the "Listen" function still has not yet been activated on system A. Any attempt at this point to send any keyboard input from system A to system B will crash QtT on A with a segfault. I included the backtrace further down in this post so I can first provide what seems like a key behavior / clue.
If as above both QtSM and QtT on system A are started fresh but instead of waiting for inbound connects from B an outbound connect is issued from A to B then QtT works fine. More importantly after termination of that session all inbound connects from B to A now trigger the listen function and A shows the expected:
Incoming AGW Connection from WA3WLH-7
I should mention that this QtT was compiled from source on a 32bit Bookworm system and that no custom mods have been applied so hopefully offsets in the backtrace will align with or be close with those from the binary available for download.
I should also mention that the above behavior is identical if DW is used instead of QtSM so this seems to be a QtT issue.
Anyone else seeing this behavior?
73 de Rich WA3WLH
Here is the backtrace from the QtT segfault:
Thread 1 "QtTermTCP" received signal SIGSEGV, Segmentation fault.
0xb67cc366 in QIODevice::write(char const*, long long) ()
?? from /lib/i386-linux-gnu/sse2/libQt5Core.so.5
(gdb) bt
#0? 0xb67cc366 in QIODevice::write(char const*, long long) ()
??? at /lib/i386-linux-gnu/sse2/libQt5Core.so.5
#1? 0x080966e7 in Send_AGW_D_Frame(TAGWPort_t*, unsigned char*, int) ()
#2? 0x0809729e in AGW_AX25_data_in(void*, unsigned char*, int) ()
#3? 0x08074b16 in QtTermTCP::LreturnPressed(Ui_ListenSession*) ()
#4? 0x080752ca in QtTermTCP::eventFilter(QObject*, QEvent*) ()
#5? 0xb68a72b5 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5
#6? 0xb78f23e5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
??? at /lib/i386-linux-gnu/libQt5Widgets.so.5
#7? 0xb78fa7b2 in QApplication::notify(QObject*, QEvent*) ()
??? at /lib/i386-linux-gnu/libQt5Widgets.so.5
#8? 0xb68a758a in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
??? at /lib/i386-linux-gnu/sse2/libQt5Core.so.5
#9? 0xb68a760f in QCoreApplication::forwardEvent(QObject*, QEvent*, QEvent*) ()
??? at /lib/i386-linux-gnu/sse2/libQt5Core.so.5
#10 0xb7954e9a in? () at /lib/i386-linux-gnu/libQt5Widgets.so.5
#11 0xb79598b6 in? () at /lib/i386-linux-gnu/libQt5Widgets.so.5
#12 0xb78f23f6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
??? at /lib/i386-linux-gnu/libQt5Widgets.so.5
#13 0xb78fa064 in QApplication::notify(QObject*, QEvent*) ()
??? at /lib/i386-linux-gnu/libQt5Widgets.so.5
#14 0xb68a758a in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
??? at /lib/i386-linux-gnu/sse2/libQt5Core.so.5
#15 0xb68a7828 in QCoreApplication::sendSpontaneousEvent(QObject*, QEvent*) ()
??? at /lib/i386-linux-gnu/sse2/libQt5Core.so.5
#16 0xb6efc1f9 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /lib/i386-linux-gnu/sse2/libQt5Gui.so.5
#17 0xb6f02669 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib/i386-linux-gnu/sse2/libQt5Gui.so.5
#18 0xb6ecfd04 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/i386-linux-gnu/sse2/libQt5Gui.so.5
#19 0xb2c8971b in? () at /lib/i386-linux-gnu/libQt5XcbQpa.so.5
#20 0xb58fb5ba in g_main_context_dispatch () at /lib/i386-linux-gnu/libglib-2.0.so.0
#21 0xb58fb879 in? () at /lib/i386-linux-gnu/libglib-2.0.so.0
#22 0xb58fb924 in g_main_context_iteration () at /lib/i386-linux-gnu/libglib-2.0.so.0
#23 0xb6905cf5 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/i386-linux-gnu/sse2/libQt5Core.so.5
#24 0xb2c89ba1 in? () at /lib/i386-linux-gnu/libQt5XcbQpa.so.5
#25 0xb68a5c97 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
??? at /lib/i386-linux-gnu/sse2/libQt5Core.so.5
#26 0xb68aea00 in QCoreApplication::exec() ()
??? at /lib/i386-linux-gnu/sse2/libQt5Core.so.5
#27 0xb6ef39a1 in QGuiApplication::exec() ()
??? at /lib/i386-linux-gnu/sse2/libQt5Gui.so.5
#28 0xb78f2364 in QApplication::exec() () at /lib/i386-linux-gnu/libQt5Widgets.so.5
#29 0x0805af34 in main ()
