View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005889 | ardour | bugs | public | 2014-03-21 16:15 | 2014-03-22 22:31 |
| Reporter | oofus | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | i7 3770K 3.5GHz,16GB Memory | OS | Kubuntu | OS Version | 13.10 64bit |
| Summary | 0005889: Ardour should warn that a session is read only when it is opened, not just fail to save on close. | ||||
| Description | Ardour should warn that a session is read only when it is opened, not just fail to save on close. Using save from the file menu brings up an error in the log window, but it says something about not being able to copy the session file to the .bak file. This is not the same as reporting that the session file could not be saved, or is read only. After loading a session working on it for quite some time with a lot of changes, on quit I was just presented with a dialogue that said the session couldn't be saved, but with no explanation as to why. At this point it is too late, then work has been done and is about to be lost. If the error reported that the session file was read only then that could possibly be addressed and save attempted again, but the messages either aren't there or are vague at best. | ||||
| Tags | No tags attached. | ||||
|
|
It appears Ardour does already have mechanisms to deal with this. The issue here was a combination of an NTFS partition mounted using NTFS-3G and being accessed by gvfs (Ardour uses this for file access in some instances). It appears there is a bug somewhere in that combination. New files can be created and existing files can be written to, but existing files don't appear to be able to be copied. Ardour fails at this point during session save as the first thing it tries to do is copy the existing session file to the .bak backup. Once that fails session saving stops and a dialogue is displayed warning that saving was not possible. |
|
|
all GIO in ardour is gone since 3.5-1760-gba128ee (CairoCanvas branch). This should /fix/ this particular problem. Please confirm |
