Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1942326 - samsung ml-2240 stopped printing with cups-2.3.3op2
Summary: samsung ml-2240 stopped printing with cups-2.3.3op2
Keywords:
Status: CLOSED DUPLICATE of bug 1935318
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Dohnal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-24 07:51 UTC by Miklos Szeredi
Modified: 2021-03-24 09:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-24 09:31:40 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Miklos Szeredi 2021-03-24 07:51:44 UTC 
Description of problem:

After upgrading from fc32 to fc33 printing to Samsung ML-2240 stopped working.

Test page sometimes prints normally, but sometimes prints error.  Printing a PDF does not seem to work at all.  Sometimes the printer just flashes, sometimes it prints an error message, but never the actual document.


Version-Release number of selected component (if applicable):

cups-2.3.3op2-1.fc33.x86_64


How reproducible:

Very

Steps to Reproduce:
1. Print test page
2.
3.

Actual results:

Prints something like this:

"INTERNAL ERROR - FALSE

   POSITION : {random number}

   SYSTEM   : h6wsim_snipe/x1_pa_sim

   LINE     : 254

   VERSION  : SPL 5.07 06-27-2006"


Expected results:

Print test page

Additional info:
Comment 1 Zdenek Dohnal 2021-03-24 08:30:33 UTC 
Hi Miklos,

thank you for reporting the issue!

Would you mind telling me how is your printer connected?

If it is by USB, it maybe the same problem as https://bugzilla.redhat.com/show_bug.cgi?id=1935318 .

In that case, would you mind trying these rpms https://koji.fedoraproject.org/koji/taskinfo?taskID=64422836 and tell me if they works?

If the rpms don't help, please follow https://fedoraproject.org/wiki/How_to_debug_printing_problems#My_printer_doesn.27t_print_correctly_or_at_all.2C_but_I_can_see_the_printer_in_print_dialog and provide all information mentioned there.


Thank you in advance!
Comment 2 Zdenek Dohnal 2021-03-24 09:05:19 UTC 
There are testing rpms with longer timeout too https://koji.fedoraproject.org/koji/taskinfo?taskID=64412423 - if the previous rpms don't work, please the link in this comment.

The core of the problem for USB appears to be shorter timeout than old Samsung devices can handle, so I'm trying to figure out the shortest timeout possible to support currently broken devices and don't hurdle too much new devices.
Comment 3 Miklos Szeredi 2021-03-24 09:25:29 UTC 
(In reply to Zdenek Dohnal from comment #2)
> There are testing rpms with longer timeout too
> https://koji.fedoraproject.org/koji/taskinfo?taskID=64412423 - if the
> previous rpms don't work, please the link in this comment.
> 
> The core of the problem for USB appears to be shorter timeout than old
> Samsung devices can handle, so I'm trying to figure out the shortest timeout
> possible to support currently broken devices and don't hurdle too much new
> devices.

Second one seems to be okay.

Thanks.
Comment 4 Zdenek Dohnal 2021-03-24 09:31:40 UTC 

*** This bug has been marked as a duplicate of bug 1935318 ***
Comment 5 Zdenek Dohnal 2021-03-24 09:32:46 UTC 
Thanks for the confirmation, Miklos!
Note You need to log in before you can comment on or make changes to this bug.