Bug 863524

What kind of bluetooth keyboard is that? It looks like I need to buy some more hardware...

I get this behaviour when I connect an Appple Magic Trackpad with a USB Bluetooth dongle.  Given https://bugzilla.redhat.com/show_bug.cgi?id=847874 I doubt you need special bluetooth hardware to reproduce this.  If you get a trackpad and need help configuring it, send me email and I'll be happy to help - it's pretty easy.

I will occasionally get this, at which point I have to re-do the settings for my trackpad:
Oct 13 07:04:22 badboy kernel: [43918.913666] power_supply hid-7C:C3:A1:4A:69:AD-battery: driver failed to report `capacity' property: -5
Oct 13 07:04:30 badboy kernel: [43926.908545] power_supply hid-7C:C3:A1:4A:69:AD-battery: driver failed to report `capacity' property: -5
Oct 13 07:04:30 badboy kernel: [43926.930194] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0
Oct 13 07:04:30 badboy kernel: [43926.980183] power_supply hid-7C:C3:A1:4A:69:AD-battery: driver failed to report `capacity' property: -5
Oct 13 07:04:30 badboy kernel: [43926.980283] input: Apple Wireless Trackpad as /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0/bluetooth/hci0/hci0:45/input21
Oct 13 07:04:30 badboy kernel: [43926.981065] magicmouse 0005:05AC:030E.0007: input,hidraw5: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 00:15:83:3D:0A:57
Oct 13 07:04:30 badboy kernel: [43926.982157] power_supply hid-7C:C3:A1:4A:69:AD-battery: driver failed to report `capacity' property: -5

it is called rii mini and is easy to find, but beware, there are non-bt radio variants

@John Schmitt
Can you please attach the lsinput output, there are some devices that do not report the correct info about how to grab the information, resulting in the error you get, in those cases I need to add a quirk to the kernel, I just need to make sure you are having the same case..

@Serge Pavlovsky
can you paste upower -d and lsinput too, your keyboard is probably not correctly reporting the battery status, we probably need to add quirk to the kernel but since I'm familiar with the Apple devices I'm not sure how easy will it be to fix the reporting for your device..

Thanks

Created attachment 631610 [details]
/proc/bus/input/devices

I cannot find anything like 'lsinput' or 'input-utils' so I'm attaching the contents of /proc/bus/input/devices.  I'll be happy to provide whatever I can.

Created attachment 631613 [details]
sudo lsusb -v

In case it helps, lsusb -v.

# upower -d
Device: /org/freedesktop/UPower/devices/battery_hid_DCo2Co26oAAo9Eo0D_battery
  native-path:          /sys/devices/pci0000:00/0000:00:13.0/usb5/5-2/5-2:1.0/bluetooth/hci0/hci0:21/0005:0A5C:8502.0004/power_supply/hid-DC:2C:26:AA:9E:0D-battery
  model:                Macro Keyboard
  power supply:         no
  updated:              Mon Oct 22 18:48:06 2012 (12 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               discharging
    energy:              0 Wh
    energy-empty:        0 Wh
    energy-full:         0 Wh
    energy-full-design:  0 Wh
    energy-rate:         0 W
    percentage:          100%
    capacity:            100%
  History (charge):
    1350920819	100.000	discharging
    1350920819	0.000	unknown
  History (rate):
    1350920819	0.000	unknown

Daemon:
  daemon-version:  0.9.17
  can-suspend:     yes
  can-hibernate    yes
  on-battery:      no
  on-low-battery:  no
  lid-is-closed:   no
  lid-is-present:  no
  is-docked:       no

i have no idea where to get lsinput

(In reply to comment #6)
> Created attachment 631613 [details]
> sudo lsusb -v
> 
> In case it helps, lsusb -v.

Well you have the same Apple trackpad that I do, so it must work, do you have any other bluetooth battery operated, which kernel, and upower -d please. Tho if you have linux 3.4+ it should just work

(In reply to comment #8)
> i have no idea where to get lsinput

input utils should have it, and well from your output I'm not seeing anything wrong, are you using a recent kernel 3.4+?

# cat /proc/version 
Linux version 3.6.1-1.fc17.x86_64 (mockbuild@) (gcc version 4.7.2 20120921 (Red Hat 4.7.2-2) (GCC) ) #1 SMP Wed Oct 10 12:13:05 UTC 2012

there are no packages with names resembling input utils in repo

(In reply to comment #12)
> there are no packages with names resembling input utils in repo

ok can you attach the content of rdesc file on
/sys/kernel/debug/hid/[YOUR DEVICE]/rdesc

your problem is that it's not reporting the battery status correctly right?

my problem is that something tries to show me battery status when my computer has no battery
if it is intended to show battery status of bluetooth devices then i have no objection other than it is called something like (after double translation) "laptop battery" when it must be more like "bluetooth keyboard battery"

and also it has some problems with getting actual status value:
---
Oct 22 19:11:33 underdark upowerd[1554]: (upowerd:1554): UPower-Linux-WARNING **: no voltage values, using 10V as approximation
---
already advanced to next level:
----
Oct 22 19:19:47 underdark upowerd[1554]: (upowerd:1554): GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s1 != NULL' failed
Oct 22 19:19:47 underdark upowerd[1554]: (upowerd:1554): UPower-Linux-WARNING **: unknown status string:
---
and soon it will crash


i was not able to find it under /sys/kernel/debug/hid
then i checked its status in bt settings and it was off
i pressed on switch in applet few times and got
---
Oct 22 19:31:22 underdark bluetoothd[732]: bluetoothd[732]: Host is down (112)
Oct 22 19:31:22 underdark bluetoothd[732]: Host is down (112)
Oct 22 19:31:23 underdark kernel: [130347.894357] gnome-control-c[15299]: segfault at 7 ip 0000003b36e30e7c sp 00007fff1721f6a0 error 4 in libgobject-2.0.so.0.3200.4[3b36e00000+4b000]
Oct 22 19:31:24 underdark abrt[15315]: Saved core dump of pid 15299 (/usr/bin/gnome-control-center) to /var/spool/abrt/ccpp-2012-10-22-19:31:23-15299 (45715456 bytes)
---

then as a last resort i tried to press some buttons on keyboard to check if it will work and keys worked and it appeared under /sys/kernel/debug/hid
/var/log/messages was silent
creating attachment

Created attachment 631637 [details]
/sys/kernel/debug/hid/0005:0A5C:8502.0007/rdesc

@Daniel Nicoletti input-utils doesn't seem to exist in any f17 repo.
My magic touchpad works well enough but I don't understand why there is so much noise from upowerd in /var/log/messages. Excerpt:

Oct 22 08:53:35 badboy kernel: [35890.874169] power_supply hid-7C:C3:A1:4A:69:AD-battery: driver failed to report `capacity' property: -5
Oct 22 08:53:35 badboy kernel: [35890.891847] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0
Oct 22 08:53:35 badboy kernel: [35890.965326] power_supply hid-7C:C3:A1:4A:69:AD-battery: driver failed to report `capacity' property: -5
Oct 22 08:53:35 badboy kernel: [35890.965424] input: Apple Wireless Trackpad as /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0/bluetooth/hci0/hci0:45/input21
Oct 22 08:53:35 badboy kernel: [35890.965791] magicmouse 0005:05AC:030E.0007: input,hidraw5: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 00:15:83:3D:0A:57
Oct 22 08:53:35 badboy kernel: [35890.972253] power_supply hid-7C:C3:A1:4A:69:AD-battery: driver failed to report `capacity' property: -5
Oct 22 08:53:54 badboy upowerd[14936]: (upowerd:14936): GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s1 != NULL' failed
Oct 22 08:53:54 badboy upowerd[14936]: (upowerd:14936): UPower-Linux-WARNING **: unknown status string:

The last two lines repeat every 30 seconds.
After that message about 'driver failed to report...' I have to invoke synclient again to restore my settings.


$ upower -d
Device: /org/freedesktop/UPower/devices/battery_hid_7CoC3oA1o4Ao69oAD_battery
  native-path:          /sys/devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0/bluetooth/hci0/hci0:42/0005:05AC:030E.0006/power_supply/hid-7C:C3:A1:4A:69:AD-battery
  power supply:         no
  updated:              Mon Oct 22 09:38:24 2012 (24 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               empty
    energy:              0 Wh
    energy-empty:        0 Wh
    energy-full:         0 Wh
    energy-full-design:  0 Wh
    energy-rate:         0 W
    percentage:          0%
    capacity:            100%

Daemon:
  daemon-version:  0.9.17
  can-suspend:     yes
  can-hibernate    yes
  on-battery:      no
  on-low-battery:  no
  lid-is-closed:   no
  lid-is-present:  no                                                                                                                                                                                                                                                                                                                                                        
  is-docked:       no

or more likely, when i pressed keyboard keys, log actually was not silent, but had
-------
Oct 22 19:33:00 underdark kernel: [130443.935677] hid-generic 0005:0A5C:8502.0007: unknown main item tag 0x0
Oct 22 19:33:00 underdark kernel: [130444.067756] input: Macro Keyboard as /devices/pci0000:00/0000:00:13.0/usb5/5-2/5-2:1.0/bluetooth/hci0/hci0:21/input17
Oct 22 19:33:00 underdark kernel: [130444.069121] hid-generic 0005:0A5C:8502.0007: input,hidraw3: BLUETOOTH HID v1.1b Keyboard [Macro Keyboard] on 00:02:72:B2:3B:85
Oct 22 19:33:00 underdark upowerd[1554]: (upowerd:1554): UPower-Linux-WARNING **: no voltage values, using 10V as approximation
Oct 22 19:33:00 underdark upowerd[1554]: ** (upowerd:1554): ERROR **: Failed to register GObject with DBusConnection: org.freedesktop.DBus.Error.ObjectPathInUse A handler is already registered for /org/freedesktop/UPower/devices/battery_hid_DCo2Co26oAAo9Eo0D_battery
Oct 22 19:33:00 underdark kernel: [130444.225402] traps: upowerd[1554] trap int3 ip:3b3624e991 sp:7fff9ddfa030 error:0
Oct 22 19:33:00 underdark abrtd: Directory 'ccpp-2012-10-22-19:33:00-1554' creation detected
Oct 22 19:33:00 underdark abrt[15446]: Saved core dump of pid 1554 (/usr/libexec/upowerd) to /var/spool/abrt/ccpp-2012-10-22-19:33:00-1554 (18587648 bytes)
Oct 22 19:33:00 underdark abrt[15446]: Lock file '/var/spool/abrt/ccpp-2012-10-05-18:17:48-1359/.lock' is locked by process 740
Oct 22 19:33:00 underdark abrtd: '/var/spool/abrt/oops-2012-01-11-00:22:20-1062-1' is not a problem directory
Oct 22 19:33:00 underdark systemd[1]: upower.service: main process exited, code=dumped, status=5
Oct 22 19:33:00 underdark systemd[1]: Unit upower.service entered failed state.
Oct 22 19:33:01 underdark abrtd: '/var/spool/abrt/oops-2012-01-11-00:22:20-1062-0' is not a problem directory
Oct 22 19:33:01 underdark abrtd: '/var/spool/abrt/oops-2012-01-11-00:22:20-1062-1' is not a problem directory
Oct 22 19:33:02 underdark abrtd: '/var/spool/abrt/oops-2012-01-11-00:22:20-1062-0' is not a problem directory
Oct 22 19:33:02 underdark abrtd: Формируется протокол сбоя
Oct 22 19:33:02 underdark abrtd: Cannot disassemble function at 0x0, not computing fingerprint

@Serge
For the problem of the battery icon not being clear enough
that it's the battery of the keyboard you would need a new
bug against it (I use KDE so I dunno the component)
Does upowerd keyboard report the right status? From the
log messages I think no. So in short I think the problem is
that some devices (including my Apple keyboard) report the
wrong range of status:
INPUT(3)[INPUT]
    Field(0)
      Application(Consumer.0001)
      Usage(1)
        GenericDeviceControls.BatteryStrength
      Logical Minimum(0)
      Logical Maximum(255)
      Report Size(8)
      Report Count(1)
      Report Offset(0)
      Flags( Variable Absolute )
As you can see according to the device report
descriptor (rdesc), the battery value should
go from 0-255 but at least for my keyboard it
goes from 0-100. Also it says INPUT, but for
my keyboard it's only able to get the report
if FEATURE was used, so your device doesn't
follow HID specification and needs a kernel
quirk.

Can you test a kernel patch?

@John
Since you have a different issue it would be better to have a new bug report
(if you do please notify me here since I'm not subscribed to bug reports)

if you kill upowerd and run upowerd -d does it report the right battery status?

i can test patch but i don't know how to get upowerd keyboard report status

also i think upowerd should not require kernel patches to not crash

(In reply to comment #21)
> also i think upowerd should not require kernel patches to not crash

Right it should not crash, and I don't know why it does. But since I introduced the kernel patch I want it to work. Can you paste the contents of /proc/bus/input/devices, so I can know the vendor and product codes.

Thanks.

I: Bus=0005 Vendor=0a5c Product=8502 Version=011b
N: Name="Macro Keyboard"
P: Phys=00:02:72:B2:3B:85
S: Sysfs=/devices/pci0000:00/0000:00:13.0/usb5/5-2/5-2:1.0/bluetooth/hci0/hci0:21/input18
U: Uniq=DC:2C:26:AA:9E:0D
H: Handlers=sysrq kbd mouse1 event14 
B: PROP=0
B: EV=12001f
B: KEY=70000 1000002000007 ff9f387ad941d7ff febeffdfffefffff fffffffffffffffe
B: REL=103
B: ABS=70000000000
B: MSC=10
B: LED=1f

@Daniel You requested a different bug for my issue so please have a look at https://bugzilla.redhat.com/show_bug.cgi?id=847874

Hmm... seeing this with a Logitech Elite Duo wireless keyboard and mouse as well:

[philipp@builder SPECS]$ upower -d
Device: /org/freedesktop/UPower/devices/keyboard_1_3x4
  native-path:          /sys/devices/pci0000:00/0000:00:12.2/usb1/1-3/1-3.4
  vendor:               Logitech, Inc.
  model:                Elite Duo
  power supply:         no
  updated:              Thu May 23 17:37:22 2013 (24882 seconds ago)
  has history:          yes
  has statistics:       no
  keyboard
    present:             yes
    rechargeable:        yes
    state:               discharging
    percentage:          100%

Device: /org/freedesktop/UPower/devices/ups_hiddev0
  native-path:          /sys/devices/pci0000:00/0000:00:12.1/usb4/4-1/4-1:1.0/usbmisc/hiddev0
  power supply:         yes
  updated:              Fri May 24 00:31:52 2013 (12 seconds ago)
  has history:          yes
  has statistics:       yes
  ups
    present:             yes
    state:               fully-charged
    time to empty:       6.1 minutes
    percentage:          100%

Daemon:
  daemon-version:  0.9.19
  can-suspend:     no
  can-hibernate:   no
  on-battery:      no
  on-low-battery:  no
  lid-is-closed:   no
  lid-is-present:  no
  is-docked:       yes
[philipp@builder SPECS]$

[philipp@builder SPECS]$ lsusb -v -s 1:4

Bus 001 Device 004: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x046d Logitech, Inc.
  idProduct          0xc505 Cordless Mouse+Keyboard Receiver
  bcdDevice           17.21
  iManufacturer           1 
  iProduct                2 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           84
    bNumInterfaces          3
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower               98mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      1 Keyboard
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      63
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      2 Mouse
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     190
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      2 Mouse
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      52
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               5

Errr...


[philipp@builder SPECS]$ sudo lsusb -v -s 1:4

Bus 001 Device 004: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x046d Logitech, Inc.
  idProduct          0xc505 Cordless Mouse+Keyboard Receiver
  bcdDevice           17.21
  iManufacturer           1 
  iProduct                2 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           84
    bNumInterfaces          3
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower               98mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      1 Keyboard
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      63
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      2 Mouse
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength     190
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      1 Boot Interface Subclass
      bInterfaceProtocol      2 Mouse
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      52
         Report Descriptors: 
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               5
Device Status:     0x0001
  Self Powered

When the the battery percentage is running low, get charged battery replace in... 

If that's not the case, it means ***you need a thin coin to screw the battery bay tie until you can get the upower command can reports the current percentage of the battery: ***

$ upower -d


  model:                Apple Wireless Trackpad
  power supply:         no
  updated:              Wed Jun  5 21:39:48 2013 (8 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               discharging
    energy:              0 Wh
    energy-empty:        0 Wh
    energy-full:         0 Wh
    energy-full-design:  0 Wh
    energy-rate:         0 W
    percentage:          75%
    capacity:            100%

At this stay, your motion would lag any more in normal status.

Then you may config rsyslog to discard the mesg from upowerd.

After you screw the battery bay tie, for magic touch pad you should only see this msg from upowerd:

Jun  5 20:46:35 XXXX upowerd[1207]: (upowerd:1207): UPower-Linux-WARNING **: no voltage values, using 10V as approximation


In this scenario, it would cause touch pad lag.

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

I am observing this 'upowerd [..] UPower-Linux-WARNING **: no voltage values, using 10V as approximation'-spamming-syslog-issue on Fedora 19 as well.

It occurs after connecting a wiimote (a 16 € clone as sold on amazon, not a original Nintendo one) via bluetooth. On Fedora 19 it is correctly connected/paired directly by Bluez (by the BlueZ wiimote plugin - which is installed by default).

Machine: Thinkpad X220
Fedora: 19, x64

I bought a new bluetooth dongle to see if I can resolve my issues.  The new dongle has the same problems plus some different problems.

On this computer, triple click seems to disable the pad for several minutes.  Is there a different category which would apply to this bug?

I don't understand, with a different brand of bluetooth dongle, why my setup on a different computer works so well.  Both F18, both with an Apple touchpad.

(In reply to John Schmitt from comment #32)
> I bought a new bluetooth dongle to see if I can resolve my issues.  The new
> dongle has the same problems plus some different problems.
> 
> On this computer, triple click seems to disable the pad for several minutes.
> Is there a different category which would apply to this bug?
> 
> I don't understand, with a different brand of bluetooth dongle, why my setup
> on a different computer works so well.  Both F18, both with an Apple
> touchpad.

Triple click with Apple touchpad is a known issue with crap bluetooth dongles, just throw in the trash... for the kernel issue 3.10 has most connect issues fixed, if after that you have errors then your device needs a kernel quirk.

@Daniel, thanks for the info.

Linux xxx 3.10.4-100.fc18.x86_64 #1 SMP Thu Aug 1 21:13:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

On the topic if crap bluetooth dongles, this new one was $20 while the previous one was $10.  I was hoping that spending an extra $10 would get me something that worked.

Can you recommend a make and model?

(In reply to John Schmitt from comment #34)
> @Daniel, thanks for the info.
> 
> Linux xxx 3.10.4-100.fc18.x86_64 #1 SMP Thu Aug 1 21:13:27 UTC 2013 x86_64
> x86_64 x86_64 GNU/Linux
> 
> On the topic if crap bluetooth dongles, this new one was $20 while the
> previous one was $10.  I was hoping that spending an extra $10 would get me
> something that worked.
> 
> Can you recommend a make and model?
I have brought several dongles and all shared the same chip (at least lsusb said so, cambridge something iirc), after some googling I found the fault was with this chip, so I brought one like this http://dx.com/p/mini-usb-bluetooth-v3-0-adapter-dongle-121165 not sure it has the same chip but from outside it's the same.. Now triple clicks doesn't freeze anymore :)

Now if you have 3.10 what's the exact issue that you have?

If I'd kept the packaging, I'd buy another bluetooth dongle of the same kind I use on this computer, works perfectly:

Device: /org/freedesktop/UPower/devices/battery_hid_b8of6ob1o2foeeoda_battery
  native-path:          /sys/devices/pci0000:00/0000:00:1d.1/usb7/7-2/7-2:1.0/bluetooth/hci0/hci0:42/0005:05AC:030E.000D/power_supply/hid-b8:f6:b1:2f:ee:da-battery
  model:                Apple Wireless Trackpad
  power supply:         no
  updated:              Mon Aug 12 14:42:27 2013 (25 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               discharging
    energy:              0 Wh
    energy-empty:        0 Wh
    energy-full:         0 Wh
    energy-full-design:  0 Wh
    energy-rate:         0 W
    percentage:          46%
    capacity:            100%

Daemon:
  daemon-version:  0.9.19
  can-suspend:     yes
  can-hibernate:   yes
  on-battery:      no
  on-low-battery:  no
  lid-is-closed:   no
  lid-is-present:  no
  is-docked:       no

My exact issues on my new failing dongle are just as described in the bug, plus:

- when pairing, I get a message that says something like "device added successfully, but failed to connect" which allows me to move, scroll, single and double click

- triple click on the touchpad disconnects it

I'm seeing this in Fedora 19 with an HP Bluetooth mouse.  Let me know if you want any additional info.

However, there seems to be development of a patch to address this, regarding devices like this that don't supply a voltage.  Here's a link: http://lists.freedesktop.org/archives/devkit-devel/2013-August/001469.html

(In reply to Stan King from comment #38)
> I'm seeing this in Fedora 19 with an HP Bluetooth mouse.  Let me know if you
> want any additional info.
> 
> However, there seems to be development of a patch to address this, regarding
> devices like this that don't supply a voltage.  Here's a link:
> http://lists.freedesktop.org/archives/devkit-devel/2013-August/001469.html

I'm having the exact same issue with an HP Bluetooth Mouse X4000b.
`$ cat /proc/bus/input/devices` :
I: Bus=0005 Vendor=03f0 Product=024c Version=010c
N: Name="HP Bluetooth Mouse X4000b"
P: Phys=cc:af:78:ed:ad:89
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input20
U: Uniq=00:02:76:4e:91:af
H: Handlers=mouse3 event18 
B: PROP=0
B: EV=17
B: KEY=70000 0 0 0 0
B: REL=103
B: MSC=10

BTW: This is the journal log as I am turning of the bluetooth adapter:

Dec 11 22:39:50 FedPadSSD bluetoothd[456]: bluetoothd[456]: Endpoint unregistered: sender=:1.53 path=/MediaEndpoint/A2DPSink
Dec 11 22:39:50 FedPadSSD bluetoothd[456]: bluetoothd[456]: Endpoint unregistered: sender=:1.53 path=/MediaEndpoint/A2DPSource
Dec 11 22:39:50 FedPadSSD bluetoothd[456]: bluetoothd[456]: Endpoint unregistered: sender=:1.53 path=/MediaEndpoint/HFPAG
Dec 11 22:39:50 FedPadSSD bluetoothd[456]: bluetoothd[456]: Endpoint unregistered: sender=:1.53 path=/MediaEndpoint/HFPHS
Dec 11 22:39:50 FedPadSSD bluetoothd[456]: Unregister path: /org/bluez/456/hci0
Dec 11 22:39:50 FedPadSSD bluetoothd[456]: Endpoint unregistered: sender=:1.53 path=/MediaEndpoint/A2DPSink
Dec 11 22:39:50 FedPadSSD bluetoothd[456]: Endpoint unregistered: sender=:1.53 path=/MediaEndpoint/A2DPSource
Dec 11 22:39:50 FedPadSSD bluetoothd[456]: Endpoint unregistered: sender=:1.53 path=/MediaEndpoint/HFPAG
Dec 11 22:39:50 FedPadSSD bluetoothd[456]: Endpoint unregistered: sender=:1.53 path=/MediaEndpoint/HFPHS
Dec 11 22:39:50 FedPadSSD kernel: usb 1-1.4: USB disconnect, device number 5
Dec 11 22:39:50 FedPadSSD systemd[1]: Service bluetooth.target is not needed anymore. Stopping.
Dec 11 22:39:50 FedPadSSD systemd[1]: Stopping Bluetooth.
Dec 11 22:39:50 FedPadSSD systemd[1]: Stopped target Bluetooth.
Dec 11 22:39:50 FedPadSSD dbus[479]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.53" (uid=1000 pid=1577 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.0" (uid=0 pid=456 comm="/usr/sbin/bluetoothd -n ")
Dec 11 22:39:50 FedPadSSD dbus[479]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.53" (uid=1000 pid=1577 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.0" (uid=0 pid=456 comm="/usr/sbin/bluetoothd -n ")
Dec 11 22:39:50 FedPadSSD dbus[479]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.53" (uid=1000 pid=1577 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.0" (uid=0 pid=456 comm="/usr/sbin/bluetoothd -n ")
Dec 11 22:39:50 FedPadSSD dbus[479]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.53" (uid=1000 pid=1577 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.0" (uid=0 pid=456 comm="/usr/sbin/bluetoothd -n ")
Dec 11 22:39:50 FedPadSSD bluetoothd[456]: hci0: Set IO Capability (0x0018) failed: Invalid Index (0x11)
Dec 11 22:39:50 FedPadSSD dbus-daemon[479]: dbus[479]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.53" (uid=1000 pid=1577 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.0" (uid=0 pid=456 comm="/usr/sbin/bluetoothd -n ")
Dec 11 22:39:50 FedPadSSD dbus-daemon[479]: dbus[479]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.53" (uid=1000 pid=1577 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.0" (uid=0 pid=456 comm="/usr/sbin/bluetoothd -n ")
Dec 11 22:39:50 FedPadSSD dbus-daemon[479]: dbus[479]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.53" (uid=1000 pid=1577 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.0" (uid=0 pid=456 comm="/usr/sbin/bluetoothd -n ")
Dec 11 22:39:50 FedPadSSD dbus-daemon[479]: dbus[479]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.53" (uid=1000 pid=1577 comm="/usr/bin/pulseaudio --start ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.0" (uid=0 pid=456 comm="/usr/sbin/bluetoothd -n ")
Dec 11 22:39:50 FedPadSSD bluetoothd[456]: bluetoothd[456]: hci0: Set IO Capability (0x0018) failed: Invalid Index (0x11)
Dec 11 22:39:50 FedPadSSD gnome-session[1451]: Agent unregistration failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Method "UnregisterAgent" with signature "o" on interface "org.bluez.Adapter" doesn't exist
Dec 11 22:39:50 FedPadSSD gnome-session[1451]: 'g-io-error-quark'
Dec 11 22:39:50 FedPadSSD dbus-daemon[479]: dbus[479]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.203" (uid=1000 pid=1727 comm="/usr/bin/gnome-shell ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.0" (uid=0 pid=456 comm="/usr/sbin/bluetoothd -n ")
Dec 11 22:39:50 FedPadSSD dbus[479]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.203" (uid=1000 pid=1727 comm="/usr/bin/gnome-shell ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.0" (uid=0 pid=456 comm="/usr/sbin/bluetoothd -n ")

I can confirm this is happening on the latest FC19 X86_64 on a Vaio S as well.
-----------------------------------------------
[root@blackvaio ~]# uname -a
Linux blackvaio.servermasters.com 3.11.10-200.fc19.x86_64 #1 SMP Mon Dec 2 20:28:03 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
-----------------------------------------------
[root@blackvaio ~]# upower -d
Device: /org/freedesktop/UPower/devices/line_power_ADP1
  native-path:          /sys/devices/LNXSYSTM:00/device:00/ACPI0003:00/power_supply/ADP1
  power supply:         yes
  updated:              Tue Dec 17 13:49:37 2013 (2443 seconds ago)
  has history:          no
  has statistics:       no
  line-power
    online:             yes

Device: /org/freedesktop/UPower/devices/battery_hid_00o02o76o4doa1o8d_battery
  native-path:          /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/bluetooth/hci0/hci0:21/0005:054C:06A1.0001/power_supply/hid-00:02:76:4d:a1:8d-battery
  model:                VGP-BMS11
  power supply:         no
  updated:              Tue Dec 17 14:29:54 2013 (26 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               discharging
    energy:              0 Wh
    energy-empty:        0 Wh
    energy-full:         0 Wh
    energy-full-design:  0 Wh
    energy-rate:         0 W
    percentage:          79%
    capacity:            100%

Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:          /sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0C09:00/PNP0C0A:00/power_supply/BAT1
  vendor:               Sony Corporation
  power supply:         yes
  updated:              Tue Dec 17 13:51:24 2013 (2336 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               fully-charged
    energy:              52.27 Wh
    energy-empty:        0 Wh
    energy-full:         52.27 Wh
    energy-full-design:  52.27 Wh
    energy-rate:         0 W
    voltage:             12.334 V
    percentage:          100%
    capacity:            100%
    technology:          lithium-ion

Daemon:
  daemon-version:  0.9.20
  can-suspend:     yes
  can-hibernate:   yes
  on-battery:      no
  on-low-battery:  no
  lid-is-closed:   no
  lid-is-present:  yes
  is-docked:       no

-----------------------------------------------

Question, why is a bluetooth device registered as a "battery providing voltage" ?

I also get 2 battery icons on the Xfce panel, one charging, and the other discharging but always stays as 80%.  (interesting, since according to the /var/log it's assuming 10 volts. I guess 100% is then 12 volts right?)

and here is /var/log  (I guess this goes on forever):
Dec 17 14:22:54 blackvaio upowerd[1000]: (upowerd:1000): UPower-Linux-WARNING **: no voltage values, using 10V as approximation
Dec 17 14:23:24 blackvaio upowerd[1000]: (upowerd:1000): UPower-Linux-WARNING **: no voltage values, using 10V as approximation
Dec 17 14:23:54 blackvaio upowerd[1000]: (upowerd:1000): UPower-Linux-WARNING **: no voltage values, using 10V as approximation
Dec 17 14:24:24 blackvaio upowerd[1000]: (upowerd:1000): UPower-Linux-WARNING **: no voltage values, using 10V as approximation
Dec 17 14:24:54 blackvaio upowerd[1000]: (upowerd:1000): UPower-Linux-WARNING **: no voltage values, using 10V as approximation


The problem compounds into "machine unusable" form, after coming back from a suspend while using a truecrypt-mounted /home, but I think this is a different bug. (i.e. systemd race condition cannot read prefs for mouse/network/etc before reacquiring the truecrypt FS pointers)

The following commits should improve the log filling situation (released in upower 0.9.22). No changes made on the actual problem :
http://cgit.freedesktop.org/upower/commit/?id=12f6f4014502d41d343dcfaf39a65a3ae504ce04
http://cgit.freedesktop.org/upower/commit/?id=6d3a68d7d4a737b2d79fb93547707b7c715aae2d

leho@gusto ~ $ [-] sudo upower -d
Device: /org/freedesktop/UPower/devices/battery_wiimote_battery
  native-path:          /sys/devices/pci0000:00/0000:00:1d.2/usb7/7-2/7-2:1.0/bluetooth/hci0/hci0:38/0005:057E:0306.0017/power_supply/wiimote_battery
  power supply:         no
  updated:              Fri Dec 27 02:18:59 2013 (3 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               empty
    energy:              0 Wh
    energy-empty:        0 Wh
    energy-full:         0 Wh
    energy-full-design:  0 Wh
    energy-rate:         0 W
    percentage:          0%
    capacity:            100%

Daemon:
  daemon-version:  0.9.20
  on-battery:      no
  on-low-battery:  no
  lid-is-closed:   no
  lid-is-present:  no
  is-docked:       no

I guess I'l be updating to 0.9.22 soon

Hey guys, see if adding a udev-rule changes/improves the situation. I have created a /etc/udev/rules.d/10-local.rules:

># Set bluetooth power up
>ACTION=="add", KERNEL=="hci0", RUN+="/usr/bin/hciconfig hci0 up"

I just recently upgraded to F20 (with Bluez5), adding this allows my bluetooth mouse to resume operation after reboots.  I realize this will probably not have the same effect on F19 with Bluez4, but perhaps someone more experienced with udev and udev rules can alter it and adapt it to better integrate these devices; otherwise, Bluez5 may be available in F19 and may be able to mend this issue.

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.