Due to this Chrome bug https://code.google.com/p/chromium/issues/detail?id=354782, serial connections fail on some linux setups (might be related to udev version, not entirely clear yet). This bug only occurs on Chrome 34 and up, since then they switched to use udev for enumerating serial devices.
The problem is that the device enumeration returns e.g., ttyACM0, while serial.connect expects /dev/ttyACM0.
This is not something we can fix, though we could add a workaround if it turns out this affects a lot of people (e.g. add /dev/ when on Linux and it is not present yet or something like that).
Due to this Chrome bug https://code.google.com/p/chromium/issues/detail?id=354782, serial connections fail on some linux setups (might be related to udev version, not entirely clear yet). This bug only occurs on Chrome 34 and up, since then they switched to use udev for enumerating serial devices.
The problem is that the device enumeration returns e.g.,
ttyACM0, whileserial.connectexpects/dev/ttyACM0.This is not something we can fix, though we could add a workaround if it turns out this affects a lot of people (e.g. add
/dev/when on Linux and it is not present yet or something like that).