开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Linuxham
  2. Messages
Expanded Topics Messages Polls
Date
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

On Sat, Mar 29, 2025 at 8:17?PM Bob W6CP via <bob=[email protected]> wrote:
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

On Sun, Mar 30, 2025 at 6:39?PM Jeff KP3FT via <kp3ft=[email protected]> wrote:
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:

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.


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:

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,
Joel, W4JBB

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!

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



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

Re: For Sale: Several RPi Zero 2s and Accessories - Make Offer

 

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 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
For Sale: Several RPi Zero 2s and Accessories - Make Offer

 

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
Re: Fldigi Lockup

 

开云体育

Well, today on the 80 meter NBEMS nets I was about to send traffic with Flmsg and when I looked up Fldigi was locked up while I was just receiving other traffic.
There's a lot of activity on these nets so maybe I'll have to shutdown and reboot in between nets.
It has to be just my setup because I don't hear anyone else with this problem. I'll keep plugging away.

Ron NY3J

On 3/27/25 22:14, Ron Wenig wrote:

So I just finished a net with the local ARES group on their FM repeater. There was a lot of traffic that I received and I passed traffic and no lockup. So hopefully disabling USB sleep fixed it.
When I built Fldigi I didn't install pavucontrol because like I said there was a message that popped up saying there was a conflict with pipewire and pulseaudio.
The one thing I noticed is I can click the speaker icon in the task bar, select the USB Audio Device and adjust the audio levels which is easier than using pavucontrol and the sound levels both speaker and mic seem to be okay.
I have PortAudio selected with pipewire.

Thanks again and 73, Ron NY3J

On 3/27/25 14:58, Ron NY3J via groups.io wrote:
Hi Joe,

I am running Mint 22.1 and Fldigi version 4.2.06.09 and I use Rigcat for rig control. Usually Fldigi does run 20% or less CPU. It's usually during a net when there's lots of things happening that, without warning, I look at Fldigi and it stopped. Very embarrassing when NCS just called on me to send my traffic :-)

So the autosuspend was 2 and I used the instructions in the Linuxmint forum to set it to -1. Thanks for the information. It's interesting that it didn't effect my wireless USB keyboard and mouse.

73, Ron NY3J

On 3/27/25 14:23, Joseph Counsil, K?OG via groups.io wrote:
On Thu, Nov 21, 2024 at 07:56 PM, Ron NY3J wrote:
I am running Linux Mint 22 Cinnamon and Fldigi version 4.2.06.09
Ron,
?
Are you running Mint 22.0 or is it Mint 22.1?? I'm running Mint 22.1 and Fldigi 4.2.06.26 and have no problems.? I use Flrig 2.0.05.93 for rig control, and sometimes run two instances of Fldigi with no problems.? I'm using pulseaudio.? If I look at top, I see Fldigi uses less than 20% CPU, and mostly runs around 5%-10% range.
?
Perhaps you would benefit from upgrading to Mint 22.1 (if you are not already there), and build/install Fldigi 4.2.06.26.
?
It seems possible you are experiencing a USB sleep issue.? Here is a way to disable USB sleep at boot time:
?
?
You might also try setting the file /sys/module/usbcore/parameters/autosuspend to the contents of "-1" if it is not already set to that.
?
73,
-Joe-
K0OG
Re: Fldigi 4.2.06.26 on Linux (LMDE 6)

 

开云体育

Thanks Bob for the AFC info hints, all agreed with here.

This strange behaviour I only noticed in the later alpha releases for 4.2.06, I don’t recall experiencing any such weirdness before.

Thanks again and 73.

Dave G0WBX
Re: Fldigi 4.2.06.26 on Linux (LMDE 6)

 

开云体育

Kind of known/derived knowledge plus some of the manual Dave.

It is pointed out that Thor/Domino being IFK have a wide tuning margin. It follows then that FSQ/IFKP (also IFK) will have the same "feature". Olivia/Contestia have an adjustable tuning margin that can allow decoding somewhat away from the centre. (In real life though there seems to be some degradation on a low s/n signal)

OFDM/8PSK HAVE to use RSID (and/or the pilot tone) to centre the signal before their own and built in far more critical (phase locked) AFC is employed.

Multicarrier PSK doesn't appear to have a working AFC. RsID and the ability to lock RX/TX with an offset seems to works well for that. To me that is the only unanswered AFC question.

MFSK is known to be frequency critical and single carrier PSK performs similarly better . I tend to use the data scope for that. I have also noticed far more BPSK31 stations using RsID in the last few months. RTTY also has an adjustable AFC.

Not much left... I did notice some strange AFC button behaviour maybe a year ago, but not really using it I wasn't worried. Pretty sure I reported it (here) at the time.

Cheers Bob VK2YQA

On 29/3/25 00:16, Dave, G?WBX via groups.io wrote:

?
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.
?
Re: Fldigi 4.2.06.26 on Linux (LMDE 6)

 

Replying to my own posts ...? Not ideal but...
?
I crafted the last mail in the groups.io web page, while Fldigi was running in the background, with the "errant" disabled AFC control with "unlit" LED, but AFC observed to be active.
?
After I sent the last mail, and shutdown the browser (Firefox 136.0.2 64 bit) and restored Fldigi to front-of-house....
?
The AFC button was NOT greyed out any more, AND it was showing AFC active!? I.e.? The? "Green LED" is lit.
?
This is beyond my ability to debug.?? But I can follow instructions to gather information if so desired.
?
73.
??? Dave G0WBX.
?
?
Fldigi 4.2.06.26 on Linux (LMDE 6)

 

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.
?
?
Re: CQRLOG not opening

 

FYI
There is also in install script at
?
It is for Ubuntu but I guess that it would go also with Mint (not tested).
It does the job from beginning including MariaDB, no need to install any package versions of Cqrlog first.

Script installs first all dependencies and after that the latest official Cqrlog (the tgz file from cqrlog.com/download).
Then it offers direct update to CqrlogAlpha.
41 - 60 of 53997