[Touch-packages] [Bug 2063371] Re: protection-domain-mapper and qrtr-tools should not be in ubuntu-desktop-raspi
*** This bug is a duplicate of bug 2062667 *** https://bugs.launchpad.net/bugs/2062667 ** This bug has been marked a duplicate of bug 2062667 Fails on (and should be removed from) raspi desktop -- 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/2063371 Title: protection-domain-mapper and qrtr-tools should not be in ubuntu- desktop-raspi Status in ubuntu-meta package in Ubuntu: New Bug description: I noticed from our automated certification tests on raspberry pi Noble desktop images that the pd-mapper service was failing on boot. It looks like this is a package only intended for qualcomm desktop system, and not something that is needed by raspberry pi. It looks like this got added with https://code.launchpad.net/~xnox/ubuntu- seeds/+git/ubuntu/+merge/453233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2063371/+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 2063371] [NEW] protection-domain-mapper and qrtr-tools should not be in ubuntu-desktop-raspi
Public bug reported: I noticed from our automated certification tests on raspberry pi Noble desktop images that the pd-mapper service was failing on boot. It looks like this is a package only intended for qualcomm desktop system, and not something that is needed by raspberry pi. It looks like this got added with https://code.launchpad.net/~xnox/ubuntu-seeds/+git/ubuntu/+merge/453233 ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- 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/2063371 Title: protection-domain-mapper and qrtr-tools should not be in ubuntu- desktop-raspi Status in ubuntu-meta package in Ubuntu: New Bug description: I noticed from our automated certification tests on raspberry pi Noble desktop images that the pd-mapper service was failing on boot. It looks like this is a package only intended for qualcomm desktop system, and not something that is needed by raspberry pi. It looks like this got added with https://code.launchpad.net/~xnox/ubuntu- seeds/+git/ubuntu/+merge/453233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2063371/+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 1957455] [NEW] Failure connecting to ap setup with a mode
Public bug reported: One of the tests we run for the network manager snap uncovered this problem on uc18 with network-manager 1.10 snap, but I've also been able to reproduce it in the previous snap version, as well as with core20 and with focal. On a laptop with intel wifi card, we installed a fresh image (see above) and network-manager snap or deb as appropriate. The most straightforward way to run the test we are using, for example with Ubuntu core 18: $ sudo snap install checkbox --devmode --channel=uc18/stable After it is installed: $ cd /snap/checkbox18/current/providers/plainbox-provider-checkbox/bin $ ./wifi_nmcli_test.py ap wlan0 a NB: in the above example, replace wlan0 with the correct device if it's something else, and replace uc18 track and checkbox18 directory as appropriate, if you are using uc20 or focal use the uc20 track. This test uses network-manager to create an ap, then tries to connect to it. Output with uc18: https://pastebin.canonical.com/p/CBFqj2Mcgr/ Output with focal: https://pastebin.canonical.com/p/4Shm6pWzpM/ This test can also run in bg mode, and works fine with that. So the test itself works, and network-manager seems to be able to create an AP in some mode, but it doesn't seem to work with a ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1957455 Title: Failure connecting to ap setup with a mode Status in network-manager package in Ubuntu: New Bug description: One of the tests we run for the network manager snap uncovered this problem on uc18 with network-manager 1.10 snap, but I've also been able to reproduce it in the previous snap version, as well as with core20 and with focal. On a laptop with intel wifi card, we installed a fresh image (see above) and network-manager snap or deb as appropriate. The most straightforward way to run the test we are using, for example with Ubuntu core 18: $ sudo snap install checkbox --devmode --channel=uc18/stable After it is installed: $ cd /snap/checkbox18/current/providers/plainbox-provider-checkbox/bin $ ./wifi_nmcli_test.py ap wlan0 a NB: in the above example, replace wlan0 with the correct device if it's something else, and replace uc18 track and checkbox18 directory as appropriate, if you are using uc20 or focal use the uc20 track. This test uses network-manager to create an ap, then tries to connect to it. Output with uc18: https://pastebin.canonical.com/p/CBFqj2Mcgr/ Output with focal: https://pastebin.canonical.com/p/4Shm6pWzpM/ This test can also run in bg mode, and works fine with that. So the test itself works, and network-manager seems to be able to create an AP in some mode, but it doesn't seem to work with a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1957455/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
I also tried this on my pi400 and confirmed I can see and connect to bluetooth devices after updating to bluez 5.55-0ubuntu1.1 from groovy- proposed ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Committed Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: Fix Committed Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+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 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
hah, ok that makes more sense then. Looks like this works, thanks! -- 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: Fix Committed Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+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 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
Ok, yeah I see it running: /usr/bin/python3 /tmp/ubuntu-release-upgrader-n98wh3a9/bionic --mode=server --frontend=DistUpgradeViewNonInteractive and $ sudo cat /tmp/ubuntu-release-upgrader-n98wh3a9/DistUpgradeVersion.py VERSION = '18.04.33' after letting it run a while, I did see it seemed to be stuck on ntp and asking me what I wanted to do. I Switched windows but I was pretty sure I didn't press anything else. It had progressed when I went back, but I wouldn't have expected it to be asking at all. I'll try to reproduce again, but it takes a while to get there. -- 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: Fix Committed Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+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 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
Strange, that link seems to suggest it is in proposed already, but when I try to run 'do-release-upgrade -p -f DistUpgradeViewNonInteractive', I don't seem to get that. Do I need to do some other manual step to get it first, or do I need it from xenial instead since that's where I'm coming from? Even though I used -p, proposed doesn't seem to be on in /etc/apt/source.list (after I got the error from above again, I killed the upgrader and checked this) $ apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:18.04.32 Candidate: 1:18.04.32 Version table: *** 1:18.04.32 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1:18.04.17 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages -- 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: Fix Committed Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to
[Touch-packages] [Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
>From a xenial system, I tried upgrading to bionic with do-release- upgrade with -f DistUpgradeViewNonInteractive and *not* setting up the force-confdef option, and it asks for input Here's where it got stuck waiting for input: Configuration file '/etc/ntp.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** ntp.conf (Y/I/N/O/D/Z) [default=N] ? -- 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Bionic: New Status in ubuntu-release-upgrader source package in Bionic: In Progress Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
For the xenial->bionic question, I had already implemented the workaround mentioned here to use Dpkg::Options::="--force-confdef" across all upgrade tests, which has been working fine. I can remove the workaround and try it if you are specifically interested in finding out whether it's necessary on the upgrade to bionic though. -- 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: In Progress Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: In Progress Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: In Progress Bug description: I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+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 1796193] [NEW] unattended do-release-upgrade asks about /etc/cron.daily/apt-compat
Public bug reported: I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/1796193 Title: unattended do-release-upgrade asks about /etc/cron.daily/apt-compat Status in apt package in Ubuntu: New Bug description: I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+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 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade
I was able to test this on a m10 tablet. The fix seems to have gone through to the cooler image I was trying to test - r13 in ubuntu- touch/staging/bq-aquaris-pd.en, and now no longer hangs on install. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1653725 Title: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade Status in Canonical System Image: Confirmed Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Triaged Status in lxc source package in Xenial: Fix Committed Status in lxc source package in Yakkety: Fix Committed Status in lxc source package in Zesty: Fix Released Bug description: # SRU ## Rationale LXC 2.0.6 introduced a writability test for /var/lib/lxc which breaks the corner case of partly-writable systems like the Ubuntu phone. This upload fixes this by changing the test to a simple readability one. ## Test case 1) Attempt to run lxc-start with /var/lib/lxc on a read-only filesystem but /var/lib/lxc/ on a writable one. 2) Confirm that the container now starts. ## Regression potential This upload only changes the check from read/write to read so the only consequence of this should be more cases now being allowed. In the case where a writable /var/lib/lxc is in fact absolutely required for the requested operation, the operation will still fail, just a bit later and with a slightly less clear error message (as was the case pre-2.0.6). # Original report As in topic. Since the 20161217 rootfs, after upgrade of lxc from 2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the lxc-android-config service does not start - making the devices unbootable. The syslog only states this: Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and Container Initialization... Jan 3 10:50:30 ubuntu-phablet kernel: [5.790810] (3)[1:systemd]SLEEP_EN = 0x1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting Light Display Manager... Jan 3 10:50:30 ubuntu-phablet systemd-udevd[672]: Could not generate persistent MAC address for ifb0: No such file or directory Jan 3 10:50:30 ubuntu-phablet systemd-udevd[684]: Could not generate persistent MAC address for ifb1: No such file or directory Jan 3 10:50:30 ubuntu-phablet lxc-start[1220]: You lack access to /var/lib/lxc Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Control process exited, code=exited status=1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Failed to start LXC Android Config and Container Initialization. Jan 3 10:50:30 ubuntu-phablet systemd[1]: Dependency failed for force-mtp.service. Jan 3 10:50:30 ubuntu-phablet systemd[1]: force-mtp.service: Job force-mtp.service/start failed with result 'dependency'. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Unit entered failed state. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Failed with result 'exit-code'. This makes all of our frieza and cooler devices useless for testing purposes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1653725/+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 1579135] Re: kernel BUG on snap disconnect from within a snap
Unfortunately no, I mentioned earlier that I'm no longer able to reproduce the problem but John said nothing went in that should have fixed it. I'll leave it up to you guys if you'd like to invalidate it or keep it open, but for me it is now unreproducible. :( -- 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/1579135 Title: kernel BUG on snap disconnect from within a snap Status in apparmor package in Ubuntu: Incomplete Bug description: First, a bit of background: I've built a go binary of the upstream snappy integration tests, and built them into a snap so that we can easily keep them up to date, and call them from other test suites. I'm running through the tests in qemu on a current 16 image (built yesteray), and hitting this most of the time with the homeInterface Suite tests in particular. The networkInterfaceSuite tests also seem to produce a similar problem: sudo snap connect home-consumer:home ubuntu-core:home [/] Connect home-consumer:home to ubuntu-core:home home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable sudo snap disconnect home-consumer:home ubuntu-core:home [ 519.416354] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 519.417327] IP: [] profile_cmp+0x2f/0x180 [ 519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 [ 519.418574] Oops: [#1] SMP [ 519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 nls_iso8859_1 usb_storage ahci libahci squashfs [ 519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 4.4.0-21-generic #37-Ubuntu [ 519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 88001b58c000 [ 519.425385] RIP: 0010:[] [] profile_cmp+0x2f/0x180 [ 519.426242] RSP: 0018:88001b58fcb0 EFLAGS: 00010086 [ 519.426791] RAX: RBX: 88001b1b1400 RCX: 0006 [ 519.427628] RDX: RSI: RDI: 0009 [ 519.428405] RBP: 88001b58fcc0 R08: 000a R09: 0274 [ 519.429127] R10: 88001f236890 R11: 0274 R12: [ 519.429956] R13: 000b R14: R15: 88001abff950 [ 519.430957] FS: 7f0c1609b740() GS:88001fc0() knlGS: [ 519.432256] CS: 0010 DS: ES: CR0: 80050033 [ 519.433030] CR2: 0038 CR3: 1b14b000 CR4: 06f0 [ 519.433868] Stack: [ 519.434204] 000c 88001abff9b0 88001b58fd08 8138a0c3 [ 519.435355] 00011f2b9450 880c 88001abff950 88001b1b1760 [ 519.436480] 88001f236848 88001abff900 88001f236840 88001b58fd98 [ 519.437609] Call Trace: [ 519.438007] [] aa_vec_unique+0x163/0x240 [ 519.438709] [] __aa_labelset_update_subtree+0x687/0x820 [ 519.439537] [] aa_replace_profiles+0x59b/0xb70 [ 519.440268] [] ? __kmalloc+0x22e/0x250 [ 519.440944] [] policy_update+0x9f/0x1f0 [ 519.441617] [] profile_replace+0x13/0x20 [ 519.442299] [] __vfs_write+0x18/0x40 [ 519.443032] [] vfs_write+0xa9/0x1a0 [ 519.443721] [] ? do_sys_open+0x1bf/0x2a0 [ 519.16] [] SyS_write+0x55/0xc0 [ 519.445042] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 [ 519.451336] RIP [] profile_cmp+0x2f/0x180 [ 519.452088] RSP [ 519.452570] CR2: 0038 [ 519.453032] ---[ end trace 65ff12ee2e7c26af ]--- The details of this test can be found at: https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer Will follow up with more details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+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 1579135] Re: kernel BUG on snap disconnect from within a snap
I'll keep running to see if I can reproduce it again. -- 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/1579135 Title: kernel BUG on snap disconnect from within a snap Status in apparmor package in Ubuntu: Incomplete Bug description: First, a bit of background: I've built a go binary of the upstream snappy integration tests, and built them into a snap so that we can easily keep them up to date, and call them from other test suites. I'm running through the tests in qemu on a current 16 image (built yesteray), and hitting this most of the time with the homeInterface Suite tests in particular. The networkInterfaceSuite tests also seem to produce a similar problem: sudo snap connect home-consumer:home ubuntu-core:home [/] Connect home-consumer:home to ubuntu-core:home home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable sudo snap disconnect home-consumer:home ubuntu-core:home [ 519.416354] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 519.417327] IP: [] profile_cmp+0x2f/0x180 [ 519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 [ 519.418574] Oops: [#1] SMP [ 519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 nls_iso8859_1 usb_storage ahci libahci squashfs [ 519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 4.4.0-21-generic #37-Ubuntu [ 519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 88001b58c000 [ 519.425385] RIP: 0010:[] [] profile_cmp+0x2f/0x180 [ 519.426242] RSP: 0018:88001b58fcb0 EFLAGS: 00010086 [ 519.426791] RAX: RBX: 88001b1b1400 RCX: 0006 [ 519.427628] RDX: RSI: RDI: 0009 [ 519.428405] RBP: 88001b58fcc0 R08: 000a R09: 0274 [ 519.429127] R10: 88001f236890 R11: 0274 R12: [ 519.429956] R13: 000b R14: R15: 88001abff950 [ 519.430957] FS: 7f0c1609b740() GS:88001fc0() knlGS: [ 519.432256] CS: 0010 DS: ES: CR0: 80050033 [ 519.433030] CR2: 0038 CR3: 1b14b000 CR4: 06f0 [ 519.433868] Stack: [ 519.434204] 000c 88001abff9b0 88001b58fd08 8138a0c3 [ 519.435355] 00011f2b9450 880c 88001abff950 88001b1b1760 [ 519.436480] 88001f236848 88001abff900 88001f236840 88001b58fd98 [ 519.437609] Call Trace: [ 519.438007] [] aa_vec_unique+0x163/0x240 [ 519.438709] [] __aa_labelset_update_subtree+0x687/0x820 [ 519.439537] [] aa_replace_profiles+0x59b/0xb70 [ 519.440268] [] ? __kmalloc+0x22e/0x250 [ 519.440944] [] policy_update+0x9f/0x1f0 [ 519.441617] [] profile_replace+0x13/0x20 [ 519.442299] [] __vfs_write+0x18/0x40 [ 519.443032] [] vfs_write+0xa9/0x1a0 [ 519.443721] [] ? do_sys_open+0x1bf/0x2a0 [ 519.16] [] SyS_write+0x55/0xc0 [ 519.445042] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 [ 519.451336] RIP [] profile_cmp+0x2f/0x180 [ 519.452088] RSP [ 519.452570] CR2: 0038 [ 519.453032] ---[ end trace 65ff12ee2e7c26af ]--- The details of this test can be found at: https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer Will follow up with more details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+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 1579135] Re: kernel BUG on snap disconnect from within a snap
Strange, I rebuilt the snap today, built a new amd64 snappy image, and ran through all the tests in kvm twice with no crash. Did something go in that could have fixed it? -- 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/1579135 Title: kernel BUG on snap disconnect from within a snap Status in apparmor package in Ubuntu: Incomplete Bug description: First, a bit of background: I've built a go binary of the upstream snappy integration tests, and built them into a snap so that we can easily keep them up to date, and call them from other test suites. I'm running through the tests in qemu on a current 16 image (built yesteray), and hitting this most of the time with the homeInterface Suite tests in particular. The networkInterfaceSuite tests also seem to produce a similar problem: sudo snap connect home-consumer:home ubuntu-core:home [/] Connect home-consumer:home to ubuntu-core:home home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable sudo snap disconnect home-consumer:home ubuntu-core:home [ 519.416354] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 519.417327] IP: [] profile_cmp+0x2f/0x180 [ 519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 [ 519.418574] Oops: [#1] SMP [ 519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 nls_iso8859_1 usb_storage ahci libahci squashfs [ 519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 4.4.0-21-generic #37-Ubuntu [ 519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 88001b58c000 [ 519.425385] RIP: 0010:[] [] profile_cmp+0x2f/0x180 [ 519.426242] RSP: 0018:88001b58fcb0 EFLAGS: 00010086 [ 519.426791] RAX: RBX: 88001b1b1400 RCX: 0006 [ 519.427628] RDX: RSI: RDI: 0009 [ 519.428405] RBP: 88001b58fcc0 R08: 000a R09: 0274 [ 519.429127] R10: 88001f236890 R11: 0274 R12: [ 519.429956] R13: 000b R14: R15: 88001abff950 [ 519.430957] FS: 7f0c1609b740() GS:88001fc0() knlGS: [ 519.432256] CS: 0010 DS: ES: CR0: 80050033 [ 519.433030] CR2: 0038 CR3: 1b14b000 CR4: 06f0 [ 519.433868] Stack: [ 519.434204] 000c 88001abff9b0 88001b58fd08 8138a0c3 [ 519.435355] 00011f2b9450 880c 88001abff950 88001b1b1760 [ 519.436480] 88001f236848 88001abff900 88001f236840 88001b58fd98 [ 519.437609] Call Trace: [ 519.438007] [] aa_vec_unique+0x163/0x240 [ 519.438709] [] __aa_labelset_update_subtree+0x687/0x820 [ 519.439537] [] aa_replace_profiles+0x59b/0xb70 [ 519.440268] [] ? __kmalloc+0x22e/0x250 [ 519.440944] [] policy_update+0x9f/0x1f0 [ 519.441617] [] profile_replace+0x13/0x20 [ 519.442299] [] __vfs_write+0x18/0x40 [ 519.443032] [] vfs_write+0xa9/0x1a0 [ 519.443721] [] ? do_sys_open+0x1bf/0x2a0 [ 519.16] [] SyS_write+0x55/0xc0 [ 519.445042] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 [ 519.451336] RIP [] profile_cmp+0x2f/0x180 [ 519.452088] RSP [ 519.452570] CR2: 0038 [ 519.453032] ---[ end trace 65ff12ee2e7c26af ]--- The details of this test can be found at: https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer Will follow up with more details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+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 1579135] Re: kernel BUG on snap disconnect from within a snap
@Jamie: simply building that snap and installing it, and even connecting/disconnecting the slots doesn't seem to reproduce the problem easily. The easiest way I can come up with for reproducing it is to use the snap that I'm using [attached]. To run into the problem I see, install this snap, and run: snappy-tests -check.f homeInterfaceSuite ** Attachment added: "snappy-tests_0.1_amd64.snap" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+attachment/4657519/+files/snappy-tests_0.1_amd64.snap -- 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/1579135 Title: kernel BUG on snap disconnect from within a snap Status in apparmor package in Ubuntu: New Bug description: First, a bit of background: I've built a go binary of the upstream snappy integration tests, and built them into a snap so that we can easily keep them up to date, and call them from other test suites. I'm running through the tests in qemu on a current 16 image (built yesteray), and hitting this most of the time with the homeInterface Suite tests in particular. The networkInterfaceSuite tests also seem to produce a similar problem: sudo snap connect home-consumer:home ubuntu-core:home [/] Connect home-consumer:home to ubuntu-core:home home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable sudo snap disconnect home-consumer:home ubuntu-core:home [ 519.416354] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 519.417327] IP: [] profile_cmp+0x2f/0x180 [ 519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 [ 519.418574] Oops: [#1] SMP [ 519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 nls_iso8859_1 usb_storage ahci libahci squashfs [ 519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 4.4.0-21-generic #37-Ubuntu [ 519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 88001b58c000 [ 519.425385] RIP: 0010:[] [] profile_cmp+0x2f/0x180 [ 519.426242] RSP: 0018:88001b58fcb0 EFLAGS: 00010086 [ 519.426791] RAX: RBX: 88001b1b1400 RCX: 0006 [ 519.427628] RDX: RSI: RDI: 0009 [ 519.428405] RBP: 88001b58fcc0 R08: 000a R09: 0274 [ 519.429127] R10: 88001f236890 R11: 0274 R12: [ 519.429956] R13: 000b R14: R15: 88001abff950 [ 519.430957] FS: 7f0c1609b740() GS:88001fc0() knlGS: [ 519.432256] CS: 0010 DS: ES: CR0: 80050033 [ 519.433030] CR2: 0038 CR3: 1b14b000 CR4: 06f0 [ 519.433868] Stack: [ 519.434204] 000c 88001abff9b0 88001b58fd08 8138a0c3 [ 519.435355] 00011f2b9450 880c 88001abff950 88001b1b1760 [ 519.436480] 88001f236848 88001abff900 88001f236840 88001b58fd98 [ 519.437609] Call Trace: [ 519.438007] [] aa_vec_unique+0x163/0x240 [ 519.438709] [] __aa_labelset_update_subtree+0x687/0x820 [ 519.439537] [] aa_replace_profiles+0x59b/0xb70 [ 519.440268] [] ? __kmalloc+0x22e/0x250 [ 519.440944] [] policy_update+0x9f/0x1f0 [ 519.441617] [] profile_replace+0x13/0x20 [ 519.442299] [] __vfs_write+0x18/0x40 [ 519.443032] [] vfs_write+0xa9/0x1a0 [ 519.443721] [] ? do_sys_open+0x1bf/0x2a0 [ 519.16] [] SyS_write+0x55/0xc0 [ 519.445042] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 [ 519.451336] RIP [] profile_cmp+0x2f/0x180 [ 519.452088] RSP [ 519.452570] CR2: 0038 [ 519.453032] ---[ end trace 65ff12ee2e7c26af ]--- The details of this test can be found at: https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer Will follow up with more details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+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 1579135] Re: kernel BUG on snap disconnect from within a snap
Linux localhost.localdomain 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -- 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/1579135 Title: kernel BUG on snap disconnect from within a snap Status in apparmor package in Ubuntu: New Bug description: First, a bit of background: I've built a go binary of the upstream snappy integration tests, and built them into a snap so that we can easily keep them up to date, and call them from other test suites. I'm running through the tests in qemu on a current 16 image (built yesteray), and hitting this most of the time with the homeInterface Suite tests in particular. The networkInterfaceSuite tests also seem to produce a similar problem: sudo snap connect home-consumer:home ubuntu-core:home [/] Connect home-consumer:home to ubuntu-core:home home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable sudo snap disconnect home-consumer:home ubuntu-core:home [ 519.416354] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 519.417327] IP: [] profile_cmp+0x2f/0x180 [ 519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 [ 519.418574] Oops: [#1] SMP [ 519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 nls_iso8859_1 usb_storage ahci libahci squashfs [ 519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 4.4.0-21-generic #37-Ubuntu [ 519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 88001b58c000 [ 519.425385] RIP: 0010:[] [] profile_cmp+0x2f/0x180 [ 519.426242] RSP: 0018:88001b58fcb0 EFLAGS: 00010086 [ 519.426791] RAX: RBX: 88001b1b1400 RCX: 0006 [ 519.427628] RDX: RSI: RDI: 0009 [ 519.428405] RBP: 88001b58fcc0 R08: 000a R09: 0274 [ 519.429127] R10: 88001f236890 R11: 0274 R12: [ 519.429956] R13: 000b R14: R15: 88001abff950 [ 519.430957] FS: 7f0c1609b740() GS:88001fc0() knlGS: [ 519.432256] CS: 0010 DS: ES: CR0: 80050033 [ 519.433030] CR2: 0038 CR3: 1b14b000 CR4: 06f0 [ 519.433868] Stack: [ 519.434204] 000c 88001abff9b0 88001b58fd08 8138a0c3 [ 519.435355] 00011f2b9450 880c 88001abff950 88001b1b1760 [ 519.436480] 88001f236848 88001abff900 88001f236840 88001b58fd98 [ 519.437609] Call Trace: [ 519.438007] [] aa_vec_unique+0x163/0x240 [ 519.438709] [] __aa_labelset_update_subtree+0x687/0x820 [ 519.439537] [] aa_replace_profiles+0x59b/0xb70 [ 519.440268] [] ? __kmalloc+0x22e/0x250 [ 519.440944] [] policy_update+0x9f/0x1f0 [ 519.441617] [] profile_replace+0x13/0x20 [ 519.442299] [] __vfs_write+0x18/0x40 [ 519.443032] [] vfs_write+0xa9/0x1a0 [ 519.443721] [] ? do_sys_open+0x1bf/0x2a0 [ 519.16] [] SyS_write+0x55/0xc0 [ 519.445042] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 [ 519.451336] RIP [] profile_cmp+0x2f/0x180 [ 519.452088] RSP [ 519.452570] CR2: 0038 [ 519.453032] ---[ end trace 65ff12ee2e7c26af ]--- The details of this test can be found at: https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer Will follow up with more details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+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 1579135] Re: kernel BUG on snap disconnect from within a snap
Tail end of syslog: May 6 16:03:58 localhost kernel: [ 595.676922] audit: type=1400 audit(1462550638.144:10477): apparmor="ALLOWED" operation="recvmsg" profile="snap.snappy-tests.snappy-tests//null-/usr/bin/sudo" pid=1908 comm="sudo" family="netlink" sock_type="raw" protocol=9 requested_mask="receive" denied_mask="receive" May 6 16:03:58 localhost kernel: [ 595.681696] audit: type=1400 audit(1462550638.148:10478): apparmor="ALLOWED" operation="create" profile="snap.snappy-tests.snappy-tests//null-/usr/bin/sudo" pid=1908 comm="sudo" family="netlink" sock_type="raw" protocol=9 requested_mask="create" denied_mask="create" May 6 16:03:58 localhost kernel: [ 595.686123] audit: type=1400 audit(1462550638.152:10479): apparmor="ALLOWED" operation="sendmsg" profile="snap.snappy-tests.snappy-tests//null-/usr/bin/sudo" pid=1908 comm="sudo" family="netlink" sock_type="raw" protocol=9 requested_mask="send" denied_mask="send" May 6 16:03:58 localhost kernel: [ 595.690588] audit: type=1400 audit(1462550638.156:10480): apparmor="ALLOWED" operation="recvmsg" profile="snap.snappy-tests.snappy-tests//null-/usr/bin/sudo" pid=1908 comm="sudo" family="netlink" sock_type="raw" protocol=9 requested_mask="receive" denied_mask="receive" May 6 16:03:58 localhost kernel: [ 595.695250] audit: type=1400 audit(1462550638.164:10481): apparmor="ALLOWED" operation="recvmsg" profile="snap.snappy-tests.snappy-tests//null-/usr/bin/sudo" pid=1908 comm="sudo" family="netlink" sock_type="raw" protocol=9 requested_mask="receive" denied_mask="receive" May 6 16:07:41 localhost /usr/lib/snapd/snapd[1578]: taskrunner.go:234: DEBUG: Running task 67 on Doing: Disconnect home-consumer:home from ubuntu-core:home May 6 16:07:41 localhost /usr/lib/snapd/snapd[1578]: task.go:250: DEBUG: 2016-05-06T16:07:41Z ERROR cannot disconnect plug "home" from snap "home-consumer" from slot "home" from snap "ubuntu-core", it is not connected May 6 16:09:15 localhost systemd[1]: Starting Cleanup of Temporary Directories... May 6 16:09:15 localhost systemd-tmpfiles[1919]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. May 6 16:09:15 localhost systemd[1]: Started Cleanup of Temporary Directories. -- 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/1579135 Title: kernel BUG on snap disconnect from within a snap Status in apparmor package in Ubuntu: New Bug description: First, a bit of background: I've built a go binary of the upstream snappy integration tests, and built them into a snap so that we can easily keep them up to date, and call them from other test suites. I'm running through the tests in qemu on a current 16 image (built yesteray), and hitting this most of the time with the homeInterface Suite tests in particular. The networkInterfaceSuite tests also seem to produce a similar problem: sudo snap connect home-consumer:home ubuntu-core:home [/] Connect home-consumer:home to ubuntu-core:home home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable sudo snap disconnect home-consumer:home ubuntu-core:home [ 519.416354] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 519.417327] IP: [] profile_cmp+0x2f/0x180 [ 519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 [ 519.418574] Oops: [#1] SMP [ 519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 nls_iso8859_1 usb_storage ahci libahci squashfs [ 519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 4.4.0-21-generic #37-Ubuntu [ 519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 88001b58c000 [ 519.425385] RIP: 0010:[] [] profile_cmp+0x2f/0x180 [ 519.426242] RSP: 0018:88001b58fcb0 EFLAGS: 00010086 [ 519.426791] RAX: RBX: 88001b1b1400 RCX: 0006 [ 519.427628] RDX: RSI: RDI: 0009 [ 519.428405] RBP: 88001b58fcc0 R08: 000a R09: 0274 [ 519.429127] R10: 88001f236890 R11: 0274 R12: [ 519.429956] R13: 000b R14: R15: 88001abff950 [ 519.430957] FS: 7f0c1609b740() GS:88001fc0() knlGS: [ 519.432256] CS: 0010 DS: ES: CR0: 80050033 [ 519.433030] CR2: 0038 CR3: 1b14b000 CR4: 06f0 [ 519.433868] Stack: [ 519.434204] 000c 88001abff9b0 88001b58fd08 8138a0c3 [ 519.435355] 00011f2b9450 880c
[Touch-packages] [Bug 1579135] [NEW] kernel BUG on snap disconnect from within a snap
Public bug reported: First, a bit of background: I've built a go binary of the upstream snappy integration tests, and built them into a snap so that we can easily keep them up to date, and call them from other test suites. I'm running through the tests in qemu on a current 16 image (built yesteray), and hitting this most of the time with the homeInterface Suite tests in particular. The networkInterfaceSuite tests also seem to produce a similar problem: sudo snap connect home-consumer:home ubuntu-core:home [/] Connect home-consumer:home to ubuntu-core:home home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable sudo snap disconnect home-consumer:home ubuntu-core:home [ 519.416354] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 519.417327] IP: [] profile_cmp+0x2f/0x180 [ 519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 [ 519.418574] Oops: [#1] SMP [ 519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 nls_iso8859_1 usb_storage ahci libahci squashfs [ 519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 4.4.0-21-generic #37-Ubuntu [ 519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 88001b58c000 [ 519.425385] RIP: 0010:[] [] profile_cmp+0x2f/0x180 [ 519.426242] RSP: 0018:88001b58fcb0 EFLAGS: 00010086 [ 519.426791] RAX: RBX: 88001b1b1400 RCX: 0006 [ 519.427628] RDX: RSI: RDI: 0009 [ 519.428405] RBP: 88001b58fcc0 R08: 000a R09: 0274 [ 519.429127] R10: 88001f236890 R11: 0274 R12: [ 519.429956] R13: 000b R14: R15: 88001abff950 [ 519.430957] FS: 7f0c1609b740() GS:88001fc0() knlGS: [ 519.432256] CS: 0010 DS: ES: CR0: 80050033 [ 519.433030] CR2: 0038 CR3: 1b14b000 CR4: 06f0 [ 519.433868] Stack: [ 519.434204] 000c 88001abff9b0 88001b58fd08 8138a0c3 [ 519.435355] 00011f2b9450 880c 88001abff950 88001b1b1760 [ 519.436480] 88001f236848 88001abff900 88001f236840 88001b58fd98 [ 519.437609] Call Trace: [ 519.438007] [] aa_vec_unique+0x163/0x240 [ 519.438709] [] __aa_labelset_update_subtree+0x687/0x820 [ 519.439537] [] aa_replace_profiles+0x59b/0xb70 [ 519.440268] [] ? __kmalloc+0x22e/0x250 [ 519.440944] [] policy_update+0x9f/0x1f0 [ 519.441617] [] profile_replace+0x13/0x20 [ 519.442299] [] __vfs_write+0x18/0x40 [ 519.443032] [] vfs_write+0xa9/0x1a0 [ 519.443721] [] ? do_sys_open+0x1bf/0x2a0 [ 519.16] [] SyS_write+0x55/0xc0 [ 519.445042] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 [ 519.451336] RIP [] profile_cmp+0x2f/0x180 [ 519.452088] RSP [ 519.452570] CR2: 0038 [ 519.453032] ---[ end trace 65ff12ee2e7c26af ]--- The details of this test can be found at: https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer Will follow up with more details ** Affects: apparmor (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/1579135 Title: kernel BUG on snap disconnect from within a snap Status in apparmor package in Ubuntu: New Bug description: First, a bit of background: I've built a go binary of the upstream snappy integration tests, and built them into a snap so that we can easily keep them up to date, and call them from other test suites. I'm running through the tests in qemu on a current 16 image (built yesteray), and hitting this most of the time with the homeInterface Suite tests in particular. The networkInterfaceSuite tests also seem to produce a similar problem: sudo snap connect home-consumer:home ubuntu-core:home [/] Connect home-consumer:home to ubuntu-core:home home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable sudo snap disconnect home-consumer:home ubuntu-core:home [ 519.416354] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 519.417327] IP: [] profile_cmp+0x2f/0x180 [ 519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 [ 519.418574] Oops: [#1] SMP [ 519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm snd_timer irqbypass
[Touch-packages] [Bug 1579135] Re: kernel BUG on snap disconnect from within a snap
** Attachment added: "/var/cache/apparmor" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+attachment/4657381/+files/var-cache-apparmor.tgz -- 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/1579135 Title: kernel BUG on snap disconnect from within a snap Status in apparmor package in Ubuntu: New Bug description: First, a bit of background: I've built a go binary of the upstream snappy integration tests, and built them into a snap so that we can easily keep them up to date, and call them from other test suites. I'm running through the tests in qemu on a current 16 image (built yesteray), and hitting this most of the time with the homeInterface Suite tests in particular. The networkInterfaceSuite tests also seem to produce a similar problem: sudo snap connect home-consumer:home ubuntu-core:home [/] Connect home-consumer:home to ubuntu-core:home home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable sudo snap disconnect home-consumer:home ubuntu-core:home [ 519.416354] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 519.417327] IP: [] profile_cmp+0x2f/0x180 [ 519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 [ 519.418574] Oops: [#1] SMP [ 519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 nls_iso8859_1 usb_storage ahci libahci squashfs [ 519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 4.4.0-21-generic #37-Ubuntu [ 519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 88001b58c000 [ 519.425385] RIP: 0010:[] [] profile_cmp+0x2f/0x180 [ 519.426242] RSP: 0018:88001b58fcb0 EFLAGS: 00010086 [ 519.426791] RAX: RBX: 88001b1b1400 RCX: 0006 [ 519.427628] RDX: RSI: RDI: 0009 [ 519.428405] RBP: 88001b58fcc0 R08: 000a R09: 0274 [ 519.429127] R10: 88001f236890 R11: 0274 R12: [ 519.429956] R13: 000b R14: R15: 88001abff950 [ 519.430957] FS: 7f0c1609b740() GS:88001fc0() knlGS: [ 519.432256] CS: 0010 DS: ES: CR0: 80050033 [ 519.433030] CR2: 0038 CR3: 1b14b000 CR4: 06f0 [ 519.433868] Stack: [ 519.434204] 000c 88001abff9b0 88001b58fd08 8138a0c3 [ 519.435355] 00011f2b9450 880c 88001abff950 88001b1b1760 [ 519.436480] 88001f236848 88001abff900 88001f236840 88001b58fd98 [ 519.437609] Call Trace: [ 519.438007] [] aa_vec_unique+0x163/0x240 [ 519.438709] [] __aa_labelset_update_subtree+0x687/0x820 [ 519.439537] [] aa_replace_profiles+0x59b/0xb70 [ 519.440268] [] ? __kmalloc+0x22e/0x250 [ 519.440944] [] policy_update+0x9f/0x1f0 [ 519.441617] [] profile_replace+0x13/0x20 [ 519.442299] [] __vfs_write+0x18/0x40 [ 519.443032] [] vfs_write+0xa9/0x1a0 [ 519.443721] [] ? do_sys_open+0x1bf/0x2a0 [ 519.16] [] SyS_write+0x55/0xc0 [ 519.445042] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 [ 519.451336] RIP [] profile_cmp+0x2f/0x180 [ 519.452088] RSP [ 519.452570] CR2: 0038 [ 519.453032] ---[ end trace 65ff12ee2e7c26af ]--- The details of this test can be found at: https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer Will follow up with more details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+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 1579135] Re: kernel BUG on snap disconnect from within a snap
** Attachment added: "/var/lib/snapd/apparmor/profiles" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+attachment/4657380/+files/profiles.tgz -- 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/1579135 Title: kernel BUG on snap disconnect from within a snap Status in apparmor package in Ubuntu: New Bug description: First, a bit of background: I've built a go binary of the upstream snappy integration tests, and built them into a snap so that we can easily keep them up to date, and call them from other test suites. I'm running through the tests in qemu on a current 16 image (built yesteray), and hitting this most of the time with the homeInterface Suite tests in particular. The networkInterfaceSuite tests also seem to produce a similar problem: sudo snap connect home-consumer:home ubuntu-core:home [/] Connect home-consumer:home to ubuntu-core:home home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable sudo snap disconnect home-consumer:home ubuntu-core:home [ 519.416354] BUG: unable to handle kernel NULL pointer dereference at 0038 [ 519.417327] IP: [] profile_cmp+0x2f/0x180 [ 519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 [ 519.418574] Oops: [#1] SMP [ 519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 nls_iso8859_1 usb_storage ahci libahci squashfs [ 519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 4.4.0-21-generic #37-Ubuntu [ 519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [ 519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 88001b58c000 [ 519.425385] RIP: 0010:[] [] profile_cmp+0x2f/0x180 [ 519.426242] RSP: 0018:88001b58fcb0 EFLAGS: 00010086 [ 519.426791] RAX: RBX: 88001b1b1400 RCX: 0006 [ 519.427628] RDX: RSI: RDI: 0009 [ 519.428405] RBP: 88001b58fcc0 R08: 000a R09: 0274 [ 519.429127] R10: 88001f236890 R11: 0274 R12: [ 519.429956] R13: 000b R14: R15: 88001abff950 [ 519.430957] FS: 7f0c1609b740() GS:88001fc0() knlGS: [ 519.432256] CS: 0010 DS: ES: CR0: 80050033 [ 519.433030] CR2: 0038 CR3: 1b14b000 CR4: 06f0 [ 519.433868] Stack: [ 519.434204] 000c 88001abff9b0 88001b58fd08 8138a0c3 [ 519.435355] 00011f2b9450 880c 88001abff950 88001b1b1760 [ 519.436480] 88001f236848 88001abff900 88001f236840 88001b58fd98 [ 519.437609] Call Trace: [ 519.438007] [] aa_vec_unique+0x163/0x240 [ 519.438709] [] __aa_labelset_update_subtree+0x687/0x820 [ 519.439537] [] aa_replace_profiles+0x59b/0xb70 [ 519.440268] [] ? __kmalloc+0x22e/0x250 [ 519.440944] [] policy_update+0x9f/0x1f0 [ 519.441617] [] profile_replace+0x13/0x20 [ 519.442299] [] __vfs_write+0x18/0x40 [ 519.443032] [] vfs_write+0xa9/0x1a0 [ 519.443721] [] ? do_sys_open+0x1bf/0x2a0 [ 519.16] [] SyS_write+0x55/0xc0 [ 519.445042] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 [ 519.451336] RIP [] profile_cmp+0x2f/0x180 [ 519.452088] RSP [ 519.452570] CR2: 0038 [ 519.453032] ---[ end trace 65ff12ee2e7c26af ]--- The details of this test can be found at: https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer Will follow up with more details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+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 1414992] Re: Generating /boot/initrd.img-touch = dpkg: warning: version 'touch' has bad syntax: version number does not start with digit
*** This bug is a duplicate of bug 1384450 *** https://bugs.launchpad.net/bugs/1384450 The new phablet-tools from the bug that this is duped to does not help. I tried reinstalling initramfs-tools after reinstalling my device with the new phablet-tools and I still get this: phablet@ubuntu-phablet:~$ sudo apt-get install --reinstall initramfs-tools Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 13 not upgraded. Need to get 44.7 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports/ vivid/main initramfs-tools all 0.103ubuntu9 [44.7 kB] Fetched 44.7 kB in 0s (61.2 kB/s) (Reading database ... 40373 files and directories currently installed.) Preparing to unpack .../initramfs-tools_0.103ubuntu9_all.deb ... Unpacking initramfs-tools (0.103ubuntu9) over (0.103ubuntu9) ... Setting up initramfs-tools (0.103ubuntu9) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools-ubuntu-touch (0.81) ... Processing triggers for initramfs-tools (0.103ubuntu9) ... update-initramfs: Generating /boot/initrd.img-touch dpkg: warning: version 'touch' has bad syntax: version number does not start with digit grep: /boot/config-touch: No such file or directory WARNING: missing /lib/modules/touch Device driver support needs thus be built-in linux image! depmod: FATAL: touch: not absolute path. depmod: ERROR: could not open directory /tmp/mkinitramfs_zyfajz/lib/modules/3.4.67: No such file or directory depmod: FATAL: could not search modules: No such file or directory E: No boot partition found ! run-parts: /etc/initramfs/post-update.d//zz-flash-touch-initrd exited with return code 1 dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1414992 Title: Generating /boot/initrd.img-touch = dpkg: warning: version 'touch' has bad syntax: version number does not start with digit Status in initramfs-tools-ubuntu-touch package in Ubuntu: New Bug description: Encountered when trying to test that a phone image upgraded with -proposed still boots. According to pitti: naming it initrd.img-touch is broken, that's not what initramfs-tools and other tools expect so at the very least, i-t-ubuntu-touch needs to disable the trigger somehow http://dev-jenkins.ubuntu-ci:8080/job/vila-bootesting/23/console is an example using adt-run --apt-upgrade to test libpng. The base phone image is ubuntu-touch/devel- proposed/krillin/version-87.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-touch/+bug/1414992/+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 1379381] Re: [Dash] shows splash screen with Scopes when starting up the phone
I saw what may be a variation of this on an update from 112 to 114 this morning. When I unlocked after the update/reboot, I did not see the scopes screen, but the home screen of unity8 instead - except there were no icons. After about 1-2 minutes, it flickered slightly and went dark, then went to the screen with just the word scopes described above, and eventually went back to unity but the icons were there this time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1379381 Title: [Dash] shows splash screen with Scopes when starting up the phone Status in Ubuntu UX bugs: Triaged Status in “unity8” package in Ubuntu: Confirmed Bug description: Ubuntu 14.10 r274 1. Start up the phone. 2. Immediately when the welcome screen appears, unlock it. What you see: A splash screen with the word Scopes. What you should see: The first thing you see on unlocking the phone should not be the word Scopes. Some of the ways this bug could be fixed: - rename the Dash app from Scopes to Ubuntu - use a different splash screen mode for the Dash - special-case the Dash so that it has no splash screen at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1379381/+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 1370644] Re: unity8-autopilot device unlock seems racy
Any ideas on this? We're seeing it on some of the MP testing jobs too it seems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1370644 Title: unity8-autopilot device unlock seems racy Status in “unity8” package in Ubuntu: New Bug description: In some test runs, we see unlocking fail with: I: Unlock failed, script output: 'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.UnityGreeter was not provided by any .service files It's not reliably reproducible, but probably happens at least once a day for us in CI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1370644/+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 1370644] [NEW] unity8-autopilot device unlock seems racy
Public bug reported: In some test runs, we see unlocking fail with: I: Unlock failed, script output: 'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.UnityGreeter was not provided by any .service files It's not reliably reproducible, but probably happens at least once a day for us in CI ** Affects: unity8 (Ubuntu) Importance: Undecided Assignee: Michael Terry (mterry) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1370644 Title: unity8-autopilot device unlock seems racy Status in “unity8” package in Ubuntu: New Bug description: In some test runs, we see unlocking fail with: I: Unlock failed, script output: 'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.UnityGreeter was not provided by any .service files It's not reliably reproducible, but probably happens at least once a day for us in CI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1370644/+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 1368874] [NEW] dbus 1.8.6-1ubuntu1 fails to upgrade on ppc64el vm
Public bug reported: Trying to do a dist-upgrade in utopicI'm getting: Errors were encountered while processing: dbus E: Sub-process /usr/bin/dpkg returned an error code (1) Details from term.log: Setting up dbus (1.8.6-1ubuntu1) ... insserv: warning: script 'S99autotest' missing LSB tags and overrides insserv: warning: script 'autotest' missing LSB tags and overrides insserv: There is a loop between service grub-common and urandom if started insserv: loop involving service urandom at depth 4 insserv: loop involving service hwclock at depth 3 insserv: There is a loop between service grub-common and udev if started insserv: loop involving service udev at depth 1 insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not be true! insserv: Starting autotest depends on grub-common and therefore on system facility `$all' which can not
[Touch-packages] [Bug 1360368] [NEW] upowerd health check failures
Public bug reported: We ran baselines of many processes on an idle nexus4 using health-check for the last trusty image, and some of those have regressed since then. These could be real regressions, or they could be something that's expected due to changes that happened since that image. We need someone to investigate these and report whether it requires a fix, or whether the thresholds need to be adjusted, and why. For upowerd, we see quite a lot more file IO and syncs than it did in trusty. Here are the results from the latest run at: Results from a recent test run can be seen at http://ci.ubuntu.com/smokeng/utopic/touch/mako/204:20140822:20140811.1/9853 /health-check/ process: upowerd PASSED: 0.09 = 0.086667: health-check.cpu-load.cpu-load-total.system-cpu-percent FAILED: 0.02 0.136667: health-check.cpu-load.cpu-load-total.total-cpu-percent PASSED: 0.06 = 0.05: health-check.cpu-load.cpu-load-total.user-cpu-percent FAILED: 0.01667 3.189998: health-check.file-access.file-access-total.access-count-total-rate FAILED: 0.01667 1.06: health-check.file-io-operations.file-io-operations-total.close-call-total-rate FAILED: 0.01667 1.06: health-check.file-io-operations.file-io-operations-total.open-call-total-rate FAILED: 0.01667 1.04: health-check.file-io-operations.file-io-operations-total.read-call-total-rate FAILED: 0.01667 0.026667: health-check.file-io-operations.file-io-operations-total.write-call-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.fdatasync-call-count-total-rate FAILED: 0.0 0.01: health-check.file-system-syncs.sync-system-calls-total.fsync-call-count-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.sync-call-count-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.syncfs-call-count-total-rate PASSED: 0.00278 = 0.0: health-check.heap-usage-via-brk.heap-usage-via-brk-total.brk-size-total-Kbytes-rate PASSED: 0.00278 = 0.0: health-check.memory-usage-via-mmap.memory-usage-via-mmap-total.mmap-total-Kbytes-rate PASSED: 256.0 = 0.0: health-check.network-connections.network-connections-total.receive-total-rate PASSED: 256.0 = 0.0: health-check.network-connections.network-connections-total.send-total-rate PASSED: 0.25 = 0.01: health-check.wakeup-events.wakeup-events-total.wakeup-total-rate ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: health-check ** Tags added: health-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1360368 Title: upowerd health check failures Status in “upower” package in Ubuntu: New Bug description: We ran baselines of many processes on an idle nexus4 using health- check for the last trusty image, and some of those have regressed since then. These could be real regressions, or they could be something that's expected due to changes that happened since that image. We need someone to investigate these and report whether it requires a fix, or whether the thresholds need to be adjusted, and why. For upowerd, we see quite a lot more file IO and syncs than it did in trusty. Here are the results from the latest run at: Results from a recent test run can be seen at http://ci.ubuntu.com/smokeng/utopic/touch/mako/204:20140822:20140811.1/9853 /health-check/ process: upowerd PASSED: 0.09 = 0.086667: health-check.cpu-load.cpu-load-total.system-cpu-percent FAILED: 0.02 0.136667: health-check.cpu-load.cpu-load-total.total-cpu-percent PASSED: 0.06 = 0.05: health-check.cpu-load.cpu-load-total.user-cpu-percent FAILED: 0.01667 3.189998: health-check.file-access.file-access-total.access-count-total-rate FAILED: 0.01667 1.06: health-check.file-io-operations.file-io-operations-total.close-call-total-rate FAILED: 0.01667 1.06: health-check.file-io-operations.file-io-operations-total.open-call-total-rate FAILED: 0.01667 1.04: health-check.file-io-operations.file-io-operations-total.read-call-total-rate FAILED: 0.01667 0.026667: health-check.file-io-operations.file-io-operations-total.write-call-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.fdatasync-call-count-total-rate FAILED: 0.0 0.01: health-check.file-system-syncs.sync-system-calls-total.fsync-call-count-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.sync-call-count-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.syncfs-call-count-total-rate PASSED: 0.00278 = 0.0: health-check.heap-usage-via-brk.heap-usage-via-brk-total.brk-size-total-Kbytes-rate PASSED: 0.00278 = 0.0: health-check.memory-usage-via-mmap.memory-usage-via-mmap-total.mmap-total-Kbytes-rate PASSED: 256.0 =
[Touch-packages] [Bug 1360373] [NEW] network manager health-check failures
Public bug reported: We ran baselines of many processes on an idle nexus4 using health-check for the last trusty image, and some of those have regressed since then. These could be real regressions, or they could be something that's expected due to changes that happened since that image. We need someone to investigate these and report whether it requires a fix, or whether the thresholds need to be adjusted, and why. Results from a recent test run can be seen at http://ci.ubuntu.com/smokeng/utopic/touch/mako/199:20140819:20140811.1/9777 /health-check/1555795/ For network manager, wee see wakeups are all over the place, sometimes way less than what we expect, sometimes almost double what we expect. So sometimes it passes, but sometimes we see quite a bit more wakeups causing it to fail. process: NetworkManager FAILED: 0.4 0.45: health-check.cpu-load.cpu-load-total.system-cpu-percent PASSED: 0.7 = 0.69: health-check.cpu-load.cpu-load-total.total-cpu-percent PASSED: 0.5 = 0.24: health-check.cpu-load.cpu-load-total.user-cpu-percent PASSED: 0.5 = 0.08: health-check.file-access.file-access-total.access-count-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.fdatasync-call-count-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.fsync-call-count-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.sync-call-count-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.syncfs-call-count-total-rate PASSED: 0.00278 = 0.0: health-check.heap-usage-via-brk.heap-usage-via-brk-total.brk-size-total-Kbytes-rate PASSED: 0.00278 = 0.0: health-check.memory-usage-via-mmap.memory-usage-via-mmap-total.mmap-total-Kbytes-rate PASSED: 1024.0 = 0.16: health-check.network-connections.network-connections-total.receive-total-rate PASSED: 1024.0 = 0.0: health-check.network-connections.network-connections-total.send-total-rate PASSED: 0.0 = 0.0: health-check.polling-system-calls.polling-system-calls-total.poll-count-infinite-total-rate PASSED: 0.0 = 0.0: health-check.polling-system-calls.polling-system-calls-total.poll-count-zero-total-rate FAILED: 1.0 1.973332: health-check.wakeup-events.wakeup-events-total.wakeup-total-rate ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: health-check ** Tags added: health-check -- 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/1360373 Title: network manager health-check failures Status in “network-manager” package in Ubuntu: New Bug description: We ran baselines of many processes on an idle nexus4 using health- check for the last trusty image, and some of those have regressed since then. These could be real regressions, or they could be something that's expected due to changes that happened since that image. We need someone to investigate these and report whether it requires a fix, or whether the thresholds need to be adjusted, and why. Results from a recent test run can be seen at http://ci.ubuntu.com/smokeng/utopic/touch/mako/199:20140819:20140811.1/9777 /health-check/1555795/ For network manager, wee see wakeups are all over the place, sometimes way less than what we expect, sometimes almost double what we expect. So sometimes it passes, but sometimes we see quite a bit more wakeups causing it to fail. process: NetworkManager FAILED: 0.4 0.45: health-check.cpu-load.cpu-load-total.system-cpu-percent PASSED: 0.7 = 0.69: health-check.cpu-load.cpu-load-total.total-cpu-percent PASSED: 0.5 = 0.24: health-check.cpu-load.cpu-load-total.user-cpu-percent PASSED: 0.5 = 0.08: health-check.file-access.file-access-total.access-count-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.fdatasync-call-count-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.fsync-call-count-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.sync-call-count-total-rate PASSED: 0.0 = 0.0: health-check.file-system-syncs.sync-system-calls-total.syncfs-call-count-total-rate PASSED: 0.00278 = 0.0: health-check.heap-usage-via-brk.heap-usage-via-brk-total.brk-size-total-Kbytes-rate PASSED: 0.00278 = 0.0: health-check.memory-usage-via-mmap.memory-usage-via-mmap-total.mmap-total-Kbytes-rate PASSED: 1024.0 = 0.16: health-check.network-connections.network-connections-total.receive-total-rate PASSED: 1024.0 = 0.0: health-check.network-connections.network-connections-total.send-total-rate PASSED: 0.0 = 0.0: health-check.polling-system-calls.polling-system-calls-total.poll-count-infinite-total-rate PASSED: 0.0 = 0.0: health-check.polling-system-calls.polling-system-calls-total.poll-count-zero-total-rate FAILED:
[Touch-packages] [Bug 1360376] [NEW] indicator-message-service health-check failures
Public bug reported: We ran baselines of many processes on an idle nexus4 using health-check for the last trusty image, and some of those have regressed since then. These could be real regressions, or they could be something that's expected due to changes that happened since that image. We need someone to investigate these and report whether it requires a fix, or whether the thresholds need to be adjusted, and why. Results from a recent test run can be seen at http://ci.ubuntu.com/smokeng/utopic/touch/mako/204:20140822:20140811.1/9853 /health-check/ For indicator message service, we're seeing the wakeup rate at .25 wakeups/sec, quite a bit higher than what was expected. Is this related perhaps to https://bugs.launchpad.net/ubuntu/+source/indicator- messages/+bug/1308130 ? ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: health-check ** Tags added: health-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1360376 Title: indicator-message-service health-check failures Status in “indicator-messages” package in Ubuntu: New Bug description: We ran baselines of many processes on an idle nexus4 using health- check for the last trusty image, and some of those have regressed since then. These could be real regressions, or they could be something that's expected due to changes that happened since that image. We need someone to investigate these and report whether it requires a fix, or whether the thresholds need to be adjusted, and why. Results from a recent test run can be seen at http://ci.ubuntu.com/smokeng/utopic/touch/mako/204:20140822:20140811.1/9853 /health-check/ For indicator message service, we're seeing the wakeup rate at .25 wakeups/sec, quite a bit higher than what was expected. Is this related perhaps to https://bugs.launchpad.net/ubuntu/+source /indicator-messages/+bug/1308130 ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1360376/+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 1360381] [NEW] maliit-server health-check failures
Public bug reported: We ran baselines of many processes on an idle nexus4 using health-check for the last trusty image, and some of those have regressed since then. These could be real regressions, or they could be something that's expected due to changes that happened since that image. We need someone to investigate these and report whether it requires a fix, or whether the thresholds need to be adjusted, and why. Results from a recent test run can be seen at http://ci.ubuntu.com/smokeng/utopic/touch/mako/204:20140822:20140811.1/9853 /health-check/ There were some pretty large changes in maliit-server - CPU went from ~.01 to ~2.0 for system and overall cpu usage! An otherwise idle process eating 2% of the cpu seems a little odd to me. It also looks like wakeups went up somewhat, which we need to either understand the reason for, or raise the threshold on them. ** Affects: maliit-framework (Ubuntu) Importance: Undecided Status: New ** Tags: health-check ** Tags added: health-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1360381 Title: maliit-server health-check failures Status in “maliit-framework” package in Ubuntu: New Bug description: We ran baselines of many processes on an idle nexus4 using health- check for the last trusty image, and some of those have regressed since then. These could be real regressions, or they could be something that's expected due to changes that happened since that image. We need someone to investigate these and report whether it requires a fix, or whether the thresholds need to be adjusted, and why. Results from a recent test run can be seen at http://ci.ubuntu.com/smokeng/utopic/touch/mako/204:20140822:20140811.1/9853 /health-check/ There were some pretty large changes in maliit-server - CPU went from ~.01 to ~2.0 for system and overall cpu usage! An otherwise idle process eating 2% of the cpu seems a little odd to me. It also looks like wakeups went up somewhat, which we need to either understand the reason for, or raise the threshold on them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1360381/+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 1340604] Re: [phone] crash files are only uploaded on boot
Changing the upstart job to have it start/stop with dbus does not work for me. It still thinks it's not online and I get messages like this in syslog: Jul 22 16:18:06 ubuntu-phablet whoopsie[850]: Not online; processing later (/var/crash/_usr_lib_arm-linux-gnueabihf_url-dispatcher_update-directory.32011.crash) If I instead have it start/stop with network-manager, I don't get the messages about it being offline. However it does seem like it gets stuck, or it's waiting on some lock in whoopsie still. I see the .upload file come up, but whoopsie doesn't seem to be doing anything. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1340604 Title: [phone] crash files are only uploaded on boot Status in “whoopsie” package in Ubuntu: New Bug description: On the phone (mako utopic #125) it seems that crash files are only uploaded on boot and not when the crash occurs. whoopsie is running but doesn't seem to detect that a crash file is ready for upload. = Test Case = 1. In a shell run: $ bash -c 'kill -SEGV $$' 2. Wait until the file _bin_bash.32011.uploaded is created - Check that after a moment whoopsie-upload-all is running - Check the progress of the upload in /var/log/upstart/apport-noui.log - Upon upload, check that /var/log/syslog contains a OOPS entry from whoopsie = Actual Result = whoopsie-upload-all times out and the crash file is not uploaded. If the device is rebooted, the crash is uploaded immediately. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: whoopsie 0.2.34 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.4-0ubuntu2 Architecture: armhf CrashReports: 640:32011:114:63916:2014-07-11 10:44:24.101108181 +0200:2014-07-11 10:44:07.613514715 +0200:/var/crash/_bin_bash.32011.crash 644:32011:114:0:2014-07-11 10:44:24.101108181 +0200:2014-07-11 10:44:24.101108181 +0200:/var/crash/_bin_bash.32011.upload Date: Fri Jul 11 10:45:02 2014 InstallationDate: Installed on 2014-07-11 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140711-020204) RelatedPackageVersions: apport-noui 2.14.4-0ubuntu2 SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1340604/+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 1340604] Re: [phone] crash files are only uploaded on boot
Looking at syslog on my phone after a fresh install, I'm seeing this: Jul 16 18:14:03 ubuntu-phablet whoopsie[2080]: whoopsie 0.2.34 starting up. Jul 16 18:14:03 ubuntu-phablet whoopsie[2080]: Using lock path: /var/lock/whoopsie/lock Jul 16 18:14:28 ubuntu-phablet whoopsie[2154]: Could not connect to the system bus: Timeout was reached Jul 16 18:14:29 ubuntu-phablet whoopsie[2154]: offline -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1340604 Title: [phone] crash files are only uploaded on boot Status in “whoopsie” package in Ubuntu: New Bug description: On the phone (mako utopic #125) it seems that crash files are only uploaded on boot and not when the crash occurs. whoopsie is running but doesn't seem to detect that a crash file is ready for upload. = Test Case = 1. In a shell run: $ bash -c 'kill -SEGV $$' 2. Wait until the file _bin_bash.32011.uploaded is created - Check that after a moment whoopsie-upload-all is running - Check the progress of the upload in /var/log/upstart/apport-noui.log - Upon upload, check that /var/log/syslog contains a OOPS entry from whoopsie = Actual Result = whoopsie-upload-all times out and the crash file is not uploaded. If the device is rebooted, the crash is uploaded immediately. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: whoopsie 0.2.34 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.4-0ubuntu2 Architecture: armhf CrashReports: 640:32011:114:63916:2014-07-11 10:44:24.101108181 +0200:2014-07-11 10:44:07.613514715 +0200:/var/crash/_bin_bash.32011.crash 644:32011:114:0:2014-07-11 10:44:24.101108181 +0200:2014-07-11 10:44:24.101108181 +0200:/var/crash/_bin_bash.32011.upload Date: Fri Jul 11 10:45:02 2014 InstallationDate: Installed on 2014-07-11 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140711-020204) RelatedPackageVersions: apport-noui 2.14.4-0ubuntu2 SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1340604/+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
