[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-06-25 Thread Seth Arnold
Ron, you look at the profiles that failed to compile/load in the journalctl -u apparmor output, and decide what to do with those profiles -- if they are for programs that no longer exist because the package has since been removed, you can just delete the profile file. If they are for programs that

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-06-25 Thread Ron
This may be a dumb question, but once we *have* this bug, how do we fix it? I'm not that practiced at apparmor. -- 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/1756800

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-05-28 Thread Christian Boltz
Looks like you have a syntax error in /etc/apparmor.d/tunables/multiarch around line 13. Can you please attach this file? Also, did you modify it manually? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu.

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-05-27 Thread marsteegh
I have a similar issue, getting these messages from apparmor: May 28 06:52:02 bureau apparmor[993]: AppArmor parser error for /etc/apparmor.d/usr.sbin.nscd in /etc/apparmor.d/tunables/multiarch at line 13: syntax error, unexpected TOK_EQUALS, expecting TOK_OPEN May 28 06:52:02 bureau

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-04-04 Thread Jamie Strandboge
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1761176 filed for messaging-app. -- 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/1756800 Title: Failed to start

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-04-04 Thread Jamie Strandboge
Actually, only messaging-app is affected by this bug, so we don't need to remove the other two. -- 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/1756800 Title: Failed to

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-04-04 Thread Jamie Strandboge
"Do we need to worry about: ubuntu-download-manager: /etc/apparmor.d/usr.lib.ubuntu-download-manager.udm-extractor messaging-app: /etc/apparmor.d/usr.bin.messaging-app content-hub-testability: /etc/apparmor.d/content-hub-testability " Yes. I did an archive grep and found media-hub, but that

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package apparmor - 2.12-4ubuntu3 --- apparmor (2.12-4ubuntu3) bionic; urgency=medium * Remove old Ubuntu Touch profiles for packages removed from the archive since they need apparmor-easyprof-ubuntu to compile, and it was also removed from the

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-04-03 Thread Seth Arnold
$ diff -u <(grep etc/apparmor.d Contents-xenial | awk '{print $1}') <(grep etc/apparmor.d Contents-bionic | awk '{print $1}') --- /dev/fd/63 2018-04-03 17:45:57.438698038 -0700 +++ /dev/fd/62 2018-04-03 17:45:57.438698038 -0700 @@ -23,16 +23,19 @@ etc/apparmor.d/abstractions/enchant

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-04-03 Thread Seth Arnold
Do we need to worry about: ubuntu-download-manager: /etc/apparmor.d/usr.lib.ubuntu-download-manager.udm-extractor messaging-app: /etc/apparmor.d/usr.bin.messaging-app content-hub-testability: /etc/apparmor.d/content-hub-testability Thanks -- You received this bug notification because you are

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-04-03 Thread Steve Langasek
** Changed in: apparmor (Ubuntu) Importance: Undecided => Medium -- 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/1756800 Title: Failed to start AppArmor initialization

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-04-03 Thread Jamie Strandboge
Uploaded 2.12-4ubuntu3 to address this. -- 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/1756800 Title: Failed to start AppArmor initialization with status=123/n/a Status

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-04-03 Thread Jamie Strandboge
media-hub is another application that was removed in bionic that is affected. ** Changed in: apparmor (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu.

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-04-03 Thread Jamie Strandboge
** Changed in: apparmor (Ubuntu) Status: Won't Fix => In Progress ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-03-29 Thread Seth Arnold
Infinity suggests: - Versioned breaks from apparmor against the other two packages - Using the apparmor maintainer scripts to remove the conffiles Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu.

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-03-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu.

Re: [Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-03-20 Thread Seth Arnold
On Wed, Mar 21, 2018 at 12:46:04AM -, Rocko wrote: > Thanks, removing the packages makes the errors go away. Good, I'm glad to hear this worked. > Do you think the error message is misleading? Instead of saying "Failed > to start AppArmor initialization", perhaps it should say, "Failed to >

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-03-20 Thread Rocko
Thanks, removing the packages makes the errors go away. Do you think the error message is misleading? Instead of saying "Failed to start AppArmor initialization", perhaps it should say, "Failed to load some profiles"? -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-03-20 Thread Jamie Strandboge
This isn't really a bug in apparmor-- the profiles weren't purged from the system. We could perhaps add a Conflicts on webbrowser-app mediascanner2.0 to apparmor, but that doesn't feel right (and wouldn't remove the conffiles anyway (so this bug would remain)). Perhaps ubuntu- release-upgrader

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-03-20 Thread Jamie Strandboge
No, the script is returning non-zero because some of the profiles didn't load, but the rest of the profiles will load fine. You can prove this to yourself using 'sudo aa-status'. As for those two profiles, the come from https://launchpad.net/ubuntu/+source/webbrowser-app/ and

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-03-20 Thread Rocko
I get this: $ sudo apparmor_parser --replace /etc/apparmor.d/usr.bin.webbrowser-app AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open '/usr/share/apparmor/hardware/graphics.d' $ sudo apparmor_parser --replace

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-03-19 Thread Seth Arnold
Hello Rocko, Can you try the following? sudo apparmor_parser --replace /etc/apparmor.d/usr.bin.webbrowser-app sudo apparmor_parser --replace /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor Thanks -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

2018-03-19 Thread Rocko
Another user reported what sounds like the same issue at https://ubuntuforums.org/showthread.php?t=2386129=13749658#post13749658 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu.