Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 1622 - Cryptic error message when existing project cannot be saved
Cryptic error message when existing project cannot be saved
Status: RESOLVED FIXED
Product: Audacity
Classification: Unclassified
Component: User Interface
2.2.0
Per OS All
: P3 RepeatableAll
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-29 00:53 UTC by Gale Andrews
Modified: 2019-09-01 14:38 UTC (History)
7 users (show)

See Also:
Steps To Reproduce:
1 Create a new subfolder on a drive. 2 Create some audio, save the project to the new subfolder, then close the project. 3 Disable write access for the subfolder e.g. on the Security tab of the Windows Properties of the subfolder. This might e.g. mimic a USB drive where write protection had been turned on. 4 Open the project, Add a new track (which appears to work because the waves are not affected in the existing track). 5 Save Project. After about 5 seconds, an unhelpful message is returned "Could not create safety file: <path>\<project name>.aup.bak." On Linux a tilde is appended instead of .bak. 6 The message may especially confuse those who remember that we stopped writing aup.bak as an openable project backup a long time ago. This is worse than the previous message in 2.1.3 release which was "Couldn't write to file <path to aup file>: Error opening file." However after OK'ing that message, 2.1.3 deletes the AUP file (!). At least 2.2.0-alpha does not do that. 7 The log in 2.2.0-alpha shows (in my case on Windows): <time> Error: Failed to copy the file 'S:\Newr\newr.aup' to 'S:\Newr\newr.aup.bak' (error 5: access is denied.) <time> Error: File 'S:\Newr\newr.aup' couldn't be renamed 'S:\Newr\newr.aup.bak' (error 0: the operation completed successfully.)
Release Note:
GROUP: Projects * '''If you try to save changes to an already saved project but the save fails, for example due to write error or write protection, only a cryptic error is displayed:''' "Could not create safety file: <path>\<project name>.aup.bak" (or aup~ on Linux).
First Git SHA:
Group: ---
Workaround:
Closed: 2019-09-01 00:00:00


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gale Andrews 2017-03-29 00:53:04 UTC
A data loss problem is found in 2.1.3 release, but it has already been fixed. See Steps to Reproduce.
Comment 1 Peter Sampson 2018-02-13 07:33:00 UTC
Testing with 2.2.2 RC1 on W10 and macOS 10.13.3 High Sierra
Tested using a USB clip drive  - with h/w write protection at step 3

We seem to have improved the situation for the use case in the Steps to reproduce - as when recording at Step 4 when the Stop button is pressed you now get the error message (and the apparent new audio is removed, visually):
>File Error:
>Audacity failed to write to a file
>Perhaps <device> is not writable or the disk is full

I suspect that this change may be down to Paul's disk-full error trapping that was added recently.



However if you then move to step 5 and try to Save Project - you still get the same "unhelpful" error message:
>"Could not create safety file: ... "

At this juncture it would be *much* better for the user to see the message
>Audacity failed to write to a file
>Perhaps <device> is not writable or the disk is full
Comment 2 Peter Sampson 2018-02-13 07:36:15 UTC
Curiously if you then remove the USB clip and then try to Save Project you do get:
>File Error:
>Audacity failed to write to a file
>Perhaps <device> is not writable or the disk is full
Comment 4 Peter Sampson 2019-09-01 14:38:41 UTC
(In reply to James Crook from comment #3)
Tested on W10 with audacity-2.3.3-alpha-341-72f36f8a82e9ed4a184b9029cb53780e62a9bea8

Tested using a USB thumb-drive and using the write-protect.

You now get a sensible useful error message telling you that the device may be locked or unavailable.