[Touch-packages] [Bug 1660316] Re: apparmor denial of CUPS

2020-06-09 Thread Arie Skliarouk
Looks like the same error in ubuntu 20.04: Jun 5 00:00:07 cmdesk01 kernel: [4025941.209572] audit: type=1400 audit(1591304407.264:388): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=1792223 comm="cups-browsed" capability=23 capname="sys_nice" -- You received this

[Touch-packages] [Bug 1852903] Re: systemd Caught , dumped core

2020-02-02 Thread Arie Skliarouk
Yes, it is our custom service: # cat /var/tmp/keepsessions.service [Unit] Description=SiteTools keep sessions Wants=network-online.target Wants=docker.service After=network-online.target After=docker.service [Service] ExecStart=/opt/sitetools/keepsessions ExecStartPost=/opt/sitetools/onstart

[Touch-packages] [Bug 1852903] Re: systemd Caught , dumped core

2019-11-18 Thread Arie Skliarouk
** Attachment added: "/var/crash/_lib_systemd_systemd.0.crash" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852903/+attachment/5306190/+files/_lib_systemd_systemd.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1852903] Re: systemd Caught , dumped core

2019-11-17 Thread Arie Skliarouk
This started happening after automatic upgrade: 2019-11-14 06:57:49 startup packages remove 2019-11-14 06:57:49 status installed linux-image-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:50 remove linux-image-4.15.0-1051-aws:amd64 4.15.0-1051.53 2019-11-14 06:57:50 status

[Touch-packages] [Bug 1852903] Re: systemd Caught , dumped core

2019-11-17 Thread Arie Skliarouk
** Attachment added: "systemd 237-3ubuntu10.31 coredump (amd64)" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852903/+attachment/5306050/+files/core.systemd.2982.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed

[Touch-packages] [Bug 1852903] [NEW] systemd Caught , dumped core

2019-11-17 Thread Arie Skliarouk
Public bug reported: Several days ago an ubuntu 18.04 in ec2 env updated systemd and udev to 237-3ubuntu10.31 This caused systemd to segfault and stop receiving any systemctl command (they timeout). [ 198.482652] systemd[1]: segfault at 50 ip 5630ddd60200 sp 7ffc9c3ea890 error 4 in