date:20160718

[Group.of.nepali.translators] [Bug 1572874] Re: plymouth is disabled after upgrade from trusty due to missing "splash" kernel arg

2016-07-18 Thread Launchpad Bug Tracker

[Expired for plymouth (Ubuntu Xenial) because there has been no activity
for 60 days.]

** Changed in: plymouth (Ubuntu Xenial)
   Status: Incomplete => Expired

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

Title:
  plymouth is disabled after upgrade from trusty due to missing "splash"
  kernel arg

Status in plymouth package in Ubuntu:
  Invalid
Status in plymouth source package in Xenial:
  Expired

Bug description:
  I upgraded a mostly clean install of 14.04.4 -> 16.04 (Ubuntu GNOME).
  Plymouth is never displayed on the upgraded system.

  This is due to the grub config not having the "splash" kernel
  commandline argument currently

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: grub2-common 2.02~beta2-36ubuntu3
  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: GNOME
  Date: Thu Apr 21 00:47:49 2016
  InstallationDate: Installed on 2016-02-25 (55 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: grub2
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1572874/+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 1593319] Re: menu displays briefly and then disappears

2016-07-18 Thread Jeremy Bicha

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

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

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

** Changed in: icinga (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  menu displays briefly and then disappears

Status in icinga package in Ubuntu:
  Triaged
Status in icinga source package in Xenial:
  Triaged
Status in icinga package in Debian:
  New

Bug description:
  The menu displays briefly and then disappears. The affected file is
  menu.html, which is the same as was packaged in 12.04 and functions
  properly there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: icinga 1.13.3-2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun 16 09:24:13 2016
  SourcePackage: icinga
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icinga/+bug/1593319/+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 1604128] Re: [2.0RC2] Unable to add a public SSH Key due to lp1604147

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package maas -
2.0.0~rc2+bzr5156-0ubuntu1~16.04.2

---
maas (2.0.0~rc2+bzr5156-0ubuntu1~16.04.2) xenial-proposed; urgency=medium

  * debian/patches/lp1604128_workaround_python_lp1604147: Work around a
regression in the recent update to Python 3.5.2 that lost the
pathlib.Path.path property. (LP: #1604128)

 -- Andres Rodriguez   Mon, 18 Jul 2016 16:56:26
-0400

** Changed in: maas (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/1604128

Title:
  [2.0RC2] Unable to add a public SSH Key due to lp1604147

Status in MAAS:
  In Progress
Status in MAAS 2.0 series:
  New
Status in MAAS trunk series:
  In Progress
Status in maas package in Ubuntu:
  Fix Released
Status in maas source package in Xenial:
  Fix Released
Status in maas source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  With a recent update of python from 3.5.1 to 3.5.2, the pathlib.Path.path 
property is gone. This impacts MAAS as it will cause it to fail importing SSH 
keys, which prevents users from deploying.

  [Test Case]
  1. Install MAAS
  2. Import SSH Key (example, maas maas sshkeys create key="$(ssh-add -L | grep 
lee.tra...@canonical.com)")

  With fix - The key will be imported correctly.
  Without fix - The key will fail to import.

  Work around sudden loss of pathlib.Path.path property in Python 3.5.2
  release.

  [Regression Potential]
  None. Tested and proved that using the different path fixes the issue.

  == Original bug report ==
  When I add a public SSH key over the API or in the UI I get the following 
error

  $ maas maas sshkeys create key="$(ssh-add -L | grep lee.tra...@canonical.com)"
  {"key": ["Invalid SSH public key: 'PosixPath' object has no attribute 
'path'"]}

  This was introduced in 5118 in the validation code of SSH keys but
  appears to be exposing a bigger bug. If you run ./bin/test.rack
  src/provisioningserver/utils/tests/test_sshkey.py the tests fail. I'm
  guessing that something is mocking check_output in a previous test and
  not unmocking it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1604128/+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 1595739] Re: please backport arm64 mem{set, cpy, move} optimizations

2016-07-18 Thread dann frazier

** Also affects: glibc (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/1595739

Title:
  please backport arm64 mem{set,cpy,move} optimizations

Status in glibc package in Ubuntu:
  Confirmed
Status in glibc source package in Xenial:
  New

Bug description:
  Optimizations to AArch64's memset, memcpy & memmove routines have
  recently landed upstream. The attached patch applies these clean
  cherry-picks to the current glibc packaging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1595739/+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 1604128] Re: [2.0RC2] Unable to add a public SSH Key due to lp1604147

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package maas - 2.0.0~rc2+bzr5156-0ubuntu2

---
maas (2.0.0~rc2+bzr5156-0ubuntu2) yakkety; urgency=medium

  * debian/patches/lp1604128_workaround_python_lp1604147: Work around a
regression in the recent update to Python 3.5.2 that lost the
pathlib.Path.path property. (LP: #1604128)

 -- Andres Rodriguez   Mon, 18 Jul 2016 17:10:55
-0400

** Changed in: maas (Ubuntu Yakkety)
   Status: New => Fix Released

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

Title:
  [2.0RC2] Unable to add a public SSH Key due to lp1604147

Status in MAAS:
  In Progress
Status in MAAS 2.0 series:
  New
Status in MAAS trunk series:
  In Progress
Status in maas package in Ubuntu:
  Fix Released
Status in maas source package in Xenial:
  Fix Committed
Status in maas source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  With a recent update of python from 3.5.1 to 3.5.2, the pathlib.Path.path 
property is gone. This impacts MAAS as it will cause it to fail importing SSH 
keys, which prevents users from deploying.

  [Test Case]
  1. Install MAAS
  2. Import SSH Key (example, maas maas sshkeys create key="$(ssh-add -L | grep 
lee.tra...@canonical.com)")

  With fix - The key will be imported correctly.
  Without fix - The key will fail to import.

  Work around sudden loss of pathlib.Path.path property in Python 3.5.2
  release.

  [Regression Potential]
  None. Tested and proved that using the different path fixes the issue.

  == Original bug report ==
  When I add a public SSH key over the API or in the UI I get the following 
error

  $ maas maas sshkeys create key="$(ssh-add -L | grep lee.tra...@canonical.com)"
  {"key": ["Invalid SSH public key: 'PosixPath' object has no attribute 
'path'"]}

  This was introduced in 5118 in the validation code of SSH keys but
  appears to be exposing a bigger bug. If you run ./bin/test.rack
  src/provisioningserver/utils/tests/test_sshkey.py the tests fail. I'm
  guessing that something is mocking check_output in a previous test and
  not unmocking it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1604128/+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 1603283] Re: REGRESSION: resume fails on recent 4.4.0-31, works on -28

2016-07-18 Thread Joseph Salisbury

Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.15

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

** Tags added: kernel-da-key

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

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

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

** Tags added: needs-bisect

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

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

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

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

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603283/+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 1436940] Re: Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041] is not supported

2016-07-18 Thread Kees Cook

Hm, not fixed for me. still seeing firmware crashes. :(


** Changed in: linux-firmware (Ubuntu Xenial)
   Status: Fix Released => Confirmed

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

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

Title:
  Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041]
  is not supported

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in linux source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Confirmed

Bug description:
  The firmware for this card isn't included with Ubuntu.  The firmware
  provided in /lib/firmware/ath10k/QCA6174 in Ubuntu 16.04 crashes when
  used with this card.  This included firmware is likely for the QCA6174
  instead of this card, the QCA6164.

  Yes, you read that right: the files for the QCA6164 need to be a
  folder called QCA6174 in order for the card to work.  Running
  "modprobe ath10k_pci" shows that the ath10k_pci module looks for
  firmware in a folder called QCA6174, but not in any folder called
  QCA6164.

  It seems that before this issue can be resolved, the ath10k_pci module
  must be changed so that it recognizes firmware for both the QCA6164
  and QCA6174, in separate folders.

  ---

  HOW TO GET THIS CARD TO WORK:

  1) Use a kernel that supports this card

  According to WikiDevi, support for this card was added in kernel 4.3.
  If you're running Ubuntu 16.04 LTS or above, your kernel is fine; skip
  to the next step.  If you're running Ubuntu 15.10 or below, see
  https://wiki.ubuntu.com/Kernel/MainlineBuilds for info on installing a
  newer kernel.  Alternatively, you can use backports.  This is a lot
  more work, but if you really need to keep using an older kernel for
  some reason, there are some guides to installing backports in the
  comments below.

  2) Get rid of the firmware folder for this card that's included with
  Ubuntu:

  sudo rm -r /lib/firmware/ath10k/QCA6174/

  3) Download the latest firmware:

  wget https://github.com/kvalo/ath10k-firmware/archive/master.zip

  4) Unzip the downloaded file.  Inside the ath10k-firmware-master
  folder is a folder named QCA6174.  Copy the QCA6174 folder to
  /lib/firmware/ath10k:

  unzip master.zip
  sudo cp -r ath10k-firmware-master/QCA6174/ /lib/firmware/ath10k/

  5) Rename two of the firmware files like so:

  cd /lib/firmware/ath10k/QCA6174/hw2.1/
  sudo mv firmware-5.bin_SW_RM.1.1.1-00157-QCARMSWPZ-1 firmware-5.bin
  cd /lib/firmware/ath10k/QCA6174/hw3.0/
  sudo mv firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1 firmware-4.bin

  6) Reboot your computer.  Run "lshw -C network" to see if your card is
  recognized.  You can delete the files you downloaded earlier:

  cd ~
  rm master.zip
  rm -r ath10k-firmware-master/

  I've verified that this works with Ubuntu 16.04 LTS (with kernel
  4.4.0-21-generic); let me know if it doesn't work for you in the
  comments below.

  ---

  Miles Krell

  Last updated May 23, 2016

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436940/+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 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

2016-07-18 Thread Joseph Salisbury

Do you have a machine that could be used to test some kernels?  If so,
we can perform a kernel bisect to identify the commit that caused the
regression.

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

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

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

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

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

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

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602577/+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 1603449] Re: [LTCTest][Opal][OP820] Machine crashed with Oops: Kernel access of bad area, sig: 11 [#1] while executing Froze PE Error injection

2016-07-18 Thread Tim Gardner

Guo Wen Shan - how about if you take a stab at the backports for these 2
patches, 'cause I don't think they make sense for a 4.4 kernel.

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  [LTCTest][Opal][OP820] Machine crashed with Oops: Kernel access of bad
  area, sig: 11 [#1] while executing Froze PE Error injection

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  In Progress

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2016-07-13 
01:28:56 ==
  ---Problem Description---
  Machine crashed with Oops: Kernel access of bad area, sig: 11 [#1]
   
  ---uname output---
  Linux ltc-garri2 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  root@ltc-garri2:~# lspci
  :00:00.0 PCI bridge: IBM Device 03dc
  :01:00.0 Infiniband controller: Mellanox Technologies MT27600 [Connect-IB]
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0002:00:00.0 PCI bridge: IBM Device 03dc
  0002:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
  0003:00:00.0 PCI bridge: IBM Device 03dc
  0004:00:00.0 PCI bridge: IBM Device 03dc
  0005:00:00.0 PCI bridge: IBM Device 03dc
  0005:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:02.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:03.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:04.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:03:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 
xHCI Host Controller (rev 02)
  0005:04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 
x2 4-port SATA 6 Gb/s Controller (rev 11)
  0005:05:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge 
(rev 03)
  0005:06:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED 
Graphics Family (rev 30)
  0005:07:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
  0005:07:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
  0006:00:00.0 PCI bridge: IBM Device 03dc
  0006:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
  0007:00:00.0 PCI bridge: IBM Device 03dc
  0008:00:00.0 Bridge: IBM Device 04ea
  0008:00:00.1 Bridge: IBM Device 04ea
  0008:00:01.0 Bridge: IBM Device 04ea
  0008:00:01.1 Bridge: IBM Device 04ea
  0009:00:00.0 Bridge: IBM Device 04ea
  0009:00:00.1 Bridge: IBM Device 04ea
  0009:00:01.0 Bridge: IBM Device 04ea
  0009:00:01.1 Bridge: IBM Device 04ea
   

   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Install a P8 Open Power 8335-GTB Hardware with Ubuntu 16.04.1.
  Then execute the Frozen PE error injection tests as shown below:

  root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
  0004:00:00.0 PCI bridge: IBM Device 03dc
  root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
  eeh_slot_resets=0

  
  root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
  0004:00:00.0 PCI bridge: IBM Device 03dc
  root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
  eeh_slot_resets=0
  root@ltc-garri2:~# echo 0:0:4:0:0 > 
/sys/kernel/debug/powerpc/PCI0004/err_injct && lspci -ns 0004:00:00.0; echo $?
  0004:00:00.0 0604: 1014:03dc
  0

  Immediately the kernel crashes with a Oops Message.
   
  Contact Information = pavsu...@in.ibm.com 
   
  Stack trace output:
   [  289.297946] Call Trace:
  [  289.297969] [c00feeb8b9e0] [c0083c78] pnv_eeh_reset+0x58/0x170 
(unreliable)
  [  289.298042] [c00feeb8ba60] [c0038250] eeh_reset_pe+0xb0/0x1c0
  [  289.298105] [c00feeb8bb00] [c0af444c] 
eeh_reset_device+0xd8/0x228
  [  289.298165] [c00feeb8bba0] [c003c520] 
eeh_handle_normal_event+0x390/0x440
  [  289.298234] [c00feeb8bc20] [c003c9c4] 
eeh_handle_event+0x184/0x370
  [  289.298304] [c00feeb8bcd0] [c003cd88] 
eeh_event_handler+0x1d8/0x1e0
  [  289.298374] [c00feeb8bd80] [c00e6420] kthread+0x110/0x130
  [  289.298434] [c00feeb8be30] [c0009538] 
ret_from_kernel_thread+0x5c/0xa4
  [  289.298501] Instruction dump:
  [  289.298531] 6000

[Group.of.nepali.translators] [Bug 1584417] Re: Location/Timezone picker crashes on install

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubiquity - 2.21.63.2

---
ubiquity (2.21.63.2) xenial; urgency=high

  [ Shih-Yuan Lee (FourDollars) ]
  * Some places doesn't have the location information. (LP: #1584417)

  [ Dimitri John Ledkov ]
  * Fix substitution variables syntax from $() -> ${} in
translations. (LP: #1603926)
  * Automatic update of included source packages: console-setup
1.108ubuntu15.2, partman-base 187ubuntu2.1.

 -- Dimitri John Ledkov   Mon, 18 Jul 2016 14:28:29
+0100

** Changed in: ubiquity (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/1584417

Title:
  Location/Timezone picker crashes on install

Status in OEM Priority Project:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Released

Bug description:
  During Ubuntu 16.04LTS install, in the "Where are you?" screen,
  ubiquity crashes with AttributeError in geoname_add_tzdb(): NoneType
  object has no attribute 'human_country'.

  Retyping by hand since this afterwards it crashes the install

  Traceback:
  File /usr/lib/ubiquity/plugins/ubi-timezone.py  line 165 in geoname_cb
self.geoname_add_tzdb(text,model)
  File /usr/lib/ubiquity/plugins/ubi-timezone.py line 145 in geoname_add_tzdb
model.append([name, '', loc.human_country,
  AttributeError: NoneType object has no attribute 'human_country'

  ApportVersion 2.20.1-0ubuntu2
  Ubiquity 2.21.63

  Repo steps:
  * in the text box, erase the value, and start typing "st".  It crashes after 
the letter "s" (freezes, with the crash windows hidden behind the main one)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1584417/+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 1602035] Re: Maps app no longer works because MapQuest disabled access

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-gnome-meta - 0.58.1

---
ubuntu-gnome-meta (0.58.1) xenial; urgency=medium

  * Refreshed dependencies
  * Removed gnome-maps from desktop-recommends (LP: #1602035)

 -- Jeremy Bicha   Thu, 14 Jul 2016 11:35:57 -0400

** Changed in: ubuntu-gnome-meta (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/1602035

Title:
  Maps app no longer works because MapQuest disabled access

Status in Gnome Maps:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-maps package in Ubuntu:
  Triaged
Status in libchamplain package in Ubuntu:
  Triaged
Status in ubuntu-gnome-meta package in Ubuntu:
  Fix Released
Status in gnome-maps source package in Trusty:
  Triaged
Status in gnome-maps source package in Wily:
  Triaged
Status in gnome-maps source package in Xenial:
  Triaged
Status in libchamplain source package in Xenial:
  Triaged
Status in ubuntu-gnome-meta source package in Xenial:
  Fix Released
Status in gnome-maps package in Debian:
  Confirmed
Status in gnome-maps package in Fedora:
  Unknown

Bug description:
  As of today, MapQuest has disabled their free map tile feed. This
  means the Maps app no longer displays anything except a warning
  pointing to

  http://devblog.mapquest.com/2016/06/15/modernization-of-mapquest-
  results-in-changes-to-open-tile-access/

  Screenshot attached.

  [Impact]
  GNOME Maps is included by default in Ubuntu GNOME 15.10 and 16.04. The app 
currently is useless.

  Triaged as "High" because it "prevents the application or any
  dependencies from functioning correctly at all".
  https://wiki.ubuntu.com/Bugs/Importance

  This also breaks libchamplain (a library for embedding maps into your
  app). Once a fix is released, apps using libchamplain will likely need
  to be patched to use a different map provider.

  [Test Case]
  Install gnome-maps. Open the Maps app. Do you see maps?

  Note that maps are cached so you may not notice the feed has been
  disabled unless you try viewing a specific area at a close enough zoom
  that you have not viewed recently.

  [Regression Potential]
  No Stable Release Update is ready yet for this issue.

  https://mail.gnome.org/archives/desktop-devel-
  list/2016-July/msg3.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-maps/+bug/1602035/+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 1603926] Re: In ubiquity many translations have incorrect substituition variables

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubiquity - 2.21.63.2

---
ubiquity (2.21.63.2) xenial; urgency=high

  [ Shih-Yuan Lee (FourDollars) ]
  * Some places doesn't have the location information. (LP: #1584417)

  [ Dimitri John Ledkov ]
  * Fix substitution variables syntax from $() -> ${} in
translations. (LP: #1603926)
  * Automatic update of included source packages: console-setup
1.108ubuntu15.2, partman-base 187ubuntu2.1.

 -- Dimitri John Ledkov   Mon, 18 Jul 2016 14:28:29
+0100

** Changed in: ubiquity (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/1603926

Title:
  In ubiquity many translations have incorrect substituition variables

Status in Ubuntu Translations:
  New
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Released
Status in ubiquity source package in Yakkety:
  Fix Released

Bug description:
  https://translations.launchpad.net/ubuntu/xenial/+source/ubiquity/+pots
  /ubiquity-
  debconf/de/+translate?batch=10=all=Download+updates+while

  Currently is:

  English:  
  Download updates while installing ${RELEASE}

  
  Current German:   
  Herunterladen der Aktualisierungen, während $(RELEASE) aktualisiert wird

  But should be

  Herunterladen der Aktualisierungen, während ${RELEASE} aktualisiert
  wird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1603926/+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 1590688] Re: clamav-daemon doesn't start after installation

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package clamav - 0.99+dfsg-1ubuntu3

---
clamav (0.99+dfsg-1ubuntu3) yakkety; urgency=medium

  * Ensure freshclam service is run after package install (LP: #1590688)

 -- Christian Ehrhardt   Thu, 07 Jul
2016 09:22:41 +0200

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

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

Title:
  clamav-daemon doesn't start after installation

Status in clamav package in Ubuntu:
  Fix Released
Status in clamav source package in Xenial:
  Triaged
Status in clamav package in Debian:
  New

Bug description:
  [Impact]

   * Installing clamav the user expects things start to run
   * Naturally the daemon can only run after the virus-database is updated 
(conditions in systemd service)
   * But the freshclam service to update the virus-db is not starting either 
 since the move to systemd (Regression to old behavior)

  [Test Case]

   * (enable proposed if needed)
   * apt-get install clamav-freshclam
   * systemctl status clamav-freshclam.service
   * this should show "active" (fixed) and not just "loaded" (broken)

  [Regression Potential]

   * The fix is fairly straightforward so there shouldn't be a lot. But it 
 affects postinst and while not changing, it has to move some code there 
 and might affect something in postinst I missed to think about.

   * It worked for adt in Y & X and for my manual tests in LXD containers 
 fine

  [Other Info]
   
   * This is (intentionally) only addressing the regression for now.
 Once fixed we think of splitting the part of auto-starting clamav-
 daemon later on once the DB is ready


  
  Steps to reproduce:

  1. Fresh 16.04 Server installation
  2. "sudo apt-get install clamav-daemon clamav-freshclam"
  3. ClamAV doesn't start even though it should.

  $ systemctl status clamav-daemon
  ● clamav-daemon.service - Clam AntiVirus userspace daemon
     Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled; vendor 
preset: enabled)
     Active: inactive (dead)
  Condition: start condition failed at Thu 2016-06-09 11:58:19 EEST; 7min ago
   Docs: man:clamd(8)
     man:clamd.conf(5)
     http://www.clamav.net/lang/en/doc/

  $ systemctl status clamav-freshclam.service
  ● clamav-freshclam.service - ClamAV virus database updater
     Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; enabled; 
vendor preset: enabled)
     Active: inactive (dead)
   Docs: man:freshclam(1)
     man:freshclam.conf(5)
     http://www.clamav.net/lang/en/doc/

  Also directory /var/run/clamav/ mentioned in /etc/clamav/clamd.conf
  seems to be missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: clamav-daemon 0.99+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun  9 12:00:59 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-06-09 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: clamav
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1590688/+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 1604058] Re: virtualbox+usb 3.0 breaks boot, -28 kernel works

2016-07-18 Thread Joseph Salisbury

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

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

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

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

** Tags added: kernel-da-key regression-release xenial

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => 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/1604058

Title:
  virtualbox+usb 3.0 breaks boot, -28 kernel works

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Hi guys
  linux-image-4.4.0-31-generic kernel started crashing on boot with 
xhci_pci_probe
  on usb 3.0
  -28 worked

  please see more + kernel logs on 
  https://forums.virtualbox.org/viewtopic.php?f=3=78656

  thnx
  Lubos

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604058/+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 1603574] Re: Hotplug remove and re-add adds PCI adapter to next PCI domain (PCI)

2016-07-18 Thread Tim Gardner

https://lists.ubuntu.com/archives/kernel-team/2016-July/079182.html

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

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
   Status: New

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  Hotplug remove and re-add adds PCI adapter to next PCI domain (PCI)

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

Bug description:
  == Comment: #26 - Guilherme Guaglianoni Piccoli  - 
2016-07-15 16:26:38 ==
  When performing hotplug operations in PowerPC currently, if we remove a PHB 
and re-add it later, its domain address is incremented. An example below (drmgr 
is the tool we use in PowerPC to perform this operation):

  
  (i) $>  lspci
  :60:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet
  :60:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet

  (ii) $>  drmgr -c phb -s "PHB 20" -r  # removing a PHB

  (iii) $>  lspci #empty

  (iv) $>  drmgr -c phb -s "PHB 20" -a  # re-adding the PHB

  (v) $>  lspci
  0001:60:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet
  0001:60:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet

  
  This behavior is harmful when kernel is using network predictable naming for 
interfaces, for example, since after the PHB re-add, the PCI address of NIC 
functions changes, and so the interfaces' naming also change. Recently, a patch 
was merged to powerpc-next to avoid this situation, by relating the PCI domain 
number with device-tree properties. With the patch, the above steps (i) and (v) 
present the same output for lspci.

  We want to ask Canonical to merge the patch in Ubuntu Xenial's kernel,
  since it will solve multiple bugs we've experienced by performing NIC
  hotplug - the commit is present on powerpc-next under the commit-id
  63a72284b15.

  A link to the patch:
  
https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?id=63a72284b159c569ec52f380c9

  Thanks in advance,


  Guilherme

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603574/+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 1602724] Re: Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

2016-07-18 Thread Tim Gardner

https://lists.ubuntu.com/archives/kernel-team/2016-July/079171.html

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

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

Bug description:
  == Comment: #0 - Heitor Ricardo Alves de Siqueira  - 
2016-07-12 12:54:27 ==
  Current nvme driver in Ubuntu 16.04 kernel does not handle error recovery; we 
are missing some patches from the upstream nvme driver.

  We would like to ask Canonical to cherry pick the following patches for the 
16.04 kernel, if possible:
  * 9396dec916c0 ("nvme: use a work item to submit async event requests")
  * 79f2b358c9ba ("nvme: don't poll the CQ from the kthread")
  * 2d55cd5f511d ("nvme: replace the kthread with a per-device watchdog 
timer")
  * 9bf2b972afea ("NVMe: Fix reset/remove race")
  * c875a7093f04 ("nvme: Avoid reset work on watchdog timer function during 
error recovery")
  * a5229050b69c ("NVMe: Always use MSI/MSI-x interrupts")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602724/+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 1503758] Re: /usr/lib/unity-settings-daemon/unity-settings-daemon:5:XIQueryDevice:xdevice_get_dimensions:input_info_find_size_match:get_mappable_output_info:do_touch

2016-07-18 Thread Ara Pulido

** Changed in: oem-priority
   Status: In Progress => Fix Released

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

Title:
  /usr/lib/unity-settings-daemon/unity-settings-
  
daemon:5:XIQueryDevice:xdevice_get_dimensions:input_info_find_size_match:get_mappable_output_info:do_touchscreen_mapping

Status in OEM Priority Project:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in unity-settings-daemon package in Fedora:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-settings-daemon.  This problem was most recently seen
  with version 15.04.1+15.10.20150818-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6e9dcc008057a747fb5c2e65cd47f07e5b672724
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1503758/+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 1602524] Re: [LTC-Test] - NMI watchdog Bug and call traces when trinity is executed.

2016-07-18 Thread Tim Gardner

https://lists.ubuntu.com/archives/kernel-team/2016-July/079167.html

** Also affects: linux (Ubuntu Yakkety)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Triaged

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  [LTC-Test] - NMI watchdog Bug and call traces when trinity is
  executed.

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

Bug description:
  == Comment: #0 - Santhosh G  ==
  Problem Statement:
  NMI watchdog bug and call traces occurs when trinity is executed.

  Environment:
  P8 PowerVM Lpar

  uname o/p:
  uname -a
  Linux tuleta4u-lp5 4.4.0-11-generic #26-Ubuntu SMP Sat Mar 5 14:21:51 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:

  1) Install ubuntu 16.04 in a PowerVM LPAR.
  2) Download trinity-1.5 and set up ./configure.sh;make;make install
  3)Execute trinity as 
 './trinity --dangerous'

  The test runs for more than one hour and trinity gets killed with call
  traces:

  [19744.229979] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 21s! 
[trinity-c3:26544]
  [19744.229991] Modules linked in: hidp hid bnep rfcomm l2tp_ppp l2tp_netlink 
l2tp_core ip6_udp_tunnel udp_tunnel af_key mpls_router llc2 nfnetlink dn_rtmsg 
xfrm_user xfrm_algo can_raw crypto_user can_bcm cmtp kernelcapi 
scsi_transport_iscsi sctp libcrc32c nfc af_alg caif_socket caif phonet af_rxrpc 
bluetooth can pppoe pppox irda crc_ccitt atm appletalk ipx p8023 p8022 psnap 
llc pseries_rng rtc_generic autofs4 ibmvscsi ibmveth
  [19744.230024] CPU: 3 PID: 26544 Comm: trinity-c3 Not tainted 
4.4.0-11-generic #26-Ubuntu
  [19744.230026] task: cae87e60 ti: cae24000 task.ti: 
cae24000
  [19744.230028] NIP: c03fac78 LR: c03fabfc CTR: 
c039ef10
  [19744.230029] REGS: cae27980 TRAP: 0901   Not tainted  
(4.4.0-11-generic)
  [19744.230030] MSR: 80009033   CR: 2400  
XER: 2000
  [19744.230035] CFAR: c03fae6c SOFTE: 1
 GPR00: c03fabfc cae27c00 c15a3b00 
c000f7f03ba8
 GPR04: 0e02adcb cae27cb0  

 GPR08: 8000  c000ef886000 
c0af0870
 GPR12: 2400 ce7f1c80
  [19744.230045] NIP [c03fac78] ext4_es_lookup_extent+0xc8/0x2c0
  [19744.230047] LR [c03fabfc] ext4_es_lookup_extent+0x4c/0x2c0
  [19744.230048] Call Trace:
  [19744.230050] [cae27c00] [c03fabfc] 
ext4_es_lookup_extent+0x4c/0x2c0 (unreliable)
  [19744.230053] [cae27c50] [c03a6f18] 
ext4_map_blocks+0x78/0x610
  [19744.230055] [cae27d10] [c039f14c] ext4_llseek+0x23c/0x3f0
  [19744.230057] [cae27de0] [c02e02a8] SyS_lseek+0xe8/0x130
  [19744.230060] [cae27e30] [c0009204] system_call+0x38/0xb4
  [19744.230061] Instruction dump:
  [19744.230062] 2fa9 409effec e93e0028 3b80 e9490458 e92a0440 39290001 
f92a0440
  [19744.230065] 7c2004ac 7d20d828 3129 7d20d92d <40c2fff4> 6000 
7f83e378 38210050

  
  == Comment: #8 - Santhosh G  ==

  Tried the scenario as given in 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=128126#c26
  -
  # Create a 624GiB file; Mostly filled with holes though
  $ dd if=/dev/zero of=file-0.bin bs=1M count=1 seek=598382 
  # Invoke lseek with SEEK_DATA option starting with file offset 0
  while [ 1 ]; do xfs_io -f -c "seek -d 0" file-0.bin; done
  
  and I was able to hit the issue in 16.04.1 

  kernel version:
  4.4.0-28-generic

  dmesg o/p:

  [ 1197.994822]40-...: (5249 ticks this GP) idle=975/141/0 
softirq=7812/7812 fqs=5251 
  [ 1197.995071] (t=5251 jiffies g=29144 c=29143 q=3418)
  [ 1197.995115] Task dump for CPU 40:
  [ 1197.995117] xfs_io  R  running task0  3601   3489 
0x00040004
  [ 1197.995121] Call Trace:
  [ 1197.995126] [c03c7c8675b0] [c00fbc00] 
sched_show_task+0xe0/0x180 (unreliable)
  [ 1197.995131] [c03c7c867620] [c013eb74] 
rcu_dump_cpu_stacks+0xe4/0x150
  [ 1197.995134] [c03c7c867670] [c01442a4] 
rcu_check_callbacks+0x6b4/0x9b0
  [ 1197.995136] [c03c7c8677a0] [c014c108] 
update_process_times+0x58/0xa0
  [ 1197.995140] [c03c7c8677d0] [c0163818]

[Group.of.nepali.translators] [Bug 1603468] Re: ovs nat: conntrack netlink event are missing

2016-07-18 Thread Tim Gardner

https://lists.ubuntu.com/archives/kernel-team/2016-July/079165.html

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux (Ubuntu Yakkety)
   Status: Incomplete => Fix Committed

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  ovs nat: conntrack netlink event are missing

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

Bug description:
  Fixed upstream by this patch:
  d913d3a763a6 openvswitch: fix conntrack netlink event delivery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603468/+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 1590688] Re: clamav-daemon doesn't start after installation

2016-07-18 Thread Robie Basak

** Also affects: clamav (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/1590688

Title:
  clamav-daemon doesn't start after installation

Status in clamav package in Ubuntu:
  Confirmed
Status in clamav source package in Xenial:
  New
Status in clamav package in Debian:
  New

Bug description:
  [Impact]

   * Installing clamav the user expects things start to run
   * Naturally the daemon can only run after the virus-database is updated 
(conditions in systemd service)
   * But the freshclam service to update the virus-db is not starting either 
 since the move to systemd (Regression to old behavior)

  [Test Case]

   * (enable proposed if needed)
   * apt-get install clamav-freshclam
   * systemctl status clamav-freshclam.service
   * this should show "active" (fixed) and not just "loaded" (broken)

  [Regression Potential]

   * The fix is fairly straightforward so there shouldn't be a lot. But it 
 affects postinst and while not changing, it has to move some code there 
 and might affect something in postinst I missed to think about.

   * It worked for adt in Y & X and for my manual tests in LXD containers 
 fine

  [Other Info]
   
   * This is (intentionally) only addressing the regression for now.
 Once fixed we think of splitting the part of auto-starting clamav-
 daemon later on once the DB is ready


  
  Steps to reproduce:

  1. Fresh 16.04 Server installation
  2. "sudo apt-get install clamav-daemon clamav-freshclam"
  3. ClamAV doesn't start even though it should.

  $ systemctl status clamav-daemon
  ● clamav-daemon.service - Clam AntiVirus userspace daemon
     Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled; vendor 
preset: enabled)
     Active: inactive (dead)
  Condition: start condition failed at Thu 2016-06-09 11:58:19 EEST; 7min ago
   Docs: man:clamd(8)
     man:clamd.conf(5)
     http://www.clamav.net/lang/en/doc/

  $ systemctl status clamav-freshclam.service
  ● clamav-freshclam.service - ClamAV virus database updater
     Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; enabled; 
vendor preset: enabled)
     Active: inactive (dead)
   Docs: man:freshclam(1)
     man:freshclam.conf(5)
     http://www.clamav.net/lang/en/doc/

  Also directory /var/run/clamav/ mentioned in /etc/clamav/clamd.conf
  seems to be missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: clamav-daemon 0.99+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun  9 12:00:59 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-06-09 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: clamav
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1590688/+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 1591622] Re: Can't login to system, system is booting up error

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package console-setup - 1.108ubuntu15.2

---
console-setup (1.108ubuntu15.2) xenial; urgency=medium

  * Reorganize and correct console-setup, keyboard-setup and setvtrgb along the
lines of the logic in 16.04: (LP: #1591622, #1593156)
- debian/console-setup-linux.setvtrgb.service: don't require being run
  before system-getty.slice.
- debian/keyboard-configuration.links: both console-setup and
  keyboard-setup systemd units should be installed to sysinit.target rather
  than multi-user.
- debian/keyboard-configuration.keyboard-setup.service: move loadkeys call
  at local-fs-pre.target and in this more suitable location.
- debian/keyboard-configuration.console-setup.service: move to running
  after the screen, keyboard, and filesystems are ready and set up all of
  what may still need to be done to configure the virtual consoles
  appropriately: set a final keymap, font, etc.

console-setup (1.108ubuntu15.1) xenial; urgency=medium

  * debian/console-setup-linux.setvtrgb.service: port the upstart job for
applying our preferred color settings to a systemd unit so it gets run.
This will fix debconf prompts on console being extra ugly. (LP: #1576893)
  * debian/console-setup-linux.links: enable our setvtrgb service in sysinit.
  * debian/keyboard-configuration.links: fix link source for console-setup
service. (LP: #1572697)
  * debian/control: add dh-systemd to Build-Depends.
  * debian/keyboard-configuration.keyboard-setup.service: also enable
keyboard-setup as a systemd service so we can have proper keymaps enabled
in VTs. (LP: #1579267)
  * debian/keyboard-configuration.links: enable keyboard-setup service.

 -- Mathieu Trudel-Lapierre   Thu, 16 Jun 2016
14:41:19 +0300

** Changed in: console-setup (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/1591622

Title:
  Can't login to system, system is booting up error

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  Fix Released
Status in console-setup source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Regression in console-setup 1.108ubuntu15.1 in xenial-proposed which 
introduced a dependency loop caused logins to fail in around 10% of boots.

  [Test case]
  1) reboot
  2) attempt to login

  In the failure case, the system will display an error message:
  "System is booting up. See pam_nologin(8)."

  [Regression Potential]
  This is intended to fix a regression already found in xenial-proposed due to 
dependencies in the systemd units. Other ordering issues may arise, such that 
it is possible for another process to otherwise fail to load because of the 
invalid dependencies between systemd jobs. Care is to be taken in testing the 
proposed fix, and involves many reboot tests.

  ---

  On login screen (LightDM) I cant login to system because system error is 
displayed: System is booting up. See pam_nologin(8). This message is appearing 
randomly, sometimes when I boot system I can login and sometimes not. It starts 
to show after last console-setup-linux, console-setup and 
keyboard-configuration to version 1.108ubuntu15.1.
  Photo with error in attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-lowlatency 4.4.10
  Uname: Linux 4.4.0-23-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun 12 08:50:29 2016
  InstallationDate: Installed on 2015-02-13 (484 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmConfig:
   [Seat:*]
   allow-guest = false
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (47 days ago)
  mtime.conffile..etc.init.lightdm.conf: 2015-06-08T20:05:20

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1591622/+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 1576893] Re: console colors are not correctly applied

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package console-setup - 1.108ubuntu15.2

---
console-setup (1.108ubuntu15.2) xenial; urgency=medium

* Reorganize and correct console-setup, keyboard-setup and setvtrgb along the
lines of the logic in 16.04: (LP: #1591622, #1593156)
- debian/console-setup-linux.setvtrgb.service: don't require being run
before system-getty.slice.
- debian/keyboard-configuration.links: both console-setup and
keyboard-setup systemd units should be installed to sysinit.target rather
than multi-user.
- debian/keyboard-configuration.keyboard-setup.service: move loadkeys call
at local-fs-pre.target and in this more suitable location.
- debian/keyboard-configuration.console-setup.service: move to running
after the screen, keyboard, and filesystems are ready and set up all of
what may still need to be done to configure the virtual consoles
appropriately: set a final keymap, font, etc.

console-setup (1.108ubuntu15.1) xenial; urgency=medium

* debian/console-setup-linux.setvtrgb.service: port the upstart job for
applying our preferred color settings to a systemd unit so it gets run.
This will fix debconf prompts on console being extra ugly. (LP: #1576893)
* debian/console-setup-linux.links: enable our setvtrgb service in sysinit.
* debian/keyboard-configuration.links: fix link source for console-setup
service. (LP: #1572697)
* debian/control: add dh-systemd to Build-Depends.
* debian/keyboard-configuration.keyboard-setup.service: also enable
keyboard-setup as a systemd service so we can have proper keymaps enabled
in VTs. (LP: #1579267)
* debian/keyboard-configuration.links: enable keyboard-setup service.

-- Mathieu Trudel-Lapierre Thu, 16 Jun 2016
14:41:19 +0300

** Changed in: console-setup (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/1576893

Title:
console colors are not correctly applied

Status in console-setup package in Ubuntu:
Fix Released
Status in console-setup source package in Xenial:
Fix Released

Bug description:
[Impact]
Debconf prompts are incredibly ugly on virtual console; colors are off from
the "official" aubergine background. This applies to Ubuntu specifically since
other flavors may specify a different color scheme that may not be affected.

[Test case]
1) sudo dpkg-reconfigure debconf

[Regression potential]
None. This only applies to the display colors for a console, and only on a
linux virtual console (ie. not a terminal).

---

At least on Xenial and onwards, our color scheme for the VTs is not
being applied, since setvtrgb is not getting run on boot (it's still
only an upstart job).

Porting setvtrgb to a systemd unit makes the pretty colors appear, and
I can get my debconf/newt prompts back with an aubergine background.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1576893/+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 1572697] Re: broken symlink console-setup.service [systemd]

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package console-setup - 1.108ubuntu15.2

---
console-setup (1.108ubuntu15.2) xenial; urgency=medium

  * Reorganize and correct console-setup, keyboard-setup and setvtrgb along the
lines of the logic in 16.04: (LP: #1591622, #1593156)
- debian/console-setup-linux.setvtrgb.service: don't require being run
  before system-getty.slice.
- debian/keyboard-configuration.links: both console-setup and
  keyboard-setup systemd units should be installed to sysinit.target rather
  than multi-user.
- debian/keyboard-configuration.keyboard-setup.service: move loadkeys call
  at local-fs-pre.target and in this more suitable location.
- debian/keyboard-configuration.console-setup.service: move to running
  after the screen, keyboard, and filesystems are ready and set up all of
  what may still need to be done to configure the virtual consoles
  appropriately: set a final keymap, font, etc.

console-setup (1.108ubuntu15.1) xenial; urgency=medium

  * debian/console-setup-linux.setvtrgb.service: port the upstart job for
applying our preferred color settings to a systemd unit so it gets run.
This will fix debconf prompts on console being extra ugly. (LP: #1576893)
  * debian/console-setup-linux.links: enable our setvtrgb service in sysinit.
  * debian/keyboard-configuration.links: fix link source for console-setup
service. (LP: #1572697)
  * debian/control: add dh-systemd to Build-Depends.
  * debian/keyboard-configuration.keyboard-setup.service: also enable
keyboard-setup as a systemd service so we can have proper keymaps enabled
in VTs. (LP: #1579267)
  * debian/keyboard-configuration.links: enable keyboard-setup service.

 -- Mathieu Trudel-Lapierre   Thu, 16 Jun 2016
14:41:19 +0300

** Changed in: console-setup (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/1572697

Title:
  broken symlink console-setup.service [systemd]

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Console font and other configs from kbd/console-setup may not be applied on 
boot.

  [Test case]
  1) Configure a keymap / key translation table.
  2) Boot the system
  3) Console should have the key translation table applied.

  [Regression potential]
  Minimal; this applies configuration that should always be applied on boot and 
only applies as a fix to a regression from previous releases, and only on a 
virtual console.

  ---

  keyboard-configuration 1.108ubuntu15 contains console-setup.service in
  /lib/systemd/system/multi-user.target.wants, but as a broken symlink:

  $ dpkg -L keyboard-configuration | grep multi-user.target.wants
  /lib/systemd/system/multi-user.target.wants
  /lib/systemd/system/multi-user.target.wants/console-setup.service

  $ sudo find -L /lib/systemd/system -type l -ls
    1315455  0 lrwxrwxrwx   1 root root   22 Apr 20 03:11 
/lib/systemd/system/multi-user.target.wants/console-setup.service -> 
/console-setup.service

  Symlink should point to ../console-setup.service instead.

  I originally reported this in
  https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1534121
  against console-setup, which was the wrong package to refer to. My
  apologies for messing that up.

  Additional info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy keyboard-configuration
  keyboard-configuration:
    Installed: 1.108ubuntu15
    Candidate: 1.108ubuntu15
    Version table:
   *** 1.108ubuntu15 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1572697/+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 1579267] Re: plymouth-start.service: After: reference to non-existent keyboard-setup.service

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package console-setup - 1.108ubuntu15.2

---
console-setup (1.108ubuntu15.2) xenial; urgency=medium

console-setup (1.108ubuntu15.1) xenial; urgency=medium

-- Mathieu Trudel-Lapierre Thu, 16 Jun 2016
14:41:19 +0300

** Changed in: console-setup (Ubuntu Xenial)
Status: Fix Committed => Fix Released

Title:
plymouth-start.service: After: reference to non-existent keyboard-
setup.service

Status in console-setup package in Ubuntu:
Fix Released
Status in console-setup source package in Xenial:
Fix Released

Bug description:
[Impact]
Keymaps are not correctly set on virtual console (in gettys)

[Test case]
Set keymap, using us, intl variant. Test that dead keys behave correctly (ie.
hitting an apostrophe and then e yields "é" rather than "'e".

[Regression potential]
System that carry a keyboard configuration but the system administrators rely
on the fact that the local console keymap remains in US will find that it no
longer behaves as expected.

---

16.04 amd64.

plymouth-start.service refers to a non-existent keyboard-
setup.service:

$ grep keyboard -r /lib/systemd/system/*
/lib/systemd/system/plymouth-start.service:After=systemd-udev-trigger.service
systemd-udevd.service keyboard-setup.service
tj@T300CHI:~$ apt-file search keyboard-setup.service
tj@T300CHI:~$

The file only exists in 16.10 in console-setup-linux

This caught me out whilst I was debugging some console-setup issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1579267/+subscriptions

[Group.of.nepali.translators] [Bug 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 229-4ubuntu7

---
systemd (229-4ubuntu7) xenial-proposed; urgency=medium

  * Add pre-dependency to dpkg >= 1.17.14 on udev, to ensure that
dpkg-maintscript-helper symlink_to_dir is available. (LP: #1585406)
  * Add activation rate limiting for socket units. (LP: #1568094)
  * Split out udev rule to name USB network interfaces by MAC address into
73-usb-net-by-mac.rules, so that it's easier to disable. (Closes: #824025)
  * 73-usb-net-by-mac.rules: Disable when net.ifnames=0 is specified on the
kernel command line or if /etc/udev/rules.d/80-net-setup-link.rules is a
symlink to /dev/null, to be consistent with disabling the *.link files and
the documented way to disable ifnames. (Closes: #824491, LP: #1593379)
  * coredump: Fix "Coredump file descriptor missing". (LP: #1602256)

 -- Martin Pitt   Tue, 12 Jul 2016 17:37:25
+0200

** Changed in: systemd (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/1593379

Title:
  systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or
  /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd package in Debian:
  Fix Released

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB
  devices.

  It appears the regression is here:
  * Set MAC based name for USB network interfaces only for universally
  administered (i. e. stable) MACs, not for locally administered (i. e.
  randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link
  (as link files don't currently support globs for MACAddress=) and replace
  with an udev rule in /lib/udev/rules.d/73-special-net-names.rules.
  (Closes: #812575, LP: #1574483)

  As Raspberry Pi's use eth0 via USB, this breaks running systems.

  Before:
  ii  systemd229-4ubuntu4 armhfsystem and service manager
  ii  udev   229-4ubuntu4 armhf/dev/ and hotplug management daem

  3: eth0:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  After:

  ii  systemd  229-4ubuntu6armhf   
system and service manager
  ii  udev 229-4ubuntu6armhf   
/dev/ and hotplug management daemon

  3: enxb827eb1639e9:  mtu 1500 qdisc 
pfifo_fast state UP mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  cat /proc/cmdline
  dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 
bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 
smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 
vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 
rootfstype=ext4 elevator=deadline rootwait

  With the default interfaces configuration, all networking is lost on
  reboot after upgrade.

  
  SRU TEST CASE
  =
   * Boot with "net.ifnames=0" on the kernel command line, and connect an USB 
ethernet device. It will still be called enxDEADBEEF with current xenial. With 
the -proposed version it will instead keep the kernel name, like "usb0" as 
intended.

   * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules"
  (the other documented way to disable ifnames) and do the above
  connect/name check test again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1585406] Re: package udev 225-1ubuntu9.1 failed to install/upgrade: dpkg-maintscript-helper: error: command symlink_to_dir is unknown

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 229-4ubuntu7

---
systemd (229-4ubuntu7) xenial-proposed; urgency=medium

  * Add pre-dependency to dpkg >= 1.17.14 on udev, to ensure that
dpkg-maintscript-helper symlink_to_dir is available. (LP: #1585406)
  * Add activation rate limiting for socket units. (LP: #1568094)
  * Split out udev rule to name USB network interfaces by MAC address into
73-usb-net-by-mac.rules, so that it's easier to disable. (Closes: #824025)
  * 73-usb-net-by-mac.rules: Disable when net.ifnames=0 is specified on the
kernel command line or if /etc/udev/rules.d/80-net-setup-link.rules is a
symlink to /dev/null, to be consistent with disabling the *.link files and
the documented way to disable ifnames. (Closes: #824491, LP: #1593379)
  * coredump: Fix "Coredump file descriptor missing". (LP: #1602256)

 -- Martin Pitt   Tue, 12 Jul 2016 17:37:25
+0200

** Changed in: systemd (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/1585406

Title:
  package udev 225-1ubuntu9.1 failed to install/upgrade: dpkg-
  maintscript-helper: error: command symlink_to_dir is unknown

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  Died during upgrade from 15.10 x86-64.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 225-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-37.43-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CustomUdevRuleFiles: 60-vboxdrv.rules 51-android.rules 99-lexscan.rules
  Date: Tue May 24 16:29:40 2016
  DuplicateSignature: package:udev:225-1ubuntu9.1:subprocess new pre-removal 
script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2013-05-02 (1118 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Serval WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-37-generic 
root=UUID=1fc67f3a-3070-4bdf-b16d-81d1e5d68535 ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: systemd
  Title: package udev 225-1ubuntu9.1 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-05-24 (0 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Serval WS
  dmi.board.vendor: System76, Inc.
  dmi.board.version: serw9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RS76:bd10/26/2015:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Serval WS
  dmi.product.version: serw9
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1585406/+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 1568094] Re: Many error message such as "Start request repeated too quickly."

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 229-4ubuntu7

---
systemd (229-4ubuntu7) xenial-proposed; urgency=medium

  * Add pre-dependency to dpkg >= 1.17.14 on udev, to ensure that
dpkg-maintscript-helper symlink_to_dir is available. (LP: #1585406)
  * Add activation rate limiting for socket units. (LP: #1568094)
  * Split out udev rule to name USB network interfaces by MAC address into
73-usb-net-by-mac.rules, so that it's easier to disable. (Closes: #824025)
  * 73-usb-net-by-mac.rules: Disable when net.ifnames=0 is specified on the
kernel command line or if /etc/udev/rules.d/80-net-setup-link.rules is a
symlink to /dev/null, to be consistent with disabling the *.link files and
the documented way to disable ifnames. (Closes: #824491, LP: #1593379)
  * coredump: Fix "Coredump file descriptor missing". (LP: #1602256)

 -- Martin Pitt   Tue, 12 Jul 2016 17:37:25
+0200

** Changed in: systemd (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/1568094

Title:
  Many error message such as "Start request repeated too quickly."

Status in laptop-mode-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in laptop-mode-tools source package in Xenial:
  New
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  * Analysis:

  The error messages are caused by a bad interaction between systemd and
  laptop-mode-tools.

  * Fixes:

  There is a fix in systemd:
  https://github.com/systemd/systemd/pull/3148

  The problem can also be fixed by updating laptop-mode-tools.

  * Symptoms:

  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: Starting Show Plymouth Boot Screen...
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee

[Group.of.nepali.translators] [Bug 1602256] Re: sometimes "systemd-coredump[]: Coredump file descriptor missing." is seen, upstream #2984

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 229-4ubuntu7

---
systemd (229-4ubuntu7) xenial-proposed; urgency=medium

  * Add pre-dependency to dpkg >= 1.17.14 on udev, to ensure that
dpkg-maintscript-helper symlink_to_dir is available. (LP: #1585406)
  * Add activation rate limiting for socket units. (LP: #1568094)
  * Split out udev rule to name USB network interfaces by MAC address into
73-usb-net-by-mac.rules, so that it's easier to disable. (Closes: #824025)
  * 73-usb-net-by-mac.rules: Disable when net.ifnames=0 is specified on the
kernel command line or if /etc/udev/rules.d/80-net-setup-link.rules is a
symlink to /dev/null, to be consistent with disabling the *.link files and
the documented way to disable ifnames. (Closes: #824491, LP: #1593379)
  * coredump: Fix "Coredump file descriptor missing". (LP: #1602256)

 -- Martin Pitt   Tue, 12 Jul 2016 17:37:25
+0200

** Changed in: systemd (Ubuntu Xenial)
   Status: Triaged => Fix Released

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

Title:
  sometimes "systemd-coredump[]: Coredump file descriptor missing."
  is seen, upstream #2984

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New

Bug description:
  Please include this upstream fix/pull request:

  coredump: use next_datagram_size_fd instead of ioctl(FIONREAD) #3237
  https://github.com/systemd/systemd/pull/3237

  Reported as
  sometimes "systemd-coredump[]: Coredump file descriptor missing." is 
seen, upstream #2984
  https://github.com/systemd/systemd/issues/2984

  Or make a release using systemd tag=v230

   :~$ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04

  :~$ apt-cache policy systemd
  systemd:
    Installed: 229-4ubuntu6
    Candidate: 229-4ubuntu6
    Version table:
   *** 229-4ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  SRU INFORMATION
  ---
  This only affects systemd-coredump which we don't use in Ubuntu by default 
(we use Apport), so the regression potential is very low. There is no 
straightforward reproducer for this (see upstream bug report: 
https://github.com/systemd/systemd/issues/2984). But our systemd package has 
integration tests for coredump: 
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/tests/boot-and-services?h=ubuntu-xenial#n436
 

  Thus if the updated package still succeeds its autopkgtests, this
  should provide sufficient regression testing for this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1602256/+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 1602256] Re: sometimes "systemd-coredump[]: Coredump file descriptor missing." is seen, upstream #2984

2016-07-18 Thread Martin Pitt

Reopening as LeK said in comment #4 that this cherry-pick did not help
in his case.

** Changed in: systemd (Ubuntu Xenial)
   Status: Fix Released => 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/1602256

Title:
  sometimes "systemd-coredump[]: Coredump file descriptor missing."
  is seen, upstream #2984

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New

Bug description:
  Please include this upstream fix/pull request:

  coredump: use next_datagram_size_fd instead of ioctl(FIONREAD) #3237
  https://github.com/systemd/systemd/pull/3237

  Reported as
  sometimes "systemd-coredump[]: Coredump file descriptor missing." is 
seen, upstream #2984
  https://github.com/systemd/systemd/issues/2984

  Or make a release using systemd tag=v230

   :~$ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04

  :~$ apt-cache policy systemd
  systemd:
    Installed: 229-4ubuntu6
    Candidate: 229-4ubuntu6
    Version table:
   *** 229-4ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  SRU INFORMATION
  ---
  This only affects systemd-coredump which we don't use in Ubuntu by default 
(we use Apport), so the regression potential is very low. There is no 
straightforward reproducer for this (see upstream bug report: 
https://github.com/systemd/systemd/issues/2984). But our systemd package has 
integration tests for coredump: 
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/tests/boot-and-services?h=ubuntu-xenial#n436
 

  Thus if the updated package still succeeds its autopkgtests, this
  should provide sufficient regression testing for this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1602256/+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 1570093] Re: multipath-tools update introduced syslog messages about partx

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package multipath-tools -
0.5.0+git1.656f8865-5ubuntu4

---
multipath-tools (0.5.0+git1.656f8865-5ubuntu4) yakkety; urgency=medium

  [ Dragan Stancevic ]
  * multipath-tools: fix dm- device filtering
   - Allow filtering of DEV_UEVENT dev_type
   - Resolves LP: #1570093

 -- Louis Bouchard   Mon, 18 Jul 2016
12:37:04 +0200

** Changed in: multipath-tools (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  multipath-tools update introduced syslog messages about partx

Status in multipath-tools package in Ubuntu:
  Fix Released
Status in multipath-tools source package in Xenial:
  New
Status in multipath-tools package in Debian:
  New

Bug description:
  During a path loss event, the syslog is showing these messages where
  prior to the recent upgrade to multipath-tools I didn't see anything
  like this.  To me this seems like either a problem or it seems like a
  print message that should go into a different log file.

  Apr 13 11:21:00 ICTM1618S01H4 systemd-udevd[14861]: Process '/usr/bin/partx 
-d --nr 1-1024 /dev/sdam' failed with exit code 1.
  ...
  Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get udev uid: 
Invalid argument
  Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get sysfs uid: 
Invalid argument
  Apr 13 11:21:00 ICTM1618S01H4 multipath: dm-15: failed to get sgio uid: No 
such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: multipath-tools 0.5.0+git1.656f8865-5ubuntu2
  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
  Date: Wed Apr 13 15:29:36 2016
  SourcePackage: multipath-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+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 1603975] [NEW] thinkpad yoga 260 wacom touchscreen not working

2016-07-18 Thread Chris J Arges

Public bug reported:

[Impact]
Users of Lenovo Thinkpad Yoga 260 laptops can't use the touchscreen if it has 
been deactivated from Windows beforehand.

[Fix]
d4a9689 HID: wacom: Support switching from vendor-defined device mode on G9 and 
G11
967143a HID: wacom: Initialize hid_data.inputmode to -1
b107ac0 HID: wacom: break out parsing of device and registering of input


d4a9689 is the actual fix and the two others make this a clean cherry-pick.

[Test Case]
On a Lenovo Thinkpad Yoga 260, try using the touchscreen.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  arges  2392 F pulseaudio
CurrentDesktop: Unity
Date: Mon Jul 18 07:20:48 2016
HibernationDevice: RESUME=UUID=0e49e62b-8bc0-48ef-8e7c-bcce9770d74b
InstallationDate: Installed on 2016-07-16 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20FD0004US
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-31-generic N/A
 linux-backports-modules-4.4.0-31-generic  N/A
 linux-firmware1.157.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/16/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N1GET35W (1.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FD0004US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET35W(1.12):bd11/16/2015:svnLENOVO:pn20FD0004US:pvrThinkPadYoga260:rvnLENOVO:rn20FD0004US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20FD0004US
dmi.product.version: ThinkPad Yoga 260
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Chris J Arges (arges)
 Status: In Progress


** Tags: amd64 apport-bug xenial

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Chris J Arges (arges)

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

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: linux (Ubuntu)
 Assignee: Chris J Arges (arges) => (unassigned)

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

Title:
  thinkpad yoga 260 wacom touchscreen not working

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

Bug description:
  [Impact]
  Users of Lenovo Thinkpad Yoga 260 laptops can't use the touchscreen if it has 
been deactivated from Windows beforehand.

  [Fix]
  d4a9689 HID: wacom: Support switching from vendor-defined device mode on G9 
and G11
  967143a HID: wacom: Initialize hid_data.inputmode to -1
  b107ac0 HID: wacom: break out parsing of device and registering of input

  
  d4a9689 is the actual fix and the two others make this a clean cherry-pick.

  [Test Case]
  On a Lenovo Thinkpad Yoga 260, try using the touchscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arges  2392 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 18 07:20:48 2016
  HibernationDevice: RESUME=UUID=0e49e62b-8bc0-48ef-8e7c-bcce9770d74b
  InstallationDate: Installed on 2016-07-16 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20FD0004US
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET35W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FD0004US
  dmi.board.vendor: LENOVO

[Group.of.nepali.translators] [Bug 1103593] Re: Unity always shows all devices in launcher when CD is inserted

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity - 7.4.0+16.04.20160715-0ubuntu1

---
unity (7.4.0+16.04.20160715-0ubuntu1) xenial; urgency=medium

  [ Eleni Maria Stea ]
  * PanelView: Don't draw it if the geo doesn't intersect the monitor
geo (as in ezoom)
  * speeds up the showdesktop plugin in lowgfx mode

  [ Andrea Azzarone ]
  * Add whitelist for auto-repated keys. (LP: #1586491)
  * Fix scale window activation if in show desktop mode. (LP: #1582056)
  * Order matters in the rendering. Draw launcher shadow after the
background in all cases. (LP: #1586374)
  * Fallback to volume name if no other identifier is available. (LP:
#1103593)
  * Do not trigger screensaver on session inactive. (LP: #1587507)
  * Use SwitcherController::SetDetail instead of detail=... (LP:
#1587618)
  * UnitySettings: Add an option to enable/disable pam account checking.
(LP: #1460649)
  * Lockscreen: Make sure warning and errors are properly shown to the
user (LP: #1593696)
  * Add missing header to fix compilation error with -Duse_pch=OFF.
  * Filter out fullscreen window in show desktop mode. (LP: #1597706)
  * Make sure file manager icon is not removed when unpinned. (LP:
#1578792)
  * Properly calculate the intersection geometry in PanelView::Draw.
This is needed to properly call SyncGeometries and to avoid problems
such as lp:1595698. (LP: #1595698)

  [ Alberto Milone ]
  * UnitySettings: Add dconf keys for disabling multitouch gestures (LP:
#1589520)

  [ Marco Trevisan (Treviño) ]
  * LockScreenAcceleratorController: use key::Grabber to handle allowed
bindings (LP: #1438754)
  * LockScreenAcceleratorController: check if a setting key is available
instead of crashing
  * ApplicationLauncherIcon: ensure quirks are properly set on icon
initialization
  * Views: Toggle animators durations based on low-gfx setting (LP:
#1598770)
  * unity7.conf: use different compiz profile based on
unity_support_test result (LP: #1598770)

 -- Marco Trevisan (Treviño)   Fri, 15 Jul 2016 10:14:41
+

** Changed in: unity (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/1103593

Title:
  Unity always shows all devices in launcher when CD is inserted

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

Bug description:
  [Impact]
  In Ubuntu 12.10 the default behavior when inserting a CD (or a USB memory 
stick, etc.) is to add a list of mounted devices to the launcher.  This takes 
up a lot of extra space for me as I usually have several Samba mounts.  
Furthermore, I don't need or want to see my CD in the launcher.

  I can click right on the mounted devices and select "Unlock from
  launcher", but the next time I insert a CD they're back.  Disabling
  this "feature" should be an option in 12.10.  I believe it was an
  option in 12.04 via CCSM.   Thanks.

  [Test Case]
  1. Add an usb memory stick to device blacklist
  2. Mount a cd 
  3. Make sure the usb is still blacklisted.

  [Possible Rgressions]
  Nothing known.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1103593/+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 1582340] Re: [SRU] Sync drupal7 7.43-3 (universe) from Debian unstable (main)

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package drupal7 - 7.44-1ubuntu1~16.04.0

---
drupal7 (7.44-1ubuntu1~16.04.0) xenial; urgency=medium

  * Backport a version of drupal7 to Ubuntu 16.04 LTS that is
installable with php7 (LP: #1582340)

drupal7 (7.44-1ubuntu1) yakkety; urgency=medium

  * Depend on php-xml (LP: #1595788)

drupal7 (7.44-1) unstable; urgency=high

  * New upstream version
  * Fixes a security vulnerability (SA-CORE-2016-002): Privilege
escalation (within the webapp users realm)

drupal7 (7.43-3) unstable; urgency=medium

  * Moved the farbstatic sources from debian/missing-sources
todebian/missing-sources/misc, to keep lintian happy
  * The right name for one of our conditional dependencies is no longer
php-sqlite, but php-sqlite3. Thanks to Nish Aravamudan for pointing
this out!

drupal7 (7.43-2) unstable; urgency=medium

  * Update dependencies to use PHP 7 instead of 5 (Closes: #821482)
  * Updated debian/watch to work reliably
  * Standards-version 3.9.6.0→3.9.8 (no changes needed)

drupal7 (7.43-1) unstable; urgency=high

  * New upstream version
  * Fixes several security vulnerabilities (SA-CORE-2016-001): File
upload access bypass and DoS, brute force amplification attack via
XML-RPC, open redirect via path manipulation, reflected file
download, wrong modes set on some user accounts setting saves,
information disclosure of email addresses
  * Several non-security bugfixes from 7.42 included
  * Fix typo in README.Debian
  * Add several needed lintian overrides

 -- Jeremy Bicha   Fri, 24 Jun 2016 13:29:56 -0400

** Changed in: drupal7 (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/1582340

Title:
  [SRU] Sync drupal7 7.43-3 (universe) from Debian unstable (main)

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

Bug description:
  Drupal7 in 16.04 has been left as broken while we wait on upstream
  Drupal7 to gain PHP7.0 compatibility. This has been achieved in
  Debian's current version, which we should be able to sync as we have
  no delta currently.

  [Impact]

   * drupal7 is currently uninstallable in 16.04.

  [Test Case]

   * There is no test case for this issue, other than attempting to
  install drupal7 itself, which will currently fail due to php5
  dependencies.

  [Regression Potential]

   * As drupal7 is currently uninstallable, there is no possibility of
  regression in 16.04 itself.

  [Other Info]
   
   * To reiterate, the plan for drupal7 in 16.04 was to wait for PHP7 
compatibility to be available and to SRU in the corresponding version.

  Please sync drupal7 7.43-3 (universe) from Debian unstable (main)

  Changelog entries since current xenial version 7.41-1:

  drupal7 (7.43-3) unstable; urgency=medium

    * Moved the farbstatic sources from debian/missing-sources
  todebian/missing-sources/misc, to keep lintian happy
    * The right name for one of our conditional dependencies is no longer
  php-sqlite, but php-sqlite3. Thanks to Nish Aravamudan for pointing
  this out!

   -- Gunnar Wolf   Mon, 09 May 2016 12:25:34 -0500

  drupal7 (7.43-2) unstable; urgency=medium

    * Update dependencies to use PHP 7 instead of 5 (Closes: #821482)
    * Updated debian/watch to work reliably
    * Standards-version 3.9.6.0→3.9.8 (no changes needed)

   -- Gunnar Wolf   Mon, 09 May 2016 10:54:11 -0500

  drupal7 (7.43-1) unstable; urgency=high

    * New upstream version
    * Fixes several security vulnerabilities (SA-CORE-2016-001): File
  upload access bypass and DoS, brute force amplification attack via
  XML-RPC, open redirect via path manipulation, reflected file
  download, wrong modes set on some user accounts setting saves,
  information disclosure of email addresses
    * Several non-security bugfixes from 7.42 included
    * Fix typo in README.Debian
    * Add several needed lintian overrides

   -- Gunnar Wolf   Thu, 25 Feb 2016 22:43:55 -0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drupal7/+bug/1582340/+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 1571640] Re: unity-greeter scaling factor changes after a delay

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity-settings-daemon -
15.04.1+16.04.20160701-0ubuntu1

---
unity-settings-daemon (15.04.1+16.04.20160701-0ubuntu1) xenial; urgency=medium

  [ Robert Ancell ]
  * Correctly check value of XDG_CURRENT_DESKTOP.

  [ Marco Trevisan (Treviño) ]
  * PowerManager: connect to keyboard BrightnessChanged signal to update
the cached current value properly (LP: #1510344)
  * GsdPowerManager: don't cache kbd backlight current value (LP:
#1583861)
  * common: backport g-s-d commits for having single shared dbus proxies
  * ScreensaverProxy: redirect supported calls to gnome screensaver APIs
(LP: #1415265, LP: #1584161)

  [ Sebastien Bacher ]
  * Don't hit an xerror when a device is removed while being configured
(LP: #1503758)
  * wacom: don't segfault when a device is removed while being
configured. (LP: #1439427)

  [ Marco Trevisan (Treviño) ]
  * GsdPowerManager: use proper return value for upower_kbd_toggle
wherever we use it (LP: #1592816)

  [ Kai-Heng Feng ]
  * SettingsManager: Queue up signals before getting D-Bus connection.
(LP: #1571640)

 -- Marco Trevisan (Treviño)   Fri, 01 Jul 2016 13:28:54
+

** Changed in: unity-settings-daemon (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/1571640

Title:
  unity-greeter scaling factor changes after a delay

Status in unity-greeter package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-greeter source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in unity-greeter source package in Yakkety:
  Fix Released
Status in unity-settings-daemon source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * Unity Greeter does not have the right scale at the beginning, after
  a short delay, it changes to the right scale.

  [Test Case]

   * It can be easily observed on HiDPI display, when Unity Greeter is
  starting.

  [Regression Potential]

   * If u-s-d failed to launch, Unity Greeter stuck at waiting u-s-d's
  signal and failed to proceed. But it's not likely to happen.

  

  Just after the upgrade to ubuntu 16.04, when lightdm starts the
  resolution is 2560x1600. Then, after about half a second it is
  automatically changed to 1280x800. This happens systematically at each
  boot. No external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:39:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (525 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1571640/+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 1460649] Re: Can't unlock screen with last day password (before expired)

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity - 7.4.0+16.04.20160715-0ubuntu1

---
unity (7.4.0+16.04.20160715-0ubuntu1) xenial; urgency=medium

  [ Eleni Maria Stea ]
  * PanelView: Don't draw it if the geo doesn't intersect the monitor
geo (as in ezoom)
  * speeds up the showdesktop plugin in lowgfx mode

  [ Andrea Azzarone ]
  * Add whitelist for auto-repated keys. (LP: #1586491)
  * Fix scale window activation if in show desktop mode. (LP: #1582056)
  * Order matters in the rendering. Draw launcher shadow after the
background in all cases. (LP: #1586374)
  * Fallback to volume name if no other identifier is available. (LP:
#1103593)
  * Do not trigger screensaver on session inactive. (LP: #1587507)
  * Use SwitcherController::SetDetail instead of detail=... (LP:
#1587618)
  * UnitySettings: Add an option to enable/disable pam account checking.
(LP: #1460649)
  * Lockscreen: Make sure warning and errors are properly shown to the
user (LP: #1593696)
  * Add missing header to fix compilation error with -Duse_pch=OFF.
  * Filter out fullscreen window in show desktop mode. (LP: #1597706)
  * Make sure file manager icon is not removed when unpinned. (LP:
#1578792)
  * Properly calculate the intersection geometry in PanelView::Draw.
This is needed to properly call SyncGeometries and to avoid problems
such as lp:1595698. (LP: #1595698)

  [ Alberto Milone ]
  * UnitySettings: Add dconf keys for disabling multitouch gestures (LP:
#1589520)

  [ Marco Trevisan (Treviño) ]
  * LockScreenAcceleratorController: use key::Grabber to handle allowed
bindings (LP: #1438754)
  * LockScreenAcceleratorController: check if a setting key is available
instead of crashing
  * ApplicationLauncherIcon: ensure quirks are properly set on icon
initialization
  * Views: Toggle animators durations based on low-gfx setting (LP:
#1598770)
  * unity7.conf: use different compiz profile based on
unity_support_test result (LP: #1598770)

 -- Marco Trevisan (Treviño)   Fri, 15 Jul 2016 10:14:41
+

** Changed in: unity (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/1460649

Title:
  Can't unlock screen with last day password (before expired)

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

Bug description:
  [Impact]

  When I login with last day password, all ok. But when I locked screen, I 
can't unlock it, receive error «Invalid password, please try again».
  I think, this bug more globally — «unity-panel-service --lockscreen-mode» 
does not have function for changing user password.

  
  [Test case]
  How to reproduce:

  You need working LDAP-server and Ubuntu with LDAP client. My client,
  Ubuntu 14.04:

  cat

[Group.of.nepali.translators] [Bug 1438754] Re: Backlight cannot be adjusted at lock screen

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity - 7.4.0+16.04.20160715-0ubuntu1

---
unity (7.4.0+16.04.20160715-0ubuntu1) xenial; urgency=medium

  [ Eleni Maria Stea ]
  * PanelView: Don't draw it if the geo doesn't intersect the monitor
geo (as in ezoom)
  * speeds up the showdesktop plugin in lowgfx mode

  [ Andrea Azzarone ]
  * Add whitelist for auto-repated keys. (LP: #1586491)
  * Fix scale window activation if in show desktop mode. (LP: #1582056)
  * Order matters in the rendering. Draw launcher shadow after the
background in all cases. (LP: #1586374)
  * Fallback to volume name if no other identifier is available. (LP:
#1103593)
  * Do not trigger screensaver on session inactive. (LP: #1587507)
  * Use SwitcherController::SetDetail instead of detail=... (LP:
#1587618)
  * UnitySettings: Add an option to enable/disable pam account checking.
(LP: #1460649)
  * Lockscreen: Make sure warning and errors are properly shown to the
user (LP: #1593696)
  * Add missing header to fix compilation error with -Duse_pch=OFF.
  * Filter out fullscreen window in show desktop mode. (LP: #1597706)
  * Make sure file manager icon is not removed when unpinned. (LP:
#1578792)
  * Properly calculate the intersection geometry in PanelView::Draw.
This is needed to properly call SyncGeometries and to avoid problems
such as lp:1595698. (LP: #1595698)

  [ Alberto Milone ]
  * UnitySettings: Add dconf keys for disabling multitouch gestures (LP:
#1589520)

  [ Marco Trevisan (Treviño) ]
  * LockScreenAcceleratorController: use key::Grabber to handle allowed
bindings (LP: #1438754)
  * LockScreenAcceleratorController: check if a setting key is available
instead of crashing
  * ApplicationLauncherIcon: ensure quirks are properly set on icon
initialization
  * Views: Toggle animators durations based on low-gfx setting (LP:
#1598770)
  * unity7.conf: use different compiz profile based on
unity_support_test result (LP: #1598770)

 -- Marco Trevisan (Treviño)   Fri, 15 Jul 2016 10:14:41
+

** Changed in: unity (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/1438754

Title:
  Backlight cannot be adjusted at lock screen

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

Bug description:
  [Inpact]

  This affects 14.04 LTS. I haven't tried any more recent versions.

  When the screen is locked, it is not possible to use the Fn+Brightness
  up/down keys.

  If I am using an external monitor, then I turn down the backlight
  brightness to zero. I often use my laptop at the office with an
  external monitor and the backlight turned off.  When I come home and
  resume, the backlight is off and I cannot switch it on to see the
  login prompt.

  
  [Test Case]

  Steps to reproduce
  1. Set backlight brightness to off using Fn+brightness down
  2. Lock computer with Super+L
  3. Attempt to increase brightness with Fn+brightness up

  Expected results:
  Backlight switches on, and Lock/login screen becomes visible

  Actual results:
  Backlight remains off and Lock/login screen is not visible

  
  [Regression Potential] 

  Some media-key bindings couldn't work as expected (so keys for
  suspension, volume control, power...)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1438754/+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 1578792] Re: nautilus/files doesn't show up in the launcher when unpinned

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity - 7.4.0+16.04.20160715-0ubuntu1

---
unity (7.4.0+16.04.20160715-0ubuntu1) xenial; urgency=medium

  [ Eleni Maria Stea ]
  * PanelView: Don't draw it if the geo doesn't intersect the monitor
geo (as in ezoom)
  * speeds up the showdesktop plugin in lowgfx mode

  [ Andrea Azzarone ]
  * Add whitelist for auto-repated keys. (LP: #1586491)
  * Fix scale window activation if in show desktop mode. (LP: #1582056)
  * Order matters in the rendering. Draw launcher shadow after the
background in all cases. (LP: #1586374)
  * Fallback to volume name if no other identifier is available. (LP:
#1103593)
  * Do not trigger screensaver on session inactive. (LP: #1587507)
  * Use SwitcherController::SetDetail instead of detail=... (LP:
#1587618)
  * UnitySettings: Add an option to enable/disable pam account checking.
(LP: #1460649)
  * Lockscreen: Make sure warning and errors are properly shown to the
user (LP: #1593696)
  * Add missing header to fix compilation error with -Duse_pch=OFF.
  * Filter out fullscreen window in show desktop mode. (LP: #1597706)
  * Make sure file manager icon is not removed when unpinned. (LP:
#1578792)
  * Properly calculate the intersection geometry in PanelView::Draw.
This is needed to properly call SyncGeometries and to avoid problems
such as lp:1595698. (LP: #1595698)

  [ Alberto Milone ]
  * UnitySettings: Add dconf keys for disabling multitouch gestures (LP:
#1589520)

  [ Marco Trevisan (Treviño) ]
  * LockScreenAcceleratorController: use key::Grabber to handle allowed
bindings (LP: #1438754)
  * LockScreenAcceleratorController: check if a setting key is available
instead of crashing
  * ApplicationLauncherIcon: ensure quirks are properly set on icon
initialization
  * Views: Toggle animators durations based on low-gfx setting (LP:
#1598770)
  * unity7.conf: use different compiz profile based on
unity_support_test result (LP: #1598770)

 -- Marco Trevisan (Treviño)   Fri, 15 Jul 2016 10:14:41
+

** Changed in: unity (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/1578792

Title:
  nautilus/files doesn't show up in the launcher when unpinned

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

Bug description:
  [Impact]

  When nautilus is unpinned, it doesn't show up in the launcher. When
  it's pinned, you can see the open windows with arrows on the side as
  usual, and switch between windows if there are several of them. But
  when I unpin it, it will disappear entirely. Sometimes when I open it,
  it will display for one second and then disappear.

  [Test case]

   - Unpin nautilus from launcher (via quicklist or trashing it)
   - launch "Files" from dash
   - Nautilus icon should stay in the launcher until the file manager is opened

  [Regresion potential]

  Nautilus icon might stay there also if not pineed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  5 21:29:59 2016
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x494+2091+171'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2016-01-22 (103 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1578792/+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 1582056] Re: Switching windows in Unity fails to bring program to foreground

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity - 7.4.0+16.04.20160715-0ubuntu1

---
unity (7.4.0+16.04.20160715-0ubuntu1) xenial; urgency=medium

  [ Eleni Maria Stea ]
  * PanelView: Don't draw it if the geo doesn't intersect the monitor
geo (as in ezoom)
  * speeds up the showdesktop plugin in lowgfx mode

  [ Andrea Azzarone ]
  * Add whitelist for auto-repated keys. (LP: #1586491)
  * Fix scale window activation if in show desktop mode. (LP: #1582056)
  * Order matters in the rendering. Draw launcher shadow after the
background in all cases. (LP: #1586374)
  * Fallback to volume name if no other identifier is available. (LP:
#1103593)
  * Do not trigger screensaver on session inactive. (LP: #1587507)
  * Use SwitcherController::SetDetail instead of detail=... (LP:
#1587618)
  * UnitySettings: Add an option to enable/disable pam account checking.
(LP: #1460649)
  * Lockscreen: Make sure warning and errors are properly shown to the
user (LP: #1593696)
  * Add missing header to fix compilation error with -Duse_pch=OFF.
  * Filter out fullscreen window in show desktop mode. (LP: #1597706)
  * Make sure file manager icon is not removed when unpinned. (LP:
#1578792)
  * Properly calculate the intersection geometry in PanelView::Draw.
This is needed to properly call SyncGeometries and to avoid problems
such as lp:1595698. (LP: #1595698)

  [ Alberto Milone ]
  * UnitySettings: Add dconf keys for disabling multitouch gestures (LP:
#1589520)

  [ Marco Trevisan (Treviño) ]
  * LockScreenAcceleratorController: use key::Grabber to handle allowed
bindings (LP: #1438754)
  * LockScreenAcceleratorController: check if a setting key is available
instead of crashing
  * ApplicationLauncherIcon: ensure quirks are properly set on icon
initialization
  * Views: Toggle animators durations based on low-gfx setting (LP:
#1598770)
  * unity7.conf: use different compiz profile based on
unity_support_test result (LP: #1598770)

 -- Marco Trevisan (Treviño)   Fri, 15 Jul 2016 10:14:41
+

** Changed in: unity (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/1582056

Title:
  Switching windows in Unity fails to bring program to foreground

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

Bug description:
  This bug has been, well, bugging me for a while. It was hard to
  reproduce but I have finally found a way to reproduce it. I think
  there is more than one way of reproducing this bug.

  [Impact]
  After activating the "Show Desktop" mode switching windows using the scale 
plugin fails to properly bring the correct window to foreground.

  [Test Case]
  Here is what worked for me.

  Three Gnome Terminals open, and Chromium.
  Click on "Show Desktop" or ALT-TAB to "Show Desktop".
  Now Click On Terminal in the Unity Launcher, and it will bring up the last 
active terminal.
  Click on the Terminal again, and you will be presented with a selection 
window to pick one of three terminals.
  Pick anything other than the active terminal.
  The new active terminal will come to the foreground, and immediately 
disappear.
  The old active terminal will remain on the screen.

  This bug has been present since at least Ubuntu 14.10.

  [Possible Regressions]
  Nothing known.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1582056/+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 1582433] Re: Dash does not handle .desktop files correctly if there are hyphens in the directory path

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity-lens-applications -
7.1.0+16.04.20160701-0ubuntu1

---
unity-lens-applications (7.1.0+16.04.20160701-0ubuntu1) xenial; urgency=medium

  [ Andrea Azzarone ]
  * Fallback from pkginfo.application_name in case app is NULL. (LP:
#1582433)

 -- Marco Trevisan (Treviño)   Fri, 01 Jul 2016 10:44:01
+

** Changed in: unity-lens-applications (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/1582433

Title:
  Dash does not handle .desktop files correctly if there are hyphens in
  the directory path

Status in unity-lens-applications package in Ubuntu:
  Fix Released
Status in unity-lens-applications source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  The Unity dash can fail to display the icon or title from a .desktop
  file correctly if it resides under a directory containing a hyphen
  character.

  [Test case]

  As an example (on my 16.04 machine):

  $ cat << EOF > test.desktop
  [Desktop Entry]
  Name=Hyphen test
  Exec=/bin/true
  Type=Application
  Icon=/usr/share/icons/suru/apps/256/dash.png
  EOF

  $ chmod +x test.desktop
  $ mkdir ~/.local/share/applications/hyphen-test
  $ mv test.desktop ~/.local/share/applications/hyphen-test/

  Now, open the dash and search for "hyphen". On my machine, I see the
  correct icon but no title is displayed underneath.

  $ mv ~/.local/share/applications/hyphen-test
  ~/.local/share/applications/hyphen

  Searching for "hyphen" in the dash now shows an entry with the correct
  icon and title (but also still shows the defunct previous entry
  without title).

  The effect of the hyphenated path seems variable. Some apps show the
  wrong icon, some have a missing title, some have both errors.

  The problem only seems to be with hyphens in the directories. Hyphens
  in the file itself are fine. See the screenshot - Might and Magic 4&5
  has had a desktop file installed under a subdirectory with a hyphen,
  whereas Heroes of Might and Magic has a desktop file in the root
  directory but contains a hyphen in the filename. The latter is shown
  correctly, but the desktop files in the former directory are not shown
  properly.

  [Possible Regressions]
  Nothing known.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1582433/+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 1575460] Re: Intel video driver not installed by default on Lubuntu 16.04 fresh install

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package lubuntu-meta - 0.65.1

---
lubuntu-meta (0.65.1) xenial-proposed; urgency=medium

  * Refreshed dependencies
  * Added xserver-xorg-video-intel to core [amd64 i386] (LP: #1575460)

 -- Julien Lavergne   Mon, 04 Jul 2016 22:52:54 +0200

** Changed in: lubuntu-meta (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/1575460

Title:
  Intel video driver not installed by default on Lubuntu 16.04 fresh
  install

Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in lubuntu-meta source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * xserver-xorg-video-intel is not included in Lubuntu ISO because it
  switched to recommends on the common seeds. Since Lubuntu ISO doesn't
  include recommends, so xserver-xorg-video-intel is missing (but
  included on other flavors).

   * xserver-xorg-video-intel is not mandatory for Intel users, but it
  needs a recent hardware to work correctly. According to the packages
  description :

  "The use of this driver is discouraged if your hw is new enough (ca. 2007
  and newer). You can try uninstalling this driver and let the server use
  it's builtin modesetting driver instead."

   * However, Lubuntu targets old hardwares, and there are a lot of
  reports from Intel users that, without this drivers, X doesn't load.

  [Test Case]

   * Install Lubuntu 16.04 with an official 16.04 ISO, on a system with an 
Intel graphic device.
   * Boot on the installed system, and the boot process should stop before X is 
loading.
   * To confirm the fix, install manually xserver-xorg-video-intel and boot 
again.

  [Regression Potential]

   * Stick with the old driver may have an impact on the performances of
  the driver (the new one should be better for 3D and others graphic
  stuff).

   * However, others flavors kept this driver on the ISO, and according
  to the reports, it's probably safe to keep this driver for now.

  [Original report]

  I did a new installation of Lubuntu 16.04 LTS on a intel atom netbook
  installation completes with any problem.

  On booting the installed system i only got a black screen with the message: 
"/dev/sda1: clean, 121563/920272 files"
  I've changed to a terminal (CTRL+ALT+F1), and reading logs i've
   found xserver-xorg-video-intel package is NOT INSTALLED

  installed the xserver-xorg-video-intel package, and everything works
  ok now.

  Tried again with other computers (intel gpu all) and i've downloaded
  the iso again and still happens

  can confirm this happen to at least other two people on ubuntu forums:

  http://ubuntuforums.org/showthread.php?t=2322111
  http://ubuntuforums.org/showthread.php?t=2321916

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1575460/+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 1557026] Re: [SRU]Network Manager sets powersave off by default in xenial

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package network-manager -
1.2.0-0ubuntu0.16.04.3

---
network-manager (1.2.0-0ubuntu0.16.04.3) xenial; urgency=medium

  * cli-initialize-connection-list-in-do_device_connect.patch:
Make sure connection list available for nmc_secrets_requested().
(LP: #1595707).
  * Removing default_powersave_on.patch, and instead install config
file that accomplishes the same (LP: #1557026)
  * Fix invalid nmcli option in bug report script
debian/source_network-manager.py (LP: #1582803)

 -- Aron Xu   Tue, 05 Jul 2016 16:01:03 +0800

** Changed in: network-manager (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/1557026

Title:
  [SRU]Network Manager sets powersave off by default in xenial

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  NetworkManager consumes more power than previous releases because powersave 
support is not updated.

  [Test Case]
  With the patch applied, network device power management should be on when 
supported, for example:

  $ sudo iwconfig wlan0 | grep "Power Management"
Power Management:on

  [Regression Potential]
  Regression may happen when the power management feature of certain device 
isn't implemented properly in kernel, but since we are quite conservative on 
enabling power management in kernel development such case should be rare.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1557026/+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 1304388] Re: unity-control-center crashed with SIGSEGV in default_app_changed()

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity-control-center -
15.04.0+16.04.20160705-0ubuntu1

---
unity-control-center (15.04.0+16.04.20160705-0ubuntu1) xenial; urgency=medium

  [ Trent Lloyd ]
  * Fix crash when application supports no mime-type (LP: #1304388)

  [ Marco Trevisan (Treviño) ]
  * CcAppearancePanel: read COMPIZ_CONFIG_PROFILE value to choose the
right settings path (LP: #1598770)

 -- Marco Trevisan (Treviño)   Tue, 05 Jul 2016 14:48:55
+

** Changed in: unity-control-center (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/1304388

Title:
  unity-control-center crashed with SIGSEGV in default_app_changed()

Status in unity-control-center package in Ubuntu:
  Fix Released
Status in unity-control-center source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Crash report and bug appeared straight after boot, cause unknown, though 
system went on to run normally after.
  Ubuntu 14.04 Beta 2

  [Test case]
  Set Firefox Nightly as default browser
  UCC should not crash in that case

  [Regression potential]
  This is a null-pointer check, there's nothing to worry about.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140407-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Apr  8 13:25:48 2014
  ExecutablePath: /usr/bin/unity-control-center
  ProcCmdline: unity-control-center
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xac26dcbd:mov(%eax),%ecx
   PC (0xac26dcbd) ok
   source "(%eax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/unity-control-center-1/panels/libinfo.so
   g_cclosure_marshal_VOID__VOID () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: unity-control-center crashed with SIGSEGV in 
g_cclosure_marshal_VOID__VOID()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1304388/+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 1503758] Re: /usr/lib/unity-settings-daemon/unity-settings-daemon:5:XIQueryDevice:xdevice_get_dimensions:input_info_find_size_match:get_mappable_output_info:do_touch

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity-settings-daemon -
15.04.1+16.04.20160701-0ubuntu1

---
unity-settings-daemon (15.04.1+16.04.20160701-0ubuntu1) xenial; urgency=medium

  [ Robert Ancell ]
  * Correctly check value of XDG_CURRENT_DESKTOP.

  [ Marco Trevisan (Treviño) ]
  * PowerManager: connect to keyboard BrightnessChanged signal to update
the cached current value properly (LP: #1510344)
  * GsdPowerManager: don't cache kbd backlight current value (LP:
#1583861)
  * common: backport g-s-d commits for having single shared dbus proxies
  * ScreensaverProxy: redirect supported calls to gnome screensaver APIs
(LP: #1415265, LP: #1584161)

  [ Sebastien Bacher ]
  * Don't hit an xerror when a device is removed while being configured
(LP: #1503758)
  * wacom: don't segfault when a device is removed while being
configured. (LP: #1439427)

  [ Marco Trevisan (Treviño) ]
  * GsdPowerManager: use proper return value for upower_kbd_toggle
wherever we use it (LP: #1592816)

  [ Kai-Heng Feng ]
  * SettingsManager: Queue up signals before getting D-Bus connection.
(LP: #1571640)

 -- Marco Trevisan (Treviño)   Fri, 01 Jul 2016 13:28:54
+

** Changed in: unity-settings-daemon (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/1503758

Title:
  /usr/lib/unity-settings-daemon/unity-settings-
  
daemon:5:XIQueryDevice:xdevice_get_dimensions:input_info_find_size_match:get_mappable_output_info:do_touchscreen_mapping

Status in OEM Priority Project:
  In Progress
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in unity-settings-daemon package in Fedora:
  Unknown

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-settings-daemon.  This problem was most recently seen
  with version 15.04.1+15.10.20150818-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6e9dcc008057a747fb5c2e65cd47f07e5b672724
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1503758/+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 1582803] Re: [SRU]bug report script uses invalid nm options

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package network-manager -
1.2.0-0ubuntu0.16.04.3

---
network-manager (1.2.0-0ubuntu0.16.04.3) xenial; urgency=medium

  * cli-initialize-connection-list-in-do_device_connect.patch:
Make sure connection list available for nmc_secrets_requested().
(LP: #1595707).
  * Removing default_powersave_on.patch, and instead install config
file that accomplishes the same (LP: #1557026)
  * Fix invalid nmcli option in bug report script
debian/source_network-manager.py (LP: #1582803)

 -- Aron Xu   Tue, 05 Jul 2016 16:01:03 +0800

** Changed in: network-manager (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/1582803

Title:
  [SRU]bug report script uses invalid nm options

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Xenial reports have those warnings "Error: Object 'nm' is unknown, try 'nmcli 
help'." the "nm-cli" syntax changed and the hook needs to be updated

  [Test Case]
  Future apport report to errors.ubuntu.com should have proper information 
output from nmcli command, rather than throwing an error message.

  [Regression Potential]
  This is a simple change of the command line option on information collection, 
which should be safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582803/+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 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity-settings-daemon -
15.04.1+16.04.20160701-0ubuntu1

---
unity-settings-daemon (15.04.1+16.04.20160701-0ubuntu1) xenial; urgency=medium

  [ Robert Ancell ]
  * Correctly check value of XDG_CURRENT_DESKTOP.

  [ Marco Trevisan (Treviño) ]
  * PowerManager: connect to keyboard BrightnessChanged signal to update
the cached current value properly (LP: #1510344)
  * GsdPowerManager: don't cache kbd backlight current value (LP:
#1583861)
  * common: backport g-s-d commits for having single shared dbus proxies
  * ScreensaverProxy: redirect supported calls to gnome screensaver APIs
(LP: #1415265, LP: #1584161)

  [ Sebastien Bacher ]
  * Don't hit an xerror when a device is removed while being configured
(LP: #1503758)
  * wacom: don't segfault when a device is removed while being
configured. (LP: #1439427)

  [ Marco Trevisan (Treviño) ]
  * GsdPowerManager: use proper return value for upower_kbd_toggle
wherever we use it (LP: #1592816)

  [ Kai-Heng Feng ]
  * SettingsManager: Queue up signals before getting D-Bus connection.
(LP: #1571640)

 -- Marco Trevisan (Treviño)   Fri, 01 Jul 2016 13:28:54
+

** Changed in: unity-settings-daemon (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/1583861

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in upower source package in Xenial:
  Fix Committed

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

  
  To reset the idle-delay, just call
gsettings reset org.gnome.desktop.session idle-delay

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+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 1594493] Re: Extension Pack incompatiblity

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package virtualbox-guest-additions-iso -
5.0.24-0ubuntu1.16.04.1

---
virtualbox-guest-additions-iso (5.0.24-0ubuntu1.16.04.1) xenial; urgency=medium

  * Update to the latest minor release for xenial (LP: #1594493)

 -- Gianfranco Costamagna   Tue, 05 Jul 2016
10:16:17 +0200

** Changed in: virtualbox-guest-additions-iso (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: virtualbox-ext-pack (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/1594493

Title:
  Extension Pack incompatiblity

Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-guest-additions-iso package in Ubuntu:
  Fix Released
Status in virtualbox source package in Xenial:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Xenial:
  Fix Released

Bug description:
  [ test case ]
  Updating virtualbox and download the latest ext pack from upstream should 
stop give the useless warning to the user, and also installing 
virtualbox-ext-pack will stop it

  VirtualBox provides an VM VirtualBox Extension Pack for VirtualBox
  5.0.  This extension provies support for USB 2.0 and USB 3.0 devices,
  VirtualBox RDP and PXE boot for Intel cards.  The current release is
  5.0.22.  However, the main virtualbox release in Ubuntu 16.04 is
  5.0.18.   VirtualBox warns of incompatibility due to the version
  discrepancies between virutalbox and the extension pack.

  I am requesting VirtualBox be updated to 5.0.22 in Ubuntu 16.04.
  Since 5.0.18, all changes to VirtualBox have been bugfixes/maintenance
  releases.  It appears there are security fixes also made in the
  releases below.

  Link: https://www.virtualbox.org/wiki/Changelog

  VirtualBox 5.0.22 (released 2016-06-16)

  This is a maintenance release. The following items were fixed and/or
  added:

  VMM: fixes for certain Intel Atom hosts (bug #14915)
  VMM: properly restore the complete FPU state for 32-bit guests on 64-bit 
hosts on Intel Sandy Bridge and Ivy Bridge CPUs
  VMM: new I/O-APIC implementation fixing several bugs and improving the 
performance under certain conditions (bug #15295 and others)
  VMM: fixed a potential Linux guest panic on AMD hosts
  VMM: fixed a potential hang with 32-bit EFI guests on Intel CPUs (VT-x 
without unrestricted guest execution)
  GUI: don't allow to start subsequent separate VM instances
  GUI: raised upper limit for video capture screen resolution (bug #15432)
  GUI: warn if the VM has less than 128MB VRAM configured and 3D enabled
  Main: when monitoring DNS configuration changes on Windows hosts avoid false 
positives from competing DHCP renewals. This should fix NAT link flaps when 
host has multiple DHCP configured interfaces, in particular when the host uses 
OpnVPN.
  Main: properly display an error message if the VRDE server cannot be enabled 
at runtime, for example because another service is using the same port
  NAT: Initialize guest address guess for wildcard port-forwarding rules with 
default guest address (bug #15412)
  VGA: fix for a problem which made certain legacy guests crash under certain 
conditions (bug #14811)
  ACPI: properly notify the guest if the ACPI battery state changed
  OVF: fixed import problems for some appliances using an AHCI controller 
created by 3rd party applications
  SDK: reduced memory usage in the webservice Java bindings
  Windows hosts: fixed performance regresson with SMP guests (5.0 regression)
  Windows hosts: fixes for the shared clipboard
  Windows hosts: Windows hardening fix
  Windows Additions: fixes to retain the guest display layout when resizing or 
disabling the guest monitors
  Linux hosts: EL 6.8 fix (bug #15411)
  Linux hosts: Linux 4.7 fix (bug #15459)
  Linux Additions: Linux 4.7 fixes (bug #15444)
  Linux Additions: fix for certain 32-bit guests (5.0.18 regression; bug #15320)
  Linux Additions: fixed mouse pointer offset (5.0.18 regression; bug #15324)
  Linux Additions: made old X.Org releases work again with kernels 3.11 and 
later (5.0.18 regression; bug #15319)
  Linux Additions: fixed X.Org crash after hard guest reset (5.0.18 regression; 
bug #15354)
  Linux Additions: don't stop the X11 setup if loading the shared folders 
module fails (5.0.18 regression)
  Linux Additions: don't complain if the Drag and Drop service is not available 
on the host
  Solaris Additions: added support for X.org 1.18
  VirtualBox 5.0.20 (released 2016-04-28)

  This is a maintenance release. The following items were fixed and/or
  added:

  Storage: fixed a regression causing write requests from the BIOS to cause a 
Guru

[Group.of.nepali.translators] [Bug 1584161] Re: Freedesktop Screensaver API is not implemented

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity-settings-daemon -
15.04.1+16.04.20160701-0ubuntu1

---
unity-settings-daemon (15.04.1+16.04.20160701-0ubuntu1) xenial; urgency=medium

  [ Robert Ancell ]
  * Correctly check value of XDG_CURRENT_DESKTOP.

  [ Marco Trevisan (Treviño) ]
  * PowerManager: connect to keyboard BrightnessChanged signal to update
the cached current value properly (LP: #1510344)
  * GsdPowerManager: don't cache kbd backlight current value (LP:
#1583861)
  * common: backport g-s-d commits for having single shared dbus proxies
  * ScreensaverProxy: redirect supported calls to gnome screensaver APIs
(LP: #1415265, LP: #1584161)

  [ Sebastien Bacher ]
  * Don't hit an xerror when a device is removed while being configured
(LP: #1503758)
  * wacom: don't segfault when a device is removed while being
configured. (LP: #1439427)

  [ Marco Trevisan (Treviño) ]
  * GsdPowerManager: use proper return value for upower_kbd_toggle
wherever we use it (LP: #1592816)

  [ Kai-Heng Feng ]
  * SettingsManager: Queue up signals before getting D-Bus connection.
(LP: #1571640)

 -- Marco Trevisan (Treviño)   Fri, 01 Jul 2016 13:28:54
+

** Changed in: unity-settings-daemon (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/1584161

Title:
  Freedesktop Screensaver API is not implemented

Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Released

Bug description:
  This is what we get in an unity session:

  gdbus call --session --dest org.freedesktop.ScreenSaver --object-path
  /org/freedesktop/ScreenSaver --method
  org.freedesktop.ScreenSaver.GetActive

  Error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod:
  Interfaccia "org.freedesktop" inesistente sull'oggetto nel percorso
  /org/freedesktop/ScreenSaver

  Side effect of this is bug #1415265

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1584161/+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 1594493] Re: Extension Pack incompatiblity

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package virtualbox - 5.0.24-dfsg-
0ubuntu1.16.04.1

---
virtualbox (5.0.24-dfsg-0ubuntu1.16.04.1) xenial; urgency=medium

  * Update to the latest minor release for xenial (LP: #1594493)

 -- Gianfranco Costamagna   Tue, 05 Jul 2016
10:17:21 +0200

** Changed in: virtualbox (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/1594493

Title:
  Extension Pack incompatiblity

Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-ext-pack package in Ubuntu:
  Fix Released
Status in virtualbox-guest-additions-iso package in Ubuntu:
  Fix Released
Status in virtualbox source package in Xenial:
  Fix Released
Status in virtualbox-ext-pack source package in Xenial:
  Fix Released
Status in virtualbox-guest-additions-iso source package in Xenial:
  Fix Released

Bug description:
  [ test case ]
  Updating virtualbox and download the latest ext pack from upstream should 
stop give the useless warning to the user, and also installing 
virtualbox-ext-pack will stop it

  VirtualBox provides an VM VirtualBox Extension Pack for VirtualBox
  5.0.  This extension provies support for USB 2.0 and USB 3.0 devices,
  VirtualBox RDP and PXE boot for Intel cards.  The current release is
  5.0.22.  However, the main virtualbox release in Ubuntu 16.04 is
  5.0.18.   VirtualBox warns of incompatibility due to the version
  discrepancies between virutalbox and the extension pack.

  I am requesting VirtualBox be updated to 5.0.22 in Ubuntu 16.04.
  Since 5.0.18, all changes to VirtualBox have been bugfixes/maintenance
  releases.  It appears there are security fixes also made in the
  releases below.

  Link: https://www.virtualbox.org/wiki/Changelog

  VirtualBox 5.0.22 (released 2016-06-16)

  This is a maintenance release. The following items were fixed and/or
  added:

  VMM: fixes for certain Intel Atom hosts (bug #14915)
  VMM: properly restore the complete FPU state for 32-bit guests on 64-bit 
hosts on Intel Sandy Bridge and Ivy Bridge CPUs
  VMM: new I/O-APIC implementation fixing several bugs and improving the 
performance under certain conditions (bug #15295 and others)
  VMM: fixed a potential Linux guest panic on AMD hosts
  VMM: fixed a potential hang with 32-bit EFI guests on Intel CPUs (VT-x 
without unrestricted guest execution)
  GUI: don't allow to start subsequent separate VM instances
  GUI: raised upper limit for video capture screen resolution (bug #15432)
  GUI: warn if the VM has less than 128MB VRAM configured and 3D enabled
  Main: when monitoring DNS configuration changes on Windows hosts avoid false 
positives from competing DHCP renewals. This should fix NAT link flaps when 
host has multiple DHCP configured interfaces, in particular when the host uses 
OpnVPN.
  Main: properly display an error message if the VRDE server cannot be enabled 
at runtime, for example because another service is using the same port
  NAT: Initialize guest address guess for wildcard port-forwarding rules with 
default guest address (bug #15412)
  VGA: fix for a problem which made certain legacy guests crash under certain 
conditions (bug #14811)
  ACPI: properly notify the guest if the ACPI battery state changed
  OVF: fixed import problems for some appliances using an AHCI controller 
created by 3rd party applications
  SDK: reduced memory usage in the webservice Java bindings
  Windows hosts: fixed performance regresson with SMP guests (5.0 regression)
  Windows hosts: fixes for the shared clipboard
  Windows hosts: Windows hardening fix
  Windows Additions: fixes to retain the guest display layout when resizing or 
disabling the guest monitors
  Linux hosts: EL 6.8 fix (bug #15411)
  Linux hosts: Linux 4.7 fix (bug #15459)
  Linux Additions: Linux 4.7 fixes (bug #15444)
  Linux Additions: fix for certain 32-bit guests (5.0.18 regression; bug #15320)
  Linux Additions: fixed mouse pointer offset (5.0.18 regression; bug #15324)
  Linux Additions: made old X.Org releases work again with kernels 3.11 and 
later (5.0.18 regression; bug #15319)
  Linux Additions: fixed X.Org crash after hard guest reset (5.0.18 regression; 
bug #15354)
  Linux Additions: don't stop the X11 setup if loading the shared folders 
module fails (5.0.18 regression)
  Linux Additions: don't complain if the Drag and Drop service is not available 
on the host
  Solaris Additions: added support for X.org 1.18
  VirtualBox 5.0.20 (released 2016-04-28)

  This is a maintenance release. The following items were fixed and/or
  added:

  Storage: fixed a regression causing write requests from the BIOS to cause a 
Guru Meditation with the LsiLogic SCSI controller (5.0.18 regression; bug 
#15317)
  Storage: several emulation fixes in the BusLogic SCSI controller

[Group.of.nepali.translators] [Bug 1589520] Re: Add dconf keys for disabling multitouch gestures

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity - 7.4.0+16.04.20160715-0ubuntu1

---
unity (7.4.0+16.04.20160715-0ubuntu1) xenial; urgency=medium

  [ Eleni Maria Stea ]
  * PanelView: Don't draw it if the geo doesn't intersect the monitor
geo (as in ezoom)
  * speeds up the showdesktop plugin in lowgfx mode

  [ Andrea Azzarone ]
  * Add whitelist for auto-repated keys. (LP: #1586491)
  * Fix scale window activation if in show desktop mode. (LP: #1582056)
  * Order matters in the rendering. Draw launcher shadow after the
background in all cases. (LP: #1586374)
  * Fallback to volume name if no other identifier is available. (LP:
#1103593)
  * Do not trigger screensaver on session inactive. (LP: #1587507)
  * Use SwitcherController::SetDetail instead of detail=... (LP:
#1587618)
  * UnitySettings: Add an option to enable/disable pam account checking.
(LP: #1460649)
  * Lockscreen: Make sure warning and errors are properly shown to the
user (LP: #1593696)
  * Add missing header to fix compilation error with -Duse_pch=OFF.
  * Filter out fullscreen window in show desktop mode. (LP: #1597706)
  * Make sure file manager icon is not removed when unpinned. (LP:
#1578792)
  * Properly calculate the intersection geometry in PanelView::Draw.
This is needed to properly call SyncGeometries and to avoid problems
such as lp:1595698. (LP: #1595698)

  [ Alberto Milone ]
  * UnitySettings: Add dconf keys for disabling multitouch gestures (LP:
#1589520)

  [ Marco Trevisan (Treviño) ]
  * LockScreenAcceleratorController: use key::Grabber to handle allowed
bindings (LP: #1438754)
  * LockScreenAcceleratorController: check if a setting key is available
instead of crashing
  * ApplicationLauncherIcon: ensure quirks are properly set on icon
initialization
  * Views: Toggle animators durations based on low-gfx setting (LP:
#1598770)
  * unity7.conf: use different compiz profile based on
unity_support_test result (LP: #1598770)

 -- Marco Trevisan (Treviño)   Fri, 15 Jul 2016 10:14:41
+

** Changed in: unity (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/1589520

Title:
  Add dconf keys for disabling multitouch gestures

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

Bug description:
  Not an actual solution to LP: #1264795 (which should probably be fixed
  in the driver), but a simply way for users to disable gestures in
  dconf.

  [Inpact]

  It's not possible to disable unity7 multi-touch gestures

  [Test case]

  * It should be possible to disable gestures by using gsettings:
   gsettings set com.canonical.Unity.Gestures launcher-drag false
   gsettings set com.canonical.Unity.Gestures dash-tap false
   gsettings set com.canonical.Unity.Gestures windows-drag-pinch false

  [Possible regressions]

  Gestures might not work anymore

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

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity - 7.4.0+16.04.20160715-0ubuntu1

---
unity (7.4.0+16.04.20160715-0ubuntu1) xenial; urgency=medium

  [ Eleni Maria Stea ]
  * PanelView: Don't draw it if the geo doesn't intersect the monitor
geo (as in ezoom)
  * speeds up the showdesktop plugin in lowgfx mode

  [ Andrea Azzarone ]
  * Add whitelist for auto-repated keys. (LP: #1586491)
  * Fix scale window activation if in show desktop mode. (LP: #1582056)
  * Order matters in the rendering. Draw launcher shadow after the
background in all cases. (LP: #1586374)
  * Fallback to volume name if no other identifier is available. (LP:
#1103593)
  * Do not trigger screensaver on session inactive. (LP: #1587507)
  * Use SwitcherController::SetDetail instead of detail=... (LP:
#1587618)
  * UnitySettings: Add an option to enable/disable pam account checking.
(LP: #1460649)
  * Lockscreen: Make sure warning and errors are properly shown to the
user (LP: #1593696)
  * Add missing header to fix compilation error with -Duse_pch=OFF.
  * Filter out fullscreen window in show desktop mode. (LP: #1597706)
  * Make sure file manager icon is not removed when unpinned. (LP:
#1578792)
  * Properly calculate the intersection geometry in PanelView::Draw.
This is needed to properly call SyncGeometries and to avoid problems
such as lp:1595698. (LP: #1595698)

  [ Alberto Milone ]
  * UnitySettings: Add dconf keys for disabling multitouch gestures (LP:
#1589520)

  [ Marco Trevisan (Treviño) ]
  * LockScreenAcceleratorController: use key::Grabber to handle allowed
bindings (LP: #1438754)
  * LockScreenAcceleratorController: check if a setting key is available
instead of crashing
  * ApplicationLauncherIcon: ensure quirks are properly set on icon
initialization
  * Views: Toggle animators durations based on low-gfx setting (LP:
#1598770)
  * unity7.conf: use different compiz profile based on
unity_support_test result (LP: #1598770)

 -- Marco Trevisan (Treviño)   Fri, 15 Jul 2016 10:14:41
+

** Changed in: unity (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/1586491

Title:
  Volume up and down keys no longer autorepeat

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

Bug description:
  [Impact]
  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

  [Test Case]
  #1. Hold the volume up/down keys
  #2. Make sure the keys auto-repeat and you can turn up/down the volume 
holding the volume up/down keys

  [Possible Regressions]
  Nothing known.

  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

[Group.of.nepali.translators] [Bug 1592816] Re: unity-settings-daemon crashed with SIGSEGV in idle_set_mode()

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity-settings-daemon -
15.04.1+16.04.20160701-0ubuntu1

---
unity-settings-daemon (15.04.1+16.04.20160701-0ubuntu1) xenial; urgency=medium

  [ Robert Ancell ]
  * Correctly check value of XDG_CURRENT_DESKTOP.

  [ Marco Trevisan (Treviño) ]
  * PowerManager: connect to keyboard BrightnessChanged signal to update
the cached current value properly (LP: #1510344)
  * GsdPowerManager: don't cache kbd backlight current value (LP:
#1583861)
  * common: backport g-s-d commits for having single shared dbus proxies
  * ScreensaverProxy: redirect supported calls to gnome screensaver APIs
(LP: #1415265, LP: #1584161)

  [ Sebastien Bacher ]
  * Don't hit an xerror when a device is removed while being configured
(LP: #1503758)
  * wacom: don't segfault when a device is removed while being
configured. (LP: #1439427)

  [ Marco Trevisan (Treviño) ]
  * GsdPowerManager: use proper return value for upower_kbd_toggle
wherever we use it (LP: #1592816)

  [ Kai-Heng Feng ]
  * SettingsManager: Queue up signals before getting D-Bus connection.
(LP: #1571640)

 -- Marco Trevisan (Treviño)   Fri, 01 Jul 2016 13:28:54
+

** Changed in: unity-settings-daemon (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/1592816

Title:
  unity-settings-daemon crashed with SIGSEGV in idle_set_mode()

Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Released

Bug description:
  Crashed after an upgrade->reboot->login->sleep->resume cycle.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity-settings-daemon 15.04.1+16.10.20160613-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-25.44-lowlatency 4.4.13
  Uname: Linux 4.4.0-25-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun 15 06:47:04 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2015-07-13 (338 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fe020c30cfe:mov0x8(%rax),%rcx
   PC (0x7fe020c30cfe) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-settings-daemon crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sbuild sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1592816/+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 1586374] Re: Launcher sizing wrong in low graphics mode

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity - 7.4.0+16.04.20160715-0ubuntu1

---
unity (7.4.0+16.04.20160715-0ubuntu1) xenial; urgency=medium

  [ Eleni Maria Stea ]
  * PanelView: Don't draw it if the geo doesn't intersect the monitor
geo (as in ezoom)
  * speeds up the showdesktop plugin in lowgfx mode

  [ Andrea Azzarone ]
  * Add whitelist for auto-repated keys. (LP: #1586491)
  * Fix scale window activation if in show desktop mode. (LP: #1582056)
  * Order matters in the rendering. Draw launcher shadow after the
background in all cases. (LP: #1586374)
  * Fallback to volume name if no other identifier is available. (LP:
#1103593)
  * Do not trigger screensaver on session inactive. (LP: #1587507)
  * Use SwitcherController::SetDetail instead of detail=... (LP:
#1587618)
  * UnitySettings: Add an option to enable/disable pam account checking.
(LP: #1460649)
  * Lockscreen: Make sure warning and errors are properly shown to the
user (LP: #1593696)
  * Add missing header to fix compilation error with -Duse_pch=OFF.
  * Filter out fullscreen window in show desktop mode. (LP: #1597706)
  * Make sure file manager icon is not removed when unpinned. (LP:
#1578792)
  * Properly calculate the intersection geometry in PanelView::Draw.
This is needed to properly call SyncGeometries and to avoid problems
such as lp:1595698. (LP: #1595698)

  [ Alberto Milone ]
  * UnitySettings: Add dconf keys for disabling multitouch gestures (LP:
#1589520)

  [ Marco Trevisan (Treviño) ]
  * LockScreenAcceleratorController: use key::Grabber to handle allowed
bindings (LP: #1438754)
  * LockScreenAcceleratorController: check if a setting key is available
instead of crashing
  * ApplicationLauncherIcon: ensure quirks are properly set on icon
initialization
  * Views: Toggle animators durations based on low-gfx setting (LP:
#1598770)
  * unity7.conf: use different compiz profile based on
unity_support_test result (LP: #1598770)

 -- Marco Trevisan (Treviño)   Fri, 15 Jul 2016 10:14:41
+

** Changed in: unity (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/1586374

Title:
  Launcher sizing wrong in low graphics mode

Status in Unity Tweak Tool:
  Invalid
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  I used ccsm to enable low graphics mode. I'm not sure what this does other 
than remove blur effects and transparency, which is what I wanted.

  If I put the launcher at the bottom rather than the left, it doesn't
  look right.

  The colour doesn't cover the whole height of the bar, and so I can see
  my wallpaper through the gap between maximised windows and the colour
  in the launcher.

  My screen dimensions are 1366x768 (16:9) (and a second screen on
  extended mode with the same dimensions).

  I've attached a picture of what it looks like.

  [Test Case]
  #1. Enable low graphics mode using ccsm
  #2. Move the Unity launcher at the bottom (gsettings set 
com.canonical.Unity.Launcher launcher-position Bottom)
  #3. Make sure the launcher is correctly drawn.

  [Possible Regressions]
  Nothing known

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-tweak-tool/+bug/1586374/+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 1587618] Re: alt-backtick on desktop icon whilst alt-tabbing prevents further alt-tabbing

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity - 7.4.0+16.04.20160715-0ubuntu1

---
unity (7.4.0+16.04.20160715-0ubuntu1) xenial; urgency=medium

  [ Eleni Maria Stea ]
  * PanelView: Don't draw it if the geo doesn't intersect the monitor
geo (as in ezoom)
  * speeds up the showdesktop plugin in lowgfx mode

  [ Andrea Azzarone ]
  * Add whitelist for auto-repated keys. (LP: #1586491)
  * Fix scale window activation if in show desktop mode. (LP: #1582056)
  * Order matters in the rendering. Draw launcher shadow after the
background in all cases. (LP: #1586374)
  * Fallback to volume name if no other identifier is available. (LP:
#1103593)
  * Do not trigger screensaver on session inactive. (LP: #1587507)
  * Use SwitcherController::SetDetail instead of detail=... (LP:
#1587618)
  * UnitySettings: Add an option to enable/disable pam account checking.
(LP: #1460649)
  * Lockscreen: Make sure warning and errors are properly shown to the
user (LP: #1593696)
  * Add missing header to fix compilation error with -Duse_pch=OFF.
  * Filter out fullscreen window in show desktop mode. (LP: #1597706)
  * Make sure file manager icon is not removed when unpinned. (LP:
#1578792)
  * Properly calculate the intersection geometry in PanelView::Draw.
This is needed to properly call SyncGeometries and to avoid problems
such as lp:1595698. (LP: #1595698)

  [ Alberto Milone ]
  * UnitySettings: Add dconf keys for disabling multitouch gestures (LP:
#1589520)

  [ Marco Trevisan (Treviño) ]
  * LockScreenAcceleratorController: use key::Grabber to handle allowed
bindings (LP: #1438754)
  * LockScreenAcceleratorController: check if a setting key is available
instead of crashing
  * ApplicationLauncherIcon: ensure quirks are properly set on icon
initialization
  * Views: Toggle animators durations based on low-gfx setting (LP:
#1598770)
  * unity7.conf: use different compiz profile based on
unity_support_test result (LP: #1598770)

 -- Marco Trevisan (Treviño)   Fri, 15 Jul 2016 10:14:41
+

** Changed in: unity (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/1587618

Title:
  alt-backtick on desktop icon whilst alt-tabbing prevents further alt-
  tabbing

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

Bug description:
  [Impact]

  # Alt-Backtick on Desktop Icon Whilst Alt-Tabbing Prevents Further
  Alt-Tabbing

  ## Version information

    * `uname -r` -> `4.4.0-22-generic`
    * `unity --version` -> `unity 7.4.0`

  If more information is required, please ask.

  ## Why I think this is a bug

  When you select an icon other than the desktop icon, it is possible to
  continue `alt-tab`. With a small number of tabs this can be annoying
  if you accidentally start to `alt-backtick` in the desktop icon
  instead of the one you wanted to.

  [Test case]

  ## Steps

    * `alt-tab` until desktop icon is highlighted
    * `alt-backtick` on desktop icon
    * Attempt to `alt-tab` once more

  ## What happens

  Further input such as `alt-tab` and `alt-backtick` is ignored until I
  stop pressing them.

  ## What I think this should do

  I believe it should allow me to continue to `alt-tab` to another icon.
  This would not lead to any bad behaviour.

  [Possible Regressions]
  Nothing known.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1587618/+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 1595495] Re: DASD drives can only hold 3 partitions

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package partman-base - 187ubuntu2.1

---
partman-base (187ubuntu2.1) xenial; urgency=medium

  * On s390[x], Prevent using extended partitions on DASD drives that can
only hold 3 partitions. Parted doesn't have special knowledge about
that and claims that msdos partition table on DASD drives can hold
usual maximum number of partitions types. LP: #1595495.

 -- Dimitri John Ledkov   Thu, 23 Jun 2016 12:06:00
+0100

** Changed in: partman-base (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/1595495

Title:
  DASD drives can only hold 3 partitions

Status in partman-base package in Ubuntu:
  Fix Released
Status in partman-base source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * DASD drives have two types ECKD and FBA.
   * ECKD have been made to use dasd partition table by default, however can be 
used with msdos partition table
   * FBA devices use msdos partition table by default
   * Both types of drives can only hold 3 partitions
   * However parted/partman default to using logical partitions with default 
installation recipe, thus exploading instalations.

  [Test Case]

   * Start the installer, activate ECKD and/or FBA devices
   * In case of ECKD choose to use msdos partition table (label)
   * The installer should only create primary partitions, and not offer to 
create logical partitions in any way

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/1595495/+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 1595707] Re: [SRU]crash in nmc_find_connection

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package network-manager -
1.2.0-0ubuntu0.16.04.3

---
network-manager (1.2.0-0ubuntu0.16.04.3) xenial; urgency=medium

  * cli-initialize-connection-list-in-do_device_connect.patch:
Make sure connection list available for nmc_secrets_requested().
(LP: #1595707).
  * Removing default_powersave_on.patch, and instead install config
file that accomplishes the same (LP: #1557026)
  * Fix invalid nmcli option in bug report script
debian/source_network-manager.py (LP: #1582803)

 -- Aron Xu   Tue, 05 Jul 2016 16:01:03 +0800

** Changed in: network-manager (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/1595707

Title:
  [SRU]crash in nmc_find_connection

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Ubuntu error tracker receives some reports agains 1.2.0 for a crash in 
nmc_find_connection() when connecting to a password protected wlan connection, 
by running command: nmcli device connect wlan0
  T he problem page at 
https://errors.ubuntu.com/problem/16ece0c3816c93d9c763402902edf04448cbe6c8 
contains more details.

  [Test Case]
  After applying the patch, errors.ubuntu.com should stop receiving new crash 
reports for this problem.

  [Regression Potential]
  The fix is making the connection list available for certain 
nmc_secrets_requested() call, which should be harmless.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1595707/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package nux - 4.0.8+16.04.20160705-0ubuntu1

---
nux (4.0.8+16.04.20160705-0ubuntu1) xenial; urgency=medium

  * unity_support_test: add llvmpipe as software-rendererd (LP:
#1598770)

 -- Marco Trevisan (Treviño)   Tue, 05 Jul 2016 10:54:14
+

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

** Changed in: compiz (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/1598770

Title:
  Unity in low-graphics mode has animations and unneeded redraws

Status in compiz package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in compiz source package in Xenial:
  Fix Released
Status in nux source package in Xenial:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in unity-control-center source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  When unity is in Low graphics mode (because of software rendering)
  there are still window animations and fade effects which we should get
  rid of.

  
  [Test case]

  This should apply naturally to a (virtual-)machine with no hardware
  acceleration or There are multiple ways to force low-gfx mode:

  1) Add an upstart job such as:

  cat << EOF > ~/.config/upstart/lowgfx.conf
  start on starting unity7

  pre-start script
#initctl set-env --global UNITY_LOW_GFX_MODE=1
initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1
  end script
  EOF 

  
  2) Run unity with:
 COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx

  On login unity should use opaque views (dash, switcher, launcher,
  shortcut-dialogs) with no fading and reduced effects. Windows should
  also use smaller shadows.

  
  [Regression potential]

  Some settings from unity-control-center couldn't be applied to normal
  profile. Low graphics mode might be used as normal one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1595788] Re: drupal7 needs dependency on php-xml

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package drupal7 - 7.44-1ubuntu1~16.04.0

---
drupal7 (7.44-1ubuntu1~16.04.0) xenial; urgency=medium

  * Backport a version of drupal7 to Ubuntu 16.04 LTS that is
installable with php7 (LP: #1582340)

drupal7 (7.44-1ubuntu1) yakkety; urgency=medium

  * Depend on php-xml (LP: #1595788)

drupal7 (7.44-1) unstable; urgency=high

  * New upstream version
  * Fixes a security vulnerability (SA-CORE-2016-002): Privilege
escalation (within the webapp users realm)

drupal7 (7.43-3) unstable; urgency=medium

  * Moved the farbstatic sources from debian/missing-sources
todebian/missing-sources/misc, to keep lintian happy
  * The right name for one of our conditional dependencies is no longer
php-sqlite, but php-sqlite3. Thanks to Nish Aravamudan for pointing
this out!

drupal7 (7.43-2) unstable; urgency=medium

  * Update dependencies to use PHP 7 instead of 5 (Closes: #821482)
  * Updated debian/watch to work reliably
  * Standards-version 3.9.6.0→3.9.8 (no changes needed)

drupal7 (7.43-1) unstable; urgency=high

  * New upstream version
  * Fixes several security vulnerabilities (SA-CORE-2016-001): File
upload access bypass and DoS, brute force amplification attack via
XML-RPC, open redirect via path manipulation, reflected file
download, wrong modes set on some user accounts setting saves,
information disclosure of email addresses
  * Several non-security bugfixes from 7.42 included
  * Fix typo in README.Debian
  * Add several needed lintian overrides

 -- Jeremy Bicha   Fri, 24 Jun 2016 13:29:56 -0400

** Changed in: drupal7 (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/1595788

Title:
  drupal7 needs dependency on php-xml

Status in drupal7 package in Ubuntu:
  Fix Released
Status in drupal7 source package in Xenial:
  Fix Released
Status in drupal7 package in Debian:
  New

Bug description:
  What happens
  
  $ sudo apt install drupal7
  (on Ubuntu 16.04 LTS currently, you'll also need to sudo apt install 
libapache2-mod-php
  $ sudo a2enconf drupal7
  Enabling conf drupal7.
  To activate the new configuration, you need to run:
service apache2 reload
  $ sudo systemctl reload apache2

  Open your webbrowser to http://localhost/drupal/install.php

  The installer complains that it needs the php xml extensions. See
  attached screenshot.

  What works
  ==
  $ sudo apt install php-xml
  $ sudo systemctl reload apache2

  What's needed
  =
  drupal7 should depend on php-xml

  
  drupal7 7.44-1 on Ubuntu 16.10 (yakkety) and
  drupal7 7.43-3~16.04.0 on Ubuntu 16.04 LTS from xenial-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drupal7/+bug/1595788/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package compiz -
1:0.9.12.2+16.04.20160714-0ubuntu1

---
compiz (1:0.9.12.2+16.04.20160714-0ubuntu1) xenial; urgency=medium

  [ Eleni Maria Stea ]
  * Added options for no animation in expo and scale plugins. They skip
the intermediate fading steps that force several redraws.
  * Added a new option in show desktop plugin that skips the fade
animation: useful when performance is more important than eyecandy.

  [ Marco Trevisan (Treviño) ]
  * debian: add unity-lowgfx profile to compizconfig (LP: #1598770)
  * Composite: use C++ goodness for managing damaging rectangles
  * ccsGSettingsBackend: don't try to update setting if wrapper is not
found
  * migration scripts: remove unsupported plugins for all the unity
profiles

 -- Marco Trevisan (Treviño)   Thu, 14 Jul 2016 16:00:57
+

** Changed in: unity (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/1598770

Title:
  Unity in low-graphics mode has animations and unneeded redraws

Status in compiz package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in compiz source package in Xenial:
  Fix Released
Status in nux source package in Xenial:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in unity-control-center source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  When unity is in Low graphics mode (because of software rendering)
  there are still window animations and fade effects which we should get
  rid of.

  
  [Test case]

  This should apply naturally to a (virtual-)machine with no hardware
  acceleration or There are multiple ways to force low-gfx mode:

  1) Add an upstart job such as:

  cat << EOF > ~/.config/upstart/lowgfx.conf
  start on starting unity7

  pre-start script
#initctl set-env --global UNITY_LOW_GFX_MODE=1
initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1
  end script
  EOF 

  
  2) Run unity with:
 COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx

  On login unity should use opaque views (dash, switcher, launcher,
  shortcut-dialogs) with no fading and reduced effects. Windows should
  also use smaller shadows.

  
  [Regression potential]

  Some settings from unity-control-center couldn't be applied to normal
  profile. Low graphics mode might be used as normal one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1597706] Re: Unity shell not drawn if show desktop is activated and a window is in fullscreen mode

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity - 7.4.0+16.04.20160715-0ubuntu1

---
unity (7.4.0+16.04.20160715-0ubuntu1) xenial; urgency=medium

  [ Eleni Maria Stea ]
  * PanelView: Don't draw it if the geo doesn't intersect the monitor
geo (as in ezoom)
  * speeds up the showdesktop plugin in lowgfx mode

  [ Andrea Azzarone ]
  * Add whitelist for auto-repated keys. (LP: #1586491)
  * Fix scale window activation if in show desktop mode. (LP: #1582056)
  * Order matters in the rendering. Draw launcher shadow after the
background in all cases. (LP: #1586374)
  * Fallback to volume name if no other identifier is available. (LP:
#1103593)
  * Do not trigger screensaver on session inactive. (LP: #1587507)
  * Use SwitcherController::SetDetail instead of detail=... (LP:
#1587618)
  * UnitySettings: Add an option to enable/disable pam account checking.
(LP: #1460649)
  * Lockscreen: Make sure warning and errors are properly shown to the
user (LP: #1593696)
  * Add missing header to fix compilation error with -Duse_pch=OFF.
  * Filter out fullscreen window in show desktop mode. (LP: #1597706)
  * Make sure file manager icon is not removed when unpinned. (LP:
#1578792)
  * Properly calculate the intersection geometry in PanelView::Draw.
This is needed to properly call SyncGeometries and to avoid problems
such as lp:1595698. (LP: #1595698)

  [ Alberto Milone ]
  * UnitySettings: Add dconf keys for disabling multitouch gestures (LP:
#1589520)

  [ Marco Trevisan (Treviño) ]
  * LockScreenAcceleratorController: use key::Grabber to handle allowed
bindings (LP: #1438754)
  * LockScreenAcceleratorController: check if a setting key is available
instead of crashing
  * ApplicationLauncherIcon: ensure quirks are properly set on icon
initialization
  * Views: Toggle animators durations based on low-gfx setting (LP:
#1598770)
  * unity7.conf: use different compiz profile based on
unity_support_test result (LP: #1598770)

 -- Marco Trevisan (Treviño)   Fri, 15 Jul 2016 10:14:41
+

** Changed in: unity (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/1597706

Title:
  Unity shell not drawn if show desktop is activated and a window is in
  fullscreen mode

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

Bug description:
  [Impact]
  Unity shell is not drawn if show desktop is activated and a window is in 
fullscreen mode

  
  [Test case]

  To reproduce
  1. Open gnome-terminal
  2. Make it fullscreen (F11)
  3. Use alt+tab to activate show-desktop mode

  Expected
  Desktop and unity are displayed

  Actual
  Desktop is shown but unity is not displayed

  
  [Regression potential]

  Unity shell might not be drawn in some cases where there are
  fullscreen windows.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1597706/+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 1599523] Re: [SRU] MAAS 2.0rc2 to Xenial

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package maas -
2.0.0~rc2+bzr5156-0ubuntu1~16.04.1

---
maas (2.0.0~rc2+bzr5156-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream bugfix release, 2.0.0 RC2 bzr5143 (LP: #1599523):
- This new upstream release is a bug fix release that addresses several
  of the issues present in beta3, and improves the reliability of MAAS
  in Xenial. For changes please see the CHANGELOG.

 -- Andres Rodriguez   Tue, 12 Jul 2016 22:25:58
-0400

** Changed in: maas (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/1599523

Title:
  [SRU] MAAS 2.0rc2 to Xenial

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

Bug description:
  We would like to request a SRU for MAAS 2.0. This follow the approval
  by the Ubuntu Technical Board for backporting new MAAS upstream
  releases.

  [Impact]
  This is a new version of MAAS that provides bugfixes only. It increases MAAS' 
reliability and serviceability and greatly improves MAAS as a whole in 
comparison to MAAS beta3, which is currently in Xenial Main

  [Regression Potential]
  Minimal. MAAS has been thoroughly tested stand alone and upgrading from 2.0b3 
to 2.0rc1. It has been QA'd in a CI lab as well as other production deployments:

  Tests done:

  1. Upgraded a production lab from 2.0b3 to 2.0rc1.

  2. MAAS CI Lab:
   - Tests Installation (from pkgs), configuration / customization of MAAS, 
enlistment, commissioning. It also tests deployments with Juju.
   - Tests various API's
   - Tests are performed against Xenial

  3. Other manual testing include:
   - Installation (both fresh and upgrades)
   - Configuration
   - Taking nodes through the lifecycle for regression testing.
   - Custom configuration to ensure proper operation.
   - Tests API's for regressions, and keeping backwards compatibility.

  2.0.0 (rc2)
  ===

  LP: #1582070Pick up wrong grub.cfg if another filesystem exists

  LP: #1599223[2.0] confusing reverse DNS lookups because MAAS
  creates multiple PTR records

  LP: #1600259[2.0] reverse DNS sometimes assigns FQDN where it
  should assign IFACE.FQDN

  LP: #157[2.0rc1] after upgrade from 2.0b3, Error on request
  (13) subnet.list: 'NoneType' object is not iterable

  LP: #1598461[2.0rc1] Image import dates are inconsistent

  LP: #1598937[2.0rc1] Following fresh install maas command fails -
  PermissionError: [Errno 13] Permission denied:
  '/home/ubuntu/.maascli.db'

  LP: #1597787[1.9.3,2.0] cannot create more than 4 partitions when
  disk is configured with mbr

  LP: #1600267[1.9,2.0,UX] Can't add aliases when parent interface
  is set to 'DCHP'

  LP: #1600198[1.9,2.0,UX] Creating a Bcache disk is not prevented
  when is not created in partition

  
  2.0.0 (rc1)
  ===

  Issues fixed in this release
  

  LP: #1576357Determine a method for how to reconnect a deleted rack
  controller

  LP: #1592246[2.0b7, regression] maas-rack register makes up a new
  hostname

  LP: #1595753[beta8] HMC power driver regression -- Not able to
  connect via SSH.

  LP: #1592885[2.0b7] Date and time format should be consistent
  accross logs

  LP: #1597324[2.0b8] Unable to set default gateway interface

  LP: #1515188[1.9] VMware power management fails when VMs are
  organized in nested subfolders

  LP: #1596046[2.0] maas 2.0 pxeboot fails on PowerNV

  2.0.0 (beta8)
  =

  Issues fixed in this release
  

  LP: #1590081Allow ed25519 and ecdsa ssh keys

  LP: #1462078[2.0b2, UI] Can't add a device and it does not show
  why

  LP: #1573626[2.0b3] Interfaces on region controllers are not
  discovered

  LP: #1562107[2.0b4, UI] No feedback when failing to assign static
  IP address on the Node Details Page

  LP: #1583670[2.0b5] No way to read settings, like proxy, for non-
  admin users

  LP: #1585016[2.0b5] Commissing with LVM breaks deployments

  LP: #1581729[2.0b5] dns templates still in /etc/maas/templates

  LP: #1588907[2.0b6] django.db.utils.IntegrityError: insert or
  update on table "piston3_consumer" violates foreign key constraint LP:
  "piston3_consumer_user_id_4ac0863fa7e05162_fk_auth_user_id

  LP: #1581130[2.0b6] Image status stays out-of-sync after adding
  custom image

  LP: #1590144[2.0b6] core count not updated during commissioning if
  MAAS previously stored a higher core count

  LP: #1592282[2.0b7] Adding rack controller instructions could be
  in the GUI

  LP: #1592132[2.0b7] Enlisting output returns objects

  LP: #1592137[2.0b7, UI] Can't sort IP addresses under a subnet
  details

[Group.of.nepali.translators] [Bug 1603137] Re: libbfd changed name without transition

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package binutils - 2.26.1-1ubuntu1~16.04.1

---
binutils (2.26.1-1ubuntu1~16.04.1) xenial; urgency=medium

  * debian/rules: 2.26.1 changed sonames for libbfd and libopcodes, but
there were no changes to the public ABI.  Add compatibility symlinks and
revert the shlibs change.  LP: #1603137.

 -- Steve Langasek   Thu, 14 Jul 2016
19:30:17 +

** 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/1603137

Title:
  libbfd changed name without transition

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

Bug description:
  [SRU Justification]
  the latest binutils update in xenial to 2.26.1-1ubuntu1~16.04 changed the 
name of the libbfd library from: libbfd-2.26-system.so to 
libbfd-2.26.1-system.so
  This apparently happened without transitioning all dependencies.
  For example it broke the perf tool from the linux-tools-common package as it 
is still linked against the old libbfd name.

  To reproduce run "perf" with linux >= 4.4.0-24.43 and binutils
  2.26.1-1ubuntu1~16.04 and you get an cannot open libbfd-2.26-system.so
  error.

  [Test case]
  1. Install eztrace on 16.04.
  2. Install binutils from xenial-updates.
  3. Run 'eztrace'.  Confirm that this fails with a library error.
  4. Install binutils from xenial-proposed.
  5. Run 'eztrace'.  Confirm that this gives usage output instead of failing 
with a library error.

  [Regression potential]
  Packages which depend on libbfd-2.26-system.so are currently broken with the 
binutils in xenial-updates.  No packages appear to have been built yet against 
the libbfd-2.26.1-system.so soname.  Therefore the regression potential is 
minimal.  The solution is intended to be compatible with both upstream sonames, 
so that any future packages which do rebuild against the 2.26.1 soname will 
have a versioned dependency on binutils (>= 2.26.1), binutils (<= 2.27).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1603137/+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 1589097] Re: gnome-menus and bamfdaemon failed to install/upgrade: triggers looping, abandoned

2016-07-18 Thread Launchpad Bug Tracker

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

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

  [ Marco Trevisan (Treviño) ]
  * BamfMatcher: allow overriding desktop with the environment var
BAMF_DESKTOP_FILE_HINT

  [ Andrea Azzarone ]
  * Daemon: manually set to complete the startup notification on view
state change (LP: #1582430)

  [ Marco Trevisan (Treviño) ]
  * debian/bamfdaemon.triggers: use interest-noawait (LP: #1589097)

 -- Marco Trevisan (Treviño)   Fri, 01 Jul 2016 10:44:07
+

** 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/1589097

Title:
  gnome-menus and bamfdaemon failed to install/upgrade: triggers
  looping, abandoned

Status in bamf package in Ubuntu:
  Fix Released
Status in gnome-menus package in Ubuntu:
  Confirmed
Status in bamf source package in Xenial:
  Fix Released
Status in gnome-menus source package in Xenial:
  New

Bug description:
  [Impact]

  During upgrade from 15.10 to 16.04

  gnome-menus and bamfdaemon triggers start looping forever.

  [Test case]

  Do a distro upgrade from 15.10 to 16.04

  [Regression potential]

  Nothing known at this stage. There's no behavior change, just a timing
  one.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-menus 3.13.3-6ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Jun  4 07:35:11 2016
  Dependencies:

  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-10-01 (246 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-06-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1589097/+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 1592990] Re: HCPGIR450W CP entered; disabled wait PSW 00020000 80000000 00000000 00004502

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package s390-tools - 1.34.0-0ubuntu8.2

---
s390-tools (1.34.0-0ubuntu8.2) xenial; urgency=medium

  * zipl: Import off-by-one patch to resolve failure to start subchannel
in FBA loader. LP: #1592990.

 -- Dimitri John Ledkov   Tue, 28 Jun 2016 10:51:39
+0100

** Changed in: s390-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/1592990

Title:
  HCPGIR450W CP entered; disabled wait PSW 0002 8000 
  4502

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Xenial:
  Fix Released

Bug description:
  zVM v6.3 zBC12 V7000 FICON SAN048B

  Installed Ubuntu on zBC12 with FICON attached (via SAN048B switches)
  using instructions at
  https://wiki.ubuntu.com/S390X/Installation%20In%20zVM.

  Installation build completed OK but IPL fails (after initial boot options 
appear and timeout to default) with following error message:
  HCPGIR450W CP entered; disabled wait PSW 0002 8000  4502

  A trace was taken using:

  #CP TR SSCH RUN
  #CP IPL 
  #cp tr end

  The resulting trace appears to fail at the same point in the trace on every 
IPL.
  Several builds have been attempted on different VMs with identical symptoms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1592990/+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 1582430] Re: spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is already playing music

2016-07-18 Thread Launchpad Bug Tracker

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

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

  [ Marco Trevisan (Treviño) ]
  * BamfMatcher: allow overriding desktop with the environment var
BAMF_DESKTOP_FILE_HINT

  [ Andrea Azzarone ]
  * Daemon: manually set to complete the startup notification on view
state change (LP: #1582430)

  [ Marco Trevisan (Treviño) ]
  * debian/bamfdaemon.triggers: use interest-noawait (LP: #1589097)

 -- Marco Trevisan (Treviño)   Fri, 01 Jul 2016 10:44:07
+

** 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/1582430

Title:
  spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is
  already playing music

Status in bamf package in Ubuntu:
  In Progress
Status in bamf source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is already 
playing music

  [Test Case]

  1. Start Rhythmbox.
  2. Play some music.
  3. Close the Rhythmbox window.
  4. Open Rhythmbox from Dash or Launcher (if Rhythmbox is locked to it).
  5. Admire annoying spinning wheel for about 13 seconds.

  If Rhythmbox is reopened from the sound tray menu it is ok, no
  spinning wheel.

  [Possible Regresssions]
  Unity fails to notify the application startup or the startup notification 
process finishes too soon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1582430/+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 1571640] Re: unity-greeter scaling factor changes after a delay

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package unity-greeter - 16.10.1-0ubuntu2

---
unity-greeter (16.10.1-0ubuntu2) yakkety; urgency=medium

  * debian/control:
- Require unity-settings-daemon that has xsettings signal fixes.

 -- Robert Ancell   Fri, 24 Jun 2016
09:21:10 +1200

** Changed in: unity-greeter (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  unity-greeter scaling factor changes after a delay

Status in unity-greeter package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-greeter source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Fix Committed
Status in unity-greeter source package in Yakkety:
  Fix Released
Status in unity-settings-daemon source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * Unity Greeter does not have the right scale at the beginning, after
  a short delay, it changes to the right scale.

  [Test Case]

   * It can be easily observed on HiDPI display, when Unity Greeter is
  starting.

  [Regression Potential]

   * If u-s-d failed to launch, Unity Greeter stuck at waiting u-s-d's
  signal and failed to proceed. But it's not likely to happen.

  

  Just after the upgrade to ubuntu 16.04, when lightdm starts the
  resolution is 2560x1600. Then, after about half a second it is
  automatically changed to 1280x800. This happens systematically at each
  boot. No external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:39:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (525 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1571640/+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 1327412] Re: Delay during PXE Boot, IP-Config gives up

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package klibc - 2.0.4-8ubuntu1.16.04.1

---
klibc (2.0.4-8ubuntu1.16.04.1) xenial; urgency=medium

  * debian/patches/broadcast_dhcp_send.patch: yiaddr should always be set to 0
(INADDR_ANY) when sending those messages we're sending as a DHCP client,
so DHCPDISCOVER and DHCPREQUEST for now. DHCPDISCOVER already did the
right thing since 2.0.4-8ubuntu1, this fixes DHCPREQUEST. (LP: #1327412)

 -- Mathieu Trudel-Lapierre   Tue, 26 Apr 2016
12:59:59 -0400

** Changed in: klibc (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/1327412

Title:
  Delay during PXE Boot, IP-Config gives up

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Trusty:
  Fix Released
Status in klibc source package in Wily:
  Won't Fix
Status in klibc source package in Xenial:
  Fix Released
Status in klibc package in Debian:
  New

Bug description:
  [Impact]
  PXE booting users with live images or other minimal setups using klibc-utils.

  [Test case]
  Attempt to PXE boot using Ubuntu live images; see below for details.

  [Regression potential]
  This forces the yiaddr (client requested/current IP) to be set to 0 when 
sending DHCP messages; currently the messages are DHCPREQUEST and DHCPDISCOVER, 
which should typically only happen when there is no IP set on the device and it 
is otherwise unable to receive unicast (on account of not being configured). 
Should there be a need to send other messages which would require setting the 
yiaddr value to the current configured IP address, a naive change would break. 
The yiaddr variable would need to be adjusted to pull value from a new 
location, or initialized directly by the callers to dhcp_send() where the 
business logic would reside.

  ---

  Attempting to PXE boot both the 12.04.3 and 14.04 Live images.   PXE
  boot works normally (PXE Menu, select desired image, image begins
  loading), then the boot process hangs while IP-Config attempts to get
  an IP address:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 2 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 3 secs - giving up

  These lines appear very quickly (5 seconds has NOT elapsed), after
  about a minute, we get this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 4 secs - giving up

  Some time later, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 6 secs - giving up

  Until finally, this:

  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: no response after 9 secs - giving up
  IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP
  IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP
  IP-Config: eth0 guessed broadcast address 172.25.11.31
  IP-Config: eth0 complete (dhcp from 172.25.10.20):
  (snip)

  While watching the DHCP server logs, Ubuntu is either not sending a
  DHCP Discover at times, or is not replying back with a DHCPRequest
  during these sessions, presumably ignoring an response from the DHCP
  server.  From the initial booting of the system via PXE, to when
  Ubuntu finally shows the desktop, almost 12 minutes will have elapsed.

  I am seeing this same behavior on both 12.04.3 and 14.04.  After
  finding a number of similar erros via Google and no real resolution, I
  have opened this bug.

  The system experiencing this issue has multiple ethernet interfaces
  (actual HW, not a VM), some Google found solutions suggest hard coding
  DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf, however this isn't
  acceptable as a system attempting to PXE boot may be using an
  alternate port for the network.

  I have found what looks to be a very similar bug filed for Debian,
  #584583, which also contains a patch for this issue (under Debian).

  I have no problems in PXE booting to various Windows, RedHat, Centos,
  or Fedora OSs.  Ubuntu is the only Live OS that I'm attempting to boot
  at present.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340
  CrashDB: ubuntu

[Group.of.nepali.translators] [Bug 1509031] Re: can no longer alt-drag firefox/thunderbird windows above top of screen

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package metacity - 1:3.18.5-0ubuntu0.1

---
metacity (1:3.18.5-0ubuntu0.1) xenial; urgency=medium

  * New upstream bugfix release.
- Fixes issues with windows not being destroyed after drag and drop
  (LP: #1592953).
- Fixes issues with moving windows above top of screen (LP: #1509031).
  * Drop fix_xerror_in_free_win.diff, applied upstream.
  * Add a patch from upstream to restore window resize using titlebar
(titlebar_resize.diff, LP: #1596574).

 -- Dmitry Shachnev   Tue, 28 Jun 2016 15:32:39
+0300

** Changed in: metacity (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/1509031

Title:
  can no longer alt-drag firefox/thunderbird windows above top of screen

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

Bug description:
  [General information about the SRU]
  * It includes fix for bug 1582687 which was already backported.
  * It fixes bug 1509031, bug 1592953 and bug 1596574.
  * Other commits are minor bugfixes, the full log can be seen here:
https://git.gnome.org/browse/metacity/log/?h=3.18.5
  * There is also a NEWS file, here:
https://git.gnome.org/browse/metacity/tree/NEWS?h=3.18.5

  [Impact]
  Windows can not be moved above the top of screen because the coordinates 
system used is wrong.

  [Test Case]
  * Launch a non-CSD application, such as Firefox or Thunderbird;
  * Try Alt-dragging it above the top of the screen.

  [Regression Potential]
  The fix is changing the coordinates system to the right one and should not 
cause any regressions.

  -

  After upgrading to 15.10, I can no longer Alt-drag Firefox and
  Thunderbird windows above the top of the screen.  When I attempt to do
  so, the window snaps downward along the y-axis so that the titlebar
  aligns with top of screen.  Other applications such as gnome-terminal
  do not seem to be affected.

  I ran git-bisect on metacity, and narrowed the regression down to this
  commit:

  
https://github.com/GNOME/metacity/commit/90b36abebdf69be0abaec4015d01e46296f6f5d6

  commit 90b36abebdf69be0abaec4015d01e46296f6f5d6
  Author: Alberts Muktupāvels 
  Date:   Fri Apr 3 23:30:20 2015 +0300

  window: add a meta_window_get_titlebar_rect

  Based on mutter commits:
  
https://git.gnome.org/browse/mutter/commit/?id=3a0af0faaebb1af75925c70ad98e73c61e57639b
  
https://git.gnome.org/browse/mutter/commit/?id=ac099343dab7b5048ce242958c454c55d1924902

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: metacity 1:3.17.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu Oct 22 13:35:02 2015
  InstallationDate: Installed on 2014-09-22 (394 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: metacity
  UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1509031/+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 1551747] Re: ubuntu-fan causes issues during network configuration

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-fan - 0.9.1

---
ubuntu-fan (0.9.1) xenial; urgency=medium

  [ Andy Whitcroft ]
  * fanatic: fix legacy command line form syntax error (LP: #1584150)
  * fanctl/fanatic: add help commands/options with initial pointers
(LP: #1535054)

  [ Jay Vosburgh ]
  * fanatic: fix underlay with calculation (LP: #1584092)

  [ Andy Whitcroft ]
  * fanctl/fanatic: remove invalid web reference from manual pages.
(LP: #1582956)
  * fanatic: detect user specified underlay address without overlay
(LP: #1584692)
  * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775)
  * fanatic: test-host -- use the selected underlay width to calculate the 
remote addresses
(LP: #1584878)
  * fanctl: fix net start/stop exit codes. (LP: #1551747)
  * fanatic: install ping and nc when needed (LP: #1586176)
  * fanatic: switch docker testing to lts images (LP: #1586169)

 -- Andy Whitcroft   Mon, 04 Jul 2016 14:35:39 +0100

** Changed in: ubuntu-fan (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/1551747

Title:
  ubuntu-fan causes issues during network configuration

Status in cloud-init:
  New
Status in Snappy:
  Confirmed
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Yakkety:
  Fix Released

Bug description:
  it seems that ubuntu-fan is causing issues with network configuration.

  On 16.04 daily image:

  root@localhost:~# snappy list
  NameDate   Version  Developer
  canonical-pi2   2016-02-02 3.0  canonical
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical
  ubuntu-core 2016-02-22 16.04.0-10.armhf canonical

  I see this when I'm activating a wifi card on a raspberry pi 2.

  root@localhost:~# ifdown wlan0
  ifdown: interface wlan0 not configured
  root@localhost:~# ifup wlan0
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/wlan0/c4:e9:84:17:31:9b
  Sending on   LPF/wlan0/c4:e9:84:17:31:9b
  Sending on   Socket/fallback
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x81c0c95e)
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x81c0c95e)
  DHCPREQUEST of 192.168.0.170 on wlan0 to 255.255.255.255 port 67 
(xid=0x5ec9c081)
  DHCPOFFER of 192.168.0.170 from 192.168.0.251
  DHCPACK of 192.168.0.170 from 192.168.0.251
  RTNETLINK answers: File exists
  bound to 192.168.0.170 -- renewal in 17145 seconds.
  run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1
  Failed to bring up wlan0.

  ===
  [Impact]

  Installing ubuntu-fan can trigger error messages when initialising
  with no fan configuration.

  [Test Case]

  As above.

  [Regression Potential]

  Low, suppresses errorneous error messages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1551747/+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 1584092] Re: Docker misconfigured when using non-default overlay/underlay netmask size

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-fan - 0.9.1

---
ubuntu-fan (0.9.1) xenial; urgency=medium

  [ Andy Whitcroft ]
  * fanatic: fix legacy command line form syntax error (LP: #1584150)
  * fanctl/fanatic: add help commands/options with initial pointers
(LP: #1535054)

  [ Jay Vosburgh ]
  * fanatic: fix underlay with calculation (LP: #1584092)

  [ Andy Whitcroft ]
  * fanctl/fanatic: remove invalid web reference from manual pages.
(LP: #1582956)
  * fanatic: detect user specified underlay address without overlay
(LP: #1584692)
  * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775)
  * fanatic: test-host -- use the selected underlay width to calculate the 
remote addresses
(LP: #1584878)
  * fanctl: fix net start/stop exit codes. (LP: #1551747)
  * fanatic: install ping and nc when needed (LP: #1586176)
  * fanatic: switch docker testing to lts images (LP: #1586169)

 -- Andy Whitcroft   Mon, 04 Jul 2016 14:35:39 +0100

** Changed in: ubuntu-fan (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/1584092

Title:
  Docker misconfigured when using non-default overlay/underlay netmask
  size

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released

Bug description:
  Fan allows for variable sized subnet map sizes.  For example, if I
  want to map a /24 to a /16 instead of the default /16 to /8, Fan
  supports this.  However, when configuring this via fanatic, I see that
  docker configuration fails.  In /etc/default/docker, the --fixed-cidr
  flag is defined incorrectly.

  $ sudo fanatic
  Welcome to the fanatic fan networking wizard.  This will help you set
  up an example fan network and optionally configure docker and/or LXD touse 
this network.  See fanatic(1) for more details.

  Configure fan underlay (hit return to accept, or specify alternative) 
[192.168.0.0/16]: 192.168.1.0/24
  Configure fan overlay (hit return to accept, or specify alternative) 
[250.0.0.0/8]: 250.99.0.0/16
  Create LXD networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 [Yn]: 
Y
  Profile fan-250-99 created
  Create docker networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 
[Yn]: Y
  Job for docker.service failed because the control process exited with error 
code. See "systemctl status docker.service" and "journalctl -xe" for details.
  Test LXD networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16
  (NOTE: potentially triggers large image downloads) [Yn]: n
  Test docker networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16
  (NOTE: potentially triggers large image downloads) [Yn]: n
  This host IP address: 192.168.1.10
  Remote test host IP address (none to skip):
  /usr/sbin/fanatic: Testing skipped

  $ grep "DOCKER_OPTS" /etc/default/docker
  # Use DOCKER_OPTS to modify the daemon startup options.
  #DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4"
  DOCKER_OPTS=" -b fan-250-99 --mtu=1450 --iptables=false 
--fixed-cidr=250.99.10.0/40"

  May 20 05:15:30 macbook docker[27364]:
  time="2016-05-20T05:15:30.411933688-07:00" level=fatal msg="Error
  starting daemon: Error initializing network controller: invalid CIDR
  address: 250.99.10.0/40"

  ===
  [Impact]

  Non default network splits are not honoured correctly.

  [Test Case]

  Setup fan with non /8 /16 split, as per reporter.

  [Regression Potential]

  Low, as these currently do not work correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584092/+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 1584775] Re: fanatic does not use the correct LXD command to import image for fanatic-test container

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-fan - 0.9.1

---
ubuntu-fan (0.9.1) xenial; urgency=medium

  [ Andy Whitcroft ]
  * fanatic: fix legacy command line form syntax error (LP: #1584150)
  * fanctl/fanatic: add help commands/options with initial pointers
(LP: #1535054)

  [ Jay Vosburgh ]
  * fanatic: fix underlay with calculation (LP: #1584092)

  [ Andy Whitcroft ]
  * fanctl/fanatic: remove invalid web reference from manual pages.
(LP: #1582956)
  * fanatic: detect user specified underlay address without overlay
(LP: #1584692)
  * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775)
  * fanatic: test-host -- use the selected underlay width to calculate the 
remote addresses
(LP: #1584878)
  * fanctl: fix net start/stop exit codes. (LP: #1551747)
  * fanatic: install ping and nc when needed (LP: #1586176)
  * fanatic: switch docker testing to lts images (LP: #1586169)

 -- Andy Whitcroft   Mon, 04 Jul 2016 14:35:39 +0100

** Changed in: ubuntu-fan (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/1584775

Title:
  fanatic does not use the correct LXD command to import image for
  fanatic-test container

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released

Bug description:
  Something I noticed while trying to use fanatic (see related bug
  1584692):

  /usr/sbin/fanatic: 808: /usr/sbin/fanatic: lxd-images: not found

  Because of this the lxd test cannot spin up the test container, as it can't 
import the image.
  I managed to get it to work by patching fanatic like this:

  ---
  # Check if we have images already...
  lxc image show fanatic-test >/dev/null 2>&1
  if [ "$?" -ne 0 ]; then
  echo "local lxd test: pulling container images ..."
  lxc image copy ubuntu:xenial local: --alias fanatic-test
  local rc="$?"
  if [ "$rc" -ne 0 ]; then
  echo "local lxd test: lxc image import failure, 
skipping test."
  return "$rc"
  fi
  fi
  ---

  There's no lxd-images on my machine and I suspect it used to be one in
  an earlier version of the LXD package. I'm using lxd 2.0.1-0ubuntu1~16
  amd64

  ubuntu-fan is 0.9.0

  ===
  [Impact]

  LXC has changed how images are fetched.  Preventing testing of a new
  install.

  [Test Case]

  Setup the default fan overlay/underlay and request LXC testing.

  [Regression Potential]

  Low, this is only used during initial setup.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584775/+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 1535054] Re: fanatic doesn't respond to --help

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-fan - 0.9.1

---
ubuntu-fan (0.9.1) xenial; urgency=medium

  [ Andy Whitcroft ]
  * fanatic: fix legacy command line form syntax error (LP: #1584150)
  * fanctl/fanatic: add help commands/options with initial pointers
(LP: #1535054)

  [ Jay Vosburgh ]
  * fanatic: fix underlay with calculation (LP: #1584092)

  [ Andy Whitcroft ]
  * fanctl/fanatic: remove invalid web reference from manual pages.
(LP: #1582956)
  * fanatic: detect user specified underlay address without overlay
(LP: #1584692)
  * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775)
  * fanatic: test-host -- use the selected underlay width to calculate the 
remote addresses
(LP: #1584878)
  * fanctl: fix net start/stop exit codes. (LP: #1551747)
  * fanatic: install ping and nc when needed (LP: #1586176)
  * fanatic: switch docker testing to lts images (LP: #1586169)

 -- Andy Whitcroft   Mon, 04 Jul 2016 14:35:39 +0100

** Changed in: ubuntu-fan (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/1535054

Title:
  fanatic doesn't respond to --help

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released

Bug description:
  Trying out fanatic today I found it didn't respect a lot of
  conventional input, like --help or -h.

  Please provide useful output for -? and -h and --help as well as
  "fanatic help"

  Also, you have a typo with "uknown command" :)

  Thanks!

  ===
  [Impact]

  Barrier to user adoption.

  [Test Case]

  Confirm fanatic --help et al produce useful output.

  [Regression Potential]

  Low, these are only triggered by specific command line forms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1535054/+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 1574892] Re: IDLE 3.5.1+ runtime error on Options -> Configure IDLE

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package python3.5 - 3.5.2-2~16.01

---
python3.5 (3.5.2-2~16.01) xenial-proposed; urgency=medium

  * SRU: LP: #1591887. Backport 3.5.2 to 16.04 LTS.

python3.5 (3.5.2-2) unstable; urgency=medium

  * asyncio: Fix callbacks race in SelectorLoop.sock_connect, proposed patch
taken from https://github.com/python/asyncio/pull/366.
  * asyncio: Fix NameError in asyncio.sslproto. Closes: #827453.

python3.5 (3.5.2-1) unstable; urgency=medium

  * Python 3.5.2 release.
- Issue #26867: Ubuntu's openssl OP_NO_SSLv3 is forced on by default;
  fix test.
- Issue #27365: Allow non-ascii in idlelib/NEWS.txt.

python3.5 (3.5.2~rc1-3) unstable; urgency=medium

  * Fix building with the wheel files in the source package.

python3.5 (3.5.2~rc1-1) unstable; urgency=medium

  * Python 3.5.2 release candidate 1.
- Issue #15657: Delete incorrect statement from PyMethodDef documentation.
- Issue #27289: Prevent test_urllib2net failures due to EOFError raised
  by ftplib.
- Issue #25455: Clean up reference loops created in tests for recursive.
- Issue #27190: Raise NotSupportedError if sqlite3 is older than 3.3.1.
- Issue #27188: Fix various sqlite3 documentation errors.
- Issue #15476: Make "code object" its own entry in the index.
- Issue #8491: Add link to Gnu Readline configuration documentation.
- Issue #24617: Add comment for os.mkdir about mode quirks.
- Issue #27280: Fix typo in IPv6Network documentation.
- Issue #17500, and https://github.com/python/pythondotorg/issues/945:
  Remove unused and outdated icons.
- Issue #20900: distutils register command now decodes HTTP responses
  correctly.
- Issue #5124: Paste with selection should always replace.
  This is how paste work on Windows, Mac, modern Linux apps, and ttk
  widgets.  The exception was X11 tk widgets.
- Issue #27223: aio: Fix _read_ready and _write_ready to respect _conn_lost.
- Issue #22970: asyncio: Fix inconsistency cancelling Condition.wait.
- Issue #22558: Add remaining doc links to source code for Python-coded
  modules.
- Issue #21386: Implement missing IPv4Address.is_global property.
- Issue #27194: superfluous truncate calls in tarfile.py slow down
  extraction.
- Issue #14209: pkgutil.iter_zipimport_modules ignores the prefix for
  packages.
- Issue #24136: Document generalized unpacking, PEP 448.
- Issue #27286: Fixed compiling BUILD_MAP_UNPACK_WITH_CALL opcode.  Calling
  function with generalized unpacking (PEP 448) and conflicting keyword
  names could cause undefined behavior.
- Issue #25455: Fixed a crash in repr of ElementTree.Element with recursive
  tag.
  * Extend debian/copyright to the files shipped in the wheel files.

python3.5 (3.5.1-16) unstable; urgency=high

  * Restore the distutils-init patch, only applied on upstream trunk.

python3.5 (3.5.1-15) unstable; urgency=high

  * Fix bad update of the distutils-install-layout patch.

python3.5 (3.5.1-14) unstable; urgency=medium

  * Update to 20160609 from the 3.5 branch.
- A new version of typing.py provides several new classes and
  features: @overload outside stubs, Reversible, DefaultDict, Text,
  ContextManager, Type[], NewType(), TYPE_CHECKING, and numerous bug
  fixes (note that some of the new features are not yet implemented in
  mypy or other static analyzers).  Also classes for PEP 492
  (Awaitable, AsyncIterable, AsyncIterator) have been added (in fact
  they made it into 3.5.1 but were never mentioned).
- Issue #25738: Stop http.server.BaseHTTPRequestHandler.send_error() from
  sending a message body for 205 Reset Content.  Also, don't send Content
  header fields in responses that don't have a body.
- Issue #21313: Fix the "platform" module to tolerate when sys.version
  contains truncated build information.
- Issue #26839: On Linux, :func:`os.urandom` now calls ``getrandom()`` with
  ``GRND_NONBLOCK`` to fall back on reading ``/dev/urandom`` if the urandom
  entropy pool is not initialized yet. Closes: #824379.
- Issue #27164: In the zlib module, allow decompressing raw Deflate streams
  with a predefined zdict.
- Issue #24291: Fix wsgiref.simple_server.WSGIRequestHandler to completely
  write data to the client.  Previously it could do partial writes and
  truncate data.  Also, wsgiref.handler.ServerHandler can now handle stdout
  doing partial writes, but this is deprecated.
- Issue #26809: Add ``__all__`` to :mod:`string`.
- Issue #26373: subprocess.Popen.communicate now correctly ignores
  BrokenPipeError when the child process dies before .communicate()
  is called in more/all circumstances.
- Issue #24759: Make clear in idlelib.idle_test.__init__ that the directory
  is a private implementation of test.test_idle and tool for maintainers.
- Issue #27196: Stop 'ThemeChanged'

[Group.of.nepali.translators] [Bug 1596574] Re: Cannot resize window by dragging the top edge

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package metacity - 1:3.18.5-0ubuntu0.1

---
metacity (1:3.18.5-0ubuntu0.1) xenial; urgency=medium

  * New upstream bugfix release.
- Fixes issues with windows not being destroyed after drag and drop
  (LP: #1592953).
- Fixes issues with moving windows above top of screen (LP: #1509031).
  * Drop fix_xerror_in_free_win.diff, applied upstream.
  * Add a patch from upstream to restore window resize using titlebar
(titlebar_resize.diff, LP: #1596574).

 -- Dmitry Shachnev   Tue, 28 Jun 2016 15:32:39
+0300

** Changed in: metacity (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/1596574

Title:
  Cannot resize window by dragging the top edge

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

Bug description:
  [General information about the SRU]
  * It includes fix for bug 1582687 which was already backported.
  * It fixes bug 1509031, bug 1592953 and bug 1596574.
  * Other commits are minor bugfixes, the full log can be seen here:
https://git.gnome.org/browse/metacity/log/?h=3.18.5
  * There is also a NEWS file, here:
https://git.gnome.org/browse/metacity/tree/NEWS?h=3.18.5

  [Impact]
  This affects only users of Metacity with compositing mode disabled (which are 
usually users on old hardware or virtualized systems).

  [Test Case]
  * gsettings set org.gnome.metacity compositing-manager false;
  * Try resizing a window by dragging its top edge.

  [Regression Potential]
  The fix is one-line and should not cause any regressions.

  -

  Bug Version: 1:3.18.4-0ubuntu0.3

  Metacity running without composite manager.

  Users cannot resize window by dragging its top edge.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: metacity 1:3.18.4-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Jun 27 23:18:31 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: metacity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1596574/+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 1584878] Re: fanatic remote host test fails when using non-default subnet sizes

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-fan - 0.9.1

---
ubuntu-fan (0.9.1) xenial; urgency=medium

  [ Andy Whitcroft ]
  * fanatic: fix legacy command line form syntax error (LP: #1584150)
  * fanctl/fanatic: add help commands/options with initial pointers
(LP: #1535054)

  [ Jay Vosburgh ]
  * fanatic: fix underlay with calculation (LP: #1584092)

  [ Andy Whitcroft ]
  * fanctl/fanatic: remove invalid web reference from manual pages.
(LP: #1582956)
  * fanatic: detect user specified underlay address without overlay
(LP: #1584692)
  * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775)
  * fanatic: test-host -- use the selected underlay width to calculate the 
remote addresses
(LP: #1584878)
  * fanctl: fix net start/stop exit codes. (LP: #1551747)
  * fanatic: install ping and nc when needed (LP: #1586176)
  * fanatic: switch docker testing to lts images (LP: #1586169)

 -- Andy Whitcroft   Mon, 04 Jul 2016 14:35:39 +0100

** Changed in: ubuntu-fan (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/1584878

Title:
  fanatic remote host test fails when using non-default subnet sizes

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released

Bug description:
  When conducting the remote host testing, fanatic incorrectly
  calculates the ip for the remote test host on the Fan.

  My remote host ip's are 192.168.1.3 and 192.168.1.10.  I'm using non-
  default subnet sizes for the overlay/underlays (ie -o 250.99.0.0/16
  and -u 192.168.1.0/24).  Both LXD and Docker tests pass, but, as
  noted, the remote host testing fails:

  test slave: ping test (250.99.1.4) ...
  test slave: ping test ... FAIL

  You'll notice the ip is incorrect, 250.99.1.4.  It should be
  250.99.3.1 in this example.

  Raw output of failing fanatic test run is below:

  $ sudo fanatic
  Welcome to the fanatic fan networking wizard.  This will help you set
  up an example fan network and optionally configure docker and/or LXD to
  use this network.  See fanatic(1) for more details.

  Configure fan underlay (hit return to accept, or specify alternative) 
[192.168.0.0/16]: 192.168.1.0/24
  Configure fan overlay (hit return to accept, or specify alternative) 
[250.0.0.0/8]: 250.99.0.0/16
  Create LXD networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 [Yn]: 
Y
  Profile fan-250-99 created
  Create docker networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 
[Yn]: Y
  Test LXD networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16
  (NOTE: potentially triggers large image downloads) [Yn]: Y
  local lxd test: creating test container (Ubuntu:16.04) ...
  Creating fanatic-test
  Starting fanatic-test
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  test master: ping test (250.99.10.166) ...
  test slave: ping test (250.99.10.1) ...
  test master: ping test ... PASS
  test master: short data test (250.99.10.1 -> 250.99.10.166) ...
  test slave: ping test ... PASS
  test slave: short data test (250.99.10.166 -> 250.99.10.1) ...
  test slave: short data ... PASS
  test master: short data ... PASS
  test slave: long data test (250.99.10.166 -> 250.99.10.1) ...
  test master: long data test (250.99.10.1 -> 250.99.10.166) ...
  test master: long data ... PASS
  test slave: long data ... PASS
  local lxd test: destroying test container ...
  local lxd test: test complete PASS (master=0 slave=0)
  Test docker networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16
  (NOTE: potentially triggers large image downloads) [Yn]: Y
  local docker test: creating test container ...
  e47583ee4f18c95edfcb28e5b2514c0924527f30b3485f62d343fe8bf1000170
  test master: ping test (250.99.10.0) ...
  test slave: ping test (250.99.10.1) ...
  test master: ping test ... PASS
  test master: short data test (250.99.10.1 -> 250.99.10.0) ...
  test slave: ping test ... PASS
  test slave: short data test (250.99.10.0 -> 250.99.10.1) ...
  test slave: short data ... PASS
  test master: short data ... PASS
  test slave: long data test (250.99.10.0 -> 250.99.10.1) ...
  test master: long data test (250.99.10.1 -> 250.99.10.0) ...
  test master: long data ... PASS
  test slave: long data ... PASS
  local docker test: destroying test container ...
  fanatic-test
  fanatic-test
  local docker test: test complete PASS (master=0 slave=0)
  This host IP address: 192.168.1.10
  Remote test host IP address (none to skip): 192.168.1.3
  host test: starting ...
  test slave: ping test (250.99.1.4) ...
  test slave: ping test ... FAIL
  --- transcript start ---
  PING 250.99.1.4

[Group.of.nepali.translators] [Bug 1584692] Re: fanatic does not use the user-specified underlay, but 192.168.0.0/16

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-fan - 0.9.1

---
ubuntu-fan (0.9.1) xenial; urgency=medium

  [ Andy Whitcroft ]
  * fanatic: fix legacy command line form syntax error (LP: #1584150)
  * fanctl/fanatic: add help commands/options with initial pointers
(LP: #1535054)

  [ Jay Vosburgh ]
  * fanatic: fix underlay with calculation (LP: #1584092)

  [ Andy Whitcroft ]
  * fanctl/fanatic: remove invalid web reference from manual pages.
(LP: #1582956)
  * fanatic: detect user specified underlay address without overlay
(LP: #1584692)
  * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775)
  * fanatic: test-host -- use the selected underlay width to calculate the 
remote addresses
(LP: #1584878)
  * fanctl: fix net start/stop exit codes. (LP: #1551747)
  * fanatic: install ping and nc when needed (LP: #1586176)
  * fanatic: switch docker testing to lts images (LP: #1586169)

 -- Andy Whitcroft   Mon, 04 Jul 2016 14:35:39 +0100

** Changed in: ubuntu-fan (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/1584692

Title:
  fanatic does not use the user-specified underlay, but 192.168.0.0/16

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released

Bug description:
  On a xenial machine, I tried to use fanatic to configure the fan with
  underlay 10.88.0.0/16 and the suggested overlay 250.0.0.0/8, but the
  underlay suggested by fanatic (192.168.0.0/16) was used instead of
  10.88.0.0/16 I specified.

  Here's the paste of the session: http://paste.ubuntu.com/16630235/

  ===
  [Impact]

  Configuration for some combinations which including using the default
  overlay only will be miss-parsed.

  [Test Case]

  As above.

  [Regression Potential]

  Low, only affects new setup.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584692/+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 1586176] Re: [Yakkety] fanatic fails running docker test

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-fan - 0.9.1

---
ubuntu-fan (0.9.1) xenial; urgency=medium

  [ Andy Whitcroft ]
  * fanatic: fix legacy command line form syntax error (LP: #1584150)
  * fanctl/fanatic: add help commands/options with initial pointers
(LP: #1535054)

  [ Jay Vosburgh ]
  * fanatic: fix underlay with calculation (LP: #1584092)

  [ Andy Whitcroft ]
  * fanctl/fanatic: remove invalid web reference from manual pages.
(LP: #1582956)
  * fanatic: detect user specified underlay address without overlay
(LP: #1584692)
  * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775)
  * fanatic: test-host -- use the selected underlay width to calculate the 
remote addresses
(LP: #1584878)
  * fanctl: fix net start/stop exit codes. (LP: #1551747)
  * fanatic: install ping and nc when needed (LP: #1586176)
  * fanatic: switch docker testing to lts images (LP: #1586169)

 -- Andy Whitcroft   Mon, 04 Jul 2016 14:35:39 +0100

** Changed in: ubuntu-fan (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/1586176

Title:
  [Yakkety] fanatic fails running docker test

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released

Bug description:
  On Yakkety 16.10, fanatic fails trying to run docker tests and then
  hangs:

  $sudo fanatic
  Welcome to the fanatic fan networking wizard.  This will help you set
  up an example fan network and optionally configure docker and/or LXD to
  use this network.  See fanatic(1) for more details.

  Configure fan underlay (hit return to accept, or specify alternative) 
[192.168.0.0/16]:
  Configure fan overlay (hit return to accept, or specify alternative) 
[250.0.0.0/8]:
  LXD already configured
  Docker already configured
  Test LXD networking for underlay:192.168.1.16/16 overlay:250.0.0.0/8
  (NOTE: potentially triggers large image downloads) [Yn]: n
  Test docker networking for underlay:192.168.1.16/16 overlay:250.0.0.0/8
  (NOTE: potentially triggers large image downloads) [Yn]: Y
  local docker test: pulling container images ...
  Using default tag: latest
  latest: Pulling from library/ubuntu
  6d28225f8d96: Pull complete
  166102ec41af: Pull complete
  d09bfba2bd6a: Pull complete
  c80dad39a6c0: Pull complete
  a3ed95caeb02: Pull complete
  Digest: 
sha256:5718d664299eb1db14d87db7bfa6945b28879a67b74f36da3e34f5914866b71c
  Status: Downloaded newer image for ubuntu:latest
  local docker test: creating test container ...
  f0cc43d63b6f687e47773fb6087bf1615dc7f479ef8e536594e0f4ec6a08b404
  test master: ping test (250.1.16.0) ...
  test slave: ping test (250.1.16.1) ...
  test slave: ping test ... FAIL
  --- transcript start ---
  /bin/sh: 74: ping: not found
  --- transcript end ---
  test slave: short data test (250.1.16.0 -> 250.1.16.1) ...
  test master: ping test ... PASS
  test master: short data test (250.1.16.1 -> 250.1.16.0) ...

  ===
  [Impact]

  Unable to test docker configuration due to the removal of ping from
  the default images.

  [Test Case]

  Request docker configuration and testing.

  [Regression Potential]

  Low, only used during initial configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1586176/+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 1582956] Re: fan[ctl | atic] man page has reference to ubuntu.com/fan which 404s

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-fan - 0.9.1

---
ubuntu-fan (0.9.1) xenial; urgency=medium

  [ Andy Whitcroft ]
  * fanatic: fix legacy command line form syntax error (LP: #1584150)
  * fanctl/fanatic: add help commands/options with initial pointers
(LP: #1535054)

  [ Jay Vosburgh ]
  * fanatic: fix underlay with calculation (LP: #1584092)

  [ Andy Whitcroft ]
  * fanctl/fanatic: remove invalid web reference from manual pages.
(LP: #1582956)
  * fanatic: detect user specified underlay address without overlay
(LP: #1584692)
  * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775)
  * fanatic: test-host -- use the selected underlay width to calculate the 
remote addresses
(LP: #1584878)
  * fanctl: fix net start/stop exit codes. (LP: #1551747)
  * fanatic: install ping and nc when needed (LP: #1586176)
  * fanatic: switch docker testing to lts images (LP: #1586169)

 -- Andy Whitcroft   Mon, 04 Jul 2016 14:35:39 +0100

** Changed in: ubuntu-fan (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/1582956

Title:
  fan[ctl | atic]  man page has reference to ubuntu.com/fan which 404s

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released

Bug description:
  Reading the man page for fanctl and fanatic I see a reference to
  ubuntu.com/fan, but that page is currently 404'ing

  Specifically:

  $ man fanctl
   -or-
  $ man fanatic

  . . .

  SEE ALSO
     fanctl(8) /usr/share/doc/ubuntu-fan/README
     http://www.ubuntu.com/fan

  ===
  [Impact]

  Missleading documentation.

  [Test Case]

  Confirm non-existant link is removed from manual page.

  [Regression Potential]

  None, non functional change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1582956/+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 1584150] Re: fanatic: legacy mode triggers syntax error

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-fan - 0.9.1

---
ubuntu-fan (0.9.1) xenial; urgency=medium

  [ Andy Whitcroft ]
  * fanatic: fix legacy command line form syntax error (LP: #1584150)
  * fanctl/fanatic: add help commands/options with initial pointers
(LP: #1535054)

  [ Jay Vosburgh ]
  * fanatic: fix underlay with calculation (LP: #1584092)

  [ Andy Whitcroft ]
  * fanctl/fanatic: remove invalid web reference from manual pages.
(LP: #1582956)
  * fanatic: detect user specified underlay address without overlay
(LP: #1584692)
  * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775)
  * fanatic: test-host -- use the selected underlay width to calculate the 
remote addresses
(LP: #1584878)
  * fanctl: fix net start/stop exit codes. (LP: #1551747)
  * fanatic: install ping and nc when needed (LP: #1586176)
  * fanatic: switch docker testing to lts images (LP: #1586169)

 -- Andy Whitcroft   Mon, 04 Jul 2016 14:35:39 +0100

** Changed in: ubuntu-fan (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/1584150

Title:
  fanatic: legacy mode triggers syntax error

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released

Bug description:
  Attempting to use the legacy command line format leads to a syntax
  error.

  ===
  [Impact]

  Legacy use cases will fail.

  [Test Case]

  Confirm "fanctl up 250.0.0.0/8 192.168.0.0/16" is parsed correctly.

  [Regression Potential]

  Low, these are rarely used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584150/+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 1586169] Re: [Yakkety] fanatic fails running lxd test

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-fan - 0.9.1

---
ubuntu-fan (0.9.1) xenial; urgency=medium

  [ Andy Whitcroft ]
  * fanatic: fix legacy command line form syntax error (LP: #1584150)
  * fanctl/fanatic: add help commands/options with initial pointers
(LP: #1535054)

  [ Jay Vosburgh ]
  * fanatic: fix underlay with calculation (LP: #1584092)

  [ Andy Whitcroft ]
  * fanctl/fanatic: remove invalid web reference from manual pages.
(LP: #1582956)
  * fanatic: detect user specified underlay address without overlay
(LP: #1584692)
  * fanatic: switch from lxd-images to using cached lxc images. (LP: #1584775)
  * fanatic: test-host -- use the selected underlay width to calculate the 
remote addresses
(LP: #1584878)
  * fanctl: fix net start/stop exit codes. (LP: #1551747)
  * fanatic: install ping and nc when needed (LP: #1586176)
  * fanatic: switch docker testing to lts images (LP: #1586169)

 -- Andy Whitcroft   Mon, 04 Jul 2016 14:35:39 +0100

** Changed in: ubuntu-fan (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/1586169

Title:
  [Yakkety] fanatic fails running lxd test

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released

Bug description:
  Running Yakkety 16.10, fanatic text for lxd fails because the
  "requested image couldn't be found", but then continues to emit error
  messages until killed.  fanatic should gracefully fail the test and
  move on.  Raw output is as follows:

  $ sudo fanatic
  Welcome to the fanatic fan networking wizard.  This will help you set
  up an example fan network and optionally configure docker and/or LXD to
  use this network.  See fanatic(1) for more details.

  Configure fan underlay (hit return to accept, or specify alternative) 
[192.168.0.0/16]:
  Configure fan overlay (hit return to accept, or specify alternative) 
[250.0.0.0/8]:
  Create LXD networking for underlay:192.168.0.0/16 overlay:250.0.0.0/8 [Yn]: Y
  Profile fan-250 created
  Create docker networking for underlay:192.168.0.0/16 overlay:250.0.0.0/8 
[Yn]: Y
  Test LXD networking for underlay:192.168.1.16/16 overlay:250.0.0.0/8
  (NOTE: potentially triggers large image downloads) [Yn]: Y
  local lxd test: creating test container (Ubuntu:16.10) ...
  Creating fanatic-test
  error: The requested image couldn't be found.
  lxd test: Waiting for addresses on eth0 ...
  error: not found
  lxd test: Waiting for addresses on eth0 ...
  error: not found
  lxd test: Waiting for addresses on eth0 ...
  error: not found
  lxd test: Waiting for addresses on eth0 ...
  error: not found

  ===
  [Impact]

  Unable to test LXC configuration.

  [Test Case]

  Configure fan and confirm LXC testing.

  [Regression Potential]

  Low, only used during initial configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1586169/+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 1592953] Re: Nautilus bookmarks folders leave permanent 'icon' on desktop

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package metacity - 1:3.18.5-0ubuntu0.1

---
metacity (1:3.18.5-0ubuntu0.1) xenial; urgency=medium

  * New upstream bugfix release.
- Fixes issues with windows not being destroyed after drag and drop
  (LP: #1592953).
- Fixes issues with moving windows above top of screen (LP: #1509031).
  * Drop fix_xerror_in_free_win.diff, applied upstream.
  * Add a patch from upstream to restore window resize using titlebar
(titlebar_resize.diff, LP: #1596574).

 -- Dmitry Shachnev   Tue, 28 Jun 2016 15:32:39
+0300

** Changed in: metacity (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/1592953

Title:
  Nautilus bookmarks folders leave permanent 'icon' on desktop

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

Bug description:
  [General information about the SRU]
  * It includes fix for bug 1582687 which was already backported.
  * It fixes bug 1509031, bug 1592953 and bug 1596574.
  * Other commits are minor bugfixes, the full log can be seen here:
    https://git.gnome.org/browse/metacity/log/?h=3.18.5
  * There is also a NEWS file, here:
    https://git.gnome.org/browse/metacity/tree/NEWS?h=3.18.5

  [Impact]
  When using drag-and-drop, the temporary windows are unmapped but never 
destroyed. This makes the compositor still draw them, which leads to unwanted 
artifacts on desktop.

  [Test Case]
  * Try dragging a bookmark from nautilus window to desktop;
  * There should be no artifacts remaining on the desktop.

  [Regression Potential]
  The fix is adding two lines and should not cause any regressions.

  -

  I'm using metacity in 16.04.

  Having opened nautilus with some folders on the left area (with favorite 
locations) if a accidentaly drag one location a permanent rectangular area with
  the name of that folder will remain on desktop in that location that the drop 
was 'made' and sits on top of every windwos sth very annoyning.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1592953/+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 1569400] Re: mk-sbuild fails with cp: /etc/localtime... are the same file

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-dev-tools - 0.155ubuntu2

---
ubuntu-dev-tools (0.155ubuntu2) xenial; urgency=medium

  * mk-sbuild: fix failure to copy /etc/localtime into the target
chroot.  LP: #1569400.

 -- Steve Langasek   Fri, 01 Jul 2016
12:21:58 -0700

** Changed in: ubuntu-dev-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/1569400

Title:
  mk-sbuild fails with cp: /etc/localtime... are the same file

Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools source package in Xenial:
  Fix Released

Bug description:
  [SRU Justification]
  The mk-sbuild command fails to completely set up its schroot environment if 
/etc/localtime is a symlink to the default timezone file (Etc/UTC), due to 
wrong 'cp' options.  This makes the tool unusable in xenial on systems with a 
default config.  It also causes the tool to do the wrong thing on systems with 
a user-configured timezone, as the Etc/UTC file within the chroot environment 
will be overwritten by the host system's zone file, rather than changing the 
*target* of the /etc/localtime symlink.

  [Test case]
  1. Verify that /etc/localtime is a symlink to /usr/share/zoneinfo/Etc/UTC on 
your system.
  2. Install ubuntu-dev-tools.
  3. Run 'mk-sbuild yakkety'.  When prompted to edit ~/.sbuildrc, you can 
accept the defaults.
  4. Run 'sg sbuild' to make sure you are in the 'sbuild' group in case this is 
newly added.
  5. Run 'mk-sbuild yakkety' again.  Verify that the command output ends with 
the line:
  cp: '/etc/localtime' and 
'/var/lib/schroot/chroots/yakkety-amd64/etc/localtime' are the same file.
  6. Run 'echo $?' to verify that the return value of mk-sbuild is 1.
  7. Install ubuntu-dev-tools from xenial-proposed.
  8. Run 'sudo rm -rf /var/lib/schroot/chroots/yakkety-amd64' to remove the 
incompletely-bootstrapped directory from the previous attempt.
  9. Run 'mk-sbuild yakkety' again.  Confirm that the command exits 0.
  10. Confirm that 'schroot -l' shows the yakkety-amd64 chroot.

  [Regression potential]
  Minimal.  We don't want to dereference /etc/localtime when copying it into 
the target environment; this never DTRT and often fails altogether. The fix for 
this is small and targeted.

  
  On my system, /etc/localtime points to Etc/UTC. When I run mk-sbuild, it 
fails as follows:

  I: Base system installed successfully.
  cp: '/etc/localtime' and 
'/var/lib/schroot/chroots/xenial-amd64/etc/localtime' are the same file
  rbasak@diglett:~$ stat /etc/localtime
    File: '/etc/localtime' -> '/usr/share/zoneinfo/Etc/UTC'
    Size: 27  Blocks: 0  IO Block: 4096   symbolic link
  Device: fa00h/64000dInode: 24904635Links: 1
  Access: (0777/lrwxrwxrwx)  Uid: (0/root)   Gid: (0/root)
  Access: 2016-04-12 14:34:01.913544692 +
  Modify: 2016-04-09 14:16:56.0 +
  Change: 2016-04-11 14:33:38.788003973 +
   Birth: -
  rbasak@diglett:~$ stat /var/lib/schroot/chroots/xenial-amd64/etc/localtime
    File: '/var/lib/schroot/chroots/xenial-amd64/etc/localtime' -> 
'/usr/share/zoneinfo/Etc/UTC'
    Size: 27  Blocks: 0  IO Block: 4096   symbolic link
  Device: fa00h/64000dInode: 25958842Links: 1
  Access: (0777/lrwxrwxrwx)  Uid: (0/root)   Gid: (0/root)
  Access: 2016-04-12 14:39:39.042359630 +
  Modify: 2016-04-12 14:39:39.038359620 +
  Change: 2016-04-12 14:39:39.038359620 +
   Birth: -
  rbasak@diglett:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-dev-tools 0.155 [modified: usr/bin/mk-sbuild]
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Tue Apr 12 14:52:21 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this notice.
   No journal files were opened due to insufficient permissions.
  PackageArchitecture: all
  SourcePackage: ubuntu-dev-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1569400/+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 1594407] Re: [SRU] New stable release 1.8.2

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package gst-plugins-base1.0 - 1.8.2-1ubuntu0.1

---
gst-plugins-base1.0 (1.8.2-1ubuntu0.1) xenial; urgency=medium

  * No-change backport to 16.04

gst-plugins-base1.0 (1.8.2-1ubuntu1) yakkety; urgency=medium

  * Merge from Debian unstable (LP: #1594407). Remaining changes:
+ 0001-riff-Add-input-buffer-size-to-GstCaps.patch: Take patch from
  Alfonso Sanchez-Beato on upstream bug #737599 to add a field in the
  GstCaps containing the suggested buffer size for this stream.
+ Update Vcs-* for Ubuntu

gst-plugins-base1.0 (1.8.2-1) unstable; urgency=medium

  * debian/control.in:
+ Remove duplicated field name.
  * New upstream bugfix release.

 -- Iain Lane   Mon, 20 Jun 2016 17:50:06 +0100

** Changed in: gst-plugins-base1.0 (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/1594407

Title:
  [SRU] New stable release 1.8.2

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Released
Status in gstreamer-vaapi source package in Xenial:
  Fix Released
Status in gstreamer1.0 source package in Xenial:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1594407/+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 1594407] Re: [SRU] New stable release 1.8.2

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package gst-plugins-bad1.0 - 1.8.2-1ubuntu0.1

---
gst-plugins-bad1.0 (1.8.2-1ubuntu0.1) xenial; urgency=medium

  * Backport to 16.04
  * debian/build-deps.in: Revert change to OpenJPEG 2.1.

gst-plugins-bad1.0 (1.8.2-1ubuntu1) yakkety; urgency=medium

  * Merge with Debian unstable (LP: #1594407); remaining changes:
+ Stop installing camerabin2 basecamerabin jpegformat - plugins which have
moved to -good.
+ Provide gstreamer-plugins-bad-1.0.pc with Requires on
  gstreamer-plugins-good-1.0 - the package we've moved the referenced
  library to. This maintains compatibility with upstream software and
  other distributions.
+ debian/patches/adding-mirsink-and-android-media-over-hybris-support.patch:
  - Adding mirsink and Android media over hybris support, for hardware
accelerated decode using libstagefright and the hybris compat layer.
+ debian/control.in:
  - Making the hybris plugin as part of a separated package, and i386 and
armhf only (can only work with android compatible archs)
+ debian/build-deps.in:
  - Adding mirsink/android decoder specific build dependencies for i386 and
armhf (libplatform-api1-dev and libmedia-dev)
+ Split videoparsers and faad out into their own packages.
+ Disable gl and glx on armhf as it's not useful there.
+ debian/control{,.in}: Update Vcs-* for Ubuntu
+ debian/watch: Update Vcs-* for new URL scheme

gst-plugins-bad1.0 (1.8.2-1) unstable; urgency=medium

  * New upstream bugfix release.
  * debian/build-deps.in:
+ Switch from OpenJPEG 1.5 to 2.1.

gst-plugins-bad1.0 (1.8.1-2) unstable; urgency=medium

  * debian/build-deps.in:
+ Patch by Tobias Frost to fix FTBFS on Hurd (Closes: #822675).

 -- Iain Lane   Mon, 20 Jun 2016 17:49:58 +0100

** Changed in: gst-plugins-bad1.0 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: gst-plugins-good1.0 (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/1594407

Title:
  [SRU] New stable release 1.8.2

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Released
Status in gstreamer-vaapi source package in Xenial:
  Fix Released
Status in gstreamer1.0 source package in Xenial:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1594407/+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 1594118] Re: Indicator shows outdated translations

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package evolution-indicator - 0.2.20-0ubuntu23

---
evolution-indicator (0.2.20-0ubuntu23) xenial; urgency=medium

  * debian/control:
- set X-Ubuntu-Use-Langpack, the package moved to universe but we want
  to keep using the launchpad translations (lp: #1594118)

 -- Sebastien Bacher   Thu, 23 Jun 2016 10:11:12
-0400

** Changed in: evolution-indicator (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/1594118

Title:
  Indicator shows outdated translations

Status in evolution-indicator package in Ubuntu:
  Fix Released
Status in evolution-indicator source package in Xenial:
  Fix Released

Bug description:
  * Impact
  the messaging menu strings about evolution have missing outdated/missing 
translations

  * Test case
  install evolution-indicator and check that the indicator-messages string to 
e.g compose a new message is translated

  * Regression potential
  the translations are already missing so none

  -

  I've just upgraded Ubuntu and noticed that Evolution Indicator (under
  the Email symbol in the top right corner next to the time) is showing
  outdated translations for Scottish Gaelic (gd).

  This one
  
https://translations.launchpad.net/evolution-indicator/trunk/+pots/evolution-indicator/gd/7/+translate
  was fixed
   Translated and reviewed by GunChleoc on 2013-09-14
  but it's still showing

  Co-chuir Teachdaireachd Ùr
   Suggested in app-install-data in Ubuntu Xenial package 
"app-install-data-ubuntu" by alasdair caimbeul on 2011-12-17

  There may be others but I haven't checked. Is it possible that there
  is something broken about the way this module pulls its translations?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-indicator/+bug/1594118/+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 1594407] Re: [SRU] New stable release 1.8.2

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package gst-plugins-good1.0 - 1.8.2-1ubuntu0.1

---
gst-plugins-good1.0 (1.8.2-1ubuntu0.1) xenial; urgency=medium

  * No-change backport to 16.04

gst-plugins-good1.0 (1.8.2-1ubuntu1) yakkety; urgency=medium

  * Merge with Debian unstable (LP: #1594407); remaining changes:
+ Import plugins from -bad that are needed for main applications.
  - jpegformat
  - camerabin2 (+ basecamerabinsrc + photography)
+ Break and Replace -bad versions which contained these plugins.
+ Add a library package containing the shared library and a -dev package for
  compiling against it. Add Breaks and Replaces against the plugins packages
  which formerly contained files shipped here.
+ Add 'pluginsdir' variable to our added pcfile for compatibility with
  some external software
+ debian/control{,.in}: Update Vcs-* for Ubuntu

gst-plugins-good1.0 (1.8.2-1) unstable; urgency=medium

  * New upstream bugfix release.

 -- Iain Lane   Mon, 20 Jun 2016 17:50:12 +0100

** Changed in: gst-plugins-ugly1.0 (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/1594407

Title:
  [SRU] New stable release 1.8.2

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Released
Status in gstreamer-vaapi source package in Xenial:
  Fix Released
Status in gstreamer1.0 source package in Xenial:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1594407/+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 1594407] Re: [SRU] New stable release 1.8.2

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package gst-plugins-ugly1.0 - 1.8.2-1ubuntu0.1

---
gst-plugins-ugly1.0 (1.8.2-1ubuntu0.1) xenial; urgency=medium

  * No-change backport to 16.04

gst-plugins-ugly1.0 (1.8.2-1ubuntu1) yakkety; urgency=medium

  * Merge with Debian unstable (LP: #1594407). Remaining changes:
+ Split AMR out into a gstreamer1.0-plugins-ugly-amr package.
+ Run dh_install with --fail-missing to error out if files aren't
  installed.
+ debian/control{,.in}: Update Vcs-* for Ubuntu

gst-plugins-ugly1.0 (1.8.2-1) unstable; urgency=medium

  * New upstream bugfix release.

 -- Iain Lane   Mon, 20 Jun 2016 17:50:19 +0100

** Changed in: gstreamer-vaapi (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/1594407

Title:
  [SRU] New stable release 1.8.2

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Released
Status in gstreamer-vaapi source package in Xenial:
  Fix Released
Status in gstreamer1.0 source package in Xenial:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1594407/+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 1594407] Re: [SRU] New stable release 1.8.2

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package gst-libav1.0 - 1.8.2-1~ubuntu1

---
gst-libav1.0 (1.8.2-1~ubuntu1) xenial; urgency=medium

  * No-change backport from Yakkety to 16.04 for stable update. (LP:
#1594407)

gst-libav1.0 (1.8.2-1) unstable; urgency=medium

  * New upstream bugfix release.

gst-libav1.0 (1.8.1-1) unstable; urgency=medium

  * New upstream bugfix release.

 -- Iain Lane   Wed, 22 Jun 2016 11:06:22 +0100

** Changed in: gst-libav1.0 (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/1594407

Title:
  [SRU] New stable release 1.8.2

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Released
Status in gstreamer-vaapi source package in Xenial:
  Fix Released
Status in gstreamer1.0 source package in Xenial:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1594407/+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 1594407] Re: [SRU] New stable release 1.8.2

2016-07-18 Thread Launchpad Bug Tracker

This bug was fixed in the package gstreamer-vaapi - 1.8.2-1~ubuntu2

---
gstreamer-vaapi (1.8.2-1~ubuntu2) xenial; urgency=medium

  * Rebuild against gstreamer 1.8.2 (LP: #1594407)

 -- Iain Lane   Tue, 28 Jun 2016 09:12:21
+0100

** Changed in: gstreamer1.0 (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/1594407

Title:
  [SRU] New stable release 1.8.2

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Released
Status in gstreamer-vaapi source package in Xenial:
  Fix Released
Status in gstreamer1.0 source package in Xenial:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1594407/+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

88 matches

Mail list logo