Bug 345789 - Printing stall Okular if network printer is offline
Summary: Printing stall Okular if network printer is offline
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: printing (show other bugs)
Version: 0.20.2
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-02 04:34 UTC by thekernel
Modified: 2018-11-30 04:04 UTC (History)
2 users (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 thekernel 2015-04-02 04:34:43 UTC
I have a Office box that supplies a shared printer, but this box is sometimes off.

Laptop running kubuntu, printing to file, .pdf
Stalls okular
The option to print eventually appears, but the app has stalled and has to be terminated.

If I bring the office box back online, the print dialogue comes up quickly and I see the network printer, but can easily select to .pdf and it's done.

Reproducible: Always

Steps to Reproduce:
1.Device that only uses a Network Printer
2.Network Printer is off
3.Print

Actual Results:  
Print dialogue takes about 60 seconds to appear and Okular is actually stalled at this point and has to be terminated via the close button.
The rest of kde is fine

Expected Results:  
Okular stalls
Comment 1 Jonathan Verner 2015-04-02 12:58:37 UTC
Possibly a duplicate of #329740 or #334708?
Comment 2 thekernel 2015-04-02 15:12:37 UTC
(In reply to Jonathan Verner from comment #1)
> Possibly a duplicate of #329740 or #334708?

Sounds similar to #329740
I'll have to do some more digging when I get time. Thanks Jonathan
Comment 3 Albert Astals Cid 2015-04-02 15:19:53 UTC
It is similar, but not the same thing, since in those accessing the remote printer is more a side effect of what we really want to do, but in the printing dialog, it needs to contact the printer, sure it should not get blocked, but it's harder to fix, much more when that code is in Qt upstream.
Comment 4 Andrew Crouthamel 2018-10-31 04:08:17 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2018-11-15 10:52:24 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
mark the bug 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 Bug Janitor Service 2018-11-30 04:04:51 UTC
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!