[Group.of.nepali.translators] [Bug 1674273] Re: Resolver ignores ndots option
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) 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/1674273 Title: Resolver ignores ndots option Status in glibc package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in glibc source package in Xenial: Confirmed Status in linux source package in Xenial: Invalid Bug description: This is a re-report of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/401202 since that one was apparently closed as no-fix simply because it was too old. This still occurs in xenial. Original description: Regardless of ndots option in /etc/resolv.conf, when NXDOMAIN is returned from the DNS server then resolver always try another attempt with the original name extended by what is in search option. For example, if you're looking for very.long.url.nowhere and there is a line "search ubuntu.com" in resolv.conf you will get addres of server very.long.url.nowhere.ubuntu.com if such exists. It is incorrect, it should occurs only for urls having less that ndots option dots in its name. My system is a standard Ubuntu Xenial desktop amd64 using network manager and the default configured Wired Connection 1 (i.e. DHCP). To reproduce: - sudo install /dev/fd/0 /etc/NetworkManager/dnsmasq.d/domain <<<'log-queries=extra' - sudo killall dnsmasq - ping some.long.non-existent.name - Watch /var/log/syslog In my case: Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 query[A] some.long.non-existent.name from 127.0.0.1 Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 forwarded some.long.non-existent.name to 192.168.5.1 Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 reply some.long.non-existent.name is NXDOMAIN Mar 20 23:19:22 eragon dnsmasq[27367]: 47 127.0.0.1/52417 query[A] some.long.non-existent.name.sebunger.dnsalias.org from 127.0.0.1 Mar 20 23:19:22 eragon dnsmasq[27367]: 47 127.0.0.1/52417 forwarded some.long.non-existent.name.sebunger.dnsalias.org to 192.168.5.1 Mar 20 23:19:23 eragon dnsmasq[27367]: 47 127.0.0.1/52417 reply some.long.non-existent.name.sebunger.dnsalias.org is Mar 20 23:19:23 eragon dnsmasq[27367]: 47 127.0.0.1/52417 reply sebunger.dnsalias.org is 203.173.156.30 My /etc/resolv.conf (which is a sym-link to ../run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.1.1 search sebunger.dnsalias.org options ndots:1 (I added the options ndots with no effect) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/pcmC1D0c', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3 NonfreeKernelModules: nvidia_uvm nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=/dev/mapper/vg0-root ro rootdelay=120 quiet splash ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 RfKill: Tags: xenial xenial Uname: Linux 4.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy kvm lpadmin plugdev sambashare ssh sudo users video _MarkForUpload: True dmi.bios.date: 06/12/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: GA-MA770-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd06/12/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA770-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to:
[Group.of.nepali.translators] [Bug 1766401] Re: full config file wiped after apt-upgrade issued
This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: cloud-init 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/1766401 Title: full config file wiped after apt-upgrade issued Status in cloud-images: New Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Artful: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in cloud-init source package in Cosmic: Fix Released Bug description: === Begin SRU Template === [Impact] Upgrades of cloud-init on official Ubuntu 16.04 and 17.10 images running on IBM public cloud will be unreachable after a reboot. This is because cloud-init incorrectly recognizes the newly added 'IBMCloud' as the datasource to use and skips use of the previously used ConfigDrive or NoCloud datasource. This is because a.) Official 16.04 and 17.10 images of Ubuntu have seeded data in their /var/lib/cloud/seed/ directory that was used on first boot and should be continued to be used. b.) IBMCloud's datasource in some scenarios appears looks similar to that of Config Drive. The version of cloud-init in xenial and artful checks to disable config-drive in order to identify the IBMCloud datasource. That should not happen unless the IBMCloud datasource is enabled, which is configured off in those images. The fix is to continue using the existing datasource on those images. [Test Case] * Launch an image on IBM public cloud. * add -proposed * apt-get update && apt-get install cloud-init * reboot * ssh back in If you are able to ssh back in, then this bug has been fixed. [Regression Potential] This specific fix is tightly contained down the path involved in IBM cloud. The most likely failure scenario would be failure in 18.04 images which do not have the additional datasources built into the images. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=11172924 === End SRU Template === file: 50-cloud-init.cfg wiped of it's initial (working) configuration after a standard apt-upgrade was issued. Cloud provider is SoftLayer. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1766401/+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 1770712] Re: It would be nice if cloud-init provides full version in logs
This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: cloud-init 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/1770712 Title: It would be nice if cloud-init provides full version in logs Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Artful: Confirmed Status in cloud-init source package in Bionic: Confirmed Status in cloud-init source package in Cosmic: Fix Released Bug description: Cloud-init rsyslog has the major version of cloud-init: May 11 17:40:51 maas-enlisting-node cloud-init[550]: Cloud-init v. 18.2 running 'init-local' at Fri, 11 May 2018 17:40:47 +. Up 15.63 seconds. However, it would be nice if it places the whole version, so that we can now exactly what version of cloud-init its running, e.g: May 11 17:40:51 maas-enlisting-node cloud-init[550]: Cloud-init v. 18.2 (27-g6ef92c98-0ubuntu1~18.04.1) running 'init-local' at Fri, 11 May 2018 17:40:47 +. Up 15.63 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1770712/+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 1774666] Re: Bond interfaces stuck at 1500 MTU on Bionic
This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: cloud-init 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/1774666 Title: Bond interfaces stuck at 1500 MTU on Bionic Status in cloud-init: Fix Released Status in MAAS: Invalid Status in cloud-init package in Ubuntu: Fix Released Status in netplan.io package in Ubuntu: Confirmed Status in cloud-init source package in Xenial: New Status in netplan.io source package in Xenial: Invalid Status in cloud-init source package in Artful: New Status in netplan.io source package in Artful: Invalid Status in cloud-init source package in Bionic: New Status in netplan.io source package in Bionic: Invalid Status in cloud-init source package in Cosmic: Fix Released Status in netplan.io source package in Cosmic: Confirmed Bug description: When deploying a machine through MAAS with bonded network interfaces, the bond does not have a 9000 byte MTU applied despite the attached VLANs having had a 9000 MTU explicitly set. The MTU size is set on the bond members, but not on the bond itself in Netplan. Consequently, when the bond is brought up, the interface MTU is decreased from 9000 to 1500. Manually changing the interface MTU after boot is successful. This is not observed when deploying Xenial on the same machine. The bond comes up at the expected 9000 byte MTU. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1774666/+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 1761096] Re: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed
I confirm that every second $ systemctl restart dnsmasq hangs Also I confirm that removing squid resolved the situation. I found that it does this: 1. /bin/sh /etc/init.d/dnsmasq systemd-stop-resolvconf 2. /bin/sh /etc/init.d/dnsmasq systemd-start-resolvconf Both will call hooks like: 0 0 11642 11634 20 0 4364 660 wait S? 0:00 \_ run-parts --arg=-a --arg=lo.dnsmasq /etc/resolvconf/update.d 0 0 11659 11642 20 0 4364 664 wait S? 0:00 \_ run-parts /etc/resolvconf/update-libc.d 0 0 11672 11659 20 0 4504 704 wait S? 0:00 \_ /bin/sh /etc/resolvconf/update-libc.d/squid 0 0 11673 11672 20 0 4504 1648 wait S? 0:00 \_ /bin/sh /usr/sbin/invoke-rc.d squid reload 4 0 11691 11673 20 0 24888 1388 poll_s S? 0:00 \_ systemctl reload squid.service This is what actually times out - the squid hook. The "systemctl reload squid.service" call seems to take too long every second time?! A single "systemctl reload squid.service" for these seems to take ~100 seconds for me. OTOH a direct call to it is fast every time. This needs to be debugged in detail, but seems well reproducible. ** Also affects: dnsmasq (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: dnsmasq (Ubuntu Xenial) Status: New => Confirmed ** Changed in: dnsmasq (Ubuntu) Status: New => Fix Released ** Changed in: dnsmasq (Ubuntu Xenial) Importance: Undecided => High ** Tags added: server-next ** Also affects: squid (Ubuntu) Importance: Undecided Status: New ** Changed in: squid (Ubuntu Xenial) Status: New => Confirmed ** Changed in: squid (Ubuntu Xenial) Importance: Undecided => High ** Changed in: squid (Ubuntu) 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/1761096 Title: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed Status in dnsmasq package in Ubuntu: Fix Released Status in squid package in Ubuntu: Fix Released Status in dnsmasq source package in Xenial: Confirmed Status in squid source package in Xenial: Confirmed Bug description: Setup to reproduce: Ubuntu Xenial amd64 net install iso from http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer- amd64/current/images/netboot/mini.iso Install system with mostly defaults + LVM + OpenSSH server Note that this bug applies to both DHCP and static IP+DNS network configurations Once server rebooted and is available, log in and install dnsmasq + squid: apt-get update && apt-get install squid dnsmasq output of this can be found at https://pastebin.com/9Atuipju journalctl -xe output at https://pastebin.com/uLhfM4jN Furthermore at this point I can run alternating errors root@ubuntu-min:~# date ; service dnsmasq start ; date Wed Apr 4 09:18:07 CEST 2018 Wed Apr 4 09:18:07 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq stop ; date Wed Apr 4 09:18:39 CEST 2018 Wed Apr 4 09:18:39 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq start ; date Wed Apr 4 09:19:10 CEST 2018 Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl status dnsmasq.service" and "journalctl -xe" for details. Wed Apr 4 09:20:40 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq start ; date Wed Apr 4 09:42:57 CEST 2018 Wed Apr 4 09:42:57 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq stop ; date Wed Apr 4 09:43:14 CEST 2018 Wed Apr 4 09:43:14 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq start ; date Wed Apr 4 09:43:26 CEST 2018 Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl status dnsmasq.service" and "journalctl -xe" for details. Wed Apr 4 09:44:56 CEST 2018 and so on... Each and every 1 out of 2 stop/start cycle fails in 1m30s timeout Complete journalctl -xe output attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1761096/+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 1707136] Re: ryncd does not start when RSYNC_ENABLE is specified
Per former comments marking as fixed and adding Xenial task. It is still an issue in Xenial, but since no one here was participating I wonder about the severity. Also we would certainly not backport the fix that was taken. I filtered it a bit and it looks like http://paste.ubuntu.com/p/TNvQpqbNRb/ So with that you still won't be able to get it through /etc/default/rsyncd. All you'd find is a comment in there how to do it now. Marking it low due to that ** Also affects: rsync (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: rsync (Ubuntu) Status: Confirmed => Fix Released ** Changed in: rsync (Ubuntu Xenial) Status: New => Triaged ** Changed in: rsync (Ubuntu Xenial) Importance: Undecided => Low -- 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/1707136 Title: ryncd does not start when RSYNC_ENABLE is specified Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Xenial: Triaged Status in rsync package in Debian: Fix Released Bug description: In the good old days, all you needed to ensure rsyncd started upon boot was to set RSYNC_ENABLE to true in /etc/default/rsync. With the systemd transition, this broke, and you need to manually issue systemctl enable rsync in order for it to be wanted by multi-user.target, which causes it to start upon boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1707136/+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 1743873] Re: rsync version for xenial
For the usual SRU policy [1] it is unlikely and would require a lot of exceptions and checks to take the full 3.1.2. You'd really have to show that it is not working at all. Otherwise usually only individual fixes are backported. The other issue you mentioned is already tracked on it's own so I won't consider that for the xenial task here for it. [1]: https://wiki.ubuntu.com/StableReleaseUpdates ** Also affects: rsync (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: rsync (Ubuntu) Status: Confirmed => Fix Released ** Changed in: rsync (Ubuntu Xenial) Status: New => Opinion ** Changed in: rsync (Ubuntu Xenial) Importance: Undecided => Low -- 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/1743873 Title: rsync version for xenial Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Xenial: Opinion Status in rsync package in Debian: Fix Released Bug description: Any chance that rsync could be updated to 3.1.2 for xenial? The --backup-dir option in 3.1.1 doesn't work properly - it creates empty directories even when no files need to be put in them. Thanks, -Jeff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1743873/+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 1521173] Re: AER: Corrected error received: id=00e0
** Changed in: linux (Ubuntu) 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Bug description: Note: Current workaround is to add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+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 1776359] Re: linux-raspi2: 4.4.0-1092.100 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate 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/1776359 Title: linux-raspi2: 4.4.0-1092.100 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1776822 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/1776359/+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 1776361] Re: linux-snapdragon: 4.4.0-1095.100 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate 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/1776361 Title: linux-snapdragon: 4.4.0-1095.100 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1776822 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/1776361/+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 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
This bug was fixed in the package menu - 2.1.47ubuntu2.1 --- menu (2.1.47ubuntu2.1) bionic; urgency=medium * Switch triggers to use noawait (LP: #1768905) -- Julian Andres Klode Tue, 05 Jun 2018 10:48:23 -0700 ** Changed in: menu (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in menu source package in Xenial: Fix Committed Status in apt source package in Artful: Confirmed Status in menu source package in Artful: Fix Released Status in apt source package in Bionic: Confirmed Status in menu source package in Bionic: Fix Released Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+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 1396654] Re: C++ demangling support missing from perf
** Also affects: linux-meta-hwe (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-meta-hwe (Ubuntu Zesty) ** No longer affects: linux-meta-hwe (Ubuntu Yakkety) -- 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/1396654 Title: C++ demangling support missing from perf Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe package in Ubuntu: New Status in linux source package in Xenial: Incomplete Status in linux-meta-hwe source package in Xenial: New Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Released Bug description: Hi, It appears that C++ demangling support is missing from linux-tools-3.16.0-24, on Utopic on arm64. Could the following please be added to the build dependencies for that package: libiberty-dev binutils-dev Installing the above and rebuilding the package fixed the problem for me. Cheers, -- Steve --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.7-0ubuntu8 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied DistroRelease: Ubuntu 14.10 IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 RfKill: Error: [Errno 2] No such file or directory Tags: utopic utopic Uname: Linux 3.16.0-24-generic aarch64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to utopic on 2014-11-17 (9 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654/+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 1776337] Re: linux-oem: 4.13.0-1031.34 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1776333 phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Wednesday, 20. June 2018 08:30 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1776333 - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Wednesday, 20. June 2018 08:30 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/1776337 Title: linux-oem: 4.13.0-1031.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1776333 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776337/+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 1683445] Re: E6430 brightness control not working
** Also affects: gnome-settings-daemon (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unity-settings-daemon (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/1683445 Title: E6430 brightness control not working Status in GNOME Settings Daemon: Fix Released Status in Nouveau Xorg driver: Won't Fix Status in OEM Priority Project: New Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon source package in Xenial: New Status in unity-settings-daemon source package in Xenial: New Status in gnome-settings-daemon source package in Zesty: Fix Released Status in unity-settings-daemon source package in Zesty: Triaged Bug description: Impact -- It looks like GNOME's brightness control simply used the first backlight device it saw instead of one currently in use. This meant that the brightness control would not work on some computers with multiple GPUs. Test Case - From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update. Restart. Does the brightness control now work correctly? Regression Potential This looks like a minimal fix for this issue. It was accepted as part of gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros will be upgrading to. Original Bug Report --- The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source Nouveau driver shows the brightness slider moving but does not affect the brightness. When using the kernel boot option acpi_backlight=vendor , the brightness control works. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2081 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Apr 17 20:00:56 2017 HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6 InstallationDate: Installed on 2017-04-10 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: Dell Inc. Latitude E6430 ProcFB: 0 nouveaufb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0H3MT5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6430 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1683445/+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 1705538] Re: Update Package request for libservicelog
** Changed in: ubuntu-power-systems 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/1705538 Title: Update Package request for libservicelog Status in The Ubuntu-power-systems project: Fix Released Status in libservicelog package in Ubuntu: Fix Released Status in libservicelog source package in Xenial: Fix Released Bug description: [Impact] Update Package request for libservicelog. Some upstream patches have been requested to be included in both bionic and xenial. The addressed issues can potentially affect customer environments, causing possible segmentation faults. [Test Case] The packages will be validated by the requesting party (see original description). Besides making sure servicelog does not segfault anymore and performing general dogfooding, the upstream test-suite will need to be run and made sure to pass on the affected systems. [Regression Potential] Hard to assess but the requested patches have been in upstream trunk since at least a year and no issues have been reported - changes also present in Debian and Ubuntu bionic since last year. [Original Description] ---Problem Description--- Update Package request for libservicelog Machine Type = lpar ---Steps to Reproduce--- servicelog --dump ---uname output--- Linux tuleta4u-lp9 4.10.0-27-generic #30~16.04.2-Ubuntu SMP Thu Jun 29 16:06:52 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Please pull below mentioned patches for libservicelog package commit 4fe9d9239f172604e16268ca1fb6fff1c06632b2 Author: Ankit Kumar Date: Sat May 20 01:38:41 2017 +0530 Validate text string before and after bind call While binding string to query, if string is NULL then bind call gets ignored. While fetching data from string, if data is NULL then current code makes query as NULL and returns. This patch validates text string before and after bind call. It assigns string to "" incase data is NULL points to NULL pointer. After this we will be able to display information even if some of string data is NULL. It also does NULL checks for compulsory string. Signed-off-by: Ankit Kumar [Killed redundant goto statements - Vasant] Signed-off-by: Vasant Hegde commit 787594814eb88e3149cd660bcb6aaa6d3dd1347c Author: Ankit Kumar Date: Sat May 20 01:10:49 2017 +0530 Correct string length calculation and validates destination buffer size before strncpy This patch corrects string length calculation logic and validates destination buffer size before calling strncpy to avoid memory corruption. Signed-off-by: Ankit Kumar [Moved memset to right place and removed redundant condition check - Vasant] Signed-off-by: Vasant Hegde commit 48875ee8614eeefaa3d5d8ff92fb424915738169 Author: Ankit Kumar Date: Thu Sep 15 16:16:49 2016 +0530 NULL check before strdup call This patch does "NULL checks" before passing argument to strdup call. Signed-off-by: Ankit Kumar Signed-off-by: Vasant Hegde commit 40b4f7a52e61fb9da30b4cb9b5de9a85673da262 Author: Ankit Kumar Date: Thu Sep 15 16:16:48 2016 +0530 NULL check before strlen call This patch checks NULL pointer before strlen call. Signed-off-by: Ankit Kumar [Fixed build warning - Vasant] Signed-off-by: Vasant Hegde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1705538/+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 1705538] Re: Update Package request for libservicelog
This bug was fixed in the package libservicelog - 1.1.16-0ubuntu1.1 --- libservicelog (1.1.16-0ubuntu1.1) xenial; urgency=medium * debian/patches: Cherry-pick and rebase upstream fixes for additional NULL checking, string length calculation and validation. (LP: #1705538) - 0001-Correct-string-length-calculation-and-validates-dest.patch - 0002-NULL-check-before-strdup-call.patch - 0003-NULL-check-before-strlen-call.patch - 0004-Validate-text-string-before-and-after-bind-call.patch -- Łukasz 'sil2100' Zemczak Wed, 21 Feb 2018 17:44:12 +0100 ** Changed in: libservicelog (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/1705538 Title: Update Package request for libservicelog Status in The Ubuntu-power-systems project: Fix Released Status in libservicelog package in Ubuntu: Fix Released Status in libservicelog source package in Xenial: Fix Released Bug description: [Impact] Update Package request for libservicelog. Some upstream patches have been requested to be included in both bionic and xenial. The addressed issues can potentially affect customer environments, causing possible segmentation faults. [Test Case] The packages will be validated by the requesting party (see original description). Besides making sure servicelog does not segfault anymore and performing general dogfooding, the upstream test-suite will need to be run and made sure to pass on the affected systems. [Regression Potential] Hard to assess but the requested patches have been in upstream trunk since at least a year and no issues have been reported - changes also present in Debian and Ubuntu bionic since last year. [Original Description] ---Problem Description--- Update Package request for libservicelog Machine Type = lpar ---Steps to Reproduce--- servicelog --dump ---uname output--- Linux tuleta4u-lp9 4.10.0-27-generic #30~16.04.2-Ubuntu SMP Thu Jun 29 16:06:52 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Please pull below mentioned patches for libservicelog package commit 4fe9d9239f172604e16268ca1fb6fff1c06632b2 Author: Ankit Kumar Date: Sat May 20 01:38:41 2017 +0530 Validate text string before and after bind call While binding string to query, if string is NULL then bind call gets ignored. While fetching data from string, if data is NULL then current code makes query as NULL and returns. This patch validates text string before and after bind call. It assigns string to "" incase data is NULL points to NULL pointer. After this we will be able to display information even if some of string data is NULL. It also does NULL checks for compulsory string. Signed-off-by: Ankit Kumar [Killed redundant goto statements - Vasant] Signed-off-by: Vasant Hegde commit 787594814eb88e3149cd660bcb6aaa6d3dd1347c Author: Ankit Kumar Date: Sat May 20 01:10:49 2017 +0530 Correct string length calculation and validates destination buffer size before strncpy This patch corrects string length calculation logic and validates destination buffer size before calling strncpy to avoid memory corruption. Signed-off-by: Ankit Kumar [Moved memset to right place and removed redundant condition check - Vasant] Signed-off-by: Vasant Hegde commit 48875ee8614eeefaa3d5d8ff92fb424915738169 Author: Ankit Kumar Date: Thu Sep 15 16:16:49 2016 +0530 NULL check before strdup call This patch does "NULL checks" before passing argument to strdup call. Signed-off-by: Ankit Kumar Signed-off-by: Vasant Hegde commit 40b4f7a52e61fb9da30b4cb9b5de9a85673da262 Author: Ankit Kumar Date: Thu Sep 15 16:16:48 2016 +0530 NULL check before strlen call This patch checks NULL pointer before strlen call. Signed-off-by: Ankit Kumar [Fixed build warning - Vasant] Signed-off-by: Vasant Hegde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1705538/+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
