top of page

Bug reports

Public·20 members

V13.0.1 will not run on my Debian V13.1 installation

My Linux system runs Debian V.13.1 with XFCE The Wine version is the current STABLE version: wine-10.0 I initially tried copying the necessary VarAC files from the ZIP installation to the standard VarAC directory - but that would not run. Then I performed a full fresh installation from the Installation EXE file to a new sub-directory. When starting VarAC with Wine, it starts and successfully completes the personal configuration screen, but when it restarts VarAC to implement the newly configured INI VarAC bombs out and ends. Below is the VarAC LOG file, which seems to point to some SQL related issue.... Hopefully it will make more sense you you? As can be seen from the log file this is a totally fresh install.... 05/11/2025 08:32:45 - Starting VarAC (V13.0.1)

05/11/2025 08:32:45 - OS: Microsoft Windows NT 6.1.7601 Service Pack 1

05/11/2025 08:32:45 - OS: Microsoft Windows NT 6.1.7601 Service Pack 1

05/11/2025 08:32:46 - Debug mode…


120 Views

Hi,

I'm using Linux Mint 22.2 Cinnamon, and VARA and VarAC work almost as expected.


Since I'm not a Debian user or a Wine expert, I'm not sure how much I can help, but it might be related to the Wine-Mono version bundled with your Debian system.

I once heard that SQLite had a compatibility issue with some Wine-Mono 7.x (or earlier) builds.


You might want to start by checking which Mono version you have.

You can do this by running:


$ wine uninstaller


Mine shows:

Wine Mono Runtime 9.4.0

Wine Mono Windows Support 9.4.0


If yours is older, you can install a newer version with:

$ winetricks -q wine-mono9.4.0


By the way, from your log there seems to be another issue — the VARA modem doesn’t launch.

I imagine that’s because its directory hasn’t been set yet in your VarAC settings.

Once VarAC opens correctly, you can specify the modem path there, which should resolve that problem.

I hope this helps.

Gene / JI1BQW

Happening with V12 and V13

We have a 20 station VarAC FM network in Nassau County Florida. We use one station (W4NAS) as a relay (VIA) to Beacon, Broadcast and Chat to the West end of the county. Every time W4NAS is used as a relay station, VarAC on site at W4NAS issues a n INCOMMING CONNECTION REQUEST...don't know who that is message. It only happens on relays and we have that message switched off at W4NAS. With 12 stations beaconing 24/7, it gets kind of chatty!


Just changed VARA FM digipeater on W4NAS from W4NAS to WNAS-1. Same problem.


W4NAS is manned part of the time (Nassau Emergency Operations) and full time during an emergency and the message is annoying. If we shut off the speakers, an operator can miss important items when looking at something else.


Bug?

N9HEL

112 Views
irad d
irad d
yesterday

THere is a problem with VARA modem sending indications that has double meanings and VarAC is not always able to determin in 100% what is the right meaning. I am working on this with the VARA author. Meanwhile you can disable this message completly by editing this parameter in the VarAC ini file:


IncomingConnectionRequestAlert=ON --> OFF


Lost Ability to Connect and Send Email 13.0.1

After upgrading, I lost the ability for gateway to send email. Pressing "Send Test Email" results in "Failed" response and the following message in the log:

"The server's SSL certificate could not be validated for the following reasons:

• The server certificate has the following errors:

• The revocation function was unable to check revocation for the certificate."


The "IMAP Test" returns a "Success" message.


Testing has involved:


129 Views
irad d
irad d
Oct 30

Well documented issue. When you upgrade to V13.0.1 an AV or similar protection mechanism rule is blocking the new VarAC executable.


From this:https://www.varac-hamradio.com/post/configuring-varac-email-gateway-using-a-gmail-account


It can affect IMAP and SMTP:


Symptom: The IMAP (incoming email) test fails even though your settings appear to be correct. And sometimes also getting error like "The server certificate has the following errors: The revocation function was unable to check revocation for the certificate".


  • Possible Cause: An antivirus program may be scanning and blocking incoming IMAP connections.

  • Resolution: Disable this feature or add an exception for VarAC. For example, in Norton 360, the setting is called “Scan inbound emails (POP3, IMAP4).”


PSK Reporter self-reporting issue on V13.0.1

Hi VarAC Development Team,

I'd like to report a possible defect that appeared in the latest version (13.0.1). Regardless of the "Self report" setting, VarAC reports my own station to PSK Reporter immediately after beaconing. I've attached some screenshots for your reference.

Environment:

  • OS: Linux Mint 22.2

  • VarAC v13.0.1 (Linux compatible mode enabled)

  • VARA v4.8.9


165 Views
irad d
irad d
Nov 01

Hey Gene. I confirm this bug. Great catch! It happens now as I enabled the feature of seeing your own beacons on the list, and VarAC reports all beacons to PSK :) I fixed it. TU!

bottom of page