[Bug 1927868] Re: vRouter not working after update to 16.3.1
@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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] [NEW] vRouter not working after update to 16.3.1
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 underlying tap interfaces are also in down. neutron-l3-agent has many logs similar to the following: 2021-05-08 15:01:45.286 39411 ERROR neutron.agent.l3.ha_router [-] Gateway interface for router 02945b59-639b-41be-8237-3b7933b4e32d was not set up; router will not work properly and journal logs report at around the same time May 08 15:01:40 lar1615.srv-louros.grnet.gr neutron-keepalived-state-change[18596]: 2021-05-08 15:01:40.765 18596 INFO neutron.agent.linux.ip_lib [-] Failed sending gratuitous ARP to 62.62.62.62 on qg-5a6efe8c-6b in namespace qrouter-02945b59-639b-41be-8237-3b7933b4e32d: Exit code: 2; Stdin: ; Stdout: Interface "qg-5a6efe8c-6b" is down May 08 15:01:40 lar1615.srv-louros.grnet.gr neutron-keepalived-state-change[18596]: 2021-05-08 15:01:40.767 18596 INFO neutron.agent.linux.ip_lib [-] Interface qg-5a6efe8c-6b or address 62.62.62.62 in namespace qrouter-02945b59-639b-41be-8237-3b7933b4e32d was deleted concurrently The neutron packages installed are: ii neutron-common 2:16.3.1-0ubuntu1~cloud0 all Neutron is a virtual network service for Openstack - common ii neutron-dhcp-agent 2:16.3.1-0ubuntu1~cloud0 all Neutron is a virtual network service for Openstack - DHCP agent ii neutron-l3-agent 2:16.3.1-0ubuntu1~cloud0 all Neutron is a virtual network service for Openstack - l3 agent ii neutron-metadata-agent 2:16.3.1-0ubuntu1~cloud0 all Neutron is a virtual network service for Openstack - metadata agent ii neutron-metering-agent 2:16.3.1-0ubuntu1~cloud0 all Neutron is a virtual network service for Openstack - metering agent ii neutron-openvswitch-agent 2:16.3.1-0ubuntu1~cloud0 all Neutron is a virtual network service for Openstack - Open vSwitch plugin agent ii python3-neutron2:16.3.1-0ubuntu1~cloud0 all Neutron is a virtual network service for Openstack - Python library ii python3-neutron-lib2.3.0-0ubuntu1~cloud0 all Neutron shared routines and utilities - Python 3.x ii python3-neutronclient 1:7.1.1-0ubuntu1~cloud0 all client API library for Neutron - Python 3.x Downgrading to 16.3.0 resolves the issues. ** Affects: neutron (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916791] [NEW] grub installation crashes
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: failed to create kernel channel, -22" error. The installation proceeds after that (although it is slower than normal), and it finally crashes giving me the "executing grub-install /dev/nvme0n1 failed. This is a fatal error" error. I don't know if what I am describing in the beginning is related to the final error I'm getting. I am a beginner in Linux ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 24 19:12:25 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash acpi=off --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916791 Title: grub installation crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1916791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893227] Re: Scrambled display with newer grubx64.efi bootloader and terminal_output gfxterm
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1893227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893227] [NEW] Scrambled display with newer grubx64.efi bootloader and terminal_output gfxterm
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 scrambled and unreadable. See attached screenshot. We have noticed that the problem manifests itself when terminal_output is set to "gfxterm" but is not present when set to "console". Additionally we verified that in Bionic the problem manifests itself with boot loader provided by 1.93.19+2.02-2ubuntu8.17 (sha1sum: 7be316b0542921956dc3742d70b26e409ca83ef0 /boot/efi/EFI/BOOT/grubx64.efi) while the boot loader provided by 1.93.15+2.02-2ubuntu8.14 (sha1sum: 2895a67157d97b0d3825987639d817a08aad3da8 /boot/efi/EFI/BOOT/grubx64.efi) works just fine. Problem manifests itself in Focal hosts as well featuring grub-efi- amd64-signed version 1.142.4+2.04-1ubuntu26.2. Boot loader and related files are installed by grub in /boot/efi/EFI/BOOT/ during the image creation like this: ``` grub-install --boot-directory=/boot --efi-directory=/boot/efi --target=x86_64-efi --removable --uefi-secure-boot --no-nvram ``` said invocation among other things does copy files provided by grub-efi-amd64-signed package: ``` grub-install: info: copying `/usr/lib/grub/x86_64-efi-signed/gcdx64.efi.signed' -> `/boot/efi/EFI/BOOT/grubx64.efi'. grub-install: info: copying `/usr/lib/shim/shimx64.efi.signed' -> `/boot/efi/EFI/BOOT/BOOTX64.EFI'. grub-install: info: copying `/usr/lib/shim/mmx64.efi' -> `/boot/efi/EFI/BOOT/mmx64.efi'. grub-install: info: copying `/usr/lib/shim/BOOTX64.CSV' -> `/boot/efi/EFI/BOOT/BOOTX64.CSV'. grub-install: info: copying `/boot/grub/x86_64-efi/load.cfg' -> `/boot/efi/EFI/BOOT/grub.cfg'. ``` A naive experimentation, swapping the old boot loader in place of the newer, restores display back to normal. We will be happy to provide more details if needed. ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot_2020-08-27_17-20-38.png" https://bugs.launchpad.net/bugs/1893227/+attachment/5405198/+files/Screenshot_2020-08-27_17-20-38.png -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1893227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882449] [NEW] Upgrade from 18.04 LTS to 20.04LTS failed
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 Dist-upgrade failed: 'Broken packages after upgrade: colord' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 21:38:16 2020 InstallationDate: Installed on 2020-01-20 (138 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-06-07 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882449 Title: Upgrade from 18.04 LTS to 20.04LTS failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1882449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879734] Re: Kafka module binary package missing from syslog-ng
For what's it worth there is a commit in debian package version 3.27.1-1 which enables kafka support: https://github.com/gcsideal/syslog-ng- debian/commit/d7ab46c6f8d33d35c3d3ee0d09536be654b11929 This package has been actually introduced in Debian's NEW queue a couple of days ago. I 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 Ubuntu. https://bugs.launchpad.net/bugs/1879734 Title: Kafka module binary package missing from syslog-ng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1879734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879734] [NEW] Kafka module binary package missing from syslog-ng
Public bug reported: Hello and thanks for maintaining this package. syslog-ng-incubator source package used to provide syslog-ng-mod-kafka binary package up to Bionic release. Given that syslog-ng-incubator has been discontinued and modules have been migrated to syslog-ng by upstream (as pointed out here https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=921650) I would expect syslog-ng source package to provide a kafka module as well. The new librdkafka based destination has been imported from incubator to syslog-ng as of upstream version 3.21.1: https://github.com/syslog-ng /syslog-ng/commit/9eb963513afed9363783274bbcd2be2e97ceb10f So Ubuntu Focal, featuring upstream version 3.25.1 (https://github.com/gcsideal/syslog-ng- debian/commit/09828d93626bd6e425ac3baaec01611ce870fb22) does include the new librdkafka based implementation. Could you please provide a binary package for 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 package missing from syslog-ng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1879734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
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 xrandr --output DP-1-3 --mode 1360x768 --rate 60 made it work. If I go for a resolution of 1920x1080, I have output only for a rate of 25 Hz. I don't know why exactly this happens. Maybe it depends on the TV? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1771185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622951] Re: bless fails to handle user config
> 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 Debian repo some time ago here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914217, but there hasn't been any response yet. Note that 0.6.2 was released today with more improvements. ** Bug watch added: Debian Bug tracker #914217 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914217 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622951 Title: bless fails to handle user config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bless/+bug/1622951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764645] Re: Bluetooth not working
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 find it afterwards, and no fix is working. Seriously, this is frustrating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764645 Title: Bluetooth not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1767652] Re: kicad on ubuntu mate 18.04 cursor ghosting (eeshcema), pcb design shrinked (pcbnew)
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767652 Title: kicad on ubuntu mate 18.04 cursor ghosting (eeshcema), pcb design shrinked (pcbnew) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kicad/+bug/1767652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770430] [NEW] Kicad 4.0.7 doesn't display its graphics properly
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 the actual board designs. Reading various fora, it seems to be a problem with Python (wxpython?) between Kicad and the new Ubuntu. The attached image is a screen shot from Pcbnew, that shows how the program displays circuit board designs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kicad 4.0.7+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Thu May 10 16:26:01 2018 InstallationDate: Installed on 2017-09-21 (230 days ago) InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Alpha amd64 (20170829) SourcePackage: kicad UpgradeStatus: Upgraded to bionic on 2018-05-04 (6 days ago) ** Affects: kicad (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "pcbnew_cropped.png" https://bugs.launchpad.net/bugs/1770430/+attachment/5137277/+files/pcbnew_cropped.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770430 Title: Kicad 4.0.7 doesn't display its graphics properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kicad/+bug/1770430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422190] Re: phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422190 Title: phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1422190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674389 Title: Session Indicator's "Suspend" button has no effect in Unity 8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679591] Re: Laptop suspends when closing lid with an external display plugged
** Also affects: mir Importance: Undecided Status: New ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Importance: Undecided => High ** Changed in: mir Importance: Undecided => High ** Changed in: mir Assignee: (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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679591 Title: Laptop suspends when closing lid with an external display plugged To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1679591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 inhibition just means that another program has requested a suspend inhibition from repowerd. In any case, as discussed in bug 1668596, repowerd will soon stop acquiring logind suspend inhibitions. ** 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/1674389 Title: Session Indicator's "Suspend" button has no effect in Unity 8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668596] Re: Closing the lid does not suspend the device
** 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 notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674736] Re: messages are logged on every input event
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1674736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668596] Re: Closing the lid does not suspend the device
** 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 about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674736] Re: messages are logged on every input event
> I think its bad practice to log this way on a production system, maybe just > my opinion. > Can this be restricted to when a debug option is enabled? We decided to make logging always-on in repowerd based on bad debugging experiences with the old USC/powerd combination. This decision has paid off since it has made it much easier to debug problems in the wild, especially ones that are hard to reproduce. No need to tell the user to enable debugging and then try to reproduce it again... when something goes wrong they can just send us the log file and we will have the full picture of what was going on in repowerd. As discussed above, the cost of logging is negligible, so, in my opinion, we have much to lose and little to gain by disabling full logging by default. Of course, we can revisit this decision if we find that the cost-benefit scale is starting to tip the other way. 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) ** Changed in: repowerd (Ubuntu) Importance: Undecided => Low ** 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/1674736 Title: messages are logged on every input event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1674736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668596] Re: Closing the lid does not suspend the device
> 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 suspend with a lid being shut. > For example when you're downloading some files in the background, or watching a video on an external screen - your laptop might be docked and closed in that case. repowerd already handles the external display case and doesn't suspend if an external display is connected and active when the lid is closed (you can still suspend explicitly or by inactivity timeout if configured). In other cases, whether closing the lid should respect suspend blocks is a matter of trade-offs: + The user won't inadvertently interrupt a critical operation that has acquired a suspend block (e.g. flashing a firmware update) + A suspend block is more meaningful, provides stronger guarantees + Better support for multiple user sessions (e.g. a non-active user is flashing firmware and the active user closes the lid) - Broken (malicious?) apps holding suspend blocks for more than required can keep the device awake - Closing the lid has unpredictable behavior (may or may not suspend) An approach I have been considering for the past few days and I am warming up to: * Closing the lid (if configured to suspend) and explicitly suspending, should not take into account blocks and should suspend unconditionally UNLESS any blocks have been requested by a privileged (euid=0) process. * Suspending after an inactivity timeout (if configured) should always take into account suspend blocks The differentiation is that the first case involves explicit user actions, whereas the second case does not. The "UNLESS" part in the first case allows privileged processes to force suspend blocks for very important cases (e.g. firmware updates). For the cases the user doesn't want to suspend after closing the lid they can change the setting in the power settings dialog. Thoughts? -- 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 this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674736] Re: messages are logged on every input event
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's true that the log seems somewhat spammed with these messages. However, activity events affect repowerd's state machine fundamentally and we would not be able to debug effectively if we didn't log them. > is probably not great for battery life >From past measurements, the CPU time used by logging, and thus the effect on power, is negligible. The measurements also make sense from coarse-grained analysis of the processing involved: every time we have an input event the system needs to react to it possibly by compositing and doing other app specific processing. A couple of times per second, if we have input events, we also send an activity event to repowerd, which needs to update its state (inactivity timeouts etc). Logging the activity event is a negligible portion of the overall processing involved. If we still consider this is an issue we could reduce the maximum rate at which USC sends activity events. For example, we could change from the current 2Hz to 1Hz. The downside is that the accuracy of inactivity timeouts depends on the rate of activity events. With 2Hz we have a maximum error of 0.5s, with 1Hz the maximum error goes up to 1s. Another related topic is that we currently log to both /var/log/repowerd.log /var/log/syslog. /v/l/syslog logging was added so that we could correlate easily between repowerd events and other system events (e.g. suspending). If we think that the benefit of easy correlation is not worth repowerd "spamming" /v/l/syslog, we could consider logging only to /v/l/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/1674736 Title: messages are logged on every input event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1674736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync
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.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667352 Title: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668596] Re: Closing the lid does not suspend the device
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 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 this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660438] Re: display brightness & slider follows hw keys or mousing, but jumps about & brightness flickers at low end
** 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 about & brightness flickers at low end To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1660438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668596] Re: Closing the lid does not suspend the device
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_requestSysState(:1.219,active,1) 2017-02-28T09:50:13.030120+01:00 ubuntu-Inspiron-3138 repowerd[1041]: UnityScreenService: dbus_requestSysState(:1.219,active,1) => 1 2017-02-28T09:50:14.484885+01:00 ubuntu-Inspiron-3138 repowerd[1041]: UnityScreenService: dbus_clearSysState(:1.219,1) And ~10 seconds later it requests the "active" state again and never clears it after that: 2017-02-28T09:50:25.021176+01:00 ubuntu-Inspiron-3138 repowerd[1041]: UnityScreenService: dbus_requestSysState(:1.219,active,1) 2017-02-28T09:50:25.030948+01:00 ubuntu-Inspiron-3138 repowerd[1041]: UnityScreenService: dbus_requestSysState(:1.219,active,1) => 2 -- 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 this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668596] Re: Closing the lid does not suspend the device
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 this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1233988] Re: With Mir enabled: platform-api apps crash with SIGABRT in __gnu_cxx::__verbose_terminate_handler(), thrown from mir::client::DisplayConfiguration::copy_to_client()
** 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 Title: With Mir enabled: platform-api apps crash with SIGABRT in __gnu_cxx::__verbose_terminate_handler(), thrown from mir::client::DisplayConfiguration::copy_to_client() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1233988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543495] Re: [FHD] boot splash not in native orientation
** 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.launchpad.net/bugs/1543495 Title: [FHD] boot splash not in native orientation To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1543495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667001] Re: [amd] screen-unblanking seems to flicker backlight on/off 5 times before display resumes
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 before display resumes To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637730] Re: com.canonical.Unity.Screen interface introspection data is missing signals
** 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 missing signals To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1637730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301083] Re: Drag and Drop File Auto Opens Folders
@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 same Ubuntu Gnome 16.04 installation that I had when I reported this bug 7 months ago and I've learnt to live with it. But it's still very annoying and I am considering switching to Open Suse Leap with Gnome 3.20 because of this bug and other problems that I am currently having with 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/1301083 Title: Drag and Drop File Auto Opens Folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1301083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637730] Re: com.canonical.Unity.Screen interface introspection data is missing signals
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637730 Title: com.canonical.Unity.Screen interface introspection data is missing signals To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1637730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660438] Re: display brightness & slider follows hw keys, but brightness does not follow slider unity8 zesty
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 systemd package (see bug 1661568). I wonder if what you are seeing is a side-effect of the aforementioned systemd issue. My proposal is to try again in a few days, when the fixed systemd package will have landed to zesty (hopefully). If the problem persists we can investigate further. ** Changed in: repowerd (Ubuntu) Status: New => Incomplete -- 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, but brightness does not follow slider unity8 zesty To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1660438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595947] Re: brightness not changing from either u-s-s or hardkey on unity8-desktop
** 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 unity8-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663106] Re: [regression] Logging in to Unity8 takes 25 seconds (the default DBus timeout)
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-upgrade the issue appeared, which indicates that one of the dist-upgraded packages is involved. I have uploaded the full dist-upgraded package list at: https://pastebin.canonical.com/178774/. 2. In a fully updated zesty system exhibiting the issue, downgrading USC to 0.9.0 does not fix the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663106 Title: [regression] Logging in to Unity8 takes 25 seconds (the default DBus timeout) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661568] Re: logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property
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.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1661568/+attachment/4812524/+files/systemd-fix-1661568.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661568 Title: logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1661568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661568] [NEW] logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property
Public bug reported: logind fails to emit a DBus PropertiesChanged signal for the org.freedesktop.login1.Seat.ActiveSession DBus property. See https://github.com/systemd/systemd/issues/5210. This breaks repowerd on zesty since repowerd depends on this signal to track the active session. ** 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 Ubuntu. https://bugs.launchpad.net/bugs/1661568 Title: logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1661568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 for dimming the screen. If you set the normal brightness value at a normal or high level, do you notice the screen dimming a bit before the inactivity timeout expires, or do you just see the screen blanking without dimming first? -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 may need to reflash a clean image if things go very wrong. To try the updated packages follow the instructions from the link below: https://wiki.ubuntu.com/Process/Merges/TestPlans/repowerd Let me know if/how the fix works for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588526 Title: [mako] Alarm doesn't ring when screen locked To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630382] Re: [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 may need to reflash a clean image if things go very wrong. To try the updated packages follow the instructions from the link below: https://wiki.ubuntu.com/Process/Merges/TestPlans/repowerd Let me know if/how the fix works for you. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630382] Re: [mako] Awful life battery since OTA 13
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647895] Re: Tablet suspends while playing video or audio in browser
** 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 go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1647895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647895] Re: Tablet suspends while playing video or audio in browser
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 Title: Tablet suspends while playing video or audio in browser To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1647895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588526 Title: [mako] Alarm doesn't ring when screen locked To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642360] Re: Display occasionally stays on forever after boot in rc-proposed
** 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 stays on forever after boot in rc-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642360] Re: Display occasionally stays on forever after boot in rc-proposed
** 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. This happens if the lightdm job starts before the keep-
display-on-during-boot job starts, in which case the keep-display-on-
during-boot job never gets the signal it needs to stop ("stop on started
lightdm").
This issue can be reproduced easily by changing the related upstart
script timings, for example, by inserting a "sleep 10" at the end of the
- repowerd.conf post-start stanza.
+ repowerd.conf pre-start stanza (or post-start stanza, it has the same
+ effect).
--
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 stays on forever after boot in rc-proposed
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642360/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642360] Re: Display occasionally stays on forever after boot in rc-proposed
** 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. This happens if the lightdm job starts before the keep-
display-on-during-boot job starts, in which case the keep-display-on-
during-boot job never gets the signal it needs to stop ("stop on started
lightdm").
This issue can be reproduced easily by changing the related upstart
script timings, for example, by inserting a "sleep 10" at the end of the
- repowerd.conf pre-start stanza.
+ repowerd.conf post-start stanza.
--
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 stays on forever after boot in rc-proposed
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642360/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565985] Re: vagrant vb ubuntu/xenial64 cannot mount synced folders
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 folders To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1565985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602604] Re: package repowerd 2016.06+15.04.20160706.1-0ubuntu1 [modified: lib/systemd/system/repowerd.service] [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] failed to install/upgrad
** 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/1602604 Title: package repowerd 2016.06+15.04.20160706.1-0ubuntu1 [modified: lib/systemd/system/repowerd.service] [origin: LP-PPA-ci-train-ppa- service-stable-phone-overlay] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1602604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633108] [NEW] syslog deleted after reaching 20M limit
Public bug reported: Due to logrotate rules in lxc-android-config, when /var/log/syslog reaches 20M it is deleted and logging continues in a brand new empty file. If the timing is unfortunate users may lose all syslog information pertaining to a bug or other event of interest soon after the bug/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-1633108-logrotate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633108 Title: syslog deleted after reaching 20M limit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1633108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
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: canonical-devices-system-image Status: Fix Committed => 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-proposed image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618391] Re: Brightness is too strong
> 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 sure which the best team to handle this. ** Changed in: canonical-devices-system-image Status: Fix Committed => Confirmed ** Changed in: repowerd (Ubuntu) Status: Confirmed => 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/1618391 Title: Brightness is too strong To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630382] Re: Awful life battery since OTA 13
** 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 this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
** 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 after updating to 15Sept2016's rc-proposed image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
** 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-proposed image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
** 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 rc-proposed image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
** 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) -- 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-proposed image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
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 perhaps in phone upgrade UI?) that the first boot after an upgrade may take a significantly longer time than usual, so the users expect the delay. -- 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-proposed image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
** 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/bugs/1623853 Title: Device appears to be off after updating to 15Sept2016's rc-proposed image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
** 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 Ubuntu. https://bugs.launchpad.net/bugs/1623853 Title: Device appears to be off after updating to 15Sept2016's rc-proposed image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
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 (depending on the user timeout). To test this, copy *both* attached files into /etc/init/ on the device (overwrite the existing repowerd.conf, keep-display-on-during-boot.conf is a new file) and reboot. If you want to try the scenario described in this bug, do: sudo rm /var/lib/apparmor/profiles/.apparmor.md5sums before rebooting. Please try it out and let me know what you think, so I can push the fixes to the respective packages. -- 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-proposed image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1502145] Re: Apps can keep screen lit permanently
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 screen lit permanently To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
> 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 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-proposed image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
> 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 implicitly, about the boot time dependencies. As an example of why this is fragile, if we decide to move USC before or in parallel with apparmor reprofiling (which I suggest we do), this logic will stop having the desired effect. It would be much better to use a suspend block during the whole boot process (repowerd started -> unity8 started) using the init system facilities, as described in comment #31. 2. this lock by itself would only improve the user experience very slightly, since it would brighten the backlight but the screen would still remain black and unresponsive to power keys for some time until USC starts. I think the best solution from a UX and cleanliness perspective would be: 1. Start USC before or in parallel with apparmor reprofiling, so the user gets some visual indication that the system is working and can at least turn the screen on/off. This is optional, but I think improves UX a lot. 2. Acquire a suspend blocker (using an init job) when repowerd starts, release when unity8 (not USC) has started or failed to start. I'll try to find a way to recreate the "profiles need recompilation" scenario without flashing a new image, so we can test easily. I will provide a prototype for the proposed solution for people to try out. -- 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-proposed image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630382] Re: Awful life battery since OTA 13
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: Syncing filesystems...
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.507337] Freezing user space
processes ... (elapsed 0.001 seconds) done.
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.526535] sync done.
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.749455] Freezing remaining
freezable tasks ... (elapsed 0.003 seconds) done.
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.752782] Suspending console(s)
(use no_console_suspend to debug)
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.764166] msm_fb_ext_suspend:
Turning off HPD circuitry
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.803446] PM: suspend of devices
complete after 46.878 msecs
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.805216] PM: late suspend of
devices complete after 1.739 msecs
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.808878] active wake lock
alarm_rtc, time left 96
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.808909] power_suspend_late return
-11
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.808970] dpm_run_callback():
power_suspend_late+0x0/0x68 returns -11
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.809031] PM: Device power.0 failed
to suspend noirq: error -11
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.811290] PM: noirq resume of
devices complete after 2.227 msecs
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.814952] PM: early suspend of
devices complete after 1.739 msecs
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.814983] PM: Some devices failed
to power down
// Immediately resume
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.821575] msm_fb_ext_resume:
Turning on HPD circuitry
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.827496] PM: resume of devices
complete after 12.482 msecs
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.829022] Restarting tasks ... done.
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.869919] PM: suspend exit
2016-10-04 16:14:27.047214477 UTC
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.869950] suspend: exit suspend,
ret = -11 (2016-10-04 16:14:27.047214477 UTC)
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.869950] active wake lock
alarm_rtc, time left 89
Oct 4 18:14:27 ubuntu-phablet kernel: [20994.869950] suspend: abort suspend
Oct 4 18:14:27 ubuntu-phablet kernel: [20995.761511] wake lock alarm_rtc,
expired
... and this is going on continuously while the phone is idle. The phone
suspends but it immediately wakes up, seemingly because a very short
alarm is set ("active wake lock alarm_rtc, time left XX", XX is in
milliseconds), then it suspends again, and wakes up again immediately,
and so on. I don't know who is setting this alarm.
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1603024 could
be related.
--
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1630382/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630382] Re: Awful life battery since OTA 13
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/1630382 Title: Awful life battery since OTA 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1630382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628507] Re: Mir fails to cross-build with newer sbuild versions
** 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 not installable + Depends: abi-compliance-checker:armhf but it is not installable This is caused by a change ([1]) in the way sbuild installs build-deps for the package under build. Previously sbuild used the 'apt-get build- dep' command, but recent versions calculate the build-deps manually (using the Dpkg perl module) and install the -dummy package instead. This change isn't a problem in and of itself, but unfortunately uncovers a problem in the cmake-data and abi-compliance-checker packages. In particular, the two packages are not multi-arch ready and sbuild can't - know that it needs to install their native/build (amd64) version, using - the host (armhf) version instead. + know that it needs to install their native/build (amd64) version, so it + uses the host (armhf) version instead. The previous 'apt-get build-dep' way worked because APT is patched in ubuntu (but not in debian) to consider packages with architecture 'all' as 'Multi-Arch: foreign' ([1],[2]). The Dpkg perl modules don't contain such a patch. [1] https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/?id=e227c8f3e10edd78bc71350380f559c481634b79 [2] https://wiki.debian.org/Multiarch/CrossDependencies [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666772 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628507 Title: Mir fails to cross-build with newer sbuild versions To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1628507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628507] Re: Mir fails to cross-build with newer sbuild versions
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-compliance-checker as ':native' in the build-deps. This makes sbuild build-dep installation happy, but still fails during the actual package build, because dpkg-checkbuilddeps doesn't use packages with architecture 'all' to satisfy ':native' build-deps. Not sure what the right behavior for dpkg-checkbuilddeps should be. * Fix the abi-compliance-checker package to support Multi-Arch. This is the ideal solution and should be eventually done for future releases. However, backporting the change to older releases is not too appealing at this point (we need to unblock Mir CI). ** Also affects: abi-compliance-checker (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/1628507 Title: Mir fails to cross-build with newer sbuild versions To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1628507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 alarm not going off at all until you pressed the power button? Unless I am misunderstanding, your comment seems to describe two independent issues seen in two different occasions: 1. alarm not going off at all 2. change in alarm sound not being applied -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588526 Title: Alarm doesn't ring when screen locked To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627053] [NEW] Need visual indication that video recording isn't capturing sound
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 visual indication the users has no way of knowing that the video won't have any sound, until they try to play back the video, and then it's too late. I have a few important videos without sound for this reason :/. Also, taking a step back, a more fundamental solution would be to follow Matthew's suggestion from bug 1554142: the camera-app shouldn't ask for a special microphone permission, "the ability to record video includes the ability to use the microphone". ** Affects: camera-app (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/1627053 Title: Need visual indication that video recording isn't capturing sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1627053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
> 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 all the timeout logic is in repowerd itself; USC is used only as a source of events (e.g. power button, touches). In this case, since repowerd doesn't get any requests to disallow suspending, it correctly suspends after the normal timeout. I think a sensible solution would be to disallow suspending until at least USC (and possibly unity8) is up and running. This could be achieved by acquiring and releasing a suspend blocker from repowerd at the init system level, with a prohibit_suspend_at_boot upstart/systemd job: on "repowerd started" acquire a suspend blocker, on "usc/unity8 started" release the blocker. Even without the suspend issue, the initial delay after first boot due to apparmor recompilation or whatnot does not provide a good experience, since there is no visual indication that something is going on for a significant amount of time. This brings up the following questions: 0. Why do we need to recompile the profiles at first boot? 1. Could we start USC before the recompilation and other time consuming tasks start, so at least the user would be able to see the dots animating (and incidentally this would also solve the suspend issue)? -- 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-proposed image To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618391] Re: Brightness is too strong
> 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. The screenBrightnessSettingMininum config has no effect on autobrightness; it only affects the minimum value manually settable by the user. Autobrightness is governed by the curve specified in "config_autoBrightnessLcdBacklightValues" in the device specific config file (/usr/share/powerd/device_configs/config-default.xml) 2. By pure chance, this bug has no effect on E4.5 and allows an even darker setting on MX4 (not sure about PRO5) for the manual case, since it defaults to 10 for min brightness, whereas the actual config values for the aforementioned devices are 10 and 15 respectively. Suggested steps to improve the situation: * Fix typo in repowerd (assigned to me) * Change device specific config files to have lower minimum values for both (manual) brightness setting and the autobrightness curve. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618391 Title: Brightness is too strong To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615001] Re: lock display when idle timeout not honoured
** 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 about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568043] Re: gnome-photos crashed with SIGABRT in g_assertion_message()
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 to: https://bugs.launchpad.net/gnome-photos/+bug/1568043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 927636] Re: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
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 this bug go to: https://bugs.launchpad.net/plymouth/+bug/927636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615001] Re: lock display when idle timeout not honoured
** Changed in: repowerd Status: New => In Progress ** Changed in: repowerd (Ubuntu) Status: New => In Progress ** Changed in: repowerd Importance: Undecided => High ** Changed in: repowerd (Ubuntu) Importance: Undecided => High ** Changed in: repowerd (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/bugs/1615001 Title: lock display when idle timeout not honoured To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613601] Re: [MIR] unity-system-compositor
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 python3. > - Can we subscribe phablet-team, ubuntu-phonedations-bugs, or unity- api-team to LP bugs? Added mir-team, see https://bugs.launchpad.net/ubuntu/+source/unity- system-compositor/+bug/1613601/+subscriptions > - Does anyone know if we can drop the "sleep .1" from the wrapper script? I worry the answer is no, and that we will never drop it. The original authors don't recall the exact reason it was added, so more investigation is needed before we take any action. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613601 Title: [MIR] unity-system-compositor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1613601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613585] Re: [MIR] repowerd
> 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 to Ubuntu. https://bugs.launchpad.net/bugs/1613585 Title: [MIR] repowerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1613585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613871] Re: Regression: In dark conditions autobrightness does not adapt
> 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 "remind" the Nexus4 display that the brightness has changed. An update: In the latest package release 2016.08.2+16.10.20160823.1-0ubuntu1 I have provided a workaround for the Nexus 4, by applying the last normal brightness value before letting autobrightness take over when turning on the display. This is not ideal, but it's what powerd did in the past, and fixes Nexus 4 to have a quick reaction time. Note that this workaround applies only to Nexus 4. Other devices use the autobrightness setting directly when turning on the display (and autobrightness is enabled, of course), providing a smoother display-on experience. -- 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: In dark conditions autobrightness does not adapt To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613871] Re: Regression: In dark conditions autobrightness does not adapt
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 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 "remind" the Nexus4 display that the brightness has changed. This problematic behavior is not present on other devices (krillin, arale), and all findings point to some system layer below repowerd as the culprit. This Nexus4 behavior doesn't affect the validity of the proposed fix, since repowerd itself is doing the right thing. I will file a new bug for this Nexus4 specific issue when the fix for this bug lands in the image, so that the problem is easy for others to reproduce. -- 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: In dark conditions autobrightness does not adapt To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613871] Re: Regression: In dark conditions autobrightness does not adapt
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/~ci-train-ppa-service/+archive/ubuntu/landing-031/ in case anyone wants to try before it reaches the stable-phone-overlay PPA and an image. To install follow the instructions here: https://wiki.ubuntu.com/Process/Merges/TestPlans/repowerd -- 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: In dark conditions autobrightness does not adapt To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615001] Re: lock display when idle timeout not honoured
** 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 Ubuntu. https://bugs.launchpad.net/bugs/1615001 Title: lock display when idle timeout not honoured To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613871] Re: Regression: In dark conditions autobrightness does not adapt
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613871 Title: Regression: In dark conditions autobrightness does not adapt To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615001] Re: lock display when idle timeout not honoured
** 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 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 about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613585] Re: [MIR] repowerd
> 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/1613585 Title: [MIR] repowerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1613585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613871] Re: Regression: Rc-proposed Nexus 4 autobrightness does not work
> 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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613871 Title: Regression: Rc-proposed Nexus 4 autobrightness does not work To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613871] Re: Regression: Rc-proposed Nexus 4 autobrightness does not work
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 Nexus 4 autobrightness does not work To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613506] Re: The call screen still turns off after rejecting the call on the remote end without answering.
** 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 end without answering. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613585] Re: [MIR] repowerd
> - 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-team is also related, but just because of some overlap of engineers working on both projects, not because mir and repowerd are really related topic-wise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613585 Title: [MIR] repowerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1613585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613506] Re: The call screen still turns off after rejecting the call on the remote end without answering.
** 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 after rejecting the call on the remote end without answering. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613871] Re: Regression: Rc-proposed Nexus 4 autobrightness does not work
> > 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 type being used on > the device? OK, mystery solved, the bug reporter is using the bq-aquaris.en/mako channel (not the ubuntu/mako channel). ** Description changed: OS ubuntu 15.04 - since r.380 autobrightness does not work anymore + since bq-aquaris.en/mako r.380 autobrightness does not work anymore -- 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 notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613871] Re: Regression: Rc-proposed Nexus 4 autobrightness does not work
> 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 type being used on the device? -- 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 notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613871] Re: Regression: Rc-proposed Nexus 4 autobrightness does not work
@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 reduce the debouncing delay, the trade-off being increased susceptibility to transient light changes. -- 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 notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613871] Re: Regression: Rc-proposed Nexus 4 autobrightness does not work
@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 notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613601] [NEW] [MIR] unity-system-compositor
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 our convergence effort * Used by default on phablet images and in the Unity8 session on the desktop [Security] * No known security issues at this time * A security review is recommended. The package had been reviewed in the past by the security team for use on the phone, but it has changed significantly since then. [Quality assurance] * This package has unit and integration tests that run with each package build * CI is used during development [Dependencies] * All dependencies are in main * It 'Suggests' repowerd which already has a MIR: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1613585 [Standards compliance] * Follows FHS and Debian Policy. * This package uses cmake. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images * mir-development-team/unity-system-compositor-team are subscribed to project and ubuntu package bugs respectively (The unity-system-compositor developers are the Mir developers) ** Affects: unity-system-compositor (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/1613601 Title: [MIR] unity-system-compositor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1613601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613585] [NEW] [MIR] repowerd
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 package has unit and integration tests that run with each package build * CI is used during development [Dependencies] Most dependencies are already in main with the exception of the following binary packages from the platform-api source package: * libubuntu-application-api3 * libubuntu-platform-hardware-api3 Note that platform-api was previously in main in trusty (https://launchpad.net/ubuntu/+source/platform-api), so unless something has changed significantly it would be straightforward to repromote for yakkety. [Standards compliance] * Follows FHS and Debian Policy. * This package uses cmake. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images * repowerd-team is subscribed to both repowerd project and repowerd ubuntu package bugs ** Affects: repowerd (Ubuntu) Importance: Undecided Status: New ** Description changed: [Availability] * Available in universe [Rationale] - * This packages is the new power manager for our phablet efforts (it's already in RC phablet images) + * 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 package has unit and integration tests that run with each package build * CI is used during development [Dependencies] Most dependencies are already in main with the exception of the following binary packages from the platform-api source package: - * libubuntu-application-api3 - * libubuntu-platform-hardware-api3 + * libubuntu-application-api3 + * libubuntu-platform-hardware-api3 Note that platform-api was previously in main in trusty (https://launchpad.net/ubuntu/+source/platform-api), so unless something has changed significantly it would be straightforward to repromote for yakkety. [Standards compliance] * Follows FHS and Debian Policy. * This package uses cmake. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images * repowerd-team is subscribed to both repowerd project and repowerd ubuntu package bugs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613585 Title: [MIR] repowerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1613585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
