David Ranch

Hello everyone, KD6YAM and I recently noticed this issue in Linux Mint 22.1 and Ubuntu 24.04.2 as of 06/23/25. Please note that special event callsigns in different countries can get quite long plus the two digit SSID. See https://ham.stackexchange.com/questions/10339/which-country-s-hams-have-the-longest-call-signs for some ideas but the field could get quite long with say 3 char + 2 number + 4 char + 2 number SSID == 11 char total + 1 null terminator byte or 12 bytes minimum w/o any consideration...

Hello everyone, KD6YAM and I recently noticed this issue in Linux Mint 22.1 and Ubuntu 24.04.2 as of 06/23/25. Please note that special event callsigns in different countries can get quite long plus the two digit SSID. See https://ham.stackexchange.com/questions/10339/which-country-s-hams-have-the-longest-call-signs for some ideas but the field could get quite long with say 3 char + 2 number + 4 char + 2 number SSID == 11 char total + 1 null terminator byte

Good to hear you got things working though looking back in the thread, I never did see why you were starting Linpac with -m anyway. Btw, for the other mailbox error you're seeing, If you look at this other doc, see item #15: https://www.trinityos.com/HAM/CentosDigitalModes/RPi/rpi-setup.html#28c.configure-linpac I've added this missing step to the future ax25mail-utils README doc

Yes, I highly recommend to build from the develop branch which will get you the nearly complete 0.29 version. It has mostly build fixes and other things but nothing for your listen issue. If you start Linpac from the terminal and the program loads, do you see any errors? If you then exit out of Linpac with the :sys command, do you see any errors there in the terminal program? Also check the $HOME/LinPac/error.log file for any errors too.

Ok, if you look at the permissions of the axlisten tool in your last screenshot, it's already SUID root (that's what the red probably means). Specifically, it shows: -rwsr-xr-x root root Since you're a new Linux user, I'll give some explanation. This file is owned by the user "root" and also have group ownership of "root". The permission area is broken into three areas: owner, group, other. The "root" owner here can (r)ead, (w)rite, and (s)execute this program with SUID permissions. Putting that...

The "ls" commands color coding can differ from OS to OS so that doesn't show what's wrong. Try running "ls -la" to see what it means. That said, it's probably a broken symlink which is easy to fix and NOT a 32bit vs 64bit file issue. Next, if Linpac+Linux AX.25 stack is showing the axlisten output when using one sound device but not the other, your problem isn't Linpac.. it's going to be the stack setup for the "broken" sound device. Finally, per the Linpac manual: " -m : disable monitor. When this...

The included Linpac documentation is lacking on this topic but I had covered this in my other Centos documentation. The issue here is that to display decodes of all AX.25 traffic in the bottom Linpac pane, axlisten needs root access to the kernel but this is generally considered poor security practice. I personally consider this low risk but there is one solution to fix this using the "ax25spyd" solution. It's old, unmaintained, and has been quirky in the past and I haven't tested it in years. I've...

Hello Cody, I will try to reproduce this but until then, you might want to try testing this with the "develop" Git branch of Linpac as there are various fixes in there.