[Group.of.nepali.translators] [Bug 1508329] Re: CVE-2015-7799
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Invalid ** Changed in: linux (Ubuntu Yakkety) Status: Fix Committed => 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/1508329 Title: CVE-2015-7799 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty 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-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Committed 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-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New 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-mvl-dove 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-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New 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: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove 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: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Sta
[Group.of.nepali.translators] [Bug 1547400] Re: CVE-2016-2853
** Summary changed: - aufs fails to handle sanitize xattrs in workdir, copies SUID binaries from no-suid fuse mounts + CVE-2016-2853 ** Project changed: linux => ubuntu-translations ** Changed in: ubuntu-translations Status: Confirmed => New ** Changed in: ubuntu-translations Remote watch: Email to sfjro@users # => None ** No longer affects: ubuntu-translations ** Bug watch removed: Email to sfjro@users # mailto:sf...@users.sourceforge.net ** CVE removed: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-2854 -- 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/1547400 Title: CVE-2016-2853 Status in linux package in Ubuntu: Confirmed 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: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New 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: New 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: New Status in linux source package in Trusty: New 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: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New 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 Wily: New 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 linux-mako source package in Wily: New Status in linux-manta source package in Wily: New Status in linux-raspi2 source package in Wily: New Status in linux-snapdragon source package in Wily: Invalid Status in linux-ti-omap4 source package in Wily: Invalid Status in linux source package in Xenial: Confirmed Status in linux-armadaxp source package in Xenial: Invalid Status in linux-flo source package in Xenial: New Status in linux-goldfish source package in Xenial: New Status in linux-lts-quantal source package in Xenial: Invalid Status in linux-lts-raring sour
[Group.of.nepali.translators] [Bug 1580361] Re: CVE-2015-0569
** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux (Ubuntu Wily) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Yakkety) 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/1580361 Title: CVE-2015-0569 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: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: New 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: New 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: New Status in linux source package in Trusty: Invalid 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: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New 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: Invalid 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: Invalid 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 St
[Group.of.nepali.translators] [Bug 1441303] Re: CVE-2010-5321
** Changed in: linux-lts-xenial (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: linux-lts-xenial (Ubuntu Vivid) 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/1441303 Title: CVE-2010-5321 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: New Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty 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: New Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Won't Fix Status in linux-lts-backport-natty source package in Lucid: Won't Fix Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: New 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-mvl-dove source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New 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: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Utopic: Won't Fix Status in linux-lts-backport-natty source package in Utopic: Won't Fix Status in linux source package in Vivid: New Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-flo source package in Vivid: New Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-goldfish source package in Vivid: New Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in linux-lts-raring source package in Vivid: Invalid Status in linux-lts-saucy source package in Vivid: Invalid Sta
[Group.of.nepali.translators] [Bug 1575611] Re: CVE-2008-2544
** Changed in: linux (Ubuntu Precise) Status: New => Invalid ** Changed in: linux (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux (Ubuntu Wily) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Yakkety) 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/1575611 Title: CVE-2008-2544 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: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: New 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: New 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: New Status in linux source package in Trusty: Invalid 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: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New 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: Invalid 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: Invalid 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 St
[Group.of.nepali.translators] [Bug 1614215] Re: "md5sums differ" message seems to indicate an install problem
** Also affects: apparmor (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Yakkety) Importance: Low Assignee: Tyler Hicks (tyhicks) Status: In Progress ** Changed in: apparmor (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: apparmor (Ubuntu Xenial) Status: New => In Progress ** Changed in: apparmor (Ubuntu Xenial) Assignee: (unassigned) => Tyler Hicks (tyhicks) ** Description changed: + [Impact] + Confusing output from a diff command executed during the apparmor update process leaves users concerned about the state of their system. + + [Test Case] + 1. Make sure that apparmor 2.10.95-0ubuntu2 from the -release pocket is installed + + 2. Update to the apparmor package in -proposed + + 3. Look at the output during the update process to verify that the + following message is *not* printed: + + Files /var/lib/dpkg/info/apparmor.md5sums and + /var/lib/apparmor/profiles/.apparmor.md5sums differ + + [Regression Potential] + Considered to be extremely low. The change is a one-liner that pipes the stdout of diff command to /dev/null (the -q option of diff is not sufficient). + + [Original description] + Upon applying the latest Ubuntu routine-update, I observed these messages: Setting up apparmor (2.10.95-0ubuntu2.2) ... Installing new version of config file /etc/apparmor.d/abstractions/dbus-session-strict ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Skipping profile in /etc/apparmor.d/disable: usr.sbin.apache2 Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Files /var/lib/dpkg/info/apparmor.md5sums and /var/lib/apparmor/profiles/.apparmor.md5sums differ "The reason why I am filing a bug report" is the LAST line. I presume that if md5sums do not agree, something was probably done improperly in preparing this particular software-update blast. However, in-passing, I would also point out line #3, about "start and stop actions no longer supported." That seems to me to be something (of much less importance, obviously) that might have been overlooked. (I've seen =that= message for some time now.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Aug 17 14:22:55 2016 InstallationDate: Installed on 2016-03-02 (168 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: apparmor Syslog: - Aug 10 10:36:07 IntersignVM dbus[1638]: [system] AppArmor D-Bus mediation is enabled - Aug 11 13:10:08 IntersignVM dbus[1655]: [system] AppArmor D-Bus mediation is enabled - Aug 16 08:40:24 IntersignVM dbus[1693]: [system] AppArmor D-Bus mediation is enabled - Aug 17 13:58:37 IntersignVM dbus[1657]: [system] AppArmor D-Bus mediation is enabled + Aug 10 10:36:07 IntersignVM dbus[1638]: [system] AppArmor D-Bus mediation is enabled + Aug 11 13:10:08 IntersignVM dbus[1655]: [system] AppArmor D-Bus mediation is enabled + Aug 16 08:40:24 IntersignVM dbus[1693]: [system] AppArmor D-Bus mediation is enabled + Aug 17 13:58:37 IntersignVM dbus[1657]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to xenial on 2016-05-11 (98 days ago) -- 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/1614215 Title: "md5sums differ" message seems to indicate an install problem Status in AppArmor: Invalid Status in Ubuntu GNOME: Invalid Status in apparmor package in Ubuntu: In Progress Status in apparmor source package in Xenial: In Progress Status in apparmor source package in Yakkety: In Progress Bug description: [Impact] Confusing output from a diff command executed during the apparmor update process leaves users concerned about the state of their system. [Test Case] 1. Make sure that apparmor 2.10.95-0ubuntu2 from the -release pocket is installed 2. Update to the apparmor package in -proposed 3. Look at the output during the update process to verify that the following message is *not* printed: Files /var/lib/dpkg/info/apparmor.md5sums and /var/lib/apparmor/profiles/.apparmor.md5sums differ [Regression Potential] Considered to be extremely low. The change is a one-liner that pipes the stdout of diff command to /dev/null (the -q option of diff is not sufficient). [Origi
[Group.of.nepali.translators] [Bug 1553503] Re: multi monitors - black flashes or black screen when the mouse cursor leaves a monitor
This patch came in via v4.4.18 stable. Marking fix released since this bug won't auto-close. ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu) 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/1553503 Title: multi monitors - black flashes or black screen when the mouse cursor leaves a monitor Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: When the mouse cursor leaves one of the screens, there is either : - no problem - the screen becomes black just below the position of the cursor and instantly comes back to normal. - the screen becomes entirely black with some random colored pixels flickering on the far left of the screen. I have to move the cursor to the black screen, otherwise it stays black. It happens on Ubuntu Gnome 16.04 Beta and Ubuntu Mate 16.04 Beta. I have tested with other distributions (Debian Jessie and Fedora) and everything is fine. Hardware : Intel Ironlake (Thinkpad X201) with an external monitor plugged in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CasperVersion: 1.367 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Mar 5 13:17:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) MachineType: LENOVO 3680KD3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET70WW (1.40 ) dmi.board.name: 3680KD3 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3680KD3:pvrThinkPadX201:rvnLENOVO:rn3680KD3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3680KD3 dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Sat Mar 5 13:03:55 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id2202 vendor BOE xserver.version: 2:1.17.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1553503/+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 1616813] Re: Please add support for alps touchpad.
Merged in v4.8 ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Ying-Chun Liu (paulliu) -- 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/1616813 Title: Please add support for alps touchpad. Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Bug description: Hi, We need to support alps touchpad. Please considering SRU. The following ko needs to be used: 1. hid-generic.ko 3. hid-alps.ko This driver is backported from mainline v4.8-rc3 to linux 4.4 in xenial. Yours, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1616813/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1612089] Re: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled
** No longer affects: cloud-archive/newton -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1612089 Title: Fix for CVE-2016-5403 causes crash on migration if memory stats are enabled Status in Ubuntu Cloud Archive: New Status in Ubuntu Cloud Archive icehouse series: Fix Committed Status in Ubuntu Cloud Archive kilo series: Fix Committed Status in Ubuntu Cloud Archive liberty series: Fix Committed Status in Ubuntu Cloud Archive mitaka series: New Status in qemu package in Ubuntu: Fix Released Status in qemu-kvm source package in Precise: Fix Released Status in qemu source package in Trusty: Fix Released Status in qemu source package in Xenial: Fix Released Status in qemu source package in Yakkety: Fix Released Bug description: If memory statistics are enabled for the memory baloon device in libvirt like this: Then qemu exits with "qemu-system-x86_64: Virtqueue size exceeded" after the VM is migrated or when starting the VM again after a managedsave. This bug is present since 2.0.0+dfsg-2ubuntu1.26 and was not present in 2.0.0+dfsg-2ubuntu1.24. It's most probably caused by the Fix for CVE-2016-5403. Steps to reproduce: 1. Create a VM with libvirt which contains the above memory balloon device 2. Start the VM and let the Linux kernel boot (bug does not appear if the kernel is not yet booted, eg. while in the PXE boot phase) 3. Issue a managedsave 4. Start the VM again 5. The VM is restored and "crashes" right after it starts running again. 6. You can find the qemu output "qemu-system-x86_64: Virtqueue size exceeded" in the log at /var/log/libvirt/vmname.log ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-x86 2.0.0+dfsg-2ubuntu1.26 ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39 Uname: Linux 3.13.0-93-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Thu Aug 11 08:39:33 2016 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1612089/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1606277] Re: log-observe interface is broken in latest snap-confine
This was fixed 1.0.38-0ubuntu0.16.04.3 in xenial. ** Changed in: snap-confine (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/1606277 Title: log-observe interface is broken in latest snap-confine Status in Snappy Launcher: Fix Released Status in snap-confine package in Ubuntu: Fix Released Status in snap-confine source package in Xenial: Fix Released Status in snap-confine source package in Yakkety: Fix Released Bug description: The log-observe interface is broken due to how we handle bind mounts now. This can be seen with 'snappy-debug': $ sudo snap install snappy-debug $ sudo snap connect snappy-debug:log-observe ubuntu-core:log-observe $ sudo /snap/bin/snappy-debug.security scanlog kernel.printk_ratelimit = 0 Traceback (most recent call last): File "/snap/snappy-debug/22/bin/snappy-security-scanlog", line 580, in sys.exit(main()) File "/snap/snappy-debug/22/bin/snappy-security-scanlog", line 569, in main from_end=opt.only_new) File "/snap/snappy-debug/22/bin/snappy-security-scanlog", line 92, in __init__ self.scan_log(log_file, snap_name, follow, from_end) File "/snap/snappy-debug/22/bin/snappy-security-scanlog", line 157, in scan_log log = open_file_read(log_file) File "/snap/snappy-debug/22/bin/snappy-security-scanlog", line 71, in open_file_read orig = codecs.open(path, 'r', "UTF-8", errors="replace") File "/usr/lib/python3.5/codecs.py", line 895, in open file = builtins.open(filename, mode, buffering) FileNotFoundError: [Errno 2] No such file or directory: '/var/log/syslog' This is because /var/log/syslog is not available at runtime due to the bind mounts. This can be shown by installing hello-world, adjusting /var/lib/snapd/apparmor/profiles/snap.hello-world.sh to have "/**/ r," (to be able to read any directory), reloading the profile, then doing: $ hello-world.sh ... bash-4.3$ ls /var/log/ alternatives.log btmp dpkg.log fsck watchdog bootstrap.log dmesg faillog lastlog wtmp This may also be a problem with other interfaces, I haven't checked extensively, though it seems that /var/lib/extrausers (from the nameservice abstraction) won't work right, and (at least) ppp (/var/log/ppp) and timezone-control (/usr/share/zoneinfo) are also affected. WORKAROUND for snappy-debug: launch outside of the launcher: $ sudo SNAP=/snap/snappy-debug/current PATH=$PATH:/snap/snappy-debug/current/bin /snap/snappy-debug/current/bin/snappy-security scanlog To manage notifications about this bug go to: https://bugs.launchpad.net/snap-confine/+bug/1606277/+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 1612305] Re: linux: 4.4.0-36.55 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-36.55 /xenial-proposed-frozen.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing 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/1612305 Title: linux: 4.4.0-36.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released 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-36.55 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1582767] Re: apparmor permissions missing for winbind
Hi, just to note I'd consider this not important enough for an SRU given the fact that it is a very rare case and people can add the rule themselves if the need to. ** Changed in: ntp (Ubuntu Xenial) Status: New => 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/1582767 Title: apparmor permissions missing for winbind Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Xenial: Won't Fix Bug description: When using Winbind, ntpd needs to access the Winbind pipe: May 17 16:23:15 bo kernel: [ 27.598551] type=1400 audit(1463494995.048:18): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/samba/winbindd/pipe" pid=1517 comm="ntpd" requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0 Would there be any reason not to allow this ? I added the following line to /etc/apparmor/init/network-interface-security/usr.sbin.ntpd: /run/samba/winbindd/pipe rw, Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1582767/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1579246] Re: [SRU]handle 802.1x on ethernet properly
** Changed in: network-manager-applet (Ubuntu Xenial) Importance: Undecided => High ** Project changed: network-manager => network-manager-applet -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1579246 Title: [SRU]handle 802.1x on ethernet properly Status in Network Manager Applet: Fix Released Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Xenial: Fix Committed Bug description: [Impact] nm-applet does not save passwords for 802.1X on Ethernet connections, thus users will need to input password every time when connecting to it. [Test case] Connect to an 802.1X enabled Ethernet port, choose save password when authentication. Disconnect the network and reconnect, users should not be prompted again for credentials. [Regression potential] The fix is a one liner that only deals with secrets handling of certain time, potential of regression is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1579246/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working
** Changed in: isc-dhcp (Ubuntu Wily) Status: Fix Committed => Won't Fix ** Tags removed: verification-needed-wily -- 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/1529815 Title: InfiniBand DHCP flow with PRA and DHCP relay not working Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Fix Committed Status in isc-dhcp source package in Wily: Won't Fix Status in isc-dhcp source package in Xenial: Fix Released Bug description: [Impact] * Infiniband users relying on DHCP can't use DHCP relay. [Test Case] * Comment #13 * Mellanox has tested themselves. * Clear way of knowing if fix worked (tcpdump). [Regression Potential] * Only related to Infiniband. * Infiniband support could stop working (unlikely, already tested). [Other Info] DHCP client is sending discover with Unicast type request for the offer, in this configuration of IB to ETH through a relay we need the type to be broadcast. The issue is that when using dhclient from the client on Ubuntu (and only on Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in unicast instead of broadcast. It seems there is no way to correct this from the client side using dhclient configuration file. this issue exist even when we use always-broadcast statement in configuration file. in other vendors we see that discover request type is broadcast. attached pcap files from working (other vendor) and not working (Ubuntu) clients. DHCP CLIENT (IPoIB) Ubuntu 14.04 kernel 3.13.0-74 Mellanox OFED 3.1-1.0.3 or inbox driver isc-dhcp-client 4.2.4-7ubuntu12.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+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 1609733] Re: glance-common package doesn't contains dependencies/files for using cinder store
https://review.openstack.org/#/c/348336/ ** Also affects: glance (Juju Charms Collection) Importance: Undecided Status: New ** Changed in: glance (Juju Charms Collection) Status: New => Fix Committed ** Changed in: glance (Juju Charms Collection) Milestone: None => 16.10 ** Changed in: glance (Juju Charms Collection) Assignee: (unassigned) => Andrey Pavlov (apavlov-e) ** Changed in: glance (Juju Charms Collection) 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/1609733 Title: glance-common package doesn't contains dependencies/files for using cinder store Status in python-glance-store package in Ubuntu: Fix Released Status in python-glance-store source package in Xenial: Fix Committed Status in python-glance-store source package in Yakkety: Fix Released Status in glance package in Juju Charms Collection: Fix Committed Bug description: glance is being installed from debian packages can not be used with storing images in cinder. 1) python-glance-store package doesn't depend from 'python-cinderclient', 'oslo.rootwrap' and 'os-brick' I thing that is due to strange 'extra' dependencies definition in the pip package https://pypi.python.org/pypi/glance_store/0.15.0 information from the url: http://packages.ubuntu.com/xenial/python- glance-store 2) glance-common debian package doesn't contain files for rootwrap functionality - /etc/glance/rootwrap.conf /etc/sudoers.d/glance_sudoers and directory /etc/glance/rootwrap.d from the url: http://packages.ubuntu.com/xenial/all/glance- common/filelist for example in nova-common - http://packages.ubuntu.com/xenial/all/nova-common/filelist maybe glance-store should contain these files because it contains file /usr/bin/python2-glance-rootwrap 1) Ubuntu 14.04 with repositories where glance of version 12.0.0 is available (installed by Ubuntu Juju Chrams) 2) glance version is 12.0.0 3) I expect that all needed files/packages are installed and all that I need - is to change glance.conf and restart glance-api 4) I need to install packages, create files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-glance-store/+bug/1609733/+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 1615449] Re: Use upstream manpages instead of stub Debian-provided man page
This bug was fixed in the package p11-kit - 0.23.2-5 Sponsored for Jeremy Bicha (jbicha) --- p11-kit (0.23.2-5) unstable; urgency=medium * Build and ship upstream manpages. (Thanks, Julien Cristau) + Add b-d on gtk-doc-tools. + Pass --enable-doc to ./configure. + Drop minimal debian/p11-kit.1 manpage. Closes: #834992 -- Andreas Metzler Sun, 21 Aug 2016 16:03:45 +0200 ** Changed in: p11-kit (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/1615449 Title: Use upstream manpages instead of stub Debian-provided man page Status in p11-kit package in Ubuntu: Fix Released Status in p11-kit source package in Xenial: New Bug description: Impact == The Debian provided stub manpage is not very useful. Now that upstream includes manpages, we should build and ship those instead. This replaces p11-kit1. with the much more verbose and useful trust.1, pkcs11.conf.5 and p11-kit.8 Test Case Run man p11-kit, man trust and man pkcs11.conf Regression Potential For yakkety, please sync p11-kit 0.23.2-5. For xenial, I am including a debdiff to backport the changes from 0.23.2-4 and 0.23.2-5 with the exception of enabling all hardening flags since I think the SRU policy discourages making changes like that. 0.23.2-4 updates the package descriptions in debian/control. Please sync p11-kit 0.23.2-5 (main) from Debian unstable (main) Changelog entries since current yakkety version 0.23.2-4: p11-kit (0.23.2-5) unstable; urgency=medium * Build and ship upstream manpages. (Thanks, Julien Cristau) + Add b-d on gtk-doc-tools. + Pass --enable-doc to ./configure. + Drop minimal debian/p11-kit.1 manpage. Closes: #834992 -- Andreas Metzler Sun, 21 Aug 2016 16:03:45 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1615449/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1577049] Re: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04
This bug was fixed in the package accountsservice - 0.6.40-2ubuntu15 --- accountsservice (0.6.40-2ubuntu15) yakkety; urgency=medium [ Laurent Bigonville ] * Drop the -dbg package and rely on the automatically built -dbgsym one [ Jeremy Bicha ] * 0014-libsystemd.patch: - Backport patch to adapt to systemd 209, fixes missing "Switch User" functionality in GNOME Shell (LP: #1577049) * debian/control: - Bump minimum systemd for above patch - Drop build-dependencies only needed for obsolete pam-pin -- Jeremy Bicha Thu, 25 Aug 2016 21:15:10 -0400 ** Changed in: accountsservice (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/1577049 Title: Switch user feature has disappeared from GNOME Shell since upgrade from 15.10 to 16.04 Status in accountsservice: Unknown Status in Ubuntu GNOME: Fix Committed Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Xenial: In Progress Status in accountsservice package in Debian: Fix Released Bug description: Impact == Ubuntu 16.04's accountsservice was built without systemd support because systemd dropped libsystemd-login because that functionality was merged into libsystemd. At a minimum, this broke GNOME Shell's "Switch User" feature. Test Case = 1. From Ubuntu GNOME 16.04.1, install the updated accountsservice packages. 2. Add a user if necessary to ensure you have at least 2 user accounts configured. 3. Reload gnome-shell. You can do this with Alt+F2 and entering the lower case letter r. Or you can log out of all user accounts and log back in. 4. Click the system status area in the top right of GNOME Shell. 5. Click your user name. "Switch User" should appear in the list. Regression Potential None. The one-line change to accountsservice's configure check was made in Debian's accountsservice 0.6.40-3 a year ago(!). The patch is upstreamed and was included in accountsservice 0.6.42 released in June. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1577049/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp