Bug 355005 - no notification on printing failure
Summary: no notification on printing failure
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: printing (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-11-07 19:50 UTC by jrollins
Modified: 2018-10-27 02:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jrollins 2015-11-07 19:50:49 UTC
The Debian package of okular will silently fail to print if the cups-bsd package is not installed.  The only indication that there is something wrong is the following the terminal output if okular was opened from a terminal:

usage: lpr [-cdfghlmnpqrstv] [-#num] [-1234 font] [-C class] [-i [numcols]]
        [-J job] [-Pprinter] [-T title] [-U user] [-wnum] [name ...]

If okular was not opened from the terminal it just silently fails to print, with absolutely no notification to the user that anything is amiss.  This is incredibly aggravating if the printer is somewhere far away.

It would be great if okular could display a notification to the user of these printer failures.  Okular should be able to figure out that the correct dependencies are not installed, and notify the user that printing will not be possible until they are.  This would alleviate a lot of aggravation on the part of the users who don't have the necessary packages installed.

Thanks so much.  

Reproducible: Always

Steps to Reproduce:
1. open a document in okular
2. attempt to print
3.
Comment 1 jrollins 2015-11-07 19:53:17 UTC
There are Debian bugs about this issue, but their resolution involved making sure that the needed cups-bsd package was included as a package Recommends.  They don't solve the overall problem of okular not notifying the user of the problem if the cups-bsd package was never installed for whatever reason:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748533
Comment 2 Albert Astals Cid 2015-11-10 23:43:14 UTC
Which package provides lpr if not cups-bsd?

What is the exit status of that lpr command if passed some random crap in the command line (so it gives you that usage output). You can know the exit status by doing
  lpr somecrap
  echo $?
Comment 3 jrollins 2015-11-14 16:19:54 UTC
(In reply to Albert Astals Cid from comment #2)
> Which package provides lpr if not cups-bsd?

There are two packages in Debian that provide a command called 'lpr': lpr and cups-bsd.  I don't quite understand the difference between them.  From the description:

lpr: BSD lpr/lpd line printer spooling system
cups-bsd: Common UNIX Printing System(tm) - BSD commands

> What is the exit status of that lpr command if passed some random crap in
> the command line (so it gives you that usage output). You can know the exit
> status by doing
>   lpr somecrap
>   echo $?

This command does not produce the output that I see from okular:

servo:~ 0$ lpr somecrap
lpr: cannot open somecrap: No such file or directory
servo:~ 1$ 

So presumably that's not the command being issued by okular.
Comment 4 Albert Astals Cid 2015-11-24 23:05:59 UTC
> So presumably that's not the command being issued by okular.
True, you can find the command line okular uses by running kdebugdialog and enabling all okular debug ouput in there and then trying to print.

For me it'd be something as
lpr -P Deskjet_3050A_J611 -#1 -J entrada_hill_of_freedom.pdf -o media=A4 -o portrait -o sides=one-sided -o outputorder=normal -o Collate=False -o page-left=10 -o page-top=10 -o page-right=10 -o page-bottom=10 -o fit-to-page -o PageSize=A4 -o ColorModel=CMYGray -o OutputMode=FastDraft -r /tmp/kde-tsdgeosDitoDT/okularc11740.ps
Comment 5 Andrew Crouthamel 2018-09-25 21:52:34 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 02:47:21 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!