FS#41127 - [lxpanel] 0.6.2-1: battery plugin should have option to show extended information
Attached to Project:
Community Packages
Opened by Henry Gebhardt (hsgg) - Tuesday, 08 July 2014, 01:32 GMT
Last edited by Balló György (City-busz) - Monday, 13 October 2014, 00:16 GMT
Opened by Henry Gebhardt (hsgg) - Tuesday, 08 July 2014, 01:32 GMT
Last edited by Balló György (City-busz) - Monday, 13 October 2014, 00:16 GMT
|
Details
Description:
In arch linux there is an option missing for the lxpanel battery plugin. The upstream plugin can show more detailed information about a battery. This is configured by enabling the "Show Extended Information" checkbox in the plugin configuration dialog, which is missing in Arch. lxpanel learned this in commit 9c9d3a0, before 0.6.0. Thanks! |
This task depends upon
Closed by Balló György (City-busz)
Monday, 13 October 2014, 00:16 GMT
Reason for closing: Works for me
Monday, 13 October 2014, 00:16 GMT
Reason for closing: Works for me
Comment by Doug Newgard (Scimmia) -
Tuesday, 08 July 2014, 03:07 GMT
Comment by
Bartłomiej Piotrowski (Barthalion)
- Saturday, 26 July 2014, 10:47 GMT
Comment by Henry Gebhardt (hsgg) -
Saturday, 26 July 2014, 18:21 GMT
Comment by
Felix Yan (felixonmars) - Friday,
19 September 2014, 03:30 GMT
Comment by
Balló György (City-busz) - Tuesday,
07 October 2014, 22:19 GMT
- Field changed: Status (Unconfirmed → Assigned)
- Field changed: Category (Packages: Extra → Packages)
- Field changed: Architecture (All → All)
- Task assigned to Bartłomiej Piotrowski (Barthalion)
Orphan, assigning to last packager
And it's not missing where? The commit you mentioned is about
displaying additional information in tooltip, not "Show Extended
Information" checkbox.
Ah, sorry I meant commit 5c0c599, which introduces the checkbox to
make the information displayed in the other commit configurable.
This was also introduced before 0.6.0.
I've checked the source we are building from, and the "Show
Extended Information" related code are present. If 0.7.0-2 still
gets the checkbox missing for you, it would be more likely an
upstream issue.
It works for me with 0.7.1-3. Could you still reproduce the
problem?