[Group.of.nepali.translators] [Bug 1446537] Re: apport hook fails in add_info with TypeError: 'str' does not support the buffer interface
Great, thanks. I only did a few spot checks yesterday and they looked unaffected too. ** Also affects: apport (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Xenial) Status: New => Triaged -- 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/1446537 Title: apport hook fails in add_info with TypeError: 'str' does not support the buffer interface Status in apport package in Ubuntu: Fix Committed Status in apport source package in Xenial: In Progress Bug description: on vivid ⟫ ubuntu-bug ubiquity dpkg-query: aucun paquet ne correspond à ubiquity ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/source_ubiquity.py", line 61, in add_info if 'Buffer I/O error on device' in syslog: TypeError: 'str' does not support the buffer interface ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 21 10:15:56 2015 InstallationDate: Installed on 2013-09-03 (594 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1446537/+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 1582960] Re: adt-buildvm-ubuntu-cloud -r yakkety produces image that does not work with adt-run
I suppose this is not specific to the yakkety image for you, i. e. a xenial image does work. The root cause is a regression in Python 3.5 (https://bugs.debian.org/822431) and I added a workaround in https://bugs.debian.org/821778 in autopkgtest 3.20.5. ** Bug watch added: Debian Bug tracker #822431 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822431 ** Bug watch added: Debian Bug tracker #821778 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821778 ** Changed in: autopkgtest (Ubuntu) Status: New => Fix Released ** Also affects: autopkgtest (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: autopkgtest (Ubuntu Xenial) Status: New => Triaged ** Changed in: autopkgtest (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/1582960 Title: adt-buildvm-ubuntu-cloud -r yakkety produces image that does not work with adt-run Status in autopkgtest package in Ubuntu: Fix Released Status in autopkgtest source package in Xenial: Triaged Bug description: mwhudson@aeglos:~$ adt-buildvm-ubuntu-cloud -r yakkety Downloading https://cloud-images.ubuntu.com/yakkety/current/yakkety-server-cloudimg-amd64-disk1.img... 323.6/325.2 MB (100%) Download successful. Resizing image, adding 20G... Image resized. Building seed image... Booting image to run cloud-init... Moving image into final destination ./adt-yakkety-amd64-cloud.img mwhudson@aeglos:~$ adt-run openafs --- qemu --debug adt-yakkety-amd64-cloud.img adt-run [13:42:14]: version 3.20.4 adt-run [13:42:14]: host aeglos; command line: /usr/bin/adt-run openafs --- qemu --debug adt-yakkety-amd64-cloud.img adt-virt-qemu: DBG: executing open adt-virt-qemu: DBG: Creating temporary overlay image in /tmp/adt-virt-qemu.vi1o66t2/overlay.img adt-virt-qemu: DBG: execute-timeout: qemu-img create -f qcow2 -b /home/mwhudson/adt-yakkety-amd64-cloud.img /tmp/adt-virt-qemu.vi1o66t2/overlay.img adt-virt-qemu: DBG: Detected KVM capable Intel host CPU, enabling nested KVM adt-virt-qemu: DBG: find_free_port: trying 10022 adt-virt-qemu: DBG: find_free_port: 10022 is free adt-virt-qemu: DBG: Forwarding local port 10022 to VM ssh port 22 adt-virt-qemu: DBG: expect: " login: " adt-virt-qemu: DBG: expect: found ""login prompt on ttyS0"" adt-virt-qemu: DBG: expect: "ok" adt-virt-qemu: DBG: expect: found ""b'ok'"" adt-virt-qemu: DBG: setup_shell(): there already is a shell on ttyS1 adt-virt-qemu: DBG: expect: "#" adt-virt-qemu: DBG: expect: found ""b'#'"" adt-virt-qemu: DBG: expect: "(qemu)" adt-virt-qemu: DBG: expect: found ""b'(qemu)'"" adt-virt-qemu: DBG: expect: "(qemu)" adt-virt-qemu: DBG: expect: found ""b'(qemu)'"" adt-virt-qemu: DBG: expect: "#" adt-virt-qemu: DBG: expect: found ""b'#'"" adt-virt-qemu: DBG: expect: "#" adt-virt-qemu: DBG: expect: found ""b'#'"" adt-virt-qemu: DBG: expect: "#" adt-virt-qemu: DBG: expect: found ""b'#'"" adt-virt-qemu: DBG: Copying host timezone Pacific/Auckland to VM adt-virt-qemu: DBG: expect: "#" adt-virt-qemu: DBG: expect: found ""b'#'"" adt-virt-qemu: DBG: expect: "/python" adt-virt-qemu: DBG: expect: found ""b'/python'"" adt-virt-qemu: DBG: expect: "# " adt-virt-qemu: DBG: expect: found ""b'# '"" adt-virt-qemu: DBG: expect: "# " adt-virt-qemu: DBG: expect: found ""b'# '"" adt-virt-qemu: DBG: execute-timeout: /tmp/adt-virt-qemu.vi1o66t2/runcmd true qemu-system-x86_64: terminating on signal 15 from pid 4494 adt-virt-qemu: DBG: cleanup... Unexpected error: Traceback (most recent call last): File "/usr/share/autopkgtest/python/VirtSubproc.py", line 705, in mainloop command() File "/usr/share/autopkgtest/python/VirtSubproc.py", line 643, in command r = f(c, ce) File "/usr/share/autopkgtest/python/VirtSubproc.py", line 258, in cmd_open caller.hook_open() File "/usr/bin/adt-virt-qemu", line 567, in hook_open make_auxverb(shareddir) File "/usr/bin/adt-virt-qemu", line 413, in make_auxverb status = VirtSubproc.execute_timeout(None, 5, VirtSubproc.auxverb + ['true'])[0] File "/usr/share/autopkgtest/python/VirtSubproc.py", line 144, in execute_timeout (out, err) = sp.communicate(instr) File "/usr/lib/python3.5/subprocess.py", line 1057, in communicate self.wait() File "/usr/lib/python3.5/subprocess.py", line 1648, in wait (pid, sts) = self._try_wait(0) File "/usr/lib/python3.5/subprocess.py", line 1598, in _try_wait (pid, sts) = os.waitpid(self.pid, wait_flags) File "/usr/share/autopkgtest/python/VirtSubproc.py", line 64, in alarm_handler raise Timeout() VirtSubproc.Timeout adt-run [13:42:29]: ERROR: testbed failure: testbed gave exit status 16 after quit No idea what's going on,
[Group.of.nepali.translators] [Bug 1494350] Re: QEMU: causes vCPU steal time overflow on live migration
Fix released for Wily (4.2.0-36.41) ** Changed in: linux (Ubuntu Trusty) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Wily) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Vivid) 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/1494350 Title: QEMU: causes vCPU steal time overflow on live migration Status in Linux: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Status in linux package in Debian: Fix Released Bug description: [Impact] It is possible to have vcpu->arch.st.last_steal initialized from a thread other than vcpu thread, say the main thread, via KVM_SET_MSRS. That can cause steal_time overflow later (when subtracting from vcpu threads sched_info.run_delay). [Test Case] Testing Steps with patched trusty kernel: Using savemv & loadvm to simulate the migration process. In guest: 1. check steal_time data location rdmsr 0x4b564d03 <- returns the start address 0x7fc0d000 2. exam the steal time before savevm in qemu monitor (qemu) xp /ug 0x7fc0d000 xp /ug 0x7fc0d000 7fc0d000:144139048 < steal time value before savevm (qemu) savevm mytestvm7 savevm mytestvm7 (qemu) quit quit 3. give some load to the host system, e.g. stress --cpu 4. start the guest with "-loadvm mytestvm7" to restore the state of the VM, thus the steal_time MSR 5. exam the steal time value again (qemu) xp /ug 0x7fc0d000 xp /ug 0x7fc0d000 7fc0d000:147428917 < with high cpu load after loadvm, steal time still shows a linear increase The steal_time value would go backward (because of the overflow) after the restoration of the VM state without the fix. - I'm pasting in text from Debian Bug 785557 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785557 b/c I couldn't find this issue reported. It is present in QEMU 2.3, but I haven't tested later versions. Perhaps someone else will find this bug and confirm for later versions. (Or I will when I have time!) Hi, I'm trying to debug an issue we're having with some debian.org machines running in QEMU 2.1.2 instances (see [1] for more background). In short, after a live migration guests running Debian Jessie (linux 3.16) stop accounting CPU time properly. /proc/stat in the guest shows no increase in user and system time anymore (regardless of workload) and what stands out are extremely large values for steal time: % cat /proc/stat cpu 2400 0 1842 650879168 2579640 0 25 136562317270 0 0 cpu0 1366 0 1028 161392988 1238598 0 11 383803090749 0 0 cpu1 294 0 240 162582008 639105 0 8 39686436048 0 0 cpu2 406 0 338 163331066 383867 0 4 333994238765 0 0 cpu3 332 0 235 163573105 318069 0 1 1223752959076 0 0 intr 355773871 33 10 0 0 0 0 3 0 1 0 0 36 144 0 0 1638612 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 5001741 41 0 8516993 0 3669582 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ctxt 837862829 btime 1431642967 processes 8529939 procs_runn
[Group.of.nepali.translators] [Bug 1556685] Re: Wrong installation path (0.16 instead of 0.17)
** Changed in: oce (Ubuntu) Status: New => Fix Released ** Also affects: oce (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: oce (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1556685 Title: Wrong installation path (0.16 instead of 0.17) Status in oce package in Ubuntu: Fix Released Status in oce source package in Xenial: Confirmed Status in oce package in Debian: Fix Released Bug description: System: Xenial (16.04) Package: oce (0.17.1-1) OCE package installs some data into "oce-0.16" directory instead of oce-0.17. In debian/rules file at line #26, it should be: -DOCE_INSTALL_CMAKE_DATA_DIR:PATH=lib/$(DEB_HOST_MULTIARCH)/oce-0.17 \ instead of -DOCE_INSTALL_CMAKE_DATA_DIR:PATH=lib/$(DEB_HOST_MULTIARCH)/oce-0.16 \ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oce/+bug/1556685/+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 1582889] [NEW] SRU of LXCFS 2.0.1 (upstream bugfix release)
Public bug reported: LXCFS upstream released LXC 2.0.1 as a bugfix release with following changelog: - Fix cpuinfo on s390x. - Use recursive cgroup values in diskstats. - Allow traversal (rx) to controller directories. - Fix do_mount_cgroups() crash on failure. - Better error handling in a number of path processing functions. - Better error handling in swap calculation. Just like Ubuntu itself, upstream releases long term support releases, as is 2.0 and then periodic point releases including all the accumulated bugfixes. Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support. This bugfix release has already been uploaded to Yakkety and automatically backported in the upstream PPAs for all Ubuntu releases. So far without any reported regression. This should qualify under the minor upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release. Once the SRU hits -updates, we will be backporting this to trusty-backports as well, making sure we have the same version everywhere. ** Affects: lxcfs (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: lxcfs (Ubuntu Trusty) Importance: Undecided Assignee: Stéphane Graber (stgraber) Status: Triaged ** Affects: lxcfs (Ubuntu Xenial) Importance: Undecided Assignee: Stéphane Graber (stgraber) Status: In Progress ** Also affects: lxcfs (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lxcfs (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: lxcfs (Ubuntu) Status: New => Fix Released ** Changed in: lxcfs (Ubuntu Trusty) Status: New => Triaged ** Changed in: lxcfs (Ubuntu Xenial) Status: New => In Progress ** Changed in: lxcfs (Ubuntu Trusty) Assignee: (unassigned) => Stéphane Graber (stgraber) ** Changed in: lxcfs (Ubuntu Xenial) Assignee: (unassigned) => Stéphane Graber (stgraber) -- 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/1582889 Title: SRU of LXCFS 2.0.1 (upstream bugfix release) Status in lxcfs package in Ubuntu: Fix Released Status in lxcfs source package in Trusty: Triaged Status in lxcfs source package in Xenial: In Progress Bug description: LXCFS upstream released LXC 2.0.1 as a bugfix release with following changelog: - Fix cpuinfo on s390x. - Use recursive cgroup values in diskstats. - Allow traversal (rx) to controller directories. - Fix do_mount_cgroups() crash on failure. - Better error handling in a number of path processing functions. - Better error handling in swap calculation. Just like Ubuntu itself, upstream releases long term support releases, as is 2.0 and then periodic point releases including all the accumulated bugfixes. Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support. This bugfix release has already been uploaded to Yakkety and automatically backported in the upstream PPAs for all Ubuntu releases. So far without any reported regression. This should qualify under the minor upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release. Once the SRU hits -updates, we will be backporting this to trusty-backports as well, making sure we have the same version everywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1582889/+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 1582891] [NEW] SRU of LXD 2.0.1 (upstream bugfix release)
Public bug reported: LXD upstream released LXC 2.0.1 as a bugfix release with following changelog: - Don't fail to start when shmounts can't be mounted, instead fail container startup - Invalidate the simplestreams cache on proxy change - Write the container's config file on start to the log path directly - Fix crash in list due to empty responses (Issue #1903) - Fail when removing non-existent profiles (Issue #1886) - Document --alias to image import (Issue #1900) - Fix "lxc start" and "lxc stop" options (stateful/stateless) - Give better error on invalid source stream (simplestreams) - Add basic REST API usage example to README.md - Fix typo in lxc stop --help - Convert lxc-to-lxd to stable supported pylxd API (Issue #1901) - Properly log image update failures - Better validate and rollback bad images (Issue #1913) - Send operation return value through SmartError - Fix basic filtering in lxc list (Issue #1917) - Tell the user how to launch a container on first start (Issue #1931) - Redirect "remote" to "remote:" when not conflicting (Issue #1931) - Don't load the LXC config for snapshots (Issue #1935) - list: Allow filtering by unset key (Issue #1917) - Fix example in lxc launch - Update Japanese translation and other po files - Fall back to cpuset.cpus on older kernels (Issue #1929) - Properly validate the server configuration keys (Issue #1939) - Fix daemonConfig handling of storage - Don't remove config file on forkmigrate - Fix config handling following config validation change - Fixed Markdown syntax in documentation - Don't fail early when removing disks (Issue #1964) - Don't recursively delete devices - Don't fail when some unix devices fail to be deleted - Use the same config checks for unix-char and unix-block - Allow removing when fs object no longer exists (Issue #1967) - Do proper logfile expiry (Issue #1966) - Make logging a bit more consistent - Don't ignore zfs errors - Properly update the mode, uid and gid on existing files (Issue #1975) - Detect invalid certificate files (Issue #1977) - Fix broken apparmor status check - Allow on/off as boolean strings - Properly validate the container configuration keys (Issue #1940) - Don't mask rsync transfer errors - Move execPath to a global variable - Use custom netcat instead of nc -U for rsync over websocket (Issue #1944) - Fix wrong state dir path in migration - Don't fail deleting images when the storage delete fails - Improve messages in the Japanese translation - Add more checks for the criu binary - Rework (live) migration tests - Make it explicit in documentation that devices on create are optional - Properly record the source of all image copies (Issue #2010) - Don't mark containers as ERROR while being created (Issue #1988) - Cleanup events sent for operations (Issue #1992) - Fix ZFS refcounting issues (Issue #1916 and Issue #2013) - Propagate snapshot config when copying a snapshot (Issue #2017) - Implement lxc config show for snapshots - Add Unix socket example to REST API usage. Just like Ubuntu itself, upstream releases long term support releases, as is 2.0 and then periodic point releases including all the accumulated bugfixes. Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support. This bugfix release has already been uploaded to Yakkety and automatically backported in the upstream PPAs for all Ubuntu releases. So far without any reported regression. This should qualify under the minor upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release. Once the SRU hits -updates, we will be backporting this to trusty-backports as well, making sure we have the same version everywhere. ** Affects: lxd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: lxd (Ubuntu Trusty) Importance: Undecided Assignee: Stéphane Graber (stgraber) Status: Triaged ** Affects: lxd (Ubuntu Xenial) Importance: Undecided Assignee: Stéphane Graber (stgraber) Status: In Progress ** Also affects: lxd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: lxd (Ubuntu) Status: New => Fix Released ** Changed in: lxd (Ubuntu Trusty) Status: New => Triaged ** Changed in: lxd (Ubuntu Xenial) Status: New => In Progress ** Changed in: lxd (Ubuntu Trusty) Assignee: (unassigned) => Stéphane Graber (stgraber) ** Changed in: lxd (Ubuntu Xenial) Assignee: (unassigned) => Stéphane Graber (stgraber) -- 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/1582891 Title:
[Group.of.nepali.translators] [Bug 1582887] [NEW] SRU of LXC 2.0.1 (upstream bugfix release)
Public bug reported: LXC upstream released LXC 2.0.1 as a bugfix release with following changelog: - apparmor: Also allow fstype=fuse for fuse filesystems - attach: adapt lxc-attach tests & add test for pty logging - attach: don't fail attach on failure to setup a SIGWINCH handler. - attach: fix a variety of lxc-attach pts handling issues - attach: switch console pty to raw mode (fixes ncurses-based programs) - attach: use raw settings of ssh for pty - bindings: fixed python-lxc reference to var before assignment in create() - bindings: set PyErr when Container.__init__ fails - cgfsng: defer to cgfs if needed subsystems are not available - cgfsng: don't require that systemd subsystem be mounted - core: Added missing type to keys in lxc_list_nicconfigs - core: Allow configuration file values to be quoted - core: log: remove duplicate definitons and bump buffer size - core: sync: properly fail on unexpected message sizes - core: Unshare netns after setting the userns mappings (fixes ownership of /proc/net) - core: various fixes as reported by static analysis - c/r: add an option to use faster inotify support in CRIU - c/r: rearrange things to pass struct migrate_opts all the way down - doc: ignore temporary files generated by doxygen - doc: tweak manpage generation date to be compatible with reproducible builds - doc: update MAINTAINERS - doc: update to translated manpages - init: add missing lsb headers to sysvinit scripts - init: don't make sysv init scripts dependant on distribution specifics - init: drop obsolete syslog.target from lxc.service.in - lxc-attach: add logging option to manpage - lxc-checkconfig: better render when stdout isn't a terminal - lxc-create: fix -B best option - lxc-destroy: avoid double print - lxc-ls: use fewer syscalls when doing ipc - templates: Add apt-transport-https to minbase variant of Ubuntu template - templates: fix a typo in the capabilities name for Gentoo (sys_resource) - templates: logic fix in the Centos template for RHEL7+ support - templates: tweak Alpine DHCP configuration to send its hostname - templates: tweak to network configuration of the Oracle template Just like Ubuntu itself, upstream releases long term support releases, as is 2.0 and then periodic point releases including all the accumulated bugfixes. Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support. This bugfix release has already been uploaded to Yakkety and automatically backported in the upstream PPAs for all Ubuntu releases. So far without any reported regression. This should qualify under the minor upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release. Once the SRU hits -updates, we will be backporting this to trusty-backports as well, making sure we have the same version everywhere. ** Affects: lxc (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: lxc (Ubuntu Trusty) Importance: Undecided Assignee: Stéphane Graber (stgraber) Status: Triaged ** Affects: lxc (Ubuntu Xenial) Importance: Undecided Assignee: Stéphane Graber (stgraber) Status: In Progress ** Also affects: lxc (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Status: New => Fix Released ** Changed in: lxc (Ubuntu Trusty) Status: New => In Progress ** Changed in: lxc (Ubuntu Trusty) Status: In Progress => Triaged ** Changed in: lxc (Ubuntu Xenial) Status: New => In Progress ** Changed in: lxc (Ubuntu Trusty) Assignee: (unassigned) => Stéphane Graber (stgraber) ** Changed in: lxc (Ubuntu Xenial) Assignee: (unassigned) => Stéphane Graber (stgraber) -- 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/1582887 Title: SRU of LXC 2.0.1 (upstream bugfix release) Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Triaged Status in lxc source package in Xenial: In Progress Bug description: LXC upstream released LXC 2.0.1 as a bugfix release with following changelog: - apparmor: Also allow fstype=fuse for fuse filesystems - attach: adapt lxc-attach tests & add test for pty logging - attach: don't fail attach on failure to setup a SIGWINCH handler. - attach: fix a variety of lxc-attach pts handling issues - attach: switch console pty to raw mode (fixes ncurses-based programs) - attach: use raw settings of ssh for pty - bindings: fixed python-lxc reference to var before assignment in create() - bindings: set PyErr when Container.__init__ fails
[Group.of.nepali.translators] [Bug 1564960] Re: mlx switchdev needs patches to work in 16.04
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1564960 Title: mlx switchdev needs patches to work in 16.04 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux source package in Yakkety: Fix Released Bug description: mlx switchdev is incomplete in 16.04. A small set of patches will make it functional. These apply mostly to mlxsw, although there are a few patches in net/bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564960/+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 1581645] Re: [SRU] Juju 2.0 beta7 for Xenial
** Changed in: juju-core (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/1581645 Title: [SRU] Juju 2.0 beta7 for Xenial Status in juju-core package in Ubuntu: Fix Released Status in juju-core source package in Xenial: New Bug description: Juju 2.0 is not quite final, as per the risks and timeline outlined in the FFe for Xenial, bug 1545913. As such, we intend to release SRU's post-xenial release. This updates juju to the lastest 2.0 milestone version. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] This beta brings critical updates for MAAS support, as well as azure and other substrates. Many race conditions have also been fixed. A full list of targeted bugs can be seen against the milestone: https://launchpad.net/juju-core/+milestone/2.0-beta7 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here. http://reports.vapour.ws/releases/3966 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1581645/+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 1248289] Re: Missing libunwind support in perf
** Also affects: linux (Ubuntu Yakkety) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: Confirmed ** Changed in: linux (Ubuntu Yakkety) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1248289 Title: Missing libunwind support in perf Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: Hi, I'm trying to use perf's libunwind support in 13.04 with kernel 3.11.0-12-generic on amd64. Typically you can do this by using the "-g dwarf" flag, but it appears the perf command included in linux- tools-3.11.0-12-generic was not compiled with libunwind. This may be as simple as the build machine didn't have libunwind installed. Having dwarf support in perf with default Ubuntu kernels would be very useful as it provides a way to get profiling information when -fomitframepointer is used. Relevant upstream code: https://github.com/torvalds/linux/blob/v3.11/tools/perf/Makefile#L459 https://github.com/torvalds/linux/blob/v3.11/tools/perf/builtin-record.c#L758 Let me know if I can provide any other information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248289/+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 1582847] Re: linux-raspi2: 4.4.0-1011.14 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Description changed: This bug is for tracking the 4.4.0-1011.14 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: 1582431 phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 17. May 2016 20:04 UTC ** Description changed: This bug is for tracking the 4.4.0-1011.14 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: 1582431 - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Tuesday, 17. May 2016 20:04 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/1582847 Title: linux-raspi2: 4.4.0-1011.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-1011.14 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: 1582431 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582847/+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 1582679] Re: linux-snapdragon: 4.4.0-1014.16 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Description changed: This bug is for tracking the 4.4.0-1014.16 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: 1582431 phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Tuesday, 17. May 2016 20:02 UTC ** Description changed: This bug is for tracking the 4.4.0-1014.16 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: 1582431 - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Tuesday, 17. May 2016 20:02 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/1582679 Title: linux-snapdragon: 4.4.0-1014.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-1014.16 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: 1582431 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1582679/+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 1581645] Re: [SRU] Juju 2.0 beta7 for Xenial
** Also affects: juju-core (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/1581645 Title: [SRU] Juju 2.0 beta7 for Xenial Status in juju-core package in Ubuntu: New Status in juju-core source package in Xenial: New Bug description: Juju 2.0 is not quite final, as per the risks and timeline outlined in the FFe for Xenial, bug 1545913. As such, we intend to release SRU's post-xenial release. This updates juju to the lastest 2.0 milestone version. [SRU Information] juju-core has a stable release exception, including for major version updates, https://wiki.ubuntu.com/JujuUpdates. [Impact] This beta brings critical updates for MAAS support, as well as azure and other substrates. Many race conditions have also been fixed. A full list of targeted bugs can be seen against the milestone: https://launchpad.net/juju-core/+milestone/2.0-beta7 [QA/Testing] Juju practices continuous integration and testing of the juju source tree. The results for this release can be seen here. http://reports.vapour.ws/releases/3966 In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/. Finally, manual verification and testing of the package has been done per https://wiki.ubuntu.com/JujuUpdate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1581645/+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 1548421] Re: python stacktrace during 'apport-bug'
This bug was fixed in the package apport - 2.20.1-0ubuntu4
---
apport (2.20.1-0ubuntu4) yakkety; urgency=medium
* data/general-hooks/ubuntu.py: Fix stacktrace when parsing
DpkgTerminalLog.txt. (LP: #1548421)
* data/general-hooks/ubuntu.py: Restore starting package problem duplicate
signatures with the word package, the package name, and its version.
(LP: #1581682)
-- Brian Murray Mon, 16 May 2016 14:16:15 -0700
** Changed in: apport (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/1548421
Title:
python stacktrace during 'apport-bug'
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Xenial:
In Progress
Bug description:
smoser@milhouse:~/src/maas-images/trunk$ sudo apport-bug
/var/crash/libtesseract4.0.crash
[sudo] password for smoser:
sys:1: PyGIWarning: Wnck was imported without specifying a version first. Use
gi.require_version('Wnck', '3.0') before import to ensure that the right
version gets loaded.
sys:1: PyGIWarning: GdkX11 was imported without specifying a version first.
Use gi.require_version('GdkX11', '3.0') before import to ensure that the right
version gets loaded.
ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 66, in add_info
check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 170, in
check_attachment_for_errors
trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 468, in trim_dpkg_log
report['DpkgTerminalLog'] = '\n'.join([str(line.encode('utf-8')) for line
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 468, in
report['DpkgTerminalLog'] = '\n'.join([str(line.encode('utf-8')) for line
in lines])
AttributeError: 'bytes' object has no attribute 'encode'
seems like a python2 to python3 conversion bug.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apport 2.20-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportLog:
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashReports:
640:0:116:846362:2016-02-22 12:27:09.709648847 -0500:2016-02-22
12:27:10.709648847 -0500:/var/crash/libtesseract4.0.crash
644:0:116:0:2016-02-22 12:27:11.629635693 -0500:2016-02-22
12:27:11.629635693 -0500:/var/crash/libtesseract4.0.upload
CurrentDesktop: Unity
Date: Mon Feb 22 12:35:39 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (214 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1548421/+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 1581682] Re: Duplicate signature for Package problems missing info
This bug was fixed in the package apport - 2.20.1-0ubuntu4 --- apport (2.20.1-0ubuntu4) yakkety; urgency=medium * data/general-hooks/ubuntu.py: Fix stacktrace when parsing DpkgTerminalLog.txt. (LP: #1548421) * data/general-hooks/ubuntu.py: Restore starting package problem duplicate signatures with the word package, the package name, and its version. (LP: #1581682) -- Brian Murray Mon, 16 May 2016 14:16:15 -0700 ** Changed in: apport (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/1581682 Title: Duplicate signature for Package problems missing info Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: In Progress Bug description: The code in apport which creates a duplicate signature for package installation failures changed in Ubuntu 16.04 and as part of that change we are no longer starting the duplicate signature with the following: dupe_sig = 'package:%s:%s:%s' % (package, version, report['ErrorMessage']) This change was made because 'ErrorMessage' was too vague, however having 'package:%s:%s' was useful in the Ubuntu Error Tracker. The Error Tracker buckets package installation failures based off the duplicate signature and without the string 'package:$package' its hard to know if a bucket is about about a package installation failure. Additionally, buckets end up containing a mish-mash of different packages. In the following error notice how the package version table contains a bunch of unrelated version numbers: https://errors.ubuntu.com/problem/23630ea42dcd530db3633a250e04751630e2ac02 The duplicate signature for problems with the type package should be changed to start with package and the package name at least. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1581682/+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 1582852] Re: IMA crashes while verifying signatures
** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged -- 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/1582852 Title: IMA crashes while verifying signatures Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: The application of a kernel patch to fix Bug 1569924 causes crashes when IMA is verifying signatures: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569924 The following fix was applied: commit e6b195bb9adbf92b62f466b02fb8ae9b4294ad5e Author: Tadeusz Struk Date: Tue Feb 2 10:08:53 2016 -0800 crypto: KEYS: convert public key and digsig asym to the akcipher api This patch was taken from here: https://github.com/torvalds/linux/commit/db6c43bd2132dc2dd63d73a6d1ed601cffd0ae06.patch The series was posted here (not sure whether this is the latest version) https://lkml.org/lkml/2016/2/2/575 The following two patches should be applied as well. They stem from that same series of patches as the one that is already applied. https://github.com/torvalds/linux/commit/eb5798f2e28f3b43091cecc71c84c3f6fb35c7de.patch https://github.com/torvalds/linux/commit/d846e78e491ff4dd0747026c02414844d504fcb6.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582852/+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 1582847] [NEW] linux-raspi2: 4.4.0-1011.14 -proposed tracker
Public bug reported: This bug is for tracking the 4.4.0-1011.14 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: 1582431 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-raspi2 (Ubuntu Xenial) Importance: Medium Status: New ** Tags: block-proposed block-proposed-xenial kernel-release-tracking-bug xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Tags added: block-proposed-xenial ** Also affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-security Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) **
[Group.of.nepali.translators] [Bug 1581651] Re: Xenial desktop unusable under simple I/O through USB
** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1581651 Title: Xenial desktop unusable under simple I/O through USB Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: Hello! After installing Xenial [0] I experience the following: when I do I/O through USB (to/from simple pendrives, or an external HDD I have), the desktop becomes unusable, because it goes very very unresponsive. With unresponsive I mean: - all windows go greyed out (like when it's failing to answer in time, as if the process inside that window locked up) - firefox and thunderbird start to pop up the typical "the script is taking too much to finis, want to kill it/continue/etc" (in whatever tab I'll be, so it's not the JS scripts (for once!) - the mouse pointer goes jumpy, not really following my hand movement - I see in thee indicator-multiload widget that CPU time is "wasted" in "waiting i/o"; which I confirmed looking at "top". So, in short: even while understanding that CPU would wait a little for i/o and that the system will be under a little load by writing a pen-drive, I find current situation beyond a normal experience. How can I start to debug this? What I can try? Can I provide you more info? Thanks! Regards, [0] from scratch, in the computer where I always work; I previously had Trusty here ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: facundo2338 F pulseaudio /dev/snd/controlC3: facundo2338 F pulseaudio /dev/snd/controlC2: facundo2338 F pulseaudio /dev/snd/controlC0: facundo2338 F pulseaudio CurrentDesktop: Unity Date: Fri May 13 16:13:12 2016 HibernationDevice: RESUME=UUID=5dabff2e-722b-4c99-8bf5-003643ad0d04 InstallationDate: Installed on 2016-04-01 (42 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=6ba5d9f5-e21f-4e58-800d-89ec0b7d1e9b ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: GA-970A-D3 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.:bvrF7:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581651/+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 1574347] Re: [SRU]network-manager
This bug was fixed in the package network-manager - 1.2.2-0ubuntu1 --- network-manager (1.2.2-0ubuntu1) yakkety; urgency=medium * Rebase to upstream stable point release. (LP: #1574347) * Use gbp-pq to manage patches. * d/rules: Allow parallel building of the package. -- Aron Xu Fri, 13 May 2016 06:40:53 + ** Changed in: network-manager (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/1574347 Title: [SRU]network-manager Status in NetworkManager: Fix Released Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Bug description: [Impact] NM needs to re-read the DEVTYPE after the device name changed, an example is that WiFi network list disappears from network manager applet Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. [Testcase] After upgrading to the new version, the repeating the above steps should give expected behavior. [Regression Potential] Potential of causing regression is relatively small for a one line change to re-read a value to be known. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1582776] Re: HVM/SSD Xenial AWS AMI doesn't launch on r3.large
Would it be possible for you to test the 16.04 kernel against other instance types to see if the bug happens with them as well? The latest 16.04 kernel can be downloaded from: https://launchpad.net/~canonical-kernel-security-team/+archive/ubuntu/ppa/+build/9734451 With this kernel, you need to install both the linux-image and linux- image-extra .deb packages. If the bug is tied to the kernel, we could the test other kernel versions to narrow down the last good version and first bad version. That will allow us to perform a kernel bisect to find the exact commit that caused this. Thanks in advance! ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1582776 Title: HVM/SSD Xenial AWS AMI doesn't launch on r3.large Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: **NOTE** The additional information attached to this bug report is for my laptop and does not apply to this bug report. Using ubuntu-bug, I'm not sure how to control this. Using the debian bug tool, I would have just edited the file If you attempt to launch an ec2 instance using IMAGE ami-c1cb23ac099720109477/ubuntu/images-testing/hvm-ssd /ubuntu-xenial-daily-amd64-server-20160516.1 099720109477 available public x86_64 machine on an instance of type r3.large, the kernel doesn't boot. You get output such as the attached log (kernel-ami-c1cb23ac.log). You get essentially the same result if you try to launch an image from ami-840910ee which is the AMI you get from http://cloud- images.ubuntu.com/locator/ with the search string "16.04 hvm us-east ssd" and picking the latest version. HVM is supposed to work on r3.large. We have used this successfully with Ubuntu 12.04, 14.04, and 15.10 and also with CentOS 5, 6, and 7. r3.large is supposed to work with both HVM and PV. We have no problems with this AMI on m4 or c4 instances which only support HVM. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ejb 14140 F pulseaudio Date: Tue May 17 11:06:11 2016 HibernationDevice: RESUME=UUID=1c991c18-29ed-4f63-b481-89ef40b91b94 InstallationDate: Installed on 2016-04-22 (24 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: docker0 no wireless extensions. enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=/dev/mapper/jblin0-root_16_04 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582776/+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 1573567] Re: Can't open gufw in Ubuntu 16.04
** Changed in: gui-ufw (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gui-ufw (Ubuntu) Assignee: (unassigned) => Devid Antonio Filoni (d.filoni) -- 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/1573567 Title: Can't open gufw in Ubuntu 16.04 Status in Gufw: Triaged Status in One Hundred Papercuts: Confirmed Status in gui-ufw package in Ubuntu: Fix Released Status in gui-ufw source package in Xenial: In Progress Bug description: [Impact] * gui-ufw doesn't start in Xenial due to missing dependency on python-gi as we can see on the following traceback. Uploaded package (I'm attaching debdiff too) adds missing dep. [Test Case] * Try to run gufw on a system where python-gi package is not installed [Regression Potential] * We cannot evaluate regressions as the package at the moment does not work at all, however upstream (costales) is very active, as you can see from this bug comments too, so I'm really confident he will fix any possible big issue ASAP if asked for. [Other Info] ORIGINAL BUG: Traceback (most recent call last): File "/usr/share/gufw/gufw/gufw.py", line 21, in from view.gufw import Gufw File "/usr/share/gufw/gufw/view/gufw.py", line 19, in import gi ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gufw 16.04.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 20:17:49 2016 InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=zh_TW:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_TW.UTF-8 SHELL=/bin/bash SourcePackage: gui-ufw UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gui-ufw/+bug/1573567/+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 1573567] Re: Can't open gufw in Ubuntu 16.04
** Also affects: gui-ufw (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/1573567 Title: Can't open gufw in Ubuntu 16.04 Status in Gufw: Triaged Status in One Hundred Papercuts: Confirmed Status in gui-ufw package in Ubuntu: Confirmed Status in gui-ufw source package in Xenial: New Bug description: Traceback (most recent call last): File "/usr/share/gufw/gufw/gufw.py", line 21, in from view.gufw import Gufw File "/usr/share/gufw/gufw/view/gufw.py", line 19, in import gi ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gufw 16.04.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 20:17:49 2016 InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=zh_TW:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_TW.UTF-8 SHELL=/bin/bash SourcePackage: gui-ufw UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gui-ufw/+bug/1573567/+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 1519836] Re: MaaS fails to boot Hyper-V Generation 2 virtual machines
** Also affects: grub2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: grub2-signed (Ubuntu) Status: New => Fix Released ** Changed in: grub2-signed (Ubuntu) Importance: Undecided => High ** Changed in: grub2 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: grub2-signed (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1519836 Title: MaaS fails to boot Hyper-V Generation 2 virtual machines Status in MAAS: Invalid Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in grub2 source package in Xenial: New Status in grub2-signed source package in Xenial: New Bug description: When trying to deploy a "Generation 2" virtual machine on Hyper-V, grub fails to fetch the linux kernel and initrd from MaaS. The operation times out immediately, because the Generation 2 VMs are missing the Programmable Interval Timer (PIT). The current version of grub still requires this interface to exist, in order to calculate time. There is a patch that uses the EFI SetTimer() available here: http://savannah.gnu.org/bugs/?42944 and an alternative in the discussion here: https://lists.gnu.org/archive/html/grub-devel/2014-10/msg00016.html that uses pmtimer instead. I am aware that grub is a critical package. What is the official/proper way to fix this issue? Can a patched grubnetx64.efi be packaged with MaaS? Do we have to wait for this fix to merge? Gabriel To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1519836/+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 1580674] Re: [SRU] mitaka point releases
Just for reference - all neutron-* updates are in the unapproved queue for SRU team processing. ** Changed in: cloud-archive Status: New => Invalid ** Changed in: neutron (Ubuntu) Status: New => Invalid ** Changed in: neutron-fwaas (Ubuntu) Status: New => Invalid ** Changed in: neutron-lbaas (Ubuntu) Status: New => Invalid ** Changed in: neutron-vpnaas (Ubuntu) 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/1580674 Title: [SRU] mitaka point releases Status in Ubuntu Cloud Archive: Invalid Status in Ubuntu Cloud Archive mitaka series: New Status in Landscape Server: New Status in Landscape Server 16.05 series: New Status in neutron package in Ubuntu: Invalid Status in neutron-fwaas package in Ubuntu: Invalid Status in neutron-lbaas package in Ubuntu: Invalid Status in neutron-vpnaas package in Ubuntu: Invalid Status in neutron source package in Xenial: New Status in neutron-fwaas source package in Xenial: New Status in neutron-lbaas source package in Xenial: New Status in neutron-vpnaas source package in Xenial: New Status in neutron-api package in Juju Charms Collection: New Status in neutron-gateway package in Juju Charms Collection: New Status in neutron-openvswitch package in Juju Charms Collection: New Bug description: New point releases for misc openstack components for the mitaka release: neutron 8.1.0 neutron-fwaas 8.1.0 neutron-lbaas 8.1.0 neutron-vpnaas 8.1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1580674/+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 1580674] Re: [SRU] mitaka point releases
** Also affects: neutron-openvswitch (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: neutron-api (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: neutron-gateway (Juju Charms Collection) 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/1580674 Title: [SRU] mitaka point releases Status in Ubuntu Cloud Archive: New Status in Ubuntu Cloud Archive mitaka series: New Status in Landscape Server: New Status in Landscape Server 16.05 series: New Status in neutron package in Ubuntu: New Status in neutron-fwaas package in Ubuntu: New Status in neutron-lbaas package in Ubuntu: New Status in neutron-vpnaas package in Ubuntu: New Status in neutron source package in Xenial: New Status in neutron-fwaas source package in Xenial: New Status in neutron-lbaas source package in Xenial: New Status in neutron-vpnaas source package in Xenial: New Status in neutron-api package in Juju Charms Collection: New Status in neutron-gateway package in Juju Charms Collection: New Status in neutron-openvswitch package in Juju Charms Collection: New Bug description: New point releases for misc openstack components for the mitaka release: neutron 8.1.0 neutron-fwaas 8.1.0 neutron-lbaas 8.1.0 neutron-vpnaas 8.1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1580674/+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 1580674] Re: [SRU] mitaka point releases
** Also affects: landscape Importance: Undecided Status: New ** Also affects: landscape/16.05 Importance: Undecided Status: New ** Changed in: landscape/16.05 Milestone: None => 16.05 -- 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/1580674 Title: [SRU] mitaka point releases Status in Ubuntu Cloud Archive: New Status in Ubuntu Cloud Archive mitaka series: New Status in Landscape Server: New Status in Landscape Server 16.05 series: New Status in neutron package in Ubuntu: New Status in neutron-fwaas package in Ubuntu: New Status in neutron-lbaas package in Ubuntu: New Status in neutron-vpnaas package in Ubuntu: New Status in neutron source package in Xenial: New Status in neutron-fwaas source package in Xenial: New Status in neutron-lbaas source package in Xenial: New Status in neutron-vpnaas source package in Xenial: New Bug description: New point releases for misc openstack components for the mitaka release: neutron 8.1.0 neutron-fwaas 8.1.0 neutron-lbaas 8.1.0 neutron-vpnaas 8.1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1580674/+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 1564156] Re: xenial: invalid opcode when using llvmpipe
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: Fix Released Status in System76: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in llvm-toolchain-3.8 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-3.8 source package in Xenial: Fix Released Status in mesa source package in Xenial: Confirmed Bug description: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" ** Note: "Download updates while installing Ubuntu" doesn't currently seem to be working. If after installing 16.04 on effected Skylake hardware you find that Unity/Compiz is broken, switch to a VT with Control+Alt+F1, login, and then run: sudo apt-get update sudo apt-get dist-upgrade You should see the `libllvm3.8` package get updated. After a reboot, Unity/Compiz should be working. == In detail == The Ubuntu 16.04 desktop ISOs include libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISOs. It will be included on the 16.04.1 ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+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 1382079] Re: Project selector not working
** Also affects: cloud-archive/kilo Importance: Undecided Status: New ** Changed in: cloud-archive Status: In Progress => Invalid ** Changed in: cloud-archive/kilo Assignee: (unassigned) => Liang Chen (cbjchen) ** Changed in: cloud-archive Assignee: Liang Chen (cbjchen) => (unassigned) ** Changed in: cloud-archive/kilo Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1382079 Title: Project selector not working Status in Ubuntu Cloud Archive: Invalid Status in Ubuntu Cloud Archive kilo series: In Progress Status in OpenStack Dashboard (Horizon): Fix Released Status in horizon package in Ubuntu: Fix Released Status in horizon source package in Vivid: Won't Fix Status in horizon source package in Wily: Fix Released Status in horizon source package in Xenial: Fix Released Bug description: [Impact] * Not able to switch projects by the project dropdown list. [Test Case] 1 - enable Identity V3 in local_settings.py 2 - Log in on Horizon 3 - make sure that the SESSION_BACKEND is "signed_cookies" 4 - Try to change project on the dropdown [Regression Potential] * None When you try to select a new project on the project dropdown, the project doesn't change. The commit below has introduced this bug on Horizon's master and has passed the tests verifications. https://github.com/openstack/horizon/commit/16db58fabad8934b8fbdfc6aee0361cc138b20af For what I've found so far, the context being received in the decorator seems to be the old context, with the token to the previous project. When you take the decorator out, the context received by the "can_access" function receives the correct context, with the token to the new project. Steps to reproduce: 1 - Enable Identity V3 (to have a huge token) 2 - Log in on Horizon (lots of permissions loaded on session) 3 - Certify that you SESSION_BACKEND is "signed_cookies" 4 - Try to change project on the dropdown The project shall remain the same. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1382079/+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 1582679] [NEW] linux-snapdragon: -proposed tracker
Public bug reported: 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: 1582431 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-snapdragon (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-snapdragon (Ubuntu Xenial) Importance: Medium Status: New ** Tags: block-proposed block-proposed-xenial kernel-release-tracking-bug xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Tags added: block-proposed-xenial ** Also affects: linux-snapdragon (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates
[Group.of.nepali.translators] [Bug 1562042] Re: Traceback in error log during heat-engine service shutdown
Ubuntu SRU information [Impact] OpenStack heat installations may end up with a load of non-functional heat-engine processes as the controller process fails to terminate them correctly on shutdown. [Test Case] sudo apt-get install heat-engine sudo service heat-engine restart [Regression Potential] Minimal; in newton and backports in process to other stable branches. ** Changed in: heat (Ubuntu Xenial) Assignee: (unassigned) => James Page (james-page) ** Changed in: heat (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: cloud-archive/mitaka Status: Triaged => In Progress ** Changed in: cloud-archive Status: Triaged => Fix Released ** Changed in: cloud-archive/mitaka Assignee: (unassigned) => James Page (james-page) ** Changed in: cloud-archive/liberty Status: Triaged => In Progress ** Changed in: cloud-archive/liberty Assignee: (unassigned) => James Page (james-page) ** Changed in: heat (Ubuntu Wily) Assignee: (unassigned) => James Page (james-page) ** Changed in: heat (Ubuntu Wily) Status: Triaged => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1562042 Title: Traceback in error log during heat-engine service shutdown Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive liberty series: In Progress Status in Ubuntu Cloud Archive mitaka series: In Progress Status in heat: Fix Released Status in heat package in Ubuntu: Fix Released Status in heat source package in Wily: In Progress Status in heat source package in Xenial: In Progress Status in heat source package in Yakkety: Fix Released Bug description: During shutdown of heat-engine service this traceback could be observed in log: ``` 2016-03-25 17:29:22.259 22588 DEBUG oslo_service.service [-] Stop services. stop /usr/lib/python2.7/dist-packages/oslo_service/service.py:583 2016-03-25 17:29:22.261 22588 DEBUG heat.engine.service [-] Attempting to stop engine service... _stop_rpc_server /usr/lib/python2.7/dist-packages/heat/engine/service.py:410 2016-03-25 17:29:22.262 22588 ERROR heat.engine.service [-] Failed to stop engine service, 'NoneType' object has no attribute 'stop' 2016-03-25 17:29:22.264 22588 CRITICAL heat-engine [-] AttributeError: 'NoneType' object has no attribute 'groups' 2016-03-25 17:29:22.264 22588 ERROR heat-engine Traceback (most recent call last): 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/bin/heat-engine", line 10, in 2016-03-25 17:29:22.264 22588 ERROR heat-engine sys.exit(main()) 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/heat/cmd/engine.py", line 79, in main 2016-03-25 17:29:22.264 22588 ERROR heat-engine launcher.wait() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 577, in wait 2016-03-25 17:29:22.264 22588 ERROR heat-engine self.stop() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 586, in stop 2016-03-25 17:29:22.264 22588 ERROR heat-engine service.stop() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/osprofiler/profiler.py", line 117, in wrapper 2016-03-25 17:29:22.264 22588 ERROR heat-engine return f(*args, **kwargs) 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/heat/engine/service.py", line 426, in stop 2016-03-25 17:29:22.264 22588 ERROR heat-engine for stack_id in list(self.thread_group_mgr.groups.keys()): 2016-03-25 17:29:22.264 22588 ERROR heat-engine AttributeError: 'NoneType' object has no attribute 'groups' 2016-03-25 17:29:22.264 22588 ERROR heat-engine 2016-03-25 17:29:22.388 22599 INFO oslo_service.service [-] Parent process has died unexpectedly, exiting ``` Full log could be found here: http://pastebin.com/raw/mgRbgvjd To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1562042/+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 1562042] Re: Traceback in error log during heat-engine service shutdown
** Changed in: cloud-archive/mitaka Status: Fix Released => Triaged -- 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/1562042 Title: Traceback in error log during heat-engine service shutdown Status in Ubuntu Cloud Archive: Triaged Status in Ubuntu Cloud Archive liberty series: Triaged Status in Ubuntu Cloud Archive mitaka series: Triaged Status in heat: Fix Released Status in heat package in Ubuntu: Fix Released Status in heat source package in Wily: Triaged Status in heat source package in Xenial: Triaged Status in heat source package in Yakkety: Fix Released Bug description: During shutdown of heat-engine service this traceback could be observed in log: ``` 2016-03-25 17:29:22.259 22588 DEBUG oslo_service.service [-] Stop services. stop /usr/lib/python2.7/dist-packages/oslo_service/service.py:583 2016-03-25 17:29:22.261 22588 DEBUG heat.engine.service [-] Attempting to stop engine service... _stop_rpc_server /usr/lib/python2.7/dist-packages/heat/engine/service.py:410 2016-03-25 17:29:22.262 22588 ERROR heat.engine.service [-] Failed to stop engine service, 'NoneType' object has no attribute 'stop' 2016-03-25 17:29:22.264 22588 CRITICAL heat-engine [-] AttributeError: 'NoneType' object has no attribute 'groups' 2016-03-25 17:29:22.264 22588 ERROR heat-engine Traceback (most recent call last): 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/bin/heat-engine", line 10, in 2016-03-25 17:29:22.264 22588 ERROR heat-engine sys.exit(main()) 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/heat/cmd/engine.py", line 79, in main 2016-03-25 17:29:22.264 22588 ERROR heat-engine launcher.wait() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 577, in wait 2016-03-25 17:29:22.264 22588 ERROR heat-engine self.stop() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 586, in stop 2016-03-25 17:29:22.264 22588 ERROR heat-engine service.stop() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/osprofiler/profiler.py", line 117, in wrapper 2016-03-25 17:29:22.264 22588 ERROR heat-engine return f(*args, **kwargs) 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/heat/engine/service.py", line 426, in stop 2016-03-25 17:29:22.264 22588 ERROR heat-engine for stack_id in list(self.thread_group_mgr.groups.keys()): 2016-03-25 17:29:22.264 22588 ERROR heat-engine AttributeError: 'NoneType' object has no attribute 'groups' 2016-03-25 17:29:22.264 22588 ERROR heat-engine 2016-03-25 17:29:22.388 22599 INFO oslo_service.service [-] Parent process has died unexpectedly, exiting ``` Full log could be found here: http://pastebin.com/raw/mgRbgvjd To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1562042/+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 1565267] Re: Gnome Calendar has white corners
https://launchpad.net/ubuntu/+source/gnome-calendar/3.20.2-0ubuntu1 ** Also affects: gnome-calendar (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: gnome-calendar (Ubuntu Xenial) Importance: Undecided => High ** Changed in: gnome-calendar (Ubuntu Xenial) Status: New => In Progress ** Changed in: gnome-calendar (Ubuntu Xenial) Importance: High => Low ** Changed in: gnome-calendar (Ubuntu) Importance: Medium => Low ** Changed in: gnome-calendar (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/1565267 Title: Gnome Calendar has white corners Status in GNOME Calendar: Fix Released Status in Ubuntu theme: New Status in gnome-calendar package in Ubuntu: Fix Released Status in gnome-calendar source package in Xenial: In Progress Bug description: * Impact the gnome-calendar window corners don't look right (white squares instead of rounded) * Test case start gnome-calendar under unity and look at the windows corner, they should be rounded. The update also include a bugfix new revesion so make sure calendar events are correctly listed and that the calendar works correctly * Regression potential the update has only small bugfixes and should be safe but keep an eye for new issues -- Gnome Calendar still looks like it is not using the proper CSD that other Gnome apps do (maps, weather, etc.) nor does it look like a patched Unity app. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-calendar 3.19.92-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 2 07:12:41 2016 InstallationDate: Installed on 2016-03-27 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1565267/+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 1562042] Re: Traceback in error log during heat-engine service shutdown
This bug was fixed in the package heat - 1:6.0.0-0ubuntu2~cloud0 --- heat (1:6.0.0-0ubuntu2~cloud0) xenial-newton; urgency=medium . * New package for the Ubuntu Cloud Archive. . heat (1:6.0.0-0ubuntu2) yakkety; urgency=medium . * d/p/engine-shutdown.patch: Cherry pick fix to ensure that heat-engine worker processes are shutdown correctly when SIGINT is received early in the process lifecycle (LP: #1562042). . heat (1:6.0.0-0ubuntu1) xenial; urgency=medium . * New upstream release for OpenStack Mitaka. . heat (1:6.0.0~rc1-0ubuntu1) xenial; urgency=medium . * New upstream release candidate for OpenStack Mitaka. * d/control: Align (build-)depends with upstream. . heat (1:6.0.0~b3-0ubuntu1) xenial; urgency=medium . * New upstream milestone for OpenStack Mitaka. * d/p/use-oslo-config-fixture-for-tests.patch: Removed. Fixed upstream. * d/control: Align (build-)depends with upstream. . heat (1:6.0.0~b2-0ubuntu2) xenial; urgency=medium . * d/p/use-oslo-config-fixture-for-tests.patch: Cherry-picked from upstream master branch to fix test failures with new oslo.config versions. . heat (1:6.0.0~b2-0ubuntu1) xenial; urgency=medium . * New upstream milestone for OpenStack Mitaka. * d/control: Align (build-)depends with upstream. . heat (1:6.0.0~b1-0ubuntu1) xenial; urgency=medium . * New upstream milestone for OpenStack Mitaka. * d/control: Align (build-)depends with upstream. * d/p/fixup-assert-regex.patch: Rebased. . heat (1:5.0.0-0ubuntu1) wily; urgency=medium . * New upstream release for OpenStack Liberty. . heat (1:5.0.0~rc2-0ubuntu1) wily; urgency=medium . * New upstream release candidate for OpenStack Liberty. * Don't clean heat.egg-info ensuring that non-py resources actually get installed (LP: #1505444). . heat (1:5.0.0~rc1-0ubuntu1) wily; urgency=medium . * New upstream release candidate for OpenStack Liberty. * d/control: Align (build-)depends with upstream. * d/watch: Update to cope with upstream rc versioning. * d/rules: Drop removal of .eggs directory in override_dh_auto_clean. * d/control: Bump minimum pbr version to 1.8. . heat (1:5.0.0~b3-0ubuntu1) wily; urgency=medium . * New upstream milestone for OpenStack Liberty. * d/control: Align (build-)depends with upstream. * d/p/fix-dummy-resource-missing.patch: Dropped. Fixed in milestone. * d/p/move-extensions.patch: Dropped. Fixed in milestone. . heat (1:5.0.0~b2-0ubuntu2) wily; urgency=medium . * d/control: Add python-pymysql to (build-)depends. * d/p/fix-dummy-resource-missing.patch: Cherry-picked from master to fix failing tests. * d/p/move-extensions: Cherry-picked from master to fix failing tests. . heat (1:5.0.0~b2-0ubuntu1) wily; urgency=medium . * New upstream milestone for OpenStack Liberty. * d/control: Align (build-)depends with upstream. * d/p/fix-requirements.patch: Dropped. No longer needed. * d/p/fixup-assert-regex.patch: Rebased. * d/rules: Remove .eggs directory in override_dh_auto_clean. . heat (1:5.0.0~b1-0ubuntu4) wily; urgency=medium . * d/heat-common.install: Include missing templates directory (LP: #1431013). * d/python-heat.install: Include missing migrate.cfg. . heat (1:5.0.0~b1-0ubuntu2) wily; urgency=medium . * No change rebuild with SQLAlchemy 1.0.6. . heat (1:5.0.0~b1-0ubuntu1) wily; urgency=medium . [ Corey Bryant ] * New upstream milestone for OpenStack Liberty: - d/control: Align (build-)depends with upstream. - d/p/fix-requirements.patch: Rebased. - d/p/sudoers_patch.patch: Rebased. . [ James Page ] * d/s/options: Ignore any removal of egg-info data during package clean. * d/control: Drop MySQL and PostgreSQL related BD's, not required for unit testing. . heat (2015.1.0-0ubuntu1.1) vivid; urgency=medium . * debian/heat-common.install: install missing scripts (LP: #1453160): - /usr/bin/heat-db-setup - /usr/bin/heat-keystone-setup-domain . heat (2015.1.0-0ubuntu1) vivid; urgency=medium . * New upstream release for OpenStack Kilo. (LP: #1449744) * d/p/fix-requirements.patch: Refreshed . heat (2015.1~rc1-0ubuntu1) vivid; urgency=medium . * New upstream milestone release for Openstack kilo; - d/control: Align with upstream dependencies. . heat (2015.1~b3-0ubuntu1) vivid; urgency=medium . [ Corey Bryant ] * New upstream milestone release for OpenStack kilo: - d/control: Align with upstream dependencies. - d/p/sudoers_patch.patch: Rebased. - d/p/fix-requirements.patch: Rebased. . [ James Page ] * d/p/fixup-assert-regex.patch: Tweak test to use assertRegexpMatches. . heat (2015.1~b2-0ubuntu3) vivid; urgency=medium . * d/pydist-overrides: Add overrides for oslo packages. * d/control: Add missing BD on python-testresources. * d/*: wrap-and-sort. . heat (2015.1~b2-0ubuntu2) vivid; urgency=medium . * d/rules: Call debhel
