@Corey In our case there was no release upgrade. We have been to Ussuri
for many weeks and running happily. The problem came up only after we
update the relevant ubuntu packages from 16.3.0 to 16.3.1. Just
reverting back to 16.3.0 resolved the issue.
--
You received this bug notification because
Public bug reported:
We run a juju managed Openstack Ussuri on Bionic. After updating neutron
packages from 16.3.0 to 16.3.1 all virtual routers stopped working. It
seems that most (not all) namespaces are created but have only the lo
interface and sometime the ha-XYZ interface in DOWN state. The
Public bug reported:
I am trying to install Ubuntu 20.04.1 alongside Windows 10 on my new XMG
laptop. The laptop has a NVMe SSD and a Nvidia 2060 graphics card.
Firstly, after selecting Ubuntu from boot options, I get a "Initramfs
unpacking failed: Decoding failed" error followed by a "nouveau DRM
** Tags added: focal
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893227
Title:
Scrambled display with newer grubx64.efi bootloader and
terminal_output gfxterm
To manage
Public bug reported:
Hello and thanks for maintaining grub in Ubuntu.
We've been using grub EFI boot loader in Bionic and Focal official cloud
images. After upgrading grub packages from 2.02-2ubuntu8.14 to
2.02-2ubuntu8.17 we are having trouble with console display (provided by
QEMU VNC) as it is
Public bug reported:
main.log
2020-06-07 21:24:46,248 DEBUG Marking 'ubuntu-desktop' for upgrade
2020-06-07 21:24:46,486 WARNING Can't mark 'ubuntu-desktop' for upgrade
(E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by
held packages.)
2020-06-07 21:25:38,166 ERROR Di
managed to apply a slightly modified version of that patch to Ubuntu
source package version 3.25.1-3 and successfully built it, producing a
kafka module binary package.
Cheers,
Alexandros
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
kafka destinations?
Thanks,
Alexandros
** Affects: syslog-ng (Ubuntu)
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/1879734
Title:
Kafka module binary
Playing with different resolutions and rates using xrandr solved the
problem for me on a DELL XPS 15 with Ubuntu 18.04. If I go with a
resolution of 1920x1080 and a rate of 60 Hz the TV shows a black screen.
Changing to other modes and rates solves the problem. For example,
typing in a terminal
> https://afrantzis.com/posts/bless-0-6-1/ Bless has moved to a new home,
> https://github.com/afrantzis/bless, and a new release has been made.
>
> 1) Does this fix the issue?
Yes (along with many other issues).
> 2) Will the official packages be updated?
I filed an update request for the Debia
I am on Ubuntu 18.04, have both a wireless headset and speakers, amd
after connecting them for the first time and everything works properly,
after my PC reboots or even sleeps and I am trying to re-connect them,
while they are paired they do not connect at all. If I remove the
device, I cannot even
That worked indeed! Thanks!
On 14/05/2018 03:57 μμ, Darren Legge wrote:
> The new ppa fixes it for me.
> https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-4
> http://kicad-pcb.org/download/ubuntu/
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Public bug reported:
After upgrading to UbuntuStudio 18.04, Kicad 4.0.7 won't display its graphics
properly, neither Eeschma, not Pcbnew.
As the mouse moves around the screen displays the cross that follows it many
times (image won't refresh), in both Eeschema and Pcbnew, and Pcbnew won't show
I have the same problem in
Ubuntu 16.04
4.4.0-34-generic
Realtek RT2561/RT61 rev B 802.11g driver: rt61pci
I dont know it's a kernel issue only but testing in another distro with
4.4.13 it'ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** 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
signee: (unassigned) => Alexandros Frantzis (afrantzis)
** Changed in: mir (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
** Changed in: mir
Status: New => In Progress
** Changed in: mir (Ubuntu)
Status: New => In Progress
--
You received this bug notifi
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
** 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 notif
** 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 notifica
** 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 a
Also note that repowerd logs are log-rotated, so there is no risk of
taking up too much disk space.
> Otherwise I am in favor of not spamming syslog.
Sure, I will remove /v/l/syslog output.
** Changed in: repowerd (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
> Question, does repowerd "know" there's a lid involved? (or could we
make it know there's a lid involved)
It knows about the lid, so we could customize the behavior just for the
lid-closing action.
> I'm open to other thoughts - but I can't imagine where a user would
expect their device to not s
Some clarifications: these log messages correspond to activity events as
they arrive from USC. They are not sent for every input event, but
instead at most once every 0.5s seconds and only if USC gets an input
event in that interval.
Now to the concerns:
> This makes debugging cumbersome and
It'
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"
https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1667352/+attachment/4839390/+files/protobuf-zesty-fix-1667352
As mentioned in the previous comment the failure to suspend is caused by
a program incorrectly holding a suspend block after it is needed.
Repowerd correctly respects the block and doesn't suspend until the
block is released. Do we want repowerd to act differently?
--
You received this bug notifi
** Changed in: repowerd (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1660438
Title:
display brightness & slider follows hw keys or mousing, but jumps
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: dbus_r
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 th
** 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
Tit
** 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.
https://bugs.l
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 times
** 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 mi
@joshu aghora (josh-gura)
Well it seems that the Ubuntu Gnome team has no plans to fix this for 16.04
LTS.
You can either add the Gnome Team staging :ppa from Launchpad and
upgrade Gnome to 3.20 (not ideal, because it might break the system) or
move to another distro.
I am still running the sam
** 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 a
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 sys
** 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
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 dist-upgra
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: "systemd-fix-1661568.de
.
** 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 *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 notificati
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
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
** 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
T
** 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 g
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
Titl
** 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
** 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. Th
** 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. Th
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 folde
** 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.
https://bugs.launchpad.net/bugs/160
/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
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: can
> 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
** 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 th
** 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 aft
** 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 rc
** 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 15Sept2016's
** 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)
-
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 perh
** 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.
https://bugs.launchpad.net/b
** 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 Ub
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 (dep
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 scre
> 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
--
You
> 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 impli
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: Synci
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.
https://bugs.launchpad.net/bugs/163038
** 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 is
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 abi-com
@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
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 visua
> 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 al
> 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.
** 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 a
Getting this in 16.04 Ubuntu Gnome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568043
Title:
gnome-photos crashed with SIGABRT in g_assertion_message()
To manage notifications about this bug go
Just happened to me also on Ubuntu Gnome 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about
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 pytho
> 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 t
> 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 "rem
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 does
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:
https://launchpad.net/~
** 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
** 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 a
** 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
> 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.
https://bugs.launchpad.net/bugs/161358
> 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
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 N
** 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 remote
> - 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).
mir-te
** 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 i
> 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 typ
@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 redu
@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 manage
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 ou
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 p
1 - 100 of 622 matches
Mail list logo
