Still affected on xenial,
dmidecode:
Installed: 3.0-2ubuntu0.2
Was this bug really fixed?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1688162
Title:
dmidecode should print
This is latest version:
dmidecode:
Installed: 3.0-2ubuntu0.2
Candidate: 3.0-2ubuntu0.2
Version table:
*** 3.0-2ubuntu0.2 500
500 http://mirror.yandex.ru/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
3.0-2 500
500
This bug was fixed in the package dmidecode - 3.1-1
---
dmidecode (3.1-1) unstable; urgency=medium
* New upstream release (LP: #1688162) (Closes: #860897):
- Remove applied patches:
+ debian/patches/0110-nosysfs.patch
+
Hi Jens, we usually try to keep dmidecode without Delta to Debian.
For the SRUs Delta is fine and as I said if no one helps I can try to assist
here.
If you want to volunteer there is also the USBSD [1] where new people are
guided to help themselfe and the community.
For the current release it
Hi Christian,
Yepp, the patch looks good. Would be nice to get this integrated (or to
sync dmidecode with the current GNU version).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
Also I think the bios needs to report wrong data length to trigger this,
which might be why it isn't seen all around IMHO.
** Changed in: dmidecode (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
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
7 matches
Mail list logo
