Hi,
I've an USB-Serial adapter.
Due to the rule in /lib/udev/rules.d/95-upower-wup.rules, it is grabbed by
upowerd.
It appears that the IDS (vendorID/ProductID) in that rule is wrong.
My USB-Serial adapter has 0043:6001 which is reported by lsusb as Future
Technology Devices International, Ltd.
In the udev rule, we find: Watts Up, Inc.
Output of lsusb:
Bus 004 Device 002: ID 0403:6001 Future Technology Devices International, Ltd
FT232 USB-Serial (UART) IC
Contents of the usb rule:
SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="0403",
ATTRS{idProduct}=="6001", ATTRS{serial}=="A80?????", ENV{UPOWER_VENDOR}="Watts
Up, Inc.", ENV{UPOWER_PRODUCT}="Watts Up? Pro", ENV{UP_MONITOR_TYPE}="wup"
http://www.linux-usb.org/usb.ids is consistant with my lsusb output.
Regards
Jean-Luc
- -- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (900, 'unstable'), (700, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.34-k8-2 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages upower depends on:
ii dbus 1.2.24-1 simple interprocess messaging syst
ii libc6 2.11.2-1 Embedded GNU C Library: Shared lib
ii libdbus-1-3 1.2.24-1 simple interprocess messaging syst
ii libdbus-glib-1-2 0.86-1 simple interprocess messaging syst
ii libglib2.0-0 2.24.1-1 The GLib library of C routines
ii libgudev-1.0-0 157-1 GObject-based wrapper library for
ii libpolkit-gobject-1-0 0.96-2 PolicyKit Authorization API
ii libupower-glib1 0.9.4-2 abstraction for power management -
ii libusb-0.1-4 2:0.1.12-15 userspace USB programming library
ii udev 157-1 /dev/ and hotplug management daemo
Versions of packages upower recommends:
ii pm-utils 1.3.0-2 utilities and scripts for power ma
ii policykit-1 0.96-2 framework for managing administrat
upower suggests no packages.
- -- no debconf information
iD8DBQFMIHVBUdGGXzzGnNARAtbrAJ9ULxHZY0OC/YHvDuYG51uIyoVUpACgoXgC
qd85K1ZU3ywQYMUjSPh6WW4=
=LVEj
-----END PGP SIGNATURE-----
Hi Jean-Luc, I had a short discussion with the upstream developer of upower, Richard Hughes, on IRC. I'll copy it here for reference. You can see that the problem apparently is, that the watts up pro device uses a generic usb->serial dongle. You can get the daemon log, by switching to root, killing the running upowerd process and then starting it manually via "/usr/lib/upower/upowerd -v" Please attach that log file to the bug report. Thanks, Michael
Hi Michael, Le 17/09/2010 17:15, Michael Biebl a écrit : [ ...] "generic device" is not the property by Watt-thing... I've done the following: 1 - start minicom and try to use my serial-USB adapter. I get: [jean-luc@tangerine] % minicom minicom: cannot open /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A800c7v9-if00-port0: Device or resource busy 2 - I looked what is the real device related to the indicated id: [jean-luc@tangerine] % ls -l /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A800c7v9-if00-port0 lrwxrwxrwx 1 root root 13 17 sept. 17:37 /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A800c7v9-if00-port0 -> ../../ttyUSB0 3 - And who "owns" the device to render it "busy": jean-luc@tangerine] % sudo lsof | grep ttyUSB0 upowerd 2514 root 11u CHR 188,0 0t0 4703 /dev/ttyUSB0 This is why I said upowerd was the "culprit". As you asked, I've killed upowerd. --> this way, I can normally access my device via minicom as usual. Then I've startd upowerd -v and replugged the USB line. Here is the related part of the log: TI:18:29:54 FI:up-device-list.c FN:up_device_list_insert,94 - added /sys/devices/pci0000:00/0000:00:12.1/usb4/4-1/4-1:1.0/ttyUSB0/tty/ttyUSB0 TI:18:29:54 FI:up-daemon.c FN:up_daemon_device_added_cb,900 - emitting added: /org/freedesktop/UPower/devices/monitor_ttyUSB0 (during coldplug 0) TI:18:30:04 FI:up-device-wup.c FN:up_device_wup_poll_cb,90 - Polling: /org/freedesktop/UPower/devices/monitor_ttyUSB0 TI:18:30:04 FI:up-device-wup.c FN:up_device_wup_parse_command,211 - no start char in ^^3<86><CE><F8><86><98>f<F0>^N<C0>^X<F3>^X TI:18:30:04 FI:up-device-wup.c FN:up_device_wup_refresh,411 - failed to parse ^^3<86><CE><F8><86><98>f<F0>^N<C0>^X<F3>^X TI:18:30:15 FI:up-device-wup.c FN:up_device_wup_poll_cb,90 - Polling: /org/freedesktop/UPower/devices/monitor_ttyUSB0 TI:18:30:15 FI:up-device-wup.c FN:up_device_wup_parse_command,211 - no start char in ^X<CF>3<98><86><98> TI:18:30:15 FI:up-device-wup.c FN:up_device_wup_refresh,411 - failed to parse ^X<CF>3<98><86><98> TI:18:30:25 FI:up-device-wup.c FN:up_device_wup_poll_cb,90 - Polling: /org/freedesktop/UPower/devices/monitor_ttyUSB0 But once I've killed upowerd, then the device is free again. I tried to restart dbus, but it is not really kind with the system... Regards Jean-Luc
Okay, so upower is failing to detect the coldplug properly. Can you try applying 163d5fc355670722ce45893e5af60ea4bde06a82 and rebuilding upower and retrying with your device? Thanks. Richard.
Jean-Luc, if you need help with getting upower built with this patch or you need binary packages, let me know. Michael
We believe that the bug you reported is fixed in the latest version of
upower, which is due to be installed in the Debian FTP archive:
libupower-glib-dev_0.9.5-5_i386.deb
to main/u/upower/libupower-glib-dev_0.9.5-5_i386.deb
libupower-glib1_0.9.5-5_i386.deb
to main/u/upower/libupower-glib1_0.9.5-5_i386.deb
upower-doc_0.9.5-5_all.deb
to main/u/upower/upower-doc_0.9.5-5_all.deb
upower_0.9.5-5.diff.gz
to main/u/upower/upower_0.9.5-5.diff.gz
upower_0.9.5-5.dsc
to main/u/upower/upower_0.9.5-5.dsc
upower_0.9.5-5_i386.deb
to main/u/upower/upower_0.9.5-5_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 586751@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl <biebl@debian.org> (supplier of updated upower package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
Format: 1.8
Date: Sat, 23 Oct 2010 21:39:56 +0200
Source: upower
Binary: upower upower-doc libupower-glib1 libupower-glib-dev
Architecture: source all i386
Version: 0.9.5-5
Distribution: unstable
Urgency: low
Maintainer: Utopia Maintenance Team <pkg-utopia-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <biebl@debian.org>
Description:
libupower-glib-dev - abstraction for power management - development files
libupower-glib1 - abstraction for power management - shared library
upower - abstraction for power management
upower-doc - abstraction for power management - documentation
Closes: 586751 595083
Changes:
upower (0.9.5-5) unstable; urgency=low
.
* debian/patches/00git_dont_poll_serial_port_if_no_wup_adaptor.patch
- Do not continue to poll the serial port if there is no Watts Up Pro
adaptor. Patch cherry-picked from upstream Git. (Closes: #586751)
* Drop libdevkit-power-gobject library packages as all reverse dependencies
have been updated to use the new API provided by libupower-glib.
(Closes: #595083)
Checksums-Sha1:
bab8bdc8f62c0a35d4742d5547f4ac77f531865c 2252 upower_0.9.5-5.dsc
a0fac52b12ad840843f0fc718344a0e3af23c0f2 9640 upower_0.9.5-5.diff.gz
032aafa512b4e8e1632ec218b4b4e5f734640d51 60022 upower-doc_0.9.5-5_all.deb
72e6b671173eeabbd2f275c57aa17d5d7106da7d 89368 upower_0.9.5-5_i386.deb
d5e6006a73a616f71cb6ae6b8de16581f824867a 35628 libupower-glib1_0.9.5-5_i386.deb
54c4e552d525e0cdd175306191b55b711a2247ac 41836 libupower-glib-dev_0.9.5-5_i386.deb
Checksums-Sha256:
99d3b72fdfda33a92268b9816e3654a88e19755633cbd998dbd0acdcae369dd2 2252 upower_0.9.5-5.dsc
e2a9193b53ae8795332ca5b16acd2a90ba684e19680cb637591143cc23027650 9640 upower_0.9.5-5.diff.gz
9dc8a23413899a265ba485b766b0e2c5fa59b95a2265bc58b1c24a02860493e2 60022 upower-doc_0.9.5-5_all.deb
72cfc9204a2b74ba8a89ee6149125c1d2955d454478b6f4ca771c292f42c683a 89368 upower_0.9.5-5_i386.deb
54e3e76dc80528e02e80d766bd81d4e27c46a48811424e19c488060c05acca04 35628 libupower-glib1_0.9.5-5_i386.deb
c58fe3fcbaad5208ac682ad8bce5e44ee5410546ca838f470c0a2522324f2a51 41836 libupower-glib-dev_0.9.5-5_i386.deb
Files:
8bd7bd74530c903e8f7176287ce7b282 2252 admin optional upower_0.9.5-5.dsc
fb8edc16a176c73900e9a6af5424de02 9640 admin optional upower_0.9.5-5.diff.gz
5b81e01ec367e8e4d4c7f06b11b4f58b 60022 doc optional upower-doc_0.9.5-5_all.deb
467ea5b1e1ff57c7898cc8dc7988cc93 89368 admin optional upower_0.9.5-5_i386.deb
a2c46bd925c4d1ad5c6c22f807fa9649 35628 libs optional libupower-glib1_0.9.5-5_i386.deb
43a2ecd95a032989e648999223ad5548 41836 libdevel optional libupower-glib-dev_0.9.5-5_i386.deb
iQIcBAEBCAAGBQJMwzx2AAoJEGrh3w1gjyLcYrUP/AtBUUPCJ0IA3HRgCfjA4Pct
W4VQyNRNqw91cOh6AActMTvtmii2LPZgTdgq7a0i8r50SUsYJt/wmN2l5jeIdYJx
f4KnS5dqfWnE9UKoROyeiur3qs8sD6RQvp5LtY+7KOaTJh+wPUEFdalUgMcmFeMB
hQ5Su6UIXSlKD7oOS2ms3UqHmKn2dYk8kxaPUwP5Cv0dGa33Rpy/JRws5vuKT2ki
Q0Swn36xrJ3EVDvHoyeGUYIB3kxPp5IMEPs84D+jPBxZIWQGc/D8iC9zQEO3w50v
PugWoRhv1ZZAfZNm46JPZ2/oFU5NYxx5BEq/Hxkg2AW9SxGIaEo+9D4oK/J/SuLJ
b1zNbRex6BumBR1n9bAW6LL9Wlr38stugriNNjPpqk8oOOJT8vt8nLjNnvzMSYGJ
71tfcj5x0vSkBZSuKEznlptlrXWxwPDHySFZnrfpiG8gNajlBZ5qHYMS6kF0Og2M
l2cp4RhsRFXNMwcVvIq+Y/8MUq//QH8lKXewxYxuVhqSEsUmRDQQjsGOqujX/B01
SHkVDHL5M1OjSGKgGBWhFvbFE0WGlc7NpvQYMqtDJjg11beL+lhA5TrQjyxnvQf8
0mzrRKnwGCxSdEf0aNrSvqNiKFkDxeL0HutucYcALH24VIBT1JAK2DDFmzO9hiQf
n9OSHE7raOXP7xPLe+pY
=cU0B
-----END PGP SIGNATURE-----
Hello Joost, you reported bug http://bugs.debian.org/586751 against a version of upower older than the one currently found in Debian jessie. In case you are running the latest upower version from Debian jessie, could you please test if you still experience the problem? It would be nice if you could test and reply, so this bug could be marked as fixed in jessie and closed. Btw. did you report this upstream? It looked like upstream was very responsive, so he might have fixed this quickly? Thanks, *t
I don't know whether this bug should be closed, but at this moment we are unable to verify whether this problem still persists. *t---------- Forwarded message ---------- Date: Thu, 04 Dec 2014 11:10:43 +0100 Yup.
Hello Richard, is there anything we can do about this? See also these: http://bugs.debian.org/586751 http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=34;bug=586751 *t I don't know whether this bug should be closed, but at this moment we are unable to verify whether this problem still persists. *t ---------- Forwarded message ---------- Date: Thu, 04 Dec 2014 11:10:43 +0100 Yup.
Dear Customer, Your item has arrived at the USPS Post Office at January 23, but the courier was unable to deliver parcel to you. Postal label is enclosed to this e-mail. Please check the attachment! All the best, Salvador Nolan, USPS Senior Support Manager.
This bug report was re-opened withouth further information provided. Closing it again. If it is still an issue today, please file a new bug report. Michael