[Touch-packages] [Bug 2011458] [NEW] ssh fails to rebind when it is killed with -HUP
Public bug reported: In kinetic and lunar gce images we are facing an issue when ssh is being killed with -HUP SSH is failing to rebind port 22. It is not failing in other previous systems. It can be reproduced by running # pkill -o -HUP sshd || true # journalctl -n 20 Mar 13 14:58:52 mar131454-025105 sshd[1371]: Received SIGHUP; restarting. Mar 13 14:58:52 mar131454-025105 sshd[1371]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Mar 13 14:58:52 mar131454-025105 sshd[1371]: error: Bind to port 22 on :: failed: Address already in use. Mar 13 14:58:52 mar131454-025105 sshd[1371]: fatal: Cannot bind any address. Mar 13 14:58:52 mar131454-025105 systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Mar 13 14:58:52 mar131454-025105 systemd[1]: ssh.service: Failed with result 'exit-code'. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2011458 Title: ssh fails to rebind when it is killed with -HUP Status in openssh package in Ubuntu: New Bug description: In kinetic and lunar gce images we are facing an issue when ssh is being killed with -HUP SSH is failing to rebind port 22. It is not failing in other previous systems. It can be reproduced by running # pkill -o -HUP sshd || true # journalctl -n 20 Mar 13 14:58:52 mar131454-025105 sshd[1371]: Received SIGHUP; restarting. Mar 13 14:58:52 mar131454-025105 sshd[1371]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Mar 13 14:58:52 mar131454-025105 sshd[1371]: error: Bind to port 22 on :: failed: Address already in use. Mar 13 14:58:52 mar131454-025105 sshd[1371]: fatal: Cannot bind any address. Mar 13 14:58:52 mar131454-025105 systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Mar 13 14:58:52 mar131454-025105 systemd[1]: ssh.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2011458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1869435 Title: Performance regression on ubuntu focal Status in systemd package in Ubuntu: Opinion Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1869661 Title: lxc 3.23 (?) breaks nested lxd with snaps Status in lxc package in Ubuntu: New Bug description: It looks like the latest release of lxd broke our snapd lxd test. The failure looks like it's lxd itself that can no longer run a nested lxd. The full log is available on e.g. https://api.travis-ci.org/v3/job/668138958/log.txt, search for """ Starting my-inner-ubuntu + MATCH from-the-INSIDE-inside + lxd.lxc exec my-nesting-ubuntu -- lxd.lxc exec my-inner-ubuntu -- echo from-the-INSIDE-inside Error: EOF grep error: pattern not found, got: """ The relevant part of the test is: https://github.com/snapcore/snapd/blob/master/tests/main/lxd/task.yaml#L153 I.e. this test creates an lxd container and sets up lxd inside this container. Happy to help with debugging (if needed), it really easy to reproduce with the above spread script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1869661/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1869435 Title: Performance regression on ubuntu focal Status in systemd package in Ubuntu: Incomplete Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1869435 Title: Performance regression on ubuntu focal Status in systemd package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375
Title:
groupdel doesn't support extrausers
Status in snapd:
Triaged
Status in shadow package in Ubuntu:
Fix Released
Status in shadow source package in Xenial:
Fix Committed
Status in shadow source package in Bionic:
Fix Committed
Status in shadow source package in Disco:
Fix Committed
Bug description:
snapd needs the ability to call 'groupdel --extrausers foo' to clean
up after itself, but --extrausers is currently unsupported.
[Impact]
On ubuntu-core systems we want to be able to manage "extrausers" in the same
way as regular users. This requires updates to the various
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.
This is an important feature for Ubuntu Core
[Test Case]
0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
1. install the libnss-extrausers and add "extrauers" to the passwd and shadow
line (see /usr/share/doc/libnss-extrausers/README for the modifications in
sswitch.conf)
2. run "groupadd --extrausers foo" and verify "grep foo
/var/lib/extrausers/group"
3 check /var/lib/extrausers/group for the new "foo" group
4. run "groupdel --extrausers foo"
5. check /var/lib/extrausers/group and ensure the "foo" group is removed
[Regression Potential]
* low: this adds a new (optional) option which is off by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: 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
[Touch-packages] [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 Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: 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)
[Touch-packages] [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 Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: 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)
[Touch-packages] [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 Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: 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)
[Touch-packages] [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 Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: 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)
[Touch-packages] [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
[Touch-packages] [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
[Touch-packages] [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
[Touch-packages] [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 Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1495580 Title: chfn needs to learn about the --extrausers argument and use libnss- extrausers files when set Status in Snappy: Fix Released Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Xenial: Fix Committed Status in shadow source package in Bionic: Fix Released Bug description: as seen in bug 1492327, adduser now works for creating users in the extrausers db but when it tries to update the GECOS field at the end of adding a user (interactively and noninteractively) chfn falls over ... chfn needs similar patches to the other shadow binaries that recently got extrausers support. TEST CASE: - create a user "foo" on an Ubuntu Core system - run "chfn --extrausers -f some-name foo" on an Ubuntu Core system REGRESSION POTENTIAL: - low: this requires the new (and optional) --extrausers switch to change anything. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1495580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/984390 Title: $PATH is taken from login.defs not /etc/environment Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Precise: Won't Fix Status in shadow source package in Xenial: Fix Committed Status in shadow source package in Bionic: Fix Committed Bug description: TEST CASE: $PATH isn't sourced from /etc/environment, instead the version in /etc/login.defs is used. (The example below comes from a precise install.) | james@panlong:~$ echo $PATH | /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games | james@panlong:~$ sudo su - buildd | buildd@panlong:~$ echo $PATH | /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games | buildd@panlong:~$ cat /etc/environment | PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" | buildd@panlong:~$ grep PATH /etc/login.defs | # Three items must be defined: MAIL_DIR, ENV_SUPATH, and ENV_PATH. | # *REQUIRED* The default PATH settings, for superuser and normal users. | ENV_SUPATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin | ENV_PATH PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games | #CRACKLIB_DICTPATH | buildd@panlong:~$ sudo sed -i -e "s#^ENV_PATH.*#ENV_PATH PATH=/wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games#" /etc/login.defs | buildd@panlong:~$ logout | james@panlong:~$ sudo su - buildd | buildd@panlong:~$ echo $PATH | /wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games | buildd@panlong:~$ REGRESSION POTENTIAL: - medium: it changes (incorrect) existing behaviour so https://xkcd.com/1172/ may apply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/984390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1659534 Title: userdel doesn't supports extrausers Status in Snappy: In Progress Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Xenial: Fix Committed Status in shadow source package in Bionic: Fix Committed Bug description: TEST CASE: - run userdel --extrausers foo on a ubuntu core system REGRESSION POTENTIAL: - low, this option will only take effect when "userdel --extrauser" is used. On an Ubuntu Core system is impossible to delete an user from the extrausers db: root@localhost:/# userdel --extrausers alice userdel: unrecognized option '--extrausers' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * core18 systems fail to update hostname * this happens due to /etc/hostname actually being a symlink to a file under /etc/writable/, adjust hostnamed to take that into account when trying to update /etc/hostname [Test Case] * run a core18 system, check that dhcp acquire hostname is correctly updated in /etc/writable/hostname [Regression Potential] * This is cherrypick of code that has gone missing since xenial. * There is no change of behaviour for the classic systems. * Currently, core18 systems simply fail to update hostname/machine-info files, thus the worst case is that they will still fail to do so. [Other Info] * original bug report The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to systemd in 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) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Bionic: Fix Committed Bug description: [Impact] On Ubuntu Core we recently hit the a race in daemon-reload and systemctl twice. This race is fixed in systemd upstream: "fix race between daemon-reload and other commands #8803" and a subsequent fix in "PR#11121". Note that this is a general problem in systemd with daemon-reload and systemctl commands, we just happen to hit it more often on Ubuntu Core but the test-case below explodes just fine on a normal Ubuntu release like 16.04 or 18.04 (not on 18.10+ as its fixed there). [TEST CASE] To reproduce its enough to run: for i in $(seq 50); do systemctl daemon-reload & systemctl start ssh & done This will result in "systemctl start ssh" hanging in ppoll. With the patch applied the hangs go away. [REGRESSION POTENTIAL] Medium/High, this change is already in the systemd upstream and in use disco and later but the backport required some manual resolving of conflicts the code because changed between 229,237 and the fixed code in 240. Its also not fully clear if the fix relies on the new systemd "coldplug" functionality that was added in more recent git revisions. The upstream fix is https://github.com/systemd/systemd/pull/8803 and https://github.com/systemd/systemd/pull/11121 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * core18 systems fail to update hostname * this happens due to /etc/hostname actually being a symlink to a file under /etc/writable/, adjust hostnamed to take that into account when trying to update /etc/hostname [Test Case] * run a core18 system, check that dhcp acquire hostname is correctly updated in /etc/writable/hostname [Regression Potential] * This is cherrypick of code that has gone missing since xenial. * There is no change of behaviour for the classic systems. * Currently, core18 systems simply fail to update hostname/machine-info files, thus the worst case is that they will still fail to do so. [Other Info] * original bug report The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * core18 systems fail to update hostname * this happens due to /etc/hostname actually being a symlink to a file under /etc/writable/, adjust hostnamed to take that into account when trying to update /etc/hostname [Test Case] * run a core18 system, check that dhcp acquire hostname is correctly updated in /etc/writable/hostname [Regression Potential] * This is cherrypick of code that has gone missing since xenial. * There is no change of behaviour for the classic systems. * Currently, core18 systems simply fail to update hostname/machine-info files, thus the worst case is that they will still fail to do so. [Other Info] * original bug report The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * core18 systems fail to update hostname * this happens due to /etc/hostname actually being a symlink to a file under /etc/writable/, adjust hostnamed to take that into account when trying to update /etc/hostname [Test Case] * run a core18 system, check that dhcp acquire hostname is correctly updated in /etc/writable/hostname [Regression Potential] * This is cherrypick of code that has gone missing since xenial. * There is no change of behaviour for the classic systems. * Currently, core18 systems simply fail to update hostname/machine-info files, thus the worst case is that they will still fail to do so. [Other Info] * original bug report The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * core18 systems fail to update hostname * this happens due to /etc/hostname actually being a symlink to a file under /etc/writable/, adjust hostnamed to take that into account when trying to update /etc/hostname [Test Case] * run a core18 system, check that dhcp acquire hostname is correctly updated in /etc/writable/hostname [Regression Potential] * This is cherrypick of code that has gone missing since xenial. * There is no change of behaviour for the classic systems. * Currently, core18 systems simply fail to update hostname/machine-info files, thus the worst case is that they will still fail to do so. [Other Info] * original bug report The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * core18 systems fail to update hostname * this happens due to /etc/hostname actually being a symlink to a file under /etc/writable/, adjust hostnamed to take that into account when trying to update /etc/hostname [Test Case] * run a core18 system, check that dhcp acquire hostname is correctly updated in /etc/writable/hostname [Regression Potential] * This is cherrypick of code that has gone missing since xenial. * There is no change of behaviour for the classic systems. * Currently, core18 systems simply fail to update hostname/machine-info files, thus the worst case is that they will still fail to do so. [Other Info] * original bug report The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1783810 Title: [SRU] blocks boot on core18 Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Bionic: Fix Released Bug description: The current version of libuuid is using getrandom() without the GRND_NONBLOCK flag. This means that in early boot the boot is blocked until the crng is initialized to "level=1" which on virtual machines may take some time. Upstream fixed this in https://github.com/karelzak/util- linux/commit/a9cf659e0508c1f56813a7d74c64f67bbc962538 and we should just backport the fix. [Impact] * Makes systems that use libuuid in early boot hang [Test Case] * boot a fresh core18 system with kernel 4.15 [Regression Potential] * little, change is very targeted This is uploaded to the bionic-proposed queue now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1783810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1663666 Title: max-format is not a positive integer assertion installing unity8-session snap Status in unity8 package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1663666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to unity8 in 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 Status in unity8 package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1659955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1596892 Title: Arale is shutted down when power button is pressed when the greeter is visible Status in Ubuntu system image: New Status in Unity 8: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1596892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1574779 Title: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1574779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1574779 Title: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1574779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1574779 Title: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1574779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1574779 Title: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1574779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1578049
Title:
std::runtime_error executing profile_appstart.sh for dialer app
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1578049/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1578049
Title:
std::runtime_error executing profile_appstart.sh for dialer app
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1578049/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1578049
Title:
std::runtime_error executing profile_appstart.sh for dialer app
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1578049/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1574779 Title: "RuntimeError: Wrong Nr of events" executing the app-launch-profiler Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1574779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 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 Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1550363 Title: Time to start gallery app is better when cache is not used Status in gallery-app package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1550363/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1513600] Re: [Scopes] Music scope blank using url-dispatcher
I am clicking on the "new albums from 7digtal >" It happens about once every 30 tries I am using a krillin with the channel --channel=ubuntu-touch/rc-proposed /bq-aquaris.en -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1513600 Title: [Scopes] Music scope blank using url-dispatcher Status in unity8 package in Ubuntu: New Bug description: Sporadically I get a blank page when I use the url-dispatcher to go to the music scope. The same issue has been reproduced going to the photos scope. After go to the scope I am waiting until the scope header is loaded and the loading bar has disappeared. To go to both affected scopes we I am doing: > url-dispatcher scope://musicaggregator > url-dispatcher scope://com.canonical.scopes.photos_photos I see a similar behavior when from the music scope I go to an online music scope such as "7 digital". What I see is that the 7digital scope doesn't show any data. I checked there is internet in the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1513600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1518028] Re: [Scopes] Carousel showing pictures that were deleted
Pawel, the issue seems to be fixed in the build 185, I can't reproduce it any more. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1518028 Title: [Scopes] Carousel showing pictures that were deleted Status in unity8 package in Ubuntu: New Bug description: The pictures stored in the sdcard are displayed in the photos carousel after those were deleted Steps: 1. Copy a bunch of pictures from my desktop through mtp to the sd card pictures dir 2. Go to photos scope (the pictures are shown in the carousel) 3. Click on "My photos", all the pictures appear in the my photos screen 4. Using nautilus delete all the pictures from the device sdcard 5. In the device go to the photos scope and refresh the scope manually 6. The pictures are still in the carousel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1518028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1518028] Re: [Scopes] Carousel showing pictures that were deleted
These are the images used to copy to the sdcard ** Attachment added: "numbers.tar.gz" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1518028/+attachment/4522622/+files/numbers.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1518028 Title: [Scopes] Carousel showing pictures that were deleted Status in unity8 package in Ubuntu: New Bug description: The pictures stored in the sdcard are displayed in the photos carousel after those were deleted Steps: 1. Copy a bunch of pictures from my desktop through mtp to the sd card pictures dir 2. Go to photos scope (the pictures are shown in the carousel) 3. Click on "My photos", all the pictures appear in the my photos screen 4. Using nautilus delete all the pictures from the device sdcard 5. In the device go to the photos scope and refresh the scope manually 6. The pictures are still in the carousel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1518028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1518028] Re: [Scopes] Carousel showing pictures that were deleted
Hi Pawel, I am on 183 on krillin (rc-proposed). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1518028 Title: [Scopes] Carousel showing pictures that were deleted Status in unity8 package in Ubuntu: New Bug description: The pictures stored in the sdcard are displayed in the photos carousel after those were deleted Steps: 1. Copy a bunch of pictures from my desktop through mtp to the sd card pictures dir 2. Go to photos scope (the pictures are shown in the carousel) 3. Click on "My photos", all the pictures appear in the my photos screen 4. Using nautilus delete all the pictures from the device sdcard 5. In the device go to the photos scope and refresh the scope manually 6. The pictures are still in the carousel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1518028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1518028] Re: [Scopes] Carousel showing pictures that were deleted
** Attachment added: "DSC_1660.JPG" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1518028/+attachment/4522237/+files/DSC_1660.JPG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1518028 Title: [Scopes] Carousel showing pictures that were deleted Status in unity8 package in Ubuntu: New Bug description: The pictures stored in the sdcard are displayed in the photos carousel after those were deleted Steps: 1. Copy a bunch of pictures from my desktop through mtp to the sd card pictures dir 2. Go to photos scope (the pictures are shown in the carousel) 3. Click on "My photos", all the pictures appear in the my photos screen 4. Using nautilus delete all the pictures from the device sdcard 5. In the device go to the photos scope and refresh the scope manually 6. The pictures are still in the carousel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1518028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1518028] [NEW] [Scopes] Carousel showing pictures that were deleted
Public bug reported: The pictures stored in the sdcard are displayed in the photos carousel after those were deleted Steps: 1. Copy a bunch of pictures from my desktop through mtp to the sd card pictures dir 2. Go to photos scope (the pictures are shown in the carousel) 3. Click on "My photos", all the pictures appear in the my photos screen 4. Using nautilus delete all the pictures from the device sdcard 5. In the device go to the photos scope and refresh the scope manually 6. The pictures are still in the carousel ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1518028 Title: [Scopes] Carousel showing pictures that were deleted Status in unity8 package in Ubuntu: New Bug description: The pictures stored in the sdcard are displayed in the photos carousel after those were deleted Steps: 1. Copy a bunch of pictures from my desktop through mtp to the sd card pictures dir 2. Go to photos scope (the pictures are shown in the carousel) 3. Click on "My photos", all the pictures appear in the my photos screen 4. Using nautilus delete all the pictures from the device sdcard 5. In the device go to the photos scope and refresh the scope manually 6. The pictures are still in the carousel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1518028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1518028] Re: [Scopes] Carousel showing pictures that were deleted
** Attachment added: "DSC_1661.JPG" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1518028/+attachment/4522238/+files/DSC_1661.JPG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1518028 Title: [Scopes] Carousel showing pictures that were deleted Status in unity8 package in Ubuntu: New Bug description: The pictures stored in the sdcard are displayed in the photos carousel after those were deleted Steps: 1. Copy a bunch of pictures from my desktop through mtp to the sd card pictures dir 2. Go to photos scope (the pictures are shown in the carousel) 3. Click on "My photos", all the pictures appear in the my photos screen 4. Using nautilus delete all the pictures from the device sdcard 5. In the device go to the photos scope and refresh the scope manually 6. The pictures are still in the carousel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1518028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429988] Re: Preview and photos are unfocused
I noticed that when I have the camera-app opened and then lock and unlock the krillin, the camera is not doing auto focus any more as it was doing that few builds ago. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1429988 Title: Preview and photos are unfocused Status in camera-app: Confirmed Status in camera-app package in Ubuntu: Confirmed Bug description: BQ Aquarius running stable rtm The camera can get in a state where it can no longer properly focus on the image. The preview shows a fuzzy image which is also the case with the pictures taken. Rebooting the phone does not correct this. (this was reproduced once by switching front and back cameras but it corrected with another switch) To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1429988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1513600] Re: [Scopes] Music scope blank using url-dispatcher
** Description changed: Sporadically I get a blank page when I use the url-dispatcher to go to the music scope. The same issue has been reproduced going to the photos scope. After go to the scope I am waiting until the scope header is loaded and the loading bar has disappeared. To go to both affected scopes we I am doing: > url-dispatcher scope://musicaggregator > url-dispatcher scope://com.canonical.scopes.photos_photos + + I see a similar behavior when from the music scope I go to an online + music scope such as "7 digital". What I see is that the 7digital scope + doesn't show any data. I checked there is internet in the device. ** Attachment added: "FailedTestScreenshot (1).png" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1513600/+attachment/4516838/+files/FailedTestScreenshot%20%281%29.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1513600 Title: [Scopes] Music scope blank using url-dispatcher Status in unity8 package in Ubuntu: New Bug description: Sporadically I get a blank page when I use the url-dispatcher to go to the music scope. The same issue has been reproduced going to the photos scope. After go to the scope I am waiting until the scope header is loaded and the loading bar has disappeared. To go to both affected scopes we I am doing: > url-dispatcher scope://musicaggregator > url-dispatcher scope://com.canonical.scopes.photos_photos I see a similar behavior when from the music scope I go to an online music scope such as "7 digital". What I see is that the 7digital scope doesn't show any data. I checked there is internet in the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1513600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1513600] [NEW] [Scopes] Music scope blank using url-dispatcher
Public bug reported: Sporadically I get a blank page when I use the url-dispatcher to go to the music scope. The same issue has been reproduced going to the photos scope. After go to the scope I am waiting until the scope header is loaded and the loading bar has disappeared. To go to both affected scopes we I am doing: > url-dispatcher scope://musicaggregator > url-dispatcher scope://com.canonical.scopes.photos_photos ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Description changed: Sporadically I get a blank page when I use the url-dispatcher to go to the music scope. The same issue has been reproduced going to the photos scope. + After go to the scope I am waiting until the scope header is loaded and + the loading bar has disappeared. + To go to both affected scopes we I am doing: - > url-dispatcher scope://musicaggregator - > url-dispatcher scope://com.canonical.scopes.photos_photos + > url-dispatcher scope://musicaggregator + > url-dispatcher scope://com.canonical.scopes.photos_photos -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1513600 Title: [Scopes] Music scope blank using url-dispatcher Status in unity8 package in Ubuntu: New Bug description: Sporadically I get a blank page when I use the url-dispatcher to go to the music scope. The same issue has been reproduced going to the photos scope. After go to the scope I am waiting until the scope header is loaded and the loading bar has disappeared. To go to both affected scopes we I am doing: > url-dispatcher scope://musicaggregator > url-dispatcher scope://com.canonical.scopes.photos_photos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1513600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1513600] Re: [Scopes] Music scope blank using url-dispatcher
** Attachment added: "DSC_1649.JPG" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1513600/+attachment/4513680/+files/DSC_1649.JPG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1513600 Title: [Scopes] Music scope blank using url-dispatcher Status in unity8 package in Ubuntu: New Bug description: Sporadically I get a blank page when I use the url-dispatcher to go to the music scope. The same issue has been reproduced going to the photos scope. After go to the scope I am waiting until the scope header is loaded and the loading bar has disappeared. To go to both affected scopes we I am doing: > url-dispatcher scope://musicaggregator > url-dispatcher scope://com.canonical.scopes.photos_photos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1513600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1513600] Re: [Scopes] Music scope blank using url-dispatcher
** Attachment added: "DSC_1650.JPG" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1513600/+attachment/4513679/+files/DSC_1650.JPG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1513600 Title: [Scopes] Music scope blank using url-dispatcher Status in unity8 package in Ubuntu: New Bug description: Sporadically I get a blank page when I use the url-dispatcher to go to the music scope. The same issue has been reproduced going to the photos scope. After go to the scope I am waiting until the scope header is loaded and the loading bar has disappeared. To go to both affected scopes we I am doing: > url-dispatcher scope://musicaggregator > url-dispatcher scope://com.canonical.scopes.photos_photos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1513600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483855] [NEW] Getting assertion 'db != NULL' failed when using the url dispatcher
Public bug reported: Trying to use the url dispatcher I got this error when trying to go to this url and other too: ** (process:31929): WARNING **: Unable to dispatch url 'scope://com.canonical.scopes.photos_photos':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'scope://com.canonical.scopes.photos_photos' is not handleable by the URL Dispatcher then in the log I found this: ** (process:2011): WARNING **: Unable to create tables: database is locked ** (process:2011): CRITICAL **: url_db_find_url: assertion 'db != NULL' failed After all, ted suggested that restarting the url dispatcher would work and it did. ** Affects: url-dispatcher (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1483855 Title: Getting assertion 'db != NULL' failed when using the url dispatcher Status in url-dispatcher package in Ubuntu: New Bug description: Trying to use the url dispatcher I got this error when trying to go to this url and other too: ** (process:31929): WARNING **: Unable to dispatch url 'scope://com.canonical.scopes.photos_photos':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'scope://com.canonical.scopes.photos_photos' is not handleable by the URL Dispatcher then in the log I found this: ** (process:2011): WARNING **: Unable to create tables: database is locked ** (process:2011): CRITICAL **: url_db_find_url: assertion 'db != NULL' failed After all, ted suggested that restarting the url dispatcher would work and it did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1483855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483854] [NEW] Getting assertion 'db != NULL' failed when using the url dispatcher
Public bug reported: Trying to use the url dispatcher I got this error when trying to go to this url and other too: ** (process:31929): WARNING **: Unable to dispatch url 'scope://com.canonical.scopes.photos_photos':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'scope://com.canonical.scopes.photos_photos' is not handleable by the URL Dispatcher then in the log I found this: ** (process:2011): WARNING **: Unable to create tables: database is locked ** (process:2011): CRITICAL **: url_db_find_url: assertion 'db != NULL' failed After all, ted suggested that restarting the url dispatcher would work and it did. ** Affects: url-dispatcher (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1483854 Title: Getting assertion 'db != NULL' failed when using the url dispatcher Status in url-dispatcher package in Ubuntu: New Bug description: Trying to use the url dispatcher I got this error when trying to go to this url and other too: ** (process:31929): WARNING **: Unable to dispatch url 'scope://com.canonical.scopes.photos_photos':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'scope://com.canonical.scopes.photos_photos' is not handleable by the URL Dispatcher then in the log I found this: ** (process:2011): WARNING **: Unable to create tables: database is locked ** (process:2011): CRITICAL **: url_db_find_url: assertion 'db != NULL' failed After all, ted suggested that restarting the url dispatcher would work and it did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1483854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1472789] [NEW] libmtp error copying big files
Public bug reported: An error message is shown when trying to copy a file of 3GB from my ubuntu desktop to my krillin phone using Nautilus. Steps to reproduce: 1. Plug a krillin device 2. Create a file with dd if=/dev/urandom of=/tmp/bigfile.txt bs=1024 count=300 3. Using Nautilus, copy the file to the Documents directory in the device In my machine it is happening that after that 2.1 GB are copied the process does not copy more content and an error screen appears (see atached). The error displayed is: libmtp error: Could not send object The free space in my device is about 3.7 GB My desktop os: Ubuntu 15.04 My krilling version is: 58 (rc-proposed) ** Affects: mtp (Ubuntu) Importance: Undecided Status: New ** Attachment added: error_screen_mtp.png https://bugs.launchpad.net/bugs/1472789/+attachment/4426573/+files/error_screen_mtp.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1472789 Title: libmtp error copying big files Status in mtp package in Ubuntu: New Bug description: An error message is shown when trying to copy a file of 3GB from my ubuntu desktop to my krillin phone using Nautilus. Steps to reproduce: 1. Plug a krillin device 2. Create a file with dd if=/dev/urandom of=/tmp/bigfile.txt bs=1024 count=300 3. Using Nautilus, copy the file to the Documents directory in the device In my machine it is happening that after that 2.1 GB are copied the process does not copy more content and an error screen appears (see atached). The error displayed is: libmtp error: Could not send object The free space in my device is about 3.7 GB My desktop os: Ubuntu 15.04 My krilling version is: 58 (rc-proposed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1472789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1464014] Re: Exception raised executing _get_current_page_header in the last scope in Krilling
What I had to do in my code is to overwrite the medhod get_scope_title which it is located in unity8.shell.emulators.dash because it was raising an exception when it tries to access to the isCurrent property of a QQuickLoader which hasn't this property. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1464014 Title: Exception raised executing _get_current_page_header in the last scope in Krilling Status in unity8 package in Ubuntu: New Bug description: I am testing using the krilling (vivid version) phone using the Dash class in unit8/shell/emulators/dash.py. I created a method to go through all the scopes (from today until photos) verifying that the titles are correct. When I execute the method _get_current_page_header being in the last scope (photos), then the following exception is raised. Traceback (most recent call last): File /home/phablet/test/ubuntu_system_tests/tests/test_scopes.py, line 56, in test_default_scopes print(dash.get_scope_title()) File /home/phablet/test/ubuntu_system_tests/helpers/unity8/dash.py, line 74, in get_scope_title return self._get_current_page_header().title File /usr/lib/python3/dist-packages/unity8/shell/emulators/dash.py, line 182, in _get_current_page_header if i.isCurrent: File /usr/lib/python3/dist-packages/autopilot/introspection/dbus.py, line 416, in __getattr__ (self.__class__.__name__, name)) AttributeError: Class 'QQuickLoader' has no attribute 'isCurrent'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1464014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1464014] Re: Exception raised executing _get_current_page_header in the last scope in Krilling
Hi, I executed in the last image and it is working this test. But the error that I mentioned in the bug is still happening In the following merge proposal you can find the test that I did which has overwritten the method get_scope_title. It fails when there is a QQuickLoader that has not the isCurrent attribute. https://code.launchpad.net/~canonical-platform-qa/ubuntu-system- tests/test_sanity_default_scopes/+merge/261678 The information of the image used is the following: phablet@ubuntu-phablet:~/test$ system-image-cli -i current build number: 46 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-06-22 18:29:03 version version: 46 version ubuntu: 20150622.1 version device: 20150529-8e13c5f version custom: 20150528-722-29-15-vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1464014 Title: Exception raised executing _get_current_page_header in the last scope in Krilling Status in unity8 package in Ubuntu: New Bug description: I am testing using the krilling (vivid version) phone using the Dash class in unit8/shell/emulators/dash.py. I created a method to go through all the scopes (from today until photos) verifying that the titles are correct. When I execute the method _get_current_page_header being in the last scope (photos), then the following exception is raised. Traceback (most recent call last): File /home/phablet/test/ubuntu_system_tests/tests/test_scopes.py, line 56, in test_default_scopes print(dash.get_scope_title()) File /home/phablet/test/ubuntu_system_tests/helpers/unity8/dash.py, line 74, in get_scope_title return self._get_current_page_header().title File /usr/lib/python3/dist-packages/unity8/shell/emulators/dash.py, line 182, in _get_current_page_header if i.isCurrent: File /usr/lib/python3/dist-packages/autopilot/introspection/dbus.py, line 416, in __getattr__ (self.__class__.__name__, name)) AttributeError: Class 'QQuickLoader' has no attribute 'isCurrent'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1464014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1464014] Re: Exception raised executing _get_current_page_header in the last scope in Krilling
I am getting this error when I execute this test in the krilling
Traceback (most recent call last):
File /usr/lib/python3/dist-packages/unity8/shell/tests/test_emulators.py,
line 51, in test_search
self.dash.enter_search_query('Test')
File /usr/lib/python3/dist-packages/unity8/shell/emulators/dash.py, line
172, in enter_search_query
objectName=processingIndicator).visible.wait_for(False)
File /usr/lib/python3/dist-packages/autopilot/introspection/types.py, line
180, in wait_for
failure_msg))
AssertionError: After 10.0 seconds test on QQuickRectangle.visible failed:
False != dbus.Boolean(True, variant_level=1)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1464014
Title:
Exception raised executing _get_current_page_header in the last scope
in Krilling
Status in unity8 package in Ubuntu:
New
Bug description:
I am testing using the krilling (vivid version) phone using the Dash
class in unit8/shell/emulators/dash.py. I created a method to go
through all the scopes (from today until photos) verifying that the
titles are correct. When I execute the method _get_current_page_header
being in the last scope (photos), then the following exception is
raised.
Traceback (most recent call last):
File /home/phablet/test/ubuntu_system_tests/tests/test_scopes.py, line
56, in test_default_scopes
print(dash.get_scope_title())
File /home/phablet/test/ubuntu_system_tests/helpers/unity8/dash.py, line
74, in get_scope_title
return self._get_current_page_header().title
File /usr/lib/python3/dist-packages/unity8/shell/emulators/dash.py, line
182, in _get_current_page_header
if i.isCurrent:
File /usr/lib/python3/dist-packages/autopilot/introspection/dbus.py, line
416, in __getattr__
(self.__class__.__name__, name))
AttributeError: Class 'QQuickLoader' has no attribute 'isCurrent'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1464014/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1464014] [NEW] Exception raised executing _get_current_page_header in the last scope in Krilling
Public bug reported: I am testing using the krilling (vivid version) phone using the Dash class in unit8/shell/emulators/dash.py. I created a method to go through all the scopes (from today until photos) verifying that the titles are correct. When I execute the method _get_current_page_header being in the last scope (photos), then the following exception is raised. Traceback (most recent call last): File /home/phablet/test/ubuntu_system_tests/tests/test_scopes.py, line 56, in test_default_scopes print(dash.get_scope_title()) File /home/phablet/test/ubuntu_system_tests/helpers/unity8/dash.py, line 74, in get_scope_title return self._get_current_page_header().title File /usr/lib/python3/dist-packages/unity8/shell/emulators/dash.py, line 182, in _get_current_page_header if i.isCurrent: File /usr/lib/python3/dist-packages/autopilot/introspection/dbus.py, line 416, in __getattr__ (self.__class__.__name__, name)) AttributeError: Class 'QQuickLoader' has no attribute 'isCurrent'. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1464014 Title: Exception raised executing _get_current_page_header in the last scope in Krilling Status in unity8 package in Ubuntu: New Bug description: I am testing using the krilling (vivid version) phone using the Dash class in unit8/shell/emulators/dash.py. I created a method to go through all the scopes (from today until photos) verifying that the titles are correct. When I execute the method _get_current_page_header being in the last scope (photos), then the following exception is raised. Traceback (most recent call last): File /home/phablet/test/ubuntu_system_tests/tests/test_scopes.py, line 56, in test_default_scopes print(dash.get_scope_title()) File /home/phablet/test/ubuntu_system_tests/helpers/unity8/dash.py, line 74, in get_scope_title return self._get_current_page_header().title File /usr/lib/python3/dist-packages/unity8/shell/emulators/dash.py, line 182, in _get_current_page_header if i.isCurrent: File /usr/lib/python3/dist-packages/autopilot/introspection/dbus.py, line 416, in __getattr__ (self.__class__.__name__, name)) AttributeError: Class 'QQuickLoader' has no attribute 'isCurrent'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1464014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1463559] [NEW] Incorrect file digest when it is downloaded through webbrowser-app with touch
Public bug reported: I download an image from a webpage and the sha1 digest is not the same than the original. It is happening at least in the krilling (touch). I tested this scenario with different images and always it is happening the same. Steps to reproduce: 1. Go to lillypilly.canonical.com/~platform-qa/page3.html 2. Touch in the ubuntu image 3. Select Save image 4. Select to open with the Galery 5. Once it is downloaded, press open 6. The file is in ~/Pictures/ubuntu.jpg The file sha1 digest is 7cad64e34de2eebe73b49756b09a50a4a1948c7a The original sha1 digest is 429cbd692c4abd3e5c785edf5dcf0993d21076b1 If you download the image either with chrome or firefox, the obtained digest is the correct one. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1463559 Title: Incorrect file digest when it is downloaded through webbrowser-app with touch Status in webbrowser-app package in Ubuntu: New Bug description: I download an image from a webpage and the sha1 digest is not the same than the original. It is happening at least in the krilling (touch). I tested this scenario with different images and always it is happening the same. Steps to reproduce: 1. Go to lillypilly.canonical.com/~platform-qa/page3.html 2. Touch in the ubuntu image 3. Select Save image 4. Select to open with the Galery 5. Once it is downloaded, press open 6. The file is in ~/Pictures/ubuntu.jpg The file sha1 digest is 7cad64e34de2eebe73b49756b09a50a4a1948c7a The original sha1 digest is 429cbd692c4abd3e5c785edf5dcf0993d21076b1 If you download the image either with chrome or firefox, the obtained digest is the correct one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1463559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
