Bug 1812515 - Gnome discovers printer during install, but does not install it so it works
Summary: Gnome discovers printer during install, but does not install it so it works
Keywords:
Status: CLOSED DUPLICATE of bug 191908
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-control-center
Version: 33
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-11 13:39 UTC by Pat Kelly
Modified: 2021-11-06 13:50 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-06 13:50:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pat Kelly 2020-03-11 13:39:09 UTC
Description of problem: Using a Brother model HL-L6200DW which is wire connected to the local network. This printer uses driver "Brother_HL-L6200DW series, driverless". On a new, clean, bare metal, install of Fedora, the printer is discovered, but will not function.


Version-Release number of selected component (if applicable): 3.36.0-1.fc32


How reproducible: 100%


Steps to Reproduce:
1. Make a new, clean, bare metal, install of Fedora 32
2. When complete open gcc and on the Devices tab select Printers
3. Try to print a test page or print any other printable document

Actual results: Printer will not function


Expected results: Printer prints test page or any other printable document


Additional info:
The printer can be set up and works when set up with either CUPS or the Printer Settings application. A work around  has been discovered that allows the printer to be set up successfully with the gcc Devices - Printers. Open gcc to the Printers tab. Unlock the tab and Remove the printer using the menu option for Remove Printer. Use the Add... button at the top of the tab and set the printer up. The printer will print test pages and other documents.

This has been filed as an Issue with Gnome as Gnome > Settings > Issues #749.

Comment 1 James Cassell 2020-04-21 19:09:50 UTC
Can confirm on my system with network-attached Brother MFC-L9550CDW printer.  Printer is auto-configured but does not work.  If I delete the auto-configured printer, it gets re-added automatically.

Comment 2 Pat Kelly 2020-05-16 19:47:11 UTC
This issue is still present in F33 Rawhide with Gnome version 3.37.1. The Gnome issue referenced above has been updated.

Comment 3 Pat Kelly 2020-08-06 18:20:00 UTC
This issue is still present in F33 Rawhide 0804 drop with Gnome version 3.37.3. The Gnome issue referenced above has been updated.

Comment 4 Ben Cotton 2020-08-11 13:13:34 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 5 Pat Kelly 2020-08-21 15:17:01 UTC
There is a major regression in this bug. This started back when F33 was still Rawhide a few weeks ago. I waited until now to report it incase it was caused by a missing file that would be present in the Branched version. At this time the printer can not be installed with the gnome Settings - Printers or with the application Print Settings. When I try to install with CUPS in the Discovered Network Printers there are four lines listed for this printer (HL-L6200DW) Three lines show "Brother HL-L6200DW series (Brother HL-L6200DW series)". The fourth line shows "Brother HL-L6200DW series (fully driverless) (Brother HL-L6200DW series)". I tried to install the printer 4 times (once for each line described above) starting from scratch each time. On the select a "driver" page the there are two possible selections depending on which of the original four lines was selected. The selections at this level are: "Brother HL-L6200DW series - IPP Everywhere", or "Brother HL-L6200DW series, fully driverless, cups-filters 1.27.5 (en)"

All attempts failed: Theree times the failure mode was failure to find a PPD file. One combination looked like the install worked, but when a test page was attempted the failure was that it couldn't find the printer.

The only combination that works is to install with CUPS and on the "Driver" selection screen choose "Select Another Make/Manufacturer" Then select Generic as the manufacturer and select "Generic PCL 6/PCL XL Printer Foomatic/PXLMono (en). With the Generic driver the printer works.

Comment 6 Fedora Admin user for bugzilla script actions 2021-08-21 00:04:37 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 7 Ben Cotton 2021-11-04 13:46:51 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2021-11-04 14:16:19 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Ben Cotton 2021-11-04 15:13:56 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 10 Pat Kelly 2021-11-06 13:50:15 UTC

*** This bug has been marked as a duplicate of bug 191908 ***


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