Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1258250 - audacity fails to start - exits with code 255
Summary: audacity fails to start - exits with code 255
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: audacity
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Timms
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-30 14:41 UTC by Pete Houston
Modified: 2015-12-22 22:07 UTC (History)
3 users (show)

Fixed In Version: audacity-2.1.2-0.7.rc1.fc22 audacity-2.1.2-0.7.rc1.fc23
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-18 09:59:02 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Pete Houston 2015-08-30 14:41:59 UTC 
Description of problem:

Starting audacity from a shell prompt just returns the user to the prompt with no diagnostic messages at all. Exit code is 255. This happens even with "audacity -version" eg:

$ audacity -version
$ echo $?
255
$ 

Version-Release number of selected component (if applicable):

audacity 2.1.1-1.fc22

How reproducible:

Always.

Steps to Reproduce:

1. sudo dnf install audacity
2. audacity

Actual results:

audacity fails to start - no errors/warnings/diagnostics. Exits with error code 255 and control returns to the shell.

Expected results:

audacity starts and shell waits for it to finish.

Additional info:

Audacity does not start when run from menus in the display manager either (Gnome, Enlightenment)
Comment 1 Brent R Brian 2015-08-30 19:25:02 UTC 
works fine if you run it with sudo
Comment 2 Brent R Brian 2015-08-30 19:46:39 UTC 
also runs as user if you 

rm -rf .audacity-data
Comment 3 David Timms 2015-08-30 22:05:45 UTC 
Hi Brent, was this the first time you had installed Audacity on the machine ?

That is, is the .audacity-data folder what this version created, or from an earlier version, and if so what version ?
Comment 4 Pete Houston 2015-08-31 13:51:03 UTC 
Thanks Brent for the tip. I confirm that removing the old ~/.audacity-data directory solves the problem for me.

According to the old audacity.cfg file the previous version was 1.3.13-beta.
Comment 5 Fedora Update System 2015-11-21 12:17:16 UTC 
audacity-2.1.2-0.7.rc1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-51664dda77
Comment 6 Fedora Update System 2015-12-04 10:59:26 UTC 
audacity-2.1.2-0.7.rc1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-4320723725
Comment 7 Fedora Update System 2015-12-04 17:20:28 UTC 
audacity-2.1.2-0.7.rc1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update audacity'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-4320723725
Comment 8 Brent R Brian 2015-12-04 19:17:29 UTC 
(In reply to David Timms from comment #3)
> Hi Brent, was this the first time you had installed Audacity on the machine ?
> 
> That is, is the .audacity-data folder what this version created, or from an
> earlier version, and if so what version ?

The last version I used was from FEDORA 20 ... skipped F21 ... I keep the machine updated.
Comment 9 Fedora Update System 2015-12-18 09:58:47 UTC 
audacity-2.1.2-0.7.rc1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Comment 10 Fedora Update System 2015-12-22 22:07:17 UTC 
audacity-2.1.2-0.7.rc1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.