[Group.of.nepali.translators] [Bug 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode
** Changed in: oem-priority 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/1728547 Title: SRU: Add support for keeping the dGPU on in power saving mode Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Fix Released Status in ubuntu-drivers-common source package in Zesty: Fix Committed Status in ubuntu-drivers-common source package in Artful: Fix Released Bug description: SRU Request: [Impact] Some systems don't play well when the dGPU is disabled. It should still be possible to use the Intel iGPU without disabling the dGPU. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common" 2) Make sure the nvidia packages are installed, and enable power saving mode: sudo prime-select intel 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Install the mesa-utils package: sudo apt install mesa-utils 5) Check the output of the following command (which should mention Intel): glxinfo | grep OpenGL [Regression Potential] Low, as the feature is disabled by default. This is only for hardware specific workarounds. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1728547/+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 997217] Re: salsauthd maxes cpu
Ok, trusty isn't affected because the loop there has an exit clause:
+ ret = read(s, rbuf+rc, sizeof(rbuf)-rc);
+ if ( ret<0 ) {
+ rc = ret;
+ break;
+ } else {
+ if (ret == 0) {
+ loopc += 1;
+ } else {
+ loopc = 0;
+ }
+ if (loopc > sizeof(rbuf)) { // arbitrary chosen value
+ break;
+ }
That comes from trusty's patch named 0034-fix_dovecot_authentication.patch. So
trusty does loop for a bit (sizeof(rbuf) is 1000), but won't get stuck. Someone
added the loop counter as a safety net, but didn't change the "ret<0" check
into "ret<=0" which would also have fixed this.
In precise, that same patch (0034) adds the loop, but *without* an exit
clause, hence this bug.
Xenial is interesting. Upstream at some point adopted the patch that
does *NOT* exit the loop, but the code is so similar that someone
decided the patch from the package was already applied and dropped it
from the package, reintroducing the bug.
To add to the confusion, in xenial that patch file was super slightly renamed
from 0034_fix_dovecot_authentication.patch to
0034-fix_dovecot_authentication.patch (can you spot what changed?) and got
totally different contents:
--- cyrus-sasl2.orig/lib/checkpw.c
+++ cyrus-sasl2/lib/checkpw.c
@@ -587,16 +587,14 @@ static int read_wait(int fd, unsigned de
/* Timeout. */
errno = ETIMEDOUT;
return -1;
- case +1:
- if (FD_ISSET(fd, )) {
- /* Success, file descriptor is readable. */
- return 0;
- }
- return -1;
case -1:
if (errno == EINTR || errno == EAGAIN)
continue;
default:
+ if (FD_ISSET(fd, )) {
+ /* Success, file descriptor is readable. */
+ return 0;
+ }
/* Error catch-all. */
return -1;
}
>From bionic onwards, the upstream version has the loop with no loop
counter, but it checks read()'s result for <= 0, not just 0, so it's
fixed there.
Bottom line, only xenial is currently affected (and precise, but precise
is EOL).
** Changed in: cyrus-sasl2 (Ubuntu Trusty)
Status: Triaged => 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/997217
Title:
salsauthd maxes cpu
Status in cyrus-sasl2 package in Ubuntu:
Fix Released
Status in cyrus-sasl2 source package in Precise:
Won't Fix
Status in cyrus-sasl2 source package in Trusty:
Invalid
Status in cyrus-sasl2 source package in Xenial:
Triaged
Bug description:
[Impact]
The rimap authentication mechanism in saslauthd can hit a condition
where it will start spinning and using all available CPU. This
condition can be easily encountered when an authentication is
happening and the imap service is being restarted.
Furthermore, the saslauthd child process that picked up that
authentication request and that is spinning now won't be reaped nor
can it service further requests. If all children are left in this
state, the authentication service as a whole won't be working anymore.
[Test Case]
This test can be performed in a LXD or VM.
* install the needed packages. mail-stack-delivery is used to have an
imap server available on localhost that needs no further
configuration. Accept the defaults for all debconf prompts:
sudo apt update
sudo apt install sasl2-bin mail-stack-delivery
* set the password "ubuntu" for the ubuntu user
echo ubuntu:ubuntu | sudo chpasswd
* start saslauthd like this, with just one child:
sudo /usr/sbin/saslauthd -a rimap -O localhost -r -n 1
* restart dovecot
sudo service dovecot restart
* test saslauthd authentication:
$ sudo testsaslauthd -u ubuntu -p ubuntu
0: OK "Success."
* Now let's break it. In one terminal watch the output of top:
top
* in another terminal, run the following:
sudo testsaslauthd -u ubuntu -p ubuntu & sleep 1; sudo service dovecot stop
* observe in the "top" terminal that saslauthd is consuming a lot of
cpu. If that's not happening, try starting dovecot again and adjusting
the sleep value in the previous test command, but 1s was enough in all
my runs.
* start dovecot and repeat the authentication request. Since the only
saslauthd child is now spinning, this will block:
sudo service dovecot start
$ sudo testsaslauthd -u ubuntu -p ubuntu
[Regression Potential]
* discussion of how regressions are most likely to manifest as a
result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the
[Group.of.nepali.translators] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
This bug was fixed in the package systemd - 229-4ubuntu21.5 --- systemd (229-4ubuntu21.5) xenial; urgency=medium [ Dimitri John Ledkov ] * systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * hwdb: update micmute on Dell laptops. (LP: #1738153) * hwdb: Use wlan keycode for all Dell systems. (LP: #1762385) * units: Disable journald Watchdog (LP: #1773148) [ Mauricio Faria de Oliveira ] * core: Fix for service to enter the 'failed' state (rather than 'inactive') after it repeatedly fails restart. (LP: #1795658) [ Dimitri John Ledkov ] * Disable dh_installinit generation of tmpfiles for the systemd package. (LP: #1748147) -- Dimitri John Ledkov Mon, 08 Oct 2018 16:10:42 +0100 ** Changed in: systemd (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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
This bug was fixed in the package systemd - 229-4ubuntu21.5 --- systemd (229-4ubuntu21.5) xenial; urgency=medium [ Dimitri John Ledkov ] * systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * hwdb: update micmute on Dell laptops. (LP: #1738153) * hwdb: Use wlan keycode for all Dell systems. (LP: #1762385) * units: Disable journald Watchdog (LP: #1773148) [ Mauricio Faria de Oliveira ] * core: Fix for service to enter the 'failed' state (rather than 'inactive') after it repeatedly fails restart. (LP: #1795658) [ Dimitri John Ledkov ] * Disable dh_installinit generation of tmpfiles for the systemd package. (LP: #1748147) -- Dimitri John Ledkov Mon, 08 Oct 2018 16:10:42 +0100 ** Changed in: systemd (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/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in debhelper source package in Xenial: Won't Fix Status in rsyslog source package in Xenial: Invalid Status in systemd source package in Xenial: Fix Released Status in debhelper source package in Artful: Won't Fix Status in rsyslog source package in Artful: Invalid Status in systemd source package in Artful: Won't Fix Status in debhelper source package in Bionic: Won't Fix Status in rsyslog source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Released Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if rsyslog is installed (default) [Resolution] Ensure that dh_installinit does not "helpfully" generate partial systemd-tmpfiles snippets in systemd package postinst. Ensure that a generic systemd-tmpfiles call is done in systemd postinst, which takes into account /all/ configurations, not just some. [Regression Potential] * This fix was already tested in bionic and works well there. * Bad autogenerated calls to systemd-tmpfiles are removed from systemd postinst, and replaced by a call that takes all configs into account, thus this is a very safe thing to do - and simply repeats what is done on boot, thus is as safe as it gets. [Test Case] 1. Launch xenila container 2. ls -latr /var 3. apt install --reinstall systemd 4. ls -latr /var The ownership, group and permissions for /var/log should remain the same. To manage notifications about this bug go to: https://bugs.launchpad.net/debhelper/+bug/1748147/+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 1738153] Re: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial
This bug was fixed in the package systemd - 229-4ubuntu21.5 --- systemd (229-4ubuntu21.5) xenial; urgency=medium [ Dimitri John Ledkov ] * systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * hwdb: update micmute on Dell laptops. (LP: #1738153) * hwdb: Use wlan keycode for all Dell systems. (LP: #1762385) * units: Disable journald Watchdog (LP: #1773148) [ Mauricio Faria de Oliveira ] * core: Fix for service to enter the 'failed' state (rather than 'inactive') after it repeatedly fails restart. (LP: #1795658) [ Dimitri John Ledkov ] * Disable dh_installinit generation of tmpfiles for the systemd package. (LP: #1748147) -- Dimitri John Ledkov Mon, 08 Oct 2018 16:10:42 +0100 ** Changed in: systemd (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/1738153 Title: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial Status in OEM Priority Project: Confirmed Status in OEM Priority Project xenial series: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Won't Fix Bug description: [Impact] dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 0x100150, so need to add a new mapping for it. related commit: https://github.com/systemd/systemd/pull/5012 [Test Case] 1. install the udev package which applied patch. 2. check if Microphone mute hotkey works. 3. if it not works, please provide the log of evtest. [Regression Potential] low regression potential, because it just add one more mapping. also affect: LP: #1736352 LP: #1740080 LP: #1734609 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1738153/+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 1762385] Re: dell_wmi: Unknown key codes
This bug was fixed in the package systemd - 229-4ubuntu21.5 --- systemd (229-4ubuntu21.5) xenial; urgency=medium [ Dimitri John Ledkov ] * systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * hwdb: update micmute on Dell laptops. (LP: #1738153) * hwdb: Use wlan keycode for all Dell systems. (LP: #1762385) * units: Disable journald Watchdog (LP: #1773148) [ Mauricio Faria de Oliveira ] * core: Fix for service to enter the 'failed' state (rather than 'inactive') after it repeatedly fails restart. (LP: #1795658) [ Dimitri John Ledkov ] * Disable dh_installinit generation of tmpfiles for the systemd package. (LP: #1748147) -- Dimitri John Ledkov Mon, 08 Oct 2018 16:10:42 +0100 ** Changed in: systemd (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/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+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 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate
This bug was fixed in the package systemd - 229-4ubuntu21.5 --- systemd (229-4ubuntu21.5) xenial; urgency=medium [ Dimitri John Ledkov ] * systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * hwdb: update micmute on Dell laptops. (LP: #1738153) * hwdb: Use wlan keycode for all Dell systems. (LP: #1762385) * units: Disable journald Watchdog (LP: #1773148) [ Mauricio Faria de Oliveira ] * core: Fix for service to enter the 'failed' state (rather than 'inactive') after it repeatedly fails restart. (LP: #1795658) [ Dimitri John Ledkov ] * Disable dh_installinit generation of tmpfiles for the systemd package. (LP: #1748147) -- Dimitri John Ledkov Mon, 08 Oct 2018 16:10:42 +0100 ** Changed in: systemd (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/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * systemd aborts journald, upon watchdog expiry and generates lots of crash reports * it appears that journald is simply stuck in fsync * it has been agreed to disable watchdog timer on journald [Test Case] * watch drop-off of errors w.r.t. watchdog timer [Regression Potential] * Potentially journald does get stuck, and thus is no longer automatically restarted with a sigabrt crash. However, so far, it is not known to do that. [Other Info] * Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1773148/+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 1795658] Re: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently
This bug was fixed in the package systemd - 229-4ubuntu21.5 --- systemd (229-4ubuntu21.5) xenial; urgency=medium [ Dimitri John Ledkov ] * systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * hwdb: update micmute on Dell laptops. (LP: #1738153) * hwdb: Use wlan keycode for all Dell systems. (LP: #1762385) * units: Disable journald Watchdog (LP: #1773148) [ Mauricio Faria de Oliveira ] * core: Fix for service to enter the 'failed' state (rather than 'inactive') after it repeatedly fails restart. (LP: #1795658) [ Dimitri John Ledkov ] * Disable dh_installinit generation of tmpfiles for the systemd package. (LP: #1748147) -- Dimitri John Ledkov Mon, 08 Oct 2018 16:10:42 +0100 ** Changed in: systemd (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/1795658 Title: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently Status in systemd package in Ubuntu: Invalid Status in systemd source package in Xenial: Fix Released Bug description: [Impact] * In case a service unit has repeatedly failed to restart, it should be reported as 'failed' permanently, but currently it's instead reported as 'inactive'. * System monitoring tools that evaluate the status of systemd service units and act upon it (for example: restart service, report permanent failure) are currently misled by information in 'systemctl status .service'. * System management tools based on such information may take wrong and/or sub-optimal actions in the managed systems regarding such service units. * This systemd patch [1] directly addresses this issue (see systemd github PR #3166 [2]), and its code is still effectice in upstream systemd today, without further fixes/changes (the only changes were in doc text and the busname files that were removed, but still without further fixes to this). [Test Case] * This is copied from systemd PR #3166 [2]. * This has been tested by a customer as well, and with its system monitoring and management solution, for interoperability verification. $ cat
[Group.of.nepali.translators] [Bug 1799773] Re: Accelerate the build: Drop unused checksum generation
** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: livecd-rootfs (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/1799773 Title: Accelerate the build: Drop unused checksum generation Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: New Status in livecd-rootfs source package in Bionic: New Status in livecd-rootfs source package in Cosmic: Fix Released Bug description: [Impact] * Image builds take time * Some of the time is spent computing checksums * Those checksums are never used * Time and energy is wasted * build/(md5|sha256)sum.txt is not used by livecd-rootfs and not exposed by launchpad-buildd [Test Case] * Build images * Disable checksums * Build images * Ensure image deliverables are unchanged [Regression Potential] * Someone was using the checksums outside of launchpad-buildd; because launchpad-buildd doesn't present those artifacts * The checksums are included beside the squashfs in live-build ISOs but none of our projects use live-build to build ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1799773/+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 1649616] Re: Keystone Token Flush job does not complete in HA deployed environment
newton is EOL ** Changed in: keystone/newton Status: In Progress => Won't Fix ** Changed in: keystone/ocata 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/1649616 Title: Keystone Token Flush job does not complete in HA deployed environment Status in Ubuntu Cloud Archive: Invalid Status in Ubuntu Cloud Archive mitaka series: Fix Released Status in Ubuntu Cloud Archive newton series: Fix Released Status in Ubuntu Cloud Archive ocata series: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in OpenStack Identity (keystone) newton series: Won't Fix Status in OpenStack Identity (keystone) ocata series: Fix Released Status in puppet-keystone: Fix Released Status in tripleo: Fix Released Status in keystone package in Ubuntu: Invalid Status in keystone source package in Xenial: Fix Released Status in keystone source package in Yakkety: Fix Released Status in keystone source package in Zesty: Fix Released Bug description: [Impact] * The Keystone token flush job can get into a state where it will never complete because the transaction size exceeds the mysql galara transaction size - wsrep_max_ws_size (1073741824). [Test Case] 1. Authenticate many times 2. Observe that keystone token flush job runs (should be a very long time depending on disk) >20 hours in my environment 3. Observe errors in mysql.log indicating a transaction that is too large Actual results: Expired tokens are not actually flushed from the database without any errors in keystone.log. Only errors appear in mysql.log. Expected results: Expired tokens to be removed from the database [Additional info:] It is likely that you can demonstrate this with less than 1 million tokens as the >1 million token table is larger than 13GiB and the max transaction size is 1GiB, my token bench-marking Browbeat job creates more than needed. Once the token flush job can not complete the token table will never decrease in size and eventually the cloud will run out of disk space. Furthermore the flush job will consume disk utilization resources. This was demonstrated on slow disks (Single 7.2K SATA disk). On faster disks you will have more capacity to generate tokens, you can then generate the number of tokens to exceed the transaction size even faster. Log evidence: [root@overcloud-controller-0 log]# grep " Total expired" /var/log/keystone/keystone.log 2016-12-08 01:33:40.530 21614 INFO keystone.token.persistence.backends.sql [-] Total expired tokens removed: 1082434 2016-12-09 09:31:25.301 14120 INFO keystone.token.persistence.backends.sql [-] Total expired tokens removed: 1084241 2016-12-11 01:35:39.082 4223 INFO keystone.token.persistence.backends.sql [-] Total expired tokens removed: 1086504 2016-12-12 01:08:16.170 32575 INFO keystone.token.persistence.backends.sql [-] Total expired tokens removed: 1087823 2016-12-13 01:22:18.121 28669 INFO keystone.token.persistence.backends.sql [-] Total expired tokens removed: 1089202 [root@overcloud-controller-0 log]# tail mysqld.log 161208 1:33:41 [Warning] WSREP: transaction size limit (1073741824) exceeded: 1073774592 161208 1:33:41 [ERROR] WSREP: rbr write fail, data_len: 0, 2 161209 9:31:26 [Warning] WSREP: transaction size limit (1073741824) exceeded: 1073774592 161209 9:31:26 [ERROR] WSREP: rbr write fail, data_len: 0, 2 161211 1:35:39 [Warning] WSREP: transaction size limit (1073741824) exceeded: 1073774592 161211 1:35:40 [ERROR] WSREP: rbr write fail, data_len: 0, 2 161212 1:08:16 [Warning] WSREP: transaction size limit (1073741824) exceeded: 1073774592 161212 1:08:17 [ERROR] WSREP: rbr write fail, data_len: 0, 2 161213 1:22:18 [Warning] WSREP: transaction size limit (1073741824) exceeded: 1073774592 161213 1:22:19 [ERROR] WSREP: rbr write fail, data_len: 0, 2 Disk utilization issue graph is attached. The entire job in that graph takes from the first spike is disk util(~5:18UTC) and culminates in about ~90 minutes of pegging the disk (between 1:09utc to 2:43utc). [Regression Potential] * Not identified To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1649616/+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 1799425] Re: linux-hwe: 4.15.0-39.42~16.04.1 -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 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 -- kernel-stable-master-bug: 1799411 phase: Packaging reason: prepare-package: Package not yet uploaded prepare-package-meta: Package not yet uploaded prepare-package-signed: Package not yet uploaded + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Wednesday, 24. October 2018 17:30 UTC ** 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 -- kernel-stable-master-bug: 1799411 - phase: Packaging + phase: Uploaded reason: - prepare-package: Package not yet uploaded - prepare-package-meta: Package not yet uploaded - prepare-package-signed: Package not yet uploaded - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Wednesday, 24. October 2018 17:30 UTC + promote-to-proposed: Builds not complete -- 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/1799425 Title: linux-hwe: 4.15.0-39.42~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 upload-to-ppa 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: 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 -- kernel-stable-master-bug: 1799411 phase: Uploaded reason: promote-to-proposed: Builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799425/+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 1796634] Re: [0cf3:e007] Can't turn on BT by Wireless hotkey
** Also affects: linux-firmware (Ubuntu Cosmic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: 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/1796634 Title: [0cf3:e007] Can't turn on BT by Wireless hotkey Status in HWE Next: New Status in OEM Priority Project: New Status in Gaming Edition: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Xenial: New Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Cosmic: In Progress Bug description: [Impact] The issue has been found on new Dell laptop with DW1820 combo card(BT is [0cf3:e007]) 1) Use wireless hotkey to turn off WiFi/BT. 2) Wait 5 minutes. 3) Use wireless hotkey to turn on WiFi/BT. 4) Wifi is back, but BT is still off 5) Only reboot can recovery the BT state [Fix] Qualcomm releases a new firmware to fix it. [Regression Potential] Can't evaluate it, but from our verification and S3 stress test, there is no any issues result from the firmwares. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1796634/+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 1799736] [NEW] Restore the ability to produce core16 images
Public bug reported: [Impact] Ubuntu Core is an all-snap Ubuntu variant that we are building through cdimage. In the past there was only one core series, 16, and all the images we were building were based on that series. Thanks to that all the support for building ubuntu-core images in livecd-rootfs through ubuntu-image was only needed in later series, as all were build using devel. Currently we have two different ubuntu-core image sets based of different bases: core16 and core18 images. As a convention, we have decided that cdimage (and or other components) will be building ubuntu- core images based of the suite that the build is being run for. Since core16 is based on xenial and core18 on bionic, we have decided the following scheme: * Suite: xenial -> ubuntu-core 16 image * Suite: bionic or later -> ubuntu-core 18 image For this to work, we need to have all the needed changes in xenial and bionic. livecd-rootfs on xenial is missing all the ubuntu-image build- enablement changes, so these need to be backported. Besides that, both xenial and bionic need to get backports of the per-distro-series core- series selection. Without these fixes in xenial, no ubuntu-core 16 images can be built anymore. This is needed in case we'd have need for any security- vulnerability fix image re-releases. [Test Case] For xenial: * On a xenial system install latest xenial-proposed livecd-rootfs * Create a temporary directory and cd into it * Copy the /usr/share/livecd-rootfs/live-build/auto directory into the current directory * sudo PROJECT=ubuntu-core SUITE=xenial ARCH=amd64 PROPOSED=0 IMAGEFORMAT="ubuntu-image" lb config -> Make sure that the configured model assertion is for core16 * sudo PROJECT=ubuntu-core SUITE=xenial ARCH=amd64 PROPOSED=0 IMAGEFORMAT="ubuntu-image" lb build -> Make sure the build runs and finishes correctly * Boot test the newly created image with kvm -> Make sure the image is still bootable [Regression Potential] As part of the backport only new code is added - code that is executed in certain code paths only. Most regressions might appear in the ubuntu- core image generation, which was not available for xenial. But in case the code has been added in the wrong way, potentially this might result in livecd-rootfs not being able to generate proper classic images anymore. A run of lb config and lb build for a non ubuntu-image project is recommended. ** Affects: livecd-rootfs (Ubuntu) Importance: High Assignee: Łukasz Zemczak (sil2100) Status: Fix Released ** Affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: In Progress ** Affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: In Progress => Fix Released ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: New => Confirmed ** Branch linked: lp:~sil2100/livecd-rootfs/xenial-ui-support-and-core- suite -- 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/1799736 Title: Restore the ability to produce core16 images Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: In Progress Status in livecd-rootfs source package in Bionic: Confirmed Bug description: [Impact] Ubuntu Core is an all-snap Ubuntu variant that we are building through cdimage. In the past there was only one core series, 16, and all the images we were building were based on that series. Thanks to that all the support for building ubuntu-core images in livecd-rootfs through ubuntu-image was only needed in later series, as all were build using devel. Currently we have two different ubuntu-core image sets based of different bases: core16 and core18 images. As a convention, we have decided that cdimage (and or other components) will be building ubuntu-core images based of the suite that the build is being run for. Since core16 is based on xenial and core18 on bionic, we have decided the following scheme: * Suite: xenial -> ubuntu-core 16 image * Suite: bionic or later -> ubuntu-core 18 image For this to work, we need to have all the needed changes in xenial and bionic. livecd-rootfs on xenial is missing all the ubuntu-image build- enablement changes, so these need to be backported. Besides that, both xenial and bionic need to get backports of the per-distro-series core- series selection. Without these fixes in xenial, no ubuntu-core 16 images can be built anymore. This is needed in case we'd have
[Group.of.nepali.translators] [Bug 1792400] Re: smbd failed in host when both lxd container and host have smbd
** Changed in: samba (Ubuntu Trusty) Status: Fix Committed => 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/1792400 Title: smbd failed in host when both lxd container and host have smbd Status in samba package in Ubuntu: Fix Released Status in samba source package in Trusty: Invalid Status in samba source package in Xenial: Fix Released Bug description: [Impact] * Issue: the current init script * won't start samba related services on the host if there is a process of the same binary in a container * might on stop affect a process that it was not intended to stop * Solution: Fix init scripts to * start action to have a safer process detection with containers around * stop action to not affect unintended processes due to stale pidfiles [Test Case] * 1. Start a container * 2. Start samba in the Container (or winbind or nmbd) * 3. Start samba in the host (or winbind or nmbd) => it will not start as such a binary is already running * #2 and #3 can be switched, and then as 4. restart smbd in the host => it will shut down but not re-start Fixed: The container process should have no influence This also fixes issues where the pidfile would not be updated * install and start smbd * "Simulate" a corrupted pidfile by putting the PID of a different process in it * stop the sambd service => without the fixes this will drag down the other process you put in the pidfile Fixed: a stale pidfile entry should not let non-smbd (or winbind, nmbd) processes be affected [Regression Potential] * We tried to think of all edge cases of these start/stop actions but didn't come up with one that is broken. Aside from missing one of those cases there might be non-archive scripts that expect the old behavior. But even for thse no critical ones came to my mind so far. Worst case there'd be a combination that leads to the service no(re-)starting after the SRU - so thinking about potential cases is important. [Other Info] * n/a --- Setup: install smbd in host and lxd-container. Now restart smbd in host: service smbd restart All is OK. Problem: nmap shows "closed" on ports 139 and 445. And users cannot use smbd server in host. ● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd) Loaded: loaded (/etc/init.d/smbd; bad; vendor preset: enabled) Active: active (exited) since Die 2016-10-18 17:35:23 CEST; 2s ago Docs: man:systemd-sysv-generator(8) Process: 24218 ExecStop=/etc/init.d/smbd stop (code=exited, status=0/SUCCESS) Process: 21980 ExecReload=/etc/init.d/smbd reload (code=exited, status=0/SUCCESS) Process: 25190 ExecStart=/etc/init.d/smbd start (code=exited, status=0/SUCCESS) Okt 18 17:35:22 speedy systemd[1]: Starting LSB: start Samba SMB/CIFS daemon (smbd)... Okt 18 17:35:23 speedy smbd[25190]: * Starting SMB/CIFS daemon smbd Okt 18 17:35:23 speedy smbd[25190]:...done. Okt 18 17:35:23 speedy systemd[1]: Started LSB: start Samba SMB/CIFS daemon (smbd). ps axf | grep smbd: 25356 pts/2S+ 0:00 | \_ grep --color=auto smbd 19915 ?Ss 0:08 \_ /usr/sbin/smbd -D 19919 ?S 0:00 \_ /usr/sbin/smbd -D However, netstat -tpln | grep "smbd" returns nothing and also nmap shows "closed" on ports 139 and 445. Workaround [1]: change /etc/init.d/smbd: if ! start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/smbd -- -D ; then to if ! start-stop-daemon --start --quiet --oknodo --pidfile /var/run/samba/smbd.pid --exec /usr/sbin/smbd -- -D ; then I reported this to: https://discuss.linuxcontainers.org/t/samba-in-host-and-container/2523 apt-cache policy samba samba: Installed: 2:4.3.11+dfsg-0ubuntu0.16.04.15 Candidate: 2:4.3.11+dfsg-0ubuntu0.16.04.16 Version table: 2:4.3.11+dfsg-0ubuntu0.16.04.16 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2:4.3.11+dfsg-0ubuntu0.16.04.15 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 2:4.3.8+dfsg-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 1. https://serverfault.com/questions/810544/samba-daemon-does-not- work-as-systemd-service-but-works-in-foreground To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1792400/+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 :
[Group.of.nepali.translators] [Bug 1798706] Re: Incomplete linking with boost_regex
Bionic and later releases don't need the boost regex library thus this bug does not affect the latest releases. ** Changed in: gce-compute-image-packages (Ubuntu) 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/1798706 Title: Incomplete linking with boost_regex Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Bug description: SRU Justification = [Impact] oslogin fails on Xenial and Trusty. In auth.log we see: Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to dlopen(pam_oslogin_login.so): /lib/security/pam_oslogin_login.so: cannot open shared object file: No such file or directory Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: pam_oslogin_login.so Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM unable to dlopen(pam_oslogin_admin.so): /lib/security/pam_oslogin_admin.so: cannot open shared object file: No such file or directory Oct 17 16:35:59 davecore-oslogin sshd[10073]: PAM adding faulty module: pam_oslogin_admin.so The error message is a bit deceptive - PAM tries to load the module from the correct location, fails, and then tries the other location where it is missing. It then reports the missing error rather than the real error. symlink the module into both paths leads to a much more useful error message: Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to dlopen(pam_oslogin_login.so): /lib/security/pam_oslogin_login.so: undefined symbol: _ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE Oct 18 06:45:12 dja-202158 sshd[16554]: PAM adding faulty module: pam_oslogin_login.so Oct 18 06:45:12 dja-202158 sshd[16554]: PAM unable to dlopen(pam_oslogin_admin.so): /lib/security/pam_oslogin_admin.so: undefined symbol: _ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE [Test case] - set up GCE VM - turn on oslogin - attempt to log in [Fix] debian/patches/0002-Set-LDFLAGS-at-the-end-of-the-c-command-line-right-b.patch re-orders the link flags to link boost_regex for oslogin. However, this didn't change the flags for PAM module linking. So fix that too. [Regression Potential] - fixes a regression - limited to oslogin, and how it is linked. [Other Notes] We still see a scary list of warnings when building, but they don't seem to have an impact on the common path: dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail13put_mem_blockEPv used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail14verify_optionsEjNS_15regex_constants12_match_flagsE used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZNK5boost9re_detail31cpp_regex_traits_implementationIcE17transform_primaryEPKcS4_ used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost13match_resultsIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISB_12maybe_assignERKSF_ used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail12perl_matcherIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS_9sub_matchISC_EEENS_12regex_traitsIcNS_16cpp_regex_traitsIcE14construct_initERKNS_11basic_regexIcSJ_EENS_15regex_constants12_match_flagsE used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost11basic_regexIcNS_12regex_traitsIcNS_16cpp_regex_traitsIcE9do_assignEPKcS7_j used by debian/google-compute-engine-oslogin/lib/libnss_google-compute-engine-oslogin-1.3.1.so found in none of the libraries dpkg-shlibdeps: warning: symbol _ZN5boost9re_detail19raise_runtime_errorERKSt13runtime_error used by
[Group.of.nepali.translators] [Bug 1799401] Re: linux: 4.4.0-139.165 -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 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 1799403 (linux-aws), bug 1799404 (linux-lts-xenial) derivatives: bug 1799405 (linux-aws), bug 1799407 (linux-euclid), bug 1799408 (linux-kvm), bug 1799409 (linux-raspi2), bug 1799410 (linux-snapdragon) + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Wednesday, 24. October 2018 11:34 UTC ** 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 backports: bug 1799403 (linux-aws), bug 1799404 (linux-lts-xenial) derivatives: bug 1799405 (linux-aws), bug 1799407 (linux-euclid), bug 1799408 (linux-kvm), bug 1799409 (linux-raspi2), bug 1799410 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 24. October 2018 11:34 UTC + + -- swm properties -- + phase: 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/1799401 Title: linux: 4.4.0-139.165 -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 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 upload-to-ppa 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: 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 1799403 (linux-aws), bug 1799404 (linux-lts-xenial) derivatives: bug 1799405 (linux-aws), bug 1799407 (linux-euclid), bug 1799408 (linux-kvm), bug 1799409 (linux-raspi2), bug 1799410 (linux-snapdragon) kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 24. October 2018 11:34 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1799401/+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 1775068] Re: Volume control not working Dell XPS 27 (7760)
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Fix Committed Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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
