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 1943939 - New cups stop working with Samsung ML-1640
Summary: New cups stop working with Samsung ML-1640
Keywords:
Status: CLOSED DUPLICATE of bug 1935318
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 33
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Zdenek Dohnal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-28 15:51 UTC by Mario
Modified: 2021-04-07 05:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-07 05:41:41 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
journalctl | grep cups* (3.71 KB, application/octet-stream)
2021-03-28 15:51 UTC, Mario 		no flags Details
print error (27.72 KB, image/jpeg)
2021-03-28 15:54 UTC, Mario 		no flags Details
View All

Description Mario 2021-03-28 15:51:47 UTC 
Created attachment 1767141 [details]
journalctl | grep cups*

Systemctl status cups not have any output errors
Comment 1 Mario 2021-03-28 15:54:56 UTC 
Created attachment 1767143 [details]
print error
Comment 2 Zdenek Dohnal 2021-04-07 05:41:41 UTC 
Hi Mario,

thank you for reporting the issue!

Your issue is actually a duplicate of bug 1935318 - the core of problem is that several Samsung devices don't honor USB standard and internally expects delays between reading and sending data via endpoints.

I proposed a workaround upstream in 1935318 (by raising timeout) and there are links to koji with testing rpms for 5s and 10s timeouts. Would you mind trying the testing rpms and leave a feedback at bug #1935318 ?

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