The debian report claims it's fixed in 0.9.5-5, but I am still seeing
the port grabbed as default behaviour in 0.9.9-4, shipped with Ubuntu
11.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/507247
It's fixed upstreams an in Debian:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586751
** Bug watch added: Debian Bug tracker #586751
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586751
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have filed bug #33846 against upower although in my experience the
upower maintainers have not been the most responsive. In the meantime,
can we please patch out this rule?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To clarify, that is a freedesktop.org bug[1].
[1] https://bugs.freedesktop.org//show_bug.cgi?id=33846
** Bug watch added: freedesktop.org Bugzilla #33846
http://bugs.freedesktop.org/show_bug.cgi?id=33846
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
also seems to cause problems for connection an arduino
** Changed in: devicekit-power (Ubuntu)
Status: New = Confirmed
--
devkit-power keeps /dev/ttyUSB0 open, misdetecting Watts-Up power monitor
https://bugs.launchpad.net/bugs/507247
You received this bug notification because you are a
the offending file rules file is now called /lib/udev/rules.d/95-upower-
wup.rules . deleting it allows me to program the arduino.
--
devkit-power keeps /dev/ttyUSB0 open, misdetecting Watts-Up power monitor
https://bugs.launchpad.net/bugs/507247
You received this bug notification because you
I am affected by this bug as well with a different device. I experience
identical behavior when I connect the serial console on a Gumstix Tobi
board to my Ubuntu Karmic installation. The problem was not present in
the previous version so this is a regression. I also have multiple
FTDI devices
Thank you for digging, the rules are indeed the problem.
I found the rule too, eventually, but as far as I can tell it's only documented
in the sources of the module.
As you say, the serial number is far too wide a match : devices with a
serial number in that range are widely used.
I would
Actually, the rules file is quite old. I'm not sure why it's only just
showeed up in this form, but I think some changes to usbserial have
affected the ability to have more than one application using the device.
This may have been there previously (or perhaps from the point where
devicekit took
