Version-Release number of selected component: sox-14.4.2rc2-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: play -q /home/syl/freedos/vgacpy6/vgacpy3.voc crash_function: startwrite executable: /usr/bin/sox global_pid: 3852 kernel: 4.0.4-301.fc22.x86_64 runlevel: N 5 type: CCpp uid: 500 var_log_messages: [System Logs]:\n-- Logs begin at mer. 2014-07-30 15:01:01 CEST, end at sam. 2015-05-30 17:01:01 CEST. -- Truncated backtrace: Thread no. 1 (4 frames) #0 startwrite at ao.c:39 #1 try_device at sox.c:2547 #2 set_default_device at sox.c:2569 #3 parse_options_and_filenames at sox.c:2681
Created attachment 1032906 [details] File: backtrace
Created attachment 1032907 [details] File: cgroup
Created attachment 1032908 [details] File: core_backtrace
Created attachment 1032909 [details] File: dso_list
Created attachment 1032910 [details] File: environ
Created attachment 1032911 [details] File: limits
Created attachment 1032912 [details] File: maps
Created attachment 1032913 [details] File: mountinfo
Created attachment 1032914 [details] File: namespaces
Created attachment 1032915 [details] File: open_fds
Created attachment 1032916 [details] File: proc_pid_status
Hi. Thank you for your report. Could you please publish vgacpy3.voc? It seems that ao.c:38 ao->buf_size = sox_globals.bufsiz - (sox_globals.bufsiz % (ft->encoding.bits_per_sample >> 3)); divides by zero in your case but I can not reproduce the crash.
(In reply to Frantisek Kluknavsky from comment #12) > Hi. Thank you for your report. Could you please publish vgacpy3.voc? > It seems that ao.c:38 > ao->buf_size = sox_globals.bufsiz - (sox_globals.bufsiz % > (ft->encoding.bits_per_sample >> 3)); > divides by zero in your case but I can not reproduce the crash. Sure. This is one sound from Vga-copy. http://www.moenk.de/pages/vgacopy.html
Created attachment 1034437 [details] Vgacopy welcome! sound
Still does not crash, plays "welcome" sound and then displays an error message "play FAIL sox: `vgacpy3.voc' premature EOF: Numerical result out of range". (Fedora 22 Workstation in a virtual machine) Will try harder tomorrow.
It happens on Fedora 23. Steps to reproduce: -Stop pulseaudio (pulseaudio -k) -Run "play vgacpy3.voc", -q option is irrelevant.
*** Bug 1309426 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
It happens on Fedora 24. Steps to reproduce: -Stop pulseaudio (pulseaudio -k) -Run "play vgacpy3.voc", -q option is irrelevant.
After changing hardware once and changing Fedora several times, I still can not reproduce it. The closest thing I achieved was a freeze after `pasuspender -- play vgacpy3.voc`. Sorry.
Finally, I found how to reproduce it, but only in mock: $ mock -r fedora-rawhide-x86_64 --init $ mock -r fedora-rawhide-x86_64 --install ./x86_64/sox-14.4.2.0-20.fc29.x86_64.rpm $ mock -r fedora-rawhide-x86_64 --copyin ~/Downloads/vgacpy3.voc /var/tmp $ mock -r fedora-rawhide-x86_64 --shell INFO: mock.py version 1.4.9 starting (python version = 3.6.4)... Start: init plugins INFO: selinux disabled Finish: init plugins Start: run Start: chroot init INFO: calling preinit hooks INFO: enabled root cache INFO: enabled dnf cache Start: cleaning dnf metadata Finish: cleaning dnf metadata INFO: enabled HW Info plugin Finish: chroot init Start: shell <mock-chroot> sh-4.4# play /var/tmp/vgacpy3.voc Home directory not accessible: Permission denied ALSA lib confmisc.c:767:(parse_card) cannot find card '0' ALSA lib conf.c:4555:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4555:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name ALSA lib conf.c:4555:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:5034:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2565:(snd_pcm_open_noupdate) Unknown PCM default Floating point exception (core dumped) <mock-chroot> sh-4.4# There are also another types of errors that not appear on non-mock environment, but the main point is that `ft->encoding.bits_per_sample` is zero when entering `startwrite`, which caused division by zero. (For now, I am not able to say what _exactly_ cause the exception. It looks like an issue with HW configuration/access from the mock side.)
Created attachment 1447781 [details] fedora-rawhide-x86_64.cfg Added mock config file
*** Bug 1492910 has been marked as a duplicate of this bug. ***
*** Bug 1540762 has been marked as a duplicate of this bug. ***
sox-14.4.2.0-21.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-e85437f88d
sox-14.4.2.0-21.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-0e80a87457
sox-14.4.2.0-21.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-0e80a87457
sox-14.4.2.0-21.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-e85437f88d
sox-14.4.2.0-22.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-57a9f93beb
sox-14.4.2.0-22.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-f7a1334c68
sox-14.4.2.0-22.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-57a9f93beb
sox-14.4.2.0-22.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-f7a1334c68
sox-14.4.2.0-22.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
sox-14.4.2.0-22.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.