Re: [Rosegarden-user] QLockFile Problem (was: Project Lock file)
> What package is qlockfile in? Although presumably it wouldn't compile if it's > missing. It certainly wouldn't. That's in the Qt headers and libs package. Usually called something with "dev". Like qtbase5-dev. Ted. On 6/21/21 8:30 PM, Will Godfrey wrote: For the sake of completeness, this is on devuan beowulf (equivalent to debian buster without systemD) It seems to be running qt 5.11 although there seem to be a lot of bits of qt4 in there as well. I'm seeing this issue on fairly recent builds of master. What package is qlockfile in? Although presumably it wouldn't compile if it's missing. On Mon, 21 Jun 2021 18:11:17 -0400 Ted Felix wrote: This is odd. I thought the lock mechanism we're using (QLockFile) was keyed on process ID. Therefore it should go away automatically when it realizes that process is no longer running. Or something like that. I've changed the subject to hopefully get David Faure's attention. QLockFile is his. Hopefully he has some insight as to why you might be having so much trouble with it. Works great for me. Even if rosegarden crashes (and I crash it all the time) I am never locked out of a file since we switched to QLockFile. Ted. On 6/21/21 6:18 AM, Will Godfrey wrote: I would like to suggest moving these into /tmp That way, when restarting the computer they will be cleared. I've got something like 300 different projects on my 'music' computer and often get blocked when loading projects I've not run for some time, and then have to hunt out the file. I have no idea why the lock wasn't cleared, but it is quite obvious that a project can't still be open over a reboot! ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] QLockFile Problem (was: Project Lock file)
For the sake of completeness, this is on devuan beowulf (equivalent to debian buster without systemD) It seems to be running qt 5.11 although there seem to be a lot of bits of qt4 in there as well. I'm seeing this issue on fairly recent builds of master. What package is qlockfile in? Although presumably it wouldn't compile if it's missing. On Mon, 21 Jun 2021 18:11:17 -0400 Ted Felix wrote: > This is odd. I thought the lock mechanism we're using (QLockFile) >was keyed on process ID. Therefore it should go away automatically when >it realizes that process is no longer running. Or something like that. > > I've changed the subject to hopefully get David Faure's attention. >QLockFile is his. Hopefully he has some insight as to why you might be >having so much trouble with it. > > Works great for me. Even if rosegarden crashes (and I crash it all >the time) I am never locked out of a file since we switched to QLockFile. > >Ted. > >On 6/21/21 6:18 AM, Will Godfrey wrote: >> I would like to suggest moving these into /tmp >> That way, when restarting the computer they will be cleared. >> >> I've got something like 300 different projects on my 'music' computer and >> often >> get blocked when loading projects I've not run for some time, and then have >> to >> hunt out the file. I have no idea why the lock wasn't cleared, but it is >> quite >> obvious that a project can't still be open over a reboot! >> > > >___ >Rosegarden-user mailing list >Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe >https://lists.sourceforge.net/lists/listinfo/rosegarden-user -- Will J Godfrey https://willgodfrey.bandcamp.com/ http://yoshimi.github.io Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] QLockFile Problem (was: Project Lock file)
This is odd. I thought the lock mechanism we're using (QLockFile) was keyed on process ID. Therefore it should go away automatically when it realizes that process is no longer running. Or something like that. I've changed the subject to hopefully get David Faure's attention. QLockFile is his. Hopefully he has some insight as to why you might be having so much trouble with it. Works great for me. Even if rosegarden crashes (and I crash it all the time) I am never locked out of a file since we switched to QLockFile. Ted. On 6/21/21 6:18 AM, Will Godfrey wrote: I would like to suggest moving these into /tmp That way, when restarting the computer they will be cleared. I've got something like 300 different projects on my 'music' computer and often get blocked when loading projects I've not run for some time, and then have to hunt out the file. I have no idea why the lock wasn't cleared, but it is quite obvious that a project can't still be open over a reboot! ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
