[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-10-18 Thread Yuan-Chen Cheng
** Changed in: oem-priority
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-10-14 Thread Matthieu Clemenceau
** Tags added: fr-126

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-22 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.11-0ubuntu27.9

---
apport (2.20.11-0ubuntu27.9) focal; urgency=medium

  [ YC Cheng ]
  * apport/apport/hookutils.py: add acpidump using built-in
dump_acpi_tables.py. (LP: #1888352)
  * bin/oem-getlogs: add "-E" in the usage, since we'd like to talk to
pulseaudio session and that need environment infomation. Also remove
acpidump since we will use the one from hook.

 -- Brian Murray   Wed, 02 Sep 2020 09:48:39 -0700

** Changed in: apport (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-17 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-09 Thread Yuan-Chen Cheng
** Changed in: oem-priority
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-08 Thread Yuan-Chen Cheng
given #14, verified done

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  In Progress
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-08 Thread Alex Hung
After using apport-unpack for #8, acpidump looks good

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  In Progress
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-08 Thread Alex Hung
@ycheng-twn,

#10 and #11 are basically the same except orders of some tables; however
this is as expected.

the gz file of #8 contains a "single" plain text file. Shouldn't it be
one file for each log file?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  In Progress
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-08 Thread Yuan-Chen Cheng
for the apport.gz, per what I know, it's all plain text after we un-gzip
it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  In Progress
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-08 Thread Yuan-Chen Cheng
this is output of dump_acpi_tables.py on that machine.

** Attachment added: "dump_acpi_tables.py.log"
   
https://bugs.launchpad.net/apport/+bug/1888352/+attachment/5408887/+files/dump_acpi_tables.py.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  In Progress
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-08 Thread Yuan-Chen Cheng
this is output of acpidump-acpica on that machine

** Attachment added: "acpidump-acpica.log"
   
https://bugs.launchpad.net/apport/+bug/1888352/+attachment/5408884/+files/acpidump-acpica.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  In Progress
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-08 Thread Alex Hung
@ycheng-twn,

1. Is it normal that everything is in a plain text file?
2. There is an extra space for acpidump. This causes acpixtract to fail to 
extract ACPI tables.
3. The content looks "reasonable", but /sys/firmware/acpi/tables/* are required 
to byte-to-byte compare after 1 & 2 are fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  In Progress
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-06 Thread Yuan-Chen Cheng
the oem-getlogs file using the apport 2.20.11-0ubuntu27.9 from the proposed 
channel.
I am going to find uefi expert to double check

** Attachment added: "oemlogs-f1-test-20200907111510+0800.apport.gz"
   
https://bugs.launchpad.net/oem-priority/+bug/1888352/+attachment/5408229/+files/oemlogs-f1-test-20200907111510+0800.apport.gz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  In Progress
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-06 Thread Yuan-Chen Cheng
** Changed in: oem-priority
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  In Progress
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-04 Thread Timo Aaltonen
Hello Yuan-Chen, or anyone else affected,

Accepted apport into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu27.9 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apport (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-09-02 Thread Brian Murray
I've uploaded this to the focal SRU queue for review by an SRU team
member.

** Also affects: apport (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: apport (Ubuntu Focal)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  In Progress
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-08-31 Thread Yuan-Chen Cheng
** Description changed:

  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.
+ 
+ To SRU to focal:
+ 
+ [Impact]
+ 
+  * for OEM project, lts is been used. And collect log is important.
+With built-in tool to get acpidump, we don't need to install
+extra tool in the end-customer's machine. That make it much
+easier for the oem process.
+ 
+  * By call built-in utility, we no lounger need to install extra
+tools to collect data that's both complete and convenient for
+HWE people to work on.
+ 
+ [Test Case]
+ 
+  * before this applied, run oem-getlog without install acpidump. 
+we can't get the dump data. After this applied, we can just dump
+the data HWE need.
+ 
+  * test step: install the new package, run
+ 
+sudo -E oem-getlogs [-c case_id] to get the
+ 
+use apport-unpack to unpack the apport file.
+ 
+check the acpidump file. HWE people know much better on check
+the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
+by HWE/ACPI/UEFI expert, it's pretty safe to do so.
+ 
+ [Regression Potential]
+ 
+  * Given the modification change the way to collect log, even it
+failed, it won't break apport itself. Just the collected log
+might contain data not so valid.
+ 
+  * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
+just reviewed and updated the dump_acpi_tables.py script, I
+believe it will have good quality.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

  To SRU to focal:

  [Impact]

   * for OEM project, lts is been used. And collect log is important.
 With built-in tool to get acpidump, we don't need to install
 extra tool in the end-customer's machine. That make it much
 easier for the oem process.

   * By call built-in utility, we no lounger need to install extra
 tools to collect data that's both complete and convenient for
 HWE people to work on.

  [Test Case]

   * before this applied, run oem-getlog without install acpidump. 
 we can't get the dump data. After this applied, we can just dump
 the data HWE need.

   * test step: install the new package, run

 sudo -E oem-getlogs [-c case_id] to get the

 use apport-unpack to unpack the apport file.

 check the acpidump file. HWE people know much better on check
 the acpidump file. Give the dump_acpi_tables.py just updated and SRUed
 by HWE/ACPI/UEFI expert, it's pretty safe to do so.

  [Regression Potential]

   * Given the modification change the way to collect log, even it
 failed, it won't break apport itself. Just the collected log
 might contain data not so valid.

   * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they
 just reviewed and updated the dump_acpi_tables.py script, I
 believe it will have good quality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-08-31 Thread Brian Murray
Could you please add some SRU information to the bug description to
facilitate the SRU process?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-08-26 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.11-0ubuntu45

---
apport (2.20.11-0ubuntu45) groovy; urgency=medium

  [ YC Cheng ]
  * apport/hookutils.py: add acpidump using built-in dump_acpi_tables.py.
(LP: #1888352)
  * bin/oem-getlogs: add "-E" in the usage, since we'd like to talk to
pulseaudio session and that need environment infomation. Also remove
acpidump since we will use the one from hook.

  [ Brian Murray ]
  * data/general-hooks/ubuntu.py: Check for /var/run/reboot-required.pkgs and
add it to the report as RebootRequiredPkgs.

 -- Brian Murray   Wed, 26 Aug 2020 15:57:02 -0700

** Changed in: apport (Ubuntu Groovy)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Groovy:
  Fix Released

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-08-26 Thread Yuan-Chen Cheng
please kindly also SRU it to focal, since oem project use lts mostly.
I'll take responsibility to verify sru or other thing I can do.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Groovy:
  In Progress

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-08-26 Thread Brian Murray
** Changed in: apport (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: apport (Ubuntu Groovy)
 Assignee: (unassigned) => Brian Murray (brian-murray)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Groovy:
  In Progress

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-08-15 Thread Rex Tsai
** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  New
Status in apport source package in Groovy:
  New

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-07-24 Thread Francis Ginther
** Tags added: id-5f19aa4ac192ba29af392378

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  New
Status in apport source package in Groovy:
  New

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-07-23 Thread Brian Murray
** Also affects: apport (Ubuntu Groovy)
   Importance: High
   Status: New

** Tags removed: rls-gg-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  New
Status in apport source package in Groovy:
  New

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-07-21 Thread Ubuntu Foundations Team Bug Bot
The attachment "apport_42to43.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  New

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-07-21 Thread Sebastien Bacher
** Also affects: apport (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: rls-gg-incoming

** Changed in: apport (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1888352

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  New

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp