[Dx-packages] [Bug 1674389] Re: Session Indicator's "Suspend" button has no effect in Unity 8

** 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

[Dx-packages] [Bug 1674389] Re: Session Indicator's "Suspend" button has no effect in Unity 8

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

[Dx-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5

... 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

[Dx-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5

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

[Dx-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5

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

[Dx-packages] [Bug 1588526] Re: [mako] Alarm doesn't ring when screen locked

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

[Dx-packages] [Bug 1588526] Re: [mako] Alarm doesn't ring when screen locked

** 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

[Dx-packages] [Bug 1588526] Re: Alarm doesn't ring when screen locked

@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

[Dx-packages] [Bug 1609793] Re: Unity tests crashes when compiling google-mocks with gcc-6

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.