Red Hat Bugzilla – Bug 6769
lpr 0.46 breaks netatalk printing
Last modified: 2008-05-01 11:37:52 EDT
lpr 0.46 has changed the format of the control file to
require a device/inode line. This breaks the netatalk
printer access protocol daemon. Attempting to print a file
causes lpd to send mail saying:
Your printer job (<name>)
was not printed because it was not linked to the original
How does netatalk print files?
First, I was wrong about the device/inode line. It's not required.
Netatalk builds the control and data files in the spool directory with
user = group = root. I wrote a patch to netatalk that fchown()s the
data file just like the lpr command does. I've posted the patch on
the linux-atalk mailing list but I haven't heard anything.
Please send me a copy of the patch so it can be included in the RPM.
I would like to point out that apparently this breakage is either version or
installation specific... I use the combination of:
bash$ rpm -q netatalk
bash$ rpm -q lpr
without any problems. Upgrading to any later version of lpr DOES break
printing, with a different message (see bug 8288).
Just had a thought... perhaps adding this patch (assuming it was added), is what
broke printer accounting for me (hint).
I don't think 2.1.3-6 includes the patch. The control file is unchanged,
so I don't see how that would break accounting. I'm currently using my
patched version with lpr 0.48-1.
I suppose netatalk 2.1.3-6 and lpr 0.46-1 would work if the printer
operator were in the "root" group. Is that the case in your setup?
(The "root" user doesn't work because lpd changes that to "lp".)
I'm not sure if I understand you... yes, root can print, and I can print, and
I'm a member of root. But other users can print, that aren't a member of root,
or lp, or daemon, or anything (I've put no restrictions on printing... yet).
/var/spool/lpd is set to root.daemon, and the spool directories inside it are
set to root.lp.
Does that help?
Never mind. The difference is that you are printing Linux-to-Mac and
I am printing Mac-to-Linux. Our bugs are completely unrelated.
This should be fixed in 0.50-2, as it does not require that the
files owners/groups be changed.