[Group.of.nepali.translators] [Bug 1555865] Re: CVE-2015-7515
** Changed in: linux-armadaxp (Ubuntu Precise) 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/1555865 Title: CVE-2015-7515 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: New Status in linux-lts-trusty source package in Vivid: New Status in linux-lts-utopic source package in Vivid: New Status in linux-lts-vivid source package in Vivid: New Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: New Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: New Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: New Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in
[Group.of.nepali.translators] [Bug 1581065] Re: incorrect parsing of != dependency versions
This bug was fixed in the package dh-python - 2.20151103ubuntu2 --- dh-python (2.20151103ubuntu2) yakkety; urgency=medium * dhpython/pydist.py: Ensure that != dependency versions are ignored (LP: #1581065). -- James PageThu, 12 May 2016 17:04:43 +0100 ** Changed in: dh-python (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/1581065 Title: incorrect parsing of != dependency versions Status in dh-python package in Ubuntu: Fix Released Status in dh-python source package in Xenial: Triaged Status in dh-python source package in Yakkety: Fix Released Bug description: Some updates to requirements for openstack projects (glance and keystone specifically) is causing dh-python to incorrectly generate a != version dependency; this is the requires.txt entry: cryptography!=1.3.0,>=1.0 which causes (utimately): dpkg-gencontrol: warning: can't parse dependency python-cryptography (!= 1.3.0) from the generated dependency line: "python-castellan, python-crypto (>= 2.6), python-cryptography (!= 1.3.0), python-debtcollector, python-eventlet, python-futurist, python-glance-store, python-httplib2, python-iso8601, python- jsonschema, python-keystoneauth1, python-keystoneclient, python- keystonemiddleware, python-migrate, python-monotonic, python-openssl, python-oslo.concurrency, python-oslo.config, python-oslo.context, python-oslo.db, python-oslo.i18n, python-oslo.log, python- oslo.messaging, python-oslo.middleware, python-oslo.policy, python- oslo.serialization, python-oslo.service, python-oslo.utils, python- osprofiler, python-paste, python-pastedeploy, python-pbr, python- prettytable, python-retrying, python-semantic-version, python-six (>= 1.9.0), python-sqlalchemy (>= 1.0~), python-sqlalchemy (<< 1.1), python-stevedore, python-taskflow, python-webob, python-wsme, python:any (<< 2.8), python:any (>= 2.6~), python:any (>= 2.7.5-5~), python:any (>= 2.7~)," ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dh-python 2.20151103ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 12 15:15:36 2016 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-17 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) PackageArchitecture: all SourcePackage: dh-python UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1581065/+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 1581186] Re: mtr 0.86 doesn't respect terminal colors
This bug was fixed in the package mtr - 0.86-1ubuntu1 --- mtr (0.86-1ubuntu1) yakkety; urgency=medium * Pull commits from upstream to fix terminal colours (LP: #1581186) -- Adam ConradThu, 12 May 2016 12:34:22 -0600 ** Changed in: mtr (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/1581186 Title: mtr 0.86 doesn't respect terminal colors Status in mtr package in Ubuntu: Fix Released Status in mtr source package in Xenial: Fix Committed Status in mtr package in Debian: Unknown Bug description: [ SRU Justification ] mtr 0.86 added more colours to the curses output, but this broke how it blends in with dark terminals with non-standard colours, and light terminals in general. While this is purely cosmetic, it's pretty ugly compared to mtr 0.85, and the fix is trivial and trivially verified as correct (or, more correct than 0.86) on several different terminal colour schemes. As a man who uses mtr daily, it's been driving me mildly nuts. [ Solution ] Two commits upstream fix this, so it's a little more readable again on light terminals, and doesn't mess with non-standard terminals: 63a1f1493bfbaf7e55eb7e20b3791fc8b14cf92d 7571201cf7a3394e0dcd2b037aba1836089cc084 [ Test Case ] Run old and new mtr on a variety of terminal schemes (default gnome-terminal, inverted gnome-terminal, default and inverted xterm, etc) to see if it's (a) as readable or more than before, (b) now shows sanely default bg colours, (c) works correctly with transparent backgrounds. The first point is somewhat subjective, though a quick test here shows that on "xterm -rv", the bold text has switched from some barely- readable grey-on-white to something approaching black-on-white, so I think this is moving in a winning direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtr/+bug/1581186/+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 1581186] [NEW] mtr 0.86 doesn't respect terminal colors
Public bug reported: [ SRU Justification ] mtr 0.86 added more colours to the curses output, but this broke how it blends in with dark terminals with non-standard colours, and light terminals in general. While this is purely cosmetic, it's pretty ugly compared to mtr 0.85, and the fix is trivial and trivially verified as correct (or, more correct than 0.86) on several different terminal colour schemes. As a man who uses mtr daily, it's been driving me mildly nuts. [ Solution ] Two commits upstream fix this, so it's a little more readable again on light terminals, and doesn't mess with non-standard terminals: 63a1f1493bfbaf7e55eb7e20b3791fc8b14cf92d 7571201cf7a3394e0dcd2b037aba1836089cc084 [ Test Case ] Run old and new mtr on a variety of terminal schemes (default gnome-terminal, inverted gnome-terminal, default and inverted xterm, etc) to see if it's (a) as readable or more than before, (b) now shows sanely default bg colours, (c) works correctly with transparent backgrounds. The first point is somewhat subjective, though a quick test here shows that on "xterm -rv", the bold text has switched from some barely- readable grey-on-white to something approaching black-on-white, so I think this is moving in a winning direction. ** Affects: mtr (Ubuntu) Importance: Undecided Status: New ** Affects: mtr (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: mtr (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/1581186 Title: mtr 0.86 doesn't respect terminal colors Status in mtr package in Ubuntu: New Status in mtr source package in Xenial: New Bug description: [ SRU Justification ] mtr 0.86 added more colours to the curses output, but this broke how it blends in with dark terminals with non-standard colours, and light terminals in general. While this is purely cosmetic, it's pretty ugly compared to mtr 0.85, and the fix is trivial and trivially verified as correct (or, more correct than 0.86) on several different terminal colour schemes. As a man who uses mtr daily, it's been driving me mildly nuts. [ Solution ] Two commits upstream fix this, so it's a little more readable again on light terminals, and doesn't mess with non-standard terminals: 63a1f1493bfbaf7e55eb7e20b3791fc8b14cf92d 7571201cf7a3394e0dcd2b037aba1836089cc084 [ Test Case ] Run old and new mtr on a variety of terminal schemes (default gnome-terminal, inverted gnome-terminal, default and inverted xterm, etc) to see if it's (a) as readable or more than before, (b) now shows sanely default bg colours, (c) works correctly with transparent backgrounds. The first point is somewhat subjective, though a quick test here shows that on "xterm -rv", the bold text has switched from some barely- readable grey-on-white to something approaching black-on-white, so I think this is moving in a winning direction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtr/+bug/1581186/+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 1569577] Re: please remove var/lib/snapd/apparmor/additional from debian/snapd.dirs
This bug was fixed in the package snapd - 2.0.3 --- snapd (2.0.3) xenial; urgency=medium * New upstream micro release: - integration-tests, debian/tests: add unity snap autopkg test - snappy: introduce first feature flag for assumes: common-data-dir - timeout,snap: add YAML unmarshal function for timeout.Timeout - many: go into state.Retry state when unmounting a snap fails. (LP: #1571721, #1575399) - daemon,client,cmd/snap: improve output after snap install/refresh/remove (LP: #1574830) - integration-tests, debian/tests: add test for home interface - interfaces,overlord: support unversioned data - interfaces/builtin: improve the bluez interface - cmd: don't include the unit tests when building with go test -c for integration tests - integration-tests: teach some new trick to the fake store, reenable the app refresh test - many: move with some simplifications test snap building to snap/snaptest - asserts: define type for revision related errors - snap/snaptest,daemon,overlord/ifacestate,overlord/snapstate: unify mocking snaps behind MockSnap - snappy: fix openSnapFile's handling of sideInfo - daemon: improve snap sideload form handling - snap: add short and long description to the man-page (LP: #1570280) - snappy: remove unused SetProperty - snappy: use more accurate test data - integration-tests: add a integration test about remove removing all revisions - overlord/snapstate: make "snap remove" remove all revisions of a snap (LP: #1571710) - integration-tests: re-enable a bunch of integration tests - snappy: remove unused dbus code - overlord/ifacestate: fix setup-profiles to use new snap revision for setup (LP: #1572463) - integration-tests: add regression test for auth bug LP:#1571491 - client, snap: remove obsolete TypeCore which was used in the old SystemImage days - integration-tests: add apparmor test - cmd: don't perform type assertion when we know error to be nil - client: list correct snap types - intefaces/builtin: allow getsockname on connected x11 plugs (LP: #1574526) - daemon,overlord/snapstate: read name out of sideloaded snap early, improved change summary - overlord: keep tasks unlinked from a change hidden, prune them - integration-tests: snap list on fresh boot is good again - integration-tests: add partial term to the find test - integration-tests: changed default release to 16 - integration-tests: add regression test for snaps not present after reboot - integration-tests: network interface - integration-tests: add proxy related environment variables to snapd env file - README.md: snappy => snap - etc: trivial typo fix (LP:#1569892) - debian: remove unneeded /var/lib/snapd/apparmor/additional directory (LP: #1569577) -- Michael VogtTue, 03 May 2016 07:51:57 +0200 ** Changed in: snapd (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/1569577 Title: please remove var/lib/snapd/apparmor/additional from debian/snapd.dirs Status in Snappy: Fix Committed Status in snapd package in Ubuntu: Fix Committed Status in snapd source package in Xenial: Fix Released Bug description: /var/lib/snapd/apparmor/additional is no longer used by anything. Please remove it from debian/snapd.dirs. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1569577/+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 1571721] Re: Removing when an app is running results in a half removal
This bug was fixed in the package snapd - 2.0.3 --- snapd (2.0.3) xenial; urgency=medium * New upstream micro release: - integration-tests, debian/tests: add unity snap autopkg test - snappy: introduce first feature flag for assumes: common-data-dir - timeout,snap: add YAML unmarshal function for timeout.Timeout - many: go into state.Retry state when unmounting a snap fails. (LP: #1571721, #1575399) - daemon,client,cmd/snap: improve output after snap install/refresh/remove (LP: #1574830) - integration-tests, debian/tests: add test for home interface - interfaces,overlord: support unversioned data - interfaces/builtin: improve the bluez interface - cmd: don't include the unit tests when building with go test -c for integration tests - integration-tests: teach some new trick to the fake store, reenable the app refresh test - many: move with some simplifications test snap building to snap/snaptest - asserts: define type for revision related errors - snap/snaptest,daemon,overlord/ifacestate,overlord/snapstate: unify mocking snaps behind MockSnap - snappy: fix openSnapFile's handling of sideInfo - daemon: improve snap sideload form handling - snap: add short and long description to the man-page (LP: #1570280) - snappy: remove unused SetProperty - snappy: use more accurate test data - integration-tests: add a integration test about remove removing all revisions - overlord/snapstate: make "snap remove" remove all revisions of a snap (LP: #1571710) - integration-tests: re-enable a bunch of integration tests - snappy: remove unused dbus code - overlord/ifacestate: fix setup-profiles to use new snap revision for setup (LP: #1572463) - integration-tests: add regression test for auth bug LP:#1571491 - client, snap: remove obsolete TypeCore which was used in the old SystemImage days - integration-tests: add apparmor test - cmd: don't perform type assertion when we know error to be nil - client: list correct snap types - intefaces/builtin: allow getsockname on connected x11 plugs (LP: #1574526) - daemon,overlord/snapstate: read name out of sideloaded snap early, improved change summary - overlord: keep tasks unlinked from a change hidden, prune them - integration-tests: snap list on fresh boot is good again - integration-tests: add partial term to the find test - integration-tests: changed default release to 16 - integration-tests: add regression test for snaps not present after reboot - integration-tests: network interface - integration-tests: add proxy related environment variables to snapd env file - README.md: snappy => snap - etc: trivial typo fix (LP:#1569892) - debian: remove unneeded /var/lib/snapd/apparmor/additional directory (LP: #1569577) -- Michael VogtTue, 03 May 2016 07:51:57 +0200 ** Changed in: snapd (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/1571721 Title: Removing when an app is running results in a half removal Status in Snappy: Fix Committed Status in snapd package in Ubuntu: Fix Committed Status in snapd source package in Xenial: Fix Released Bug description: |-- sergiusens@lindon:~/source/github.com/sergiusens/telegram-snap (master *) --| $ sudo snap remove telegram [sudo] password for sergiusens: [\] Remove snap "telegram" from the system error: cannot perform the following tasks: - Remove snap "telegram" from the system (remove /snap/telegram/11/bin/Telegram: read-only file system) |-- sergiusens@lindon:~/source/github.com/sergiusens/telegram-snap (master *) --| $ sudo snap remove telegram [|] Remove security profile for snap "telegram" error: cannot perform the following tasks: - Remove snap "telegram" from the system (remove /snap/telegram/11/bin/Telegram: read-only file system) I had an apps/telegram/command: telegram and it was running during the removal (it was not a daemon). To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1571721/+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 1572463] Re: setup-profile configures security based on snap.Info from DisconnectSnap, which still sees older revision
This bug was fixed in the package snapd - 2.0.3 --- snapd (2.0.3) xenial; urgency=medium * New upstream micro release: - integration-tests, debian/tests: add unity snap autopkg test - snappy: introduce first feature flag for assumes: common-data-dir - timeout,snap: add YAML unmarshal function for timeout.Timeout - many: go into state.Retry state when unmounting a snap fails. (LP: #1571721, #1575399) - daemon,client,cmd/snap: improve output after snap install/refresh/remove (LP: #1574830) - integration-tests, debian/tests: add test for home interface - interfaces,overlord: support unversioned data - interfaces/builtin: improve the bluez interface - cmd: don't include the unit tests when building with go test -c for integration tests - integration-tests: teach some new trick to the fake store, reenable the app refresh test - many: move with some simplifications test snap building to snap/snaptest - asserts: define type for revision related errors - snap/snaptest,daemon,overlord/ifacestate,overlord/snapstate: unify mocking snaps behind MockSnap - snappy: fix openSnapFile's handling of sideInfo - daemon: improve snap sideload form handling - snap: add short and long description to the man-page (LP: #1570280) - snappy: remove unused SetProperty - snappy: use more accurate test data - integration-tests: add a integration test about remove removing all revisions - overlord/snapstate: make "snap remove" remove all revisions of a snap (LP: #1571710) - integration-tests: re-enable a bunch of integration tests - snappy: remove unused dbus code - overlord/ifacestate: fix setup-profiles to use new snap revision for setup (LP: #1572463) - integration-tests: add regression test for auth bug LP:#1571491 - client, snap: remove obsolete TypeCore which was used in the old SystemImage days - integration-tests: add apparmor test - cmd: don't perform type assertion when we know error to be nil - client: list correct snap types - intefaces/builtin: allow getsockname on connected x11 plugs (LP: #1574526) - daemon,overlord/snapstate: read name out of sideloaded snap early, improved change summary - overlord: keep tasks unlinked from a change hidden, prune them - integration-tests: snap list on fresh boot is good again - integration-tests: add partial term to the find test - integration-tests: changed default release to 16 - integration-tests: add regression test for snaps not present after reboot - integration-tests: network interface - integration-tests: add proxy related environment variables to snapd env file - README.md: snappy => snap - etc: trivial typo fix (LP:#1569892) - debian: remove unneeded /var/lib/snapd/apparmor/additional directory (LP: #1569577) -- Michael VogtTue, 03 May 2016 07:51:57 +0200 ** Changed in: snapd (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/1572463 Title: setup-profile configures security based on snap.Info from DisconnectSnap, which still sees older revision Status in Snappy: Fix Committed Status in snapd package in Ubuntu: Fix Committed Status in snapd source package in Xenial: Fix Released Bug description: When the same snap is sideloaded two times the security profile stops working: ``` $ sudo snap install youtube-dl_2016.03.27_amd64.snap [\] Setup snap "youtube-dl" security profiles $ youtube-dl.run WARNING: Assuming --restrict-filenames since file system encoding cannot encode all characters. Set the LC_ALL environment variable to fix this. Usage: youtube-dl [OPTIONS] URL [URL...] youtube-dl: error: You must provide at least one URL. Type youtube-dl --help to see a list of all options. $ sudo snap install youtube-dl_2016.03.27_amd64.snap [-] Copy snap "youtube-dl" data $ youtube-dl.run /bin/sh: 0: Can't open /snap/youtube-dl/12/command-run.wrapper $ dmesg|tail -n1 [13348.347319] audit: type=1400 audit(1461143833.011:132): apparmor="DENIED" operation="open" profile="snap.youtube-dl.run" name="/snap/youtube-dl/12/command-run.wrapper" pid=28849 comm="command-run.wra" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 $ grep SNAP_REVISION}= /var/lib/snapd/apparmor/profiles/snap.youtube-dl.run @{SNAP_REVISION}="11" ``` $ snap changes|grep sideload 6Done2016-04-20T09:17:02Z 2016-04-20T09:17:03Z Install "/tmp/snapd-sideload-pkg-620395148" snap file 7Done2016-04-20T09:17:10Z 2016-04-20T09:17:11Z Install "/tmp/snapd-sideload-pkg-340731359" snap file To manage notifications about this
[Group.of.nepali.translators] [Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu
Thanks for testing, John. To narrow it down further, can you test some of the 3.18 release candidates? They can all be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/ I'd suggest trying -rc1 first. If that version does not have the bug, try some of the newer candidates: v3.18-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc1-utopic/ v3.18-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc4-vivid/ v3.18-rc7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc7-vivid/ Once we know the last good kernel version and the first bad one, we can bisect between them. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: High Assignee: Joseph Salisbury (jsalisbury) Status: Confirmed ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Vivid) Status: New => In Progress ** Changed in: linux (Ubuntu Wily) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Yakkety) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Wily) Importance: Undecided => High ** Changed in: linux (Ubuntu Vivid) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Wily) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Vivid) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- 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/1571798 Title: Broadwell ECRC Support missing in Ubuntu Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: Here is the problem statement from the Dell team: When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel Quick Assist Card, the memory location that corresponds to ECRC is set to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot. This causes the card to not function unless we implement the following workaround using setpci. “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for the Intel Quick Assit Card. We’ve verified the memory location is correct when booting to other OSes, such as RHEL 7.2 and Windows Server 2012 R2. If there is any information you can give as to why this may be occurring in Ubuntu or where we may start to debug when the memory is changed, we would appreciate it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+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 1578006] Re: Xenial minimal install: "W: plymouth: The plugin label.so is missing, the selected theme might not work as expected."
This bug was fixed in the package plymouth - 0.9.2-3ubuntu13.1 --- plymouth (0.9.2-3ubuntu13.1) xenial; urgency=medium * Fix hook script to not print warnings about label.so when using the ubuntu-text theme. LP: #1578006. -- Steve LangasekTue, 10 May 2016 10:28:16 -0700 ** Changed in: plymouth (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/1578006 Title: Xenial minimal install: "W: plymouth: The plugin label.so is missing, the selected theme might not work as expected." Status in plymouth package in Ubuntu: Fix Released Status in plymouth source package in Xenial: Fix Released Bug description: [SRU Justification] All users of ubuntu-text-based plymouth themes get a spurious warning when generating initramfs. This warning is trivially fixable. [Regression potential] Only the regression potential of a new binary build. The only change to the code is to bypass this warning message for the 'ubuntu-text' plugin. [Test case] 1. Install the plymouth-theme-ubuntu-text package. 2. Uninstall/deconfigure all graphical themes (e.g.: apt remove plymouth-theme-ubuntu) 3. Run update-initramfs -u 4. Confirm that a warning message is shown about label.so being missing. 5. Install plymouth from -proposed. 6. Run update-initramfs -u 7. Confirm that no warning message is shown. 8. Boot and confirm that the text theme is shown correctly. I installed a minimal Xenial system. Whenever the initramfs is regenerated, I see W: plymouth: The plugin label.so is missing, the selected theme might not work as expected. W: plymouth: You might want to install the plymouth-themes and plymouth-label package to fix this. The following plymouth packages are installed: # dpkg -l | grep plymouth ii libplymouth4:amd64 0.9.2-3ubuntu13 amd64graphical boot animation and logger - shared libraries ii plymouth 0.9.2-3ubuntu13 amd64boot animation, logger and I/O multiplexer ii plymouth-theme-ubuntu-text 0.9.2-3ubuntu13 amd64boot animation, logger and I/O multiplexer - ubuntu text theme A minimal install of Ubuntu should pull in the appropriate packages so that Plymouth doesn't complain. (As it is, I don't see much of a splash screen on startup.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1578006/+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 1580355] Re: promote *_diag modules from linux-image-extra to linux-image
** Also affects: linux (Ubuntu Yakkety) Importance: Wishlist Status: Triaged ** Changed in: linux (Ubuntu Yakkety) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** 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) => 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/1580355 Title: promote *_diag modules from linux-image-extra to linux-image Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Committed Bug description: Hi, For checkpoint restore support via CRIU, we need to use the following modules: udp_diag tcp_diag inet_diag netlink_diag af_packet_diag unix_diag some of which aren't included in linux-image, requiring users to install linux-image-extra. It would be handy if these were in the main kernel package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1580355/+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 1578622] Re: glance do not require hypervisor_mapping
This bug was fixed in the package simplestreams - 0.1.0~bzr430-0ubuntu1 --- simplestreams (0.1.0~bzr430-0ubuntu1) yakkety; urgency=medium * New upstream snapshot. - set a default user agent (LP: #1578622) - glance mirror: do not require that hypervisor_config be present (LP: #1578624) - Optimise read_signed method for better performance (LP: #1580534) -- Scott MoserThu, 12 May 2016 12:55:30 -0400 ** Changed in: simplestreams (Ubuntu Yakkety) 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/1578622 Title: glance do not require hypervisor_mapping Status in simplestreams: Fix Committed Status in simplestreams package in Ubuntu: Fix Released Status in simplestreams source package in Xenial: Confirmed Status in simplestreams source package in Yakkety: Fix Released Bug description: currently the glance mirror requires hypervisor_mapping config in the api. Better to not required that as a library consumer would not necessarily provide it. To manage notifications about this bug go to: https://bugs.launchpad.net/simplestreams/+bug/1578622/+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 1580534] Re: Signature verification is too slow
This bug was fixed in the package simplestreams - 0.1.0~bzr430-0ubuntu1 --- simplestreams (0.1.0~bzr430-0ubuntu1) yakkety; urgency=medium * New upstream snapshot. - set a default user agent (LP: #1578622) - glance mirror: do not require that hypervisor_config be present (LP: #1578624) - Optimise read_signed method for better performance (LP: #1580534) -- Scott MoserThu, 12 May 2016 12:55:30 -0400 ** Changed in: simplestreams (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/1580534 Title: Signature verification is too slow Status in simplestreams: Fix Committed Status in simplestreams package in Ubuntu: Fix Released Status in simplestreams source package in Xenial: Confirmed Bug description: [Impact] When running against http://cloud- images.ubuntu.com/releases/streams/v1/com.ubuntu.cloud:released:download.sjson, read_signed() in simplestreams/utils.py seems to take minutes (402 seconds in my instrumented timing) running 100% CPU. At the time of my test, download.sjson is 451737 bytes in 1870 lines. This makes a uvtool sync virtually unusable on Xenial. [Development Fix] The culprit is the constant += of a string as it is read in. This is inefficient in Python as each += results in a new string that has to be allocated. Keeping the lines in a list and joining them at the end reduces the time to 0.127 seconds. [Stable Fix] No change cherry-pick of fix committed upstream. [Test Case] On a machine with reasonable connectivity, run: uvt-simplestreams- libvirt sync release=xenial arch=amd64 Expected result: takes a few seconds with minimal CPU use. Actual result: takes more than five minutes with CPU pegged at 100%. Scott also has a more direct test case here: http://paste.ubuntu.com/16377613/ [Original Notes] Merge proposal to follow. I'm filing this bug to track a Xenial SRU. To manage notifications about this bug go to: https://bugs.launchpad.net/simplestreams/+bug/1580534/+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 1578624] Re: set custom user agent
This bug was fixed in the package simplestreams - 0.1.0~bzr430-0ubuntu1 --- simplestreams (0.1.0~bzr430-0ubuntu1) yakkety; urgency=medium * New upstream snapshot. - set a default user agent (LP: #1578622) - glance mirror: do not require that hypervisor_config be present (LP: #1578624) - Optimise read_signed method for better performance (LP: #1580534) -- Scott MoserThu, 12 May 2016 12:55:30 -0400 ** Changed in: simplestreams (Ubuntu Yakkety) 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/1578624 Title: set custom user agent Status in simplestreams: Fix Committed Status in simplestreams package in Ubuntu: Fix Released Status in simplestreams source package in Trusty: Confirmed Status in simplestreams source package in Wily: Confirmed Status in simplestreams source package in Xenial: Confirmed Status in simplestreams source package in Yakkety: Fix Released Bug description: In order for web service to aggregate custom logs, simplestreams client should identify itself via user-agent. To manage notifications about this bug go to: https://bugs.launchpad.net/simplestreams/+bug/1578624/+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 1581140] Re: SRU: Fix PR ld/20060, ld --gc-sections fail with __tls_get_addr_opt.
fixed in 16.10 with binutils 2.26-9ubuntu1 ** Changed in: binutils (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/1581140 Title: SRU: Fix PR ld/20060, ld --gc-sections fail with __tls_get_addr_opt. Status in binutils: Unknown Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Xenial: New Bug description: Fix PR ld/20060, ld --gc-sections fail with __tls_get_addr_opt. This is a regression compared to earlier releases (2.24). Affects ppc* only. Acceptance criteria: The new test cases pass on ppc64el. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1581140/+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 1581140] [NEW] SRU: Fix PR ld/20060, ld --gc-sections fail with __tls_get_addr_opt.
Public bug reported: Fix PR ld/20060, ld --gc-sections fail with __tls_get_addr_opt. This is a regression compared to earlier releases (2.24). Affects ppc* only. Acceptance criteria: The new test cases pass on ppc64el. ** Affects: binutils Importance: Unknown Status: Unknown ** Affects: binutils (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: binutils (Ubuntu Xenial) Importance: Undecided Status: New ** Summary changed: - Fix PR ld/20060, ld --gc-sections fail with __tls_get_addr_opt. + SRU: Fix PR ld/20060, ld --gc-sections fail with __tls_get_addr_opt. ** Also affects: binutils (Ubuntu Xenial) Importance: Undecided Status: New ** Bug watch added: Sourceware.org Bugzilla #20060 https://sourceware.org/bugzilla/show_bug.cgi?id=20060 ** Also affects: binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=20060 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/1581140 Title: SRU: Fix PR ld/20060, ld --gc-sections fail with __tls_get_addr_opt. Status in binutils: Unknown Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Xenial: New Bug description: Fix PR ld/20060, ld --gc-sections fail with __tls_get_addr_opt. This is a regression compared to earlier releases (2.24). Affects ppc* only. Acceptance criteria: The new test cases pass on ppc64el. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1581140/+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 1580534] Re: Signature verification is too slow
** Also affects: simplestreams (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/1580534 Title: Signature verification is too slow Status in simplestreams: New Status in simplestreams package in Ubuntu: New Status in simplestreams source package in Xenial: New Bug description: When running against http://cloud- images.ubuntu.com/releases/streams/v1/com.ubuntu.cloud:released:download.sjson, read_signed() in simplestreams/utils.py seems to take minutes (402 seconds in my instrumented timing) running 100% CPU. At the time of my test, download.sjson is 451737 bytes in 1870 lines. This makes a uvtool sync virtually unusable on Xenial. The culprit is the constant += of a string as it is read in. This is inefficient in Python as each += results in a new string that has to be allocated. Keeping the lines in a list and joining them at the end reduces the time to 0.127 seconds. Merge proposal to follow. I'm filing this bug to track a Xenial SRU. To manage notifications about this bug go to: https://bugs.launchpad.net/simplestreams/+bug/1580534/+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 1581005] Re: Dell XPS 15 9550 Freezes when HDMI is plugged in
Do you happen to know the commit that fixes this in the 4.6 kernel? If not, we can perform a "Reverse" bisect to identify the fix. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => 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 ** Tags added: kernel-da-key -- 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/1581005 Title: Dell XPS 15 9550 Freezes when HDMI is plugged in Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: This is fixed upstream in the 4.6.0 series. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.39 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: michael2087 F pulseaudio CurrentDesktop: Unity Date: Thu May 12 07:25:29 2016 HibernationDevice: RESUME=UUID=20adf9e8-41f0-4bf8-8075-dcff091511d4 InstallationDate: Installed on 2016-03-12 (60 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=ea2a2622-df89-4bf1-8f58-99f313ed3908 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581005/+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 1576409] Re: calling init.d script with "status" invokes pager
** Changed in: systemd (Debian) 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/1576409 Title: calling init.d script with "status" invokes pager Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd package in Debian: Fix Released Bug description: Running e. g. "/etc/init.d/networking status" runs a pager (less by default). This is unexpected from an init.d script, and potentially breaks scripts or CLI programs that do this operation, as this then hangs eternally in the interactive pager process until the user quits it. This reportedly happens with "vagrant up" (see original Debian bug https://bugs.debian.org/765175). SRU INFORMATION: Test case: Run "/etc/init.d/networking status". In current xenial this invokes less which you need to quit. With the proposed fix this should return to the shell immediately without a pager. Regression potential: very low. The main visible change is the interactive usage of "/etc/init.d/foo status", but nothing in Ubuntu (nor hopefully anywhere else) *relies* on the fact that systemctl invokes a pager, particularly as this is not always done (it depends on whether stdout is a terminal and how many lines are written). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1576409/+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 1387908] Re: [udev] FIDO u2f security keys should be supported out of the box
This bug was fixed in the package systemd - 229-6ubuntu1 --- systemd (229-6ubuntu1) yakkety; urgency=medium * Merge with Debian unstable. Remaining Ubuntu changes: - Hack to support system-image read-only /etc, and modify files in /etc/writable/ instead. systemd (229-6) unstable; urgency=medium * systemd-container: Prefer renamed "btrfs-progs" package name over "btrfs-tools". (Closes: #822629) * systemd-container: Recommend libnss-mymachines. (Closes: #822615) * Drop systemd-dbg, in favor of debhelpers' automatic -dbgsym packages. * Drop Add-targets-for-compatibility-with-Debian-insserv-sy.patch; we don't need $x-display-manager any more as most/all DMs ship native services, and $mail-transport-agent is not widely used (not even by our default MTA exim4). * Unify our two patches for Debian specific configuration files. * Drop udev-re-enable-mount-propagation-for-udevd.patch, i. e. run udevd in its own slave mount name space again. laptop-mode-tools 1.68 fixed the original bug (#762018), thus add a Breaks: to earlier versions. * Ship fbdev-blacklist.conf in /lib/modprobe.d/ instead of /etc/modprobe.d/; remove the conffile on upgrades. * Replace util-Add-hidden-suffixes-for-ucf.patch with patch that got committed upstream. * Replace Stop-syslog.socket-when-entering-emergency-mode.patch with patch that got committed upstream. * debian/udev.README.Debian: Adjust documentation of MAC based naming for USB network cards to the udev rule, where this was moved to in 229-5. * debian/extra/init-functions.d/40-systemd: Invoke status command with --no-pager, to avoid blocking scripts that call an init.d script with "status" with an unexpected pager process. (Closes: #765175, LP: #1576409) * Add debian/extra/rules/70-debian-uaccess.rules: Make FIDO U2F dongles accessible to the user session. This avoids having to install libu2f-host0 (which isn't discoverable at all) to make those devices work. (LP: #1387908) * libnss-resolve: Enable systemd-resolved.service on package installation, as this package makes little sense without resolved. * Add a DHCP exit hook for pushing received NTP servers into timesyncd. (LP: #1578663) * debian/udev.postinst: Fix migration check from the old persistent-net generator to not apply to chroots. (Closes: #813141) * Revert "enable TasksMax= for all services by default, and set it to 512". Introducing a default limit on number of threads broke a lot of software which regularly needs more, such as MySQL and RabbitMQ, or services that spawn off an indefinite number of subtasks that are not in a scope, like LXC or cron. 512 is way too much for most "simple" services, and it's way too little for the ones mentioned above. Effective (and much stricter) limits should instead be put into units individually. (Closes: #823530, LP: #1578080) * Split out udev rule to name USB network interfaces by MAC address into 73-usb-net-by-mac.rules, so that it's easier to disable. (Closes: #824025) * 73-usb-net-by-mac.rules: Disable when net.ifnames=0 is specified on the kernel command line, to be consistent with disabling the *.link files. * 73-special-net-names.rule: Name the IBM integrated management module virtual USB network card "ibmimm". Thanks Marco d'Itri! -- Martin PittThu, 12 May 2016 10:30:59 +0200 ** Changed in: systemd (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/1387908 Title: [udev] FIDO u2f security keys should be supported out of the box Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: Confirmed Status in systemd source package in Xenial: Fix Released Bug description: [Impact] * Users plugin U2F key and it does not work in Google Chrome [Test Case] * Have stock ubuntu install, without custom U2F rules or libu2f-host0 installed * Use U2F factor authentication website e.g. google apps, github, yubico, etc. * Pluging in the key, should just work and complete U2F authentication instead of timing out [Regression Potential] * Should not conflict with libu2f-host0 udev rules which is where these are currently shipped FIDO u2f is an emerging standard for public-private cryptography based 2nd factor authentication, which improves on OTP by mitigating phishing, man-in-the-middle attacks and reply attacks. Google Chrome supports u2f devices which are now widely available from Yubico (new premium neo Yubikeys and Security keys). However, udev rules are required to setup permissions to allow the web-browsers which are running as regular users to access the devices in question. E.g.:
[Group.of.nepali.translators] [Bug 1578080] Re: percona cluster hits resource limits in HA Openstack cloud with xenial
This bug was fixed in the package systemd - 229-6ubuntu1 --- systemd (229-6ubuntu1) yakkety; urgency=medium * Merge with Debian unstable. Remaining Ubuntu changes: - Hack to support system-image read-only /etc, and modify files in /etc/writable/ instead. systemd (229-6) unstable; urgency=medium * systemd-container: Prefer renamed "btrfs-progs" package name over "btrfs-tools". (Closes: #822629) * systemd-container: Recommend libnss-mymachines. (Closes: #822615) * Drop systemd-dbg, in favor of debhelpers' automatic -dbgsym packages. * Drop Add-targets-for-compatibility-with-Debian-insserv-sy.patch; we don't need $x-display-manager any more as most/all DMs ship native services, and $mail-transport-agent is not widely used (not even by our default MTA exim4). * Unify our two patches for Debian specific configuration files. * Drop udev-re-enable-mount-propagation-for-udevd.patch, i. e. run udevd in its own slave mount name space again. laptop-mode-tools 1.68 fixed the original bug (#762018), thus add a Breaks: to earlier versions. * Ship fbdev-blacklist.conf in /lib/modprobe.d/ instead of /etc/modprobe.d/; remove the conffile on upgrades. * Replace util-Add-hidden-suffixes-for-ucf.patch with patch that got committed upstream. * Replace Stop-syslog.socket-when-entering-emergency-mode.patch with patch that got committed upstream. * debian/udev.README.Debian: Adjust documentation of MAC based naming for USB network cards to the udev rule, where this was moved to in 229-5. * debian/extra/init-functions.d/40-systemd: Invoke status command with --no-pager, to avoid blocking scripts that call an init.d script with "status" with an unexpected pager process. (Closes: #765175, LP: #1576409) * Add debian/extra/rules/70-debian-uaccess.rules: Make FIDO U2F dongles accessible to the user session. This avoids having to install libu2f-host0 (which isn't discoverable at all) to make those devices work. (LP: #1387908) * libnss-resolve: Enable systemd-resolved.service on package installation, as this package makes little sense without resolved. * Add a DHCP exit hook for pushing received NTP servers into timesyncd. (LP: #1578663) * debian/udev.postinst: Fix migration check from the old persistent-net generator to not apply to chroots. (Closes: #813141) * Revert "enable TasksMax= for all services by default, and set it to 512". Introducing a default limit on number of threads broke a lot of software which regularly needs more, such as MySQL and RabbitMQ, or services that spawn off an indefinite number of subtasks that are not in a scope, like LXC or cron. 512 is way too much for most "simple" services, and it's way too little for the ones mentioned above. Effective (and much stricter) limits should instead be put into units individually. (Closes: #823530, LP: #1578080) * Split out udev rule to name USB network interfaces by MAC address into 73-usb-net-by-mac.rules, so that it's easier to disable. (Closes: #824025) * 73-usb-net-by-mac.rules: Disable when net.ifnames=0 is specified on the kernel command line, to be consistent with disabling the *.link files. * 73-special-net-names.rule: Name the IBM integrated management module virtual USB network card "ibmimm". Thanks Marco d'Itri! -- Martin PittThu, 12 May 2016 10:30:59 +0200 ** Changed in: systemd (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/1578080 Title: percona cluster hits resource limits in HA Openstack cloud with xenial Status in percona-xtradb-cluster-5.6 package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in percona-cluster package in Juju Charms Collection: Won't Fix Status in systemd package in Debian: Confirmed Bug description: I'm trying to deploy Mitaka Openstack using the 16.04 charms on Xenial using Juju 1.25.5 and MAAS 1.9.2, with as many components of Openstack being HA as possible. When deployed, after running for a while mysql (which is a 3 node cluster) starts refusing connections, and erroring: 2016-05-03 01:25:28 13795 [ERROR] Error log throttle: 50 'Can't create thread to handle new connection' error(s) suppressed When I look at systemd-cgtop, I can see it maxing out at 512 connections. To get it going again I do a: $ sudo systemctl edit mysql and set: TasksMax=infinity Sometimes I even need to edit /etc/systemd/system.conf and bump DefaultTasksMax to 1024 or higher, depending on long its been left running. I've noticed that dropping worker-multiplier setting on nova-cloud-
[Group.of.nepali.translators] [Bug 1578663] Re: create DHCP exit hook for setting NTP servers through dhclient
This bug was fixed in the package systemd - 229-6ubuntu1 --- systemd (229-6ubuntu1) yakkety; urgency=medium * Merge with Debian unstable. Remaining Ubuntu changes: - Hack to support system-image read-only /etc, and modify files in /etc/writable/ instead. systemd (229-6) unstable; urgency=medium * systemd-container: Prefer renamed "btrfs-progs" package name over "btrfs-tools". (Closes: #822629) * systemd-container: Recommend libnss-mymachines. (Closes: #822615) * Drop systemd-dbg, in favor of debhelpers' automatic -dbgsym packages. * Drop Add-targets-for-compatibility-with-Debian-insserv-sy.patch; we don't need $x-display-manager any more as most/all DMs ship native services, and $mail-transport-agent is not widely used (not even by our default MTA exim4). * Unify our two patches for Debian specific configuration files. * Drop udev-re-enable-mount-propagation-for-udevd.patch, i. e. run udevd in its own slave mount name space again. laptop-mode-tools 1.68 fixed the original bug (#762018), thus add a Breaks: to earlier versions. * Ship fbdev-blacklist.conf in /lib/modprobe.d/ instead of /etc/modprobe.d/; remove the conffile on upgrades. * Replace util-Add-hidden-suffixes-for-ucf.patch with patch that got committed upstream. * Replace Stop-syslog.socket-when-entering-emergency-mode.patch with patch that got committed upstream. * debian/udev.README.Debian: Adjust documentation of MAC based naming for USB network cards to the udev rule, where this was moved to in 229-5. * debian/extra/init-functions.d/40-systemd: Invoke status command with --no-pager, to avoid blocking scripts that call an init.d script with "status" with an unexpected pager process. (Closes: #765175, LP: #1576409) * Add debian/extra/rules/70-debian-uaccess.rules: Make FIDO U2F dongles accessible to the user session. This avoids having to install libu2f-host0 (which isn't discoverable at all) to make those devices work. (LP: #1387908) * libnss-resolve: Enable systemd-resolved.service on package installation, as this package makes little sense without resolved. * Add a DHCP exit hook for pushing received NTP servers into timesyncd. (LP: #1578663) * debian/udev.postinst: Fix migration check from the old persistent-net generator to not apply to chroots. (Closes: #813141) * Revert "enable TasksMax= for all services by default, and set it to 512". Introducing a default limit on number of threads broke a lot of software which regularly needs more, such as MySQL and RabbitMQ, or services that spawn off an indefinite number of subtasks that are not in a scope, like LXC or cron. 512 is way too much for most "simple" services, and it's way too little for the ones mentioned above. Effective (and much stricter) limits should instead be put into units individually. (Closes: #823530, LP: #1578080) * Split out udev rule to name USB network interfaces by MAC address into 73-usb-net-by-mac.rules, so that it's easier to disable. (Closes: #824025) * 73-usb-net-by-mac.rules: Disable when net.ifnames=0 is specified on the kernel command line, to be consistent with disabling the *.link files. * 73-special-net-names.rule: Name the IBM integrated management module virtual USB network card "ibmimm". Thanks Marco d'Itri! -- Martin PittThu, 12 May 2016 10:30:59 +0200 ** Changed in: systemd (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1578663 Title: create DHCP exit hook for setting NTP servers through dhclient Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Yakkety: Fix Released Bug description: Similar to /etc/dhcp/dhclient-exit-hooks.d/ntpdate, we should ship a DHCP exit hook for timesyncd to update the timesyncd configuration in /run/systemd/timesyncd.conf.d/01-dhclient.conf to set the picked up NTP servers, and restart timesyncd. SRU INFORMATION === Rationale: This is a regression compared to trusty where we used ntpdate; /etc/dhcp/dhclient-exit-hooks.d/ntpdate ran ntpdate on the new NTP servers. This causes timesyncd to always try and talk to the disto configured server (ntp.ubuntu.com) which might be disallowed by firewall rules or other networking policy. Thus machines in such an environment never get a correct time sync even when they get a local NTP server advertised over DHCP (unless they use systemd-networkd, which is not done by default in Xenial). Test case: - Set up a DHCP server that includes NTP information. For example, you can set LXC_DHCP_CONFILE=/etc/lxc/dnsmasq.conf in
[Group.of.nepali.translators] [Bug 1571174] Re: package squid3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
This bug was fixed in the package dpkg - 1.18.4ubuntu1.1 --- dpkg (1.18.4ubuntu1.1) xenial; urgency=medium * Add Breaks on ufw (<< 0.35-0ubuntu2~) for trigger loops (LP: #1571174) -- Adam ConradThu, 12 May 2016 04:35:55 -0600 ** Changed in: dpkg (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/1571174 Title: package squid3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in dpkg package in Ubuntu: Invalid Status in squid3 package in Ubuntu: Invalid Status in dpkg source package in Xenial: Fix Released Status in squid3 source package in Xenial: In Progress Bug description: [ SRU Justification ] Older versions of ufw had an interest-await trigger, causing trigger loops in some cases, especially the case of upgrading squid3. The newer version fixed this, however if squid is upgraded first, that's no help. [ Test Case ] == In a wily chroot with updates/security enabled == apt-get install ufw squid3 sed -i -e 's/wily/xenial/g' /etc/apt/sources.list apt-get update apt-get dist-upgrade == Repeat the above with xenial-proposed added before the upgrade == Should succeed if either squid or dpkg have been updated for the Breaks. [ Test Case 2 ] [racb] I noticed that this doesn't reproduce every time, so try it a few times. Steps to reproduce: lxc launch ubuntu:wily squid3-upgrade lxc exec squid3-upgrade bash apt-get update && apt-get -y dist-upgrade apt-get install -y squid3 ufw sed -i s/wily/xenial/g /etc/apt/sources.list apt-get update systemctl mask systemd-sysctl.service # workaround for LP: #1580984 DEBIAN_FRONTEND=noninteractive apt-get -y -o DPkg::options::=--force-confnew dist-upgrade Expected result: success Actual result: dpkg: dependency problems prevent processing triggers for ufw: ufw depends on python3; however: Package python3 is not configured yet. ufw depends on python3:any (>= 3.3.2-2~); however: Package python3 is not configured yet. dpkg: error processing archive /var/cache/apt/archives/squid3_3.5.12-1ubuntu7_all.deb (--unpack): dependency problems - leaving triggers unprocessed E: Sub-process /usr/bin/dpkg returned an error code (1) Cleanup after test: exit lxc delete -f squid3-upgrade [ Original Report ] During an upgrade from 15.10 to 16.04, upgrading squid3 erred out... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: squid3 3.3.8-1ubuntu16.2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sat Apr 16 05:33:51 2016 DuplicateSignature: package:squid3:3.3.8-1ubuntu16.2:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-12-07 (131 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: squid3 Title: package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-16 (0 days ago) modified.conffile..etc.apparmor.d.usr.sbin.squid3: [deleted] modified.conffile..etc.init.d.squid3: [deleted] modified.conffile..etc.init.squid3.conf: [deleted] modified.conffile..etc.logrotate.d.squid3: [deleted] modified.conffile..etc.resolvconf.update.libc.d.squid3: [deleted] modified.conffile..etc.squid3.errorpage.css: [deleted] modified.conffile..etc.squid3.msntauth.conf: [deleted] modified.conffile..etc.squid3.squid.conf: [deleted] modified.conffile..etc.ufw.applications.d.squid3: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1571174/+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 1581097] [NEW] click-apparmor does not properly calculate the policy version with 15.10 policy
Public bug reported: aa-clickhook fails with wily frameworks because of this: apparmor.easyprof.AppArmorException: "Could not find templates directory '/usr/share/apparmor/easyprof/templates/ubuntu/15.1'". It is reading the json 15.10 number for policy version as 15.1. ** Affects: click-apparmor (Ubuntu) Importance: High Assignee: Jamie Strandboge (jdstrand) Status: In Progress ** Affects: click-apparmor (Ubuntu Xenial) Importance: High Assignee: Jamie Strandboge (jdstrand) Status: Triaged ** Affects: click-apparmor (Ubuntu Yakkety) Importance: High Assignee: Jamie Strandboge (jdstrand) Status: In Progress ** Also affects: click-apparmor (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: click-apparmor (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: click-apparmor (Ubuntu Yakkety) Status: New => In Progress ** Changed in: click-apparmor (Ubuntu Xenial) Status: New => Triaged ** Changed in: click-apparmor (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: click-apparmor (Ubuntu Xenial) Importance: Undecided => High ** Changed in: click-apparmor (Ubuntu Yakkety) Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Changed in: click-apparmor (Ubuntu Xenial) Assignee: (unassigned) => Jamie Strandboge (jdstrand) -- 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/1581097 Title: click-apparmor does not properly calculate the policy version with 15.10 policy Status in click-apparmor package in Ubuntu: In Progress Status in click-apparmor source package in Xenial: Triaged Status in click-apparmor source package in Yakkety: In Progress Bug description: aa-clickhook fails with wily frameworks because of this: apparmor.easyprof.AppArmorException: "Could not find templates directory '/usr/share/apparmor/easyprof/templates/ubuntu/15.1'". It is reading the json 15.10 number for policy version as 15.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1581097/+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 1451453] Re: cinder fails to build with python 2.7.9 in trusty
** Also affects: keystone (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: python-glanceclient (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cinder (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: keystone (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: python-glanceclient (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: cinder (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Wily) 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/1451453 Title: cinder fails to build with python 2.7.9 in trusty Status in cinder package in Ubuntu: Triaged Status in keystone package in Ubuntu: Triaged Status in neutron package in Ubuntu: Triaged Status in python-glanceclient package in Ubuntu: Triaged Status in cinder source package in Wily: New Status in keystone source package in Wily: New Status in neutron source package in Wily: New Status in python-glanceclient source package in Wily: New Status in cinder source package in Xenial: New Status in keystone source package in Xenial: New Status in neutron source package in Xenial: New Status in python-glanceclient source package in Xenial: New Bug description: seen in a test rebuild in trusty with python 2.7.9: https://launchpad.net/ubuntu/+archive/test-rebuild-20150501-updates/+build/7375304 Traceback (most recent call last): File "/build/buildd/cinder-2014.1.4/cinder/tests/test_wsgi.py", line 165, in test_app_using_ssl response = urllib2.urlopen('https://127.0.0.1:%d/' % server.port) File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python2.7/urllib2.py", line 431, in open response = self._open(req, data) File "/usr/lib/python2.7/urllib2.py", line 449, in _open '_open', req) File "/usr/lib/python2.7/urllib2.py", line 409, in _call_chain result = func(*args) File "/usr/lib/python2.7/urllib2.py", line 1240, in https_open context=self._context) File "/usr/lib/python2.7/urllib2.py", line 1197, in do_open raise URLError(err) URLError: Ran 3020 tests in 142.297s FAILED (failures=2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1451453/+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 1572120] Re: SRU: ubuntu-mate-artwork 16.04.6.1 bug fix release
This bug was fixed in the package ubuntu-mate-artwork - 16.04.6.1 --- ubuntu-mate-artwork (16.04.6.1) xenial; urgency=medium [ Adolfo Jayme Barrientos ] * Add 1px padding to calendar widget elements; looks better. Thanks, Khurshid Alam. (LP: #1537794) [ Will Cooke ] * Adds these fixes for Calendar: (LP: #1551744, #1558659) [ Martin Wimpress ] * Merged fixes from ubuntu-themes. * Closes (LP: #1572120) -- Martin WimpressTue, 19 Apr 2016 13:26:03 +0100 ** Changed in: ubuntu-mate-artwork (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/1572120 Title: SRU: ubuntu-mate-artwork 16.04.6.1 bug fix release Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-mate-artwork source package in Xenial: Fix Released Bug description: A bug fix update for ubuntu-mate-artwork is ready for upload. Here are the changes: ubuntu-mate-artwork (16.04.6.1) xenial; urgency=medium [ Adolfo Jayme Barrientos ] * Add 1px padding to calendar widget elements; looks better. Thanks, Khurshid Alam. (LP: #1537794) [ Will Cooke ] * Adds these fixes for Calendar: (LP: #1551744, #1558659) [ Martin Wimpress ] * Merged fixes from ubuntu-themes. * Closes (LP: #1572120) -- Martin Wimpress Tue, 19 Apr 2016 13:26:03 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1572120/+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 1572120] Re: SRU: ubuntu-mate-artwork 16.04.6.1 bug fix release
This bug was fixed in the package ubuntu-mate-artwork - 16.04.6.1 --- ubuntu-mate-artwork (16.04.6.1) xenial; urgency=medium [ Adolfo Jayme Barrientos ] * Add 1px padding to calendar widget elements; looks better. Thanks, Khurshid Alam. (LP: #1537794) [ Will Cooke ] * Adds these fixes for Calendar: (LP: #1551744, #1558659) [ Martin Wimpress ] * Merged fixes from ubuntu-themes. * Closes (LP: #1572120) -- Martin WimpressTue, 19 Apr 2016 13:26:03 +0100 ** Changed in: ubuntu-mate-artwork (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/1572120 Title: SRU: ubuntu-mate-artwork 16.04.6.1 bug fix release Status in ubuntu-mate-artwork package in Ubuntu: Fix Committed Status in ubuntu-mate-artwork source package in Xenial: Fix Released Bug description: A bug fix update for ubuntu-mate-artwork is ready for upload. Here are the changes: ubuntu-mate-artwork (16.04.6.1) xenial; urgency=medium [ Adolfo Jayme Barrientos ] * Add 1px padding to calendar widget elements; looks better. Thanks, Khurshid Alam. (LP: #1537794) [ Will Cooke ] * Adds these fixes for Calendar: (LP: #1551744, #1558659) [ Martin Wimpress ] * Merged fixes from ubuntu-themes. * Closes (LP: #1572120) -- Martin Wimpress Tue, 19 Apr 2016 13:26:03 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1572120/+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 1537794] Re: Wrong padding for gtkCalender (Unity7, Xenial)
This bug was fixed in the package ubuntu-mate-artwork - 16.04.6.1 --- ubuntu-mate-artwork (16.04.6.1) xenial; urgency=medium [ Adolfo Jayme Barrientos ] * Add 1px padding to calendar widget elements; looks better. Thanks, Khurshid Alam. (LP: #1537794) [ Will Cooke ] * Adds these fixes for Calendar: (LP: #1551744, #1558659) [ Martin Wimpress ] * Merged fixes from ubuntu-themes. * Closes (LP: #1572120) -- Martin WimpressTue, 19 Apr 2016 13:26:03 +0100 ** Changed in: ubuntu-mate-artwork (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/1537794 Title: Wrong padding for gtkCalender (Unity7, Xenial) Status in ubuntu-mate-artwork package in Ubuntu: Fix Committed Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-mate-artwork source package in Xenial: Fix Released Status in ubuntu-themes source package in Xenial: New Bug description: After recent update, gtkCalender using 0px padding on top-bottom which makes it looks ugly. A mere 1px padding could solve the issue. See the screenshot for comparison: http://i.imgur.com/rFciw8h.png Patch (for Ambiance): Index: ubuntu-themes-14.04+16.04.20160120/Ambiance/gtk-3.0/gtk-widgets.css === --- ubuntu-themes-14.04+16.04.20160120.orig/Ambiance/gtk-3.0/gtk-widgets.css +++ ubuntu-themes-14.04+16.04.20160120/Ambiance/gtk-3.0/gtk-widgets.css @@ -806,7 +806,7 @@ GtkComboBox .menu .menuitem *:insensitiv border-radius: 0; border-style: solid; border-width: 0; -padding: 0; +padding: 1px; color: @dark_fg_color; } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1537794/+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 1537794] Re: Wrong padding for gtkCalender (Unity7, Xenial)
** Also affects: ubuntu-themes (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-mate-artwork (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ubuntu-mate-artwork (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/1537794 Title: Wrong padding for gtkCalender (Unity7, Xenial) Status in ubuntu-mate-artwork package in Ubuntu: Fix Committed Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-mate-artwork source package in Xenial: Fix Released Status in ubuntu-themes source package in Xenial: New Bug description: After recent update, gtkCalender using 0px padding on top-bottom which makes it looks ugly. A mere 1px padding could solve the issue. See the screenshot for comparison: http://i.imgur.com/rFciw8h.png Patch (for Ambiance): Index: ubuntu-themes-14.04+16.04.20160120/Ambiance/gtk-3.0/gtk-widgets.css === --- ubuntu-themes-14.04+16.04.20160120.orig/Ambiance/gtk-3.0/gtk-widgets.css +++ ubuntu-themes-14.04+16.04.20160120/Ambiance/gtk-3.0/gtk-widgets.css @@ -806,7 +806,7 @@ GtkComboBox .menu .menuitem *:insensitiv border-radius: 0; border-style: solid; border-width: 0; -padding: 0; +padding: 1px; color: @dark_fg_color; } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1537794/+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 1512002] Re: Annoying dialog "Authentication is required to change your own user data"
This bug was fixed in the package accountsservice - 0.6.40-2ubuntu11 --- accountsservice (0.6.40-2ubuntu11) xenial; urgency=medium * debian/patches/change-own-data-inactive.patch: - updated to use allow_any=yes to avoid displaying unndeed dialog for remote sessions as well, thanks Alkis Georgopoulos (lp: #1512002) -- Sebastien BacherFri, 29 Apr 2016 16:15:39 +0200 ** Changed in: accountsservice (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/1512002 Title: Annoying dialog "Authentication is required to change your own user data" Status in accountsservice: Confirmed Status in accountsservice package in Ubuntu: Fix Released Status in indicator-messages package in Ubuntu: Invalid Status in policykit-1-gnome package in Ubuntu: Invalid Status in accountsservice source package in Xenial: Fix Released Bug description: * Impact Sometimes useless "Authentication is required to change your own user data" prompts are displayed * Test case $ ssh -X localhost $ /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 & $ dbus-send --system --print-reply=literal --dest=org.freedesktop.Accounts /org/freedesktop/Accounts/User1001 org.freedesktop.Accounts.User.SetXHasMessages boolean:true that shouldn't trigger a prompt * Regression potential it allows the change to be done without prompting in more cases, shouldn't have an impact on cases which were already working -- Every few days a dialog pops up saying "Authentication is required to change your own user data" with an entry field for a password. If I type my user's password the dialog will reappear with an empty entry field. If I click on the cross to close the window many times it will be gone, but reappear a few days later. I don't know what this window is for and it makes no difference whether I close it or leave it. I don't use the gnome keyring. This started with Ubuntu 15.04 or maybe with an earlier release, and is still there in Ubuntu 15.10, also on machines I did a fresh install. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1512002/+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 1576726] Re: [SRU]network-manager
This bug was fixed in the package network-manager-applet - 1.2.0-0ubuntu0.16.04.1 --- network-manager-applet (1.2.0-0ubuntu0.16.04.1) xenial; urgency=medium * Rebase to upstream stable release (lp: #1576726) -- Aron XuFri, 29 Apr 2016 22:53:10 +0800 ** Changed in: network-manager-applet (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/1576726 Title: [SRU]network-manager Status in network-manager package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in network-manager-openvpn package in Ubuntu: New Status in network-manager-ssh package in Ubuntu: New Status in network-manager-strongswan package in Ubuntu: New Status in network-manager-vpnc package in Ubuntu: New Status in network-manager source package in Xenial: Fix Committed Status in network-manager-applet source package in Xenial: Fix Released Status in network-manager-openconnect source package in Xenial: New Status in network-manager-openvpn source package in Xenial: New Status in network-manager-ssh source package in Xenial: New Status in network-manager-strongswan source package in Xenial: New Status in network-manager-vpnc source package in Xenial: New Bug description: [Impact] Xenial was released with upstream beta2 version of network-manager to keep in time for the release schedule, and upstream stable release has been made so it's time to update to it. [Testcase] After upgrading the package, user should still be able to connect to networks like Ethernet, Wi-Fi and VPNs. [Regression Potential] Potential of causing regression is relatively small because there is not big changes made during beta2 -> stable process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576726/+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 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...
This doesn't really depend on any extra steps -- I've just uploaded grub2 and grub2-signed to xenial-proposed queue, so as soon as it's reviewed by a member of the SRU team it will be available in proposed. >From there, we'll need people to test this carefully to make sure nothing is broken and that it's fulfilling its intended purposed (ie. fixing the issue), after that we'll be able to make it available to the general public in -updates. ** Also affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: grub2-signed (Ubuntu) Status: New => Fix Released ** Changed in: grub2-signed (Ubuntu Xenial) Status: New => In Progress ** Changed in: grub2-signed (Ubuntu Xenial) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: grub2-signed (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: grub2-signed (Ubuntu) Importance: Undecided => Medium ** Changed in: zfs-linux (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/1527727 Title: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/... Status in grub: Unknown Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in grub2 source package in Xenial: In Progress Status in grub2-signed source package in Xenial: In Progress Status in zfs-linux source package in Xenial: New Bug description: [Impact] Installs over ZFS where a ZFS disk is expected to be used as a root device. [Test case] - Run update-grub on a system with a ZFS root filesystem. [Regression Potential] Installs relying on the current broken behavior to avoid listing other operating systems in grub menu may find that new entries are added. --- update-grub runs /usr/sbin/grub-probe Without libzfslinux support compiled in, /usr/sbin/grub-probe runs ["zpool", "status", poolname] to find out ZFS info. zpool responds with device names as used at (I think!) pool creation time. Often, this is /dev/disk/by-id/... names, without the path. grub-probe then parses the output, and takes the names of devices, and if they do not start with a "/", it prepends "/dev/". It then tests the existence of the path name of the device. it fails. grub-probe then returns something like /usr/sbin/grub-probe: error: failed to get canonical path of `/dev /ata-ST31000333AS_-part1'. The actual path is of course /dev/disk/by- id/ST31000333AS_-part1 It can prepend smarter than "/dev" or it can understand ZFS natively, to fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1527727/+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 1490347] Re: [Regresision] 16:04 + 15:10 - Cannot pair with devices using (Legacy) PIN codes
** Also affects: bluez (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/1490347 Title: [Regresision] 16:04 + 15:10 - Cannot pair with devices using (Legacy) PIN codes Status in Bluez Utilities: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in bluez package in Ubuntu: Triaged Status in bluez source package in Wily: Triaged Status in bluez source package in Xenial: New Bug description: Bluez 5.3 does not have support for pairing with devices (such as keyboards) that use a PIN code for pairing. A mouse pairs correctly. From my research it seems as if the ChromeOS project developed patches to fix this and they are supposed to have been included in Bluez 5.4 (that statement dated April 2013) but I've not yet identified them. "The agent's implementation in bt_console/bluetoothctl upstream is incomplete, missing some functions like DisplayPincode." https://code.google.com/p/chromium/issues/detail?id=222661 Along with the loss of Headset profiles meaning VoIP applications can no longer use HSP/HFP profiles (requiring functionality yet to land in Ofono) this cripples the use of Bluetooth for much else than A2DP or mouse input. Attempting to pair with, for example, an Apple Wireless Keyboard that pairs and works correctly with 14.04 LTS, fails totally on 15.10. The mouse shown below is already paired, connected, and working. $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# scan on Discovery started [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48 [bluetooth]# pair 00:0A:95:4B:BD:C2 Attempting to pair with 00:0A:95:4B:BD:C2 >>> at this point nothing is happening >>> so I press Enter on the keyboard and... [agent] PIN code: 791166 >>> I type 791166 Enter and ... [agent] PIN code: 237744 >>> I type 237744 Enter and... [agent] PIN code: 358866 >>> I type 358866 Enter and... Request PIN code [agent] Enter PIN code: 1234 >>> I type 1234 Enter on the keyboard and 1234 at the prompt... Failed to pair: org.bluez.Error.AuthenticationFailed This cycle repeats in various permuations. Sometimes the final "Request PIN code" does not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1490347/+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 1578007] Re: apt in yakkety no longer creates partial
This is somewhat expected. The code to setup partial was deprecated in APT, we only set the Log in python-apt anymore. I think I need to provide a binding for GetLock(), which is now supposed to create the partial directory. ** Package changed: apt (Ubuntu) => python-apt (Ubuntu) ** Changed in: python-apt (Ubuntu) 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/1578007 Title: apt in yakkety no longer creates partial Status in Snapcraft: In Progress Status in python-apt package in Ubuntu: Confirmed Status in snapcraft package in Ubuntu: Fix Released Status in snapcraft source package in Xenial: New Bug description: This now fails: http://paste.ubuntu.com/16208927/ With an error that looks like http://paste.ubuntu.com/16208917/ If 'partial' is created in `downloaddir` then it works again To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1578007/+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 1481737] Proposed package removed from archive
The version of haproxy in the proposed pocket of Vivid that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. ** Changed in: haproxy (Ubuntu Vivid) Status: Fix Committed => 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/1481737 Title: HAProxy init script does not work correctly with nbproc configuration option Status in haproxy package in Ubuntu: Fix Released Status in haproxy source package in Trusty: Fix Released Status in haproxy source package in Vivid: Won't Fix Status in haproxy source package in Wily: Fix Released Status in haproxy source package in Xenial: Fix Released Bug description: [SRU justification] The sysVinit script does not completely stop processes when nbproc > 1 [Impact] Stopping haproxy without this fix leaves all but one process running [Fix] Use temporary pidfile in a loop containing one single PID as the --pid option is not available for start-stop-daemon. [Test Case] Set nbproc > 4 in /etc/haproxy/haproxy.cfg resart haproxy & verify that there is more than one haproxy process Run : $ ps aux | grep haproxy | grep -v grep | wc -l 4 $ service haproxy stop $ ps aux | grep haproxy | grep -v grep | wc -l Without the patch, the result of the last command will be 3. With the fix, it will be 0 [Regression] The regression risk is in the use of a temporary file instead of the start-stop-daemon option. It has been tested with TMPDIR="/tmp/My Dir" to check for spaces in directory names. [Original description of the problem] In case you have more than one process enabled in the haproxy config, the init script fails to stop all of those processes. So to clarify you need to have this in your haproxy.cfg: """ ... global maxconn 32000 ulimit-n65536 userhaproxy group haproxy nbproc 2 ... """ the problem is more visible if you set the nbproc to higher number. service haproxy stop --> will only stop on of the haproxy processes. The problem is so that start-stop-daemon can't handle pid files with multiple lines. Only stopping the first one. HAProxy does write all the pids started by itself into the pid file, so the problem is not in HAProxy, but in the start-stop-daemon or more likely in the init scrip of haproxy. One solution or workaround is to remove pidfile option of start-stop-daemon in the init script, than it wil work as killall and will stop the haproxy processes properly. To proof you can try this sequence: service haproxy start #if its not running ps ax | grep haproxy | grep -v grep | wc -l #this should report 2 service haproxy restart ps ax | grep haproxy | grep -v grep | wc -l #this will report 3 The workaround as a diff: root@ubi1:/opt# diff /etc/init.d/haproxy /etc/init.d/haproxy.orig 62c62 < --retry 5 --exec $HAPROXY || ret=$? --- > --retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$? extra infos: root@ubi1:/opt# lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 root@ubi1:/opt# apt-cache policy haproxy haproxy: Installed: 1.4.24-2ubuntu0.2 Candidate: 1.4.24-2ubuntu0.2 Version table: 1.5.3-1~ubuntu14.04.1 0 100 http://us.archive.ubuntu.com/ubuntu/ trusty-backports/main amd64 Packages *** 1.4.24-2ubuntu0.2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.4.24-2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+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 1581016] Re: New upstream microreleases 9.1.22, 9.3.13, 9.4.8, 9.5.3
postgresql-9.5 9.5.3-1 got uploaded to sid and will autosync to yakkety by tomorrow. ** No longer affects: postgresql-9.4 (Ubuntu Yakkety) ** No longer affects: postgresql-9.4 (Ubuntu Xenial) ** No longer affects: postgresql-9.4 (Ubuntu Precise) ** No longer affects: postgresql-9.4 (Ubuntu Trusty) ** Changed in: postgresql-9.5 (Ubuntu Yakkety) Status: New => Fix Committed ** Changed in: postgresql-9.4 (Ubuntu) Status: New => Invalid ** No longer affects: postgresql-9.1 (Ubuntu Yakkety) ** No longer affects: postgresql-9.1 (Ubuntu Wily) ** No longer affects: postgresql-9.1 (Ubuntu Xenial) ** Changed in: postgresql-9.1 (Ubuntu) Status: New => Invalid ** No longer affects: postgresql-9.3 (Ubuntu Yakkety) ** No longer affects: postgresql-9.3 (Ubuntu Xenial) ** No longer affects: postgresql-9.3 (Ubuntu Wily) ** No longer affects: postgresql-9.3 (Ubuntu Precise) ** Changed in: postgresql-9.3 (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/1581016 Title: New upstream microreleases 9.1.22, 9.3.13, 9.4.8, 9.5.3 Status in postgresql-9.1 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.4 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Fix Committed Status in postgresql-9.1 source package in Precise: New Status in postgresql-9.1 source package in Trusty: New Status in postgresql-9.3 source package in Trusty: New Status in postgresql-9.4 source package in Wily: New Status in postgresql-9.5 source package in Xenial: New Status in postgresql-9.5 source package in Yakkety: Fix Committed Bug description: Today, PostgreSQL will push new upstream microreleases which should go into stables as per the usual MRE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1581016/+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 1572607] Re: netcfg/disable_autoconfig=true still prompts for "Auto-configure networking?"
** Changed in: ubuntu-z-systems 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/1572607 Title: netcfg/disable_autoconfig=true still prompts for "Auto-configure networking?" Status in Ubuntu on IBM z Systems: Fix Released Status in debian-installer package in Ubuntu: Triaged Status in netcfg package in Ubuntu: Fix Released Status in debian-installer source package in Xenial: Triaged Status in netcfg source package in Xenial: Triaged Status in debian-installer source package in Yakkety: Triaged Status in netcfg source package in Yakkety: Fix Released Bug description: == Comment: - Ofer Baruch - 2016-04-20 05:28:06 == I am trying to install Ubuntu using a parm file so i won't get any prompts until SSH is available to connect to the guest. the "Auto-configure networking?" prompt keeps popping although i have specifically asked to turn it off. this used to work fine for me a week ago and i didn't even had the netcfg/disable_autoconfig=true in my parm file. now that i got the prompt (i assumed you guys fixed something) i added the netcfg/disable_autoconfig=true parameter but i still get the prompt. i am attaching the console output. This will affect affect IBM Wave functionality... IBM Wave allows the user to install Ubuntu without any need to access z/VM (Wave will do everything for you). when SSH is available the user can continue the installation. as we get the prompt in the middle of the installation the user can't continue the install as SSH is not yet available and he does not have access to the z/VM console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1572607/+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 1572607] Re: netcfg/disable_autoconfig=true still prompts for "Auto-configure networking?"
This bug was fixed in the package netcfg - 1.135ubuntu5 --- netcfg (1.135ubuntu5) yakkety; urgency=medium * When DHCP is disabled via preseed, do not ask the DHCP question on s390x by propagating the seen flags from preseed-only keys to the interactive question. This is a side-effect / regression from 1.135ubuntu3. LP: #1572607 -- Dimitri John LedkovWed, 11 May 2016 11:44:18 +0100 ** Changed in: netcfg (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/1572607 Title: netcfg/disable_autoconfig=true still prompts for "Auto-configure networking?" Status in Ubuntu on IBM z Systems: In Progress Status in debian-installer package in Ubuntu: Triaged Status in netcfg package in Ubuntu: Fix Released Status in debian-installer source package in Xenial: Triaged Status in netcfg source package in Xenial: Triaged Status in debian-installer source package in Yakkety: Triaged Status in netcfg source package in Yakkety: Fix Released Bug description: == Comment: - Ofer Baruch - 2016-04-20 05:28:06 == I am trying to install Ubuntu using a parm file so i won't get any prompts until SSH is available to connect to the guest. the "Auto-configure networking?" prompt keeps popping although i have specifically asked to turn it off. this used to work fine for me a week ago and i didn't even had the netcfg/disable_autoconfig=true in my parm file. now that i got the prompt (i assumed you guys fixed something) i added the netcfg/disable_autoconfig=true parameter but i still get the prompt. i am attaching the console output. This will affect affect IBM Wave functionality... IBM Wave allows the user to install Ubuntu without any need to access z/VM (Wave will do everything for you). when SSH is available the user can continue the installation. as we get the prompt in the middle of the installation the user can't continue the install as SSH is not yet available and he does not have access to the z/VM console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1572607/+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 1562733] Re: apt signature requierements prevent updates from some repositories
** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: appstream (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/1562733 Title: apt signature requierements prevent updates from some repositories Status in appstream package in Ubuntu: Triaged Status in apt package in Ubuntu: In Progress Status in appstream source package in Xenial: New Status in apt source package in Xenial: New Bug description: Since xenial updated the requirements for the strength of PGP signatures of packages, packages from some repositories are no longer updated. Apt-get update reports these errors: E: Failed to fetch http://[...]/Release No Hash entry in Release file /var/lib/apt/lists/partial/[...] which is considered strong enough for security purposes E: Some index files failed to download. They have been ignored, or old ones used instead. While the motivation for the change is valid, the result is a potential security problem, as the new versions of the packages that may fix recently discovered vulnerabilities are not automatically installed. One less important but unfortunate effect is a scary message that is displayed to the user, without clear explanation that the problem needs to be addressed by the repository owner. Related: Bug #1558331 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1562733/+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 1571174] Re: package squid3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Changed in: dpkg (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/1571174 Title: package squid3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in dpkg package in Ubuntu: Invalid Status in squid3 package in Ubuntu: Invalid Status in dpkg source package in Xenial: New Status in squid3 source package in Xenial: In Progress Bug description: During an upgrade from 15.10 to 16.04, upgrading squid3 erred out... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: squid3 3.3.8-1ubuntu16.2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sat Apr 16 05:33:51 2016 DuplicateSignature: package:squid3:3.3.8-1ubuntu16.2:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-12-07 (131 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: squid3 Title: package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-16 (0 days ago) modified.conffile..etc.apparmor.d.usr.sbin.squid3: [deleted] modified.conffile..etc.init.d.squid3: [deleted] modified.conffile..etc.init.squid3.conf: [deleted] modified.conffile..etc.logrotate.d.squid3: [deleted] modified.conffile..etc.resolvconf.update.libc.d.squid3: [deleted] modified.conffile..etc.squid3.errorpage.css: [deleted] modified.conffile..etc.squid3.msntauth.conf: [deleted] modified.conffile..etc.squid3.squid.conf: [deleted] modified.conffile..etc.ufw.applications.d.squid3: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1571174/+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 1579036] Re: add dep8 tests for the scripts/check.sh SPL/SPLAT tests
Hello Colin, or anyone else affected, Accepted spl-linux into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/spl- linux/0.6.5.6-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: spl-linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: spl-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/1579036 Title: add dep8 tests for the scripts/check.sh SPL/SPLAT tests Status in spl-linux package in Ubuntu: In Progress Status in spl-linux source package in Xenial: Fix Committed Bug description: [SRU Justification][XENIAL] Add dep8 SPL/SPLAT regression tests from the spl source to sanity check that the SPL driver module is behaving sanely. This SRU is to fix issues found in the MIR review, https://bugs.launchpad.net/ubuntu/+source/spl- linux/+bug/1569294/comments/2 [FIX] Modified version of the scripts/check.sh added to the dep8 test directory [TESTCASE] adt-run spl-linux_0.6.5.6-0ubuntu3.dsc --- qemu --ram-size 4096 adt-xenial-amd64-cloud.img ..with the tests we now get the spl splat checks running by adt: Loading splat -- Running SPLAT Tests -- kmem:kmem_alloc Pass kmem:kmem_zalloc Pass kmem:vmem_alloc Pass kmem:vmem_zalloc Pass kmem:slab_small Pass kmem:slab_large Pass kmem:slab_align Pass kmem:slab_reapPass kmem:slab_age Pass kmem:slab_lockPass taskq:single Pass taskq:multiple Pass taskq:system Pass taskq:wait Pass taskq:frontPass taskq:recurse Pass taskq:contention Pass taskq:delayPass taskq:cancel Pass taskq:dynamic Pass krng:freq Pass mutex:tryenter Pass mutex:race Pass mutex:ownedPass mutex:ownerPass condvar:signal1 Pass condvar:broadcast1 Pass condvar:signal2 Pass condvar:broadcast2 Pass condvar:timeout Pass thread:create Pass thread:exit Pass thread:tsd Pass rwlock:N-rd/1-wrPass rwlock:0-rd/N-wrPass rwlock:held Pass rwlock:tryenter Pass rwlock:rw_downgrade Pass rwlock:rw_tryupgradePass time:time1Pass time:time2Pass vnode:vn_open Pass vnode:vn_openatPass vnode:vn_rdwr Pass vnode:vn_getattr Pass vnode:vn_sync Pass kobj:open Pass kobj:size/readPass atomic:64-bit Pass list:create/destroy Pass list:ins/rm head Pass list:ins/rm tail Pass list:insert_after Pass list:insert_beforePass list:remove Pass list:active Pass
[Group.of.nepali.translators] [Bug 1580782] Re: linux: 4.4.0-23.40 -proposed tracker
** Changed in: linux (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/1580782 Title: linux: 4.4.0-23.40 -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-23.40 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-phase-changed:Thursday, 12. May 2016 00:28 UTC kernel-stable-phase:Packaging -- swm properties -- phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1580782/+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 1580952] Re: [SRU] Update apt/xenial to 1.2.12
** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apt (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/1580952 Title: [SRU] Update apt/xenial to 1.2.12 Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: New Bug description: Since the version in xenial, we released two more new bug fix releases upstream. We'd like to get this into xenial under the "New upstream microreleases" rule. [Impact] Most visible for xenial users: -> AppStream now updates even if some repositories failed to be fetched (see #1562733 for reference) -> Third-party repositories will no longer print "Unknown public key" type errors when a new key was added (and another key was successfully used to verify the repo). This happen(s/ed) on the Chrome repositories, for example, and leads users to manually receive keys from the key server which weakens their security. The rest are other bugfixes. Full changelogs: apt (1.2.11) unstable; urgency=medium [ David Kalnischkies ] * ensure transaction states are changed only once -> more sanity checks * stop handling items in doomed transactions. Thanks to Barr Detwix & Vincent Lefevre for log files (Closes: 817240) -> fixes a lot of "E: Unpatched file doesn't exist (anymore)!" that happen sometimes * do not require non-broken systems in 'upgrade' -> allows people to fix their broken system in upgrade * detect compressed status files on extension again -> regression from 1.1, single flag changed * recheck Pre-Depends satisfaction in SmartConfigure (LP: #1569099) -> already in xenial * fix Alt-Filename handling of file method -> off-by-one error when removing file extensions to get uncompressed filename * allow uncompressed files to be empty in store again -> this caused failures when fetching empty files * silently skip acquire of empty index files -> clean up of the above * ensure outdated files are dropped without lists-cleanup -> ensures proper cleanup [ Kelemen Gábor ] * Hungarian program translation update (Closes: 820638) -- Julian Andres KlodeMon, 25 Apr 2016 15:23:49 +0200 apt (1.2.12) unstable; urgency=medium [ Patrick Cable ] * refactored no_proxy code to work regardless of where https proxy is set -> no_proxy should really work for all ways to set an https proxy (actually LP: #1575877) [ James McCoy ] * deb822: Restore support for -{Add,Remove} -> Adds - in front of Add and Remove strings... [ David Kalnischkies ] * don't show NO_PUBKEY warning if repo is signed by another key (Closes: 618445) -> this helps the DSA->RSA key transitions, at it gets rid of the unkown public key warnings on the Chrome repository * allow redirection for items without a space in the desc again -> small bug fix * don't sent uninstallable rc-only versions via EDSP -> Fixes EDSP/CUDF solvers to not try to install package versions in config-file state * respect user pinning in M-A:same version (un)screwing -> used the wrong function get a candidate version [ Julian Andres Klode ] * update: Run Post-Invoke-Success if not all sources failed -> This fixes the problem with AppStream not being updated because a mirror failed (see #1562733) * debian/gbp.conf: Set debian-branch to 1.2.y -> Build infrastructure [ Frans Spiesschaert ] * Dutch program translation update (Closes: 823976) -- Julian Andres Klode Wed, 11 May 2016 10:56:53 +0200 [Regression Potential] APT has a very thorough regression test suite and the releases have passed our upstream CI system on travis, and autopkgtests on Debian unstable and Ubuntu xenial; so there's no huge regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1580952/+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 1570012] Re: kpatch-build build log file needs to be smaller
This bug was fixed in the package kpatch - 0.3.2-1ubuntu5 --- kpatch (0.3.2-1ubuntu5) yakkety; urgency=medium * Use debian/rules to build the kernel (LP: #1578661) * During kernel builds, generate output when not in debug mode to prevent builders timing out due to the build appearing hung (LP: #1570012) -- Benjamin M RomerWed, 04 May 2016 12:49:33 -0400 ** Changed in: kpatch (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/1570012 Title: kpatch-build build log file needs to be smaller Status in kpatch package in Ubuntu: Fix Released Status in kpatch source package in Xenial: Fix Committed Bug description: The .kpatch/build.log file is enormous because it is carrying around the entire build log for two kernel builds, when realistically it only needs to keep the last build performed. There's no reason to hang on to the initial kernel build after it is complete, as a) it should normally complete without error, and b) if there is a problem, the script will bail out there anyway. The script needs the second build output for checking for unresolved symbols, but since this build is only touching files modified by the patch, it should be much smaller. Running the build in non-debug mode cuts down on noise as well, though some output is still necessary to avoid timeouts. Adding a function to output dots during the kernel builds will take care of timeouts without cluttering the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kpatch/+bug/1570012/+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 1578661] Re: make kpatch-build kernel building match ubuntu build
This bug was fixed in the package kpatch - 0.3.2-1ubuntu5 --- kpatch (0.3.2-1ubuntu5) yakkety; urgency=medium * Use debian/rules to build the kernel (LP: #1578661) * During kernel builds, generate output when not in debug mode to prevent builders timing out due to the build appearing hung (LP: #1570012) -- Benjamin M RomerWed, 04 May 2016 12:49:33 -0400 ** Changed in: kpatch (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/1578661 Title: make kpatch-build kernel building match ubuntu build Status in kpatch package in Ubuntu: Fix Released Status in kpatch source package in Xenial: Fix Committed Bug description: [Impact] Currently kpatch-build uses 'make' to build the kernel; however when we build the ubuntu kernel we use debian/rules to do the build. By using debian/rules we can match all build quirks. [Test Case] Use kpatch-build to build a patch. [Regression Potential] We are using a different mechanism to build the kernel, however the underlying mechanisms should be similar. Testing is required to ensure this doesn't change the behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kpatch/+bug/1578661/+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 1574789] Re: xorg.conf.d/90-zap.conf destroys xorg keyboard settings
Hello Alkis, or anyone else affected, Accepted ubuntu-mate-settings into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-mate-settings/16.04.5.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: ubuntu-mate-settings (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: With Ubuntu MATE 16.04, I'm unable to switch between keyboard layouts properly. My locale is LANG=el_GR.UTF-8 and LANGUAGE=el. The Ubuntu MATE installer correctly made those settings for me: - $ grep -i xkboptions /etc/default/keyboard + $ grep -i xkboptions /etc/default/keyboard XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" I.e. I should be able to switch between the US and the Greek keyboard layout using Alt+Shift, and the keyboard scroll led indicates the active language. Unfortunately ubuntu-mate-default-settings overrides the correct settings, making me unable to switch languages via Alt+Shift: $ grep -i xkboptions /usr/share/X11/xorg.conf.d/90-zap.conf - Option "XKbOptions" "terminate:ctrl_alt_bksp,grp" + Option "XKbOptions" "terminate:ctrl_alt_bksp,grp" So, please make sure that 90-zap.conf *adds* "terminate:ctrl_alt_bksp,grp" to the current xkboptions, instead of *replacing* them. If it's unable to add instead of replacing settings, then please completely remove 90-zap.conf. + + [Impact] + + * Ubuntu MATE included the ability to kill the X server using + Ctrl+Alt+BkSpc over a year ago while the initial Compiz integration was + being added. That facility is a hangover and no longer required. + + * This updated version of Ubuntu MATE Settings removes + usr/share/X11/xorg.conf.d/90-zap.conf and restores the ability to switch + keyboard layouts using Alt+Shift. + + [Test Cases] + + * Install Ubuntu MATE 16.04 using Greek language and locale and US + language. You will be unable to switch between the US and the Greek + keyboard layout using Alt+Shift. + + * Once Ubuntu MATE Settings 16.04.5.1 is installed it will be possible + to switch between keyboard layouts using Alt+Shift. + + [Regression Potential] + + * The ability to kill the X session using Ctrl+Alt+BkSpc will be lost. + But none of the other Ubuntu flavours support this functionality and + it's removal restore the default Xorg behaviour. ** Changed in: ubuntu-mate-settings (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- 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/1574789 Title: xorg.conf.d/90-zap.conf destroys xorg keyboard settings Status in ubuntu-mate: Fix Committed Status in ubuntu-mate-settings package in Ubuntu: Fix Committed Status in ubuntu-mate-settings source package in Xenial: Fix Committed Bug description: With Ubuntu MATE 16.04, I'm unable to switch between keyboard layouts properly. My locale is LANG=el_GR.UTF-8 and LANGUAGE=el. The Ubuntu MATE installer correctly made those settings for me: $ grep -i xkboptions /etc/default/keyboard XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" I.e. I should be able to switch between the US and the Greek keyboard layout using Alt+Shift, and the keyboard scroll led indicates the active language. Unfortunately ubuntu-mate-default-settings overrides the correct settings, making me unable to switch languages via Alt+Shift: $ grep -i xkboptions /usr/share/X11/xorg.conf.d/90-zap.conf Option "XKbOptions" "terminate:ctrl_alt_bksp,grp" So, please make sure that 90-zap.conf *adds* "terminate:ctrl_alt_bksp,grp" to the current xkboptions, instead of *replacing* them. If it's unable to add instead of replacing settings, then please completely remove 90-zap.conf. [Impact] * Ubuntu MATE included the ability to kill the X server using Ctrl+Alt+BkSpc over a year ago while the initial Compiz integration was being added. That facility is a hangover and no longer required. * This updated version of Ubuntu MATE Settings removes