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:
For installation instructions, start at:
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:
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:
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>,
|
Re: Macro for timed band-switching?
David, that was a great detailed explanation. I appreciate the time you took to post this.?
?
Greg
KE5DXA?
|
Re: [winfldigi] RX/RTX Character Set
fldigi 4.2.06.27 development version available for testing
Download at ? | | 2025-04-05 19:38 | 4.9M | ? | ? | | 2025-04-05 19:38 | 6.6M | ? | ? | | 2025-03-21 07:41 | 122K | ? | ? | | 2025-03-21 07:41 | 532 | ? | ? | | 2025-04-05 19:38 | 877K | ?
|
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
toggle quoted message
Show quoted text
On Tue, Apr 1, 2025 at 10:21?PM George Stein - NJ3H via <nj3h= [email protected]> wrote: Thank you David for your reply. Is this something that could be added in a future version of FLDigi?
?
Regards,?
George?
|
Re: Macro for timed band-switching?
Thank you for this writeup!
|
Re: Macro for timed band-switching?
To test the use of fldigi-shell from a cron script file I created two cron entries using "crontab"
dave@tk7:~$ crontab -l # Edit this file to introduce tasks to be run by cron. # # Each task to run has to be defined through a single line # indicating with different fields when the task will be run # and what command to run for the task # # To define the time you can provide concrete values for # minute (m), hour (h), day of month (dom), month (mon), # and day of week (dow) or use '*' in these fields (for 'any'). # # Notice that tasks will be started based on the cron's system # daemon's notion of time and timezones. # # Output of the crontab jobs (including errors) is sent through # email to the user the crontab file belongs to (unless redirected). # # For example, you can run a backup of all your user accounts # at 5 a.m every week with: # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/ # # For more information see the manual pages of crontab(5) and cron(8) # # m h ?dom mon dow ? command 30 21 * * * /home/dave/bin/fldigi-shell -c "rig.set_frequency 14070000" 45 21 * * * /home/dave/bin/fldigi-shell -c "rig.set_frequency 7070000"
a few minutes before 2130 and then waited for the cron demon?to execute the 2130 and 2145 entries.
Worked perfectly.
73, David, W1HKJ
toggle quoted message
Show quoted text
On Tue, Apr 1, 2025 at 8:52?PM w1hkj < w1hkj25@...> wrote: A little more on using the Perl script, fldigi-shell.? I just updated the fldigi WIKI xmlrpc how-to:?
Tested the XML::RPC install script and works perfect on Mint 21.3.
The fldigi-shell script can be used interactively as a command line remote control of a running fldigi instance, or it can process commands one at a time and exit after each command.? To satisfy this users request two simple fldigi-shell script invocations are needed:
dave@tk7:~$ fldigi-shell -c "rig.set_frequency 14103000"3580000.000000 dave@tk7:~$ fldigi-shell -c "rig.set_frequency 10148020"14103000.000000 ? These commands can be added to as a cron job, see "man cron"
Cron jobs are a scheduling tool used in Linux and Unix-like systems to automate tasks by running commands or scripts at specific times or intervals. They are defined using a specific syntax in a file called crontab.
Cron jobs automate repetitive tasks by scheduling commands or scripts to run automatically.
Time-Based Scheduling: They allow you to schedule tasks based on minutes, hours, days, months, and days of the week.
Crontab: Cron jobs are defined in a file called crontab, which is a text file that contains the scheduled tasks.
Cron Daemon: The cron daemon is a background process that periodically checks the crontab file and executes tasks at the specified times.
How they work: 1. Define the Schedule: ? ? You define the schedule for a task using a specific syntax in the crontab file. 2. Cron Daemon Checks: ? ? The cron daemon periodically checks the crontab file for tasks that need to be executed. 3. Task Execution: ? ? When a task's scheduled time arrives, the cron daemon executes the corresponding command or script. Basic Syntax: ? ? The basic syntax for a cron job entry in the crontab file is: Code
* * * * * command_or_script | | | | | | | | | +-- Day of the week (0-6) (Sunday=0 or 7) | | | +---- Month (1-12) | | +------ Day of the month (1-31) | +-------- Hour (0-23) +---------- Minute (0-59) Asterisks (*): An asterisk means "every" for that particular field.
Examples: 0 8 * * * /scripts/monitor.sh - Run the script /scripts/monitor.sh every day at 8:00 AM. 0 16 4 * * /root/clearcache.sh - Run the script /root/clearcache.sh on the 4th day of each month at 4:00 PM. 0 9 1 12 * /root/backup.sh - Run the script /root/backup.sh on the 1st of December at 9:00 AM.
73, David, W1HKJ
For very long duration timing and band/frequency changes you should set up a chron?job that sends xmlrpc commands to the fldigi xmlrpc server.??
see:??
This Perl script gives full examples of how to send various commands to fldigi .
73, David, W1HKJ
Oops!? I'm using FLDigi.? I read through the docs on using "Timer" in a macro, but still baffled on how to set it up.? Thanks, 73
|
Re: Macro for timed band-switching?
A little more on using the Perl script, fldigi-shell.? I just updated the fldigi WIKI xmlrpc how-to:?
Tested the XML::RPC install script and works perfect on Mint 21.3.
The fldigi-shell script can be used interactively as a command line remote control of a running fldigi instance, or it can process commands one at a time and exit after each command.? To satisfy this users request two simple fldigi-shell script invocations are needed:
dave@tk7:~$ fldigi-shell -c "rig.set_frequency 14103000"3580000.000000 dave@tk7:~$ fldigi-shell -c "rig.set_frequency 10148020"14103000.000000 ? These commands can be added to as a cron job, see "man cron"
Cron jobs are a scheduling tool used in Linux and Unix-like systems to automate tasks by running commands or scripts at specific times or intervals. They are defined using a specific syntax in a file called crontab.
Cron jobs automate repetitive tasks by scheduling commands or scripts to run automatically.
Time-Based Scheduling: They allow you to schedule tasks based on minutes, hours, days, months, and days of the week.
Crontab: Cron jobs are defined in a file called crontab, which is a text file that contains the scheduled tasks.
Cron Daemon: The cron daemon is a background process that periodically checks the crontab file and executes tasks at the specified times.
How they work: 1. Define the Schedule: ? ? You define the schedule for a task using a specific syntax in the crontab file. 2. Cron Daemon Checks: ? ? The cron daemon periodically checks the crontab file for tasks that need to be executed. 3. Task Execution: ? ? When a task's scheduled time arrives, the cron daemon executes the corresponding command or script. Basic Syntax: ? ? The basic syntax for a cron job entry in the crontab file is: Code
* * * * * command_or_script | | | | | | | | | +-- Day of the week (0-6) (Sunday=0 or 7) | | | +---- Month (1-12) | | +------ Day of the month (1-31) | +-------- Hour (0-23) +---------- Minute (0-59) Asterisks (*): An asterisk means "every" for that particular field.
Examples: 0 8 * * * /scripts/monitor.sh - Run the script /scripts/monitor.sh every day at 8:00 AM. 0 16 4 * * /root/clearcache.sh - Run the script /root/clearcache.sh on the 4th day of each month at 4:00 PM. 0 9 1 12 * /root/backup.sh - Run the script /root/backup.sh on the 1st of December at 9:00 AM.
73, David, W1HKJ
toggle quoted message
Show quoted text
For very long duration timing and band/frequency changes you should set up a chron?job that sends xmlrpc commands to the fldigi xmlrpc server.??
see:??
This Perl script gives full examples of how to send various commands to fldigi .
73, David, W1HKJ
Oops!? I'm using FLDigi.? I read through the docs on using "Timer" in a macro, but still baffled on how to set it up.? Thanks, 73
|
Re: Macro for timed band-switching?
For very long duration timing and band/frequency changes you should set up a chron?job that sends xmlrpc commands to the fldigi xmlrpc server.??
see:??
This Perl script gives full examples of how to send various commands to fldigi .
73, David, W1HKJ
toggle quoted message
Show quoted text
Oops!? I'm using FLDigi.? I read through the docs on using "Timer" in a macro, but still baffled on how to set it up.? Thanks, 73
|
Re: Macro for timed band-switching?
Oops!? I'm using FLDigi.? I read through the docs on using "Timer" in a macro, but still baffled on how to set it up.? Thanks, 73
|
Re: Fldigi 4.2.06.26 crash when trying to view "show active frequencies"
David,
Please run fldigi from within the gnu debugger, gdb.??.
Send me the results of the backtrace command after you force another crash.
David
toggle quoted message
Show quoted text
David,
Was the updated fldigi installed over an existing one? (i.e. with
an existing configuration) If so, try deleting (or renaming) your
.fldigi folder.
Bob W6CP
On 3/29/25 12:00, David Ranch, KI6ZHD
via wrote:
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 0x00007bbe98f36c19 in __GI___fortify_fail
(msg=msg@entry=0x7bbe98fce77d "stack smashing detected") at
./debug/fortify_fail.c:24
? [Error: fortify_fail.c was not found in source tree]
#22 0x00007bbe98f37ea4 in __stack_chk_fail () at
./debug/stack_chk_fail.c:24
? [Error: stack_chk_fail.c was not found in source tree]
#23 0x00007bbe9a1b8e3a in ??? () at
/lib/x86_64-linux-gnu/libmbedcrypto.so.7
#24 0x00007bbe9a1b4823 in mbedtls_entropy_init () at
/lib/x86_64-linux-gnu/libmbedcrypto.so.7
--
This is 100% reproducable so I'm curious if other people are
seeing this as well.? Any recommendations on a fix?
--David
KI6ZHD
|
Re: Macro for timed band-switching?
what program?
Thanks Dan KC2STA
toggle quoted message
Show quoted text
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
-- Dan Ziolkowski KC2STA SKCC #4290T Ubuntu LINUX
|
Macro for timed band-switching?
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
|
Re: Fldigi 4.2.06.26 crash when trying to view "show active frequencies"
David,
Was the updated fldigi installed over an existing one? (i.e. with
an existing configuration) If so, try deleting (or renaming) your
.fldigi folder.
Bob W6CP
On 3/29/25 12:00, David Ranch, KI6ZHD
via groups.io wrote:
toggle quoted message
Show quoted text
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 0x00007bbe98f36c19 in __GI___fortify_fail
(msg=msg@entry=0x7bbe98fce77d "stack smashing detected") at
./debug/fortify_fail.c:24
? [Error: fortify_fail.c was not found in source tree]
#22 0x00007bbe98f37ea4 in __stack_chk_fail () at
./debug/stack_chk_fail.c:24
? [Error: stack_chk_fail.c was not found in source tree]
#23 0x00007bbe9a1b8e3a in ??? () at
/lib/x86_64-linux-gnu/libmbedcrypto.so.7
#24 0x00007bbe9a1b4823 in mbedtls_entropy_init () at
/lib/x86_64-linux-gnu/libmbedcrypto.so.7
--
This is 100% reproducable so I'm curious if other people are
seeing this as well.? Any recommendations on a fix?
--David
KI6ZHD
|
Re: Fldigi 4.2.06.26 crash when trying to view "show active frequencies"
first, googling the error, "stack smashing detected", indicates gcc protection found a buffer overflow.
with that and the traceback, I'd suggest opening a bug upstream... it's a code foul up.
toggle quoted message
Show quoted text
On Sat, Mar 29, 2025, 12:00 David Ranch, KI6ZHD via <linuxham-fld= [email protected]> wrote:
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 0x00007bbe98f36c19 in __GI___fortify_fail
(msg=msg@entry=0x7bbe98fce77d "stack smashing detected") at
./debug/fortify_fail.c:24
? [Error: fortify_fail.c was not found in source tree]
#22 0x00007bbe98f37ea4 in __stack_chk_fail () at
./debug/stack_chk_fail.c:24
? [Error: stack_chk_fail.c was not found in source tree]
#23 0x00007bbe9a1b8e3a in ??? () at
/lib/x86_64-linux-gnu/libmbedcrypto.so.7
#24 0x00007bbe9a1b4823 in mbedtls_entropy_init () at
/lib/x86_64-linux-gnu/libmbedcrypto.so.7
--
This is 100% reproducable so I'm curious if other people are
seeing this as well.? Any recommendations on a fix?
--David
KI6ZHD
|
Re: Fldigi 4.2.06.26 crash when trying to view "show active frequencies"
Hi David
Worked without fault here. "Recent activity for grid QF" showed
up okay. Also ran in terminal with no errant info,
Fairly vanilla configure here, just --enable-optimizations=native
on Debian 12.10, i5 Toshiba laptop.
Cheers Bob VK2YQA
On 30/3/25 06:00, David Ranch, KI6ZHD
via groups.io wrote:
toggle quoted message
Show quoted text
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:
|
Re: For Sale: Several RPi Zero 2s and Accessories - Make Offer
³§´Ç±ô»å¡
Please contact me at joel.b.black@... and we¡¯ll finalize the deal.
Thanks,
toggle quoted message
Show quoted text
On Mar 29, 2025, at 12:58?PM, Bob Finch, W9YA via groups.io <w9ya.ham@...> wrote:
If it's not too late...how about $50 ?
?
es vy 73 om de "Baab" w9ya
|
Fldigi 4.2.06.26 crash when trying to view "show active frequencies"
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 0x00007bbe98f36c19 in __GI___fortify_fail
(msg=msg@entry=0x7bbe98fce77d "stack smashing detected") at
./debug/fortify_fail.c:24
? [Error: fortify_fail.c was not found in source tree]
#22 0x00007bbe98f37ea4 in __stack_chk_fail () at
./debug/stack_chk_fail.c:24
? [Error: stack_chk_fail.c was not found in source tree]
#23 0x00007bbe9a1b8e3a in ??? () at
/lib/x86_64-linux-gnu/libmbedcrypto.so.7
#24 0x00007bbe9a1b4823 in mbedtls_entropy_init () at
/lib/x86_64-linux-gnu/libmbedcrypto.so.7
--
This is 100% reproducable so I'm curious if other people are
seeing this as well.? Any recommendations on a fix?
--David
KI6ZHD
|
Re: For Sale: Several RPi Zero 2s and Accessories - Make Offer
I'd be interested in two of the Pis & 2 cases, if you didn't mind splitting them (I'd pick up the shipping). No need for the displays from my side... Say, $20?+ shipping for the pis and 2 cases? I don't mind if they're with or without presoldered headers.
Otherwise, I yield to Bob as he did offer first!
toggle quoted message
Show quoted text
On Sat, Mar 29, 2025 at 1:58?PM Bob Finch, W9YA via <w9ya.ham= [email protected]> wrote: If it's not too late...how about $50 ?
?
es vy 73 om de "Baab" w9ya
|
Re: For Sale: Several RPi Zero 2s and Accessories - Make Offer
If it's not too late...how about $50 ?
?
es vy 73 om de "Baab" w9ya
|
Re: For Sale: Several RPi Zero 2s and Accessories - Make Offer
Neil,
They are 2 Ws (with WiFi).
Joel, W4JBB
toggle quoted message
Show quoted text
On Sat, Mar 29, 2025 at 11:59, Neil Hanlon, N1HAN < neil@...> wrote:
Are they zero 2 or zero 2w (wifi)?
On Sat, Mar 29, 2025, 11:36 Joel Black - W4JBB via
<joel.b.black=
[email protected]> wrote:
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 with
out 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
|