date:20160913

[Group.of.nepali.translators] [Bug 1621985] Re: [SRU] New stable micro release 2.17

2016-09-13 Thread Launchpad Bug Tracker

This bug was fixed in the package snapcraft - 2.17+16.10.1ubuntu3

---
snapcraft (2.17+16.10.1ubuntu3) yakkety; urgency=medium

  * --skip-install for yakkety as snapd is too broken here.

 -- Sergio Schvezov   Wed, 14 Sep 2016
01:38:53 +

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

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

Title:
  [SRU] New stable micro release 2.17

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

Bug description:
  This is an SRU bug to release 2.17 of snapcraft which follows the
  guidelines defined in the wiki over at
  https://wiki.ubuntu.com/SnapcraftUpdates

  The list of bugs and features in this release are defined at
  https://launchpad.net/snapcraft/+milestone/2.17

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1621985/+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 1618726] Re: ifup & ifdown crash if multiple interfaces are listed in no-scripts

2016-09-13 Thread Mathew Hodson

** Also affects: ifupdown (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837732
   Importance: Unknown
   Status: Unknown

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

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

Title:
  ifup & ifdown crash if multiple interfaces are listed in no-scripts

Status in ifupdown package in Ubuntu:
  Fix Committed
Status in ifupdown source package in Xenial:
  In Progress
Status in ifupdown package in Debian:
  Unknown

Bug description:
  [Impact]
  ifup and ifupdown segfault if multiple interfaces are listed in no-scripts

  This is a trivially reproducible crash in ifup/ifdown, with a patch
  attached.

  [Test Case]
  Steps to reproduce:
  1) echo no-scripts foo bar >> /etc/network/interfaces
  2) ifup baz

  Expected results:
  Unknown interface baz

  Actual results:
  Segmentation fault (core dumped)

  It's irrelevant whether the second interface is on the same no-scripts line 
or separate one. This will crash just the same:
  echo no-scripts foo >> /etc/network/interfaces
  echo no-scripts bar >> /etc/network/interfaces

  [Regression potential]
  Seems slight. The patch fixes a clear bug in code that is only used to 
process the no-scripts (and apparently no-auto-down) stanzas.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1618726/+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 1618726] Re: ifup & ifdown crash if multiple interfaces are listed in no-scripts

2016-09-13 Thread Michael Hudson-Doyle

I posted https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837732

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

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

** Description changed:

+ [Impact]
+ ifup and ifupdown segfault if multiple interfaces are listed in no-scripts
+ 
  This is a trivially reproducible crash in ifup/ifdown, with a patch
  attached.
  
+ [Test Case]
  Steps to reproduce:
  1) echo no-scripts foo bar >> /etc/network/interfaces
  2) ifup baz
  
  Expected results:
  Unknown interface baz
  
  Actual results:
  Segmentation fault (core dumped)
  
  It's irrelevant whether the second interface is on the same no-scripts line 
or separate one. This will crash just the same:
  echo no-scripts foo >> /etc/network/interfaces
  echo no-scripts bar >> /etc/network/interfaces
+ 
+ [Regression potential]
+ Seems slight. The patch fixes a clear bug in code that is only used to 
process the no-scripts (and apparently no-auto-down) stanzas.

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

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

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

Title:
  ifup & ifdown crash if multiple interfaces are listed in no-scripts

Status in ifupdown package in Ubuntu:
  Fix Committed
Status in ifupdown source package in Xenial:
  In Progress

Bug description:
  [Impact]
  ifup and ifupdown segfault if multiple interfaces are listed in no-scripts

  This is a trivially reproducible crash in ifup/ifdown, with a patch
  attached.

  [Test Case]
  Steps to reproduce:
  1) echo no-scripts foo bar >> /etc/network/interfaces
  2) ifup baz

  Expected results:
  Unknown interface baz

  Actual results:
  Segmentation fault (core dumped)

  It's irrelevant whether the second interface is on the same no-scripts line 
or separate one. This will crash just the same:
  echo no-scripts foo >> /etc/network/interfaces
  echo no-scripts bar >> /etc/network/interfaces

  [Regression potential]
  Seems slight. The patch fixes a clear bug in code that is only used to 
process the no-scripts (and apparently no-auto-down) stanzas.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1618726/+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 1311888] Re: "pkg-config --libs OpenIPMIpthread" fails

2016-09-13 Thread Nish Aravamudan

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

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

** Changed in: openipmi (Ubuntu Xenial)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

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

Title:
  "pkg-config --libs OpenIPMIpthread" fails

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

Bug description:
  When you try to run "pkg-config --libs OpenIPMIpthread" expected
  output should be:

  -lOpenIPMIpthread -lOpenIPMIutils -lOpenIPMI

  but instead you get:

  Package pthread was not found in the pkg-config search path.
  Perhaps you should add the directory containing `pthread.pc'
  to the PKG_CONFIG_PATH environment variable
  Package 'pthread', required by 'OpenIPMIpthread', not found

  
  This is an issue known back in 2008, with a WORKING fix: 
http://sourceforge.net/p/openipmi/feature-requests/5/

  Stumbled upon this problem over a year ago while trying to compile
  collectd, it's definitely problem with the file
  /usr/lib/pkgconfig/OpenIPMIpthread.pc

  
  Description:Ubuntu 14.04 LTS
  Release:14.04
  libopenipmi-dev 2.0.18-0ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1311888/+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 1623187] [NEW] initramfs includes qle driver, but not firmware

2016-09-13 Thread dann frazier

Public bug reported:

[Impact]
The qle driver for the Qlogic FastLinQ QL45000 Series 40GbE Adapter doesn't 
find devices. This is because the driver, by default, is loaded by the 
initramfs, and the initramfs does not contain the required firmware blob. The 
root cause is that the driver does not use implement the MODULE_FIRMWARE 
macro(), which is required for initramfs-tools to find and pre-load the 
required firmware.

[Test Case]
Install a system with a Qlogic FastLinQ QL45000 Series 40GbE Adapter. On 
failure, dmesg will show:

[ 5.934190] qede 0009:90:00.0: Direct firmware load for 
qed/qed_init_values_zipped-8.4.2.0.bin failed with error -2
[ 5.934208] [qed_slowpath_start:741()]Failed to find fw file - 
/lib/firmware/qed/qed_init_values_zipped-8.4.2.0.bin
[ 5.934280] qede: probe of 0009:90:00.0 failed with error -2
[ 5.934353] qede 0009:90:00.1: enabling device ( -> 0002)
[ 5.935115] qede 0009:90:00.1: Direct firmware load for 
qed/qed_init_values_zipped-8.4.2.0.bin failed with error -2
[ 5.935139] [qed_slowpath_start:741()]Failed to find fw file - 
/lib/firmware/qed/qed_init_values_zipped-8.4.2.0.bin
[ 5.935236] qede: probe of 0009:90:00.1 failed with error -2

[Regression Risk]
Fix is upstream and the macro usage is well defined.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: In Progress

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

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

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

Title:
  initramfs includes qle driver, but not firmware

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

Bug description:
  [Impact]
  The qle driver for the Qlogic FastLinQ QL45000 Series 40GbE Adapter doesn't 
find devices. This is because the driver, by default, is loaded by the 
initramfs, and the initramfs does not contain the required firmware blob. The 
root cause is that the driver does not use implement the MODULE_FIRMWARE 
macro(), which is required for initramfs-tools to find and pre-load the 
required firmware.

  [Test Case]
  Install a system with a Qlogic FastLinQ QL45000 Series 40GbE Adapter. On 
failure, dmesg will show:

  [ 5.934190] qede 0009:90:00.0: Direct firmware load for 
qed/qed_init_values_zipped-8.4.2.0.bin failed with error -2
  [ 5.934208] [qed_slowpath_start:741()]Failed to find fw file - 
/lib/firmware/qed/qed_init_values_zipped-8.4.2.0.bin
  [ 5.934280] qede: probe of 0009:90:00.0 failed with error -2
  [ 5.934353] qede 0009:90:00.1: enabling device ( -> 0002)
  [ 5.935115] qede 0009:90:00.1: Direct firmware load for 
qed/qed_init_values_zipped-8.4.2.0.bin failed with error -2
  [ 5.935139] [qed_slowpath_start:741()]Failed to find fw file - 
/lib/firmware/qed/qed_init_values_zipped-8.4.2.0.bin
  [ 5.935236] qede: probe of 0009:90:00.1 failed with error -2

  [Regression Risk]
  Fix is upstream and the macro usage is well defined.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1623187/+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 1596474] Re: openipmi adding to autoload fail

2016-09-13 Thread Launchpad Bug Tracker

This bug was fixed in the package openipmi - 2.0.18-0ubuntu12

---
openipmi (2.0.18-0ubuntu12) yakkety; urgency=medium

  * debian/openipmi.init: add Default-Start and Default-Stop values
(LP: #1596474).
  * Forward-port fix from 2.0.16-1.1: fix pkg-config files: pthread.pc
does not exist in Ubuntu (LP: #1311888).

 -- Nishanth Aravamudan   Mon, 12 Sep
2016 10:56:21 -0700

** Changed in: openipmi (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/1596474

Title:
  openipmi adding to autoload fail

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

Bug description:
  [Impact]

   * Attempting to set the openipmi service to autostart (or any other
  systemd manipulation of that service) results in:

  /bin/systemctl enable openipmi
  openipmi.service is not a native service, redirecting to systemd-sysv-install
  Executing /lib/systemd/systemd-sysv-install enable openipmi
  update-rc.d: error: openipmi Default-Start contains no runlevels, aborting.

* The fix specifies the common default values for Default-Start and
  Default-Stop in the init-script.

  [Test Case]

   * Install openipmi and execute `systemctl enable openipmi`. A
  successful execution indicates the issue has been fixed.

  [Regression Potential]

   * Currently, the init-script provides no Default-Start or Default-
  Stop value. I believe the chance for regression by adding these is
  very low, as they are expected to be specified by systemd (at least).

  
  I tried to add openipmi service to autostart and I've got following error:

  /bin/systemctl enable openipmi
  openipmi.service is not a native service, redirecting to systemd-sysv-install
  Executing /lib/systemd/systemd-sysv-install enable openipmi
  update-rc.d: error: openipmi Default-Start contains no runlevels, aborting.
  echo $?
  1

  update-rc.d openipmi enable
  update-rc.d: error: openipmi Default-Start contains no runlevels, aborting.

  grep Default-Start /etc/init.d/openipmi
  # Default-Start:

  lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04

  apt-cache policy openipmi
  openipmi:
    Installed: 2.0.18-0ubuntu11
    Candidate: 2.0.18-0ubuntu11
    Version table:
   *** 2.0.18-0ubuntu11 500
  500 mirror:///ubuntu/lists/archive.ubuntu.com-list- xenial/main 
amd64 Packages
  100 /var/lib/dpkg/status

  Angle brackets and text inside changed manually while bug reporting.

  After changing /etc/init.d/openipmi line above to
  # Default-Start: 2 3 4 5
  problem was solved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1596474/+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 1614131] Re: [SRU] OpenStack Mitaka point releases

2016-09-13 Thread James Page

** Also affects: cloud-archive
   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/1614131

Title:
  [SRU] OpenStack Mitaka point releases

Status in Ubuntu Cloud Archive:
  New
Status in aodh package in Ubuntu:
  Invalid
Status in cinder package in Ubuntu:
  Invalid
Status in keystone package in Ubuntu:
  Invalid
Status in nova package in Ubuntu:
  Invalid
Status in aodh source package in Xenial:
  Fix Committed
Status in cinder source package in Xenial:
  Fix Committed
Status in keystone source package in Xenial:
  Fix Committed
Status in nova source package in Xenial:
  Fix Committed

Bug description:
  This SRU will include the following point releases:
  aodh 2.0.4
  cinder 8.1.0
  keystone 9.1.0
  nova 13.1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1614131/+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 1623094] Re: cloud-init in xenial crashes on "null" vif type in network_data.json

2016-09-13 Thread Scott Moser

** Description changed:

- NOTE: this was originally reported in cpc-rax bug 1621968. Re-reporting
- here for tracking purposes as requested. Please see that issue for log
- files and more details.
+ Begin SRU Template
+ [Impact]
+ Instances of ubuntu launched on Rackspace public cloud would have broken
networking and WARN messages in /var/log/cloud-init.log.
+
+ With this new cloud-init in place, any vms launched with a config drive
+ would not work properly.
+
+ [Test Case]
+ Show failure
+ * create a vm on rackspace. using image ba8782e1-ec35-4bdc-b8f7-2f28e343094a
+openstack server create --config-drive=1 --key-name=brickies --flavor=2
--image=ba8782e1-ec35-4bdc-b8f7-2f28e343094a my-xenial-cfgdrv
+
+ * ssh will fail to system. go to rackspace cloud console, view the
+ servers' console and log in as root via password provided.
+
+ Now, to fix:
+ * log into system on console
+ * get the proposed package:
+echo "http://archive.ubuntu.com/ubuntu $(lsb_release -sc)-proposed main" |
tee /etc/apt/sources.list/proposed.list
+apt-get update
+apt-get install cloud-init
+ * reboot
+
+ You should now be able to ssh into the system.
+
+ [Regression Potential]
+ Low regression potential, as this is a fix for a regression.
+ It could potentially have fallout on other openstack cloud guests, but only
in cases where there was already failure.
+ End SRU Template
+
+
+ NOTE: this was originally reported in cpc-rax bug 1621968. Re-reporting here
for tracking purposes as requested. Please see that issue for log files and
more details.

In recent versions of cloud-init[1], we've found that when we attach a
configdrive to a cloud server cloud-init crashes before it has a chance
to complete its tasks - most critically, generating the SSH keys.

The root of this issue seems to be that cloud-init wants to parse the
included network config on the configdrive.. Our network config uses a
"null" vif type, which causes cloud-init to bomb out with an error like
this:

Sep 09 14:48:40 shtest2 cloud-init[2910]: ValueError: Unknown
network_data link type: None

[1]# dpkg -s cloud-init | grep ^Version
Version: 0.7.7~bzr1256-0ubuntu1~16.04.1

** Changed in: cloud-init
Status: New => Fix Released

** Changed in: cloud-init
Importance: Undecided => Medium

** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New

** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released

** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium

** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New

** Changed in: cloud-init (Ubuntu Xenial)
Status: New => In Progress

** Changed in: cloud-init (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/1623094

Title:
cloud-init in xenial crashes on "null" vif type in network_data.json

Status in cloud-init:
Fix Released
Status in cloud-init package in Ubuntu:
Fix Released
Status in cloud-init source package in Xenial:
In Progress

Bug description:
Begin SRU Template
[Impact]
Instances of ubuntu launched on Rackspace public cloud would have broken
networking and WARN messages in /var/log/cloud-init.log.

With this new cloud-init in place, any vms launched with a config
drive would not work properly.

[Test Case]
Show failure
* create a vm on rackspace. using image ba8782e1-ec35-4bdc-b8f7-2f28e343094a
openstack server create --config-drive=1 --key-name=brickies --flavor=2
--image=ba8782e1-ec35-4bdc-b8f7-2f28e343094a my-xenial-cfgdrv

* ssh will fail to system. go to rackspace cloud console, view the
servers' console and log in as root via password provided.

Now, to fix:
* log into system on console
* get the proposed package:
echo "http://archive.ubuntu.com/ubuntu $(lsb_release -sc)-proposed main" |
tee /etc/apt/sources.list/proposed.list
apt-get update
apt-get install cloud-init
* reboot

You should now be able to ssh into the system.

[Regression Potential]
Low regression potential, as this is a fix for a regression.
It could potentially have fallout on other openstack cloud guests, but only
in cases where there was already failure.
End SRU Template

NOTE: this was originally reported in cpc-rax bug 1621968. Re-reporting here
for tracking purposes as requested. Please see that issue for log files and
more details.

In recent versions of cloud-init[1], we've found that when we attach a
configdrive to a cloud server cloud-init crashes before it has a
chance to complete its tasks - most critically, generating the SSH
keys.

The root of this issue seems to be that cloud-init wants to parse the
included network

[Group.of.nepali.translators] [Bug 1623107] [NEW] [SRU] python-pylxd 2.0.4

2016-09-13 Thread Corey Bryant

Public bug reported:

This SRU gets us to the latest pylxd point release for xenial.

** Affects: python-pylxd (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: python-pylxd (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Also affects: python-pylxd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: python-pylxd (Ubuntu)
   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/1623107

Title:
  [SRU] python-pylxd 2.0.4

Status in python-pylxd package in Ubuntu:
  Invalid
Status in python-pylxd source package in Xenial:
  New

Bug description:
  This SRU gets us to the latest pylxd point release for xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pylxd/+bug/1623107/+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 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

2016-09-13 Thread Andreas Pokorny

** Bug watch added: GNOME Bug Tracker #768138
   https://bugzilla.gnome.org/show_bug.cgi?id=768138

** Also affects: gtk via
   https://bugzilla.gnome.org/show_bug.cgi?id=768138
   Importance: Unknown
   Status: Unknown

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

Title:
  keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

Status in Canonical System Image:
  Confirmed
Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in libertine package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  New
Status in libertine source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server package in Ubuntu RTM:
  New

Bug description:
  [Impact]

  Auto key repeating does not work in Libertine X apps which is very
  frustrating to users.

  [Test Case]

  1. Install xterm in libertine
  2. Start xterm from the "Xapps" scope
  3. Wait for xterm to appear
  4. Press and hold a key

  See how it only appears once and not multiple times as it should.

  [Regression Potential]

  Non observed.

  
  Original Description:

  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591356/+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 1575727] Re: Cloud-init incorrect openstack datasource on dpkg-reconfigure

2016-09-13 Thread Scott Moser

** Also affects: cloud-init (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Trusty)
   Importance: Undecided => Low

** Description changed:

+  Begin SRU Template 
+ [Impact] 
+ When re-configuring cloud-init package by running dpkg-reconfigure, the 
OpenStack data source is incorrectly written to the configuration file 
/etc/cloud/cloud.cfg.d/90_dpkg.cfg.
+ 
+ The result is that dpkg-reconfigure and selecting OpenStack results in
+ non-functional openstack datasource.
+ 
+ [Test Case]
+ # launch a container
+ $ lxc launch ubuntu-daily:xenial x1
+ $ lxc exec x1 dpkg-reconfigure cloud-init
+ ## Note that 'OpenStack' is not checked.
+ ## Select OpenStack, hit enter
+ $ lxc exec x1 cat /etc/cloud/cloud.cfg.d/90_dpkg.cfg 
+ # to update this file, run dpkg-reconfigure cloud-init
+ datasource_list: [ NoCloud, ConfigDrive, OpenNebula, Azure, AltCloud, OVF, 
MAAS, GCE, Openstack, CloudSigma, SmartOS, Ec2, CloudStack, None ]
+ 
+ Note, the reconfigured file was written, but contains 'Openstack' (lower
+ case s), when OpenStack is what is needed.
+ 
+ When fixed, this will have 'OpenStack'.
+ 
+ [Regression Potential] 
+ Regression potential would be limited to people running dpkg-reconfigure for 
cloud-init.
+  End SRU Template 
+ 
+ 
  On Ubuntu 14.04 LTS when re-configuring the cloud-init package by
  running dpkg-reconfigure, the OpenStack data source is incorrectly
  written to the configuration file /etc/cloud/cloud.cfg.d/90_dpkg.cfg
  
  From a default install:
  
  datasource_list: [ NoCloud, ConfigDrive, OpenNebula, Azure, AltCloud,
  OVF, MAAS, GCE, OpenStack, CloudSigma, Ec2, CloudStack, SmartOS, None ]
  
  After running dpkg-reconfigure, selecting all options.
  
  datasource_list: [ NoCloud, ConfigDrive, OpenNebula, Azure, AltCloud,
  OVF, MAAS, GCE, Openstack, CloudSigma, Ec2, CloudStack, SmartOS, None ]
  
- 
  Note that it reads "Openstack" instead of "OpenStack".

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

Title:
  Cloud-init incorrect openstack datasource on dpkg-reconfigure

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Trusty:
  Confirmed
Status in cloud-init source package in Xenial:
  Confirmed

Bug description:
   Begin SRU Template 
  [Impact] 
  When re-configuring cloud-init package by running dpkg-reconfigure, the 
OpenStack data source is incorrectly written to the configuration file 
/etc/cloud/cloud.cfg.d/90_dpkg.cfg.

  The result is that dpkg-reconfigure and selecting OpenStack results in
  non-functional openstack datasource.

  [Test Case]
  # launch a container
  $ lxc launch ubuntu-daily:xenial x1
  $ lxc exec x1 dpkg-reconfigure cloud-init
  ## Note that 'OpenStack' is not checked.
  ## Select OpenStack, hit enter
  $ lxc exec x1 cat /etc/cloud/cloud.cfg.d/90_dpkg.cfg 
  # to update this file, run dpkg-reconfigure cloud-init
  datasource_list: [ NoCloud, ConfigDrive, OpenNebula, Azure, AltCloud, OVF, 
MAAS, GCE, Openstack, CloudSigma, SmartOS, Ec2, CloudStack, None ]

  Note, the reconfigured file was written, but contains 'Openstack'
  (lower case s), when OpenStack is what is needed.

  When fixed, this will have 'OpenStack'.

  [Regression Potential] 
  Regression potential would be limited to people running dpkg-reconfigure for 
cloud-init.
   End SRU Template 


  On Ubuntu 14.04 LTS when re-configuring the cloud-init package by
  running dpkg-reconfigure, the OpenStack data source is incorrectly
  written to the configuration file /etc/cloud/cloud.cfg.d/90_dpkg.cfg

  From a default install:

  datasource_list: [ NoCloud, ConfigDrive, OpenNebula, Azure, AltCloud,
  OVF, MAAS, GCE, OpenStack, CloudSigma, Ec2, CloudStack, SmartOS, None
  ]

  After running dpkg-reconfigure, selecting all options.

  datasource_list: [ NoCloud, ConfigDrive, OpenNebula, Azure, AltCloud,
  OVF, MAAS, GCE, Openstack, CloudSigma, Ec2, CloudStack, SmartOS, None
  ]

  Note that it reads "Openstack" instead of "OpenStack".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1575727/+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 1613708] Re: [regression] Xmir: Some buttons are unclickable after rotating the screen

2016-09-13 Thread Ken VanDine

** Also affects: xorg-server (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/1613708

Title:
  [regression] Xmir: Some buttons are unclickable after rotating the
  screen

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

Bug description:
  [Impact]

  XMir clients do not have their input transform matrix modified
  properly when the screen dimensions and orientation change (ie.
  rotation).

  This shows up primarily on Bq M10 tablets which rotate on startup.

  [Test Case]

  Install XMir on a device that supports screen rotation.  Connect a
  client (using Libertine is the easiest way to do this).  Attempt to
  use direct or indirect pointer input on the right side of the screen.
  The bug is it does nothing.

  [Regression Potential]

  This change affects only the XMir server.  There is potential that
  XMir functionality is compromized but mainline x.org functionality is
  unaffected.

  This XMir patch update is pulled directly from Ubuntu current
  development release "Yakkety Yak" where it has been in production for
  more than 6 weeks without apparent regressions.

  [Other Info]

  The patch update also includes bugfixes for bug #1617925, bug
  #1617932, and bug #1591356.

  -- original bug description follows --

  Enviroment:

  current build number: 169
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-08-16 10:23:29
  version version: 169
  version ubuntu: 20160816
  version device: 20160809.0
  version custom: 20160805--42-20-vivid

  Product: BQ M10 FHD

  Steps to reproduce:

  1º Open LibreOffice and try to print something
  2º Print settings window appear, try to click on Accept/Cancel/Exit etc
  3º Buttons on LibreOffice won't respond

  1º Open Firefox
  2º Mouse-over on search,downloads,bookmarks etc
  3º Seems like mouse-over is not focused and is clicking is not responding

  Current result: Some Xapps buttons are not responding(tested on
  Firefox and LibreOffice Writer)

  Expected result:

  Add info: This is using xmir from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-053/+packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613708/+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 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

2016-09-13 Thread Ken VanDine

** Also affects: xorg-server (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gtk+3.0 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: libertine (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/1591356

Title:
  keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in libertine package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  New
Status in libertine source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server package in Ubuntu RTM:
  New

Bug description:
  [Impact]

  Auto key repeating does not work in Libertine X apps which is very
  frustrating to users.

  [Test Case]

  1. Install xterm in libertine
  2. Start xterm from the "Xapps" scope
  3. Wait for xterm to appear
  4. Press and hold a key

  See how it only appears once and not multiple times as it should.

  [Regression Potential]

  Non observed.

  
  Original Description:

  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591356/+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 1615745] Re: package does not include dhcp hook scripts

2016-09-13 Thread Scott Moser

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: cloud-init (Ubuntu Xenial)
   Status: Fix Released => In Progress

** Changed in: cloud-init (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/1615745

Title:
  package does not include dhcp hook scripts

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress

Bug description:
  A recent azure change added some files to cloud-init.
  Installed from tools/ by setup.py, these are put in the filesystem at
./etc/dhcp/dhclient-exit-hooks.d/hook-dhclient
./etc/NetworkManager/dispatcher.d/hook-network-manager

  They are not currentlypicked up by the ubuntu package 0.7.7-13
  -g41271bd-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cloud-init 0.7.7-13-g41271bd-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15
  Uname: Linux 4.4.0-9134-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Mon Aug 22 16:53:55 2016
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1615745/+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 1590553] Re: Xmir -rootless: Buttons are randomly unclickable (popups vanish instantly)

2016-09-13 Thread Ken VanDine

** Also affects: xorg-server (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/1590553

Title:
  Xmir -rootless: Buttons are randomly unclickable (popups vanish
  instantly)

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  New

Bug description:
  Xmir -rootless: Buttons are randomly unclickable

  I've noticed this in LibreOffice Impress and Chromium browser.
  Sometimes when clicking buttons, the button just flickers and does
  nothing. Sometimes it also involves a popup menu flickering and out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1590553/+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 1612313] Re: maas datasource needs support for vendor-data

2016-09-13 Thread Scott Moser

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu)
   Status: New => Fix Released

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  maas datasource needs support for vendor-data

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress

Bug description:
  maas datasource does not support vendor-data.
  We would like to take advantage of vendordata in maas, and thus cloud-init 
needs it.

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

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

[Group.of.nepali.translators] [Bug 1602724] Re: Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

2016-09-13 Thread Tim Gardner

https://lists.ubuntu.com/archives/kernel-team/2016-September/079944.html

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

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

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

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

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

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

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

[Group.of.nepali.translators] [Bug 1524907] Re: [SRU] Race condition in SIGTERM signal handler

2016-09-13 Thread James Page

** Also affects: cloud-archive/liberty
   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/1524907

Title:
  [SRU] Race condition in SIGTERM signal handler

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive liberty series:
  In Progress
Status in oslo.service:
  Fix Released
Status in python-oslo.service package in Ubuntu:
  Fix Released
Status in python-oslo.service source package in Wily:
  Won't Fix
Status in python-oslo.service source package in Xenial:
  Fix Released
Status in python-oslo.service source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * See bug description. We are seeing this in a Liberty production
 environment and (at least) nova-conductor services are failing to
 restart properly.

   * this fix just missed the version of python-oslo.service we have in the
 Liberty UCA so queueing up for backport

  [Test Case]

   * Start a service that has a high number of workers, check that all
 are up then do a service stop (or killall -s SIGTERM nova-conductor)
 and check that all workers/process are stopped.

  [Regression Potential]

   * none


  If the process launcher gets a SIGTERM signal, it calls _sigterm() to
  handle it. This function calls SignalHandler() singleton to get the
  instance of SignalHandler. This singleton acquires a lock to ensure
  that the singleton is unique.

  Problem arises when the process launcher gets a second SIGTERM while
  the singleton lock (called 'singleton_lock') is locked. _sigterm() is
  called again (reentrant call!), but we enter a dead lock. If eventlet
  is used, eventlet fails on an assertion error: "Cannot switch to
  MAINLOOP from MAINLOOP".

  The bug can occurs with SIGTERM and SIGHUP signals.

  I saw this issue with OpenStack services managed by systemd with a
  wrong configuration: SIGTERM is sent to all processes of the cgroups,
  instead of only sending the SIGTERM signal to the "main" process
  ("Main PID" in systemd). When the process launcher gets a SIGTERM, it
  sends a new SIGTERM signal to each child process. If systemd already
  sent a first SIGTERM to child processes, they now get two SIGTERM
  "shortly".

  For OpenStack services managed by systemd, the service file must
  contain "KillMode=process" to only send SIGTERM to the main process
  ("Main PID").

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1524907/+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 1583621] Re: File /etc/ceilometer/gnocchi_resources.yaml missing in ceilometer package

2016-09-13 Thread James Page

This is resolved for Newton in:

ceilometer (1:7.0.0~b3-0ubuntu1) yakkety; urgency=medium

  [ David Della Vecchia ]
  * New upstream version.
  * d/control: Fixing spelling mistake.

  [ Corey Bryant ]
  * New upstream version.
  * d/control: Add python-cotyledon to (Build-)Depends.
  * New upstream version.
  * d/ceilometer-common.install: Install new/existing config and sample files
from usr/etc.
  * d/rules: Exclude install of ceilometer-config-generator.conf.
  * d/ceilometer-common.postinst: Ensure proper permissions for
/etc/ceilometer/rootwrap*.

  [ Dimitri John Ledkov ]
  * Check ipmi agent is running only on i386 & amd64.

  [ James Page ]
  * New upstream release.

 -- James Page   Fri, 02 Sep 2016 11:51:21 +0100


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

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

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

** Also affects: cloud-archive
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/mitaka
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/liberty
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/newton
   Importance: Undecided
   Status: New

** Changed in: cloud-archive/newton
   Status: New => Fix Released

** Changed in: cloud-archive/newton
   Importance: Undecided => Medium

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

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

** Changed in: cloud-archive/liberty
   Importance: Undecided => Medium

** Changed in: cloud-archive/mitaka
   Importance: Undecided => Medium

** Changed in: cloud-archive/mitaka
   Status: New => Triaged

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

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

Title:
  File /etc/ceilometer/gnocchi_resources.yaml missing in ceilometer
  package

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive liberty series:
  New
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Xenial:
  Triaged
Status in ceilometer source package in Yakkety:
  Fix Released

Bug description:
  The file gnocchi_resources.yaml is needed when ceilometer is set up
  with gnocchi as backend. It is contained in the upstream source. IIUC
  this affects Liberty and Mitaka packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1583621/+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 1524907] Re: Race condition in SIGTERM signal handler

2016-09-13 Thread Louis Bouchard

** Also affects: python-oslo.service (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: python-oslo.service (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: python-oslo.service (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Changed in: python-oslo.service (Ubuntu Wily)
   Status: New => Won't Fix

** Changed in: python-oslo.service (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: python-oslo.service (Ubuntu Yakkety)
   Status: New => Fix Released

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

Title:
  Race condition in SIGTERM signal handler

Status in Ubuntu Cloud Archive:
  Fix Released
Status in oslo.service:
  Fix Released
Status in python-oslo.service package in Ubuntu:
  Fix Released
Status in python-oslo.service source package in Wily:
  Won't Fix
Status in python-oslo.service source package in Xenial:
  Fix Released
Status in python-oslo.service source package in Yakkety:
  Fix Released

Bug description:
  If the process launcher gets a SIGTERM signal, it calls _sigterm() to
  handle it. This function calls SignalHandler() singleton to get the
  instance of SignalHandler. This singleton acquires a lock to ensure
  that the singleton is unique.

  Problem arises when the process launcher gets a second SIGTERM while
  the singleton lock (called 'singleton_lock') is locked. _sigterm() is
  called again (reentrant call!), but we enter a dead lock. If eventlet
  is used, eventlet fails on an assertion error: "Cannot switch to
  MAINLOOP from MAINLOOP".

  The bug can occurs with SIGTERM and SIGHUP signals.

  I saw this issue with OpenStack services managed by systemd with a
  wrong configuration: SIGTERM is sent to all processes of the cgroups,
  instead of only sending the SIGTERM signal to the "main" process
  ("Main PID" in systemd). When the process launcher gets a SIGTERM, it
  sends a new SIGTERM signal to each child process. If systemd already
  sent a first SIGTERM to child processes, they now get two SIGTERM
  "shortly".

  For OpenStack services managed by systemd, the service file must
  contain "KillMode=process" to only send SIGTERM to the main process
  ("Main PID").

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1524907/+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 913880] Re: mouse scroll down over sound indicator while expo is active selects previous desktop

2016-09-13 Thread Launchpad Bug Tracker

This bug was fixed in the package compiz -
1:0.9.12.2+16.04.20160823-0ubuntu1

---
compiz (1:0.9.12.2+16.04.20160823-0ubuntu1) xenial; urgency=medium

  [ Andrea Azzarone ]
  * [expo] limit scroll to workarea. (LP: #913880)

 -- Marco Trevisan (Treviño)   Tue, 23 Aug 2016 16:06:02
+

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

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

Title:
  mouse scroll down over sound indicator while expo is active selects
  previous desktop

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

Bug description:
  [Impact]

  Scrolling on indicators doesn't work when expo is active

  [Test case]

  To reproduce:

  1) Activate the workspace switcher (super + S).
  2) Place your mouse cursor over the sound indicator.

  Scrolliong the mouse wheel *up* will change the current system volume
  only. Scrolling the mouse wheel *down* changes both the system volume
  *and* selects the previous desktop in the switcher. Surely the
  behavior should be consistent between scrolling up and down?

  [Regression potential]

  Changing workspace with mouse wheel or double-clicks might not work
  anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/913880/+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 1621985] Re: [SRU] New stable micro release 2.17

[Group.of.nepali.translators] [Bug 1618726] Re: ifup & ifdown crash if multiple interfaces are listed in no-scripts

[Group.of.nepali.translators] [Bug 1618726] Re: ifup & ifdown crash if multiple interfaces are listed in no-scripts

[Group.of.nepali.translators] [Bug 1311888] Re: "pkg-config --libs OpenIPMIpthread" fails

[Group.of.nepali.translators] [Bug 1623187] [NEW] initramfs includes qle driver, but not firmware

[Group.of.nepali.translators] [Bug 1596474] Re: openipmi adding to autoload fail

[Group.of.nepali.translators] [Bug 1614131] Re: [SRU] OpenStack Mitaka point releases

[Group.of.nepali.translators] [Bug 1623094] Re: cloud-init in xenial crashes on "null" vif type in network_data.json

[Group.of.nepali.translators] [Bug 1623107] [NEW] [SRU] python-pylxd 2.0.4

[Group.of.nepali.translators] [Bug 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

[Group.of.nepali.translators] [Bug 1575727] Re: Cloud-init incorrect openstack datasource on dpkg-reconfigure

[Group.of.nepali.translators] [Bug 1613708] Re: [regression] Xmir: Some buttons are unclickable after rotating the screen

[Group.of.nepali.translators] [Bug 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work

[Group.of.nepali.translators] [Bug 1615745] Re: package does not include dhcp hook scripts

[Group.of.nepali.translators] [Bug 1590553] Re: Xmir -rootless: Buttons are randomly unclickable (popups vanish instantly)

[Group.of.nepali.translators] [Bug 1612313] Re: maas datasource needs support for vendor-data

[Group.of.nepali.translators] [Bug 1602724] Re: Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

[Group.of.nepali.translators] [Bug 1524907] Re: [SRU] Race condition in SIGTERM signal handler

[Group.of.nepali.translators] [Bug 1583621] Re: File /etc/ceilometer/gnocchi_resources.yaml missing in ceilometer package

[Group.of.nepali.translators] [Bug 1524907] Re: Race condition in SIGTERM signal handler

[Group.of.nepali.translators] [Bug 913880] Re: mouse scroll down over sound indicator while expo is active selects previous desktop

21 matches

Site Navigation

Mail list logo

Footer information