[Group.of.nepali.translators] [Bug 1712746] Re: mwifiex causes kernel oops when AP mode is enabled
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: hwe-next Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1712746 Title: mwifiex causes kernel oops when AP mode is enabled Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: When it's in AP mode, there's quite a chance to find kernel oops during reboot. This is caused by the wiphy may be NULL for some reason. It's likely a bug in mwifiex. We've already pinged Marvell and Murata. Before there's a real fix available, we should check wiphy before accessing it. I've tried a 4.13-rc6 kernel. Though it has oops for NULL pointer deference too, it happens in a different function in mwifiex. Thus the workaround for Xenial may or may not help for other series. Will need to reproduce this issue with Zesty and then we can decide whether this workaround should be applied to Zesty. [ 30.701441] BUG: unable to handle kernel NULL pointer dereference at 00f0 [ 30.709511] IP: [] mwifiex_get_cfp+0x49/0x150 [mwifiex] [ 30.716494] PGD 0 [ 30.718575] Oops: [#1] SMP [ 30.721918] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conni [ 30.836915] CPU: 1 PID: 679 Comm: kworker/u5:0 Not tainted 4.4.0-57-generic #78-Ubuntu [ 30.845018] Hardware name: Dell Inc. Edge Gateway 5000/ , BIOS 01.05.00 10/18/2016 [ 30.853218] Workqueue: MWIFIEX_WORK_QUEUE mwifiex_main_work_queue [mwifiex] [ 30.860362] task: 880077c11980 ti: 880075e48000 task.ti: 880075e48000 [ 30.868018] RIP: 0010:[] [] mwifiex_get_cfp+0x49/0x150 [mwifiex] [ 30.877484] RSP: 0018:880075e4bbf8 EFLAGS: 00010202 [ 30.882920] RAX: RBX: 0004 RCX: 0004 [ 30.890221] RDX: 001000110010 RSI: 0004 RDI: 0004 [ 30.897520] RBP: 880075e4bc28 R08: 0003 R09: 0001 [ 30.904821] R10: 0001 R11: 02ff R12: 0095 [ 30.912123] R13: R14: 880075e4 R15: 0095 [ 30.919425] FS: () GS:88007130() knlGS: [ 30.927701] CS: 0010 DS: ES: CR0: 8005003b [ 30.933581] CR2: 00f0 CR3: 01e0a000 CR4: 001006e0 [ 30.940882] Stack: [ 30.942944] 0118 880075e4 8800750c4000 880075e3ed59 [ 30.950592] 0095 880075e3ee01 880075e4bcd0 c05846fc [ 30.958232] 880075e4bc50 8140bcb5 880075e4bc70 [ 30.965873] Call Trace: [ 30.968397] [] mwifiex_parse_single_response_buf+0x1fc/0x560 [mwifiex] [ 30.976772] [] ? find_next_bit+0x15/0x20 [ 30.982490] [] mwifiex_handle_event_ext_scan_report+0x15c/0x340 [mwifiex] [ 30.991139] [] mwifiex_process_sta_event+0x276/0xb40 [mwifiex] [ 30.998806] [] mwifiex_process_event+0x102/0x1c0 [mwifiex] [ 31.006120] [] mwifiex_main_process+0x5de/0x8d0 [mwifiex] [ 31.013346] [] mwifiex_main_work_queue+0x1f/0x30 [mwifiex] [ 31.020650] [] process_one_work+0x165/0x480 [ 31.026624] [] worker_thread+0x4b/0x4c0 [ 31.032240] [] ? process_one_work+0x480/0x480 [ 31.038387] [] kthread+0xd8/0xf0 [ 31.043384] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 31.050071] [] ret_from_fork+0x3f/0x70 [ 31.055596] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 31.062276] Code: 85 c9 0f 84 ef 00 00 00 40 0f b6 de 49 89 fe 41 89 cd 89 df 41 89 d4 e8 46 f1 00 00 84 c0 49 8b 86 e0 13 00 00 0f 84 98 00 [ 31.082756] RIP [] mwifiex_get_cfp+0x49/0x150 [mwifiex] [ 31.089820] RSP [ 31.093392] CR2: 00f0 [ 31.096787] ---[ end trace f3a762be5787f138 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1712746/+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 1737944] Re: linux-gcp: 4.13.0-1003.6 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1738791 phase: Uploaded + kernel-stable-phase-changed:Thursday, 21. December 2017 00:01 UTC + kernel-stable-phase:Promoted to proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1738791 - phase: Uploaded - kernel-stable-phase-changed:Thursday, 21. December 2017 00:01 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1737944 Title: linux-gcp: 4.13.0-1003.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1738791 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/1737944/+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 1704533] Re: French language locale missing : Gnome-Weather
This bug was fixed in the package libgweather - 3.24.1-0ubuntu0.2 --- libgweather (3.24.1-0ubuntu0.2) zesty; urgency=medium * Add langpack-hack.patch: - Rename the gettext template to work around Launchpad issue. This fixes the untranslated weather conditions in the GNOME Weather app. (LP: #1704533) -- Gunnar Hjalmarsson Mon, 11 Dec 2017 20:29:00 +0100 ** Changed in: libgweather (Ubuntu Zesty) Status: Fix Committed => Fix Released ** Changed in: libgweather (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/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: In Progress Status in gnome-weather package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Xenial: Fix Released Status in libgweather source package in Zesty: Fix Released Status in libgweather source package in Artful: Fix Released Bug description: [Impact] The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building libgweather, which makes the libgweather-common binary look for translations in files named "libgweather-3.0.mo". The template name in Rosetta (LP) is "libgweather", so the files provided by the language packs are named "libgweather.mo". This mismatch results in the messages describing the weather type always be displayed in English. The uploaded package works around the issue by setting GETTEXT_PACKAGE to "libgweather". In bionic the template name in Rosetta has been changed to "libgweather-3.0", and thus the workaround will be reversed. [Test Case] * Install French language support * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is displayed in English. * Install these packages from -proposed: - gir1.2-gweather-3.0 - libgweather-3-6 - libgweather-common * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is now displayed in French. [Regression Potential] None. [Original description] In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+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 1704533] Re: French language locale missing : Gnome-Weather
This bug was fixed in the package libgweather - 3.26.0-1ubuntu0.1 --- libgweather (3.26.0-1ubuntu0.1) artful; urgency=medium * Add langpack-hack.patch: - Rename the gettext template to work around Launchpad issue. This fixes the untranslated weather conditions in the GNOME Weather app. (LP: #1704533) -- Gunnar Hjalmarsson Mon, 11 Dec 2017 12:54:00 +0100 ** Changed in: libgweather (Ubuntu Artful) 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/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: In Progress Status in gnome-weather package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Xenial: Fix Released Status in libgweather source package in Zesty: Fix Released Status in libgweather source package in Artful: Fix Released Bug description: [Impact] The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building libgweather, which makes the libgweather-common binary look for translations in files named "libgweather-3.0.mo". The template name in Rosetta (LP) is "libgweather", so the files provided by the language packs are named "libgweather.mo". This mismatch results in the messages describing the weather type always be displayed in English. The uploaded package works around the issue by setting GETTEXT_PACKAGE to "libgweather". In bionic the template name in Rosetta has been changed to "libgweather-3.0", and thus the workaround will be reversed. [Test Case] * Install French language support * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is displayed in English. * Install these packages from -proposed: - gir1.2-gweather-3.0 - libgweather-3-6 - libgweather-common * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is now displayed in French. [Regression Potential] None. [Original description] In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+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 1735046] Re: mkfs.btrfs error checking mount status of loop device backing_file
I just marked xenial explicitly as fixed here. The fix is in all
supported ubuntu releases > trusty.
** Also affects: btrfs-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: btrfs-tools (Ubuntu)
Status: New => Fix Released
** Changed in: btrfs-tools (Ubuntu Trusty)
Status: New => In Progress
** Changed in: btrfs-tools (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: btrfs-tools (Ubuntu Trusty)
Assignee: (unassigned) => Ryan Harper (raharper)
** Also affects: btrfs-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: btrfs-tools (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: btrfs-tools (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1735046
Title:
mkfs.btrfs error checking mount status of loop device backing_file
Status in btrfs-tools package in Ubuntu:
Fix Released
Status in btrfs-tools source package in Trusty:
In Progress
Status in btrfs-tools source package in Xenial:
Fix Released
Bug description:
SRU Template
[Impact]
* Users may be unable to successfully create a btrfs filesystem on
block devices when a loop device is mounted and the backing file
no longer exists. This typically happens in the precense of
overlayroot but may be encountered in other situations.
This affects the btrfs-tools package prior to the 3.13 release.
* Backporting the fix from the upstream repository is required to
allow Trusty MAAS/Cloud images which use overlayrootfs to create
btrfs filesystems in the presence of a loopdevice with a missing
backing file.
* All patches applied are already accepted upstream. Xenial, Artful,
and Bionic are not affected.
[Test Case]
* On a Trusty 14.04 system with a secondary disk (vdb)
- apt-get install btrfs-tools
- truncate -s 1G testloop.img
- losetup /dev/loop0 testloop.img
- mkfs.ext4 /dev/loop0
- mount /dev/loop0 /mnt
- rm testloop.img
- mkfs.btrfs --force /dev/vdb
PASS if mkfs.btrfs returns 0 and /dev/vdb has a btrfs filesystem
FAIL if mkfs.btrfs returns non-zero and /dev/vdb does not have a
btrfs filesystem. mkfs.btrfs returns the error message:
Error: error checking /dev/vdb mount status
[Regression Potential]
* mkfs.btrfs fails to detect that the target device is already mounted
and an existing btrfs filesystem is destroyed.
[Original Description]
# lsb_release -rd
Description:Ubuntu 14.04.5 LTS
Release:14.04
# apt-cache policy btrfs-tools
btrfs-tools:
Installed: 3.12-1ubuntu0.1
Candidate: 3.12-1ubuntu0.1
Version table:
*** 3.12-1ubuntu0.1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.12-1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
# mkfs.btrfs --force /dev/vdd succeeds
# # mkfs.btrfs --force /dev/vdd
Error: error checking /dev/vdd mount status
# strace -f mkfs.btrfs --force /dev/vdd
stat("/dev/loop0", {st_mode=S_IFBLK|0660, st_rdev=makedev(7, 0), ...}) = 0
lstat("/dev", {st_mode=S_IFDIR|0755, st_size=4180, ...}) = 0
lstat("/dev/loop0", {st_mode=S_IFBLK|0660, st_rdev=makedev(7, 0), ...}) = 0
open("/sys/block//loop0/loop/backing_file", O_RDONLY) = 5
fstat(5, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fe8bd73c000
read(5, "/root.tmp.img (deleted)\n", 4096) = 24
close(5)= 0
munmap(0x7fe8bd73c000, 4096)= 0
lstat("/dev", {st_mode=S_IFDIR|0755, st_size=4180, ...}) = 0
lstat("/dev/vdd", {st_mode=S_IFBLK|0660, st_rdev=makedev(253, 48), ...}) = 0
lstat("/root.tmp.img (deleted)", 0x7ffeaa3f0bf0) = -1 ENOENT (No such file or
directory)
close(4)= 0
munmap(0x7fe8bd73d000, 4096)= 0
close(3)= 0
write(2, "Error: error checking /dev/vdd m"..., 44Error: error checking
/dev/vdd mount status
) = 44
exit_group(1) = ?
+++ exited with 1 +++
It appears that mkfs.btrfs doesn't like the loop device, /dev/loop0
which has a deleted backing file.
root@ubuntu:~# cat /sys/block/loop0/loop/backing_file
/root.tmp.img (deleted)
root@ubuntu:~# ls -al /root.tmp.img
ls: cannot access /root.tmp.img: No such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: btrfs-tools 3.12-1ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-135.184-generic 3.13.11-ckt39
Uname: Linux 3.13.0-135-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
[Group.of.nepali.translators] [Bug 1738862] Re: linux-oem: 4.13.0-1012.13 -proposed tracker
Based on master bug #1738823. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => 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/1738862 Title: linux-oem: 4.13.0-1012.13 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.13.0-1011.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1738823 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/1738862/+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 1738862] Re: linux-oem: 4.13.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1738862 Title: linux-oem: 4.13.0-1012.13 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.13.0-1011.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1738823 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/1738862/+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 1738842] Re: linux-hwe-edge: 4.13.0-21.24~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed -- 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/1738842 Title: linux-hwe-edge: 4.13.0-21.24~16.04.1 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.13.0-21.24~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1738823 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/1738842/+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 1739404] Re: Latest security updates reverted fixes for powerpc arch
This bug was fixed in the package percona-xtradb-cluster-5.6 - 5.6.37-26.21-0ubuntu0.17.04.2 --- percona-xtradb-cluster-5.6 (5.6.37-26.21-0ubuntu0.17.04.2) zesty-security; urgency=medium * Restore accidentally dropped changes from 5.6.34-26.19-0ubuntu1.1 (LP: #1739404): - d/p/ibuf-uses-full-memory-barrier-powerpc.patch: This patch implements a full memory barrier for InnoDB mutex entry/exit on PowerPC. - d/p/weak-memory-compat.patch: Removed as is covered by the new patch ibuf-uses-full-memory-barrier-ppc64.patch. -- James Page Wed, 20 Dec 2017 12:30:49 + ** Changed in: percona-xtradb-cluster-5.6 (Ubuntu Zesty) Status: In Progress => Fix Released ** Changed in: percona-xtradb-cluster-5.6 (Ubuntu Xenial) 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/1739404 Title: Latest security updates reverted fixes for powerpc arch Status in percona-xtradb-cluster-5.6 package in Ubuntu: Invalid Status in percona-xtradb-cluster-5.6 source package in Xenial: Fix Released Status in percona-xtradb-cluster-5.6 source package in Zesty: Fix Released Bug description: The latest security updates for pxc-5.6 dropped changes made for Xenial (and Zesty) under 5.6.34-26.19-0ubuntu0.16.04.2 related to deployment on power architecture (see bug 1657256). Impact of this is that at some point in time PXC will crash on PPC64EL based deployments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.6/+bug/1739404/+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 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
This bug was fixed in the package initramfs-tools - 0.125ubuntu13 --- initramfs-tools (0.125ubuntu13) bionic; urgency=medium [ Oliver Grawert ] * make fixrtc catch "n/a" string and fall back to a sane value for the date command instead (LP: #1623125) -- Michael Vogt Wed, 20 Dec 2017 09:44:43 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Bug description: [TEST CASE] * this will be tested by the snappy team * without this fix the dragonboard will not boot on a freshly written image [REGRESSION POTENTIAL] * low as it only fixes an invalid string trying to boot a new dragonboard image results in: error: assertion is signed with expired public key "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by canonical this is due to a clock skew that should normally be catched by the fixrtc script in the initrd. the script is supposed to check the last mount time of the writable disk (SD card) and if this does not exist, fall back to the filesystem creation time ... in former versions of mkfs.ext4 the last mount time filed was simply left empty, so this fallback worked fine ... in xenial the fields now look like: Filesystem created: Tue Sep 13 17:32:20 2016 Last mount time: n/a Last write time: Tue Sep 13 17:32:20 2016 due to the script running with "set -e" it falls over on the "n/a" and exists before falling back to creation time, there needs to be a check added for the "n/a" string now. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+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 1738842] Re: linux-hwe-edge: 4.13.0-21.24~16.04.1 -proposed tracker
Copying certification-testing from #1736121. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => 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/1738842 Title: linux-hwe-edge: 4.13.0-21.24~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.13.0-21.24~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1738823 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/1738842/+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 1738842] Re: linux-hwe-edge: 4.13.0-21.24~16.04.1 -proposed tracker
Copying regression-testing from #1736121. ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1738842 Title: linux-hwe-edge: 4.13.0-21.24~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.13.0-21.24~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1738823 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/1738842/+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 1738862] Re: linux-oem: 4.13.0-1012.13 -proposed tracker
Copying regression-testing from #1736124. ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => 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/1738862 Title: linux-oem: 4.13.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.13.0-1011.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1738823 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/1738862/+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 1735532] Re: Include uvp-monitor in xenial and trusty, update artful
This bug was fixed in the package uvp-monitor - 2.2.0.316-0ubuntu1~17.10.1 --- uvp-monitor (2.2.0.316-0ubuntu1~17.10.1) artful; urgency=medium * Backport to artful (LP: #1735532). * New upstream release. * Add debian/watch. * debian/control: switch priority from extra to optional. * debian/patches/init.d_script_fixes.patch: - Fix some lintian errors with the init.d script by adding local_fs dependency on start/stop. -- Łukasz 'sil2100' Zemczak Thu, 30 Nov 2017 12:08:03 +0100 ** Changed in: uvp-monitor (Ubuntu Artful) 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/1735532 Title: Include uvp-monitor in xenial and trusty, update artful Status in uvp-monitor package in Ubuntu: Fix Released Status in uvp-monitor source package in Trusty: New Status in uvp-monitor source package in Xenial: New Status in uvp-monitor source package in Artful: Fix Released Bug description: [Impact] As per T-Systems request, we have packaged the uvp-monitor daemon for their cloud images resource monitoring. The main Ubuntu images officially available on the T-Systems cloud are xenial and trusty images. We would like to request backporting of the new uvp-monitor package to those series so that we can get those pre-installed on their images. It's a direct request from the cloud provider as only this way the packages can have the same functionality as other linux distributions on this cloud. The packages will not work on non-T-Systems instances and will be only consumed on that specific cloud. We're also updating artful here as it has an older version and we would like to keep all supported series up-to-date with the same version. [Test Case] * Install uvp-monitor from -proposed * Check if uvp-monitor is running (systemctl status uvp-monitor) * Go to the ECS page on the T-Systems interface, go to Monitoring and check if Disk Usage is reported (note: some time might be needed for the data to be gathered) * Reboot the instance and confirm that uvp-monitor is still running [Regression Potential] None. The package will only be installed and enabled on T-Systems cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvp-monitor/+bug/1735532/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
This bug was fixed in the package linux - 4.13.0-21.24 --- linux (4.13.0-21.24) artful; urgency=low * linux: 4.13.0-21.24 -proposed tracker (LP: #1738823) * Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models (LP: #1734147) - [Config] CONFIG_SPI_INTEL_SPI_PLATFORM=n -- Thadeu Lima de Souza Cascardo Mon, 18 Dec 2017 14:13:33 -0200 ** Changed in: linux (Ubuntu Artful) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Artful) 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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects Acer Aspire E5-771G. --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to
[Group.of.nepali.translators] [Bug 1739033] Re: Corosync: Assertion 'sender_node != NULL' failed when bind iface is ready after corosync boots
** Changed in: corosync (Ubuntu)
Status: New => Fix Released
** Changed in: corosync (Ubuntu Trusty)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: corosync (Ubuntu Xenial)
Assignee: (unassigned) => Victor Tapia (vtapia)
** Changed in: corosync (Ubuntu Xenial)
Status: New => In Progress
** Changed in: corosync (Ubuntu Trusty)
Status: New => In Progress
** Changed in: corosync (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: corosync (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1739033
Title:
Corosync: Assertion 'sender_node != NULL' failed when bind iface is
ready after corosync boots
Status in corosync package in Ubuntu:
Fix Released
Status in corosync source package in Trusty:
In Progress
Status in corosync source package in Xenial:
In Progress
Bug description:
[Description]
Corosync sigaborts if it starts before the interface it has to bind to
is ready.
On boot, if no interface in the bindnetaddr range is up/configured,
corosync binds to lo (127.0.0.1). Once an applicable interface is up,
corosync crashes with the following error message:
corosync: votequorum.c:2019: message_handler_req_exec_votequorum_nodeinfo:
Assertion `sender_node != NULL' failed.
Aborted (core dumped)
The last log entries show that the interface is trying to join the
cluster:
Dec 19 11:36:05 [22167] xenial-pacemaker corosync debug [TOTEM ]
totemsrp.c:2089 entering OPERATIONAL state.
Dec 19 11:36:05 [22167] xenial-pacemaker corosync notice [TOTEM ]
totemsrp.c:2095 A new membership (169.254.241.10:444) was formed. Members
joined: 704573706
During the quorum calculation, the generated nodeid (704573706) for
the node is being used instead of the nodeid specified in the
configuration file (1), and the assert fails because the nodeid is not
present in the member list. Corosync should use the correct nodeid and
continue running after the interface is up, as shown in a fixed
corosync boot:
Dec 19 11:50:56 [4824] xenial-corosync corosync notice [TOTEM ]
totemsrp.c:2095 A new membership (169.254.241.10:80) was formed.
Members joined: 1
[Environment]
Xenial 16.04.3
Packages:
ii corosync 2.3.5-3ubuntu1amd64cluster engine
daemon and utilities
ii libcorosync-common4:amd642.3.5-3ubuntu1amd64cluster engine
common library
[Reproducer]
Config:
totem {
version: 2
member {
memberaddr: 169.254.241.10
}
member {
memberaddr: 169.254.241.20
}
transport: udpu
crypto_cipher: none
crypto_hash: none
nodeid: 1
interface {
ringnumber: 0
bindnetaddr: 169.254.241.0
mcastport: 5405
ttl: 1
}
}
quorum {
provider: corosync_votequorum
expected_votes: 2
}
nodelist {
node {
ring0_addr: 169.254.241.10
nodeid: 1
}
node {
ring0_addr: 169.254.241.20
nodeid: 2
}
}
1. ifdown interface (169.254.241.10)
2. start corosync (/usr/sbin/corosync -f)
3. ifup interface
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1739033/+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 1738842] Re: linux-hwe-edge: 4.13.0-21.24~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/promote-to-security 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/1738842 Title: linux-hwe-edge: 4.13.0-21.24~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.13.0-21.24~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1738823 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/1738842/+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 1738862] Re: linux-oem: 4.13.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/promote-to-security 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/1738862 Title: linux-oem: 4.13.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.13.0-1011.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1738823 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/1738862/+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 1739418] [NEW] Please build minimized images in a 1GiB image
Public bug reported: [Impact] * Without the fix the initial size of the image is ~2.2GiB, even for minimized images. Changing it to 1GiB allows detecting an increase in packages' installed installed size in case they would exceed this smaller limit. * Minimized images are generated for Xenial, too, and having this limit in effect may help keeping images small. [Test Case] * Generate all minimized an non-minimized images to see that all the builds still succeed. [Regression Potential] * Since partitions images are expanded to pre-defined sizes at the end of image generation this change should not change the resulting image sizes where having free space is needed at run-time. * The change may break building images, hence the tests in the Test Cases section. * The change is tested extensively in Bionic ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Assignee: Balint Reczey (rbalint) Status: In Progress ** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released ** Changed in: livecd-rootfs (Ubuntu Xenial) Assignee: (unassigned) => Balint Reczey (rbalint) -- 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/1739418 Title: Please build minimized images in a 1GiB image Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: In Progress Bug description: [Impact] * Without the fix the initial size of the image is ~2.2GiB, even for minimized images. Changing it to 1GiB allows detecting an increase in packages' installed installed size in case they would exceed this smaller limit. * Minimized images are generated for Xenial, too, and having this limit in effect may help keeping images small. [Test Case] * Generate all minimized an non-minimized images to see that all the builds still succeed. [Regression Potential] * Since partitions images are expanded to pre-defined sizes at the end of image generation this change should not change the resulting image sizes where having free space is needed at run-time. * The change may break building images, hence the tests in the Test Cases section. * The change is tested extensively in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1739418/+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 1739033] Re: Corosync: Assertion 'sender_node != NULL' failed when bind iface is ready after corosync boots
** Also affects: corosync (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Trusty)
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/1739033
Title:
Corosync: Assertion 'sender_node != NULL' failed when bind iface is
ready after corosync boots
Status in corosync package in Ubuntu:
New
Status in corosync source package in Trusty:
New
Status in corosync source package in Xenial:
New
Bug description:
[Description]
Corosync sigaborts if it starts before the interface it has to bind to
is ready.
On boot, if no interface in the bindnetaddr range is up/configured,
corosync binds to lo (127.0.0.1). Once an applicable interface is up,
corosync crashes with the following error message:
corosync: votequorum.c:2019: message_handler_req_exec_votequorum_nodeinfo:
Assertion `sender_node != NULL' failed.
Aborted (core dumped)
The last log entries show that the interface is trying to join the
cluster:
Dec 19 11:36:05 [22167] xenial-pacemaker corosync debug [TOTEM ]
totemsrp.c:2089 entering OPERATIONAL state.
Dec 19 11:36:05 [22167] xenial-pacemaker corosync notice [TOTEM ]
totemsrp.c:2095 A new membership (169.254.241.10:444) was formed. Members
joined: 704573706
During the quorum calculation, the generated nodeid (704573706) for
the node is being used instead of the nodeid specified in the
configuration file (1), and the assert fails because the nodeid is not
present in the member list. Corosync should use the correct nodeid and
continue running after the interface is up, as shown in a fixed
corosync boot:
Dec 19 11:50:56 [4824] xenial-corosync corosync notice [TOTEM ]
totemsrp.c:2095 A new membership (169.254.241.10:80) was formed.
Members joined: 1
[Environment]
Xenial 16.04.3
Packages:
ii corosync 2.3.5-3ubuntu1amd64cluster engine
daemon and utilities
ii libcorosync-common4:amd642.3.5-3ubuntu1amd64cluster engine
common library
[Reproducer]
Config:
totem {
version: 2
member {
memberaddr: 169.254.241.10
}
member {
memberaddr: 169.254.241.20
}
transport: udpu
crypto_cipher: none
crypto_hash: none
nodeid: 1
interface {
ringnumber: 0
bindnetaddr: 169.254.241.0
mcastport: 5405
ttl: 1
}
}
quorum {
provider: corosync_votequorum
expected_votes: 2
}
nodelist {
node {
ring0_addr: 169.254.241.10
nodeid: 1
}
node {
ring0_addr: 169.254.241.20
nodeid: 2
}
}
1. ifdown interface (169.254.241.10)
2. start corosync (/usr/sbin/corosync -f)
3. ifup interface
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1739033/+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 1721261] Re: [SRU] Release minimized image related changes to Xenial
** Changed in: livecd-rootfs (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/1721261 Title: [SRU] Release minimized image related changes to Xenial Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Bug description: [Impact] * Ability to generate minimized images is a new feature of livecd-rootfs. Minimized images have smaller footprint on disk, may not use initramfs to boot and may have smaller RAM footprint as well. * Using minimal images can save bandwidth and system resources and we would like to make those improvements available for Xenial users. [Test Case] * A new autopkgtest (minimized) was added to test building minimized images. The test logs show the generated image sizes for ubuntu-cpc images with and without minimization and the minimized images have to be smaller. [Regression Potential] * The changes should not affect images which are not minimized but the minimized images may not boot on some systems. For example the Linux kernel does not boot in a Vagrant VM without initramfs, but the minimized Vagrant image does not include initramfs. * In case the effect of changes are not limited to the minimized image they may make packages missing from regular images and/or may make the regular images unbootable. [Other Info] * The current patch works around the 'minimized' autopkgtest failure on ppc64el which affects Artful and can be observed when the Linux kernel package does not depend on initramfs-tools (LP: #1700972) thus the minimized images don't include initramfs support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1721261/+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 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
** Also affects: ubuntu-fan (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Bionic) Importance: Critical Assignee: Stefan Bader (smb) Status: Confirmed ** Also affects: ubuntu-fan (Ubuntu Zesty) 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/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures Status in juju: Invalid Status in OPNFV: Fix Committed Status in ubuntu-fan package in Ubuntu: Confirmed Status in ubuntu-fan source package in Xenial: Fix Committed Status in ubuntu-fan source package in Zesty: New Status in ubuntu-fan source package in Artful: New Status in ubuntu-fan source package in Bionic: Confirmed Bug description: I'm seeing this error as the status of multiple containers in my deploy: http://paste.ubuntu.com/26166720/ I can't connect to the parent machines anymore either - it seems networking is totally hosed on the machines. This is with juju 2.3.1. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+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 1738842] Re: linux-hwe-edge: 4.13.0-21.24~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1738842 Title: linux-hwe-edge: 4.13.0-21.24~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.13.0-21.24~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1738823 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/1738842/+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 1738862] Re: linux-oem: 4.13.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1738862 Title: linux-oem: 4.13.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.13.0-1011.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1738823 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/1738862/+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 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
** Changed in: snappy Status: Triaged => Fix Released ** Changed in: initramfs-tools-ubuntu-core (Ubuntu) Status: Triaged => Confirmed ** Changed in: initramfs-tools-ubuntu-core (Ubuntu) Status: Confirmed => Fix Released ** Changed in: initramfs-tools-ubuntu-core (Ubuntu Xenial) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Bug description: [TEST CASE] * this will be tested by the snappy team * without this fix the dragonboard will not boot on a freshly written image [REGRESSION POTENTIAL] * low as it only fixes an invalid string trying to boot a new dragonboard image results in: error: assertion is signed with expired public key "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by canonical this is due to a clock skew that should normally be catched by the fixrtc script in the initrd. the script is supposed to check the last mount time of the writable disk (SD card) and if this does not exist, fall back to the filesystem creation time ... in former versions of mkfs.ext4 the last mount time filed was simply left empty, so this fallback worked fine ... in xenial the fields now look like: Filesystem created: Tue Sep 13 17:32:20 2016 Last mount time: n/a Last write time: Tue Sep 13 17:32:20 2016 due to the script running with "set -e" it falls over on the "n/a" and exists before falling back to creation time, there needs to be a check added for the "n/a" string now. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+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 1739404] Re: Latest security updates reverted fixes for powerpc arch
** Also affects: percona-xtradb-cluster-5.6 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: percona-xtradb-cluster-5.6 (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: percona-xtradb-cluster-5.6 (Ubuntu Xenial) Status: New => Triaged ** Changed in: percona-xtradb-cluster-5.6 (Ubuntu Zesty) Status: New => Triaged ** Changed in: percona-xtradb-cluster-5.6 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: percona-xtradb-cluster-5.6 (Ubuntu Zesty) Importance: Undecided => High ** Changed in: percona-xtradb-cluster-5.6 (Ubuntu) Status: Confirmed => Invalid ** Description changed: The latest security updates for pxc-5.6 dropped changes made for Xenial (and Zesty) under 5.6.34-26.19-0ubuntu0.16.04.2 related to deployment on - power architecture. + power architecture (see bug 1657256). -- 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/1739404 Title: Latest security updates reverted fixes for powerpc arch Status in percona-xtradb-cluster-5.6 package in Ubuntu: Invalid Status in percona-xtradb-cluster-5.6 source package in Xenial: Triaged Status in percona-xtradb-cluster-5.6 source package in Zesty: Triaged Bug description: The latest security updates for pxc-5.6 dropped changes made for Xenial (and Zesty) under 5.6.34-26.19-0ubuntu0.16.04.2 related to deployment on power architecture (see bug 1657256). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.6/+bug/1739404/+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 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
** Also affects: initramfs-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: initramfs-tools-ubuntu-core (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: + [TEST CASE] + * this will be tested by the snappy team + * without this fix the dragonboard will not boot on a freshly written image + + trying to boot a new dragonboard image results in: error: assertion is signed with expired public key "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by canonical this is due to a clock skew that should normally be catched by the fixrtc script in the initrd. the script is supposed to check the last mount time of the writable disk (SD card) and if this does not exist, fall back to the filesystem creation time ... in former versions of mkfs.ext4 the last mount time filed was simply left empty, so this fallback worked fine ... in xenial the fields now look like: Filesystem created: Tue Sep 13 17:32:20 2016 Last mount time: n/a Last write time: Tue Sep 13 17:32:20 2016 due to the script running with "set -e" it falls over on the "n/a" and exists before falling back to creation time, there needs to be a check added for the "n/a" string now. ** Description changed: [TEST CASE] * this will be tested by the snappy team * without this fix the dragonboard will not boot on a freshly written image + [REGRESSION POTENTIAL] + * low as it only fixes an invalid string trying to boot a new dragonboard image results in: error: assertion is signed with expired public key "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by canonical this is due to a clock skew that should normally be catched by the fixrtc script in the initrd. the script is supposed to check the last mount time of the writable disk (SD card) and if this does not exist, fall back to the filesystem creation time ... in former versions of mkfs.ext4 the last mount time filed was simply left empty, so this fallback worked fine ... in xenial the fields now look like: Filesystem created: Tue Sep 13 17:32:20 2016 Last mount time: n/a Last write time: Tue Sep 13 17:32:20 2016 due to the script running with "set -e" it falls over on the "n/a" and exists before falling back to creation time, there needs to be a check added for the "n/a" string now. -- 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/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Triaged Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools-ubuntu-core package in Ubuntu: Triaged Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: New Bug description: [TEST CASE] * this will be tested by the snappy team * without this fix the dragonboard will not boot on a freshly written image [REGRESSION POTENTIAL] * low as it only fixes an invalid string trying to boot a new dragonboard image results in: error: assertion is signed with expired public key "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by canonical this is due to a clock skew that should normally be catched by the fixrtc script in the initrd. the script is supposed to check the last mount time of the writable disk (SD card) and if this does not exist, fall back to the filesystem creation time ... in former versions of mkfs.ext4 the last mount time filed was simply left empty, so this fallback worked fine ... in xenial the fields now look like: Filesystem created: Tue Sep 13 17:32:20 2016 Last mount time: n/a Last write time: Tue Sep 13 17:32:20 2016 due to the script running with "set -e" it falls over on the "n/a" and exists before falling back to creation time, there needs to be a check added for the "n/a" string now. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+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
