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

Audacity Bugzilla



Bug 2732 - Faux recovery offered on launch (very moonphase)
Faux recovery offered on launch (very moonphase)
Status: RESOLVED FIXED
Product: Audacity
Classification: Unclassified
Component: Application Core
3.0.0
All All
: P3 MoonPhase
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2021-04-03 11:54 UTC by Peter Sampson
Modified: 2021-05-30 14:36 UTC (History)
11 users (show)

See Also:
Steps To Reproduce:
1) launch Audacity 3.0.x 2) observe no recovery offered 3) get some audio 4) make some edits 5) Exit Audacity 6) Don't save project when this is offered 7) relaunch Audacity 3.0.1 8) Observe: Faux recovery dialog (see attachment)
Release Note:
Group: Recovery *On rare occasions when launching Audacity you may be offered a false Recovery when you know full well there was no prior crash of Audacity yo induce this. We think this usually occurs if you relaunch Audacity after having previously exited Audacity without accepting the offer to save the project.
First Git SHA:
Group: ---
Workaround:
Just discard the offered recovery (providing you are absolutely sure that there is no real project to recover). If instead you accept the recovery offered an empty project will be "recovered"
Closed: 2021-05-30 00:00:00
petersampsonaudacity: Regression+


Attachments
Faux specious recovery dialog (164.74 KB, image/png)
2021-04-03 11:54 UTC, Peter Sampson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Sampson 2021-04-03 11:54:52 UTC
Created attachment 1135 [details]
Faux specious recovery dialog

Sometimes after exiting Audacity without saving the project when offered  - on the next relaunch a faux, specious, recovery can be offered.

If you accept this recovery it "recovers" an empty project.

This is thought to be a possible close cousin to Bug #2700
>"Failed to open the project database"

This is extremely moonphase and happens very rarely - and no damage to data appears to be caused for any of the few users who have reported this. 

I have marked this a a regression as this has not happened in 2.4.2 or earlier Audacities
Comment 1 Steve Daulton 2021-04-03 20:48:51 UTC
Another report here: https://forum.audacityteam.org/viewtopic.php?p=421803#p421803
Comment 2 Peter Sampson 2021-04-04 09:01:50 UTC
And I just got another one just now after installing and launching 
latest alpha Audacity 3.0.0 19df017   :-//
Comment 3 Peter Sampson 2021-04-10 14:14:05 UTC
This is very rare - and we think may yet be "fixed" by the "fixes" for Bug #2700

No data is lost as a result of this bug.

Accordingly I have reduced this to P3 and added a Release Note and a Workaround.
Comment 4 Paul L 2021-04-10 18:02:43 UTC
(In reply to Peter Sampson from comment #3)

I am not yet convinced it had a common cause with 2700.  I have not studied the problem enough.
Comment 5 Peter Sampson 2021-05-19 10:09:10 UTC
We are not seeing reports of this with 3.2.0
Comment 6 Peter Sampson 2021-05-30 14:36:48 UTC
With 3.0.2 we are no lonfer seeing repoerts of this from users.  And I am not seeing this is any of my 3.0.3 alpha testing.

Accordibgly I shall close this bug