[Touch-packages] [Bug 1767795] Re: Error Message

2018-05-23 Thread Christopher M. Penalver
** Package changed: xorg (Ubuntu) => apparmor (Ubuntu) -- 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/1767795 Title: Error Message Status in apparmor package in Ubuntu:

[Touch-packages] [Bug 1767795] Re: Error Message

2018-05-23 Thread Seth Arnold
Philipp, can you please run: apport-collect 1767795 to get the apparmor-related artifacts? Thanks -- 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/1767795 Title: Error M

[Touch-packages] [Bug 1767795] Re: Error Message

2018-06-03 Thread Philipp Batram
apport information ** Tags added: apport-collected ** Description changed: By starting the system in the long list of terms it shows one FAILED. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.

[Touch-packages] [Bug 1767795] Re: Error Message

2018-06-04 Thread Seth Arnold
Hrm, I thought the logged information would include status on which profile failed to start. Bummer. If you run: sudo /etc/init.d/apparmor reload do you get any error messages there? Please paste the output here. Thanks -- You received this bug notification because you are a member of Ubuntu T

Re: [Touch-packages] [Bug 1767795] Re: Error Message

2018-06-03 Thread Philipp Batram
Hi Seth, I did like you said. Thanks for helping! Am 24.05.2018 um 00:37 schrieb Seth Arnold: > Philipp, can you please run: > > apport-collect 1767795 > > to get the apparmor-related artifacts? > > Thanks > -- You received this bug notification because you are a member of Ubuntu Touch seeded

Re: [Touch-packages] [Bug 1767795] Re: Error Message

2018-06-05 Thread Philipp Batram
[] Reloading apparmor configuration (via systemctl): apparmor.serviceapparmor.service is not active, cannot reload.  failed! Am 04.06.2018 um 23:35 schrieb Seth Arnold: > Hrm, I thought the logged information would include status on which > profile failed to start. Bummer. > > If you run: