sudo /etc/init.d/apparmor start
sam@sam-
[sudo] password for sam:
Sorry, try again.
[sudo] password for sam:
* Reloading AppArmor profiles * AppArmor not available as kernel LSM.
invoke-rc.d: initscript apparmor, action "reload" failed.
sam@sam-
* Starting AppArmor profiles * AppArmor not available as kernel LSM.
sam@sam-
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Manfred Hampl
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
good day[morning/
Revision history for this message
|
#2 |
by the way'actionparsnip'i like to thanks you cause now i learned how to copy/paste using the terminal
Revision history for this message
|
#3 |
No worries. It's the same in any application in any OS.
This may be helpful
https:/
Revision history for this message
|
#4 |
Maybe similar to http://
What is the output of the following terminal commands:
cat /proc/cmdline
grep GRUB_CMDLINE_LINUX /etc/default/grub
Please copy/paste the output into this question document as done before.
Revision history for this message
|
#5 |
sam@sam-
ii spark 2011.0.deb-5 SPARK programming language toolset
sam@sam-
sam@sam-
sam@sam-
sam@sam-
ii spark 2011.0.deb-5 SPARK programming language toolset
sam@sam-
cat /proc/cmdline
grep GRUB_CMDLINE_LINUX /etc/default/grub
Revision history for this message
|
#6 |
sam@sam-
ii spark 2011.0.deb-5 SPARK programming language toolset
sam@sam-
sam@sam-
sam@sam-
sam@sam-
ii spark 2011.0.deb-5 SPARK programming language toolset
sam@sam-
cat /proc/cmdline
grep GRUB_CMDLINE_LINUX /etc/default/grub
ii: cannot connect to host: Connection timed out
sam@sam-
sam@sam-
sam@sam-
sam@sam-
sam@sam-
ii: remote host closed connection: File exists
sam@sam-
sam@sam-
sam@sam-
BOOT_IMAGE=
sam@sam-
GRUB_CMDLINE_
GRUB_CMDLINE_
GRUB_CMDLINE_
sam@sam-
sam@sam-
Revision history for this message
|
#7 |
thanks Manfred,i really appreciated your help
Revision history for this message
|
#8 |
Your grub configuratuion contains the option to disable apparmor.
If you want to have apparmor running, you have to remove "apparmor=0" from GRUB_CMDLINE_
Revision history for this message
|
#9 |
sam@sam-
GRUB_CMDLINE_
sam@sam-
GRUB_CMDLINE_
sam@sam-
[sudo] password for sam:
E: Invalid operation removeapparmor=0
sam@sam-
Revision history for this message
|
#10 |
sam@sam-
bash: /etc/default/grub: Permission denied
sam@sam-
Revision history for this message
|
#11 |
You misunderstood my comment. What I gave as a description of the steps to do, but not a command to execute.
open a terminal and issue the command
gksudo gksudo gedit /etc/default/grub
This should ask for your password as the confirmation for an administrative action, and the open an editor with the grob configuration file loaded.
In the editor window scroll down until you find a line that starts with GRUB_CMDLINE_
In that line remove the text "apparmor=0"
Save the file and close the editor.
Then issue the command
sudo update-grub
and if there is no error message shown, finally reboot your computer and check whether apparmor is running after the reboot.
Revision history for this message
|
#12 |
sir,pls be patient with me i m geek to computer and i wish to learn. thanking you sir very much for your kind anticipation
Revision history for this message
|
#13 |
Thanks i will do that
On Apr 2, 2014 6:42 PM, "Manfred Hampl" <
<email address hidden>> wrote:
> Your question #246376 on ubuntu-docs in Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> You misunderstood my comment. What I gave as a description of the steps
> to do, but not a command to execute.
>
> open a terminal and issue the command
>
> gksudo gksudo gedit /etc/default/grub
>
> This should ask for your password as the confirmation for an
> administrative action, and the open an editor with the grob configuration
> file loaded.
> In the editor window scroll down until you find a line that starts with
> GRUB_CMDLINE_
> In that line remove the text "apparmor=0"
> Save the file and close the editor.
> Then issue the command
>
> sudo update-grub
>
> and if there is no error message shown, finally reboot your computer and
> check whether apparmor is running after the reboot.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#14 |
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_HIDDEN_
GRUB_HIDDEN_
GRUB_TIMEOUT=10
GRUB_DISTRIBUTO
GRUB_CMDLINE_
GRUB_CMDLINE_
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM=
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=
GRUB_CMDLINE_
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="48
GRUB_GFXPAYLOAD
Revision history for this message
|
#15 |
I just see that you have TWO occurences of GRUB_CMDLINE_
Furthermore I recommend that you also delete the string "i915.senaphore
And the same with "drn.vblankffde
Revision history for this message
|
#16 |
Sir.how to delete these two thread.any command line for terminal.pls
further advise.thank you very much
On Apr 2, 2014 7:16 PM, "Manfred Hampl" <
<email address hidden>> wrote:
> Your question #246376 on ubuntu-docs in Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> I just see that you have TWO occurences of
> GRUB_CMDLINE_
> delete one.
>
> Furthermore I recommend that you also delete the string
> "i915.senaphore
> with n), so this options does not do anything and is redundant.
>
> And the same with "drn.vblankffde
> it miosses an o (...blankoff...). What you currently have is not having
> any effect and should be deleted.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
|
#17 |
I have already given the command for starting the editor in one of my previous postings:
gksudo gksudo gedit /etc/default/grub
Do not forget to update your grub bootloader afterwards with the command
sudo update-grub
and do not forget to reboot to really activate the changes.
Revision history for this message
|
#18 |
sam@sam-
sudo update-grub
Revision history for this message
|
#19 |
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_HIDDEN_
GRUB_HIDDEN_
GRUB_TIMEOUT=10
GRUB_DISTRIBUTO
GRUB_CMDLINE_
GRUB_CMDLINE_
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM=
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=
GRUB_CMDLINE_
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="48
GRUB_GFXPAYLOAD
Revision history for this message
|
#20 |
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_HIDDEN_
GRUB_HIDDEN_
GRUB_TIMEOUT=10
GRUB_DISTRIBUTO
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM=
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=
GRUB_CMDLINE_
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="48
GRUB_GFXPAYLOAD
Revision history for this message
|
#21 |
AppArmor not available as kernel LSM.
Revision history for this message
|
#22 |
sam@sam-
[sudo] password for sam:
* Reloading AppArmor profiles * AppArmor not available as kernel LSM.
invoke-rc.d: initscript apparmor, action "reload" failed.
sam@sam-
Revision history for this message
|
#23 |
sam@sam-
[sudo] password for sam:
* Reloading AppArmor profiles * AppArmor not available as kernel LSM.
invoke-rc.d: initscript apparmor, action "reload" failed.
sam@sam-
[sudo] password for sam:
Generating grub.cfg ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-
Found initrd image: /boot/initrd.
Found linux image: /boot/vmlinuz-
Found initrd image: /boot/initrd.
Found linux image: /boot/vmlinuz-
Found initrd image: /boot/initrd.
Found memtest86+ image: /boot/memtest86
done
sam@sam-
Revision history for this message
|
#24 |
sam@sam-
[sudo] password for sam:
FATAL: Module apparmor not found.
sam@sam-
* Starting AppArmor profiles Skipping profile in /etc/apparmor.
Skipping profile in /etc/apparmor.
sam@sam-
Warning: unknown mime-type for "/etc/apparmor/
Error: no such file "/etc/apparmor/
sam@sam-
apparmor module is loaded.
18 profiles are loaded.
18 profiles are in enforce mode.
/sbin/dhclient
/usr/bin/evince
/usr/
/usr/
/usr/
/usr/
/usr/
/usr/
/usr/
/usr/
/usr/
/usr/
/usr/
/usr/
/usr/
/usr/
/usr/sbin/cupsd
/usr/
0 profiles are in complain mode.
3 processes have profiles defined.
3 processes are in enforce mode.
/sbin/dhclient (1208)
/usr/
/usr/sbin/cupsd (826)
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
sam@sam-
Revision history for this message
|
#25 |
Thanks Manfred Hampl, that solved my question.
Revision history for this message
|
#27 |
Fine to see that your system is again running with apparmor as desired.
Just a comment:
It seems that you have deleted more than recommended form the grub configuration file.
The boot command line option
"pcie_aspm= "
in GRUB_CMDLINE_
GRUB_CMDLINE_
As your system seems to run even with these erroneous modifications, I am not sure whether I should recommend re-doing the whole exercise of editing the grub config file etc.
Revision history for this message
|
#28 |
Thanks for the help.the system ok but video distorted.i hope you may help
me fix this issue.thanks again you are very kind
On Apr 3, 2014 2:42 PM, "Manfred Hampl" <
<email address hidden>> wrote:
>
> Your question #246376 on ubuntu-docs in Ubuntu changed:
> https:/
>
> Manfred Hampl posted a new comment:
> Fine to see that your system is again running with apparmor as desired.
> Just a comment:
> It seems that you have deleted more than recommended form the grub
configuration file.
>
> The boot command line option
> "pcie_aspm= "
> in GRUB_CMDLINE_
before) and you deleted the line
> GRUB_CMDLINE_
>
> As your system seems to run even with these erroneous modifications, I
> am not sure whether I should recommend re-doing the whole exercise of
> editing the grub config file etc.
>
> --
> You received this question notification because you asked the question.