mate-power-manager does not handle UP_DEVICE_STATE_UNKNOWN device state

Bug #1428131 reported by Vlad Orlov
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu MATE
Fix Released
Undecided
Unassigned
mate-power-manager (Debian)
Fix Released
Unknown
mate-power-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

The upower-related code in m-p-m does not handle UP_DEVICE_STATE_UNKNOWN device state. It leads to an assert (and program abort) if such state is received.

The upstream pull request [1] fixes that.

[1] https://github.com/mate-desktop/mate-power-manager/pull/131

Changed in mate-power-manager (Debian):
status: Unknown → New
Changed in ubuntu-mate:
status: New → Triaged
Changed in mate-power-manager (Ubuntu):
status: New → Invalid
status: Invalid → New
Changed in mate-power-manager (Debian):
status: New → Fix Released
Revision history for this message
Colin Watson (cjwatson) wrote :

This bug was fixed in the package mate-power-manager - 1.8.1+dfsg1-4

---------------
mate-power-manager (1.8.1+dfsg1-4) unstable; urgency=medium

  * debian/patches:
    + Add 0002_handle-UP-DEVICE-STATE-UNKNOWN.patch. Handle
      UP_DEVICE_STATE_UNKNOWN device states, avoid g_assert_not_reached().
      Fix segfaulting of mate-power-statistics in certain situations.
      (Closes: #779719). See also #774546.

 -- Mike Gabriel <email address hidden> Thu, 05 Mar 2015 05:42:14 +0100

Changed in mate-power-manager (Ubuntu):
status: New → Fix Released
Changed in ubuntu-mate:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.