[Group.of.nepali.translators] [Bug 1617155] Re: Sync cracklib2 2.9.2-3 (main) from Debian unstable (main)
This bug was fixed in the package cracklib2 - 2.9.2-3 Sponsored for Jeremy Bicha (jbicha) --- cracklib2 (2.9.2-3) unstable; urgency=medium * Fix "Buffer overflow processing long words" by applying patch from https://build.opensuse.org/package/view_file/Base:System/cracklib/ 0004-overflow-processing-long-words.patch (Closes: #835386) * remove obsolete debian/pycompat * change Vcs-* fields to https variants * Bump Standards-Version to 3.9.8 (no changes) * Fix "FTCBFS: invokes host-arch executable cracklib-packer" by applying Helmut Grohne's patch to fix cross compilation (Closes: #792860) -- Jan Dittberner Thu, 25 Aug 2016 17:29:17 +0200 cracklib2 (2.9.2-2) unstable; urgency=medium * Fix "CVE-2016-6318: Stack-based buffer overflow when parsing large GECOS field" by applying patch by Salvatore Bonaccorso (Closes: #834502) -- Jan Dittberner Tue, 23 Aug 2016 18:50:44 +0200 ** Also affects: cracklib2 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cracklib2 (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/1617155 Title: Sync cracklib2 2.9.2-3 (main) from Debian unstable (main) Status in cracklib2 package in Ubuntu: Fix Released Status in cracklib2 source package in Xenial: New Status in cracklib2 package in Debian: Fix Released Bug description: Please sync cracklib2 2.9.2-3 (main) from Debian unstable (main) Changelog entries since current yakkety version 2.9.2-1build2: cracklib2 (2.9.2-3) unstable; urgency=medium * Fix "Buffer overflow processing long words" by applying patch from https://build.opensuse.org/package/view_file/Base:System/cracklib/ 0004-overflow-processing-long-words.patch (Closes: #835386) * remove obsolete debian/pycompat * change Vcs-* fields to https variants * Bump Standards-Version to 3.9.8 (no changes) * Fix "FTCBFS: invokes host-arch executable cracklib-packer" by applying Helmut Grohne's patch to fix cross compilation (Closes: #792860) -- Jan Dittberner Thu, 25 Aug 2016 17:29:17 +0200 cracklib2 (2.9.2-2) unstable; urgency=medium * Fix "CVE-2016-6318: Stack-based buffer overflow when parsing large GECOS field" by applying patch by Salvatore Bonaccorso (Closes: #834502) -- Jan Dittberner Tue, 23 Aug 2016 18:50:44 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1617155/+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 1577049] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04
** Bug watch added: Debian Bug tracker #779740 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779740 ** Also affects: accountsservice (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779740 Importance: Unknown Status: Unknown ** Bug watch added: freedesktop.org Bugzilla #91678 https://bugs.freedesktop.org/show_bug.cgi?id=91678 ** Also affects: accountsservice via https://bugs.freedesktop.org/show_bug.cgi?id=91678 Importance: Unknown Status: Unknown -- 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/1577049 Title: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04 Status in accountsservice: Unknown Status in Ubuntu GNOME: Fix Committed Status in accountsservice package in Ubuntu: Fix Committed Status in accountsservice source package in Xenial: In Progress Status in accountsservice package in Debian: Unknown Bug description: Impact == Ubuntu 16.04's accountsservice was built without systemd support because systemd dropped libsystemd-login because that functionality was merged into libsystemd. At a minimum, this broke GNOME Shell's "Switch User" feature. Test Case = 1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages. 2. Add a user if necessary to ensure you have at least 2 user accounts configured. 3. Reload gnome-shell. You can do this with Alt+F2 and entering the lower case letter r. Or you can log out of all user accounts and log back in. 4. Click the system status area in the top right of GNOME Shell. 5. Click your user name. "Switch User" should appear in the list. Regression Potential None. The one-line change to accountsservice's configure check was made in Debian's accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was included in accountsservice 0.6.42 released in June. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1577049/+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 1577049] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04
** Package changed: gnome-shell (Ubuntu) => accountsservice (Ubuntu) ** Changed in: accountsservice (Ubuntu) Status: Triaged => 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/1577049 Title: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04 Status in Ubuntu GNOME: Fix Committed Status in accountsservice package in Ubuntu: Fix Committed Status in accountsservice source package in Xenial: Triaged Bug description: Impact == Ubuntu 16.04's accountsservice was built without systemd support because systemd dropped libsystemd-login because that functionality was merged into libsystemd. At a minimum, this broke GNOME Shell's "Switch User" feature. Test Case = 1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages. 2. Because Ubuntu does not automatically restart accountsservice on upgrades like Debian does (maybe we should?), you'll need to run this command: sudo systemctl restart accounts-daemon.service Or just restart your computer. 3. Add a user if necessary to ensure you have at least 2 user accounts configured. 4. Click the system status area in the top right of GNOME Shell. 5. Click your user name. Extra options should appear including "Switch User" Regression Potential None. This change was made in Debian's accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was included in accountsservice 0.6.42 released in June. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1577049/+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 1602243] Re: [16.10 FEAT] Upgrade Docker to newest version 1.12
block-proposed because I want to test the "docker inside lxd" thing before this migrates. ** Also affects: docker.io (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: docker.io (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Michael Hudson-Doyle (mwhudson) ** Changed in: docker.io (Ubuntu) Status: Triaged => Fix Committed ** Also affects: containerd (Ubuntu) Importance: Undecided Status: New ** Also affects: runc (Ubuntu) Importance: Undecided Status: New ** Changed in: containerd (Ubuntu) Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson) ** Changed in: runc (Ubuntu) Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson) ** Changed in: containerd (Ubuntu) Status: New => Fix Committed ** Changed in: runc (Ubuntu) Status: New => Fix Committed ** Tags added: block-proposed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1602243 Title: [16.10 FEAT] Upgrade Docker to newest version 1.12 Status in Ubuntu on IBM z Systems: Triaged Status in containerd package in Ubuntu: Fix Committed Status in docker.io package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Committed Status in containerd source package in Xenial: New Status in docker.io source package in Xenial: New Status in runc source package in Xenial: New Bug description: Update Ubuntu 16.10 support for Docker 1.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1602243/+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 1617080] [NEW] update-manager apport package hook should gather HWE infromation
Public bug reported: Sometimes systems can have a hard time installing the HWE replacements, https://errors.ubuntu.com/problem/fc13839a8f1631b1e1907d410c7f161d7fc9, it'd be helpful if apport were to gather information about what HWE packages are installed and which HWE replacement packages are recommended. Test Case - 1) Run ubuntu-bug update-manager 2) Observe there are no HWE fields in the report With the version of update-manager from -proposed you'll now see HWEunsupported (the output of hwe-support-status --show-all-unsupported) and HWEreplacements (the output of hwe-support-status --show- replacements). If you are running the -lts-xenial stack these may be empty. ** Affects: update-manager (Ubuntu) Importance: Medium Assignee: Brian Murray (brian-murray) Status: Triaged ** Affects: update-manager (Ubuntu Trusty) Importance: High Assignee: Brian Murray (brian-murray) Status: Triaged ** Affects: update-manager (Ubuntu Xenial) Importance: Medium Status: Triaged ** Also affects: update-manager (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: update-manager (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: update-manager (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: update-manager (Ubuntu Trusty) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: update-manager (Ubuntu Trusty) Status: New => Triaged ** Changed in: update-manager (Ubuntu Trusty) Importance: Undecided => High ** Changed in: update-manager (Ubuntu) Status: New => Triaged ** Changed in: update-manager (Ubuntu) Importance: Undecided => Medium ** Changed in: update-manager (Ubuntu Xenial) Status: New => Triaged ** Changed in: update-manager (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/1617080 Title: update-manager apport package hook should gather HWE infromation Status in update-manager package in Ubuntu: Triaged Status in update-manager source package in Trusty: Triaged Status in update-manager source package in Xenial: Triaged Bug description: Sometimes systems can have a hard time installing the HWE replacements, https://errors.ubuntu.com/problem/fc13839a8f1631b1e1907d410c7f161d7fc9, it'd be helpful if apport were to gather information about what HWE packages are installed and which HWE replacement packages are recommended. Test Case - 1) Run ubuntu-bug update-manager 2) Observe there are no HWE fields in the report With the version of update-manager from -proposed you'll now see HWEunsupported (the output of hwe-support-status --show-all- unsupported) and HWEreplacements (the output of hwe-support-status --show-replacements). If you are running the -lts-xenial stack these may be empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1617080/+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 1579246] Re: [SRU]handle 802.1x on ethernet properly
This bug was fixed in the package network-manager-applet - 1.2.2-0ubuntu2 --- network-manager-applet (1.2.2-0ubuntu2) yakkety; urgency=medium * Fix handling of 802.1x secrets for ethernet connections (LP: #1579246) -- Aron Xu Thu, 18 Aug 2016 17:31:26 +0800 ** Changed in: network-manager-applet (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/1579246 Title: [SRU]handle 802.1x on ethernet properly Status in NetworkManager: Fix Released Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Xenial: Fix Committed Bug description: [Impact] nm-applet does not save passwords for 802.1X on Ethernet connections, thus users will need to input password every time when connecting to it. [Test case] Connect to an 802.1X enabled Ethernet port, choose save password when authentication. Disconnect the network and reconnect, users should not be prompted again for credentials. [Regression potential] The fix is a one liner that only deals with secrets handling of certain time, potential of regression is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1579246/+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 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs
This bug was fixed in the package busybox - 1:1.22.0-19ubuntu2 --- busybox (1:1.22.0-19ubuntu2) yakkety; urgency=medium * debian/patches/readlink-in-slash-bin.patch: put readlink in /bin/ like coreutils. Closes LP: #1615021. -- Steve Langasek Tue, 23 Aug 2016 12:36:39 -0700 ** Changed in: busybox (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1615021 Title: Unable to network boot Ubuntu 16.04 installer normally on Briggs Status in busybox package in Ubuntu: Fix Released Status in debian-installer package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Committed Status in busybox source package in Xenial: Won't Fix Status in debian-installer source package in Xenial: Triaged Status in systemd source package in Xenial: In Progress Status in busybox source package in Yakkety: Fix Released Status in debian-installer source package in Yakkety: Triaged Status in systemd source package in Yakkety: Fix Committed Bug description: == Comment: #7 - Guilherme Guaglianoni Piccoli - 2016-08-19 10:08:07 == The normal procedure to perform a Netboot installation of Ubuntu 16.04 is to download the latest vmlinux and initrd.gz files available, and kexec them with no parameters (at least in ppc64el). We're experiencing a strange issue in which the installer freezes before menus are showed. The system hangs in the point specified below, right after the i40e driver initialization: [ 11.052832] i40e 0002:01:00.0 enP2p1s0f0: renamed from eth0 [ 11.073976] i40e 0002:01:00.1 enP2p1s0f1: renamed from eth1 [ 11.117799] i40e 0002:01:00.2 enP2p1s0f2: renamed from eth2 [ 11.225745] i40e 0002:01:00.3 enP2p1s0f3: renamed from eth3 ***HANG*** The most difficult part in this issue is that it seems to be a timing issue/race condition, and many debug trials end up by avoiding the issue reproduction (heisenbug). We were successful though in getting logs by booting the kernel with the command-line "BOOT_DEBUG=2" and by changing the initrd in order to enable systemd debug; only the files "init" and "start-udev" were changed in initrd, both attached here. We've attached here a saved screen session that shows the entire boot process until it gets flooded with lots of messages like: "starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink /etc/ udev/rules.d/80-net-setup-link.rules': No such file or directory' seq 3244 queued, 'add' 'pci_bus' starting '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' passed 408 byte device to netlink monitor 0x1003cfe8020seq 3236 running'/bin/readlink /etc/udev/rules.d/80-net-setup-l ink.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules': No such file or directory' '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules'(err) 'failed to execute '/bin/readlink' '/bin/readlink /etc/ udev/rules.d/80-net-setup-link.rules': No such file or directory' Process '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' failed with exit code 2. PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' /lib/udev/rules.d/73-usb-net-by-mac.rules:6 passed device to netlink monitor 0x1003d01f730 " Then it keeps hanged in this stage. We re-tested it by changing the file 73-usb-net-by-mac.rules in initrd, replacing " /etc/udev/rules.d/80-net-setup-link.rules" to "/lib/udev/rules.d/80 -net-setup-link.rules", since the former does not exist whereas the latter does. Same issue were observed! Notice that if we boot the installer with command-line "net.ifnames=0" or "net.ifnames=1", the problem does not reproduces anymore. We want to ask Canonical's help in investigating this issue. Thanks, Guilherme SRU INFORMATION for systemd === Test case: * Check what happens for uevents on devices which are not USB network interfaces: udevadm test /sys/devices/virtual/mem/null udevadm test /sys/class/net/lo With the current version these will run PROGRAM '/bin/readlink /etc/udev/rules.d/80-net-setup-link.rules' /lib/udev/rules.d/73-usb-net-by-mac.rules:6 which is pointless. With the proposed version these should be gone. * Ensure that the rule still works as intended by connecting an USB network device that has a permanent MAC address (e. g. Android tethering uses a temporary MAC): You should get a MAC-based name like "enx12345678" for it. Now disconnect it again, disable ifnames with sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules and reconnect the device. You should now
[Group.of.nepali.translators] [Bug 1616157] Re: [SRU] 2.13
This bug was fixed in the package snapd - 2.13+16.10
---
snapd (2.13+16.10) yakkety; urgency=medium
* New upstream release: LP: #1616157
- many: respect dirs.SnapSnapsDir in tests
- tests: update listing test for latest stable image
- many: hook in start of code to fetch/check assertions when
installing snap from store
- boot: add missing udevadm mock to fix FTBFS
- interfaces: add lxd-support interface
- dirs,snap: handle empty root directory in SetRootDir
- dirs,snap: define methods for SNAP_USER_DATA and SNAP_USER_COMMON
- tests: spread all-snap test cleanup
- tests: add all-snap spread image tests
- store,tests: have just one envvar SNAPPY_USE_STAGING_STORE to
control talking to staging
- overlord/hookstate: use snap run posix parameters.
- interfaces/builtin: allow bind in the network interface
- asserts,overlord/devicestate: simplify private key/key pairs APIs,
they take just key ids
- dependencies: update godeps
- boot: add support for "devmode: {true,false}" in seed.yaml
- many: teach prepare-image to copy the model assertion (and
prereqs) into the seed area of the image
- tests: start teaching the fakestore about assertions
- asserts/sysdb: embed the new format official root/trusted
assertions
- overlord/devicestate: first pass at device registration logic
- tests: add process-control interface spread test
- tests: disable unity test
- tests: adapt to new spread version
- asserts: add serial-proof device assertion
- client, cmd/snap: use the new multi-refresh endpoint
- many: preparations for image code to fetch model prereqs
- debian: add extra checks when debian/snapd.postrm purge is run
- overlord/snapstate, daemon: support for multi-snap refresh
- tests: do not leave "squashfs-root" around
- snap-exec: Fix broken `snap run --shell` and add test
- overlord/snapstate: check changes to SnapState for conflicts also.
- docs/interfaces: change snappy command to snap
- tests: test `snap run --hook` using in-tree snap-exec.
- partition: ensure that snap_{kernel,core} is not overriden with an
empty value
- asserts,overlord/assertstate: introduce an assertstate task
handler to fetch snap assertions
- spread: disable re-exec to always test development tree.
- interfaces: implement a fuse interface
- interfaces/hardware-observe.go: re-add /run/udev/data
- overlord/assertstate,daemon: reorg how the assert manager exposes
the assertion db and adding to it
- release: Remove "UBUNTU_CODENAME" from the test data
- many: implement snapctl command.
- interfaces: mpris updates (fix unconfined introspection, add name
attribute)
- asserts: export DecodePublicKey
- asserts: introduce support for assertions with no authority,
implement serial-request
- interfaces: bluez: add a few more tests to verify interface
connection works
- interfaces: bluez: add missing mount security snippet case
- interfaces: add kernel-module interface for module insertion.
- integration-tests: look for ubuntu-device-flash on PATH before
calling sudo
- client, cmd, daemon, osutil: support --yaml and --sudoer flags for
create-user
- spread: use snap-confine from ppa:snappy-dev/image for the tests
- many: move to purely hash based key lookup and to new
key/signature format (v1)
- spread: Use /home/gopath in spread.yaml
- tests: base security spread tests
-- Michael Vogt Wed, 24 Aug 2016 14:48:28
+0200
** Changed in: snapd (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/1616157
Title:
[SRU] 2.13
Status in snapd package in Ubuntu:
Fix Released
Status in snapd source package in Xenial:
Fix Committed
Bug description:
This is a new version of snapd.
The changelog for 2.13 is available here
https://github.com/snapcore/snapd/blob/2.13/debian/changelog, the raw
git changelog is available here:
https://github.com/snapcore/snapd/commits/2.13 (note that the debian
changelog is auto-generated from the merges of the git commits so
there is usually no need to look at the raw git commits).
The snappy team released a new 2.13 micro release that we want SRU
into xenial. The new process described in
https://wiki.ubuntu.com/SnapdUpdates was used and we have done
integration-tests on the snappy images, autopkgtests on classic and
unit tests.
The following automatic tests are run:
- travis unit tests https://travis-ci.org/snapcore/snapd/branches (check for
2.13 here)
- travis/spread based integration/system tests:
https://travis-ci.org/snapcore/snapd/branches (check for 2.13 here under
"spread")
- jenkins autopkgt
[Group.of.nepali.translators] [Bug 1616517] Re: whoopsie does not send fields from some package management application crashes
This bug was fixed in the package whoopsie - 0.2.24.6ubuntu3 --- whoopsie (0.2.24.6ubuntu3) trusty-proposed; urgency=medium * Allow uploading of any field with data less than 1KB, creating a whitelist of fields with large data, and a blacklist of fields we don't want in the Error Tracker. (LP: #1616559) * src/whoopsie.c: Add fields from package management applications that can be larger than 1KB to the list of accepted fields. (LP: #1616517) -- Brian Murray Tue, 23 Aug 2016 17:17:02 -0700 ** Changed in: whoopsie (Ubuntu Trusty) 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/1616517 Title: whoopsie does not send fields from some package management application crashes Status in whoopsie package in Ubuntu: Triaged Status in whoopsie source package in Trusty: Fix Released Status in whoopsie source package in Xenial: Fix Committed Bug description: The package hook for update-manager and aptdaemon add information like /var/log/apt/term.log and /var/log/apt/history.log that would be useful in debugging crashes from those applications. However, those files can be larger than 1 KB so whoopsie does not send them to the Error Tracker. We should be sending those fields along. Test Case - 1) launch update-manager 2) kill -11 the update-manager process 3) locate the update-manager .crash file and observe DpkgHistoryLog.txt in it 4) send crash report to Error Tracker (look for .uploaded file) 5) view crash report in Error Tracker (find OOPS ID by looking at syslog / whoopsie status) 6) observe DpkgHistoryLog.txt not in it With the version of the package from -proposed DpkgHistoryLog.txt should appear on the OOPS page for the crash that was sent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1616517/+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 1616781] Re: DINO2M - System hangs with a black screen during s4 stress test
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1616781 Title: DINO2M - System hangs with a black screen during s4 stress test Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: System hangs with a black screen during s4 stress test Keyboard backlight LED is still on and adjustable, but tty1 is not avalible to switch to. System needs to be hardware shutdown. Steps: 1. install Ubuntu 16.04 and boot to OS 2. run s4 stress test (30 cycles) 3. check if the test can be completed Expected results: Test should be able to be completed Actual results: System hangs with a black screen Additional information: BIOS: 99.2.22 CPU: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4x) GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1616781/+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 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled
** Also affects: cloud-archive/icehouse Importance: Undecided Status: New ** Also affects: cloud-archive/newton Importance: Undecided Status: New ** Also affects: cloud-archive/mitaka Importance: Undecided Status: New ** Also affects: cloud-archive/kilo Importance: Undecided Status: New ** Also affects: cloud-archive/liberty Importance: Undecided Status: New ** Changed in: cloud-archive/icehouse Assignee: (unassigned) => Corey Bryant (corey.bryant) ** Changed in: cloud-archive/kilo Assignee: (unassigned) => Corey Bryant (corey.bryant) ** Changed in: cloud-archive/liberty Assignee: (unassigned) => Corey Bryant (corey.bryant) ** Changed in: cloud-archive/mitaka Assignee: (unassigned) => Corey Bryant (corey.bryant) ** Changed in: cloud-archive/newton Assignee: (unassigned) => Corey Bryant (corey.bryant) -- 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/1612089 Title: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled Status in Ubuntu Cloud Archive: New Status in Ubuntu Cloud Archive icehouse series: New Status in Ubuntu Cloud Archive kilo series: New Status in Ubuntu Cloud Archive liberty series: New Status in Ubuntu Cloud Archive mitaka series: New Status in Ubuntu Cloud Archive newton series: New Status in qemu package in Ubuntu: Fix Released Status in qemu-kvm source package in Precise: Fix Released Status in qemu source package in Trusty: Fix Released Status in qemu source package in Xenial: Fix Released Status in qemu source package in Yakkety: Fix Released Bug description: If memory statistics are enabled for the memory baloon device in libvirt like this: Then qemu exits with "qemu-system-x86_64: Virtqueue size exceeded" after the VM is migrated or when starting the VM again after a managedsave. This bug is present since 2.0.0+dfsg-2ubuntu1.26 and was not present in 2.0.0+dfsg-2ubuntu1.24. It's most probably caused by the Fix for CVE-2016-5403. Steps to reproduce: 1. Create a VM with libvirt which contains the above memory balloon device 2. Start the VM and let the Linux kernel boot (bug does not appear if the kernel is not yet booted, eg. while in the PXE boot phase) 3. Issue a managedsave 4. Start the VM again 5. The VM is restored and "crashes" right after it starts running again. 6. You can find the qemu output "qemu-system-x86_64: Virtqueue size exceeded" in the log at /var/log/libvirt/vmname.log ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-x86 2.0.0+dfsg-2ubuntu1.26 ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39 Uname: Linux 3.13.0-93-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Thu Aug 11 08:39:33 2016 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1612089/+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 1616677] Re: [Hyper-V] Rebase Hyper-V to 4.7.2 (stable)
All patches are upstream ** Changed in: linux (Ubuntu Yakkety) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1616677 Title: [Hyper-V] Rebase Hyper-V to 4.7.2 (stable) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: Please rebase the Hyper-V drivers and tools in lts-xenial (and yakkity) to the final v4.7.2 stable upstream kernel. The following files comprise Hyper-V support in the upstream kernel: arch/x86/kernel/cpu/mshyperv.c arch/x86/include/asm/mshyperv.h arch/x86/include/uapi/asm/hyperv.h include/linux/hyperv.h drivers/hv/channel.c drivers/hv/channel_mgmt.c drivers/hv/connection.c drivers/hv/hv_balloon.c drivers/hv/hv.c drivers/hv/hv_fcopy.c drivers/hv/hv_kvp.c drivers/hv/hv_snapshot.c drivers/hv/hv_util.c drivers/hv/hv_utils_transport.c drivers/hv/hv_utils_transport.h drivers/hv/hyperv_vmbus.h drivers/hv/ring_buffer.c drivers/hv/vmbus_drv.c tools/hv/hv_fcopy_daemon.c tools/hv/hv_get_dhcp_info.sh tools/hv/hv_get_dns_info.sh tools/hv/hv_kvp_daemon.c tools/hv/hv_set_ifconfig.sh tools/hv/hv_vss_daemon.c tools/hv/lsvmbus drivers/input/serio/hyperv-keyboard.c drivers/net/hyperv/hyperv_net.h drivers/net/hyperv/netvsc.c drivers/net/hyperv/netvsc_drv.c drivers/net/hyperv/rndis_filter.c drivers/scsi/storvsc_drv.c drivers/hid/hid-hyperv.c drivers/pci/host/pci-hyperv.c drivers/video/fbdev/hyperv_fb.c While I know a number of post-4.6 commits are already included, I am including all of the commits from 4.6 to 4.7.2 for reference: channel_mgmt.c : commit cd95aad5579371ac332507fc946008217fc37e6c : Drivers: hv: vmbus: handle various crash scenarios connection.c : commit 5cc472477f928fb8584eb8e08245c9cf9002d74a : Drivers: hv: vmbus: Export the vmbus_set_event() API hv_balloon.c : commit 77c0c9735bc0ba5898e637a3a20d6bcb50e3f67d : Drivers: hv: balloon: don't crash when memory is added in non-sorted order hv_balloon.c : commit d19a55d6ed5bf0ffe553df2d8bf91d054ddf2d76 : Drivers: hv: balloon: reset host_specified_ha_region hv_kvp.c : commit 4dbfc2e68004c60edab7e8fd26784383dd3ee9bc : Drivers: hv: kvp: fix IP Failover hyperv_fb.c : commit 696ca5e82c057a272381ae6064d59eb97a578397 : drivers:hv: Use new vmbus_mmio_free() from client drivers. hyperv.h : commit 97fb77dc87582300fa3c141b63699f853576cab1 : drivers:hv: Make a function to free mmio regions through vmbus hyperv.h : commit a6341f24cdf1ec14dc26743a409a17378db5 : Drivers: hv: vmbus: Introduce functions for estimating room in the ring buffer hyperv.h : commit ab028db41ca9174caab7f9e3fc0a2e7f4a418410 : Drivers: hv: vmbus: Implement APIs to support "in place" consumption of vmbus packets hyperv_net.h : commit 10082f98878a9dff1563745f9f1dd9d1ff142700 : hv_netvsc: Eliminate status from struct hv_netvsc_packet hyperv_net.h : commit 3d541ac5a92af708d0085925d136f875f3a58d57 : hv_netvsc: untangle the pointer mess hyperv_net.h : commit c85e4924452ae8225c8829f3fa8a2f7baa34bc5c : hv_netvsc: Fix book keeping of skb during batching process hyperv_vmbus.h : commit 4dbfc2e68004c60edab7e8fd26784383dd3ee9bc : Drivers: hv: kvp: fix IP Failover hyperv_vmbus.h : commit 5cc472477f928fb8584eb8e08245c9cf9002d74a : Drivers: hv: vmbus: Export the vmbus_set_event() API hyperv_vmbus.h : commit cd95aad5579371ac332507fc946008217fc37e6c : Drivers: hv: vmbus: handle various crash scenarios lsvmbus : commit 552beb4930ef3889d42a049eb9ba3533b4cbe0f6 : tools: hv: lsvmbus: add pci pass-through UUID netvsc_drv.c : commit 15cfd40771e18a4e9b788c64c9db2606f958b93d : hv_netvsc: Fix the list processing for network change event netvsc_drv.c : commit 1bdcec8a5f05445752a0639edd603ac09ae6c553 : hv_netvsc: use start_remove flag to protect netvsc_link_change() netvsc_drv.c : commit 84bf9cefb162b197da20a0f4388929f4b5ba5db4 : hv_netvsc: Implement support for VF drivers on Hyper-V pci-hyperv.c : commit 696ca5e82c057a272381ae6064d59eb97a578397 : drivers:hv: Use new vmbus_mmio_free() from client drivers. pci-hyperv.c : commit bdd74440d9e887b1fa648eefa17421def5f5243c : PCI: hv: Add explicit barriers to config space access pci-hyperv.c : commit deb22e5c84c884a129d801cf3bfde7411536998d : PCI: hv: Report resources release after stopping the bus ring_buffer.c : commit a6341f24cdf1ec14dc26743a409a17378db5 : Drivers: hv: vmbus: Introduce functions for estimating room in the ring buffer rndi
[Group.of.nepali.translators] [Bug 1570923] Re: bacula-dir won't start with "undefined symbol: mysql_init"
** Changed in: bacula 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/1570923 Title: bacula-dir won't start with "undefined symbol: mysql_init" Status in Bacula: Fix Released Status in bacula package in Ubuntu: Fix Released Status in bacula source package in Xenial: In Progress Bug description: [Impact] * bacula-dir fails to start after installation. [Test Case] * Install bacula-director-mysql after installing mysql-server. bacula-dir fails to start (and the installation fails). * In a successful case, the bacula-dir process will start (and be running after installation). [Regression Potential] * The fix for this is to backport an upstream fix that changes the build to not use libmysqlclient_r.* files (which are no longer shiipped with MySQL 5.7). The regression potential should be low, as bacula-dir currently does not start at all. 1. Ubuntu release : Description:Ubuntu Xenial Xerus (development branch) Release:16.04 2. Version of package bacula-director-mysql: Installed: 7.0.5+dfsg-4build1 Candidate: 7.0.5+dfsg-4build1 Version table: *** 7.0.5+dfsg-4build1 500 500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status 3. Expectation : bacula-dir should start 4. bacula-dir did not start because of : root@xenial:~# bacula-dir -d 99 bacula-dir: dird.c:194-0 Debug level = 99 bacula-dir: address_conf.c:264-0 Initaddr 0.0.0.0:9101 root@xenial:~# bacula-dir: dir_plugins.c:148-0 Load dir plugins bacula-dir: dir_plugins.c:150-0 No dir plugin dir! bacula-dir: symbol lookup error: /usr/lib/bacula/libbaccats-7.0.5.so: undefined symbol: mysql_init To manage notifications about this bug go to: https://bugs.launchpad.net/bacula/+bug/1570923/+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 1569843] Re: smartd spindown check fails on newer disks, disabling check. Disks then spin-up when polled for SMART data.
16.10 now has 6.5+svn4324-1. ** Changed in: smartmontools (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/1569843 Title: smartd spindown check fails on newer disks, disabling check. Disks then spin-up when polled for SMART data. Status in smartmontools package in Ubuntu: Fix Released Status in smartmontools source package in Xenial: Triaged Bug description: Problem: Support for additional power modes in modern disks like Seagate ST8000AS0002 causes reporting of some power states as "unknown". Where smartd checks disk while these additional states are active, it detects that the disk fails to comply with ATA standard and ceases to use the -n directive. From then on, smartd will check the disk regardless of current power mode, causing the disk to wake from idle every time smartd polls the disk state. Symptoms: * Initially, disks do not wake from standby as smartd detects that they are idle. * At some point, smartd polls disk when in "unknown" power state. The following appears in /var/log/syslog: "Device: , CHECK POWER STATUS returned 130, not ATA compliant, ignoring -n Directive" OR "Device: , CHECK POWER STATUS returned 129, not ATA compliant, ignoring -n Directive" * Following this, disk wakes from standby (spins up) every time smartd polls for SMART status. What should have happened: Support for more recent version of ATA spec for power modes is included in updated smartmontools. By updating, smartmontools will not detect more recent disks as not supporting ATA specification and as such, will not disable -n directive. As such, smartmontools will continue to check if disks are spun down before polling for SMART data. --> As an aside, and more of an upstream issue, but a better check for smartmon to perform would be "is the disk in known sleep/standby power state" directly before waking it every time, rather than detecting if the disk is ever in an unknown power state and disabling the check. This has the advantage of not breaking the "do not wake from sleep to poll for SMART data" function if further power modes are added to the ATA spec in future revisions as long as no new sleep/standby modes are added... Cause: Current version of smartd is r4214. Support for ACS-2 disks not included. See smartmontools ticket here: https://www.smartmontools.org/ticket/184 Patch included 27/3/16 in r4255 (smartd) and r4256 (smartctl). (About two weeks ago). Ubuntu version: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 Smartmontools version: smartmontools: Installed: 6.4+svn4214-1 Candidate: 6.4+svn4214-1 Version table: *** 6.4+svn4214-1 500 500 http://au.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1569843/+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 1608652] Re: [Ubuntu 16.04] FCoE Lun not visible in OS with inbox driver - Issue with ioremap() call on 32bit kernel
Merged in v4.8-rc1 ** Also affects: linux (Ubuntu Yakkety) Importance: Medium Status: Triaged ** Changed in: linux (Ubuntu Yakkety) Status: Triaged => 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/1608652 Title: [Ubuntu 16.04] FCoE Lun not visible in OS with inbox driver - Issue with ioremap() call on 32bit kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: Broadcom has a fix for this issue that it will be sending upstream on/by 8/15/16 BUG REPRODUCTION DETAILS Test Case Instance- Reproducibility of Bug- Always Last Known Working Build - NA Time to Reproduce Bug - 5 Minutes Steps To Reproduce Bug- == 1. Map a LUN and make sure the FCoE Lun is visible in the UEFI/ as well as Legacy BIOS 2. Boot to OS, and check "fdisk -l" the Lun is not listed. Logs ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ modinfo lpfc|grep -i version version:0:11.0.0.10. srcversion: 77EBC3EEDF32DABDDF14B7F vermagic: 4.4.0-22-generic SMP mod_unload modversions 686 ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ lsmod|grep lpfc lpfc 614400 0 scsi_transport_fc 57344 1 lpfc ubuntu_sl@dhcp-10-227-71-12:~$ cd /sys/class/fc_host ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ ls ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ dmesg logs == ubuntu_sl@dhcp-10-227-71-12:/sys/class/fc_host$ dmesg|grep lpfc [ 12.521665] Modules linked in: hid_generic ahci crc32_pclmul lpfc(+) igb be2net aesni_intel ptp aes_i586 vxlan xts pps_core libahci usbhid lrw scsi_transport_fc gf128mul megaraid_sas ablk_helper wmi ip6_udp_tunnel cryptd hid i2c_algo_bit udp_tunnel fjes [ 13.532543] [] ? lpfc_pci_probe_one_s4.isra.38+0x207/0x970 [lpfc] [ 13.581554] [] ? lpfc_pci_probe_one_s4.isra.38+0x207/0x970 [lpfc] [ 13.675661] [] ? lpfc_pci_probe_one_s4.isra.38+0x207/0x970 [lpfc] [ 13.723254] [] lpfc_pci_probe_one_s4.isra.38+0x207/0x970 [lpfc] [ 13.770876] [] lpfc_pci_probe_one+0xa2/0xe40 [lpfc] [ 14.551773] [] lpfc_init+0xe4/0x1000 [lpfc] [ 15.046636] lpfc :1b:00.2: ioremap failed for SLI4 PCI config registers. [ 15.082558] lpfc :1b:00.2: 0:1410 Failed to set up pci memory space. [ 15.118685] lpfc :1b:00.3: ioremap failed for SLI4 PCI config registers. [ 15.155054] lpfc :1b:00.3: 0:1410 Failed to set up pci memory space. [ 592.495893] lpfc :1b:00.2: ioremap failed for SLI4 PCI config registers. [ 592.495900] lpfc :1b:00.2: 0:1410 Failed to set up pci memory space. [ 592.496028] lpfc :1b:00.3: ioremap failed for SLI4 PCI config registers. [ 592.496030] lpfc :1b:00.3: 0:1410 Failed to set up pci memory space. Setup Details = SUT: 10.227.65.215(IMM IP) (USERID/PASSW0RD) OS IP: 10.227.73.172(ubuntu_sl/Swamiji001) Switch: 10.227.65.35(admin/Pass1234, Port no: 6,17) IBM Target: 10.227.65.50(emulex/passw0rd) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608652/+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 1600124] Re: Adjust KBL PCI-ID's
This bug was fixed in the package libdrm - 2.4.67-1ubuntu0.16.04.2 --- libdrm (2.4.67-1ubuntu0.16.04.2) xenial; urgency=medium * add-more-kbl-pciids.diff, remove-invalid-kbl-pciids.diff: Update KBL pciids. (LP: #1600124) -- Timo Aaltonen Fri, 12 Aug 2016 09:42:55 +0300 ** Changed in: libdrm (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1600124 Title: Adjust KBL PCI-ID's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in libdrm source package in Xenial: Fix Released Status in linux source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Committed Status in xserver-xorg-video-intel source package in Xenial: Fix Released Bug description: Current list of KBL PCI-ID's is incomplete, there are a few that are should not be listed and few that are missing. To fix this, adjust the list in kernel/libdrm/mesa/ddx to match upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1600124/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
This bug was fixed in the package xserver-xorg-video-intel - 2:2.99.917+git20160325-1ubuntu1.1 --- xserver-xorg-video-intel (2:2.99.917+git20160325-1ubuntu1.1) xenial; urgency=medium [ Sean Davis ] * preserve-mouse-cursor-after-vt-switch.patch: Fix lost mouse cursor after unlocking. (LP: #1568604) [ Timo Aaltonen ] * add-more-kbl-pciids.diff, remove-invalid-kbl-pciids.diff: Update KBL pciids. (LP: #1600124) -- Timo Aaltonen Fri, 12 Aug 2016 09:32:54 +0300 ** Changed in: xserver-xorg-video-intel (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Xenial: Fix Released Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1600124] Re: Adjust KBL PCI-ID's
This bug was fixed in the package xserver-xorg-video-intel - 2:2.99.917+git20160325-1ubuntu1.1 --- xserver-xorg-video-intel (2:2.99.917+git20160325-1ubuntu1.1) xenial; urgency=medium [ Sean Davis ] * preserve-mouse-cursor-after-vt-switch.patch: Fix lost mouse cursor after unlocking. (LP: #1568604) [ Timo Aaltonen ] * add-more-kbl-pciids.diff, remove-invalid-kbl-pciids.diff: Update KBL pciids. (LP: #1600124) -- Timo Aaltonen Fri, 12 Aug 2016 09:32:54 +0300 ** Changed in: xserver-xorg-video-intel (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1600124 Title: Adjust KBL PCI-ID's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in libdrm source package in Xenial: Fix Released Status in linux source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Committed Status in xserver-xorg-video-intel source package in Xenial: Fix Released Bug description: Current list of KBL PCI-ID's is incomplete, there are a few that are should not be listed and few that are missing. To fix this, adjust the list in kernel/libdrm/mesa/ddx to match upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1600124/+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 1612365] Re: Migrate LVFS to Amazon S3
This bug was fixed in the package fwupd - 0.7.0-0ubuntu4.3 --- fwupd (0.7.0-0ubuntu4.3) xenial-proposed; urgency=medium * Download metadata from Amazon S3 instead. (LP: #1612365) -- Mario Limonciello Thu, 11 Aug 2016 15:47:41 -0500 ** Changed in: fwupd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1612365 Title: Migrate LVFS to Amazon S3 Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Fix Released Status in fwupd source package in Yakkety: Fix Released Bug description: [Impact] * The current fwupd implementation bangs on an instance of LVFS (which runs on OpenShift). As more distros have been picking up fwupd, it's become apparent that openshift can't scale and carry the load. * This has meant that FW updates can't be distributed in a timely manner and a lot of clients time out * Upstream is moving all data to Amazon S3 instead and keeping the LVFS openshift instance only as the frontend for OEM use. This change happened upstream in this commit: https://github.com/hughsie/fwupd/commit/96e1ea6b265728aad5bf43f18009abb3befc34a0 [Test Case] 1) Update to new fwupd package 2) run fwupdmgr refresh Make sure that no errors are reported [Regression Potential] * Regression potential is low. The data is still signed with the same keys, it's just been moved to a different backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1612365/+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 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled
** Also affects: cloud-archive 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/1612089 Title: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled Status in Ubuntu Cloud Archive: New Status in qemu package in Ubuntu: Fix Released Status in qemu-kvm source package in Precise: Fix Released Status in qemu source package in Trusty: Fix Released Status in qemu source package in Xenial: Fix Released Status in qemu source package in Yakkety: Fix Released Bug description: If memory statistics are enabled for the memory baloon device in libvirt like this: Then qemu exits with "qemu-system-x86_64: Virtqueue size exceeded" after the VM is migrated or when starting the VM again after a managedsave. This bug is present since 2.0.0+dfsg-2ubuntu1.26 and was not present in 2.0.0+dfsg-2ubuntu1.24. It's most probably caused by the Fix for CVE-2016-5403. Steps to reproduce: 1. Create a VM with libvirt which contains the above memory balloon device 2. Start the VM and let the Linux kernel boot (bug does not appear if the kernel is not yet booted, eg. while in the PXE boot phase) 3. Issue a managedsave 4. Start the VM again 5. The VM is restored and "crashes" right after it starts running again. 6. You can find the qemu output "qemu-system-x86_64: Virtqueue size exceeded" in the log at /var/log/libvirt/vmname.log ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-x86 2.0.0+dfsg-2ubuntu1.26 ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39 Uname: Linux 3.13.0-93-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Thu Aug 11 08:39:33 2016 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1612089/+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 1600452] Re: "Failed to set variable: (2) Invalid Parameter" when enrolling MOK
Here's the pull request:
https://github.com/rhinstaller/shim/pull/60
Once this is merged we can then backport this into Yakkety/Xenial or any
other affected versions.
** Also affects: mokutil (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: mokutil (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: mokutil (Ubuntu)
Importance: Undecided => Medium
** Changed in: mokutil (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/1600452
Title:
"Failed to set variable: (2) Invalid Parameter" when enrolling MOK
Status in mokutil package in Ubuntu:
Confirmed
Status in mokutil source package in Xenial:
Confirmed
Bug description:
## Testing Environment:
Lenovo Thinkpad P50, fresh install of Ubuntu 16.04
$ apt-cache policy mokutil
mokutil:
Installed: 0.3.0-0ubuntu3
Candidate: 0.3.0-0ubuntu3
Version table:
*** 0.3.0-0ubuntu3 500
500 http://cn.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy shim
shim:
Installed: 0.8-0ubuntu2
Candidate: 0.8-0ubuntu2
Version table:
*** 0.8-0ubuntu2 500
500 http://cn.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
## Steps to reproduce:
(1) do not disable SecureBoot as suggested during the install.
(2) install virtualbox-5.0 from the virtualbox ppa (deb
http://download.virtualbox.org/virtualbox/debian xenial contrib)
(3) Follow instructions here to manually sign the vboxdrv kernel
module (https://askubuntu.com/questions/760671/could-not-load-vboxdrv-
after-upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur/768310#768310)
$ openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform
DER -out MOK.der -nodes -days 36500 -subj "/CN=Descriptive name/"
$ sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256
./MOK.priv ./MOK.der $(modinfo -n vboxdrv)
$ sudo mokutil --import MOK.der
(enter password)
(4) reboot, click "enroll mok", "continue", "yes", enter password,
(screenshots here: https://sourceware.org/systemtap/wiki/SecureBoot)
## Expected behavior:
new mok will be enrolled and I will be asked to reboot (several users
from the original askubuntu answer indicated that these exact steps
worked for them.
## Actual behaviour:
"Error: Failed to set variable: (2) Invalid Parameter"
## Troubleshooting steps taken:
- tried different passwords, and was able to eliminate that being the cause.
- found relevant lines of code producing the error: lines 919-931 in
https://github.com/rhinstaller/shim/blob/master/MokManager.c
/# C code
efi_status = uefi_call_wrapper(RT->SetVariable, 5, db_name,
&shim_lock_guid,
EFI_VARIABLE_NON_VOLATILE
| EFI_VARIABLE_BOOTSERVICE_ACCESS
| EFI_VARIABLE_APPEND_WRITE,
MokNewSize, MokNew);
}
if (efi_status != EFI_SUCCESS) {
console_error(L"Failed to set variable", efi_status);
return efi_status;
}
C Code #/
- unable to find where uefi_call_wrapper() is defined
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mokutil 0.3.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jul 9 18:56:59 2016
InstallationDate: Installed on 2016-07-08 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: mokutil
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mokutil/+bug/1600452/+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 1607880] Re: [SRU] OpenStack mitaka point release for horizon 9.1.0
This bug was fixed in the package horizon - 2:9.1.0-0ubuntu1~cloud0 --- horizon (2:9.1.0-0ubuntu1~cloud0) trusty-mitaka; urgency=medium . * New upstream release for the Ubuntu Cloud Archive. . horizon (2:9.1.0-0ubuntu1) xenial; urgency=medium . * New upstream point release for OpenStack Mitaka (LP: #1607880). * d/p/ubuntu_settings.patch: Rebased. * d/control: Align (build-)depends with upstream. ** Changed in: cloud-archive/mitaka 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/1607880 Title: [SRU] OpenStack mitaka point release for horizon 9.1.0 Status in Ubuntu Cloud Archive: Invalid Status in Ubuntu Cloud Archive mitaka series: Fix Released Status in horizon package in Ubuntu: Invalid Status in horizon source package in Xenial: Fix Released Bug description: New point releases for misc openstack components for the mitaka release: horizon 9.1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1607880/+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 1585942] Re: Mesa causes a segmentation fault on arm64 (wrong count of uniform locations)
Reopening ubuntu-system-settings-online-accounts so that its arm64 tests
would be re-enabled.
** Changed in: webbrowser-app (Ubuntu Xenial)
Status: New => Fix Released
** No longer affects: ubuntu-system-settings-online-accounts (Ubuntu
Xenial)
** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
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/1585942
Title:
Mesa causes a segmentation fault on arm64 (wrong count of uniform
locations)
Status in Canonical System Image:
Fix Released
Status in mesa package in Ubuntu:
Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
Triaged
Status in webbrowser-app package in Ubuntu:
Fix Released
Status in mesa source package in Xenial:
Fix Released
Status in webbrowser-app source package in Xenial:
Fix Released
Bug description:
This error appeared when running unit tests for a QML app in our
Jenkins/silo infrastructure, on arm64 only:
https://launchpadlibrarian.net/261581280/buildlog_ubuntu-yakkety-arm64
.ubuntu-system-settings-online-
accounts_0.7+16.10.20160525.1-0ubuntu1_BUILDING.txt.gz
Pasting the relevant lines here in case the link above goes away:
===
QT_PLUGIN_PATH=/usr/lib/aarch64-linux-gnu/qt5/plugins
LD_LIBRARY_PATH=/usr/lib/aarch64-linux-gnu${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
xvfb-run -s '-screen 0 640x480x24' -a dbus-test-runner -t
./tst_online_accounts_qml
DBus daemon:
unix:abstract=/tmp/dbus-2tbhBHxLZq,guid=03f9df417d619b79067a68045745ad95
task-0: Started with PID: 16930
task-0: * Start testing of online_accounts_qml *
task-0: Config: Using QtTest library 5.5.1, Qt 5.5.1
(arm64-little_endian-lp64 shared (dynamic) release build; by GCC 5.3.1 20160519)
task-0: PASS : online_accounts_qml::AccountCreationPage::initTestCase()
task-0: QWARN : online_accounts_qml::AccountCreationPage::test_fallback()
file:///dummy/path/testPlugin/Main.qml: File not found
task-0: PASS : online_accounts_qml::AccountCreationPage::test_fallback()
task-0: QWARN : online_accounts_qml::AccountCreationPage::test_flickable()
file:///dummy/path/testPlugin/Main.qml: File not found
task-0: PASS : online_accounts_qml::AccountCreationPage::test_flickable()
task-0: PASS : online_accounts_qml::AccountCreationPage::cleanupTestCase()
task-0: QWARN : online_accounts_qml::UnknownTestFunc() QEGLPlatformContext:
Failed to make temporary surface current, format not updated
task-0: PASS : online_accounts_qml::AuthorizationPage::initTestCase()
task-0: QWARN : online_accounts_qml::AuthorizationPage::test_1_one_account()
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:54:
TypeError: Cannot call method 'indexOf' of undefined
task-0: PASS : online_accounts_qml::AuthorizationPage::test_1_one_account()
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_2_add_another(with button)
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:54:
TypeError: Cannot call method 'indexOf' of undefined
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_2_add_another(with button)
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:79:23:
Unable to assign [undefined] to QString
task-0: PASS :
online_accounts_qml::AuthorizationPage::test_2_add_another(with button)
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_2_add_another(with button)
[PERFORMANCE]: Last frame took 254 ms to render.
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_2_add_another(without button)
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:54:
TypeError: Cannot call method 'indexOf' of undefined
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_2_add_another(without button)
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/AuthorizationPage.qml:79:23:
Unable to assign [undefined] to QString
task-0: PASS :
online_accounts_qml::AuthorizationPage::test_2_add_another(without button)
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_2_add_another(without button)
[PERFORMANCE]: Last frame took 210 ms to render.
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_3_many_accounts(first account)
[PERFORMANCE]: Last frame took 146 ms to render.
task-0: QWARN :
online_accounts_qml::AuthorizationPage::test_3_many_accounts(first account)
file:///«BUILDDIR»/ubuntu-system-settings-online-accounts-0.7+16.10.20160525.1/online-accounts-ui/qml/
[Group.of.nepali.translators] [Bug 1616894] [NEW] [BYT] display hotplug doesn't work on console
Public bug reported: Baytrail (server) machines can't be booted up without a monitor connected, because hotplug doesn't work without X. This has been fixed upstream in v4.8-rc1, four commits need to be backported: 4570d833390b100 drm/i915/vlv: Make intel_crt_reset() per-encoder 4c732e6ee9e7190 drm/i915/vlv: Reset the ADPA in vlv_display_power_well_init() 21842ea84f161ae drm/i915/vlv: Disable HPD in valleyview_crt_detect_hotplug() 84c8e0963da434d drm/i915: Enable polling when we don't have hpd ** Affects: linux (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: linux (Ubuntu) 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/1616894 Title: [BYT] display hotplug doesn't work on console Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: In Progress Bug description: Baytrail (server) machines can't be booted up without a monitor connected, because hotplug doesn't work without X. This has been fixed upstream in v4.8-rc1, four commits need to be backported: 4570d833390b100 drm/i915/vlv: Make intel_crt_reset() per-encoder 4c732e6ee9e7190 drm/i915/vlv: Reset the ADPA in vlv_display_power_well_init() 21842ea84f161ae drm/i915/vlv: Disable HPD in valleyview_crt_detect_hotplug() 84c8e0963da434d drm/i915: Enable polling when we don't have hpd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616894/+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 1568170] Re: add software boutique to advanced mate menu
** Also affects: mate-menu (Ubuntu) Importance: Undecided Status: New ** Also affects: mate-menu (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ubuntu-mate Status: Confirmed => Triaged ** Changed in: mate-menu (Ubuntu Xenial) Status: New => Triaged ** Tags added: xenial ** Changed in: mate-menu (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: mate-menu (Ubuntu Xenial) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: mate-menu (Ubuntu Xenial) Milestone: None => xenial-updates ** Changed in: mate-menu (Ubuntu) Status: New => Triaged ** Changed in: mate-menu (Ubuntu) Importance: Undecided => Medium ** Changed in: mate-menu (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) -- 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/1568170 Title: add software boutique to advanced mate menu Status in ubuntu-mate: Triaged Status in mate-menu package in Ubuntu: Triaged Status in mate-menu source package in Xenial: Triaged Bug description: The system section/plugin of the advanced mate menu shows an entry for 'Package Manager', so why not show the new beautiful software boutique above it or in place of it, similar to Linux Mint showing the 'Software Manager'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1568170/+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 1605761] Re: Main Menu editor destroys applications menu when processing a non-ASCII character.
** Changed in: ubuntu-mate
Assignee: (unassigned) => Martin Wimpress (flexiondotorg)
** Also affects: mozo (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mozo (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: mozo (Ubuntu Xenial)
Milestone: None => xenial-updates
** Changed in: mozo (Ubuntu)
Status: New => Fix Committed
** Changed in: mozo (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-mate
Importance: Low => Medium
** Changed in: mozo (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: mozo (Ubuntu Xenial)
Assignee: (unassigned) => Martin Wimpress (flexiondotorg)
** Changed in: mozo (Ubuntu)
Assignee: (unassigned) => Martin Wimpress (flexiondotorg)
** Changed in: mozo (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/1605761
Title:
Main Menu editor destroys applications menu when processing a non-
ASCII character.
Status in ubuntu-mate:
Fix Committed
Status in mozo package in Ubuntu:
Fix Committed
Status in mozo source package in Xenial:
Triaged
Bug description:
There is a entry in my applications menu named "Life Is Strange™"
(note the ™ character). When using the Main Menu editor to make
adjustments to the layout of the menus, a serious error occurs while
processing the ™ character and as a result, destroys the entire
~/.config/menus/mate-applications.menu file to 0 kB. Occurs in Ubuntu
MATE 16.04.1.
A workaround is to rename the affecting program's name in a text
editor before using the Main Menu tool.
This is the back trace from mate-panel:
-
/usr/lib/python2.7/dist-packages/Mozo/MenuEditor.py:533: UnicodeWarning:
Unicode equal comparison failed to convert both arguments to Unicode -
interpreting them as being unequal
if node.childNodes[0].nodeName == 'Filename' and
node.childNodes[0].childNodes[0].nodeValue == filename:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/Mozo/MainWindow.py", line 430, in
on_menu_tree_drag_data_received
self.editor.copyItem(item, new_parent)
File "/usr/lib/python2.7/dist-packages/Mozo/MenuEditor.py", line 298, in
copyItem
self.save()
File "/usr/lib/python2.7/dist-packages/Mozo/MenuEditor.py", line 68, in save
fd.write(re.sub("\n[\s]*([^\n<]*)\n[\s]*\n', '')))
File "/usr/lib/python2.7/xml/dom/minidom.py", line 61, in toprettyxml
return writer.getvalue()
File "/usr/lib/python2.7/StringIO.py", line 271, in getvalue
self.buf += ''.join(self.buflist)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 15:
ordinal not in range(128)
** (mate-panel:12720): WARNING **: Error loading menu layout from
"/home/luke/.config/menus/mate-applications.menu": Error on line 1
char 1: Document was empty or contained only whitespace
-
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1605761/+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 1616533] Re: "Forecast not available" error in GNOME Weather app
** Also affects: libmateweather (Ubuntu) Importance: Undecided Status: New ** Changed in: libmateweather (Ubuntu) Status: New => Triaged ** Changed in: libmateweather (Ubuntu) Importance: Undecided => High ** Changed in: libmateweather (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Also affects: libgweather (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: libmateweather (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-weather (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: libmateweather (Ubuntu Xenial) Status: New => Triaged ** Changed in: libmateweather (Ubuntu Xenial) Importance: Undecided => High ** Changed in: libmateweather (Ubuntu Xenial) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) -- 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/1616533 Title: "Forecast not available" error in GNOME Weather app Status in libgweather: Confirmed Status in gnome-weather package in Ubuntu: Triaged Status in libgweather package in Ubuntu: Triaged Status in libmateweather package in Ubuntu: Triaged Status in gnome-weather source package in Xenial: New Status in libgweather source package in Xenial: New Status in libmateweather source package in Xenial: Triaged Bug description: As reported at http://www.omgubuntu.co.uk/2016/08/gnome-weather- forecast-not-available The weather forecast provider used by the GNOME Weather app discontinued or moved its service. To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1616533/+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 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts
Same for account-plugins -- this was marked for being fixed in y, but the comment that closes it was for xenial already, and yet the xenial task is still open. This is horribly confusing and wrong, so I mark as v-failed for the time being as at least the wrong gnome-control-center- signon in yakkety needs to be fixed. ** Changed in: account-plugins (Ubuntu Yakkety) Status: Fix Released => In Progress ** Tags removed: verification-needed ** Tags added: verification-failed ** Changed in: account-plugins (Ubuntu Yakkety) Assignee: (unassigned) => Alberto Mardegan (mardy) ** Changed in: gnome-control-center-signon (Ubuntu Yakkety) Assignee: (unassigned) => Alberto Mardegan (mardy) -- 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/1565772 Title: [SRU] Allow plugins to decide which username to set on new accounts Status in Online Accounts: Account plugins: Fix Released Status in Canonical System Image: Fix Released Status in Online Accounts: GNOME Control Center: Fix Released Status in webapps-sprint: Fix Committed Status in account-plugins package in Ubuntu: In Progress Status in gnome-control-center-signon package in Ubuntu: In Progress Status in account-plugins source package in Xenial: Fix Committed Status in gnome-control-center-signon source package in Xenial: Fix Committed Status in account-plugins source package in Yakkety: In Progress Status in gnome-control-center-signon source package in Yakkety: In Progress Bug description: This bug is related to bug 1547647, even though it makes sense in any case. Currently, the ApOAuthPlugin class in libaccount-plugin gets the username from the SignonIdentity, which in turn gets it from signon- ui, which in the current WebKit1 implementation gets it from the DOM of the login webpage. This is a hack, it's fragile, not trivial to port to the Oxide web engine, and possibly against some providers' guidelines. We should retrieve the username using some REST API provided by the service, and in order to do so we need to extend libaccounts-plugin with some hooks which subclasses can use to get the username. Once we fix this we can also get rid of the files /etc/signon-ui /webkit-options.d/, which are conflicting with those installed by the KDE account plugins packages. SRU information === [Impact] The same file /etc/signon-ui/webkit- options.d/www.facebook.com.conf is installed by the account-plugin- facebook package (used by Unity) and by kaccount-providers (used by KDE). See this bug's duplicates to see actual bug reports. [Test Case] Install both account-plugin-facebook and kaccount- providers and you'll get the conflict. [Regression Potential] Users running KDE will be completely unaffected by this. Users running Unity might see a change when creating accounts in System Settings->Online Accounts: with this bugfix, the account's display name is obtained by making a REST API call to the remote service, rather than by scrapping the DOM of the server webpages (which is a hack, and prone to errors if the providers' webpage changes). The new way of retrieving the username is the proper one, and it's been tested to work reliably. In any case, the worst thing that might happen is that accounts get created with an empty display name, which is mostly an aesthetic problem (the display name is used only for UI purposes). To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1565772/+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 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts
Argh, I saw too late that this is already marked as fixed for yakkety , but the version there is 0.1.9+16.04.20160405-0ubuntu1 . I. e. it is smaller than the version in xenial, which breaks upgrades. This is a blocker for releasing the update, so y needs to be updated ASAP. ** Changed in: gnome-control-center-signon (Ubuntu Yakkety) Status: Fix Released => In Progress ** Changed in: account-plugins (Ubuntu Xenial) 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/1565772 Title: [SRU] Allow plugins to decide which username to set on new accounts Status in Online Accounts: Account plugins: Fix Released Status in Canonical System Image: Fix Released Status in Online Accounts: GNOME Control Center: Fix Released Status in webapps-sprint: Fix Committed Status in account-plugins package in Ubuntu: In Progress Status in gnome-control-center-signon package in Ubuntu: In Progress Status in account-plugins source package in Xenial: Fix Committed Status in gnome-control-center-signon source package in Xenial: Fix Committed Status in account-plugins source package in Yakkety: In Progress Status in gnome-control-center-signon source package in Yakkety: In Progress Bug description: This bug is related to bug 1547647, even though it makes sense in any case. Currently, the ApOAuthPlugin class in libaccount-plugin gets the username from the SignonIdentity, which in turn gets it from signon- ui, which in the current WebKit1 implementation gets it from the DOM of the login webpage. This is a hack, it's fragile, not trivial to port to the Oxide web engine, and possibly against some providers' guidelines. We should retrieve the username using some REST API provided by the service, and in order to do so we need to extend libaccounts-plugin with some hooks which subclasses can use to get the username. Once we fix this we can also get rid of the files /etc/signon-ui /webkit-options.d/, which are conflicting with those installed by the KDE account plugins packages. SRU information === [Impact] The same file /etc/signon-ui/webkit- options.d/www.facebook.com.conf is installed by the account-plugin- facebook package (used by Unity) and by kaccount-providers (used by KDE). See this bug's duplicates to see actual bug reports. [Test Case] Install both account-plugin-facebook and kaccount- providers and you'll get the conflict. [Regression Potential] Users running KDE will be completely unaffected by this. Users running Unity might see a change when creating accounts in System Settings->Online Accounts: with this bugfix, the account's display name is obtained by making a REST API call to the remote service, rather than by scrapping the DOM of the server webpages (which is a hack, and prone to errors if the providers' webpage changes). The new way of retrieving the username is the proper one, and it's been tested to work reliably. In any case, the worst thing that might happen is that accounts get created with an empty display name, which is mostly an aesthetic problem (the display name is used only for UI purposes). To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1565772/+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
