Teamviewer on Debian Trixie etc.
4
Had to install Teamviewer to help a ham friend the other day, but got caught out by the policykit-1 dependency not available, as Trixie now uses pkexec & polkitd instead. I had to rebuild the latest debian/Ubuntu deb from Teamviewer ; adrian@debian:~$ cd /home/adrian/Downloads adrian@debian:~/Downloads$ dpkg-deb --raw-extract teamviewer_15.64.3_amd64.deb teamviewer adrian@debian:~/Downloads$ sed -i "s/policykit-1/pkexec, polkitd/" teamviewer/DEBIAN/control adrian@debian:~/Downloads$ fakeroot -- dpkg-deb --build teamviewer teamviewer-rebuilt.deb dpkg-deb: building package 'teamviewer' in 'teamviewer-rebuilt.deb'. adrian@debian:~/Downloads$ sudo apt install ./teamviewer-rebuilt.deb Note, selecting 'teamviewer' instead of './teamviewer-rebuilt.deb' Installing: teamviewer Summary: Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 1 Download size: 0 B / 123 MB Space needed: 413 MB / 1,568 GB available Get:1 /home/adrian/Downloads/teamviewer-rebuilt.deb teamviewer amd64 15.64.3 [123 MB] Selecting previously unselected package teamviewer. (Reading database ... 628311 files and directories currently installed.) Preparing to unpack .../teamviewer-rebuilt.deb ... Unpacking teamviewer (15.64.3) ... Setting up teamviewer (15.64.3) ... Processing triggers for mailcap (3.74) ... Processing triggers for desktop-file-utils (0.28-1) ... Processing triggers for hicolor-icon-theme (0.18-2) ... Processing triggers for gnome-menus (3.36.0-2) ... Processing triggers for mate-menus (1.26.1-1) ... Processing triggers for dbus (1.16.2-2) ... adrian@debian:~/Downloads$ This executed fine and works well. 73 vk4tux
|
CTY-3512 Country Files - 22 April 2025
The Country (CTY) Files were updated on 22 April 2025: https://www.country-files.com/cty-3512-22-april-2025/ For installation instructions, start at: https://www.country-files.com/ Hover your mouse over the word Contest in the menu, then select the software you are using. To install the file, follow the link to your software at the top of the page. If you are interested in a bigger CTY.DAT for everyday logging, you can get it here: https://www.country-files.com/big-cty-22-april-2025/ Note that the release notes (and Version Entity) for this larger file are different than what is shown below. There is a separate link to them. As a reminder, there is an RSS feed of the latest country file announcements: https://www.country-files.com/feed/ Here are the release notes: 22 April 2025 (CTY-3512) VER20250422, Version entity is Vanuatu, YJ Added/changed Entities/Prefixes/Callsigns: * TX5U is French Polynesia, FO * TO974REF is Reunion Island, FR * MM0PLX/P is Scotland, GM * GB1GLJ and GB8MD are both Wales, GW * IR0IABJ is Sardinia, IS * KQ6KC is in CQ zone 4, not CQ zone 5 * AB1U, K9WWW, KC0BRA, KC9C, KQ2X, N5NPD, W0DNR, W0OIT and WE8RV are all United States, K in CQ zone 3, ITU zone 6 * N7ML and W0YKS are both United States, K in CQ zone 4, ITU zone 6 * AA7TJ, AB9TS, K1CPT, K2TKB, K3LKS, K6LJ, K7TRT, K9LTX, K9TF, KA8GIM, KC9GNK, KC9JIK, KD9OFG, KF7HIL, KK7VXK, KN4SLP, N9DMT, N9SEO, NA9DM, NE9U, W2EH, W9BED, W9JAB, WA7AFV, WJ9O and WT9Q are all United States, K in CQ zone 4, ITU zone 7 * AE4JM, AG4H, K3JWI, K4AZE, K4WNY, KB3KYH, KD4CXE, KE4VQM, KG5UN, KK4PC, KM4CRB, KM4ECH, KM4HQE, KO4OSL, KO4VJN, KQ4FBF, KQ4MYC, KQ4RLN, KW4OV, KY4DMD, N4KWX, N6XBP, NB6O, NT4M, W4BQN, W4FCL, W4FXZ, W4JHV, W4YPW, W4YTO, W5SGL, W6JSL, W7BAZ, W7XB, WA6GYC, WB4MSN, WF5X and WN1R are all United States, K in CQ zone 4, ITU zone 8 * AD7JL, AI5SM, AJ6TE, K0CHA, K0DVH, K5JSG, K5KIP, K6HLC, KA7HBH, KB6QPI, KB8NUF, KC9LC, KE8AE, KE8ZZH, KI8GM, KM7SAD, N0CK, N0GJR, N6ZFO, N8JAA, N8OYY, N8SLT, N8XT, N9MXI, W8KXW, WD9GMK, WF8D and WT9Y are all United States, K in CQ zone 5, ITU zone 8 * KN4FTF is Hawaii, KH6 * K7VRK and KD3AXV are both Alaska, KL * 5P0WARD/C, 5P0WARD/D, 5P0WARD/F, 5P0WARD/G, 5P0WARD/H, 5P0WARD/I, 5P0WARD/J, 5P0WARD/K, 5P0WARD/U, 5P0WARD/V and 5P0WARD/W are all Denmark, OZ * TA1AO/4 is Asiatic Turkey, TA * R8FF/P and RV9CDW/6 are both European Russia, UA * R0KA/9 is Asiatic Russia, UA9 in CQ zone 18 * RX0TX/P is Asiatic Russia, UA9 in CQ zone 18, ITU zone 32 * VK7IAN/4 is Australia, VK in ITU zone 55 Removed Entities/Prefixes/Callsigns: * EM1UTQ and RI1ANV in Antarctica, CE9 * EA9ADD in Spain, EA * TO3Z in Guadeloupe, FG * GS4WAB/P in Scotland, GM * IQ0AK/P in Sardinia, IS * AB9NE, AC4CA, AC4ZH, AE0CW, AI4LU, K0EMT, K0SB, K1NA, K1WTF, K2OO, K3IFR, K3PS, K3TD, K4NO, K4PKM, K4YA, K5WK, K5WP, K5XI, K6ND, K7TAR, KB9JJA, KC8GCR, KD5DD, KE5MHV, KI8I, KJ5AZV, KM4CRC, KO4O, KO4YIN, KS9W, N3BUO, N3CY, N3LHQ, N4KCD, N7DH, N8ELA, N8JRT, N8LA, N9OHW, NG5U, NJ0U, NN7W, W0MHK, W0SX, W3GW, W4BCG, W8MC, W8NUD, WA2IVD, WA4KY, WA4MLD, WA9KIA, WB4GHZ, WM4U and WQ3U in United States, K * KB7YEJ, KJ7UFK, N8YAK and W8OES in Alaska, KL * K4W in Puerto Rico, KP4 * R25BLIN and UB8M/1 in European Russia, UA * VK9YB in Norfolk Island, VK9N Though I am subscribed to this reflector so that I can make these announcements, I do not see most messages posted to it. If you have any comments or corrections to the country file, please contact me directly. 73 - Jim AD1C -- Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us
|
FLDIGI - RTTY output to Serial Device
7
Greetings: I have setup an RTTY -> phone -> modem ->ASR-33 demo here at the Computer Museum @ System Source (Hunt Valley, MD) (https://museum.syssrc.com) I am taking an RTTY Feed, (for example http://internet-tty.net:8000/ITTY) and feeding the sound into a telephone handset. When the handset is in a modem (I am just using the modem microphone since I don't think we have a modem for 45baud, Baudot) the sound goes into the sound card and is decoded by fldigi. I have not figured out how to easily get the text (which appears on fldigi screen) to the serial port which goes to the teletype. I have hacked it by logging the RTTY text to a file, and then I am using a Python script to clean up the log file and print on the ASR-33. Hoping to find a way to simplify and pipe the rtty signal directly to /dev/ttyUSB0. Thanks Bob (More details, not really important for the question, but here is the setup) Raspberry Pi 5, with USB sound dongle: mplayer gets rtty feed. Sound redirected from HDMI to USB Sound Dongle that is wired to old school Dial-up telephone. When phone goes off hook, we hear the RTTY signal from the phone earpiece. Earpiece is set in acoustic modem. just used the microphone which is wired back into microphone input on USB sound dongle. Fldigi decodes RTTY, and logs to /home/pi/.fldigi/fldigiyyyymmdd.log Python opens the file, skips two the end, the cuts the beginning of each line which logging info, and it sends the ASCII text to a USB->Serial Dongle. ASR-33 has a 3rd party card to take RS-232 as input instead of Current loop.
|
kcat (kachina 505dsp) used to play nice with fldigi but now not so much
4
I use kcat all the time and it works great. I use fldigi only now and then. But I built fldigi from source yesterday, to get all the new-and-improved, all looked clean. But now doesn't work with kcat. I wish I had tried this before blowing away my old fldigi. I can't say what version it was, or if for sure it would have worked yesterday. But it used to work. fldigi version 4.2.06 kcat version 1.2.5 Sequence & Symptoms: - start fldigi - some alsa lib errors, JackShmReadWritePtr messages - some complaints about not being able to open sockets - But it starts up and shows a nice normal looking window. - start kcat - no indicated issues I start fldigi in a terminal window and after starting kcat I can see that the two are talking over the xmlrpc link, constant streaming of freq/band/mode messages in the fldigi terminal window that look ok. Frequency, mode, bandwidth are the same in both gui windows. If I change mode or bandwidth on kcat, fldigi tracks. Likewise if I change mode or bandwidth from fldigi, kcat tracks. ===> If I try to change frequency from kcat, it won't, meaning it briefly shows the changed frequency then jumps back. ===> If I change frequency from fldigi, fldigi updates the display as if normal, but nothing happens on the kcat end (stays stuck on same freq as when started). If I close fldigi, kcat can then manage the frequency as normal. So it would seem fldigi is not allowing kcat to change frequency. I think this setup worked a few months ago. kcat has not changed. fldigi has changed. I would try building a downlevel fldigi to test against but I don't know how, and can't find instructions. Any suggestions appreciated. Bill N7DZ
|
Fldigi 4.2.06.27 (was Re: [winfldigi] RX/RTX Character Set)
4
Built and runs OK, but ... a) Not sure where the new font choices appear, I can't see anything new listed in the config font menu choices relating specifically to RTTY. That, and more worryingly... b) The new .27 alpha, has wiped out my pre-existing macro configurations and log's!.... I had backups, so copied them back into the default .Fldigi folder structure (as I had to do for .26) and ran it again. Same result, logs etc are empty (it appears to write new blank/default files without checking first it seems.) Past alpha (pre .26) updates didn't have this issue, but .26 and .27 do it seems. .27 with a vengeance it seems! OS: LMDE 6 64bit, on 4 core intel with 8G RAM. All up-to-date. 73. Dave G0WBX
|
CTY-3511 Country Files - 12 April 2025
The Country (CTY) Files were updated on 12 April 2025: https://www.country-files.com/cty-3511-12-april-2025/ For installation instructions, start at: https://www.country-files.com/ Hover your mouse over the word Contest in the menu, then select the software you are using. To install the file, follow the link to your software at the top of the page. If you are interested in a bigger CTY.DAT for everyday logging, you can get it here: https://www.country-files.com/big-cty-12-april-2025/ Note that the release notes (and Version Entity) for this larger file are different than what is shown below. There is a separate link to them. As a reminder, there is an RSS feed of the latest country file announcements: https://www.country-files.com/feed/ Here are the release notes: 12 April 2025 (CTY-3511) VER20250412, Version entity is Balearic Islands, EA6 Added/changed Entities/Prefixes/Callsigns: * II0GDF/9 and IQ6CC/9 are both Sicily, *IT9 * TO3E is Martinique, FM * WC8L is in ITU zone 7, not ITU zone 8 * WC8L is in CQ zone 4, not CQ zone 5 * KH6KK is Guam, KH2 * KI7KPB and N6MHR are both Alaska, KL * LW3EMP/I is Argentina, LU * R1961AG, R1994YU, R1996VK, R2014NC and R80DGZ are all European Russia, UA * VK/M0LEP/P is Australia, VK in CQ zone 29, ITU zone 58 Removed Entities/Prefixes/Callsigns: * VK0AI in Antarctica, CE9 * GB0GGR and GB5AG in Scotland, GM * K0DSC, KO4NOL and W0ERJ in United States, K * KG7IAL and KG7JSU in Hawaii, KH6 * AG6PI and K7HJK in Alaska, KL * N7BPT in Puerto Rico, KP4 * LU1VJK/V, LU5DLH/D, LU7ETZ/D, LU9EI/D, LW2EAS/D and LW6DR/D in Argentina, LU * R0QAW/P and R4FBJ/0/P in Asiatic Russia, UA9 * UT1KY/WAP and UT7UA/WAP in Ukraine, UR * LU1ZI in South Shetland Islands, VP8/h Though I am subscribed to this reflector so that I can make these announcements, I do not see most messages posted to it. If you have any comments or corrections to the country file, please contact me directly. 73 - Jim AD1C -- Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us
|
FLRIG kill when connect to FLdigi
When I connect fldigi to be controlled via flrig (ft-817), flrig closes unexpectedly. It even opens the window to report the problem via bugzilla. I can only use Flrig if I am disconnected from FLdigi. Fldigi: Enable Flrig xcvr Control with fldigi as client Flrig PTT meus modem Has anyone experienced this and managed to fix it? Fedora 41 XFCE Fldigi 4.2.06 Flrig 2.0.05
|
FS: RPi 5 / 8 Gb w/ 256 GB SSD and Accessories
2
Still finding "experiments." I have a RPi 5 with 8 GB RAM. It also has a Raspberry Pi Foundation active cooling fan and third-party daughterboard (SupTronics X1000 v1.5) for an M.2 NVME SSD. Includes a black Raspberry Pi Foundation enclosure. The RPi with fan and daughterboard mostly fit inside the case. The top will not snap down due to the SSD board GPIO header extension. Also includes a Geekworm 5 VDC / 5 A power supply. All of it works, I'm just no longer interested in pursuing the use of a Raspberry Pi. $100 total shipped to your door. Please respond direct if interested. Regards, Joel, W4JBB
|
FLDIGI Bookworm Lag Fix
If you are encountering lag and freezing with FLDIGI after upgrading to Bookworm, the issue may be with the Wayland display server native to that operating system. Reverting to X11 may resolve the issue, and is extremely easy to accomplish through sudo raspi-config. Here is a website I found with simple instructions: https://pimylifeup.com/raspberry-pi-wayland-x11/
|
CTY-3510 Country Files - 06 April 2025
The Country (CTY) Files were updated on 06 April 2025: https://www.country-files.com/cty-3510-06-april-2025/ For installation instructions, start at: https://www.country-files.com/ Hover your mouse over the word Contest in the menu, then select the software you are using. To install the file, follow the link to your software at the top of the page. If you are interested in a bigger CTY.DAT for everyday logging, you can get it here: https://www.country-files.com/big-cty-06-april-2025/ Note that the release notes (and Version Entity) for this larger file are different than what is shown below. There is a separate link to them. As a reminder, there is an RSS feed of the latest country file announcements: https://www.country-files.com/feed/ Here are the release notes: 6 April 2025 (CTY-3510) VER20250406, Version entity is Morocco, CN Added/changed Entities/Prefixes/Callsigns: * EF0F/8 is Canary Islands, EA8 * M0KXR is Northern Ireland, GI * GB5WAA and GB9WAA are both Scotland, GM * KB2DJE, KG5DVX and NV2T are all Hawaii, KH6 * KD7CYC and NN7C are both Alaska, KL * LU1DHL/W, LU6DO/V and LU8YE/Y are all Argentina, LU in ITU zone 16 * R9FCS/4, UE80MA and UE80SZ are all European Russia, UA * RA/EU1FY is Kaliningrad, UA2 * RK4PA/9 is Asiatic Russia, UA9 in ITU zone 20 Removed Entities/Prefixes/Callsigns: * IT9ECY/CH in Sicily, *IT9 * EM1U, KC4/KB1EHE, KC4/KB1IFZ and VK0/FT4YM/P in Antarctica, CE9 * EA5IKT/P in Spain, EA * FO/F4LYI and FO/F6BCW in Marquesas Islands, FO/m * G6ICR in Isle of Man, GD * G0HCQ, G0JCE, G4WZG, G5RDX, GB4CDG and M0TFU in Scotland, GM * M0KWG and M0TDZ in Wales, GW * IZ3QBN/CRT in Italy, I * K3JWI, KG7SPL, NE9U and W5SGL in United States, K * AA7LE, KJ6NCW and W2DK in Hawaii, KH6 * KD6UDQ and WH6IQ in Alaska, KL * LU1VNH/V, LU1YY/V, LU3WFJ/XA, LU5DTF/D, LU6DJ/D, LU6DM/D, LU6UVI/D, LU8DBB/D, LU8DCH/D, LU8EMD/D, LU8XW/XP, LW2EDL/D, LW5EVI/D and LW9EVV/D in Argentina, LU * R102AE, R102ME, R9YDX/6, UB0IBA/7 and UE82AWD in European Russia, UA * UB9MCW/P in Asiatic Russia, UA9 * VK9/W5EIT in Cocos (Keeling) Islands, VK9C Though I am subscribed to this reflector so that I can make these announcements, I do not see most messages posted to it. If you have any comments or corrections to the country file, please contact me directly. 73 - Jim AD1C -- Jim Reisert AD1C, <jjreisert at alum.mit.edu>, https://ad1c.us
|
Macro for timed band-switching?
8
Hi all, I've read through the documentation but still confused on how to set macros for automatic band-switching at certain hours. I just want to use it for switching between two bands once per 24-hours; no mode changes or anything. I'd like to switch to 14.103 at 12 noon EST and stay there till 4:59 PM EST, then switch to 10.148.2 at 5 PM EST and stay there overnight till 11:59 AM EST. Any assistance would be greatly appreciated. Thanks, 73
|
[winfldigi] RX/RTX Character Set
fldigi 4.2.06.27 development version available for testing Download at https://www.w1hkj.org/alpha/fldigi/ fldigi-4.2.06.27.tar.gz2025-04-05 19:384.9M fldigi-4.2.06.27_set..>2025-04-05 19:386.6M fldigi-dark-scheme.png2025-03-21 07:41122K readme.dmg.txt2025-03-21 07:41532 readme.txt2025-04-05 19:38877K commit 39f388baf4b364a4abedc366f7fc7d5d346aadb5 Author: dave-w1hkj <w1hkj@...> Date: Sat Apr 5 09:35:00 2025 -0600 Alpha * version 4.2.06.27 commit e4ed761d6e6fea3740d70654d5aff2722dcde225 Author: dave-w1hkj <w1hkj@...> Date: Fri Apr 4 14:06:16 2025 -0500 TTY ITA2 * allow user to select USTTY or ITA2 for Baudot shifted characters 73, David, W1HKJ
|
Fldigi 4.2.06.26 crash when trying to view "show active frequencies"
5
Hello Everyone, I'm re-setting up my station on Ubuntu 24.04 and just compiled up Fldigi and Flrig. For Fldigi, I configured the ./configure stage for compiling with the following: -- $ ./configure --build=x86_64-linux-gnu --prefix=/usr '--includedir=${prefix}/include' '--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' --sysconfdir=/etc --localstatedir =/var --disable-option-checking --disable-silent-rules '--libdir=${prefix}/lib/x86_64-linux-gnu' --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --with-libmbe dtls LIBMBEDTLS_CFLAGS=-I/usr/include/mbedtls 'LIBMBEDTLS_LIBS=-lmbedtls -lmbedx509 -lmbedcrypto' -- Everything seems to be running well except if I click on the "Open List" book icon and then click on the "Show active frequencies" dialog bubble icon on the right of the book icon, the waterfall and general UI freezes for about 5 seconds and then I see in the terminal I started it in: -- *** stack smashing detected ***: terminated Segmentation fault (core dumped) -- The stack trace I'm getting from the coredump is as follows: -- --- source code stack trace --- #0 __GI___pthread_enable_asynccancel () at ./nptl/cancellation.c:33 [Error: cancellation.c was not found in source tree] #1 0x00007bbe98f1c598 in __GI___libc_write (nbytes=15, buf=0x5d7c99d99dc8, fd=2) at ../sysdeps/unix/sysv/linux/write.c:26 [Error: write.c was not found in source tree] #2 __GI___libc_write (fd=2, buf=0x5d7c99d99dc8, nbytes=15) at ../sysdeps/unix/sysv/linux/write.c:24 [Error: write.c was not found in source tree] #3 0x00007bbe98e93975 in _IO_new_file_write (f=0x7bbe990044e0 <_IO_2_1_stderr_>, data=0x5d7c99d99dc8, n=15) at ./libio/fileops.c:1181 [Error: fileops.c was not found in source tree] #4 0x00007bbe98e93bda in new_do_write (to_do=<optimized out>, data=0x5d7c99d99dc8 "\nCaught signal ", fp=0x7bbe990044e0 <_IO_2_1_stderr_>) at ./libio/libioP.h:1030 [Error: libioP.h was not found in source tree] #5 _IO_new_file_xsputn (n=15, data=<optimized out>, f=<optimized out>) at ./libio/fileops.c:1255 [Error: fileops.c was not found in source tree] #6 _IO_new_file_xsputn (f=0x7bbe990044e0 <_IO_2_1_stderr_>, data=<optimized out>, n=15) at ./libio/fileops.c:1197 [Error: fileops.c was not found in source tree] #7 0x00007bbe98e86a12 in __GI__IO_fwrite (buf=0x5d7c99d99dc8, size=1, count=15, fp=0x7bbe990044e0 <_IO_2_1_stderr_>) at ./libio/libioP.h:1030 [Error: libioP.h was not found in source tree] #8 0x00007bbe99356dc4 in std::basic_ostream<char, std::char_traits<char> >& std::__ostream_insert<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*, long) () at /lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x00007bbe9935713c in std::basic_ostream<char, std::char_traits<char> >& std::operator<< <std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*) () at /lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x00005d7c99c39e89 in ??? () #11 0x00005d7c99c39f99 in ??? () #12 0x00007bbe98e45330 in <signal handler called> () at /lib/x86_64-linux-gnu/libc.so.6 #13 0x00005d7c99c39f80 in ??? () #14 0x00007bbe98e45330 in <signal handler called> () at /lib/x86_64-linux-gnu/libc.so.6 #15 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44 [Error: pthread_kill.c was not found in source tree] #16 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78 [Error: pthread_kill.c was not found in source tree] #17 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 [Error: pthread_kill.c was not found in source tree] #18 0x00007bbe98e4527e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 [Error: raise.c was not found in source tree] #19 0x00007bbe98e288ff in __GI_abort () at ./stdlib/abort.c:79 [Error: abort.c was not found in source tree] #20 0x00007bbe98e297b6 in __libc_message_impl (fmt=fmt@entry=0x7bbe98fce765 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:134 [Error: libc_fatal.c was not found in source tree] #21 0x00007bbe98
|
For Sale: Several RPi Zero 2s and Accessories - Make Offer
6
I am cleaning out and found several RPi Zero 2s and accessories. What I have found so far: 2 ea. RPi Zero 2s with pre-soldered GPIO headers 2 ea. RPi Zero 2s without pre-soldered GPIO headers 2 ea. color-coded Pi GPIO headers to be soldered onto the two RPi Zero 2s without headers 1 ea. GPIO header extension 2 ea. Adafruit 1.3" MiniPiTFT displays 2 ea. StarTech USB micro-B to USB A (for USB A power supplies) 4 ea. FLIRC RPi Zero 2 cases 2 ea. sb Components clear acrylic RPi Zero 2 cases 1 ea. case for RPi Zero 2 - I am not sure what this one is but it's put together in layers Make me a reasonable offer and I'll pay for shipping. I was playing around with DigiPi for a while and that's why I have all these. I am no longer playing around with DigiPi - I just don't have the time or money for "experimenting" any more. 73, Joel, W4JBB
|
Fldigi Lockup
18
I am running Linux Mint 22 Cinnamon and Fldigi version 4.2.06.09 and I'm running into a problem. After a bit of operation Fldigi will lock up. When I check top it tells me Fldigi is using more than 100% CPU utilization. I have to kill and restart Fldigi. This happened with the stable version 4.2.06 and on another Linux Mint computer. I have no problems on the Windows 11 computer. Does anyone else have this issue and is there a way I can trouble shoot this. I have 7.7 gig of memory and 1 Terra Byte of storage. 73, Ron NY3J
|
Fldigi 4.2.06.26 on Linux (LMDE 6)
4
Hi again... Pulled and built 4.2.06.26 without issue a few days ago, and everything was good. A major OS update appeared "took" without issue, and Fldigi still behaved as one would expect, even after restarts and so on. Great! Fired it all up this morning (March 28th, 10AM UK) and all good. Had to shutdown the PC some time later to move some other hardware about, much easier if I can move the PC and monitors out of the way. Put it all back and started it all again. No issue... But, after a while running in the background (while I did some email's in another UI desktop) while it was running PSK31 mode (that WAS showing the AFC control as able to be used, but NOT active.) On restoring Fldigi to "the front" (AKA "in focus") and active use, that AFC button is again greyed out. But, fiddling with the radio and a steady strong signal, the AFC is ACTIVE, but not working correctly, even though the greyed out button shows it as INACTIVE. And of course, I can't control it. Restarting Fldigi, the PC etc, that AFC button is permanently greyed out, but the underlying AFC functionality is still ACTIVE!.. Someone made mention of the fact that AFC was not valid* for all modes. Where is that information please? As I can't see it in the web help doc's. Only this, in Fldigi's built in help. AFC (AFC) control When this button is pressed, an indicator on the button turns yellow, and the program will automatically retune to drifting signals. When the button is again pressed, AFC is off, and the tuning will stay where you leave it. No mention of which modes it applies to, or not... (* Valid or not, when the control is greyed out, and the LED also shows grey) it seems to be active for all modes, if you watch it's behavior on a busy waterfall, especially a weak signal with stronger ones nearby/encroaching.) So, what on earth is going on? Still confused of Central UK. 73 Dave G0WBX.
|
CQRLOG not opening
5
Hi all, new to Linux and new to group. Have installed CQRLOG from software manager within Mint-Cinnamon. Opens with database error and will not go any further. My goal is to make Linux my primary OS with Windows on separate drive and would like to have the logger available on Linux drive. Thanks to mediators for letting me in the group and any tips/advice is welcome. 73, Mike K0TQ
|
Fldigi
2
After redoing my desktop to the UbuntuMate release 24.10 and installing FLdigi, this came up: configure: error: in `/home/will/Downloads/fldigi-4.2.06': configure: error: The pkg-config script could not be found or is too old. Make sure it is in your PATH or set the PKG_CONFIG environment variable to the full path to pkg-config. Alternatively, you may set the environment variables PNG_CFLAGS and PNG_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. To get pkg-config, see <http://pkg-config.freedesktop.org/>. See `config.log' for more details Is there a way around this to get FLdigi sorted for use? Will 2M0WHN
|
WSJTX failure?
4
Started the PC and all is fine. That is until I started WSJTx. Apparently the radio does not communicate with the PC. Did a reinstall of WSJT and updated as best I could but it does not work. So tried JS8Call. Nothing. Same 'problem' has arisen. Which is strange as FLdigi works fine. So it is not a baud rate problem. I checked all those settings is WSJT and radio. Both are fine. Hamlib is working as FLdigi would not TX. So something in an update has gone kaput! Any ideas as to what may have caused this? Will 2M0WHN
|
CALL3.txt - where to get "fresh" (WSJT-X)
I understand that CALL3.txt is filled individually. But still, maybe there are links? Do not suggest links that I know of (http://www.mmmonvhf.de/dbase.php and https://wsjt-x-improved.sourceforge.io/CALL3.TXT).
|