from:"Chris J Arges"

[Group.of.nepali.translators] [Bug 1870514] Re: update containerd:amd64 1.3.3-0 stops docker daemon

2020-12-01 Thread Chris J Arges

** Also affects: containerd (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/1870514

Title:
  update containerd:amd64 1.3.3-0 stops docker daemon

Status in containerd package in Ubuntu:
  Confirmed
Status in containerd source package in Xenial:
  New
Status in containerd source package in Bionic:
  Confirmed

Bug description:
  hello we have had in several vms, the problem that after updating to "
  containerd:amd64 1.3.3" the docker daemon is stopped and so are all
  running containers

  the vms run with ubuntu 18.04.1/18.04.2

  journal log during the update:

  ```
  -- Logs begin at Tue 2020-01-14 09:58:27 CET, end at Fri 2020-04-03 11:30:39 
CEST. --
  Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00" 
level=info msg="level=info ts=2020-04-03T04:09:09.648358396Z caller=loki.go:55 
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f 
msg=\"ignoring empty line\" line=" 
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
  Apr 03 06:09:09 server dockerd[1751]: time="2020-04-03T06:09:09+02:00" 
level=info msg="level=info ts=2020-04-03T04:09:09.660781933Z caller=loki.go:55 
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f 
msg=\"ignoring empty line\" line=\"\"" 
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
  Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03 
06:09:14+02:00","message":"interface enp0s3 works fine"}
  Apr 03 06:09:14 server interface_rules[1485]: {"time":"2020-04-03 
06:09:14+02:00","message":"interface enp0s8 works fine"}
  Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00" 
level=info msg="level=info ts=2020-04-03T04:09:24.650166885Z caller=loki.go:55 
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f 
msg=\"ignoring empty line\" line=" 
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
  Apr 03 06:09:24 server dockerd[1751]: time="2020-04-03T06:09:24+02:00" 
level=info msg="level=info ts=2020-04-03T04:09:24.663239678Z caller=loki.go:55 
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f 
msg=\"ignoring empty line\" line=\"\"" 
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
  Apr 03 06:09:31 server systemd[1]: Starting Daily apt upgrade and clean 
activities...
  Apr 03 06:09:39 server dockerd[1751]: time="2020-04-03T06:09:39+02:00" 
level=info msg="level=info ts=2020-04-03T04:09:39.64981528Z caller=loki.go:55 
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f 
msg=\"ignoring empty line\" line=" 
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
  Apr 03 06:09:39 server dockerd[1751]: time="2020-04-03T06:09:39+02:00" 
level=info msg="level=info ts=2020-04-03T04:09:39.665086076Z caller=loki.go:55 
container_id=1eefb971e84cdaa4eadb0ac890fe9adf5275a4e9cbcf9635cf941b3aa469dd1f 
msg=\"ignoring empty line\" line=\"\"" 
plugin=255e05f2d4535991812f30e4cb5ea39fe0b498ca612c26dd89909de318b7f68d
  Apr 03 06:09:43 server systemd[1]: Stopping Docker Application Container 
Engine...
  Apr 03 06:09:43 server dockerd[1751]: 
time="2020-04-03T06:09:43.571408106+02:00" level=info msg="Processing signal 
'terminated'"
  Apr 03 06:09:43 server dockerd[1751]: 
time="2020-04-03T06:09:43.614841270+02:00" level=info msg="Daemon shutdown 
complete"
  Apr 03 06:09:43 server dockerd[1751]: 
time="2020-04-03T06:09:43.614972021+02:00" level=info msg="stopping event 
stream following graceful shutdown" error="context canceled" 
module=libcontainerd namespace=moby
  Apr 03 06:09:43 server systemd[1]: Stopped Docker Application Container 
Engine.
  Apr 03 06:09:43 server systemd[1]: Stopping containerd container runtime...
  Apr 03 06:09:43 server systemd[1]: Closed Docker Socket for the API.
  Apr 03 06:09:43 server containerd[1736]: 
time="2020-04-03T06:09:43.896546147+02:00" level=info msg="Stop CRI service"
  Apr 03 06:09:43 server containerd[1736]: 
time="2020-04-03T06:09:43.897819071+02:00" level=info msg="Stop CRI service"
  Apr 03 06:09:43 server containerd[1736]: 
time="2020-04-03T06:09:43.899864471+02:00" level=info msg="Event monitor 
stopped"
  Apr 03 06:09:43 server containerd[1736]: 
time="2020-04-03T06:09:43.900291027+02:00" level=info msg="Stream server 
stopped"
  Apr 03 06:09:43 server systemd[1]: Stopped containerd container runtime.
  Apr 03 06:09:47 server systemd[1]: Reloading.
  Apr 03 06:09:48 server systemd[1]: Reloading.
  Apr 03 06:09:49 server systemd[1]: Reloading.
  Apr 03 06:09:49 server systemd[1]: Starting containerd container runtime...
  Apr 03 06:09:49 server containerd[1904]: 
time="2020-04-03T06:09:49.951538613+02:00" level=info msg="starting

[Group.of.nepali.translators] [Bug 1758963] Re: Please don't ship empty directories in the source package

2018-03-28 Thread Chris J Arges

** Also affects: update-manager (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/1758963

Title:
  Please don't ship empty directories in the source package

Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  New

Bug description:
  [Impact]

  Empty directories can't be stored in Git, which is a very popular
  version control system for maintaining source packages.

  Keeping the empty directory in the source package prevent others from
  easily contributing to the package by importing it in full to a local
  repository, making changes, then generating an updated source package
  with tools like git-buildpackage. In that workflow the empty directory
  would be lost potentially causing errors if the installed binary
  package relied on it or causing autopkgtest failures if tests used it.

  The backport to a stable release helps further maintenance of the
  package in git-based workflows and avoids accidentally breaking
  autopkgtests when the existence of the empty dirs matter.

  The upload may drop the empty dirs or place placeholder (e.g.:
  */.keep) files  in the source package.

  [Test Case]

  Extract the source package, then run the following command int the
  extracted source directory:

   find . -depth -type d -empty

  [Regression Potential]

  The removed directories or the added placeholders may cause run-time
  issues or cause autopkgtest failures. To prevent those please check
  that the placeholder files are not shipped in the binary packages and
  also run autokgtests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1758963/+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 1746666] Re: lspci fails with 'Error reading sysfs label: Operation not permitted'

2018-03-13 Thread Chris J Arges

I can reproduce this on a local xenial machine.
The artful/bionic packages do not have this problem.

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

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

Title:
  lspci fails with 'Error reading sysfs label: Operation not permitted'

Status in dellserver:
  New
Status in pciutils package in Ubuntu:
  Fix Released
Status in pciutils source package in Xenial:
  Confirmed

Bug description:
  Description:
  On a 4 socket server, when #lspci is run, it fails with output:
  lspci: Error reading /sys/bus/pci/devices/:9a:00.0/label: Operation not 
permitted

  How Reproducible:
  Always

  Version
  pciutils-3.3.1-1.1ubuntu1.1

  Steps:
  1. Install Ubuntu-Server-16.04.3
  2. Observe #lspci

  Additional Info:
  * Upstream master branch from pciutils works fine in this setup. 
(https://kernel.googlesource.com/pub/scm/utils/pciutils/pciutils/)

  * v3.4.0 also works fine in this setup.

  * v3.3.1 fails.

  * Going through code quickly, looks like one of the required patches is :
  
https://kernel.googlesource.com/pub/scm/utils/pciutils/pciutils/+/ef6c9ec3a45992d9e7ef4716d444252baf2013e1

  Not sure what other patches might be required for fixing this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/174/+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 1746666] Re: lspci fails with 'Error reading sysfs label: Operation not permitted'

2018-03-13 Thread Chris J Arges

** Also affects: pciutils (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/174

Title:
  lspci fails with 'Error reading sysfs label: Operation not permitted'

Status in dellserver:
  New
Status in pciutils package in Ubuntu:
  Fix Released
Status in pciutils source package in Xenial:
  Confirmed

Bug description:
  Description:
  On a 4 socket server, when #lspci is run, it fails with output:
  lspci: Error reading /sys/bus/pci/devices/:9a:00.0/label: Operation not 
permitted

  How Reproducible:
  Always

  Version
  pciutils-3.3.1-1.1ubuntu1.1

  Steps:
  1. Install Ubuntu-Server-16.04.3
  2. Observe #lspci

  Additional Info:
  * Upstream master branch from pciutils works fine in this setup. 
(https://kernel.googlesource.com/pub/scm/utils/pciutils/pciutils/)

  * v3.4.0 also works fine in this setup.

  * v3.3.1 fails.

  * Going through code quickly, looks like one of the required patches is :
  
https://kernel.googlesource.com/pub/scm/utils/pciutils/pciutils/+/ef6c9ec3a45992d9e7ef4716d444252baf2013e1

  Not sure what other patches might be required for fixing this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/174/+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 1729389] Re: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react

2018-01-24 Thread Chris J Arges

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

Title:
  [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then
  don't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Confirmed
Status in linux-firmware source package in Artful:
  Fix Released

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN ISCAN INQUIRY
    RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
    TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+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 1717040] Re: Please backport libzstd 1.3.1+dfsg-1 (universe) from artful

2018-01-24 Thread Chris J Arges

** Also affects: libzstd (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Andreas Hasenack (ahasenack)
   Status: 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/1717040

Title:
  Please backport libzstd 1.3.1+dfsg-1 (universe) from artful

Status in libzstd package in Ubuntu:
  In Progress
Status in libzstd source package in Xenial:
  In Progress
Status in libzstd source package in Zesty:
  Won't Fix
Status in libzstd source package in Artful:
  In Progress
Status in libzstd source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * libzstd v0.5.1 is an experimental version,
     which generates and read an experimental format
     incompatible with official libzstd v1+ format.

   * Backporting a newer version >= v1.0, such as artful's v1.3.1,
     fixes this issue

   * This backport/SRU is being requested by upstream.

  [Test Case]

   * with the pristine package from each release, compress a big file.
  For example, /usr/bin/snap. Name the resulting compressed file
  according to the version that was used to compress it, like this:

  Xenial:
  $ zstd /usr/bin/snap -o snap.0.5.1.zst
  Compressed 15528016 bytes into 4134889 bytes ==> 26.63%

  Zesty:
  $ zstd /usr/bin/snap -o snap.1.1.2.zst
  /usr/bin/snap: 30.59%   (10825608 => 3311295 bytes, snap.1.1.2.zst)

   * Upgrade to the package made available through this SRU and compress
  it again:

  Xenial:
  $ zstd /usr/bin/snap -o snap.1.3.1.zst
  /usr/bin/snap: 25.11%   (15528016 => 3899137 bytes, snap.1.3.1.zst)

  Zesty:
  $ zstd /usr/bin/snap -o snap.1.3.1.zst
  /usr/bin/snap: 30.59%   (10825608 => 3311290 bytes, snap.1.3.1.zst)

  * Uncompress all the generated files using the new version. This
  proves it can handle files compressed by the old one:

  Xenial:
  $ zstd -d snap.0.5.1.zst -o snap.0.5.1
  snap.0.5.1.zst  : 15528016 bytes
  $ zstd -d snap.1.3.1.zst -o snap.1.3.1
  snap.1.3.1.zst  : 15528016 bytes

  Zesty:
  $ zstd -d snap.1.1.2.zst -o snap.1.1.2
  snap.1.1.2.zst  : 10825608 bytes
  $ zstd -d snap.1.3.1.zst -o snap.1.3.1
  snap.1.3.1.zst  : 10825608 bytes

   * Take md5sums of all uncompressed files and the original. They must
  of course match:

  Xenial:
  $ md5sum /usr/bin/snap snap.0.5.1 snap.1.3.1
  0fa4fa69d79ef4685aaa93be5b3aa33f  /usr/bin/snap
  0fa4fa69d79ef4685aaa93be5b3aa33f  snap.0.5.1
  0fa4fa69d79ef4685aaa93be5b3aa33f  snap.1.3.1

  Zesty:
  $ md5sum /usr/bin/snap snap.1.1.2 snap.1.3.1
  ba0a3ef5f519688bc5b0b58f190e73a4  /usr/bin/snap
  ba0a3ef5f519688bc5b0b58f190e73a4  snap.1.1.2
  ba0a3ef5f519688bc5b0b58f190e73a4  snap.1.3.1

  * Downgrade zstd back to the original version of the ubuntu release
  you are testing:

  Xenial:
  $ sudo apt install zstd=0.5.1-1

  Zesty:
  $ sudo apt install zstd=1.1.2-1 libzstd1=1.1.2-1

  * Try to decompress the zst file created with the 1.3.1 version from the 
previous test. In xenial only, it should fail to recognize the format:
  $ zstd -d snap.1.3.1.zst -o /dev/null
  zstd: /dev/null already exists; do you wish to overwrite (y/N) ? y
  zstd: snap.1.3.1.zst: not in zstd format

  In zesty it should work:
  $ zstd -d snap.1.3.1.zst -o snap.1.3.1-new
  snap.1.3.1.zst  : 9909192 bytes

  * Still in zesty, compare the md5, which should match:
  $ md5sum snap.1.3.1-new /usr/bin/snap
  7c980688861eef598a56c7970d952028  snap.1.3.1-new
  7c980688861eef598a56c7970d952028  /usr/bin/snap

  [Regression Potential]

   * During transition, if some user switches to newer zstd version, and
  then send compressed data to another user has not yet updated zstd,
  the receiver will not be able to decompress as long as he does not
  update.

   * Note though that newer version contains a compatibility module
  which makes it able to read data generated by older versions, such as
  v0.5.1. Any existing document compressed with v0.5.1 will still be
  readable after update to v1.3.1.

  [Other Info]

   * Linux kernel 4.14 now integrates zstd compression / decompression,
  primarily for BtrFS and SquashFS, with patches available for reiser4,
  zram, and initrd. Kernel version does not support compatibility
  module, hence cannot read data from v0.5.1. Userland tools associated
  with these services will fail if they link to Ubuntu LTS libzstd, as
  generating incompatible data.

   * On top of the incompatible format issue, libzstd v0.5.1 API is old
  and missing several features that applications relying on libzstd
  need, such as streaming interface, or bulk processing for dictionary
  compression.

  --- Original description ---

  Please backport libzstd 1.3.1+dfsg-1 (universe) from artful to xenial.

  Reason for the backport:
  
  Current version in Xenial is v0.5.1,
  it's an experimental version, using its own, incompatible format.
  As a

[Group.of.nepali.translators] [Bug 1702724] Re: Doesn't auto open update-manager as it should

2018-01-17 Thread Chris J Arges

Hello Sebastien, or anyone else affected,

Accepted update-notifier into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/update-
notifier/3.168.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: update-notifier (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: update-notifier (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  Doesn't auto open update-manager as it should

Status in update-notifier package in Ubuntu:
  Fix Released
Status in update-notifier source package in Xenial:
  Fix Committed

Bug description:
  * Impact

  Since Xenial it seems that update-manager is not presented to users as
  often as it should.

  * Test case

  Use xenial for a week, update-manager should auto open to show you
  pending updates

  * Regression potential

  The UI might be displayed more often than it used to be

  
  -

  One possible reason is that update-notifier is trying to be too smart
  about when it should open the updater and reset the counter when the
  dpkg/apt logs timestamps change. The logic behind that was to try to
  not bother command line users and don't present them the graphical UI
  if they are doing their update using apt directly. That's not very
  obvious how it's working though and not playing well with unattended-
  upgrades (security updates get installed in background, the system
  thinks it's users doing their updates manually and is never prompting
  as a result).

  The suggested fix is to just drop that smart behaviour and prompt
  users after the configured delay. Command line users who don't like
  that can just change the setting to "never"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1702724/+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 1743026] [NEW] qemu-nbd -c /dev/nbd0 fails to map partitions

2018-01-12 Thread Chris J Arges

Public bug reported:

[impact]
4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to mount 
virtual disks onto a local filesystem (see test case for reproducer). 4.4.0-98 
works without issue.

I was able to bisect the issue down to
907196aba0d891c6d580abe69c36d3b4fd512dcc (a cherry-pick from
37091fdd831f28a6509008542174ed324dd645bc). Reverting this from 4.4 fixes
the issue.

Installing the mainline kernel shows mainline is _not_ affected by this
bug.

In addition this is also reported in debian here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829532

[test case]
# given a vmdk disk with multiple partitions
sudo modprobe nbd
sudo qemu-nbd -d /dev/nbd0
sudo qemu-nbd -r -c /dev/nbd0 disk.vmdk
ls /dev/nbd0*
# here you won't see multiple partition, nor be able to mount a partition 
locally

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: New

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

** Description changed:

  [impact]
  4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to 
mount virtual disks onto a local filesystem (see test case for reproducer).
  
  I was able to bisect the issue down to
- 907196aba0d891c6d580abe69c36d3b4fd512dcc. Reverting this from 4.4 fixes
+ 907196aba0d891c6d580abe69c36d3b4fd512dcc (a cherry-pick from
+ 37091fdd831f28a6509008542174ed324dd645bc). Reverting this from 4.4 fixes
  the issue.
  
  In addition this is also reported in debian here:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829532
  
  [test case]
  # given a vmdk disk with multiple partitions
  sudo modprobe nbd
  sudo qemu-nbd -d /dev/nbd0
  sudo qemu-nbd -r -c /dev/nbd0 disk.vmdk
  ls /dev/nbd0*
  # here you won't see multiple partition, nor be able to mount a partition 
locally

** Description changed:

  [impact]
- 4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to 
mount virtual disks onto a local filesystem (see test case for reproducer).
+ 4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to 
mount virtual disks onto a local filesystem (see test case for reproducer). 
4.4.0-98 works without issue.
  
  I was able to bisect the issue down to
  907196aba0d891c6d580abe69c36d3b4fd512dcc (a cherry-pick from
  37091fdd831f28a6509008542174ed324dd645bc). Reverting this from 4.4 fixes
  the issue.
+ 
+ Installing the mainline kernel shows mainline is _not_ affected by this
+ bug.
  
  In addition this is also reported in debian here:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829532
  
  [test case]
  # given a vmdk disk with multiple partitions
  sudo modprobe nbd
  sudo qemu-nbd -d /dev/nbd0
  sudo qemu-nbd -r -c /dev/nbd0 disk.vmdk
  ls /dev/nbd0*
  # here you won't see multiple partition, nor be able to mount a partition 
locally

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

Title:
  qemu-nbd -c /dev/nbd0 fails to map partitions

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

Bug description:
  [impact]
  4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to 
mount virtual disks onto a local filesystem (see test case for reproducer). 
4.4.0-98 works without issue.

  I was able to bisect the issue down to
  907196aba0d891c6d580abe69c36d3b4fd512dcc (a cherry-pick from
  37091fdd831f28a6509008542174ed324dd645bc). Reverting this from 4.4
  fixes the issue.

  Installing the mainline kernel shows mainline is _not_ affected by
  this bug.

  In addition this is also reported in debian here:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829532

  [test case]
  # given a vmdk disk with multiple partitions
  sudo modprobe nbd
  sudo qemu-nbd -d /dev/nbd0
  sudo qemu-nbd -r -c /dev/nbd0 disk.vmdk
  ls /dev/nbd0*
  # here you won't see multiple partition, nor be able to mount a partition 
locally

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743026/+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 1724867] Re: langford 0.0.20130228-5 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

2017-11-08 Thread Chris J Arges

Hello Seth, or anyone else affected,

Accepted langford into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/langford/0.0.20130228-5ubuntu1~16.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

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

** Tags added: verification-needed verification-needed-xenial

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

Title:
  langford 0.0.20130228-5 ADT test failure with linux-hwe-edge
  4.13.0-16.19~16.04.3

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

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/langford/20171018_120558_d9a48@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/l/langford/20171018_121613_d9a48@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/langford/20171018_121338_d9a48@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/langford/20171018_120515_d9a48@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/langford/+bug/1724867/+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 1565060] Re: defaults file is ignored

2017-11-08 Thread Chris J Arges

Hello ben, or anyone else affected,

Accepted bind9 into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bind9/1:9.10.3.dfsg.P4-10.1ubuntu5.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: bind9 (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

** Tags added: verification-needed verification-needed-zesty

** Changed in: bind9 (Ubuntu Xenial)
   Status: In Progress => 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/1565060

Title:
  defaults file is ignored

Status in bind9 package in Ubuntu:
  Fix Released
Status in bind9 source package in Xenial:
  Fix Committed
Status in bind9 source package in Yakkety:
  Won't Fix
Status in bind9 source package in Zesty:
  Fix Committed
Status in bind9 package in Debian:
  Fix Committed

Bug description:
  [Impact]

  Server start up options set in /etc/default/bind9 via the OPTIONS
  variable are ignored.

  The fix is to have the systemd service file source that file and use
  the given OPTIONS value. This is already being done in Ubuntu Artful
  and higher. The fix here is the same.

  [Test Case]

  # install bind9
  $ sudo apt install bind9

  # start it up
  $ sudo service bind9 start

  # inspect the command line of the process:
  $ ps fxaw|grep named|grep -v grep
396 ?Ssl0:00 /usr/sbin/named -f -u bind

  # edit /etc/default/bind9 and include "-4" to the OPTIONS value so it looks 
like this:
  # startup options for the server
  OPTIONS="-4 -u bind"

  # restart bind9
  sudo service bind9 restart

  # inspect the process command line again. Only the fixed version of the 
package will include the newly added "-4" parameter:
  $ ps fxaw|grep named|grep -v grep
  17891 ?Ssl0:00 /usr/sbin/named -f -4 -u bind

  
  [Regression Potential] 
  Administrators who have for some reason altered the defaults file with an 
incorrect value for OPTIONS might be surprised after this update, since now 
that file is actually parsed and if it's indeed incorrect, the service may fail 
to start.

  [Other Info]
  None at this time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1565060/+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 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

2017-10-25 Thread Chris J Arges

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

** Also affects: cloud-init (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/1711760

Title:
[2.3] resolv.conf is not set (during commissioning or testing)

Status in MAAS:
Fix Committed
Status in cloud-init package in Ubuntu:
Confirmed
Status in resolvconf package in Ubuntu:
In Progress
Status in cloud-init source package in Xenial:
New
Status in resolvconf source package in Xenial:
New

Bug description:
=== Begin SRU Template ===
[Impact]
Without this fix applied, dns settings provided to the dhcp response
in the initramfs are not reflected in the "real root".

Thus dns resolution does not work. Of most interest was the MAAS use
case of the 'root=http://<>/squashfs' use case. MAAS 2.3 uses this for
the installation environment and also the rescue environment.

[Test Case]
There are two tests for this.

a.) local/non-MAAS test
Download the test case attached.
Run it and follow the instructions.
Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
without the fix there would be no data in /etc/resolv.conf. With the
fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

b.) MAAS test.
For the full maas test, you need to build a image stream for maas
with the fix included in the squashfs image and then import that
stream to maas and use the rescue environment and verify dns.
This process is beyond the scope of the SRU template, but is
described partially in

http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README

[Regression Potential]
Regression potential should be very low. There are gates in the code
to make sure that this code is inactive other than when it is explicitly
enabled.

net-interface-handler will exit without doing anything unless:
a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf
and these files have non-empty values for a variable mentioned above.
(These files are written by the initramfs code when 'ip=' is seen).

b.) this is not a container.

b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface)
if open-iscsi has written this file due to open-iscsi root, then it
will handle this functionality. resolvconf will get out of the way.

c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns'
This lowers the scope of changes in runtime to cases with where either the
new flag is seen or cloud-config-url is passed. The MAAS use case will
contain this flag.

[Other Info]

=== End SRU Template ===

Using MAAS 2.3, during commissioning (and likely in the rest of the
ephemeral environment) we have noticed that resolv.conf is not set
with the DNS server.

That said, during the commissioning process, MAAS does not send any
metadata to cloud-init to configure the network, rather, we expect the
image to boot from the network via DHCP. So, cloud-init writes:

ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback

# control-manual ens3
iface ens3 inet dhcp
broadcast 192.168.122.255
dns-nameservers 192.168.122.2
gateway 192.168.122.1
netmask 255.255.255.0

Which correctly includes the DNS server. However:

ubuntu@manual:~$ ping google.com
ping: unknown host google.com

If restart the interfacE:

ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3
ifdown: interface ens3 not configured
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/ens3/52:54:00:ea:57:31
Sending on LPF/ens3/52:54:00:ea:57:31
Sending on Socket/fallback
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354)
DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354)
DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67
(xid=0x5403eb14)
DHCPOFFER of 192.168.122.195 from 192.168.122.2
DHCPACK of 192.168.122.195 from 192.168.122.2
Restarting ntp (via systemctl): ntp.service.
bound to 192.168.122.195 -- renewal in 290 seconds.

ubuntu@manual:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY

[Group.of.nepali.translators] [Bug 1716357] Re: a typo in evince-previewer.desktop breaks /etc/mailcap

2017-10-04 Thread Chris J Arges

Does this also affect Artful? Looks like Zesty is also affected.

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

** Also affects: evince (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  a typo in evince-previewer.desktop breaks /etc/mailcap

Status in evince package in Ubuntu:
  Fix Committed
Status in evince source package in Xenial:
  New
Status in evince source package in Zesty:
  New

Bug description:
  * Impact
  there is an extra ";" in the mimetype list leading to a buggy mailcap entry

  * Test case:
  check if /etc/mailcap contains a line
  "; evince-previewer %s; test=test -n "$DISPLAY""

  * regression potentiel
  check that evince is correcly used when trying to open file associated to it

  -

  
  Release version: Ubuntu 16.04.3 LTS
  Package version: 3.18.2-1ubuntu4.1

  /usr/share/applications/evince-previewer.desktop comes from the evince
  package. It has an empty entry in mime types between application/x
  -ext-cb7 and application/oxps.

  ===8<===
  ...
  
MimeType=application/pdf;application/x-bzpdf;application/x-gzpdf;application/x-xzpdf;application/x-ext-pdf;application/postscript;application/x-bzpostscript;application/x-gzpostscript;image/x-eps;image/x-bzeps;image/x-gzeps;application/x-ext-ps;application/x-ext-eps;application/x-dvi;application/x-bzdvi;application/x-gzdvi;application/x-ext-dvi;image/vnd.djvu;application/x-ext-djv;application/x-ext-djvu;image/tiff;application/x-cbr;application/x-cbz;application/x-cb7;application/x-ext-cbr;application/x-ext-cbz;application/x-ext-cb7;;application/oxps;application/vnd.ms-xpsdocument;
  ...
  ===>8===

  This entry gets included in /etc/mailcap via update-mime trigger from
  the package mime-support and the result is a broken line:

  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  ; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

  Some programs that use /etc/mailcap get confused by the broken line so
  it would be nice if the typo it originates from was fixed.

  The expected result in /etc/mailcap from running update-mime:
  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1716357/+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 1562817] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_write_volume_cb() from source_set_port_cb() from pa_source_process_msg() from s

2017-08-23 Thread Chris J Arges

Hello TBS, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

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

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

** Tags added: verification-needed verification-needed-xenial

Title:
pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
source_write_volume_cb() from source_set_port_cb() from
pa_source_process_msg() from source_process_msg()

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

Bug description:
https://errors.ubuntu.com/problem/3bb5044276ea358334e8e662559a1cbd45240cd9

---

[Impact]
pulseaudio daemon crashes, interrupting sound output/input.

[Test Case]
Theoretical test case (crash does not happen for all users):
1. Find some headphones and/or microphone. Ensure you do not wear the
headphones during the test as it may be loud.
2. Set audio output/input volumes to maximum.
3. Unplug and replug the headphones/microphone.
4. Check that that pulseaudio process is still running, with a start time
older than when you began this test case.

[Regression Potential]
Low. This SRU affects the pulseaudio daemon only so the worst case would be
loss of sound output/input. The same patches have been released to
17.10 for a month already and zero regressions of the crashes have
occurred worldwide since then.

[Other Info]
Debdiff patch is attached to the most prolific bug 1539209.

[Original Description]

This error is there when i get back to the computer after a while of
no use, and at login after restart. haven't seen this error while the
system is "active"/in use.

I have been unable to provoke the error to come.

I'm not sure it is related, but when i plug in a headset, the audio volume
goes through the roof, and a loud (painfully so) scratching sound is coming
from the headset until i press Vol+. Vol- does nothing till i have pressed up
at least once.
But the bug report thing does not pop up when the sound issue is there.

Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

pulseaudio:
Installed: 1:8.0-0ubuntu2
Candidate: 1:8.0-0ubuntu2
Version table:
*** 1:8.0-0ubuntu2 500
500 http://dk.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tbs 22776 F pulseaudio
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Mar 28 12:39:45 2016
ExecutablePath: /usr/bin/pulseaudio
InstallationDate: Installed on 2016-01-14 (73 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
Signal: 6
SourcePackage: pulseaudio
StacktraceTop:
pa_alsa_path_set_volume () from /usr/lib/pulse-8.0/modules/libalsa-util.so
?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
pa_source_process_msg () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
UpgradeStatus: Upgraded to xenial on 2016-03-19 (8 days ago)
UserGroups: adm cdrom dialout dip lp lpadmin plugdev root sambashare sudo
vboxusers
dmi.bios.date: 09/18/2015
dmi.bios.vendor: LENOVO

[Group.of.nepali.translators] [Bug 1672171] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profil

2017-08-23 Thread Chris J Arges

Hello bikram, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

** Tags added: verification-needed verification-needed-xenial

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from profile_new_connection()
  from profile_handler() from _dbus_object_tree_dispatch_and_unlock()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Get a Bluetooth audio device capable of multiple profiles (e.g. high 
 fidelity A2DP and the lower quality headset profiles).
  2. Pair it with your machine and select the device in sound settings.
  3. Turn the Bluetooth audio device off and on again, making sure it is 
 set to active if not automatically so.
  4. Select the device in sound settings.
  5. Check that that pulseaudio process is still running, with a start 
 time older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would 
  be loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Other Info]
  Debdiff patch is attached to the most prolific bug 1539209.

  [Original Description]

  Bluetooth device keep disconnect and audio output tab is empty

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bikram14994 F pulseaudio
   /dev/snd/controlC0:  bikram14994 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: Unity:Unity7
  Date: Sun Mar 12 21:52:24 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_bluetooth_transport_set_state () from 
/usr/lib/pulse-10.0/modules/libbluez5-util.so
   ?? () from /usr/lib/pulse-10.0/modules/libbluez5-util.so
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
  Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_set_state()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0Y004V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn0Y004V:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3437
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to :

[Group.of.nepali.translators] [Bug 1690028] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from endpoint_set_configuration() from en

2017-08-23 Thread Chris J Arges

Hello errors.ubuntu.com, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

** Tags added: verification-needed verification-needed-xenial

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from
  endpoint_set_configuration() from endpoint_handler() from
  _dbus_object_tree_dispatch_and_unlock()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Get a Bluetooth audio device capable of multiple profiles (e.g. high 
 fidelity A2DP and the lower quality headset profiles).
  2. Pair it with your machine and select the device in sound settings.
  3. Turn the Bluetooth audio device off and on again, making sure it is 
 set to active if not automatically so.
  4. Select the device in sound settings.
  5. Check that that pulseaudio process is still running, with a start 
 time older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would 
  be loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Other Info]
  Debdiff patch is attached to the most prolific bug 1539209.

  [Original Description]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5a76b9eca937daf6dc05fd32a35fa50e58ccf8f5 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1690028/+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 1463424] Re: package trousers 0.3.13-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-01-29 Thread Chris J Arges

Related Debian issue, fixed in Xenial>
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767690

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

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

** No longer affects: trousers (Ubuntu Xenial)

** No longer affects: trousers (Ubuntu Yakkety)

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

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

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

Status in trousers package in Ubuntu:
  Fix Released
Status in trousers source package in Vivid:
  New

Bug description:
  I received this error when installing trousers.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: trousers 0.3.13-3
  Uname: Linux 4.1.0-040100rc4-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  AptOrdering:
   trousers: Install
   trousers: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Jun  9 08:50:57 2015
  DuplicateSignature: package:trousers:0.3.13-3:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-02-19 (109 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: trousers
  Title: package trousers 0.3.13-3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/trousers/+bug/1463424/+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 1452202] Re: ubuntu preseed install fails to set a hostname

2016-09-28 Thread Chris J Arges

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

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

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

Title:
  ubuntu preseed install fails to set a hostname

Status in netcfg:
  New
Status in netcfg package in Ubuntu:
  In Progress
Status in netcfg source package in Trusty:
  In Progress
Status in netcfg source package in Xenial:
  New

Bug description:
  [Impact]

   * DHCP hostname take precedence over netcfg/hostname, if set.

  The problem is that the system read the preseed file after having run
  netcfg, thus the preseed parameter cannot be loaded straight from the
  start.

  [Test Case]

   * HOWTO reproduce :

  Install Ubuntu using a preseed[1] file[2] and add the following line in the 
preseed recipe :
  d-i netcfg/hostname string 

  If the machine get a HOSTNAME from DHCP server or from a reverse
  lookup, netcfg/hostname doesn't take precedence.

  [1] - url=http:///
  [2] - https://help.ubuntu.com/lts/installation-guide/example-preseed.txt

  [Regression Potential]

   * none expected, the change is trivial, and has been tested severals
  time from more than one person.

  [Other Info]

   * Debian bug : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755848
     Patch has been submitted to Debian
   * There is an old patch introduced in 2012 [Use netcfg/hostname for the 
hostname if found. (Closes: #606636)] but that doesn't work as expected.
   * The submitted debdiff include a script called 56netcfg-hostname under 
finish-install.d that override the hostname if netcfg/hostname set at the end 
of the installation.

  [Original Description]

  == Comment: #0 - Edward R. Cheslek  - 2015-04-28 
18:04:01 ==
  ---Problem Description---
  An install using a preseed file fails to configure the hostname of the system 
being installed.

  Contact Information = eches...@us.ibm.com

  ---uname output---
  Ubuntu 15.04 ppc64le

  Machine Type = Tuleta pKVM guest

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   set up an automated install using a preseed file.  Grub menu entry:

  menuentry "Test" {
  linux   ubuntu-installer/ppc64el/vmlinux tasks=standard 
pkgsel/language-pack-patterns= pkgsel/install-language-support=false auto=true 
preseed/url=http://10.33.11.31/data/autoinst/ted.preseed
  initrd  ubuntu-installer/ppc64el/initrd.gz
  }

  The install will begin, and reach the hostname configuration screen,
  then stop, waiting for input.  The hostname is set in the preseed
  file, which is attached.

  Install method: http from ports.ubuntu.com

  Install disk info: n/a

  Install ISO Information: n/a

  *Additional Instructions for eches...@us.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #1 - SANDHYA VENUGOPALA  - 2015-04-29 
06:08:18 ==
  Some literature that is floating around -

  when booting from an installation CD and using a preseed file on a
  network, the installer will need answers to some questions (hostname,
  network configuration, ...) before it can load the preseed file. On
  the other hand, including a customized preseed file in a setup CD will
  allow for more automation, but requires re-mastering of the CD.

  The configuration of domain and host name, and keymap are still being
  asked, even if you have them in your preseed file as shown above. So
  if you want to kickstart the preseeded installation without a single
  questions asked, append the following more options to kernel boot
  prompt:

  console-keymaps-at/keymap=us hostname=myhost domain=example.com
  locale=en_US

  Perhaps David Heller can throw some light on this and let us know if
  its bug.

  == Comment: #2 - Edward R. Cheslek  - 2015-04-29 
07:57:29 ==
  I'm booting and installing from the network.  Even if I leave the hostname 
related options out of my preseed, it still picks up and displays the correct 
hostname from dhcp.

  == Comment: #3 - David Heller  - 2015-05-05 14:12:52 ==
  I'm not very familiar with this particular preseed option so I'm not sure how 
it's supposed to behave.  However, in a quick test on Ubuntu 15.04, adding 
"netcfg/hostname=blah" to the kernel cmdline worked: it successfully overrode 
the hostname from DHCP (the way it is usually set in my environment) with no 
other changes required.

  In the preseed however, I could not make it work, even if I commented
  out the related lines:

  #d-i netcfg/get_hostname string unassigned-hostname
  #d-i netcfg/get_domain string unassigned-domain
  d-i netcfg/hostname string blah

  And looking in the installer log, it could be a order of operations
  thing, since we

[Group.of.nepali.translators] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-09-28 Thread Chris J Arges

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

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  In Progress
Status in sysvinit source package in Xenial:
  Won't Fix
Status in zfs-linux source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been intensively tested by the upsteam zfs
  test script suite.

   * This is a upstream commit merge in 0.7.0.

   * A ubuntu package has been tested (including the upstream commit) by
  a user of the community facing this bug, and confirmed it addresses
  the problem (see comment #7).

  [Other Info]

   * Upstream commit :
  
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1607920/+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 1606960] Re: linux: 4.4.0-34.53 -proposed tracker

2016-09-21 Thread Chris J Arges

** Changed in: kernel-sru-workflow/promote-to-security
   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/1606960

Title:
  linux: 4.4.0-34.53 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-34.53 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1606960/+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 1620754] Re: hash(datetime.datetime(...)) fails with python3.5 on armhf (on an arm64 host) with a bus error

2016-09-14 Thread Chris J Arges

Hello Matthias, or anyone else affected,

Accepted python3.4 into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python3.4/3.4.3-1ubuntu1~14.04.4 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: python3.4 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: python-cryptography (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: python3.5 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: python3.4 (Ubuntu)
   Status: New => Invalid

** Changed in: python3.4 (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  hash(datetime.datetime(...)) fails with python3.5 on armhf (on an
  arm64 host) with a bus error

Status in Python:
  New
Status in python-cryptography package in Ubuntu:
  Fix Released
Status in python3.4 package in Ubuntu:
  Invalid
Status in python3.5 package in Ubuntu:
  Fix Released
Status in python-cryptography source package in Trusty:
  New
Status in python3.4 source package in Trusty:
  Fix Committed
Status in python3.5 source package in Trusty:
  New
Status in python3.5 source package in Xenial:
  New

Bug description:
  seen with
  https://launchpad.net/ubuntu/+source/python-cryptography/1.4-2/+build/10476934
  https://launchpad.net/ubuntu/+source/python-cryptography/1.5-1/+build/10678695

  the TestInvalidityDate.test_invalid_invalidity_date test is the first
  one to fail with a bus error. No reasonable traceback from gdb.

  Trying to build python3.5, python-cffi and python-cryptography with
  -mno-unaligned-access doesn't fix the issue (buildds running on a
  64bit kernel).

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/1620754/+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 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04

2016-09-07 Thread Chris J Arges

Hello Alberto, or anyone else affected,

Accepted ubuntu-drivers-common into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-drivers-common/1:0.4.17.2 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Also affects: nvidia-graphics-drivers-367 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Tags added: verification-needed

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

Title:
  SRU request: Include the 367 driver in Ubuntu 16.04

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  In Progress
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-367 source package in Xenial:
  New
Status in ubuntu-drivers-common source package in Xenial:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  The nvidia packages in Ubuntu 16.04 do not support recent NVIDIA GPUs.

  The new driver also requires changes in ubuntu-drivers-common, as gpu-
  manager needs to be able to unload the nvidia-drm module in order to
  power down the dGPU in hybrid systems.

  
  [Test Case]
  1) Enable the xenial-proposed repository, and install the nvidia-367 package

  2) Restart and see if the system boots correctly. If unsure, please
  attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log

  [Regression Potential]
  Low, the packages are already in Yakkety.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+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 1620779] Re: update jtreg in 16.04 LTS to the version required by openjdk-9

2016-09-07 Thread Chris J Arges

** Also affects: jtreg (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/1620779

Title:
  update jtreg in 16.04 LTS to the version required by openjdk-9

Status in jtreg package in Ubuntu:
  New
Status in jtreg source package in Xenial:
  New

Bug description:
  update jtreg in 16.04 LTS to the version required by openjdk-9.
  Starting with recent openjdk-9 snapshot, openjdk-9 expects jtreg
  version 4.2-b03 for running the tests.  Proposing to update xenial to
  this new upstream version.

  jtreg is only used for opendjk, and the openjdk-8 tests still run with
  the new jtreg version.

  acceptance criteria: jtreg builds, and a (PPA) build for openjdk-8
  succeeds as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jtreg/+bug/1620779/+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 1612684] Re: dies when run in a place that is not inside the snap chroot

2016-08-31 Thread Chris J Arges

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

Title:
  dies when run in a place that is not inside the snap chroot

Status in Snappy Launcher:
  Fix Released
Status in snap-confine package in Ubuntu:
  Fix Released
Status in snap-confine source package in Xenial:
  Fix Committed

Bug description:
  When running any snap from a place that is not inside the snap chroot
  (like /tmp/some-subdir or /srv) running the snap-confine launcher dies
  with a ugly error.

  TEST CASE:
  1. mkdir /tmp/99
  2. cd /tmp/99
  3. sudo snap install hello-world
  4. verify that it shows: "cannot remain in /tmp/99, please run this snap from 
another location. errmsg: No such file or directory"
  5. install snap-confine from xenial-proposed
  6. verify that hello-world runs now (and shows a message that it switches to 
/tmp)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-confine/+bug/1612684/+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 1600452] Re: "Failed to set variable: (2) Invalid Parameter" when enrolling MOK

2016-08-25 Thread Chris J Arges

Here's the pull request:
https://github.com/rhinstaller/shim/pull/60

Once this is merged we can then backport this into Yakkety/Xenial or any
other affected versions.

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

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

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

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

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

Title:
  "Failed to set variable: (2) Invalid Parameter" when enrolling MOK

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

Bug description:
  ## Testing Environment:
  Lenovo Thinkpad P50, fresh install of Ubuntu 16.04

  $ apt-cache policy mokutil
  mokutil:
Installed: 0.3.0-0ubuntu3
Candidate: 0.3.0-0ubuntu3
Version table:
   *** 0.3.0-0ubuntu3 500
  500 http://cn.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy shim
  shim:
Installed: 0.8-0ubuntu2
Candidate: 0.8-0ubuntu2
Version table:
   *** 0.8-0ubuntu2 500
  500 http://cn.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status


  ## Steps to reproduce:
  (1) do not disable SecureBoot as suggested during the install.

  (2) install virtualbox-5.0 from the virtualbox ppa (deb
  http://download.virtualbox.org/virtualbox/debian xenial contrib)

  (3) Follow instructions here to manually sign the vboxdrv kernel
  module (https://askubuntu.com/questions/760671/could-not-load-vboxdrv-
  after-upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur/768310#768310)

  $ openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform
  DER -out MOK.der -nodes -days 36500 -subj "/CN=Descriptive name/"

  $ sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256
  ./MOK.priv ./MOK.der $(modinfo -n vboxdrv)

  $ sudo mokutil --import MOK.der

  (enter password)

  (4) reboot, click "enroll mok", "continue", "yes", enter password,
  (screenshots here: https://sourceware.org/systemtap/wiki/SecureBoot)

  ## Expected behavior:

  new mok will be enrolled and I will be asked to reboot (several users
  from the original askubuntu answer indicated that these exact steps
  worked for them.

  ## Actual behaviour:

  "Error: Failed to set variable: (2) Invalid Parameter"

  ## Troubleshooting steps taken:
  - tried different passwords, and was able to eliminate that being the cause.
  - found relevant lines of code producing the error: lines 919-931 in 
https://github.com/rhinstaller/shim/blob/master/MokManager.c

  /# C code
efi_status = uefi_call_wrapper(RT->SetVariable, 5, db_name,
   _lock_guid,
   EFI_VARIABLE_NON_VOLATILE
   | EFI_VARIABLE_BOOTSERVICE_ACCESS
   | EFI_VARIABLE_APPEND_WRITE,
   MokNewSize, MokNew);
}

if (efi_status != EFI_SUCCESS) {
console_error(L"Failed to set variable", efi_status);
return efi_status;
  }
  C Code #/
  - unable to find where uefi_call_wrapper() is defined

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mokutil 0.3.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul  9 18:56:59 2016
  InstallationDate: Installed on 2016-07-08 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: mokutil
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mokutil/+bug/1600452/+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 1615380] Re: security issues on borgbackup

2016-08-24 Thread Chris J Arges

Can you confirm if everything is fixed in Yakkety first?
Thanks

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

** Also affects: borgbackup (Ubuntu)
   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/1615380

Title:
  security issues on borgbackup

Status in borgbackup package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  New
Status in borgbackup source package in Xenial:
  New
Status in virtualbox source package in Xenial:
  New

Bug description:
  as explained here, upstream is asking to SRU borgbackup because of the fixes 
below
  https://github.com/borgbackup/borg/compare/28cbf2481564%5E...f32c8858ad3f
  
https://github.com/borgbackup/borg/commit/dde18d6a7660837ce7b4f30d31960bdc74252570

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/borgbackup/+bug/1615380/+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 1613718] Re: [SRU] Juju 2.0-beta15 for Xenial

2016-08-17 Thread Chris J Arges

Hello Nicholas, or anyone else affected,

Accepted juju-core into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/juju-
core/2.0~beta15-0ubuntu1.16.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: juju-core (Ubuntu)
   Status: New => Fix Released

** Changed in: juju-core (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  [SRU] Juju 2.0-beta15 for Xenial

Status in juju-core package in Ubuntu:
  Fix Released
Status in juju-core source package in Xenial:
  Fix Committed

Bug description:
  Juju 2.0 is not quite final, as per the risks and timeline outlined in
  the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
  post-xenial release. This updates juju to the lastest 2.0 milestone
  version.

  [SRU Information]

  juju-core has a stable release exception, including for major version
  updates, https://wiki.ubuntu.com/JujuUpdates.

  [Impact]
  This update brings many critical fixes and enhancements in comparison to the 
current beta12 release.

  A full list of targeted bugs can be seen against the milestone, and
  the intervening milestones:

  https://launchpad.net/juju-core/+milestone/2.0-beta13
  https://launchpad.net/juju-core/+milestone/2.0-beta14
  https://launchpad.net/juju-core/+milestone/2.0-beta15

  [QA/Testing]
  Juju practices continuous integration and testing of the juju source tree. 
The results for this release can be seen here.

  http://reports.vapour.ws/releases/4233

  In addition, juju has adt test coverage for all supported archs,
  http://autopkgtest.ubuntu.com/packages/j/juju-core/.

  Finally, manual verification and testing of the package has been done
  per https://wiki.ubuntu.com/JujuUpdates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1613718/+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 1613718] Re: [SRU] Juju 2.0-beta15 for Xenial

2016-08-17 Thread Chris J Arges

** Also affects: juju-core (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/1613718

Title:
  [SRU] Juju 2.0-beta15 for Xenial

Status in juju-core package in Ubuntu:
  New
Status in juju-core source package in Xenial:
  New

Bug description:
  Juju 2.0 is not quite final, as per the risks and timeline outlined in
  the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
  post-xenial release. This updates juju to the lastest 2.0 milestone
  version.

  [SRU Information]

  juju-core has a stable release exception, including for major version
  updates, https://wiki.ubuntu.com/JujuUpdates.

  [Impact]
  This update brings many critical fixes and enhancements in comparison to the 
current beta12 release.

  A full list of targeted bugs can be seen against the milestone, and
  the intervening milestones:

  https://launchpad.net/juju-core/+milestone/2.0-beta13
  https://launchpad.net/juju-core/+milestone/2.0-beta14
  https://launchpad.net/juju-core/+milestone/2.0-beta15

  [QA/Testing]
  Juju practices continuous integration and testing of the juju source tree. 
The results for this release can be seen here.

  http://reports.vapour.ws/releases/4233

  In addition, juju has adt test coverage for all supported archs,
  http://autopkgtest.ubuntu.com/packages/j/juju-core/.

  Finally, manual verification and testing of the package has been done
  per https://wiki.ubuntu.com/JujuUpdates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1613718/+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 1612713] Re: Please merge debian version of golang-juju-loggo-dev

2016-08-17 Thread Chris J Arges

** Also affects: golang-juju-loggo (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/1612713

Title:
  Please merge debian version of golang-juju-loggo-dev

Status in golang-juju-loggo package in Ubuntu:
  Triaged
Status in golang-juju-loggo source package in Xenial:
  New

Bug description:
  The current package in ubuntu is old and the maintainer is no longer
  able to maintain the package. I'd like to request we replace this
  package with the debian version which is newer and has a maintainer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-juju-loggo/+bug/1612713/+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 1350523] Re: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed.

2016-08-10 Thread Chris J Arges

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

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

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

** Changed in: compiz (Ubuntu Xenial)
   Status: New => Invalid

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

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

Title:
  compiz assert failure: compiz: device.cpp:147: float
  frame_device_get_window_resolution_x(UFDevice): Assertion `status ==
  UFStatusSuccess' failed.

Status in frame:
  In Progress
Status in compiz package in Ubuntu:
  Won't Fix
Status in frame package in Ubuntu:
  Fix Released
Status in compiz source package in Xenial:
  Invalid
Status in frame source package in Xenial:
  New

Bug description:
  [Impact]

  Unity might crash on systems with touch screen or multi-gesture
  supporting touchpads.

  [Test case]

  The crash is pretty random, it happens in some cases where unity is
  locked and after a suspension. Without having to touch any input.

  [Regression Potential]

  Regression potential: fix is very safe. We're just removing asserts in
  code, returning safe values and printing errors instead.

  
  Not sure if the cause is running autopilot tests.

  ProblemType: CrashDistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.11+14.10.20140707-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  .tmp.unity.support.test.0:

  .tmp.unity.support.test.1:

  ApportVersion: 2.14.5-0ubuntu1
  Architecture: amd64
  AssertionMessage: compiz: device.cpp:147: float 
frame_device_get_window_resolution_x(UFDevice): Assertion `status == 
UFStatusSuccess' failed.
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Jul 30 21:46:07 2014
  DistUpgraded: 2014-05-04 22:52:42,676 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: NVIDIA Corporation Device [10de:0491]
  InstallationDate: Installed on 2014-02-13 (166 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211)
  MachineType: System manufacturer System Product Name
  ProcCmdline: compiz
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic 
root=UUID=5607f5b0-7033-4580-a503-1d178b40c2b5 ro quiet splash vt.handoff=7
  Signal: 6SourcePackage: compiz
  StacktraceTop:
   __assert_fail_base (fmt=0x7f25565248b0 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7f2539d8e36f "status == 
UFStatusSuccess", file=file@entry=0x7f2539d8e364 "device.cpp", 
line=line@entry=147, function=function@entry=0x7f2539d8e3e0 "float 
frame_device_get_window_resolution_x(UFDevice)") at assert.c:92
   __GI___assert_fail (assertion=0x7f2539d8e36f "status == UFStatusSuccess", 
file=0x7f2539d8e364 "device.cpp", line=147, function=0x7f2539d8e3e0 "float 
frame_device_get_window_resolution_x(UFDevice)") at assert.c:101
   frame_device_get_window_resolution_x () from 
/usr/lib/x86_64-linux-gnu/libframe.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6
  Title: compiz assert failure: compiz: device.cpp:147: float 
frame_device_get_window_resolution_x(UFDevice): Assertion `status == 
UFStatusSuccess' failed.
  UpgradeStatus: Upgraded to utopic on 2014-05-04 (86 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers
  dmi.bios.date: 09/13/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri:

[Group.of.nepali.translators] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-08-04 Thread Chris J Arges

** Also affects: isc-dhcp (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Dan Streetman (ddstreet)
   Status: 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/1609898

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Precise:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  In Progress

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression potential]

  None.  Non-standard (i.e. not /64) subnets served by dhcpv6 currently
  are broken, this fixes that.

  [Other info]

  This is fixed in debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+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 1600257] Re: Broken bash completion with old ppa packages present

2016-07-28 Thread Chris J Arges

** Also affects: juju-core (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/1600257

Title:
  Broken bash completion with old ppa packages present

Status in juju-core:
  Triaged
Status in juju-core package in Ubuntu:
  Fix Released
Status in juju-core source package in Xenial:
  Fix Committed

Bug description:
  I am using juju 2.0-beta11-xenial-amd64 and when I tried to tab
  complete an application name, I got a Traceback with a KeyError. I was
  trying to tab-complete "kubernetes" an application that is deployed by
  juju.

  $ juju ssh kuberTraceback (most recent call last):
File "", line 5, in 
  KeyError: 'services'

  We renamed 'services' to 'application' in 2.0 and I suspect something
  is not up to date. This also looks like a Python Traceback. If someone
  can tell me where the python code is I can take a shot at fixing this
  problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1600257/+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: 20FD0

[Group.of.nepali.translators] [Bug 1599219] Re: SRU: spl-linux: xenial: apply fix Fix do_div() types in condvar:timeout

2016-07-13 Thread Chris J Arges

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

Title:
  SRU: spl-linux: xenial: apply fix Fix do_div() types in
  condvar:timeout

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

Bug description:
  [SRU JUSTIFICATION][XENIAL]

  The do_div() macro expects unsigned types and this is detected in
  powerpc implementation of do_div(). Make whole_delta and remain_delta 
unsigned.

  [FIX]
  Upstream spl fix 2a552736b7fc2bcb810cc520abd2ff9e229a9904 ("Fix do_div() 
types in condvar:timeout"), https://github.com/zfsonlinux/spl.git

  [TEST CASE]
  Must pass zfs regression tests.

  [REGRESSION POTENTIAL]
  Minimal, this touches the spl splat test module, so it's fix to the spl tests 
rather than core spl module.

  

  spl 0.6.5.7 has the following do_div fix that should be SRU'd to spl-
  linux 0.6.5.6 for Xenial:

  [PATCH] Fix do_div() types in condvar:timeout

  The do_div() macro expects unsigned types and this is detected in
  powerpc implementation of do_div().

  Signed-off-by: Brian Behlendorf 
  Closes #516

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spl-linux/+bug/1599219/+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 1599221] Re: SRU: spl-linux: backport dep8 adt fixes from Yakkety

2016-07-13 Thread Chris J Arges

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

Title:
  SRU: spl-linux: backport dep8 adt fixes from Yakkety

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

Bug description:
  [SRU JUSTIFICATION][XENIAL]
  Since Xenial is an LTS, it makes sense to backport fixes to the adt testing 
that have landed in Yakkety in 0.6.5.7-0ubuntu4 and 0.6.5.7-0ubuntu3

  [FIX]
  Merge of adt test changes from Yakkety 0.6.5.7-0ubuntu4 and 0.6.5.7-0ubuntu3

  [REGRESSION POTENTAL]
  Will not break core spl functionality.  Any regressions in the tests will 
break the testing and not spl per se.

  ---

  Backport dep8 adt fix from Yakkety; namely:

  Add isolation-machine to tests/control
  Also restrict spl tests to 64 bit systems as that all we support for ZFS

  This is an amalgamation of two debian/tests sets of changes from
  0.6.5.7-0ubuntu4 and 0.6.5.7-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spl-linux/+bug/1599221/+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 1537793] Re: Autoupdate should be less frequent and more randomly distributed

2016-06-08 Thread Chris J Arges

Hello Bret, or anyone else affected,

Accepted snapd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/snapd/2.0.8 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

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

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

** Tags added: verification-needed

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

Title:
  Autoupdate should be less frequent and more randomly distributed

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

Bug description:
  Currently the autoupdate timer (snappy/debian/snappy-autopilot.timer)
  is set to hourly with a 15 minute accuracy.

  As snappy will be included in 16.04 desktops (millions of them), this
  rate has the potential to seriously overload the Click Package Index
  service. I suggest changing this to 3 times per day, randomly
  distributed across 24hr on a per host basis so we don't get top-of-the
  hour thundering herds.

  Further rationale is to also avoid having updates downloaded by all
  hosts within the first hour of release, since gradual/staged updates
  are not implemented for snaps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1537793/+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 1587988] Re: LDAP ping doesn't prefers site-local DCS

2016-06-01 Thread Chris J Arges

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

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

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

** Also affects: sssd (Ubuntu Yakkety)
   Importance: High
   Status: 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/1587988

Title:
  LDAP ping doesn't prefers site-local DCS

Status in sssd package in Ubuntu:
  Fix Released
Status in sssd source package in Trusty:
  New
Status in sssd source package in Wily:
  New
Status in sssd source package in Xenial:
  New
Status in sssd source package in Yakkety:
  Fix Released

Bug description:
  [Description]

  If an active directory domain has any domain controllers defined that are not 
accesible
  from a specific location, then  sssd should prefer site-local DCs in LDAP 
ping.

  This behavior has been fixed on upstream via:
  
https://git.fedorahosted.org/cgit/sssd.git/commit/?id=a1c6869c67fcf4971ac843315b97bf46893ca92d

  [Reproduction]

  
  [Possible regressions]

  * None identified

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1587988/+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 1586515] Re: kpatch-build should support flavors

2016-05-27 Thread Chris J Arges

** Also affects: kpatch (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/1586515

Title:
  kpatch-build should support flavors

Status in kpatch package in Ubuntu:
  New
Status in kpatch source package in Xenial:
  New

Bug description:
  kpatch-build should be able to make patches against any flavor of
  Ubuntu kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kpatch/+bug/1586515/+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 1585156] Re: SRU: update creduce to the final 2.5.0 release

2016-05-25 Thread Chris J Arges

Hello Matthias, or anyone else affected,

Accepted creduce into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/creduce/2.5.0-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

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

** Tags added: verification-needed

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

Title:
  SRU: update creduce to the final 2.5.0 release

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

Bug description:
  SRU: update creduce (a tool helping to reduce test cases) to the final
  2.5.0 release.  Compared to the snapshot in 16.04 LTS, the final
  release includes two bug fixes (in clang_delta). Everything else in
  the diff are cleanups, including a local patch accepted upstream.

  release summary: http://www.flux.utah.edu/listarchives/creduce-
  dev/msg00273.html

  Acceptence criteria: builds on all architectures and passes the tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/creduce/+bug/1585156/+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 1577051] Re: aa-logprof fails with unknown mode "reweive"

2016-05-20 Thread Chris J Arges

** Also affects: apparmor (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/1577051

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  New

Bug description:
  Ubuntu 16.04.

  Profiling apache tomcat.
   
  1) aa-genprof on the catalina.sh script that is used to start and stop 
tomcat. 
  2) Start and stop tomcat. 
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  
  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1577051/+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 1582374] Re: Log contains unknown mode senw

2016-05-20 Thread Chris J Arges

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

** Also affects: apparmor (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/1582374

Title:
  Log contains unknown mode senw

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Xenial:
  New

Bug description:
  Ref #1243932.  Same title but appears to be different cause.

  Ubuntu 16.04.  Error thrown on 'sudo aa-logprof'

  Python 3.5.1+: /usr/bin/python3
  Mon May 16 20:13:30 2016

  A problem occurred in a Python script.  Here is the sequence of
  function calls leading up to the error, in the order they occurred.

   /usr/sbin/aa-logprof in ()
 42 
 43 if profiledir:
 44 apparmor.profile_dir = apparmor.get_full_path(profiledir)
 45 if not os.path.isdir(apparmor.profile_dir):
 46 raise apparmor.AppArmorException("%s is not a 
directory."%profiledir)
 47 
 48 apparmor.loadincludes()
 49 
 50 apparmor.do_logprof_pass(logmark)
 51 
  apparmor = 
  apparmor.do_logprof_pass = 
  logmark = ''

   /usr/lib/python3/dist-packages/apparmor/aa.py in do_logprof_pass(logmark='', 
passno=0, pid={13215: [['unknown_hat', 13215, '/usr/sbin/apache2', 
'null-www.xx.co.uk', 'PERMITTING', 'null-www.xx.co.uk'], 
['path', 13215, 'null-complain-profile', 'null-complain-profile', 'HINT', 
'PERMITTING', {'::r', 'r'}, '/proc/13215/attr/current', '']], 13697: [['path', 
13697, 'null-complain-profile', 'null-complain-profile', 'HINT', 'PERMITTING', 
{'::a', '::w', 'a', 'w'}, '/proc/13697/attr/current', '']]})
   2184 ##repo_cfg = read_config('repository.conf')
   2185 ##if not repo_cfg['repository'].get('enabled', False) or 
repo_cfg['repository]['enabled'] not in ['yes', 'no']:
   2186 ##UI_ask_to_enable_repo()
   2187 
   2188 log_reader = apparmor.logparser.ReadLog(pid, logfile, 
existing_profiles, profile_dir, log)
   2189 log = log_reader.read_log(logmark)
   2190 #read_log(logmark)
   2191 
   2192 for root in log:
   2193 handle_children('', '', root)
  global log = [[['path', 13697, 'null-complain-profile', 
'null-complain-profile', 'HINT', 'PERMITTING', {'::a', '::w', 'a', 'w'}, 
'/proc/13697/attr/current', '']], [['unknown_hat', 13215, '/usr/sbin/apache2', 
'null-www.po4management.co.uk', 'PERMITTING', 'null-www.xx.co.uk'], 
['path', 13215, 'null-complain-profile', 'null-complain-profile', 'HINT', 
'PERMITTING', {'::r', 'r'}, '/proc/13215/attr/current', '']]]
  log_reader = 
  log_reader.read_log = >
  logmark = ''

   /usr/lib/python3/dist-packages/apparmor/logparser.py in 
read_log(self=, logmark='')
402 self.add_event_to_tree(event)
403 except AppArmorException as e:
404 ex_msg = ('%(msg)s\n\nThis error was caused by the 
log line:\n%(logline)s' %
405 {'msg': e.value, 'logline': line})
406 # when py3 only: Drop the original 
AppArmorException by passing None as the parent exception
407 raise AppArmorBug(ex_msg)  # py3-only: from None
408 
409 self.LOG.close()
410 self.logmark = ''
411 return self.log
  global AppArmorBug = 
  ex_msg = 'Log contains unknown mode senw\n\nThis error was c...otocol=6 
requested_mask="send" denied_mask="send"'
  AppArmorBug: Log contains unknown mode senw

  This error was caused by the log line:
  type=AVC msg=audit(1463403689.381:267599): apparmor="ALLOWED" 
operation="file_perm" profile="/usr/sbin/apache2//null-www.xx.co.uk" 
pid=13215 comm="apache2" laddr=:::192.168.1.100 lport=80 
faddr=:::192.168.1.100 fport=45658 family="inet6" sock_type="stream" 
protocol=6 requested_mask="send" denied_mask="send"
  __cause__ = None
  __class__ = 
  __context__ = AppArmorException('Log contains unknown mode senw',)
  __delattr__ = 
  __dict__ = {}
  __dir__ = 
  __doc__ = 'This class represents AppArmor exceptions "that should never 
happen"'
  __eq__ = 
  __format__ = 
  __ge__ = 
  __getattribute__ = 
  __gt__ = 
  __hash__ = 
  __init__ = 
  __le__ = 
  __lt__ = 
  __module__ = 'apparmor.common'
  __ne__ = 
  __new__ = 
  __reduce__ = 
  __reduce_ex__ = 
  __repr__ = 
  __setattr__ = 
  __setstate__ = 
  __sizeof__ = 
  __str__ = 
  __subclasshook__ = 
  __suppress_context__ = False
  __traceback__ = 
  __weakref__ = None
  args = ('Log contains unknown mode senw\n\nThis error was c...otocol=6 
requested_mask="send" denied_mask="send"',)
  with_traceback = 

  The above is a description of an error in

[Group.of.nepali.translators] [Bug 1583128] Re: HDF5 I/O broken with integer variables

2016-05-18 Thread Chris J Arges

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

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

Title:
  HDF5 I/O broken with integer variables

Status in octave package in Ubuntu:
  Fix Released
Status in octave source package in Wily:
  New
Status in octave source package in Xenial:
  New

Bug description:
  As described in the upstream report [1], HDF5 I/O using load/save is
  broken in 4.0.0. This is a regression with the potential for data loss
  (almost happened to us!).

  The bug is fixed upstream with [2], and I plan on asking for an SRU
  nomination.

  [Test Case]

  1. Extract the attached .tar.gz, which contains test_hdf5_save.m and
  test_hdf5_load.m from the upstream report.

  2. Run:

  2.1. On Octave 3.8:

   octave:1> test_hdf5_save
   x = 123456789

  2.2. On Octave 4.0.0:

   octave:1> test_hdf5_load
   x = 255

  3. Run (the other way around):

  3.1. On Octave 4.0.0:

   octave:2> test_hdf5_save
   x = 123456789

  3.2. Octave 3.8:

   octave:1> test_hdf5_load
   x = 21

  As you can see, in both cases the result is wrong.

  With the updated package installed (see attached debdiff), the result
  is instead

  octave:1> test_hdf5_save
  x = 123456789

  octave:1> test_hdf5_load
  x = 123456789

  in both directions (3.8 -> 4.0.0 and 4.0.0 -> 3.8), as expected.

  [Regression Potential]

  There's really no risk of any regressions. The fix is small and self
  contained, and the behavior before the fix is completely wrong and
  could result in data loss.

  [1] http://savannah.gnu.org/bugs/?45225
  [2] http://hg.savannah.gnu.org/hgweb/octave/rev/d54aa96abadf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/octave/+bug/1583128/+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 1583128] Re: HDF5 I/O broken with integer variables

2016-05-18 Thread Chris J Arges

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

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

Title:
  HDF5 I/O broken with integer variables

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

Bug description:
  As described in the upstream report [1], HDF5 I/O using load/save is
  broken in 4.0.0. This is a regression with the potential for data loss
  (almost happened to us!).

  The bug is fixed upstream with [2], and I plan on asking for an SRU
  nomination.

  [Test Case]

  1. Extract the attached .tar.gz, which contains test_hdf5_save.m and
  test_hdf5_load.m from the upstream report.

  2. Run:

  2.1. On Octave 3.8:

   octave:1> test_hdf5_save
   x = 123456789

  2.2. On Octave 4.0.0:

   octave:1> test_hdf5_load
   x = 255

  3. Run (the other way around):

  3.1. On Octave 4.0.0:

   octave:2> test_hdf5_save
   x = 123456789

  3.2. Octave 3.8:

   octave:1> test_hdf5_load
   x = 21

  As you can see, in both cases the result is wrong.

  With the updated package installed (see attached debdiff), the result
  is instead

  octave:1> test_hdf5_save
  x = 123456789

  octave:1> test_hdf5_load
  x = 123456789

  in both directions (3.8 -> 4.0.0 and 4.0.0 -> 3.8), as expected.

  [Regression Potential]

  There's really no risk of any regressions. The fix is small and self
  contained, and the behavior before the fix is completely wrong and
  could result in data loss.

  [1] http://savannah.gnu.org/bugs/?45225
  [2] http://hg.savannah.gnu.org/hgweb/octave/rev/d54aa96abadf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/octave/+bug/1583128/+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 1583128] Re: HDF5 I/O broken with integer variables

2016-05-18 Thread Chris J Arges

** Also affects: octave (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/1583128

Title:
  HDF5 I/O broken with integer variables

Status in octave package in Ubuntu:
  New
Status in octave source package in Xenial:
  New

Bug description:
  As described in the upstream report [1], HDF5 I/O using load/save is
  broken in 4.0.0. This is a regression with the potential for data loss
  (almost happened to us!).

  The bug is fixed upstream with [2], and I plan on asking for an SRU
  nomination.

  [Test Case]

  1. Extract the attached .tar.gz, which contains test_hdf5_save.m and
  test_hdf5_load.m from the upstream report.

  2. Run:

  2.1. On Octave 3.8:

   octave:1> test_hdf5_save
   x = 123456789

  2.2. On Octave 4.0.0:

   octave:1> test_hdf5_load
   x = 255

  3. Run (the other way around):

  3.1. On Octave 4.0.0:

   octave:2> test_hdf5_save
   x = 123456789

  3.2. Octave 3.8:

   octave:1> test_hdf5_load
   x = 21

  As you can see, in both cases the result is wrong.

  With the updated package installed (see attached debdiff), the result
  is instead

  octave:1> test_hdf5_save
  x = 123456789

  octave:1> test_hdf5_load
  x = 123456789

  in both directions (3.8 -> 4.0.0 and 4.0.0 -> 3.8), as expected.

  [Regression Potential]

  There's really no risk of any regressions. The fix is small and self
  contained, and the behavior before the fix is completely wrong and
  could result in data loss.

  [1] http://savannah.gnu.org/bugs/?45225
  [2] http://hg.savannah.gnu.org/hgweb/octave/rev/d54aa96abadf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/octave/+bug/1583128/+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 1573243] Re: examples tests expect the old installation message

2016-05-13 Thread Chris J Arges

Hello Leo, or anyone else affected,

Accepted snapcraft into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/snapcraft/2.8.8b in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

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

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

** Tags added: verification-needed

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

Title:
  examples tests expect the old installation message

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

Bug description:
  Snapcraft examples tests are expecting an outdated install message.

  _StringException: Traceback (most recent call last):
File 
"/home/jenkins-slave/workspace/github-snapcraft-examples-tests-cloud/examples_tests/test_webcam_webui.py",
 line 27, in test_webcam_webui
  self.install_snap(self.example_dir, snap_name, '1')
File 
"/home/jenkins-slave/workspace/github-snapcraft-examples-tests-cloud/examples_tests/__init__.py",
 line 159, in install_snap
  self.assertThat(output, MatchesRegex(expected, flags=re.DOTALL))
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 435, in 
assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: '\r[|] Prepare snap 
"/tmp/snapd-sideload-pkg-607477781"\x1b[K\r[/] Mount snap 
"webcam-webui"\x1b[K\r[-] Setup snap "webcam-webui" security 
profiles\x1b[K\r[\\] Make snap "webcam-webui" available to the 
system\x1b[K\r[|] Make snap "webcam-webui" available to the system\x1b[K\n' 
does not match /Installing webcam-webui_1_amd64.snap\n.*webcam-webui +.* +.* 
+sideload *\n.*/

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1573243/+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 1572963] Re: snapcraft upload can fail while monitoring scan status

2016-05-13 Thread Chris J Arges

Hello Vincent, or anyone else affected,

Accepted snapcraft into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/snapcraft/2.8.8b in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

** Tags added: verification-needed

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

Title:
  snapcraft upload can fail while monitoring scan status

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

Bug description:
  [Impact]

   * Spurious errors on the Ubuntu Store currently cause snap uploads to
 fail.

   * This fix will handle those spurious errors correctly.

  [Test Case]

   * snapcraft upload a snap. It should still work. Spurious errors while
 scanning the status url should not fail the upload.

  [Regression Potential]

   * None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1572963/+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 1577750] Re: Search for libraries for 16.10 cause a build failure

2016-05-13 Thread Chris J Arges

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

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

Title:
  Search for libraries for 16.10 cause a build failure

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

Bug description:
  We are missing library support for 16.10 and need a way to fail
  gracefully

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1577750/+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 1576998] Re: some unit tests are importing mock

2016-05-13 Thread Chris J Arges

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

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

Title:
  some unit tests are importing mock

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

Bug description:
  In python 3, it should be unittest.mock

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1576998/+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 1390061] Re: bash-completion tilde expansion every time

2016-05-11 Thread Chris J Arges

Hello Ove, or anyone else affected,

Accepted bash-completion into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/bash-
completion/1:2.1-4ubuntu0.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: bash-completion (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

** Also affects: bash-completion (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

Title:
  bash-completion tilde expansion every time

Status in bash-completion package in Ubuntu:
  Fix Released
Status in bash-completion source package in Trusty:
  Fix Committed
Status in bash-completion source package in Wily:
  New
Status in bash-completion source package in Xenial:
  In Progress

Bug description:
  [Impact]

  when authenticate AD, with bask-completion, it's very slow.

  [Testcase]

  Below command should output nothing.

  root@ubuntu1404:~# strace bash -c ". /etc/bash_completion; quote_readline 
'/something'; echo" 2>&1 | grep /etc/passwd
  root@ubuntu1404:~# strace bash -c ". /etc/bash_completion; quote_readline 
'/something'; echo" 2>&1 | grep sss

  but we have something

  root@ubuntu1404:~# strace bash -c ". /etc/bash_completion; quote_readline 
'/something'; echo" 2>&1 | grep /etc/passwd
  open("/etc/passwd", O_RDONLY|O_CLOEXEC) = 3
  root@ubuntu1404:~# strace bash -c ". /etc/bash_completion; quote_readline 
'/something'; echo" 2>&1 | grep sss
  open("/lib/i386-linux-gnu/libnss_sss.so.2", O_RDONLY|O_CLOEXEC) = 3
  open("/var/lib/sss/mc/passwd", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3
  connect(4, {sa_family=AF_LOCAL, sun_path="/var/lib/sss/pipes/nss"}, 110) = 0

  [Regeression Potential]

  Regression possible about
  https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1288314

  but there is no problem with ~ completion in my test

  I thested ~// ~// with no problem

  [Other Info]

  This is not from upstream, no need to fix for upstream.
  But fix code seems harmless. just specify special character ~

  // The original description

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  root@ubuntu1404:~# lsb_release -rd
  Description:Ubuntu 14.04.1 LTS
  Release:14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  root@ubuntu1404:~# apt-cache policy bash-completion
  bash-completion:
    Installed: 1:2.1-4
    Candidate: 1:2.1-4
    Version table:
   *** 1:2.1-4 0
  500 http://se.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  When I use bash-completion it should not read the /etc/passwd file or contact 
the Active directory.
  It is very hard to see this problem unless you run this on a machine with 
slow authentication... but the commands below will show if the /etc/passwd or 
sssd are used by bash_completion or not:

  root@ubuntu1404:~# strace bash -c ". /etc/bash_completion; quote_readline 
'/something'; echo" 2>&1 | grep /etc/passwd
  root@ubuntu1404:~# strace bash -c ". /etc/bash_completion; quote_readline 
'/something'; echo" 2>&1 | grep sss

  When the ~ are escaped on line 545 and 547 in /usr/share/bash-
  completion/bash_completion then bash_completion works as expected.

  4) What happened instead

  Every time you use tab-completion in bash on ubuntu 14.04 it will read
  the /etc/passwd file and if sssd are installed and configured for
  Active Directory authentication it will talk to sssd... and this can
  be slow in some environments.

  root@ubuntu1404:~# strace bash -c ". /etc/bash_completion; quote_readline 
'/something'; echo" 2>&1 | grep /etc/passwd
  open("/etc/passwd", O_RDONLY|O_CLOEXEC) = 3
  root@ubuntu1404:~# strace bash -c ". /etc/bash_completion; quote_readline 
'/something'; echo" 2>&1 | grep sss
  open("/lib/i386-linux-gnu/libnss_sss.so.2", O_RDONLY|O_CLOEXEC) = 3
  open("/var/lib/sss/mc/passwd",

[Group.of.nepali.translators] [Bug 1578661] Re: make kpatch-build kernel building match ubuntu build

2016-05-06 Thread Chris J Arges

** Also affects: kpatch (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/1578661

Title:
  make kpatch-build kernel building match ubuntu build

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

Bug description:
  [Impact]
  Currently kpatch-build uses 'make' to build the kernel; however when we build 
the ubuntu kernel we use debian/rules to do the build. By using debian/rules we 
can match all build quirks.

  [Test Case]
  Use kpatch-build to build a patch.

  [Regression Potential]
  We are using a different mechanism to build the kernel, however the 
underlying mechanisms should be similar. Testing is required to ensure this 
doesn't change the behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kpatch/+bug/1578661/+subscriptions

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

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

2016-05-04 Thread Chris J Arges

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

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

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

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

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

Bug description:
  Guys,

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

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

   PCI device example from inside a Xenial guest:

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

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

  ---
   *** How it works?

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

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

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

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

   service openvswitch-switch stop
   service dpdk stop

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

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

   service dpdk start
   service openvswitch-switch start

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

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

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

   *** Where it fails?

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

   ethtool -L ens5 combined 4

   2- Try to fire up ens4:

   ip link set dev ens4 up

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

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

  Best,
  Thiago

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

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

2016-05-04 Thread Chris J Arges

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

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

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

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

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

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1546565/+subscriptions

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

[Group.of.nepali.translators] [Bug 1573117] Re: stress-ng: clone system calls randomly fail with -EINVAL on aarch64

2016-05-04 Thread Chris J Arges

** Changed in: stress-ng (Ubuntu)
   Status: Fix Committed => Fix Released

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

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

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

Bug description:
  [SRU] Xenial

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

  [REPODUCER + FIX]
  For example, run:

  stress-ng --vm-rw 1 -v

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1573117/+subscriptions

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

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

2016-05-04 Thread Chris J Arges

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

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

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

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

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

Bug description:
  Guys,

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

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

   PCI device example from inside a Xenial guest:

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

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

  ---
   *** How it works?

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

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

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

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

   service openvswitch-switch stop
   service dpdk stop

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

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

   service dpdk start
   service openvswitch-switch start

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

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

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

   *** Where it fails?

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

   ethtool -L ens5 combined 4

   2- Try to fire up ens4:

   ip link set dev ens4 up

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

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

  Best,
  Thiago

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

[Group.of.nepali.translators] [Bug 1569249] Re: Quiesce ceph-common postinst

2016-04-28 Thread Chris J Arges

** Also affects: ceph (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/1569249

Title:
  Quiesce ceph-common postinst

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

Bug description:
  Currently there is some output from usermod during postinst, even if
  there is no change to the user:

  Setting up ceph-common (10.1.1-0ubuntu1) ...
  usermod: no changes

  So just add a "2> /dev/null" to the call to usermod like it is done
  with all the other user management calls in the postinst.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1569249/+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 1555338] Re: Linux netfilter IPT_SO_SET_REPLACE memory corruption

2016-03-10 Thread Chris J Arges

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

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

Title:
  Linux netfilter IPT_SO_SET_REPLACE memory corruption

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  New
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux source package in Wily:
  New
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in linux-lts-utopic source package in Xenial:
  Invalid

Bug description:
  [From https://code.google.com/p/google-security-
  research/issues/detail?id=758 ]

  A memory corruption vulnerability exists in the IPT_SO_SET_REPLACE
  ioctl in the netfilter code for iptables support. This ioctl is can be
  triggered by an unprivileged user on PF_INET sockets when unprivileged
  user namespaces are available (CONFIG_USER_NS=y). Android does not
  enable this option, but desktop/server distributions and Chrome OS
  will commonly enable this to allow for containers support or
  sandboxing.

  In the mark_source_chains function (net/ipv4/netfilter/ip_tables.c) it
  is possible for a user-supplied ipt_entry structure to have a large
  next_offset field. This field is not bounds checked prior to writing a
  counter value at the supplied offset:

  newpos = pos + e->next_offset;
  ...
  e = (struct ipt_entry *) (entry0 + newpos);
  e->counters.pcnt = pos;

  This means that an out of bounds 32-bit write can occur in a 64kb
  range from the allocated heap entry, with a controlled offset and a
  partially controlled write value ("pos") or zero. The attached proof-
  of-concept (netfilter_setsockopt_v3.c) triggers the corruption
  multiple times to set adjacent heap structures to zero.

  This issue affects (at least) kernel versions 3.10, 3.18 and 4.4. It
  appears that a similar codepath is accessible via
  arp_tables.c/ARPT_SO_SET_REPLACE as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555338/+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 1555338] Re: Linux netfilter IPT_SO_SET_REPLACE memory corruption

2016-03-10 Thread Chris J Arges

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

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

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

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

** Also affects: linux-lts-utopic (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  Linux netfilter IPT_SO_SET_REPLACE memory corruption

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  New
Status in linux source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  New
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux source package in Wily:
  New
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in linux-lts-utopic source package in Xenial:
  New

Bug description:
  [From https://code.google.com/p/google-security-
  research/issues/detail?id=758 ]

  A memory corruption vulnerability exists in the IPT_SO_SET_REPLACE
  ioctl in the netfilter code for iptables support. This ioctl is can be
  triggered by an unprivileged user on PF_INET sockets when unprivileged
  user namespaces are available (CONFIG_USER_NS=y). Android does not
  enable this option, but desktop/server distributions and Chrome OS
  will commonly enable this to allow for containers support or
  sandboxing.

  In the mark_source_chains function (net/ipv4/netfilter/ip_tables.c) it
  is possible for a user-supplied ipt_entry structure to have a large
  next_offset field. This field is not bounds checked prior to writing a
  counter value at the supplied offset:

  newpos = pos + e->next_offset;
  ...
  e = (struct ipt_entry *) (entry0 + newpos);
  e->counters.pcnt = pos;

  This means that an out of bounds 32-bit write can occur in a 64kb
  range from the allocated heap entry, with a controlled offset and a
  partially controlled write value ("pos") or zero. The attached proof-
  of-concept (netfilter_setsockopt_v3.c) triggers the corruption
  multiple times to set adjacent heap structures to zero.

  This issue affects (at least) kernel versions 3.10, 3.18 and 4.4. It
  appears that a similar codepath is accessible via
  arp_tables.c/ARPT_SO_SET_REPLACE as well.

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

56 matches

Mail list logo