Apparmor Init Failed, Exit Code 123











up vote
9
down vote

favorite
4












Apparmor fails boot and command line start with same result as below



x@x-NICEPUTER:~$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● apparmor.service loaded failed failed LSB: AppArmor initialization

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

x@x-NICEPUTER:~$ systemctl status apparmor.service
● apparmor.service - LSB: AppArmor initialization
Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2016-05-03 21:52:29 MDT; 1h 15min ago
Docs: man:systemd-sysv-generator(8)
Process: 523 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)

May 03 21:52:22 x-NICEPUTER apparmor[523]: 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'
May 03 21:52:28 x-NICEPUTER apparmor[523]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
May 03 21:52:29 x-NICEPUTER apparmor[523]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
May 03 21:52:29 x-NICEPUTER apparmor[523]: 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'
May 03 21:52:29 x-NICEPUTER apparmor[523]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
May 03 21:52:29 x-NICEPUTER apparmor[523]: ...fail!
May 03 21:52:29 x-NICEPUTER systemd[1]: apparmor.service: Control process exited, code=exited status=123
May 03 21:52:29 x-NICEPUTER systemd[1]: Failed to start LSB: AppArmor initialization.
May 03 21:52:29 x-NICEPUTER systemd[1]: apparmor.service: Unit entered failed state.
May 03 21:52:29 x-NICEPUTER systemd[1]: apparmor.service: Failed with result 'exit-code'.


Directories apparmor/hardware/ and file graphics.d do not exist inside /usr/share/
Thus #include /usr/share/apparmor/hardware/graphics.d at line 26 of /etc/apparmor.d/usr.bin.webbrowser-app returns null and causes the failure.



How can I properly fix this or at the least create a workaround that allows apparmor.service to intialize without a failure?



uname -a
Linux x-NICEPUTER 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
sudo lshw
[sudo] password for x:
x-niceputer
description: Computer
width: 64 bits
capabilities: smbios-2.4 vsyscall32
*-core
description: Motherboard
physical id: 0
*-memory
description: System memory
physical id: 0
size: 3793MiB
*-cpu
product: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz









share|improve this question


























    up vote
    9
    down vote

    favorite
    4












    Apparmor fails boot and command line start with same result as below



    x@x-NICEPUTER:~$ systemctl --failed
    UNIT LOAD ACTIVE SUB DESCRIPTION
    ● apparmor.service loaded failed failed LSB: AppArmor initialization

    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.

    1 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.

    x@x-NICEPUTER:~$ systemctl status apparmor.service
    ● apparmor.service - LSB: AppArmor initialization
    Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
    Active: failed (Result: exit-code) since Tue 2016-05-03 21:52:29 MDT; 1h 15min ago
    Docs: man:systemd-sysv-generator(8)
    Process: 523 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)

    May 03 21:52:22 x-NICEPUTER apparmor[523]: 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'
    May 03 21:52:28 x-NICEPUTER apparmor[523]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
    May 03 21:52:29 x-NICEPUTER apparmor[523]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
    May 03 21:52:29 x-NICEPUTER apparmor[523]: 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'
    May 03 21:52:29 x-NICEPUTER apparmor[523]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
    May 03 21:52:29 x-NICEPUTER apparmor[523]: ...fail!
    May 03 21:52:29 x-NICEPUTER systemd[1]: apparmor.service: Control process exited, code=exited status=123
    May 03 21:52:29 x-NICEPUTER systemd[1]: Failed to start LSB: AppArmor initialization.
    May 03 21:52:29 x-NICEPUTER systemd[1]: apparmor.service: Unit entered failed state.
    May 03 21:52:29 x-NICEPUTER systemd[1]: apparmor.service: Failed with result 'exit-code'.


    Directories apparmor/hardware/ and file graphics.d do not exist inside /usr/share/
    Thus #include /usr/share/apparmor/hardware/graphics.d at line 26 of /etc/apparmor.d/usr.bin.webbrowser-app returns null and causes the failure.



    How can I properly fix this or at the least create a workaround that allows apparmor.service to intialize without a failure?



    uname -a
    Linux x-NICEPUTER 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
    sudo lshw
    [sudo] password for x:
    x-niceputer
    description: Computer
    width: 64 bits
    capabilities: smbios-2.4 vsyscall32
    *-core
    description: Motherboard
    physical id: 0
    *-memory
    description: System memory
    physical id: 0
    size: 3793MiB
    *-cpu
    product: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz









    share|improve this question
























      up vote
      9
      down vote

      favorite
      4









      up vote
      9
      down vote

      favorite
      4






      4





      Apparmor fails boot and command line start with same result as below



      x@x-NICEPUTER:~$ systemctl --failed
      UNIT LOAD ACTIVE SUB DESCRIPTION
      ● apparmor.service loaded failed failed LSB: AppArmor initialization

      LOAD = Reflects whether the unit definition was properly loaded.
      ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
      SUB = The low-level unit activation state, values depend on unit type.

      1 loaded units listed. Pass --all to see loaded but inactive units, too.
      To show all installed unit files use 'systemctl list-unit-files'.

      x@x-NICEPUTER:~$ systemctl status apparmor.service
      ● apparmor.service - LSB: AppArmor initialization
      Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
      Active: failed (Result: exit-code) since Tue 2016-05-03 21:52:29 MDT; 1h 15min ago
      Docs: man:systemd-sysv-generator(8)
      Process: 523 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)

      May 03 21:52:22 x-NICEPUTER apparmor[523]: 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'
      May 03 21:52:28 x-NICEPUTER apparmor[523]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
      May 03 21:52:29 x-NICEPUTER apparmor[523]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
      May 03 21:52:29 x-NICEPUTER apparmor[523]: 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'
      May 03 21:52:29 x-NICEPUTER apparmor[523]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
      May 03 21:52:29 x-NICEPUTER apparmor[523]: ...fail!
      May 03 21:52:29 x-NICEPUTER systemd[1]: apparmor.service: Control process exited, code=exited status=123
      May 03 21:52:29 x-NICEPUTER systemd[1]: Failed to start LSB: AppArmor initialization.
      May 03 21:52:29 x-NICEPUTER systemd[1]: apparmor.service: Unit entered failed state.
      May 03 21:52:29 x-NICEPUTER systemd[1]: apparmor.service: Failed with result 'exit-code'.


      Directories apparmor/hardware/ and file graphics.d do not exist inside /usr/share/
      Thus #include /usr/share/apparmor/hardware/graphics.d at line 26 of /etc/apparmor.d/usr.bin.webbrowser-app returns null and causes the failure.



      How can I properly fix this or at the least create a workaround that allows apparmor.service to intialize without a failure?



      uname -a
      Linux x-NICEPUTER 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
      sudo lshw
      [sudo] password for x:
      x-niceputer
      description: Computer
      width: 64 bits
      capabilities: smbios-2.4 vsyscall32
      *-core
      description: Motherboard
      physical id: 0
      *-memory
      description: System memory
      physical id: 0
      size: 3793MiB
      *-cpu
      product: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz









      share|improve this question













      Apparmor fails boot and command line start with same result as below



      x@x-NICEPUTER:~$ systemctl --failed
      UNIT LOAD ACTIVE SUB DESCRIPTION
      ● apparmor.service loaded failed failed LSB: AppArmor initialization

      LOAD = Reflects whether the unit definition was properly loaded.
      ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
      SUB = The low-level unit activation state, values depend on unit type.

      1 loaded units listed. Pass --all to see loaded but inactive units, too.
      To show all installed unit files use 'systemctl list-unit-files'.

      x@x-NICEPUTER:~$ systemctl status apparmor.service
      ● apparmor.service - LSB: AppArmor initialization
      Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
      Active: failed (Result: exit-code) since Tue 2016-05-03 21:52:29 MDT; 1h 15min ago
      Docs: man:systemd-sysv-generator(8)
      Process: 523 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)

      May 03 21:52:22 x-NICEPUTER apparmor[523]: 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'
      May 03 21:52:28 x-NICEPUTER apparmor[523]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
      May 03 21:52:29 x-NICEPUTER apparmor[523]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
      May 03 21:52:29 x-NICEPUTER apparmor[523]: 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'
      May 03 21:52:29 x-NICEPUTER apparmor[523]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
      May 03 21:52:29 x-NICEPUTER apparmor[523]: ...fail!
      May 03 21:52:29 x-NICEPUTER systemd[1]: apparmor.service: Control process exited, code=exited status=123
      May 03 21:52:29 x-NICEPUTER systemd[1]: Failed to start LSB: AppArmor initialization.
      May 03 21:52:29 x-NICEPUTER systemd[1]: apparmor.service: Unit entered failed state.
      May 03 21:52:29 x-NICEPUTER systemd[1]: apparmor.service: Failed with result 'exit-code'.


      Directories apparmor/hardware/ and file graphics.d do not exist inside /usr/share/
      Thus #include /usr/share/apparmor/hardware/graphics.d at line 26 of /etc/apparmor.d/usr.bin.webbrowser-app returns null and causes the failure.



      How can I properly fix this or at the least create a workaround that allows apparmor.service to intialize without a failure?



      uname -a
      Linux x-NICEPUTER 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
      sudo lshw
      [sudo] password for x:
      x-niceputer
      description: Computer
      width: 64 bits
      capabilities: smbios-2.4 vsyscall32
      *-core
      description: Motherboard
      physical id: 0
      *-memory
      description: System memory
      physical id: 0
      size: 3793MiB
      *-cpu
      product: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz






      boot security 16.04 systemd apparmor






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked May 4 '16 at 6:14









      xtrchessreal

      5911720




      5911720






















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          17
          down vote



          accepted










          Seems to be a reported bug (#1554803)



          It can be solved installing apparmor-easyprof-ubuntu or creating the folders by hand.



          sudo apt-get install apparmor-easyprof-ubuntu





          share|improve this answer























          • Would you mind expanding your answer and providing the proper steps to install the package you are referring to or to create the necessary folders. I looked at the bug it is indeed the same I see. Thank you :)
            – xtrchessreal
            May 4 '16 at 22:54










          • how this solving this problem ?
            – Ebuzer Taha KANAT
            Feb 27 '17 at 23:42






          • 1




            @EbuzerTahaKANAT I don't think this solves the AppArmor problem but provides a way to keep systemd from failing AppArmor initialization on boot. I built the folders and empty files by hand and, I ran the installation of apparmor-easyprof-ubuntu. Files (video.d, graphics.d, and audio.d) are still empty in my system and boot no longer records a fail code. These files are supposed to contain AppArmor policy code, I think, its a guess based on first line here launchpad.net/apparmor-easyprof-ubuntu Not sure if Apparmor protects these devices? Bug still open!
            – xtrchessreal
            Apr 12 '17 at 19:13












          • For me, I was unable to install any package because ifconfig and network-manager would not load (I have a USB wifi dongle). So @xtrchessreal 's suggestion is what worked.
            – midopa
            Dec 13 '17 at 6:14




















          up vote
          2
          down vote













          For me, I couldn't install any packages because both ifconfig and network-manager could not find/start my USB wifi dongle.



          So @xtrchessreal's comment is what worked for me:



          In the recovery mode shell, create the following directories:



          mkdir -p /usr/share/apparmor/hardware/graphics.d
          mkdir -p /usr/share/apparmor/hardware/audio.d
          mkdir -p /usr/share/apparmor/hardware/video.d


          And then reboot






          share|improve this answer























          • apparmor-easyprof-ubuntu IMPORTANT: this project is no longer actively maintained by the Ubuntu Security team of Canonical. Per launchpad.net/apparmor-easyprof-ubuntu I wonder if it maintained elsewhere?
            – xtrchessreal
            Dec 13 '17 at 20:34












          • Good to know! I'm just going to remove it from the answer then.
            – midopa
            Dec 25 '17 at 8:37











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f767272%2fapparmor-init-failed-exit-code-123%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          17
          down vote



          accepted










          Seems to be a reported bug (#1554803)



          It can be solved installing apparmor-easyprof-ubuntu or creating the folders by hand.



          sudo apt-get install apparmor-easyprof-ubuntu





          share|improve this answer























          • Would you mind expanding your answer and providing the proper steps to install the package you are referring to or to create the necessary folders. I looked at the bug it is indeed the same I see. Thank you :)
            – xtrchessreal
            May 4 '16 at 22:54










          • how this solving this problem ?
            – Ebuzer Taha KANAT
            Feb 27 '17 at 23:42






          • 1




            @EbuzerTahaKANAT I don't think this solves the AppArmor problem but provides a way to keep systemd from failing AppArmor initialization on boot. I built the folders and empty files by hand and, I ran the installation of apparmor-easyprof-ubuntu. Files (video.d, graphics.d, and audio.d) are still empty in my system and boot no longer records a fail code. These files are supposed to contain AppArmor policy code, I think, its a guess based on first line here launchpad.net/apparmor-easyprof-ubuntu Not sure if Apparmor protects these devices? Bug still open!
            – xtrchessreal
            Apr 12 '17 at 19:13












          • For me, I was unable to install any package because ifconfig and network-manager would not load (I have a USB wifi dongle). So @xtrchessreal 's suggestion is what worked.
            – midopa
            Dec 13 '17 at 6:14

















          up vote
          17
          down vote



          accepted










          Seems to be a reported bug (#1554803)



          It can be solved installing apparmor-easyprof-ubuntu or creating the folders by hand.



          sudo apt-get install apparmor-easyprof-ubuntu





          share|improve this answer























          • Would you mind expanding your answer and providing the proper steps to install the package you are referring to or to create the necessary folders. I looked at the bug it is indeed the same I see. Thank you :)
            – xtrchessreal
            May 4 '16 at 22:54










          • how this solving this problem ?
            – Ebuzer Taha KANAT
            Feb 27 '17 at 23:42






          • 1




            @EbuzerTahaKANAT I don't think this solves the AppArmor problem but provides a way to keep systemd from failing AppArmor initialization on boot. I built the folders and empty files by hand and, I ran the installation of apparmor-easyprof-ubuntu. Files (video.d, graphics.d, and audio.d) are still empty in my system and boot no longer records a fail code. These files are supposed to contain AppArmor policy code, I think, its a guess based on first line here launchpad.net/apparmor-easyprof-ubuntu Not sure if Apparmor protects these devices? Bug still open!
            – xtrchessreal
            Apr 12 '17 at 19:13












          • For me, I was unable to install any package because ifconfig and network-manager would not load (I have a USB wifi dongle). So @xtrchessreal 's suggestion is what worked.
            – midopa
            Dec 13 '17 at 6:14















          up vote
          17
          down vote



          accepted







          up vote
          17
          down vote



          accepted






          Seems to be a reported bug (#1554803)



          It can be solved installing apparmor-easyprof-ubuntu or creating the folders by hand.



          sudo apt-get install apparmor-easyprof-ubuntu





          share|improve this answer














          Seems to be a reported bug (#1554803)



          It can be solved installing apparmor-easyprof-ubuntu or creating the folders by hand.



          sudo apt-get install apparmor-easyprof-ubuntu






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited May 5 '16 at 21:16









          muru

          135k20291493




          135k20291493










          answered May 4 '16 at 20:13









          ant

          18612




          18612












          • Would you mind expanding your answer and providing the proper steps to install the package you are referring to or to create the necessary folders. I looked at the bug it is indeed the same I see. Thank you :)
            – xtrchessreal
            May 4 '16 at 22:54










          • how this solving this problem ?
            – Ebuzer Taha KANAT
            Feb 27 '17 at 23:42






          • 1




            @EbuzerTahaKANAT I don't think this solves the AppArmor problem but provides a way to keep systemd from failing AppArmor initialization on boot. I built the folders and empty files by hand and, I ran the installation of apparmor-easyprof-ubuntu. Files (video.d, graphics.d, and audio.d) are still empty in my system and boot no longer records a fail code. These files are supposed to contain AppArmor policy code, I think, its a guess based on first line here launchpad.net/apparmor-easyprof-ubuntu Not sure if Apparmor protects these devices? Bug still open!
            – xtrchessreal
            Apr 12 '17 at 19:13












          • For me, I was unable to install any package because ifconfig and network-manager would not load (I have a USB wifi dongle). So @xtrchessreal 's suggestion is what worked.
            – midopa
            Dec 13 '17 at 6:14




















          • Would you mind expanding your answer and providing the proper steps to install the package you are referring to or to create the necessary folders. I looked at the bug it is indeed the same I see. Thank you :)
            – xtrchessreal
            May 4 '16 at 22:54










          • how this solving this problem ?
            – Ebuzer Taha KANAT
            Feb 27 '17 at 23:42






          • 1




            @EbuzerTahaKANAT I don't think this solves the AppArmor problem but provides a way to keep systemd from failing AppArmor initialization on boot. I built the folders and empty files by hand and, I ran the installation of apparmor-easyprof-ubuntu. Files (video.d, graphics.d, and audio.d) are still empty in my system and boot no longer records a fail code. These files are supposed to contain AppArmor policy code, I think, its a guess based on first line here launchpad.net/apparmor-easyprof-ubuntu Not sure if Apparmor protects these devices? Bug still open!
            – xtrchessreal
            Apr 12 '17 at 19:13












          • For me, I was unable to install any package because ifconfig and network-manager would not load (I have a USB wifi dongle). So @xtrchessreal 's suggestion is what worked.
            – midopa
            Dec 13 '17 at 6:14


















          Would you mind expanding your answer and providing the proper steps to install the package you are referring to or to create the necessary folders. I looked at the bug it is indeed the same I see. Thank you :)
          – xtrchessreal
          May 4 '16 at 22:54




          Would you mind expanding your answer and providing the proper steps to install the package you are referring to or to create the necessary folders. I looked at the bug it is indeed the same I see. Thank you :)
          – xtrchessreal
          May 4 '16 at 22:54












          how this solving this problem ?
          – Ebuzer Taha KANAT
          Feb 27 '17 at 23:42




          how this solving this problem ?
          – Ebuzer Taha KANAT
          Feb 27 '17 at 23:42




          1




          1




          @EbuzerTahaKANAT I don't think this solves the AppArmor problem but provides a way to keep systemd from failing AppArmor initialization on boot. I built the folders and empty files by hand and, I ran the installation of apparmor-easyprof-ubuntu. Files (video.d, graphics.d, and audio.d) are still empty in my system and boot no longer records a fail code. These files are supposed to contain AppArmor policy code, I think, its a guess based on first line here launchpad.net/apparmor-easyprof-ubuntu Not sure if Apparmor protects these devices? Bug still open!
          – xtrchessreal
          Apr 12 '17 at 19:13






          @EbuzerTahaKANAT I don't think this solves the AppArmor problem but provides a way to keep systemd from failing AppArmor initialization on boot. I built the folders and empty files by hand and, I ran the installation of apparmor-easyprof-ubuntu. Files (video.d, graphics.d, and audio.d) are still empty in my system and boot no longer records a fail code. These files are supposed to contain AppArmor policy code, I think, its a guess based on first line here launchpad.net/apparmor-easyprof-ubuntu Not sure if Apparmor protects these devices? Bug still open!
          – xtrchessreal
          Apr 12 '17 at 19:13














          For me, I was unable to install any package because ifconfig and network-manager would not load (I have a USB wifi dongle). So @xtrchessreal 's suggestion is what worked.
          – midopa
          Dec 13 '17 at 6:14






          For me, I was unable to install any package because ifconfig and network-manager would not load (I have a USB wifi dongle). So @xtrchessreal 's suggestion is what worked.
          – midopa
          Dec 13 '17 at 6:14














          up vote
          2
          down vote













          For me, I couldn't install any packages because both ifconfig and network-manager could not find/start my USB wifi dongle.



          So @xtrchessreal's comment is what worked for me:



          In the recovery mode shell, create the following directories:



          mkdir -p /usr/share/apparmor/hardware/graphics.d
          mkdir -p /usr/share/apparmor/hardware/audio.d
          mkdir -p /usr/share/apparmor/hardware/video.d


          And then reboot






          share|improve this answer























          • apparmor-easyprof-ubuntu IMPORTANT: this project is no longer actively maintained by the Ubuntu Security team of Canonical. Per launchpad.net/apparmor-easyprof-ubuntu I wonder if it maintained elsewhere?
            – xtrchessreal
            Dec 13 '17 at 20:34












          • Good to know! I'm just going to remove it from the answer then.
            – midopa
            Dec 25 '17 at 8:37















          up vote
          2
          down vote













          For me, I couldn't install any packages because both ifconfig and network-manager could not find/start my USB wifi dongle.



          So @xtrchessreal's comment is what worked for me:



          In the recovery mode shell, create the following directories:



          mkdir -p /usr/share/apparmor/hardware/graphics.d
          mkdir -p /usr/share/apparmor/hardware/audio.d
          mkdir -p /usr/share/apparmor/hardware/video.d


          And then reboot






          share|improve this answer























          • apparmor-easyprof-ubuntu IMPORTANT: this project is no longer actively maintained by the Ubuntu Security team of Canonical. Per launchpad.net/apparmor-easyprof-ubuntu I wonder if it maintained elsewhere?
            – xtrchessreal
            Dec 13 '17 at 20:34












          • Good to know! I'm just going to remove it from the answer then.
            – midopa
            Dec 25 '17 at 8:37













          up vote
          2
          down vote










          up vote
          2
          down vote









          For me, I couldn't install any packages because both ifconfig and network-manager could not find/start my USB wifi dongle.



          So @xtrchessreal's comment is what worked for me:



          In the recovery mode shell, create the following directories:



          mkdir -p /usr/share/apparmor/hardware/graphics.d
          mkdir -p /usr/share/apparmor/hardware/audio.d
          mkdir -p /usr/share/apparmor/hardware/video.d


          And then reboot






          share|improve this answer














          For me, I couldn't install any packages because both ifconfig and network-manager could not find/start my USB wifi dongle.



          So @xtrchessreal's comment is what worked for me:



          In the recovery mode shell, create the following directories:



          mkdir -p /usr/share/apparmor/hardware/graphics.d
          mkdir -p /usr/share/apparmor/hardware/audio.d
          mkdir -p /usr/share/apparmor/hardware/video.d


          And then reboot







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Dec 25 '17 at 8:38

























          answered Dec 13 '17 at 6:22









          midopa

          1234




          1234












          • apparmor-easyprof-ubuntu IMPORTANT: this project is no longer actively maintained by the Ubuntu Security team of Canonical. Per launchpad.net/apparmor-easyprof-ubuntu I wonder if it maintained elsewhere?
            – xtrchessreal
            Dec 13 '17 at 20:34












          • Good to know! I'm just going to remove it from the answer then.
            – midopa
            Dec 25 '17 at 8:37


















          • apparmor-easyprof-ubuntu IMPORTANT: this project is no longer actively maintained by the Ubuntu Security team of Canonical. Per launchpad.net/apparmor-easyprof-ubuntu I wonder if it maintained elsewhere?
            – xtrchessreal
            Dec 13 '17 at 20:34












          • Good to know! I'm just going to remove it from the answer then.
            – midopa
            Dec 25 '17 at 8:37
















          apparmor-easyprof-ubuntu IMPORTANT: this project is no longer actively maintained by the Ubuntu Security team of Canonical. Per launchpad.net/apparmor-easyprof-ubuntu I wonder if it maintained elsewhere?
          – xtrchessreal
          Dec 13 '17 at 20:34






          apparmor-easyprof-ubuntu IMPORTANT: this project is no longer actively maintained by the Ubuntu Security team of Canonical. Per launchpad.net/apparmor-easyprof-ubuntu I wonder if it maintained elsewhere?
          – xtrchessreal
          Dec 13 '17 at 20:34














          Good to know! I'm just going to remove it from the answer then.
          – midopa
          Dec 25 '17 at 8:37




          Good to know! I'm just going to remove it from the answer then.
          – midopa
          Dec 25 '17 at 8:37


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f767272%2fapparmor-init-failed-exit-code-123%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Mont Emei

          Province de Neuquén

          Soliste