Hello Amarnath Chitumalla,
you are right that because of https://bugs.launchpad.net/hplip/+bug/1197416 I have currently invoking hp-config_usb_printer deactivated in 56-hpmud.rules.
Because of the comment in 56-hpmud.rules for the invoking hp-config_usb_printer rule "This rule will add the printer and install plugin" I already had the feeling that this could have something to do with firmware upload.
I appreciate very much your suggestion how to disable the groups and plugin popups in config_usb_printer.py to avoid the issues in https://bugs.launchpad.net/hplip/+bug/1197416
Alternatively I am thinking about to replace invoking hp-config_usb_printer by invoking only hp-firmware in that udev rule like
hp-firmware -s $env{BUSNUM}:$env{DEVNUM}
but I do not know if this could have bad side effects when that device does not need firmware upload.
Hello Amarnath Chitumalla,
you are right that because of /bugs.launchpad .net/hplip/ +bug/1197416 usb_printer
https:/
I have currently invoking hp-config_
deactivated in 56-hpmud.rules.
Because of the comment in 56-hpmud.rules usb_printer rule
for the invoking hp-config_
"This rule will add the printer and install plugin"
I already had the feeling that this could have
something to do with firmware upload.
I appreciate very much your suggestion how to usb_printer. py to avoid the issues in /bugs.launchpad .net/hplip/ +bug/1197416
disable the groups and plugin popups
in config_
https:/
Alternatively I am thinking about to replace usb_printer by invoking
invoking hp-config_
only hp-firmware in that udev rule like
hp-firmware -s $env{BUSNUM} :$env{DEVNUM}
but I do not know if this could have bad side effects
when that device does not need firmware upload.