Bug 1910908 - 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 NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-control-center
Version: 36
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Pete Walter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-25 15:54 UTC by Pat Kelly
Modified: 2022-05-17 13:31 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-05-17 13:31:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pat Kelly 2020-12-25 15:54:52 UTC
Description of problem: Using a Brother model HL-L6200DW which is wire connected to the local network. On a new, clean, bare metal, install of Fedora 33 Workstation, the printer is discovered, but will not function after install complete.


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


How reproducible:100%


Steps to Reproduce:
1. Make a new, clean, bare metal, install of Fedora 33 Workstation
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 gcc Settings -> Printers, CUPS, or the Printer Settings application using driver (Generic PCL 6/PCL XL Printer Foomatic/pxlmono.

Comment 1 Vladimír Slávik 2021-03-05 17:04:53 UTC
pmkelly, thank you for the report. Unfortunately, changes made in the Live CD environment do not carry over to the installed system. Whatever you do with packages, settings, printers etc. before reboot to the new system, is lost. Any customizations you do in Live, you need to repeat these on the system. (Except for the very few things the installer lets you do in its GUI.)

There isn't enough information to go on, but it sounds a bit as if you installed drivers in the Live environment? That would then be the difference, so just install them on the system too. Sorry it this is a wrong guess.

Comment 2 Pat Kelly 2021-03-05 17:42:40 UTC
No, I'm not trying to install while Live is running. After the install is completely done after first boot with password and everything done I look in GCC Printers and see that the printer was found, But the printer does not have a driver installed so it won't print.

If I Remove the printer and and then click Add the printer is found and after I wait for it to find a driver. It finds a Generic driver that works (Generic PCL 6/PCL XL Printer Foomatic/pxlmono), but it is not the correct driver and some printer features are not available.

Then I remove the driver again with GCC Printers and switch to using CUPs. With CUPs I reinstall the printer using the correct driver (HL-L6200DW series - IPP Everywhere). The printer works fine. Then if I go back to GCC Printers the printer shows as installed with the correct driver and will print a test page for GCC Printers.

At this point the printer has all features available and will print the applications without problems.

Apparently whatever software is trying to install the printer during Install can fine a driver at all. When I try to reinstall the printer with GCC Printer it finds the wring one.

Brother is a popular brand of printers and this is a common model. If CUPs can install it with no problems something in the other software must have a problem with finding the correct driver or any driver for that matter.

Comment 3 Vladimír Slávik 2021-03-05 18:10:10 UTC
Thanks, that's clearer now. Anaconda does not handle printers in any way. Printer driver packages get installed only as one thing on a list. Whatever happens to printers, happens after the system started. Thus reassigning to Gnome control center, since that's what you used...

Comment 4 Pat Kelly 2021-11-06 13:40:11 UTC
With F35 WS installation (clean install not an upgrade) the situation has changed a bit. I don't have to use CUPS to get the correct driver installed. So the current scenario is as follows:

I'm not trying to install while Live is running. After the install is completely done after first boot with password and everything done I look in GCC Printers and see that the printer was found, But the printer does not have a driver installed so it won't print. If I Remove the printer in GCC and and then click Add the printer is found and after I wait for it to find a driver it finds the correct driver (HL-L6200DW series - IPP Everywhere) and the printer is installed correctly. I can print a test page from GCC and the printer works fine from applications.

The bug is now that the printer is not installed with it's correct driver during the F35 WS installation.

Comment 5 Pat Kelly 2022-02-02 19:47:53 UTC
This issue still exists in Rawhide (F35) as described above in comment 4 (2021-11-06 13:40:11 UTC)

Comment 6 Pat Kelly 2022-02-02 19:53:44 UTC
Sorry mistaken F35 above it is F36. This issue still exists in Rawhide (F36) as described above in comment 4 (2021-11-06 13:40:11 UTC)

Comment 7 Ben Cotton 2022-02-08 20:19:25 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 8 Pat Kelly 2022-05-17 13:31:45 UTC
This problem is apparently due to a default IP Everywhere driver being loaded instead of the one provided by Brother. This results in lack of compatibility with Firefox. There is a workaround. However I will continue to load the Brother IP Everywhere as it provides the compatibility with Firefox and it seems a cleaner solution than implementing the workaround. I will continue monitoring this for future releases to see if the default driver ever becomes compatible with Firefox.

I believe the position of the maintainers is that this is not a bug; so I am closing it as "NOTABUG"


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