Try running: sudo aa-logprof This will walk through almost all the apparmor denied messages and give you a chance to allow or deny the accesses so future runs of the programs can work as you expect. Due to an unfortunate bug, not _all_ apparmor denied messages are handled, so you may need to do some hands-on profile editing.
Iterate the "sudo aa-logprof" and "sudo service cups restart" (at least I think that's the newfangled upstart command) until aa-logprof does ask you any more questions. Then look through dmesg output for the messages that might have slipped through the tools and add "w" permissions for the listed files as appropriate. -----Original Message----- From: zsolt.ruszinyák <[email protected]> Sender: [email protected] Date: Mon, 26 Dec 2011 20:11:26 To: <[email protected]> Reply-To: Bug 908864 <[email protected]> Subject: [apparmor] [Bug 908864] Re: My Lexmark x2650 printer stopped working after upgrading to 11.10: Idle - File "/usr/local/lexmark/lxk08/bin/printdriver" has insecure permissions (0100775/uid=0/gid=2). ** Attachment added: "troubleshoot.txt" https://bugs.launchpad.net/bugs/908864/+attachment/2647679/+files/troubleshoot.txt ** Also affects: apparmor Importance: Undecided Status: New -- You received this bug notification because you are a member of AppArmor Developers, which is the registrant for AppArmor. https://bugs.launchpad.net/bugs/908864 Title: My Lexmark x2650 printer stopped working after upgrading to 11.10: Idle - File "/usr/local/lexmark/lxk08/bin/printdriver" has insecure permissions (0100775/uid=0/gid=2). Status in AppArmor Linux application security framework: New Status in “cups” package in Ubuntu: New Bug description: I used Ubuntu 9.04 for a long time and the driver available on the manufacturer's site: http://support.lexmark.com/index?page=content&id=DR860&actp=search&viewlocale=en_US&segment=SUPPORT&productCode=LEXMARK_X2650&locale=EN&userlocale=EN_US&searchid=1324929199490 worked perfectly! after installing the newest Ubuntu, I can't even finish the installation process of the driver, the Setup says "no connection", even though there is connection to the printer, because it appears in the list of printers when introduced to the USB. from what I have learnt on the web, recent changes in Cups and AppArmor caused that the connection to a printer with 3rd party driver is often blocked. but this is too high a game for me to solve here... have tried in another machine too, the same result, which means that THIS PRINTER JUST STOPPED WORKING IN LINUX at all. That is sad. I have to go back to older Ubuntu's just for the printer!!!!!!!!! This is insane. See my debugging results. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cups 1.5.0-8ubuntu5 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Mon Dec 26 20:43:21 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2) Lpstat: device for 2600-Series: usb://Lexmark/2600%20Series?serial=3001960G9644833&interface=1 MachineType: ASUSTeK Computer INC. 1000H Papersize: letter PpdFiles: 2600-Series: Lexmark 2600 Series, 1.0 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=2e7845e1-2b31-4fe5-95bc-334f43798f52 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1005 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1000H dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x00000000 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1005:bd08/01/2008:svnASUSTeKComputerINC.:pn1000H:pvrx.x:rvnASUSTeKComputerINC.:rn1000H:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 1000H dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/908864/+subscriptions -- AppArmor mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor -- AppArmor mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
