Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-13 Thread P V Mathew 

On 2017-12-12 05:24, Brian Potkin wrote:

On Mon 11 Dec 2017 at 20:02:42 +, Brian Potkin wrote:


On Mon 11 Dec 2017 at 22:28:15 +0530, P V Mathew wrote:


dmesg showed some sort of infinite loop?

Oops. realize now, may be about 2-3 years ago when my var partition got
full,

had moved the var/log on to /home/ and sym-linked to it in var. May be

this is not consistent with apparmor(not sure?).

When I do that I can still print but the error_log is not written to
because cupsd cannot change the permissions on /var/log/cups (as shown
by systemctl status cups after restarting cups).

I reckon the location of /var/log and the permissions on it is the
cause of your getting an empty error_log and has nothing to do with
the subject of your report. It would occur whether or not apparmor
is installed. You can check this.

Sorry once again. Even /usr/share was as symlink.

This symlinking business happened over a period of
15 years. Each time one partition gets full I had the habit
of symlinking it to some place where space is available
rather than resizing partitions etc. When I change my
hardware, I always clone the existing system. So the
symlinks continued...

After following integri solution of mount bind for every
symlink, all is right and working fine.




any way,  pieces of dmesg|grep cups attached.  Not possible to attach full

file as similar lines keeps repeating.

Please let me know if any more input is required.

Thanks, Mathew.

 From bb.bbz2:

[ 2121.775238] audit: type=1400 audit(1513009058.480:17316): apparmor="DENIED" \
operation="chown" profile="/usr/sbin/cupsd" 
name="/home/log/cups/" \
pid=5896 comm="cupsd" requested_mask="w" denied_mask="w" 
fsuid=0 ouid=0

[ 2121.775251] audit: type=1400 audit(1513009058.480:17317): apparmor="DENIED" \
operation="capable" profile="/usr/sbin/cupsd" pid=5896 
comm="cupsd" \
capability=12  capname="net_admin"

apparmor is new to buster and I am new to apparmor; but this looks like
cupsd has been refused write permission.

intrigeri is our lifeline for things apparmor, so I have cc'ed him (her?)
for advice.

I missed this in bb.bz2:

  [ 2153.319653] cupsd[5896]: segfault at c ip 7f36a1f13f46 sp 
7ffc5bb5ba28 error 4 in libc-2.25.so[7f36a1e92000199000]

You did say cupsd crashed?

Yes. Even this issue seems to have resolved.

I am out of my depth with this sort of thing but came across

  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052

Please read and carry out the instructions in message #38 there. You
don't need sudo. How do you go on?

Did not have to do this.
I Do not use sudo(some how not my preference.), use ssh instead.

Cheers,

Brian.


Thanks for all the help.

May I remove apparmor now. Have no need for it. All this arose

because Debian had introduced it as default.   But I am happy to

have a learned a few things in between.

Regards and thanks once again for all your help.

Mathew

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-12 Thread P V Mathew 

On 2017-12-12 13:41, intrigeri wrote:

Control: tag -1 + moreinfo
Control: retitle -1 Printing is broken with AppArmor enabled if /var/log is a 
symlink to some other place

Hi,

Thanks Mathew for testing again, and Brian for adding me in the loop!
I'm Cc'ing the AppArmor team so the resolution of this problem does
not depend solely on myself :)

P V Mathew:

as requested have reinstalled apparmor
The following programs are not working
man(from command line) but man2html ok

Interesting, I don't have this problem. I notice that AppArmor
confinement was added in man-db (2.7.6.1-3), and then updated in
man-db (2.7.6.1-4). This is off-topic here so could you please report
a bug against man-db about this, including the corresponding AppArmor
denial logs? Feel free to X-Debbugs-Cc pkg-apparmor-team@.
In the meantime you can "sudo aa-disable /usr/bin/man".


cups started on reboot but by the time logged in, it had stopped.
[...]
Oops. realize now, may be about 2-3 years ago when my var partition got full,
had moved the var/log on to /home/ and sym-linked to it in var. May be
this is not consistent with apparmor(not sure?).

Right, this can cause lots of problems with AppArmor, and not only for
cupsd so I'm not going to suggest solutions that would address your
problem for cupsd only but leave other bits of your system broken.

I recommend you either:

A. bind-mount /home/log on /var/log instead of using a symlink

Thanks.
Works.
After changing all symlinks in similar way all the
reported issues(cups, man,icedove) resolved.
Regards.


B. use an AppArmor alias

# echo '/var/log/ -> /home/log/' >> /etc/apparmor.d/tunables/alias
# systemctl restart apparmor

Works?

If this works, then I suggest the cups maintainers close this bug or
tag it wontfix: with a path-based LSM like AppArmor, there's no
general solution to problems caused by such uncommon customization
applied locally by sysadmins, other than education and documentation
about AppArmor so they're able to adjust their AppArmor
configuration accordingly.

Regards,

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-12 Thread intrigeri 
Control: tag -1 + moreinfo
Control: retitle -1 Printing is broken with AppArmor enabled if /var/log is a 
symlink to some other place

Hi,

Thanks Mathew for testing again, and Brian for adding me in the loop!
I'm Cc'ing the AppArmor team so the resolution of this problem does
not depend solely on myself :)

P V Mathew:
> as requested have reinstalled apparmor

> The following programs are not working

> man(from command line) but man2html ok

Interesting, I don't have this problem. I notice that AppArmor
confinement was added in man-db (2.7.6.1-3), and then updated in
man-db (2.7.6.1-4). This is off-topic here so could you please report
a bug against man-db about this, including the corresponding AppArmor
denial logs? Feel free to X-Debbugs-Cc pkg-apparmor-team@.
In the meantime you can "sudo aa-disable /usr/bin/man".

> cups started on reboot but by the time logged in, it had stopped.
> [...]
> Oops. realize now, may be about 2-3 years ago when my var partition got full,
> had moved the var/log on to /home/ and sym-linked to it in var. May be
> this is not consistent with apparmor(not sure?).

Right, this can cause lots of problems with AppArmor, and not only for
cupsd so I'm not going to suggest solutions that would address your
problem for cupsd only but leave other bits of your system broken.

I recommend you either:

A. bind-mount /home/log on /var/log instead of using a symlink

B. use an AppArmor alias

   # echo '/var/log/ -> /home/log/' >> /etc/apparmor.d/tunables/alias
   # systemctl restart apparmor

Works?

If this works, then I suggest the cups maintainers close this bug or
tag it wontfix: with a path-based LSM like AppArmor, there's no
general solution to problems caused by such uncommon customization
applied locally by sysadmins, other than education and documentation
about AppArmor so they're able to adjust their AppArmor
configuration accordingly.

Regards,
-- 
intrigeri

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-11 Thread Brian Potkin 
On Mon 11 Dec 2017 at 20:02:42 +, Brian Potkin wrote:

> On Mon 11 Dec 2017 at 22:28:15 +0530, P V Mathew wrote:
> 
> > dmesg showed some sort of infinite loop?
> > 
> > Oops. realize now, may be about 2-3 years ago when my var partition got
> > full,
> > 
> > had moved the var/log on to /home/ and sym-linked to it in var. May be
> > 
> > this is not consistent with apparmor(not sure?).
> 
> When I do that I can still print but the error_log is not written to
> because cupsd cannot change the permissions on /var/log/cups (as shown
> by systemctl status cups after restarting cups).

I reckon the location of /var/log and the permissions on it is the
cause of your getting an empty error_log and has nothing to do with
the subject of your report. It would occur whether or not apparmor
is installed. You can check this.

> > any way,  pieces of dmesg|grep cups attached.  Not possible to attach full
> > 
> > file as similar lines keeps repeating.
> > 
> > Please let me know if any more input is required.
> 
> Thanks, Mathew.
> 
> From bb.bbz2:
> 
> [ 2121.775238] audit: type=1400 audit(1513009058.480:17316): 
> apparmor="DENIED" \
>operation="chown" profile="/usr/sbin/cupsd" 
> name="/home/log/cups/" \
>pid=5896 comm="cupsd" requested_mask="w" denied_mask="w" 
> fsuid=0 ouid=0   
> 
> [ 2121.775251] audit: type=1400 audit(1513009058.480:17317): 
> apparmor="DENIED" \
>operation="capable" profile="/usr/sbin/cupsd" pid=5896 
> comm="cupsd" \
>capability=12  capname="net_admin"
> 
> apparmor is new to buster and I am new to apparmor; but this looks like
> cupsd has been refused write permission.
> 
> intrigeri is our lifeline for things apparmor, so I have cc'ed him (her?)
> for advice.

I missed this in bb.bz2:

 [ 2153.319653] cupsd[5896]: segfault at c ip 7f36a1f13f46 sp 
7ffc5bb5ba28 error 4 in libc-2.25.so[7f36a1e92000199000]

You did say cupsd crashed?

I am out of my depth with this sort of thing but came across

 https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052

Please read and carry out the instructions in message #38 there. You
don't need sudo. How do you go on?

Cheers,

Brian.

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-11 Thread Brian Potkin 
For the attention of intrigeri:

Mathew's mail is in reply to

https://lists.debian.org/debian-printing/2017/12/msg00032.html

He and I have spent some time is looking at a number of issues he has
experienced with the printing system when upgrading from jessie to
buster. It looks like apparmor is involved. I do not experience them.


On Mon 11 Dec 2017 at 22:28:15 +0530, P V Mathew wrote:

> as requested have reinstalled apparmor
> 
> The following programs are not working
> 
> man(from command line) but man2html ok
> 
> icedove - (double free error} ---bizarre? Using standalone download of
> thunderbird for this mail.
> 
> cups started on reboot but by the time logged in, it had stopped.
> 
> cups was restarted and command
> 
> lp -d PDF a.ps was used
> 
> the subject error returned.
> 
> but eventually cups stopped again.
> 
> dmesg showed some sort of infinite loop?
> 
> Oops. realize now, may be about 2-3 years ago when my var partition got
> full,
> 
> had moved the var/log on to /home/ and sym-linked to it in var. May be
> 
> this is not consistent with apparmor(not sure?).

When I do that I can still print but the error_log is not written to
because cupsd cannot change the permissions on /var/log/cups (as shown
by systemctl status cups after restarting cups).

> any way,  pieces of dmesg|grep cups attached.  Not possible to attach full
> 
> file as similar lines keeps repeating.
> 
> Please let me know if any more input is required.

Thanks, Mathew.

>From bb.bbz2:

[ 2121.775238] audit: type=1400 audit(1513009058.480:17316): apparmor="DENIED" \
   operation="chown" profile="/usr/sbin/cupsd" 
name="/home/log/cups/" \
   pid=5896 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 
ouid=0   

[ 2121.775251] audit: type=1400 audit(1513009058.480:17317): apparmor="DENIED" \
   operation="capable" profile="/usr/sbin/cupsd" pid=5896 
comm="cupsd" \
   capability=12  capname="net_admin"

apparmor is new to buster and I am new to apparmor; but this looks like
cupsd has been refused write permission.

intrigeri is our lifeline for things apparmor, so I have cc'ed him (her?)
for advice.

Cheers,

Brian.

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-11 Thread P V Mathew 

as requested have reinstalled apparmor

The following programs are not working

man(from command line) but man2html ok

icedove - (double free error} ---bizarre? Using standalone download of 
thunderbird for this mail.


cups started on reboot but by the time logged in, it had stopped.

cups was restarted and command

lp -d PDF a.ps was used

the subject error returned.

but eventually cups stopped again.

dmesg showed some sort of infinite loop?

Oops. realize now, may be about 2-3 years ago when my var partition got 
full,


had moved the var/log on to /home/ and sym-linked to it in var. May be

this is not consistent with apparmor(not sure?).

any way,  pieces of dmesg|grep cups attached.  Not possible to attach full

file as similar lines keeps repeating.

Please let me know if any more input is required.

Regards

Mathew




bb.bz2
Description: application/bzip


a.bz2
Description: application/bzip

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-11 Thread Mathew pv 
Sure, no problem.

On 11 Dec 2017 19:51, "Brian Potkin"  wrote:

> On Mon 11 Dec 2017 at 09:01:58 +, Brian Potkin wrote:
>
> > On Sun 10 Dec 2017 at 22:53:02 +0530, P V Mathew wrote:
> >
> > > Thanks for all the help.
> > >
> > > Just uninstalled AppArmor and
> > > rebooted the system.
> > >
> > > Everything fine now.
> > >
> > > Even localhost:631 is fine.
> >
> > Excellent.
> >
> > > Sorry once again for the trouble.
> >
> > It was an interesting issue; no trouble.
>
> But now I would like to impose on your good will.
>
> I do not know if you are aware of it, but apparmor has been activated
> as an experiment in buster to see if it would be suitable in a stable
> release. Would you reinstall it and look for "audit" in journalctl or
> syslog when your printing fails and the connection to localhost:631
> resets. It would be useful for us to have any error messages.
>
> Cheers,
>
> Brian.
>

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-11 Thread Brian Potkin 
On Mon 11 Dec 2017 at 09:01:58 +, Brian Potkin wrote:

> On Sun 10 Dec 2017 at 22:53:02 +0530, P V Mathew wrote:
> 
> > Thanks for all the help.
> > 
> > Just uninstalled AppArmor and
> > rebooted the system.
> > 
> > Everything fine now.
> > 
> > Even localhost:631 is fine.
> 
> Excellent.
> 
> > Sorry once again for the trouble.
> 
> It was an interesting issue; no trouble.

But now I would like to impose on your good will.

I do not know if you are aware of it, but apparmor has been activated
as an experiment in buster to see if it would be suitable in a stable
release. Would you reinstall it and look for "audit" in journalctl or
syslog when your printing fails and the connection to localhost:631
resets. It would be useful for us to have any error messages.

Cheers,

Brian.

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-11 Thread Brian Potkin 
On Sun 10 Dec 2017 at 22:53:02 +0530, P V Mathew wrote:

> Thanks for all the help.
> 
> Just uninstalled AppArmor and
> rebooted the system.
> 
> Everything fine now.
> 
> Even localhost:631 is fine.

Excellent.

> Sorry once again for the trouble.

It was an interesting issue; no trouble.


> Regards and Best Wishes

And to you, Mathew.

Brian.

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-10 Thread P V Mathew 


Thanks for all the help.

Just uninstalled AppArmor and
rebooted the system.

Everything fine now.

Even localhost:631 is fine.

Sorry once again for the trouble.

Regards and Best Wishes
Mathew

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-10 Thread P V Mathew 

On 2017-12-10 22:05, Brian Potkin wrote:

On Sun 10 Dec 2017 at 19:33:58 +0530, P V Mathew wrote:


On 2017-12-10 18:41, Brian Potkin wrote:

Part of your log has

   DEBUG: envp[1]="CONTENT_TYPE=text/plain"

CUPS has identified the job as being a text file. All the filters
complete successfully and the output is a PostScript file. All is
well with the cupsfilters command - but now I am mystified.

cupsfilter does the same as CUPS except the final file is not sent
to a printer. 'lp -d  filename.ps' gives

   Unsupported document-format "application/octet-stream"
and this is an indication of CUPS being unable to MIME type the
submitted file. But it has MIME typed it with cupsfilter!

I can reproduce your observation of the error message by moving
mime.types out of /usr/share/cups/mime, but then cupsfilter fails
to run to completion. I cannot reproduce the empty error_log you
get; mine records the error. That's using my cupsd.conf.

I take a further look at the issue later today. Meanwhile you could
check that the files in /usr/share/cups/mime are what is in the
cups-core-drivers and cups-daemon packages.

Have checked files in /usr/share/cups/mime.
Other than cups-core-drivers and cups-daemon packages
there are some more files in the directory.
attaching listing of the directory.  Only issue is that some
.convs(cupsfilters-ghostscript, cupsfilters-mupdf, cupsfilters-poppler)
files do not have have the corresponding .types
files and command.types does not have any corresponding
command.convs.

Nothing to worry about there; I have the same.
  

Also the issue of connection getting reset on trying
http://localhost:631 stil remains. This will mean that
I will not be able to do any printer administration.

Has this been mentioned before? There are command line utilities to do
printer administration.

Yes. Briefly in one of my mails.

What do you get with

lp -d PDF -o document-format=text/plain /etc/nsswitch ?

Printing? Error message?

>lp -d PDF -o document-format=text/plain /etc/nsswitch.conf
lp: Unsupported document-format "text/plain".

No error logs. Logging seems to have stopped after  last update of Debian.
Not even access log.

Regards
Mathew

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-10 Thread Brian Potkin 
On Sun 10 Dec 2017 at 19:33:58 +0530, P V Mathew wrote:

> On 2017-12-10 18:41, Brian Potkin wrote:
> > 
> > Part of your log has
> > 
> >   DEBUG: envp[1]="CONTENT_TYPE=text/plain"
> > 
> > CUPS has identified the job as being a text file. All the filters
> > complete successfully and the output is a PostScript file. All is
> > well with the cupsfilters command - but now I am mystified.
> > 
> > cupsfilter does the same as CUPS except the final file is not sent
> > to a printer. 'lp -d  filename.ps' gives
> > 
> >   Unsupported document-format "application/octet-stream"
> > and this is an indication of CUPS being unable to MIME type the
> > submitted file. But it has MIME typed it with cupsfilter!
> > 
> > I can reproduce your observation of the error message by moving
> > mime.types out of /usr/share/cups/mime, but then cupsfilter fails
> > to run to completion. I cannot reproduce the empty error_log you
> > get; mine records the error. That's using my cupsd.conf.
> > 
> > I take a further look at the issue later today. Meanwhile you could
> > check that the files in /usr/share/cups/mime are what is in the
> > cups-core-drivers and cups-daemon packages.
> Have checked files in /usr/share/cups/mime.
> Other than cups-core-drivers and cups-daemon packages
> there are some more files in the directory.
> attaching listing of the directory.  Only issue is that some
> .convs(cupsfilters-ghostscript, cupsfilters-mupdf, cupsfilters-poppler)
> files do not have have the corresponding .types
> files and command.types does not have any corresponding
> command.convs.

Nothing to worry about there; I have the same.
 
> Also the issue of connection getting reset on trying
> http://localhost:631 stil remains. This will mean that
> I will not be able to do any printer administration.

Has this been mentioned before? There are command line utilities to do
printer administration.

What do you get with

lp -d PDF -o document-format=text/plain /etc/nsswitch ?

Printing? Error message?

Cheers,

Brian.

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-10 Thread P V Mathew 


On 2017-12-10 18:41, Brian Potkin wrote:

On Sun 10 Dec 2017 at 15:04:12 +0530, P V Mathew wrote:


thanks.

On 2017-12-10 01:34, Brian Potkin wrote:

tags 883765 unreproducible
thanks.


On Sat 09 Dec 2017 at 20:06:28 +0530, P V Mathew wrote:


Sorry for the delay.
Unfortunately had to downgrade my desktop to Debian stretch. That is okay
now.

At least you are printing now.

Yes, from stretch.

We will try to improve on that.


The same errors occur on laptop(Debian Buster) also.  Hence, will send the
details.
Tried lp -d PDF a.ps. The subject error is printed again.

I am unable to reproduce this behaviour with printer-driver-cups-pdf.


The error_log remains empty.

Or this. Please try (as root)

   cupsfilter -p /etc/cups/PDF.ppd -m printer/foo -e /etc/services > 2>log > 
out.ps

log attached

Post log here.


The access_log remains empty.
The cups-pdf_log remains empty.
cupsd.conf is attached.

Your cupsd.conf worked for me.


also output of dpkg --get-selections |grep cups is attached.

Seems ok.

Do you have apparmor running?

Installed but not running.

No problem there, then.

Part of your log has

  DEBUG: envp[1]="CONTENT_TYPE=text/plain"

CUPS has identified the job as being a text file. All the filters
complete successfully and the output is a PostScript file. All is
well with the cupsfilters command - but now I am mystified.

cupsfilter does the same as CUPS except the final file is not sent
to a printer. 'lp -d  filename.ps' gives

  Unsupported document-format "application/octet-stream"
and this is an indication of CUPS being unable to MIME type the
submitted file. But it has MIME typed it with cupsfilter!

I can reproduce your observation of the error message by moving
mime.types out of /usr/share/cups/mime, but then cupsfilter fails
to run to completion. I cannot reproduce the empty error_log you
get; mine records the error. That's using my cupsd.conf.

I take a further look at the issue later today. Meanwhile you could
check that the files in /usr/share/cups/mime are what is in the
cups-core-drivers and cups-daemon packages.

Have checked files in /usr/share/cups/mime.
Other than cups-core-drivers and cups-daemon packages
there are some more files in the directory.
attaching listing of the directory.  Only issue is that some
.convs(cupsfilters-ghostscript, cupsfilters-mupdf, cupsfilters-poppler)
files do not have have the corresponding .types
files and command.types does not have any corresponding
command.convs.

Also the issue of connection getting reset on trying
http://localhost:631 stil remains. This will mean that
I will not be able to do any printer administration.

Regards
Mathew


mimeFiles.bz2
Description: application/bzip

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-10 Thread Brian Potkin 
On Sun 10 Dec 2017 at 15:04:12 +0530, P V Mathew wrote:

> thanks.
> 
> On 2017-12-10 01:34, Brian Potkin wrote:
> > tags 883765 unreproducible
> > thanks.
> > 
> > 
> > On Sat 09 Dec 2017 at 20:06:28 +0530, P V Mathew wrote:
> > 
> > > Sorry for the delay.
> > > Unfortunately had to downgrade my desktop to Debian stretch. That is okay
> > > now.
> > At least you are printing now.
> Yes, from stretch.

We will try to improve on that.

> > > The same errors occur on laptop(Debian Buster) also.  Hence, will send the
> > > details.
> > > Tried lp -d PDF a.ps. The subject error is printed again.
> > I am unable to reproduce this behaviour with printer-driver-cups-pdf.
> > 
> > > The error_log remains empty.
> > Or this. Please try (as root)
> > 
> >   cupsfilter -p /etc/cups/PDF.ppd -m printer/foo -e /etc/services > 2>log > 
> > out.ps
> log attached
> > 
> > Post log here.
> > 
> > > The access_log remains empty.
> > > The cups-pdf_log remains empty.
> > > cupsd.conf is attached.
> > Your cupsd.conf worked for me.
> > 
> > > also output of dpkg --get-selections |grep cups is attached.
> > Seems ok.
> > 
> > Do you have apparmor running?
> Installed but not running.

No problem there, then.

Part of your log has

 DEBUG: envp[1]="CONTENT_TYPE=text/plain"

CUPS has identified the job as being a text file. All the filters
complete successfully and the output is a PostScript file. All is
well with the cupsfilters command - but now I am mystified.

cupsfilter does the same as CUPS except the final file is not sent
to a printer. 'lp -d  filename.ps' gives

 Unsupported document-format "application/octet-stream"

and this is an indication of CUPS being unable to MIME type the
submitted file. But it has MIME typed it with cupsfilter!

I can reproduce your observation of the error message by moving
mime.types out of /usr/share/cups/mime, but then cupsfilter fails
to run to completion. I cannot reproduce the empty error_log you
get; mine records the error. That's using my cupsd.conf.

I take a further look at the issue later today. Meanwhile you could
check that the files in /usr/share/cups/mime are what is in the
cups-core-drivers and cups-daemon packages.

Cheers,

Brian.

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-10 Thread P V Mathew 

thanks.

On 2017-12-10 01:34, Brian Potkin wrote:

tags 883765 unreproducible
thanks.


On Sat 09 Dec 2017 at 20:06:28 +0530, P V Mathew wrote:


Sorry for the delay.
Unfortunately had to downgrade my desktop to Debian stretch. That is okay
now.

At least you are printing now.

Yes, from stretch.

The same errors occur on laptop(Debian Buster) also.  Hence, will send the
details.
Tried lp -d PDF a.ps. The subject error is printed again.

I am unable to reproduce this behaviour with printer-driver-cups-pdf.


The error_log remains empty.

Or this. Please try (as root)

  cupsfilter -p /etc/cups/PDF.ppd -m printer/foo -e /etc/services > 2>log > 
out.ps

log attached


Post log here.


The access_log remains empty.
The cups-pdf_log remains empty.
cupsd.conf is attached.

Your cupsd.conf worked for me.


also output of dpkg --get-selections |grep cups is attached.

Seems ok.

Do you have apparmor running?

Installed but not running.

regards

Mathew



log.bz2
Description: application/bzip

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-09 Thread Brian Potkin 
tags 883765 unreproducible
thanks.


On Sat 09 Dec 2017 at 20:06:28 +0530, P V Mathew wrote:

> Sorry for the delay.
> Unfortunately had to downgrade my desktop to Debian stretch. That is okay
> now.

At least you are printing now.

> The same errors occur on laptop(Debian Buster) also.  Hence, will send the
> details.
> Tried lp -d PDF a.ps. The subject error is printed again.

I am unable to reproduce this behaviour with printer-driver-cups-pdf.

> The error_log remains empty.

Or this. Please try (as root)

 cupsfilter -p /etc/cups/PDF.ppd -m printer/foo -e /etc/services > 2>log > 
out.ps

Post log here.

> The access_log remains empty.
> The cups-pdf_log remains empty.
> cupsd.conf is attached.

Your cupsd.conf worked for me.

> also output of dpkg --get-selections |grep cups is attached.

Seems ok.

Do you have apparmor running?

 systemctl status apparmor.service

Regards,

Brian.

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-09 Thread P V Mathew 

missing attachment in last mail
 output of dpkg --get-selections |grep cups is attached.

Regards
P V Mathew

On 2017-12-08 16:12, Brian Potkin wrote:

Do not forget to include the bug in any reply, P V. You sent the last
mail only to me.


On Fri 08 Dec 2017 at 12:07:43 +0530, P V Mathew wrote:


Thanks for your prompt reply.
(1) The same error occurs for every printer chosen, even for PDF printer.

An error_log is needed. Let us have have one for the  PDF printer and
we'll go from there.


(2) Before update of Debian Buster yesterday every thing was ok.
(3) Firefox replies--Connection reset--- for localhost:631
(4) Tried removing and reinstalling cups in buster.
(5) Looks more like a Debian Buster problem as many other programs(icedove,
file, man etc)
     are not workinag.

This looks like a problem with the upgrade rather than something
specific to the printing system.


(6)as desired, output of lpstat -t is given below.
==
cups>lpstat -t
scheduler is running
system default destination: RA
device for ETD: socket://10.53.54.27
device for HP_deskjet_5100: hp:/usb/deskjet_5100?serial=MY37G3N13T8B
device for HP_LaserJet_Pro_M202dw:
hp:/usb/HP_LaserJet_Pro_M202dw?serial=VNC3J23029
device for HP_LaserJet_Pro_M202dw_01FF68_:
ipp://NPI01FF68.local:631/ipp/print
device for HP_PVM: socket://192.168.192.198
device for Kyocera_TASKalfa_3510i: socket://10.53.100.155
device for Kyocera_TASKalfa_3510i_71_: ipps://KM25E478.local:443/ipp/print
device for NehaMangal: socket://192.168.192.198
device for RA: socket://192.168.193.201
device for RitwikAnand: socket://192.168.192.201
device for SudhirBishnoi:
hp:/net/HP_LaserJet_Professional_P1606dn?ip=10.53.40.5
ETD accepting requests since 2017-11-20T14:57:01 IST
HP_deskjet_5100 accepting requests since 2016-05-19T16:13:04 IST
HP_LaserJet_Pro_M202dw accepting requests since 2016-03-28T11:10:41 IST
HP_LaserJet_Pro_M202dw_01FF68_ accepting requests since 2017-12-08T11:50:59
IST
HP_PVM accepting requests since 2017-03-17T09:13:21 IST
Kyocera_TASKalfa_3510i accepting requests since 2016-12-13T11:53:40 IST
Kyocera_TASKalfa_3510i_71_ accepting requests since 2017-12-08T11:50:59 IST
NehaMangal accepting requests since 2017-03-20T12:40:19 IST
RA accepting requests since 2017-12-06T17:00:12 IST
RitwikAnand accepting requests since 2017-05-15T11:14:20 IST
SudhirBishnoi accepting requests since 2016-12-16T14:30:51 IST
printer ETD is idle.  enabled since 2017-11-20T14:57:01 IST
printer HP_deskjet_5100 disabled since 2016-05-19T16:13:04 IST -
     Backend /usr/lib/cups/backend/hp does not exist!

Is hplip installed?


printer HP_LaserJet_Pro_M202dw disabled since 2016-03-28T11:10:41 IST -
     File "/usr/lib/cups/filter/hpps" not available: No such file or
directory
printer HP_LaserJet_Pro_M202dw_01FF68_ is idle.  enabled since
2017-12-08T11:50:59 IST
printer HP_PVM is idle.  enabled since 2017-03-17T09:13:21 IST
printer Kyocera_TASKalfa_3510i is idle.  enabled since 2016-12-13T11:53:40
IST
printer Kyocera_TASKalfa_3510i_71_ is idle.  enabled since
2017-12-08T11:50:59 IST
printer NehaMangal is idle.  enabled since 2017-03-20T12:40:19 IST
printer RA is idle.  enabled since 2017-12-06T17:00:12 IST
printer RitwikAnand is idle.  enabled since 2017-05-15T11:14:20 IST
printer SudhirBishnoi disabled since 2016-12-16T14:30:51 IST -
     Backend /usr/lib/cups/backend/hp does not exist!
===

I can understand the HP printers not working if there is no hp backend,
but not any of the other printers. We really need error_logs.

Regards,

Brian.





InstalledPackages.tbz
Description: application/bzip-compressed-tar

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-09 Thread P V Mathew 

Sorry for the delay.
Unfortunately had to downgrade my desktop to Debian stretch. That is 
okay now.
The same errors occur on laptop(Debian Buster) also.  Hence, will send 
the details.

Tried lp -d PDF a.ps. The subject error is printed again.
The error_log remains empty.
The access_log remains empty.
The cups-pdf_log remains empty.
cupsd.conf is attached.
also output of dpkg --get-selections |grep cups is attached.

Regards
P V Mathew

On 2017-12-08 16:12, Brian Potkin wrote:

Do not forget to include the bug in any reply, P V. You sent the last
mail only to me.


On Fri 08 Dec 2017 at 12:07:43 +0530, P V Mathew wrote:


Thanks for your prompt reply.
(1) The same error occurs for every printer chosen, even for PDF printer.

An error_log is needed. Let us have have one for the  PDF printer and
we'll go from there.


(2) Before update of Debian Buster yesterday every thing was ok.
(3) Firefox replies--Connection reset--- for localhost:631
(4) Tried removing and reinstalling cups in buster.
(5) Looks more like a Debian Buster problem as many other programs(icedove,
file, man etc)
     are not workinag.

This looks like a problem with the upgrade rather than something
specific to the printing system.


(6)as desired, output of lpstat -t is given below.
==
cups>lpstat -t
scheduler is running
system default destination: RA
device for ETD: socket://10.53.54.27
device for HP_deskjet_5100: hp:/usb/deskjet_5100?serial=MY37G3N13T8B
device for HP_LaserJet_Pro_M202dw:
hp:/usb/HP_LaserJet_Pro_M202dw?serial=VNC3J23029
device for HP_LaserJet_Pro_M202dw_01FF68_:
ipp://NPI01FF68.local:631/ipp/print
device for HP_PVM: socket://192.168.192.198
device for Kyocera_TASKalfa_3510i: socket://10.53.100.155
device for Kyocera_TASKalfa_3510i_71_: ipps://KM25E478.local:443/ipp/print
device for NehaMangal: socket://192.168.192.198
device for RA: socket://192.168.193.201
device for RitwikAnand: socket://192.168.192.201
device for SudhirBishnoi:
hp:/net/HP_LaserJet_Professional_P1606dn?ip=10.53.40.5
ETD accepting requests since 2017-11-20T14:57:01 IST
HP_deskjet_5100 accepting requests since 2016-05-19T16:13:04 IST
HP_LaserJet_Pro_M202dw accepting requests since 2016-03-28T11:10:41 IST
HP_LaserJet_Pro_M202dw_01FF68_ accepting requests since 2017-12-08T11:50:59
IST
HP_PVM accepting requests since 2017-03-17T09:13:21 IST
Kyocera_TASKalfa_3510i accepting requests since 2016-12-13T11:53:40 IST
Kyocera_TASKalfa_3510i_71_ accepting requests since 2017-12-08T11:50:59 IST
NehaMangal accepting requests since 2017-03-20T12:40:19 IST
RA accepting requests since 2017-12-06T17:00:12 IST
RitwikAnand accepting requests since 2017-05-15T11:14:20 IST
SudhirBishnoi accepting requests since 2016-12-16T14:30:51 IST
printer ETD is idle.  enabled since 2017-11-20T14:57:01 IST
printer HP_deskjet_5100 disabled since 2016-05-19T16:13:04 IST -
     Backend /usr/lib/cups/backend/hp does not exist!

Is hplip installed?


printer HP_LaserJet_Pro_M202dw disabled since 2016-03-28T11:10:41 IST -
     File "/usr/lib/cups/filter/hpps" not available: No such file or
directory
printer HP_LaserJet_Pro_M202dw_01FF68_ is idle.  enabled since
2017-12-08T11:50:59 IST
printer HP_PVM is idle.  enabled since 2017-03-17T09:13:21 IST
printer Kyocera_TASKalfa_3510i is idle.  enabled since 2016-12-13T11:53:40
IST
printer Kyocera_TASKalfa_3510i_71_ is idle.  enabled since
2017-12-08T11:50:59 IST
printer NehaMangal is idle.  enabled since 2017-03-20T12:40:19 IST
printer RA is idle.  enabled since 2017-12-06T17:00:12 IST
printer RitwikAnand is idle.  enabled since 2017-05-15T11:14:20 IST
printer SudhirBishnoi disabled since 2016-12-16T14:30:51 IST -
     Backend /usr/lib/cups/backend/hp does not exist!
===

I can understand the HP printers not working if there is no hp backend,
but not any of the other printers. We really need error_logs.

Regards,

Brian.



cupsd.conf.tbz
Description: application/bzip-compressed-tar

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-08 Thread Brian Potkin 
Do not forget to include the bug in any reply, P V. You sent the last
mail only to me.


On Fri 08 Dec 2017 at 12:07:43 +0530, P V Mathew wrote:

> Thanks for your prompt reply.
> (1) The same error occurs for every printer chosen, even for PDF printer.

An error_log is needed. Let us have have one for the  PDF printer and
we'll go from there.

> (2) Before update of Debian Buster yesterday every thing was ok.
> (3) Firefox replies--Connection reset--- for localhost:631
> (4) Tried removing and reinstalling cups in buster.
> (5) Looks more like a Debian Buster problem as many other programs(icedove,
> file, man etc)
>     are not workinag.

This looks like a problem with the upgrade rather than something
specific to the printing system. 

> (6)as desired, output of lpstat -t is given below.
> ==
> cups>lpstat -t
> scheduler is running
> system default destination: RA
> device for ETD: socket://10.53.54.27
> device for HP_deskjet_5100: hp:/usb/deskjet_5100?serial=MY37G3N13T8B
> device for HP_LaserJet_Pro_M202dw:
> hp:/usb/HP_LaserJet_Pro_M202dw?serial=VNC3J23029
> device for HP_LaserJet_Pro_M202dw_01FF68_:
> ipp://NPI01FF68.local:631/ipp/print
> device for HP_PVM: socket://192.168.192.198
> device for Kyocera_TASKalfa_3510i: socket://10.53.100.155
> device for Kyocera_TASKalfa_3510i_71_: ipps://KM25E478.local:443/ipp/print
> device for NehaMangal: socket://192.168.192.198
> device for RA: socket://192.168.193.201
> device for RitwikAnand: socket://192.168.192.201
> device for SudhirBishnoi:
> hp:/net/HP_LaserJet_Professional_P1606dn?ip=10.53.40.5
> ETD accepting requests since 2017-11-20T14:57:01 IST
> HP_deskjet_5100 accepting requests since 2016-05-19T16:13:04 IST
> HP_LaserJet_Pro_M202dw accepting requests since 2016-03-28T11:10:41 IST
> HP_LaserJet_Pro_M202dw_01FF68_ accepting requests since 2017-12-08T11:50:59
> IST
> HP_PVM accepting requests since 2017-03-17T09:13:21 IST
> Kyocera_TASKalfa_3510i accepting requests since 2016-12-13T11:53:40 IST
> Kyocera_TASKalfa_3510i_71_ accepting requests since 2017-12-08T11:50:59 IST
> NehaMangal accepting requests since 2017-03-20T12:40:19 IST
> RA accepting requests since 2017-12-06T17:00:12 IST
> RitwikAnand accepting requests since 2017-05-15T11:14:20 IST
> SudhirBishnoi accepting requests since 2016-12-16T14:30:51 IST
> printer ETD is idle.  enabled since 2017-11-20T14:57:01 IST
> printer HP_deskjet_5100 disabled since 2016-05-19T16:13:04 IST -
>     Backend /usr/lib/cups/backend/hp does not exist!

Is hplip installed?

> printer HP_LaserJet_Pro_M202dw disabled since 2016-03-28T11:10:41 IST -
>     File "/usr/lib/cups/filter/hpps" not available: No such file or
> directory
> printer HP_LaserJet_Pro_M202dw_01FF68_ is idle.  enabled since
> 2017-12-08T11:50:59 IST
> printer HP_PVM is idle.  enabled since 2017-03-17T09:13:21 IST
> printer Kyocera_TASKalfa_3510i is idle.  enabled since 2016-12-13T11:53:40
> IST
> printer Kyocera_TASKalfa_3510i_71_ is idle.  enabled since
> 2017-12-08T11:50:59 IST
> printer NehaMangal is idle.  enabled since 2017-03-20T12:40:19 IST
> printer RA is idle.  enabled since 2017-12-06T17:00:12 IST
> printer RitwikAnand is idle.  enabled since 2017-05-15T11:14:20 IST
> printer SudhirBishnoi disabled since 2016-12-16T14:30:51 IST -
>     Backend /usr/lib/cups/backend/hp does not exist!
> ===

I can understand the HP printers not working if there is no hp backend,
but not any of the other printers. We really need error_logs.

Regards,

Brian.

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-08 Thread P V Mathew 

Thanks for your prompt reply.
(1) The same error occurs for every printer chosen, even for PDF printer.
(2) Before update of Debian Buster yesterday every thing was ok.
(3) Firefox replies--Connection reset--- for localhost:631
(4) Tried removing and reinstalling cups in buster.
(5) Looks more like a Debian Buster problem as many other 
programs(icedove, file, man etc)

    are not working.
(6)as desired, output of lpstat -t is given below.
==
cups>lpstat -t
scheduler is running
system default destination: RA
device for ETD: socket://10.53.54.27
device for HP_deskjet_5100: hp:/usb/deskjet_5100?serial=MY37G3N13T8B
device for HP_LaserJet_Pro_M202dw: 
hp:/usb/HP_LaserJet_Pro_M202dw?serial=VNC3J23029
device for HP_LaserJet_Pro_M202dw_01FF68_: 
ipp://NPI01FF68.local:631/ipp/print

device for HP_PVM: socket://192.168.192.198
device for Kyocera_TASKalfa_3510i: socket://10.53.100.155
device for Kyocera_TASKalfa_3510i_71_: ipps://KM25E478.local:443/ipp/print
device for NehaMangal: socket://192.168.192.198
device for RA: socket://192.168.193.201
device for RitwikAnand: socket://192.168.192.201
device for SudhirBishnoi: 
hp:/net/HP_LaserJet_Professional_P1606dn?ip=10.53.40.5

ETD accepting requests since 2017-11-20T14:57:01 IST
HP_deskjet_5100 accepting requests since 2016-05-19T16:13:04 IST
HP_LaserJet_Pro_M202dw accepting requests since 2016-03-28T11:10:41 IST
HP_LaserJet_Pro_M202dw_01FF68_ accepting requests since 
2017-12-08T11:50:59 IST

HP_PVM accepting requests since 2017-03-17T09:13:21 IST
Kyocera_TASKalfa_3510i accepting requests since 2016-12-13T11:53:40 IST
Kyocera_TASKalfa_3510i_71_ accepting requests since 2017-12-08T11:50:59 IST
NehaMangal accepting requests since 2017-03-20T12:40:19 IST
RA accepting requests since 2017-12-06T17:00:12 IST
RitwikAnand accepting requests since 2017-05-15T11:14:20 IST
SudhirBishnoi accepting requests since 2016-12-16T14:30:51 IST
printer ETD is idle.  enabled since 2017-11-20T14:57:01 IST
printer HP_deskjet_5100 disabled since 2016-05-19T16:13:04 IST -
    Backend /usr/lib/cups/backend/hp does not exist!
printer HP_LaserJet_Pro_M202dw disabled since 2016-03-28T11:10:41 IST -
    File "/usr/lib/cups/filter/hpps" not available: No such file or 
directory
printer HP_LaserJet_Pro_M202dw_01FF68_ is idle.  enabled since 
2017-12-08T11:50:59 IST

printer HP_PVM is idle.  enabled since 2017-03-17T09:13:21 IST
printer Kyocera_TASKalfa_3510i is idle.  enabled since 
2016-12-13T11:53:40 IST
printer Kyocera_TASKalfa_3510i_71_ is idle.  enabled since 
2017-12-08T11:50:59 IST

printer NehaMangal is idle.  enabled since 2017-03-20T12:40:19 IST
printer RA is idle.  enabled since 2017-12-06T17:00:12 IST
printer RitwikAnand is idle.  enabled since 2017-05-15T11:14:20 IST
printer SudhirBishnoi disabled since 2016-12-16T14:30:51 IST -
    Backend /usr/lib/cups/backend/hp does not exist!
===

Thanks.
On 2017-12-07 18:17, Brian Potkin wrote:

tags 883765 moreinfo
thanks


Thank you for your report, P V Mathew,


On Thu 07 Dec 2017 at 15:59:35 +0530, P V Mathew wrote:


Package: cups-client
Version: 2.2.6-2
Severity: normal

Dear Maintainer,


After update today, trying to print  postscript/pdf file resulted in the
error:
lp:Unsupported document-format "application/octet-stream".

Same issue with pdf files also.

commands used:
lp -d  filename.ps
lp -d  filename.pdf

The printer make and model, please. Network or USB? See

https://wiki.debian.org/DissectingandDebuggingtheCUPSPrintingSystem

on how to get an error_log. Compress it before sending it here. Give the
output of 'lpstat -t'.

Regards,

Brian.

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-07 Thread Brian Potkin 
tags 883765 moreinfo
thanks


Thank you for your report, P V Mathew,


On Thu 07 Dec 2017 at 15:59:35 +0530, P V Mathew wrote:

> Package: cups-client
> Version: 2.2.6-2
> Severity: normal
> 
> Dear Maintainer,
> 
> 
> After update today, trying to print  postscript/pdf file resulted in the
> error: 
> lp:Unsupported document-format "application/octet-stream".
> 
> Same issue with pdf files also.
> 
> commands used:
>   lp -d  filename.ps
>   lp -d  filename.pdf 

The printer make and model, please. Network or USB? See

https://wiki.debian.org/DissectingandDebuggingtheCUPSPrintingSystem

on how to get an error_log. Compress it before sending it here. Give the
output of 'lpstat -t'.

Regards,

Brian.

Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-07 Thread P V Mathew 
Package: cups-client
Version: 2.2.6-2
Severity: normal

Dear Maintainer,


After update today, trying to print  postscript/pdf file resulted in the
error: 
lp:Unsupported document-format "application/octet-stream".

Same issue with pdf files also.

commands used:
lp -d  filename.ps
lp -d  filename.pdf 


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ml_IN.utf8, LC_CTYPE=ml_IN.utf8 (charmap=UTF-8), 
LANGUAGE=ml_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cups-client depends on:
ii  adduser3.116
ii  cups-common2.2.6-2
ii  libc6  2.25-2
ii  libcups2   2.2.6-2
ii  libcupsimage2  2.2.6-2

cups-client recommends no packages.

Versions of packages cups-client suggests:
ii  cups   2.2.6-2
ii  cups-bsd   2.2.6-2
pn  smbclient  
ii  xpp1.5-cvs20081009-3

-- no debconf information