[Group.of.nepali.translators] [Bug 1818880] Re: Deadlock when detaching network interface
** No longer affects: qemu -- 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/1818880 Title: Deadlock when detaching network interface Status in Ubuntu Cloud Archive: Confirmed Status in qemu package in Ubuntu: Fix Released Status in qemu source package in Xenial: Confirmed Status in qemu source package in Bionic: Fix Released Status in qemu source package in Cosmic: Fix Released Status in qemu source package in Disco: Fix Released Bug description: [Impact] Qemu guests hang indefinitely [Description] When running a Qemu guest with VirtIO network interfaces, detaching an interface that's currently being used can result in a deadlock. The guest instance will hang and become unresponsive to commands, and the only option is to kill -9 the instance. The reason for this is a dealock between a monitor and an RCU thread, which will fight over the BQL (qemu_global_mutex) and the critical RCU section locks. The monitor thread will acquire the BQL for detaching the network interface, and fire up a helper thread to deal with detaching the network adapter. That new thread needs to wait on the RCU thread to complete the deletion, but the RCU thread wants the BQL to commit its transactions. This bug is already fixed upstream (73c6e4013b4c rcu: completely disable pthread_atfork callbacks as soon as possible) and included for other series (see below), so we don't need to backport it to Bionic onwards. Upstream commit: https://git.qemu.org/?p=qemu.git;a=commit;h=73c6e4013b4c $ git describe --contains 73c6e4013b4c v2.10.0-rc2~1^2~8 $ rmadison qemu ===> qemu | 1:2.5+dfsg-5ubuntu10.34 | xenial-updates/universe | amd64, ... qemu | 1:2.11+dfsg-1ubuntu7| bionic/universe | amd64, ... qemu | 1:2.12+dfsg-3ubuntu8| cosmic/universe | amd64, ... qemu | 1:3.1+dfsg-2ubuntu2 | disco/universe| amd64, ... [Test Case] Being a racing condition, this is a tricky bug to reproduce consistently. We've had reports of users running into this with OpenStack deployments and Windows Server guests, and the scenario is usually like this: 1) Deploy a 16vCPU Windows Server 2012 R2 guest with a virtio network interface 2) Stress the network interface with e.g. Windows HLK test suite or similar 3) Repeatedly attach/detach the network adapter that's in use It usually takes more than ~4000 attach/detach cycles to trigger the bug. [Regression Potential] Regressions for this might arise from the fact that the fix changes RCU lock code. Since this patch has been upstream and in other series for a while, it's unlikely that it would regressions in RCU code specifically. Other code that makes use of the RCU locks (MMIO and some monitor events) will be thoroughly tested for any regressions with use-case scenarios and scripted runs. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace
** Also affects: libnotify (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libnotify (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: libnotify (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: libnotify (Ubuntu Bionic) Importance: Undecided => Medium -- 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/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace Status in libnotify package in Ubuntu: In Progress Status in libnotify source package in Xenial: New Status in libnotify source package in Bionic: New Bug description: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap: git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path Running them with G_MESSAGES_DEBUG=all should provide translation logging [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1530523] Re: kcm_driver_manager: Infinitely shows Collecting information
This was fixed in Xenial with libqapt 3.0.2-0ubuntu1.2 and in other releases with more recent packages. This shouldn't have been set to Incomplete. ** Changed in: libqapt (Ubuntu Xenial) Status: Incomplete => Fix Released ** Project changed: kubuntu-ppa => ubuntu-translations ** No longer affects: ubuntu-translations ** Changed in: libqapt (Ubuntu) Status: Expired => 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/1530523 Title: kcm_driver_manager: Infinitely shows Collecting information Status in libqapt package in Ubuntu: Fix Released Status in libqapt source package in Xenial: Fix Released Bug description: [Impact] * libQapt needs apt-xapian-index in order to search for packages, otherwise it never returns a result. * As a consequence Driver Manager doesn't find packages and is empty. * Before, apt-xapian-index was installed as a dependence of Muon (libmuon), which is not included in the default install anymore. [Test Case] * Update libqapt and run `kcmshell5 kcm_driver_manager`. * After some time (~1 minute) Driver Manager shows suggested packages. [Regression Potential] * Low, Driver Manager is useless as of now. * The same fix was applied in Yakkety. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libqapt/+bug/1530523/+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 1819046] [NEW] Systemd unit file reads settings from wrong path
Public bug reported: [Impact] Systemd Unit file doesn't read any settings by default [Description] The unit file shipped with the Xenial pacemaker package tries to read environment settings from /etc/sysconfig/ instead of /etc/default/. The result is that settings defined in /etc/default/pacemaker are not effective. Since the /etc/default/pacemaker file is created with default values when the pacemaker package is installed, we should source that in the systemd unit file. [Test Case] 1) Deploy a Xenial container: $ lxc launch ubuntu:xenial pacemaker 2) Update container and install pacemaker: root@pacemaker:~# apt update && apt install pacemaker -y 3) Check the systemd unit file for the "EnvironmentFile" option: root@pacemaker:~# systemctl cat pacemaker | grep EnvironmentFile EnvironmentFile=-/etc/sysconfig/pacemaker EnvironmentFile=-/etc/sysconfig/sbd [Regression Potential] The regression potential for this should be very low, since the configuration file is already being created by default and other systemd unit files are using the /etc/default config. In case the file doesn't exist or the user removed it, the "-" prefix will gracefully ignore the missing file according to the systemd.exec manual [0]. Nonetheless, the new package will be tested with autopkgtests and the fix will be validated in a reproduction environment. [0] https://www.freedesktop.org/software/systemd/man/systemd.exec.html ** Affects: pacemaker (Ubuntu) Importance: Undecided Assignee: Heitor R. Alves de Siqueira (halves) Status: Fix Released ** Affects: pacemaker (Ubuntu Xenial) Importance: Undecided Assignee: Heitor R. Alves de Siqueira (halves) Status: Confirmed ** Tags: sts ** Also affects: pacemaker (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu Xenial) Status: New => Confirmed ** Changed in: pacemaker (Ubuntu) Status: Confirmed => Fix Released ** Changed in: pacemaker (Ubuntu Xenial) Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves) -- 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/1819046 Title: Systemd unit file reads settings from wrong path Status in pacemaker package in Ubuntu: Fix Released Status in pacemaker source package in Xenial: Confirmed Bug description: [Impact] Systemd Unit file doesn't read any settings by default [Description] The unit file shipped with the Xenial pacemaker package tries to read environment settings from /etc/sysconfig/ instead of /etc/default/. The result is that settings defined in /etc/default/pacemaker are not effective. Since the /etc/default/pacemaker file is created with default values when the pacemaker package is installed, we should source that in the systemd unit file. [Test Case] 1) Deploy a Xenial container: $ lxc launch ubuntu:xenial pacemaker 2) Update container and install pacemaker: root@pacemaker:~# apt update && apt install pacemaker -y 3) Check the systemd unit file for the "EnvironmentFile" option: root@pacemaker:~# systemctl cat pacemaker | grep EnvironmentFile EnvironmentFile=-/etc/sysconfig/pacemaker EnvironmentFile=-/etc/sysconfig/sbd [Regression Potential] The regression potential for this should be very low, since the configuration file is already being created by default and other systemd unit files are using the /etc/default config. In case the file doesn't exist or the user removed it, the "-" prefix will gracefully ignore the missing file according to the systemd.exec manual [0]. Nonetheless, the new package will be tested with autopkgtests and the fix will be validated in a reproduction environment. [0] https://www.freedesktop.org/software/systemd/man/systemd.exec.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1819046/+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 1815624] Re: PostGIS DoS vulnerability in Trusty and Xenial
** Information type changed from Private Security to Public Security ** Also affects: postgis (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: postgis (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: postgis (Ubuntu) Status: New => Fix Released ** Changed in: postgis (Ubuntu Trusty) Status: New => Confirmed ** Changed in: postgis (Ubuntu Xenial) Status: New => Confirmed -- 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/1815624 Title: PostGIS DoS vulnerability in Trusty and Xenial Status in postgis package in Ubuntu: Fix Released Status in postgis source package in Trusty: Confirmed Status in postgis source package in Xenial: Confirmed Bug description: PostGIS < 2.3.3 is vulberable. In Ubuntu Trusty and Xenial Postgres can be DoSed via PostGIS. Please upgrade packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgis/+bug/1815624/+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 1666203] Re: pam_tty_audit failed in pam_open_session
This bug was fixed in the package pam - 1.1.8-3.6ubuntu3 --- pam (1.1.8-3.6ubuntu3) cosmic; urgency=medium * debian/patches-applied/fix-pam_tty_audit.patch: (LP: #1666203) Fix pam_tty_audit log_passwd support and regression. -- Eric Desrochers Thu, 28 Feb 2019 01:20:35 + ** Changed in: pam (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/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Fix Released Status in pam source package in Xenial: In Progress Status in pam source package in Bionic: Fix Released Status in pam source package in Cosmic: Fix Released Status in pam package in Debian: Fix Released Bug description: [Impact] * Kernel keystroke auditing via pam_tty_audit.so not working * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. [Test Case] 1) Open a shell & escalate to root 2) Update /etc/pam.d/common-session & /etc/pam.d/common-session-noninteractive and add the following line directly after the line: "session required pam_unix.so": "session required pam_tty_audit.so enable=*" 3) Start a second new shell session on the box and type a variety of commands 4) Exit the second shell session to flush the buffer? 5) In the root shell run "aureport -tty -i". The output should show the commands run in the other shell. [Regression Potential] * Low, we are simply including the missing header file and copy the old status as initialization of new. The fix is already found/part of Debian and Disco. [Pending SRU] All regressions found in Bionic and Cosmic looks like long standing ADT failure. Nothing has been introduce by this particular SRU. [Other Info] # Upstream fix: https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee # git describe --contains c5f829931a22c65feffee16570efdae036524bee Linux-PAM-1_2_0~75 # rmadision pam => pam | 1.1.8-1ubuntu2.2 | trusty-updates | source => pam | 1.1.8-3.2ubuntu2 | xenial | source => pam | 1.1.8-3.2ubuntu2.1 | xenial-updates | source => pam | 1.1.8-3.6ubuntu2 | bionic | source => pam | 1.1.8-3.6ubuntu2 | cosmic | source pam | 1.3.1-5ubuntu1 | disco| source [Original Description] Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHAN
[Group.of.nepali.translators] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session
This bug was fixed in the package pam - 1.1.8-3.6ubuntu2.18.04.1 --- pam (1.1.8-3.6ubuntu2.18.04.1) bionic; urgency=medium * debian/patches-applied/fix-pam_tty_audit.patch: (LP: #1666203) Fix pam_tty_audit log_passwd support and regression. -- Eric Desrochers Wed, 27 Feb 2019 14:26:50 + ** Changed in: pam (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/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Fix Released Status in pam source package in Xenial: In Progress Status in pam source package in Bionic: Fix Released Status in pam source package in Cosmic: Fix Released Status in pam package in Debian: Fix Released Bug description: [Impact] * Kernel keystroke auditing via pam_tty_audit.so not working * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. [Test Case] 1) Open a shell & escalate to root 2) Update /etc/pam.d/common-session & /etc/pam.d/common-session-noninteractive and add the following line directly after the line: "session required pam_unix.so": "session required pam_tty_audit.so enable=*" 3) Start a second new shell session on the box and type a variety of commands 4) Exit the second shell session to flush the buffer? 5) In the root shell run "aureport -tty -i". The output should show the commands run in the other shell. [Regression Potential] * Low, we are simply including the missing header file and copy the old status as initialization of new. The fix is already found/part of Debian and Disco. [Pending SRU] All regressions found in Bionic and Cosmic looks like long standing ADT failure. Nothing has been introduce by this particular SRU. [Other Info] # Upstream fix: https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee # git describe --contains c5f829931a22c65feffee16570efdae036524bee Linux-PAM-1_2_0~75 # rmadision pam => pam | 1.1.8-1ubuntu2.2 | trusty-updates | source => pam | 1.1.8-3.2ubuntu2 | xenial | source => pam | 1.1.8-3.2ubuntu2.1 | xenial-updates | source => pam | 1.1.8-3.6ubuntu2 | bionic | source => pam | 1.1.8-3.6ubuntu2 | cosmic | source pam | 1.3.1-5ubuntu1 | disco| source [Original Description] Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm
[Group.of.nepali.translators] [Bug 1759188] Re: [8086:3e92] display becomes blank after S3
** Changed in: hwe-next 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/1759188 Title: [8086:3e92] display becomes blank after S3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: [Impact] The display becomes black after S3 with the following error messages. [ 38.304449] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 0050 w(1) [ 38.304462] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK on first message, retry [ 38.306726] [drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpd] NAK for addr: 0050 w(1) [ 38.306733] [drm:drm_do_probe_ddc_edid [drm]] drm: skipping non-existent adapter i915 gmbus dpd [ 38.311251] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode HDMI ID: DP-HDMI ADAPTOR\004 (err 0) [ 38.313538] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode adaptor ID: 44 (err 0) [ 38.313554] [drm:intel_hdmi_set_edid [i915]] DP dual mode adaptor (type 1 HDMI) detected (max TMDS clock: 165000 kHz) [ 38.313557] [drm:drm_helper_hpd_irq_event [drm_kms_helper]] [CONNECTOR:115:HDMI-A-1] status updated from disconnected to disconnected [Fix] This commit pointed out by Timo fixes the issue. [Regression Potential] Should be low, although the change applies broadly. From the patch description, it explains it should be safe. > This workaround was designed to minimize the impact only > to save the bad case with that link rates. But HW engineers > indicated that it should be safe to apply broadly, although > they were expecting the DPLL0 link rate to be unchanged on > runtime. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759188/+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 1730544] Re: AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC
** Changed in: linux (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: hwe-next Status: Triaged => 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/1730544 Title: AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Won't Fix Status in linux-oem source package in Xenial: Fix Released Bug description: From vendor's suggestion, there are some patches in v4.14-rc6 are required to enable the 2 NICs 417a3ae net: aquantia: Bad udp rate on default interrupt coalescing b82ee71 net: aquantia: Enable coalescing management via ethtool interface 6849540 net: aquantia: mmio unmap was not performed on driver removal 4c8bb60 net: aquantia: Limit number of MSIX irqs to the number of cpus 93d87b8 net: aquantia: Fixed transient link up/down/up notification 5d8d84e net: aquantia: Add queue restarts stats counter 65e665e net: aquantia: Reset nic statistics on interface up/down And to avoid conflict, cherry pick 2 more commits 3aec641 aquantia: Fix Tx queue hangups 65e665e net: aquantia: Reset nic statistics on interface up/down To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1730544/+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 1806818] Re: Fix Intel I210 doesn't work when ethernet cable gets plugged
** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux-oem (Ubuntu Xenial) Status: New => 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/1806818 Title: Fix Intel I210 doesn't work when ethernet cable gets plugged Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Bug description: [Impact] Plugging ethernet cable cannot wake up Intel I210 when it's runtime suspended. It's because the PME is not enabled. [Fix] PCI core doesn't enable PME because the driver explicitly saves its PCI state before runtime suspend routine. Don't save PCI state fixes the issue. [Test] PME is correctly enabled, and cable plugging starts to work. [Regression Potential] Minimal. The fix limits to on device, and it's specific to runtime power management. Other functionalities are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806818/+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 1742094] Re: [16.04][classic] Redpine: wowlan feature doesn't work
** Changed in: hwe-next
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/1742094
Title:
[16.04][classic] Redpine: wowlan feature doesn't work
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
Steps to reproduce:
1. Ensure WoWLAN is enabled in BIOS.
2. Initiate connection to an AP (using nmcli)
3. Configure the device for WoWLAN, run the command:
$ sudo iw phy phy0 wowlan enable magic-packet
4. Enter S5/S4/S3 (using poweroff, etc.)
5. From another computer on the same network run the following command:
$ wakeonlan {mac} (in my case `wakeonlan 00:23:a7:ec:b4:04`)
Expected result: the device starts/resume
This bug is only for tracking purporse, please do not triage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1742094/+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 1785033] Re: GRUB needs to support 64-bit efi linear frame buffer address
** Changed in: hwe-next Status: In Progress => 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/1785033 Title: GRUB needs to support 64-bit efi linear frame buffer address Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in grub2 source package in Trusty: Fix Released Status in grub2-signed source package in Trusty: Fix Released Status in grub2 source package in Xenial: Fix Released Status in grub2-signed source package in Xenial: Fix Released Status in grub2 source package in Bionic: Fix Released Status in grub2-signed source package in Bionic: Fix Released Status in grub2 source package in Cosmic: Fix Released Status in grub2-signed source package in Cosmic: Fix Released Bug description: [Rationale] More firmwares support above 4G mmio configureation and the EFI Graphics Output Protocol can return a 64-bit linear frame buffer address have been implemented in some firmware/BIOS. Grub2 currently only pass 32-bit framebuffer base to kernel. The Linux kernel has already added support to handle 64-bit linear framebuffer address in the efifb driver now. So GRUB2 should support 64-bit EFI linear frame buffer address. [Impact] Some machines block booting with firmware/bios implemented 64-bit EFI linear frame buffer address,due to Grub passing incorrect(only 32-bit) EFI linear frame buffer. [Test cases] Need Bios/Firmware support, 1) Make sure the machine with the Bios implemented 64-bit EFI linear frame buffer address. some machine need to enable above 4G mmio on bios setup menu. 2) Boot up. [Solution] A patch has been committed and accepted by maintainer http://git.savannah.gnu.org/cgit/grub.git/commit/?id=886edba8770ccbc3def0af2a7d6b346d00d0af2f [Regression Potential] Minimal, it's unlikely completing the whole framebuffer address will affect those which hasn't used above 32-bits framebuffer address. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1785033/+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 1814651] Re: linux-aws: 4.4.0-1077.87 -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 => Fix Released ** 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 ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1814647 - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 06. March 2019 16:33 UTC + phase: Testing + phase-changed: Thursday, 07. March 2019 15:24 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-proposed: Pending -- ready for review + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + snap-release-to-beta: Pending -- snap not in beta channel + snap-release-to-edge: Pending -- snap not in edge channel + verification-testing: Pending -- Ready -- 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/1814651 Title: linux-aws: 4.4.0-1077.87 -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 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: Fix Released 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: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1814647 phase: Testing phase-changed: Thursday, 07. March 2019 15:24 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 snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Pending -- Ready To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814651/+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 1814654] Re: linux-kvm: 4.4.0-1041.47 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1814647 phase: Testing phase-changed: Tuesday, 26. February 2019 14:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - 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/1814654 Title: linux-kvm: 4.4.0-1041.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1814647 phase: Testing phase-changed: Tuesday, 26. February 2019 14:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814654/+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 1814655] Re: linux-raspi2: 4.4.0-1104.112 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1814647 - phase: Ready for Testing - phase-changed: Saturday, 02. March 2019 08:30 UTC + phase: Holding before Release + phase-changed: Thursday, 07. March 2019 15:24 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release -- 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/1814655 Title: linux-raspi2: 4.4.0-1104.112 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released 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: 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1814647 phase: Holding before Release phase-changed: Thursday, 07. March 2019 15:24 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814655/+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 1814657] Re: linux-snapdragon: 4.4.0-1108.113 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1814647 - phase: Ready for Testing - phase-changed: Saturday, 02. March 2019 08:38 UTC + phase: Holding before Release + phase-changed: Thursday, 07. March 2019 14:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release -- 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/1814657 Title: linux-snapdragon: 4.4.0-1108.113 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released 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: 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1814647 phase: Holding before Release phase-changed: Thursday, 07. March 2019 14:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814657/+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 1738164] Re: [snap] U2F doesn't work with yubikey
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released ** No longer affects: chromium-browser (Ubuntu Xenial) ** No longer affects: chromium-browser (Ubuntu Bionic) ** No longer affects: chromium-browser (Ubuntu Cosmic) -- 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/1738164 Title: [snap] U2F doesn't work with yubikey Status in chromium-browser package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Xenial: Confirmed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Confirmed Bug description: (initially reported by Daniel at https://forum.snapcraft.io/t/call- for-testing-chromium-62-0-3202-62/2569/50) « U2F (Universal 2nd Factor) isn’t working when signing into my gmail account trying to use my yubikey. This is a USB device which IIRC chromium needs bidirectional communication with. » This requires investigation, but the yubikey I have is too old and doesn't support U2F. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+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 1818996] Re: auth.conf.d directory missing
** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) 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/1818996 Title: auth.conf.d directory missing Status in apt package in Ubuntu: New Status in apt source package in Trusty: New Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: New Bug description: [Impact] apt in disco and the current set of SRUs introduce support for .conf snippets in auth.conf.d, but accidentally did not introduce the auth.conf.d directory, making it hard to discover if support for it exists, and requiring users to create the dir if it is missing - that's bad UX. [Test case] Install apt, make sure /etc/apt/auth.conf.d exists [Regression potential] It's just a directory, what could possibly go wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1818996/+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 1813346] Re: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic
This bug was fixed in the package cloud-init - 18.5-21-g8ee294d5-0ubuntu1~18.04.1 --- cloud-init (18.5-21-g8ee294d5-0ubuntu1~18.04.1) bionic; urgency=medium * New upstream snapshot. (LP: #1813346) - opennebula: also exclude epochseconds from changed environment vars - systemd: Render generator from template to account for system differences. [Robert Schweikert] - sysconfig: On SUSE, use STARTMODE instead of ONBOOT [Robert Schweikert] - flake8: use ==/!= to compare str, bytes, and int literals [Paride Legovini] cloud-init (18.5-17-gd1a2fe73-0ubuntu1~18.04.1) bionic; urgency=medium * New upstream snapshot. - opennebula: exclude EPOCHREALTIME as known bash env variable with a delta - tox: fix disco httpretty dependencies for py37 - run-container: uncomment baseurl in yum.repos.d/*.repo when using a proxy [Paride Legovini] - lxd: install zfs-linux instead of zfs meta package [Johnson Shi] - net/sysconfig: do not write a resolv.conf file with only the header. [Robert Schweikert] - net: Make sysconfig renderer compatible with Network Manager. [Eduardo Otubo] - cc_set_passwords: Fix regex when parsing hashed passwords [Marlin Cremers] - net: Wait for dhclient to daemonize before reading lease file [Jason Zions] - [Azure] Increase retries when talking to Wireserver during metadata walk [Jason Zions] - Add documentation on adding a datasource. - doc: clean up some datasource documentation. - ds-identify: fix wrong variable name in ovf_vmware_transport_guestinfo. - Scaleway: Support ssh keys provided inside an instance tag. [PORTE Loïc] - OVF: simplify expected return values of transport functions. - Vmware: Add support for the com.vmware.guestInfo OVF transport. - HACKING.rst: change contact info to Josh Powers - Update to pylint 2.2.2. - Release 18.5 - tests: add Disco release [Joshua Powers] - net: render 'metric' values in per-subnet routes - write_files: add support for appending to files. [James Baxter] - config: On ubuntu select cloud archive mirrors for armel, armhf, arm64. - dhclient-hook: cleanups, tests and fix a bug on 'down' event. - NoCloud: Allow top level 'network' key in network-config. - ovf: Fix ovf network config generation gateway/routes - azure: detect vnet migration via netlink media change event [Tamilmani Manoharan] - Azure: fix copy/paste error in error handling when reading azure ovf. [Adam DePue] - tests: fix incorrect order of mocks in test_handle_zfs_root. - doc: Change dns_nameserver property to dns_nameservers. [Tomer Cohen] - OVF: identify label iso9660 filesystems with label 'OVF ENV'. - logs: collect-logs ignore instance-data-sensitive.json on non-root user - net: Ephemeral*Network: add connectivity check via URL - azure: _poll_imds only retry on 404. Fail on Timeout - resizefs: Prefix discovered devpath with '/dev/' when path does not exist [Igor Galić] - azure: retry imds polling on requests.Timeout - azure: Accept variation in error msg from mount for ntfs volumes [Jason Zions] - azure: fix regression introduced when persisting ephemeral dhcp lease [Aswin Rajamannar] - azure: add udev rules to create cloud-init Gen2 disk name symlinks - tests: ec2 mock missing httpretty user-data and instance-identity routes - azure: remove /etc/netplan/90-hotplug-azure.yaml when net from IMDS - azure: report ready to fabric after reprovision and reduce logging [Aswin Rajamannar] - query: better error when missing read permission on instance-data - instance-data: fallback to instance-data.json if sensitive is absent. - docs: remove colon from network v1 config example. [Tomer Cohen] - Add cloud-id binary to packages for SUSE [Jason Zions] - systemd: On SUSE ensure cloud-init.service runs before wicked [Robert Schweikert] - update detection of openSUSE variants [Robert Schweikert] - azure: Add apply_network_config option to disable network from IMDS - Correct spelling in an error message (udevadm). [Katie McLaughlin] - tests: meta_data key changed to meta-data in ec2 instance-data.json - tests: fix kvm integration test to assert flexible config-disk path - tools: Add cloud-id command line utility - instance-data: Add standard keys platform and subplatform. Refactor ec2. - net: ignore nics that have "zero" mac address. - tests: fix apt_configure_primary to be more flexible - Ubuntu: update sources.list to comment out deb-src entries. -- Chad Smith Mon, 28 Jan 2019 20:25:39 -0700 ** Changed in: cloud-init (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: cloud-init (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, w
[Group.of.nepali.translators] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker
Verification tests completed successfully with the Xenial kernel in -proposed. ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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/1814647 Title: linux: 4.4.0-143.169 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial) derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 (linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Tuesday, 26. February 2019 14:24 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814647/+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 1802979] Re: journald log driver does not support reading
This bug was fixed in the package docker.io - 18.09.2-0ubuntu1~18.10.1 --- docker.io (18.09.2-0ubuntu1~18.10.1) cosmic; urgency=medium * Backport to 18.10 (LP: #1815683). -- Michael Hudson-Doyle Wed, 13 Feb 2019 13:25:20 +1300 ** Changed in: docker.io (Ubuntu Cosmic) 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/1802979 Title: journald log driver does not support reading Status in docker.io package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in docker.io source package in Bionic: New Status in docker.io source package in Cosmic: Fix Released Bug description: I can't get logs out of containers that use journald using the `docker logs` command. ``` $ docker logs fa95590f3c6b Error response from daemon: configured logging driver does not support reading ``` The journald logging driver usually supports reading logs. According to this issue on github (https://github.com/moby/moby/issues/31404) it only works if the binary is properly linked. The docker binary from this package doesn't seem to support it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1802979/+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 1815683] Re: update to docker 18.09.2
This bug was fixed in the package docker.io - 18.09.2-0ubuntu1~18.10.1 --- docker.io (18.09.2-0ubuntu1~18.10.1) cosmic; urgency=medium * Backport to 18.10 (LP: #1815683). -- Michael Hudson-Doyle Wed, 13 Feb 2019 13:25:20 +1300 ** Changed in: docker.io (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/1815683 Title: update to docker 18.09.2 Status in docker.io package in Ubuntu: Fix Released Status in docker.io source package in Xenial: Fix Committed Status in docker.io source package in Bionic: Fix Committed Status in docker.io source package in Cosmic: Fix Released Bug description: We should update to docker.io 18.09.2 in disco, cosmic, bionic, xenial. [test case] The autopkgtests per https://wiki.ubuntu.com/DockerUpdates. [regression potential] https://wiki.ubuntu.com/DockerUpdates again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1815683/+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 1813346] Re: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic
This bug was fixed in the package cloud-init - 18.5-21-g8ee294d5-0ubuntu1~18.10.1 --- cloud-init (18.5-21-g8ee294d5-0ubuntu1~18.10.1) cosmic; urgency=medium * New upstream snapshot. (LP: #1813346) - opennebula: also exclude epochseconds from changed environment vars - systemd: Render generator from template to account for system differences. [Robert Schweikert] - sysconfig: On SUSE, use STARTMODE instead of ONBOOT [Robert Schweikert] - flake8: use ==/!= to compare str, bytes, and int literals [Paride Legovini] cloud-init (18.5-17-gd1a2fe73-0ubuntu1~18.10.1) cosmic; urgency=medium * New upstream snapshot. - opennebula: exclude EPOCHREALTIME as known bash env variable with a delta - tox: fix disco httpretty dependencies for py37 - run-container: uncomment baseurl in yum.repos.d/*.repo when using a proxy [Paride Legovini] - lxd: install zfs-linux instead of zfs meta package [Johnson Shi] - net/sysconfig: do not write a resolv.conf file with only the header. [Robert Schweikert] - net: Make sysconfig renderer compatible with Network Manager. [Eduardo Otubo] - cc_set_passwords: Fix regex when parsing hashed passwords [Marlin Cremers] - net: Wait for dhclient to daemonize before reading lease file [Jason Zions] - [Azure] Increase retries when talking to Wireserver during metadata walk [Jason Zions] - Add documentation on adding a datasource. - doc: clean up some datasource documentation. - ds-identify: fix wrong variable name in ovf_vmware_transport_guestinfo. - Scaleway: Support ssh keys provided inside an instance tag. [PORTE Loïc] - OVF: simplify expected return values of transport functions. - Vmware: Add support for the com.vmware.guestInfo OVF transport. - HACKING.rst: change contact info to Josh Powers - Update to pylint 2.2.2. - Release 18.5 - tests: add Disco release [Joshua Powers] - net: render 'metric' values in per-subnet routes - write_files: add support for appending to files. [James Baxter] - config: On ubuntu select cloud archive mirrors for armel, armhf, arm64. - dhclient-hook: cleanups, tests and fix a bug on 'down' event. - NoCloud: Allow top level 'network' key in network-config. - ovf: Fix ovf network config generation gateway/routes - azure: detect vnet migration via netlink media change event [Tamilmani Manoharan] - Azure: fix copy/paste error in error handling when reading azure ovf. [Adam DePue] - tests: fix incorrect order of mocks in test_handle_zfs_root. - doc: Change dns_nameserver property to dns_nameservers. [Tomer Cohen] - OVF: identify label iso9660 filesystems with label 'OVF ENV'. - logs: collect-logs ignore instance-data-sensitive.json on non-root user - net: Ephemeral*Network: add connectivity check via URL - azure: _poll_imds only retry on 404. Fail on Timeout - resizefs: Prefix discovered devpath with '/dev/' when path does not exist [Igor Galić] - azure: retry imds polling on requests.Timeout - azure: Accept variation in error msg from mount for ntfs volumes [Jason Zions] - azure: fix regression introduced when persisting ephemeral dhcp lease [Aswin Rajamannar] - azure: add udev rules to create cloud-init Gen2 disk name symlinks - tests: ec2 mock missing httpretty user-data and instance-identity routes - azure: remove /etc/netplan/90-hotplug-azure.yaml when net from IMDS - azure: report ready to fabric after reprovision and reduce logging [Aswin Rajamannar] - query: better error when missing read permission on instance-data - instance-data: fallback to instance-data.json if sensitive is absent. - docs: remove colon from network v1 config example. [Tomer Cohen] - Add cloud-id binary to packages for SUSE [Jason Zions] - systemd: On SUSE ensure cloud-init.service runs before wicked [Robert Schweikert] - update detection of openSUSE variants [Robert Schweikert] - azure: Add apply_network_config option to disable network from IMDS - Correct spelling in an error message (udevadm). [Katie McLaughlin] -- Chad Smith Mon, 28 Jan 2019 20:19:18 -0700 ** Changed in: cloud-init (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/1813346 Title: sru cloud-init (18.4.0 update to 18.5-21-g8ee294d5) Xenial, Bionic, Cosmic Status in cloud-init package in Ubuntu: Confirmed Status in cloud-init source package in Xenial: Fix Committed Status in cloud-init source package in Bionic: Fix Committed Status in cloud-init source package in Cosmic: Fix Released Bug description: == Begin SRU Template == [Impact] This release sports both bug-f
