K3b fails to detect sox

Bug #1076310 reported by Colin Mills
32
This bug affects 4 people
Affects Status Importance Assigned to Milestone
k3b
Fix Released
Medium
k3b (Debian)
Fix Released
Unknown
k3b (Ubuntu)
Fix Released
Undecided
Unassigned
Quantal
Won't Fix
Medium
Unassigned

Bug Description

The current version of k3b in Quantal (2.0.2-5ubuntu1) fails to detect the sox package. To reprodce:-
open k3b
Open 'Settings'
Open 'Configure k3b'
Select 'programs'
Select sox

k3b reports that sox is not found.

This bug only occurs in k3b version 2.0.2-5ubuntu1. The bug is not present in the Precise version (2.0.2-3ubuntu4) or the most recent Raring version (2.0.2-6ubuntu1)

Revision history for this message
In , Janet (bugzilla-kerridis) wrote :

Although sox package is installed (Debian Sid, sox --version: sox: SoX v14.4.0) k3b reports "not found". sox executable is in /usr/bin. I tried reinstalling but that did not change anything.

Reproducible: Always

Revision history for this message
In , Pino Toscano (pinotree) wrote :

Git commit 2b672a2928d57b1132644ee4da1d6c664050bce1 by Pino Toscano.
Committed on 08/07/2012 at 22:20.
Pushed by pino into branch '2.0'.

fix sox detection with sox >= 14.4.0

sox 1.14.0 changed the string that is printed out on --version, breaking the simply string matching done;
add a new case to cover also this new version

(cherry picked from commit 79cd49cac3a6b7031556aae53ce3ecff8c360cb9)

M +3 -0 plugins/encoder/sox/k3bsoxencoder.cpp

http://commits.kde.org/k3b/2b672a2928d57b1132644ee4da1d6c664050bce1

Revision history for this message
In , Pino Toscano (pinotree) wrote :

Git commit 79cd49cac3a6b7031556aae53ce3ecff8c360cb9 by Pino Toscano.
Committed on 08/07/2012 at 22:20.
Pushed by pino into branch 'master'.

fix sox detection with sox >= 14.4.0

sox 1.14.0 changed the string that is printed out on --version, breaking the simply string matching done;
add a new case to cover also this new version

M +3 -0 plugins/encoder/sox/k3bsoxencoder.cpp

http://commits.kde.org/k3b/79cd49cac3a6b7031556aae53ce3ecff8c360cb9

Revision history for this message
Tshering Namgyal Wangdi (drwangdi) wrote :

sox(not found) by k3b in kubuntu 12.10 64 bit quantal even after installing from Package Manager.

System - Dell Inspiron N5050
Processor Intel Pentium(R) CPU B960 @ 2.2 GHz
2 Gb RAM

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in k3b (Ubuntu):
status: New → Confirmed
Micah Gersten (micahg)
tags: added: quantal regression-release
Changed in k3b (Ubuntu Quantal):
status: New → Triaged
importance: Undecided → Medium
Changed in k3b (Ubuntu):
status: Confirmed → Fix Released
Changed in k3b:
importance: Unknown → Medium
status: Unknown → Fix Released
Changed in k3b (Debian):
status: Unknown → Fix Released
Revision history for this message
Uqbar (uqbar) wrote :

Fix released? When? Where?

Revision history for this message
Uqbar (uqbar) wrote :

I have a proposal for a workaround similar to the one already in use for normalize-audio.
As root:
1. mv /usr/bin/sox /usr/bin/sox.org
2. with your text editor create the file /user/bin/sox like this one:
#/bin/bash
case "$1" in
        --version)
       sox.orig --version | sed -e 's/sox.orig: SoX v/sox: Version/g'
        ;;
        *)
        sox.orig $*
        ;;
esac

I've checked the mentioneed patch by Pino Torscano (grazie, Pino!) and it works now.
I don't want to discuss who broke what. It's simply a shame that this happened twice to the same package (that is K3b).

Revision history for this message
dgharmon (dgharmon0-deactivatedaccount) wrote :

re: mv /usr/bin/sox /usr/bin/sox.org

Shouldn't that be sox.orig, and k3b still reports sox (not found)

Revision history for this message
Uqbar (uqbar) wrote :

Yes, it'a typo. The workaound actually works the bug around when you fix the typo.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

Changed in k3b (Ubuntu Quantal):
status: Triaged → Won't Fix
Revision history for this message
Uqbar (uqbar) wrote :

This is the right way to do things. It's called the ostrich policy.
If you wait long enough, the problem will vanish or make no sense any more.
From time to time I am getting notifications like this.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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