Description of problem: FLDIGI crashes within seconds of opening. Tried changing tile_x and tile_y values in fldigi.prefs but crashes still occur although it appears to take a longer or shorter time before the crash, but it still crashes no matter what values I had changed. Version-Release number of selected component: fldigi-4.1.13-2.fc32 Additional info: reporter: libreport-2.13.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/gnome-launched-fldigi.desktop-6560.scope cmdline: fldigi crash_function: diediedie executable: /usr/bin/fldigi journald_cursor: s=825b5e5c4e7b4c0fb6c08046198f9fe8;i=1dc900;b=49620e2bd4b146eba4149477bf473665;m=fe803f7b;t=5b0049e7a9528;x=f455c74d33a5129a kernel: 5.8.10-200.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1716178 [details] File: backtrace
Created attachment 1716179 [details] File: core_backtrace
Created attachment 1716180 [details] File: cpuinfo
Created attachment 1716181 [details] File: dso_list
Created attachment 1716182 [details] File: environ
Created attachment 1716183 [details] File: exploitable
Created attachment 1716184 [details] File: limits
Created attachment 1716185 [details] File: maps
Created attachment 1716186 [details] File: mountinfo
Created attachment 1716187 [details] File: open_fds
Created attachment 1716188 [details] File: proc_pid_status
Created attachment 1716189 [details] File: var_log_messages
This looks to be either Portaudio or Pulse Audio related. I would try renaming your ~/.fldigi/fldigi.prefs (or whatever it's called) and re-set things up. If you can still reproduce the problem I'll reach out to the author.
Similar problem has been detected: In response to instructions in Bug 1882175, deleted entire .fldigi folder path and dnf reinstalled fldigi. Crash occurred while trying to set up TCP control to flrig running correctly on another Fedora machine that is also connected to the radio. reporter: libreport-2.13.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/gnome-launched-fldigi.desktop-5542.scope cmdline: fldigi crash_function: diediedie executable: /usr/bin/fldigi journald_cursor: s=825b5e5c4e7b4c0fb6c08046198f9fe8;i=1e0e1c;b=50d3b0e80ee34408b05fab5f27ce2c0f;m=5dd3cc36;t=5b0250e797783;x=64519df37fac41e1 kernel: 5.8.10-200.fc32.x86_64 package: fldigi-4.1.13-2.fc32 reason: fldigi killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
In an email response, had added the following information: I deleted the entire .fldigi folder path and dnf reinstalled fldigi. It let me go through the setup, but I was unable to get it to initialize with my Yaesu FT-450D radio through the SignaLink interface. That's likely me not yet knowing how to set up fldigi, and it crashed again. I was trying to get it to connect via TCP to the working flrig on another Fedora machine that is separately connected to the radio and works to the extent that flrig works with an FT-450D. I let abrt generate a new backtrace from the latest crash in case that might provide some additional information. That was entered separately above to this bug.
Obviously it should crash... But have you confirmed you can connect? I'm assuming you're running the standard workstation profile for FirewallD which allows connections over port 1000 by default.
That was supposed to be "shouldn't crash"... Any progress to report?
(In reply to Richard Shaw from comment #17) > That was supposed to be "shouldn't crash"... > > Any progress to report? A short update: fldigi is working on my Fedora laptop, and it can decode RTTY and CW (I haven't yet found which of the many different digital encoding methods the other stations are using). However, I have not yet been able to find a way for the Hamlib interface to key the transmitter; I've tried all of the /dev/tty connections it sees, and there are no other options to pick from; still working on that (/dev/ttyUSB0 doesn't show up in the fldigi pull-down list). Also yet to do is run to ground the TCP connection to flrig on the other Fedora machine. However, I think you can close the bug about fldigi crashing; let me know if you'd like me to post that on the Bugzilla site directly. Thanks, Mark
FEDORA-2020-f7922c404d has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f7922c404d
FEDORA-2020-fb9399a75a has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-fb9399a75a
FEDORA-EPEL-2020-edab67d2d9 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-edab67d2d9
FEDORA-2020-c8eb74407c has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c8eb74407c
FEDORA-2020-c8eb74407c has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-c8eb74407c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c8eb74407c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-fb9399a75a has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-fb9399a75a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fb9399a75a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-edab67d2d9 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-edab67d2d9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-f7922c404d has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f7922c404d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f7922c404d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-6cdc6bf610 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6cdc6bf610 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-fbf4c1b0fd has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-fbf4c1b0fd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fbf4c1b0fd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-c9192fc3b2 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-c9192fc3b2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c9192fc3b2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-c8eb74407c has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-fbf4c1b0fd has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-c9192fc3b2 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-6cdc6bf610 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.