[Touch-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade
After the extensive upgrades of today no network. As per this bug report, network-manager seems to be gone. In my case this is a 24.04 Ubuntu Desktop QEMU/KVM VM running on my main Debian server host. In my case the command was "sudo apt dist-upgrade" ** Attachment added: "dpkg listing" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+attachment/5760309/+files/dpkg-network-manager.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade
The "sudo dhcpcd" command worked to get my network back. I had to do another update/upgrade cycle before network-manager would re-install. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Thank you for your incredibly thorough analysis of this. Since finding this via bug 2046470, I have tried, without success, to create a test to show any difference in performance or power or whatever between irqbalance enabled/disabled on my Ubuntu 20.04 test server. While my vote carries little weight here, I give it anyhow: A) Change it from an opt-out to an opt-in and remove the dependency from ubuntu-standard Mainly because, and from my own investigation, I agree with: > To me this seems to be a perfect case for a few special images/deployments > known to match the workload profile that needs this to enable it. > It is also more likely that a professional admin of such a large scale machine > (or cluster thereof) can make the opt-in decision and evaluation better than > expecting every user of Ubuntu to think about an opt-out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Lots of good comments. I sort of agree with: > So if we're going to make a change, there > should be due diligence to demonstrate a > benefit, it should not be based on > Internet hype. However, I would have said: If irqbalance is to be included by default, then there should be due diligence to demonstrate a clear benefit. Simplier is better, and every added thing can have issues, bug 2046470 being an example for irqbalance. On my Ubuntu 20.04 test server (kernel 6.7-rc8) running a 24.04 server VM (with 4 vcpus) I ran 3 token passing ping pong pairs, monitoring power and idle states on the host with irqbalance enabled and disabled on both host and guest. The results were: irqbalance disabled: pair 1: 4.3378 uSec/loop pair 2: 4.4207 uSec/loop pair 3: 4.5144 uSec/loop Processor energy: 87,500 Joules. irqbalance enabled: pair 1: 4.5828 uSec/loop +5.6% pair 2: 4.7084 uSec/loop +6.5% pair 3: 4.7704 uSec/loop +5.7% Processor energy: 92,252 Joules. +5.43% The attached graph is processor power at 15 seconds per sample from 30 seconds before until some seconds after the test completes. The extra extra energy for the irqbalanced test is because the test took longer to complete. I also have graphs for all idle states usage and above/below stats, none of which reveal anything. Another test done was iperf3 between the guest and host forcing a small tcp window size. The test was run for 22 minutes. The command: iperf3 --interval 0 --bidir --window 1024 --time 1320 -c s19.smythies.com irqbalance enabled: 412 MBytes sent 45.1 GBytes rec'd Processor energy: 69,272 Joules. irqbalance disabled: 413 MBytes sent, 0.24% improved 45.2 GBytes rec'd, 0.22% improved Processor energy: 70,560 Joules. +1.86% The related idle graphs don't reveal anything. A third test was iperf3 between the guest and host using the default (big) tcp window size. The test was run for 22 minutes. The command: iperf3 --interval 0 --bidir --time 1320 -c s19.smythies.com irqbalance enabled: 6.99 TBytes sent 2.10 TBytes rec'd 9.09 TBytes total Processor energy: 77,888 Joules. irqbalance disabled: 7.62 TBytes sent, 9.0% improved 1.62 TBytes rec'd, 22.9% worse 9.24 TBytes total, 1.65% improved Processor energy: 80,166 Joules. +2.92% The graphs (not attached) show the main differences are in idle state 0 usage. Other notes: Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz HWP enabled intel_pstate CPU frequency driver powersave governor ** Attachment added: "power.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1833322/+attachment/5737186/+files/power.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post t
[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Hi Christian, Thank you for your reply to my post. > I do not know the ping pong test, A simple token passing ring, that is useful for getting the system to utilize shallow idles states. Otherwise it can be difficult to get to such shallow states on my test system, without them being timer based. While not relevant to this thread, the test presents a challenge for the TEO (Timer Events Orientated) idle governor, and the menu governor should perform better. > but on iperf, I think that is in the noise > range as far as I remember. Agreed. I am just searching for good example type tests is all. > If you'd just re-run that as-is what is the delta > on your test box? Oh. it's repeatable. I just haven't got to re-testing it yet with 24.04 as my host hardware. > let me ask, what kind of system (cpu, size, nodes, ...) > was that. Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz 6 cores, 2 threads per core, 12 CPUs. HWP enabled (A.K.A. Intel Speed Shift) intel_pstate CPU frequency driver powersave governor teo idle governor (but menu used below) No throttling involved, ever. > Your results show no change or minimal > degradation while at the same time losing > a bit of power. Have you also had a chance > to try the powerthresh argument > that Steve mentioned above? I was just searching for a good test, and since that post I did find a really good one (not reported here). However, that was with 20.04 which has an old version of irqbalance. So I made my system dual boot adding 24.04. That same test is now not good at all for showing any differences. And yes, also tested with the powerthresh argument. Just for completeness, the attached graph shows processor package power and the only other graph that had some slight signal above the noise, the "idle state 1 was to deep" graph. The test: 6 ping pong pairs, with almost no work done at each stop, 300 million loops. About 27 minutes. Legend: irqb-menu-disable: irqbalance disabled, menu governor. irqb-menu-enable-1: irqbalance enabled with powerthresh=1, menu governor. irqb-menu-enable: irqbalance enabled, menu governor. Power: see graph, same for all. irqbalance disabled: 5.1854 uSec/loop irqbalance enabled powerthresh=1: 5.1966 uSec/loop irqbalance enabled: 5.1817 uSec/loop ** Attachment added: "power-and-1-above.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1833322/+attachment/5738151/+files/power-and-1-above.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in Ubuntu on IBM z Systems: New Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help
[Touch-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
Ever since the default changed to never blanking the screen, and after I whined in comment #18 above, I have been running this in /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT=" consoleblank=300 " always save a copy of grub first, and do "sudo update-grub afterwards", then re-boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kbd source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604010] Re: sntp missing
** Changed in: serverguide Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1604010 Title: sntp missing Status in Ubuntu Server Guide: Fix Released Status in ntp package in Ubuntu: Fix Released Status in ntp package in Debian: Fix Released Bug description: In Ubuntu 16.04, the binary file /usr/bin/sntp is missing from the package ntp. The associated man page /usr/share/man/man1/sntp.1.gz is still included. How to reproduce: $ sudo apt-get install ntp $ dpkg-query -L ntp | grep sntp /usr/share/man/man1/sntp.1.gz Expected result: /usr/bin/sntp was included in Ubuntu 14.04: $ dpkg-query -L ntp | grep sntp /usr/bin/sntp /usr/share/man/man1/sntp.1.gz The sntp program remains a very useful tool for interactively testing on the command line the offset of the local clock to a remote NTP server (like "ntpdate -qu [ntp-server]" previously). It should be included in the same package as its man page. To manage notifications about this bug go to: https://bugs.launchpad.net/serverguide/+bug/1604010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later
@John: That patch works great, thanks. On kernel 4.14-rc6 + patch, I re-did the stuff from my comment #22, which in turn was implementing one of the methods from your comment #19. This time it worked. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Xenial: Confirmed Status in apparmor source package in Zesty: Confirmed Status in apparmor source package in Artful: Confirmed Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later
Further to my comment #32: That setup then breaks lots of stuff if I subsequently boot a normal default kernel (i.e. 4.4.0-96-generic). I'm going back to just booting with apparmor disabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Xenial: Confirmed Status in apparmor source package in Zesty: Confirmed Status in apparmor source package in Artful: Confirmed Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later
@John: O.K., I think this excerpt from kern.log is what you might be looking for. ** Attachment added: "kern.log.txt" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+attachment/4995556/+files/kern.log.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Xenial: Confirmed Status in apparmor source package in Zesty: Confirmed Status in apparmor source package in Artful: Confirmed Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727158] Re: lscpu shows incorrect instantaneous CPU MHz value
This is not a bug, the change was done on purpose. What is displayed here and under /proc/cpuinfo has changed. For Intel processors it simply displays tsc now. One of several upstream references for this is: https://bugzilla.kernel.org/show_bug.cgi?id=197153 If you want to observe your current CPU frequencies do this: cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq ** Bug watch added: Linux Kernel Bug Tracker #197153 https://bugzilla.kernel.org/show_bug.cgi?id=197153 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1727158 Title: lscpu shows incorrect instantaneous CPU MHz value Status in util-linux package in Ubuntu: Confirmed Bug description: Ubuntu 17.10: lscpu has the following fields of interest to this report: Model name: Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz CPU MHz: 3499.996 CPU max MHz: 5900. CPU min MHz: 1600. The CPU MHz field is incorrect: At idle it never shows down-step, and at full load, it never shows the CPU's boost frequency (which should be up to about 4.6GHz on my system). This was working correctly under Ubuntu 17.04, showing the full range between 1600 and 4600. But with Ubuntu 17.10 it remains constantly at the CPU's design spec of 3499.996. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: util-linux 2.30.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 22:00:02 2017 InstallationDate: Installed on 2017-09-01 (53 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1727158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727158] Re: lscpu shows incorrect instantaneous CPU MHz value
The changes that were introduced in kernel 4.13-rc1 have been reverted in kernel 4.14-rc8 (and queued for backporting to stable kernels). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1727158 Title: lscpu shows incorrect instantaneous CPU MHz value Status in util-linux package in Ubuntu: Confirmed Bug description: Ubuntu 17.10: lscpu has the following fields of interest to this report: Model name: Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz CPU MHz: 3499.996 CPU max MHz: 5900. CPU min MHz: 1600. The CPU MHz field is incorrect: At idle it never shows down-step, and at full load, it never shows the CPU's boost frequency (which should be up to about 4.6GHz on my system). This was working correctly under Ubuntu 17.04, showing the full range between 1600 and 4600. But with Ubuntu 17.10 it remains constantly at the CPU's design spec of 3499.996. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: util-linux 2.30.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 22:00:02 2017 InstallationDate: Installed on 2017-09-01 (53 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1727158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471459] Re: First run of nano creates a directory in $HOME, if run as sudo will be root owned
Requested information. Fresh server installation from Wily daily a couple of days ago: doug@serv64-dev:~$ sudo sudo -V | head -1 Sudo version 1.8.12 doug@serv64-dev:~$ sudo sudo -V | grep -e ve: -e HOME Environment variables to remove: PYTHONHOME Environment variables to preserve: HOME doug@serv64-dev:~$ sudo grep -v ^# /etc/sudoers Defaultsenv_reset Defaultsmail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" rootALL=(ALL:ALL) ALL %admin ALL=(ALL) ALL %sudo ALL=(ALL:ALL) ALL doug@serv64-dev:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Wily Werewolf (development branch) Release:15.10 Codename: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1471459 Title: First run of nano creates a directory in $HOME, if run as sudo will be root owned Status in One Hundred Papercuts: Confirmed Status in nano package in Ubuntu: Confirmed Bug description: If nano is started for the first with sudo then a root owned directory named .nano is created in the user's $HOME directory. If 1st. started as a user then the user owns .nano & ownership will not be altered by subsequent use of sudo nano. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nano 2.4.1-1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 Date: Sat Jul 4 20:06:16 2015 InstallationDate: Installed on 2015-02-25 (128 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224) SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1471459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1484587] Re: CPU frequency management fails to re-engage on resume from suspend
When a user is using the intel_pstate driver in performance mode, then yes, prior to Kernel 4.2RC1 the CPU frequency will be typically be stuck after resume from suspend. This is not a pm-ultils issue (which is how I stumbled across this bug report). To test that the issue is fixed on kernel 4.2, just use primitive commands and not these higher level utilities (that I neither use or know anything about). For example use: grep MHz /proc/cpuinfo to observe CPU frequencies. The commit that, I think, fixes this issue is: commit 6c1e45917dec5e7c99ba8125fd8cc50f6e482a21 Author: Doug Smythies Date: Mon Jun 1 21:12:34 2015 -0700 intel_pstate: Force setting target pstate when required -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1484587 Title: CPU frequency management fails to re-engage on resume from suspend Status in linux package in Ubuntu: Confirmed Status in pm-utils package in Ubuntu: Confirmed Bug description: Behavior: CPU frequency management fails to re-engage on resume from suspend. On resume, the CPUs are stuck around a single frequency (usually a low idle frequency). I use indicator-cpufreq for manual governor control. On resume, indicator-cpufreq indicates the low frequency state in its live cpu performance display in the icon. However, in its governor menu, it still shows as in use whichever governor was selected before suspend, even though that governor is not actually or properly controlling the CPU state. Upon manually switching to the unused governor in indicator-cpufreq, this behavior resolves, and the newly-chosen governor begins performing its duties. I can then immediately switch back to the desired (pre-suspend) governor with no issues. PM logs appear to show a successful resume of cpu frequency management, even though the modules did not actually gain effective control of the processor frequencies. Expected behavior: On resume, the CPU frequencies should continue being managed as they were before suspend without the need for manual user input. Also, in the event that they do not, an error/warning should appear -- if not to the user, then in the pm suspend/resume logs. Other information that may or may not be relevant: On this system, the "powersave" governor is always automatically chosen at startup, although not until a minute or so after session login. The choice of an alternate governor "performance" from indicator-cpufreq is not persistent across reboots. Further, if I manually toggle the governors at the beginning of my first session after boot, and I settle on "performance", some automated script will force it back to "powersave" at the usual time about a minute after login. To use the "performance" governor, I must select it after waiting an interval following login, and I must always switch to powersave and back to performance after each resume from suspend. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3887 F pulseaudio /dev/snd/controlC1: adam 3887 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 13 11:41:27 2015 InstallationDate: Installed on 2014-08-10 (368 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ENVY 15 x360 PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 22D6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 89.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 15 x360 PC dmi.product.version: 0974100022405F0420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484587/+subscripti
[Touch-packages] [Bug 1493156] [NEW] pm-suspend aborts if highest numbered CPU offline, as of kernel 4.2
Public bug reported:
Kernel 4.2 includes a significant commit
(87549141d516aee71d511138e27117c41e8aef68), after the patch the files
and directory are present even if the CPU is offline. If the CPU is
offline, writing to those files isn't allowed and so the echo in
94cpufreq fails.
If the failed echo is not the last pass through the loop, then
the bad exit code gets overwritten with a good one before
the loop exits. If the failed echo is the last pass through the loop, due to
the highest numbered CPU being offline, then then 94cpufreq returns an error
code and pm-suspend aborts.
So what is needed is something like (and this doesn't actually work
yet):
hibernate_cpufreq()
{
( cd /sys/devices/system/cpu/
for x in cpu[0-9]*; do
# if cpufreq is a symlink, it is handled by another cpu. Skip.
[ -L "$x/cpufreq" ] && continue
gov="$x/cpufreq/scaling_governor"
# if we do not have a scaling_governor file, skip.
[ -f "$gov" ] || continue
+ # if the CPU is offline, skip, unless no file, i.e. CPU0.
+ [ $(cat "$x/online") = "1" -o ! -f "$x/online" ] || continue
Or
+ if [ $(cat "$x/online") = "1" ] || [ ! -f "$x/online" ]; then
+ continue;
+fi
Or something similar that actually works.
# if our temporary governor is not available, skip.
grep -q "$TEMPORARY_CPUFREQ_GOVERNOR" \
"$x/cpufreq/scaling_available_governors" || continue
savestate "${x}_governor" < "$gov"
echo "$TEMPORARY_CPUFREQ_GOVERNOR" > "$gov"
done )
}
Or just force a good return code at the end (which is what I'm doing
now, so that I can move on).
Note: I also filed this same bug report upstream.
https://bugs.freedesktop.org/show_bug.cgi?id=91914
** Affects: pm-utils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1493156
Title:
pm-suspend aborts if highest numbered CPU offline, as of kernel 4.2
Status in pm-utils package in Ubuntu:
New
Bug description:
Kernel 4.2 includes a significant commit
(87549141d516aee71d511138e27117c41e8aef68), after the patch the files
and directory are present even if the CPU is offline. If the CPU is
offline, writing to those files isn't allowed and so the echo in
94cpufreq fails.
If the failed echo is not the last pass through the loop, then
the bad exit code gets overwritten with a good one before
the loop exits. If the failed echo is the last pass through the loop, due to
the highest numbered CPU being offline, then then 94cpufreq returns an error
code and pm-suspend aborts.
So what is needed is something like (and this doesn't actually work
yet):
hibernate_cpufreq()
{
( cd /sys/devices/system/cpu/
for x in cpu[0-9]*; do
# if cpufreq is a symlink, it is handled by another cpu. Skip.
[ -L "$x/cpufreq" ] && continue
gov="$x/cpufreq/scaling_governor"
# if we do not have a scaling_governor file, skip.
[ -f "$gov" ] || continue
+ # if the CPU is offline, skip, unless no file, i.e. CPU0.
+ [ $(cat "$x/online") = "1" -o ! -f "$x/online" ] || continue
Or
+ if [ $(cat "$x/online") = "1" ] || [ ! -f "$x/online" ]; then
+ continue;
+fi
Or something similar that actually works.
# if our temporary governor is not available, skip.
grep -q "$TEMPORARY_CPUFREQ_GOVERNOR" \
"$x/cpufreq/scaling_available_governors" || continue
savestate "${x}_governor" < "$gov"
echo "$TEMPORARY_CPUFREQ_GOVERNOR" > "$gov"
done )
}
Or just force a good return code at the end (which is what I'm doing
now, so that I can move on).
Note: I also filed this same bug report upstream.
https://bugs.freedesktop.org/show_bug.cgi?id=91914
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1493156/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"
Which kernel are you using? On my development 17.10 Desktop, I get the same as you but only for mainline kernels 4.14-rc2 and 4.14-rc3. Earlier kernels, including mainline 4.14-rc1, seem to be fine with respect to this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" Status in apparmor package in Ubuntu: New Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"
Paul wrote: > I am using Linux 4.14-rc3+. O.K. that is/was really important information. While I have been calling this a kernel regression, it might be that a great number of apparmor profiles need to be updated to accommodate the new security stuff that was introduced in kernel 4.14-rc2 (it missed -rc1 due to some issues, and it is not normal to include such major changes in anything other than -rc1). i.e. It might be that this is a non-backwards compatible kernel change. Anyway, I know nothing about this area of the kernel, and will step back now. To be able to proceed with my own work, I have compiled kernel 4.14-rc3 (and now 4.14-rc4) with apparmor disabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" Status in apparmor package in Ubuntu: New Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later
> I've found that it's more than just cups blows up, some networking > related items (DHCP client, network manager IIRC) also explode. yes, and libvirtd and mysql. I was not aware of "teardown". I'll try it when I get a chance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Xenial: Confirmed Status in apparmor source package in Zesty: New Status in apparmor source package in Artful: Confirmed Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later
John wrote: > Ubuntu's parser is missing upstream commit r3700, resulting in this failure. Is there any boot option that would allow Ubuntu mainline kernels to work? For my own work, and as mentioned in comment #3, I am compiling with "# CONFIG_SECURITY_APPARMOR is not set". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Xenial: Confirmed Status in apparmor source package in Zesty: Confirmed Status in apparmor source package in Artful: Confirmed Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later
@John: I tried your suggestion on my main 16.04.3 test server. I edited /etc/apparmor/parser.conf, keeping an "original copy" first. And used "the hand edited features 4.14 feature file attached". It made things worse, as in addition to mysql and libvirt not starting, now the network doesn't start either. I restored /etc/apparmor/parser.conf and changed my GRUB_CMDLINE_LINUX_DEFAULT in grub, adding "apparmor=0". and now everything is fine using the Ubuntu mainline kernel 4.14-rc5. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Xenial: Confirmed Status in apparmor source package in Zesty: Confirmed Status in apparmor source package in Artful: Confirmed Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1649168] Re: weekly log rotation is often a day late
In addition to the proper fix for this issue, they are wanting to make a fundamental change to how weekly log rotation works by eliminating the migration to Sunday portion. This part of the change should NOT be done, in my opinion. Before it is too late, Please chime in on the upstream thread. https://github.com/logrotate/logrotate/issues/93 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1649168 Title: weekly log rotation is often a day late Status in logrotate package in Ubuntu: New Bug description: Over the last few Ubuntu releases, the status file the logrotate generates and uses has added more detail to the time stamp information. In 12.04 it seems to only keep information to the day. In 14.04 it seems to keep information to the second. In 16.04 it seems to keep information to the second. However, the weekly section of the logrotate program calculates the time since the last rotation to the second with absolutely no jitter margin, and therefore as often as every other week, weekly logs that should rotate on Sunday do not rotate until Monday. I have 43 weeks of weekly rotation data, where on 17 of those weeks the rotation was on Monday and not Sunday. Note that the week after Monday rotation it will always rotate on Sunday due to "the current weekday is before the weekday of the last rotation" condition. Code segment: case ROT_WEEKLY: /* rotate if: 1) the current weekday is before the weekday of the last rotation 2) more then a week has passed since the last rotation */ state->doRotate = ((now.tm_wday < state->lastRotated.tm_wday) || ((mktime(&now) - mktime(&state->lastRotated)) > (7 * 24 * 3600))); There is an upstream bug report at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825776 which I will attempt to link in. It suggests introducing a 60 jitter allowance. I would make it more myself. I first noticed this issue during 16.04 development in 2016.02 (Feb). However, that computer had previously been a 12.04 server, so I do not have good data about 14.04. See also: https://ubuntuforums.org/showthread.php?t=2320149 Do not ask me to run apport collect for this bug report, because it is not needed, and it never works for me anyhow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1649168/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
@fish : Yes your issue does not belong here. To figure out where your issue actually belongs, some details are missing: If your stuck at low frequency issue only occurs after a suspend and on battery power, then your issue is covered by: https://bugzilla.kernel.org/show_bug.cgi?id=90041 (and it is not resolved quite yet, even though that is the status). If your issue always occurs and you are not using the proper Dell AC adapter, then that is why. Otherwise, I don't know. Try the acpi_cpufreq CPU frequency scaling driver instead. Also have a look at: https://bugzilla.kernel.org/show_bug.cgi?id=189861 ** Bug watch added: Linux Kernel Bug Tracker #90041 http://bugzilla.kernel.org/show_bug.cgi?id=90041 ** Bug watch added: Linux Kernel Bug Tracker #189861 http://bugzilla.kernel.org/show_bug.cgi?id=189861 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_d
[Touch-packages] [Bug 1427910] Re: apt doesn't correctly fill APT::NeverAutoRemove
autoremove seems to want to remove the second to last regular kernel on my systems also. I always have a bunch of mainline kernels installed on my computers, and maybe that is the reason. Example: $ sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: gconf-service gconf-service-backend gconf2 gconf2-common libavahi-glib1 libbonobo2-0 libbonobo2-common libcanberra0 libgconf-2-4 libgnome-2-0 libgnome2-common libgnomevfs2-0 libgnomevfs2-common libllvm3.8 libmircommon5 liborbit-2-0 linux-headers-4.4.0-67 linux-headers-4.4.0-67-generic linux-headers-4.4.0-72 linux-headers-4.4.0-72-generic linux-headers-4.4.0-77 linux-headers-4.4.0-77-generic linux-headers-4.4.0-83 linux-headers-4.4.0-83-generic linux-headers-4.4.0-92 linux-headers-4.4.0-92-generic linux-image-4.4.0-67-generic linux-image-4.4.0-72-generic linux-image-4.4.0-77-generic linux-image-4.4.0-83-generic linux-image-4.4.0-92-generic linux-image-extra-4.4.0-67-generic linux-image-extra-4.4.0-72-generic linux-image-extra-4.4.0-77-generic linux-image-extra-4.4.0-83-generic linux-image-extra-4.4.0-92-generic sound-theme-freedesktop 0 upgraded, 0 newly installed, 37 to remove and 0 not upgraded. After this operation, 1,535 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. The current regular kernel is 4.4.0-93 and I expect 4.4.0-92 to be left alone. I am running servers 16.04.3 and apt 1.2.24. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1427910 Title: apt doesn't correctly fill APT::NeverAutoRemove Status in apt package in Ubuntu: Confirmed Bug description: After kernel update I have 3 kernel packages: ii linux-headers-3.13.0-43 ii linux-headers-3.13.0-45 ii linux-headers-3.13.0-43-generic ii linux-headers-3.13.0-45-generic ii linux-headers-3.13.0-46 ii linux-headers-3.13.0-46-generic ii linux-headers-generic 3.13.0.46.53 ii linux-image-3.13.0-43-generic ii linux-image-3.13.0-45-generic ii linux-image-3.13.0-46-generic ii linux-image-extra-3.13.0-43-generic ii linux-image-extra-3.13.0-45-generic ii linux-image-extra-3.13.0-46-generic And apt-config dump | grep linux returns: APT::NeverAutoRemove:: "^linux-image-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-image-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-46-generic$"; Then I do: apt-get purge linux-headers-3.13.0-43 linux-headers-3.13.0-43-generic linux-image-3.13.0-43-generic linux-image-extra-3.13.0-43-generic Then again apt-config dump | grep linux returns: APT::NeverAutoRemove:: "^linux-image-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-image-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-46-generic$"; It has 43 and 46. Suppose to be two last versions 45 and 46, because I have them. Apt doesn't work correctly. It now suggests: apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-image-3.13.0-45-generic linux-image-extra-3.13.0-45-generic It needs to be fixed. Thank you in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1427910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel
In my case autoremove wants to delete the second-latest regular kernel version. Maybe because I have a bunch of mainline kernels installed also. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Confirmed Bug description: This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (114 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified] mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2016-07-30T12:15:32.706300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427910] Re: apt doesn't correctly fill APT::NeverAutoRemove
** Attachment added: "I'll attach the entire 01autoremove-kernels file as a text file" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1427910/+attachment/4941613/+files/01autoremove-kernels.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1427910 Title: apt doesn't correctly fill APT::NeverAutoRemove Status in apt package in Ubuntu: Confirmed Bug description: After kernel update I have 3 kernel packages: ii linux-headers-3.13.0-43 ii linux-headers-3.13.0-45 ii linux-headers-3.13.0-43-generic ii linux-headers-3.13.0-45-generic ii linux-headers-3.13.0-46 ii linux-headers-3.13.0-46-generic ii linux-headers-generic 3.13.0.46.53 ii linux-image-3.13.0-43-generic ii linux-image-3.13.0-45-generic ii linux-image-3.13.0-46-generic ii linux-image-extra-3.13.0-43-generic ii linux-image-extra-3.13.0-45-generic ii linux-image-extra-3.13.0-46-generic And apt-config dump | grep linux returns: APT::NeverAutoRemove:: "^linux-image-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-image-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-46-generic$"; Then I do: apt-get purge linux-headers-3.13.0-43 linux-headers-3.13.0-43-generic linux-image-3.13.0-43-generic linux-image-extra-3.13.0-43-generic Then again apt-config dump | grep linux returns: APT::NeverAutoRemove:: "^linux-image-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-image-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-46-generic$"; It has 43 and 46. Suppose to be two last versions 45 and 46, because I have them. Apt doesn't work correctly. It now suggests: apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-image-3.13.0-45-generic linux-image-extra-3.13.0-45-generic It needs to be fixed. Thank you in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1427910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427910] Re: apt doesn't correctly fill APT::NeverAutoRemove
> Well, Doug, it preserves the latest 2 kernels. > You have several 4.13 and 4.10 builds, and 4.13 > 4.10 > 4.4. Didn't it used to ignore manually installed kernels and only count automatically installed kernels? This issue only came up about a year or two ago, I think. > Note that your version number is wrong too, > it should be ~rc7, not -rc7, That is not under my control. And yes, I know it doesn't sort properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1427910 Title: apt doesn't correctly fill APT::NeverAutoRemove Status in apt package in Ubuntu: Confirmed Bug description: After kernel update I have 3 kernel packages: ii linux-headers-3.13.0-43 ii linux-headers-3.13.0-45 ii linux-headers-3.13.0-43-generic ii linux-headers-3.13.0-45-generic ii linux-headers-3.13.0-46 ii linux-headers-3.13.0-46-generic ii linux-headers-generic 3.13.0.46.53 ii linux-image-3.13.0-43-generic ii linux-image-3.13.0-45-generic ii linux-image-3.13.0-46-generic ii linux-image-extra-3.13.0-43-generic ii linux-image-extra-3.13.0-45-generic ii linux-image-extra-3.13.0-46-generic And apt-config dump | grep linux returns: APT::NeverAutoRemove:: "^linux-image-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-image-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-45-generic$"; APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-46-generic$"; Then I do: apt-get purge linux-headers-3.13.0-43 linux-headers-3.13.0-43-generic linux-image-3.13.0-43-generic linux-image-extra-3.13.0-43-generic Then again apt-config dump | grep linux returns: APT::NeverAutoRemove:: "^linux-image-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-image-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-headers-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13\.0-46-generic$"; APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-43-generic$"; APT::NeverAutoRemove:: "^linux-tools-3\.13\.0-46-generic$"; It has 43 and 46. Suppose to be two last versions 45 and 46, because I have them. Apt doesn't work correctly. It now suggests: apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-image-3.13.0-45-generic linux-image-extra-3.13.0-45-generic It needs to be fixed. Thank you in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1427910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1649168] Re: weekly log rotation is often a day late
The now upstream committed solution to this issue ( https://github.com/logrotate/logrotate/issues/93 ) does not change the default way logrotate worked in the past. So now it just has to make its way downstream. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1649168 Title: weekly log rotation is often a day late Status in logrotate package in Ubuntu: New Bug description: Over the last few Ubuntu releases, the status file the logrotate generates and uses has added more detail to the time stamp information. In 12.04 it seems to only keep information to the day. In 14.04 it seems to keep information to the second. In 16.04 it seems to keep information to the second. However, the weekly section of the logrotate program calculates the time since the last rotation to the second with absolutely no jitter margin, and therefore as often as every other week, weekly logs that should rotate on Sunday do not rotate until Monday. I have 43 weeks of weekly rotation data, where on 17 of those weeks the rotation was on Monday and not Sunday. Note that the week after Monday rotation it will always rotate on Sunday due to "the current weekday is before the weekday of the last rotation" condition. Code segment: case ROT_WEEKLY: /* rotate if: 1) the current weekday is before the weekday of the last rotation 2) more then a week has passed since the last rotation */ state->doRotate = ((now.tm_wday < state->lastRotated.tm_wday) || ((mktime(&now) - mktime(&state->lastRotated)) > (7 * 24 * 3600))); There is an upstream bug report at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825776 which I will attempt to link in. It suggests introducing a 60 jitter allowance. I would make it more myself. I first noticed this issue during 16.04 development in 2016.02 (Feb). However, that computer had previously been a 12.04 server, so I do not have good data about 14.04. See also: https://ubuntuforums.org/showthread.php?t=2320149 Do not ask me to run apport collect for this bug report, because it is not needed, and it never works for me anyhow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1649168/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604010] Re: sntp missing
** Changed in: serverguide Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1604010 Title: sntp missing Status in Ubuntu Server Guide: Fix Committed Status in ntp package in Ubuntu: Fix Released Status in ntp package in Debian: Fix Released Bug description: In Ubuntu 16.04, the binary file /usr/bin/sntp is missing from the package ntp. The associated man page /usr/share/man/man1/sntp.1.gz is still included. How to reproduce: $ sudo apt-get install ntp $ dpkg-query -L ntp | grep sntp /usr/share/man/man1/sntp.1.gz Expected result: /usr/bin/sntp was included in Ubuntu 14.04: $ dpkg-query -L ntp | grep sntp /usr/bin/sntp /usr/share/man/man1/sntp.1.gz The sntp program remains a very useful tool for interactively testing on the command line the offset of the local clock to a remote NTP server (like "ntpdate -qu [ntp-server]" previously). It should be included in the same package as its man page. To manage notifications about this bug go to: https://bugs.launchpad.net/serverguide/+bug/1604010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
Kernel 4.12-rc1 has this change, so the console now defaults to never going blank. I disagree with this change. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kbd source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases
@Gunnar : Thank you for the workaround. It solved my problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1872200 Title: apt does not accept globs and regexes in some cases Status in apt package in Ubuntu: Confirmed Bug description: Observed with Ubuntu 20.04 Beta. apt remove 'mypackage*' does not remove all installed packages starting with “mypackage”. Instead: $ sudo apt remove 'mypackage*' Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mypackage* However: $ sudo apt list --installed 'mypackage*' Listing... Done mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic] mypackage1/focal,now 0.3.2-5build1 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases
I tested apt version 2.0.3. This: sudo apt install gnome-user-docs* gnome-getting-started-docs* whereas it did not before, and I had to use Gunnar's workaround from comment #6 above. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1872200 Title: apt does not accept globs and regexes in some cases Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Fix Committed Status in apt source package in Groovy: Fix Released Bug description: [Impact] Users can't use * wildcards anymore in focal, except by accident in apt list. For apt list, we now start restricting wildcard syntax to the same syntax install now accepts, and at the same time we remove the restrictions on which patterns are accepted (which only accepted patterns starting in ~ or ?), so !~napt now works, and does not accidentally match as a wildcard. [Test case] Test that * wildcards work for both install and list, and test that a ? wildcard does not. We included autopkgtests for those: BEGIN TESTS # # * wildcards should still work testsuccessequal "Listing... automatic1/now 1.0 i386 [installed,local] automatic2/now 1.0 i386 [installed,local]" apt list 'automatic*' testfailureequal "Reading package lists... Building dependency tree... Reading state information... Note, selecting 'automatic1' for glob 'automatic*' Note, selecting 'automatic2' for glob 'automatic*' automatic1 is already the newest version (1.0). automatic1 set to manually installed. automatic2 is already the newest version (1.0). automatic2 set to manually installed. You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: broken : Depends: does-not-exist but it is not installable E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution)." apt install -s 'automatic*' # other wildcards should fail testfailureequal "Listing... E: input:0-10: error: Expected pattern automatic? ^^" apt list 'automatic?' testfailureequal "Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package automatic?" apt install -s 'automatic?' END TESTS # Also it might be worth checking that apt list !~napt works. This used to produce an empty list, as it was accidentally matched as a wildcard and produced no result - now it produces every package whose name does not contain "apt". [Regression potential] The changes only affect interactive users, as apt(8) is not stable for in-script use, hence they can fix up their command-line if it stops working for them (though, really, more should work now). No scripts will be broken :) [Squashed in changes] The SRU also fixes potential build failures by correctly prefxing nullptr_t with the std:: namespace, and includes updated Dutch documentation. [Original bug report] Observed with Ubuntu 20.04 Beta. apt remove 'mypackage*' does not remove all installed packages starting with “mypackage”. Instead: $ sudo apt remove 'mypackage*' Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mypackage* However: $ sudo apt list --installed 'mypackage*' Listing... Done mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic] mypackage1/focal,now 0.3.2-5build1 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'
I have a 20.04 VM that I had not run for awhile (Feb 12th). It has kmod version 26-3ubuntu1, and installed mainline kernel 5.6.0-050600rc4-lowlatency fine. The other two physical 20.04 test servers have kmod version 27-1ubuntu1, and both spew the error 5600 times during kernel installation the first time. If I reinstall the same kernel there are no errors spewed. If I purge the kernel and re-install it, then the error is spewed 5600 times again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1864992 Title: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' Status in curtin: Invalid Status in subiquity: New Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: During a Focal install from the ISO image several errors like: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' are logged in curtin's install logs. The installed system boots and works fine, but the error is clearly something we want to get rid of. At first glance this seems related to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261 but the version of initramfs-tools in both the installer and installed system (checked with `chroot /target dpkg -l initramfs-tools` during the installation) is 0.136ubuntu1, which should contain Rafael's fix for that bug. I wonder if the update-initramfs diversion has a role here. I verified this happens at least on amd64 and arm64. I'm attaching the full install logs for a amd64 installation. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperVersion: 1.439 DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 ProcFB: 0 qxldrmfb ProcKernelCmdLine: initrd=/casper/initrd quiet --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1864992/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'
** Changed in: kmod (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1864992 Title: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' Status in curtin: Invalid Status in subiquity: New Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: During a Focal install from the ISO image several errors like: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' are logged in curtin's install logs. The installed system boots and works fine, but the error is clearly something we want to get rid of. At first glance this seems related to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261 but the version of initramfs-tools in both the installer and installed system (checked with `chroot /target dpkg -l initramfs-tools` during the installation) is 0.136ubuntu1, which should contain Rafael's fix for that bug. I wonder if the update-initramfs diversion has a role here. I verified this happens at least on amd64 and arm64. I'm attaching the full install logs for a amd64 installation. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperVersion: 1.439 DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 ProcFB: 0 qxldrmfb ProcKernelCmdLine: initrd=/casper/initrd quiet --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1864992/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864436] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file
I think bug 1864992 and this one are duplicates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1864436 Title: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file Status in kmod package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 linux Ubuntu 5.4.0-14.17-generic 5.4.18 linux-modules-5.4.0-15-generic 5.4.0-15.18 Upgrading from 5.4.0-14.17 to 5.4.0-15.18 leads to a large number of repeated error messages: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-15-generic/modules.builtin.bin' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'
For what it's worth, the versions of things in my test computers, all servers, no GUI: name: serv-ff (a 20.04 VM, that has not had an update since around February 12th): initramfs-tools: 0.133ubuntu14 kmod; 26-3ubuntu1 name: s18 (a physical i5-9600K based computer, up to date as of a few days ago): initramfs-tools: 0.136ubuntu1 kmod; 27-1ubuntu1 name: s15 (a physical i7-2600K based computer, up to date as of a few days ago): initramfs-tools: 0.136ubuntu1 kmod; 27-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1864992 Title: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' Status in curtin: Invalid Status in subiquity: New Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: During a Focal install from the ISO image several errors like: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' are logged in curtin's install logs. The installed system boots and works fine, but the error is clearly something we want to get rid of. At first glance this seems related to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261 but the version of initramfs-tools in both the installer and installed system (checked with `chroot /target dpkg -l initramfs-tools` during the installation) is 0.136ubuntu1, which should contain Rafael's fix for that bug. I wonder if the update-initramfs diversion has a role here. I verified this happens at least on amd64 and arm64. I'm attaching the full install logs for a amd64 installation. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperVersion: 1.439 DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 ProcFB: 0 qxldrmfb ProcKernelCmdLine: initrd=/casper/initrd quiet --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1864992/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1314653] Re: sysvinit: default cpufreq governor to powersave for intel-pstate driver
I changed this from "won't fix" and set the importance to high. Why because it has to be fixed and should actually be critical. ** Changed in: sysvinit (Ubuntu Trusty) Status: Won't Fix => Confirmed ** Changed in: sysvinit (Ubuntu Trusty) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1314653 Title: sysvinit: default cpufreq governor to powersave for intel-pstate driver Status in sysvinit package in Ubuntu: Fix Released Status in sysvinit source package in Trusty: Confirmed Status in sysvinit source package in Utopic: Fix Released Bug description: When defaulting to the intel-pstate driver, there are only a couple of cpufreq governors available, none of which are handled in the /etc/init.d/ondemand script. Since this driver is meant to be used for power saving, it seems wrong to leave the system in the kernel default configured "performance" governor after boot, so I think it is pertinent to set this to "powersave" if it is the only suitable non-power hungry governor available. How to reproduce: 1. enable the intel_pstate driver on a recent Intel machine (Sandybridge or above) edit /etc/default/grub, modify the following: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=enable" and run: sudo update-grub and reboot. 2. login 3. wait at least 60 seconds for /etc/init.d/ondemand to complete check out the default cpufreq governor, you will see it is still set to the boot default of "performance": cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor With the attached fix the system will boot into a less aggressive cpufreq governor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1314653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412897] [NEW] newest libxml2 update in vivid breaks serverguide validation
Public bug reported: Under vivid, the serverguide validation script gives and error: doug@desk-dev:~/sguide-trunk/serverguide$ scripts/validate.sh serverguide/C/serverguide.xml --Validating serverguide/C/serverguide.xml ... serverguide/C/serverguide.xml:2: element legalnotice: validity error : ID legal already defined If I downgrade the libxml2 package via: sudo dpkg -i libxml2_2.9.1+dfsg1-4ubuntu1_amd64.deb then the validation works: doug@desk-dev:~/sguide-trunk/serverguide$ scripts/validate.sh serverguide/C/serverguide.xml --Validating serverguide/C/serverguide.xml ... doug@desk-dev:~/sguide-trunk/serverguide$ The issue might be this upstream bug report (yet the conditions seem a little different): https://bugzilla.gnome.org/show_bug.cgi?id=737840 Note that as far as I have been able to determine, so far, the documents actually build properly. Thanks to Ian Nicholson for this one. ** Affects: libxml2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1412897 Title: newest libxml2 update in vivid breaks serverguide validation Status in libxml2 package in Ubuntu: New Bug description: Under vivid, the serverguide validation script gives and error: doug@desk-dev:~/sguide-trunk/serverguide$ scripts/validate.sh serverguide/C/serverguide.xml --Validating serverguide/C/serverguide.xml ... serverguide/C/serverguide.xml:2: element legalnotice: validity error : ID legal already defined If I downgrade the libxml2 package via: sudo dpkg -i libxml2_2.9.1+dfsg1-4ubuntu1_amd64.deb then the validation works: doug@desk-dev:~/sguide-trunk/serverguide$ scripts/validate.sh serverguide/C/serverguide.xml --Validating serverguide/C/serverguide.xml ... doug@desk-dev:~/sguide-trunk/serverguide$ The issue might be this upstream bug report (yet the conditions seem a little different): https://bugzilla.gnome.org/show_bug.cgi?id=737840 Note that as far as I have been able to determine, so far, the documents actually build properly. Thanks to Ian Nicholson for this one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1412897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448535] [NEW] Lockscreen timeout un-blanks the screen
Public bug reported: Just to separate the variables, use a different "Turn screen off when inactive for" time and "Lock screen after" time under "Brightness and Lock" under "System Setting". Leave the system inactive. The screen goes blank after the appropriate inactive period. After the additional screen lock time (or immediately if it is set to "When Screen turns off"), the screen turns back on and stays on, forever. However, just move the mouse and then the screen will blank after the appropriate inactive period, and this time, and subsequent times, it will stay off. Now, unlock the computer, and this whole sequence will repeat. I'm told this is not the same as bug 1292041 ,but I think it is related. Why? Because this issue started the same day as that bug, namely 2014.03.12 (March 12th 2014). This issue is repeatable on: Ubuntu desktop 14.04; Ubuntu desktop 15.04, as upgraded from previous; Ubuntu desktop 15.04, as newly installed, albeit during development. This issue does not occur with Ubuntu desktop 12.04. And did not occur with desktop 14.04 development prior to 2014.03.12. Note: All of my work is with Virtual Computer guests on an Ubuntu server 14.04 host. doug@desk-ss:~$ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 unity 7.3.2+15.04.20150420-0ubuntu1 doug@desk-dev:~$ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 unity 7.3.2+15.04.20150420-0ubuntu1 doug@desk-tt:~$ lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 unity 7.2.4+14.04.20141217-0ubuntu1 doug@desk-pp:~$ lsb_release -rd Description:Ubuntu 12.04.5 LTS Release:12.04 unity 5.20.0-0ubuntu3 ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1448535 Title: Lockscreen timeout un-blanks the screen Status in unity package in Ubuntu: New Bug description: Just to separate the variables, use a different "Turn screen off when inactive for" time and "Lock screen after" time under "Brightness and Lock" under "System Setting". Leave the system inactive. The screen goes blank after the appropriate inactive period. After the additional screen lock time (or immediately if it is set to "When Screen turns off"), the screen turns back on and stays on, forever. However, just move the mouse and then the screen will blank after the appropriate inactive period, and this time, and subsequent times, it will stay off. Now, unlock the computer, and this whole sequence will repeat. I'm told this is not the same as bug 1292041 ,but I think it is related. Why? Because this issue started the same day as that bug, namely 2014.03.12 (March 12th 2014). This issue is repeatable on: Ubuntu desktop 14.04; Ubuntu desktop 15.04, as upgraded from previous; Ubuntu desktop 15.04, as newly installed, albeit during development. This issue does not occur with Ubuntu desktop 12.04. And did not occur with desktop 14.04 development prior to 2014.03.12. Note: All of my work is with Virtual Computer guests on an Ubuntu server 14.04 host. doug@desk-ss:~$ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 unity 7.3.2+15.04.20150420-0ubuntu1 doug@desk-dev:~$ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 unity 7.3.2+15.04.20150420-0ubuntu1 doug@desk-tt:~$ lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 unity 7.2.4+14.04.20141217-0ubuntu1 doug@desk-pp:~$ lsb_release -rd Description:Ubuntu 12.04.5 LTS Release:12.04 unity 5.20.0-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1448535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411802] Re: "powersave" governor should be listed as one possible value for the ondemand init.d script
There has been some regression with this file, because the above mentioned change was originally done a long time ago. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1411802 Title: "powersave" governor should be listed as one possible value for the ondemand init.d script Status in sysvinit package in Ubuntu: Confirmed Bug description: On my system i have the following CPU: Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz The only possible options for the scaling governors are "powersave" and "performance" $ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors performance powersave The intention of the /etc/init.d/ondemand script is to select the autoscaling cpu governor The powersave is the equivalent of "ondemand" or "interactive". A patch may be: $ diff ondemand /etc/init.d/ondemand -u --- ondemand 2015-01-16 14:15:03.450942021 -0500 +++ /etc/init.d/ondemand 2015-01-16 13:49:58.392155974 -0500 @@ -36,6 +36,10 @@ GOVERNOR="ondemand" break ;; + *powersave*) + GOVERNOR="powersave" + break + ;; *) exit 0 ;; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1411802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411802] Re: "powersave" governor should be listed as one possible value for the ondemand init.d script
For my post above please note that there is not a regression, as I did the edit to /etc/init.d/ondemand myself a long time ago, and then forgot that I had done so. Since your are changing back from the intel_pstate driver being disabled by default to enabled by default, this change needs to be included. It is urgent because it should be included as part of the 14.04.2 release in less than a week. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1411802 Title: "powersave" governor should be listed as one possible value for the ondemand init.d script Status in sysvinit package in Ubuntu: Confirmed Bug description: On my system i have the following CPU: Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz The only possible options for the scaling governors are "powersave" and "performance" $ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors performance powersave The intention of the /etc/init.d/ondemand script is to select the autoscaling cpu governor The powersave is the equivalent of "ondemand" or "interactive". A patch may be: $ diff ondemand /etc/init.d/ondemand -u --- ondemand 2015-01-16 14:15:03.450942021 -0500 +++ /etc/init.d/ondemand 2015-01-16 13:49:58.392155974 -0500 @@ -36,6 +36,10 @@ GOVERNOR="ondemand" break ;; + *powersave*) + GOVERNOR="powersave" + break + ;; *) exit 0 ;; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1411802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1314653] Re: sysvinit: default cpufreq governor to powersave for intel-pstate driver
Why are you not going to do this for Trusty? Many of us (well, O.K. me) have been forcing the use of the intel_pstate driver in 14.04 and 14.04.1. Now it is my understanding that the intel_pstate driver will be enabled by default in 14.04.2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1314653 Title: sysvinit: default cpufreq governor to powersave for intel-pstate driver Status in sysvinit package in Ubuntu: Fix Released Status in sysvinit source package in Trusty: Won't Fix Status in sysvinit source package in Utopic: Fix Released Bug description: When defaulting to the intel-pstate driver, there are only a couple of cpufreq governors available, none of which are handled in the /etc/init.d/ondemand script. Since this driver is meant to be used for power saving, it seems wrong to leave the system in the kernel default configured "performance" governor after boot, so I think it is pertinent to set this to "powersave" if it is the only suitable non-power hungry governor available. How to reproduce: 1. enable the intel_pstate driver on a recent Intel machine (Sandybridge or above) edit /etc/default/grub, modify the following: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=enable" and run: sudo update-grub and reboot. 2. login 3. wait at least 60 seconds for /etc/init.d/ondemand to complete check out the default cpufreq governor, you will see it is still set to the boot default of "performance": cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor With the attached fix the system will boot into a less aggressive cpufreq governor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1314653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411802] Re: "powersave" governor should be listed as one possible value for the ondemand init.d script
*** This bug is a duplicate of bug 1314653 *** https://bugs.launchpad.net/bugs/1314653 ** This bug has been marked a duplicate of bug 1314653 sysvinit: default cpufreq governor to powersave for intel-pstate driver -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1411802 Title: "powersave" governor should be listed as one possible value for the ondemand init.d script Status in sysvinit package in Ubuntu: Confirmed Bug description: On my system i have the following CPU: Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz The only possible options for the scaling governors are "powersave" and "performance" $ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors performance powersave The intention of the /etc/init.d/ondemand script is to select the autoscaling cpu governor The powersave is the equivalent of "ondemand" or "interactive". A patch may be: $ diff ondemand /etc/init.d/ondemand -u --- ondemand 2015-01-16 14:15:03.450942021 -0500 +++ /etc/init.d/ondemand 2015-01-16 13:49:58.392155974 -0500 @@ -36,6 +36,10 @@ GOVERNOR="ondemand" break ;; + *powersave*) + GOVERNOR="powersave" + break + ;; *) exit 0 ;; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1411802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1649168] [NEW] weekly log rotation is often a day late
Public bug reported: Over the last few Ubuntu releases, the status file the logrotate generates and uses has been adding more and more detailed time stamp information. In 12.04 it seems to only keep information to the day. In 14.04 it seems to only keep information to the hour. In 16.04 it seems to keep information to the second. However, the weekly section of the logrotate program calculates the time since the last rotation to the second with absolutely no jitter margin, and therefore as often as every other week, weekly logs that should rotate on Sunday do not rotate until Monday. I have 43 weeks of weekly rotation data, where on 17 of those weeks the rotation was on Monday and not Sunday. Note that the week after Monday rotation it will always rotate on Sunday due to "the current weekday is before the weekday of the last rotation" condition. Code segment: case ROT_WEEKLY: /* rotate if: 1) the current weekday is before the weekday of the last rotation 2) more then a week has passed since the last rotation */ state->doRotate = ((now.tm_wday < state->lastRotated.tm_wday) || ((mktime(&now) - mktime(&state->lastRotated)) > (7 * 24 * 3600))); There is an upstream bug report at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825776 which I will attempt to link in. It suggests introducing a 60 jitter allowance. I would make it more myself. I first noticed this issue during 16.04 development in 2016.02 (Feb). See also: https://ubuntuforums.org/showthread.php?t=2320149 Do not ask me to run apport collect for this bug report, because it is not needed, and it never works for me anyhow. ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New ** Summary changed: - weekly log roation is often a day late + weekly log rotation is often a day late -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1649168 Title: weekly log rotation is often a day late Status in logrotate package in Ubuntu: New Bug description: Over the last few Ubuntu releases, the status file the logrotate generates and uses has been adding more and more detailed time stamp information. In 12.04 it seems to only keep information to the day. In 14.04 it seems to only keep information to the hour. In 16.04 it seems to keep information to the second. However, the weekly section of the logrotate program calculates the time since the last rotation to the second with absolutely no jitter margin, and therefore as often as every other week, weekly logs that should rotate on Sunday do not rotate until Monday. I have 43 weeks of weekly rotation data, where on 17 of those weeks the rotation was on Monday and not Sunday. Note that the week after Monday rotation it will always rotate on Sunday due to "the current weekday is before the weekday of the last rotation" condition. Code segment: case ROT_WEEKLY: /* rotate if: 1) the current weekday is before the weekday of the last rotation 2) more then a week has passed since the last rotation */ state->doRotate = ((now.tm_wday < state->lastRotated.tm_wday) || ((mktime(&now) - mktime(&state->lastRotated)) > (7 * 24 * 3600))); There is an upstream bug report at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825776 which I will attempt to link in. It suggests introducing a 60 jitter allowance. I would make it more myself. I first noticed this issue during 16.04 development in 2016.02 (Feb). See also: https://ubuntuforums.org/showthread.php?t=2320149 Do not ask me to run apport collect for this bug report, because it is not needed, and it never works for me anyhow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1649168/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1649168] Re: weekly log rotation is often a day late
There is also issue 93 at GitHub: https://github.com/logrotate/logrotate/issues/93 I seem to be unable to create a GitHub account so that I can add to the issue discussion, and point to here. ** Bug watch added: github.com/logrotate/logrotate/issues #93 https://github.com/logrotate/logrotate/issues/93 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1649168 Title: weekly log rotation is often a day late Status in logrotate package in Ubuntu: New Bug description: Over the last few Ubuntu releases, the status file the logrotate generates and uses has been adding more and more detailed time stamp information. In 12.04 it seems to only keep information to the day. In 14.04 it seems to only keep information to the hour. In 16.04 it seems to keep information to the second. However, the weekly section of the logrotate program calculates the time since the last rotation to the second with absolutely no jitter margin, and therefore as often as every other week, weekly logs that should rotate on Sunday do not rotate until Monday. I have 43 weeks of weekly rotation data, where on 17 of those weeks the rotation was on Monday and not Sunday. Note that the week after Monday rotation it will always rotate on Sunday due to "the current weekday is before the weekday of the last rotation" condition. Code segment: case ROT_WEEKLY: /* rotate if: 1) the current weekday is before the weekday of the last rotation 2) more then a week has passed since the last rotation */ state->doRotate = ((now.tm_wday < state->lastRotated.tm_wday) || ((mktime(&now) - mktime(&state->lastRotated)) > (7 * 24 * 3600))); There is an upstream bug report at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825776 which I will attempt to link in. It suggests introducing a 60 jitter allowance. I would make it more myself. I first noticed this issue during 16.04 development in 2016.02 (Feb). See also: https://ubuntuforums.org/showthread.php?t=2320149 Do not ask me to run apport collect for this bug report, because it is not needed, and it never works for me anyhow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1649168/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1649168] Re: weekly log rotation is often a day late
** Description changed: Over the last few Ubuntu releases, the status file the logrotate - generates and uses has been adding more and more detailed time stamp - information. + generates and uses has added more detail to the time stamp information. In 12.04 it seems to only keep information to the day. - In 14.04 it seems to only keep information to the hour. + In 14.04 it seems to keep information to the second. In 16.04 it seems to keep information to the second. However, the weekly section of the logrotate program calculates the time since the last rotation to the second with absolutely no jitter margin, and therefore as often as every other week, weekly logs that should rotate on Sunday do not rotate until Monday. I have 43 weeks of weekly rotation data, where on 17 of those weeks the rotation was on Monday and not Sunday. Note that the week after Monday rotation it will always rotate on Sunday due to "the current weekday is before the weekday of the last rotation" condition. Code segment: - case ROT_WEEKLY: - /* rotate if: -1) the current weekday is before the weekday of the -last rotation -2) more then a week has passed since the last -rotation */ - state->doRotate = ((now.tm_wday < state->lastRotated.tm_wday) -|| -((mktime(&now) - - mktime(&state->lastRotated)) > - (7 * 24 * 3600))); + case ROT_WEEKLY: + /* rotate if: + 1) the current weekday is before the weekday of the + last rotation + 2) more then a week has passed since the last + rotation */ + state->doRotate = ((now.tm_wday < state->lastRotated.tm_wday) + || + ((mktime(&now) - + mktime(&state->lastRotated)) > + (7 * 24 * 3600))); - There is an upstream bug report at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825776 + There is an upstream bug report at: + https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825776 which I will attempt to link in. It suggests introducing a 60 jitter allowance. I would make it more myself. - I first noticed this issue during 16.04 development in 2016.02 (Feb). + I first noticed this issue during 16.04 development in 2016.02 (Feb). However, that computer had previously been a 12.04 server, so I do not have good data about 14.04. See also: https://ubuntuforums.org/showthread.php?t=2320149 Do not ask me to run apport collect for this bug report, because it is not needed, and it never works for me anyhow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1649168 Title: weekly log rotation is often a day late Status in logrotate package in Ubuntu: New Bug description: Over the last few Ubuntu releases, the status file the logrotate generates and uses has added more detail to the time stamp information. In 12.04 it seems to only keep information to the day. In 14.04 it seems to keep information to the second. In 16.04 it seems to keep information to the second. However, the weekly section of the logrotate program calculates the time since the last rotation to the second with absolutely no jitter margin, and therefore as often as every other week, weekly logs that should rotate on Sunday do not rotate until Monday. I have 43 weeks of weekly rotation data, where on 17 of those weeks the rotation was on Monday and not Sunday. Note that the week after Monday rotation it will always rotate on Sunday due to "the current weekday is before the weekday of the last rotation" condition. Code segment: case ROT_WEEKLY: /* rotate if: 1) the current weekday is before the weekday of the last rotation 2) more then a week has passed since the last rotation */ state->doRotate = ((now.tm_wday < state->lastRotated.tm_wday) || ((mktime(&now) - mktime(&state->lastRotated)) > (7 * 24 * 3600))); There is an upstream bug report at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825776 which I will attempt to link in. It suggests introducing a 60 jitter allowance. I would make it more myself. I first noticed this issue during 16.04 development in 2016.02 (Feb). However, that computer had previously been a 12.04 server, so I do not have good data about 14.04. See also: https://ubuntuforums.org/showthread.php?t=2320149 Do not ask
[Touch-packages] [Bug 1540672] Re: [xenial] dhcp server does not work with apparmor enabled
This issue has returned. I'll supply the extra requested information as soon as I can. ** Changed in: isc-dhcp (Ubuntu) Status: Fix Released => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1540672 Title: [xenial] dhcp server does not work with apparmor enabled Status in isc-dhcp package in Ubuntu: Incomplete Bug description: I only seem to be able to make my dhcp server work properly by disabling apparmor. With apparmor enabled it seems to complain that it is unable to open the leases file for append. With apparmor either disabled completely (via linux command line in grub), or set to complain mode for /usr/sbin/dhcpd, the dhcp server appears to work fine (so far). Observed with 2.10-0ubuntu11, and 2.10-0ubuntu12 (from the update of today). I do not know about any previous version, as this is my first attempt with xenial at setting up a dhcp server. My system is being built fresh from the daily Ubuntu server AMD64 ISO of 2016.01.30. The hard disk is new, as the old one (12.04 server) failed. I do not know if it is relevant, but I do notice an edit date of 2016.01.25 in /etc/apparmor.d/usr.sbin.dhcpd The main problem log line: kernel: [ 22.629981] audit: type=1400 audit(1454368046.405:10): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=1198 comm="dhcpd" capability=1 capname="dac_override" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1540672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540672] Re: [xenial] dhcp server does not work with apparmor enabled
I can not seem to run the requested command. I just get this: ubuntu-bug 1540672 No pending crash reports. Try --help for more information. Note: while experienced at bug reports and such, I have never ever successfully run any of the collect stuff. ** Attachment added: "the requested file" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1540672/+attachment/4581937/+files/usr.sbin.dhcpd.002 ** Changed in: isc-dhcp (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1540672 Title: [xenial] dhcp server does not work with apparmor enabled Status in isc-dhcp package in Ubuntu: Confirmed Bug description: I only seem to be able to make my dhcp server work properly by disabling apparmor. With apparmor enabled it seems to complain that it is unable to open the leases file for append. With apparmor either disabled completely (via linux command line in grub), or set to complain mode for /usr/sbin/dhcpd, the dhcp server appears to work fine (so far). Observed with 2.10-0ubuntu11, and 2.10-0ubuntu12 (from the update of today). I do not know about any previous version, as this is my first attempt with xenial at setting up a dhcp server. My system is being built fresh from the daily Ubuntu server AMD64 ISO of 2016.01.30. The hard disk is new, as the old one (12.04 server) failed. I do not know if it is relevant, but I do notice an edit date of 2016.01.25 in /etc/apparmor.d/usr.sbin.dhcpd The main problem log line: kernel: [ 22.629981] audit: type=1400 audit(1454368046.405:10): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=1198 comm="dhcpd" capability=1 capname="dac_override" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1540672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540672] Re: [xenial] dhcp server does not work with apparmor enabled
I am suggesting that the issue was fixed by this: 2016-02-17 17:24:06 upgrade isc-dhcp-server:amd64 4.3.3-5ubuntu4 4.3.3-5ubuntu5 And then broken again by this: 2016-02-26 08:22:59 upgrade isc-dhcp-server:amd64 4.3.3-5ubuntu5 4.3.3-5ubuntu7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1540672 Title: [xenial] dhcp server does not work with apparmor enabled Status in isc-dhcp package in Ubuntu: Confirmed Bug description: I only seem to be able to make my dhcp server work properly by disabling apparmor. With apparmor enabled it seems to complain that it is unable to open the leases file for append. With apparmor either disabled completely (via linux command line in grub), or set to complain mode for /usr/sbin/dhcpd, the dhcp server appears to work fine (so far). Observed with 2.10-0ubuntu11, and 2.10-0ubuntu12 (from the update of today). I do not know about any previous version, as this is my first attempt with xenial at setting up a dhcp server. My system is being built fresh from the daily Ubuntu server AMD64 ISO of 2016.01.30. The hard disk is new, as the old one (12.04 server) failed. I do not know if it is relevant, but I do notice an edit date of 2016.01.25 in /etc/apparmor.d/usr.sbin.dhcpd The main problem log line: kernel: [ 22.629981] audit: type=1400 audit(1454368046.405:10): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=1198 comm="dhcpd" capability=1 capname="dac_override" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1540672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1543794] Re: isc-dhcp-server fails to start on second & further attempts with 'Can't open /var/lib/dhcp/dhcpd.leases for append'
Yes, isc-dhcp - 4.3.3-5ubuntu8 fixes the issue with the dhclient stuff that caused this: Feb 26 14:05:21 DOUG-64 kernel: [ 17.518717] audit: type=1400 audit(1456524321.220:10): apparmor="DENIED" operation="open" profile="/sbin/dhclient" name="/etc/ssl/openssl.cnf" pid=483 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 However, that is not what this bug report is about. This bug report is about these ones: Feb 27 07:53:07 DOUG-64 kernel: [ 21.350331] audit: type=1400 audit(1456588387.171:12): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/dhcpd" pid=1248 comm="dhcpd" capability=1 capname="dac_override" Feb 27 07:53:07 DOUG-64 kernel: [ 21.466959] audit: type=1400 audit(1456588387.287:13): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/dhcpd" pid=1248 comm="dhcpd" capability=3 capname="fowner" Note: the above are "ALLOWED" because I have it set to complain mode. which were fixed, but have now returned. setting back to confirmed. ** Changed in: isc-dhcp (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1543794 Title: isc-dhcp-server fails to start on second & further attempts with 'Can't open /var/lib/dhcp/dhcpd.leases for append' Status in isc-dhcp package in Ubuntu: Confirmed Bug description: During the first start of isc-dhcp-server (using the systemd service unit), a blank dhcpd.leases file is created (presumably owned by root:root). dhcpd starts successfully (and then exits due to no subnet definitions, that's expected). Attempting to start the service again fails with 'Can't open /var/lib/dhcp/dhcpd.leases for append' (the dhcpd.leases file ownership is now dhcpd.dhcpd), and apparmor logs a denial of the dac_override capability. Removing the leases file repeats this process (first start works as expected, future ones do not). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-server 4.3.3-5ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Tue Feb 9 20:58:12 2016 InstallationDate: Installed on 2016-02-09 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540672] Re: [xenial] dhcp server does not work with apparmor enabled
Note 1: isc-dhcp-server 4.3.3-5ubuntu8 does not fix this issue. Note 2: There seems to be other apparmor issues, one of which was fixed by isc-dhcp-client 4.3.3-5ubuntu8. The other remaining one is with named: Feb 27 07:53:07 DOUG-64 kernel: [ 21.320614] audit: type=1400 audit(1456588387.143:11): apparmor="DENIED" operation="open" profile="/usr/sbin/named" name="/proc/sys/net/ipv4/ip_local_port_range" pid=1345 comm="named" requested_mask="r" denied_mask="r" fsuid=109 ouid=0 but if I set that one to "complain" my system crashes during re-boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1540672 Title: [xenial] dhcp server does not work with apparmor enabled Status in isc-dhcp package in Ubuntu: Confirmed Bug description: I only seem to be able to make my dhcp server work properly by disabling apparmor. With apparmor enabled it seems to complain that it is unable to open the leases file for append. With apparmor either disabled completely (via linux command line in grub), or set to complain mode for /usr/sbin/dhcpd, the dhcp server appears to work fine (so far). Observed with 2.10-0ubuntu11, and 2.10-0ubuntu12 (from the update of today). I do not know about any previous version, as this is my first attempt with xenial at setting up a dhcp server. My system is being built fresh from the daily Ubuntu server AMD64 ISO of 2016.01.30. The hard disk is new, as the old one (12.04 server) failed. I do not know if it is relevant, but I do notice an edit date of 2016.01.25 in /etc/apparmor.d/usr.sbin.dhcpd The main problem log line: kernel: [ 22.629981] audit: type=1400 audit(1454368046.405:10): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=1198 comm="dhcpd" capability=1 capname="dac_override" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1540672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549736] Re: dhclient needs read access to /etc/ssl/openssl.cnf
4.3.3-5ubuntu8 does fix the apparmor issue. However, now my IP address lease does not renew. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1549736 Title: dhclient needs read access to /etc/ssl/openssl.cnf Status in isc-dhcp package in Ubuntu: Fix Committed Bug description: Release: Xenial/16.04 syslog shows the following apparmor message: [ 2329.028426] audit: type=1400 audit(1456387524.080:27): apparmor="DENIED" operation="open" profile="/sbin/dhclient" name="/etc/ssl/openssl.cnf" pid=3660 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Not sure it has any observable impact. For standard installs I did not notice anything. Just saw it when trying to debug another problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1549736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540672] Re: [xenial] dhcp server does not work with apparmor enabled
*** This bug is a duplicate of bug 1543794 *** https://bugs.launchpad.net/bugs/1543794 Yes, I think bug #1543794 is a duplicate. ** This bug has been marked a duplicate of bug 1543794 isc-dhcp-server fails to start on second & further attempts with 'Can't open /var/lib/dhcp/dhcpd.leases for append' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1540672 Title: [xenial] dhcp server does not work with apparmor enabled Status in isc-dhcp package in Ubuntu: Incomplete Bug description: I only seem to be able to make my dhcp server work properly by disabling apparmor. With apparmor enabled it seems to complain that it is unable to open the leases file for append. With apparmor either disabled completely (via linux command line in grub), or set to complain mode for /usr/sbin/dhcpd, the dhcp server appears to work fine (so far). Observed with 2.10-0ubuntu11, and 2.10-0ubuntu12 (from the update of today). I do not know about any previous version, as this is my first attempt with xenial at setting up a dhcp server. My system is being built fresh from the daily Ubuntu server AMD64 ISO of 2016.01.30. The hard disk is new, as the old one (12.04 server) failed. I do not know if it is relevant, but I do notice an edit date of 2016.01.25 in /etc/apparmor.d/usr.sbin.dhcpd The main problem log line: kernel: [ 22.629981] audit: type=1400 audit(1454368046.405:10): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=1198 comm="dhcpd" capability=1 capname="dac_override" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1540672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551351] Re: dhclient does not renew leases
This occurs also on my server, and as of two days ago. My system is not renewing the lease of its IP address from my ISP. (while I have static IP adresses, my ISP still requires using dhcp). The expire time is 24 hours, and exactly 24 hours since my last re-boot, internet stopped working. Confirmed again after another 24 hours, but this time I was watching for it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Release: Xenial I think this only recently started after some bind9 updates triggered a rebuild. When booting dhclient gets started and acquires an IP address, but it does seem to lock up somewhere as it does not renew the lease. In my environment I set the lease time to 5 minutes, so I notice such things rather soon. I looked on the dhcp server side but saw any further dhcp messages come in from the client side. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Feb 29 12:32:52 2016 DhclientLeases: SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1551351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551351] Re: dhclient does not renew leases
Well, that one got set as a duplicate of this one. Please see also bug #1551415. I did manage to avoid having to re-boot, via the Rob Whyte method "sudo dhclient eth0", however my leases file is now out of date, but I did observe a new lease actually being granted via capturing the packets on tcpdump. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp source package in Xenial: Confirmed Bug description: Release: Xenial I think this only recently started after some bind9 updates triggered a rebuild. When booting dhclient gets started and acquires an IP address, but it does seem to lock up somewhere as it does not renew the lease. In my environment I set the lease time to 5 minutes, so I notice such things rather soon. I looked on the dhcp server side but saw any further dhcp messages come in from the client side. Related bugs: * bug 1551415: systemctl stop networking hang / timeout ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Feb 29 12:32:52 2016 DhclientLeases: SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1551351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551351] Re: dhclient does not renew leases
Stefan, I think the answer is yes. Just a few minutes before my lease was going to expire, I did: "sudo dhclient enp4s0" However, I didn't notice any change in the leases file, so I expected internet it to stop working after the expire time, but it didn't stop working. So I looked at my tcpdump captures and realized that the lease was granted, it just didn't update the leases file. I never killed anything first, and dhclient is still running... Oh, crap, I see I now have a bunch of dhclients running. doug@DOUG-64:~$ ps aux | grep dhcl root 1049 0.0 0.0 181364 2808 ?Ss Feb29 0:00 /sbin/dhclient -1 -v -pf /run/dhclient.enp4s0.pid -lf /var/lib/dhcp/dhclient.enp4s0.leases -I -df /var/lib/dhcp/dhclient6.enp4s0.leases enp4s0 root 7008 0.0 0.0 181364 2796 ?Ss 07:34 0:00 dhclient enp4s0 root 7368 0.0 0.0 181364 2744 ?Ss 08:01 0:00 dhclient enp4s0 root 7616 0.0 0.0 181364 2688 ?Ss 08:36 0:00 dhclient enp4s0 root 7810 0.0 0.0 181364 2816 ?Ss 08:36 0:00 dhclient enp4s0 I was just trying to avoid having a gap in internet access. I don't really want to do the ifdown && ifup method if I can avoid it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp source package in Xenial: Confirmed Bug description: Release: Xenial I think this only recently started after some bind9 updates triggered a rebuild. When booting dhclient gets started and acquires an IP address, but it does seem to lock up somewhere as it does not renew the lease. In my environment I set the lease time to 5 minutes, so I notice such things rather soon. I looked on the dhcp server side but saw any further dhcp messages come in from the client side. Related bugs: * bug 1551415: systemctl stop networking hang / timeout ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Feb 29 12:32:52 2016 DhclientLeases: SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1551351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
What has been done here is incorrect. The old "ondemand" script was modified so that if the intel_pstate driver was being used, and therefore "ondemand" did not exist, it would fall through to setting the "powersave" governor (refer to bug #1314643). Note that "powersave" with the intel_pstate CPU frequency scaling driver is NOT the same as "powersave" with the acpi-cpufreq CPU frequency scaling driver. The preferred governor with the intel_pstate driver is powersave. I'm saying that this: # more modern processors that support intel_pstate behave worse with # ondemand/powersave and should use performance if [ `cat /sys/devices/system/cpu/cpu$FIRSTCPU/cpufreq/scaling_driver` = intel_pstate ]; then echo 'CPU supports intel_pstate, keeping "performance"' exit 0 fi is incorrect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10%
[Touch-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
>> The preferred governor with the intel_pstate driver is powersave. > Do you have some references/proof for that? This is contrary to what > kernel developers say, see comment 1. In my opinion, that reference is obsolete. While I don't work for Intel, the intel_pstate CPU frequency driver is pretty much the only thing that I work on, and for a few years now, and through 3 maintainers. Why would Intel expend so much effort on powersave mode, if it were better to merely set performance mode and forget about it? The objective with powersave mode is best energy/ performance tradeoff. There are still issues, yes. For example whenever clock modulation becomes involved. Also, there can be a tendency to incorrectly drive up the CPU frequency. There is work in progress that should address these issues (see: http://askubuntu.com/questions/812530 /cpu-frequency-scaling-not-working-as-intended-on-vanilla- ubuntu-16-04/812721#812721 and the reference links therein.) I'll try to come back, maybe this weekend, with some energy comparison numbers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_
[Touch-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
The table formatting got messed up, trying again: Load: idle0.5XX 2X 3X 4X 5X 100% powersave 570811037 16075 29147 45913 61165 76650 81695 3.817.3610.72 19.43 30.61 40.78 51.10 54.46 performance 574914536 22841 38475 51757 64425 77000 81733 3.839.6915.23 25.65 34.50 42.95 51.33 54.49 0.7%31.7% 42.1% 32.0% 12.7% 5.3%0.5%0.0% -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0
[Touch-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
Using kernel 4.8-rc5 I did some energy tests, using a SpecPower simulator that I made one time. I reused intel_pstate powersave data from a previous test. Reference: http://marc.info/?l=linux-kernel&m=147326197513427&w=2 Big numbers are Joules (package Joules from turbostat) Smaller numbers are watts, 1500 Seconds test run time. X ~= 18.2% on a real SpecPower. Load: idle0.5XX 2X 3X 4X 5X 100% powersave 570811037 16075 29147 45913 61165 76650 81695 3.817.3610.72 19.43 30.61 40.78 51.10 54.46 performance 574914536 22841 38475 51757 64425 77000 81733 3.839.6915.23 25.65 34.50 42.95 51.33 54.49 0.7%31.7% 42.1% 32.0% 12.7% 5.3%0.5%0.0% Note: A real SpecPower test-bed tends to get less dramatic results than my simulator. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |
[Touch-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
@Haw Loeung: It would be good to understand in more detail your findings. As far as I know (and I am not an expert in this area), great care has been taken to avoid things like wakeups just to decide to go idle. I did a test on my computer (Ubuntu 16.04 server, no GUI), but to avoid extra overheads, I used the /proc/timer_stats method. I also did the test over 300 seconds, so as to dilute influence from the command itself. Kernel: 4.8.0-040800rc5-generic intel_pstate, "idle" system: powersave: 14722 events, 49.073 events / second performance: 14964 events, 49.879 events / second intel_pstate: extra "idle" system: powersave: 6381 total events, 21.269 events / second performance: 6788 events, 22.626 events / second Which kernel are you using? There was a flurry of high wakeups activity in June, but I thought it all got resolved. Note that there was a slight increase in wakeups with the recent change to a utilization based algorithm, but that was good thing because it solved a very long standing issue whereby the CPU frequency might not increase under high load for periodic workflows that just so happened to be idle on jiffy boundaries. You mention "on some workloads". Could you be more specific? i.e. so that I can attempt to recreate your scenario on my computer. My script: $ cat ./set_cpu_timer_stats_2 #! /bin/bash # Take a 300 second time sample # A long time is needed to amortize/dilute the effect of the command itself. # Reset the counters echo "0" > /proc/timer_stats echo "1" > /proc/timer_stats # Now let the sample time elapse sleep 300 # Now observe the timer counters cat /proc/timer_stats # And turn off timer stats. echo "0" > /proc/timer_stats What does "extra idle" mean?: $ cat set_cpu_turn_off_services #! /bin/bash # Turn off some services to try to get "idle" to be more "idle" sudo systemctl stop mysql.service sudo systemctl stop apache2.service sudo systemctl stop nmbd.service sudo systemctl stop smbd.service sudo systemctl stop cron.service sudo systemctl stop winbind.service sudo systemctl stop apt-daily.timer Recent wakeups thread: http://marc.info/?t=14661775703&r=1&w=2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42%
[Touch-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
@Haw Loeung: In addition to what I wrote earlier: > With the new Ubuntu archive servers, we saw constantly high load > and after some tinkering, we found that it was mostly CPUs > being woken up to see if they should enter idle states. > Changing the CPU frequency scaling governor to "performance" saw a > considerable drop. What do you mean by "high load"? And when you say "saw a considerable drop", does that mean in wakeups per second or load? Note that you should observe a significant difference in load average on a server between powersave and performance mode, and that actually indicates things are working as they should be. For the SpecPower simulator test I posted above, I'll add some more data for the 0.5X and X lines: 0.5X, where Performance used 31.7% more package power: Powersave: Busy%: 12.58% (load average = 1.01) Bzy MHz: 1651 Performance: Busy%: 5.04% (load average = 0.40) Bzy MHz: 3686 X, where Performance used 42.1% more package power: Powersave: Busy%: 23.66% (load average = 1.89) Bzy MHz: 1798 Performance: Busy%: 10.56% (load average = 0.84) Bzy MHz: 3681 Isn't energy consumption what really matters, as long as performance doesn't suffer too much? What I would like to see for your servers is the results from: sudo turbostat -J -S --debug sleep 300 For the intel_pstate CPU frequency scaling driver and the powersave and performance scaling governors with your work flow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | +
[Touch-packages] [Bug 1540672] [NEW] [xenial] dhcp server does not work with apparmor enabled
Public bug reported: I only seem to be able to make my dhcp server work properly by disabling apparmor. With apparmor enabled it seems to complain that it is unable to open the leases file for append. With apparmor either disabled completely (via linux command line in grub), or set to complain mode for /usr/sbin/dhcpd, the dhcp server appears to work fine (so far). Observed with 2.10-0ubuntu11, and 2.10-0ubuntu12 (from the update of today). I do not know about any previous version, as this is my first attempt with xenial at setting up a dhcp server. My system is being built fresh from the daily Ubuntu server AMD64 ISO of 2016.01.30. The hard disk is new, as the old one (12.04 server) failed. I do not know if it is relevant, but I do notice an edit date of 2016.01.25 in /etc/apparmor.d/usr.sbin.dhcpd The main problem log line: kernel: [ 22.629981] audit: type=1400 audit(1454368046.405:10): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=1198 comm="dhcpd" capability=1 capname="dac_override" ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: xenial ** Attachment added: "some selected syslog entries" https://bugs.launchpad.net/bugs/1540672/+attachment/4561728/+files/syslog_excerpts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1540672 Title: [xenial] dhcp server does not work with apparmor enabled Status in apparmor package in Ubuntu: New Bug description: I only seem to be able to make my dhcp server work properly by disabling apparmor. With apparmor enabled it seems to complain that it is unable to open the leases file for append. With apparmor either disabled completely (via linux command line in grub), or set to complain mode for /usr/sbin/dhcpd, the dhcp server appears to work fine (so far). Observed with 2.10-0ubuntu11, and 2.10-0ubuntu12 (from the update of today). I do not know about any previous version, as this is my first attempt with xenial at setting up a dhcp server. My system is being built fresh from the daily Ubuntu server AMD64 ISO of 2016.01.30. The hard disk is new, as the old one (12.04 server) failed. I do not know if it is relevant, but I do notice an edit date of 2016.01.25 in /etc/apparmor.d/usr.sbin.dhcpd The main problem log line: kernel: [ 22.629981] audit: type=1400 audit(1454368046.405:10): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=1198 comm="dhcpd" capability=1 capname="dac_override" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1540672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1541532] Re: migrate UTC setting from /etc/default/rcS to adjtime
The claim in comment number #4 is: > This bug was fixed in the package installation-guide - 20160121ubuntu2 Then why can I not find the master source code at: https://code.launchpad.net/~ubuntu-core-dev/installation-guide/ubuntu ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1541532 Title: migrate UTC setting from /etc/default/rcS to adjtime Status in installation-guide package in Ubuntu: Fix Released Status in lupin package in Ubuntu: Fix Released Status in mbr package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Fix Released Status in mbr package in Debian: New Bug description: This has been an Ubuntu delta in systemd and perhaps other Ubuntu packages for a long time. But /etc/default/rcS is a SysV-ism, and no other setting in there is relevant. Steps: * Bump the version guard in systemd.conf for migrating the actual setting (keep until 16.04 LTS) * Ensure that we only look at the LOCAL setting during boot, and do no actual drift correction at boot, as the kernel does that by itself. * grep the archive for software which might directly look at or even write that file (Ubuntu specific config tools and the like). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/installation-guide/+bug/1541532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540672] Re: [xenial] dhcp server does not work with apparmor enabled
I gather I was supposed to file this under isc-dhcp instead of apparmour. ** Also affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1540672 Title: [xenial] dhcp server does not work with apparmor enabled Status in apparmor package in Ubuntu: New Status in isc-dhcp package in Ubuntu: New Bug description: I only seem to be able to make my dhcp server work properly by disabling apparmor. With apparmor enabled it seems to complain that it is unable to open the leases file for append. With apparmor either disabled completely (via linux command line in grub), or set to complain mode for /usr/sbin/dhcpd, the dhcp server appears to work fine (so far). Observed with 2.10-0ubuntu11, and 2.10-0ubuntu12 (from the update of today). I do not know about any previous version, as this is my first attempt with xenial at setting up a dhcp server. My system is being built fresh from the daily Ubuntu server AMD64 ISO of 2016.01.30. The hard disk is new, as the old one (12.04 server) failed. I do not know if it is relevant, but I do notice an edit date of 2016.01.25 in /etc/apparmor.d/usr.sbin.dhcpd The main problem log line: kernel: [ 22.629981] audit: type=1400 audit(1454368046.405:10): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=1198 comm="dhcpd" capability=1 capname="dac_override" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1540672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1543794] Re: isc-dhcp-server fails to start on second & further attempts with 'Can't open /var/lib/dhcp/dhcpd.leases for append'
Try disabling apparmour. That fixed it for me. see also bug 1540672. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1543794 Title: isc-dhcp-server fails to start on second & further attempts with 'Can't open /var/lib/dhcp/dhcpd.leases for append' Status in isc-dhcp package in Ubuntu: Confirmed Bug description: During the first start of isc-dhcp-server (using the systemd service unit), a blank dhcpd.leases file is created (presumably owned by root:root). dhcpd starts successfully (and then exits due to no subnet definitions, that's expected). Attempting to start the service again fails with 'Can't open /var/lib/dhcp/dhcpd.leases for append' (the dhcpd.leases file ownership is now dhcpd.dhcpd), and apparmor logs a denial of the dac_override capability. Removing the leases file repeats this process (first start works as expected, future ones do not). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-server 4.3.3-5ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Tue Feb 9 20:58:12 2016 InstallationDate: Installed on 2016-02-09 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540672] Re: [xenial] dhcp server does not work with apparmor enabled
I used aa-logprof and it came up with the the attached file. Now I can run apparmour in enforce mode. i.e. "sudo aa-enforce /usr/sbin/dhcpd" ** Attachment added: "an apparmour profile with changes so that it works" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1540672/+attachment/4573987/+files/usr.sbin.dhcpd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1540672 Title: [xenial] dhcp server does not work with apparmor enabled Status in apparmor package in Ubuntu: New Status in isc-dhcp package in Ubuntu: New Bug description: I only seem to be able to make my dhcp server work properly by disabling apparmor. With apparmor enabled it seems to complain that it is unable to open the leases file for append. With apparmor either disabled completely (via linux command line in grub), or set to complain mode for /usr/sbin/dhcpd, the dhcp server appears to work fine (so far). Observed with 2.10-0ubuntu11, and 2.10-0ubuntu12 (from the update of today). I do not know about any previous version, as this is my first attempt with xenial at setting up a dhcp server. My system is being built fresh from the daily Ubuntu server AMD64 ISO of 2016.01.30. The hard disk is new, as the old one (12.04 server) failed. I do not know if it is relevant, but I do notice an edit date of 2016.01.25 in /etc/apparmor.d/usr.sbin.dhcpd The main problem log line: kernel: [ 22.629981] audit: type=1400 audit(1454368046.405:10): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=1198 comm="dhcpd" capability=1 capname="dac_override" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1540672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540672] Re: [xenial] dhcp server does not work with apparmor enabled
Yes, I am seeing this issue with an up to date Xenial (well, updated yesterday). I can not undo the changes to the profile. Why not? Because I didn't know that aa-logprof didn't make a backup file before messing with the file, and I had not saved one myself. However, I'll see if I can find it elsewhere. I suspect you meant to say "duplicate of bug 1543794" which myself it think it is the other way around. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1540672 Title: [xenial] dhcp server does not work with apparmor enabled Status in isc-dhcp package in Ubuntu: Incomplete Bug description: I only seem to be able to make my dhcp server work properly by disabling apparmor. With apparmor enabled it seems to complain that it is unable to open the leases file for append. With apparmor either disabled completely (via linux command line in grub), or set to complain mode for /usr/sbin/dhcpd, the dhcp server appears to work fine (so far). Observed with 2.10-0ubuntu11, and 2.10-0ubuntu12 (from the update of today). I do not know about any previous version, as this is my first attempt with xenial at setting up a dhcp server. My system is being built fresh from the daily Ubuntu server AMD64 ISO of 2016.01.30. The hard disk is new, as the old one (12.04 server) failed. I do not know if it is relevant, but I do notice an edit date of 2016.01.25 in /etc/apparmor.d/usr.sbin.dhcpd The main problem log line: kernel: [ 22.629981] audit: type=1400 audit(1454368046.405:10): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=1198 comm="dhcpd" capability=1 capname="dac_override" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1540672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1540672] Re: [xenial] dhcp server does not work with apparmor enabled
Oh, I see there was an update to this stuff a few minutes ago. It seems to fix the issue. I couldn't find the original profile file in any source package nor could I find any bizzare branch on launchpad, so I installed it on another server and copied the file back to the problem server, /etc/apparmor.d/usr.sbin.dhcpd. ** Changed in: isc-dhcp (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1540672 Title: [xenial] dhcp server does not work with apparmor enabled Status in isc-dhcp package in Ubuntu: Fix Released Bug description: I only seem to be able to make my dhcp server work properly by disabling apparmor. With apparmor enabled it seems to complain that it is unable to open the leases file for append. With apparmor either disabled completely (via linux command line in grub), or set to complain mode for /usr/sbin/dhcpd, the dhcp server appears to work fine (so far). Observed with 2.10-0ubuntu11, and 2.10-0ubuntu12 (from the update of today). I do not know about any previous version, as this is my first attempt with xenial at setting up a dhcp server. My system is being built fresh from the daily Ubuntu server AMD64 ISO of 2016.01.30. The hard disk is new, as the old one (12.04 server) failed. I do not know if it is relevant, but I do notice an edit date of 2016.01.25 in /etc/apparmor.d/usr.sbin.dhcpd The main problem log line: kernel: [ 22.629981] audit: type=1400 audit(1454368046.405:10): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=1198 comm="dhcpd" capability=1 capname="dac_override" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1540672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551351] Re: dhclient does not renew leases
>From Stephan comment 14: "Hm, of course, if one starts dhclient in debug mode (foreground) by adding a "-d", everything does work." Yes, that does seem to work, but only for about another day, at least in my case. Thereafter, my ISP stopped returning my domain name, host name and some other stuff, and would only renew the lease for 1 hour instead of the normal 1 day. I suppose it doesn't matter because, I use supersede directives for that stuff anyhow. From my tcpdump captures, I have not been able to determine what, if anything, is different in the request, including the option parameter list request. In my opinion, this bug report should have an importance level of critical. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases Status in bind9 package in Ubuntu: Confirmed Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9 source package in Xenial: Confirmed Status in isc-dhcp source package in Xenial: Confirmed Bug description: Release: Xenial I think this only recently started after some bind9 updates triggered a rebuild. When booting dhclient gets started and acquires an IP address, but it does seem to lock up somewhere as it does not renew the lease. In my environment I set the lease time to 5 minutes, so I notice such things rather soon. I looked on the dhcp server side but saw any further dhcp messages come in from the client side. Related bugs: * bug 1551415: systemctl stop networking hang / timeout ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Feb 29 12:32:52 2016 DhclientLeases: SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551351] Re: dhclient does not renew leases
Correction 1: Stefan not Stephan, sorry. Correction 2: Things broke down about another 1/2 day after the lease times changes to 1 hour. The client didn't seem to release this and resorted to broadcast type discover stuff. Then it was getting leases for 5 minutes, and the cycle continued until I re-booted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases Status in bind9 package in Ubuntu: Confirmed Status in isc-dhcp package in Ubuntu: Confirmed Status in bind9 source package in Xenial: Confirmed Status in isc-dhcp source package in Xenial: Confirmed Bug description: Release: Xenial I think this only recently started after some bind9 updates triggered a rebuild. When booting dhclient gets started and acquires an IP address, but it does seem to lock up somewhere as it does not renew the lease. In my environment I set the lease time to 5 minutes, so I notice such things rather soon. I looked on the dhcp server side but saw any further dhcp messages come in from the client side. Related bugs: * bug 1551415: systemctl stop networking hang / timeout ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Feb 29 12:32:52 2016 DhclientLeases: SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1493156] Re: pm-suspend aborts if highest numbered CPU offline, as of kernel 4.2
As of kernel 4.4-rc1 this bug becomes invalid, as the kernel was patched such
that this issue no longer occurs.
I'll wait until kernel 4.4 is finished, check again, then set the status of
this bug report to invalid.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1493156
Title:
pm-suspend aborts if highest numbered CPU offline, as of kernel 4.2
Status in pm-utils package in Ubuntu:
New
Bug description:
Kernel 4.2 includes a significant commit
(87549141d516aee71d511138e27117c41e8aef68), after the patch the files
and directory are present even if the CPU is offline. If the CPU is
offline, writing to those files isn't allowed and so the echo in
94cpufreq fails.
If the failed echo is not the last pass through the loop, then
the bad exit code gets overwritten with a good one before
the loop exits. If the failed echo is the last pass through the loop, due to
the highest numbered CPU being offline, then then 94cpufreq returns an error
code and pm-suspend aborts.
So what is needed is something like (and this doesn't actually work
yet):
hibernate_cpufreq()
{
( cd /sys/devices/system/cpu/
for x in cpu[0-9]*; do
# if cpufreq is a symlink, it is handled by another cpu. Skip.
[ -L "$x/cpufreq" ] && continue
gov="$x/cpufreq/scaling_governor"
# if we do not have a scaling_governor file, skip.
[ -f "$gov" ] || continue
+ # if the CPU is offline, skip, unless no file, i.e. CPU0.
+ [ $(cat "$x/online") = "1" -o ! -f "$x/online" ] || continue
Or
+ if [ $(cat "$x/online") = "1" ] || [ ! -f "$x/online" ]; then
+ continue;
+fi
Or something similar that actually works.
# if our temporary governor is not available, skip.
grep -q "$TEMPORARY_CPUFREQ_GOVERNOR" \
"$x/cpufreq/scaling_available_governors" || continue
savestate "${x}_governor" < "$gov"
echo "$TEMPORARY_CPUFREQ_GOVERNOR" > "$gov"
done )
}
Or just force a good return code at the end (which is what I'm doing
now, so that I can move on).
Note: I also filed this same bug report upstream.
https://bugs.freedesktop.org/show_bug.cgi?id=91914
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1493156/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1493156] Re: pm-suspend aborts if highest numbered CPU offline, as of kernel 4.2
** Changed in: pm-utils (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1493156
Title:
pm-suspend aborts if highest numbered CPU offline, as of kernel 4.2
Status in pm-utils package in Ubuntu:
Invalid
Bug description:
Kernel 4.2 includes a significant commit
(87549141d516aee71d511138e27117c41e8aef68), after the patch the files
and directory are present even if the CPU is offline. If the CPU is
offline, writing to those files isn't allowed and so the echo in
94cpufreq fails.
If the failed echo is not the last pass through the loop, then
the bad exit code gets overwritten with a good one before
the loop exits. If the failed echo is the last pass through the loop, due to
the highest numbered CPU being offline, then then 94cpufreq returns an error
code and pm-suspend aborts.
So what is needed is something like (and this doesn't actually work
yet):
hibernate_cpufreq()
{
( cd /sys/devices/system/cpu/
for x in cpu[0-9]*; do
# if cpufreq is a symlink, it is handled by another cpu. Skip.
[ -L "$x/cpufreq" ] && continue
gov="$x/cpufreq/scaling_governor"
# if we do not have a scaling_governor file, skip.
[ -f "$gov" ] || continue
+ # if the CPU is offline, skip, unless no file, i.e. CPU0.
+ [ $(cat "$x/online") = "1" -o ! -f "$x/online" ] || continue
Or
+ if [ $(cat "$x/online") = "1" ] || [ ! -f "$x/online" ]; then
+ continue;
+fi
Or something similar that actually works.
# if our temporary governor is not available, skip.
grep -q "$TEMPORARY_CPUFREQ_GOVERNOR" \
"$x/cpufreq/scaling_available_governors" || continue
savestate "${x}_governor" < "$gov"
echo "$TEMPORARY_CPUFREQ_GOVERNOR" > "$gov"
done )
}
Or just force a good return code at the end (which is what I'm doing
now, so that I can move on).
Note: I also filed this same bug report upstream.
https://bugs.freedesktop.org/show_bug.cgi?id=91914
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1493156/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301015] Re: Networking does not restart
Bug 1382059 is duplicate with bug 1298505. The serverguide has already
been fixed for 14.04. The bug remains open for the 12.04 serverguide,
but is unlikely to ever be done.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1301015
Title:
Networking does not restart
Status in “ifupdown” package in Ubuntu:
Confirmed
Bug description:
In Ubuntu Server 14.04 it appears it is not possible to restart
networking. This is fresh install from ISO.
wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
wirehive@ubuntu:~$ echo $?
1
wirehive@ubuntu:~$ sudo service networking restart
stop: Job failed while stopping
start: Job is already running: networking
wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
+ PATH=/sbin:/bin
+ RUN_DIR=/run/network
+ IFSTATE=/run/network/ifstate
+ STATEDIR=/run/network/state
+ '[' -x /sbin/ifup ']'
+ '[' -x /sbin/ifdown ']'
+ . /lib/lsb/init-functions
+++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d
2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
++ . /lib/lsb/init-functions.d/20-left-info-blocks
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d
2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
++ . /lib/lsb/init-functions.d/50-ubuntu-logging
+++ LOG_DAEMON_MSG=
++ FANCYTTY=
++ '[' -e /etc/lsb-base-logging.sh ']'
++ true
+ CONFIGURE_INTERFACES=yes
+ EXCLUDE_INTERFACES=
+ VERBOSE=no
+ '[' -f /etc/default/networking ']'
+ verbose=
+ '[' no = yes ']'
+ case "$1" in
+ init_is_upstart
+ '[' -x /sbin/initctl ']'
+ /bin/grep -q upstart
+ /sbin/initctl version
+ return 0
+ exit 1
wirehive@ubuntu:~$ sudo bash -x service networking restart
++ basename service
+ VERSION='service ver. 0.91-ubuntu1'
++ basename service
+ USAGE='Usage: service < option > | --status-all | [ service_name [ command
| --full-restart ] ]'
+ SERVICE=
+ ACTION=
+ SERVICEDIR=/etc/init.d
+ OPTIONS=
+ '[' 2 -eq 0 ']'
+ cd /
+ '[' 2 -gt 0 ']'
+ case "${1}" in
+ '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
+ '[' 2 -eq 2 -a restart = --full-restart ']'
+ '[' -z '' ']'
+ SERVICE=networking
+ shift
+ '[' 1 -gt 0 ']'
+ case "${1}" in
+ '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
+ '[' 1 -eq 2 -a '' = --full-restart ']'
+ '[' -z networking ']'
+ '[' -z '' ']'
+ ACTION=restart
+ shift
+ '[' 0 -gt 0 ']'
+ '[' -r /etc/init/networking.conf ']'
+ which initctl
+ grep -q upstart
+ initctl version
+ case "${ACTION}" in
+ stop networking
stop: Job failed while stopping
+ :
+ exec start networking
start: Job is already running: networking
wirehive@ubuntu:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377537] Re: Screen does not lock or turn off automatically
In my case this was a new 14.10 installation from the daily ISO of 2014.09.16. It was todays updates that created this issue, but the last update I did was September 30th. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1377537 Title: Screen does not lock or turn off automatically Status in “unity” package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10 (upgraded from 14.04), the screen does not lock or turn off after the designated time in System Settings / Brightness and Lock. The screen lock can still be activated manually from the System menu or keyboard shortcut (although I notice that the default has changed from CTRL-ALT-DEL to Super-L, and if I change this back in the System Settings / Keyboard / Shortcuts, both combinations work - it seems that the unity plugin in compiz (CCSM / unity / general) has aother screen lock key short cut). Other users are reporting the same issue: see http://ubuntuforums.org/showthread.php?t=2246601&highlight=turn. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 Uname: Linux 3.17.0-rc7-git-20140929.1829 x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Oct 5 08:07:30 2014 InstallationDate: Installed on 2014-02-08 (238 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140207) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1377537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
