1. 12 Oct, 2013 1 commit
  2. 10 Oct, 2013 2 commits
  3. 08 Oct, 2013 8 commits
  4. 27 Sep, 2013 1 commit
    • Martin Pitt's avatar
      linux: Track power_supply devices by name only instead of full sysfs path · 5c132c68
      Martin Pitt authored
      The full native sysfs path of wireless HID battery devices contains a lot of
      jitter like USB tree layout or sequence numbers which change after every resume
      from auto-suspend. Plus, there are kernel bugs which don't give proper remove
      events for those: http://bugzilla.kernel.org/show_bug.cgi?id=62041
      
      As device names within the same subsystem must be unique anyway, and we only
      use the device name for constructing the D-BUS object path, only consider the
      device name for the device list native → upower object lookup table, i. e. in
      up_native_get_native_path().
      
      This fixes the "A handler is already registered for <battery>" assertion crash
      if a bluetooth device comes back from auto-suspend. This fixes the
      test_bluetooth_mouse_reconnect() test case, drop the expected failure.
      
      https://launchpad.net/bugs/1112907
      5c132c68
  5. 20 Sep, 2013 2 commits
    • Martin Pitt's avatar
      Linux integration tests: Test reconnect of bluetooth mouse · 6f9ccd35
      Martin Pitt authored
      When these power down, we don't get remove uevents for the original
      power_supply devices from the kernel, but instead we get new devices with a
      different sequence number, but the same name:
      
        UDEV  [6408.025124] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:12/0005:0D62:0558.0001/power_supply/hid-00:0f:f6:6d:8e:c0-battery (power_supply)
        UDEV  [23785.90673] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:12/0005:0D62:0558.0002/power_supply/hid-00:0f:f6:6d:8e:c0-battery (power_supply)
      
      This circumvents the existing "treating add as change" check (as the native
      path is different) but breaks later on when building and registering the
      (supposedly) new object:
      
        ERROR **: Failed to register GObject with DBusConnection: org.freedesktop.DBus.Error.ObjectPathInUse A handler is already registered for /org/freedesktop/UPower/devices/mouse_hid_000ff66d8ec0_battery
      
      This reproduces https://launchpad.net/bugs/1112907
      6f9ccd35
    • Martin Pitt's avatar
      Linux integration tests: Run tests under umockdev-wrapper · 960d4413
      Martin Pitt authored
      Don't just cover the test upowerd by umockdev-wrapper, but the test suite
      itself as well, so that we can send uevents.
      
      Do this by re-execing the test suite under umockdev-wrapper if it's not already
      running under it.
      960d4413
  6. 18 Sep, 2013 1 commit
  7. 06 Sep, 2013 2 commits
  8. 04 Sep, 2013 2 commits
    • Shih-Yuan Lee (FourDollars)'s avatar
      Set locale in daemon and tool · fdc62ad2
      Shih-Yuan Lee (FourDollars) authored
      This is necessary to properly show non-UTF8 strings in debug mode (for the
      daemon) and upower --dump etc. (for the tool).
      fdc62ad2
    • Peter Wu's avatar
      hidpp: try harder not to report 0% battery · 347b8b0b
      Peter Wu authored
       (1) If the K800 keyboard is charging via the USB cable, it will report
           itself as Charging, but with a discharge level of 0 (which means
           "unknown". In this case, the previous known value (before
           connecting the cable) is always a better approximation than using
           zero.
       (2) When the K800 has fully charged (but with the cable still plugged
           in), it will still report 0 as discharge level. "Full" is 100% by
           definition, so let's fallback to that value.
      Signed-off-by: default avatarPeter Wu <lekensteyn@gmail.com>
      Signed-off-by: default avatarMartin Pitt <martinpitt@gnome.org>
      347b8b0b
  9. 03 Sep, 2013 21 commits