* Tobias Ellinghaus <[email protected]> [03-06-14 17:56]: > Am Donnerstag, 6. März 2014, 16:46:04 schrieb Patrick Shanahan: > > * Patrick Shanahan <[email protected]> [03-06-14 16:38]: [...] > > > If, as you allude, darktable compares it's pid to that contained in the > > > lock file and is supposed "make it's own correction", I am witness that > > > that does not always happen as I have had to remove the lock in able to > > > start darktable and istr that I started darktable from the cl and saw an > > > error msg announcing the existing lock file. > > > > Just tested and darktable did remove and replace the existing lock file, > > but I have had it fail in this recently. > > Interesting. I crash darktable at least a dozen times a day (sometimes on > purpose, sometimes by accident) while developing. And I never had that > happen. > It might very well be a bug. That's why I asked. Maybe I should add the > command that has the old PID to the message to help debug it.
I will be sure to record and relate conditions if and when I see it again. Tks much for your efforts. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
