By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 3048 - Kooka-trinity hangs on printing scanned images
Summary: Kooka-trinity hangs on printing scanned images
Status: RESOLVED NOTOURPROBLEM
Alias: None
Product: TDE
Classification: Unclassified
Component: tdegraphics (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: R14.0.7
  Show dependency treegraph
 
Reported: 2019-10-10 05:35 CDT by Q4OS Team
Modified: 2019-10-11 07:57 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:


Attachments
Kooka hangs on print (4.68 MB, video/mp4)
2019-10-10 05:35 CDT, Q4OS Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Q4OS Team 2019-10-10 05:35:56 CDT
Created attachment 2930 [details]
Kooka hangs on print

When I try to print scanned image in Kooka-trinity, It generates many pages, then just hangs. So I am unable to print using Kooka-trinity. I can print successfuly using OpenOffice, Chromium and other utilities, so my printer works well. The problem is only with kooka-trinity.

Exact steps to reproduce:
- TDE preliminary stable (14.0.7) on Debian Buster.
- Bug: Follow the video. Print images previously scanned in Kooka, it hangs.
Comment 1 Slávek Banko 2019-10-11 06:50:45 CDT
The video shows that the print queue icon is in the system tray when finish printing in Kooka. Is there a print job in the queue? How does the print server treat this print job? You can turn on the preview and see how the print job is prepared?
Comment 2 Q4OS Team 2019-10-11 07:42:41 CDT
I cannot reproduce this one on another hardware, the same printing procedure works well now, TDE14.0.7/Buster. Seems to be a hardware related issue, you can close this bug.
Comment 3 Slávek Banko 2019-10-11 07:57:27 CDT
Well, then we'll assume it's not our bug.