[Group.of.nepali.translators] [Bug 1600000] Re: libnss-resolve treats two trailing dots on a domain name incorrectly
** Changed in: systemd Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/160 Title: libnss-resolve treats two trailing dots on a domain name incorrectly Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Bug description: [Impact] libnss-resolve is an optional component not used by default in xenial. However it treats doubledot incorrectly, meaning it gets resolved when it shouldn't. [Fix] Cherrypick upstream patch to resolve this issue. [Testcase] * Enable resolve nss module * attempt resolving www.gnu.org.. * It should fail to resolve (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org.. 208.118.235.148 STREAM wildebeest.gnu.org 208.118.235.148 DGRAM 208.118.235.148 RAW (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ resolve dns/ dns/' /etc/nsswitch.conf (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org.. (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ dns/ resolve dns/' /etc/nsswitch.conf (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org.. 208.118.235.148 STREAM wildebeest.gnu.org 208.118.235.148 DGRAM 208.118.235.148 RAW (base)adconrad@nosferatu:~$ This is responsible for the new regression in glibc: -- FAIL: posix/tst-getaddrinfo5 original exit status 1 resolving "localhost." worked, proceeding to test resolving "localhost.." failed, test passed resolving "www.gnu.org." worked, proceeding to test resolving "www.gnu.org.." worked, test failed -- [Regression potential] Minimal, since this component is not used by default. However, systems that have this enabled exhibit standards non-compliant behavior. It is not expected for anybody to depend on this broken behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/160/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records
** Changed in: systemd
Status: New => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1647031
Title:
systemd-resolved’s 127.0.0.53 server does not follow CNAME records
Status in Nextcloud:
Fix Released
Status in systemd:
Fix Released
Status in network-manager package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in network-manager source package in Xenial:
Invalid
Status in systemd source package in Xenial:
Invalid
Status in network-manager source package in Yakkety:
Invalid
Status in systemd source package in Yakkety:
Fix Released
Bug description:
[SRU Justification]
Ubuntu 16.10 server uses systemd-resolved by default, configured both as a
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved
talking to the dbus service. The DNS stub resolver has a bug that causes it to
fail to resolve CNAME records. This went unnoticed before release because by
default the NSS module is used. But a chroot or container on the system that
does not include libnss-resolved and is configured to use the stub resolver
will experience DNS failures.
[Test case]
1. On a yakkety server system, create a xenial chroot with mk-sbuild (or
equivalent).
2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
3. Install the iputils-ping package.
4. ping www.freedesktop.org
5. Confirm that the hostname does not resolve.
6. Install the systemd package from yakkety-proposed onto the host system.
7. ping www.freedesktop.org
8. Confirm that the hostname does now resolve.
[Regression potential]
With a 247-line patch to a key service, there is some risk of regression.
Regression risk is mitigated because this patch is already present in zesty and
upstream, where no regressions have been reported, and because it only touches
the DNS stub resolver which is not the code path used by default on host
systems.
$ systemd-resolve www.freedesktop.org
www.freedesktop.org: 131.252.210.176
2610:10:20:722:a800:ff:feda:470f
(annarchy.freedesktop.org)
-- Information acquired via protocol DNS in 673.6ms.
-- Data is authenticated: no
$ ping www.freedesktop.org
ping: www.freedesktop.org: Name or service not known
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
$ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
;www.freedesktop.org. IN A
www.freedesktop.org. 7146IN CNAME annarchy.freedesktop.org.
$ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
;www.freedesktop.org. IN A
www.freedesktop.org. 14399 IN CNAME annarchy.freedesktop.org.
annarchy.freedesktop.org. 14399 IN A 131.252.210.176
I trust it needn’t be explained why this makes the internet almost
completely useless in zesty.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1734983] Re: Request to backport sosreport v3.5
** Changed in: sosreport Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1734983 Title: Request to backport sosreport v3.5 Status in sosreport: Fix Released Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Trusty: Fix Released Status in sosreport source package in Xenial: Fix Released Status in sosreport source package in Zesty: Won't Fix Status in sosreport source package in Artful: Fix Released Status in sosreport source package in Bionic: Fix Released Status in sosreport package in Debian: New Bug description: [Impact] Canonical support team (AKA STS) largely depend on sosreport package to troubleshoot system. sosreport is always in constant development including new bugfixes, new features such as new plugins[1], that can be interesting to have in a support context. v3.5 is already found in devel release (bionic). We create this LP in the attempt to justify the SRU of v3.5 backport into current supported stable releases. [1] - New plugins for : * perl * boom * vdo * os_net_config * conntrackd * ovirt_imageio * nss * sas3ircu * openstack_aodh * docker_distribution * gluster_block * snappy Plugin API enhancements * Plugin triggers by executable name * Improved log size limit handling * Better handling of compressed log files * Per-plugin package verification lists Updates to 227 plugins This will also allow us to close some sosreport LP bugs: *Docker plugin uses the wrong command for Ubuntu (LP: #1693574) [Test Case] * Install sosreport $ apt-get install sosreport * Run sosreport $ sosreport -a $ sosreport -o $ ... * Make sure it generate a tar.xz file in /tmp in the form of "/tmp/sosreport--.tar.xz" * Extract files from archive $ tar Jxvf /tmp/sosreport--.tar.xz * Look the content of sosreport, make sure the information is accurate and valid, * Make sure all files that should to be collected by sosreport aren't 0 size. (Files that should be collected may varies from one system to another, it depends on what packages are installed, ...) $ find /tmp/sosreport-- -size 0 # Note : It is normal to see some 0 size files here and there, again it depend on how the plugin is run (package detection or not inside the plugins, ...) and if the package is installed or not on the system where you run sosreport. But in most cases, if the package is installed and if sosreport has a plugin for it then it should gather information, if not then it might be a problem with the plugins itself that need adjustments. [Regression Potential] * autopkgtest[2] didn't reveal any [2] - See Comment #1 * We,STS, have intensively tested the package. During our testing, we found a severe regression that we already took action to fix it via : - Upstream issue - https://github.com/sosreport/sos/issues/1155 - Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537 - Fix Released in Ubuntu Devel release (bionic) via debdiff : lp1734983_bionic.debdiff [Other Info] * Sosreport upstream : https://github.com/sosreport/sos * rmadison -u debian,ubuntu sosreport debian: sosreport | 3.2-2| oldstable | source, amd64, arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x sosreport | 3.2-2| oldstable-kfreebsd | source, kfreebsd-amd64, kfreebsd-i386 sosreport | 3.3+git50-g3c0349b-2 | stable | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x sosreport | 3.5-1| testing| source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x sosreport | 3.5-1| unstable | source, amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x ubuntu: sosreport | 3.0-1~ubuntu12.04.1 | precise-backports/universe | source, amd64, armel, armhf, i386, powerpc sosreport | 3.1-1ubuntu2 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.1-1ubuntu2.2 | trusty-security| source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.2-2~ubuntu14.04.1 | trusty-backports | source, amd64, arm64, armhf, i386, powerpc, ppc64el sosreport | 3.2+git276-g7da50d6-3ubuntu1 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x sosreport | 3.3+git50-g3c0349b-2 | zesty
[Group.of.nepali.translators] [Bug 1803385] Re: fetch-url does not use --no-check-certificate on HTTP to HTTPS redirects
Closing this bug as Invalid. The real solution is fix-released in LP#1807023. This bug was a workaround for not having ca-certificates in d-i and use an HTTP mirror that redirected to HTTPS (the resulting certificate validation error couldn't be ignored due to HTTP protocol not using the wget option.) But this is no longer required with the ca-certificates shipped in debian-installer. Sorry, I had lost track of this bug. Mauricio ** Changed in: debian-installer-utils (Ubuntu) Status: In Progress => Invalid ** Changed in: debian-installer-utils (Ubuntu Trusty) Status: In Progress => Invalid ** Changed in: debian-installer-utils (Ubuntu Xenial) Status: In Progress => Invalid ** Changed in: debian-installer-utils (Ubuntu Bionic) Status: In Progress => Invalid ** Changed in: debian-installer-utils (Ubuntu Cosmic) Status: In Progress => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1803385 Title: fetch-url does not use --no-check-certificate on HTTP to HTTPS redirects Status in debian-installer-utils package in Ubuntu: Invalid Status in debian-installer-utils source package in Trusty: Invalid Status in debian-installer-utils source package in Xenial: Invalid Status in debian-installer-utils source package in Bionic: Invalid Status in debian-installer-utils source package in Cosmic: Invalid Status in debian-installer-utils package in Debian: New Bug description: [Impact] * fetch-url fails to download files from URL with HTTP to HTTPS redirect if server has invalid/cannot be verified certificate. * Install fails in case a preseed/other files use an HTTP URL that redirects to an HTTPS URL with an invalid certificate. * Servers/URLs that started using HTTP to HTTPS redirect and have their URLs already spread over scripts/infrastructure start to cause install/deployment failures. * This fix checks for debian-installer/allow_unauthenticated_ssl in the HTTP protocol as well (to enable --no-check-certificate), which is OK as that option must be explicitly enabled by users, indicating awareness of the SSL/HTTPS context and certificates that may not be verified. [Test Case] * Setup web-server with HTTP to HTTPS redirect and an invalid/ self-signed certificate, and put a file (eg, preseed) on it. * Boot with preseed option 'url=http:///preseed' and the install will fail in the 'network-preseed' stage, with syslog errors about invalid/cannot be verified certificates, suggesting the 'wget --no-check-certificate' option. * Other files downloaded by the installer can hit same error, if using HTTP URLs from that server. * In the installer shell, run: ~ # fetch-url http:/// [Regression Potential] * Low risk of regression, this only expands the check from HTTPS-only to HTTPS or HTTP, to *then* check for d-i/allow_unauthenticated_ssl. * The theoretical case is that a HTTP URL with no redirect to HTTPS may use --no-check-certificate, thus without actually needing it, (it should not cause problems at all, the option should be ignored) but anyway, since the user acknowledged that sort of behavior with the d-i/allow_unauthenticated_ssl, that should not be a concern. [Other Info] * Debian Bug #913740. [Problem Description] In fetch-url the --no-check-certificate option is conditioned to HTTPS. In case of HTTP to HTTPS redirect, that option is not enabled, and may cause fetch-url to fail if the certificate cannot be verified. Since that option/functionality must be explicitly requested with the debian-installer/allow_unauthenticated_ssl preseed option (i.e., user is aware of SSL/HTTPS context and agrees w/ non-verified certificates) we can just check for this in the HTTP protocol too, and assume HTTPS may potentially be used, as the user specified this option. An alternative/obvious solution in the _user_ side is to specify HTTPS URLs upfront, but there are cases when an user does not know for sure whether the server uses/supports that, or the server might change its behavior and start HTTP to HTTPS redirect after URLs have spread over (e.g., scripts and infrastructure) - thus a fix in the installer side is a simpler and more complete approach. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer-utils/+bug/1803385/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
It is fixed in Ubuntu Bionic and late but this LP bug have never been mentioned in the changelog, which explains why the status didn't change until now (after a manual status change from my part) Xenial hasn't been fix, I did some quick verification and base on the fix, which add a Depends as follow: debian/control: init-system-helpers (>= 1.47~) and considering rmadison: init-system-helpers | 1.29ubuntu1 | xenial | source, all init-system-helpers | 1.29ubuntu4 | xenial-updates | source, all I'm afraid the fix won't work for Xenial. With that being said, I will set Xenial to "Won't fix". Please feel free to re-open it if you judge Xenial need the fix by providing good justification/rational. - Eric ** Changed in: rsyslog (Ubuntu Zesty) Status: Won't Fix => Fix Released ** Changed in: rsyslog (Ubuntu Xenial) Status: In Progress => Fix Released ** Changed in: rsyslog (Ubuntu Xenial) Status: Fix Released => Won't Fix ** Changed in: rsyslog (Ubuntu Trusty) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Trusty: Won't Fix Status in rsyslog source package in Xenial: Won't Fix Status in rsyslog source package in Zesty: Fix Released Status in rsyslog source package in Artful: Fix Released Status in rsyslog package in Debian: Fix Released Bug description: [Impact] Servers or cloud instances will not log important messages after initial deployment. Manual reboot or restart of services is necessary to get expected behaviour. [Test Case] 1) Install, enable and start haproxy 2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed 3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT created 4) Restart rsyslog service 5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created 6) Restart haproxy service and observe that log now is filled with entries With the patched deb steps 3,4 and 6 becomes irrelevant and everything works out of the box. [Regression Potential] Minimal. This patch merges a patch from Debian where a trigger is added to the rsyslog package that fires when other debs drop files into /etc/rsyslog.d. [Original Bug Description] rsyslog should reload its configuration when other packages drop configuration in /etc/rsyslog.d https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337 https://anonscm.debian.org/cgit/collab- maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1664844] Re: No distinction between link-up and link-down interfaces
** Changed in: nplan (Ubuntu Zesty) Status: In Progress => Won't Fix ** Changed in: nplan (Ubuntu Artful) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Bug description: [Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan will not be able to do anything "nice" for the interface, such as rename it to what the user specified in MAAS. If I include the interface but don't specify any addresses or DHCP, it isn't clear if it will be link up (my current assumption) or link down. There should be a way to allow an interface to be recognized by netplan (and even partially configured, waiting for the user to run something like 'ifup ' on a manual but not auto-started interface in ifupdown), but marked administratively disabled. (adminStatus down) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664844/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1664844] Re: No distinction between link-up and link-down interfaces
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags removed: verification-done-artful verification-done-xenial verification-done-zesty ** Changed in: systemd (Ubuntu) Status: New => In Progress ** Changed in: systemd (Ubuntu Zesty) Status: New => Won't Fix ** Package changed: nplan (Ubuntu) => netplan.io (Ubuntu) ** Changed in: systemd (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: netplan.io (Ubuntu Xenial) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Bug description: [Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan will not be able to do anything "nice" for the interface, such as rename it to what the user specified in MAAS. If I include the interface but don't specify any addresses or DHCP, it isn't clear if it will be link up (my current assumption) or link down. There should be a way to allow an interface to be recognized by netplan (and even partially configured, waiting for the user to run something like 'ifup ' on a manual but not auto-started interface in ifupdown), but marked administratively disabled. (adminStatus down) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664844/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1490030] Re: shim-signed should include an apport hook applying to shim and shim-signed source packages
** Changed in: shim-signed (Ubuntu Wily) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1490030 Title: shim-signed should include an apport hook applying to shim and shim- signed source packages Status in shim-signed package in Ubuntu: Fix Released Status in shim-signed source package in Trusty: Fix Released Status in shim-signed source package in Wily: Won't Fix Status in shim-signed source package in Xenial: In Progress Bug description: When bug reports are filed against shim or shim-signed, we almost always want to know: - the output of 'efibootmgr -v' - the directory listing of /boot/efi/EFI/ubuntu - whether /boot/efi/EFI/ubuntu/shim$efiarch.efi and /usr/lib/shim/shim.efi.signed match - whether /boot/efi/EFI/ubuntu/grub$efiarch.efi and /usr/lib/grub/$grubarch-efi-signed/grub$efiarch.efi.signed match We should have an apport hook that provides this information automatically. The hook should be shipped in the shim-signed package, for convenience of modification without round-tripping to Microsoft for re-signing of binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1490030/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
** Changed in: rsyslog (Ubuntu Zesty) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Trusty: In Progress Status in rsyslog source package in Xenial: In Progress Status in rsyslog source package in Zesty: Won't Fix Status in rsyslog source package in Artful: Fix Released Status in rsyslog package in Debian: Fix Released Bug description: [Impact] Servers or cloud instances will not log important messages after initial deployment. Manual reboot or restart of services is necessary to get expected behaviour. [Test Case] 1) Install, enable and start haproxy 2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed 3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT created 4) Restart rsyslog service 5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created 6) Restart haproxy service and observe that log now is filled with entries With the patched deb steps 3,4 and 6 becomes irrelevant and everything works out of the box. [Regression Potential] Minimal. This patch merges a patch from Debian where a trigger is added to the rsyslog package that fires when other debs drop files into /etc/rsyslog.d. [Original Bug Description] rsyslog should reload its configuration when other packages drop configuration in /etc/rsyslog.d https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337 https://anonscm.debian.org/cgit/collab- maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft
** Changed in: shim (Ubuntu Yakkety) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1637290 Title: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in shim package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in grub2 source package in Precise: Won't Fix Status in grub2-signed source package in Precise: Won't Fix Status in livecd-rootfs source package in Precise: Invalid Status in shim source package in Precise: Won't Fix Status in shim-signed source package in Precise: Won't Fix Status in grub2 source package in Trusty: Fix Released Status in grub2-signed source package in Trusty: Fix Released Status in livecd-rootfs source package in Trusty: Fix Released Status in shim source package in Trusty: In Progress Status in shim-signed source package in Trusty: In Progress Status in grub2 source package in Xenial: Fix Released Status in grub2-signed source package in Xenial: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in shim source package in Xenial: Fix Released Status in shim-signed source package in Xenial: Fix Released Status in grub2 source package in Yakkety: Fix Released Status in grub2-signed source package in Yakkety: Fix Released Status in livecd-rootfs source package in Yakkety: Fix Released Status in shim source package in Yakkety: Won't Fix Status in shim-signed source package in Yakkety: Fix Released Bug description: [Impact] We might want to boot securely one of these days. [Test case] 1) Upgrading - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system. - Verify that the new shimx64.efi file is under /boot/efi/EFI/ubuntu, along with mmx64.efi and fbx64.efi. - Verify that /boot/efi/EFI/ubuntu/MokManager.efi no longer exists. - Verify that trying to apt install grub alone, or apt install shim alone, pulls in the correct matching versions of packages and gives the same results. 2) Booting normally - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system, with Secure Boot enabled. - Verify it boots successfully to the login prompt. - There should be no messages about "Verification failure" or other errors before the kernel is loaded. 3) Network boot. - Update to shim signed and grub2 signed EFI binaries on the TFTP server used. - Verify that a network booting system still boots normally through shim and grub, reaching a login prompt. 4) BootEntry options - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system. - Update or install fwupdate. - Verify that new updates can be applied via fwupdate, that when an update is available, fwupdate will correctly start, apply the update, and reboot to shim normally, leading to a working system. 5) live builds - confirm that the new version of livecd-rootfs has been published to -updates first, and that a daily build of the UEFI-enabled cloud images succeeds with the new shim filenames. [Regression Potential] Any failure to load the kernel from grub, or for shim to load grub, or for the system firmware to load shim (such as "Verification failure" messages) or failure to retrieve or parse BootEntry extended options (such as necessary to load MokManager or fwupdate) should be considered regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1637290/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft
** Changed in: shim (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1637290 Title: Update to the signed 0.9+1474479173.6c180c6-1ubuntu1 shim binary from Microsoft Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in shim package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in grub2 source package in Precise: Won't Fix Status in grub2-signed source package in Precise: Won't Fix Status in livecd-rootfs source package in Precise: Invalid Status in shim source package in Precise: Won't Fix Status in shim-signed source package in Precise: Won't Fix Status in grub2 source package in Trusty: Fix Released Status in grub2-signed source package in Trusty: Fix Released Status in livecd-rootfs source package in Trusty: Fix Released Status in shim source package in Trusty: In Progress Status in shim-signed source package in Trusty: In Progress Status in grub2 source package in Xenial: Fix Released Status in grub2-signed source package in Xenial: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in shim source package in Xenial: Fix Released Status in shim-signed source package in Xenial: Fix Released Status in grub2 source package in Yakkety: Fix Released Status in grub2-signed source package in Yakkety: Fix Released Status in livecd-rootfs source package in Yakkety: Fix Released Status in shim source package in Yakkety: Won't Fix Status in shim-signed source package in Yakkety: Fix Released Bug description: [Impact] We might want to boot securely one of these days. [Test case] 1) Upgrading - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system. - Verify that the new shimx64.efi file is under /boot/efi/EFI/ubuntu, along with mmx64.efi and fbx64.efi. - Verify that /boot/efi/EFI/ubuntu/MokManager.efi no longer exists. - Verify that trying to apt install grub alone, or apt install shim alone, pulls in the correct matching versions of packages and gives the same results. 2) Booting normally - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system, with Secure Boot enabled. - Verify it boots successfully to the login prompt. - There should be no messages about "Verification failure" or other errors before the kernel is loaded. 3) Network boot. - Update to shim signed and grub2 signed EFI binaries on the TFTP server used. - Verify that a network booting system still boots normally through shim and grub, reaching a login prompt. 4) BootEntry options - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system. - Update or install fwupdate. - Verify that new updates can be applied via fwupdate, that when an update is available, fwupdate will correctly start, apply the update, and reboot to shim normally, leading to a working system. 5) live builds - confirm that the new version of livecd-rootfs has been published to -updates first, and that a daily build of the UEFI-enabled cloud images succeeds with the new shim filenames. [Regression Potential] Any failure to load the kernel from grub, or for shim to load grub, or for the system firmware to load shim (such as "Verification failure" messages) or failure to retrieve or parse BootEntry extended options (such as necessary to load MokManager or fwupdate) should be considered regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1637290/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1714267] Re: segfault on bad usage of generator
** Changed in: nplan (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1714267 Title: segfault on bad usage of generator Status in nplan package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Released Bug description: [Impact] netplan's systemd-generator segfaults if called with no arguements. it should better show usage or something else and exit non-zero. [Test case] # /lib/systemd/system-generators/netplan The above command should not crash, but respond with a suitable error message. Without the update, it behaves like this: """ (netplan:842): GLib-CRITICAL **: g_strv_length: assertion 'str_array != NULL' failed ** ERROR:src/generate.c:86:main: assertion failed: (g_strv_length(files) == 3) Aborted (core dumped) """ [Regression Potential] This is a command not meant to be used directly; but spurious crashes or misbehavior of netplan at boot time, such as failing to generate networkd/NM config for a netplan yaml configuration that is valid, would consistute a potential regression of this update. --- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nplan 0.26 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Thu Aug 31 14:24:24 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: nplan UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1714267/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1630285] Re: mwifiex_pcie crashes after several bind/unbind
** Changed in: nplan (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1630285 Title: mwifiex_pcie crashes after several bind/unbind Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in nplan package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in nplan source package in Xenial: Fix Released Status in linux source package in Yakkety: Won't Fix Status in nplan source package in Yakkety: Fix Released Bug description: [Impact] netplan-configured systems with mwifiex interfaces crash if netplan attempts to unbind/bind the interface. [Test case] 1) Run 'netplan apply' on a system with mwifiex_pci driver. The system should not crash, and the mwifiex interface should remain untouched. [Regression potential] Interfaces other than those affected by unbind/bind crashes or failures should still be unbound when 'netplan apply' is run. This affects most wireless interfaces, with the notable exception of mwifiex and brcmfmac. Failure to apply netplan configuration for a legitimate mwifiex device (wireless connection driven by NetworkManager renderer using netplan) would also constitute a regression. [Original bug report] # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bind Keep doing the bind/unbind actions, it would crash very soon. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1630285/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1744968] Re: [SRU] Juju 2.3.2
Netplan SRU backport with these changes has already happened and the juju updates are now done via snaps AFAIK. Closing as Fix Released (Xenial has at least juju 2.3.7 in archive). ** Changed in: nplan (Ubuntu Xenial) Status: In Progress => Fix Released ** Changed in: nplan (Ubuntu Artful) Status: In Progress => Fix Released ** Changed in: nplan (Ubuntu Artful) Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned) ** Changed in: nplan (Ubuntu Xenial) Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned) ** Changed in: nplan (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1744968 Title: [SRU] Juju 2.3.2 Status in juju-core package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in juju-core source package in Xenial: Fix Released Status in nplan source package in Xenial: Fix Released Status in juju-core source package in Artful: Invalid Status in nplan source package in Artful: Fix Released Bug description: This syncs juju with the upstream release bringing the latest bugfixes and enhancements. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] A full list of targeted bugs can be seen against the milestone, and the intervening milestones: https://launchpad.net/juju/+milestone/2.3.2 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here: http://qa.jujucharms.com/releases/6159 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1744968/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829203] Re: linux-fips: 4.4.0-1011.14 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829209 - phase: Ready for Packaging - phase-changed: Wednesday, 15. May 2019 14:04 UTC + phase: Packaging + phase-changed: Thursday, 16. May 2019 19:06 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829203 Title: linux-fips: 4.4.0-1011.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829209 phase: Packaging phase-changed: Thursday, 16. May 2019 19:06 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829203/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829245] Re: Networking issues after upgrade to 1:2.5+dfsg-5ubuntu10.37
** No longer affects: cloud-archive -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829245 Title: Networking issues after upgrade to 1:2.5+dfsg-5ubuntu10.37 Status in qemu package in Ubuntu: Invalid Status in qemu source package in Xenial: Fix Released Bug description: Since yesterdays upgrade to qemu packages version 1:2.5+dfsg- 5ubuntu10.37, new VMs have networking issues. Their network interfaces stop working after a short time, are not even able to PXE boot but when, they will LOSE connectivity after a few seconds (longest was around a minute). Downgrading to 1:2.5+dfsg-5ubuntu10.36 fixed the issue again. Unfortunately there are no error messages thrown. This is all I can provide: 2019-05-15 12:40:14.103+: starting up libvirt version: 1.3.1, package: 1ubuntu10.25 (Marc Deslauriers Wed, 13 Mar 2019 08:10:12 -0400), qemu version: 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.37), hostname: vh-4..XXX.net LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name one-1110 -S -machine pc-i440fx-xenial,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid d006f44c-bb54-410b-ba94-15a46d0cfd46 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-one-1110/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/one//datastores/101/1110/disk.0,format=raw,if=none,id=drive-virtio-disk0,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/var/lib/one//datastores/101/1110/disk.1,format=raw,if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=44,id=hostnet0,vhost=on,vhostfd=55 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=02:00:3d:86:51:7b,bus=pci.0,addr=0x3,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 0.0.0.0:1110,password -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on Domain id=63 is tainted: host-cpu char device redirected to /dev/pts/18 (label charserial0) 2019-05-15T13:44:09.552393Z qemu-system-x86_64: terminating on signal 15 from pid 50288 2019-05-15 13:44:09.753+: shutting down 2019-05-15 13:44:27.508+: starting up libvirt version: 1.3.1, package: 1ubuntu10.25 (Marc Deslauriers Wed, 13 Mar 2019 08:10:12 -0400), qemu version: 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.36), hostname: vh-4..XXX.net LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name one-1110 -S -machine pc-i440fx-xenial,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 414fcc19-2440-4ff1-9c29-50f2770c94f1 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-one-1110/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/one//datastores/101/1110/disk.0,format=raw,if=none,id=drive-virtio-disk0,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/var/lib/one//datastores/101/1110/disk.1,format=raw,if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=44,id=hostnet0,vhost=on,vhostfd=53 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=02:00:3d:86:51:7b,bus=pci.0,addr=0x3,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 0.0.0.0:1110,password -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on Domain id=66 is tainted: host-cpu char device redirected to /dev/pts/18 (label charserial0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1829245/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1828288] Re: QEMU might fail to start on AMD CPUs when 'host-passthrough' is used
** Also affects: qemu (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1828288 Title: QEMU might fail to start on AMD CPUs when 'host-passthrough' is used Status in qemu package in Ubuntu: In Progress Status in qemu source package in Xenial: New Bug description: [Impact] * QEMU does not work in some AMD hardware when using host-passthrough as cpu-mode (usually to allow nested KVM to work). [Test Case] * to use Xenial qemu (1:2.5+dfsg-5ubuntu10.36 ou 1:2.5+dfsg-5ubuntu10.37) * to use the following XML file: https://paste.ubuntu.com/p/BSyFY7ksR5/ * to have AMD FX(tm)-8350 Eight-Core Processor CPU or similar [Regression Potential] * initial qemu code could be affected, disallowing other guests, in other architectures, to be started * suggested patch is simple, being a positional change only * patch is upstream based and identifies the issue and is reported to be a fix for the described issue [Other Info] * INITIAL CASE DESCRIPTION: When using latest QEMU (-proposed) in Xenial you might encounter the following problem when trying to initialize your guests: (c)inaddy@qemubug:~$ apt-cache policy qemu-system-x86 qemu-system-x86: Installed: 1:2.5+dfsg-5ubuntu10.37 Candidate: 1:2.5+dfsg-5ubuntu10.37 Version table: *** 1:2.5+dfsg-5ubuntu10.37 500 500 http://ubuntu.c3sl.ufpr.br//ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:2.5+dfsg-5ubuntu10.36 500 500 http://ubuntu.c3sl.ufpr.br//ubuntu xenial-updates/main amd64 Packages 1:2.5+dfsg-5ubuntu10 500 500 http://ubuntu.c3sl.ufpr.br/ubuntu xenial/main amd64 Packages (c)inaddy@qemubug:~$ virsh list --all IdName State - kdebianshut off - kguest shut off (c)inaddy@qemubug:~$ virsh start --console kguest error: Failed to start domain kguest error: internal error: process exited while connecting to monitor: warning: host doesn't support requested feature: CPUID.8001H:EDX [bit 0] warning: host doesn't support requested feature: CPUID.8001H:EDX [bit 1] warning: host doesn't support requested feature: CPUID.8001H:EDX [bit 2] warning: host doesn't support requested feature: CPUID.8001H:EDX [bit 3] warning: host doesn't support requested feature: CPUID.8001H:EDX [bit 4] warning: host doesn't support requested feature: CPUID.8001H:EDX [bit 5] warning: host doesn't support requested feature: CPUID.8001H:EDX [bit 6] warning: host doesn't support requested feature: CPUID.8001H:EDX [bit 7] warning: host doesn't support requested feature: CPUID.8001H:EDX [bit 8] warning: host doesn't support requested feature: CPUID.8001H:EDX [bit 9] warning: host doesn't support requested feature: CPUID.8001H:EDX [bit 12] warning: host doesn't support requested feature: CPUID.8001H:EDX [bit 13] warning: host doesn't support requested feature: CPU This happens because x86_cpu_get_migratable_flags() does not support CPUID_EXT2_AMD_ALIASES. After cherry-picking upstream patch 9997cf7bdac056aeed246613639675c5a9f8fdc2, that moves CPUID_EXT2_AMD_ALIASES code to after x86_cpu_filter_features(), the problem is fixed. Other QEMU versions are properly fixed and don't face this issue. Cherry-picking commit and re-building the package makes it to work: (c)inaddy@qemubug:~$ virsh start --console kguest Domain kguest started Connected to domain kguest Escape character is ^] [0.00] Linux version 4.19.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15) [0.00] Command line: root=/dev/vda noresume console=tty0 console=ttyS0,38400n8 apparmor=0 net.ifnames=0 crashkernel=256M [0.00] random: get_random_u32 called from bsp_init_amd+0x20b/0x2b0 with crng_init=0 [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1828288/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe
[Group.of.nepali.translators] [Bug 1812123] Re: Upstream Commits Needed for DPDK on Azure
** Also affects: linux-azure (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1812123
Title:
Upstream Commits Needed for DPDK on Azure
Status in linux-azure package in Ubuntu:
Confirmed
Status in linux-azure source package in Xenial:
New
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Bug description:
The following two patches are related to multi-queue. They are needed
in the linux-azure kernels for DPDK to work properly on Azure.
b5679cebf780 ("vmbus: fix subchannel removal")
5e3c420dcca5 ("uio_hv_generic: set callbacks on open")
Both commits have also been cc'd to upstream stable. Commit 5e3c420dcca5 is
in mainline as of v4.20. Commit b5679cebf780 is still in linux-next.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1812123/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829245] Re: Networking issues after upgrade to 1:2.5+dfsg-5ubuntu10.37
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.39 --- qemu (1:2.5+dfsg-5ubuntu10.39) xenial-security; urgency=medium * Disable patches from 1:2.5+dfsg-5ubuntu10.37 to prevent regression (LP: #1829245) - d/p/lp1823458/add-VirtIONet-vhost_stopped-flag-to-prevent-multiple.patch - d/p/lp1823458/do-not-call-vhost_net_cleanup-on-running-net-from-ch.patch -- Marc Deslauriers Thu, 16 May 2019 07:11:54 -0400 ** Changed in: qemu (Ubuntu Xenial) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829245 Title: Networking issues after upgrade to 1:2.5+dfsg-5ubuntu10.37 Status in Ubuntu Cloud Archive: New Status in qemu package in Ubuntu: Invalid Status in qemu source package in Xenial: Fix Released Bug description: Since yesterdays upgrade to qemu packages version 1:2.5+dfsg- 5ubuntu10.37, new VMs have networking issues. Their network interfaces stop working after a short time, are not even able to PXE boot but when, they will LOSE connectivity after a few seconds (longest was around a minute). Downgrading to 1:2.5+dfsg-5ubuntu10.36 fixed the issue again. Unfortunately there are no error messages thrown. This is all I can provide: 2019-05-15 12:40:14.103+: starting up libvirt version: 1.3.1, package: 1ubuntu10.25 (Marc Deslauriers Wed, 13 Mar 2019 08:10:12 -0400), qemu version: 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.37), hostname: vh-4..XXX.net LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name one-1110 -S -machine pc-i440fx-xenial,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid d006f44c-bb54-410b-ba94-15a46d0cfd46 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-one-1110/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/one//datastores/101/1110/disk.0,format=raw,if=none,id=drive-virtio-disk0,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/var/lib/one//datastores/101/1110/disk.1,format=raw,if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=44,id=hostnet0,vhost=on,vhostfd=55 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=02:00:3d:86:51:7b,bus=pci.0,addr=0x3,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 0.0.0.0:1110,password -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on Domain id=63 is tainted: host-cpu char device redirected to /dev/pts/18 (label charserial0) 2019-05-15T13:44:09.552393Z qemu-system-x86_64: terminating on signal 15 from pid 50288 2019-05-15 13:44:09.753+: shutting down 2019-05-15 13:44:27.508+: starting up libvirt version: 1.3.1, package: 1ubuntu10.25 (Marc Deslauriers Wed, 13 Mar 2019 08:10:12 -0400), qemu version: 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.36), hostname: vh-4..XXX.net LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name one-1110 -S -machine pc-i440fx-xenial,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 414fcc19-2440-4ff1-9c29-50f2770c94f1 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-one-1110/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/one//datastores/101/1110/disk.0,format=raw,if=none,id=drive-virtio-disk0,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/var/lib/one//datastores/101/1110/disk.1,format=raw,if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=44,id=hostnet0,vhost=on,vhostfd=53 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=02:00:3d:86:51:7b,bus=pci.0,addr=0x3,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 0.0.0.0:1110,password -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on Domain id=66 is tainted: host-cpu char device redirected to /dev/pts/18 (label charserial0) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1829245/+subscriptions
[Group.of.nepali.translators] [Bug 1829195] Re: linux-kvm: 4.4.0-1047.53 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1829209 - phase: Packaging - phase-changed: Thursday, 16. May 2019 07:34 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 16. May 2019 15:06 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829195 Title: linux-kvm: 4.4.0-1047.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829209 phase: Ready for Promote to Proposed phase-changed: Thursday, 16. May 2019 15:06 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829195/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829209] Re: linux: 4.4.0-149.175 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1829207 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true - phase: Promote to Proposed - phase-changed: Thursday, 16. May 2019 09:31 UTC + bugs-spammed: true + phase: Testing + phase-changed: Thursday, 16. May 2019 13:02 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): arch=amd64:channel=latest/beta + arch=i386:channel=latest/beta' + snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): arch=amd64:channel=latest/edge + arch=i386:channel=latest/edge' + verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829209 Title: linux: 4.4.0-149.175 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829205 (trusty/linux-aws), bug 1829207 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 16. May 2019 13:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): arch=amd64:channel=latest/beta arch=i386:channel=latest/beta' snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): arch=amd64:channel=latest/edge
[Group.of.nepali.translators] [Bug 1829380] [NEW] race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu (fix regression)
Public bug reported: [impact] this bug is to track re-uploading the fix for bug 1823458 plus a patch to fix a regression it introduced. instead of copying the details from bug 1823458, please see that bug for impact and testcase. [test case] see bug 1823458 [regression potential] see bug 1823458 additionally, the regression from the last fix is in bug 1829245. the change is in code where this still has the regression potential of causing guest networking to fail. ** Affects: cloud-archive Importance: Undecided Status: New ** Affects: qemu (Ubuntu) Importance: Undecided Status: Invalid ** Affects: qemu (Ubuntu Xenial) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: qemu (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: qemu (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: qemu (Ubuntu Xenial) Status: New => In Progress ** Changed in: qemu (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829380 Title: race condition between vhost_net_stop and CHR_EVENT_CLOSED on shutdown crashes qemu (fix regression) Status in Ubuntu Cloud Archive: New Status in qemu package in Ubuntu: Invalid Status in qemu source package in Xenial: In Progress Bug description: [impact] this bug is to track re-uploading the fix for bug 1823458 plus a patch to fix a regression it introduced. instead of copying the details from bug 1823458, please see that bug for impact and testcase. [test case] see bug 1823458 [regression potential] see bug 1823458 additionally, the regression from the last fix is in bug 1829245. the change is in code where this still has the regression potential of causing guest networking to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1829380/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1801878] Re: NULL pointer dereference at 0000000000000020 when access dst_orig->ops->family in function xfrm_lookup_with_ifid()
Patch 9e143793 has landed in D/E as well, mark this bug as fix-released.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1801878
Title:
NULL pointer dereference at 0020 when access
dst_orig->ops->family in function xfrm_lookup_with_ifid()
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
[Impact]
NULL pointer access happens when trying to access dst_orig->ops.
The function xfrm_lookup() calls xfrm_lookup_with_ifid() and there is
a line inside trying to access dst_orig->ops and it's exactly where the
panicing happens:
u16 family = dst_orig->ops->family;
As you can see that the symbol offset of ops is about 32(0x20) which
definitely is the error message shows in the kern.log:
[267265.140511] BUG: unable to handle kernel NULL pointer dereference
at 0020
struct dst_entry {
struct callback_head callback_head; /* 0 16 */
struct dst_entry * child; /* 16 8 */
struct net_device * dev; /* 24 8 */
struct dst_ops * ops; <-- /* 32 8 */
The oops:
BUG: unable to handle kernel NULL pointer dereference at 0020
IP: xfrm_lookup+0x31/0x870
PGD 0 P4D 0
Oops: [#1] SMP PTI
CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.15.0-36-generic
#39~16.04.1-Ubuntu
Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
RIP: 0010:xfrm_lookup+0x31/0x870
RSP: 0018:98b542343a48 EFLAGS: 00010246
RAX: RBX: 98b542343ac8 RCX:
RDX: 98b542343ac8 RSI: RDI: b39e4380
RBP: 98b542343ab8 R08: 0002 R09:
R10: 0020 R11: 7fb56465 R12:
R13: b39e4380 R14: 0002 R15: b39e4380
FS: () GS:98b54234() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 0020 CR3: 0004ed40a001 CR4: 001606e0
DR0: DR1: DR2:
DR3: DR6: fffe0ff0 DR7: 0400
Call Trace:
? __xfrm_policy_check+0x41d/0x630
__xfrm_route_forward+0xa3/0x110
ip_forward+0x38c/0x470
? ip_route_input_noref+0x28/0x40
ip_rcv_finish+0x124/0x410
ip_rcv+0x28e/0x3b0
? inet_del_offload+0x40/0x40
__netif_receive_skb_core+0x879/0xba0
? __skb_checksum+0x188/0x2c0
__netif_receive_skb+0x18/0x60
? __netif_receive_skb+0x18/0x60
netif_receive_skb_internal+0x37/0xe0
? tcp4_gro_complete+0x86/0x90
napi_gro_complete+0x73/0x90
dev_gro_receive+0x2ee/0x5c0
napi_gro_frags+0xa3/0x230
ena_clean_rx_irq+0x486/0x7c0 [ena]
ena_io_poll+0x41d/0x770 [ena]
net_rx_action+0x265/0x3b0
__do_softirq+0xf5/0x28f
irq_exit+0xb8/0xc0
xen_evtchn_do_upcall+0x30/0x40
xen_hvm_callback_vector+0x84/0x90
[Fix]
The patch tries to avoid the NULL pointer access before the line
mentioned "dst_orig->ops->family" in function __xfrm_route_forward.
And the function calling sequence is:
__xfrm_route_forward -> xfrm_lookup -> xfrm_lookup_with_ifid
It definitely avoids the NULL pointer access in the
xfrm_lookup_with_ifid.
commit c5e39ef174ad34cd4d26af3a83bdbccddd2ad9d6
Author: Steffen Klassert
Date: Tue Sep 11 10:31:15 2018 +0200
xfrm: Fix NULL pointer dereference when skb_dst_force clears the
dst_entry.
Since commit 222d7dbd258d ("net: prevent dst uses after free")
skb_dst_force() might clear the dst_entry attached to the skb.
The xfrm code don't expect this to happen, so we crash with
a NULL pointer dereference in this case. Fix it by checking
skb_dst(skb) for NULL after skb_dst_force() and drop the packet
in cast the dst_entry was cleared.
[Test]
The fix has been tested in the production system with the IPSec enabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801878/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829216] Re: linux-hwe: 4.15.0-51.55~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1829215 (linux-hwe-edge) -- swm properties -- kernel-stable-master-bug: 1829219 - phase: Packaging - phase-changed: Thursday, 16. May 2019 07:38 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 16. May 2019 11:07 UTC reason: - prepare-package: Pending -- package tag not yet published promote-to-proposed: Holding -- builds not complete in ppa -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829216 Title: linux-hwe: 4.15.0-51.55~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1829215 (linux-hwe-edge) -- swm properties -- kernel-stable-master-bug: 1829219 phase: Holding before Promote to Proposed phase-changed: Thursday, 16. May 2019 11:07 UTC reason: promote-to-proposed: Holding -- builds not complete in ppa To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829216/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829215] Re: linux-hwe-edge: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829216 - phase: Holding before Packaging - phase-changed: Wednesday, 15. May 2019 11:06 UTC + phase: Ready for Packaging + phase-changed: Thursday, 16. May 2019 11:08 UTC reason: - prepare-package: Stalled -- waiting for master bug - prepare-package-meta: Stalled -- waiting for master bug + prepare-package-meta: Pending -- version not specified -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829215 Title: linux-hwe-edge: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829216 phase: Ready for Packaging phase-changed: Thursday, 16. May 2019 11:08 UTC reason: prepare-package-meta: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829215/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829245] Re: Networking issues after upgrade to 1:2.5+dfsg-5ubuntu10.37
@sw0x2a thanks - my patch (that breaks things) will be reverted in a new release through the security pocket and i'll reapply the fixed version thru the normal sru process. ** Also affects: qemu (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Invalid ** Changed in: qemu (Ubuntu Xenial) Importance: Undecided => Critical -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829245 Title: Networking issues after upgrade to 1:2.5+dfsg-5ubuntu10.37 Status in Ubuntu Cloud Archive: New Status in qemu package in Ubuntu: Invalid Status in qemu source package in Xenial: New Bug description: Since yesterdays upgrade to qemu packages version 1:2.5+dfsg- 5ubuntu10.37, new VMs have networking issues. Their network interfaces stop working after a short time, are not even able to PXE boot but when, they will LOSE connectivity after a few seconds (longest was around a minute). Downgrading to 1:2.5+dfsg-5ubuntu10.36 fixed the issue again. Unfortunately there are no error messages thrown. This is all I can provide: 2019-05-15 12:40:14.103+: starting up libvirt version: 1.3.1, package: 1ubuntu10.25 (Marc Deslauriers Wed, 13 Mar 2019 08:10:12 -0400), qemu version: 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.37), hostname: vh-4..XXX.net LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name one-1110 -S -machine pc-i440fx-xenial,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid d006f44c-bb54-410b-ba94-15a46d0cfd46 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-one-1110/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/one//datastores/101/1110/disk.0,format=raw,if=none,id=drive-virtio-disk0,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/var/lib/one//datastores/101/1110/disk.1,format=raw,if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=44,id=hostnet0,vhost=on,vhostfd=55 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=02:00:3d:86:51:7b,bus=pci.0,addr=0x3,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 0.0.0.0:1110,password -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on Domain id=63 is tainted: host-cpu char device redirected to /dev/pts/18 (label charserial0) 2019-05-15T13:44:09.552393Z qemu-system-x86_64: terminating on signal 15 from pid 50288 2019-05-15 13:44:09.753+: shutting down 2019-05-15 13:44:27.508+: starting up libvirt version: 1.3.1, package: 1ubuntu10.25 (Marc Deslauriers Wed, 13 Mar 2019 08:10:12 -0400), qemu version: 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.36), hostname: vh-4..XXX.net LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name one-1110 -S -machine pc-i440fx-xenial,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 414fcc19-2440-4ff1-9c29-50f2770c94f1 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-one-1110/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/one//datastores/101/1110/disk.0,format=raw,if=none,id=drive-virtio-disk0,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/var/lib/one//datastores/101/1110/disk.1,format=raw,if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=44,id=hostnet0,vhost=on,vhostfd=53 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=02:00:3d:86:51:7b,bus=pci.0,addr=0x3,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 0.0.0.0:1110,password -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on Domain id=66 is tainted: host-cpu char device redirected to /dev/pts/18 (label charserial0) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1829245/+subscriptions ___ Mailing list:
[Group.of.nepali.translators] [Bug 1795407] Re: python-apt frontend locking
This bug was fixed in the package python-apt - 1.1.0~beta1ubuntu0.16.04.4 --- python-apt (1.1.0~beta1ubuntu0.16.04.4) xenial; urgency=medium * apt.Cache: Fix (un)locking of archives (Closes: #922416) (LP: #1826870) * apt.Cache: Use explicit, more safe locking in update() * Update mirror lists python-apt (1.1.0~beta1ubuntu0.16.04.3) xenial; urgency=medium * Frontend locking and related locking improvements (LP: #1795407) - apt.Cache: Keep / Re-establish the system lock in commit() - apt.Cache: Keep archive locked during commit()/ in fetch_archives() - apt.Cache: Reinstate locks in a finally / run dpkg inside try - Introduce frontend locking - Convert apt.Cache.commit and apt_pkg.DepCache.commit to FE lock * Other changes to make that work: - travis CI: enable PPA for new apt versions * As always, updated mirror lists -- Julian Andres Klode Mon, 29 Apr 2019 14:11:32 +0200 ** Changed in: python-apt (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Released Status in python-apt source package in Bionic: Fix Released Bug description: [Impact] Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: (1) The archives lock was only taken for a short time, when it should have been kept for the duration of an installation, as otherwise debs could disappear from archives/ while the install is running. (2) There was no lock handling at all. Tools essentially acquire the lock, and then release it before commit(). The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage both the frontend and the normal lock, and allows code to call apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() around dpkg invocations to release the inner lock. Cache.commit() takes care of locking itself now. It releases the inner lock as needed for dpkg invocations. It also now requires apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released 3. Observe that the archive lock is not released until the last dpkg run The locking behavior can be observed via strace. [Regression potential] The dpkg lock changed the most: Some lock counting might go wrong and programs might fail as a result. Any problems will be isolated, though - dpkg still acquires its locks, and if a lock miscount happens, apt would not tell dpkg to skip acquiring the frontend lock, so even if we were losing the lock anywhere, dpkg would still try to acquire it and not run unlocked. The archive lock done by commit()/fetch_archives() in apt.Cache() is now hold as long as the fetcher object exists though (as it uses the fetcher's get_lock method), which might cause unexpected behavior in apps not expecting that. The lists/ lock is unaffected by the changes, so there should not be any regressions when it comes to updating index files. [Other info (1)] CI changes: There were some improvements to type hints for mypy needed to make type checks pass, and changes to the CI's Dockerfile to pull a new apt from the apt stable PPA (as a new enough apt is only in unapproved atm). Neither of those files are used anywhere outside of the package, so they should not cause any problems. [Other info (2)] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html - This SRU depends on the apt SRU above, and breaks unattended- upgrades in bionic without its SRU due to a bug in the u-u code in handling the new API. - xenial depends on unattended-upgrades SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1822270] Re: Debconf readline frontend does not show options
This bug was fixed in the package debconf - 1.5.58ubuntu2 --- debconf (1.5.58ubuntu2) xenial; urgency=medium * Fix readline prompts when run via run-parts (LP: #1822270) - Debconf/FrontEnd/Readline.pm: force output to stdout if both stdout and stderr are pipes -- Heitor Alves de Siqueira Mon, 06 May 2019 13:31:57 -0300 ** Changed in: debconf (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: Fix Released Status in debconf source package in Xenial: Fix Released Status in debconf source package in Bionic: Fix Released Status in debconf source package in Cosmic: Fix Released Status in debconf source package in Disco: Fix Released Status in debconf source package in Eoan: Fix Released Status in debconf package in Debian: Fix Released Bug description: [Impact] debconf prompts the user for input before displaying options [Description] When upgrading packages with apt or dpkg, debconf scripts are ran through 'run-parts' with the '--report' flag. This causes script output to be handled through pipes set up by run-parts, and buffers output from maintainer scripts nicely for formatting. If debconf makes use of the readline frontend, any prompts will bypass the run-parts buffers and be displayed directly to /dev/tty. This generally causes the prompt to be displayed before the user gets any of the available options for it, and printing will block until the user inputs a valid option. Upstream commit: https://salsa.debian.org/pkg- debconf/debconf/commit/48c5ce38cfd5 [Test Case] 1) Deploy a VM through e.g. uvt-kvm $ uvt-kvm create disco release=disco 2) Remove the whiptail package to force the readline frontend in debconf root@disco:~# apt remove --purge whiptail -y 3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade through run-parts root@disco:~# apt update && apt install -y grub-legacy-ec2 root@disco:~# rm -f /boot/grub/menu.lst* root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst 4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we just need it to think menu.lst needs an upgrade) root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report ... /etc/kernel/postinst.d/x-grub-legacy-ec2: debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... What would you like to do about menu.lst? The "What would you like to do about menu.lst?" prompt will block until the user enter a valid option, even though it's being displayed before the available options. [Regression Potential] We could hit regressions if changing debconf's printing to /dev/tty is expected by other programs. The changes are needed only in the readline frontend, so that would minimize impact of any possible regressions. The fixes will be thoroughly tested with autopkgtest and use-case scenarios. # # # # [Original Description] When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1825099] Re: Unable to deploy Xenial on a s390x KVM
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1825099 Title: Unable to deploy Xenial on a s390x KVM Status in ubuntu-kernel-tests: In Progress Status in Ubuntu on IBM z Systems: Fix Released Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: Fix Released Bug description: [Impact] * chreipl is a tool that can set/change the IPL settings of a guest, meaning what should it boot next upon a reboot call (ie. which device to boot from, or to like dumpkernel, etc). v1.34 has a processing bug, meaning that chreipl does not work with virtio disk drives, as seen in VMs. The fix is to cherrypick a patch which was most likely introduced in teh v1.35 release. Please note the v1.XX series upstream code base is not public, so the patch i'm cherrypicking is a hunk from the diff between xenial and yakkety releases. [Test Case] * Use chreipl in a qemu-kvm VM, it should work. [Regression Potential] * This changes the codepath, of detecting which drive to use. Other usage by user specified id are not affected, and default usage of chreipl in xenial so far has been on best effort basis (ie. guarded with || true, in d-i) because normally it is trivial to control IPL methods from the underlying hypervisor (HMC, z/VM, qemu/libvirt) * However, this patch is needed to enable MAAS KVM pods to be able to deploy Xenial guests, as that deployment mechanism depends on working chreipl. [Other Info] * Original bug report: When trying to deploy Xenial on a s390x KVM, the deployment will fail. (it works for B/C) Looks like it will fail with: chreipl: Could not find DASD CCW device "virtio0" curtin: Installation failed with exception: Unexpected error while running command. Command: chreipl node /dev/vda Exit code: 1 Reason: - Stdout: chreipl: Could not find DASD CCW device "virtio0" Complete output from the MaaS UI: curtin: Installation started. (18.1-59-g0f993084-0ubuntu1~18.04.1) third party drivers not installed or necessary. Hit:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease Get:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease [109 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease [109 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease [107 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports xenial/universe s390x Packages [7190 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports xenial/multiverse s390x Packages [119 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main s390x Packages [672 kB] Get:8 http://ports.ubuntu.com/ubuntu-ports xenial-updates/universe s390x Packages [613 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports xenial-updates/multiverse s390x Packages [11.0 kB] Get:10 http://ports.ubuntu.com/ubuntu-ports xenial-security/main s390x Packages [432 kB] Get:11 http://ports.ubuntu.com/ubuntu-ports xenial-security/universe s390x Packages [340 kB] Get:12 http://ports.ubuntu.com/ubuntu-ports xenial-security/multiverse s390x Packages [1716 B] Get:13 http://ports.ubuntu.com/ubuntu-ports xenial-backports/main s390x Packages [7280 B] Get:14 http://ports.ubuntu.com/ubuntu-ports xenial-backports/universe s390x Packages [6536 B] Fetched 9719 kB in 2s (4674 kB/s) Reading package lists... zfs-dkms set on hold. Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: crda iw libnl-3-200 libnl-genl-3-200 linux-firmware linux-headers-4.4.0-145 linux-headers-4.4.0-145-generic linux-headers-generic linux-image-4.4.0-145-generic linux-image-generic linux-modules-4.4.0-145-generic linux-modules-extra-4.4.0-145-generic wireless-regdb Suggested packages: fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools The following NEW packages will be installed: crda iw libnl-3-200 libnl-genl-3-200 linux-firmware linux-generic linux-headers-4.4.0-145 linux-headers-4.4.0-145-generic linux-headers-generic linux-image-4.4.0-145-generic linux-image-generic linux-modules-4.4.0-145-generic linux-modules-extra-4.4.0-145-generic wireless-regdb 0 upgraded, 14 newly installed, 0 to remove and 8 not upgraded. Need to get 74.5 MB of archives. After this operation, 375 MB of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main s390x libnl-3-200 s390x 3.2.27-1ubuntu0.16.04.1 [49.7 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main s390x libnl-genl-3-200 s390x 3.2.27-1ubuntu0.16.04.1 [11.0 kB] Get:3
[Group.of.nepali.translators] [Bug 1825099] Re: Unable to deploy Xenial on a s390x KVM
This bug was fixed in the package s390-tools - 1.34.0-0ubuntu8.10 --- s390-tools (1.34.0-0ubuntu8.10) xenial; urgency=medium * chreipl: fix chreipl node for virtio devices LP: #1825099 -- Dimitri John Ledkov Fri, 26 Apr 2019 01:10:10 +0100 ** Changed in: s390-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1825099 Title: Unable to deploy Xenial on a s390x KVM Status in ubuntu-kernel-tests: In Progress Status in Ubuntu on IBM z Systems: Fix Released Status in s390-tools package in Ubuntu: Fix Released Status in s390-tools source package in Xenial: Fix Released Bug description: [Impact] * chreipl is a tool that can set/change the IPL settings of a guest, meaning what should it boot next upon a reboot call (ie. which device to boot from, or to like dumpkernel, etc). v1.34 has a processing bug, meaning that chreipl does not work with virtio disk drives, as seen in VMs. The fix is to cherrypick a patch which was most likely introduced in teh v1.35 release. Please note the v1.XX series upstream code base is not public, so the patch i'm cherrypicking is a hunk from the diff between xenial and yakkety releases. [Test Case] * Use chreipl in a qemu-kvm VM, it should work. [Regression Potential] * This changes the codepath, of detecting which drive to use. Other usage by user specified id are not affected, and default usage of chreipl in xenial so far has been on best effort basis (ie. guarded with || true, in d-i) because normally it is trivial to control IPL methods from the underlying hypervisor (HMC, z/VM, qemu/libvirt) * However, this patch is needed to enable MAAS KVM pods to be able to deploy Xenial guests, as that deployment mechanism depends on working chreipl. [Other Info] * Original bug report: When trying to deploy Xenial on a s390x KVM, the deployment will fail. (it works for B/C) Looks like it will fail with: chreipl: Could not find DASD CCW device "virtio0" curtin: Installation failed with exception: Unexpected error while running command. Command: chreipl node /dev/vda Exit code: 1 Reason: - Stdout: chreipl: Could not find DASD CCW device "virtio0" Complete output from the MaaS UI: curtin: Installation started. (18.1-59-g0f993084-0ubuntu1~18.04.1) third party drivers not installed or necessary. Hit:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease Get:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease [109 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease [109 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease [107 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports xenial/universe s390x Packages [7190 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports xenial/multiverse s390x Packages [119 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main s390x Packages [672 kB] Get:8 http://ports.ubuntu.com/ubuntu-ports xenial-updates/universe s390x Packages [613 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports xenial-updates/multiverse s390x Packages [11.0 kB] Get:10 http://ports.ubuntu.com/ubuntu-ports xenial-security/main s390x Packages [432 kB] Get:11 http://ports.ubuntu.com/ubuntu-ports xenial-security/universe s390x Packages [340 kB] Get:12 http://ports.ubuntu.com/ubuntu-ports xenial-security/multiverse s390x Packages [1716 B] Get:13 http://ports.ubuntu.com/ubuntu-ports xenial-backports/main s390x Packages [7280 B] Get:14 http://ports.ubuntu.com/ubuntu-ports xenial-backports/universe s390x Packages [6536 B] Fetched 9719 kB in 2s (4674 kB/s) Reading package lists... zfs-dkms set on hold. Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: crda iw libnl-3-200 libnl-genl-3-200 linux-firmware linux-headers-4.4.0-145 linux-headers-4.4.0-145-generic linux-headers-generic linux-image-4.4.0-145-generic linux-image-generic linux-modules-4.4.0-145-generic linux-modules-extra-4.4.0-145-generic wireless-regdb Suggested packages: fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools The following NEW packages will be installed: crda iw libnl-3-200 libnl-genl-3-200 linux-firmware linux-generic linux-headers-4.4.0-145 linux-headers-4.4.0-145-generic linux-headers-generic linux-image-4.4.0-145-generic linux-image-generic linux-modules-4.4.0-145-generic linux-modules-extra-4.4.0-145-generic wireless-regdb 0 upgraded, 14 newly installed, 0 to remove and 8 not upgraded. Need to get 74.5 MB of archives. After this operation, 375 MB of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main s390x
[Group.of.nepali.translators] [Bug 1826870] Re: cache.commit() doesn't release the archives lock
This bug was fixed in the package python-apt - 1.1.0~beta1ubuntu0.16.04.4 --- python-apt (1.1.0~beta1ubuntu0.16.04.4) xenial; urgency=medium * apt.Cache: Fix (un)locking of archives (Closes: #922416) (LP: #1826870) * apt.Cache: Use explicit, more safe locking in update() * Update mirror lists python-apt (1.1.0~beta1ubuntu0.16.04.3) xenial; urgency=medium * Frontend locking and related locking improvements (LP: #1795407) - apt.Cache: Keep / Re-establish the system lock in commit() - apt.Cache: Keep archive locked during commit()/ in fetch_archives() - apt.Cache: Reinstate locks in a finally / run dpkg inside try - Introduce frontend locking - Convert apt.Cache.commit and apt_pkg.DepCache.commit to FE lock * Other changes to make that work: - travis CI: enable PPA for new apt versions * As always, updated mirror lists -- Julian Andres Klode Mon, 29 Apr 2019 14:11:32 +0200 ** Changed in: python-apt (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1826870 Title: cache.commit() doesn't release the archives lock Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Released Status in python-apt source package in Bionic: Fix Released Status in python-apt source package in Cosmic: Fix Released Status in python-apt package in Debian: Fix Released Bug description: [Impact] cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826870/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash
This bug was fixed in the package bash - 4.3-14ubuntu1.3 --- bash (4.3-14ubuntu1.3) xenial; urgency=medium * Resurrect "Set the default path to comply with Debian policy" in deb-bash-config.diff which went missing since 4.2+dfsg-1 or so. LP: #1792004 LP: #1614080 Closes: #781367 * Add autopkgtest for the built-in path. -- Dimitri John Ledkov Fri, 03 May 2019 14:57:15 +0100 ** Changed in: bash (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash Status in bash package in Ubuntu: Fix Released Status in bash source package in Precise: Fix Released Status in bash source package in Trusty: Won't Fix Status in bash source package in Xenial: Fix Released Status in bash source package in Bionic: Fix Released Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: Fix Released Status in bash source package in Eoan: Fix Released Status in bash package in Debian: New Bug description: [Impact] * The fallback path built into bash contains '.' which leads to unexpected addition of the current working directory. It should not be there, just like it isnt' in pre-precise and cosmic+. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' Should not have '.' as any component. Nor should there be any empty components, i.e. '::'. [Regression Potential] * Normally PATH is always set by either init, systemd, or any other hypervisor. Thus this only affects executions under bash, when it was started without any environment - e.g. booting with 'init=/bin/bash'. [Other Info] * Original bug report. On ubuntu 16.04 (but also 14.04), running bash with PATH unset always adds '.' to PATH: philippe@pv-desktop:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games philippe@pv-desktop:~$ unset PATH philippe@pv-desktop:~$ /bin/bash philippe@pv-desktop:~$ echo $PATH /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. Even when testing in a virtual machine / docker, and erasing /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem still happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1616123] Re: rpc-svcgssd.service uses incorrrect variable SVCGSSDARGS
This bug was fixed in the package nfs-utils - 1:1.2.8-9ubuntu12.2 --- nfs-utils (1:1.2.8-9ubuntu12.2) xenial; urgency=medium * d/nfs-utils_env.sh: alongside RPCSVCGSSDARGS, also export SVCGSSDARGS, which is the variable name expected by the rpc-svcgssd systemd service. (LP: #1616123) -- Andreas Hasenack Thu, 25 Apr 2019 17:23:49 -0300 ** Changed in: nfs-utils (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1616123 Title: rpc-svcgssd.service uses incorrrect variable SVCGSSDARGS Status in nfs-utils package in Ubuntu: Fix Released Status in nfs-utils source package in Xenial: Fix Released Status in nfs-utils source package in Bionic: Fix Released Status in nfs-utils source package in Cosmic: Fix Released Status in nfs-utils package in Debian: Fix Committed Bug description: [Impact] Command line options set for rpc.svcgssd in the /etc/default/nfs-kernel-server file are not passed on to the service, being ignored. [Test Case] * In a VM (LXD won't work), install nfs-server and a kerberos server. Use "EXAMPLE.LOCAL" for the realm, and "localhost" for the servers, when prompted: sudo apt install nfs-server krb5-kdc krb5-user krb5-admin-server * create the EXAMPLE.LOCAL realm. Use any password you want for the database master key, it won't be requested again: sudo krb5_newrealm * create a principal for the nfs service: sudo kadmin.local -q "addprinc -randkey nfs/$(hostname -f)" * extract the key into the system wide keytab: sudo kadmin.local -q "ktadd -k /etc/krb5.keytab nfs/$(hostname -f)" * edit /etc/default/nfs-common and enable gssd: NEED_GSSD=y * edit /etc/default/nfs-kernel-server and add an option to RPCSVCGSSDOPTS: RPCSVCGSSDOPTS="-v" * restart nfs-server sudo systemctl restart nfs-server * on xenial, you also have to restart nfs-config: sudo systemctl restart nfs-config * verify if /run/sysconfig/nfs-utils has the option we added above: $ cat /run/sysconfig/nfs-utils PIPEFS_MOUNTPOINT=/run/rpc_pipefs RPCNFSDARGS=" 8" RPCMOUNTDARGS="--manage-gids" STATDARGS="" RPCSVCGSSDARGS="-v" * Verify the running rpc.gssd process. Without the fix, it won't have the "-v" option: ps axw|grep svcgssd|grep -v grep 4285 ? Ss 0:00 /usr/sbin/rpc.svcgssd With the fix, right after installing the udpated packages, the option we added to /etc/default/nfs-kernel-server will show up: ps axw|grep svcgssd|grep -v grep 5656 ? Ss 0:00 /usr/sbin/rpc.svcgssd -v [Regression Potential] This is an old bug and whoever was affected by it probably worked around the problem by now. I tried to cope with one such scenario by not just renaming the variable we export, but exporting the correct one in addition to the old incorrect one, but that's it. I hope this, and the explanation added to the shell script wrapper nfs-utils.sh, is enough to help people with corner cases. idance to testers in regression-testing the SRU. [Other Info] This patch was accepted in debian: https://salsa.debian.org/debian/nfs-utils/merge_requests/2 [Original Description] In /etc/default/nfs-kernel-server you can specify parameters for rpc.svcgssd: # Options for rpc.svcgssd. RPCSVCGSSDOPTS="-n" But the variable is named incorrectly in /lib/systemd/system/rpc- svcgssd.service: ExecStart=/usr/sbin/rpc.svcgssd $SVCGSSDARGS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1616123/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1826870] Re: cache.commit() doesn't release the archives lock
This bug was fixed in the package python-apt - 1.6.4 --- python-apt (1.6.4) bionic; urgency=medium * apt.Cache: Fix (un)locking of archives (Closes: #922416) (LP: #1826870) * apt.Cache: Use explicit, more safe locking in update() * Update mirror lists -- Julian Andres Klode Mon, 29 Apr 2019 13:49:15 +0200 ** Changed in: python-apt (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1826870 Title: cache.commit() doesn't release the archives lock Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Released Status in python-apt source package in Bionic: Fix Released Status in python-apt source package in Cosmic: Fix Released Status in python-apt package in Debian: Fix Released Bug description: [Impact] cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826870/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1825250] Re: ethmonitor does not list interfaces without assigned IP address
This bug was fixed in the package resource-agents - 1:3.9.7-1ubuntu1.1 --- resource-agents (1:3.9.7-1ubuntu1.1) xenial; urgency=medium * Fix heartbeat/ethmonitor not listing network interfaces without IP addresses (LP: #1825250). Fixed by upstream patches: - d/p/lp1825250-ethmonitor-check-if-interface-exists-by-link.patch: ethmonitor: check if interface exists by link - d/p/lp1825250-ethmonitor-fix-is_interface-regression.patch: ethmonitor: fix is_interface() regression -- Heitor Alves de Siqueira Tue, 23 Apr 2019 14:15:40 -0300 ** Changed in: resource-agents (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1825250 Title: ethmonitor does not list interfaces without assigned IP address Status in resource-agents package in Ubuntu: Fix Released Status in resource-agents source package in Xenial: Fix Released Status in resource-agents source package in Bionic: Fix Released Status in resource-agents source package in Cosmic: Fix Released Status in resource-agents source package in Disco: Fix Released Status in resource-agents source package in Eoan: Fix Released Status in resource-agents package in Debian: New Bug description: [Impact] Some network interfaces will not be monitored by ethmonitor [Description] The is_interface() function in ethmonitor tries to match an interface to a list obtained from the 'ip' tool. It lists interfaces using the 'inet' family, which omits interfaces that don't have an IP address assigned. If the interface that we're looking for is e.g. a VLAN bridge that does not have an IP address, it won't show up in the listing and is_interface() will return false. ethmonitor will miss that interface, and it won't be available for monitoring. Upstream commits: - https://github.com/ClusterLabs/resource-agents/commit/40d05029ce0b - https://github.com/ClusterLabs/resource-agents/commit/c0ac191c73f1 [Test Case] 1) Ensure there's a network interface without an assigned IP address. For example, virbr0-nic will be created automatically by uvt-kvm: # ip addr show dev virbr0-nic 11: virbr0-nic: mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:e9:5e:af brd ff:ff:ff:ff:ff:ff 2) Install pcs+arping and create a new ethmonitor resource with the target interface: # sudo apt update && sudo apt install pcs arping -y # pcs resource create p_nic ocf:heartbeat:ethmonitor interface=virbr0-nic op monitor timeout="10s" 3) Debug-start ethmonitor resource and check for "Interface does not exist messages" # pcs resource debug-start p_nic Operation start for p_nic (ocf:heartbeat:ethmonitor) returned: 'ok' (0) > stderr: WARNING: Interface virbr0-nic does not exist > stderr: NOTICE: link_status: DOWN [Regression Potential] The regression potential is low, since we are relaxing the monitoring conditions for interfaces without an assigned IP address. The patches have been tested against Travis-CI before being merged upstream, and will be tested against autopkgtest for each target distro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1825250/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent
This bug was fixed in the package bash - 4.3-14ubuntu1.3
---
bash (4.3-14ubuntu1.3) xenial; urgency=medium
* Resurrect "Set the default path to comply with Debian policy" in
deb-bash-config.diff which went missing since 4.2+dfsg-1 or so.
LP: #1792004 LP: #1614080 Closes: #781367
* Add autopkgtest for the built-in path.
-- Dimitri John Ledkov Fri, 03 May 2019 14:57:15
+0100
** Changed in: bash (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1792004
Title:
built-in PATH seems to have sbin and bin out of order; and
inconsistent
Status in apt package in Ubuntu:
Fix Released
Status in bash package in Ubuntu:
Fix Released
Status in busybox package in Ubuntu:
New
Status in dash package in Ubuntu:
New
Status in dpkg package in Ubuntu:
Won't Fix
Status in pam package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Status in bash source package in Xenial:
Fix Released
Status in bash source package in Bionic:
Fix Released
Status in bash source package in Cosmic:
Fix Released
Status in bash source package in Disco:
Fix Released
Bug description:
[Impact]
* For consistency reasons sbin should be ordered before bin in PATH.
[Test Case]
* $ env -u PATH /bin/bash -c 'echo $PATH'
And check that matching pairs in PATH, have /sbin variant leading /bin
variant.
[Regression Potential]
* Ubuntu does not ship duplicate binries, with different behaviour
between /sbin and /bin, thus all binaries will continue to be found in
all locations. Also PATH is normally already set in the environment,
and this change only affects the fallback path when bash is executed
without any environment, i.e. booting with 'init=/bin/bash'
[Other Info]
* Original bug report detailing inconsistent paths between various shells.
---
$ env -u PATH /bin/sh -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ env -u PATH /bin/dash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ systemd-run --unit test-env env # ... and check journal for PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
$ env -u PATH /bin/busybox sh -c 'echo $PATH'
/sbin:/usr/sbin:/bin:/usr/bin
$ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin'
initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin
dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin}
exported as PATH
dracut-047+31/modules.d/99shutdown/shutdown.sh:export
PATH=/usr/sbin:/usr/bin:/sbin:/bin
$ cat /etc/environment
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
apt & dpkg => should probably initiate /usr/local-less PATH
Imho the rest should probably be harmonised to:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
===
From a duplicate
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 :
$ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i;
docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'";
done
12.04
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
12.10
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
13.04
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
13.10
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
14.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
14.10
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
15.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
15.10
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
16.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
I believe later releases of bash, do too include CWD in the built-in
PATH.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1792004/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829216] Re: linux-hwe: 4.15.0-51.55~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1829215 (linux-hwe-edge) -- swm properties -- kernel-stable-master-bug: 1829219 phase: Packaging phase-changed: Thursday, 16. May 2019 07:38 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + prepare-package: Pending -- package tag not yet published + promote-to-proposed: Holding -- builds not complete in ppa -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829216 Title: linux-hwe: 4.15.0-51.55~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1829215 (linux-hwe-edge) -- swm properties -- kernel-stable-master-bug: 1829219 phase: Packaging phase-changed: Thursday, 16. May 2019 07:38 UTC reason: prepare-package: Pending -- package tag not yet published promote-to-proposed: Holding -- builds not complete in ppa To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829216/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829214] Re: linux-azure: 4.15.0-1046.50 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829213 (trusty/linux-azure) derivatives: bug 1829212 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1829219 - phase: Packaging - phase-changed: Wednesday, 15. May 2019 23:06 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 16. May 2019 10:07 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Holding -- builds not complete in ppa -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829214 Title: linux-azure: 4.15.0-1046.50 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1829213 (trusty/linux-azure) derivatives: bug 1829212 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1829219 phase: Holding before Promote to Proposed phase-changed: Thursday, 16. May 2019 10:07 UTC reason: promote-to-proposed: Holding -- builds not complete in ppa To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829214/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829212] Re: linux-azure-edge: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829214 - phase: Holding before Packaging - phase-changed: Wednesday, 15. May 2019 11:05 UTC + phase: Ready for Packaging + phase-changed: Thursday, 16. May 2019 10:08 UTC reason: - prepare-package: Stalled -- waiting for master bug - prepare-package-meta: Stalled -- waiting for master bug + prepare-package-meta: Pending -- version not specified -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829212 Title: linux-azure-edge: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure-edge package in Ubuntu: Invalid Status in linux-azure-edge source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829214 phase: Ready for Packaging phase-changed: Thursday, 16. May 2019 10:08 UTC reason: prepare-package-meta: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829212/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1825250] Re: ethmonitor does not list interfaces without assigned IP address
This bug was fixed in the package resource-agents - 1:4.1.0~rc1-1ubuntu1.1 --- resource-agents (1:4.1.0~rc1-1ubuntu1.1) bionic; urgency=medium * Fix heartbeat/ethmonitor not listing network interfaces without IP addresses (LP: #1825250). Fixed by upstream patches: - d/p/lp1825250-ethmonitor-check-if-interface-exists-by-link.patch: ethmonitor: check if interface exists by link - d/p/lp1825250-ethmonitor-fix-is_interface-regression.patch: ethmonitor: fix is_interface() regression -- Heitor Alves de Siqueira Tue, 23 Apr 2019 14:12:58 -0300 ** Changed in: resource-agents (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1825250 Title: ethmonitor does not list interfaces without assigned IP address Status in resource-agents package in Ubuntu: Fix Released Status in resource-agents source package in Xenial: Fix Committed Status in resource-agents source package in Bionic: Fix Released Status in resource-agents source package in Cosmic: Fix Released Status in resource-agents source package in Disco: Fix Released Status in resource-agents source package in Eoan: Fix Released Status in resource-agents package in Debian: New Bug description: [Impact] Some network interfaces will not be monitored by ethmonitor [Description] The is_interface() function in ethmonitor tries to match an interface to a list obtained from the 'ip' tool. It lists interfaces using the 'inet' family, which omits interfaces that don't have an IP address assigned. If the interface that we're looking for is e.g. a VLAN bridge that does not have an IP address, it won't show up in the listing and is_interface() will return false. ethmonitor will miss that interface, and it won't be available for monitoring. Upstream commits: - https://github.com/ClusterLabs/resource-agents/commit/40d05029ce0b - https://github.com/ClusterLabs/resource-agents/commit/c0ac191c73f1 [Test Case] 1) Ensure there's a network interface without an assigned IP address. For example, virbr0-nic will be created automatically by uvt-kvm: # ip addr show dev virbr0-nic 11: virbr0-nic: mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:e9:5e:af brd ff:ff:ff:ff:ff:ff 2) Install pcs+arping and create a new ethmonitor resource with the target interface: # sudo apt update && sudo apt install pcs arping -y # pcs resource create p_nic ocf:heartbeat:ethmonitor interface=virbr0-nic op monitor timeout="10s" 3) Debug-start ethmonitor resource and check for "Interface does not exist messages" # pcs resource debug-start p_nic Operation start for p_nic (ocf:heartbeat:ethmonitor) returned: 'ok' (0) > stderr: WARNING: Interface virbr0-nic does not exist > stderr: NOTICE: link_status: DOWN [Regression Potential] The regression potential is low, since we are relaxing the monitoring conditions for interfaces without an assigned IP address. The patches have been tested against Travis-CI before being merged upstream, and will be tested against autopkgtest for each target distro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1825250/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)
This bug was fixed in the package linux-firmware - 1.173.6 --- linux-firmware (1.173.6) bionic; urgency=medium * Bluetooth not working (Intel CyclonePeak) (LP: #1817518) - linux-firmware: Add firmware file for Intel Bluetooth 22161 -- Seth Forshee Tue, 07 May 2019 06:54:50 -0500 ** Changed in: linux-firmware (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Released Status in linux-firmware source package in Disco: Fix Released Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1822270] Re: Debconf readline frontend does not show options
This bug was fixed in the package debconf - 1.5.66ubuntu1 --- debconf (1.5.66ubuntu1) bionic; urgency=medium * Fix readline prompts when run via run-parts (LP: #1822270) - Debconf/FrontEnd/Readline.pm: force output to stdout if both stdout and stderr are pipes -- Heitor Alves de Siqueira Mon, 06 May 2019 13:30:30 -0300 ** Changed in: debconf (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: Fix Released Status in debconf source package in Xenial: Fix Committed Status in debconf source package in Bionic: Fix Released Status in debconf source package in Cosmic: Fix Released Status in debconf source package in Disco: Fix Released Status in debconf source package in Eoan: Fix Released Status in debconf package in Debian: Fix Released Bug description: [Impact] debconf prompts the user for input before displaying options [Description] When upgrading packages with apt or dpkg, debconf scripts are ran through 'run-parts' with the '--report' flag. This causes script output to be handled through pipes set up by run-parts, and buffers output from maintainer scripts nicely for formatting. If debconf makes use of the readline frontend, any prompts will bypass the run-parts buffers and be displayed directly to /dev/tty. This generally causes the prompt to be displayed before the user gets any of the available options for it, and printing will block until the user inputs a valid option. Upstream commit: https://salsa.debian.org/pkg- debconf/debconf/commit/48c5ce38cfd5 [Test Case] 1) Deploy a VM through e.g. uvt-kvm $ uvt-kvm create disco release=disco 2) Remove the whiptail package to force the readline frontend in debconf root@disco:~# apt remove --purge whiptail -y 3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade through run-parts root@disco:~# apt update && apt install -y grub-legacy-ec2 root@disco:~# rm -f /boot/grub/menu.lst* root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst 4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we just need it to think menu.lst needs an upgrade) root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report ... /etc/kernel/postinst.d/x-grub-legacy-ec2: debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... What would you like to do about menu.lst? The "What would you like to do about menu.lst?" prompt will block until the user enter a valid option, even though it's being displayed before the available options. [Regression Potential] We could hit regressions if changing debconf's printing to /dev/tty is expected by other programs. The changes are needed only in the readline frontend, so that would minimize impact of any possible regressions. The fixes will be thoroughly tested with autopkgtest and use-case scenarios. # # # # [Original Description] When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash
This bug was fixed in the package bash - 4.4.18-2ubuntu1.1 --- bash (4.4.18-2ubuntu1.1) bionic; urgency=medium * Resurrect "Set the default path to comply with Debian policy" in deb-bash-config.diff which went missing since 4.2+dfsg-1 or so. LP: #1792004 LP: #1614080 Closes: #781367 * Add autopkgtest for the built-in path. -- Dimitri John Ledkov Fri, 03 May 2019 14:50:32 +0100 ** Changed in: bash (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash Status in bash package in Ubuntu: Fix Released Status in bash source package in Precise: Fix Released Status in bash source package in Trusty: Won't Fix Status in bash source package in Xenial: Fix Committed Status in bash source package in Bionic: Fix Released Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: Fix Released Status in bash source package in Eoan: Fix Released Status in bash package in Debian: New Bug description: [Impact] * The fallback path built into bash contains '.' which leads to unexpected addition of the current working directory. It should not be there, just like it isnt' in pre-precise and cosmic+. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' Should not have '.' as any component. Nor should there be any empty components, i.e. '::'. [Regression Potential] * Normally PATH is always set by either init, systemd, or any other hypervisor. Thus this only affects executions under bash, when it was started without any environment - e.g. booting with 'init=/bin/bash'. [Other Info] * Original bug report. On ubuntu 16.04 (but also 14.04), running bash with PATH unset always adds '.' to PATH: philippe@pv-desktop:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games philippe@pv-desktop:~$ unset PATH philippe@pv-desktop:~$ /bin/bash philippe@pv-desktop:~$ echo $PATH /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. Even when testing in a virtual machine / docker, and erasing /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem still happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1616123] Re: rpc-svcgssd.service uses incorrrect variable SVCGSSDARGS
This bug was fixed in the package nfs-utils - 1:1.3.4-2.1ubuntu5.2 --- nfs-utils (1:1.3.4-2.1ubuntu5.2) bionic; urgency=medium * d/nfs-utils_env.sh: alongside RPCSVCGSSDARGS, also export SVCGSSDARGS, which is the variable name expected by the rpc-svcgssd systemd service. (LP: #1616123) -- Andreas Hasenack Thu, 25 Apr 2019 17:17:31 -0300 ** Changed in: nfs-utils (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1616123 Title: rpc-svcgssd.service uses incorrrect variable SVCGSSDARGS Status in nfs-utils package in Ubuntu: Fix Released Status in nfs-utils source package in Xenial: Fix Committed Status in nfs-utils source package in Bionic: Fix Released Status in nfs-utils source package in Cosmic: Fix Released Status in nfs-utils package in Debian: Fix Committed Bug description: [Impact] Command line options set for rpc.svcgssd in the /etc/default/nfs-kernel-server file are not passed on to the service, being ignored. [Test Case] * In a VM (LXD won't work), install nfs-server and a kerberos server. Use "EXAMPLE.LOCAL" for the realm, and "localhost" for the servers, when prompted: sudo apt install nfs-server krb5-kdc krb5-user krb5-admin-server * create the EXAMPLE.LOCAL realm. Use any password you want for the database master key, it won't be requested again: sudo krb5_newrealm * create a principal for the nfs service: sudo kadmin.local -q "addprinc -randkey nfs/$(hostname -f)" * extract the key into the system wide keytab: sudo kadmin.local -q "ktadd -k /etc/krb5.keytab nfs/$(hostname -f)" * edit /etc/default/nfs-common and enable gssd: NEED_GSSD=y * edit /etc/default/nfs-kernel-server and add an option to RPCSVCGSSDOPTS: RPCSVCGSSDOPTS="-v" * restart nfs-server sudo systemctl restart nfs-server * on xenial, you also have to restart nfs-config: sudo systemctl restart nfs-config * verify if /run/sysconfig/nfs-utils has the option we added above: $ cat /run/sysconfig/nfs-utils PIPEFS_MOUNTPOINT=/run/rpc_pipefs RPCNFSDARGS=" 8" RPCMOUNTDARGS="--manage-gids" STATDARGS="" RPCSVCGSSDARGS="-v" * Verify the running rpc.gssd process. Without the fix, it won't have the "-v" option: ps axw|grep svcgssd|grep -v grep 4285 ? Ss 0:00 /usr/sbin/rpc.svcgssd With the fix, right after installing the udpated packages, the option we added to /etc/default/nfs-kernel-server will show up: ps axw|grep svcgssd|grep -v grep 5656 ? Ss 0:00 /usr/sbin/rpc.svcgssd -v [Regression Potential] This is an old bug and whoever was affected by it probably worked around the problem by now. I tried to cope with one such scenario by not just renaming the variable we export, but exporting the correct one in addition to the old incorrect one, but that's it. I hope this, and the explanation added to the shell script wrapper nfs-utils.sh, is enough to help people with corner cases. idance to testers in regression-testing the SRU. [Other Info] This patch was accepted in debian: https://salsa.debian.org/debian/nfs-utils/merge_requests/2 [Original Description] In /etc/default/nfs-kernel-server you can specify parameters for rpc.svcgssd: # Options for rpc.svcgssd. RPCSVCGSSDOPTS="-n" But the variable is named incorrectly in /lib/systemd/system/rpc- svcgssd.service: ExecStart=/usr/sbin/rpc.svcgssd $SVCGSSDARGS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1616123/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent
This bug was fixed in the package bash - 4.4.18-2ubuntu1.1
---
bash (4.4.18-2ubuntu1.1) bionic; urgency=medium
* Resurrect "Set the default path to comply with Debian policy" in
deb-bash-config.diff which went missing since 4.2+dfsg-1 or so.
LP: #1792004 LP: #1614080 Closes: #781367
* Add autopkgtest for the built-in path.
-- Dimitri John Ledkov Fri, 03 May 2019 14:50:32
+0100
** Changed in: bash (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1792004
Title:
built-in PATH seems to have sbin and bin out of order; and
inconsistent
Status in apt package in Ubuntu:
Fix Released
Status in bash package in Ubuntu:
Fix Released
Status in busybox package in Ubuntu:
New
Status in dash package in Ubuntu:
New
Status in dpkg package in Ubuntu:
Won't Fix
Status in pam package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Status in bash source package in Xenial:
Fix Committed
Status in bash source package in Bionic:
Fix Released
Status in bash source package in Cosmic:
Fix Released
Status in bash source package in Disco:
Fix Released
Bug description:
[Impact]
* For consistency reasons sbin should be ordered before bin in PATH.
[Test Case]
* $ env -u PATH /bin/bash -c 'echo $PATH'
And check that matching pairs in PATH, have /sbin variant leading /bin
variant.
[Regression Potential]
* Ubuntu does not ship duplicate binries, with different behaviour
between /sbin and /bin, thus all binaries will continue to be found in
all locations. Also PATH is normally already set in the environment,
and this change only affects the fallback path when bash is executed
without any environment, i.e. booting with 'init=/bin/bash'
[Other Info]
* Original bug report detailing inconsistent paths between various shells.
---
$ env -u PATH /bin/sh -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ env -u PATH /bin/dash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ systemd-run --unit test-env env # ... and check journal for PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
$ env -u PATH /bin/busybox sh -c 'echo $PATH'
/sbin:/usr/sbin:/bin:/usr/bin
$ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin'
initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin
dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin}
exported as PATH
dracut-047+31/modules.d/99shutdown/shutdown.sh:export
PATH=/usr/sbin:/usr/bin:/sbin:/bin
$ cat /etc/environment
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
apt & dpkg => should probably initiate /usr/local-less PATH
Imho the rest should probably be harmonised to:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
===
From a duplicate
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 :
$ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i;
docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'";
done
12.04
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
12.10
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
13.04
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
13.10
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
14.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
14.10
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
15.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
15.10
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
16.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
I believe later releases of bash, do too include CWD in the built-in
PATH.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1792004/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)
This bug was fixed in the package linux-firmware - 1.175.4 --- linux-firmware (1.175.4) cosmic; urgency=medium * Bluetooth not working (Intel CyclonePeak) (LP: #1817518) - linux-firmware: Add firmware file for Intel Bluetooth 22161 -- Seth Forshee Tue, 07 May 2019 07:05:41 -0500 ** Changed in: linux-firmware (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Released Status in linux-firmware source package in Disco: Fix Released Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1822270] Re: Debconf readline frontend does not show options
This bug was fixed in the package debconf - 1.5.69ubuntu1 --- debconf (1.5.69ubuntu1) cosmic; urgency=medium * Fix readline prompts when run via run-parts (LP: #1822270) - Debconf/FrontEnd/Readline.pm: force output to stdout if both stdout and stderr are pipes -- Heitor Alves de Siqueira Mon, 06 May 2019 13:27:55 -0300 ** Changed in: debconf (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: Fix Released Status in debconf source package in Xenial: Fix Committed Status in debconf source package in Bionic: Fix Committed Status in debconf source package in Cosmic: Fix Released Status in debconf source package in Disco: Fix Released Status in debconf source package in Eoan: Fix Released Status in debconf package in Debian: Fix Released Bug description: [Impact] debconf prompts the user for input before displaying options [Description] When upgrading packages with apt or dpkg, debconf scripts are ran through 'run-parts' with the '--report' flag. This causes script output to be handled through pipes set up by run-parts, and buffers output from maintainer scripts nicely for formatting. If debconf makes use of the readline frontend, any prompts will bypass the run-parts buffers and be displayed directly to /dev/tty. This generally causes the prompt to be displayed before the user gets any of the available options for it, and printing will block until the user inputs a valid option. Upstream commit: https://salsa.debian.org/pkg- debconf/debconf/commit/48c5ce38cfd5 [Test Case] 1) Deploy a VM through e.g. uvt-kvm $ uvt-kvm create disco release=disco 2) Remove the whiptail package to force the readline frontend in debconf root@disco:~# apt remove --purge whiptail -y 3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade through run-parts root@disco:~# apt update && apt install -y grub-legacy-ec2 root@disco:~# rm -f /boot/grub/menu.lst* root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst 4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we just need it to think menu.lst needs an upgrade) root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report ... /etc/kernel/postinst.d/x-grub-legacy-ec2: debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... What would you like to do about menu.lst? The "What would you like to do about menu.lst?" prompt will block until the user enter a valid option, even though it's being displayed before the available options. [Regression Potential] We could hit regressions if changing debconf's printing to /dev/tty is expected by other programs. The changes are needed only in the readline frontend, so that would minimize impact of any possible regressions. The fixes will be thoroughly tested with autopkgtest and use-case scenarios. # # # # [Original Description] When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1616123] Re: rpc-svcgssd.service uses incorrrect variable SVCGSSDARGS
This bug was fixed in the package nfs-utils - 1:1.3.4-2.2ubuntu3.2 --- nfs-utils (1:1.3.4-2.2ubuntu3.2) cosmic; urgency=medium * d/nfs-utils_env.sh: alongside RPCSVCGSSDARGS, also export SVCGSSDARGS, which is the variable name expected by the rpc-svcgssd systemd service. (LP: #1616123) -- Andreas Hasenack Thu, 25 Apr 2019 17:13:13 -0300 ** Changed in: nfs-utils (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1616123 Title: rpc-svcgssd.service uses incorrrect variable SVCGSSDARGS Status in nfs-utils package in Ubuntu: Fix Released Status in nfs-utils source package in Xenial: Fix Committed Status in nfs-utils source package in Bionic: Fix Committed Status in nfs-utils source package in Cosmic: Fix Released Status in nfs-utils package in Debian: Fix Committed Bug description: [Impact] Command line options set for rpc.svcgssd in the /etc/default/nfs-kernel-server file are not passed on to the service, being ignored. [Test Case] * In a VM (LXD won't work), install nfs-server and a kerberos server. Use "EXAMPLE.LOCAL" for the realm, and "localhost" for the servers, when prompted: sudo apt install nfs-server krb5-kdc krb5-user krb5-admin-server * create the EXAMPLE.LOCAL realm. Use any password you want for the database master key, it won't be requested again: sudo krb5_newrealm * create a principal for the nfs service: sudo kadmin.local -q "addprinc -randkey nfs/$(hostname -f)" * extract the key into the system wide keytab: sudo kadmin.local -q "ktadd -k /etc/krb5.keytab nfs/$(hostname -f)" * edit /etc/default/nfs-common and enable gssd: NEED_GSSD=y * edit /etc/default/nfs-kernel-server and add an option to RPCSVCGSSDOPTS: RPCSVCGSSDOPTS="-v" * restart nfs-server sudo systemctl restart nfs-server * on xenial, you also have to restart nfs-config: sudo systemctl restart nfs-config * verify if /run/sysconfig/nfs-utils has the option we added above: $ cat /run/sysconfig/nfs-utils PIPEFS_MOUNTPOINT=/run/rpc_pipefs RPCNFSDARGS=" 8" RPCMOUNTDARGS="--manage-gids" STATDARGS="" RPCSVCGSSDARGS="-v" * Verify the running rpc.gssd process. Without the fix, it won't have the "-v" option: ps axw|grep svcgssd|grep -v grep 4285 ? Ss 0:00 /usr/sbin/rpc.svcgssd With the fix, right after installing the udpated packages, the option we added to /etc/default/nfs-kernel-server will show up: ps axw|grep svcgssd|grep -v grep 5656 ? Ss 0:00 /usr/sbin/rpc.svcgssd -v [Regression Potential] This is an old bug and whoever was affected by it probably worked around the problem by now. I tried to cope with one such scenario by not just renaming the variable we export, but exporting the correct one in addition to the old incorrect one, but that's it. I hope this, and the explanation added to the shell script wrapper nfs-utils.sh, is enough to help people with corner cases. idance to testers in regression-testing the SRU. [Other Info] This patch was accepted in debian: https://salsa.debian.org/debian/nfs-utils/merge_requests/2 [Original Description] In /etc/default/nfs-kernel-server you can specify parameters for rpc.svcgssd: # Options for rpc.svcgssd. RPCSVCGSSDOPTS="-n" But the variable is named incorrectly in /lib/systemd/system/rpc- svcgssd.service: ExecStart=/usr/sbin/rpc.svcgssd $SVCGSSDARGS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1616123/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1825250] Re: ethmonitor does not list interfaces without assigned IP address
This bug was fixed in the package resource-agents - 1:4.1.1-2ubuntu1 --- resource-agents (1:4.1.1-2ubuntu1) cosmic; urgency=medium * Fix heartbeat/ethmonitor not listing network interfaces without IP addresses (LP: #1825250). Fixed by upstream patches: - d/p/lp1825250-ethmonitor-check-if-interface-exists-by-link.patch: ethmonitor: check if interface exists by link - d/p/lp1825250-ethmonitor-fix-is_interface-regression.patch: ethmonitor: fix is_interface() regression -- Heitor Alves de Siqueira Tue, 23 Apr 2019 14:07:57 -0300 ** Changed in: resource-agents (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1825250 Title: ethmonitor does not list interfaces without assigned IP address Status in resource-agents package in Ubuntu: Fix Released Status in resource-agents source package in Xenial: Fix Committed Status in resource-agents source package in Bionic: Fix Committed Status in resource-agents source package in Cosmic: Fix Released Status in resource-agents source package in Disco: Fix Released Status in resource-agents source package in Eoan: Fix Released Status in resource-agents package in Debian: New Bug description: [Impact] Some network interfaces will not be monitored by ethmonitor [Description] The is_interface() function in ethmonitor tries to match an interface to a list obtained from the 'ip' tool. It lists interfaces using the 'inet' family, which omits interfaces that don't have an IP address assigned. If the interface that we're looking for is e.g. a VLAN bridge that does not have an IP address, it won't show up in the listing and is_interface() will return false. ethmonitor will miss that interface, and it won't be available for monitoring. Upstream commits: - https://github.com/ClusterLabs/resource-agents/commit/40d05029ce0b - https://github.com/ClusterLabs/resource-agents/commit/c0ac191c73f1 [Test Case] 1) Ensure there's a network interface without an assigned IP address. For example, virbr0-nic will be created automatically by uvt-kvm: # ip addr show dev virbr0-nic 11: virbr0-nic: mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:e9:5e:af brd ff:ff:ff:ff:ff:ff 2) Install pcs+arping and create a new ethmonitor resource with the target interface: # sudo apt update && sudo apt install pcs arping -y # pcs resource create p_nic ocf:heartbeat:ethmonitor interface=virbr0-nic op monitor timeout="10s" 3) Debug-start ethmonitor resource and check for "Interface does not exist messages" # pcs resource debug-start p_nic Operation start for p_nic (ocf:heartbeat:ethmonitor) returned: 'ok' (0) > stderr: WARNING: Interface virbr0-nic does not exist > stderr: NOTICE: link_status: DOWN [Regression Potential] The regression potential is low, since we are relaxing the monitoring conditions for interfaces without an assigned IP address. The patches have been tested against Travis-CI before being merged upstream, and will be tested against autopkgtest for each target distro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1825250/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)
This bug was fixed in the package linux-firmware - 1.178.1 --- linux-firmware (1.178.1) disco; urgency=medium * Bluetooth not working (Intel CyclonePeak) (LP: #1817518) - linux-firmware: Add firmware file for Intel Bluetooth 22161 -- Seth Forshee Tue, 07 May 2019 07:14:55 -0500 ** Changed in: linux-firmware (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Released Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1822270] Re: Debconf readline frontend does not show options
This bug was fixed in the package debconf - 1.5.71ubuntu1 --- debconf (1.5.71ubuntu1) disco; urgency=medium * Fix readline prompts when run via run-parts (LP: #1822270) - Debconf/FrontEnd/Readline.pm: force output to stdout if both stdout and stderr are pipes -- Heitor Alves de Siqueira Mon, 06 May 2019 13:16:57 -0300 ** Changed in: debconf (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: Fix Released Status in debconf source package in Xenial: Fix Committed Status in debconf source package in Bionic: Fix Committed Status in debconf source package in Cosmic: Fix Committed Status in debconf source package in Disco: Fix Released Status in debconf source package in Eoan: Fix Released Status in debconf package in Debian: Fix Released Bug description: [Impact] debconf prompts the user for input before displaying options [Description] When upgrading packages with apt or dpkg, debconf scripts are ran through 'run-parts' with the '--report' flag. This causes script output to be handled through pipes set up by run-parts, and buffers output from maintainer scripts nicely for formatting. If debconf makes use of the readline frontend, any prompts will bypass the run-parts buffers and be displayed directly to /dev/tty. This generally causes the prompt to be displayed before the user gets any of the available options for it, and printing will block until the user inputs a valid option. Upstream commit: https://salsa.debian.org/pkg- debconf/debconf/commit/48c5ce38cfd5 [Test Case] 1) Deploy a VM through e.g. uvt-kvm $ uvt-kvm create disco release=disco 2) Remove the whiptail package to force the readline frontend in debconf root@disco:~# apt remove --purge whiptail -y 3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade through run-parts root@disco:~# apt update && apt install -y grub-legacy-ec2 root@disco:~# rm -f /boot/grub/menu.lst* root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst 4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we just need it to think menu.lst needs an upgrade) root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report ... /etc/kernel/postinst.d/x-grub-legacy-ec2: debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... What would you like to do about menu.lst? The "What would you like to do about menu.lst?" prompt will block until the user enter a valid option, even though it's being displayed before the available options. [Regression Potential] We could hit regressions if changing debconf's printing to /dev/tty is expected by other programs. The changes are needed only in the readline frontend, so that would minimize impact of any possible regressions. The fixes will be thoroughly tested with autopkgtest and use-case scenarios. # # # # [Original Description] When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829193] Re: linux-aws: 4.4.0-1084.94 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829209 - phase: Ready for Packaging - phase-changed: Wednesday, 15. May 2019 14:03 UTC + phase: Packaging + phase-changed: Thursday, 16. May 2019 09:04 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829193 Title: linux-aws: 4.4.0-1084.94 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829209 phase: Packaging phase-changed: Thursday, 16. May 2019 09:04 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829193/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829201] Re: linux-snapdragon: 4.4.0-1114.119 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829209 - phase: Packaging - phase-changed: Wednesday, 15. May 2019 16:23 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 16. May 2019 09:04 UTC reason: - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Holding -- builds not complete in ppa -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829201 Title: linux-snapdragon: 4.4.0-1114.119 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829209 phase: Holding before Promote to Proposed phase-changed: Thursday, 16. May 2019 09:04 UTC reason: promote-to-proposed: Holding -- builds not complete in ppa To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829201/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1825250] Re: ethmonitor does not list interfaces without assigned IP address
This bug was fixed in the package resource-agents - 1:4.2.0-1ubuntu1.1 --- resource-agents (1:4.2.0-1ubuntu1.1) disco; urgency=medium * Fix heartbeat/ethmonitor not listing network interfaces without IP addresses (LP: #1825250). Fixed by upstream patches: - d/p/lp1825250-ethmonitor-check-if-interface-exists-by-link.patch: ethmonitor: check if interface exists by link - d/p/lp1825250-ethmonitor-fix-is_interface-regression.patch: ethmonitor: fix is_interface() regression -- Heitor Alves de Siqueira Tue, 23 Apr 2019 13:56:29 -0300 ** Changed in: resource-agents (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1825250 Title: ethmonitor does not list interfaces without assigned IP address Status in resource-agents package in Ubuntu: Fix Released Status in resource-agents source package in Xenial: Fix Committed Status in resource-agents source package in Bionic: Fix Committed Status in resource-agents source package in Cosmic: Fix Committed Status in resource-agents source package in Disco: Fix Released Status in resource-agents source package in Eoan: Fix Released Status in resource-agents package in Debian: New Bug description: [Impact] Some network interfaces will not be monitored by ethmonitor [Description] The is_interface() function in ethmonitor tries to match an interface to a list obtained from the 'ip' tool. It lists interfaces using the 'inet' family, which omits interfaces that don't have an IP address assigned. If the interface that we're looking for is e.g. a VLAN bridge that does not have an IP address, it won't show up in the listing and is_interface() will return false. ethmonitor will miss that interface, and it won't be available for monitoring. Upstream commits: - https://github.com/ClusterLabs/resource-agents/commit/40d05029ce0b - https://github.com/ClusterLabs/resource-agents/commit/c0ac191c73f1 [Test Case] 1) Ensure there's a network interface without an assigned IP address. For example, virbr0-nic will be created automatically by uvt-kvm: # ip addr show dev virbr0-nic 11: virbr0-nic: mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:e9:5e:af brd ff:ff:ff:ff:ff:ff 2) Install pcs+arping and create a new ethmonitor resource with the target interface: # sudo apt update && sudo apt install pcs arping -y # pcs resource create p_nic ocf:heartbeat:ethmonitor interface=virbr0-nic op monitor timeout="10s" 3) Debug-start ethmonitor resource and check for "Interface does not exist messages" # pcs resource debug-start p_nic Operation start for p_nic (ocf:heartbeat:ethmonitor) returned: 'ok' (0) > stderr: WARNING: Interface virbr0-nic does not exist > stderr: NOTICE: link_status: DOWN [Regression Potential] The regression potential is low, since we are relaxing the monitoring conditions for interfaces without an assigned IP address. The patches have been tested against Travis-CI before being merged upstream, and will be tested against autopkgtest for each target distro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1825250/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829201] Re: linux-snapdragon: 4.4.0-1114.119 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829209 phase: Packaging phase-changed: Wednesday, 15. May 2019 16:23 UTC reason: - prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829201 Title: linux-snapdragon: 4.4.0-1114.119 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1829209 phase: Packaging phase-changed: Wednesday, 15. May 2019 16:23 UTC reason: prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829201/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value
This bug was fixed in the package libreoffice-l10n - 1:6.2.3-0ubuntu0.19.04.1 --- libreoffice-l10n (1:6.2.3-0ubuntu0.19.04.1) disco; urgency=medium [ Olivier Tilloy ] * debian/patches/java.vendor-Ubuntu.patch: update to also recognize "Private Build" as java.vendor (for custom PPA builds) (LP: #1822839) [ Marcus Tomlinson ] * New upstream release (LP: #1826560) -- Marcus Tomlinson Tue, 30 Apr 2019 13:39:41 +0100 ** Changed in: libreoffice-l10n (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822839 Title: LibreOffice doesn't detect JVM because of unexpected java.vendor property value Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in openjdk-lts package in Ubuntu: New Status in libreoffice source package in Xenial: In Progress Status in libreoffice source package in Bionic: In Progress Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in openjdk-lts source package in Disco: New Status in libreoffice package in Debian: New Bug description: [Impact] * A recent OpenJDK update changes the value of the "java.vendor" property from "Oracle Corporation" to "Private Build". This breaks the code in LibreOffice that detects an installed JVM. * The fix is currently in LibreOffice 6.2.3 on eoan. [Test Case] 1. Launch the LibreOffice Start Center 2. Open Tools > Options 3. Navigate to LibreOffice > Advanced 4. A JRE should be listed with Location: /usr/lib/jvm/... [Regression Potential] * This fix is small and concentrated so potential for regression should be relatively low. * A combination of autopkgtests and manual testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1822839/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value
This bug was fixed in the package libreoffice - 1:6.2.3-0ubuntu0.19.04.1 --- libreoffice (1:6.2.3-0ubuntu0.19.04.1) disco; urgency=medium [ Olivier Tilloy ] * debian/patches/java.vendor-Ubuntu.patch: update to also recognize "Private Build" as java.vendor (for custom PPA builds) (LP: #1822839) [ Marcus Tomlinson ] * New upstream release (LP: #1826560) -- Marcus Tomlinson Tue, 30 Apr 2019 13:39:41 +0100 ** Changed in: libreoffice (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822839 Title: LibreOffice doesn't detect JVM because of unexpected java.vendor property value Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in openjdk-lts package in Ubuntu: New Status in libreoffice source package in Xenial: In Progress Status in libreoffice source package in Bionic: In Progress Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in openjdk-lts source package in Disco: New Status in libreoffice package in Debian: New Bug description: [Impact] * A recent OpenJDK update changes the value of the "java.vendor" property from "Oracle Corporation" to "Private Build". This breaks the code in LibreOffice that detects an installed JVM. * The fix is currently in LibreOffice 6.2.3 on eoan. [Test Case] 1. Launch the LibreOffice Start Center 2. Open Tools > Options 3. Navigate to LibreOffice > Advanced 4. A JRE should be listed with Location: /usr/lib/jvm/... [Regression Potential] * This fix is small and concentrated so potential for regression should be relatively low. * A combination of autopkgtests and manual testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1822839/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1614080] Re: PATH contains dot when PATH is unset before running bash
This bug was fixed in the package bash - 5.0-3ubuntu1.1 --- bash (5.0-3ubuntu1.1) disco; urgency=medium * Resurrect "Set the default path to comply with Debian policy" in deb-bash-config.diff which went missing since 4.2+dfsg-1 or so. LP: #1792004 LP: #1614080 Closes: #781367 * Add autopkgtest for the built-in path. -- Dimitri John Ledkov Fri, 03 May 2019 14:31:24 +0100 ** Changed in: bash (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash Status in bash package in Ubuntu: Fix Released Status in bash source package in Precise: Fix Released Status in bash source package in Trusty: Won't Fix Status in bash source package in Xenial: Fix Committed Status in bash source package in Bionic: Fix Committed Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: Fix Released Status in bash source package in Eoan: Fix Released Status in bash package in Debian: New Bug description: [Impact] * The fallback path built into bash contains '.' which leads to unexpected addition of the current working directory. It should not be there, just like it isnt' in pre-precise and cosmic+. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' Should not have '.' as any component. Nor should there be any empty components, i.e. '::'. [Regression Potential] * Normally PATH is always set by either init, systemd, or any other hypervisor. Thus this only affects executions under bash, when it was started without any environment - e.g. booting with 'init=/bin/bash'. [Other Info] * Original bug report. On ubuntu 16.04 (but also 14.04), running bash with PATH unset always adds '.' to PATH: philippe@pv-desktop:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games philippe@pv-desktop:~$ unset PATH philippe@pv-desktop:~$ /bin/bash philippe@pv-desktop:~$ echo $PATH /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. Even when testing in a virtual machine / docker, and erasing /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem still happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent
This bug was fixed in the package bash - 5.0-3ubuntu1.1
---
bash (5.0-3ubuntu1.1) disco; urgency=medium
* Resurrect "Set the default path to comply with Debian policy" in
deb-bash-config.diff which went missing since 4.2+dfsg-1 or so.
LP: #1792004 LP: #1614080 Closes: #781367
* Add autopkgtest for the built-in path.
-- Dimitri John Ledkov Fri, 03 May 2019 14:31:24
+0100
** Changed in: bash (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1792004
Title:
built-in PATH seems to have sbin and bin out of order; and
inconsistent
Status in apt package in Ubuntu:
Fix Released
Status in bash package in Ubuntu:
Fix Released
Status in busybox package in Ubuntu:
New
Status in dash package in Ubuntu:
New
Status in dpkg package in Ubuntu:
Won't Fix
Status in pam package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Status in bash source package in Xenial:
Fix Committed
Status in bash source package in Bionic:
Fix Committed
Status in bash source package in Cosmic:
Fix Released
Status in bash source package in Disco:
Fix Released
Bug description:
[Impact]
* For consistency reasons sbin should be ordered before bin in PATH.
[Test Case]
* $ env -u PATH /bin/bash -c 'echo $PATH'
And check that matching pairs in PATH, have /sbin variant leading /bin
variant.
[Regression Potential]
* Ubuntu does not ship duplicate binries, with different behaviour
between /sbin and /bin, thus all binaries will continue to be found in
all locations. Also PATH is normally already set in the environment,
and this change only affects the fallback path when bash is executed
without any environment, i.e. booting with 'init=/bin/bash'
[Other Info]
* Original bug report detailing inconsistent paths between various shells.
---
$ env -u PATH /bin/sh -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ env -u PATH /bin/dash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ systemd-run --unit test-env env # ... and check journal for PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
$ env -u PATH /bin/busybox sh -c 'echo $PATH'
/sbin:/usr/sbin:/bin:/usr/bin
$ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin'
initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin
dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin}
exported as PATH
dracut-047+31/modules.d/99shutdown/shutdown.sh:export
PATH=/usr/sbin:/usr/bin:/sbin:/bin
$ cat /etc/environment
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
apt & dpkg => should probably initiate /usr/local-less PATH
Imho the rest should probably be harmonised to:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
===
From a duplicate
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 :
$ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i;
docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'";
done
12.04
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
12.10
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
13.04
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
13.10
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
14.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
14.10
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
15.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
15.10
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
16.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
I believe later releases of bash, do too include CWD in the built-in
PATH.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1792004/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829216] Re: linux-hwe: 4.15.0-51.55~16.04.1 -proposed tracker
** Summary changed: - linux-hwe: 4.15.0-50.54~16.04.2 -proposed tracker + linux-hwe: 4.15.0-51.55~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829216 Title: linux-hwe: 4.15.0-51.55~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1829215 (linux-hwe-edge) -- swm properties -- kernel-stable-master-bug: 1829219 phase: Packaging phase-changed: Thursday, 16. May 2019 07:38 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829216/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829216] Re: linux-hwe: 4.15.0-50.54~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1829215 (linux-hwe-edge) -- swm properties -- kernel-stable-master-bug: 1829219 - phase: Ready for Packaging - phase-changed: Wednesday, 15. May 2019 15:06 UTC + phase: Packaging + phase-changed: Thursday, 16. May 2019 07:38 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829216 Title: linux-hwe: 4.15.0-50.54~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1829215 (linux-hwe-edge) -- swm properties -- kernel-stable-master-bug: 1829219 phase: Packaging phase-changed: Thursday, 16. May 2019 07:38 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829216/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
