sox crashed with SIGFPE

Bug #1821700 reported by DougieFresh4U
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
sox (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Has something to do with older packages:
gnome-schedule
saytime

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: sox 14.4.2-3
Uname: Linux 5.1.0-999-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 26 02:30:01 2019
ExecutablePath: /usr/bin/sox
InstallationDate: Installed on 2019-01-24 (60 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: sox -r 8000 -q -v 1 -t.ul -c 1 /usr/share/saytime/the_time_is.au -d
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/sh
Signal: 8
SourcePackage: sox
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/sox/libsox_fmt_ao.so
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: sox crashed with SIGFPE
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

Revision history for this message
DougieFresh4U (butcheeyboy) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 startwrite (ft=0x7ffe1a2573c0) at ao.c:38
 try_device (name=0x557b3474c7dc "ao") at sox.c:2547
 set_default_device (f=<optimized out>) at sox.c:2569
 parse_options_and_filenames (argc=11, argv=0x7ffe1a257cc8) at sox.c:2662
 main (argc=11, argv=0x7ffe1a257cc8) at sox.c:2885

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in sox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sox (Ubuntu):
status: New → Confirmed
Revision history for this message
PabloAB (pabloab777) wrote :

This crash seems to be produced by something like `invalidCommand | /usr/bin/play -t mp3 -`. I was using it with gtts-cli inside crontab.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.