Cura, serial port and lock files on linux - possible bug

[axsdenied 0]

Hi

I was printing from simplify3D (on linux) via USB to UM2 when I loaded Cura (15.06.01) to check another design. At startup Cura connected to the printer (which was already printing) which lead to head crashing into the right wall and the belt skipping and then the print resumed several centimeters to the side (in the air). While there was no damage to the printer, a 4h print was ruined.

I am not sure what Cura's default behaviour is but, as far as I know, Cura should not try to connect to a printer which is in use.

Simplify3D created the lock file var/lock/LCK..ttyACM0 meaning it needs exclusive access to the tty port. Cura should have checked for this file (and for the PID of the process which created it) before trying to connect to the printer. More details on serial port locking on linux can be found here. Unless I got everything wrong, cura should be following this.

Thoughts?

[nallath 1,021]

Could you (also) post this on the github issue tracker? Makes it easier to keep track.

Cura does not check the lock file as far as I can remember. To be honest, I wasn't even aware of it's existence, as I assumed that linux would handle this without my meddling (which makes way more sense imho).

[axsdenied 0]

Will post it on the github, have to make an account first.

By the way, on linux serial port is a terminal, just like text terminals. They don't get locked automatically on opening as, in some cases, it is useful to have access to a terminal from multiple programs. For example if you are using a text terminal and someone wants to send you a message. I can also see use of this for debugging devices connected via virtual serial port.