[Group.of.nepali.translators] [Bug 1578398] Re: ImageMagick Security Issue: CVE-2016-3714

[Jeremy Bicha]

** Bug watch added: Debian Bug tracker #823542
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823542

** Also affects: imagemagick (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823542
   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/1578398

Title:
  ImageMagick Security Issue: CVE-2016-3714

Status in imagemagick package in Ubuntu:
  Confirmed
Status in imagemagick source package in Precise:
  Confirmed
Status in imagemagick source package in Trusty:
  Confirmed
Status in imagemagick source package in Wily:
  Confirmed
Status in imagemagick source package in Xenial:
  Confirmed
Status in imagemagick source package in Yakkety:
  Confirmed
Status in imagemagick package in Debian:
  Unknown

Bug description:
  Imagemagick Announce on Discourse: https://www.imagemagick.org
  /discourse-server/viewtopic.php?f=4=29588

  https://imagetragick.com headlined: ImageMagick Is On Fire —
  CVE-2016–3714

  It would be great if this can be fixed quickly, to keep Ubuntu users
  safe.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: imagemagick 8:6.8.9.9-7ubuntu5
  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: KDE
  Date: Wed May  4 14:28:39 2016
  InstallationDate: Installed on 2015-08-11 (267 days ago)
  InstallationMedia: It
  SourcePackage: imagemagick
  UpgradeStatus: Upgraded to xenial on 2016-03-27 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1578398/+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 1573897] Re: Workspace Switcher Shows an Empty Space in Left Side when Launcher is Moved to Bottom

[Mathew Hodson]

** Branch unlinked: lp:~hikiko/unity/unity.scale-launcher-at-the-bottom

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

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

** Changed in: compiz (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Workspace Switcher Shows an Empty Space in Left Side when Launcher is
  Moved to Bottom

Status in compiz package in Ubuntu:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Committed

Bug description:
  Workspace Switcher mode shows an empty space in left side, where the
  Launcher was previously located, when Launcher is moved to bottom.

  See the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Apr 23 10:11:18 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Core Processor Integrated Graphics 
Controller [1558:5125]
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 003: ID 0480:a007 Toshiba America Inc External Disk USB 3.0
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: CLEVO Co. E512xQ/E4129
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=d06a5306-c849-43c7-bf3b-dc8daeaf511f ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2011
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: CALPELLACRB.86C..X.00
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: E512xQ/E4129
  dmi.board.vendor: CLEVO Co.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO Co.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrCALPELLACRB.86C..X.00:bd03/02/2011:svnCLEVOCo.:pnE512xQ/E4129:pvrNotApplicable:rvnCLEVOCo.:rnE512xQ/E4129:rvrNotApplicable:cvnCLEVOCo.:ct9:cvrN/A:
  dmi.product.name: E512xQ/E4129
  dmi.product.version: Not Applicable
  dmi.sys.vendor: CLEVO Co.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr 23 08:07:09 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 395 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1573897/+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 1562348] Re: [Bottom launcher] Maximized windows in workspace switcher are displayed with gap on the bottom

[Mathew Hodson]

** Branch linked: lp:~hikiko/compiz/compiz.scale-bottomYoffset

** Branch linked: lp:~hikiko/unity/unity.scale-launcher-at-the-bottom

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

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

** Changed in: compiz (Ubuntu)
   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/1562348

Title:
  [Bottom launcher] Maximized windows in workspace switcher are
  displayed with gap on the bottom

Status in compiz package in Ubuntu:
  Fix Committed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Committed

Bug description:
  Maximized window should fill in whole space of the workspace in
  workspace switcher. But unfortunately with launcher on the bottom it
  doesn't do that.

  It displays with gap on the bottom so it doesn't take into account
  that there is no launcher in that view.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1562348/+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 762349] Re: [SRU] Difficult to distinguish which tab is selected

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
14.04+16.04.20160415-0ubuntu2

---
ubuntu-themes (14.04+16.04.20160415-0ubuntu2) xenial; urgency=medium

  [ Will Cooke ]
  * Adds Terminal specific CSS to change tab colours making it easier to
distinguish the current selected tab from the others. Design have reviewed
and ack'd. LP: #762349

  [ Iain Lane ]
  * Update Vcs-Bzr for 16.04

 -- Iain Lane   Tue, 24 May 2016 10:54:25 +0100

** Changed in: ubuntu-themes (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/762349

Title:
  [SRU] Difficult to distinguish which tab is selected

Status in Ayatana Design:
  Fix Committed
Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Released

Bug description:
  [Impact]
   * When a user opens multiple tabs in GNOME terminal all tabs are styled in a 
*very* visually similar manner.  This makes it very hard to distinguish between 
the current active tab and all the others and on a HiDPI screen pretty much 
impossible.

  * This fix has been ack'd by design and was targeted for X but didn't
  get reviewed and OK'd in time.  Design team have approved this
  styling.

  * This bug is fixed by extending the CSS specifically for Terminal
  (i.e. no other applications are affected) giving the active tab a
  darker background colour (using only theme defined colours) and
  reworks the borders around the tabs to remove the graduated image
  borders that only look right on a light coloured background.  Changes
  have been made for both Ambiance and Radiance.

  [Test Case]
   * On a stock 16.04 install open GNOME Terminal (ctrl-alt-t)
   * Open five new tabs (ctrl-shift-t)
   * Click on the tab in the middle
   * Note that it is hard to see at a glance which tab is currently selected
   * Close Terminal and all open tabs.
   * Install the patched theme
   * Open Terminal and open five new tabs
   * Click on the tab in the middle and note that it takes on a light grey 
background compared to the unselected tabs which are dark grey.

  [Regression Potential]
   * The patch only addresses tabs that are placed at the top of the window. 
However this is the only option in Terminal, so should not cause any problems.
   * There is a work-around to match the "actions bar" (the bit with the 
dropdown selector and + button).  This bug is supposed to be fixed in v3.20 and 
could be removed.  This is commented in the CSS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/762349/+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 1574745] Re: Missing symlinks to match locales

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice-dictionaries -
1:5.1.0-1ubuntu2.2

---
libreoffice-dictionaries (1:5.1.0-1ubuntu2.2) xenial; urgency=medium

  * Modifications due to possible file conflicts which were identified
through Debian bug reports (see comment #7-9 in LP: #1574745):
- d/helper.py, d/control:
  Add conflicts fields to hunspell-es and hyphen-lt to address
  conflicts which surfaced as a result of the file renaming.
- d/hunspell-kmr.links:
  Drop ku_TR.* links for now, since they conflict with files
  installed by myspell-ku.

 -- Gunnar Hjalmarsson   Sun, 22 May 2016 04:40:00
+0200

** Changed in: libreoffice-dictionaries (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/1574745

Title:
  Missing symlinks to match locales

Status in libreoffice-dictionaries package in Ubuntu:
  Fix Released
Status in libreoffice-dictionaries source package in Xenial:
  Fix Released
Status in libreoffice-dictionaries package in Debian:
  Fix Released

Bug description:
  [Impact]

  Dictionaries like

  /usr/share/hunspell/es_ANY.aff
  /usr/share/hunspell/es_ANY.dic

  and

  /usr/share/hyphen/hyph_sv.dic

  are not recognized by LibreOffice, since their names don't include
  country codes. The proposed uploads in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/lo-dicts-symlinks

  renames such files, and also adds symlinks in some cases for locales
  with other country codes but the 'main' locale for a language.

  [Test Case]

  Example:

  * Install the Swedish language via Language Support

  * Start libreoffice with a Swedish locale
LC_CTYPE=sv_SE.UTF-8 libreoffice --writer

  * Find that hyphenation is not available

  [Regression Potential]

  There is a drawback with this fix: For e.g. Spanish and Arabic users
  the symlinks will add items in the spellcheck menus of other
  applications but LibreOffice, where it would have worked without those
  symlinks. OTOH, this is the way it has been handled in Ubuntu up to
  15.10, so the fix basically restores the previous behavior.

  Other than that, the regression risk is low. This is only about files
  (including symlinks) in the /usr/share/{hunspell,hyphen,mythes}
  directories with limited affect on the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1574745/+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 1566201] Re: /usr/bin/apturl-gtk:AttributeError:/usr/bin/apturl-gtk@47:main:enableChannel:doEnableChannel

[Launchpad Bug Tracker]

This bug was fixed in the package apturl - 0.5.2ubuntu11.1

---
apturl (0.5.2ubuntu11.1) xenial; urgency=medium

  * Fix common crashes (AttributeError in doEnableChannel), due to changes
in apt_pkg API, etc. (LP: #1566201)

  [ Brian Murray ]
  * Port to proper apt_pkg APIs.

  [ Mathieu Trudel-Lapierre ]
  * Override the start_available and start_error functions from Aptdaemon
backend correctly to match the passed parameters.
  * Use pkexec rather than gksu to do our external calls to apt-key, install,
and software-properties, etc; since they need admin privileges.

 -- Mathieu Trudel-Lapierre   Tue, 24 May 2016
12:00:20 -0400

** Changed in: apturl (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/1566201

Title:
  /usr/bin/apturl-gtk:AttributeError:/usr/bin/apturl-
  gtk@47:main:enableChannel:doEnableChannel

Status in apturl package in Ubuntu:
  Fix Committed
Status in apturl source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Users may not be able to successfully install packages using apturl, 
especially from other channels from the release archive (ie. using the partner 
archive).

  [Test case]
  1) apturl-gtk "apt:adobe-flashplugin?channel=xenial-partner"

  [Regression potential]
  Possible regressions include a failure to see a package as not being virtual 
due to not finding the package in the right specified location; also, it may be 
possible for the UI interface to be shown as completely insensitive (can't be 
clicked) in the event of a regression.

  --

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apturl.  This problem was most recently seen with version
  0.5.2ubuntu11, the problem page at
  https://errors.ubuntu.com/problem/7296934db3911cad4d00829c2f458a532da30d62
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apturl/+bug/1566201/+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 1532226] Re: No menu bar in gtk apps on fresh boot

[Launchpad Bug Tracker]

This bug was fixed in the package bamf -
0.5.3~bzr0+16.04.20160523-0ubuntu1

---
bamf (0.5.3~bzr0+16.04.20160523-0ubuntu1) xenial; urgency=medium

  * bamfdaemon-dbus-runner: don't try to start again if already running
(LP: #1581896, #1532226)

 -- Marco Trevisan (Treviño)   Mon, 23 May 2016 18:05:13
+

** Changed in: bamf (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/1532226

Title:
  No menu bar in gtk apps on fresh boot

Status in Release Notes for Ubuntu:
  Fix Released
Status in bamf package in Ubuntu:
  Fix Released
Status in bamf source package in Xenial:
  Fix Released

Bug description:
  Seen here in fresh 16.04 install using 01/07/16 image.
  Around 35% of fresh boots or restarts results in no menus in unity panel for 
most apps, notable exceptions are firefox & thunderbird
  A log out/in restores functionality.
  When this occurs there is nothing in any of the ~/.cache/upstart logs of 
obvious note

  Test case:
  fresh install, no changes
  Do a number of restarts from system settings, using either restart > restart 
or shutdown > restart, here randomly picked one or the other
  What happens here: 
  around 35% of the time the login has no menus in the unity panel for most 
apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1532226/+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 1578144] Re: cacti and cacti-spine are not compatible with MySQL 5.7 default sql_mode

[Launchpad Bug Tracker]

This bug was fixed in the package cacti-spine - 0.8.8b-1ubuntu1.1

---
cacti-spine (0.8.8b-1ubuntu1.1) xenial; urgency=medium

  * Add make_spine_sql_mode-strict_compatible.patch to enable cacti-spine
to work with the default settings of MySQL 5.7 (LP: #1578144)

 -- Paul Gevers   Sat, 14 May 2016 21:24:30 +0200

** Changed in: cacti-spine (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/1578144

Title:
  cacti and cacti-spine are not compatible with MySQL 5.7 default
  sql_mode

Status in Cacti:
  Incomplete
Status in cacti package in Ubuntu:
  Fix Released
Status in cacti-spine package in Ubuntu:
  Fix Released
Status in cacti source package in Xenial:
  Fix Released
Status in cacti-spine source package in Xenial:
  Fix Released
Status in cacti source package in Yakkety:
  Fix Released
Status in cacti-spine source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * When cacti and/or cacti-spine is used with the MySQL server on the same
     host and without modifications to the MySQL global setting, cacti fails to
     install and (e.g. for installations that upgraded) cacti and cacti-spine
     fail to run properly since MySQL 5.7 became the default (shortly before
     the Xenial release).

   * This bug renders the cacti and cacti-spine packages nearly useless for
     most users.

   * The fix forces the sql_mode NO_ZERO_DATE setting in the MySQL connection
     to be unset which enables the MySQL INSERT and UPDATE commands that
     involve the date "-00-00" to succeed.

  [Test Case]

   [ Verify issue ]

   * Install cacti on a xenial system with mysql-server installed, and see it
     fails during the population of the database via dbconfig-common. If the
     dbconfig-common defaults are choosen for the error handling (abort), the
     package fails to install.

   * Install cacti on a wily system with mysql-server installed. Connect to
     http://localhost/cacti, pass through the install process (i.e. hit "Ok",
 log in with admin/admin credentials and provide a new admin password).
 Then upgrade to xenial and see that every five minutes a line like the
 following is added to the /var/log/cacti/cacti.log file:

     05/13/2016 06:55:02 PM - CMDPHP: Poller[0] ERROR: A DB Exec
  Failed!, Error:'1292', SQL:"INSERT INTO poller_time (poller_id, pid,
  start_time, end_time) VALUES (0, 4044, NOW(), '-00-00 00:00:00')'

   * Install cacti-spine on a wily system with mysql-server installed. Connect
 to http://localhost/cacti, pass through the install process (i.e. hit
 "Ok", log in with admin/admin credentials and provide a new admin
 password). Now
     navigate to the settings item, select the poller tab and change the field
     "The poller type to use. This setting will take effect at next polling
     interval." to "spine". Then upgrade to xenial and see that every five
     minutes a line like the following is added to the /var/log/cacti/cacti.log
     file:

     05/13/2016 07:50:00 PM - SPINE: Poller[0] ERROR: SQL Failed!
  Error:'1292', Message:'Incorrect datetime value: '-00-00 00:00:00'
  for column 'end_time' at row 1', SQL Fragment:'INSERT INTO poller_time
  (poller_id, pid, start_time, end_time) VALUES (0, 4685, NOW(),
  '-00-00 00:00:00')'

   [ Verify fix ]

   * Install the proposed cacti package on a xenial system with mysql-server
     installed and very that it installs cleanly.

   * Same as previous point, but also connect to http://localhost/cacti, pass
     through the install process (i.e. hit "Ok", log in with admin/admin
     credentials and provide a new admin password). Verify that you see lines
     like the following appear every five minutes

     05/13/2016 07:09:59 PM - SYSTEM STATS: Time:298.6378 Method:cmd.php
  Processes:1 Threads:N/A Hosts:2 HostsPerProcess:2 DataSources:5
  RRDsProcessed:5

     and that lines like the following line are absent:

     05/13/2016 06:55:02 PM - CMDPHP: Poller[0] ERROR: A DB Exec
  Failed!, Error:'1292', SQL:"INSERT INTO poller_time (poller_id, pid,
  start_time, end_time) VALUES (0, 4044, NOW(), '-00-00 00:00:00')'

   * Install cacti-spine on a xenial system with mysql-server installed.
 Connect to http://localhost/cacti, pass through the install process (i.e.
 hit "Ok", log in with admin/admin credentials and provide a new admin
 password). Now
     navigate to the settings item, select the poller tab and change the field
     "The poller type to use. This setting will take effect at next polling
     interval." to "spine".  Verify that you see lines like the following
 appear every five minutes

     05/14/2016 06:00:02 PM - SYSTEM STATS: Time:1.1864 Method:spine
  Processes:1 Threads:1 Hosts:2 

[Group.of.nepali.translators] [Bug 1572764] Re: autopkgtests are not installing the generated snaps

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.9

---
snapcraft (2.9) xenial; urgency=medium

  [ Leo Arias ]
  * autopkgtests: run the install examples tests in classic. (#481)
(LP: #1572764)

  [ Matteo Bertini ]
  * Fix typo in description of the python3 example. (#504)

  [ Jamie Bennett ]
  * Documentation: Use plugs instead of caps. (#507)

  [ Chris Wayne ]
  * Add in bash completion. (#453) (LP: #1570506)

  [ Sergio Schvezov ]
  * Fail validation if plugs or slots are declared at the part level (#514)
(LP: #1581166)

  [ Kyle Fazzari ]
  * Make pull and build steps dirty if target arch changes. (#450)
(LP: #1564192)
  * Add support for the confinement property. (#501) (LP: #1580819)
  * Add support for the epoch property. (#502) (LP: #1581113)

 -- Sergio Schvezov   Tue, 24 May 2016
23:32:11 -0300

** Changed in: snapcraft (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/1572764

Title:
  autopkgtests are not installing the generated snaps

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

Bug description:
  With the new snappy on ubuntu classic we can install the example snaps
  we generate with snapcraft, and test them on the same testbed.

  [Impact]

   * No impact for users.

   * This will improve the quality of the project on ubuntu classic by
  adding more tests.

  [Test Case]

   * Run the autopkgtests.

   * The examples are just build, not installed.

  [Regression Potential]

   * N/A. This will prevent future regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1572764/+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 1581113] Re: Add support for epoch property

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.9

---
snapcraft (2.9) xenial; urgency=medium

  [ Leo Arias ]
  * autopkgtests: run the install examples tests in classic. (#481)
(LP: #1572764)

  [ Matteo Bertini ]
  * Fix typo in description of the python3 example. (#504)

  [ Jamie Bennett ]
  * Documentation: Use plugs instead of caps. (#507)

  [ Chris Wayne ]
  * Add in bash completion. (#453) (LP: #1570506)

  [ Sergio Schvezov ]
  * Fail validation if plugs or slots are declared at the part level (#514)
(LP: #1581166)

  [ Kyle Fazzari ]
  * Make pull and build steps dirty if target arch changes. (#450)
(LP: #1564192)
  * Add support for the confinement property. (#501) (LP: #1580819)
  * Add support for the epoch property. (#502) (LP: #1581113)

 -- Sergio Schvezov   Tue, 24 May 2016
23:32:11 -0300

** Changed in: snapcraft (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/1581113

Title:
  Add support for epoch property

Status in Canonical Click Reviewers tools:
  Fix Released
Status in Snapcraft:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  Fix Released
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * In order to support step upgrades, snaps need to be able to specify
  upgrade paths.

   * The method decided upon to specify upgrade paths is an optional
  "epoch" property. Valid values consist of integers and an asterisk
  (e.g. 1 is epoch 1, 1* is the upgrade path from 1 to 2, and 2 is epoch
  2).

   * `snapcraft init` should not specify "epoch" at all.

   * The "epoch" property, if specified, should be copied into the
  resulting `snap.yaml`.

   * Example YAML:

  name: foo
  version: 1
  summary: foo
  description: foo
  epoch: 1*
  
  parts:
foo:
  plugin: nil

  [Test Case]

   * Run `snapcraft init`. Make sure "epoch" is not specified.

   * Create a valid snapcraft.yaml (without "epoch" property) and run
  `snapcraft` on it. Make sure the resulting `snap.yaml` doesn't contain
  "epoch" property.

   * Create a valid snapcraft.yaml and include the "epoch" property. Run
  `snapcraft`. Make sure the resulting `snap.yaml` contains the same
  "epoch" property.

  [Regression Potential]

   * snapcraft.yaml validation could be incorrect (required properties
  may not be required correctly, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1581113/+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 1573188] Re: unity7 interface doesn't cover indicators or notifications

[Launchpad Bug Tracker]

This bug was fixed in the package snapd - 2.0.5

---
snapd (2.0.5) xenial; urgency=medium

  * New upstream release: LP: #1583085
- interfaces: add dbusmenu, freedesktop and kde notifications to
  unity7 (LP: #1573188)
- daemon: make localSnapInfo return SnapState
- cmd: make snap list with no snaps not special
- debian: workaround for XDG_DATA_DIRS issues
- cmd,po: fix conflicts, apply review from #1154
- snap,store: load and store the private flag sent by the store in
  SideInfo
- interfaces/apparmor/template.go: adjust /dev/shm to be more usable
- store: use purchase decorator in Snap and FindSnaps
- interfaces: first version of the networkmanager interface
- snap, snappy: implement the new (minmimal) kernel spec
- cmd/snap, debian: move manpage generation to depend on an environ
  key; also, fix completion

snapd (2.0.4) xenial; urgency=medium

  * New upstream release:
- interfaces: cleanup explicit denies
- integration-tests: remove the ancient integration daemon tests
- integration-tests: add network-bind interface test
- integration-tests: add actual checks for undoing install
- integration-tests: add store login test
- snap: add certain implicit slots only on classic
- integration-tests: add coverage flags to snapd.service ExecStart
  setting when building from branch
- integration-tests: remove the tests for features removed in 16.04.
- daemon, overlord/snapstate: "(de)activate" is no longer a thing
- docs: update meta.md and security.md for current snappy
- debian: always start snapd
- integration-tests: add test for undoing failed install
- overlord: handle ensureNext being in the past
- overlord/snapstate,overlord/snapstate/backend,snappy: start
  backend porting LinkSnap and UnlinkSnap
- debian/tests: add reboot capability to autopkgtest and execute
  snapPersistsSuite
- daemon,snappy,progress: drop license agreement broken logic
- daemon,client,cmd/snap: nice access denied message
  (LP: #1574829)
- daemon: add user parameter to all commands
- snap, store: rework purchase methods into decorators
- many: simplify release package and add OnClassic
- interfaces: miscellaneous policy updates
- snappy,wrappers: move desktop files handling to wrappers
- snappy: remove some obviously dead code
- interfaces/builtin: quote apparmor label
- many: remove the gadget yaml support from snappy
- snappy,systemd,wrappers: move service units generation to wrappers
- store: add method to determine if a snap must be bought
- store: add methods to read purchases from the store
- wrappers,snappy: move binary wrapper generation to new package
  wrappers
- snap: add `snap help` command
- integration-tests: remove framework-test data and avoid using
  config-snap for now
- add integration test to verify fix for LP: #1571721

 -- Michael Vogt   Thu, 19 May 2016 15:29:16
+0200

** Changed in: snapd (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  unity7 interface doesn't cover indicators or notifications

Status in Snappy:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Committed
Status in snapd source package in Xenial:
  Fix Released

Bug description:
  Using the "unity7" interface, it seems that the access required to
  utilize indicators or display notifications is not granted (note that
  installing with --devmode works).

  To duplicate:

  1) Build/install the Qt systray example snap here:
  https://github.com/kyrofa/qt-example-snaps/tree/master/systray

  2) Install without devmode, e.g. sudo snap install
  systray_1_amd64.snap

  3) Launch from the terminal with the `systray` command.

  4) Click "Show Message".

  5) Note the presence of a launcher icon, the lack of an indicator, and
  a very ugly notification, like this: http://pasteboard.co/nF8fKsP.png

  6) Uninstall the snap: sudo snap remove systray

  7) Install the snap with devmode, e.g. sudo snap install --devmode
  systray_1_amd64.snap

  8) Launch from the terminal again.

  9) Click "Show Message".

  10) Note the presence of a launcher icon, the presence of an indicator
  (with a broken icon, but that may be a different issue), and a pretty
  notification, like this: http://pasteboard.co/nFoPlFh.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1573188/+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   : 

[Group.of.nepali.translators] [Bug 1578144] Re: cacti and cacti-spine are not compatible with MySQL 5.7 default sql_mode

[Launchpad Bug Tracker]

This bug was fixed in the package cacti - 0.8.8f+ds1-4ubuntu4.16.04

---
cacti (0.8.8f+ds1-4ubuntu4.16.04) xenial; urgency=medium

  * Add make_cacti_sql_mode-strict_compatible.patch to enable cacti to
work with the default settings of MySQL 5.7 (LP: #1578144)

 -- Paul Gevers   Sat, 14 May 2016 21:00:40 +0200

** Changed in: cacti (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/1578144

Title:
  cacti and cacti-spine are not compatible with MySQL 5.7 default
  sql_mode

Status in Cacti:
  Incomplete
Status in cacti package in Ubuntu:
  Fix Released
Status in cacti-spine package in Ubuntu:
  Fix Released
Status in cacti source package in Xenial:
  Fix Released
Status in cacti-spine source package in Xenial:
  Fix Released
Status in cacti source package in Yakkety:
  Fix Released
Status in cacti-spine source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * When cacti and/or cacti-spine is used with the MySQL server on the same
     host and without modifications to the MySQL global setting, cacti fails to
     install and (e.g. for installations that upgraded) cacti and cacti-spine
     fail to run properly since MySQL 5.7 became the default (shortly before
     the Xenial release).

   * This bug renders the cacti and cacti-spine packages nearly useless for
     most users.

   * The fix forces the sql_mode NO_ZERO_DATE setting in the MySQL connection
     to be unset which enables the MySQL INSERT and UPDATE commands that
     involve the date "-00-00" to succeed.

  [Test Case]

   [ Verify issue ]

   * Install cacti on a xenial system with mysql-server installed, and see it
     fails during the population of the database via dbconfig-common. If the
     dbconfig-common defaults are choosen for the error handling (abort), the
     package fails to install.

   * Install cacti on a wily system with mysql-server installed. Connect to
     http://localhost/cacti, pass through the install process (i.e. hit "Ok",
 log in with admin/admin credentials and provide a new admin password).
 Then upgrade to xenial and see that every five minutes a line like the
 following is added to the /var/log/cacti/cacti.log file:

     05/13/2016 06:55:02 PM - CMDPHP: Poller[0] ERROR: A DB Exec
  Failed!, Error:'1292', SQL:"INSERT INTO poller_time (poller_id, pid,
  start_time, end_time) VALUES (0, 4044, NOW(), '-00-00 00:00:00')'

   * Install cacti-spine on a wily system with mysql-server installed. Connect
 to http://localhost/cacti, pass through the install process (i.e. hit
 "Ok", log in with admin/admin credentials and provide a new admin
 password). Now
     navigate to the settings item, select the poller tab and change the field
     "The poller type to use. This setting will take effect at next polling
     interval." to "spine". Then upgrade to xenial and see that every five
     minutes a line like the following is added to the /var/log/cacti/cacti.log
     file:

     05/13/2016 07:50:00 PM - SPINE: Poller[0] ERROR: SQL Failed!
  Error:'1292', Message:'Incorrect datetime value: '-00-00 00:00:00'
  for column 'end_time' at row 1', SQL Fragment:'INSERT INTO poller_time
  (poller_id, pid, start_time, end_time) VALUES (0, 4685, NOW(),
  '-00-00 00:00:00')'

   [ Verify fix ]

   * Install the proposed cacti package on a xenial system with mysql-server
     installed and very that it installs cleanly.

   * Same as previous point, but also connect to http://localhost/cacti, pass
     through the install process (i.e. hit "Ok", log in with admin/admin
     credentials and provide a new admin password). Verify that you see lines
     like the following appear every five minutes

     05/13/2016 07:09:59 PM - SYSTEM STATS: Time:298.6378 Method:cmd.php
  Processes:1 Threads:N/A Hosts:2 HostsPerProcess:2 DataSources:5
  RRDsProcessed:5

     and that lines like the following line are absent:

     05/13/2016 06:55:02 PM - CMDPHP: Poller[0] ERROR: A DB Exec
  Failed!, Error:'1292', SQL:"INSERT INTO poller_time (poller_id, pid,
  start_time, end_time) VALUES (0, 4044, NOW(), '-00-00 00:00:00')'

   * Install cacti-spine on a xenial system with mysql-server installed.
 Connect to http://localhost/cacti, pass through the install process (i.e.
 hit "Ok", log in with admin/admin credentials and provide a new admin
 password). Now
     navigate to the settings item, select the poller tab and change the field
     "The poller type to use. This setting will take effect at next polling
     interval." to "spine".  Verify that you see lines like the following
 appear every five minutes

     05/14/2016 06:00:02 PM - SYSTEM STATS: Time:1.1864 Method:spine
  Processes:1 Threads:1 Hosts:2 HostsPerProcess:2 

[Group.of.nepali.translators] [Bug 1564192] Re: Lifecycle needs to track cross compilation

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.9

---
snapcraft (2.9) xenial; urgency=medium

  [ Leo Arias ]
  * autopkgtests: run the install examples tests in classic. (#481)
(LP: #1572764)

  [ Matteo Bertini ]
  * Fix typo in description of the python3 example. (#504)

  [ Jamie Bennett ]
  * Documentation: Use plugs instead of caps. (#507)

  [ Chris Wayne ]
  * Add in bash completion. (#453) (LP: #1570506)

  [ Sergio Schvezov ]
  * Fail validation if plugs or slots are declared at the part level (#514)
(LP: #1581166)

  [ Kyle Fazzari ]
  * Make pull and build steps dirty if target arch changes. (#450)
(LP: #1564192)
  * Add support for the confinement property. (#501) (LP: #1580819)
  * Add support for the epoch property. (#502) (LP: #1581113)

 -- Sergio Schvezov   Tue, 24 May 2016
23:32:11 -0300

** Changed in: snapcraft (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/1564192

Title:
  Lifecycle needs to track cross compilation

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

Bug description:
  [Impact]

   * If a snap is built using a specific target architecture, and one
  tries to build it again for a different architecture, Snapcraft says
  the snap is already built.

  [Test Case]

   1. Build the 96boards-kernel example with `snapcraft --target-arch arm64`.
   2. Build the 96boards-kernel example with `snapcraft --target-arch armhf`.
   3. Note that Snapcraft doesn't try to rebuild the kernel for the new 
architecture, it says it's already done.
   4. Apply the fix for this bug.
   5. Build the 96boards-kernel example with `snapcraft --target-arch armhf`.
   6. Note that Snapcraft now tries to rebuild the kernel using the new target 
architecture (which should fail-- all we care about is that it tries).

  [Regression Potential]

   * Dirty state tracking (rerunning steps if YAML sections change, bug
  #1477904) may not work correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1564192/+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 1580819] Re: Add support for confinement property

[Launchpad Bug Tracker]

This bug was fixed in the package click-reviewers-tools - 0.43~14.04.1

---
click-reviewers-tools (0.43~14.04.1) xenial-proposed; urgency=medium

  [ Jamie Strandboge ]
  * sr_lint.py:
- kernel snaps may have external symlinks
- handle top-level plugs and slots with yaml data as 'null' (LP: #1579201)
- add epoch checks (LP: #1583298)
- .pyc are arch-independent, so don't complain about them
- add confinement checks (LP: #1580819)
  * data/apparmor-easyprof-ubuntu.json:
- add opengl interface as 'common' (LP: #1572140)
- add reserved bluez, network-manager and location-observe interfaces
  * sr_security.py:
- remove last reference to 'cap'
- turn resquash test into info for now until the squashfs-tools bugs are
  fixed and this is a reliable check
  * when 'confinement' is 'devmode', override the result type to 'info'
- common.py: add override_result_type to allow in support of 'confinement'
  overrides
- sr_common.py: add _devmode_override()
- sr_security.py: use override_result_type if in devmode
- LP: #1584231

 -- Jamie Strandboge   Fri, 20 May 2016 16:06:55 -0500

** Changed in: click-reviewers-tools (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/1580819

Title:
  Add support for confinement property

Status in Canonical Click Reviewers tools:
  Fix Released
Status in Snapcraft:
  Fix Released
Status in click-reviewers-tools package in Ubuntu:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in click-reviewers-tools source package in Xenial:
  Fix Released
Status in snapcraft source package in Xenial:
  Fix Released
Status in click-reviewers-tools source package in Yakkety:
  Fix Released
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * Snaps need to be able to specify if they require devmode or if they
  can be run confined. This will allow for snapd to provide reasonable
  errors if one tries to install a snap that cannot run successfully
  under confinement.

   * The YAML property should be called "confinement," and it should
  have two options: "devmode" and "strict." It should be optional, and
  `snapcraft init` should set it to "devmode."

   * The "confinement" YAML property should be copied into the resulting
  `snap.yaml`.

  * Example YAML:

  name: foo
  version: 1
  summary: foo
  description: foo
  confinement: devmode
  
  parts:
foo:
  plugin: nil

  [Test Case]

   * Run `snapcraft init`. Make sure "confinement" is "devmode."

   * Create a valid snapcraft.yaml and run `snapcraft` on it. Make sure
  the "confinement" value gets copied to the `snap.yaml`.

   * Create a valid snapcraft.yaml and remove the "confinement"
  property. Run `snapcraft`. It should print a hint about defaulting to
  "strict", and "confinement: strict" should be in the resulting
  `snap.yaml`.

  [Regression Potential]

   * snapcraft.yaml validation could be incorrect (required properties
  may not be required correctly, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1580819/+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 1570506] Re: Snapcraft should use bash-completion

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.9

---
snapcraft (2.9) xenial; urgency=medium

  [ Leo Arias ]
  * autopkgtests: run the install examples tests in classic. (#481)
(LP: #1572764)

  [ Matteo Bertini ]
  * Fix typo in description of the python3 example. (#504)

  [ Jamie Bennett ]
  * Documentation: Use plugs instead of caps. (#507)

  [ Chris Wayne ]
  * Add in bash completion. (#453) (LP: #1570506)

  [ Sergio Schvezov ]
  * Fail validation if plugs or slots are declared at the part level (#514)
(LP: #1581166)

  [ Kyle Fazzari ]
  * Make pull and build steps dirty if target arch changes. (#450)
(LP: #1564192)
  * Add support for the confinement property. (#501) (LP: #1580819)
  * Add support for the epoch property. (#502) (LP: #1581113)

 -- Sergio Schvezov   Tue, 24 May 2016
23:32:11 -0300

** Changed in: snapcraft (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/1570506

Title:
  Snapcraft should use bash-completion

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

Bug description:
  [Impact]

   * Snapcraft isn't integrated with bash-completion. Doing so makes it
  much more user-friendly.

  [Test Case]

   1. Try to utilize tab-completion for `snapcraft build` (or any Snapcraft 
command).
   2. Note that it doesn't work.
   3. Apply the fix for this bug.
   4. Note that now it works, for all Snapcraft commands.

  [Regression Potential]

   * None, this is completely new.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1570506/+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 1572140] Re: click-reviewers-tools don't know opengl interface

[Launchpad Bug Tracker]

This bug was fixed in the package click-reviewers-tools - 0.43~14.04.1

---
click-reviewers-tools (0.43~14.04.1) xenial-proposed; urgency=medium

  [ Jamie Strandboge ]
  * sr_lint.py:
- kernel snaps may have external symlinks
- handle top-level plugs and slots with yaml data as 'null' (LP: #1579201)
- add epoch checks (LP: #1583298)
- .pyc are arch-independent, so don't complain about them
- add confinement checks (LP: #1580819)
  * data/apparmor-easyprof-ubuntu.json:
- add opengl interface as 'common' (LP: #1572140)
- add reserved bluez, network-manager and location-observe interfaces
  * sr_security.py:
- remove last reference to 'cap'
- turn resquash test into info for now until the squashfs-tools bugs are
  fixed and this is a reliable check
  * when 'confinement' is 'devmode', override the result type to 'info'
- common.py: add override_result_type to allow in support of 'confinement'
  overrides
- sr_common.py: add _devmode_override()
- sr_security.py: use override_result_type if in devmode
- LP: #1584231

 -- Jamie Strandboge   Fri, 20 May 2016 16:06:55 -0500

** Changed in: click-reviewers-tools (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/1572140

Title:
  click-reviewers-tools don't know opengl interface

Status in Canonical Click Reviewers tools:
  Fix Released
Status in click-reviewers-tools package in Ubuntu:
  Fix Released
Status in click-reviewers-tools source package in Xenial:
  Fix Released
Status in click-reviewers-tools source package in Yakkety:
  Fix Released

Bug description:
  click-reviewers-tools don't know opengl interface - check ubuntu-
  clock-app in the store.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1572140/+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 1580819] Re: Add support for confinement property

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.9

---
snapcraft (2.9) xenial; urgency=medium

  [ Leo Arias ]
  * autopkgtests: run the install examples tests in classic. (#481)
(LP: #1572764)

  [ Matteo Bertini ]
  * Fix typo in description of the python3 example. (#504)

  [ Jamie Bennett ]
  * Documentation: Use plugs instead of caps. (#507)

  [ Chris Wayne ]
  * Add in bash completion. (#453) (LP: #1570506)

  [ Sergio Schvezov ]
  * Fail validation if plugs or slots are declared at the part level (#514)
(LP: #1581166)

  [ Kyle Fazzari ]
  * Make pull and build steps dirty if target arch changes. (#450)
(LP: #1564192)
  * Add support for the confinement property. (#501) (LP: #1580819)
  * Add support for the epoch property. (#502) (LP: #1581113)

 -- Sergio Schvezov   Tue, 24 May 2016
23:32:11 -0300

** Changed in: snapcraft (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/1580819

Title:
  Add support for confinement property

Status in Canonical Click Reviewers tools:
  Fix Released
Status in Snapcraft:
  Fix Released
Status in click-reviewers-tools package in Ubuntu:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in click-reviewers-tools source package in Xenial:
  Fix Released
Status in snapcraft source package in Xenial:
  Fix Released
Status in click-reviewers-tools source package in Yakkety:
  Fix Released
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * Snaps need to be able to specify if they require devmode or if they
  can be run confined. This will allow for snapd to provide reasonable
  errors if one tries to install a snap that cannot run successfully
  under confinement.

   * The YAML property should be called "confinement," and it should
  have two options: "devmode" and "strict." It should be optional, and
  `snapcraft init` should set it to "devmode."

   * The "confinement" YAML property should be copied into the resulting
  `snap.yaml`.

  * Example YAML:

  name: foo
  version: 1
  summary: foo
  description: foo
  confinement: devmode
  
  parts:
foo:
  plugin: nil

  [Test Case]

   * Run `snapcraft init`. Make sure "confinement" is "devmode."

   * Create a valid snapcraft.yaml and run `snapcraft` on it. Make sure
  the "confinement" value gets copied to the `snap.yaml`.

   * Create a valid snapcraft.yaml and remove the "confinement"
  property. Run `snapcraft`. It should print a hint about defaulting to
  "strict", and "confinement: strict" should be in the resulting
  `snap.yaml`.

  [Regression Potential]

   * snapcraft.yaml validation could be incorrect (required properties
  may not be required correctly, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1580819/+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 1581166] Re: unused and potentially confusing support for plugs/slots at a part level in the snapcraft.yaml schema

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.9

---
snapcraft (2.9) xenial; urgency=medium

  [ Leo Arias ]
  * autopkgtests: run the install examples tests in classic. (#481)
(LP: #1572764)

  [ Matteo Bertini ]
  * Fix typo in description of the python3 example. (#504)

  [ Jamie Bennett ]
  * Documentation: Use plugs instead of caps. (#507)

  [ Chris Wayne ]
  * Add in bash completion. (#453) (LP: #1570506)

  [ Sergio Schvezov ]
  * Fail validation if plugs or slots are declared at the part level (#514)
(LP: #1581166)

  [ Kyle Fazzari ]
  * Make pull and build steps dirty if target arch changes. (#450)
(LP: #1564192)
  * Add support for the confinement property. (#501) (LP: #1580819)
  * Add support for the epoch property. (#502) (LP: #1581113)

 -- Sergio Schvezov   Tue, 24 May 2016
23:32:11 -0300

** Changed in: snapcraft (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/1581166

Title:
  unused and potentially confusing support for plugs/slots at a part
  level in the snapcraft.yaml schema

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

Bug description:
  [Impact]

   * snapcraft has a schema that describes allowed snapcraft.yaml files.
  Part of this schema describes plugs and slots that are defined as the
  level of a part (so not globally and not at the level of an app).

   * keeping this code in the schema can create potential confusion for
  users who expect snapcraft to validate the input to be correct.

   * the change is minimal, altering the schema only

  [Test Case]

   * create a snapcrat.yaml with a part defining a plug and a slot
   * run snapcraft
   * snapcraft should complain about the plug/slot definition at a part level 

  ...
  parts:
foo:
  plugin: nil
  plugs: [iface1]
  slots: [iface2]
  ... 

  
  [Regression Potential] 

   * snaps that used parts defining plugs or slots will no longer build
   * snaps that will be built after removing the offending declarations will 
behave exactly as before so the regression potential is minimal

  [Other Info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1581166/+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 1584231] Re: update to 0.43 (aka, support 'confinement' field in snap v2 yaml)

[Launchpad Bug Tracker]

This bug was fixed in the package click-reviewers-tools - 0.43~14.04.1

---
click-reviewers-tools (0.43~14.04.1) xenial-proposed; urgency=medium

  [ Jamie Strandboge ]
  * sr_lint.py:
- kernel snaps may have external symlinks
- handle top-level plugs and slots with yaml data as 'null' (LP: #1579201)
- add epoch checks (LP: #1583298)
- .pyc are arch-independent, so don't complain about them
- add confinement checks (LP: #1580819)
  * data/apparmor-easyprof-ubuntu.json:
- add opengl interface as 'common' (LP: #1572140)
- add reserved bluez, network-manager and location-observe interfaces
  * sr_security.py:
- remove last reference to 'cap'
- turn resquash test into info for now until the squashfs-tools bugs are
  fixed and this is a reliable check
  * when 'confinement' is 'devmode', override the result type to 'info'
- common.py: add override_result_type to allow in support of 'confinement'
  overrides
- sr_common.py: add _devmode_override()
- sr_security.py: use override_result_type if in devmode
- LP: #1584231

 -- Jamie Strandboge   Fri, 20 May 2016 16:06:55 -0500

** Changed in: click-reviewers-tools (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/1584231

Title:
  update to 0.43 (aka, support 'confinement' field in snap v2 yaml)

Status in click-reviewers-tools package in Ubuntu:
  Fix Released
Status in click-reviewers-tools source package in Xenial:
  Fix Released
Status in click-reviewers-tools source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Upgrade to review tools 0.43. The review tools provide lint-style checks for 
clicks and snaps. This release has several bug fixes and support for new snappy 
yaml declarations, the most important of which is supporting the 'confinement' 
property.

  Here is the complete changelog:

* sr_lint.py:
  - kernel snaps may have external symlinks
  - handle top-level plugs and slots with yaml data as 'null' (LP: #1579201)
  - add epoch checks (LP: #1583298)
  - .pyc are arch-independent, so don't complain about them
  - add confinement checks (LP: #1580819)
* data/apparmor-easyprof-ubuntu.json:
  - add opengl interface as 'common' (LP: #1572140)
  - add reserved bluez, network-manager and location-observe interfaces
* sr_security.py:
  - remove last reference to 'cap'
  - turn resquash test into info for now until the squashfs-tools bugs are
fixed and this is a reliable check
* when 'confinement' is 'devmode', override the result type to 'info'
  - common.py: add override_result_type to allow in support of 'confinement'
overrides
  - sr_common.py: add _devmode_override()
  - sr_security.py: use override_result_type if in devmode
  - LP: #1584231

  [Test Case]
  The testsuite tests the above and the store is already using these checks. To 
verify the package:
  1. install the package
  2. verify click reviews work with: click-review /path/to/click
  3. verify snapv1 reviews work with: click-review /path/to/15.04/snap
  4. verify snapv2 reviews work with: click-review /path/to/16/snap

  [Regression Potential]

  The worst regression is that the lint tool would trace back to the
  user running it instead of displaying the information. The testsuite
  is run during the build and is comprehensive with the added code
  maintaining 100% coverage for sr_security.py and sr_lint.py.
  sr_common.py maintaining 98% coverage.

  [Other Info]
  The store has been running r651 for weeks with no issues. r652 and later are 
to support the new snappy 'confinement' and 'epoch' fields as per the spec and 
fixes a few minor issues. The store will land this next week and if there are 
regressions there, I will update this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-reviewers-tools/+bug/1584231/+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 1586491] Re: Volume up and down keys no longer autorepeat

[Sebastien Bacher]

** Also affects: unity (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/1586491

Title:
  Volume up and down keys no longer autorepeat

Status in unity package in Ubuntu:
  In Progress
Status in unity source package in Xenial:
  New

Bug description:
  After upgrading to unity and compiz in xenial-proposed my volume up
  and down keys stopped autorepeating, which seems to be fallout from
  the fix for
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1572241

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160526.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 27 13:45:30 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9]
  InstallationDate: Installed on 2016-01-06 (141 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: LENOVO 3443CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=1f36140c-def2-49da-a1f8-0e14cfc2d84c ro quiet splash 
intel_pstate=disable vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
  Identifier  "Configured Video Device"
  Driver "intel"
  Option "TearFree" "true" 
   EndSection
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET93WW (2.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3443CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET93WW(2.53):bd02/04/2013:svnLENOVO:pn3443CTO:pvrThinkPadX1Carbon:rvnLENOVO:rn3443CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3443CTO
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  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.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri May 27 13:17:21 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 898 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1586491/+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 1586933] Re: gpu-manager's drm output detection affects boot time

[Alberto Milone]

** Also affects: ubuntu-drivers-common (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  gpu-manager's drm output detection affects boot time

Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in ubuntu-drivers-common source package in Xenial:
  In Progress

Bug description:
  Rather than calling drm directly, gpu-manager should simply check the
  outputs connector status by using the sysfs filesystem (e.g.
  /sys/class/drm/card0-HDMI-A-1/status, etc.), thus relying on data that
  is already available.

  This should make gpu-manager a bit less resource intensive, especially
  on boot.

  The attached perf shows the problem in gpu-manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1586933/+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 1433013] Re: Super -> exec vs Alt-F2 -> exec have different environment

[Launchpad Bug Tracker]

This bug was fixed in the package upstart - 1.13.2-0ubuntu21.1

---
upstart (1.13.2-0ubuntu21.1) xenial; urgency=medium

  * Cherry-pick upstream fixes to publish global session variable changes
to the dbus environment. LP: #1433013.

 -- Dimitri John Ledkov   Thu, 19 May 2016 12:04:29
+0100

** Changed in: upstart (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/1433013

Title:
  Super -> exec vs Alt-F2 -> exec have different environment

Status in gnome-session package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Won't Fix
Status in upstart source package in Vivid:
  Won't Fix
Status in gnome-session source package in Xenial:
  Fix Released
Status in upstart source package in Xenial:
  Fix Released

Bug description:
  upstart in user session manages environmental variables and most
  things have them, however Alt-f2 started processes lack them.

  [Impact]
  Some environment variables are missing from apps that are launcher from 
Alt+f2 command lens, or in general with dbus-activation (an example might be 
gnome-terminal, global menu not working).

  [Test case]
  Super Key -> "xterm" -> Enter -> env | grep SSH

  it should return something like:
  SSH_AUTH_SOCK=/run/user/$UID/keyring-/ssh

  Alt+F2 -> "xterm" -> Enter -> env | grep SSH

  The returned values should match the results got from the xterm
  instance that has been ran from unity dash application lens (the one
  opened with Super).

  The same should be checked for the variable XDG_MENU_PREFIX

  Before this fix happened we had this result:
    via Super Key -> the environment is correct
    via Alt-F2 -> it is not

  [Regression potential]

  Nothing known. Some variables could be overridden, but this is
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1433013/+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 1569674] Re: [Kubuntu] Fail to connect to wifi after a recent update

[Launchpad Bug Tracker]

This bug was fixed in the package networkmanager-qt - 5.18.0-0ubuntu1.4

---
networkmanager-qt (5.18.0-0ubuntu1.4) xenial; urgency=medium

  * Restore the wimax symbols with their original versions

networkmanager-qt (5.18.0-0ubuntu1.3) xenial; urgency=medium

  * Add kubuntu_enable_wimax_with_nm_12.diff which reverts upstream
1611028164fed9f2ec5915e042b0b6e18a8a0892 to stay ABI compatible
  * Refresh the symbols again to bring the missing wimax symbols back

networkmanager-qt (5.18.0-0ubuntu1.2) xenial; urgency=medium

  * Refresh symbols to match the final network-manager 1.2 version

networkmanager-qt (5.18.0-0ubuntu1.1) xenial; urgency=medium

  [ Philip Muškovac ]
  * Update the Vcs URLs now that the repositories are hosted on
Launchpad

  [ Clive Johnston ]
  * Add upstream patch to Initialize gateway ping timeout,
Closes (LP: #1569674)
- upstream_Initialize_gateway_ping_timeout.patch

 -- Philip Muškovac   Wed, 18 May 2016 08:06:16 +

** Changed in: networkmanager-qt (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/1569674

Title:
  [Kubuntu] Fail to connect to wifi after a recent update

Status in networkmanager-qt package in Ubuntu:
  Fix Released
Status in networkmanager-qt source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  The new Network manager has some extra options and this breaks the usage of 
many network connections. No new connection can be created or existing ones 
edited.

  [Testcase]
  Before patch:
* Install Kubuntu 16.04
* Connect to a network (connection being done automatically)
* Create a new VPN connection
  * For example PPTP
  * Type in gateway any string longer than one character
  * Click ok
  * Receive notification error «connection.gateway-ping-timeout: can not 
set property: value "18454592" of type 'guint' is invalid or out of range for 
property 'gateway-ping-timeout' of type 'guint'»
  * notice connection is not created
* Create a new connection (wireless or wired)
  * Change the IP to manual
  * Save
  * Receive noification error «same as above»
  * Notice connection is not created
* Import a VPN connection
  * Save
  * Receive notification error «same as above»
  * Notice connection is not created

  [Fix]
  In KDE bug https://bugs.kde.org/show_bug.cgi?id=362141 for this issue a fix 
is commited. This is released in KDE Frameworks 5.21. The patch can be cherry 
picked and applied to networkmanager-qt 5.18.

  [Original Description]
  I installed the recent updates in the Update Manager and after rebooting I 
wasn't able to connect to my wifi network anymore.
  It attempts to connect to the network and fails with the following error 
message:

  Failed to update connection [network name]
  connection.gateway-ping-timeout: can not set property:
  value "46730064" of type 'guint' is invalid or out of range for property 
'gateway-ping-timeout' of type 'guint'

  I am able to use wired connection.

  1. release:
  Description:Ubuntu Xenial Xerus (development branch)
  Release:16.04

  2. network-manager version:
  network-manager:
    Installed: 1.1.93-0ubuntu3
    Candidate: 1.1.93-0ubuntu3
    Version table:
   *** 1.1.93-0ubuntu3 500
  500 http://il.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expected the machine to connect to wifi as always

  4. it failed to connect with the above error message

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 13 06:37:27 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-01 (11 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  IpRoute:
   default via 10.100.102.1 dev enp0s31f6  proto static  metric 100
   10.100.102.0/24 dev enp0s31f6  proto kernel  scope link  src 10.100.102.5  
metric 100
   169.254.0.0/16 dev enp0s31f6  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-04-12T22:28:14.870844
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  

[Group.of.nepali.translators] [Bug 1581140] Re: SRU: Fix PR ld/20060, ld --gc-sections fail with __tls_get_addr_opt.

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.26-8ubuntu2.1

---
binutils (2.26-8ubuntu2.1) xenial-proposed; urgency=medium

  * SRU LP: #1581140.
Fix PR ld/20060, ld --gc-sections fail with __tls_get_addr_opt.

 -- Matthias Klose   Thu, 12 May 2016 18:55:52 +0200

** Changed in: binutils (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/1581140

Title:
  SRU: Fix PR ld/20060, ld --gc-sections fail with __tls_get_addr_opt.

Status in binutils:
  Unknown
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Released

Bug description:
  Fix PR ld/20060, ld --gc-sections fail with __tls_get_addr_opt.

  This is a regression compared to earlier releases (2.24). Affects ppc*
  only.

  Acceptance criteria: The new test cases pass on ppc64el.

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1581140/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1571158] Re: Crash in QXcbWindow::setParent() due to NULL xcbScreen()

[Launchpad Bug Tracker]

This bug was fixed in the package qtbase-opensource-src - 5.5.1+dfsg-
16ubuntu7.1

---
qtbase-opensource-src (5.5.1+dfsg-16ubuntu7.1) xenial; urgency=medium

  * debian/patches/Blacklist-Mali-T760-Mali-T720-from-supporting-BGRA.patch
- Backport from upstream 5.6 (LP: #1557915) (LP: #1559906)
  * Add two patches from stable Qt 5.6 branch to fix another case of
QXcbWindow crashes (LP: #1571158).
- debian/patches/Fix-crash-because-of-NULL-screen-in-QXcbWindow.patch
- debian/patches/QtGui-Don-t-set-a-screen-to-a-child-window.patch
  * Fix drag and drop issues with patches from upstream. (LP: #1577313)
- debian/patches/xcb-Fix-drag-and-drop-to-Emacs.patch
- debian/patches/xcb-Fix-drag-and-drop-to-applications-like-Emacs-and.patch

 -- Timo Jyrinki   Mon, 02 May 2016 12:24:35
+

** Changed in: qtbase-opensource-src (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/1571158

Title:
  Crash in QXcbWindow::setParent() due to NULL xcbScreen()

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Application crash in certain situation.

  [Test Case]

  See bug comments for test app.

  [Regression Potential]]

  The fixes are in the currently release upstream LTS release (Qt 5.6),
  but they do touch a core component of (X11) Qt so eg multi-monitor
  setups should be tested for no regressions.

  --

  Qt 5.5.1 has problem to "[QTBUG-50081] Crash in
  QXcbWindow::setParent() due to NULL xcbScreen()".

  This is already fixed in upstream.
  https://bugreports.qt.io/browse/QTBUG-50081

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1571158/+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 1577313] Re: Drag and drop not working from Qt to some applications

[Launchpad Bug Tracker]

This bug was fixed in the package qtbase-opensource-src - 5.5.1+dfsg-
16ubuntu7.1

---
qtbase-opensource-src (5.5.1+dfsg-16ubuntu7.1) xenial; urgency=medium

  * debian/patches/Blacklist-Mali-T760-Mali-T720-from-supporting-BGRA.patch
- Backport from upstream 5.6 (LP: #1557915) (LP: #1559906)
  * Add two patches from stable Qt 5.6 branch to fix another case of
QXcbWindow crashes (LP: #1571158).
- debian/patches/Fix-crash-because-of-NULL-screen-in-QXcbWindow.patch
- debian/patches/QtGui-Don-t-set-a-screen-to-a-child-window.patch
  * Fix drag and drop issues with patches from upstream. (LP: #1577313)
- debian/patches/xcb-Fix-drag-and-drop-to-Emacs.patch
- debian/patches/xcb-Fix-drag-and-drop-to-applications-like-Emacs-and.patch

 -- Timo Jyrinki   Mon, 02 May 2016 12:24:35
+

** Changed in: qtbase-opensource-src (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/1577313

Title:
  Drag and drop not working from Qt to some applications

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Drag and drop broken from Qt application to some applications like
  Chromium and Emacs.

  [Test Case]

  See above.

  [Regression Potential]

  Drag and drop in general should be tested. The fixes have been merged
  to upstream Qt LTS release.

  --

  https://codereview.qt-project.org/#/c/150641/
  https://codereview.qt-project.org/#/c/157683/

  As requested on Kubuntu mailing list https://lists.ubuntu.com/archives
  /kubuntu-devel/2016-May/010420.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1577313/+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 1559906] Re: bgra support broken on Mali T720

[Launchpad Bug Tracker]

This bug was fixed in the package qtbase-opensource-src - 5.5.1+dfsg-
16ubuntu7.1

---
qtbase-opensource-src (5.5.1+dfsg-16ubuntu7.1) xenial; urgency=medium

  * debian/patches/Blacklist-Mali-T760-Mali-T720-from-supporting-BGRA.patch
- Backport from upstream 5.6 (LP: #1557915) (LP: #1559906)
  * Add two patches from stable Qt 5.6 branch to fix another case of
QXcbWindow crashes (LP: #1571158).
- debian/patches/Fix-crash-because-of-NULL-screen-in-QXcbWindow.patch
- debian/patches/QtGui-Don-t-set-a-screen-to-a-child-window.patch
  * Fix drag and drop issues with patches from upstream. (LP: #1577313)
- debian/patches/xcb-Fix-drag-and-drop-to-Emacs.patch
- debian/patches/xcb-Fix-drag-and-drop-to-applications-like-Emacs-and.patch

 -- Timo Jyrinki   Mon, 02 May 2016 12:24:35
+

** Changed in: qtbase-opensource-src (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/1559906

Title:
  bgra support broken on Mali T720

Status in Canonical System Image:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  [Impact]

  Black screenshots on certain mobile chipsets.

  [Test Case]

  Take a screenshot on affected mobile product.

  [Regression Potential]

  Low, only affects the specified chipsets. Already in use on Ubuntu
  phone and tablet products.

  --

  It seems the screenshots get black on Mali T720 too (frieza) and thus
  the bgra should blacklist should be further extended (from bug
  #1557915 / turbo).

  GL_VENDOR = ARM
  GL_RENDERER = Mali-T720
  GL_VERSION = OpenGL ES 3.1

  Upstream merged commit: https://codereview.qt-project.org/#/c/153756/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1559906/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1580674] Re: [SRU] mitaka point releases

[Launchpad Bug Tracker]

This bug was fixed in the package neutron - 2:8.1.0-0ubuntu0.16.04.2

---
neutron (2:8.1.0-0ubuntu0.16.04.2) xenial; urgency=medium

  [ David Della Vecchia ]
  * New upstream point release for OpenStack Mitaka (LP: #1580674).

  [ Corey Bryant ]
  * d/changelog: Change package version to 2:8.1.0-0ubuntu0.16.04.1 in order
to not conflict with yakkety version 2:8.1.0-0ubuntu1.
  * d/rules: Switch to using ostestr for unit test execution to avoid races.

 -- Corey Bryant   Wed, 18 May 2016 08:16:42
-0400

** Changed in: neutron (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/1580674

Title:
  [SRU] mitaka point releases

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Landscape Server:
  Fix Committed
Status in Landscape Server 16.05 series:
  Fix Committed
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron-fwaas package in Ubuntu:
  Fix Released
Status in neutron-lbaas package in Ubuntu:
  Fix Released
Status in neutron-vpnaas package in Ubuntu:
  Fix Released
Status in neutron source package in Xenial:
  Fix Released
Status in neutron-fwaas source package in Xenial:
  Won't Fix
Status in neutron-lbaas source package in Xenial:
  Won't Fix
Status in neutron-vpnaas source package in Xenial:
  Won't Fix
Status in neutron-api package in Juju Charms Collection:
  Fix Released
Status in neutron-gateway package in Juju Charms Collection:
  Fix Released
Status in neutron-openvswitch package in Juju Charms Collection:
  Fix Released

Bug description:
  New point releases for misc openstack components for the mitaka
  release:

  neutron 8.1.0

  The following components have new upstream releases, but don't
  actually contain any new functionality, so we'll skip for Ubuntu:

  neutron-fwaas 8.1.0
  neutron-lbaas 8.1.0
  neutron-vpnaas 8.1.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1580674/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1581577] Re: [SRU] New stable release 1.28.2

[Launchpad Bug Tracker]

This bug was fixed in the package gvfs - 1.28.2-1ubuntu1~16.04.1

---
gvfs (1.28.2-1ubuntu1~16.04.1) xenial; urgency=low

  * Merge from Debian unstable to 16.04 as a stable update (LP: #1581577).
Remaining changes:
- Run tests through sudo starting as normal user, so that it can find a
  non-root user.
- Drop libbluray-dev build dependency, it is in universe.

gvfs (1.28.2-1) unstable; urgency=medium

  * New upstream release.
  * Bump Standards-Version to 3.9.8.
  * Drop lintian overrides as they are no longer needed. With recent versions
of lintian dh-exec >= 0.13 features are detected properly and binaries
are allowed to use "/usr/lib/$srcpkg/" in RPATHs.

 -- Iain Lane   Fri, 13 May 2016 16:23:01
+0100

** Changed in: gvfs (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/1581577

Title:
  [SRU] New stable release 1.28.2

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

Bug description:
  [ Description ]

  Upstream have released a new bugfix release.

  [ Changes ]

  From NEWS:

  Major changes in 1.28.2
  ===
  * udisks2: Fix crash when mounting encrypted volume

  [ QA, testing, regression potential ]

  Under the GNOME MRE, you can believe all bugs upstream says are fixed
  are really fixed. Just test the system and make sure there are no
  regressions (e.g. look at errors.ubuntu.com).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1581577/+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 1557915] Re: bgra support broken on Mali T760

[Launchpad Bug Tracker]

This bug was fixed in the package qtbase-opensource-src - 5.5.1+dfsg-
16ubuntu7.1

---
qtbase-opensource-src (5.5.1+dfsg-16ubuntu7.1) xenial; urgency=medium

  * debian/patches/Blacklist-Mali-T760-Mali-T720-from-supporting-BGRA.patch
- Backport from upstream 5.6 (LP: #1557915) (LP: #1559906)
  * Add two patches from stable Qt 5.6 branch to fix another case of
QXcbWindow crashes (LP: #1571158).
- debian/patches/Fix-crash-because-of-NULL-screen-in-QXcbWindow.patch
- debian/patches/QtGui-Don-t-set-a-screen-to-a-child-window.patch
  * Fix drag and drop issues with patches from upstream. (LP: #1577313)
- debian/patches/xcb-Fix-drag-and-drop-to-Emacs.patch
- debian/patches/xcb-Fix-drag-and-drop-to-applications-like-Emacs-and.patch

 -- Timo Jyrinki   Mon, 02 May 2016 12:24:35
+

** Changed in: qtbase-opensource-src (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/1557915

Title:
  bgra support broken on Mali T760

Status in Canonical System Image:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  [Impact]

  Black screenshots on certain mobile chipsets.

  [Test Case]

  Take a screenshot on affected mobile product.

  [Regression Potential]

  Low, only affects the specified chipsets. Already in use on Ubuntu
  phone and tablet products.

  --

  bgra support seems broken also on Mali T760 and should be disabled in
  qtbase.

  The consequence of this bug are black screenshots on some devices.

  Upstream merged commit: https://codereview.qt-project.org/#/c/153756/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1557915/+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 1566487] Re: Container apps should use same keyboard layout as Unity 8

[Launchpad Bug Tracker]

This bug was fixed in the package xorg-server - 2:1.18.3-1ubuntu2.2

---
xorg-server (2:1.18.3-1ubuntu2.2) xenial; urgency=medium

  * debian/patches/xmir.patch:
- Fix recently added keymap code
  * debian/patches/xmir-fixes.diff:
- Merged into xmir.patch

xorg-server (2:1.18.3-1ubuntu2.1) xenial; urgency=medium

  * debian/patches/xmir.patch:
- Pass keymap from Mir to Xkb (LP: #1566487)

 -- Robert Ancell   Wed, 04 May 2016
12:19:14 +1200

** Changed in: xorg-server (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/1566487

Title:
  Container apps should use same keyboard layout as Unity 8

Status in Canonical System Image:
  Fix Committed
Status in Libertine:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  XMir clients do not get keyboard layout set in Unity 8.

  [Test Case]
  1. Set keyboard layout to non-english
  2. Start X application

  Expected result:
  Application uses selected layout

  Observed result:
  Application uses default layout

  [Regression Potential]
  Low. The change just connects the keyboard layout signal from Mir to Xkb.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1566487/+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 1579082] Re: minor changes to satisfy MIR request

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu9

---
zfs-linux (0.6.5.6-0ubuntu9) xenial; urgency=medium

  * Minor changes to satisfy MIR request (LP: #1579082)
[ Richard Laager ]
- zfs-zed: Version "Replaces: zfsutils-linux" and add versioned
 "Breaks: zfsutils-linux"
- explicitly specify the man pages so we don't include zed.8
[ Colin Ian King ]
- remove root ALL=(ALL) ALL and R_ROOT from
  debian/tree/zfsutils-linux/etc/sudoers.d/zfs. The R_ROOT serves
  no useful purpose, complicates people actually using the sudoers
  file, and pollutes the global namespace
- add init.d linitan overrides for zfsutils-linux and zfs-zed
  as initscripts will never be used and we will rebase with the
  Debian package initscripts once the package gets accepted by Debian

 -- Colin Ian King   Wed, 11 May 2016 19:40:11
+0100

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

Title:
  minor changes to satisfy MIR request

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [SRU][XENIAL]

  This SRU contains a few minor fixes to satisfy the outstanding issues
  to complete the MIR filed for ZFS linux bug 1532198

  [FIXES]

  The outstanding fixes that need to be applied to the package were:
  https://bugs.launchpad.net/ubuntu/+source/zfs-
  linux/+bug/1532198/comments/4

  "- zfs-zed Replaces zfsutils-linux without a version constraint. Is
  that correct? I assumed a file moved from one package to another, in
  which case there should be a version."

  DONE: zfs-zed, add Replaces: zfsutils-linux (<< 0.6.3)

  "- I like the dep8 tests

  So I'd say add a bug subscriber..."

  DONE: canonical-kernel-team and colin-king

  "... fix the Replaces line, ..."

  DONE: zfs-zed, add Replaces: zfsutils-linux (<< 0.6.3)

  "... address the init script lintian errors ...",

  DONE:  the initscripts will never be used, so we proposed to just add
  lintian ignores for these currently. When Debian accepts their zfs
  package we will rebase from this and will get init scripts from there.

  "... and fix the sudoers file ...",

  DONE: remove root ALL=(ALL) ALL from debian/tree/zfsutils-
  linux/etc/sudoers.d/zfs

  [REGRESSION POTENTAL]
  No actual change to the zfs code per se, more final changes to the packaging, 
regression potential minimal to zero.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1579082/+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 1579925] Re: Sync irssi-plugin-xmpp 0.53-1 (universe) from Debian unstable (main)

[Launchpad Bug Tracker]

This bug was fixed in the package irssi-plugin-xmpp -
0.52+git20160118-2~ubuntu16.04.1

---
irssi-plugin-xmpp (0.52+git20160118-2~ubuntu16.04.1) xenial; urgency=medium

  * No-change sync to xenial (LP: #1579925)

irssi-plugin-xmpp (0.52+git20160118-2) unstable; urgency=medium

  * Rebuild for new irssi version. This is #772479 again...
  * Use all hardening buildflags
  * Install modules in multiarch directory (closes: #817171)
  * Use secure URIs for Vcs-* fields
  * Declare compliance with Debian Policy 3.9.7

 -- Iain Lane   Tue, 10 May 2016 15:09:06
+0100

** Changed in: irssi-plugin-xmpp (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/1579925

Title:
  Sync irssi-plugin-xmpp 0.53-1 (universe) from Debian unstable (main)

Status in irssi-plugin-xmpp package in Ubuntu:
  Fix Released
Status in irssi-plugin-xmpp source package in Xenial:
  Fix Released

Bug description:
  Please sync irssi-plugin-xmpp 0.53-1 (universe) from Debian unstable
  (main)

  Looking at LP: 1579545, irssi-plugin-xmpp appears to be completely broken in
  Xenial, due to
  1) ABI breakage by a newer version of irssi without corresponding rebuild
 (binNMU) of irssi-plugin-xmpp
  2) Use of multiarch library path in newer version of irssi

  Both issues were discussed in #817171 and subsequently fixed in
  irssi-plugin-xmpp 0.52+git20160118-2, which unfortunately was not synced to
  Ubuntu before the Xenial release.

  irssi-plugin-xmpp does not have reverse dependencies, so updating it should
  be low-risk. (If you update to 0.53-1 instead of 0.52+git20160118-2, I don't
  know how well the daily update process copes with the transition from -dbg to
  -dbgsym packages?)

  To my knowledge, Yakkety is not affected.

  
  Changelog entries since current xenial version 0.52+git20160118-1:

  irssi-plugin-xmpp (0.53-1) unstable; urgency=medium

* Import Upstream version 0.53
* Refresh patches
* Transition to automatic dbgsym package

   -- Florian Schlichting   Sat, 19 Mar 2016 00:53:02
  +0100

  irssi-plugin-xmpp (0.52+git20160118-2) unstable; urgency=medium

* Rebuild for new irssi version. This is #772479 again...
* Use all hardening buildflags
* Install modules in multiarch directory (closes: #817171)
* Use secure URIs for Vcs-* fields
* Declare compliance with Debian Policy 3.9.7

   -- Florian Schlichting   Mon, 14 Mar 2016 23:20:10
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irssi-plugin-xmpp/+bug/1579925/+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 1570110] Re: evolution crashed with SIGSEGV, while pasting from clipboard

[Launchpad Bug Tracker]

This bug was fixed in the package webkitgtk - 2.4.11-0ubuntu0.1

---
webkitgtk (2.4.11-0ubuntu0.1) xenial; urgency=medium

  * New upstream version:
- "Fix a crash when changing elment attributes with DOM bindings"
  which impacts the evolution composer for example (lp: #1570110)
  * debian/patches/fix-arm64-build.patch:
- remove, this has been fixed upstream.

 -- Sebastien Bacher   Fri, 13 May 2016 10:52:06
+0200

** Changed in: webkitgtk (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/1570110

Title:
  evolution crashed with SIGSEGV, while pasting from clipboard

Status in WebKit:
  Fix Released
Status in webkitgtk package in Ubuntu:
  Fix Released
Status in webkitgtk source package in Xenial:
  Fix Released

Bug description:
  * Impact
  some webkitgtk consumers like the evolution composer hit segfault issues

  * Test case
  - Click New > Compose Email Message
  - Enter any email address in 'To:'
  - Enter anything into 'Subject"
  - Go to any webpage, and highlight a few lines
  - Click 'ctrl c'
  - Place cursor into the body of the open Compose Message window
  - Click 'ctrl v'

  * Regression potential
  it's a webkit update so could impact other clients of the library, check that 
the html rendering in those

  

  Guys,

   Evolution on Xenial crashes most of times that I want to copy and
  paste stuff into Mail composer window.

   From what I'm seeing, if the stuff inside of the clipboard is
  formatted, with big fonts, tables, etc, it crashes.

   The workaround is to use "Diodon" to paste into Evolution without any
  formatting, or, to open an vim session on Terminal, paste into it
  first, then, copy it again from vim, and paste into Evolution, this
  way, it doesn't crash.

   Looks very easy to reproduce!

  Cheers!
  Thiago

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: evolution 3.18.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Apr 13 18:35:02 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2016-01-30 (74 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160130)
  ProcCmdline: evolution
  SegvAnalysis:
   Segfault happened at: 0x7f9bdaf3d949:cmpq   $0x0,0x18(%rax)
   PC (0x7f9bdaf3d949) ok
   source "$0x0" ok
   destination "0x18(%rax)" (0x654e2073656d696c) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
  Title: evolution crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit-open-source/+bug/1570110/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1574789] Re: xorg.conf.d/90-zap.conf destroys xorg keyboard settings

[Martin Pitt]

> +rm_conffile /usr/share/X11/xorg.conf.d/90-zap.conf 16.04.5

Indeed, this is wrong and should be dropped. Marking as v-failed, please
reupload without this.

** Tags removed: verification-done
** Tags added: verification-failed

** Changed in: ubuntu-mate-settings (Ubuntu)
   Status: Fix Released => In Progress

** Changed in: ubuntu-mate-settings (Ubuntu Xenial)
   Status: Fix Committed => 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/1574789

Title:
  xorg.conf.d/90-zap.conf destroys xorg keyboard settings

Status in ubuntu-mate:
  Fix Committed
Status in ubuntu-mate-settings package in Ubuntu:
  In Progress
Status in ubuntu-mate-settings source package in Xenial:
  In Progress

Bug description:
  With Ubuntu MATE 16.04, I'm unable to switch between keyboard layouts
  properly.

  My locale is LANG=el_GR.UTF-8 and LANGUAGE=el.
  The Ubuntu MATE installer correctly made those settings for me:
  $ grep -i xkboptions /etc/default/keyboard
  XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll"

  I.e. I should be able to switch between the US and the Greek keyboard
  layout using Alt+Shift, and the keyboard scroll led indicates the
  active language.

  Unfortunately ubuntu-mate-default-settings overrides the correct
  settings, making me unable to switch languages via Alt+Shift:

  $ grep -i xkboptions /usr/share/X11/xorg.conf.d/90-zap.conf
  Option "XKbOptions" "terminate:ctrl_alt_bksp,grp"

  So, please make sure that 90-zap.conf *adds* "terminate:ctrl_alt_bksp,grp" to 
the current xkboptions, instead of *replacing* them.
  If it's unable to add instead of replacing settings, then please completely 
remove 90-zap.conf.

  [Impact]

   * Ubuntu MATE included the ability to kill the X server using
  Ctrl+Alt+BkSpc over a year ago while the initial Compiz integration
  was being added. That facility is a hangover and no longer required.

   * This updated version of Ubuntu MATE Settings removes
  usr/share/X11/xorg.conf.d/90-zap.conf and restores the ability to
  switch keyboard layouts using Alt+Shift.

  [Test Cases]

   * Install Ubuntu MATE 16.04 using Greek language and locale and US
  language. You will be unable to switch between the US and the Greek
  keyboard layout using Alt+Shift.

   * Once Ubuntu MATE Settings 16.04.5.1 is installed it will be
  possible to switch between keyboard layouts using Alt+Shift.

  [Regression Potential]

   * The ability to kill the X session using Ctrl+Alt+BkSpc will be
  lost. But none of the other Ubuntu flavours support this functionality
  and it's removal restore the default Xorg behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1574789/+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 1320868] Re: "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte" when removing nvidia-current package

[Alberto Milone]

** Also affects: ubuntu-drivers-common (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  "UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position
  0: invalid start byte" when removing nvidia-current package

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-drivers-common source package in Xenial:
  Triaged

Bug description:
  $sudo apt-get remove nvidia-current
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package 'nvidia-current' is not installed, so not removed
  The following package was automatically installed and is no longer required:
linux-image-generic
  Use 'apt-get autoremove' to remove it.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up nvidia-331 (331.38-0ubuntu7) ...
  INFO:Enable nvidia-331
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  Traceback (most recent call last):
File "/usr/bin/quirks-handler", line 65, in 
  operation_status = main(options)
File "/usr/bin/quirks-handler", line 44, in main
  quirks = Quirks.quirkapplier.QuirkChecker(options.package_enable, 
path=quirks_path)
File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 38, in 
__init__
  self._system_info = self.get_system_info()
File "/usr/lib/python3/dist-packages/Quirks/quirkapplier.py", line 64, in 
get_system_info
  return quirk_info.get_dmi_info()
File "/usr/lib/python3/dist-packages/Quirks/quirkinfo.py", line 46, in 
get_dmi_info
  'class', 'dmi', 'id', item)).read().strip()
File "/usr/lib/python3.4/codecs.py", line 313, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: 
invalid start byte
  dpkg: error processing package nvidia-331 (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   nvidia-331
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1320868/+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