Hi Jens, this seems to be specific to that invalid length error. As I have seen that e.g. access denied or wrong option errors work just the way they should.
# insufficient permission $ /usr/sbin/dmidecode -s baseboard-manufacturer 2>/dev/null # bad option $ sudo /usr/sbin/dmidecode -s wrong 2>/dev/null I found a change upstream that could explain why this fixes it for you: https://github.com/mirror/dmidecode/commit/74614633b31a2ac01240c72890722a86a3f3fc97 Applying only has slight errors that are easily fixed (5x offset and one fail that is easy to resolve). I'll leave it as this for now as I'm in no way a dmidecode expert - I've only seen it because it was accidentally qemu and found it interesting. But I'll subscribe myself, if nothing is happening in ~2 weeks please ping and I'll take another look. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688162 Title: dmidecode should print diagnostic messages to stderr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1688162/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
