inode_permission error for cupsd on /dev/tty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cupsys (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Hi,
From dmesg:
[ 895.934627] audit(119243252
I guess cupsd lacks some apparmor permissions to write to the tty.
I now have version 1.3.2-1ubuntu6 of the package, but can't really tell whether the new or the previous version or the upgrade caused the message, so if you just fixed such a problem in ubuntu6, please close this report.
Bye,
aot2002 (jasonbronson) wrote : | #1 |
Alexander Hunziker (alex-hunziker) wrote : | #2 |
confirming this. cupsd crashes all the time. i'm not sure when it started, but it definitely didn't happen when gutsy was first released. maybe an error in some backport/proposed updates?
Craig Maloney (craig-decafbad) wrote : | #3 |
Noticed this too. Not sure what it means, as it printed fine.
Security Events
=-=-=-=-=-=-=-=
Jan 24 07:44:20 lister kernel: [64816.981749] audit(120117866
Jan 24 07:44:20 lister kernel: [64817.024061] audit(120117866
Jan 24 07:45:44 lister kernel: [64900.646971] audit(120117874
Jan 24 07:45:44 lister kernel: [64900.692477] audit(120117874
Changed in cupsys: | |
status: | New → Confirmed |
Alexander Hunziker (alex-hunziker) wrote : | #4 |
I tried disabling apparmor, but that doesn't solve the problem. If I restart cupsys, then I can print a few documents, and then it crashes again and requires a restart.
Merike Sell (merikes) wrote : | #5 |
I'm having the same problem. Using 1.3.2-1ubuntu7.5.
I have those lines in dmesg, one or two per job it seems:
[ 1231.168000] audit(120239624
[ 1243.948000] audit(120239626
CUPS doesn't print at all, not after restarting it as well. It simply displays that the jobs have completed even though they haven't even started.
The problem was't there for me two weeks ago Sunday. Maybe I had those lines in the log, I don't know, but I didn't have any problems with printing.
January (january-weiner) wrote : | #6 |
Confirmed.
Hey, people, this is bloody serious! It's 3am here, I *MUST* print some documents for tomorrow morning, and I find my printers suddenly not working! Not even printing as root work! WTF is apparmor? How do I get rid of this thing?
(Incidentally, when I was googling for "get rid of apparmor ubuntu" I found several links about how to get rid of Ubuntu... is google trying to tell me something :-) ?)
January (january-weiner) wrote : | #7 |
Great. So I won't print the docs.
I tried to remove / disable apparmor. I removed the module by doing an rmmod apparmor. Printing still does not work, although all messages from cups say that it's OK and that job has been send, no errors whatsoever, jobs shown as completed.
I also tried aa-complain, but that did not help, either, except that the messages from apparmor are not displayed. I also included the abstractions/samba into /etc/apparmor.
Possibly then, my problem is not related to apparmor directly, but to cups. Whatever, it worked just few days ago when I last needed to print smth at home.
cheers,
j.
Chris Kälin (ck1) wrote : | #8 |
Confirmed for epson stylos colour 600 on my dad's Gutsy. Only the first time I plugged in the USB, I was able to select the first option in KDE's printer configuration. Did not work anyway. After that the 1st option (local printer) was greyed out, also after reboot etc. Still the printer can be configured by choosing the right driver. But anyway I'm running into the same problem:
operation=
if I want to print something.
The printer worked flawlessly on Feisty. Sorry, but I have my reasons I have changed my whole home machines into Fedora. A little more to configure, but a lot more stability in drivers and hardware support.
Buks Hanekom (bukshanekom) wrote : | #9 |
I think I have the same problem.
I am using Hardy Alpha 4 (Linux 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 GNU/Linux)
I have been trying to print to a HP LaserJet 1018 which is shared on a windows XP machine via Samba.
This did not work, so I plugged it directly into my laptop (kubuntu hardy Alpha 4).
It was detected, and little printer appeared in the tray which said that the printer was installed and ready to use. Ha, it did NOT work!
After some googling, I found this post on the kubuntu forum (http://
I followed the instructions to the letter and the printer reset itself when I entered the command to update the firmware.
I then added the printer using KMenu -> System -> Printing. I was able to print from open office.
I then moved the printer back to the windoze PC and tried to setup the printer again via the add printer wizard through samba.
When I click on the printer test button I get this in the kernel.log file, which seems the same as reported earlier in this post:
==> /var/log/kern.log <==
Feb 18 23:46:10 buks kernel: [38441.820449] audit(120337117
Feb 18 23:46:10 buks kernel: [38441.830251] audit(120337117
Feb 18 23:46:10 buks kernel: [38441.832097] audit(120337117
Feb 18 23:46:11 buks kernel: [38441.886584] audit(120337117
Feb 18 23:46:11 buks kernel: [38441.887012] audit(120337117
Feb 18 23:46:11 buks kernel: [38441.887907] audit(120337117
Feb 18 23:46:11 buks kernel: [38441.891499] audit(120337117
Feb 18 23:46:11 buks kernel: [38441.901246] audit(120337117
Feb 18 23:46:11 buks kernel: [38441.901994] audit(120337117
Feb 18 23:46:11 buks kernel: [38441.904585] audit(120337117
Peter Peltonen (peter-peltonen) wrote : | #10 |
- KDE System Settings backtrace Edit (7.5 KiB, text/plain)
I think I have the same problem: with HP 710C parallel port printer which used to work ok but when I now try to print something nothing happens. The only error msg I can find is in 'dmesg':
[ 51.118333] audit(120361368
lpinfo sees the port:
root@sinisusi:~# lpinfo -v
network socket
network beh
direct hpfax
direct hp
network http
network ipp
network lpd
direct parallel:/dev/lp0
file cups-pdf:/
direct scsi
network smb
lpq reports that everything is okay:
root@sinisusi:~# lpq
hp710gray is ready
no entries
CUPS access log claims everything printed just fine:
localhost - - [21/Feb/
localhost - - [21/Feb/
CUPS error log also seems to say that the document printed fine:
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
I [21/Feb/
D [21/Feb/
I [21/Feb/
I [21/Feb/
I [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
D [21/Feb/
Henning Moll (drscott) wrote : | #11 |
Here's how i solved the problem on my system...
The cups error log (http://
> ... (/usr/lib/
> ... Job stopped due to filter errors.
So i enabled logging of debug information via /etc/foomatic/
After the next print attempt, the file /tmp/foomatic-
>...
>sh: gs: command not found
>renderer return value: 127
>...
Pardon? A short check via dpkg shows, that package ghostscript - which contains /usr/bin/gs - was installed. But there was really no /usr/bin/gs.
Well, a 'sudo apt-get install --reinstall ghostscript' solved the problem. I don't know what happend, why ghostscript was not properly installed. The apparmor log entry also disappeared.
Now, please do not just execute the above apt-get command: Can you please verify if you suffer from exactly the same problem _before_ unning the command?
Merike Sell (merikes) wrote : | #12 |
In my case I also looked at CUPS log and it seemed to think that my document printed successfully even though it did not. For this time removing the printer from CUPS and then re-adding made the problem go away.
Peter Peltonen (peter-peltonen) wrote : | #13 |
My gs binary isn't missing:
peter@sinisusi:~$ ls -lah /usr/bin/gs
-rwxr-xr-x 1 root root 4.3K 2008-01-08 23:20 /usr/bin/gs
I enabled debugging from /etc/foomatic/
I reinstalled ghostscript anyway, did cupsys restart amd: printer still does not work and the apparmor entry still appears.
But by following Merike's comment I got the problem solved: Removing the printer and adding it again from CUPS web admin tool made the printer work again! The apparmor entry still appears though, but I guess that's no problem as long as my printer prints...
I still cannot access "Printers" through "System settings" (it crashes), but I guess that is a KDE problem not related to this problem.
Magnus Helander (mhelander) wrote : | #14 |
Same here,
Gutsy 7.10 / 2.6.22-14 / Gnome 2.20.1 on a HP Photosmart 3300 series using default driver.
I can print (well... actually my kids can print) drawings from tuxpaint, but not PDF from Evince 2.20.1.
Feb 27 22:40:17 magnuslinux kernel: [ 1736.580000] audit(120414841
/magnus
Marc Quinton (mquinton) wrote : | #15 |
same for me, with ubuntu-gutsy, regular updates ; I reinstalled ghostscript, restarted cupsys and now it works fine. Sorry for debuging. Did made an apt-get --reinstall to quickly.
Henning, thanks for the trick.
Marc Quinton (mquinton) wrote : | #16 |
I need give some more information : after ghostscript reinstallation, I still have the bug ; so now, I have found an other way to do the work :
- switch off printer
- shutdown cups : sudo /etc/init.d/cupsys stop
- shutdown armor : sudo /etc/init.
- restart cups : sudo /etc/init.d/cupsys start
- switch on your printer
- do some printing task
here is the dmesg (seems to be OK) :
root@ubuntu-
...
[ 190.816000] ppdev0: unregistered pardevice
[ 292.160000] ppdev0: registered pardevice
[ 292.536000] ppdev0: registered pardevice
[ 327.404000] ppdev0: unregistered pardevice
Marc Quinton (mquinton) wrote : | #17 |
an interresting link : http://
Printing with AppArmor
Ubuntu 7.10 introduces an additional security layer called AppArmor, whose support for CUPS printing is not yet complete. This will result in printing failures in certain corner cases described below. The workaround in each of these cases is to disable the AppArmor CUPS profile by running sudo aa-complain cupsd. AppArmor support may be re-enabled by running sudo aa-enforce cupsd.
* Printing to bluetooth printers does not work with AppArmor enabled. Bug #147800 : https:/
* Many third-party printer drivers (especially from printer manufacturers) do not work. Bug #152537 : https:/
seems to be duplicate with theses bugs ...
Till Kamppeter (till-kamppeter) wrote : | #18 |
Buks Hanekom, can you check again with Hardy? There your problem with the smb CUPS backend (access to Windows print server) should be fixed. If not, post your /etc/apparmor.
Till Kamppeter (till-kamppeter) wrote : | #19 |
The problems with the smb backend and AppArmor should be fixed with gutsy-updates and hardy. Therefore I am closing this bug. Please reopen if someone has still AppArmor-induced problems with printing.
The /dev/tty messages do not break any printing functionality AFAIK.
Changed in cupsys: | |
status: | Confirmed → Won't Fix |
Aaron D. Campbell (aaroncampbell) wrote : | #20 |
I could not print after an upgrade to Kubuntu Hardy. I DID have the gs binary in /usr/bin, and was able to fix the problem using the solution at island linux: http://
My dmesg output looked like this:
[ 806.888916] audit(120942975
[ 812.035287] audit(120942975
[ 882.047534] audit(120942982
[ 903.291457] audit(120942984
[ 936.094182] audit(120942988
[ 938.615397] audit(120942988
My CUPS error_log looked like this:
E [28/Apr/
E [28/Apr/
E [28/Apr/
E [28/Apr/
E [28/Apr/
E [28/Apr/
E [28/Apr/
E [28/Apr/
E [28/Apr/
E [28/Apr/
Till Kamppeter (till-kamppeter) wrote : | #21 |
The problem is that we have opened up /opt/ for third-party drivers but no /usr/local/. pitti, should we also open up /usr/local/ in an SRU for CUPS?
Martin Pitt (pitti) wrote : | #22 |
First, this should become a new bug report. It has nothing to do with the issues discussed here previously.
Till, yes, we should probably allow "/usr/local/** rix", too.
Zebra-Rake (faheyd) wrote : | #23 |
Still broke ubuntu
uname -mros
Linux 2.6.24-16-386 i686 GNU/Linux
[1477560.340585] usblp1: USB Bidirectional printer dev 17 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0807
[1477560.364391] scsi9 : SCSI emulation for USB Mass Storage devices
[1477560.365643] usb-storage: device found at 17
[1477560.365648] usb-storage: waiting for device to settle before scanning
[1477565.359301] usb-storage: device scan complete
[1477565.360695] scsi 9:0:0:0: Direct-Access EPSON Stylus Storage 1.00 PQ: 0 ANSI: 2
[1477565.369209] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[1477565.369255] sd 9:0:0:0: Attached scsi generic sg4 type 0
[1477694.986179] audit(121424771
[1477857.015243] usb 5-3.1: USB disconnect, address 16
[1477857.015374] usblp0: removed
[1477861.048354] usb 5-3.1: new high speed USB device using ehci_hcd and address 18
[1477861.160601] usb 5-3.1: configuration #1 chosen from 1 choice
[1477861.170934] usblp0: USB Bidirectional printer dev 18 if 0 alt 0 proto 2 vid 0x03F0 pid 0x4117
[1477877.075221] audit(121424789
[1477957.346912] audit(121424797
[1478089.304915] usblp0: removed
[1478089.487633] audit(121424810
[1478481.449141] audit(121424850
[1478628.941002] usb 5-3.1: USB disconnect, address 18
[1478631.950359] usb 5-3.1: new high speed USB device using ehci_hcd and address 19
[1478632.043353] usb 5-3.1: configuration #1 chosen from 1 choice
[1478632.051181] usblp0: USB Bidirectional printer dev 19 if 0 alt 0 proto 2 vid 0x03F0 pid 0x4117
[1478721.021599] audit(121424874
[1478779.078786] audit(121424879
[1478916.618161] audit(121424893
[1478968.902243] audit(121424898
[1479164.655551] audit(121424918
Zebra-Rake (faheyd) wrote : | #24 |
This is still a 7 month old and annoying bug and is still stopping me from printing on my server through my network. Please fix it.
[ 54.796391] audit(121635649
uname -r 2.6.24-19-386 on Ubuntu.
Martin Pitt (pitti) wrote : Re: [Bug 153003] Re: inode_permission error for cupsd on /dev/tty | #25 |
Zebra-Rake [2008-07-18 4:57 -0000]:
> This is still a 7 month old and annoying bug and is still stopping me from printing on my server through my network. Please fix it.
> [ 54.796391] audit(121635649
No, this won't stop you from using printing. It is purely a cosmetical
bug. If printing doesn't work for you, then for an entirely different
reason.
Christian Stöveken (excogitation) wrote : | #26 |
the "cosmetical issue" still persists in Jaunty / 2.6.28-11-generic
[ 436.263117] type=1503 audit(123748564
[ 881.696138] type=1503 audit(123748608
[ 881.703131] type=1503 audit(123748608
[ 881.786840] type=1503 audit(123748609
Stefano Prenna (stefanoprenna) wrote : | #27 |
I can confirm the same issue on Jaunty / 2.6.28-12-generic
[ 2382.703190] type=1503 audit(124275578
Noel Burton-Krahn (noel-burton-krahn) wrote : | #28 |
I had a similiar problem. My cupsys failed to print. The problem is the foomatic filter couldn't load the perl IO::Handle module, because my apparmor doesn't include /usr/local/lib/perl
/etc/
I moved the apparmor config out of the way and cups works fine:
sudo mv /etc/apparmor.
sudo /etc/init.
sudo /etc/init.d/cupsys restart
Software versions:
Ubuntu 8.04.2
cupsys 1.3.7-1ubuntu3.5
apparmor 2.1+1075-0ubuntu9.2
Aaron Roydhouse (aaron-roydhouse) wrote : | #29 |
This problem screwed up all my Ubuntu printing as well. I originally fixed my problem with my printers this addition to /etc/apparmor.
# FIXME: no policy ATM for hplip and Brother drivers
/usr/bin/hpijs Ux,
/usr/Brother/** Ux,
And that has worked fine with Jaunty 9.04 for almost a year, then suddenly now the same problem reoccurred and the filter can't run any more, even with the additions above.
In the meantime I have to switch apparmor to complain only to work around this:
sudo aa-complain cupsd
Aaron.
Aaron Roydhouse (aaron-roydhouse) wrote : | #30 |
It is really quite unhelpful that manufacturers like HP and Brother who do the good work of actually publishing and distributing Linux drivers for their printers then get them regularly broken in Ubuntu by its apparmor CUPS policy. It would be great if HP/Brother and Ubuntu could work together on a more end-user-friendly approach.
Loïc Minier (lool) wrote : | #31 |
Please file a separate bug report with the exact issue you're seeing; the bug I filed was about cupsd trying to access /dev/tty. It didn't prevent me from printing, it just caused weird logs.
i too am recieving this issue
any luck?