This seems to be a bug either in the "lshw -json" output or in the Python json module's ability to parse said output. In particular, there's been a change in the output with Eoan. Previous versions produce something like this:
I'm making inquiries to try to determine whether the new JSON output is valid or not, which will determine whether to file a bug against lshw or the Python json library.
This seems to be a bug either in the "lshw -json" output or in the Python json module's ability to parse said output. In particular, there's been a change in the output with Eoan. Previous versions produce something like this:
"capabilities" : {
"smbios-2.7" : "SMBIOS version 2.7",
"dmi-2.7" : "DMI version 2.7",
"vsyscall32" : "32-bit processes"
},
"children" : [
{
"id" : "core",
"class" : "bus",
In Eoan, the equivalent segment looks like this:
"capabilities" : {
"smbios-2.7" : "SMBIOS version 2.7",
"dmi-2.7" : "DMI version 2.7",
"smp" : "Symmetric Multi-Processing",
"vsyscall32" : "32-bit processes"
} {
"id" : "core",
"class" : "bus",
I'm making inquiries to try to determine whether the new JSON output is valid or not, which will determine whether to file a bug against lshw or the Python json library.