View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007417 | ardour | bugs | public | 2017-07-03 07:02 | 2017-07-03 12:55 |
| Reporter | michielderoo | Assigned To | |||
| Priority | low | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Linux | OS | KXStudio | OS Version | 14.10 |
| Product Version | 5.10 | ||||
| Summary | 0007417: Corrupted config | ||||
| Description | Ardour wouldn't start, giving the message: michiel@siderite:~$ /opt/Ardour-5.10.0/bin/ardour5 bind txt domain [gtk2_ardour5] to /opt/Ardour-5.10.0/share/locale Ardour5.10.0 (built using 5.10 and GCC version 4.4.7) ardour: [INFO]: Your system is configured to limit Ardour to only 65536 open files ardour: [INFO]: Loading system configuration file /opt/Ardour-5.10.0/etc/system_config ardour: [INFO]: Loading user configuration file /home/michiel/.config/ardour5/config liblrdf: error - - XML parser error: Specification mandate value for attribute sen liblrdf: error - - XML parser error: attributes construct error liblrdf: error - - XML parser error: Couldn't find end of Start Tag Configuration line 497 liblrdf: error - - XML parser error: Premature end of data in tag Configurations line 455 liblrdf: error - - XML parser error: Premature end of data in tag Protocol line 454 liblrdf: error - - XML parser error: Premature end of data in tag ControlProtocols line 443 liblrdf: error - - XML parser error: Premature end of data in tag Ardour line 2 ardour: [ERROR]: Ardour: cannot read configuration file "/home/michiel/.config/ardour5/config" ardour: [ERROR]: could not initialize Ardour. I checked the config file and it was corrupted, most likely because I closed Ardour while the disk was full. Removing the config file and starting Ardour recreated the default config file. Preferably, Ardour should not write the config file when there's not enough space on the device. Or otherwise, it should recreate the default config file on startup when it is corrupted. | ||||
| Tags | No tags attached. | ||||
|
|
Likely best solution: Save to a .tmp file first, then move/replace existing config (just like session-save). If the disk is full saving the .tmp will fail and previous config remains as-is. The same needs to happen for any file in the config-dir (instant.xml, ui_config, .colors, recent, plugin_statuses, ...) some centralized mechanism seems to be appropriate. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-07-03 07:02 | michielderoo | New Issue | |
| 2017-07-03 12:55 | x42 | Note Added: 0019863 |
