Version-Release number of selected component: hplip-3.19.12-2.fc31 Additional info: reporter: libreport-2.11.3 cgroup: 0::/user.slice/user-1000.slice/user/gnome-terminal-server.service cmdline: /usr/bin/python3 /usr/bin/hp-setup crash_function: to_string_utf8 exception_type: UnicodeDecodeError executable: /usr/bin/hp-setup interpreter: python3-3.7.6-2.fc31.x86_64 kernel: 5.4.18-200.fc31.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: sixext.py:113:to_string_utf8:UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 254: invalid continuation byte Traceback (most recent call last): File "/usr/share/hplip/ui5/setupdialog.py", line 1297, in NextButton_clicked self.showDevicesPage() File "/usr/share/hplip/ui5/setupdialog.py", line 566, in showDevicesPage filter_dict, self.search, net_search=net_search_type) File "/usr/share/hplip/base/device.py", line 494, in probeDevices detected_devices = avahi.detectNetworkDevices(ttl, timeout) File "/usr/share/hplip/base/avahi.py", line 39, in detectNetworkDevices output = to_string_utf8(p.communicate()[0]) File "/usr/share/hplip/base/sixext.py", line 113, in to_string_utf8 return s.decode("utf-8") UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 254: invalid continuation byte Local variables in innermost frame: s: b'+;enp2s0;IPv4;te100-mp1u-41-usb1;_printer._tcp;local\n=;enp2s0;IPv4;te100-mp1u-41-usb1;_printer._tcp;local;te100-mp1u-41.local;192.168.1.41;515;"adminurl=http://te100-mp1u-41.local." "usb_CLASS=PRINTER" "usb_MDL=Deskjet 2050 J510 series series" "usb_MFG=\\\xe9\t" "pdl=U" "ty=hp Deskjet 2050 J510 series series" "product=(hp Deskjet 2050 J510 series series)" "priority=0" "qtotal=1" "rp=USB1_LQ" "txtvers=1"\n'
Created attachment 1663042 [details] File: backtrace
Created attachment 1663043 [details] File: cpuinfo
Created attachment 1663044 [details] File: environ
Created attachment 1663045 [details] File: mountinfo
Created attachment 1663046 [details] File: namespaces
Created attachment 1663047 [details] File: open_fds
*** This bug has been marked as a duplicate of bug 1573430 ***