[Group.of.nepali.translators] [Bug 1578497] Re: CVE-2016-4486

[Steve Beattie]

CVE-2016-4486

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-mako (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu 

[Group.of.nepali.translators] [Bug 1578496] Re: CVE-2016-4485

[Steve Beattie]

CVE-2016-4485

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-mako (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu 

[Group.of.nepali.translators] [Bug 1320539] Re: Dash search of applications is randomly disabled when online searchs have been turned off

[Alberto Salvia Novella]

** Changed in: unity (Ubuntu Xenial)
   Importance: Low => Medium

** Changed in: unity (Ubuntu)
   Importance: Low => Medium

** Changed in: hundredpapercuts
   Importance: Low => Medium

** No longer affects: unity

-- 
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/1320539

Title:
  Dash search of applications is randomly disabled when online searchs
  have been turned off

Status in One Hundred Papercuts:
  Triaged
Status in unity package in Ubuntu:
  Triaged
Status in unity source package in Xenial:
  Triaged

Bug description:
  
  HOW TO REPRODUCE
  

  1. In "Control panel / Security and privacy / Search", disable the online 
search.
  2. Use the dash for looking for some applications.

  **
  EXPECTED BEHAVIOUR
  **

  - The dash search to always show the applications.

  **
  REAL BEHAVIOUR
  **

  - Sometimes the search of applications turns off itself, what never
  happens if the online search is on.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat May 17 20:58:29 2014
  InstallationDate: Installed on 2013-05-21 (361 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-14 (33 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1320539/+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 1578493] Re: CVE-2016-4482

[Steve Beattie]

CVE-2016-4482

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-mako (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu 

[Group.of.nepali.translators] [Bug 1575555] Re: Chrome/Chromium use "Thin" as default font weight

[Bug Watch Updater]

** Changed in: fonts-noto-cjk (Debian)
   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/157

Title:
  Chrome/Chromium use "Thin" as default font weight

Status in fonts-noto-cjk package in Ubuntu:
  In Progress
Status in fonts-noto-cjk source package in Xenial:
  In Progress
Status in fonts-noto-cjk package in Debian:
  Fix Released

Bug description:
  [Impact]

  Chromium and Google Chrome use "Thin" as the default Noto Sans CJK
  font weight, which makes some Chinese and Japanese web pages difficult
  to read, and thus gives a bad user experience.

  The fonts-noto-cjk version in the PPA

  https://launchpad.net/~gunnarhj/+archive/ubuntu/fonts-noto-cjk

  installs 7 weight specific font files instead of a single "super"
  file. This works around the Chromium/Chrome issue.

  Note: It has already been fixed in Debian (version 1:1.004+repack2-1),
  so as regards yakkety I suppose that syncing instead of uploading from
  the PPA is a good idea.

  [Test Case]

  To reproduce the bug:

  * Install Chromium or Google Chrome.
  * Go to  and notice the very thin characters.
  * Install fonts-noto-cjk from the PPA and notice the difference.

  [Regression Potential]

  This is about another font packaging form, without any change in glyph
  coverage, so the the regression risk should be low.

  [Original description]

  The package seems to only "thin" variant of the font, which makes it
  very unreadable in applications such as Chrome (when it has to fall
  back on Chinese fonts on a mostly-English page). I had to remove the
  package and then manually download the font from Google website and
  install it to make the regular weight available

  Release: 16.04 LTS
  Package Version: 1.004+repack1-1
  Expected: All weights of the noto cjk font to be installed
  Happened: Only the "thin" weight of the font seems to be installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/157/+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 1273524] Re: LXDE guest session shows error message "no session for pid "

[Gunnar Hjalmarsson]

Fixed in lightdm 1.19.0-0ubuntu1

** Changed in: lightdm (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/1273524

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Triaged
Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lxsession package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Fix Committed
Status in lxsession source package in Xenial:
  New

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+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 1509829] Re: lightdm-guest-session profile is too strict to input Japanese text with fcitx-mozc

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.19.0-0ubuntu1

---
lightdm (1.19.0-0ubuntu1) yakkety; urgency=medium

  * New upstream release:
- Use /dev/tty0 instead of /dev/console for VT operations (LP: #1566073)
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix lxsession running in guest session
- Drop support for legacy XMir
- Fix g_spawn compiler warning
  * debian/rules:
- Fix usage of dh_installinit (LP: #1292990)

 -- Robert Ancell   Thu, 05 May 2016
12:23:45 +1200

** Changed in: lightdm (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/1509829

Title:
  lightdm-guest-session profile is too strict to input Japanese text
  with fcitx-mozc

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in fcitx package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in mozc package in Ubuntu:
  Fix Released
Status in fcitx source package in Xenial:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Committed
Status in mozc source package in Xenial:
  Fix Released

Bug description:
  When logging into lightdm guest session, mozc gives an error saying
  "Failed to start Kana/Kanji conversion program. You need to reboot".
  Thus Japanese text cannot be input.

  [possibly related messages]
  10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 
audit(1445787629.866:709): apparmor="DENIED" operation="link" 
profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/dev/shm/sem.69ef545277bb" pid=9534 comm="fcitx" requested_mask="l" 
denied_mask="l" fsuid=120 ouid=120 target="/dev/shm/oFbWJv"
  10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 
audit(1445787629.870:710): apparmor="DENIED" operation="bind" 
profile="/usr/lib/lightdm/lightdm-guest-session" pid=9554 comm="mozc_server" 
family="unix" sock_type="stream" protocol=0 requested_mask="bind" 
denied_mask="bind" addr="@tmp/.mozc.d23bc799563c3f748fa591c15f46c971.session"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 26 00:45:41 2015
  InstallationDate: Installed on 2015-10-25 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1509829/+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 960157] Re: lightdm exits on SIGHUP

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.19.0-0ubuntu1

---
lightdm (1.19.0-0ubuntu1) yakkety; urgency=medium

  * New upstream release:
- Use /dev/tty0 instead of /dev/console for VT operations (LP: #1566073)
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix lxsession running in guest session
- Drop support for legacy XMir
- Fix g_spawn compiler warning
  * debian/rules:
- Fix usage of dh_installinit (LP: #1292990)

 -- Robert Ancell   Thu, 05 May 2016
12:23:45 +1200

** Changed in: lightdm (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/960157

Title:
  lightdm exits on SIGHUP

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Committed
Status in lightdm source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  LightDM quits when it receives SIGUSR1, SIGUSR2 or SIGHUP. But convention 
these signals should not quit a service (they should get it to dump state, 
reload configuration etc).

  [Test Case]
  1. Start lightdm
  2. sudo killall -SIGHUP lightdm

  Expected result:
  Nothing happens

  Observed result:
  LightDM restarts

  [Regression Potential]
  Low. We now just quit only on SIGTERM and SIGINT.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/960157/+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 1575200] Re: Error connecting to X server via IPv6

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.19.0-0ubuntu1

---
lightdm (1.19.0-0ubuntu1) yakkety; urgency=medium

  * New upstream release:
- Use /dev/tty0 instead of /dev/console for VT operations (LP: #1566073)
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix lxsession running in guest session
- Drop support for legacy XMir
- Fix g_spawn compiler warning
  * debian/rules:
- Fix usage of dh_installinit (LP: #1292990)

 -- Robert Ancell   Thu, 05 May 2016
12:23:45 +1200

** Changed in: lightdm (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/1575200

Title:
  Error connecting to X server via IPv6

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Committed

Bug description:
  I've discovered a problem in lightdm XDMCP using link-local IPv6 addresses 
without interface index to connect to X server.
  It has been originally reported at 
https://bugzilla.redhat.com/show_bug.cgi?id=1322775.

  The problem can be fixed by having the XDMCP client not transmitting
  link-local addresses in the request, but if it does, lightdm XDMCP
  server can be a lot smarter if the attached patch is applied.

  It changes the X server address selection order to set the lowest
  preference to link-local addresses, even if matching the source
  address or family.

  This is not 100% full-proof: if only link-local addresses have been
  received, one of them is used anyway. In this case, a complete
  solution would be to determine and set the address interface index if
  not ambiguous.

  However, this patch fixes the problem for most of the non-pathological 
  cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1575200/+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 1578442] Re: XDMCP Willing/Unwilling messages do not report hostname

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.19.0-0ubuntu1

---
lightdm (1.19.0-0ubuntu1) yakkety; urgency=medium

  * New upstream release:
- Use /dev/tty0 instead of /dev/console for VT operations (LP: #1566073)
- Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
- Improve XDMCP IPv6 address selection (LP: #1575200)
- Set XDMCP hostname field in to system hostname or configured value
  (LP: #1578442)
- Allow fcitx and mozc to run in guest session (LP: #1509829)
- Fix lxsession running in guest session
- Drop support for legacy XMir
- Fix g_spawn compiler warning
  * debian/rules:
- Fix usage of dh_installinit (LP: #1292990)

 -- Robert Ancell   Thu, 05 May 2016
12:23:45 +1200

** Changed in: lightdm (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/1578442

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1578442/+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 960157] Re: lightdm exits on SIGHUP

[Robert Ancell]

** Changed in: lightdm
   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/960157

Title:
  lightdm exits on SIGHUP

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Committed
Status in lightdm source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  LightDM quits when it receives SIGUSR1, SIGUSR2 or SIGHUP. But convention 
these signals should not quit a service (they should get it to dump state, 
reload configuration etc).

  [Test Case]
  1. Start lightdm
  2. sudo killall -SIGHUP lightdm

  Expected result:
  Nothing happens

  Observed result:
  LightDM restarts

  [Regression Potential]
  Low. We now just quit only on SIGTERM and SIGINT.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/960157/+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 1509829] Re: lightdm-guest-session profile is too strict to input Japanese text with fcitx-mozc

[Robert Ancell]

** Changed in: lightdm
   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/1509829

Title:
  lightdm-guest-session profile is too strict to input Japanese text
  with fcitx-mozc

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in fcitx package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Committed
Status in mozc package in Ubuntu:
  Fix Released
Status in fcitx source package in Xenial:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Committed
Status in mozc source package in Xenial:
  Fix Released

Bug description:
  When logging into lightdm guest session, mozc gives an error saying
  "Failed to start Kana/Kanji conversion program. You need to reboot".
  Thus Japanese text cannot be input.

  [possibly related messages]
  10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 
audit(1445787629.866:709): apparmor="DENIED" operation="link" 
profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/dev/shm/sem.69ef545277bb" pid=9534 comm="fcitx" requested_mask="l" 
denied_mask="l" fsuid=120 ouid=120 target="/dev/shm/oFbWJv"
  10月 26 00:40:29 test-Standard-PC-i440FX-PIIX-1996 kernel: audit: type=1400 
audit(1445787629.870:710): apparmor="DENIED" operation="bind" 
profile="/usr/lib/lightdm/lightdm-guest-session" pid=9554 comm="mozc_server" 
family="unix" sock_type="stream" protocol=0 requested_mask="bind" 
denied_mask="bind" addr="@tmp/.mozc.d23bc799563c3f748fa591c15f46c971.session"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 26 00:45:41 2015
  InstallationDate: Installed on 2015-10-25 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1509829/+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 1273524] Re: LXDE guest session shows error message "no session for pid "

[Robert Ancell]

** Changed in: lightdm
   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/1273524

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Triaged
Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Committed
Status in lxsession package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Fix Committed
Status in lxsession source package in Xenial:
  New

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1273524/+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 1578442] Re: XDMCP Willing/Unwilling messages do not report hostname

[Robert Ancell]

** Changed in: lightdm
   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/1578442

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1578442/+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 1575200] Re: Error connecting to X server via IPv6

[Robert Ancell]

** Changed in: lightdm
   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/1575200

Title:
  Error connecting to X server via IPv6

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Committed

Bug description:
  I've discovered a problem in lightdm XDMCP using link-local IPv6 addresses 
without interface index to connect to X server.
  It has been originally reported at 
https://bugzilla.redhat.com/show_bug.cgi?id=1322775.

  The problem can be fixed by having the XDMCP client not transmitting
  link-local addresses in the request, but if it does, lightdm XDMCP
  server can be a lot smarter if the attached patch is applied.

  It changes the X server address selection order to set the lowest
  preference to link-local addresses, even if matching the source
  address or family.

  This is not 100% full-proof: if only link-local addresses have been
  received, one of them is used anyway. In this case, a complete
  solution would be to determine and set the address interface index if
  not ambiguous.

  However, this patch fixes the problem for most of the non-pathological 
  cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1575200/+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 1578442] Re: XDMCP Willing/Unwilling messages do not report hostname

[Robert Ancell]

** Changed in: lightdm/1.2
   Status: New => Won't Fix

** Also affects: lightdm (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: lightdm (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: lightdm (Ubuntu Precise)
   Status: New => Won't Fix

** Changed in: lightdm/1.18
Milestone: None => 1.18.2

** Changed in: lightdm
Milestone: None => 1.19.0

** Changed in: lightdm/1.10
Milestone: None => 1.10.7

** Changed in: lightdm/1.16
Milestone: None => 1.16.8

-- 
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/1578442

Title:
  XDMCP Willing/Unwilling messages do not report hostname

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Precise:
  Won't Fix
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Wily:
  Triaged
Status in lightdm source package in Xenial:
  Triaged

Bug description:
  [Impact]
  When LightDM sends out an XDMCP Willing/Unwilling message it leaves the 
hostname blank. This field is used in clients 

  [Test Case]
  1. Start LightDM with the XDMCP server enabled
  2. Start an XDMCP client that supports showing available XDMCP servers (e.g. 
kdmchooser)

  Expected result:
  An appropriate label is used for the LightDM XDMCP server

  Observed result:
  No label is shown

  [Regression potential]
  Low. This field is now populated by the system hostname by default or a value 
specified in LightDM configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1578442/+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 1568113] Re: docs/get-started.md: Still discusses snappy-tools and snappy-remote

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.8.8

---
snapcraft (2.8.8) yakkety; urgency=medium

  * Create the 'partial' directory for apt. (#499) (LP: #1578007)

 -- Sergio Schvezov   Wed, 04 May 2016
14:22:58 -0300

** Changed in: snapcraft (Ubuntu Yakkety)
   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/1568113

Title:
  docs/get-started.md: Still discusses snappy-tools and snappy-remote

Status in Snapcraft:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  Neither of these exist anymore. This document should be updated to
  only talk about Snapcraft on Xenial. The developer website should also
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1568113/+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 1570992] Re: autopkgtests are running snapcraft from source

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.8.8

---
snapcraft (2.8.8) yakkety; urgency=medium

  * Create the 'partial' directory for apt. (#499) (LP: #1578007)

 -- Sergio Schvezov   Wed, 04 May 2016
14:22:58 -0300

** Changed in: snapcraft (Ubuntu Yakkety)
   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/1570992

Title:
  autopkgtests are running snapcraft from source

Status in Snapcraft:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  autopkgtests are running snapcraft from source. They should run the
  tests using the installed binary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1570992/+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 1573211] Re: examples tests are passing the --allow-unauthenticated flag on install

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.8.8

---
snapcraft (2.8.8) yakkety; urgency=medium

  * Create the 'partial' directory for apt. (#499) (LP: #1578007)

 -- Sergio Schvezov   Wed, 04 May 2016
14:22:58 -0300

** Changed in: snapcraft (Ubuntu Yakkety)
   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/1573211

Title:
  examples tests are passing the --allow-unauthenticated flag on install

Status in Snapcraft:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  snap install no longer takes the --allow-unauthenticated flag. We need
  to update the examples tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1573211/+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 1573697] Re: examples tests are using the removed snap service to check status

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.8.8

---
snapcraft (2.8.8) yakkety; urgency=medium

  * Create the 'partial' directory for apt. (#499) (LP: #1578007)

 -- Sergio Schvezov   Wed, 04 May 2016
14:22:58 -0300

** Changed in: snapcraft (Ubuntu Yakkety)
   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/1573697

Title:
  examples tests are using the removed snap service to check status

Status in Snapcraft:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  the recent snappy release removed the service command.

  We are using that command to check the status of the example services
  we install during the tests. We should use systemclt status instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1573697/+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 1575383] Re: the snapcraft integration coverage is not providing any useful information

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.8.8

---
snapcraft (2.8.8) yakkety; urgency=medium

  * Create the 'partial' directory for apt. (#499) (LP: #1578007)

 -- Sergio Schvezov   Wed, 04 May 2016
14:22:58 -0300

** Changed in: snapcraft (Ubuntu Yakkety)
   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/1575383

Title:
  the snapcraft integration coverage is not providing any useful
  information

Status in Snapcraft:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  Now with more than 95% of unit test coverage and a stable test-driven
  process, the integration test coverage is not giving us any new or
  useful information. Currently it is just a hack that pollutes our
  project.

  I'll remove it.

  kudos to the team.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1575383/+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 1574857] Re: mosquitto example test is using outdated snap data path

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.8.8

---
snapcraft (2.8.8) yakkety; urgency=medium

  * Create the 'partial' directory for apt. (#499) (LP: #1578007)

 -- Sergio Schvezov   Wed, 04 May 2016
14:22:58 -0300

** Changed in: snapcraft (Ubuntu Yakkety)
   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/1574857

Title:
  mosquitto example test is using outdated snap data path

Status in Snapcraft:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  The mosquitto example test is looking for a file in 
/home/ubuntu/snaps/mosquitto/*/
  That's the old snap data path. The test must be updated to use 
/home/ubuntu/snap/mosquitto/*/

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1574857/+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 1573349] Re: snapcraft examples are starting the binaries from outdated path

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.8.8

---
snapcraft (2.8.8) yakkety; urgency=medium

  * Create the 'partial' directory for apt. (#499) (LP: #1578007)

 -- Sergio Schvezov   Wed, 04 May 2016
14:22:58 -0300

** Changed in: snapcraft (Ubuntu Yakkety)
   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/1573349

Title:
  snapcraft examples are starting the binaries from outdated path

Status in Snapcraft:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  snappy is now storing the binaries in /snap/bin. Our examples tests
  are still using the old path /snaps/bin to launch them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1573349/+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 1574901] Re: busybox example no longer has permission to access files in home

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.8.8

---
snapcraft (2.8.8) yakkety; urgency=medium

  * Create the 'partial' directory for apt. (#499) (LP: #1578007)

 -- Sergio Schvezov   Wed, 04 May 2016
14:22:58 -0300

** Changed in: snapcraft (Ubuntu Yakkety)
   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/1574901

Title:
  busybox example no longer has permission to access files in home

Status in Snapcraft:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  Our busybox example touches a file in home. This needs to be updated
  to use the snap data path.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1574901/+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 1575876] Re: stage-packages cannot be used with the nodejs plugin

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.8.8

---
snapcraft (2.8.8) yakkety; urgency=medium

  * Create the 'partial' directory for apt. (#499) (LP: #1578007)

 -- Sergio Schvezov   Wed, 04 May 2016
14:22:58 -0300

** Changed in: snapcraft (Ubuntu Yakkety)
   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/1575876

Title:
  stage-packages cannot be used with the nodejs plugin

Status in Snapcraft:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  Tar extraction is wiping out the install dir which is where staged
  packages land.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1575876/+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 1575882] Re: nodejs plugin deletes downloaded npm runtime

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.8.8

---
snapcraft (2.8.8) yakkety; urgency=medium

  * Create the 'partial' directory for apt. (#499) (LP: #1578007)

 -- Sergio Schvezov   Wed, 04 May 2016
14:22:58 -0300

** Changed in: snapcraft (Ubuntu Yakkety)
   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/1575882

Title:
  nodejs plugin deletes downloaded npm runtime

Status in Snapcraft:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  Doing rebuilds is complicated as npm is extracted during build but the
  original source is wiped out by the Tar instance

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1575882/+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 1561403] Re: CVE-2016-2117

[Steve Beattie]

** Changed in: linux (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux (Ubuntu Wily)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Trusty)
   Status: New => Fix Committed

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   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/1561403

Title:
  CVE-2016-2117

Status in linux package in Ubuntu:
  New
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-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
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-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
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 Committed
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-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-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
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 

[Group.of.nepali.translators] [Bug 1570195] Re: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices

[Chris J Arges]

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux (Ubuntu Xenial)
   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/1570195

Title:
  Net tools cause kernel soft lockup after DPDK touched  VirtIO-pci
  devices

Status in dpdk package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in dpdk source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid

Bug description:
  Guys,

   I'm facing an issue here with both "ethtool" and "ip", while trying
  to manage black-listed by DPDK PCI VirtIO devices.

   You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to
  run those tests

   PCI device example from inside a Xenial guest:

  ---
  # lspci | grep Ethernet
  00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:04.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:05.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:06.0 Ethernet controller: Red Hat, Inc Virtio network device
  ---

  Where "ens3" is the first / default interface, attached to Libvirt's
  "default" network. The "ens4" is reserved for "ethtool / ip" tests
  (attached to another Libvirt's network without IPs or DHCP), "ens5"
  will be "dpdk0" and "ens6" "dpdk1"...

  ---
   *** How it works?

   1- For example, try to enable multi-queue on DPDK's devices, boot
  your Xenial guest, and run:

   ethtool -L ens5 combined 4
   ethtool -L ens6 combined 4

   2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it
  up.

   https://help.ubuntu.com/16.04/serverguide/DPDK.html

   service openvswitch-switch stop
   service dpdk stop

   OVS DPDK Options (/etc/default/openvswitch-switch):

  --
  DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist 
:00:03.0,:00:04.0'
  --

   service dpdk start
   service openvswitch-switch start

   - Enable multi-queue on OVS+DPDK inside of the VM:

   ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4
   ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00

   * Multi-queue apparently works! ovs-vswitchd consumes more that 100%
  of CPU, meaning that it multi-queue is there...

   *** Where it fails?

   1- Reboot the VM and try to run ethtool again (or go straight to 2
  below):

   ethtool -L ens5 combined 4

   2- Try to fire up ens4:

   ip link set dev ens4 up

  
   # FAIL! Both commands hangs, consuming 100% of guest's CPU...

   So, it looks like a Linux fault, because it is "allowing" the DPDK
  VirtIO App (a user land App), to interfere with kernel devices in a
  strange way...

  Best,
  Thiago

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 14 00:35 seq
   crw-rw 1 root audio 116, 33 Apr 14 00:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  Date: Thu Apr 14 01:27:27 2016
  HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de
  InstallationDate: Installed on 2016-04-07 (7 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160406)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=9911604e-353b-491f-a0a9-804724350592 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-wily
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-wily
  dmi.sys.ve

[Group.of.nepali.translators] [Bug 1546565] Re: Ownership/Permissions of vhost_user sockets for openvswitch-dpdk make them unusable by libvirt/qemu/kvm

[Chris J Arges]

** Also affects: openvswitch (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: openvswitch-dpdk (Ubuntu)

** No longer affects: openvswitch-dpdk (Ubuntu Xenial)

-- 
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/1546565

Title:
  Ownership/Permissions of vhost_user sockets for openvswitch-dpdk make
  them unusable by libvirt/qemu/kvm

Status in dpdk package in Ubuntu:
  Fix Released
Status in openvswitch package in Ubuntu:
  New
Status in dpdk source package in Xenial:
  Fix Released
Status in openvswitch source package in Xenial:
  New

Bug description:
  As of today the vhost_user sockets created by openvswitch have root:root file 
ownership.
  In fact creation is actually done by code the DPDK lib, but the path is 
passed to it from openvswitch.

  The API called to DPDK has no notion of ownership/groups.
  It just "inherits" what the current running process has.
  But due to LP:1546556 the process ownership/group can't be changed the usual 
way openvsiwtch would when using dpdk.

  KVM as invoked by libvirt will run under libvirt-qemu:kvm and will
  thereby be unable to access these sockets.

  The current workaround is:
 1. wait after start of openvswitch (only then the sockets exist)
 2. chown all created vhost_iuser sockets that are to be used 
e.g. sudo chown libvirt-qemu /var/run/openvswitch/vhost-user-1 
 3. if one wants to separate vhost_user sockets from the "rest" of 
openvswitch /var/run files use e.g.:
DPDK_OPTS='[...] -vhost_sock_dir /var/run/openvswitch-vhost [...]
 X. this has to be redone every start/restart of oepnvswitch
 Y. if permissions are changed in a way that openvswitch can no more remove 
them on shutdown they won't re-initialize properly on the next start

  That is a severe shortcoming and not really applicable to a supported 
production environment.
  There are discussions ongoing about providing an option to specify 
owner/group/permissions of vhost_user sockets which would solve the issue.
  Unfortunately the patch series is blocked by a wider discussion about moving 
the dpdk configuration to the ovsdb (which makes sense, but stalls the 
acceptance of the patches providing the interface to modify permissions.

  Link to the last thread about moving dpdk config to ovsdb: 
http://comments.gmane.org/gmane.network.openvswitch.devel/59186
  Link to the last thread about making vhost_user socket user/group 
configurable - patch 4&5 of this: 
http://openvswitch.org/pipermail/dev/2015-December/063568.html
  But as mentioned it was decided to get the db config discussion done first.

  It is unsure if the patches once final will make it into openvswitch 2.5 - it 
would be great if they would.
  But even if not they shouldn't appear too much after and we might be able to 
cherry pick them?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1546565/+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 1578305] Re: Stoney powerplay support

[Tim Gardner]

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: Confirmed

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Yakkety)
   Status: Confirmed => Fix Released

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1578305

Title:
  Stoney powerplay support

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I'd love to submit a patch right now but I can't since the clone is
  taking way too long...

  The bug is in drivers/gpu/drm/amd/amdgpu/amdgpu_powerplay.c on line 83
  you need to insert

  case CHIP_STONEY:

  before CHIP_CARRIZO to get ST to successfully init with the amdgpu
  module.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  amd1533 F pulseaudio
   /dev/snd/controlC0:  amd1533 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May  4 12:35:10 2016
  HibernationDevice: RESUME=UUID=39b1897f-c3d9-4222-9b73-94e0f6527917
  InstallationDate: Installed on 2016-05-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enx54b80aefee18  no wireless extensions.
   
   enx1a1b9c20  no wireless extensions.
   
   lono wireless extensions.
  MachineType: AMD Gardenia-ST
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=f4bc1961-0964-4010-a6e5-401bbfe28352 ro quiet splash vt.handoff=7 
amdgpu.powerplay=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: WGY5930N_Weekly_15_09_3
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Gardenia-ST
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrWGY5930N_Weekly_15_09_3:bd09/30/2015:svnAMD:pnGardenia-ST:pvr1:rvnAMD:rnGardenia-ST:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Gardenia-ST
  dmi.product.version: 1
  dmi.sys.vendor: AMD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578305/+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 1573117] Re: stress-ng: clone system calls randomly fail with -EINVAL on aarch64

[Chris J Arges]

** Changed in: stress-ng (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/1573117

Title:
  stress-ng: clone system calls randomly fail with -EINVAL on aarch64

Status in stress-ng package in Ubuntu:
  Fix Released
Status in stress-ng source package in Xenial:
  Fix Released

Bug description:
  [SRU] Xenial

  Getting -EINVAL on stressors that call clone() on aarch64. Turns out
  that the clone() thread's stack has to be 16 byte aligned.

  [REPODUCER + FIX]
  For example, run:

  stress-ng --vm-rw 1 -v

  Without the fix, this can randomly exit with -EINVAL when the stack
  being passed to the clone() system call is not aligned on a 16 byte
  boundary.

  With the fix, the clone() system call works fine and the stressor will
  run.

  [REGRESSION POTENIAL]
  Minimal. I have exhaustively tested this on multiple platforms/architectures 
and the fix ensures that the stack is aligned correctly.  stress-ng is a leaf 
project in universe and this fix only touches 3 of the stress-ng stressors that 
use the clone() system call.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1573117/+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 1559185] Re: Doesn't understand apt: urls

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software -
3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1

---
gnome-software (3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1) xenial; 
urgency=medium

  * New upstream snapshot from the wip/ubuntu-xenial branch at
git://git.gnome.org/gnome-software.
- Recognize apt: urls (LP: #1559185)
- Increase the number of displayed reviews from 10 to 30 (LP: #1559284)
- Show version information for non-installed apps (LP: #1564621)
- Show size information for non-installed apps (LP: #1571414)
- Fix sideloading of local .deb files (LP: #1573408)
- Enable the Snappy backend (LP: #1575104)

 -- William Hua   Tue, 26 Apr 2016 14:55:05
+0200

** Changed in: gnome-software (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/1559185

Title:
  Doesn't understand apt: urls

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact:
  gnome-software doesn't understand apturls

  Test case:
  start "gnome-software apt:gedit", it should opens the gedit page, clicking on 
an "apt:" url in firefox should open gnome-software on the corresponding 
package 
  one limitation, it only works for apps gnome-software knows about though (so 
mostly graphical softwares)

  Regression potential:
  it only adds support for a new type or url shouldn't regress existing code

  -

  Doing the same in software-center opens the gedit details page

  software-center used to the default handler for apt: urls, I've
  changed that to apturl but if we want to keep the previous user
  experience we should have gnome-software handle those

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1559185/+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 1557115] Re: [regression] RadioTray won't launch without python-xdg

[dino99]

** Changed in: gtk
   Status: New => Invalid

** Summary changed:

- [regression] RadioTray won't launch without python-xdg
+ [regression] RadioTray won't launch without python-xdg & 
gir1.2-appindicator3.01

-- 
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/1557115

Title:
  [regression] RadioTray won't launch without python-xdg &
  gir1.2-appindicator3.01

Status in GTK+:
  Invalid
Status in One Hundred Papercuts:
  Confirmed
Status in radiotray package in Ubuntu:
  Triaged
Status in radiotray source package in Xenial:
  Triaged
Status in radiotray package in Debian:
  New

Bug description:
  Although I've been previously running RadioTray in Ubuntu 16.04, it
  has recently become unlaunchable.

  Typically when you launch RadioTray, an indicator appears on the top-
  right-panel (left of the clock), and you are able to select a radio-
  station to stream.

  Now, when you launch it, nothing apparently happens.

  
  
  This is a lack of dependencies by default:

  Need add depends to « python-xdg and gir1.2-appindicator3.01 »

  
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: radiotray 0.7.3-5ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 14 13:35:53 2016
  InstallationDate: Installed on 2016-03-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: radiotray
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1557115/+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 1559284] Re: Increase the number of displayed reviews

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software -
3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1

---
gnome-software (3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1) xenial; 
urgency=medium

  * New upstream snapshot from the wip/ubuntu-xenial branch at
git://git.gnome.org/gnome-software.
- Recognize apt: urls (LP: #1559185)
- Increase the number of displayed reviews from 10 to 30 (LP: #1559284)
- Show version information for non-installed apps (LP: #1564621)
- Show size information for non-installed apps (LP: #1571414)
- Fix sideloading of local .deb files (LP: #1573408)
- Enable the Snappy backend (LP: #1575104)

 -- William Hua   Tue, 26 Apr 2016 14:55:05
+0200

** Changed in: gnome-software (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/1559284

Title:
  Increase the number of displayed reviews

Status in GNOME Software:
  In Progress
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  * Impact
  gnome-software displays only 10 reviews and doesn't give you a way to load 
more

  * Test case
  open a popular application (eg. Audacity, GIMP) in g-s and look at the 
reviews, there should be more than 10

  * Regression potential
  we load more data so the details page might be a bit slower to load

  

  Using xenial it seems there is no way to load more review? I reported
  that upstream but it might be a choice for them since they don't have
  lot of reviews on their server

  That commit suggests the UI exists
  
https://git.gnome.org/browse/gnome-software/commit/?id=a92da2e47478ef9c124367ad2a87efcd3f2375c0

  There might be a need to write the backend side though

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1559284/+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 1573408] Re: GNOME Software does not install third-party .deb packages

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software -
3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1

---
gnome-software (3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1) xenial; 
urgency=medium

  * New upstream snapshot from the wip/ubuntu-xenial branch at
git://git.gnome.org/gnome-software.
- Recognize apt: urls (LP: #1559185)
- Increase the number of displayed reviews from 10 to 30 (LP: #1559284)
- Show version information for non-installed apps (LP: #1564621)
- Show size information for non-installed apps (LP: #1571414)
- Fix sideloading of local .deb files (LP: #1573408)
- Enable the Snappy backend (LP: #1575104)

 -- William Hua   Tue, 26 Apr 2016 14:55:05
+0200

** Changed in: gnome-software (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/1573408

Title:
  GNOME Software does not install third-party .deb packages

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact
  installing local debs from nautilus doesn't work

  Test case
  download a deb and double click on it nautilus

  Regression potential
  the changes are restoring a feature that was working, should regression other 
parts of the code

  -

  Unlike previous versions of Ubuntu Unity, I'm unable to install the 
google-talk-plugin in Ubuntu 16.04, where it (the deb) can be downloaded here:
  https://www.google.com/tools/dlpage/hangoutplugin

  After downloading, I open the deb file from Firefox and it launches
  the gnome-software package (used in Unity now).

  The first time I click the install button in gnome-software, I notice
  a strange repositioning of the layout, but nothing else happens.

  Clicking the install button a second time puts a 
question-mark-progress-launcher onto the launcher (task) bar, but it never 
progresses:
  http://neartalk.com/ss/2016-04-22_001_1262x740.png

  So far, no one has offered a workaround:
  
http://askubuntu.com/questions/760305/how-to-install-google-hangouts-plugin-in-ubuntu-16-04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 01:02:45 2016
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1573408/+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 1573117] Re: stress-ng: clone system calls randomly fail with -EINVAL on aarch64

[Launchpad Bug Tracker]

This bug was fixed in the package stress-ng - 0.05.23-1ubuntu2

---
stress-ng (0.05.23-1ubuntu2) xenial; urgency=medium

  * Fix alignment mask to ensure stacks are 16 byte aligned (LP: #1573117)
- incorrect mask used in previous fix, now using correct mask

stress-ng (0.05.23-1ubuntu1) xenial; urgency=medium

  * Ensure all clone() calls are 16 byte aligned for aarch64 (LP: #1573117)
  * stress-mmap: handle SIGBUS signals (LP: #1569468)

 -- Colin King   Tue, 26 Apr 2016 12:16:47
+0100

** Changed in: stress-ng (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/1573117

Title:
  stress-ng: clone system calls randomly fail with -EINVAL on aarch64

Status in stress-ng package in Ubuntu:
  Fix Committed
Status in stress-ng source package in Xenial:
  Fix Released

Bug description:
  [SRU] Xenial

  Getting -EINVAL on stressors that call clone() on aarch64. Turns out
  that the clone() thread's stack has to be 16 byte aligned.

  [REPODUCER + FIX]
  For example, run:

  stress-ng --vm-rw 1 -v

  Without the fix, this can randomly exit with -EINVAL when the stack
  being passed to the clone() system call is not aligned on a 16 byte
  boundary.

  With the fix, the clone() system call works fine and the stressor will
  run.

  [REGRESSION POTENIAL]
  Minimal. I have exhaustively tested this on multiple platforms/architectures 
and the fix ensures that the stack is aligned correctly.  stress-ng is a leaf 
project in universe and this fix only touches 3 of the stress-ng stressors that 
use the clone() system call.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1573117/+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 1569468] Re: stress-ng mmap failing on zVM and LPAR

[Launchpad Bug Tracker]

This bug was fixed in the package stress-ng - 0.05.23-1ubuntu2

---
stress-ng (0.05.23-1ubuntu2) xenial; urgency=medium

  * Fix alignment mask to ensure stacks are 16 byte aligned (LP: #1573117)
- incorrect mask used in previous fix, now using correct mask

stress-ng (0.05.23-1ubuntu1) xenial; urgency=medium

  * Ensure all clone() calls are 16 byte aligned for aarch64 (LP: #1573117)
  * stress-mmap: handle SIGBUS signals (LP: #1569468)

 -- Colin King   Tue, 26 Apr 2016 12:16:47
+0100

** Changed in: stress-ng (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/1569468

Title:
  stress-ng mmap failing on zVM and LPAR

Status in stress-ng package in Ubuntu:
  Fix Released
Status in stress-ng source package in Xenial:
  Fix Released

Bug description:
  [SRU, Xenial]

  When running stress-ng on zVM and LPAR we are hitting SIGBUS errors
  because we have a sparsely allocated mmap'd backing file which due to
  over commit and a full file system causes pages not to be mapped in
  and causes memory accesses on unbacked pages to trigger a SIGBUS.

  [REPRODUCER + FIX]
  Run stress-ng --mmap 64 --maximize on a filesystem that is very nearly full 
and the SIGBUS triggers and the stressor exits early with SIGBUS.  With the 
fix, the SIGBUS is caught and the stressor can continue without premature early 
exit.

  [REGRESSION POTENTIAL]
  I am requesting syncing with 0.05.24 micro release as this contains the fix 
plus a few SIGSEGV stack trapping fixes.  stress-ng is a universe leaf project 
and the fixes touch just a few of the stress tests. These have been regression 
checked on various architectures and the code passes static analysis on 
cppcheck, CoverityScan and clang's scan-build, so regression potential is 
minimal.


  --

  Running stress-ng on s390 in all three modes.  This seems to work ok
  in z/KVM, however, on zVM and LPAR as of a few days ago on Xenial the
  mmap stressor has started failing.

  I tried to get detailed logs but either don't know the correct
  switches or they simply aren't there.

  Here is the output when I used --log-file and --verbose on an LPAR:
  root@s1lp10-jefflane:~# less stress-ng-mmap-fail.log
  stress-ng: debug: [179421] 4 processors online, 4 processors configured
  stress-ng: info:  [179421] dispatching hogs: 4 mmap
  stress-ng: debug: [179421] cache allocate: reducing cache level from L3 (too 
high) to L2
  stress-ng: info:  [179421] cache allocate: default cache size: 2048K
  stress-ng: debug: [179421] starting stressors
  stress-ng: debug: [179422] stress-ng-mmap: started [179422] (instance 0)
  stress-ng: debug: [179423] stress-ng-mmap: started [179423] (instance 1)
  stress-ng: debug: [179424] stress-ng-mmap: started [179424] (instance 2)
  stress-ng: debug: [179421] 4 stressors spawned
  stress-ng: debug: [179425] stress-ng-mmap: started [179425] (instance 3)
  stress-ng: debug: [179424] stress-ng-mmap: exited [179424] (instance 2)
  stress-ng: debug: [179422] stress-ng-mmap: exited [179422] (instance 0)
  stress-ng: debug: [179421] process [179422] terminated
  stress-ng: debug: [179421] process 179423 (stress-ng-mmap) terminated on 
signal: 7 (Bus error)
  stress-ng: debug: [179421] process [179423] terminated
  stress-ng: debug: [179421] process [179424] terminated
  stress-ng: debug: [179421] process 179425 (stress-ng-mmap) terminated on 
signal: 7 (Bus error)
  stress-ng: debug: [179421] process [179425] terminated
  stress-ng: info:  [179421] unsuccessful run completed in 300.68s (5 mins, 
0.68 secs)

  That is the only info I have for the failure, unfortunately.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: stress-ng 0.05.23-1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: s390x
  Date: Tue Apr 12 12:47:49 2016
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: stress-ng
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1569468/+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 1562033] Re: package xinit 1.3.4-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

This bug was fixed in the package xinit - 1.3.4-3ubuntu0.1

---
xinit (1.3.4-3ubuntu0.1) xenial; urgency=medium

  * postinst: Check that xinitrc exists before trying to chmod it. (LP:
#1562033)

 -- Timo Aaltonen   Fri, 22 Apr 2016 06:53:18 +0300

** Changed in: xinit (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/1562033

Title:
  package xinit 1.3.4-3 failed to install/upgrade: subprocess installed
  post-installation script returned error exit status 1

Status in xinit package in Ubuntu:
  Fix Released
Status in xinit source package in Xenial:
  Fix Released
Status in xinit source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  upgrade fails if /etc/X11/xinit/xinitrc is missing because the
  postinst script doesn't check for it's existence before running chmod
  on it.

  [Test case]

  rm /etc/X11/xinit/xinitrc
  /var/lib/dpkg/info/xinit.postinst configure 1

  [Regression potential]

  nope

  --

  During remote do-release-upgrade -d from a wily box.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: xinit 1.3.4-3
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar 25 15:06:11 2016
  DistUpgraded: 2016-03-25 15:10:36,689 ERROR failed to import apport python 
module, can't generate crash: No module named 'xml.dom'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.2.0-34-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-15-generic, x86_64: installed
   nvidia-340, 340.96, 4.2.0-34-generic, x86_64: installed
   nvidia-340, 340.96, 4.4.0-15-generic, x86_64: installed
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
     Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:1044]
  InstallationDate: Installed on 2013-03-11 (1109 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=467f6a66-74b5-4070-90db-2150245db2cf ro quiet splash radeon.audio=1 
radeon.dpm=1 clocksource=hpet hpet=enable nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.7
  SourcePackage: xinit
  Title: package xinit 1.3.4-3 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-03-25 (0 days ago)
  dmi.bios.date: 08/06/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6X58D-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160318-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Mar 17 18:05:50 2016
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.17.2-1ubuntu9.1

To manage notifi

[Group.of.nepali.translators] [Bug 1561830] Re: Hard disk writes fail in 16.04 daily on nForce 430

[Joseph Salisbury]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Tags added: performing-bisect

-- 
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/1561830

Title:
  Hard disk writes fail in 16.04 daily on nForce 430

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  I have an old PC I use for testing new operating systems.  It has
  previously had Ubuntu 15.10 installed and working.  The motherboard is
  an Asus M2NPV-VM, with Nvidia nForce 430 chipset and Nvidia GeForce
  6150 GPU.  I have installed an Nvidia GT220 card to use for more
  modern video support.

  When I attempt to install Ubuntu 16.04 beta (daily xenial-desktop-
  amd64.iso file downloaded 24/03/2016  18:17), it starts to write to
  the hard disk (Samsung HD103UJ), and after a short time the install
  got lots of disk write errors in kern.log.  After the errors, the disk
  was unable to be read either, with "fdisk -l /dev/sda" failing to read
  a sector, where it had worked before starting the install.  Unplugging
  the SATA cable to the drive and plugging it in again made the drive
  work again (on /dev/sdc), but another attempt to install failed with
  the same write errors.

  I noticed that the log had swap write errors also, so I rebooted the
  install DVD again, and this time did a "swapoff -a" command before
  attempting to install, but got the same errors again.  So I found my
  Ubuntu 15.10 install DVD and tried a new install from that, which
  worked just fine.

  On rebooting with my 16.04 daily DVD, I again did "swapoff -a" so that
  the DVD based system would run normally, then tried mounting the EXT4
  system partition I had just installed using the 15.10 install DVD.
  That worked, so I tried dd commands to do test writes to that
  partition.  The following commands worked:

dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=10k
dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=100k

  but when I did this command:

dd if=/dev/zero of=/mnt/sda8/tmp/output bs=8k count=1000k

  after a while errors started appearing in kern.log, just as with the
  attempts to install 16.04.

  It appears that with sustained write activity, the errors will start
  and then the drive will become unusable until it is unplugged and
  plugged in again.

  I have attached the kern.log and syslog files from the 15.10 install
  that worked, and the 16.04 install attempt that failed.  The first
  error message appears to be this:

  ata3: EH in SWNCQ mode,QC:qc_active 0x1FFF sactive 0x1FFF
  ata3: SWNCQ:qc_active 0x1 defer_bits 0x1FFE last_issue_tag 0x0
  dhfis 0x1 dmafis 0x0 sdbfis 0x0

  which leads me to suspect a problem with the handling of the SATA 
controller's interrupts.
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2233 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2233 F pulseaudio
  CasperVersion: 1.368
  DistroRelease: Ubuntu 16.04
  IwConfig:
   enp0s20   no wireless extensions.
   
   lono wireless extensions.
   
   enp2s9no wireless extensions.
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:0118 KYE Systems Corp. (Mouse Systems) 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash ---
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/07/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2NPV-VM ACPI BIOS Revision 1401
  dmi.board.name: M2NPV-VM
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 1.xx
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: C

[Group.of.nepali.translators] [Bug 1564621] Re: Version unknown of not-installed applications, it appears for installed ones

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software -
3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1

---
gnome-software (3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1) xenial; 
urgency=medium

  * New upstream snapshot from the wip/ubuntu-xenial branch at
git://git.gnome.org/gnome-software.
- Recognize apt: urls (LP: #1559185)
- Increase the number of displayed reviews from 10 to 30 (LP: #1559284)
- Show version information for non-installed apps (LP: #1564621)
- Show size information for non-installed apps (LP: #1571414)
- Fix sideloading of local .deb files (LP: #1573408)
- Enable the Snappy backend (LP: #1575104)

 -- William Hua   Tue, 26 Apr 2016 14:55:05
+0200

** Changed in: gnome-software (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/1564621

Title:
  Version unknown of not-installed applications, it appears for
  installed ones

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact
  non-installed software don't have a version info

  Test case
  start gnome-software, click on a non installed software, the version should 
be a number instead of "unknown"

  Regression potential
  having this information requires adding infos to items which didn't have 
some, so means more backend work which might slow down things

  --

  Applications show their version unknown in the Details section when
  they are not installed. The version shows up for installed
  applications.

  Version should appear for both not-installed and installed
  applications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1564621/+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 1571414] Re: Size of not-installed applications is "Calculating..." in Details section

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software -
3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1

---
gnome-software (3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1) xenial; 
urgency=medium

  * New upstream snapshot from the wip/ubuntu-xenial branch at
git://git.gnome.org/gnome-software.
- Recognize apt: urls (LP: #1559185)
- Increase the number of displayed reviews from 10 to 30 (LP: #1559284)
- Show version information for non-installed apps (LP: #1564621)
- Show size information for non-installed apps (LP: #1571414)
- Fix sideloading of local .deb files (LP: #1573408)
- Enable the Snappy backend (LP: #1575104)

 -- William Hua   Tue, 26 Apr 2016 14:55:05
+0200

** Changed in: gnome-software (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/1571414

Title:
  Size of not-installed applications is "Calculating..." in Details
  section

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact:
  the details view doesn't display a size for non installed softwares

  Test case:
  open gnome-software, click on an non-installed software, look at the Size 
information, it should have a value

  Regression potential:
  having this information requires adding infos to items which didn't have 
some, so means more backend work which might slow down things

  -

  The size of not-installed applications stays "Calculating..." in the
  Details section, and apparently never changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160415.1.9c08d97.ubuntu-xenial-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 17 23:06:38 2016
  InstallationDate: Installed on 2016-03-29 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1571414/+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 1575104] Re: SRU including some fixes/improvements/enabling snap backend

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software -
3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1

---
gnome-software (3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1) xenial; 
urgency=medium

  * New upstream snapshot from the wip/ubuntu-xenial branch at
git://git.gnome.org/gnome-software.
- Recognize apt: urls (LP: #1559185)
- Increase the number of displayed reviews from 10 to 30 (LP: #1559284)
- Show version information for non-installed apps (LP: #1564621)
- Show size information for non-installed apps (LP: #1571414)
- Fix sideloading of local .deb files (LP: #1573408)
- Enable the Snappy backend (LP: #1575104)

 -- William Hua   Tue, 26 Apr 2016 14:55:05
+0200

** Changed in: gnome-software (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/1575104

Title:
  SRU including some fixes/improvements/enabling snap backend

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  Impact
  gnome-software just landed in Ubuntu this cycle and still has some 
reliability issues

  Test case

  deb backend
  In addition of testing specific fixes listed in the changelog also make sure 
there is no functional regressions.

  snap backend
  the new backend is going to be enable starting with that version, searching 
for a snap (e.g "hello-world") should work, installing it should prompt for u1 
credentials and successfully install

  Regression impact
  the snap backend was not enabled before so that shouldn't create new issues, 
the deb changes are mostly covered by specific bug reports and the other small 
tweaks shouldn't create issues

  -

  The first gnome-software SRU is going to include some fixes and code
  improvements not matching referenced bugs, we also wants to enable the
  snaps backend since it's working well enough for that now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1575104/+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 1546565] Re: Ownership/Permissions of vhost_user sockets for openvswitch-dpdk make them unusable by libvirt/qemu/kvm

[Launchpad Bug Tracker]

This bug was fixed in the package dpdk - 2.2.0-0ubuntu8

---
dpdk (2.2.0-0ubuntu8) xenial; urgency=medium

  * d/p/ubuntu-backport-[36-37] fix virtio issues (LP: #1570195):
- don't let DPDK initialize virtio devices still in use by the kernel
- this avoids conflicts between kernel and dpdk usage of those devices
- an admin now has to unbind/bind devices as on physical hardware
- this is in the dpdk 16.04 release and delta can then be dropped
- d/dpdk-doc.README.Debian update for changes in virtio-pci handling
- d/dpdk.interfaces update for changes in virtio-pci handling
  * d/p/ubuntu-backport-38... fix for memory leak (LP: #1570466):
- call vhost_destroy_device on removing vhost user ports to fix memory leak
- this likely is in the dpdk 16.07 release and delta can then be dropped
  * d/p/ubuntu-fix-vhost-user-socket-permission.patch fox (LP: #1546565):
- when vhost_user sockets are created they are owner:group of the process
- the DPDK api to create those has no way to specify owner:group
- to fix that without breaking the API and potential workaround code in
  consumers of the library like openvswitch 2.6 for example. This patch
  adds an EAL commandline option to specify user:group created vhost_user
  sockets should have.

 -- Christian Ehrhardt   Mon, 25 Apr
2016 11:42:40 +0200

** Changed in: dpdk (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/1546565

Title:
  Ownership/Permissions of vhost_user sockets for openvswitch-dpdk make
  them unusable by libvirt/qemu/kvm

Status in dpdk package in Ubuntu:
  Fix Released
Status in openvswitch-dpdk package in Ubuntu:
  Invalid
Status in dpdk source package in Xenial:
  Fix Released
Status in openvswitch-dpdk source package in Xenial:
  New

Bug description:
  As of today the vhost_user sockets created by openvswitch have root:root file 
ownership.
  In fact creation is actually done by code the DPDK lib, but the path is 
passed to it from openvswitch.

  The API called to DPDK has no notion of ownership/groups.
  It just "inherits" what the current running process has.
  But due to LP:1546556 the process ownership/group can't be changed the usual 
way openvsiwtch would when using dpdk.

  KVM as invoked by libvirt will run under libvirt-qemu:kvm and will
  thereby be unable to access these sockets.

  The current workaround is:
 1. wait after start of openvswitch (only then the sockets exist)
 2. chown all created vhost_iuser sockets that are to be used 
e.g. sudo chown libvirt-qemu /var/run/openvswitch/vhost-user-1 
 3. if one wants to separate vhost_user sockets from the "rest" of 
openvswitch /var/run files use e.g.:
DPDK_OPTS='[...] -vhost_sock_dir /var/run/openvswitch-vhost [...]
 X. this has to be redone every start/restart of oepnvswitch
 Y. if permissions are changed in a way that openvswitch can no more remove 
them on shutdown they won't re-initialize properly on the next start

  That is a severe shortcoming and not really applicable to a supported 
production environment.
  There are discussions ongoing about providing an option to specify 
owner/group/permissions of vhost_user sockets which would solve the issue.
  Unfortunately the patch series is blocked by a wider discussion about moving 
the dpdk configuration to the ovsdb (which makes sense, but stalls the 
acceptance of the patches providing the interface to modify permissions.

  Link to the last thread about moving dpdk config to ovsdb: 
http://comments.gmane.org/gmane.network.openvswitch.devel/59186
  Link to the last thread about making vhost_user socket user/group 
configurable - patch 4&5 of this: 
http://openvswitch.org/pipermail/dev/2015-December/063568.html
  But as mentioned it was decided to get the db config discussion done first.

  It is unsure if the patches once final will make it into openvswitch 2.5 - it 
would be great if they would.
  But even if not they shouldn't appear too much after and we might be able to 
cherry pick them?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1546565/+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 1546565] Re: Ownership/Permissions of vhost_user sockets for openvswitch-dpdk make them unusable by libvirt/qemu/kvm

[Chris J Arges]

** Changed in: openvswitch-dpdk (Ubuntu)
   Status: Triaged => 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/1546565

Title:
  Ownership/Permissions of vhost_user sockets for openvswitch-dpdk make
  them unusable by libvirt/qemu/kvm

Status in dpdk package in Ubuntu:
  Fix Released
Status in openvswitch-dpdk package in Ubuntu:
  Invalid
Status in dpdk source package in Xenial:
  Fix Released
Status in openvswitch-dpdk source package in Xenial:
  New

Bug description:
  As of today the vhost_user sockets created by openvswitch have root:root file 
ownership.
  In fact creation is actually done by code the DPDK lib, but the path is 
passed to it from openvswitch.

  The API called to DPDK has no notion of ownership/groups.
  It just "inherits" what the current running process has.
  But due to LP:1546556 the process ownership/group can't be changed the usual 
way openvsiwtch would when using dpdk.

  KVM as invoked by libvirt will run under libvirt-qemu:kvm and will
  thereby be unable to access these sockets.

  The current workaround is:
 1. wait after start of openvswitch (only then the sockets exist)
 2. chown all created vhost_iuser sockets that are to be used 
e.g. sudo chown libvirt-qemu /var/run/openvswitch/vhost-user-1 
 3. if one wants to separate vhost_user sockets from the "rest" of 
openvswitch /var/run files use e.g.:
DPDK_OPTS='[...] -vhost_sock_dir /var/run/openvswitch-vhost [...]
 X. this has to be redone every start/restart of oepnvswitch
 Y. if permissions are changed in a way that openvswitch can no more remove 
them on shutdown they won't re-initialize properly on the next start

  That is a severe shortcoming and not really applicable to a supported 
production environment.
  There are discussions ongoing about providing an option to specify 
owner/group/permissions of vhost_user sockets which would solve the issue.
  Unfortunately the patch series is blocked by a wider discussion about moving 
the dpdk configuration to the ovsdb (which makes sense, but stalls the 
acceptance of the patches providing the interface to modify permissions.

  Link to the last thread about moving dpdk config to ovsdb: 
http://comments.gmane.org/gmane.network.openvswitch.devel/59186
  Link to the last thread about making vhost_user socket user/group 
configurable - patch 4&5 of this: 
http://openvswitch.org/pipermail/dev/2015-December/063568.html
  But as mentioned it was decided to get the db config discussion done first.

  It is unsure if the patches once final will make it into openvswitch 2.5 - it 
would be great if they would.
  But even if not they shouldn't appear too much after and we might be able to 
cherry pick them?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1546565/+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 1570195] Re: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices

[Launchpad Bug Tracker]

This bug was fixed in the package dpdk - 2.2.0-0ubuntu8

---
dpdk (2.2.0-0ubuntu8) xenial; urgency=medium

  * d/p/ubuntu-backport-[36-37] fix virtio issues (LP: #1570195):
- don't let DPDK initialize virtio devices still in use by the kernel
- this avoids conflicts between kernel and dpdk usage of those devices
- an admin now has to unbind/bind devices as on physical hardware
- this is in the dpdk 16.04 release and delta can then be dropped
- d/dpdk-doc.README.Debian update for changes in virtio-pci handling
- d/dpdk.interfaces update for changes in virtio-pci handling
  * d/p/ubuntu-backport-38... fix for memory leak (LP: #1570466):
- call vhost_destroy_device on removing vhost user ports to fix memory leak
- this likely is in the dpdk 16.07 release and delta can then be dropped
  * d/p/ubuntu-fix-vhost-user-socket-permission.patch fox (LP: #1546565):
- when vhost_user sockets are created they are owner:group of the process
- the DPDK api to create those has no way to specify owner:group
- to fix that without breaking the API and potential workaround code in
  consumers of the library like openvswitch 2.6 for example. This patch
  adds an EAL commandline option to specify user:group created vhost_user
  sockets should have.

 -- Christian Ehrhardt   Mon, 25 Apr
2016 11:42:40 +0200

** Changed in: dpdk (Ubuntu Xenial)
   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/1570195

Title:
  Net tools cause kernel soft lockup after DPDK touched  VirtIO-pci
  devices

Status in dpdk package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in dpdk source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  New

Bug description:
  Guys,

   I'm facing an issue here with both "ethtool" and "ip", while trying
  to manage black-listed by DPDK PCI VirtIO devices.

   You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to
  run those tests

   PCI device example from inside a Xenial guest:

  ---
  # lspci | grep Ethernet
  00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:04.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:05.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:06.0 Ethernet controller: Red Hat, Inc Virtio network device
  ---

  Where "ens3" is the first / default interface, attached to Libvirt's
  "default" network. The "ens4" is reserved for "ethtool / ip" tests
  (attached to another Libvirt's network without IPs or DHCP), "ens5"
  will be "dpdk0" and "ens6" "dpdk1"...

  ---
   *** How it works?

   1- For example, try to enable multi-queue on DPDK's devices, boot
  your Xenial guest, and run:

   ethtool -L ens5 combined 4
   ethtool -L ens6 combined 4

   2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it
  up.

   https://help.ubuntu.com/16.04/serverguide/DPDK.html

   service openvswitch-switch stop
   service dpdk stop

   OVS DPDK Options (/etc/default/openvswitch-switch):

  --
  DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist 
:00:03.0,:00:04.0'
  --

   service dpdk start
   service openvswitch-switch start

   - Enable multi-queue on OVS+DPDK inside of the VM:

   ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4
   ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00

   * Multi-queue apparently works! ovs-vswitchd consumes more that 100%
  of CPU, meaning that it multi-queue is there...

   *** Where it fails?

   1- Reboot the VM and try to run ethtool again (or go straight to 2
  below):

   ethtool -L ens5 combined 4

   2- Try to fire up ens4:

   ip link set dev ens4 up

  
   # FAIL! Both commands hangs, consuming 100% of guest's CPU...

   So, it looks like a Linux fault, because it is "allowing" the DPDK
  VirtIO App (a user land App), to interfere with kernel devices in a
  strange way...

  Best,
  Thiago

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 14 00:35 seq
   crw-rw 1 root audio 116, 33 Apr 14 00:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  Date: Thu Apr 14 01:27:27 2016
  HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de
  InstallationDate: Installed on 2016-04-07 (7 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160406)
  IwConfig: 

[Group.of.nepali.translators] [Bug 1570195] Re: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices

[Chris J Arges]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: dpdk (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/1570195

Title:
  Net tools cause kernel soft lockup after DPDK touched  VirtIO-pci
  devices

Status in dpdk package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in dpdk source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  New

Bug description:
  Guys,

   I'm facing an issue here with both "ethtool" and "ip", while trying
  to manage black-listed by DPDK PCI VirtIO devices.

   You'll need an Ubuntu Xenial KVM guest, with 4 VirtIO vNIC cards, to
  run those tests

   PCI device example from inside a Xenial guest:

  ---
  # lspci | grep Ethernet
  00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:04.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:05.0 Ethernet controller: Red Hat, Inc Virtio network device
  00:06.0 Ethernet controller: Red Hat, Inc Virtio network device
  ---

  Where "ens3" is the first / default interface, attached to Libvirt's
  "default" network. The "ens4" is reserved for "ethtool / ip" tests
  (attached to another Libvirt's network without IPs or DHCP), "ens5"
  will be "dpdk0" and "ens6" "dpdk1"...

  ---
   *** How it works?

   1- For example, try to enable multi-queue on DPDK's devices, boot
  your Xenial guest, and run:

   ethtool -L ens5 combined 4
   ethtool -L ens6 combined 4

   2- Install openvswitch-switch-dpdk configure DPDK and OVS and fire it
  up.

   https://help.ubuntu.com/16.04/serverguide/DPDK.html

   service openvswitch-switch stop
   service dpdk stop

   OVS DPDK Options (/etc/default/openvswitch-switch):

  --
  DPDK_OPTS='--dpdk -c 0x1 -n 4 --socket-mem 1024 --pci-blacklist 
:00:03.0,:00:04.0'
  --

   service dpdk start
   service openvswitch-switch start

   - Enable multi-queue on OVS+DPDK inside of the VM:

   ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4
   ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0xff00

   * Multi-queue apparently works! ovs-vswitchd consumes more that 100%
  of CPU, meaning that it multi-queue is there...

   *** Where it fails?

   1- Reboot the VM and try to run ethtool again (or go straight to 2
  below):

   ethtool -L ens5 combined 4

   2- Try to fire up ens4:

   ip link set dev ens4 up

  
   # FAIL! Both commands hangs, consuming 100% of guest's CPU...

   So, it looks like a Linux fault, because it is "allowing" the DPDK
  VirtIO App (a user land App), to interfere with kernel devices in a
  strange way...

  Best,
  Thiago

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 14 00:35 seq
   crw-rw 1 root audio 116, 33 Apr 14 00:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  Date: Thu Apr 14 01:27:27 2016
  HibernationDevice: RESUME=UUID=833e999c-e066-433c-b8a2-4324bb8d56de
  InstallationDate: Installed on 2016-04-07 (7 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160406)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=9911604e-353b-491f-a0a9-804724350592 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-wily
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-wily:cvnQEMU:ct1:cvrpc-i440fx-wily:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.versio

[Group.of.nepali.translators] [Bug 1570466] Re: Adding/removing ports leaks memory in dpdk

[Launchpad Bug Tracker]

This bug was fixed in the package dpdk - 2.2.0-0ubuntu8

---
dpdk (2.2.0-0ubuntu8) xenial; urgency=medium

  * d/p/ubuntu-backport-[36-37] fix virtio issues (LP: #1570195):
- don't let DPDK initialize virtio devices still in use by the kernel
- this avoids conflicts between kernel and dpdk usage of those devices
- an admin now has to unbind/bind devices as on physical hardware
- this is in the dpdk 16.04 release and delta can then be dropped
- d/dpdk-doc.README.Debian update for changes in virtio-pci handling
- d/dpdk.interfaces update for changes in virtio-pci handling
  * d/p/ubuntu-backport-38... fix for memory leak (LP: #1570466):
- call vhost_destroy_device on removing vhost user ports to fix memory leak
- this likely is in the dpdk 16.07 release and delta can then be dropped
  * d/p/ubuntu-fix-vhost-user-socket-permission.patch fox (LP: #1546565):
- when vhost_user sockets are created they are owner:group of the process
- the DPDK api to create those has no way to specify owner:group
- to fix that without breaking the API and potential workaround code in
  consumers of the library like openvswitch 2.6 for example. This patch
  adds an EAL commandline option to specify user:group created vhost_user
  sockets should have.

 -- Christian Ehrhardt   Mon, 25 Apr
2016 11:42:40 +0200

** Changed in: dpdk (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/1570466

Title:
  Adding/removing ports leaks memory in dpdk

Status in dpdk package in Ubuntu:
  Fix Released
Status in dpdk source package in Xenial:
  Fix Released

Bug description:
  I set up a nicely working OVS-DPDK with KVM Guests.
  Then in a loop I
 - add up to 512 ports
 - test connectivity
 - remove up to 512 ports

  The effective error is like the issues discussed upstream about >1023 file 
descriptors - OVS-DPDK crashes due to that.
  A lot in the log afterwards are just follow on issues.

  But the problem of this bug is that there has to be some sort of leak of file 
descriptors (or something else depending on analysis).
  Because one would expect that adding/removing the same amount of ports should 
not exceed any "more" of a limit than in the first iteration.

  Of 12 planned iterations in 2 of 2 tries I now always failed at iteration 6.
  So I hope it is rather reproducible and will start debugging it.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: openvswitch-dpdk
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: kvm libvirtd
  _MarkForUpload: True
  modified.conffile..etc.dpdk.dpdk.conf: [modified]
  modified.conffile..etc.dpdk.interfaces: [modified]
  mtime.conffile..etc.dpdk.dpdk.conf: 2016-04-14T13:58:58.618313
  mtime.conffile..etc.dpdk.interfaces: 2016-04-14T13:58:58.766313

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1570466/+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 1506187] Re: [SRU] Azure: cloud-init should use VM unique ID

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.6.3-0ubuntu1.25

---
cloud-init (0.6.3-0ubuntu1.25) precise; urgency=medium

  * Microsoft Azure: Use stable VM instance ID over SharedConfig.xml
(LP: #1506187)
- d/patches/lp-1506187-azure_use_unique_vm_id.patch: use DMI data for
  the stable VM instance ID
- d/cloud-init.preinst: migrate existing instances to stable VM instance
  ID on upgrade from prior versions of cloud-init.

 -- Daniel Watkins   Mon, 25 Apr 2016
16:53:07 -0400

** Changed in: cloud-init (Ubuntu Precise)
   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/1506187

Title:
  [SRU] Azure: cloud-init should use VM unique ID

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Precise:
  Fix Released
Status in cloud-init source package in Trusty:
  Fix Released
Status in cloud-init source package in Vivid:
  Won't Fix
Status in cloud-init source package in Wily:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
  SRU JUSTIFICATION

  [IMPACT] On Azure, the InstanceID is currently detected via a fabric
  provided XML file. With the new CRP stack, this ID is not guaranteed
  to be stable. As a result instances may go re-provision upon reboot.

  [FIX] Use DMI data to detect the instance ID and migrate existing
  instances to the new ID.

  [REGRESSION POTENTIAL] The fix is both in the cloud-init code and in
  the packaging. If the instance ID is not properly migrated, then a
  reboot may trigger re-provisioning.

  [TEST CASES]
  1. Boot instance on Azure.
  2. Apply cloud-init from -proposed. A migration message should apply.
  3. Get the new instance ID:
 $ sudo cat /sys/class/dmi/id/product_uuid
  4. Confirm that /var/lib/cloud/instance is a symlink to 
/var/lib/cloud/instances/
  5. Re-install cloud-init and confirm that migration message is NOT displayed.

  [TEST CASE 2]
  1. Build new cloud-image from -proposed
  2. Boot up instance
  3. Confirm that /sys/class/dmi/id/product_uuid is used to get instance ID 
(see /var/log/cloud-init.log)

  
  [ORIGINAL REPORT]
  The Azure datasource currently uses the InstanceID from the SharedConfig.xml 
file.  On our new CRP stack, this ID is not guaranteed to be stable and could 
change if the VM is deallocated.  If the InstanceID changes then cloud-init 
will attempt to reprovision the VM, which could result in temporary loss of 
access to the VM.

  Instead cloud-init should switch to use the VM Unique ID, which is
  guaranteed to be stable everywhere for the lifetime of the VM.  The VM
  unique ID is explained here: https://azure.microsoft.com/en-us/blog
  /accessing-and-using-azure-vm-unique-id/

  In short, the unique ID is available via DMI, and can be accessed with
  the command 'dmidecode | grep UUID' or even easier via sysfs in the
  file "/sys/devices/virtual/dmi/id/product_uuid".

  Steve

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1506187/+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 1569581] Re: snapd no longer detects apparmor changes on upgrade

[Jamie Strandboge]

Ok, I've added an apparmor task and assigned to me. Leaving the snappy
tasks open for "we will re-load all profiles for a specific snap each
time something in that snap changes *AND* we promise to detect changes
to the internal templates built into snappy" where I understand the
first part is done but the changes to internal templates is not.
Assigning zyga for the time being-- please adjust as necessary.

** Also affects: apparmor (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: snapd (Ubuntu)
   Status: New => Triaged

** Changed in: snapd (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: apparmor (Ubuntu Xenial)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: apparmor (Ubuntu)
   Status: New => Triaged

** Changed in: apparmor (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: snappy
 Assignee: (unassigned) => Zygmunt Krynicki (zyga)

** Changed in: apparmor (Ubuntu)
   Importance: Undecided => High

** Changed in: apparmor (Ubuntu Xenial)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1569581

Title:
  snapd no longer detects apparmor changes on upgrade

Status in Snappy:
  Triaged
Status in apparmor package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  Triaged
Status in apparmor source package in Xenial:
  Triaged
Status in snapd source package in Xenial:
  Triaged

Bug description:
  snappy in 16.04 used to compare /usr/share/snappy/security-policy-
  version and /var/lib/snappy/security-policy-version on boot to see if
  the apparmor package changed and therefore if it needed to regenerate
  all snap policy. This functionality was recently removed with nothing
  added to replace it.

  snapd must have a means to detect changes to the parser or the
  abstractions which the snap may #include, otherwise we cannot deliver
  parser and policy fixes from apparmor to installed snaps. It is fine
  to use a different method than what we had before, but we need to have
  something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1569581/+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 1577739] Re: samba security regression tracking bug

[Launchpad Bug Tracker]

This bug was fixed in the package samba - 2:4.3.9+dfsg-0ubuntu0.14.04.1

---
samba (2:4.3.9+dfsg-0ubuntu0.14.04.1) trusty-security; urgency=medium

  * SECURITY REGRESSION: Updated to 4.3.9 to fix multiple regressions in
the previous security updates. (LP: #1577739)
- debian/control: bump tevent Build-Depends to 0.9.28.

 -- Marc Deslauriers   Tue, 03 May 2016
09:58:20 -0400

** Changed in: samba (Ubuntu Trusty)
   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/1577739

Title:
  samba security regression tracking bug

Status in samba package in Ubuntu:
  Confirmed
Status in samba source package in Precise:
  Fix Released
Status in samba source package in Trusty:
  Fix Released
Status in samba source package in Wily:
  Fix Released
Status in samba source package in Xenial:
  Fix Released
Status in samba source package in Yakkety:
  Confirmed

Bug description:
  The samba fixes for badlock introduced a number of regressions.

  This bug tracks the update to 4.3.9 and the further backported fixes
  into 3.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1577739/+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 1577739] Re: samba security regression tracking bug

[Launchpad Bug Tracker]

This bug was fixed in the package samba - 2:3.6.25-0ubuntu0.12.04.3

---
samba (2:3.6.25-0ubuntu0.12.04.3) precise-security; urgency=medium

  * SECURITY REGRESSION: Add additional backported commits to fix
regressions in the previous security updates. (LP: #1577739)
- debian/patches/security_trailer_regression.patch: fix a regression
  verifying the security trailer in source3/rpc_server/srv_pipe.c.
- debian/patches/bug9669_regression.patch: fix a crash when running
  net rpc join against an older Samba PDC in
  source3/rpc_client/cli_pipe.c.
- debian/patches/netlogon_credentials_regression.patch: fix updating
  netlogon credentials in source3/rpc_client/cli_pipe.c.
- Thanks to Andreas Schneider for the additional backports to
  Samba 3.6!

 -- Marc Deslauriers   Tue, 03 May 2016
12:51:09 -0400

** Changed in: samba (Ubuntu Precise)
   Status: Confirmed => Fix Released

** Changed in: samba (Ubuntu Wily)
   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/1577739

Title:
  samba security regression tracking bug

Status in samba package in Ubuntu:
  Confirmed
Status in samba source package in Precise:
  Fix Released
Status in samba source package in Trusty:
  Confirmed
Status in samba source package in Wily:
  Fix Released
Status in samba source package in Xenial:
  Fix Released
Status in samba source package in Yakkety:
  Confirmed

Bug description:
  The samba fixes for badlock introduced a number of regressions.

  This bug tracks the update to 4.3.9 and the further backported fixes
  into 3.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1577739/+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 1577739] Re: samba security regression tracking bug

[Launchpad Bug Tracker]

This bug was fixed in the package samba - 2:4.3.9+dfsg-0ubuntu0.15.10.1

---
samba (2:4.3.9+dfsg-0ubuntu0.15.10.1) wily-security; urgency=medium

  * SECURITY REGRESSION: Updated to 4.3.9 to fix multiple regressions in
the previous security updates. (LP: #1577739)
- debian/control: bump tevent Build-Depends to 0.9.28.

 -- Marc Deslauriers   Tue, 03 May 2016
09:55:17 -0400

** Changed in: samba (Ubuntu Xenial)
   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/1577739

Title:
  samba security regression tracking bug

Status in samba package in Ubuntu:
  Confirmed
Status in samba source package in Precise:
  Fix Released
Status in samba source package in Trusty:
  Confirmed
Status in samba source package in Wily:
  Fix Released
Status in samba source package in Xenial:
  Fix Released
Status in samba source package in Yakkety:
  Confirmed

Bug description:
  The samba fixes for badlock introduced a number of regressions.

  This bug tracks the update to 4.3.9 and the further backported fixes
  into 3.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1577739/+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 1577905] Re: Dell TB15 audio is distorted

[Tim Gardner]

via 4.2.8-ckt9 stable

** Changed in: linux (Ubuntu Wily)
   Status: New => Fix Committed

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: 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/1577905

Title:
  Dell  TB15 audio is distorted

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  On the Dell TB15 and Dell WD15 docks, analogue audio output is
  distorted.  This is because of a missing driver quirk on docks.

  It has been fixed upstream here.
  
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

  Please backport it into Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577905/+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 1577905] Re: Dell TB15 audio is distorted

[Tim Gardner]

v4.6-rc4~18^2~2

** Changed in: linux (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/1577905

Title:
  Dell  TB15 audio is distorted

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  On the Dell TB15 and Dell WD15 docks, analogue audio output is
  distorted.  This is because of a missing driver quirk on docks.

  It has been fixed upstream here.
  
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

  Please backport it into Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577905/+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 1577905] Re: Dell TB15 audio is distorted

[Tim Gardner]

via 3.19.8-ckt20 stable

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Vivid)
   Status: New => Fix Committed

** Also affects: linux (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/1577905

Title:
  Dell  TB15 audio is distorted

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  New
Status in linux source package in Xenial:
  Fix Released

Bug description:
  On the Dell TB15 and Dell WD15 docks, analogue audio output is
  distorted.  This is because of a missing driver quirk on docks.

  It has been fixed upstream here.
  
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

  Please backport it into Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577905/+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 1577905] Re: Dell TB15 audio is distorted

[Tim Gardner]

Soon to be released in Ubuntu-4.4.0-22.38 (via v4.4.8 stable)

** Changed in: linux (Ubuntu Xenial)
   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/1577905

Title:
  Dell  TB15 audio is distorted

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  On the Dell TB15 and Dell WD15 docks, analogue audio output is
  distorted.  This is because of a missing driver quirk on docks.

  It has been fixed upstream here.
  
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

  Please backport it into Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577905/+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 1554848] Re: Please randomise automatic updates over a longer period

[Haw Loeung]

** Also affects: apt (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Trusty)
   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/1554848

Title:
  Please randomise automatic updates over a longer period

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  New
Status in unattended-upgrades source package in Trusty:
  New
Status in apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released

Bug description:
  Load on the main Ubuntu archive servers is rather peakish, and tends
  to create a traffic peak on our Internet links at fairly regular times
  each day, preventing customers from accessing the archive.  This
  impacts the cloud archive mirrors using the ubuntu-repository-cache
  charm also, because they are hitting a squid cache which is backed by
  the main archive.  This effect will be even more pronounced under the
  recently-announced automatic update policy for xenial.

  One solution which would alleviate this to some extent would be to
  spread the load over a longer period by increasing the random sleep
  time in the daily update script from 30 minutes to, say, 1-2 hours.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1554848/+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 1565567] Re: segv in sudo_getgrgid

[Marc Deslauriers]

** Also affects: sudo (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: sudo (Ubuntu Xenial)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1565567

Title:
  segv in sudo_getgrgid

Status in sudo package in Ubuntu:
  Confirmed
Status in sudo source package in Xenial:
  Confirmed

Bug description:
  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1565567/+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 1565567] Re: segv in sudo_getgrgid

[Marc Deslauriers]

Thanks for the detailed analysis.

I have uploaded a package for testing with the minimal fix in the
following PPA:

https://launchpad.net/~mdeslaur/+archive/ubuntu/testing

Once it's finished building, could someone please check if the package
resolves their issue? If so, I'll upload it to proposed as an SRU.

Thanks!


** Changed in: sudo (Ubuntu)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: sudo (Ubuntu Xenial)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Bug watch added: bugzilla.sudo.ws/ #743
   http://bugzilla.sudo.ws/show_bug.cgi?id=743

** Also affects: sudo via
   http://bugzilla.sudo.ws/show_bug.cgi?id=743
   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/1565567

Title:
  segv in sudo_getgrgid

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Confirmed
Status in sudo source package in Xenial:
  Confirmed

Bug description:
  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

To manage notifications about this bug go to:
https://bugs.launchpad.net/sudo/+bug/1565567/+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 1557115] Re: [regression] RadioTray won't launch without python-xdg

[Alex10336]

** Also affects: radiotray (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801232
   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/1557115

Title:
  [regression] RadioTray won't launch without python-xdg

Status in GTK+:
  New
Status in One Hundred Papercuts:
  Confirmed
Status in radiotray package in Ubuntu:
  Triaged
Status in radiotray source package in Xenial:
  Triaged
Status in radiotray package in Debian:
  Unknown

Bug description:
  Although I've been previously running RadioTray in Ubuntu 16.04, it
  has recently become unlaunchable.

  Typically when you launch RadioTray, an indicator appears on the top-
  right-panel (left of the clock), and you are able to select a radio-
  station to stream.

  Now, when you launch it, nothing apparently happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: radiotray 0.7.3-5ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 14 13:35:53 2016
  InstallationDate: Installed on 2016-03-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: radiotray
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1557115/+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 1512347] Re: invalid sources.list generated from reading apt-setup/local0/repository

[Colin Watson]

** Also affects: base-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: base-installer (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: base-installer (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: base-installer (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.1

-- 
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/1512347

Title:
  invalid sources.list generated from reading apt-
  setup/local0/repository

Status in base-installer package in Ubuntu:
  Fix Released
Status in base-installer source package in Xenial:
  Triaged

Bug description:
  hi,
  it looks like configure_apt from library.sh will add the contents of 
apt-setup/local0/repository verbatim to the sources file. This works only if 
the repository is prefixed with "deb ", which for apt-setup is optional. Not 
using a repository prefixed with "deb" will result in an invalid sources.list 
file. See also https://phabricator.wikimedia.org/T94177 and 
https://gerrit.wikimedia.org/r/250380

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1512347/+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 1571574] Re: 3G icon missing in network-manager-applet

[Ara Pulido]

** Also affects: network-manager-applet (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/1571574

Title:
  3G icon missing in network-manager-applet

Status in Network Manager Applet:
  New
Status in OEM Priority Project:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed
Status in network-manager-applet source package in Xenial:
  New

Bug description:
  After establishing a 3G connection, the icon shown in system tray
  should be a 3G indicator to indicate that 3G is connected.

  However, in Xenial there is no 3G icon at all.
  After 3G connection is established, it remains as the previous icon displayed.
  (e.g. 
  If no other connection was established before 3G connection was made, then 
the icon is a "hollow fan shape" after connecting to 3G.
  If wifi was connected before 3G connection was made, then the icon after 3G 
connection shows a wifi icon.)

  network-manager: 1.1.93-0ubuntu3
  OS: Xenial daily (2016 Apr. 15)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1571574/+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