** Changed in: repowerd (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: repowerd (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: repowerd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
repowerd, or some other process that acquires logind suspend
inhibitions, could be involved in this. It's easy to find out if this is
the case by running:
$ systemd-inhibit
and checking if any inhibitions with parameters What:sleep Mode:block
are active. Note that repowerd acquiring such an inhib
... I *suspect* this value may ...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1483427
Title:
Possible to manually set display brightness to 0 on Ubuntu Touch on
Aquaris E5
S
Thanks for the information.
I don't see anything wrong in the attached files. Both repowerd and the
indicator use the value set in the config-default.xml file as the
minimum value (5 out of max 255 => ~2%). I suspend this value may be too
low for this device.
Note that '5' is also the value used
Repowerd reads the min/max values from the device config xml file
shipped with the device. Does this file contain sane values?
Could someone with an E5 device paste the contents of:
1. /usr/share/powerd/device_configs/config-default.xml
2. /var/log/repowerd.log
Thanks.
--
You received this bug
I have prepared a PPA containing a new repowerd with a potential fix for
the issue here:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2276
IMPORTANT CAVEAT: The changes are experimental. Only try the PPA
packages on a development device, not one you care about keeping stable.
You m
** Also affects: repowerd
Importance: Undecided
Status: New
** Changed in: repowerd
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
** Changed in: repowerd
Status: New => In Progress
--
You received this bug notification because you are a member of DX
Pa
@Rasool
@Mark
Could you please attach the /var/log/syslog file from your device to
this bug the next time this (alarm not going off) happens to you? It
could help us figure out what is going wrong.
@Mark
Could you please clarify if "this happened the morning before last" is
referring to your ala
This also affects mir and unity-system-compositor (and many other
projects, I am sure) and is blocking all yakkety landings for them.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to google-mock in Ubuntu.
https://bugs.launchpad.net/bugs/160979
9 matches
Mail list logo
