I'm not familiar with the new grub. grub.cfg is more complex than the old grub I'm used to. So my first attempt to restart failed to deactivate apparmor.
Then I edited grub.cfg and put the apparmor=0 statement dierctly after root=xxxxx and before ro This time I think apparmor is less effective. See below: janos@Andraslinux:~$ sudo aa-status [sudo] password for janos: apparmor module is loaded. apparmor filesystem is not mounted. janos@Andraslinux:~$ dmesg | tail [ 56.010269] composite sync not supported [ 56.010284] composite sync not supported [ 56.672092] init: plymouth-stop pre-start process (1095) terminated with status 1 [ 69.534864] composite sync not supported [ 69.534877] composite sync not supported [ 72.344126] composite sync not supported [ 72.344140] composite sync not supported [ 72.403431] composite sync not supported [ 72.403445] composite sync not supported [ 194.610821] printdriver[1974]: segfault at 0 ip (null) sp bfd013fc error 4 in printdriver[8048000+b000] janos@Andraslinux:~$ Howver, as you see I still get the segfault. Could it be because apparmor module is still loaded? I'm sorry, I'm confused a littbit about your last paragraph on restart. One more point: in your previous comment you state that "Alright, because you aren't using an Ubuntu kernel, or a kernel with the interface patches". My kernel is what came with the installation DVD and updated periodically by the updater. -- 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
