On 01/10/2018 09:17 PM, david wrote:
On 01/10/2018 07:59 AM, Will Godfrey wrote:
On Wed, 10 Jan 2018 08:40:55 -0500
Ted Felix <ted@xxxxxxxxxxxx> wrote:
On 01/10/2018 02:46 AM, david wrote:
Was completely unable to duplicate the problem.
Must have been the phases of the moon or something. Thanks for
fixing it
quantum-mechanics-style simply by turning your attention toward it! :)
Ha! Computers are afraid of me.
Lock file problems tend to happen when rg crashes. My best guess is
that it was crashing when it was going down and now it isn't.
Ted.
Another way that's caught me (rather more often than I'd like to
admit) is
shutting down the desktop, without first shutting down Rosegarden.
Didn't do that!
Wasn't there some discussion on adding some kind of time stamp to the
lock
file, so that it will ignore one that was (say) over 24 hour old.
I don't remember if there was a timestamp in the orphaned lockfile, but
it clearly wouldn't have been over 24 hours old.
A thought occurred to me: When RG opens a project and finds a lockfile,
maybe have the dialog box that informs the user a lockfile exists give
them a warning about possible consequences with an option to delete the
lockfile?
Then if something gets messed up because 2 different RG sessions have
the same project open, it's because the user chose to do it.
--
David W. Jones
gnome@xxxxxxxxxxxxx
authenticity, honesty, community
http://dancingtreefrog.com
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
https://lists.linuxaudio.org/listinfo/linux-audio-user
