Bug#1079942: closed by Christoph Berg (Re: Bug#1079942: wsjtx: crash when trying to use superfox, missing sfrx binary)

2024-08-28 Thread John Flinchbaugh
ristoph Berg < > m...@debian.org> by > replying to this email. > > > -- > 1079942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079942 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > -- Forwarded

Bug#1079942: wsjtx: crash when trying to use superfox, missing sfrx binary

2024-08-28 Thread John Flinchbaugh
Package: wsjtx Version: 2.7.0~rc6+dfsg-1 Severity: important X-Debbugs-Cc: j...@hjsoft.com Dear Maintainer, wsjtx package seems to be missing the sfrx binary for the new superfox mode. Start up wsjtx. go into settings -> advanced -> special operating activity -> ( ) hound -> [ ] superfox, and s

Bug#895237: log of apache2 failing to start from certbot renewal

2024-02-07 Thread John Flinchbaugh
00:00 app01 systemd[1]: certbot.service: Consumed 3.925s CPU time. -- John Flinchbaugh j...@hjsoft.com

Bug#1051805: systemd-cron: shell redirect not working in crontab entries

2023-09-12 Thread John Flinchbaugh
Package: systemd-cron Version: 2.1.2-1 Severity: normal Dear Maintainer, I can put a simple command with a redirect to a file or /dev/null, and systemd-cron continues to email the output of the command. See the following excerpt from the email, which shows the command I'm running: Proces

Bug#678341: Digikam crashes when trying to adjust timestamp or geo tag of an image

2012-06-22 Thread John Flinchbaugh
Package: digikam Version: 4:2.6.0-1 Followup-For: Bug #678341 I see this error as well in unstable. Here's the KDE crash log: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fda

Bug#669387: digikam: upgrades database from v5 to v6 first time, then tries again and fails on next launch

2012-04-19 Thread John Flinchbaugh
Package: digikam Version: 4:2.6.0~beta3-1 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this

Bug#604394: tar: --listed-incremental and --one-file-system result in no files being included

2010-11-21 Thread John Flinchbaugh
Package: tar Version: 1.25-2 Severity: important My backup scripts stopped picking up files, so I had a look. Simplified, I found that combining --one-file-system and --listed-incremental now causes it to not find any files. Removing either of these makes the command work again. butterfly:/etc