hplip(-gui), hp-systray 3.25.6 not working because of changes in python 3.14.

[gc-user]

Is this a new report?

Yes

System Info

Void 6.12.60_1 x86_64 GenuineIntel notuptodate hold rrrrrmDDDDDDDDFFF

Package(s) Affected

hplip(-gui) 3.25.6_1

Does a report exist for this bug with the project's home (upstream) and/or another distro?

URLopener was removed in Python 3.14 and hplip tracebacks without it https://bugs.launchpad.net/hplip/+bug/2115046

The bug report has a patch as a reply to it. Not sure if it works or would be considered "trustworthy" by the void devs.

Expected behaviour

hplip tray icon (hp-systray) and main window (device manager) should start and just "work".

Actual behaviour

Neither hp-systray nor hp-toolbox or hp-plugin can be started / work as expectred but instead spit out an error message:

Traceback (most recent call last):
  File "/usr/bin/hp-plugin", line 41, in <module>
    from base import device, utils, tui, module, services
  File "/usr/share/hplip/base/device.py", line 2690, in <module>
    class LocalOpener(urllib_request.URLopener):
                      ^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'urllib.request' has no attribute 'URLopener'

Steps to reproduce

1. Install hplip hplip-gui or update to current version (3.25.6_1) with python 3.14 installed.
2. Try to start hp.systray.
3. See above error message if started from terminal to see why it won't start.

[sgn]

The patch is not correct, line 2530 of base/device.py, they use open of URLopener.

[gc-user]

I'm not a programmer, so I don't know what that means - the line or your statement.

I just went looking if maybe there was a new hplip version avalaible. Turns out there is (3.25.8), but the changelog doean't mention any bug fix (not even a mention of this bug as a known issue - I guess the hp devs are still on python 3.13), so I checked the respective file which seems to be unaltered in this regard, i.e. not fixed.

So I decided to just build the new version with this patch added. Other than some other patch needing some small adjustment, the build went through, the package installs fine, the error message is gone and the gui starts and runs fine as far as I can determine.