Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#59078 - [hplip] python-gobject dependency should be hard and not optional
Attached to Project:
Arch Linux
Opened by Toolybird (Toolybird) - Wednesday, 20 June 2018, 03:23 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 20 January 2019, 19:10 GMT
Opened by Toolybird (Toolybird) - Wednesday, 20 June 2018, 03:23 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 20 January 2019, 19:10 GMT
|
DetailsDescription:
"hp-setup -i" will complain if python-gobject is not installed: error: Unable to load pkit...is HPLIP installed? error: Python gobject/dbus may be not installed While it does continue on and successfully sets up the printer, scanning is completely broken. I had to manually install python-gobject and re-run hp-setup again. Now no more errors and scanning works. Please make python-gobject a hard depenency to resolve this issue. hplip-3.18.6-1 |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Sunday, 20 January 2019, 19:10 GMT
Reason for closing: Fixed
Additional comments about closing: 3.18.12-2
Sunday, 20 January 2019, 19:10 GMT
Reason for closing: Fixed
Additional comments about closing: 3.18.12-2
Check requirements at https://developers.hp.com/hp-linux-imaging-and-printing/install/manual/distros/other .
And it's not just the GUI. "hp-setup -i x.x.x.x" is CLI only and it reveals the problem. hp-setup is the first thing mentioned in the Arch Wiki re hplip and it would seem to be rather vital.
Most folks won't see the problem because python-gobject has already been pulled in by a desktop environment or whatever. I only noticed the issue while setting up a new minimal system without desktop bloat.
I wasted a lot of time debugging this issue and just wanted to save some other sucker the grief.
Your call.