[Bug 1895160] Re: Backport finalrd 6 to xenial and up
** Tags added: fr-689 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895160 Title: Backport finalrd 6 to xenial and up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/finalrd/+bug/1895160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898152] Re: upgrade fails to calculate if gnuradio-dev is installed
** Tags added: fr-806 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898152 Title: upgrade fails to calculate if gnuradio-dev is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898716] Re: Please trust Canonical Livepatch Service kmod signing key
** Tags added: fr-797 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898716 Title: Please trust Canonical Livepatch Service kmod signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898729] Re: shim can end up being removed
** Tags added: fr-807 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898729 Title: shim can end up being removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
** Tags added: fr-823 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818918 Title: gdb doesn't search in debug-file-directory for .gnu_debugaltlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1818918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.10, the problem page at https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. Traceback (most recent call last): - File "/usr/share/apport/apport", line 451, in - options = parse_arguments() - File "/usr/share/apport/apport", line 396, in parse_arguments - parser.print_usage() - File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage - self._print_message(self.format_usage(), file) - File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message - file.write(message) + File "/usr/share/apport/apport", line 451, in + options = parse_arguments() + File "/usr/share/apport/apport", line 396, in parse_arguments + parser.print_usage() + File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage + self._print_message(self.format_usage(), file) + File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message + file.write(message) AttributeError: 'NoneType' object has no attribute 'write' + + After working on https://bugs.launchpad.net/apport/+bug/1732962, the error tracker started throwing the error above. + it appears that print_usage is called and throwing an error because in this context (called with core_pattern) apport doesn't have an stdout or stderr. after looking at traces it seems the kernel is adding 'deleted' to the name of the process which cause argument parsing to fail. + + The fix below from bdmurray seems to fix it. + https://paste.ubuntu.com/p/pVKNP9kWP4/ + + There is report of this issue in Focal, Bionic and xenial ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
** Tags added: fr-818 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899194] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@450:parse_arguments:print_usage:_print_message
*** This bug is a duplicate of bug 1899195 *** https://bugs.launchpad.net/bugs/1899195 ** This bug has been marked a duplicate of bug 1899195 /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899194 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@450:parse_arguments:print_usage:_print_message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898879] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@442:parse_arguments:print_usage:_print_message
*** This bug is a duplicate of bug 1899195 *** https://bugs.launchpad.net/bugs/1899195 ** This bug has been marked a duplicate of bug 1899195 /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898879 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@442:parse_arguments:print_usage:_print_message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1898879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
** Description changed: - The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.10, the problem page at https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. - If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + The Ubuntu Error Tracker has been receiving reports about a problem + regarding apport. This problem was most recently seen with package + version 2.20.11-0ubuntu27.10, the problem page at + https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e + contains more details, including versions of packages affected, + stacktrace or traceback, and individual crash reports. + + Traceback (most recent call last): + File "/usr/share/apport/apport", line 451, in + options = parse_arguments() + File "/usr/share/apport/apport", line 396, in parse_arguments + parser.print_usage() + File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage + self._print_message(self.format_usage(), file) + File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message + file.write(message) + AttributeError: 'NoneType' object has no attribute 'write' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732962] Re: apport uses sys.argv instead of named arguments
Verification completed on both bionic and xenial using proposed pockets ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732962 Title: apport uses sys.argv instead of named arguments To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1732962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888231] Re: [UBUNTU 20.04] zipl: Fix KVM IPL without bootindex
For Focal, would a cherry pick of those 2 upstream checkings be enough? Upstream-ID: c9066bf5497300db5e0ba11bf111683ea225d8c8 b7f1977d3f9332f82e7f388fb18076b89b83944e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888231 Title: [UBUNTU 20.04] zipl: Fix KVM IPL without bootindex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732962] Re: apport uses sys.argv instead of named arguments
** Description changed:
SRU Description
[Impact]
- data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with some
security updates where we were trying to support a new version of apport on a
host system and one inside a container.
+ data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with some
security updates where we were trying to support a new version of apport on a
host system and one inside a container.
This SRU for xenial and bionic based on the work made in cosmic enabled
proper handling of named argument.
Note that this is disabled for now on ALL series
-
+
[Test Case]
No real test here since apport general behavior should be unchanged Just to
check that the feature is disable, /proc/sys/kernel/core_pattern
content should remain unchanged :
$> cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c %d %P %E
[Regression Potential]
- The new feature is not enabled so the regression risk is fairly low. this
will take place in a future coordinated SRU across all LTS but in the meanwhile
we can make sure that there's no regression by running apport with various
+ The new feature is not enabled so the regression risk is fairly low. this
will take place in a future coordinated SRU across all LTS but in the meanwhile
we can make sure that there's no regression by making sure apport still behave
properly. starting and killing xeyes should trigger apport normal operation
+ $> xeyes &
+ $> kill -SEGV $!
End SRU Description
data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with some
security updates where we were trying to support a new version of apport
on a host system and one inside a container. Here's something of an
example:
347 # Normal startup
348 if len(sys.argv) not in (5, 6):
349 try:
350 print('Usage: %s [global pid]' % sys.argv[0])
351 print('The core dump is read from stdin.')
We could not maintain backwards compatibility because "global pid" is an
optional argument and "dump mode" was a new argument. So if there were
five arguments its possible the last one was "dump mode" (no global pid)
or "global pid" (no support for dump mode).
Its possible to use strings in /proc/sys/kernel/core_pattern so we could
use those and have apport accept named arguments e.g:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d
--global-pid=%P
['/home/bdmurray/source-trees/apport/artful/data/apport', '--pid=5870',
'--signal=11', '--core-size=0', '--dump-mode=1', '--global-pid=5870']
Tyler said "that's probably a nice cleanup to make no matter what
because the magic arg ordering is dangerous".
** Description changed:
SRU Description
[Impact]
data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with some
security updates where we were trying to support a new version of apport on a
host system and one inside a container.
This SRU for xenial and bionic based on the work made in cosmic enabled
proper handling of named argument.
Note that this is disabled for now on ALL series
[Test Case]
No real test here since apport general behavior should be unchanged Just to
check that the feature is disable, /proc/sys/kernel/core_pattern
content should remain unchanged :
$> cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c %d %P %E
[Regression Potential]
- The new feature is not enabled so the regression risk is fairly low. this
will take place in a future coordinated SRU across all LTS but in the meanwhile
we can make sure that there's no regression by making sure apport still behave
properly. starting and killing xeyes should trigger apport normal operation
+ The new feature is not enabled so the regression risk is fairly low. this
will take place in a future coordinated SRU across all LTS but in the meanwhile
we can make sure that there's no regression by making sure apport still behave
properly. starting and killing xeyes should trigger apport normal operation and
start apport.
$> xeyes &
$> kill -SEGV $!
End SRU Description
data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with some
security updates where we were trying to support a new version of apport
on a host system and one inside a container. Here's something of an
example:
347 # Normal startup
348 if len(sys.argv) not in (5, 6):
349 try:
350 print('Usage: %s [global pid]' % sys.argv[0])
351 print('The core dump is read from stdin.')
We
[Bug 1732962] Re: apport uses sys.argv instead of named arguments
** Patch removed: "diff for xenial to support named param. (backport from cosmic)" https://bugs.launchpad.net/apport/+bug/1732962/+attachment/5405275/+files/apport_2.20.1-0ubuntu2.25.debdiff ** Patch removed: "diff for bionic to support named param. (backport from cosmic)" https://bugs.launchpad.net/apport/+bug/1732962/+attachment/5405276/+files/apport_2.20.9-0ubuntu7.18.debdiff ** Patch added: "diff for xenial to support named param. (backport from cosmic)" https://bugs.launchpad.net/apport/+bug/1732962/+attachment/5413348/+files/apport_2.20.1-0ubuntu2.25.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732962 Title: apport uses sys.argv instead of named arguments To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1732962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732962] Re: apport uses sys.argv instead of named arguments
Updated debdiff and made sure autopkgtest were successful on both xenial and bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732962 Title: apport uses sys.argv instead of named arguments To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1732962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732962] Re: apport uses sys.argv instead of named arguments
** Patch added: "diff for bionic to support named param. (backport from cosmic)" https://bugs.launchpad.net/apport/+bug/1732962/+attachment/5413349/+files/apport_2.20.9-0ubuntu7.18.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732962 Title: apport uses sys.argv instead of named arguments To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1732962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887974] Re: [20.04] Valgrind: PPC sync instruction L field should only be 2 bits in ISA 3.0
Verification done for both focal and bionic. valgrind from focal-proposed and bionic-proposed fixes LP:1887974 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887974 Title: [20.04] Valgrind: PPC sync instruction L field should only be 2 bits in ISA 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1887974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887974] Re: [20.04] Valgrind: PPC sync instruction L field should only be 2 bits in ISA 3.0
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887974 Title: [20.04] Valgrind: PPC sync instruction L field should only be 2 bits in ISA 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1887974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732962] Re: apport uses sys.argv instead of named arguments
** Description changed:
+ SRU Description
+
+ [Impact]
+ data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with some
security updates where we were trying to support a new version of apport on a
host system and one inside a container.
+ This SRU for xenial and bionic based on the work made in cosmic enabled
proper handling of named argument.
+ Note that this is disabled for now on ALL series
+
+ [Test Case]
+ No real test here since apport general behavior should be unchanged Just to
check that the feature is disable, /proc/sys/kernel/core_pattern
+ content should remain unchanged :
+
+ $> cat /proc/sys/kernel/core_pattern
+ |/usr/share/apport/apport %p %s %c %d %P %E
+
+ [Regression Potential]
+ The new feature is not enabled so the regression risk is fairly low. this
will take place in a future coordinated SRU across all LTS but in the meanwhile
we can make sure that there's no regression by running apport with various
+
+ End SRU Description
+
data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with some
security updates where we were trying to support a new version of apport
on a host system and one inside a container. Here's something of an
example:
347 # Normal startup
348 if len(sys.argv) not in (5, 6):
349 try:
350 print('Usage: %s [global pid]' % sys.argv[0])
351 print('The core dump is read from stdin.')
We could not maintain backwards compatibility because "global pid" is an
optional argument and "dump mode" was a new argument. So if there were
five arguments its possible the last one was "dump mode" (no global pid)
or "global pid" (no support for dump mode).
Its possible to use strings in /proc/sys/kernel/core_pattern so we could
use those and have apport accept named arguments e.g:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d
--global-pid=%P
['/home/bdmurray/source-trees/apport/artful/data/apport', '--pid=5870',
'--signal=11', '--core-size=0', '--dump-mode=1', '--global-pid=5870']
Tyler said "that's probably a nice cleanup to make no matter what
because the magic arg ordering is dangerous".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732962
Title:
apport uses sys.argv instead of named arguments
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1732962/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732962] Re: apport uses sys.argv instead of named arguments
** Changed in: apport (Ubuntu Xenial) Status: New => In Progress ** Changed in: apport (Ubuntu Bionic) Status: New => In Progress ** Patch added: "diff for xenial to support named param. (backport from cosmic)" https://bugs.launchpad.net/apport/+bug/1732962/+attachment/5405275/+files/apport_2.20.1-0ubuntu2.25.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732962 Title: apport uses sys.argv instead of named arguments To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1732962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732962] Re: apport uses sys.argv instead of named arguments
** Patch added: "diff for bionic to support named param. (backport from cosmic)" https://bugs.launchpad.net/apport/+bug/1732962/+attachment/5405276/+files/apport_2.20.9-0ubuntu7.18.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732962 Title: apport uses sys.argv instead of named arguments To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1732962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
Verified that the report from apport-2.20.9-0ubuntu7.17 from bionic- proposed includes the ProcFB details. Verification-done ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887974] Re: [20.04] Valgrind: PPC sync instruction L field should only be 2 bits in ISA 3.0
Both patches are available and ready for SRU on Focal and Bionic.
After being tested individually from a ppa ppa:mclemenceau/distro-work on
ppc64le instances
** Description changed:
+ SRU Description
+
+ [Impact]
+ Valgrind mishandles the L field of the sync instruction.
+ More details are available at: https://bugs.kde.org/show_bug.cgi?id=422677
+ Single line patch available online with commit
fb6f7abcbc92506d302fb18a2c5fc853d2929248
+
+ [Test Case]
+ On a PPC64le Hardware
+ # sudo apt-get install gcc valgrind
+ #cat test-sync.c
+ define __SYNC(l) ".long (0x7c0004AC | ((" #l ") << 21))"
+
+ int
+ main ()
+ {
+ asm volatile(__SYNC(4) : : : "memory");
+ }
+
+ # gcc test-sync.c && valgrind --tool=none ./a.out
+ This will report this error unpatched part of the valgrind output
+
+ dis_memsync(ppc)(sync/lwsync,flag_L)
+ disInstr(ppc): unhandled instruction: 0x7C8004AC
+ primary 31(0x1F), secondary 1196(0x4AC)
+
+ # This won't report this error once using the updated version
+
+ [Regression Potential]
+ The regression potential is very low since this bug has been submitted
upstream and is already available in Groovy. Package build and run
successfully. Not anticipating regression
+
+ End SRU Description
+
+
---Problem Description---
This is a bug report for focal.
Valgrind, including version 3.16, mishandles the L field of the sync
instruction.
More details are available at: https://bugs.kde.org/show_bug.cgi?id=422677
This is a request to backport the following Valgrind patch from
upstream:
commit fb6f7abcbc92506d302fb18a2c5fc853d2929248
Author: Carl Love
Date: Tue Jun 9 10:42:03 2020 -0500
- Power PC Fix extraction of the L field for sync instruction
-
- The L field is currently a two bit[22:21] field in ISA 3.0. The size of
the
- L field has changed over time.
-
- Currently the ISA 3.0 Valgrind sync instruction support code sets the
- flag_L for the instruction L field to a five bit value that includes bits
- that are marked reserved the sync instruction. This patch fixes the
issue for ISA 3.0
- to only setting flag_L the specified two bits.
-
- Valgrind bugzilla: https://bugs.kde.org/show_bug.cgi?id=422677
-
- Contact Information = Tulio Magno/tul...@linux.ibm.com
-
+ Power PC Fix extraction of the L field for sync instruction
+
+ The L field is currently a two bit[22:21] field in ISA 3.0. The size of
the
+ L field has changed over time.
+
+ Currently the ISA 3.0 Valgrind sync instruction support code sets the
+ flag_L for the instruction L field to a five bit value that includes bits
+ that are marked reserved the sync instruction. This patch fixes the
issue for ISA 3.0
+ to only setting flag_L the specified two bits.
+
+ Valgrind bugzilla: https://bugs.kde.org/show_bug.cgi?id=422677
+
+ Contact Information = Tulio Magno/tul...@linux.ibm.com
+
---uname output---
N/A
-
- Machine Type = Reproducible on all POWER8 and POWER9 servers
-
+
+ Machine Type = Reproducible on all POWER8 and POWER9 servers
+
---Debugger---
A debugger is not configured
-
+
---Steps to Reproduce---
- $ cat test-sync.c
+ $ cat test-sync.c
#define __SYNC(l) ".long (0x7c0004AC | ((" #l ") << 21))"
int
main ()
{
- asm volatile(__SYNC(4) : : : "memory");
+ asm volatile(__SYNC(4) : : : "memory");
}
$ gcc test-sync.c && valgrind --tool=none ./a.out
==150073== Nulgrind, the minimal Valgrind tool
==150073== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote.
==150073== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==150073== Command: ./a.out
- ==150073==
+ ==150073==
dis_memsync(ppc)(sync/lwsync,flag_L)
disInstr(ppc): unhandled instruction: 0x7C8004AC
- primary 31(0x1F), secondary 1196(0x4AC)
+ primary 31(0x1F), secondary 1196(0x4AC)
==150073== valgrind: Unrecognised instruction at address 0x180788.
==150073==at 0x180788: main (in /home/tuliom/tmp/a.out)
==150073== Your program just tried to execute an instruction that Valgrind
==150073== did not recognise.
...
-
- Userspace tool common name: Valgrind
-
- The userspace tool has the following bit modes: 64-bit
+
+ Userspace tool common name: Valgrind
+
+ The userspace tool has the following bit modes: 64-bit
Userspace deb: valgrind
Userspace tool obtained from project website: na
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887974
Title:
[20.04] Valgrind: PPC sync instruction L field should only be 2 bits
in ISA 3.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1887974/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887974] Re: [20.04] Valgrind: PPC sync instruction L field should only be 2 bits in ISA 3.0
debdiff ready for sponsorship and SRU for Focal ** Changed in: valgrind (Ubuntu Bionic) Status: New => In Progress ** Patch added: "valgrind_3.15.0-1ubuntu9.1.debdiff" https://bugs.launchpad.net/ubuntu-power-systems/+bug/1887974/+attachment/5403275/+files/valgrind_3.15.0-1ubuntu9.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887974 Title: [20.04] Valgrind: PPC sync instruction L field should only be 2 bits in ISA 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1887974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887974] Re: [20.04] Valgrind: PPC sync instruction L field should only be 2 bits in ISA 3.0
debdiff ready for sponsorship and SRU for Bionic ** Patch added: "valgrind_3.13.0-2ubuntu2.3.debdiff" https://bugs.launchpad.net/ubuntu-power-systems/+bug/1887974/+attachment/5403276/+files/valgrind_3.13.0-2ubuntu2.3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887974 Title: [20.04] Valgrind: PPC sync instruction L field should only be 2 bits in ISA 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1887974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887974] Re: [20.04] Valgrind: PPC sync instruction L field should only be 2 bits in ISA 3.0
** Changed in: valgrind (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887974 Title: [20.04] Valgrind: PPC sync instruction L field should only be 2 bits in ISA 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1887974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887974] Re: [20.04] Valgrind: PPC sync instruction L field should only be 2 bits in ISA 3.0
** Changed in: valgrind (Ubuntu Focal) Assignee: (unassigned) => Matthieu Clemenceau (mclemenceau) ** Changed in: valgrind (Ubuntu Bionic) Assignee: (unassigned) => Matthieu Clemenceau (mclemenceau) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887974 Title: [20.04] Valgrind: PPC sync instruction L field should only be 2 bits in ISA 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1887974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
** Tags added: rls-gg-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
The attached deb diff will fix issue this on bionic as of today with latest apport on bionic being 2.20.9-0ubuntu7.16 ** Description changed: - linux-firmware doesn't install any package hooks for apport, so it will - only carry some default items leaving hardware list, kernel messages - unattached. Suggest symlink /usr/share/apport/package-hooks - /source_linux-firmware.py to source_linux.py as other linux image debs - do in bug 1847967. + Updated Description to match SRU requirements for bionic - Test Case - - - 1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'. + [Impact] + linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks/source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. + + [Test Case] + 1) On an Ubuntu 18.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. - Regression Potential - - None, as we are just adding a symlink from linux-firmware to the linux source package hook. + [Regression Potential] + Very limited, as we are just adding a symlink from linux-firmware to the linux source package hook. this change has been available in Focal and Groovy without problem + Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Patch added: "apport_2.20.9-0ubuntu7.17.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1872059/+attachment/5399419/+files/apport_2.20.9-0ubuntu7.17.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869187] Re: mokutil ignores timeout parameter
Confirmed shim-signed 1.37~18.04.6+15+1533136590.3beb971-0ubuntu1 from bionic-proposed fixes the problem described on this ticket installed bionic # apt update # apt upgrade edit /etc/apt/source.list to include bionic-proposed # apt update # apt install shim-signed # dpkg -l | grep shim-signed ii shim-signed 1.37~18.04.6+15+1533136590.3beb971-0ubuntu1 amd64Secure Boot chain-loading bootloader (Microsoft-signed binary) Then install dkms firmware # sudo apt install fwts-efi-runtime-dkms Got prompt with a menu to set the MOK password # reboot Got prompt to enroll the MOK with previous password Keys shows enrolled # mokutil --list-enrolled ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869187 Title: mokutil ignores timeout parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mokutil/+bug/1869187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869187] Re: mokutil ignores timeout parameter
** Description changed: + This section is for Bionic SRU purpose + + [Impact] + Because mokutil ignores the timeout parameter in /usr/sbin/update-secureboot-policy + it becomes impossible to sign dkms-built modules with secure boot enable + + [Test Case] + With a bionic with secureboot enabled (tested in a VM) + Make sure Secure Boot is enable (should return : SecureBoot enabled) + # mokutil --sb-state + + Then install a dkms driver + # sudo apt install fwts-efi-runtime-dkms + This should prompt mok manager menu to setup Secure Boot password + The key details will be under + # mokutil --list-new + # reboot + + Without the patch nothing happen upon reboot. System boots fully + and the driver isn't installed + + With the solution installed, a menu will pop up on reboot to enroll the key + Once the key is enrolled it will show up under + # mokutil --list-enrolled + + + [Regression Potential] + This change is fairly minimal and has been shipping with Focal. + Possible regression could involve inability to sign other drivers. + + End SRU + -- + Version info: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Done upgrade and dist-upgrade on March 26th, just before reporting this. mokutil: - Installed: 0.3.0+1538710437.fb6250f-1 + Installed: 0.3.0+1538710437.fb6250f-1 dkms: - Installed: 2.8.1-5ubuntu1 + Installed: 2.8.1-5ubuntu1 shim-signed: - Installed: 1.41+15+1552672080.a4a1fbe-0ubuntu1 + Installed: 1.41+15+1552672080.a4a1fbe-0ubuntu1 Dell precision M3800, secure boot on (obviously) The backstory of it, is that in development version of 20.04 it became impossible to sign dkms-built modules with secure-boot enabled. The ncurses-based interfaces opens normally and prompts for the password twice (as usual), but after reboot the key-enrollment menu does not appear. After comparing all the packages involved into this process with the ones from 19.04, I managed to pinpoint the culprit, namely: /usr/sbin/update-secureboot-policy, lines 111 and 120 call mokutil with timeout parameter. Removing that argument like this: 111c111 < printf '%s\n%s\n' "$key" "$again" | mokutil --enable-validation >/dev/null || true --- > printf '%s\n%s\n' "$key" "$again" | mokutil --timeout -1 --enable-validation >/dev/null || true 120c120 < printf '%s\n%s\n' "$key" "$again" | mokutil --import "$SB_KEY" >/dev/null || true --- > printf '%s\n%s\n' "$key" "$again" | mokutil --timeout -1 --import "$SB_KEY" >/dev/null || true fixes the problem, yet to me it does not eliminate its root cause. Picking up those trails, I decided to fiddle with mokutil itself. In my case, adding any --timeout param (not only -1, but any integer really) triggers it to display help/usage message, nothing more. For that reason I am quite convinced that my actions related to update-secureboot-policy script are merely a workaround, while mokutil is the actual source of the problem. - - I am fully aware, that: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1856422 is a design decision, and I know why it was introduced. Yet, in case of my machine (several other ones to be checked soon) it breaks the signing process completely. + I am fully aware, that: https://bugs.launchpad.net/ubuntu/+source/shim- + signed/+bug/1856422 is a design decision, and I know why it was + introduc
[Bug 1869187] Re: mokutil ignores timeout parameter
** Changed in: shim-signed (Ubuntu Bionic) Assignee: (unassigned) => Matthieu Clemenceau (mclemenceau) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869187 Title: mokutil ignores timeout parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mokutil/+bug/1869187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878517] Re: please apply bash 5.0 patch 17
tested proposed package with Focal with 2 different instances with given script. Both tests were successful. ** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878517 Title: please apply bash 5.0 patch 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883229] Re: Ubuntu server installation on S3260M4 server gets failed
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883229 Title: Ubuntu server installation on S3260M4 server gets failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1883229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878517] Re: please apply bash 5.0 patch 17
** Description changed:
+ This section is for Focal SRU purpose
+
+ [Impact]
+ From https://ftp.gnu.org/gnu/bash
+ There were cases where bash 5.0 patch 16 reaped process substitution file
descriptors (or FIFOs) and processes to early. This is a better fix for the
problem that bash50-016 attempted to solve.
+
+ [Test Case]
+ This simple bash script pass when bash with patch 017 is installed
+ Recommend to run it before and after installing the update to notice the
difference
+
+ ```
+ #!/usr/bin/bash
+
+ ouch() {
+ cat < <(echo bar)
+ cat "$1"
+ }
+
+ ouch2() {
+ { cat; } < <(echo bar)
+ cat "$1"
+ }
+
+ ouch <(echo "foo")
+ ouch2 <(echo "foo")
+ ```
+ Expected output with the patch installed:
+
+ foo
+ bar
+ foo
+ bar
+
+ [Regression Potential]
+ This is an upstream patch level update with no additional modification. The
regression potential should be fairly low. Also the patch is intended to only
fix this problem.
+ Possible regression would be unforeseen additional process substitutions that
upstream bash would share.
+
+ End SRU
+ --
+ Original Bug Description:
+
I am using Ubuntu 20.04 for development and has hit a bug in bash 5.0
patch 16.
I can't reproduce it in pure bash, but with bats from https://github.com
/bats-core/bats-core/ it is very easy to repro:
```
# cat << EOF > ya.bats
check() {
- echo "check $@"
- ls -l /proc/self/fd
+ echo "check $@"
+ ls -l /proc/self/fd
}
@test "here file" {
- check -p <(echo "hey")
- false
+ check -p <(echo "hey")
+ false
}
EOF
$ bats ya.bats
```
Normally the output should contain the line
-lr-x-- 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918]
+ lr-x-- 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918]
which is a result of a "here file" created by bash via <(echo "hey").
In my testing, about 50% of runs don't have /dev/fd/63 listed.
I found out this is a manifest of a bug introduced in bash 5.0 patch 16
(see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-016)
The bug is fixed in 5.0 patch 17 (see
http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-017).
Please update bash to patchlevel 17.
** Patch added: "debdiff for focal SRU"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+attachment/5386580/+files/bash-5.0-6ubuntu1.1-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878517
Title:
please apply bash 5.0 patch 17
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878517] Re: please apply bash 5.0 patch 17
** Changed in: bash (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878517 Title: please apply bash 5.0 patch 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874649] Re: Update servicelog package to version v1.1.15
Booth Groovy and Focal have servicelog 1.1.15 already. I don't think there's anything to do Matthieu ** Changed in: servicelog (Ubuntu Focal) Status: New => Invalid ** Changed in: servicelog (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874649 Title: Update servicelog package to version v1.1.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1874649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878517] Re: please apply bash 5.0 patch 17
** Changed in: bash (Ubuntu Focal) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878517 Title: please apply bash 5.0 patch 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878517] Re: please apply bash 5.0 patch 17
This patch applies upstream patch 017 to groovy's bash-5..0 ** Patch added: "bash-5.0-6ubuntu2-groovy.debdiff" https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+attachment/5385047/+files/bash-5.0-6ubuntu2-groovy.debdiff ** Changed in: bash (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878517 Title: please apply bash 5.0 patch 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878517] Re: please apply bash 5.0 patch 17
** Changed in: bash (Ubuntu) Assignee: (unassigned) => Matthieu Clemenceau (mclemenceau) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878517 Title: please apply bash 5.0 patch 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878517] Re: please apply bash 5.0 patch 17
** Changed in: bash (Ubuntu Focal) Assignee: (unassigned) => Matthieu Clemenceau (mclemenceau) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878517 Title: please apply bash 5.0 patch 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874646] Re: Update libvpd package to v2.2.7
Here is the debdiff for focal SRU ** Patch added: "libvpd-2.2.6-1ubuntu1-focal.diff" https://bugs.launchpad.net/ubuntu/focal/+source/libvpd/+bug/1874646/+attachment/5383346/+files/libvpd-2.2.6-1ubuntu1-focal.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874646 Title: Update libvpd package to v2.2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1874646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874646] Re: Update libvpd package to v2.2.7
** Description changed: + This section is for Focal SRU purpose + + [Impact] + + A udev script is getting triggered whenever there is a change in sysfs. + All is does is "/bin/touch /run/run.vpdupdate". + + Script was generic and used to trigger whenever there is any change in /sys/devices/ node. + On large system it resulted in calling udev script number of times during boot and impacted on boot time performance. + + [Test Case] + It is unfortunately difficult to reproduce this problem with the proper hardware setup so IBM will very that the new udev script is in place and acting as expected and that /run/run.vupdate isn't modified unnecessarily. + + [Regression Potential] + Even if unlikely a regression potential would be to prevent the system to boot. + + -- + + Initial Bug Description below: + == Comment: #0 - Shivaprasad G. Bhat - 2020-04-24 02:51:41 == ---Problem Description--- Update libvpd package to v2.2.7 - - Contact Information = shiva...@in.ibm.com - + + Contact Information = shiva...@in.ibm.com + ---Additional Hardware Info--- - ppc64le + ppc64le - ---uname output--- ppc64le - - Machine Type = IBM Power - + + Machine Type = IBM Power + ---Debugger--- A debugger is not configured - + ---Steps to Reproduce--- - Sources are moved to github at + Sources are moved to github at https://github.com/power-ras/libvpd.git Update both libvpd and libvpd-dev - - Userspace tool common name: libvpd - - The userspace tool has the following bit modes: 64-bit + + Userspace tool common name: libvpd + + The userspace tool has the following bit modes: 64-bit Userspace rpm: libvpd - Userspace tool obtained from project website: na - - *Additional Instructions for shiva...@in.ibm.com: + Userspace tool obtained from project website: na + + *Additional Instructions for shiva...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874646 Title: Update libvpd package to v2.2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1874646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874646] Re: Update libvpd package to v2.2.7
Hey Vasant, I will prepare the SRU for 20.04 but in the meanwhile, it would help if you could confirm that the groovy version of libvpd 2.2.6-1ubuntu1 works properly for you. Thanks in Advance Matthieu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874646 Title: Update libvpd package to v2.2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1874646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874646] Re: Update libvpd package to v2.2.7
In order to SRU these cherry picked commits into Focal, would you mind providing me some simple instructions allowing me to reproduce a problem and confirm it is resolved with the updated package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874646 Title: Update libvpd package to v2.2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1874646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874646] Re: Update libvpd package to v2.2.7
Ok I guess I can rebase 2.2.7 for groovy and cherry pick for Focal Noted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874646 Title: Update libvpd package to v2.2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1874646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874646] Re: Update libvpd package to v2.2.7
** Changed in: libvpd (Ubuntu Focal) Status: New => In Progress ** Changed in: libvpd (Ubuntu Focal) Assignee: Canonical Foundations Team (canonical-foundations) => Matthieu Clemenceau (mclemenceau) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874646 Title: Update libvpd package to v2.2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1874646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874644] Re: Update ppc64-diag package to v2.7.6
I'm confused, it appears both Focal and Groovy already have ppc64-diag 2.7.6 I don't think there's anything to do here unless I'm missing something. Matt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874644 Title: Update ppc64-diag package to v2.7.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1874644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874646] Re: Update libvpd package to v2.2.7
** Changed in: libvpd (Ubuntu Groovy) Status: New => In Progress ** Changed in: libvpd (Ubuntu Groovy) Assignee: Canonical Foundations Team (canonical-foundations) => Matthieu Clemenceau (mclemenceau) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874646 Title: Update libvpd package to v2.2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1874646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874646] Re: Update libvpd package to v2.2.7
Hey Frank, I have cherry picked commits discussed in comment #2. uploaded to my ppa, successfully built and installed. I will get this package sponsored and uploaded and start looking into the SRU process for focal. Matt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874646 Title: Update libvpd package to v2.2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1874646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870579] Re: System can't find OS to boot after install with UEFI over Windows 10
Attached is the efibootmgf -v output for the third laptop an HP mt20 after I finally boot off the ubuntu boot sequence (using F9 boot menu) ** Attachment added: "efibootmgr-v.log" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1870579/+attachment/5373000/+files/efibootmgr-v.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870579 Title: System can't find OS to boot after install with UEFI over Windows 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1870579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870579] Re: System can't find OS to boot after install with UEFI over Windows 10
I installed focal on a third HP laptop and got the same results. This Laptop had Win 10 installed on it and after a full install of Focal, I removed the USB key press Enter and system would not boot again. It would say could not find OS Then after Pressing F9 to choose boot device and selecting Ubuntu as default boot it would work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870579 Title: System can't find OS to boot after install with UEFI over Windows 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1870579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838323] Re: Support Japanese new era "令和 (Reiwa)"
** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838323 Title: Support Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unicode-data/+bug/1838323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838323] Re: Support Japanese new era "令和 (Reiwa)"
tested bionic with unicode-data 10.0.0-3ubuntu0.18.04.1 from proposed. New ERA NAME REIWA was available in /usr/share/unicode but gucharmap would not find it. Also recompiling gucharmap, because it is a reverse-build-deps, fails with unicode-data 10.0.0-3ubuntu0.18.04.1. Sames results with xenial with relative version from xenial and xenial proposed of unicode-data I confirmed New ERA NAME REIWA is installed and working on Focal. I recommend will Not Fix for this SRU in Bionic and Xenial since it requires other packages to be modified so they can recompile -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838323 Title: Support Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unicode-data/+bug/1838323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838323] Re: Support Japanese new era "令和 (Reiwa)"
** Tags removed: verification-needed-bionic verification-needed-disco verification-needed-xenial ** Tags added: verification-failed-bionic verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838323 Title: Support Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unicode-data/+bug/1838323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872100] Re: "The GRUB bootloader was previously installed to a disk that is no longer present..."
** Tags added: champagne rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872100 Title: "The GRUB bootloader was previously installed to a disk that is no longer present..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1872100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870579] Re: System can't find OS to boot after install with UEFI over Windows 10
Thanks Dimitri for the link to the FirmwareTestSuite! So I got it up and running adn captured the UEFI test report. Now after booting of this key and doing a poweroff, the system was able to boot from the Ubuntu system installed on the disk. ** Attachment added: "results.html" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1870579/+attachment/5350554/+files/results.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870579 Title: System can't find OS to boot after install with UEFI over Windows 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1870579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870579] Re: System can't find OS to boot after install with UEFI over Windows 10
Thanks Dimitri for the link to the FirmwareTestSuite! So I got it up and running adn captured the UEFI test report. Now after booting of this key and doing a poweroff, the system was able to boot from the Ubuntu system installed on the disk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870579 Title: System can't find OS to boot after install with UEFI over Windows 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1870579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871615] Re: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of file on stdin at conffile prompt
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871615 Title: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of file on stdin at conffile prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1871615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor
** Changed in: grub2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor
After removing all devices plugged in one by one, Issue seems to be caused by my USB dongle needed for my wireless keyboard and mouse... I've seen report online see below https://askubuntu.com/questions/884199/grub-freezes-when-logitech-unifying-receiver-plugged-in https://h30434.www3.hp.com/t5/Notebook-Operating-System-and-Recovery/Linux-Spectre-x360-13-late-2019-does-not-work-with-Linux/td-p/7316977 Those two reports seem limited to my hardware, could be HP BIOS. the recommended workaround is to enable Legacy Mode which isn't acceptable for me since it requires to disable Secure Boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor
** Also affects: grub (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor
I started thinking this wasn't a kernel issue since I wasn't getting any display from a cold boot... I changed grub configuration to show menu and remove quiet splash from Linux CMD LINE and it turns out that when I press the power button the first thing I see is the Grub menu and no keyboard input are working, arrows or enter key when USB-C is plugged in but when I unplugged the USB-Type C monitor, I can press enter during the Grub menu and it boots. So I believe the issue is with Grub hanging while USB-C monitor plugged in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor
Unfortunately, when the screen is black I have no ssh access >From a cold boot, When I press the power button, nothing happen, the screen >remains black, I don't even see the BIOS logo or FDE password key. (when USB-C >is plugged in) I'm having a feeling the kernel might not even be started and it could be a Hardware BIOS issue... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870579] Re: System can't find OS to boot after install with UEFI
I'm able to consistently reproduce this problem on my PC. After I reinstall Win10 and then reinstall Focal, I get the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870579 Title: System can't find OS to boot after install with UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1870579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870579] [NEW] System can't find OS to boot after install with UEFI
Public bug reported: I installed Focal Fossa Beta on 2 different platform one all in one with Windows 10 and one laptop with another Linux OS. Both HP platforms I chose install with UEFI, went thru the pretty standard install process. When install is complete, I remove the key and pressed Enter. On both devices, the bios would loop trying to find an OS to boot without success I pressed F9 to look at the boot options and both system had UEFI - ubuntu available. Once I chose it., it boot to the freshly installed Focal Fossa. Subsequent reboot are successful. Also Subsequent install on top of Focal Fossa didn't show this problem. I will install Win 10 again and see if this happen again. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 3 11:54:26 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed quiet splash --- InstallationDate: Installed on 2020-04-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870579 Title: System can't find OS to boot after install with UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1870579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor
@Francis, Yes, unfortunately. I just updated this morning to 5.4.0-21 #25 I tried two different reboot without success. Let me know if there's anything else you would need or more traces. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] Re: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705064] Re: lshw doesn't have logicalname, serial number, or size for nvme device
nevermind my previous comment #9, wrong bug ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705064 Title: lshw doesn't have logicalname, serial number, or size for nvme device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1705064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705064] Re: lshw doesn't have logicalname, serial number, or size for nvme device
Focal still has lshw 02.18.85-0.3ubuntu1, I don't see 02.18.85-0.3ubuntu2 in proposed, the last push to proposed was 01-30-2020 Is this going to be push to proposed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705064 Title: lshw doesn't have logicalname, serial number, or size for nvme device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1705064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335382/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335383/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335381/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335380/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335376/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335378/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335377/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335379/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335384/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335369/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335375/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335372/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335370/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335371/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335373/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1866852/+attachment/5335374/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866852 Title: System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866852] [NEW] System Display black screen on reboot or after a clean shutdown with USB-C Dock Monitor
Public bug reported: I'm running focal devel and the latest kernel (see proc version below) Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version 9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 Dock Monitor is supported very well with multiple usb devices plugged on the monitor. However on reboot I face a black screen with no ability to enter my FDE password. Both my Laptop screen and the attached usb-c display nothing I have to hard power off and reboot without the USB-C monitor plugged in. Otherwise A reboot cycle with the usb-c unplugged works perfectly. Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic without success. I would be happy to provide much more debugging information. I will attach then to the launchpad Bug # --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mclemenceau 2988 F pulseaudio /dev/snd/controlC0: mclemenceau 2988 F pulseaudio /dev/snd/controlC1: mclemenceau 2988 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-05 (64 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13-ae0xx NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-23 (47 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.vendor: AMI dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.41 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.21:bd06/14/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.41:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 2TV18AS#ABA dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-collected champagne focal ** Tags added: champagne ** Tags added: focal ** Tags added: apport-collected ** Description changed: I'm running focal devel and the latest kernel (see proc version below) Linux version 5.4.0-18-generic (buildd@lgw01-amd64-034) (gcc version 9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 Dock Monitor is supported very well with multiple usb devices plugged on the monitor. However on reboot I face a black screen with no ability to enter my FDE password. Both my Laptop screen and the attached usb-c display nothing I have to hard power off and reboot without the USB-C monitor plugged in. Otherwise A reboot cycle with the usb-c unplugged works perfectly. - Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic - without success. I would be happy to provide much more debugging - information. I will attach then to the launchpad Bug # + Also I tried to run ubuntu-bug linux or ubuntu-bug linux-image-generic without success. I would be happy to provide much more debugging information. I will attach then to the launchpad Bug # + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: mclemenceau 2988 F pulseaudio + /dev/snd/controlC0: mclemenceau 2988 F pulseaudio + /dev/snd/controlC1: mclemenceau 2988 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-01-05 (64 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + MachineType: HP HP Spectre x360 Convertible 13-ae0xx + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-18-generic N/A + linux-backpor
[Bug 1866092] [NEW] GDM login input isn't centered
Public bug reported: Updated to latest focal devel branch as of 2020/03/04 at 4pm When you enter your password, the input text isn't centered I will attach a screenshot ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-17.21-lowlatency 5.4.22 Uname: Linux 5.4.0-17-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 4 16:57:22 2020 InstallationDate: Installed on 2020-01-05 (58 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, user) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-01-23 (41 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal ** Attachment added: "gdm.png" https://bugs.launchpad.net/bugs/1866092/+attachment/5333558/+files/gdm.png ** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866092 Title: GDM login input isn't centered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1866092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843063] Re: lshw -json output invalid in Eoan
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843063 Title: lshw -json output invalid in Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
