The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: dmidecode (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: ubiquity (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Removing it from the OEM priority queue, as it works well in Trusty
** Changed in: oem-priority
Status: New = Fix Released
** Changed in: oem-priority/precise
Status: New = Won't Fix
** Changed in: oem-priority/saucy
Status: New = Won't Fix
--
You received this bug
** Changed in: oem-priority
Assignee: (unassigned) = Ara Pulido (apulido)
--
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/1236233
Title:
BIOS that SMIBIOS is not fuly supported
Could we backport the saucy's (or trusty's ) dmidecode to Precise? I try
to find the bzr branch but lp:dmidecode seems a bit outdated.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
** Also affects: dmidecode (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: ubiquity (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dmidecode (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
It turns out that dmidecode has had its boundary moved up 2.8 for saucy.
This does not fix the issue but makes it much much less likely to be hit
in saucy release images at least.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode
@Colin
you are right, using python-dmidecode brings up extra maintain efforts,
so the solution I could image now is only trying to parse this out in
ubiquity.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
Interesting idea, but (a) it's currently in universe and would need MIR
paperwork, (b) I'm not at all comfortable with the fact that it's
basically a copy of dmidecode, so we'd need to make sure changes to
dmidecode were reflected in python-dmidecode.
--
You received this bug notification
dmidecode really ought to print this message to stderr, not stdout (at
least when the -s option is in use, indicating a desire for machine-
readable output; there might be backward-compatibility concerns with
changing it in general). That would be much less fragile than trying to
parse this out
@Colin
How about using python-dmidecode to get product name instead of parsing
the output of dmidecode in ubiquity?
--
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/1236233
Title:
14 matches
Mail list logo
