Bug 826451 - After installing groff and groff-base from updates-testing, nothing is printed on my samsung ml-1660 USB printer
After installing groff and groff-base from updates-testing, nothing is printe...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: groff (Show other bugs)
17
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jan Vcelak
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-30 04:43 EDT by Joachim Backes
Modified: 2013-03-03 20:30 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-05-30 05:20:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joachim Backes 2012-05-30 04:43:43 EDT
Description of problem:
I run "yum update --enablerepo=updates-testing" which updates groff and groff-base. After this, I'm able to print simple text files, but no more LibreOffice documents.

First I thought it's a cups problem ("yum update --enablerepo=updates-testing" updated cups too, but nothing changed after downgrading cups), so this did not help. Only downgrading groff and groff-libs was helpful.
 

Version-Release number of selected component (if applicable):
 groff             x86_64       1.21-9.fc17         updates-testing       1.1 M
 groff-base        x86_64       1.21-9.fc17         updates-testing       783 k


How reproducible:

always
Steps to Reproduce:
1.yum update --enablerepo=updates-testing
2.Try to print some LO document
3.
  
Actual results:
Nothing is printed, but I found some error message in /var/log/cups:
failed to find device: cups-ML-1660
failed to find device: cups-PDF

No such msg after having downgraded groff and groff-base

Expected results:
Printing should be done

Additional info:

Note You need to log in before you can comment on or make changes to this bug.