[Group.of.nepali.translators] [Bug 1660063] Re: chrome-gnome-shell crashed with SIGSEGV in ffi_call_unix64()
This bug was fixed in the package chrome-gnome-shell - 8-2ubuntu4 --- chrome-gnome-shell (8-2ubuntu4) zesty; urgency=medium * Add patches from Debian 8-3 (cherrypicked from upstream 8.1) to fix crashes (LP: #1660063) - array-duplicates.patch - assume-version-1.patch - dont-use-get_dbus_connection.patch -- Jeremy Bicha Thu, 23 Feb 2017 23:03:57 -0500 ** Changed in: chrome-gnome-shell (Ubuntu) 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/1660063 Title: chrome-gnome-shell crashed with SIGSEGV in ffi_call_unix64() Status in chrome-gnome-shell package in Ubuntu: Fix Released Status in chrome-gnome-shell source package in Trusty: In Progress Status in chrome-gnome-shell source package in Xenial: In Progress Status in chrome-gnome-shell source package in Yakkety: In Progress Bug description: This is happening when chromium is been closed. Get that issue with all the 8 serie --- ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: chrome-gnome-shell 8-2ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Tags: zesty third-party-packages Uname: Linux 4.9.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrome-gnome-shell/+bug/1660063/+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 1570472] Re: Set systemd as default service provider
This bug was fixed in the package puppet - 4.8.2-3ubuntu2
---
puppet (4.8.2-3ubuntu2) zesty; urgency=medium
* d/t/spec/puppet-master-passenger/zz_puppet3_compat_spec.rb: specify
to curl that 'puppet' should not be proxied.
* d/t/control: generate a certificate for puppet master if it does not
already exist, as it is needed by the tests.
* Drop:
- d/t/spec/puppet-master/install_spec.rb: generate host certificate
before attempting to use it. There is no guarantee the certificate
exist in the autopkgtest environment.
[ By generating the certificate if not present in d/t/control, we
don't need to in the spec ]
-- Nishanth Aravamudan Thu, 23 Feb
2017 17:18:09 -0800
** Changed in: puppet (Ubuntu)
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/1570472
Title:
Set systemd as default service provider
Status in puppet package in Ubuntu:
Fix Released
Status in puppet source package in Xenial:
Fix Committed
Status in puppet source package in Yakkety:
Fix Committed
Bug description:
[Impact]
* Puppet incorrectly detects the service manager on Ubuntu 16.04 and
16.10 as upstart, rather than systemd.
* Various puppet-driven commands fail as they do not use the systemd
interfaces.
[Test Case]
* # upstart is required to confuse Puppet
apt install -y puppet upstart tftpd-hpa
# fails without fix
puppet apply -e "service { 'tftpd-hpa': ensure => stopped }"
# install fixed package
# works
puppet apply -e "service { 'tftpd-hpa': ensure => stopped }"
[Regression Potential]
* Currently, puppet is unable to apply configurations to 16.04, 16.10
and 17.04 (fix is in -proposed for 17.04) when upstart is installed.
This change will make puppet correctly use systemd for service
manipulation, and I believe the likelihood of regression is low.
* The primary source of regressions would be users who have modified
their puppet installations to work around this issue. I believe they
will be generally unaffected by fixing the underlying issue.
---
AFAIK, Ubuntu has systemd as default init system since 15.04 release.
Although, puppet thinks it's still upstart.
This behavior is already fixed in upstream puppet code. Please, add this
patch to Xenial puppet package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+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 1667052] Re: linux: 4.4.0-65.86 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** 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: 1667054 derivatives: 1667056,1667058,1667061 -- swm properties -- phase: Uploaded + kernel-stable-phase-changed:Friday, 24. February 2017 02:46 UTC + kernel-stable-phase:Uploaded ** 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: 1667054 derivatives: 1667056,1667058,1667061 -- swm properties -- + boot-testing-requested: true phase: Uploaded - kernel-stable-phase-changed:Friday, 24. February 2017 02:46 UTC - kernel-stable-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/1667052 Title: linux: 4.4.0-65.86 -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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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: 1667054 derivatives: 1667056,1667058,1667061 -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667052/+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 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings
This bug was fixed in the package systemd - 231-9ubuntu3
---
systemd (231-9ubuntu3) yakkety; urgency=medium
* d/p/0001-libudev-util-change-util_replace_whitespace-to-retur.patch,
d/p/0002-udev-event-add-replace_whitespace-param-to-udev_even.patch,
d/p/0003-udev-rules-perform-whitespace-replacement-for-symlin.patch:
Cherry-pick upstream fixes from Dan Streetman to
fix by-id symlinks for devices whose IDs contain whitespace.
LP: #1647485.
-- Steve Langasek Fri, 13 Jan 2017
16:22:48 +0200
** Changed in: systemd (Ubuntu Yakkety)
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/1647485
Title:
NVMe symlinks broken by devices with spaces in model or serial strings
Status in maas-images:
Fix Released
Status in systemd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Trusty:
Fix Released
Status in systemd source package in Xenial:
Fix Released
Status in systemd source package in Yakkety:
Fix Released
Status in systemd source package in Zesty:
Fix Released
Status in systemd package in Debian:
Fix Released
Bug description:
[Impact]
After including the patch from bug 1642903, NVMe devices that include spaces
in their model or serial strings result in incorrect symlinks, e.g. if the
model string is "XYZ Corp NVMe drive" then instead of creating:
/dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
it creates:
/dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
/dev/Corp -> nvme0n1
/dev/NVMe -> nvme0n1
/dev/drive_SERIAL -> nvme0n1
This is because of the way udev handles the SYMLINK value strings; by
default, it does not do any whitespace replacement. To enable
whitespace replacement of a symlink value, the rule must also include
OPTIONS+="string_escape=replace". This is done for 'md' and 'dm'
devices in their rules. However, there are no rules that actually
want to specify multiple symlinks, and defaulting to not replacing
whitespace makes no sense; instead, the default should be to replace
all whitespace in each symlink value, unless the rule explicitly
specifies OPTIONS+="string_escape=none".
[Test Case]
This assumes using udev with the patch from bug 1642903.
Without this patch, when using a NVMe drive that contains spaces in
its model and/or serial strings, check the /dev/disk/by-id/ directory.
It should contain a partially-correct symlink to the NVMe drive, with
the name up to the first space. All following space-separated parts
of the mode/serial string should have symlinks in the /dev/ directory.
This is the incorrect behavior.
With this patch, check the /dev/disk/by-id/ directory. It should
contain a fully-correct symlink to the NVMe drive, and no part of the
drive's model/serial number string should be a link in the /dev
directory.
An example of the correct/incorrect naming is in the Impact section.
There should be no other changes to any of the symlinks under /dev
before and after this patch. Typical locations for symlinks are
/dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
/dev/disk/by-label/
[Regression Potential]
Errors in udev rules can lead to an unbootable or otherwise completely
broken system if they unintentionally break or clobber existing
/dev/disks/ symlinks.
[Other Info]
This is also tracked with upstream systemd (udev) bug 4833:
https://github.com/systemd/systemd/issues/4833
Also note, this can be worked around in individual rules ONLY (i.e.
not fixed for all rules) by appending OPTIONS+="string_escape=replace"
to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:
KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
ENV{ID_SERIAL_SHORT}=="?*",
ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
/by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"
Related bugs:
* bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
* bug 1651602: NVMe driver regression for non-smp/1-cpu systems
* bug 1649635: export nvme drive model/serial strings via sysfs (trusty)
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1647485/+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 1667422] Re: linux-raspi2: 4.4.0-1044.51 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the 4.4.0-1044.51 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 -- phase: Uploaded + kernel-stable-phase-changed:Friday, 24. February 2017 01:17 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the 4.4.0-1044.51 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 phase: Uploaded - kernel-stable-phase-changed:Friday, 24. February 2017 01:17 UTC - kernel-stable-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/1667422 Title: linux-raspi2: 4.4.0-1044.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-1044.51 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 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667422/+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 1667052] Re: linux: 4.4.0-65.86 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Thursday, 23. February 2017 15:46 UTC backports: 1667054 derivatives: 1667056,1667058,1667061 - -- swm properties -- phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Thursday, 23. February 2017 23:15 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: 1667054 derivatives: 1667056,1667058,1667061 -- swm properties -- - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 23. February 2017 23:15 UTC + 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/1667052 Title: linux: 4.4.0-65.86 -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: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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: 1667054 derivatives: 1667056,1667058,1667061 -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667052/+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 1667422] Re: linux-raspi2: 4.4.0-1044.51 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Description changed: This bug is for tracking the 4.4.0-1044.51 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 - kernel-stable-phase:Packaging - kernel-stable-phase-changed:Thursday, 23. February 2017 18:47 UTC - -- swm properties -- phase: Packaging + kernel-stable-phase-changed:Thursday, 23. February 2017 23:04 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the 4.4.0-1044.51 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 -- - phase: Packaging - kernel-stable-phase-changed:Thursday, 23. February 2017 23:04 UTC - kernel-stable-phase:Uploaded + 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/1667422 Title: linux-raspi2: 4.4.0-1044.51 -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 Committed Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: 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-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-1044.51 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 -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667422/+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 1667058] Re: linux-snapdragon: 4.4.0-1049.53 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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/1667058 Title: linux-snapdragon: 4.4.0-1049.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: 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-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 -- kernel-stable-master-bug: 1667052 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667058/+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 1656528] Re: thermald spamming syslog with 'sysfs write failed constraint_0_power_limit_uw'
This bug was fixed in the package thermald - 1.5.4-4 --- thermald (1.5.4-4) unstable; urgency=medium * fix spamming of logs when writes file (LP: #1656528) - patch from Srinivas Pandruvada at Intel, not yet mainline -- Colin King Thu, 23 Feb 2017 09:26:23 + ** Changed in: thermald (Ubuntu Zesty) 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/1656528 Title: thermald spamming syslog with 'sysfs write failed constraint_0_power_limit_uw' Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Xenial: In Progress Status in thermald source package in Yakkety: In Progress Status in thermald source package in Zesty: Fix Released Bug description: [SRU REQUEST, Xenial, Yakkety] Thermald is spamming the log with error messages on sysfs write failure messages. Demote these to debug level errors so that they aren't logged unless running in debug mode. [FIX] See comment #24, with the fix the messages are not logged when in normal non-debug running mode. [REGRESSION POTENIAL] Minimal, this just reduces the logging spam by turning messages into debug only for when running in debug mode. --- This seems somewhat related to https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1543046 For some reason thermald is writing the message "sysfs write failed constraint_0_power_limit_uw" to the syslog every few seconds. However, there's nothing in the kernel log. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.10 DISTRIB_CODENAME=yakkety DISTRIB_DESCRIPTION="Ubuntu 16.10" $ uname -a Linux graham-desktop 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l | grep thermald ii thermald 1.5.3-4amd64Thermal monitoring and controlling daemon $ grep "sysfs write failed constraint_0_power_limit_uw" /var/log/syslog | wc -l 14160 $ grep thermald /var/log/kern.log | wc -l 0 I'm an experienced Linux user but not an experienced bug submitter, so please let me know if I have failed to provide any necessary info. Am happy to attach additional logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1656528/+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 1587886] Re: strongswan ipsec status issue with apparmor
This bug was fixed in the package strongswan - 5.3.5-1ubuntu3.1
---
strongswan (5.3.5-1ubuntu3.1) xenial; urgency=medium
* fix strongswan ipsec status issue with apparmor (LP: #1587886)
-- Christian Ehrhardt Tue, 07 Feb
2017 15:25:47 +0100
** Changed in: strongswan (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/1587886
Title:
strongswan ipsec status issue with apparmor
Status in One Hundred Papercuts:
Triaged
Status in strongswan package in Ubuntu:
Fix Released
Status in strongswan source package in Xenial:
Fix Released
Status in strongswan source package in Yakkety:
Fix Committed
Bug description:
[Impact]
* Certain strongswan based vpn setups fail, especially those based on
network-manager-l2tp or neutron-vpn-netns-wrapper
* The fix is opening up the apparmor profile slightly for charon and
stroke where paths are disconnected
[Test Case]
* valid VPN setup with network-manager-l2tp, then running "sudo ipsec
status"
or
* valid neutron-vpn setup and then
# mkdir /tmp/test
# ip netns add testns
# ip netns exec testns neutron-vpn-netns-wrapper --mount_paths
"/var/run:/tmp/test" --cmd "ipsec,status"
In both cases the command fails as it can't reach charon log.
[Regression Potential]
* Since the profile for strongswan is opened up a bit (and not more
restricted) the regression potential for strongswan should be minimal.
* Yet OTOH due to the change there is a slightly higher security risk
now. That said the case seems to be exactly what the feature was
designed for [1] and there are several other packages holding a similar
flag.
[1]:
http://wiki.apparmor.net/index.php/ReleaseNotes_2_5#path_name_lookup_and_mediation_of
[Other Info]
* The part of the "valid VPN setup" both Test cases would need some more
input by the reporters if possible - to easen testing (see comments
#5+#6 and #28+#29 for the current status on tests).
* Unless this is done we have to rely more than usual on the reporters to
verify this.
$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
$ apt-cache policy strongswan
strongswan:
Installed: 5.3.5-1ubuntu3
Candidate: 5.3.5-1ubuntu3
Version table:
*** 5.3.5-1ubuntu3 500
500 http://au.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://au.archive.ubuntu.com/ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
Looks like 'ipsec status' might be causing strongswan's charon to
write to run/systemd/journal/dev-log instead of /run/systemd/journal
/dev-log and apparmor doesn't like it.
Extract from /etc/apparmor.d/abstractions/base :
/{,var/}run/systemd/journal/dev-log w,
With an established ipsec connection, issue the following :
$ sudo ipsec status
connecting to 'unix:///var/run/charon.ctl' failed: Permission denied
failed to connect to stroke socket 'unix:///var/run/charon.ctl'
$ journalctl
...
Jun 01 12:15:07 ThinkCentre-M900 kernel: audit: type=1400
audit(1464785297.366:491): apparmor="DENIED" operation="connect" info="Failed
name lookup - disconnected path" error=-13 profile="/usr/lib/ipsec/charon"
name="run/systemd/journal/dev-log" pid=4994 comm="charon" requested_mask="w"
denied_mask="w" fsuid=0 ouid=0
...
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: strongswan 5.3.5-1ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 1 23:06:53 2016
InstallationDate: Installed on 2016-05-11 (21 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: strongswan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1587886/+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 1665014] Re: SRU 0.15 tracking bug
This bug was fixed in the package ubuntu-image - 0.15+16.04ubuntu1 --- ubuntu-image (0.15+16.04ubuntu1) xenial; urgency=medium * SRU tracking number LP: #1665014 * ubuntu-image now supports gadget.yaml files with multiple volume specifications. Each volume describes a different disk image. For the multi-volume case, no implicit root file system structure is added at all; the root file system partition must be defined in the gadget.yaml. -o/--output is ignored in the multi-volume case. (LP:1641727) * Add -O/--output-dir command line options. Disk image files are written here using the volume name and a .img suffix. Deprecate -o/--output. -O and -o are mutually exclusive. * Handle structure parts with size or offset < 1MiB. (LP:1630709) * Warn when the size or offset is not a multiple of the sector size. (LP:1663172 and LP:1621151) * Allow and ignore any string values in the ``defaults`` section. (LP:1661515) * Handle a couple more cases where ubuntu-image as a snap cannot read from /tmp (model assertions and extra snaps). (LP:1663424) * Add a release script. (LP:1655669) * Version numbers for the snap now say "+snap" instead of "+real". (LP:1664296) -- Barry Warsaw Mon, 06 Feb 2017 18:36:02 -0500 ** Changed in: ubuntu-image (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/1665014 Title: SRU 0.15 tracking bug Status in ubuntu-image package in Ubuntu: Fix Released Status in ubuntu-image source package in Xenial: Fix Released Status in ubuntu-image source package in Yakkety: Fix Released Bug description: New SRU tracking bug (with exception) for ubuntu-image 0.15 in Yakkety and Xenial. See https://wiki.ubuntu.com/UbuntuImageUpdates [Impact] ubuntu-image 0.15 fixes some bugs and brings feature parity with the original design by adding support for multi-volume gadget.yaml specifications. This release deprecates -o/--output in favor of -O /--output-dir. It also handles structure parts with size or offset < 1MiB. Bugs fixed include problems with /tmp in the snap version and ignoring any values in the defaults section of the gadget.yaml [Test Case] Create an image using the official amd64 model assertion. Ensure that the resulting image boots to 'press enter to configure' phase. [Regression Potential] * ubuntu-image may not produce a bootable image. * More warnings may be emitted in the log file (due to misaligned size or offsets) * There could be bugs in multi-volume gadget support that breaks single-volume specifications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-image/+bug/1665014/+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 1665014] Re: SRU 0.15 tracking bug
This bug was fixed in the package ubuntu-image - 0.15+16.10ubuntu1 --- ubuntu-image (0.15+16.10ubuntu1) yakkety; urgency=medium * SRU tracking number LP: #1665014 * ubuntu-image now supports gadget.yaml files with multiple volume specifications. Each volume describes a different disk image. For the multi-volume case, no implicit root file system structure is added at all; the root file system partition must be defined in the gadget.yaml. -o/--output is ignored in the multi-volume case. (LP:1641727) * Add -O/--output-dir command line options. Disk image files are written here using the volume name and a .img suffix. Deprecate -o/--output. -O and -o are mutually exclusive. * Handle structure parts with size or offset < 1MiB. (LP:1630709) * Warn when the size or offset is not a multiple of the sector size. (LP:1663172 and LP:1621151) * Allow and ignore any string values in the ``defaults`` section. (LP:1661515) * Handle a couple more cases where ubuntu-image as a snap cannot read from /tmp (model assertions and extra snaps). (LP:1663424) * Add a release script. (LP:1655669) * Version numbers for the snap now say "+snap" instead of "+real". (LP:1664296) -- Barry Warsaw Mon, 06 Feb 2017 18:36:02 -0500 ** Changed in: ubuntu-image (Ubuntu Yakkety) 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/1665014 Title: SRU 0.15 tracking bug Status in ubuntu-image package in Ubuntu: Fix Released Status in ubuntu-image source package in Xenial: Fix Released Status in ubuntu-image source package in Yakkety: Fix Released Bug description: New SRU tracking bug (with exception) for ubuntu-image 0.15 in Yakkety and Xenial. See https://wiki.ubuntu.com/UbuntuImageUpdates [Impact] ubuntu-image 0.15 fixes some bugs and brings feature parity with the original design by adding support for multi-volume gadget.yaml specifications. This release deprecates -o/--output in favor of -O /--output-dir. It also handles structure parts with size or offset < 1MiB. Bugs fixed include problems with /tmp in the snap version and ignoring any values in the defaults section of the gadget.yaml [Test Case] Create an image using the official amd64 model assertion. Ensure that the resulting image boots to 'press enter to configure' phase. [Regression Potential] * ubuntu-image may not produce a bootable image. * More warnings may be emitted in the log file (due to misaligned size or offsets) * There could be bugs in multi-volume gadget support that breaks single-volume specifications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-image/+bug/1665014/+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 1662378] Re: many OOMs on busy xenial IMAP server with lots of available memory
** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux (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/1662378 Title: many OOMs on busy xenial IMAP server with lots of available memory Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: We recently noticed that a busy xenial IMAP server with about 22 days uptime has been logging a lot of OOM messages. The machine has 24G of memory. Below please find some typical memory info. I noted that there was about 11G of memory allocated to slab, and since all of the oom-killer invoked messages report order=2 or order=3 (see below for gfp_flags) I thought that maybe fragmentation was a factor. After doing echo 2 > /proc/sys/vm/drop_caches to release reclaimable slab memory, no OOMs were logged for around 30 minutes, but then they started up again, although perhaps not as frequently as before, and the amount of memory in slab was back up around its former size. To the best of my knowledge we do not have any custom VM- related sysctl tweaks on this machine. Attached please find version.log and lspci-vnvn.log. And here's a link to a kern.log from a little before time of boot onwards, containing all of the oom-killer messages: https://people.canonical.com/~pjdc/grenadilla-sanitized-kern.log.xz == Breakdown of Failed Allocations === pjdc@grenadilla:~$ grep -o 'gfp_mask=.*, order=.' kern.log-version-with-oom-killer-invoked | sort | uniq -c | sort -n 1990 gfp_mask=0x26000c0, order=2 4043 gfp_mask=0x240c0c0, order=3 pjdc@grenadilla:~$ _ == Representative (Probably) Memory Info == pjdc@grenadilla:~$ free -m totalusedfree shared buff/cache available Mem: 240971762 213 266 22121 21087 Swap: 17492 101 17391 pjdc@grenadilla:~$ cat /proc/meminfo MemTotal: 24676320 kB MemFree: 219440 kB MemAvailable: 21593416 kB Buffers: 6186648 kB Cached: 4255608 kB SwapCached: 3732 kB Active: 7593140 kB Inactive:4404824 kB Active(anon):1319736 kB Inactive(anon): 508544 kB Active(file):6273404 kB Inactive(file): 3896280 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 17912436 kB SwapFree: 17808972 kB Dirty: 524 kB Writeback: 0 kB AnonPages: 1553244 kB Mapped: 219868 kB Shmem:272576 kB Slab: 12209796 kB SReclaimable: 11572836 kB SUnreclaim: 636960 kB KernelStack: 14464 kB PageTables:54864 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit:30250596 kB Committed_AS:2640808 kB VmallocTotal: 34359738367 kB VmallocUsed: 0 kB VmallocChunk: 0 kB HardwareCorrupted: 0 kB AnonHugePages: 18432 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 2048 kB DirectMap4k: 2371708 kB DirectMap2M:22784000 kB pjdc@grenadilla:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662378/+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 1667058] Re: linux-snapdragon: 4.4.0-1049.53 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta 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/1667058 Title: linux-snapdragon: 4.4.0-1049.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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-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 -- kernel-stable-master-bug: 1667052 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667058/+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 1667058] Re: linux-snapdragon: 4.4.0-1049.53 -proposed tracker
** Summary changed: - linux-snapdragon: 4.4.0-1048.52 -proposed tracker + linux-snapdragon: 4.4.0-1049.53 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Assignee: Stefan Bader (smb) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Stefan Bader (smb) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => 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/1667058 Title: linux-snapdragon: 4.4.0-1049.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Committed 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-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 -- kernel-stable-master-bug: 1667052 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667058/+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 1667422] Re: linux-raspi2: 4.4.0-1044.51 -proposed tracker
** Also affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1667422 Title: linux-raspi2: 4.4.0-1044.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-1044.51 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 kernel-stable-phase:Packaging kernel-stable-phase-changed:Thursday, 23. February 2017 18:47 UTC -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667422/+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 1667058] Re: linux-snapdragon: 4.4.0-1048.52 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** 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: 1667052 + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Thursday, 23. February 2017 19:31 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: 1667052 - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 23. February 2017 19:31 UTC + 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/1667058 Title: linux-snapdragon: 4.4.0-1049.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Committed 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-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 -- kernel-stable-master-bug: 1667052 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667058/+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 1660707] Re: linux-raspi2: -proposed tracker
*** This bug is a duplicate of bug 1667422 *** https://bugs.launchpad.net/bugs/1667422 ** This bug is no longer a duplicate of bug 1660721 linux-raspi2: 4.4.0-1043.50 -proposed tracker ** This bug has been marked a duplicate of bug 1667422 linux-raspi2: 4.4.0-1044.51 -proposed tracker -- 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/1660707 Title: linux-raspi2: -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: New Status in Kernel SRU Workflow prepare-package-meta series: New 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-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 -- kernel-stable-master-bug: 1660704 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1660707/+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 1660721] Re: linux-raspi2: 4.4.0-1043.50 -proposed tracker
*** This bug is a duplicate of bug 1667422 *** https://bugs.launchpad.net/bugs/1667422 ** This bug has been marked a duplicate of bug 1667422 linux-raspi2: 4.4.0-1044.51 -proposed tracker -- 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/1660721 Title: linux-raspi2: 4.4.0-1043.50 -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: Incomplete 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 series: New 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 derivative-trackers-created: true kernel-stable-master-bug: 1660704 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1660721/+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 1604501] Re: ceph-osd fails to initialize when encrypt is enabled
** Changed in: charm-ceph
Importance: Undecided => High
** Changed in: charm-ceph
Status: New => Triaged
** Changed in: charm-ceph
Assignee: (unassigned) => Chris Holcombe (xfactor973)
** Changed in: ceph (Juju Charms Collection)
Status: Triaged => Invalid
** Changed in: charm-ceph-osd
Importance: Undecided => High
** Changed in: charm-ceph-osd
Status: New => Triaged
** Changed in: charm-ceph-osd
Assignee: (unassigned) => Chris Holcombe (xfactor973)
** Changed in: ceph-osd (Juju Charms Collection)
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/1604501
Title:
ceph-osd fails to initialize when encrypt is enabled
Status in OpenStack ceph charm:
Triaged
Status in OpenStack ceph-osd charm:
Triaged
Status in ceph package in Ubuntu:
Triaged
Status in ceph source package in Xenial:
Triaged
Status in ceph source package in Yakkety:
Triaged
Status in ceph source package in Zesty:
Triaged
Status in ceph package in Juju Charms Collection:
Invalid
Status in ceph-osd package in Juju Charms Collection:
Invalid
Bug description:
The config-key put command is called without a cephx user which causes the
command to fail. Error log information is:
2016-07-16 05:07:14 INFO mon-relation-changed 2016-07-16 05:07:14.918436
7f67d2797700 -1 auth: unable to find a keyring on
/etc/ceph/ceph.client.admin.keyring: (2) No such file or directory
2016-07-16 05:07:14 INFO mon-relation-changed 2016-07-16 05:07:14.919173
7f67d2797700 -1 monclient(hunting): ERROR: missing keyring, cannot use cephx
for authentication
2016-07-16 05:07:14 INFO mon-relation-changed 2016-07-16 05:07:14.919315
7f67d2797700 0 librados: client.admin initialization error (2) No such file or
directory
2016-07-16 05:07:14 INFO mon-relation-changed Error connecting to cluster:
ObjectNotFound
2016-07-16 05:07:14 INFO mon-relation-changed Traceback (most recent call
last):
2016-07-16 05:07:14 INFO mon-relation-changed File "/usr/sbin/ceph-disk",
line 9, in
2016-07-16 05:07:14 INFO mon-relation-changed
load_entry_point('ceph-disk==1.0.0', 'console_scripts', 'ceph-disk')()
2016-07-16 05:07:14 INFO mon-relation-changed File
"/usr/lib/python2.7/dist-packages/ceph_disk/main.py", line 4965, in run
2016-07-16 05:07:14 INFO mon-relation-changed main(sys.argv[1:])
2016-07-16 05:07:14 INFO mon-relation-changed File
"/usr/lib/python2.7/dist-packages/ceph_disk/main.py", line 4918, in main
2016-07-16 05:07:14 INFO mon-relation-changed main_catch(args.func, args)
2016-07-16 05:07:14 INFO mon-relation-changed File
"/usr/lib/python2.7/dist-packages/ceph_disk/main.py", line 4943, in main_catch
2016-07-16 05:07:14 INFO mon-relation-changed func(args)
2016-07-16 05:07:14 INFO mon-relation-changed File
"/usr/lib/python2.7/dist-packages/ceph_disk/main.py", line 1774, in main
2016-07-16 05:07:14 INFO mon-relation-changed
Prepare.factory(args).prepare()
2016-07-16 05:07:14 INFO mon-relation-changed File
"/usr/lib/python2.7/dist-packages/ceph_disk/main.py", line 1762, in prepare
2016-07-16 05:07:14 INFO mon-relation-changed self.prepare_locked()
2016-07-16 05:07:14 INFO mon-relation-changed File
"/usr/lib/python2.7/dist-packages/ceph_disk/main.py", line 1793, in
prepare_locked
2016-07-16 05:07:14 INFO mon-relation-changed self.lockbox.prepare()
2016-07-16 05:07:14 INFO mon-relation-changed File
"/usr/lib/python2.7/dist-packages/ceph_disk/main.py", line 2360, in prepare
2016-07-16 05:07:14 INFO mon-relation-changed self.populate()
2016-07-16 05:07:14 INFO mon-relation-changed File
"/usr/lib/python2.7/dist-packages/ceph_disk/main.py", line 2305, in populate
2016-07-16 05:07:14 INFO mon-relation-changed self.create_key()
2016-07-16 05:07:14 INFO mon-relation-changed File
"/usr/lib/python2.7/dist-packages/ceph_disk/main.py", line 2264, in create_key
2016-07-16 05:07:14 INFO mon-relation-changed base64_key,
2016-07-16 05:07:14 INFO mon-relation-changed File
"/usr/lib/python2.7/dist-packages/ceph_disk/main.py", line 439, in
command_check_call
2016-07-16 05:07:14 INFO mon-relation-changed return
subprocess.check_call(arguments)
2016-07-16 05:07:14 INFO mon-relation-changed File
"/usr/lib/python2.7/subprocess.py", line 540, in check_call
2016-07-16 05:07:14 INFO mon-relation-changed raise
CalledProcessError(retcode, cmd)
2016-07-16 05:07:14 INFO mon-relation-changed subprocess.CalledProcessError:
Command '['/usr/bin/ceph', 'config-key', 'put',
'dm-crypt/osd/e4d2604d-1e38-4563-88ae-c447ffba95e9/luks',
'61H4+6InRku1kvSqg23ckK0EsoFL1csn18ONWL8a+1s7r8wLzPUTrRRmuq4D1o1/GZ9UvFVxytPq4pZeA73ZtCeNPWlbIoKeAhZ/gbK6g1YXPjpICOmxx7aSckIO212faMiHG+jLbIAzeekhK7AKT+rxGWXYh2wYVX3rxn4dKik=']'
returned non-z
[Group.of.nepali.translators] [Bug 1595242] Re: mongodb xenial s390x packages are needed (blocks ceilometer)
** Changed in: ceilometer (Juju Charms Collection) Status: New => Invalid ** Changed in: ceilometer-agent (Juju Charms Collection) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1595242 Title: mongodb xenial s390x packages are needed (blocks ceilometer) Status in OpenStack ceilometer charm: New Status in OpenStack ceilometer-agent charm: New Status in Ubuntu on IBM z Systems: New Status in mongodb package in Ubuntu: Fix Released Status in mongodb source package in Xenial: Confirmed Status in mongodb source package in Yakkety: Confirmed Status in ceilometer package in Juju Charms Collection: Invalid Status in ceilometer-agent package in Juju Charms Collection: Invalid Status in mongodb package in Juju Charms Collection: New Status in mongodb package in Debian: Fix Released Bug description: The ceilometer and ceilometer-agent charms require the mongodb charm. s390x validation for ceilometer and ceilometer-agent is blocked on the absence of mongodb packages in s390x Xenial, and on the absence of a Xenial mongodb charm in general. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceilometer/+bug/1595242/+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 1656484] Re: /usr/bin/pollinate uses xxd but does not depend on vim-common
This bug was fixed in the package pollinate - 4.23-0ubuntu1~16.04.1 --- pollinate (4.23-0ubuntu1~16.04.1) xenial; urgency=medium * Add missing dependency on vim-common, for xxd. (LP: #1656484) -- Stefano Rivera Sat, 14 Jan 2017 14:52:03 +1100 ** Changed in: pollinate (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/1656484 Title: /usr/bin/pollinate uses xxd but does not depend on vim-common Status in pollinate package in Ubuntu: Fix Released Status in pollinate source package in Trusty: Fix Committed Status in pollinate source package in Xenial: Fix Released Status in pollinate source package in Yakkety: Fix Committed Status in pollinate source package in Zesty: Fix Released Bug description: == SRU Impact == Pretty minimal, adding a dependency to a shell script. == Regression Potential == xxd has presumably already available on machines that have pollinate, or it'd have been reported by now. VIM is rather ubiquitous... So, this is unlikely to have any effect for most users. For the rest, things are a little more fun: vim-common Recommends: vim | vim-gnome | vim-gtk | vim-gtk3 | vim-athena | vim-nox | vim-tiny So, upgraders will get a full-blown vim pulled in. They'll also get a working pollinate. == Test Case == In a minimal chroot, without vim-common & xxd: # pollinate BAD: <13>Jan 14 03:34:27 pollinate[9317]: client sent challenge to [https://entropy.ubuntu.com/] <13>Jan 14 03:34:28 pollinate[9317]: client verified challenge/response with [https://entropy.ubuntu.com/] /usr/bin/pollinate: 79: /usr/bin/pollinate: xxd: not found GOOD: <13>Jan 14 03:49:29 pollinate[22771]: client sent challenge to [https://entropy.ubuntu.com/] <13>Jan 14 03:49:31 pollinate[22771]: client verified challenge/response with [https://entropy.ubuntu.com/] <13>Jan 14 03:49:31 pollinate[22771]: client hashed response from [https://entropy.ubuntu.com/] <13>Jan 14 03:49:31 pollinate[22771]: client successfully seeded [/dev/urandom] == Original report == # journalctl | grep pollinate Jan 13 10:48:21 plato pollinate[1601]: client sent challenge to [https://entropy.ubuntu.com/] Jan 13 10:48:22 plato pollinate[1626]: client verified challenge/response with [https://entropy.ubuntu.com/] Jan 13 10:48:22 plato pollinate[1564]: /usr/bin/pollinate: 80: /usr/bin/pollinate: xxd: not found Jan 13 10:48:22 plato systemd[1]: pollinate.service: Main process exited, code=exited, status=127/n/a Jan 13 10:48:22 plato systemd[1]: pollinate.service: Unit entered failed state. Jan 13 10:48:22 plato systemd[1]: pollinate.service: Failed with result 'exit-code'. # dpkg -l | grep pollina ii pollinate 4.23-0ubuntu1~16.04 all seed the pseudo random number generator # lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1656484/+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 1621340] Re: [SRU]'multipath -r' causes /dev/mapper/ being removed
This bug was fixed in the package multipath-tools -
0.5.0+git1.656f8865-5ubuntu2.4
---
multipath-tools (0.5.0+git1.656f8865-5ubuntu2.4) xenial; urgency=medium
* debian/patches/wait-for-udev-in-dm_simplecmd_noflush.patch:
- Cherrypick from upstream: wait for udev in dm_simplecmd_noflush().
(LP: #1621340)
-- Hua Zhang Thu, 09 Feb 2017 20:08:57
+0800
** Changed in: multipath-tools (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1621340
Title:
[SRU]'multipath -r' causes /dev/mapper/ being removed
Status in multipath-tools package in Ubuntu:
Fix Released
Status in multipath-tools source package in Xenial:
Fix Released
Status in multipath-tools source package in Yakkety:
Fix Committed
Bug description:
[Impact]
"multipath -r" causes the /dev/mapper/ to disappear momentarily,
which leads to some issue in consumer applications as such OpenStack.
[Test Case]
* connect to an multipath iscsi target
* multipath -r
* /dev/mapper/ disappears momentarily
[Regression Potential]
* None
"multipath -r" causes the /dev/mapper/ to disappear momentarily, which
leads to some issue in consumer applications as such OpenStack. After some
investigation, I found that /dev/mapper/ was deleted by udev during the
reload, and it was re-created soon later by multipathd (livdevmapper code of
cause). Detailed findings are as follows:
For reload in domap (rename as well),
case ACT_RELOAD:
r = dm_addmap_reload(mpp, params);
if (r)
r = dm_simplecmd_noflush(DM_DEVICE_RESUME, mpp->alias,
0, MPATH_UDEV_RELOAD_FLAG);
break;
it passes 0 to dm_simplecmd_noflush as argument for needsync, which
makes dm_task_set_cookie call being skipped in dm_simplecmd,
if (udev_wait_flag && !dm_task_set_cookie(dmt, &cookie,
((conf->daemon)? DM_UDEV_DISABLE_LIBRARY_FALLBACK : 0) | udev_flags)) {
dm_udev_complete(cookie);
goto out;
}
because of the short-circuit evaluation. Thus _do_dm_ioctl in
libdevmapper will add DM_UDEV_DISABLE_DM_RULES_FLAG flag to
dmi->event_nr, and that will eventually be used in the udev rules
(55-dm.rules),
ENV{DM_UDEV_DISABLE_DM_RULES_FLAG}!="1", ENV{DM_NAME}=="?*",
SYMLINK+="mapper/$env{DM_NAME}"
Since the DM_UDEV_DISABLE_DM_RULES_FLAG is set, the rule will not
match. As a result the link is removed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1621340/+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 1667239] Re: FlashGT Integration and Setup: fsbmc30: After 17th reboot of soft bootme, HTX & Linux errors seen with 256 virtual LUNs
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team (canonical-kernel-team) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) 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/1667239 Title: FlashGT Integration and Setup: fsbmc30: After 17th reboot of soft bootme, HTX & Linux errors seen with 256 virtual LUNs Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: New Status in linux source package in Yakkety: New Bug description: == Comment: #1 - Application Cdeadmin - 2016-06-02 15:28:27 == State: Open by: anitrap on 01 June 2016 17:36:39 Contact: Anitra Powell (anit...@us.ibm.com ) Backup: Dion Bell (bel...@us.ibm.com) Primary BMC (1603G): = # cat /proc/ractrends/Helper/FwInfo FW_VERSION=2.13.91819 FW_DATE=Mar 10 2016 FW_BUILDTIME=10:59:31 CDT FW_DESC=8335 SRC BUILD RR9 03102016 FW_PRODUCTID=1 FW_RELEASEID=RR9 FW_CODEBASEVERSION=2.X # PNOR (1603G): # ipmitool -H 127.0.0.1 -I lanplus -U ADMIN -P admin fru list 47 Product Name : OpenPOWER Firmware Product Version : IBM-firestone-ibm-OP8_v1.7_1.62 Product Extra : hostboot-bc98d0b-1a29dff Product Extra : occ-0362706-16fdfa7 Product Extra : skiboot-5.1.13 Product Extra : hostboot-binaries-43d5a59 Product Extra : firestone-xml-e7b4fa2-c302f0e Product Extra : capp-ucode-105cb8f Partition Info: = ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu 16.04 LTS \n \l Kernel Version: 4.4.8c0ffee0+ HTX Version: htxubuntu-396 Host Name: fsbmc30p1 Machine Serial No: 210995A Machine Type/Model: 8335-GCA root@fsbmc30p1:~# uname -a Linux fsbmc30p1 4.4.8c0ffee0+ #2 SMP Tue May 24 10:50:26 CDT 2016 ppc64le ppc64le ppc64le GNU/Linux FlashGT NVMe setup: === 1 FlashGT card in slot 1 running in superpipe mode with 128 LUNs per port (total of 256 LUNs). lsscsi [0:0:0:0]diskATA ST1000NX0313 BE33 /dev/sda [1:0:0:0]diskATA ST1000NX0313 BE33 /dev/sdb [4:0:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdc [4:1:0:0]diskNVMe SAMSUNG MZ1LV960 3011 /dev/sdd [5:0:0:0]cd/dvd AMI Virtual CDROM0 1.00 /dev/sr0 [5:0:0:1]cd/dvd AMI Virtual CDROM1 1.00 /dev/sr1 [5:0:0:2]cd/dvd AMI Virtual CDROM2 1.00 /dev/sr2 [5:0:0:3]cd/dvd AMI Virtual CDROM3 1.00 /dev/sr3 [6:0:0:0]diskAMI Virtual Floppy0 1.00 /dev/sde [6:0:0:1]diskAMI Virtual Floppy1 1.00 /dev/sdf [6:0:0:2]diskAMI Virtual Floppy2 1.00 /dev/sdg [6:0:0:3]diskAMI Virtual Floppy3 1.00 /dev/sdh [7:0:0:0]diskAMI Virtual HDisk0 1.00 /dev/sdi [7:0:0:1]diskAMI Virtual HDisk1 1.00 /dev/sdj [7:0:0:2]diskAMI Virtual HDisk2 1.00 /dev/sdk [7:0:0:3]diskAMI Virtual HDisk3 1.00 /dev/sdl [7:0:0:4]diskAMI Virtual HDisk4 1.00 /dev/sdm lspci | grep -i acc 0004:01:00.0 Processing accelerators: IBM Device 0601 (rev 01) ls -l /sys/class/cxl total 0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0 lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0m -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0m lrwxrwxrwx 1 root root 0 May 31 13:27 afu0.0s -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0/afu0.0/afu0.0s lrwxrwxrwx 1 root root 0 May 31 13:27 card0 -> ../../devices/pci0004:00/0004:00:00.0/0004:01:00.0/cxl/card0 lscfg | grep afu + afu0.0 Slot1/card0/afu0.0 + afu0.0m Slot1/card0/afu0.0/afu0.0m + afu0.0s Slot1/card0/afu0.0/afu0.0s /opt/ibm/capikv/bin/cxlfstatus CXL Flash Device Status Found 0601 0004:01:00.0 Slot1 Device: SCSI Block Mode LUN WWID sg2:4:0:0:0, sdc, superpipe, 600253800253824633000460 sg3:4:1:0:0, sdd, superpipe, 600253800253824633000520 dpkg -l | grep capi 4el no description given 3.0-1970-3042652 ppc6 4el no description given 3.0-1970-30426
[Group.of.nepali.translators] [Bug 1612600] Re: backuppc 3.3.1-2ubuntu3 breaks pool graphs on the Status page
** Also affects: backuppc (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1612600
Title:
backuppc 3.3.1-2ubuntu3 breaks pool graphs on the Status page
Status in backuppc package in Ubuntu:
Fix Released
Status in backuppc source package in Xenial:
New
Bug description:
Upgraded system from 14.04 LTS to 16.04.1 LTS.
As a result, the rrd pool size graphs stopped displaying, instead
showing "default image" icons.
Investigation has shown that this is due to the permissions conflict.
Whatever user executes backuppc/index.cgi cannot run /usr/bin/rrdtool.
The fix is as per
https://sourceforge.net/p/backuppc/mailman/message/18724263/.
Namely, here's a relevant code snapshot in
/usr/share/backuppc/lib/BackupPC/CGI/GeneralInfo.pm:
$In{image} =~ /([0-9]+)/;
my $weeks = $1;
my $real = $<;# NEW
$< = $>; # NEW
print "Content-type: image/png\n\n";
print `/usr/bin/rrdtool graph - --imgformat=PNG --start=end-${weeks}w
--end=-300 --title="BackupPC Pool Size (${weeks} weeks)" --base=1000
--height=100 --width=600 --alt-autoscale-max --lower-limit=0
--vertical-label="" --slope-mode --font TITLE:10:Times --font AXIS:8:Times
--font LEGEND:8:Times --font UNIT:8:Times -c BACK#FF
DEF:ao="$LogDir/pool.rrd":ckb:AVERAGE CDEF:a=ao,1024,* AREA:a#95B8DB:"CPool in
bytes" GPRINT:a:LAST:"Current\\:%8.2lf %s" GPRINT:a:AVERAGE:"Average\\:%8.2lf
%s" GPRINT:a:MAX:"Maximum\\:%8.2lf %s\\n"`;
$< = $real; # NEW
return;
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1612600/+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 1667054] Re: linux-lts-xenial: -proposed tracker
** Also affects: linux-lts-xenial (Ubuntu Trusty) Importance: Undecided Status: New ** No longer affects: linux-lts-xenial (Ubuntu Xenial) ** Changed in: linux-lts-xenial (Ubuntu Trusty) 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/1667054 Title: linux-lts-xenial: -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: New 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-lts-xenial package in Ubuntu: Invalid Status in linux-lts-xenial source package in Trusty: 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: 1667052 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1667054/+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 1667406] [NEW] Wrongly capitalized field names in JSON output of "lxc list"
Public bug reported:
This only affects LXD 2.0.9 in Ubuntu right now.
# Rationale
LXD 2.0.9 regressed JSON output of "lxc list" when compared to LXD 2.0.8 by
having a few fields be now capitalized.
# Testcase
- lxc launch ubuntu:16.04 xen
- lxc list --format=json | grep Snapshots
- Upgrade
- lxc list --format=json | grep Snapshots
("Snapshots" is meant to be "snapshots")
# Regression potential
The commit only fixes the name of the two affected fields. It's unlikely that
someone is already relying on the wrongly capitalized name and it's certainly
worth fixing the regression for people scripting LXD.
** Affects: lxd (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: lxd (Ubuntu Trusty)
Importance: High
Status: Triaged
** Affects: lxd (Ubuntu Xenial)
Importance: High
Status: In Progress
** Also affects: lxd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: lxd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: lxd (Ubuntu)
Status: New => Fix Released
** Changed in: lxd (Ubuntu Trusty)
Status: New => Triaged
** Changed in: lxd (Ubuntu Xenial)
Status: New => Triaged
** Changed in: lxd (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: lxd (Ubuntu Xenial)
Importance: Undecided => High
--
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/1667406
Title:
Wrongly capitalized field names in JSON output of "lxc list"
Status in lxd package in Ubuntu:
Fix Released
Status in lxd source package in Trusty:
Triaged
Status in lxd source package in Xenial:
In Progress
Bug description:
This only affects LXD 2.0.9 in Ubuntu right now.
# Rationale
LXD 2.0.9 regressed JSON output of "lxc list" when compared to LXD 2.0.8 by
having a few fields be now capitalized.
# Testcase
- lxc launch ubuntu:16.04 xen
- lxc list --format=json | grep Snapshots
- Upgrade
- lxc list --format=json | grep Snapshots
("Snapshots" is meant to be "snapshots")
# Regression potential
The commit only fixes the name of the two affected fields. It's unlikely that
someone is already relying on the wrongly capitalized name and it's certainly
worth fixing the regression for people scripting LXD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1667406/+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 1652537] Re: Update chrome-gnome-shell to version 8 in all supported releases
This bug was fixed in the package chrome-gnome-shell - 8-2ubuntu3~ubuntu16.10.1 --- chrome-gnome-shell (8-2ubuntu3~ubuntu16.10.1) yakkety; urgency=medium * Backport to yakkety (LP: #1652537) * debian/rules: Force Firefox helper to use non-multiarch directory (not needed with zesty's cmake) -- Jeremy Bicha Wed, 18 Jan 2017 02:07:49 -0500 ** Changed in: chrome-gnome-shell (Ubuntu Yakkety) 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/1652537 Title: Update chrome-gnome-shell to version 8 in all supported releases Status in chrome-gnome-shell package in Ubuntu: Fix Released Status in chrome-gnome-shell source package in Trusty: In Progress Status in chrome-gnome-shell source package in Xenial: In Progress Status in chrome-gnome-shell source package in Yakkety: Fix Released Bug description: Impact == gnome-shell provides a browser plugin so that users can manage GNOME Shell extensions by visiting https:/extensions.gnome.org/ in Firefox and compatible browsers. This extension will stop working in Firefox once users upgrade to Firefox 52. Firefox 52 is scheduled for upstream release March 7, 2017 and 52 Beta will open approximately January 24. chrome-gnome-shell version 8 adds Firefox support that will keep working in Firefox 52 and beyond. There are actually two parts to chrome-gnome-shell: a system helper and a browser addon. The chrome-gnome-shell package provides the system helper. The browser addon can be installed directly without admin privileges from https://addons.mozilla.org/en/firefox/addon/gnome-shell-integration/ or for Chrome at https://chrome.google.com/webstore/detail/gnome-shell-integration/gphhapmejobijbbhgpjhcjognlahblep For more details, see https://blogs.gnome.org/ne0sight/2016/12/25/how-to-install-gnome-shell-extensions-with-firefox-52/ Test Case = - In Ubuntu GNOME, install the updated chrome-gnome-shell - Open Firefox and browse to https://extensions.gnome.org/local/ - In the list of extensions, turn on the "Applications Menu". The Activities button in the top left of the screen should now read Applications and show a menu of installed apps when clicked. - Turn off the "Applications Menu". The Applications button should revert to being a simple Activities button. * Repeat the above test with chromium-browser * If you are using Firefox 51, that test was just testing the old functionality (It's important that it still works though!). To test the new version: - Install https://addons.mozilla.org/en-US/firefox/addon/gnome-shell-integration/ - To make sure that you aren't testing the old functionality, run sudo rm /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so - Restart Firefox and do the above "Applications Menu" test. - When you are finished testing, run this command to restore the manually deleted file: sudo apt install --reinstall gnome-shell Regression Potential === It's important that installing the Firefox helper does not break the existing Firefox support for https://extensions.gnome.org/ Other Info == chrome-gnome-shell 7 is available in Ubuntu 16.10. We want to make version 8 available in -updates for 16.10, 16.04 and 14.04 LTS. (Ubuntu 12.04 LTS is completely End of Life in April and was never officially supported by Ubuntu GNOME.) For 16.10, I am backporting the updated packaging since the changes are minor and make sense. For the ubuntu-gnome-desktop metapackage update, see https://launchpad.net/bugs/1652538 It might be nice if a future chrome-gnome-shell would include the Firefox addon too instead of just the system helper, but that's complicated since I believe addons need to be signed in Ubuntu. https://wiki.mozilla.org/RapidRelease/Calendar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrome-gnome-shell/+bug/1652537/+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 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"
** Also affects: tor (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: tor (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1648143 Title: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor" Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in tor package in Ubuntu: New Status in apparmor source package in Xenial: New Status in linux source package in Xenial: Fix Committed Status in tor source package in Xenial: New Status in apparmor source package in Yakkety: New Status in linux source package in Yakkety: Fix Committed Status in tor source package in Yakkety: New Bug description: Environment: Distribution: ubuntu Distribution version: 16.10 lxc info: apiextensions: storage_zfs_remove_snapshots container_host_shutdown_timeout container_syscall_filtering auth_pki container_last_used_at etag patch usb_devices https_allowed_credentials image_compression_algorithm directory_manipulation container_cpu_time storage_zfs_use_refquota storage_lvm_mount_options network profile_usedby container_push apistatus: stable apiversion: "1.0" auth: trusted environment: addresses: 163.172.48.149:8443 172.20.10.1:8443 172.20.11.1:8443 172.20.12.1:8443 172.20.22.1:8443 172.20.21.1:8443 10.8.0.1:8443 architectures: x86_64 i686 certificate: | -BEGIN CERTIFICATE- -END CERTIFICATE- certificatefingerprint: 3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b driver: lxc driverversion: 2.0.5 kernel: Linux kernelarchitecture: x86_64 kernelversion: 4.8.0-27-generic server: lxd serverpid: 32694 serverversion: 2.4.1 storage: btrfs storageversion: 4.7.3 config: core.https_address: '[::]:8443' core.trust_password: true Container: ubuntu 16.10 Issue description -- tor can't start in a non privileged container Logs from the container: - Dec 7 15:03:00 anonymous tor[302]: Configuration was valid Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step APPARMOR spawning /usr/bin/tor: No such file or directory Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process exited, code=exited, status=231/APPARMOR Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed state. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 'exit-code'. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off time over, scheduling restart. Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset devices.list: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted] Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/chr Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/blk Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Logs from the host audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" pid=12164 comm="(tor)" Steps to reproduce - install ubuntu container 16.10 on a ubuntu 16.10 host install tor in the container Launch tor
[Group.of.nepali.translators] [Bug 1638996] Re: apparmor's raw_data file in securityfs is sometimes truncated
** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1638996 Title: apparmor's raw_data file in securityfs is sometimes truncated Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: Hi, It looks like sometimes apparmor's securityfs output is sometimes truncated, root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1# ls -al total 0 drwxr-xr-x 3 root root 0 Nov 3 16:45 . drwxr-xr-x 13 root root 0 Nov 3 16:44 .. -r--r--r-- 1 root root 0 Nov 3 16:45 attach -r--r--r-- 1 root root 0 Nov 3 16:45 mode -r--r--r-- 1 root root 0 Nov 3 16:45 name drwxr-xr-x 3 root root 0 Nov 3 16:45 profiles -r--r--r-- 1 root root 0 Nov 3 16:45 raw_abi -r--r--r-- 1 root root 46234 Nov 3 16:45 raw_data -r--r--r-- 1 root root 0 Nov 3 16:45 raw_hash -r--r--r-- 1 root root 0 Nov 3 16:45 sha1 root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1# cat raw_data > /tmp/out root@zesty:/sys/kernel/security/apparmor/policy/namespaces/lxd-zest_/profiles/usr.lib.snapd.snap-confine.1# ls -al /tmp/out -rw-r--r-- 1 root root 4009 Nov 3 16:55 /tmp/out and 2016-11-03 10:58:01 tych0 jjohansen: hi, http://paste.ubuntu.com/23421551/ 2016-11-03 10:58:18 tych0 it looks like fstat is lying to me about the size of the policy 2016-11-03 10:59:20 @jjohansen tych0: hrmm interesting, can you zip up the /tmp/out file so I can see it looks like a complete policy file? 2016-11-03 11:00:03 @jjohansen something is definitely not right there. hrmmm 2016-11-03 11:00:26 @jjohansen the size is set by the input buffer size 2016-11-03 11:00:28 tych0 jjohansen: http://files.tycho.ws/tmp/out 2016-11-03 11:00:36 tych0 yeah, i assume 2016-11-03 11:01:15 @jjohansen my guess is something is messing up in the seq_file walk of the policy 2016-11-03 11:02:38 @jjohansen tych0: yep the file is truncated, can you open a bug and I will start looking for it 2016-11-03 11:03:14 tych0 jjohansen: sure, just on linux? 2016-11-03 11:03:35 @jjohansen tych0: yeah for now, just linux 2016-11-03 11:03:43 @jjohansen we can add others if needed later 2016-11-03 11:03:44 tych0 jjohansen: FWIW, somehow it seems racy, becasue sometimes it works and sometimes it doesn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638996/+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 1648903] Re: Permission denied and inconsistent behavior in complain mode with 'ip netns list' command
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1648903
Title:
Permission denied and inconsistent behavior in complain mode with 'ip
netns list' command
Status in AppArmor:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Bug description:
On 16.04 with Ubuntu 4.4.0-53.74-generic 4.4.30
With this profile:
#include
profile test (attach_disconnected,complain) {
#include
/{,usr/}{,s}bin/ip ixr, # COMMENT OUT THIS RULE TO SEE WEIRDNESS
capability sys_admin,
capability net_admin,
capability sys_ptrace,
network netlink raw,
ptrace (trace),
/ r,
/run/netns/ rw,
/run/netns/* rw,
mount options=(rw, rshared) -> /run/netns/,
mount options=(rw, bind) /run/netns/ -> /run/netns/,
mount options=(rw, bind) / -> /run/netns/*,
mount options=(rw, rslave) /,
mount options=(rw, rslave), # LP: #1648245
umount /sys/,
umount /,
/bin/dash ixr,
}
Everything is fine when I do:
$ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p
test -- sh -c 'ip netns list'
$
and there are no ALLOWED entries in syslog.
However, if I comment out the '/{,usr/}{,s}bin/ip ixr,' rule, I get a
permission denied and a bunch of ALLOWED entries:
$ sudo apparmor_parser -r /home/jamie/apparmor.profile && sudo aa-exec -p
test -- sh -c 'ip netns list'
open("/proc/self/ns/net"): Permission denied
Dec 9 17:08:09 sec-xenial-amd64 kernel: [ 3117.862629] audit: type=1400
audit(1481324889.782:469): apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="test" pid=4314 comm="apparmor_parser"
Dec 9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870339] audit: type=1400
audit(1481324889.790:470): apparmor="ALLOWED" operation="exec" profile="test"
name="/bin/ip" pid=4317 comm="sh" requested_mask="x" denied_mask="x" fsuid=0
ouid=0 target="test//null-/bin/ip"
Dec 9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870559] audit: type=1400
audit(1481324889.790:471): apparmor="ALLOWED" operation="open"
profile="test//null-/bin/ip" name="/etc/ld.so.cache" pid=4317 comm="ip"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Dec 9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870628] audit: type=1400
audit(1481324889.790:472): apparmor="ALLOWED" operation="open"
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libdl-2.23.so"
pid=4317 comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Dec 9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870703] audit: type=1400
audit(1481324889.790:473): apparmor="ALLOWED" operation="open"
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/libc-2.23.so" pid=4317
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Dec 9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870861] audit: type=1400
audit(1481324889.790:474): apparmor="ALLOWED" operation="file_mprotect"
profile="test//null-/bin/ip" name="/bin/ip" pid=4317 comm="ip"
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Dec 9 17:08:09 sec-xenial-amd64 kernel: [ 3117.870913] audit: type=1400
audit(1481324889.790:475): apparmor="ALLOWED" operation="file_mprotect"
profile="test//null-/bin/ip" name="/lib/x86_64-linux-gnu/ld-2.23.so" pid=4317
comm="ip" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Dec 9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871019] audit: type=1400
audit(1481324889.790:476): apparmor="ALLOWED" operation="create"
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink"
sock_type="raw" protocol=0 requested_mask="create" denied_mask="create"
Dec 9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871066] audit: type=1400
audit(1481324889.790:477): apparmor="ALLOWED" operation="setsockopt"
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink"
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
Dec 9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871099] audit: type=1400
audit(1481324889.790:478): apparmor="ALLOWED" operation="setsockopt"
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink"
sock_type="raw" protocol=0 requested_mask="setopt" denied_mask="setopt"
Dec 9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871128] audit: type=1400
audit(1481324889.790:479): apparmor="ALLOWED" operation="bind"
profile="test//null-/bin/ip" pid=4317 comm="ip" family="netlink"
sock_type="raw" protocol=0 requested_mask="bind" denied_mask="bind"
Dec 9 17:08:09 sec-xenial-amd64 kernel: [ 3117.871672] audit: type=1400
audit(1481324889.794:480): apparmor="ALLOWED" operation="getsockname"
profile="test//null-/bin/ip" pid=4317 comm="ip" fa
[Group.of.nepali.translators] [Bug 1656121] Re: unexpected errno=13 and disconnected path when trying to open /proc/1/ns/mnt from a unshared mount namespace
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1656121
Title:
unexpected errno=13 and disconnected path when trying to open
/proc/1/ns/mnt from a unshared mount namespace
Status in AppArmor:
Confirmed
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Bug description:
This bug is based on a discussion with jjohansen on IRC.
While working on a feature for snapd
(https://github.com/snapcore/snapd/pull/2624) we came across an
unexpected EACCES that only seems to happen when apparmor is in the
loop.
The kernel log shows something interesting. The full log is available
here: http://paste.ubuntu.com/23789099/
Jan 12 23:16:43 autopkgtest kernel: [ 498.616822] audit: type=1400
audit(1484259403.009:67): apparmor="ALLOWED" operation="open"
info="Failed name lookup - disconnected path" error=-13 profile="snap
.test-snapd-tools.cmd//null-/usr/bin/snap//null-/usr/lib/snapd/snap-
confine" name="" pid=25299 comm="snap-confine" requested_mask="r"
denied_mask="r" fsuid=0 ouid=0
The code that triggers this is reproduced below (also visible here
https://github.com/snapcore/snapd/pull/2624/files)
+void sc_reassociate_with_pid1_mount_ns()
+{
+int init_mnt_fd __attribute__ ((cleanup(sc_cleanup_close))) = -1;
+int self_mnt_fd __attribute__ ((cleanup(sc_cleanup_close))) = -1;
+
+debug("checking if the current process shares mount namespace"
+ "with the init process");
+
+init_mnt_fd = open("/proc/1/ns/mnt",
+ O_RDONLY | O_CLOEXEC | O_NOFOLLOW | O_PATH);
+if (init_mnt_fd < 0) {
+die("cannot open mount namespace of the init process (O_PATH)");
+}
+self_mnt_fd = open("/proc/self/ns/mnt",
+ O_RDONLY | O_CLOEXEC | O_NOFOLLOW | O_PATH);
+if (self_mnt_fd < 0) {
+die("cannot open mount namespace of the current process
(O_PATH)");
+}
+char init_buf[128], self_buf[128];
+memset(init_buf, 0, sizeof init_buf);
+if (readlinkat(init_mnt_fd, "", init_buf, sizeof init_buf) < 0) {
+die("cannot perform readlinkat() on the mount namespace file "
+"descriptor of the init process");
+}
+memset(self_buf, 0, sizeof self_buf);
+if (readlinkat(self_mnt_fd, "", self_buf, sizeof self_buf) < 0) {
+die("cannot perform readlinkat() on the mount namespace file "
+"descriptor of the current process");
+}
+if (memcmp(init_buf, self_buf, sizeof init_buf) != 0) {
+debug("the current process does not share mount namespace with "
+ "the init process, re-association required");
+// NOTE: we cannot use O_NOFOLLOW here because that file will
always be a
+// symbolic link. We actually want to open it this way.
+int init_mnt_fd_real
+__attribute__ ((cleanup(sc_cleanup_close))) = -1;
+init_mnt_fd_real = open("/proc/1/ns/mnt", O_RDONLY | O_CLOEXEC);
+if (init_mnt_fd_real < 0) {
+die("cannot open mount namespace of the init process");
+}
+if (setns(init_mnt_fd_real, CLONE_NEWNS) < 0) {
+die("cannot re-associate the mount namespace with the
init process");
+}
+} else {
+debug("re-associating is not required");
+}
+}
The specific part that causes the error is:
+ init_mnt_fd_real = open("/proc/1/ns/mnt", O_RDONLY |
O_CLOEXEC);
The call to open returns -1 and errno set to 13 (EACCES) despite using
attach_disconnected.
The code in question is executed from a seguid root executable that
runs under a complain-mode profile (it is started from a process that
is already confined with such a profile). All of the profiles are
using attach_disconnected.
I can reproduce this issue each time by running:
spread -debug -v qemu:ubuntu-16.04-64:tests/regression/lp-1644439
Against the code in this pull request:
https://github.com/snapcore/snapd/pull/2624
Which is git://github.com/zyga/snapd in the "reassociate-fix" branch
Appropriate qemu images can be made using instructions from:
https://github.com/zyga/spread-qemu-images
I'm also happy to try any test kernels as I can easily run those.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1656121/+subscriptions
__
[Group.of.nepali.translators] [Bug 1658219] Re: flock not mediated by 'k'
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1658219
Title:
flock not mediated by 'k'
Status in AppArmor:
Triaged
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Bug description:
$ cat ./apparmor.profile
#include
profile test {
#include
/bin/bash ixr,
/dev/pts/* rw,
/usr/bin/flock ixr,
# Not blocked:
# aa-exec -p test -- flock -w 1 /tmp/test.lock -c true
/tmp/test.lock rw,
}
$ sudo apparmor_parser -r ./apparmor.profile
$ aa-exec -p test -- flock -w 1 /tmp/test.lock -c true && echo yes
yes
$ ls -l /tmp/test.lock
-rw-rw-r-- 1 jamie jamie 0 Jan 20 15:57 /tmp/test.lock
The flock command uses flock(LOCK_EX) and I expected it to be blocked
due to the lack of 'k'.
apparmor userspace 2.10.95-0ubuntu2.5 (xenial) and 4.9.0-12.13-generic
kernel on amd64.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1658219/+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 1557751] Re: makedumpfile generates kernel version error
This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.4 --- makedumpfile (1:1.5.9-5ubuntu0.4) xenial; urgency=medium * d/p/0006-PATCH-Support-newer-kernels.patch : Support kernel versions up to 4.8 (LP: #1557751) * Turn hardcoded timeo and retrans NFS options into parameters that can be modified in /etc/default/kdump-tools. Also use the NFS defaults (timeo=600, retrans=3) for these parameters. Make those values visible in the 'show' command if NFS is configured (LP: #1641235) * Complete support for kernel versions 4.8 and later : d/p/0007-PATCH-Looking-for-page.compound_order-compound_dtor-.patch, d/p/0008-PATCH-Skip-examining-compound-tail-pages.patch (LP: #1655625) -- Louis Bouchard Wed, 11 Jan 2017 11:33:42 +0100 ** Changed in: makedumpfile (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/1557751 Title: makedumpfile generates kernel version error Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Trusty: Confirmed Status in makedumpfile source package in Xenial: Fix Released Status in makedumpfile source package in Yakkety: Confirmed Bug description: == Comment: #7 - Vaishnavi Bhat - 2016-03-15 06:16:53 == The following warning is generated by makedumpfile * running makedumpfile --dump-dmesg /proc/vmcore /mnt/201602030129/dmesg.201602030129 The kernel version is not supported. The created dumpfile may be incomplete. The makedumpfile version on your machine is # makedumpfile -v makedumpfile: version 1.5.5 (released on 18 Dec 2013) I did a #sudo apt-get source makedumpfile and checked for the sources. In the makedumpfile.h , the LATEST_VERSION is set to #define OLDEST_VERSION KERNEL_VERSION(2, 6, 15)/* linux-2.6.15 */ #define LATEST_VERSION KERNEL_VERSION(4, 1, 0)/* linux-4.1.0 */ where as kernel version on the machine is # uname -r 4.2.0-27-generic Hence we see this mismatch and message as "The kernel version is not supported." We need canonical to change the value of LATEST_VERSION so that we do not see this message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1557751/+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 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash
This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.4 --- makedumpfile (1:1.5.9-5ubuntu0.4) xenial; urgency=medium * d/p/0006-PATCH-Support-newer-kernels.patch : Support kernel versions up to 4.8 (LP: #1557751) * Turn hardcoded timeo and retrans NFS options into parameters that can be modified in /etc/default/kdump-tools. Also use the NFS defaults (timeo=600, retrans=3) for these parameters. Make those values visible in the 'show' command if NFS is configured (LP: #1641235) * Complete support for kernel versions 4.8 and later : d/p/0007-PATCH-Looking-for-page.compound_order-compound_dtor-.patch, d/p/0008-PATCH-Skip-examining-compound-tail-pages.patch (LP: #1655625) -- Louis Bouchard Wed, 11 Jan 2017 11:33:42 +0100 ** Changed in: makedumpfile (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/1655625 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash Status in crash package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Status in crash source package in Xenial: Fix Released Status in makedumpfile source package in Xenial: Fix Released Bug description: [SRU justification] This fix is required to make the crash tool usable. It does also improve makedumpfile filtering of pages. [Impact] Kernel crashes cannot be analysed with the crash tool. makedumpfile incorrectly filter pages. [Fix] Cherry-pick upstream commits fixing those issues. [Test Case] Running crash tool on a kernel crash file will display something like : # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic crash: read error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which renders /dev/mem unusable as a live memory source. crash: trying /proc/kcore as an alternative to /dev/mem crash: seek error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: seek error: kernel virtual address: 82166130 type: "shadow_timekeeper xtime_sec" crash: seek error: kernel virtual address: 81e0d304 type: "init_uts_ns" crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and /var/crash/201701191308/dump.201701191308 do not match! With the fix, the crash command will work as expected Running the crash tool on a vmcore file produced by makedumpfile may return : crash: page excluded: kernel virtual address: <> type: "fill_task_struct" [Regression] None expected as those modifications are part of the Zesty and upstream version. The makedumpfile patches are in Yakkety and Zesty 1.6.0 & after [Original description of the problem] vmcore captured by kdump cannot be opened with crash: % sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic /var/crash/201612282137/dump.201612282137 ... ... base kernel version: 0.8.0 linux_banner: crash: /usr/lib/debug/boot/vmlinux-4 and /var/crash/201612282137/dump.201612282137 do not match! Usage: crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form) crash [OPTION]... [NAMELIST] (live system form) Enter "crash -h" for details. Looks like the 'linux_banner' cannot be understood by crash. And when the vmcore was dumping, this message being showed: [ 729.609196] kdump-tools[5192]: The kernel version is not supported. [ 729.609447] kdump-tools[5192]: The makedumpfile operation may be incomplete. ---uname output--- Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump 2. trigger kdump 3. analyse vmcore with crash Userspace tool common name: crash/makedumpfile The userspace tool has the following bit modes: 64-bit Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4 Userspace tool obtained from project website: na *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016 utsname: sysname: Linux nodename: boblp1 release: 4.8.0-32-generic version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 machine: ppc64le domainname: (none) base kernel version: 4.8.0 verify_namelist: dumpfile /proc/version: Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue D
[Group.of.nepali.translators] [Bug 1641235] Re: Ubuntu 16.10: kdump over nfs did not generate complete vmcore
This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.4 --- makedumpfile (1:1.5.9-5ubuntu0.4) xenial; urgency=medium * d/p/0006-PATCH-Support-newer-kernels.patch : Support kernel versions up to 4.8 (LP: #1557751) * Turn hardcoded timeo and retrans NFS options into parameters that can be modified in /etc/default/kdump-tools. Also use the NFS defaults (timeo=600, retrans=3) for these parameters. Make those values visible in the 'show' command if NFS is configured (LP: #1641235) * Complete support for kernel versions 4.8 and later : d/p/0007-PATCH-Looking-for-page.compound_order-compound_dtor-.patch, d/p/0008-PATCH-Skip-examining-compound-tail-pages.patch (LP: #1655625) -- Louis Bouchard Wed, 11 Jan 2017 11:33:42 +0100 ** Changed in: makedumpfile (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/1641235 Title: Ubuntu 16.10: kdump over nfs did not generate complete vmcore Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Trusty: Confirmed Status in makedumpfile source package in Xenial: Fix Released Status in makedumpfile source package in Yakkety: Confirmed Bug description: == Comment: #0 - HARSHA THYAGARAJA - 2016-11-03 08:05:59 == ---Problem Description--- kdump over nfs did not generate complete vmcore ---uname output--- Linux ltciofvtr-firestone1 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:41:40 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV (Baremetal) - Firestone ---Steps to Reproduce--- 1. Setup NFS 2. Trigger crash: echo c > /proc/sysrq-trigger == Comment: #6 - Kevin W. Rudd - 2016-11-04 16:30:49 == Hi Harsha. It looks like the base kdump NFS functionality works just fine. The known issue with makedumpfile is causing it to drop back to using "cp" to transfer the entire, non-compressed /proc/vmcore image. That's a rather large amount of data to send over to the remote server, and it appears to be sending back an I/O error after the first 122G. Further debug would need to be done to determine if this is a client- side or server-side issue. I recommend first bringing your remote NFS server up to the current release as it is currently a bit down-rev. == Comment: #8 - HARSHA THYAGARAJA - 2016-11-10 02:02:31 == Hi Kevin, I updated my peer to Ubuntu 16.10 and still saw the same observation. A snippet of the problem at hand is pasted below. [ 20.610748] kdump-tools[4559]: Starting kdump-tools: * Mounting NFS mountpoint 150.1.1.20:/home/tools ... [ 53.400516] kdump-tools[4559]: * Dumping to NFS mountpoint 150.1.1.20:/home/tools/201611100158 [ 53.409242] kdump-tools[4559]: * running makedumpfile -c -d 31 /proc/vmcore /mnt/var/crash/9.47.84.18-201611100158/dump-incomplete [ 53.526593] kdump-tools[4559]: get_mem_map: Can't distinguish the memory type. [ 53.527154] kdump-tools[4559]: The kernel version is not supported. [ 53.527488] kdump-tools[4559]: The makedumpfile operation may be incomplete. [ 53.527813] kdump-tools[4559]: makedumpfile Failed. [ 53.528117] kdump-tools[4559]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 90.754092] kdump-tools[4559]: cp: error writing '/mnt/var/crash/9.47.84.18-201611100158/vmcore-incomplete': Input/output error [ 90.754857] kdump-tools[4559]: * kdump-tools: failed to save vmcore in /mnt/var/crash/9.47.84.18-201611100158 [ 90.756155] kdump-tools[4559]: * running makedumpfile --dump-dmesg /proc/vmcore /mnt/var/crash/9.47.84.18-201611100158/dmesg.201611100158 [ 90.758731] kdump-tools[4559]: get_mem_map: Can't distinguish the memory type. [ 90.759089] kdump-tools[4559]: The kernel version is not supported. [ 90.759436] kdump-tools[4559]: The makedumpfile operation may be incomplete. [ 90.759780] kdump-tools[4559]: makedumpfile Failed. [ 90.760094] kdump-tools[4559]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 90.760668] kdump-tools[4559]: * kdump-tools: failed to save dmesg content in /mnt/var/crash/9.47.84.18-201611100158 [ 90.846117] kdump-tools[4559]: Thu, 10 Nov 2016 01:59:56 -0500 [ 90.886629] kdump-tools[4559]: Failed to read reboot parameter file: No such file or directory [ 90.887070] kdump-tools[4559]: Rebooting. == Comment: #13 - Kevin W. Rudd - 2016-11-11 17:12:33 == I was able to replicate this with debugging at both the kdump client and remote NFS server. The server was perfectly happy with the data coming at it, and appeared to be processing a COMMIT request from the client when the client shut down the connection. Looking at the client-side logs after a failure showed th
