[Bug 2058277] Re: [SRU] 2.62
Hello Brian, I don't see a relation with snapd in the error, it seems to be unrelated. Is it possible to re-execute the tests please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058277 Title: [SRU] 2.62 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2058277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058277] Re: [SRU] 2.62
Also manual tests have been executed in noble using snapd from the ppa. I ran a smoke tests and everything was ok. Also the integration with the app center was tested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058277 Title: [SRU] 2.62 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2058277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058277] Re: [SRU] 2.62
About the results: Those tests failed: - google:ubuntu-24.04-64:tests/main/listing (this is because the execution was not done with SPREAD_CORE_CHANNEL=stable) - google:ubuntu-24.04-64:tests/main/snaps-state (this is a test for a testing tool) - google:ubuntu-24.04-64:tests/main/store-state (this is a test for a testing tool) - google:ubuntu-24.04-64:tests/main/download-private (known issue removing lxd) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058277 Title: [SRU] 2.62 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2058277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058277] Re: [SRU] 2.62
tests executed with ppa https://paste.ubuntu.com/p/XngqW6FsYt/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058277 Title: [SRU] 2.62 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2058277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039017] Re: [SRU] 2.61.3
Manually tested all the supported versions and ran tests. https://warthogs.atlassian.net/jira/core/projects/ST/board?selectedIssue=ST-1958 ** Tags removed: verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-focal verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039017 Title: [SRU] 2.61.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2039017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039017] Re: [SRU] 2.61.3
In mantic-proposed I see snapd 2.60.4+23.10.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039017 Title: [SRU] 2.61.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2039017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965808] Re: [SRU] 2.55.5
Verification completed Logs https://warthogs.atlassian.net/jira/core/projects/ST/board?selectedIssue=ST-1500 note: Some spread tests failed but all of them are known issues. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-impish verification-needed-jammy ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-impish verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965808 Title: [SRU] 2.55.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1965808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955137] Re: [SRU] 2.54
SRU validation completed again on focal Logs: https://warthogs.atlassian.net/jira/core/projects/ST/board?issueKey=ST-220 ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955137 Title: [SRU] 2.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1955137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955137] Re: [SRU] 2.54
Hi, these test failures are not issues in snapd, those are related to the tests, I'll work on adapting those tests to make then work for SRU validation. When we run tests for sru validation, reexec is disabled and the snapd deb package is not generated as usual, this is making some tests fail in this case. Thanks for the review. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-hirsute verification-needed-impish ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955137 Title: [SRU] 2.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1955137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955137] Re: [SRU] 2.54
Validation done. Details: https://warthogs.atlassian.net/jira/core/projects/ST/board?issueKey=ST-220 ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-hirsute verification-needed-impish ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955137 Title: [SRU] 2.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1955137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945242] Re: Failed to refresh to pi-kernel rev 343 on uc18
** Description changed: The refresh to a new kernel snap is failing in uc18 image. Something important to remark is that the DTB's for the new kernel were installed, but it still failed to complete the refresh to the new kernel Steps to reproduce I am using a rpi3 and I create an uc18 arm64 image using the following snaps $ snap list core18 2127 core20 1084 - pi 81 - pi-kernel 278 + pi 81 + pi-kernel 278 snapd 12967 Then, once the image is booted, I login and refresh snapd and pi gadget $ sudo snap refresh snapd --beta 2021-09-27T20:49:56Z INFO Waiting for automatic snapd restart... snapd (beta) 2.52 from Canonical✓ refreshed $ sudo snap refresh pi --stable pi (18-pi/stable) 18-1 from Canonical✓ refreshed Then I refresh pi-kernel snap $ sudo snap refresh pi-kernel --stable Make current revision for snap "pi-kernel" unavailable \ Broadcast message from root@localhost (Mon 2021-09-27 20:55:04 UTC): But it fails 7Error today at 20:54 UTC today at 20:56 UTC Refresh "pi-kernel" snap + sergio-j-cazzolato@localhost:~$ snap change 7 Status Spawn Ready Summary Donetoday at 20:54 UTC today at 20:56 UTC Ensure prerequisites for "pi-kernel" are available Undone today at 20:54 UTC today at 20:56 UTC Download snap "pi-kernel" (343) from channel "18-pi/stable" Donetoday at 20:54 UTC today at 20:56 UTC Fetch and check assertions for snap "pi-kernel" (343) Undone today at 20:54 UTC today at 20:56 UTC Mount snap "pi-kernel" (343) Undone today at 20:54 UTC today at 20:56 UTC Run pre-refresh hook of "pi-kernel" snap if present Undone today at 20:54 UTC today at 20:56 UTC Stop snap "pi-kernel" services Undone today at 20:54 UTC today at 20:56 UTC Remove aliases for snap "pi-kernel" Undone today at 20:54 UTC today at 20:56 UTC Make current revision for snap "pi-kernel" unavailable Donetoday at 20:54 UTC today at 20:56 UTC Update assets from kernel "pi-kernel" (343) Undone today at 20:54 UTC today at 20:56 UTC Copy snap "pi-kernel" data Undone today at 20:54 UTC today at 20:56 UTC Setup snap "pi-kernel" (343) security profiles Undone today at 20:54 UTC today at 20:56 UTC Make snap "pi-kernel" (343) available to the system Error today at 20:54 UTC today at 20:56 UTC Automatically connect eligible plugs and slots of snap "pi-kernel" Holdtoday at 20:54 UTC today at 20:56 UTC Set automatic aliases for snap "pi-kernel" Holdtoday at 20:54 UTC today at 20:56 UTC Setup snap "pi-kernel" aliases Holdtoday at 20:54 UTC today at 20:56 UTC Run post-refresh hook of "pi-kernel" snap if present Holdtoday at 20:54 UTC today at 20:56 UTC Start snap "pi-kernel" (343) services Holdtoday at 20:54 UTC today at 20:56 UTC Clean up "pi-kernel" (343) install Holdtoday at 20:54 UTC today at 20:56 UTC Run configure hook of "pi-kernel" snap if present Holdtoday at 20:54 UTC today at 20:56 UTC Run health check of "pi-kernel" snap Donetoday at 20:54 UTC today at 20:56 UTC Handling re-refresh of "pi-kernel" as needed .. Make snap "pi-kernel" (343) available to the system + + 2021-09-27T20:55:06Z INFO Requested system restart. + + .. + Automatically connect eligible plugs and slots of snap "pi-kernel" + + 2021-09-27T20:55:07Z INFO Waiting for automatic snapd restart... + 2021-09-27T20:55:07Z INFO Waiting for automatic snapd restart... + 2021-09-27T20:56:21Z ERROR cannot finish pi-kernel installation, there was a rollback across reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945242 Title: Failed to refresh to pi-kernel rev 343 on uc18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945242] [NEW] Failed to refresh to pi-kernel rev 343 on uc18
Public bug reported: The refresh to a new kernel snap is failing in uc18 image. Something important to remark is that the DTB's for the new kernel were installed, but it still failed to complete the refresh to the new kernel Steps to reproduce I am using a rpi3 and I create an uc18 arm64 image using the following snaps $ snap list core18 2127 core20 1084 pi 81 pi-kernel 278 snapd 12967 Then, once the image is booted, I login and refresh snapd and pi gadget $ sudo snap refresh snapd --beta 2021-09-27T20:49:56Z INFO Waiting for automatic snapd restart... snapd (beta) 2.52 from Canonical✓ refreshed $ sudo snap refresh pi --stable pi (18-pi/stable) 18-1 from Canonical✓ refreshed Then I refresh pi-kernel snap $ sudo snap refresh pi-kernel --stable Make current revision for snap "pi-kernel" unavailable \ Broadcast message from root@localhost (Mon 2021-09-27 20:55:04 UTC): But it fails 7Error today at 20:54 UTC today at 20:56 UTC Refresh "pi-kernel" snap sergio-j-cazzolato@localhost:~$ snap change 7 Status Spawn Ready Summary Donetoday at 20:54 UTC today at 20:56 UTC Ensure prerequisites for "pi-kernel" are available Undone today at 20:54 UTC today at 20:56 UTC Download snap "pi-kernel" (343) from channel "18-pi/stable" Donetoday at 20:54 UTC today at 20:56 UTC Fetch and check assertions for snap "pi-kernel" (343) Undone today at 20:54 UTC today at 20:56 UTC Mount snap "pi-kernel" (343) Undone today at 20:54 UTC today at 20:56 UTC Run pre-refresh hook of "pi-kernel" snap if present Undone today at 20:54 UTC today at 20:56 UTC Stop snap "pi-kernel" services Undone today at 20:54 UTC today at 20:56 UTC Remove aliases for snap "pi-kernel" Undone today at 20:54 UTC today at 20:56 UTC Make current revision for snap "pi-kernel" unavailable Donetoday at 20:54 UTC today at 20:56 UTC Update assets from kernel "pi-kernel" (343) Undone today at 20:54 UTC today at 20:56 UTC Copy snap "pi-kernel" data Undone today at 20:54 UTC today at 20:56 UTC Setup snap "pi-kernel" (343) security profiles Undone today at 20:54 UTC today at 20:56 UTC Make snap "pi-kernel" (343) available to the system Error today at 20:54 UTC today at 20:56 UTC Automatically connect eligible plugs and slots of snap "pi-kernel" Holdtoday at 20:54 UTC today at 20:56 UTC Set automatic aliases for snap "pi-kernel" Holdtoday at 20:54 UTC today at 20:56 UTC Setup snap "pi-kernel" aliases Holdtoday at 20:54 UTC today at 20:56 UTC Run post-refresh hook of "pi-kernel" snap if present Holdtoday at 20:54 UTC today at 20:56 UTC Start snap "pi-kernel" (343) services Holdtoday at 20:54 UTC today at 20:56 UTC Clean up "pi-kernel" (343) install Holdtoday at 20:54 UTC today at 20:56 UTC Run configure hook of "pi-kernel" snap if present Holdtoday at 20:54 UTC today at 20:56 UTC Run health check of "pi-kernel" snap Donetoday at 20:54 UTC today at 20:56 UTC Handling re-refresh of "pi-kernel" as needed .. Make snap "pi-kernel" (343) available to the system ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: The refresh to a new kernel snap is failing in uc18 image. Something important to remark is that the DTB's for the new kernel were installed, but it still failed to complete the refresh to the new kernel Steps to reproduce I am using a rpi3 and I create an uc18 arm64 image using the following snaps $ snap list - Name VersionRevTracking Publisher Notes - core18 20210722 2127 latest/stable canonical✓ base - core20 20210702 1084 latest/stable canonical✓ base - pi 18-1 81 18-pi/stable canonical✓ gadget - pi-kernel 5.3.0-1040.42 27818-pi/stable canonical✓ kernel - snapd 2.52 13269 latest/betacanonical✓ snapd + core18 2127 + core20 1084 + pi 81 + pi-kernel 278 + snapd 12967 Then, once the image is booted, I login and refresh snapd and pi gadget $ sudo snap refresh snapd --beta 2021-09-27T20:49:56Z INFO Waiting for automatic snapd restart... snapd (beta) 2.52 from Canonical✓ refreshed $ sudo snap refresh pi --stable pi (18-pi/stable) 18-1 from Canonical✓ refreshed Then I refresh pi-kernel snap $ sudo snap refresh pi-kernel --stable Make current revision for snap "pi-kernel" unavailable \ Broadcast message from root@localhost (Mon 2021-09-27 20:55:04 UTC): But it fails 7Error today at
[Bug 1929842] Re: [SRU] 2.51
Manual review done, also automated snapd tests are passing on focal: https://pastebin.ubuntu.com/p/pcsMhc7VMK/ ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929842 Title: [SRU] 2.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1929842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929842] Re: [SRU] 2.51
Tests completed, logs at https://trello.com/c/sZbWsZqd/-snapd-2511 ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy verification-needed-hirsute ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-groovy verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929842 Title: [SRU] 2.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1929842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915248] Re: [SRU] 2.49
Verification completed. Tests results in https://trello.com/c/JofXO22m/1006-snapd-2492 ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915248 Title: [SRU] 2.49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1915248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904098] Re: [SRU] 2.48
The SRU validation is completed and approved. Test results: https://trello.com/c/6NyUmAhC/753-snapd-248 ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904098 Title: [SRU] 2.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1904098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904098] Re: [SRU] 2.48
** Tags removed: verification-needed-bionic verification-needed-groovy verification-needed-xenial ** Tags added: verification-done-bionic verification-done-groovy verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904098 Title: [SRU] 2.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1904098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895929] Re: [SRU] 2.47
** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895929 Title: [SRU] 2.47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1895929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891134] Re: [SRU] 2.46
Validation complete. See logs here: https://trello.com/c/abepiTWD/605-snapd-2461 Still missing the autopakgtests results, currently are blocked. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891134 Title: [SRU] 2.46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1891134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875071] Re: [SRU] 2.45
The validation is completed. Test results: https://trello.com/c/mqJ4IZqE/482-snapd-2451 ** Tags removed: verification-needed verification-needed-bionic verification-needed-eoan verification-needed-focal verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-eoan verification-done-focal verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875071 Title: [SRU] 2.45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1875071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872803] Re: VM reboots using qemu and kvm with ovmf
# To be clear with "starts rebooting" do you mean the host or the guest that reboots? The gust reboot, and I can see in the journal log of the host machine that error line -> kvm [62484]: vcpu0, guest rIP # Did you also see the same issue without OVMF/TPM enabled in the cmdline or is that a hard dependency to trigger the bug? TPM is independent, I tested with and without tpm and the reboots happen. If I run without ovmf I can't reproduce the issue, the reboots don't happen. # In a similar fashion to help reproducing for others, doe this also happen to your setup outside of GCE or is it only happening there? I also tested in DigitalOcean and I see the reboots like in gce. # Please feel free to add anything else that comes to your mind that could help recreating the issue. I use this script to reproduce the issue: https://paste.ubuntu.com/p/DnVM4fCvnB/ # In general I think eventually you might add as much extra information to this bug and then open it up to qemu-upstream (add a Qemu task to the bug here will mirror it to the mailing list). That increases the chance of others that are running on GCE to see this and chime in if it is any sort of known issue. Some important info I remember is that it can be reproduce in ubuntu focal and seems to be happening when we try to virtualize over a VM like either in GCE or DigitalOcean I'll review my logs to see which extra information I could add. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872803 Title: VM reboots using qemu and kvm with ovmf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1872803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872803] [NEW] VM reboots using qemu and kvm with ovmf
Public bug reported: I am running a vm on google cloud engine (gce) I a trying to run some nested tests for ubuntu core 20 using ovmf and tpm. The proble we have with this is that when using kvm we see random reboots on the vm during first boot. If I set more than 1 cpu like in the following example I see the random reboots much more often. How we run the vm: /usr/bin/qemu-system-x86_64 -smp 2 -m 4096 -machine ubuntu-q35,accel=kvm -global ICH9-LPC.disable_s3=1 -nographic -net nic,model=virtio -net user,hostfwd=tcp::8022-:22 -drive file=/usr/share/OVMF/OVMF_CODE.secboot.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/tmp/work-dir/image/OVMF_VARS.snakeoil.fd,if=pflash,format=raw,unit=1 -chardev socket,id=chrtpm,path=/var/snap/swtpm-mvo/current/swtpm-sock -tpmdev emulator,id=tpm0,chardev=chrtpm -device tpm-tis,tpmdev=tpm0 -drive file=/tmp/work-dir/image/ubuntu-core-new.img,cache=none,format=raw,id=disk1,if=none -device virtio-blk-pci,drive=disk1,bootindex=1 -monitor tcp:127.0.0.1:,server,nowait -usb When using only 1 cpu (-smp 1) there are less reboots bet then when running test if the cpu of qemu arrives to 100% then the machine also starts rebooting Error I see in logs: Every time the machine is rebooted I see this line in the journal logs: Apr 14 18:35:57 apr141722-614284 kernel: kvm [62484]: vcpu0, guest rIP: 0xbc4788b4 disabled perfctr wrmsr: 0xc2 data 0x The reboots are not happening when kvm is not used. Thanks ** Affects: kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872803 Title: VM reboots using qemu and kvm with ovmf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1872803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869435] Re: Performance regression on ubuntu focal
Please see thiese results: Bionic results: https://paste.ubuntu.com/p/GDfnwMMTF2/ Focal results: https://paste.ubuntu.com/p/fFzDBrtNkW/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869435 Title: Performance regression on ubuntu focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869661] Re: lxc 3.23 (?) breaks nested lxd with snaps
Hello, I still see: + lxd.lxc exec my-nesting-ubuntu -- lxd.lxc exec my-inner-ubuntu -- echo from-the-INSIDE-inside Error: EOF when using lxd from edge: google:ubuntu-18.04-64 .../tests/main/lxd# snap list lxd Name Version RevTracking Publisher Notes lxd git-350df50 14114 latest/edge canonical✓ - Is there any other thing to try? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869661 Title: lxc 3.23 (?) breaks nested lxd with snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1869661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869435] Re: Performance regression on ubuntu focal
Hi, In our tests logs we see that focal is slower than other systems like bionic. I printed all the commands we run with the times and noticed the main diff on times is when running different systemd commands. So I did a very small script to compare basic calls that we use in our snapd test suite. Now I did a new comparison between focal and bionic but changed the paramenters compared with the previous logs, now I am using the calls we see in our tests which are slower on focal compared with bionic. script used: https://paste.ubuntu.com/p/JG977dRXMy/ results bionic: https://paste.ubuntu.com/p/GDfnwMMTF2/ results focal: https://paste.ubuntu.com/p/GDfnwMMTF2/ All the results are in milliseconds. With these logs I think is more clear the performance difference between both, i.e. "systemctl list- unit-files --full" taks almost the double on bionic than focal. Does it make sense? Do you need more info? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869435 Title: Performance regression on ubuntu focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869435] [NEW] Performance regression on ubuntu focal
Public bug reported: Hello, I noticed that systmed is performin some tasks much faster in bionic than in focal, I created a script which iterates doing some operations and executed that on bionic and focal: https://paste.ubuntu.com/p/zWWQjndtXx/ I see for example how systemctl daemon reload takes more time in focal even where there are less units than in bionic results: bionic: https://paste.ubuntu.com/p/z32WScydNk/ eoan: https://paste.ubuntu.com/p/V98vd5CHwq/ focal: https://paste.ubuntu.com/p/brNjKvC2gF/ The tests was done in gce using clean instances type n1-standard-2. Please tell me if you need any extra info ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869435 Title: Performance regression on ubuntu focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846181] Re: [SRU] 2.42.1
** Tags removed: verification-needed-eoan verification-needed-xenial ** Tags added: verification-done-eoan verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846181 Title: [SRU] 2.42.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1846181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840375] Re: groupdel doesn't support extrausers
I ran the validation in eoan and I get segmentation fault when deleting the group. This is the log: https://paste.ubuntu.com/p/KpPZDcGc3w/ The group is deleted but the seg fault message is shown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840375 Title: groupdel doesn't support extrausers To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1840375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857022] Re: gtk3-nocsd preloads a setuid library
** Changed in: snapd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857022 Title: gtk3-nocsd preloads a setuid library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk3-nocsd/+bug/1857022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853730] Re: package snapd (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1
Hello, thanks for reporting this. Could you please include the version of snapd which is being installed and failed? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853730 Title: package snapd (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1853730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852544] Re: uc20 grubenv block seems odd
** Changed in: snapd (Ubuntu) Importance: Undecided => Critical ** Changed in: snapd (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852544 Title: uc20 grubenv block seems odd To manage notifications about this bug go to: https://bugs.launchpad.net/snap-pc/+bug/1852544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846181] Re: [SRU] 2.42.1
The validation has been completed for bionic and disco. Tests described on description have been executed and passed. Tests resutls here: https://trello.com/c/MyxWGYAE/23-snapd-16-2421 ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846181 Title: [SRU] 2.42.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1846181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852635] Re: mount-ns test failing with latest bionic updates
** Attachment added: "bionic-diff-unified.txt" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1852635/+attachment/5306655/+files/bionic-diff-unified.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852635 Title: mount-ns test failing with latest bionic updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1852635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852635] Re: mount-ns test failing with latest bionic updates
** Attachment added: "bionic-diff2.txt" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1852635/+attachment/5306654/+files/bionic-diff2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852635 Title: mount-ns test failing with latest bionic updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1852635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846181] Re: [SRU] 2.42.1
SRU validated, see logs here: https://trello.com/c/MyxWGYAE/23-snapd-16-2421 ** Tags removed: verification-needed verification-needed-bionic verification-needed-disco ** Tags added: verification-done verification-done-bionic verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846181 Title: [SRU] 2.42.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1846181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852635] [NEW] mount-ns test failing with latest bionic updates
Public bug reported: After the last refresh for bionic on gce the mount-ns test is failing with the error shown bellow. Also are attached the diff for the bionic previous to the update and after the update. Some usefull data: --- image for spread.yaml: test-bionic-1 --- error link: https://travis-ci.org/snapcore/spread-cron/builds/610169331#L2487 --- error description: 2019-11-11 05:36:06 Error executing google:ubuntu-18.04-64:tests/main/mount-ns:inherit : - + '[' -e please-skip-this-test ']' + diff -u google.ubuntu-18.04-64/HOST.expected.txt HOST.deterministic.txt --- google.ubuntu-18.04-64/HOST.expected.txt2019-11-11 05:16:17.0 + +++ HOST.deterministic.txt 2019-11-11 05:36:03.058621429 + @@ -1,4 +1,4 @@ -0:0 / / rw,relatime shared:1 - ext4 /dev/sda1 rw,data=ordered +0:0 / / rw,relatime shared:1 - ext4 /dev/sda1 rw 0:1 / /boot/efi rw,relatime shared:2 - vfat /dev/sda15 rw,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 1:0 / /dev rw,nosuid,relatime shared:3 - devtmpfs udev rw,size=VARIABLE,nr_inodes=0,mode=755 1:1 / /dev/hugepages rw,relatime shared:4 - hugetlbfs hugetlbfs rw,pagesize=2M @@ -7,34 +7,33 @@ 1:4 / /dev/shm rw,nosuid,nodev shared:7 - tmpfs tmpfs rw 1:5 / /proc rw,nosuid,nodev,noexec,relatime shared:8 - proc proc rw 1:6 / /proc/fs/nfsd rw,relatime shared:9 - nfsd nfsd rw -1:7 / /proc/sys/fs/binfmt_misc rw,relatime shared:10 - binfmt_misc binfmt_misc rw -1:8 / /proc/sys/fs/binfmt_misc rw,relatime shared:11 - autofs systemd-1 rw,fd=0,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=0 -1:9 / /run rw,nosuid,noexec,relatime shared:12 - tmpfs tmpfs rw,size=VARIABLE,mode=755 -1:10 / /run/lock rw,nosuid,nodev,noexec,relatime shared:13 - tmpfs tmpfs rw,size=VARIABLE -1:11 / /run/rpc_pipefs rw,relatime shared:14 - rpc_pipefs sunrpc rw -1:12 / /run/user/0 rw,nosuid,nodev,relatime shared:15 - tmpfs tmpfs rw,size=VARIABLE,mode=700 -2:0 / /snap/core/1 ro,nodev,relatime shared:16 - squashfs /dev/loop0 ro -2:1 / /snap/core18/1 ro,nodev,relatime shared:17 - squashfs /dev/loop1 ro -2:2 / /snap/test-snapd-mountinfo-classic/1 ro,nodev,relatime shared:18 - squashfs /dev/loop2 ro -2:3 / /snap/test-snapd-mountinfo-core16/1 ro,nodev,relatime shared:19 - squashfs /dev/loop3 ro -2:4 / /snap/test-snapd-mountinfo-core18/1 ro,nodev,relatime shared:20 - squashfs /dev/loop4 ro -1:13 / /sys rw,nosuid,nodev,noexec,relatime shared:21 - sysfs sysfs rw -1:14 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:22 - tmpfs tmpfs ro,mode=755 -1:15 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:23 - cgroup cgroup rw,blkio -1:16 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime shared:24 - cgroup cgroup rw,cpu,cpuacct -1:17 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:25 - cgroup cgroup rw,cpuset -1:18 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:26 - cgroup cgroup rw,devices -1:19 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:27 - cgroup cgroup rw,freezer -1:20 / /sys/fs/cgroup/hugetlb rw,nosuid,nodev,noexec,relatime shared:28 - cgroup cgroup rw,hugetlb -1:21 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:29 - cgroup cgroup rw,memory -1:22 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime shared:30 - cgroup cgroup rw,net_cls,net_prio -1:23 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime shared:31 - cgroup cgroup rw,perf_event -1:24 / /sys/fs/cgroup/pids rw,nosuid,nodev,noexec,relatime shared:32 - cgroup cgroup rw,pids -1:25 / /sys/fs/cgroup/rdma rw,nosuid,nodev,noexec,relatime shared:33 - cgroup cgroup rw,rdma -1:26 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:34 - cgroup cgroup rw,xattr,name=systemd -1:27 / /sys/fs/cgroup/unified rw,nosuid,nodev,noexec,relatime shared:35 - cgroup2 cgroup rw,nsdelegate -1:28 / /sys/fs/fuse/connections rw,relatime shared:36 - fusectl fusectl rw -1:29 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:37 - pstore pstore rw -1:30 / /sys/kernel/config rw,relatime shared:38 - configfs configfs rw -1:31 / /sys/kernel/debug rw,relatime shared:39 - debugfs debugfs rw -1:32 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:40 - securityfs securityfs rw +1:7 / /proc/sys/fs/binfmt_misc rw,nosuid,nodev,noexec,relatime shared:10 - binfmt_misc binfmt_misc rw +1:8 / /run rw,nosuid,noexec,relatime shared:11 - tmpfs tmpfs rw,size=VARIABLE,mode=755 +1:9 / /run/lock rw,nosuid,nodev,noexec,relatime shared:12 - tmpfs tmpfs rw,size=VARIABLE +1:10 / /run/rpc_pipefs rw,relatime shared:13 - rpc_pipefs sunrpc rw +1:11 / /run/user/0 rw,nosuid,nodev,relatime shared:14 - tmpfs tmpfs rw,size=VARIABLE,mode=700 +2:0 / /snap/core/1 ro,nodev,relatime shared:15 - squashfs /dev/loop0 ro +2:1 / /snap/core18/1 ro,nodev,relatime shared:16 - squashfs /dev/loop1 ro +2:2 / /snap/test-snapd-mountinfo-classic/1 ro,nodev,relatime shared:17 - squashfs /dev/loop2 ro +2:3 /
[Bug 1810027] Re: Snaps won't start - stack smashing detected
** Changed in: snapd Importance: Undecided => Medium ** Changed in: snapd (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810027 Title: Snaps won't start - stack smashing detected To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1810027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836327] Re: [SRU] 2.40
Verification done, results here: https://docs.google.com/document/d/1iIXxOUMg-Dwvkzf01ZtaSL8ZxGp3_LJgzumBSUuuX5Y/edit?usp=sharing ** Tags removed: verification-needed verification-needed-bionic verification-needed-disco verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-disco verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836327 Title: [SRU] 2.40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1836327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827495] Re: [SRU] 2.39
Hello, the validation has been completed with no issues. The test document: https://docs.google.com/document/d/1PH650GbvVytncghI1yhTJK-TItliMm59lY_mq43q2E0/edit?usp=sharing ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-disco verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827495 Title: [SRU] 2.39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1827495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831490] Re: kernel is out of memory and killed during a kernel sys_write operation
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1831490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831490] Re: kernel is out of memory and killed during a kernel sys_write operation
apport information ** Tags added: apport-collected uec-images ** Description changed: This error is being reproduced on i386 arch when using the pc-kernel snap from beta or candidate. > sudo snap install test-snapd-tools > dmesg [15131.806107] audit: type=1400 audit(1559585825.240:93): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser" [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to increase size. [15131.871614] vmalloc: allocation failure: 68481 bytes [15131.871616] apparmor_parser: page allocation failure: order:0, mode:0x24000c2 [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 4.4.0-150-generic #176-Ubuntu [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [15131.871622] c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 0001 cfee9e30 [15131.871625] c11821b6 c1a1b220 f40ba700 024000c2 cfee9e44 c1a1ce6c cfee9e18 [15131.871629] 5ed07e43 00010b81 cfee9e60 c11ba86f 024000c2 c1a1ce6c [15131.871632] Call Trace: [15131.871637] [] dump_stack+0x58/0x79 [15131.871640] [] warn_alloc_failed+0xd6/0x110 [15131.871643] [] __vmalloc_node_range+0x1ef/0x210 [15131.871645] [] __vmalloc_node+0x66/0x70 [15131.871648] [] ? __aa_kvmalloc+0x28/0x60 [15131.871650] [] vmalloc+0x38/0x40 [15131.871652] [] ? __aa_kvmalloc+0x28/0x60 [15131.871654] [] __aa_kvmalloc+0x28/0x60 [15131.871656] [] aa_simple_write_to_buffer+0x34/0x90 [15131.871658] [] policy_update+0x73/0x230 [15131.871660] [] ? security_file_permission+0x3e/0xd0 [15131.871662] [] profile_replace+0x98/0xe0 [15131.871664] [] ? policy_update+0x230/0x230 [15131.871666] [] __vfs_write+0x22/0x50 [15131.871668] [] vfs_write+0x8c/0x1b0 [15131.871669] [] SyS_write+0x51/0xb0 [15131.871672] [] do_fast_syscall_32+0x9f/0x190 [15131.871675] [] sysenter_past_esp+0x3d/0x61 [15131.871676] Mem-Info: [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0 active_file:84472 inactive_file:25195 isolated_file:0 unevictable:0 dirty:34 writeback:0 unstable:0 slab_reclaimable:7222 slab_unreclaimable:14030 mapped:8431 shmem:5785 pagetables:204 bounce:0 free:289381 free_pcp:659 free_cma:0 [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871686] lowmem_reserve[]: 0 834 1942 1942 [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB active_anon:30164kB inactive_anon:2776kB active_file:158404kB inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871693] lowmem_reserve[]: 0 0 8863 8863 [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB active_anon:36408kB inactive_anon:5496kB active_file:176764kB inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871699] lowmem_reserve[]: 0 0 0 0 [15131.871701] DMA: 12*4kB (UME) 10*8kB (UME) 7*16kB (ME) 5*32kB (UM) 2*64kB (U) 3*128kB (UM) 3*256kB (UM) 4*512kB (UME) 3*1024kB (ME) 1*2048kB (M) 0*4096kB = 8848kB [15131.871711] Normal: 87*4kB (UME) 106*8kB (UME) 168*16kB (UME) 195*32kB (UME) 135*64kB (UME) 161*128kB (ME) 120*256kB (ME) 61*512kB (UME) 25*1024kB (ME) 6*2048kB (M) 55*4096kB (M) = 364492kB [15131.871720] HighMem: 131*4kB (UM) 835*8kB (UM) 302*16kB (UM) 119*32kB (UM) 95*64kB (UM) 50*128kB (UM) 67*256kB (UM) 55*512kB (UM) 52*1024kB (M) 23*2048kB (UM) 149*4096kB (M) = 784292kB [15131.871729] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB [15131.871730] 115450 total pagecache pages [15131.871731] 0 pages in swap cache [15131.871733] Swap cache stats: add 0, delete 0, find 0/0 [15131.871734] Free swap = 0kB
[Bug 1831490] Re: kernel is out of memory and killed during a kernel sys_write operation
As the error is happening in ubuntu core 16 on i386, I couldn't install the apport snap due to is is not available for this arch (just for amd64). So I installed classic and generated the report from there, but I am not sure this information is the one you want. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1831490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831490] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1831490/+attachment/5268850/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1831490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831490] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1831490/+attachment/5268848/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1831490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831490] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1831490/+attachment/5268849/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1831490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831490] [NEW] kernel is out of memory and killed during a kernel sys_write operation
Public bug reported: This error is being reproduced on i386 arch when using the pc-kernel snap from beta or candidate. > sudo snap install test-snapd-tools > dmesg [15131.806107] audit: type=1400 audit(1559585825.240:93): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser" [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to increase size. [15131.871614] vmalloc: allocation failure: 68481 bytes [15131.871616] apparmor_parser: page allocation failure: order:0, mode:0x24000c2 [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 4.4.0-150-generic #176-Ubuntu [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [15131.871622] c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 0001 cfee9e30 [15131.871625] c11821b6 c1a1b220 f40ba700 024000c2 cfee9e44 c1a1ce6c cfee9e18 [15131.871629] 5ed07e43 00010b81 cfee9e60 c11ba86f 024000c2 c1a1ce6c [15131.871632] Call Trace: [15131.871637] [] dump_stack+0x58/0x79 [15131.871640] [] warn_alloc_failed+0xd6/0x110 [15131.871643] [] __vmalloc_node_range+0x1ef/0x210 [15131.871645] [] __vmalloc_node+0x66/0x70 [15131.871648] [] ? __aa_kvmalloc+0x28/0x60 [15131.871650] [] vmalloc+0x38/0x40 [15131.871652] [] ? __aa_kvmalloc+0x28/0x60 [15131.871654] [] __aa_kvmalloc+0x28/0x60 [15131.871656] [] aa_simple_write_to_buffer+0x34/0x90 [15131.871658] [] policy_update+0x73/0x230 [15131.871660] [] ? security_file_permission+0x3e/0xd0 [15131.871662] [] profile_replace+0x98/0xe0 [15131.871664] [] ? policy_update+0x230/0x230 [15131.871666] [] __vfs_write+0x22/0x50 [15131.871668] [] vfs_write+0x8c/0x1b0 [15131.871669] [] SyS_write+0x51/0xb0 [15131.871672] [] do_fast_syscall_32+0x9f/0x190 [15131.871675] [] sysenter_past_esp+0x3d/0x61 [15131.871676] Mem-Info: [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0 active_file:84472 inactive_file:25195 isolated_file:0 unevictable:0 dirty:34 writeback:0 unstable:0 slab_reclaimable:7222 slab_unreclaimable:14030 mapped:8431 shmem:5785 pagetables:204 bounce:0 free:289381 free_pcp:659 free_cma:0 [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871686] lowmem_reserve[]: 0 834 1942 1942 [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB active_anon:30164kB inactive_anon:2776kB active_file:158404kB inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871693] lowmem_reserve[]: 0 0 8863 8863 [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB active_anon:36408kB inactive_anon:5496kB active_file:176764kB inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871699] lowmem_reserve[]: 0 0 0 0 [15131.871701] DMA: 12*4kB (UME) 10*8kB (UME) 7*16kB (ME) 5*32kB (UM) 2*64kB (U) 3*128kB (UM) 3*256kB (UM) 4*512kB (UME) 3*1024kB (ME) 1*2048kB (M) 0*4096kB = 8848kB [15131.871711] Normal: 87*4kB (UME) 106*8kB (UME) 168*16kB (UME) 195*32kB (UME) 135*64kB (UME) 161*128kB (ME) 120*256kB (ME) 61*512kB (UME) 25*1024kB (ME) 6*2048kB (M) 55*4096kB (M) = 364492kB [15131.871720] HighMem: 131*4kB (UM) 835*8kB (UM) 302*16kB (UM) 119*32kB (UM) 95*64kB (UM) 50*128kB (UM) 67*256kB (UM) 55*512kB (UM) 52*1024kB (M) 23*2048kB (UM) 149*4096kB (M) = 784292kB [15131.871729] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB [15131.871730] 115450 total pagecache pages [15131.871731] 0 pages in swap cache [15131.871733] Swap cache stats: add 0, delete 0, find 0/0 [15131.871734] Free swap = 0kB [15131.871734] Total swap = 0kB [15131.871735] 511870 pages RAM [15131.871736] 283618 pages HighMem/MovableOnly [15131.871737] 8662 pages reserved [15131.871738] 0 pages cma reserved
[Bug 1830502] Re: apparmor uses excessive memory leading to oom kill
Hi, running the snapd tests on i386 I see the following error that could be related to this. It is failing with pc-kernel on beta and candidate but I coun't reproduce it with the version on stable. > snap list Name VersionRev Tracking Publisher Notes core 16-2.39.1 7122 beta canonical* core pc 16.04-0.10 34candidate canonical* gadget pc-kernel 4.4.0-149.175 219 candidate canonical* kernel Logs: May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: vmap allocation for size 73728 failed: use vmalloc= to increase size. May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: vmalloc: allocation failure: 68497 bytes May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: apparmor_parser: page allocation failure: order:0, mode:0x24000c2 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: CPU: 1 PID: 23415 Comm: apparmor_parser Not tainted 4.4.0-149-generic #175-Ubuntu May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: c1b15967 70e2bd9c 0286 d0cf7e00 c13c12ef c1a1ce6c 0001 d0cf7e30 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: c11821b6 c1a1b220 f479a700 024000c2 d0cf7e44 c1a1ce6c d0cf7e18 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: 70e2bd9c 00010b91 d0cf7e60 c11ba86f 024000c2 c1a1ce6c May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: Call Trace: May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] dump_stack+0x58/0x79 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] warn_alloc_failed+0xd6/0x110 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] __vmalloc_node_range+0x1ef/0x210 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] __vmalloc_node+0x66/0x70 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] ? __aa_kvmalloc+0x28/0x60 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] vmalloc+0x38/0x40 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] ? __aa_kvmalloc+0x28/0x60 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] __aa_kvmalloc+0x28/0x60 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] aa_simple_write_to_buffer+0x34/0x90 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] policy_update+0x73/0x230 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] ? security_file_permission+0x3e/0xd0 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] profile_replace+0x98/0xe0 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] ? policy_update+0x230/0x230 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] __vfs_write+0x22/0x50 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] vfs_write+0x8c/0x1b0 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] SyS_write+0x51/0xb0 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] do_fast_syscall_32+0x9f/0x190 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: [] sysenter_past_esp+0x3d/0x61 May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: Mem-Info: May 30 03:57:34 localhost.localdomain snapd[23208]: May 30 03:57:33 localhost.localdomain kernel: active_anon:10318 inactive_anon:1512 isolated_anon:0 May 30 03:57:34 localhost.localdomain snapd[23208]: active_file:77754 inactive_file:23998 isolated_file:0 May 30 03:57:34 localhost.localdomain snapd[23208]: unevictable:0 dirty:551 writeback:0 unstable:0 May 30 03:57:34 localhost.localdomain snapd[23208]: slab_reclaimable:7394 slab_unreclaimable:13711 May 30 03:57:34
[Bug 1495580] Re: chfn needs to learn about the --extrausers argument and use libnss-extrausers files when set
Validation done, no errors found. Logs: xenial: https://paste.ubuntu.com/p/PrRPMnmBkN/ ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495580 Title: chfn needs to learn about the --extrausers argument and use libnss- extrausers files when set To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1495580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984390] Re: $PATH is taken from login.defs not /etc/environment
SRU validated, no issues found. Logs: xenial: https://paste.ubuntu.com/p/9jdjdQns7t/ bionic: https://paste.ubuntu.com/p/P6CZ5WnmmB/ ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984390 Title: $PATH is taken from login.defs not /etc/environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/984390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818648] Re: [SRU] 2.38
Hello, verification is completed with no issues. Results in the doc: https://docs.google.com/document/d/1xB29Pgwqp_Cpbp53_XsHC3s-Bmh3nYjfkU72DpP1imc/edit?usp=sharing ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818648 Title: [SRU] 2.38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1818648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824234] [NEW] with snapd 2.37.4 the command "apt remove --purge -y snapd" fails on ubuntu bionic
Public bug reported: I can't uninstall and purge snapd. See how to reproduce the error: google:ubuntu-18.04-64 .../tasks/google/start-instance# apt install -y snapd Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: zenity | kdialog The following NEW packages will be installed: snapd 0 upgraded, 1 newly installed, 0 to remove and 30 not upgraded. Need to get 14.7 MB of archives. After this operation, 67.6 MB of additional disk space will be used. Get:1 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 snapd amd64 2.37.4+18.04.1 [14.7 MB] Fetched 14.7 MB in 0s (40.0 MB/s) Selecting previously unselected package snapd. (Reading database ... 95738 files and directories currently installed.) Preparing to unpack .../snapd_2.37.4+18.04.1_amd64.deb ... Unpacking snapd (2.37.4+18.04.1) ... Processing triggers for mime-support (3.60ubuntu1) ... Setting up snapd (2.37.4+18.04.1) ... md5sum: /etc/apparmor.d/usr.lib.snapd.snap-confine: No such file or directory snapd.failure.service is a disabled or a static unit, not starting it. snapd.snap-repair.service is a disabled or a static unit, not starting it. Processing triggers for man-db (2.8.3-2ubuntu0.1) ... google:ubuntu-18.04-64 .../tasks/google/start-instance# apt-cache policy snapd snapd: Installed: 2.37.4+18.04.1 Candidate: 2.37.4+18.04.1 Version table: *** 2.37.4+18.04.1 500 500 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.32.5+18.04 500 500 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages google:ubuntu-18.04-64 .../tasks/google/start-instance# apt remove --purge snapd Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: snapd* 0 upgraded, 0 newly installed, 1 to remove and 30 not upgraded. After this operation, 67.6 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 95800 files and directories currently installed.) Removing snapd (2.37.4+18.04.1) ... Processing triggers for mime-support (3.60ubuntu1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... (Reading database ... 95738 files and directories currently installed.) Purging configuration files for snapd (2.37.4+18.04.1) ... Final directory cleanup Discarding preserved snap namespaces Removing extra snap-confine apparmor rules Removing snapd cache rm: cannot remove '/var/cache/snapd/aux': Is a directory dpkg: error processing package snapd (--purge): installed snapd package post-removal script subprocess returned error exit status 1 Errors were encountered while processing: snapd E: Sub-process /usr/bin/dpkg returned an error code (1) google:ubuntu-18.04-64 .../tasks/google/start-instance# ls /var/cache/snapd/aux MJbt3BgxESyOON7gqKVEnA06NLRM3Dxd.json google:ubuntu-18.04-64 .../tasks/google/start-instance# ls /var/cache/snapd/ aux google:ubuntu-18.04-64 .../tasks/google/start-instance# ls /v var/ vmlinuz vmlinuz.old google:ubuntu-18.04-64 .../tasks/google/start-instance# ls /var/lib/snapd/ apparmor/ assertions/ cache/ cookie/ desktop/device/ features/ mount/ seccomp/seed/ sequence/ snaps/ state.json google:ubuntu-18.04-64 .../tasks/google/start-instance# ls /var/lib/snapd/ apparmor assertions cache cookie desktop device features mount seccomp seed sequence snaps state.json ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Description changed: + I can't uninstall and purge snapd. See how to reproduce the error: - I can't uninstall and purge snapd - - google:ubuntu-18.04-64 .../tasks/google/start-instance# apt install -y snapd + google:ubuntu-18.04-64 .../tasks/google/start-instance# apt install -y snapd Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done Suggested packages: - zenity | kdialog + zenity | kdialog The following NEW packages will be installed: - snapd + snapd 0 upgraded, 1 newly installed, 0 to remove and 30 not upgraded. Need to get 14.7 MB of archives. After this operation, 67.6 MB of additional disk space will be used. Get:1 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 snapd amd64 2.37.4+18.04.1 [14.7 MB] Fetched 14.7 MB in 0s (40.0 MB/s) Selecting previously unselected package snapd. (Reading database ... 95738 files and directories currently installed.) Preparing to unpack .../snapd_2.37.4+18.04.1_amd64.deb ... Unpacking snapd (2.37.4+18.04.1) ... Processing triggers for mime-support (3.60ubuntu1) ... Setting up snapd (2.37.4+18.04.1) ... md5sum: /etc/apparmor.d/usr.lib.snapd.snap-confine: No such file or directory
[Bug 1824230] [NEW] Download not resumed for base snap when using "snap install --dangerous"
Public bug reported: If I have a /var/lib/snapd/snaps/core18_xxx.snap.partial, and I download the snap jq-core18 and then install: snap install jq-core18_yyy.snap --dangerous, it is not resuming the download for the core18 snap which is the base snap for jq-core18. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824230 Title: Download not resumed for base snap when using "snap install --dangerous" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1824230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659534] Re: userdel doesn't supports extrausers
Validation done on xenial and bionic This log is part of the test I did to check --extrausers can be used to add and del users. https://paste.ubuntu.com/p/Jn2kDcNcnv/ ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-needed-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659534 Title: userdel doesn't supports extrausers To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
Validation completed. No errors detected on: bionic: 237-3ubuntu10.17 core18: systemd 237 ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819728] Re: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18)
Validation completed. No errors detected on: xenial: 229-4ubuntu21.19 bionic: 237-3ubuntu10.17 core18: systemd 237 ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819728 Title: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817949] Re: [SRU] 2.37.4
** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817949 Title: [SRU] 2.37.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1817949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817949] Re: [SRU] 2.37.4
I already updated the tags. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817949 Title: [SRU] 2.37.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1817949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817949] Re: [SRU] 2.37.4
** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817949 Title: [SRU] 2.37.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1817949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817949] Re: [SRU] 2.37.4
SRU validation done for xenial bionic and cosmic. For Trusty is still missing the autopckgtests execution on http://people.canonical.com /~ubuntu-archive/proposed-migration/trusty/update_excuses.html#snapd ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817949 Title: [SRU] 2.37.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1817949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811233] Re: [SRU] 2.37
The validation has finished. Results here: https://docs.google.com/document/d/10CC2Fh7RhplyMsgiNbI8xdqoE6NnjQZ97ViF7DzSHRc/edit?usp=sharing ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811233 Title: [SRU] 2.37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1811233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
tests results here: https://paste.ubuntu.com/p/z4Vjz2jYYG/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
Finally I could verify the fix works well and fixes the issue. We are building core18 image using the snap which has systemd from proposed. Steps to validate: 1. build core18 snap using proposed > git clone -b master https://git.launchpad.net/snap-core18 > cd snap-core18 > sed -i -e 's/current/pending/g' Makefile > sudo snapcraft 2. prepare test > git clone https://github.com/sergiocazzolato/snapd.git > git checkout tests-validate-lp-1778936 > cd snapd > < copy the core18_18_amd64.snad to tests/lib/ directory > 3. run the tests > spread -debug google:ubuntu-core-18-64:tests/main/interfaces-hostname-control -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
@xnox, testing is still ongoing, today I'll have more information about it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
To reproduce the error: 1. checkout this branch: https://github.com/sergiocazzolato/snapd/tree/tests-validate-lp-1778936 2. run the test: spread -debug google:ubuntu-core-18-64:tests/main/interfaces-hostname-control -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
@xnox Hello, I validated the fix on core18 but I still see the error trying to set the hostname This line is failing: + test-snapd-sh.with-hostname-control-plug -c 'hostnamectl set-hostname localhost' Could not set property: Failed to set static hostname: Read-only file system I created a branch where I build snapd using systemd from proposed "systemd (= 237-3ubuntu10.10)", and then I use that snapd fo build the ubuntu core 18 where I execute the test. The test which is failing is https://github.com/snapcore/snapd/blob/master/tests/main/interfaces- hostname-control/task.yaml. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786438] Re: [SRU] 2.35
Verification done for snapd 2.35.5. Test results at: https://docs.google.com/document/d/1qgPOL1f6naE5iA2zRFz1pLcAyXrlzuZN-RZfgN-8C40/edit?usp=sharing ** Tags removed: verification-needed verification-needed-bionic verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786438 Title: [SRU] 2.35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1786438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786438] Re: [SRU] 2.35
Verification done. Test results at: https://docs.google.com/document/d /1qgPOL1f6naE5iA2zRFz1pLcAyXrlzuZN-RZfgN-8C40/edit?usp=sharing ** Tags removed: verification-needed verification-needed-bionic verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786438 Title: [SRU] 2.35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1786438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786438] Re: [SRU] 2.35
Validation is in progress, results are located at: https://docs.google.com/document/d/1qgPOL1f6naE5iA2zRFz1pLcAyXrlzuZN- RZfgN-8C40/edit?usp=sharing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786438 Title: [SRU] 2.35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1786438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783810] Re: [SRU] blocks boot on core18
I validated this by using this new core18 image http://people.canonical.com/~mvo/tmp/core18-amd64-18-alpha20180803-with-lp1783810.img.xz It is working now ** Changed in: util-linux (Ubuntu) Assignee: (unassigned) => Sergio Cazzolato (sergio-j-cazzolato) ** Changed in: util-linux (Ubuntu Bionic) Assignee: (unassigned) => Sergio Cazzolato (sergio-j-cazzolato) ** Changed in: util-linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783810 Title: [SRU] blocks boot on core18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1783810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779403] Re: [SRU] 2.34.2
Verification completed. Test results: https://docs.google.com/document/d /1bZKFhcPtTc15L_9FZhke1DydxB-ol6ym1r9PWHPgyic/edit?usp=sharing ** Tags removed: verification-needed verification-needed-bionic verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779403 Title: [SRU] 2.34.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1779403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773118] Re: [SRU] 2.33
Validation done, tests results on: https://docs.google.com/document/d/1WZqYRPNeXIsjgB68GyhMTHY3F5Jema2zEp850wbP9OQ/edit?usp=sharing ** Tags removed: verification-needed verification-needed-artful verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-artful verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773118 Title: [SRU] 2.33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1773118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773118] Re: [SRU] 2.33
Verification completed. ** Tags removed: verification-needed verification-needed-artful verification-needed-bionic verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-artful verification-done-bionic verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773118 Title: [SRU] 2.33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1773118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773118] Re: [SRU] 2.33
Hello, currently doing validation. This is the document with the test results: https://docs.google.com/document/d/1WZqYRPNeXIsjgB68GyhMTHY3F5Jema2zEp850wbP9OQ/edit?usp=sharing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773118 Title: [SRU] 2.33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1773118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767833] Re: [SRU] 2.32.9
Hello, verification completed. Test results on https://docs.google.com/document/d/13vIMXPKzMb3TytmszbSoRKOVu7x4DD9SPuL74rAycN0/edit?usp=sharing ** Tags removed: verification-needed verification-needed-artful verification-needed-bionic verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-artful verification-done-bionic verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767833 Title: [SRU] 2.32.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1767833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767833] Re: [SRU] 2.32.8
Verification done. Results on https://docs.google.com/document/d/13vIMXPKzMb3TytmszbSoRKOVu7x4DD9SPuL74rAycN0/edit?usp=sharing ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767833 Title: [SRU] 2.32.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1767833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765090] Re: [SRU] 2.32.5
Validation completed. Test results at: https://docs.google.com/document/d/13vIMXPKzMb3TytmszbSoRKOVu7x4DD9SPuL74rAycN0/edit?usp=sharing ** Tags removed: verification-needed verification-needed-artful verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-artful verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765090 Title: [SRU] 2.32.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1765090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756173] Re: [SRU] 2.32
** Tags removed: verification-needed verification-needed-artful verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-artful verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756173 Title: [SRU] 2.32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1756173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735344] Re: [SRU] 2.30
Hello, test results are located here: https://docs.google.com/document/d/13vIMXPKzMb3TytmszbSoRKOVu7x4DD9SPuL74rAycN0/edit?usp=sharing Just seen some OoM erros for i386 which are known issues. More details in the document. ** Tags removed: verification-needed verification-needed-artful verification-needed-bionic verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-artful verification-done-bionic verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735344 Title: [SRU] 2.30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1735344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726258] Re: [SRU] 2.29
Verification completed ** Tags removed: verification-needed verification-needed-artful verification-needed-trusty verification-needed-xenial verification-needed-zesty ** Tags added: verification-done verification-done-artful verification-done-trusty verification-done-xenial verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726258 Title: [SRU] 2.29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1726258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732148] Re: After refresh core to #3440, cannot revert core to stable version.
Hello, I have executed this in a pi3 and a ubuntu-core vm and I could not reproduce that issue. Do you have any scripts that you use to reproduce that error? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732148 Title: After refresh core to #3440, cannot revert core to stable version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1732148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714984] Re: [SRU] 2.28
** Tags removed: verification-needed verification-needed-trusty verification-needed-xenial verification-needed-zesty ** Tags added: verification-done verification-done-trusty verification-done-xenial verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714984 Title: [SRU] 2.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1714984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715004] [NEW] Network configuration timed out updating network configuration on a dragonboard
Public bug reported: I run console-conf on my dragonboard (using stable release 2.27.5). I try to change my wifi configuration and I see this error message: "Network configuration timed out; please verify your settings." This is what I see in the syslog https://paste.ubuntu.com/25466659/ Steps to reproduce: 1- Initial setup with WiFi 2- Connect through ssh 3- run > sudo console-conf 4- Press Ok 5- Press Done 6- Wait ... Same issue happens in case the wifi configuration is changed, instead of leaving the same in step 5. The same procedure works perfectly in the pi3. ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715004 Title: Network configuration timed out updating network configuration on a dragonboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1715004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703798] Re: [SRU] 2.27.5
Verification completed for 2.27.5, results on https://docs.google.com/a/canonical.com/document/d/1hniUla7hQ1_BgSL27LlJCJAqjJ2CayA0EQlWFzDW48w/edit?usp=sharing ** Tags removed: verification-needed verification-needed-trusty verification-needed-xenial verification-needed-zesty ** Tags added: verification-done verification-done-trusty verification-done-xenial verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703798 Title: [SRU] 2.27.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1703798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703798] Re: [SRU] 2.27.4
** Tags removed: verification-needed verification-needed-trusty verification-needed-xenial verification-needed-zesty ** Tags added: verification-done verification-done-trusty verification-done-xenial verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703798 Title: [SRU] 2.27.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1703798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703798] Re: [SRU] 2.27.3
** Tags removed: verification-needed verification-needed-trusty verification-needed-xenial verification-needed-zesty ** Tags added: verification-done verification-done-trusty verification-done-xenial verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703798 Title: [SRU] 2.27.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1703798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690083] Re: [SRU] 2.26.10
** Tags removed: verification-needed verification-needed-trusty verification-needed-xenial verification-needed-yakkety verification-needed-zesty ** Tags added: verification-done verification-done-trusty verification-done-xenial verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690083 Title: [SRU] 2.26.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1690083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632388] Re: console-conf wifi only setup on pi3 beta3 image not possible
It is also happening that with the current candidate image. I also saw that when I go through the networking screen without any configuration and then press cancel, the networking screen is not showing the wlan anymore, it just shows the ethernet connection. Attached is the image that I see with the timeout error. ** Attachment added: "IMG_20170418_213143.jpg" https://bugs.launchpad.net/snappy/+bug/1632388/+attachment/4864458/+files/IMG_20170418_213143.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632388 Title: console-conf wifi only setup on pi3 beta3 image not possible To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1632388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663666] [NEW] max-format is not a positive integer assertion installing unity8-session snap
Public bug reported: I get this assertion when I run the command unity8-snap-install in my zesty vm. This happens with the today's zesty daily image. sudo snap install unity8-session --edge --devmode error: cannot perform the following tasks: - Fetch and check assertions for snap "unity8-session" (439) (Get https://assertions.ubuntu.com/v1/assertions/snap-revision/rjPkjvvl9AezpBRMi_cxP6yLUf7hychxwsOg7CT68Ygr9JnccHmvCfymWqUEZGTt?max-format=0: dial tcp: lookup assertions.ubuntu.com: no such host) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663666 Title: max-format is not a positive integer assertion installing unity8-session snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1663666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659955] [NEW] Not possible to launch apps in xenial using unity8-session.ubuntu-app-launch command using the unity8 session snap
Public bug reported: Steps: . I start unity8 session snap in my xenial . It is possible start apps manually . When run the command unity8-session.ubuntu-app-launch-appids a list of apps are printed (I select webbrowser-app_webbrowser-app_8) (also tried with other too) . I run the command "unity8-session.ubuntu-app-launch webbrowser-app_webbrowser-app_8" and I get the following output http://paste.ubuntu.com/23877063/ (everything seems to be ok) . But in the screen the app is not displayed in the screen. If I follow the same steps in zesty, the app is displayed in the screen. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - not possible to launch apps in xenial using unity8-session.ubuntu-app-launch command + Not possible to launch apps in xenial using unity8-session.ubuntu-app-launch command using the unity8 session snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659955 Title: Not possible to launch apps in xenial using unity8-session.ubuntu-app- launch command using the unity8 session snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1659955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658809] [NEW] Not installing zesty in virtual machine manager
Public bug reported: Steps: - I downloaded the image http://cdimage.ubuntu.com/daily-live/current/zesty-desktop-amd64.iso (also tried with the previous one). - Using virtual machine manager I create a vm and use that iso as image. I tried selecting the os as ubuntu and generic. I set 2048 MB of RAM memory, 1 cpu and 20GB of disk. - Then The language screen appears and I select English. - In the next scree I select "Install ubuntu", then ubuntu starts without asking nothing else. - I can use ubuntu but if I reboot the machine I cannot use it anymore and I see the error: Booting from Hard Disk... Boot failed: not a bootable disk No bootable device ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658809 Title: Not installing zesty in virtual machine manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1658809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596892] [NEW] Arale is shutted down when power button is pressed when the greeter is visible
Public bug reported: If I press the power button a dialog to select for reboot, shutdown, etc is displayed. But when I press the button immediately when the greeter appears (after start the device), this dialog does not appear and the device is shutted down directly. If I wait few seconds after the greeter appears to press the button the dialog will be displayed. It is happening in Arale in the last version (362) and previous too. ** Affects: ubuntu-system-image Importance: Undecided Status: New ** Affects: unity8 Importance: Undecided Status: New ** Also affects: unity8 Importance: Undecided Status: New ** No longer affects: unity8 (Ubuntu) ** Also affects: ubuntu-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596892 Title: Arale is shutted down when power button is pressed when the greeter is visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1596892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574779] Re: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler
These are the event I got when I executed the here app with command profile_appstart.sh -u 127.0.0.1 -p -a com.nokia.heremaps_here_1.0.9 -c 10 -s 15 It is clear that the qtmir:firstFrameDrawn event is arriving twice. This app is the only one it is being executed in the device. Processing event: qtmir:firstFrameDrawn with time 1466131228876304823 Processing event: qtmir:firstFrameDrawn with time 1466131234380455207 Processing event: app:invokeApplauncher with time 1466131244640037362 Processing event: qtmir:firstFrameDrawn with time 1466131249647493285 Processing event: qtmir:firstFrameDrawn with time 1466131254389996287 Processing event: app:invokeApplauncher with time 1466131266062964363 Processing event: qtmir:firstFrameDrawn with time 1466131270738460749 Processing event: qtmir:firstFrameDrawn with time 1466131275479211980 Processing event: app:invokeApplauncher with time 1466131287277920750 Processing event: qtmir:firstFrameDrawn with time 1466131292310432365 Processing event: qtmir:firstFrameDrawn with time 1466131297210752442 Processing event: app:invokeApplauncher with time 1466131308810520212 Processing event: qtmir:firstFrameDrawn with time 1466131313751826212 Processing event: qtmir:firstFrameDrawn with time 1466131319441808906 Processing event: app:invokeApplauncher with time 1466131330230824983 Processing event: qtmir:firstFrameDrawn with time 1466131335186896213 Processing event: qtmir:firstFrameDrawn with time 1466131339976596522 Processing event: app:invokeApplauncher with time 1466131351694725522 Processing event: qtmir:firstFrameDrawn with time 1466131356948870601 Processing event: qtmir:firstFrameDrawn with time 1466131361853824754 Processing event: app:invokeApplauncher with time 1466131373144023832 Processing event: qtmir:firstFrameDrawn with time 1466131377544375909 Processing event: qtmir:firstFrameDrawn with time 1466131382511673370 Processing event: app:invokeApplauncher with time 1466131394092874294 Processing event: qtmir:firstFrameDrawn with time 1466131399067710294 Processing event: app:invokeApplauncher with time 1466131415569112757 Processing event: qtmir:firstFrameDrawn with time 1466131420595585143 Processing event: qtmir:firstFrameDrawn with time 1466131425398448988 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574779 Title: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1574779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574779] Re: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler
** Tags added: performance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574779 Title: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1574779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574779] Re: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler
Tried with 12 and 15 seconds and I got the same error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574779 Title: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1574779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574779] Re: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler
I have used longer times (12s), I am gonna try with even longer ones to see if it is the solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574779 Title: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1574779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578049] Re: std::runtime_error executing profile_appstart.sh for dialer app
Bug fixed in bug:1575990 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578049 Title: std::runtime_error executing profile_appstart.sh for dialer app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1578049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578049] Re: std::runtime_error executing profile_appstart.sh for dialer app
this is gonna be fixed soon https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/stable-phone-overlay/+sourcepub/6405355 /+listing-archive-extra ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578049 Title: std::runtime_error executing profile_appstart.sh for dialer app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1578049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578049] [NEW] std::runtime_error executing profile_appstart.sh for dialer app
Public bug reported:
Getting the following error when profiling the following apps: dialer,
messaging, webbrowser, system-settings and address-book.
It can be reproduced with the next build too.
phablet@ubuntu-phablet:~$ profile_appstart.sh -p -a dialer-app
The lttng server is not accesible. Check lttng-relayd or firewall policies.
Falling back to local
Session auto-20160504-044646 created.
Traces will be written in /home/phablet/lttng-traces/auto-20160504-044646
UST event qtmir:firstFrameDrawn created in channel channel0
UST event app:* created in channel channel0
Tracing started for session auto-20160504-044646
x - 1
terminate called after throwing an instance of 'std::runtime_error'
what(): AppID is empty
/usr/bin/profile_appstart.sh: line 79: 26694 Aborted (core
dumped) ubuntu-app-stop ${APP_NAME}
x - 2
terminate called after throwing an instance of 'std::runtime_error'
what(): AppID is empty
/usr/bin/profile_appstart.sh: line 79: 26875 Aborted (core
dumped) ubuntu-app-stop ${APP_NAME}
x - 3
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 321
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-04-27 13:56:49
version version: 321
version ubuntu: 20160427
version device: 20160329-a9bacdb
version custom: 20160324--36-54-vivid
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578049
Title:
std::runtime_error executing profile_appstart.sh for dialer app
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1578049/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574779] [NEW] "RuntimeError: Wrong Nr of events" executing the app-launch-profiler
Public bug reported: I am getting errors when running the lttng profiler for the apps: Calculator, music, Camera, Clock, Here, Gallery , Ebay See the commands executed and the result here: http://paste.ubuntu.com/16053036/ I also tested with different parametes and always got the same error (sometimes it works) To get the process to use, run ubuntu-app-triplet with the following names for each app. calculator: com.ubuntu.calculator music: com.ubuntu.music camera: com.ubuntu.camera clock: com.ubuntu.clock here: com.nokia.heremaps gallery: com.ubuntu.gallery ebay: com.ubuntu.developer.webapps.webapp-ebay For the following apps, the results are ok: Messaging, Web Browser, System Settings, Dialer, Address Book ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574779 Title: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1574779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550363] [NEW] Time to start gallery app is better when cache is not used
Public bug reported: I was doing some tests for the main apps calculating the time that the app takes to start (from the app icon is clicked on apps scope until the app is started and the spin loader disappear). I did two kind of tests: cold and hot scenarios. The cold scenario is when the app has not any cache QML stored, hot scenario is when the app was previously opened and cache was created. After analyze the results the only app that takes more time to open in a hot scenario than cold scenario is the gallery app. Attached is a graphic with the times that the app took for different builds. The graphic includes just 4 builds but I have seen this behavior in more than 20 builds. Tests used to measure this are stored in https://code.launchpad.net /ubuntu-system-tests project I can provide more details about the tests and other results if needed. ** Affects: gallery-app (Ubuntu) Importance: Undecided Status: New ** Attachment added: "barchart_gallery.png" https://bugs.launchpad.net/bugs/1550363/+attachment/4581848/+files/barchart_gallery.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550363 Title: Time to start gallery app is better when cache is not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1550363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
