Note that the problem also exists for other boost -dev packages, and
should be fixed for them too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1552914
Title:
Can't install libboost-dev:armhf in a
This is blocking Mir cross-compilation on xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1552914
Title:
Can't install libboost-dev:armhf in a cross-build environment
To manage notifications
Public bug reported:
The current version of valgrind (1:3.11.0-1ubuntu1) was built against
version 2.21 of glibc, so its default suppression files target glibc
libraries of that version.
Valgrind needs to be updated and rebuilt to support the new version of
glibc (2.23) in xenial.
Also see bug
I am not able to reproduce this (tried on krillin) with a fake/mock
battery.
>From a shell on the phone (e.g. with phablet-shell), to enable the mock
battery:
$ gdbus call --session --dest "com.canonical.indicator.power" \
--object-path /com/canonical/indicator/power/Testing \
y8.
** Changed in: unity8 (Ubuntu)
Status: Incomplete => Triaged
** Changed in: unity8 (Ubuntu)
Assignee: Michael Terry (mterry) => Alexandros Frantzis (afrantzis)
** Summary changed:
- Initial notifications never shown and not destroyed until unity8 is stopped
+ "Placeh
Public bug reported:
Steps to reproduce:
1. In Notification.qml add:
Component.onDestruction { console.log("Notification onDestruction"); }
and a similar log message in Component.onCompleted.
2. Install dialer-app-autopilot on the phone. This installs a fake phone sim,
that, among other
repowerd exhibits the correct behavior
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585352
Title:
Screen comes on beyond the timeout after an incoming text with
proximity near
To manage
** Also affects: platform-api
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602604
Title:
package repowerd 2016.06+15.04.20160706.1-0ubuntu1 [modified:
** Changed in: platform-api
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602604
Title:
package repowerd 2016.06+15.04.20160706.1-0ubuntu1 [modified:
> Jul 13 09:49:22 foo repowerd[1416]: Loading module:
> 'libubuntu_application_api_test.so.3.0.0'
> Jul 13 09:49:22 foo repowerd[1416]: TestSensor INFO: Setup for DYNAMIC event
> injection over named pipe /tmp/sensor-fifo-1416
> Jul 13 09:49:22 foo repowerd[1416]: TestSensor WARNING: Requested
> The solution is to ship a proper /etc/ubuntu-platform-
api/application.conf file for the desktop.
An alternative would be for platform-api to somehow autodetect the
platform if no config option is provided, instead of falling back to the
test platform.
--
You received this bug notification
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609793
Title:
The top output doesn't implicate repowerd. Note, however, that the top
output is incomplete so we don't have the whole picture. For future
reference you can take textual snapshots of top with:
top -b -n10 -d1 > /tmp/top.txt
(Write to file 10 textual snapshots with 1 sec delay between snapshots)
u-s-s depends on powerd (>=0.15) | gnome-settings-daemon
Since powerd is missing (and always has been missing) on ppc64el, I
would expect the dependency to be fulfilled by gnome-settings-daemon,
but, if I understand the log correctly, the log indicates that gnome-
setting-daemon couldn't be
Ok. It works.
Thanks vary much.
Since i have now installed a proposed package update will
that mess with a future update-upgrade of my system?
Also after the installation i deselected the 'proposed' archive
from the Software & update tool.
--
You received this bug notification because you
-
service/+archive/ubuntu/landing-003/+files/repowerd_2016.06+16.10.20160705-0ubuntu1.dsc
** Affects: ubuntu
Importance: Undecided
Assignee: Alexandros Frantzis (afrantzis)
Status: In Progress
** Tags: needs-packaging
--
You received this bug notification because you
** Description changed:
- repowerd, the next-gen power daemon for ubuntu-touch, needs to be added
- to universe.
+ repowerd (https://launchpad.net/repowerd), the next-gen power daemon for
+ ubuntu-touch, needs to be added to universe.
repowerd is in the process of being released through
And again: https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1474/console
and: https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1475/console
Raising importance to high.
** Changed
Thanks for reviewing!
> - The upstream version is 2016.06. But citrain already appends the date as
> part of the version.
> So unless you plan to make a habit of updating the upstream version, you may
> eventually get to
> versions like 2016.06+17.10.20180705, which has three different dates in
Is this a duplicate of https://bugs.launchpad.net/powerd/+bug/1540804 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597364
Title:
Option for screen dimming is sometimes not visible
To manage
** Changed in: mir
Status: New => Incomplete
** No longer affects: mir (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493013
Title:
CI test failure (segmentation fault) in
Public bug reported:
[Availability]
* Available in universe
[Rationale]
* This package is the new power manager for our phablet efforts (it's already
in RC phablet images)
[Security]
* No known security issues at this time
* Has *not* been reviewed by security team
[Quality assurance]
* This
Public bug reported:
Note that a much older version of unity-system-compositor had been previously
accepted into main:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1203588
[Availability]
* Available in universe
[Rationale]
* This package is the system compositor for
** Changed in: platform-api
Status: New => Fix Committed
** Changed in: repowerd (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: repowerd (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
--
You received this bug notification be
** Changed in: repowerd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602597
Title:
repowerd.service never starts due to dependency on missing lxc-
** Changed in: repowerd (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613506
Title:
The call screen still turns off af
> > Regression: Rc-proposed Nexus 4 autobrightness does not work
> > since r.380 autobrightness does not work anymore
> Is this information correct? Nexus 4 (mako) has rc-proposed image
revisions in the 500's range, MX4 > (arale) in the 300's range. Which
device is this bug about? Is the correct
> - Is there a team from the package-subscribers [1] list that would be
> a good fit for watching bugs for this package? Else we can try adding
> the repowerd-team, but that's a pretty specific team.
Perhaps ubuntu-phonedations-bugs (but not sure exactly what topics
phonedations works on).
> Regression: Rc-proposed Nexus 4 autobrightness does not work
> since r.380 autobrightness does not work anymore
Is this information correct? Nexus 4 (mako) has rc-proposed image
revisions in the 500's range, MX4 (arale) in the 300's range. Which
device is this bug about? Is the correct image
** Changed in: repowerd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613506
Title:
The call screen still turns off after rejecting the call on the
.
** Affects: systemd (Ubuntu)
Importance: High
Assignee: Alexandros Frantzis (afrantzis)
Status: In Progress
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I have proposed a fix for this issue upstream (merged into master at
[1]) and have cherry-picked the fix as a patch for the zesty systemd
package in the attached debdiff.
[1]
https://github.com/systemd/systemd/commit/7d049e304e8c9f6478bd3c6dc1781adf21d03e80
** Patch added:
** Changed in: repowerd (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637730
Title:
com.canonical.Unity.Screen interface introspection data is
** Changed in: repowerd (Ubuntu)
Status: New => In Progress
** Changed in: repowerd (Ubuntu)
Importance: Undecided => Low
** Changed in: repowerd (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
--
You received this bug notification because you are
Could you please attach /var/log/repowerd.log at the time of the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667001
Title:
[amd] screen-unblanking seems to flicker backlight on/off 5
unity-system-compositor 0.9.1 (the aforementioned silo) is unlikely to
be causing this, since:
1. I had a zesty system I hadn't updated in a week or so, which did not
exhibit the bug. After updating only USC to 0.9.1, I still couldn't
reproduce the bug. However, after doing a subsequent
** Changed in: repowerd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595947
Title:
brightness not changing from either u-s-s or hardkey on
Kevin, I can't reproduce this issue on an older dell latitude laptop.
When pressing the brightness hardware keys (actually Fn + up/down arrow)
the brightness slider moves accordingly, and then moving the slider
correctly changes the brightness.
Note that I am running zesty with a locally fixed
** Changed in: repowerd (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
** Changed in: repowerd (Ubuntu)
Status: New => In Progress
** Changed in: repowerd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are
** Also affects: repowerd
Importance: Undecided
Status: New
** Changed in: repowerd
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
** Changed in: repowerd (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
--
You received this bug notifi
** Changed in: platform-api
Assignee: (unassigned) => Thomas Voß (thomas-voss)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602604
Title:
package repowerd 2016.06+15.04.20160706.1-0ubuntu1
The problem was that the autobrightness algorithm was too slow to react
to the first light values after being enabled. This caused both the
related issues mentioned in comments in this bug (taeibot65's and
jibel's).
The fix is in silo 31 and in the process of being merged:
** Changed in: repowerd
Assignee: Alexandros Frantzis (afrantzis) => (unassigned)
** Changed in: repowerd (Ubuntu)
Assignee: Alexandros Frantzis (afrantzis) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
After some more experimentation with this fix, I noticed a strange
behavior on Nexus4. When autobrightness is enabled and the screen turns
on under bright light, the updated repowerd autobrightness algorithm
transitions the brightness to a high value (as expected), but the N4
display sometimes
The problem is that the program with dbus address :1.219 requested the
"active" state for the system, i.e. it has disallowed suspend.
The program first requests the "active" state and then clears it:
2017-02-28T09:50:13.018142+01:00 ubuntu-Inspiron-3138 repowerd[1041]:
UnityScreenService:
Thanks for the report. Please attach /var/log/repowerd.log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668596
Title:
Closing the lid does not suspend the device
To manage notifications about
** Changed in: qtubuntu
Status: Fix Committed => Fix Released
** Changed in: platform-api
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233988
** Changed in: unity-system-compositor/0.4
Status: Fix Committed => Fix Released
** Changed in: unity-system-compositor
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
** Changed in: repowerd
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
A new package 0.7.1+16.10.20160824-0ubuntu1 has been uploaded with the
required fixes:
> - android-properties should be a Build-Dep in arm64, right?
Added.
> - Is ubuntu-desktop-mir needed anymore?
No, removed.
> - This builds its autopilot package with python2...
Switched everything to
@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
> Can repowerd simply hold a lock until the screen dbus service is
connected?
(I am assuming you are referring to a display-on lock, which also
disallows suspends).
repowerd could hold a lock, but, IMO:
1. repowerd is the wrong place to put this logic. repowerd shouldn't
have to know, even
Could you please also attach the result of (i.e. the /tmp/top.txt file):
top -b -n10 -d1 > /tmp/top.txt
on the device that exhibits this behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bob, could you please attach /var/log/repowerd.log and /var/log/syslog
to this bug. It could help us debug this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502145
Title:
Apps can keep
An interesting snippet from the syslog:
// Suspend
Oct 4 18:14:26 ubuntu-phablet kernel: [20994.425695] suspend: enter suspend
Oct 4 18:14:26 ubuntu-phablet kernel: [20994.425756] PM: suspend entry
2016-10-04 16:14:26.176861138 UTC
Oct 4 18:14:26 ubuntu-phablet kernel: [20994.425878] PM:
> You can trigger the compilation by
> sudo rm /var/cache/apparmor/*
> sudo rm /var/lib/apparmor/profiles/*
Thanks Pat. I also found another way to do the same, tricking the
apparmor boot script into thinking this is the first it runs:
sudo rm /var/lib/apparmor/profiles/.apparmor.md5sums
--
** Attachment added: "New keep-display-on-during-boot.conf file"
https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1623853/+attachment/4755812/+files/keep-display-on-during-boot.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have attached two upstart .conf files implementing a fix that keeps
the display on until the phone has booted. In particular it acquires a
display-on lock when repowerd has started and releases it when lightdm
has started. After the display-on lock is released the display stays on
for 30s-1m
** Attachment added: "Updated repowerd.conf file"
https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1623853/+attachment/4755807/+files/repowerd.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note that the fix above doesn't implement my earlier suggestion to start
USC before apparmor finishes reprofiling. Unfortunately the way the job
dependencies are structured makes this change very difficult.
I would suggest that we clearly and prominently mention in our release
notes (and also
** Also affects: ubuntu-touch-session (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-touch-session (Ubuntu)
Importance: Undecided => Critical
** Changed in: ubuntu-touch-session (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
-
** Branch linked: lp:~afrantzis/ubuntu-touch-session/keep-display-on-
during-boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623853
Title:
Device appears to be off after updating to
Public bug reported:
When recording a video and the camera-app doesn't have permission to
access the microphone, no audio will be recorded. This is expected of
course, but it would be useful to have a visual indication that this is
happening, perhaps somewhere on the camera HUD. Without this
** Changed in: repowerd
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615001
Title:
lock display when idle timeout not honoured
To manage notifications
> In experimenting with this I noticed a typo in the source when getting this
> parameter, so the min
> will always be 10 on every system in spite of the config.
Thanks Pat, this is indeed a typo in repowerd.
That being said, two things to note in relation to the "brightness is
too strong":
1.
> can you compare what powerd used to do with what repowerd is doing now
in this scenario
Based on jibel's theory from comment #23:
With powerd the timeout logic was in USC, so if USC hasn't started (e.g.
because of apparmor recompilation in this case?) the device won't
suspend.
With repowerd
@jibel
> it takes on average 4.5s to adjust on arale/rc-proposed
That's a normal amount of time for autobrightness changes. Note that we
are using Android's autobrightness algorithm with a "debouncing" delay
of 4s (which is what powerd was using, and what Android is using). Of
course, we can
@taiebot65
Can you please attach the /var/log/repowerd.log file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613871
Title:
Regression: Rc-proposed Nexus 4 autobrightness does not work
To
Can you check whether repowerd or powerd is running:
ps -Af | grep powerd
Also please attach /var/log/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613871
Title:
Regression: Rc-proposed
> Can you check whether repowerd or powerd is running:
> ps -Af | grep powerd
Please attach the full output of the command, as there are other
services with suffix 'powerd' (e.g. upowerd) that are not related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
> I'm trying to get phablet-team added to that list too.
phablet-team is actually a much better fit for repowerd, so I'd prefer
we subscribed that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> After some more experimentation with this fix, I noticed a strange behavior
> on Nexus4.
> ... but the N4 display sometimes doesn't react to this high brightness
> setting, remaining
> at an arbitrary lower brightness setting instead. It seems that it takes a
> screen content
> update to
> OK, go ahead and subscribe them and I can approve this MIR.
phablet-team has been subscribed to bugs for the repowerd package:
https://bugs.launchpad.net/ubuntu/+source/repowerd/+subscriptions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Suggested solution is:
* Remove cmake-data from the build-dep list, since cmake depends on it anyway
* During CI cross-builds remove abi-compliance-checker from the build-deps. We
don't perform any ABI checks in our cross-build job.
Other solutions that I considered and rejected:
* Mark
** Description changed:
When trying to cross-build Mir with sbuild version >= 0.68.0, the build
fails with:
sbuild-build-depends-mir-dummy:armhf : Depends: cmake-data:armhf but it is
not installable
-Depends: abi-compliance-checker:armhf
but it
** Changed in: repowerd (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: platform-api
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-touch-session (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642360
Title:
Display occasionally st
** Description changed:
Occasionally the display stays on forever after boot in rc-proposed, due
to a keep display on request.
The problem seems to be that the keep-display-on-request introduced to
fix bug 1623853, sometimes doesn't get released due to races in the
upstart scripts.
** Description changed:
Occasionally the display stays on forever after boot in rc-proposed, due
to a keep display on request.
The problem seems to be that the keep-display-on-request introduced to
fix bug 1623853, sometimes doesn't get released due to races in the
upstart scripts.
Met this issue yesterday, updated 5 mins ago to 20161102.0.0, I think
this is solved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565985
Title:
vagrant vb ubuntu/xenial64 cannot mount synced
** Changed in: ubuntu-touch-session (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623853
Title:
Device appears to be off after updating to 15Sept2016's
** Merge proposal linked:
https://code.launchpad.net/~repowerd-team/repowerd/+git/repowerd/+merge/307941
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623853
Title:
Device appears to be off
/event
occurs (e.g., see [1]).
[1] https://bugs.launchpad.net/repowerd/+bug/1632573/comments/5
** Affects: lxc-android-config (Ubuntu)
Importance: Undecided
Assignee: Alexandros Frantzis (afrantzis)
Status: In Progress
** Branch linked: lp:~afrantzis/lxc-android-config/fix
** Changed in: repowerd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630382
Title:
Awful life battery since OTA 13
To manage notifications about
The repowerd part of the fix has landed in repowerd 2016.10. Now waiting
for the upstart script addition to land:
https://code.launchpad.net/~afrantzis/ubuntu-touch-session/keep-display-
on-during-boot
** Changed in: repowerd (Ubuntu)
Status: In Progress => Fix Committed
** Changed in:
> Suggested steps to improve the situation:
>
> * Fix typo in repowerd (assigned to me)
The fix has been released in repowerd 2016.10
> * Change device specific config files to have lower minimum values for
both (manual) brightness setting and the autobrightness curve.
This is not done yet. Not
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
** Summary changed:
- Awful life battery since OTA 13
+ [mako] Awful life battery since OTA 13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630382
Title:
[mako] Awful life battery since OTA 13
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
** 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 Ubunt
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
... I *suspect* this value may ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483427
Title:
Possible to manually set display brightness to 0 on Ubuntu Touch on
Aquaris E5
To manage
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
Thanks for reporting. Please attach /var/log/syslog and
/var/log/repowerd.log from an affected device, as these will help us
debug the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647895
** No longer affects: repowerd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647895
Title:
Tablet suspends while playing video or audio in browser
To manage notifications about this bug
** Changed in: repowerd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674736
Title:
messages are logged on every input event
To manage
** Changed in: repowerd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668596
Title:
Closing the lid does not suspend the device
To manage notifications
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
** Changed in: repowerd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668596
Title:
Closing the lid does not suspend the device
To manage
I have attached a protobuf debdiff fix for this issue. It's a backport
from upstream (more details in the debian patch metadata).
** Patch added: "protobuf package fix debdiff"
501 - 600 of 619 matches
Mail list logo
