Bug 5368 - thinlocal should not wait for client to close connection before considering print job complete
Summary: thinlocal should not wait for client to close connection before considering p...
Status: CLOSED DUPLICATE of bug 1456
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Printing (show other bugs)
Version: 4.3.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.4.0
Assignee: Henrik Andersson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-24 17:00 CET by Karl Mikaelsson
Modified: 2014-11-26 16:11 CET (History)
1 user (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Karl Mikaelsson cendio 2014-11-24 17:00:27 CET 
A customer reported that thanks to bug 3610, their entire thinlocal backend stopped for all users. Thinlocal should be more aggressive in considering the job sent when it has sent all data to the client to avoid cases where a single user may lock the entire thinlocal queue for all users. A timeout for hanging connections would also be nice, but printing a large file over a slow connection is a valid use case for thinlocal.
Comment 2 Peter Åstrand cendio 2014-11-26 16:10:56 CET 

*** This bug has been marked as a duplicate of bug 1456 ***
Note You need to log in before you can comment on or make changes to this bug.