[Group.of.nepali.translators] [Bug 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

2017-08-07 Thread Dave Chiluk 
** Also affects: bluez (Ubuntu Artful)
   Importance: Low
   Status: New

** Tags removed: sts-sponsor-chiluk

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

Title:
  Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Xenial:
  New
Status in bluez source package in Yakkety:
  Won't Fix
Status in bluez source package in Artful:
  New
Status in bluez package in Debian:
  New

Bug description:
  [Impact]

   * The package contains misleading documentation mentioning the use of
  /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for
  config file has been dropped after 14.04 release. I have directly
  received a question about it from a user mislead by the documentation.

  * Additionally deprecated -f option is still used in legacy upstart
  /etc/init/bluetooth.conf. Actually this does not seem longer required
  due to upstart being removed.

  [Test Case]

   * Install bluez.

   * Look for misleading rfcomm.conf mentions in
  /etc/init/bluetooth.conf, /usr/share/doc/bluez/README.Debian.gz

  [Regression Potential]

   * This is mostly a documentation correction, however if somebody
  still depends bluetooth started with Ubuntu 16.04+ by upstart (or
  possibly some kind of upstart compatibility in systemd, is that even
  possible?) he/she may end up with bluetooth not being started. This
  seems highly unlikely.

  [Other Info]

   * Original bug description:

  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+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 1700373] Re: intel-microcode is out of date, version 20170511 fixes errata on 6th and 7th generation platforms

2017-07-12 Thread Dave Chiluk 
I have packaged up 20170707 for testing in my ppa available

https://launchpad.net/~chiluk/+archive/ubuntu/1700373

These are versioned as

Z=3.20170511.1~ubuntu17.04.0+lp1700373
Y=3.20160714.1+lp1700373b2
X=3.20151106.1+lp1700373b2

I'd appreciate some help testing these before I push on the SRU.

I've also uploaded correctly versioned packages for x, y, z to their
appropriate queues.

** Changed in: intel-microcode (Ubuntu Zesty)
   Status: Fix Released => Confirmed

** Changed in: intel-microcode (Ubuntu Zesty)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

** Tags removed: verification-done-zesty verification-needed
** Tags added: verification-done-artful

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

Title:
  intel-microcode is out of date, version 20170511 fixes errata on 6th
  and 7th generation platforms

Status in intel-microcode package in Ubuntu:
  Fix Released
Status in intel-microcode source package in Trusty:
  Won't Fix
Status in intel-microcode source package in Xenial:
  Confirmed
Status in intel-microcode source package in Yakkety:
  Confirmed
Status in intel-microcode source package in Zesty:
  Confirmed
Status in intel-microcode source package in Artful:
  Fix Released

Bug description:
  [Impact]

  * A security fix has been made available as part of intel-microcode
  * It is advisable to apply it
  * Thus an SRU of the latest intel-microcode is desirable for all stable 
releases

  [Test Case]

  * Upgrade intel-microcode package, if it is already installed / one is
  running on Intel CPUs

  * Reboot and verify no averse results, and/or that microcode for your
  cpu was loaded as expected.

  [Test case reporting]
  * Please paste the output of:

  dpkg-query -W intel-microcode
  grep -E 'model|stepping' /proc/cpuinfo | sort -u
  journalctl -k | grep microcode

  [Regression Potential]
  Microcode are proprietary blobs, and can cause any number of new errors and 
regressions. Microcode bugs have been reported before, therefore longer than 
usual phasing and monitoring of intel-microcode bugs should be done with extra 
care.

  [Other]
  caml discussion describing test case to reproduce the crash.
  https://caml.inria.fr/mantis/view.php?id=7452

  * I did not backport the full debian/changelog, as some of the changes
  were ommitted for SRU purposes, and I don't like the idea of modifying
  the changelog of others.

  * I did not backport this below change but I feel as though the SRU team 
should evaluate including it.  I left it out due to the change as little as 
possible guidance from the SRU team.  Additionally the microcode version that 
included this change was somewhere around 20111205. More information here
  
https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00030&languageid=en-fr
 

  '''
  # 0x206c2: Intel Westmere B1 (Xeon 3600, 5600, Core i7 2nd gen).
  #
  # When Intel released a fix for Intel SA-00030, they issued a MCU that
  # bumps the minimum acceptable version of the Intel TXT ACMs in the
  # TPM persistent storage.  This permanently blacklists the vulnerable
  # ACMs *even on older microcode* in order to make it somewhat harder
  # to work around the security fix through a BIOS downgrade attack.
  #
  # It is possible that such a microcode update, when peformed by the
  # operating system, could sucessfully trigger the TPM persistent
  # storage update Intel intended to happen during firmware boot: we
  # simply don't know enough to rule it out.  Should that happen, Intel
  # TXT will be permanently disabled.  This could easily interact very
  # badly with the firmware, rendering the system unbootable.  If *that*
  # happens, it would likely require either a TPM module replacement
  # (rendering sealed data useless) or a direct flash of a new BIOS with
  # updated ACMs, to repair.
  #
  # Blacklist updates for signature 0x206c2 as a safety net.
  IUC_EXCLUDE += -s !0x206c2
  '''

  * I versioned the packages 3.20170511.1~ubuntu as I feel this
  more appropriately reflects the contents of each package rather than
  simply incrementing the ubuntu version number.

  
  =

  [Original bug report]

  NB: I am *not* directly affected by this bug.

  Henrique emailed a warning to Debian devel today [1] on a potentially
  serious issue with (sky|kaby)lake processors. Excerpt:

  "This warning advisory is relevant for users of systems with the Intel
  processors code-named "Skylake" and "Kaby Lake".  These are: the 6th and
  7th generation Intel Core processors (desktop, embedded, mobile and
  HEDT), their related server processors (such as Xeon v5 and Xeon v6), as
  well as select Intel Pentium processor models.

[Group.of.nepali.translators] [Bug 1700373] Re: intel-microcode is out of date, version 20170511 fixes errata on 6th and 7th generation platforms

2017-07-03 Thread Dave Chiluk 
I should also mention that we will be following Debian's lead and not
updating this for Trusty.  Lack of early upload being one of the big
reasons for this.

** Description changed:

  [Impact]
  
  * A security fix has been made available as part of intel-microcode
  * It is advisable to apply it
  * Thus an SRU of the latest intel-microcode is desirable for all stable 
releases
  
  [Test Case]
  
  * Upgrade intel-microcode package, if it is already installed / one is
  running on Intel CPUs
  
  * Reboot and verify no averse results, and/or that microcode for your
- cpu was loaded by expecting
+ cpu was loaded as expected.
  
  [Test case reporting]
  * Please paste the output of:
  
  dpkg-query -W intel-microcode
  grep -E 'model|stepping' /proc/cpuinfo | sort -u
  journalctl -k | grep microcode
  
  [Regression Potential]
  Microcode are proprietary blobs, and can cause any number of new errors and 
regressions. Microcode bugs have been reported before, therefore longer than 
usual phasing and monitoring of intel-microcode bugs should be done with extra 
care.
+ 
+ [Other]
+ caml discussion describing test case to reproduce the crash.
+ https://caml.inria.fr/mantis/view.php?id=7452
+ 
+ =
  
  [Original bug report]
  
  NB: I am *not* directly affected by this bug.
  
  Henrique emailed a warning to Debian devel today [1] on a potentially
  serious issue with (sky|kaby)lake processors. Excerpt:
  
  "This warning advisory is relevant for users of systems with the Intel
  processors code-named "Skylake" and "Kaby Lake".  These are: the 6th and
  7th generation Intel Core processors (desktop, embedded, mobile and
  HEDT), their related server processors (such as Xeon v5 and Xeon v6), as
  well as select Intel Pentium processor models.
  
  TL;DR: unfixed Skylake and Kaby Lake processors could, in some
  situations, dangerously misbehave when hyper-threading is enabled.
  Disable hyper-threading immediately in BIOS/UEFI to work around the
  problem.  Read this advisory for instructions about an Intel-provided
  fix."
  
  It is probably a good idea to:
  (1) issue a warning to our users about this;
  (2) update intel-microcode on all our supported releases
  
  I leave the discussion on whether this can have security implications to
  others.
  
  [1] https://lists.debian.org/debian-devel/2017/06/msg00308.html
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: intel-microcode 3.20161104.1
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun Jun 25 10:14:19 2017
  InstallationDate: Installed on 2017-05-26 (30 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: intel-microcode
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: intel-microcode (Ubuntu Trusty)
   Status: Confirmed => Won't Fix

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

Title:
  intel-microcode is out of date, version 20170511 fixes errata on 6th
  and 7th generation platforms

Status in intel-microcode package in Ubuntu:
  Fix Released
Status in intel-microcode source package in Trusty:
  Won't Fix
Status in intel-microcode source package in Xenial:
  Confirmed
Status in intel-microcode source package in Yakkety:
  Confirmed
Status in intel-microcode source package in Zesty:
  Fix Committed
Status in intel-microcode source package in Artful:
  Fix Released

Bug description:
  [Impact]

  * A security fix has been made available as part of intel-microcode
  * It is advisable to apply it
  * Thus an SRU of the latest intel-microcode is desirable for all stable 
releases

  [Test Case]

  * Upgrade intel-microcode package, if it is already installed / one is
  running on Intel CPUs

  * Reboot and verify no averse results, and/or that microcode for your
  cpu was loaded as expected.

  [Test case reporting]
  * Please paste the output of:

  dpkg-query -W intel-microcode
  grep -E 'model|stepping' /proc/cpuinfo | sort -u
  journalctl -k | grep microcode

  [Regression Potential]
  Microcode are proprietary blobs, and can cause any number of new errors and 
regressions. Microcode bugs have been reported before, therefore longer than 
usual phasing and monitoring of intel-microcode bugs should be done with extra 
care.

  [Other]
  caml discussion describing test case to reproduce the crash.
  https://caml.inria.fr/mantis/view.php?id=7452

  =

  [Original bug report]

  NB: I am *not* directly affected by this bug.

  Henrique emailed a warning to Debian devel today [1] on a potentially
  serious

[Group.of.nepali.translators] [Bug 1647389] Re: Regression: Live migrations can still crash after CVE-2016-5403 fix

2017-03-31 Thread Dave Chiluk 
** Also affects: qemu (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/1647389

Title:
  Regression: Live migrations can still crash after CVE-2016-5403 fix

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

Bug description:
  [Impact]

   * Libvirt migrations using tunnelled libvirt cause a failure to
  migrate on the destination with error VQ 2 size 0x80 < last_avail_idx
  0x9 - used_idx 0xa

   * TBD: justification for backporting the fix to the stable release.
   * TBD: In addition, it is helpful, but not required, to include an
 explanation of how the upload fixes this bug.

  [Test Case]
  1. Create a VM on shared storage solution. In my case NFS.
  2. set start_libvirtd="yes" in /etc/default/libvirt-bin
  3. systemctl restart libvirt-bin
  4. virsh dommemstat 1 
  4. virsh -c qemu+ssh://${FROM}/system migrate --live --p2p --tunnelled ${VM} 
qemu+tcp://ubuntu@${TO}/system
  5. Repeat until failure to migrate, then check /var/log/libvirt/qemu/.log 
for error from above.

  * Yes --live, --p2p, and --tunnelled are all required to reproduce
  afaik.

  [Regression Potential] 
  TBD
   * discussion of how regressions are most likely to manifest as a result of 
this change. 
   * It is assumed that any SRU candidate patch is well-tested before
 upload and has a low overall risk of regression, but it's important
 to make the effort to think about what ''could'' happen in the
 event of a regression.
   * This both shows the SRU team that the risks have been considered,
 and provides guidance to testers in regression-testing the SRU.

  [Other Info]
  TBD
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance


  ___ Original Description follows _

  See updates at the end of #1612089. Sample error message:

  Dec 05 14:41:07 zbk130713 libvirtd[29690]: internal error: early end of file 
from monitor, possible problem:
  2016-12-05T14:41:07.903932Z qemu-system-x86_64: VQ 2 size 0x80 < 
last_avail_idx 0x9 - used_idx 0xa
  2016-12-05T14:41:07.903981Z qemu-system-x86_64: error while loading state for 
instance 0x0 of device ':00:05.0/virtio-balloon'
  2016-12-05T14:41:07.905180Z qemu-system-x86_64: load of migration failed: 
Operation not permitted

  Seems related to this patch series:
  https://lists.gnu.org/archive/html/qemu-devel/2016-08/msg03079.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1647389/+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 1677684] Re: /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not found

2017-03-30 Thread Dave Chiluk 
** Also affects: corosync (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: corosync (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/1677684

Title:
  /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-
  blackbox: not found

Status in corosync package in Ubuntu:
  New
Status in corosync source package in Trusty:
  New
Status in corosync source package in Xenial:
  New

Bug description:
  [Environment]

  Ubuntu Xenial 16.04
  Amd64

  [Reproduction]

  - Install corosync
  - Run the corosync-blackbox executable.

  root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L corosync |grep 
black
  /usr/bin/corosync-blackbox

  Expected results: corosync-blackbox runs OK.
  Current results:

  $ sudo corosync-blackbox
  /usr/bin/corosync-blackbox: 34: /usr/bin/corosync-blackbox: qb-blackbox: not 
found

  Fix:

  Make the package dependant of libqb-dev

  root@juju-niedbalski-xenial-machine-5:/home/ubuntu# dpkg -L libqb-dev | grep 
qb-bl
  /usr/sbin/qb-blackbox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1677684/+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 1674680] Re: Deprecated rfcomm.conf still mentioned

2017-03-21 Thread Dave Chiluk 
** Also affects: bluez (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: bluez (Ubuntu Yakkety)
   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/1674680

Title:
  Deprecated rfcomm.conf still mentioned

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Xenial:
  New
Status in bluez source package in Yakkety:
  New

Bug description:
  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+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 1673481] Re: "Failed to initialize A/V Sync" error trying to play HEVC h.265 with vdpau

2017-03-16 Thread Dave Chiluk 
** Also affects: mythtv (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: mythtv (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Dave Chiluk (chiluk)
   Status: New

** Also affects: mythtv (Ubuntu Aa-series)
   Importance: Undecided
   Status: New

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

** Changed in: mythtv (Ubuntu Yakkety)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

** Changed in: mythtv (Ubuntu Xenial)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

** Changed in: mythtv (Ubuntu Aa-series)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

** Changed in: mythtv (Ubuntu Aa-series)
   Status: New => Confirmed

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

** Changed in: mythtv (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: mythtv (Ubuntu Zesty)
   Status: New => Confirmed

** Changed in: mythtv (Ubuntu Aa-series)
   Importance: Undecided => Medium

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

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

** Changed in: mythtv (Ubuntu Zesty)
   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/1673481

Title:
  "Failed to initialize A/V Sync" error trying to play HEVC h.265 with
  vdpau

Status in mythtv package in Ubuntu:
  Confirmed
Status in mythtv source package in Xenial:
  Confirmed
Status in mythtv source package in Yakkety:
  Confirmed
Status in mythtv source package in Zesty:
  Confirmed
Status in mythtv source package in aa-series:
  Confirmed

Bug description:
  
  When trying to play HEVC / h265 / x265 video, frontend fails and reports 
"Failed to initialize A/V Sync" error when using vdpau.

  This is identical to upstream
  https://code.mythtv.org/trac/ticket/12992

  
  [Impact] 
   * When trying to play HEVC / h265 / x265 video, frontend fails and reports 
"Failed to initialize
 A/V Sync" error when using vdpau.

   * Log shows 
  vv
  mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:5855 
(StartPlayer) TV::StartPlayer(): Created player.
  mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:2532 
(HandleStateChange) TV::HandleStateChange(): Changing from None to WatchingVideo
  mythfrontend.real: mythfrontend[19461]: E Decoder videoout_vdpau.cpp:649 
(DrawSlice) VidOutVDPAU: Codec is not supported.
  mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:2632 
(HandleStateChange) TV::HandleStateChange(): Main UI disabled.
  mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:424 
(StartTV) TV::StartTV(): Entering main playback loop.
  mythfrontend.real: mythfrontend[19461]: E Decoder videoout_vdpau.cpp:559 
(DrawSlice) VidOutVDPAU: IsErrored() in DrawSlice
  mythfrontend.real: mythfrontend[19461]: I CoreContext screensaver-dbus.cpp:82 
(Inhibit) ScreenSaverDBus: Successfully inhibited screensaver via 
org.freedesktop.ScreenSaver. cookie 1810861299. nom nom
  mythfrontend.real: mythfrontend[19461]: W CoreContext screensaver-dbus.cpp:87 
(Inhibit) ScreenSaverDBus: Failed to disable screensaver: Type of message, 
'(ss)', does not match expected type '(susu)'
  mythfrontend.real: mythfrontend[19461]: E Decoder videoout_vdpau.cpp:559 
(DrawSlice) VidOutVDPAU: IsErrored() in DrawSlice
  mythfrontend.real: mythfrontend[19461]: I CoreContext screensaver-x11.cpp:149 
(DisableDPMS) ScreenSaverX11Private: DPMS Deactivated 1
  mythfrontend.real: mythfrontend[19461]: E Decoder videoout_vdpau.cpp:559 
(DrawSlice) VidOutVDPAU: IsErrored() in DrawSlice
  mythfrontend.real: mythfrontend[19461]: E CoreContext mythplayer.cpp:1838 
(AVSync) Player(0): AVSync: Unknown error in videoOutput, aborting playback.
  mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:2275 
(HandleStateChange) TV::HandleStateChange(): Attempting to change from 
WatchingVideo to None
  ^

   * This is identical to upstream
 https://code.mythtv.org/trac/ticket/12992

  [Test Case]

   1. Set up mythtv
   2. Configure vdpau video decoder with de-interlacing
   3. On frontend select play on h265/hevc encoded media
   4. See error

  [Regression Potential]

   * Fix is narrowly applied to hevc/h265 decoding in the vdpau decoder.

  [Other Info]
   
   *  https://code.mythtv.org/trac/ticket/12992

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mythtv-frontend 2:0.28.0+fixes.20160413.15cf421-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64

[Group.of.nepali.translators] [Bug 1626166] Re: lvm2 not starting lvm2-lvmetad on package install

2016-09-29 Thread Dave Chiluk 
I just installed yakkety, and got a similar result.  All of the cloud-
images and maas images have lvm2 already built in, so this would not be
seen there.

$ sudo vgcreate localvg
  Command failed with status code 5.

I installed yakkety like this.
#!/bin/bash
virt-install \
--connect qemu:///system \
--virt-type kvm \
--name yakketylvm \
--ram 2048 \
--disk pool=VMs,size=10 \
--graphics vnc \
-l ftp://ftp.utexas.edu/pub/ubuntu/dists/yakkety/main/installer-amd64/ \
--os-variant ubuntu16.04


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

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

Title:
  lvm2 not starting lvm2-lvmetad on package install

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * On Xenial after installing lvm2, you must reboot before you are able to 
run vgcreate. 
   * The package installer should be starting lvmetad.service. 
   *  $ sudo vgcreate localvg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Please enter a physical volume path.
Run `vgcreate --help' for more information.

  [Test Case]

   * Running the below commands result in the following error.
   
 $ sudo apt install lvm2
 $ sudo pvcreate /dev/sdb1 
 $ sudo vgcreate localvg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Please enter a physical volume path.
Run `vgcreate --help' for more information.

  [Regression Potential]

   * Solution TBD, opening the bug so I don't forget this in the midst
  of a sprint.

   * discussion of how regressions are most likely to manifest as a
  result of this change.

   * It is assumed that any SRU candidate patch is well-tested before
 upload and has a low overall risk of regression, but it's important
 to make the effort to think about what ''could'' happen in the
 event of a regression.

   * This both shows the SRU team that the risks have been considered,
 and provides guidance to testers in regression-testing the SRU.

  [Other Info]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1626166/+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 1628363] Re: VIA VL812 hub stops working with 4.4.0-40.60

2016-09-28 Thread Dave Chiluk 
** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  VIA VL812 hub stops working with 4.4.0-40.60

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

Bug description:
  VIA VL812 hub stops working with 4.4.0-40.60.  Works fine with
  4.4.0-39.59.

  Logs include both boot with 4.4.0-39 *(most recent) and 4.4.0-40
  (previous boot).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.40.42
  ProcVersionSignature: Ubuntu 4.4.0-39.59-generic 4.4.21
  Uname: Linux 4.4.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 27 22:48:35 2016
  HibernationDevice: RESUME=UUID=1cb62c08-3564-4d8a-846c-6963690d
  InstallationDate: Installed on 2016-01-15 (256 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-39-generic 
root=UUID=029afe58-00c3-4872-9556-b3fd990c5cf1 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
scsi_mod.use_blk_mq=y dm_mod.use_blk_mq=y crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-39-generic N/A
   linux-backports-modules-4.4.0-39-generic  N/A
   linux-firmware1.157.4
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SIX7910J.86A.0594.2013.0806.2241
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DX79SI
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG28808-500
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSIX7910J.86A.0594.2013.0806.2241:bd08/06/2013:svn:pn:pvr:rvnIntelCorporation:rnDX79SI:rvrAAG28808-500:cvn:ct3:cvr:
  klp-taint: 12289

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628363/+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 1378123] Re: unix_socket_abstract.sh triggers an AppArmor WARN

2016-07-07 Thread Dave Chiluk 
** Changed in: linux (Ubuntu Wily)
   Status: Confirmed => Won't Fix

** Changed in: linux (Ubuntu Vivid)
   Status: Confirmed => Won't Fix

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

Title:
  unix_socket_abstract.sh triggers an AppArmor WARN

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Won't Fix
Status in linux source package in Wily:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Running the unix_socket_abstract.sh regression test script in a loop
  results in an AppArmor WARN message in the logs. On my test system, it
  typically takes between 1 and 3 runs of unix_socket_abstract.sh before
  the WARN is hit. It does not seem to occur with the
  unix_socket_pathname.sh or unix_socket_unnamed.sh tests.

  Here's the script I used:

  ---
  #!/bin/sh

  dmesg -C
  while ! dmesg -c | grep "AppArmor WARN"; do
  bash unix_socket_abstract.sh
  done
  ---

  The following back trace is emitted in the logs:

  [ 1365.017477] [ cut here ]
  [ 1365.017486] WARNING: CPU: 0 PID: 26026 at 
/build/buildd/linux-3.16.0/security/apparmor/label.c:1767 
__aa_labelset_update_all+0x6f5/0x7f0()
  [ 1365.017487] AppArmor WARN __label_update: 
((__aa_label_remove_and_insert((&(((label)->ent[(label)->size - 
1])->ns)->labels), label, l) != l)):
  [ 1365.017489] Modules linked in: bnep rfcomm bluetooth 6lowpan_iphc 
kvm_intel kvm vmwgfx ttm drm_kms_helper serio_raw drm i2c_piix4 pvpanic 
parport_pc ppdev mac_hid lp parport psmouse pata_acpi floppy
  [ 1365.017505] CPU: 0 PID: 26026 Comm: apparmor_parser Tainted: GW
 3.16.0-20-generic #27-Ubuntu
  [ 1365.017507] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [ 1365.017509]  0009 88002dd23d88 8177f053 
88002dd23dd0
  [ 1365.017511]  88002dd23dc0 8106fcfd 880036602900 

  [ 1365.017513]  88003acaed00 0002 88003e02a0a0 
88002dd23e20
  [ 1365.017516] Call Trace:
  [ 1365.017522]  [] dump_stack+0x45/0x56
  [ 1365.017527]  [] warn_slowpath_common+0x7d/0xa0
  [ 1365.017530]  [] warn_slowpath_fmt+0x4c/0x50
  [ 1365.017533]  [] ? __aa_label_remove_and_insert+0x7e/0x1a0
  [ 1365.017536]  [] __aa_labelset_update_all+0x6f5/0x7f0
  [ 1365.017539]  [] ? securityfs_remove+0x9a/0xb0
  [ 1365.017542]  [] aa_remove_profiles+0x143/0x4f0
  [ 1365.017545]  [] profile_remove+0x3e/0x70
  [ 1365.017550]  [] vfs_write+0xb7/0x1f0
  [ 1365.017552]  [] ? do_sys_open+0x1b9/0x280
  [ 1365.017555]  [] SyS_write+0x46/0xb0
  [ 1365.017558]  [] system_call_fastpath+0x1a/0x1f
  [ 1365.017560] ---[ end trace 1e09e2c565d9ef95 ]---

  This occurs in an amd64 utopic vm:

  $ uname -a
  Linux sec-utopic-amd64 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:35:12 
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1378123/+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 1347788] Re: find crashed when current working directory is not readable and -exec or -execdir used

2016-02-24 Thread Dave Chiluk 
** Description changed:

  bug is similar to https://savannah.gnu.org/bugs/?15384 but for current
  directory (when it not readable or not executable)
  
  steps to reproduce
  
  DIR=`mktemp -d`
  cd $DIR
  mkdir -p 1/1 2
+ chmod a-rw 2
  cd 2
  find $DIR/1 -type d -exec echo {} \;
  find $DIR/1 -type d -execdir echo {} \;
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: findutils 4.4.2-7
  Uname: Linux 3.15.4-031504-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jul 23 20:17:19 2014
  Dependencies:
-  gcc-4.9-base 4.9-20140406-0ubuntu1
-  libc6 2.19-0ubuntu6
-  libgcc1 1:4.9-20140406-0ubuntu1
-  multiarch-support 2.19-0ubuntu6
+  gcc-4.9-base 4.9-20140406-0ubuntu1
+  libc6 2.19-0ubuntu6
+  libgcc1 1:4.9-20140406-0ubuntu1
+  multiarch-support 2.19-0ubuntu6
  InstallationDate: Installed on 2014-04-24 (89 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: findutils
  UpgradeStatus: No upgrade log present (probably fresh install)
- --- 
+ ---
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Dependencies:
-  gcc-4.9-base 4.9-20140406-0ubuntu1
-  libc6 2.19-0ubuntu6
-  libgcc1 1:4.9-20140406-0ubuntu1
-  multiarch-support 2.19-0ubuntu6
+  gcc-4.9-base 4.9-20140406-0ubuntu1
+  libc6 2.19-0ubuntu6
+  libgcc1 1:4.9-20140406-0ubuntu1
+  multiarch-support 2.19-0ubuntu6
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-24 (89 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: findutils 4.4.2-7
  PackageArchitecture: amd64
  Tags:  trusty
  Uname: Linux 3.15.4-031504-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

Title:
  find crashed when current working directory is not readable and -exec
  or -execdir used

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

Bug description:
  bug is similar to https://savannah.gnu.org/bugs/?15384 but for current
  directory (when it not readable or not executable)

  steps to reproduce

  DIR=`mktemp -d`
  cd $DIR
  mkdir -p 1/1 2
  chmod a-rw 2
  cd 2
  find $DIR/1 -type d -exec echo {} \;
  find $DIR/1 -type d -execdir echo {} \;

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: findutils 4.4.2-7
  Uname: Linux 3.15.4-031504-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jul 23 20:17:19 2014
  Dependencies:
   gcc-4.9-base 4.9-20140406-0ubuntu1
   libc6 2.19-0ubuntu6
   libgcc1 1:4.9-20140406-0ubuntu1
   multiarch-support 2.19-0ubuntu6
  InstallationDate: Installed on 2014-04-24 (89 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: findutils
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Dependencies:
   gcc-4.9-base 4.9-20140406-0ubuntu1
   libc6 2.19-0ubuntu6
   libgcc1 1:4.9-20140406-0ubuntu1
   multiarch-support 2.19-0ubuntu6
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-24 (89 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: findutils 4.4.2-7
  PackageArchitecture: amd64
  Tags:  trusty
  Uname: Linux 3.15.4-031504-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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