Yes grub2 is a little different, but its not too bad once you get used to it
use the cursor keys to move to the entry you want to edit
press e
move to the kernel line which will look something like
linux /boot/vmlinuz-3.8.0-23-generic
root=UUID=7d19c7bc-50aa-4266-9ab7-332c92f5e3aa ro quiet splash
pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0
$vt_handoff
add apparmor=0 to the end or anywhere after root= really
use ctrl-x to boot
You can directly edit /boot/grub/grub.cfg but its not recommended as your
changes will be lost any time that a kernel update is applied. If you want a
kernel config to survive a kernel update you should edit
/etc/default/grub/
After editing /etc/default/grub you will need to run
sudo update-grub
To regenerate your grub.cfg. It seems like a pita but then the change will
survive next time you get a kernel update.
The apparmor module is present (it is built into the kernel), but it is not
active or enforcing any policy. It is turned off. If you do
dmesg | grep AppArmor
if apparmor is enabled you get something like
[0.008000] AppArmor: AppArmor initialized
[0.813392] AppArmor: AppArmor Filesystem Enabled
and disabled by apparmor=0
[0.008000] AppArmor: AppArmor disabled by boot time parameter
So apparmor is not causing the print failure you are seeing.
Restart can be a little confusing. Let me try again. There are two
copies of apparmor policy. What is stored in /etc/apparmor.d/ and what
is currently active in the kernel. The restart command tries to sync the
kernel to reflect with what is in /etc/apparmor.d/ If for example you
delete a profile file from /etc/apparmor.d/ you would want that profile
to also be removed from the kernel, when you run restart to sync
/etc/apparmor.d and the loaded system policy.
In this case your kernel is missing an interface patch that allows the
restart command to introspect the kernel and determine what policy is
currently loaded. In this case restart can go through and load policy
that exists in /etc/apparmor.d/ but it can't detect that the kernel has
some policy loaded that is not in /etc/apparmor.d You can reboot
instead of using restart to clear out the loaded policy from the kernel.
This should not affect your current printing problems as you are not
deleted files in /etc/apparmor.d/, just noting that this behavior is
broken with your current kernel.
As for your kernel it most certainly is not an official Ubuntu kernel. What
DVD did you install it from?
The official Ubuntu kernels have the apparmor patches applied and have a uname
-a that looks like
Linux ortho2 3.8.0-23-generic #34-Ubuntu SMP Wed May 29 20:22:58 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
your kernel version string is showing its a derivative of
3.8.
but the rest of the version string is all wrong
13-030813-generic #201305111843 SMP Sat May 11 22:52:24 UTC 2013 i686
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1187970
Title:
apparmor prevents custom printer driver from executing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
