date:20161104

[Group.of.nepali.translators] [Bug 1635246] Re: linux-raspi2: 4.4.0-1030.37 -proposed tracker

2016-11-04 Thread Po-Hsu Lin

** Changed in: kernel-sru-workflow/regression-testing
   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/1635246

Title:
  linux-raspi2: 4.4.0-1030.37 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1635242
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635246/+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 1635247] Re: linux-snapdragon: 4.4.0-1033.37 -proposed tracker

2016-11-04 Thread Po-Hsu Lin

** Changed in: kernel-sru-workflow/regression-testing
   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/1635247

Title:
  linux-snapdragon: 4.4.0-1033.37 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Fix Released
Status in linux-snapdragon source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1635242
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635247/+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 1635242] Re: linux: 4.4.0-46.67 -proposed tracker

2016-11-04 Thread Po-Hsu Lin

http://kernel.ubuntu.com/testing/tracker-index.html
Looking good.

** Changed in: kernel-sru-workflow/regression-testing
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux: 4.4.0-46.67 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1635242/+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 1639381] Re: SRU 0.11 tracking bug

2016-11-04 Thread Barry Warsaw

** Changed in: ubuntu-image
   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/1639381

Title:
  SRU 0.11 tracking bug

Status in Ubuntu Image:
  Fix Released
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-image source package in Xenial:
  New
Status in ubuntu-image source package in Yakkety:
  New

Bug description:
  New SRU tracking bug (with exception) for ubuntu-image 0.11 in Yakkety
  and Xenial.

  See https://wiki.ubuntu.com/UbuntuImageUpdates

  [Impact]

  ubuntu-image 0.11 fixes a problem related to the sorting of structures
  in a volume.  Structure elements are now sorted by their offset order,
  even if that offset is implicit.  (LP: #1631423).  Several other
  issues are also fixed.

  [Test Case]

  Create an image without --cloud-init. Mount the file system and ensure
  that there's no var/lib/cloud/seed/nocloud-net/meta-data file.

  Create an image with --cloud-init. Mount the file system and ensure
  that the var/lib/cloud/seed/nocloud-net/meta-data file exists. The
  contents of the file should be `instance-id: nocloud-static`.

  [Regression Potential]

  When --cloud-init is given, var/lib/cloud/seed/nocloud-net/meta-data
  is not written, or the cloud-init option value is not copied to
  var/lib/cloud/seed/nocloud-net/user-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-image/+bug/1639381/+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 1639381] [NEW] SRU 0.11 tracking bug

2016-11-04 Thread Barry Warsaw

Public bug reported:

New SRU tracking bug (with exception) for ubuntu-image 0.11 in Yakkety
and Xenial.

See https://wiki.ubuntu.com/UbuntuImageUpdates

[Impact]

ubuntu-image 0.11 fixes a problem related to the sorting of structures
in a volume.  Structure elements are now sorted by their offset order,
even if that offset is implicit.  (LP: #1631423).  Several other issues
are also fixed.

[Test Case]

Create an image without --cloud-init. Mount the file system and ensure
that there's no var/lib/cloud/seed/nocloud-net/meta-data file.

Create an image with --cloud-init. Mount the file system and ensure that
the var/lib/cloud/seed/nocloud-net/meta-data file exists. The contents
of the file should be `instance-id: nocloud-static`.

[Regression Potential]

When --cloud-init is given, var/lib/cloud/seed/nocloud-net/meta-data is
not written, or the cloud-init option value is not copied to
var/lib/cloud/seed/nocloud-net/user-data

** Affects: ubuntu-image
 Importance: Undecided
 Status: In Progress

** Affects: ubuntu-image (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-image (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: ubuntu-image (Ubuntu Yakkety)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-image (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: ubuntu-image (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-image
Milestone: None => 0.11

** Changed in: ubuntu-image
   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/1639381

Title:
  SRU 0.11 tracking bug

Status in Ubuntu Image:
  In Progress
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-image source package in Xenial:
  New
Status in ubuntu-image source package in Yakkety:
  New

Bug description:
  New SRU tracking bug (with exception) for ubuntu-image 0.11 in Yakkety
  and Xenial.

  See https://wiki.ubuntu.com/UbuntuImageUpdates

  [Impact]

  ubuntu-image 0.11 fixes a problem related to the sorting of structures
  in a volume.  Structure elements are now sorted by their offset order,
  even if that offset is implicit.  (LP: #1631423).  Several other
  issues are also fixed.

  [Test Case]

  Create an image without --cloud-init. Mount the file system and ensure
  that there's no var/lib/cloud/seed/nocloud-net/meta-data file.

  Create an image with --cloud-init. Mount the file system and ensure
  that the var/lib/cloud/seed/nocloud-net/meta-data file exists. The
  contents of the file should be `instance-id: nocloud-static`.

  [Regression Potential]

  When --cloud-init is given, var/lib/cloud/seed/nocloud-net/meta-data
  is not written, or the cloud-init option value is not copied to
  var/lib/cloud/seed/nocloud-net/user-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-image/+bug/1639381/+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 1044662] Re: compiz crashed with signal 5 (SIGTRAP) in g_logv() from g_log() from g_settings_schema_get_value() from g_settings_schema_key_init() from g_settings_get

2016-11-04 Thread Andrea Azzarone

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

Title:
  compiz crashed with signal 5 (SIGTRAP) in g_logv() from g_log() from
  g_settings_schema_get_value() from g_settings_schema_key_init() from
  g_settings_get_value()

Status in Compiz:
  Fix Released
Status in GLib:
  Invalid
Status in compiz package in Ubuntu:
  Fix Released
Status in compiz source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Compiz crashes if a setting is not available when using gsettings backend, 
instead of falling back on the default.

  [Test case]
  This causes some temporary system changes:
   sudo mv /usr/share/glib-2.0/schemas/org.compiz.unityshell.gschema.xml /tmp
   sudo glib-compile-schemas /usr/share/glib-2.0/schemas/
   initctl restart unity7

  Unity should be now properly loaded, using default settings
  (~/.cache/upstart/unity7.log should complain about that, but with no
  crash).

  To restore your state:
sudo mv /tmp/org.compiz.unityshell.gschema.xml /usr/share/glib-2.0/schemas
sudo glib-compile-schemas /usr/share/glib-2.0/schemas/
  or
sudo apt-get install --reinstall unity

  [Regression potential]

  User settings might be ignored in some cases.

  -

  crash during 2012.09.01 compiz update
  (quantal installed on virtualbox)

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: compiz-core 1:0.9.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: amd64
  CurrentDmesg:
   [  104.602256] ISO 9660 Extensions: Microsoft Joliet Level 3
   [  104.732537] ISO 9660 Extensions: RRIP_1991A
   [  928.134106] show_signal_msg: 24 callbacks suppressed
   [  928.134110] compiz[1661]: segfault at 105112644 ip 7f0a55ab63ec sp 
7fff6acb4010 error 6 in libc-2.15.so[7f0a55a2b000+1b2000]
   [  929.026467] compiz[2550] trap int3 ip:7ff2c0e9dfcf sp:7fffc2102180 error:0
  Date: Sat Sep  1 11:06:53 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox-guest, 4.1.18, 3.5.0-10-generic, x86_64: installed
   virtualbox-guest, 4.1.18, 3.5.0-11-generic, x86_64: installed
   virtualbox-guest, 4.1.18, 3.5.0-13-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  Lsusb:
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=fr_CH:fr
   PATH=(custom, no user)
   LANG=fr_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic 
root=UUID=d7944af3-f0a6-4074-b1c2-cfc5e67479f2 ro quiet splash vt.handoff=7
  Signal: 5
  SourcePackage: compiz
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   getVariantAtKey () from /usr/lib/libcompizconfig_gsettings_backend.so
   readOption () from /usr/lib/compizconfig/backends/libgsettings.so
  Title: compiz crashed with signal 5 in g_settings_get_value()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz 1:0.9.8.0-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.38-0ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.1-4~ubuntu1

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

___
Mailing list:

[Group.of.nepali.translators] [Bug 1073488] Re: window management - if a window is always on top, it will always get focus after switching between workspaces

2016-11-04 Thread Andrea Azzarone

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

Title:
  window management - if a window is always on top, it will always get
  focus after switching between workspaces

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

Bug description:
  Imagine I have an small terminal window open all the time for doing
  quick arithmetics. I have set it to be always on top since I need to
  constantly see it. I have also some other windows open (other
  terminals, nautilus etc.) on which I am really working and they have
  the window focus most of the time.

  What happens:
  Whenever I switch to another workspace and come back to the current 
workspace, I see the 'always on top' window gets the focus, even if I left that 
workspace when another window had the focus.

  What should happen:
  When some window has the focus in any workspace, it should keep the focus. By 
switching to a new workspace, focus of the windows of the old workspace should 
not change.

  How to reproduce the bug:
  Open several windows in a workspace. Make one of the windows 'always on top' 
from its window accessibility menu (Window 1). Then click on some other window 
to give it focus (Window 2). Now go to another workspace (by pressing 
Ctrl+Alt+Left/Right) and then come back. You will see that Window 1 has the 
focus, instead of Window 2.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.16.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  295.40  Thu Apr  5 21:37:00 
PDT 2012
   GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Wed Oct 31 09:59:56 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-current, 295.40, 3.2.0-29-generic, x86_64: installed
   nvidia-current, 295.40, 3.2.0-31-generic, x86_64: installed
   nvidia-current, 295.40, 3.2.0-32-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:83b0]
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  JockeyStatus:
   xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, 
Enabled, In use)
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
   xorg:nvidia_experimental_304 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Proprietary, Disabled, Not in use)
   xorg:nvidia_experimental_310 - NVIDIA accelerated graphics driver 
(**experimental** beta) (Proprietary, Disabled, Not in use)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic 
root=UUID=b8c1967c-1d4e-4034-bed5-3b1357a3d26b ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier  "Default Device"
Option  "NoLogo""True"
   EndSection
  dmi.bios.date: 09/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8P67 REV 3.1
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8P67REV3.1:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.7.8-0ubuntu1.4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri:

[Group.of.nepali.translators] [Bug 1582430] Re: spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is already playing music

2016-11-04 Thread Andrea Azzarone

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

Title:
  spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is
  already playing music

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

Bug description:
  [Impact]
  spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is already 
playing music

  [Test Case]

  1. Start Rhythmbox.
  2. Play some music.
  3. Close the Rhythmbox window.
  4. Open Rhythmbox from Dash or Launcher (if Rhythmbox is locked to it).
  5. Admire annoying spinning wheel for about 13 seconds.

  If Rhythmbox is reopened from the sound tray menu it is ok, no
  spinning wheel.

  [Possible Regresssions]
  Unity fails to notify the application startup or the startup notification 
process finishes too soon.

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

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

[Group.of.nepali.translators] [Bug 1606254] Re: Super+S activates expo plugin even on a 1x1 setup

2016-11-04 Thread Andrea Azzarone

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

Title:
  Super+S activates expo plugin even on a 1x1 setup

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

Bug description:
  [Test case]
  1. Using ccsm set Horizonal/Vertical virtual size to 1
  2. Activate expo (e.g. using Super+S)

  Expected behavior:
  nothing happens

  Actual behavior:
  The plugin is activated, but it's useless

  [Regression potential]

  No expo is shown in multi-monitor with one desktop, but it's not
  something we ever supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1606254/+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 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

2016-11-04 Thread Launchpad Bug Tracker

This bug was fixed in the package dbus - 1.10.10-1ubuntu2

---
dbus (1.10.10-1ubuntu2) zesty; urgency=medium

  * debian/patches/make-uid-0-immune-to-timeout.patch:
- Add a test patch proposed by Simon McVittie upstream to fix bug
  LP: #1591411.

 -- Łukasz 'sil2100' Zemczak   Tue, 11 Oct
2016 20:12:43 +0200

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

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Unknown
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Confirmed
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1591411/+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 1573073] Re: When router has no ports _process_updated_router fails because the namespace does not exist

2016-11-04 Thread Corey Bryant

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: neutron (Ubuntu Zesty)
   Status: New => Triaged

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

Title:
  When router has no ports _process_updated_router fails because the
  namespace does not exist

Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive liberty series:
  Triaged
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive newton series:
  Triaged
Status in neutron:
  In Progress
Status in neutron package in Ubuntu:
  Triaged
Status in neutron source package in Xenial:
  Triaged
Status in neutron source package in Yakkety:
  Triaged
Status in neutron source package in Zesty:
  Triaged

Bug description:
  Happens in Kilo. Cannot test on other releases.

  Steps to reproduce:

  1) create a router and set at least a port, also the gateway is fine
  2) check that the namespace exists with
 ip netns show | grep qrouter-
  3) check the ports are there
 ip netns exec qrouter- ip addr show
  4) delete all ports from the router
  5) check that only loopback interface is present
 ip netns exec qrouter- ip addr show
  6) run the cronjob task that is installed in the file
 /etc/cron.d/neutron-l3-agent-netns-cleanup
  so basically run this command:
 /usr/bin/neutron-netns-cleanup --config-file=/etc/neutron/neutron.conf 
--config-file=/etc/neutron/l3_agent.ini
  7) the namespace should be gone:
 ip netns show | grep qrouter-
  8) delete the neutron router.
  9) check log file /var/log/neutron/vpn-agent.log

  
  When the router has no ports the namespace is deleted from the network node 
by the cronjob. However this brakes the router updates and the file 
vpn-agent.log is flooded with this traces:

  2016-04-21 16:22:17.771 23382 TRACE neutron.agent.l3.router_info Traceback 
(most recent call last):
  2016-04-21 16:22:17.771 23382 TRACE neutron.agent.l3.router_info   File 
"/usr/lib/python2.7/dist-packages/neutron/common/utils.py", line 343, in call
  2016-04-21 16:22:17.771 23382 TRACE neutron.agent.l3.router_info return 
func(*args, **kwargs)
  2016-04-21 16:22:17.771 23382 TRACE neutron.agent.l3.router_info   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/router_info.py", line 628, 
in process
  2016-04-21 16:22:17.771 23382 TRACE neutron.agent.l3.router_info 
self._process_internal_ports()
  2016-04-21 16:22:17.771 23382 TRACE neutron.agent.l3.router_info   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/router_info.py", line 404, 
in _process_internal_ports
  2016-04-21 16:22:17.771 23382 TRACE neutron.agent.l3.router_info 
existing_devices = self._get_existing_devices()
  2016-04-21 16:22:17.771 23382 TRACE neutron.agent.l3.router_info   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/l3/router_info.py", line 328, 
in _get_existing_devices
  2016-04-21 16:22:17.771 23382 TRACE neutron.agent.l3.router_info ip_devs 
= ip_wrapper.get_devices(exclude_loopback=True)
  2016-04-21 16:22:17.771 23382 TRACE neutron.agent.l3.router_info   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/ip_lib.py", line 102, in 
get_devices
  2016-04-21 16:22:17.771 23382 TRACE neutron.agent.l3.router_info 
log_fail_as_error=self.log_fail_as_error
  2016-04-21 16:22:17.771 23382 TRACE neutron.agent.l3.router_info   File 
"/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 137, in 
execute

[Group.of.nepali.translators] [Bug 1630789] Please test proposed package

2016-11-04 Thread Andy Whitcroft

Hello Tyler, or anyone else affected,

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

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

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

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

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

** Changed in: snap-confine (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  normal users can't run snaps inside of LXD containers

Status in Snappy Launcher:
  Fix Released
Status in Snappy:
  In Progress
Status in snap-confine package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in snap-confine source package in Xenial:
  Fix Committed
Status in snap-confine source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  TBD

  [Test Case]

  Look below for a test case.

  [Regression Potential]

  TBD

  [Other Info]

  * snap-confine is technically an integral part of snapd which has an
  SRU exception and is allowed to introduce new features and take
  advantage of accelerated procedure. For more information see
  https://wiki.ubuntu.com/SnapdUpdates

  == # Pre-SRU bug description follows # ==

  The kernel (4.8.0-19.21), apparmor (2.10.95-4ubuntu5), and lxd
  (2.4-0ubuntu1) needed for running snaps inside of LXD containers (bug
  #1611078) have all landed in Yakkety. We should be able to install
  squashfuse and snapd 2.16+16.10 (from yakkety-proposed) and then run
  snaps inside of unprivileged LXD containers.

  I have verified that it works well for the root user inside of the
  container but there are some issues when a normal user attempts to run
  a snap command.

  # Create yakkety container named "yakkety"
  tyhicks@host:~$ lxc launch ubuntu-daily:devel yakkety
  Creating yakkety
  Starting yakkety

  # Enter the container, enable yakkety-proposed, update, install the 
dependencies
  tyhicks@host:~$ lxc exec yakkety bash
  root@yakkety:~# echo "deb http://archive.ubuntu.com/ubuntu/ \
  yakkety-proposed restricted main multiverse universe" > \
  /etc/apt/sources.list.d/proposed.list
  root@yakkety:~# echo -e "Package: *\nPin: release a=yakkety-proposed\n\
  Pin-Priority: 400" > /etc/apt/preferences.d/proposed-updates
  root@yakkety:~# apt-get update && apt-get dist-upgrade -y
  ...
  root@yakkety:~# apt-get install -y squashfuse snapd/yakkety-proposed
  ...

  # Rebooting the container should not be needed but is done for completeness
  root@yakkety:~# reboot
  tyhicks@host:~$ lxc exec yakkety bash

  # Install the hello-world snap
  root@yakkety:~# snap install hello-world
  hello-world (stable) 6.3 from 'canonical' installed

  # Snap commands work fine as root inside the container but not as a normal 
user
  root@yakkety:~# /snap/bin/hello-world.env
  SNAP_USER_COMMON=/root/snap/hello-world/common
  ...
  root@yakkety:~# su - ubuntu -c '/snap/bin/hello-world.env'
  internal error, please report: running "hello-world.env" failed: open 
/snap/hello-world/27/meta/snap.yaml: permission denied

  # The normal user can't access /snap/hello-world/27 because of some oddness 
with the
  # dentry
  root@yakkety:~# ls -al /snap/hello-world
  total 8
  drwxr-xr-x 3 root root 4096 Oct  5 21:09 .
  drwxr-xr-x 5 root root 4096 Oct  5 21:09 ..
  drwxrwxr-x 4 root root0 Jul 11 21:20 27
  lrwxrwxrwx 1 root root2 Oct  5 21:09 current -> 27
  root@yakkety:~# su - ubuntu -c 'ls -al /snap/hello-world'
  ls: cannot access '/snap/hello-world/27': Permission denied
  total 8
  drwxr-xr-x 3 root root 4096 Oct  5 21:09 .
  drwxr-xr-x 5 root root 4096 Oct  5 21:09 ..
  d? ? ??   ?? 27
  lrwxrwxrwx 1 root root2 Oct  5 21:09 current -> 27

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-confine/+bug/1630789/+subscriptions

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

[Group.of.nepali.translators] [Bug 1633274] Re: Systemd-networkd crashes with core dump

2016-11-04 Thread Launchpad Bug Tracker

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

---
systemd (229-4ubuntu12) xenial; urgency=medium

  * unit: sent change signal before removing the unit if necessary
(LP: #1632964)
  * networkd: Fix assertion crash on adding VTI with IPv6 addresses
(LP: #1633274)
  * systemd-networkd-resolvconf-update.service: Propagate search domains
(LP: #1635256)

 -- Martin Pitt   Wed, 26 Oct 2016 13:18:42
+0200

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

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

Title:
  Systemd-networkd crashes with core dump

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  Systemd-networkd crashes with core dump, this happends in Yakkety and
  Xenial.

  The latest patch that was commited to Xenial-updates and Yakkety is the one 
that broke this.
  Everything works just fine with Xenial without latest update or Yakkety Beta 
2.

  The log entries i see is:
  Oct 14 02:37:42 Router01 systemd-networkd[3402]: Assertion 't' failed at 
../src/network/networkd-netdev-tunnel.c:210, function 
netdev_vti_fill_message_key(). Aborting.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Main process 
exited, code=dumped, status=6/ABRT
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered 
failed state.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with 
result 'core-dump'.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Service has no 
hold-off time, scheduling restart.
  Oct 14 02:37:42 Router01 systemd[1]: Stopped Network Service.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Start request 
repeated too quickly.
  Oct 14 02:37:42 Router01 systemd[1]: Failed to start Network Service.
  Oct 14 02:37:42 Router01 systemd[1]: Dependency failed for Wait for Network 
to be Configured.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd-wait-online.service: 
Job systemd-networkd-wait-online.service/start failed with result 'dependency'.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered 
failed state.
  Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with 
result 'start-limit-hit'.

  
  SRU TEST CASE: See 
https://github.com/systemd/systemd/issues/4371#issuecomment-253697041

  Regression potential: Very low, this just fixes an obvious type cast
  in networkd and touches no code that applies to other network
  interfaces. The service manager (pid 1) and other tools are entirely
  unaffected.


  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 14 02:39:05 2016
  InstallationDate: Installed on 2016-10-13 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic 
root=/dev/mapper/hostname--vg-root ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd06/11/2012:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1633274/+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 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

2016-11-04 Thread Launchpad Bug Tracker

This bug was fixed in the package systemd - 231-9ubuntu1

---
systemd (231-9ubuntu1) yakkety; urgency=medium

  * debian/gbp.conf: Switch to yakkety branch
  * unit: sent change signal before removing the unit if necessary
(LP: #1632964)
  * networkd: Fix assertion crash on adding VTI with IPv6 addresses
(LP: #1633274)

 -- Martin Pitt   Wed, 26 Oct 2016 13:11:33
+0200

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

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

Title:
  Regression: systemd does not send all queued DBus Signals when a unit
  gets inactive

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  Since the penultimate systemd package update in september
  (229-4ubuntu8) systemd does not send the remaining queued DBus signals
  (e.g. PropertiesChanged) when a unit's state changes to inactive.

  Sending those signals has been working since the release of Ubuntu
  16.04 and it is quite unfortunate for my use case this got broken
  while fixing another bug.

  Adding this upstream change to the package restores the old
  functionality (a patch for the current systemd package (systemd
  229-4ubuntu10) for xenial is attached):
  
https://github.com/systemd/systemd/commit/0dd99f86addd1f81e24e89807b6bc4aab57d5793

  SRU TEST CASE: See comment #8
  Regression potential: Low; the patch only widens the condition when a change 
signal is sent, thus at most clients would now get more D-Bus signals than 
before (in particular, the missing one at becoming inactive).

  
  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  
  package version: systemd 229-4ubuntu10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1632964/+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 1635256] Re: [xenial] search domains in networkd do not get propagated to resolvconf

2016-11-04 Thread Launchpad Bug Tracker

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

---
systemd (229-4ubuntu12) xenial; urgency=medium

  * unit: sent change signal before removing the unit if necessary
(LP: #1632964)
  * networkd: Fix assertion crash on adding VTI with IPv6 addresses
(LP: #1633274)
  * systemd-networkd-resolvconf-update.service: Propagate search domains
(LP: #1635256)

 -- Martin Pitt   Wed, 26 Oct 2016 13:18:42
+0200

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

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

Title:
  [xenial] search domains in networkd do not get propagated to
  resolvconf

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

Bug description:
  Search domains specified in networkd do not get propagated to
  /etc/resolv.conf via resolved in xenial, as systemd-networkd-
  resolvconf-update.service only tells resolvconf about DNS servers.
  This is not an issue any more in yakkety and zesty as that uses
  resolved and that unit is gone.

  This was uncovered while working on adding nameserver support to
  netplan, in bug 1626617. To fully support netplan/networkd in xenial
  we should fix this.

  SRU TEST CASE:
   * Start a xenial VM or container, and  create a networkd interface with a 
DNS server and search domain:

  $ cat /etc/systemd/network/foo.netdev
  [NetDev]
  Name=foo
  Kind=dummy

  $ cat /etc/systemd/network/foo.network
  [Match]
  Name=foo

  [Network]
  DNS=1.2.3.4
  Domains=kitchen cellar

   * sudo systemctl restart systemd-networkd

   * cat /etc/resolv.conf

  resolv.conf should have "nameserver 1.2.3.4" (unless there already are
  three nameservers), but with the current xenial version it lacks
  "search kitchen cellar". With the -proposed version, both entries
  should be there.

  REGRESSION POTENTIAL: This makes the shell hack of systemd-networkd-
  resolvconf-update.service even worse, so errors in it could break the
  existing "nameserver" integration of networkd with resolved. On xenial
  this is only really relevant with netplan and snappy (see bug
  1626617), so the number of installations that actually use this in the
  field should be low. But this is simple enough to test in isolation,
  systemd's autopkgtest already cover the "nameserver" resolvconf
  integration, and netplan's autopkgtest now cover both "nameserver" and
  "search". So overall the regression potential is very limited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635256/+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 1635155] Re: ubuntu-release-upgrader crashed with AttributeError: 'ReleaseNotesViewerWebkit' object has no attribute '_on_navigation_policy_decision_requested'

2016-11-04 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-release-upgrader - 1:16.10.8

---
ubuntu-release-upgrader (1:16.10.8) yakkety-proposed; urgency=medium

  * data/DistUpgradeQuirks.py: configure the quirk which installs the linux
metapackage to run for every release upgrade. (LP: #1633903)
  * data/DistUpgrade.cfg: add ubuntkylin-desktop to the list of supported
metapkgs. (LP: #1632665)
  * DistUpgrade/ReleaseNotesViewerWebkit.py: fix indentation of function
_on_navigation_policy_decision_requested. (LP: #1635155)

 -- Brian Murray   Tue, 25 Oct 2016 12:13:12 -0700

** Changed in: ubuntu-release-upgrader (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  ubuntu-release-upgrader crashed with AttributeError:
  'ReleaseNotesViewerWebkit' object has no attribute
  '_on_navigation_policy_decision_requested'

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
  In Progress
Status in ubuntu-release-upgrader source package in Yakkety:
  Fix Released

Bug description:
  Test Case
  -
  The function was improperly indented so was not callable given that the fix 
is straightforward we should just confirm that the new version of the package 
does not appear in the Errors Bucket.

  Regression Potential
  
  It's possible there's a coding error in the function, but this wouldn't be a 
regression since we weren't calling it all.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1635155/+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 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5

2016-11-04 Thread Launchpad Bug Tracker

This bug was fixed in the package postgresql-9.5 - 9.5.5-0ubuntu0.16.10

---
postgresql-9.5 (9.5.5-0ubuntu0.16.10) yakkety; urgency=medium

  * New upstream bug fix release (LP: #1637236)
- Fix WAL-logging of truncation of relation free space maps and visibility
  maps.
  It was possible for these files to not be correctly restored during
  crash recovery, or to be written incorrectly on a standby server. Bogus
  entries in a free space map could lead to attempts to access pages that
  have been truncated away from the relation itself, typically producing
  errors like "could not read block XXX: read only 0 of 8192 bytes".
  Checksum failures in the visibility map are also possible, if
  checksumming is enabled.

  Procedures for determining whether there is a problem and repairing it
  if so are discussed at
 https://wiki.postgresql.org/wiki/Free_Space_Map_Problems.

- Details about other changes:
  http://www.postgresql.org/docs/9.5/static/release-9-5-5.html

 -- Martin Pitt   Thu, 27 Oct 2016 17:51:11
+0200

** Changed in: postgresql-9.1 (Ubuntu Precise)
   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/1637236

Title:
  New upstream microreleases 9.1.24, 9.3.15, 9.5.5

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.5 package in Ubuntu:
  Fix Released
Status in postgresql-9.1 source package in Precise:
  Fix Released
Status in postgresql-9.1 source package in Trusty:
  Fix Released
Status in postgresql-9.3 source package in Trusty:
  Fix Released
Status in postgresql-9.5 source package in Xenial:
  Fix Released
Status in postgresql-9.5 source package in Yakkety:
  Fix Released
Status in postgresql-9.5 source package in Zesty:
  Fix Released

Bug description:
  https://www.postgresql.org/about/news/1712/

  As per the standing micro-release exception these should land in
  stable Ubuntu releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+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 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5

2016-11-04 Thread Launchpad Bug Tracker

This bug was fixed in the package postgresql-9.5 - 9.5.5-0ubuntu0.16.04

---
postgresql-9.5 (9.5.5-0ubuntu0.16.04) xenial-proposed; urgency=medium

  * New upstream bug fix release (LP: #1637236)
- Fix WAL-logging of truncation of relation free space maps and visibility
  maps.
  It was possible for these files to not be correctly restored during
  crash recovery, or to be written incorrectly on a standby server. Bogus
  entries in a free space map could lead to attempts to access pages that
  have been truncated away from the relation itself, typically producing
  errors like "could not read block XXX: read only 0 of 8192 bytes".
  Checksum failures in the visibility map are also possible, if
  checksumming is enabled.

  Procedures for determining whether there is a problem and repairing it
  if so are discussed at
 https://wiki.postgresql.org/wiki/Free_Space_Map_Problems.

- Details about other changes:
  http://www.postgresql.org/docs/9.5/static/release-9-5-5.html

 -- Martin Pitt   Thu, 27 Oct 2016 18:03:43
+0200

** Changed in: postgresql-9.5 (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  New upstream microreleases 9.1.24, 9.3.15, 9.5.5

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.5 package in Ubuntu:
  Fix Released
Status in postgresql-9.1 source package in Precise:
  Fix Released
Status in postgresql-9.1 source package in Trusty:
  Fix Released
Status in postgresql-9.3 source package in Trusty:
  Fix Released
Status in postgresql-9.5 source package in Xenial:
  Fix Released
Status in postgresql-9.5 source package in Yakkety:
  Fix Released
Status in postgresql-9.5 source package in Zesty:
  Fix Released

Bug description:
  https://www.postgresql.org/about/news/1712/

  As per the standing micro-release exception these should land in
  stable Ubuntu releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+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 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5

2016-11-04 Thread Launchpad Bug Tracker

This bug was fixed in the package postgresql-9.3 - 9.3.15-0ubuntu0.14.04

---
postgresql-9.3 (9.3.15-0ubuntu0.14.04) trusty-proposed; urgency=medium

  * New upstream bug fix release (LP: #1637236)
- Fix WAL-logging of truncation of relation free space maps and visibility
  maps.
  It was possible for these files to not be correctly restored during
  crash recovery, or to be written incorrectly on a standby server. Bogus
  entries in a free space map could lead to attempts to access pages that
  have been truncated away from the relation itself, typically producing
  errors like "could not read block XXX: read only 0 of 8192 bytes".
  Checksum failures in the visibility map are also possible, if
  checksumming is enabled.

  Procedures for determining whether there is a problem and repairing it
  if so are discussed at
 https://wiki.postgresql.org/wiki/Free_Space_Map_Problems

- Details about other changes:
  http://www.postgresql.org/docs/9.3/static/release-9-3-15.html

 -- Martin Pitt   Thu, 27 Oct 2016 21:20:52
+0200

** Changed in: postgresql-9.5 (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/1637236

Title:
  New upstream microreleases 9.1.24, 9.3.15, 9.5.5

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.5 package in Ubuntu:
  Fix Released
Status in postgresql-9.1 source package in Precise:
  Fix Released
Status in postgresql-9.1 source package in Trusty:
  Fix Released
Status in postgresql-9.3 source package in Trusty:
  Fix Released
Status in postgresql-9.5 source package in Xenial:
  Fix Released
Status in postgresql-9.5 source package in Yakkety:
  Fix Released
Status in postgresql-9.5 source package in Zesty:
  Fix Released

Bug description:
  https://www.postgresql.org/about/news/1712/

  As per the standing micro-release exception these should land in
  stable Ubuntu releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+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 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5

2016-11-04 Thread Launchpad Bug Tracker

This bug was fixed in the package postgresql-9.1 - 9.1.24-0ubuntu0.14.04

---
postgresql-9.1 (9.1.24-0ubuntu0.14.04) trusty-proposed; urgency=medium

  * New upstream bug fix release (LP: #1637236). No effective changes for
PL/Perl, the version must just be higher than the one in precise, to not
break upgrades.

 -- Martin Pitt   Thu, 27 Oct 2016 21:26:48
+0200

** Changed in: postgresql-9.1 (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

** Changed in: postgresql-9.3 (Ubuntu Trusty)
   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/1637236

Title:
  New upstream microreleases 9.1.24, 9.3.15, 9.5.5

Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.5 package in Ubuntu:
  Fix Released
Status in postgresql-9.1 source package in Precise:
  Fix Released
Status in postgresql-9.1 source package in Trusty:
  Fix Released
Status in postgresql-9.3 source package in Trusty:
  Fix Released
Status in postgresql-9.5 source package in Xenial:
  Fix Released
Status in postgresql-9.5 source package in Yakkety:
  Fix Released
Status in postgresql-9.5 source package in Zesty:
  Fix Released

Bug description:
  https://www.postgresql.org/about/news/1712/

  As per the standing micro-release exception these should land in
  stable Ubuntu releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1637236/+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 1443052] Re: User accounts login history showing incorrect history - patch

2016-11-04 Thread Mathew Hodson

** Changed in: gnome-control-center
   Importance: Medium => Undecided

** Changed in: gnome-control-center
   Status: Unknown => New

** Changed in: gnome-control-center
 Remote watch: GNOME Bug Tracker #762346 => None

** Project changed: gnome-control-center => ubuntu-translations

** No longer affects: ubuntu-translations

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

Title:
  User accounts login history showing incorrect history - patch

Status in accountsservice:
  Unknown
Status in Ubuntu GNOME:
  Triaged
Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Trusty:
  Fix Committed
Status in accountsservice source package in Xenial:
  Fix Committed

Bug description:
  Impact
  ---

  Logout times for users are correct if user logs off and then shutdown
  from GDM, however logout times are wrong if user shutdowns directly
  from the user session, because DEAD_PROCESS record is missing in that
  case and BOOT_TIME record is used instead.

  Therefore the logout time will be shown in the login-history (in the
  gnome-control-center) just before the next login time rather than when
  the logout actually occurred.

  Test case
  --

  1. Make sure that you have turned on and logged into the machine and
  then turned off from the user session several times with enough
  distance between them for you to tell that the timestamps are correct.

  2. Check that after applying the patch that the timestamps show the
  correct times for the logins and logouts and not what is described in
  the Impact section above.

  Regression potential
  

  I have not encountered any regressions while testing this patch.
  [bdmurray] - What could go wrong? What should a user testing this look for?

  --

  Original description:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1443052/+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 1635246] Re: linux-raspi2: 4.4.0-1030.37 -proposed tracker

[Group.of.nepali.translators] [Bug 1635247] Re: linux-snapdragon: 4.4.0-1033.37 -proposed tracker

[Group.of.nepali.translators] [Bug 1635242] Re: linux: 4.4.0-46.67 -proposed tracker

[Group.of.nepali.translators] [Bug 1639381] Re: SRU 0.11 tracking bug

[Group.of.nepali.translators] [Bug 1639381] [NEW] SRU 0.11 tracking bug

[Group.of.nepali.translators] [Bug 1044662] Re: compiz crashed with signal 5 (SIGTRAP) in g_logv() from g_log() from g_settings_schema_get_value() from g_settings_schema_key_init() from g_settings_get

[Group.of.nepali.translators] [Bug 1073488] Re: window management - if a window is always on top, it will always get focus after switching between workspaces

[Group.of.nepali.translators] [Bug 1582430] Re: spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is already playing music

[Group.of.nepali.translators] [Bug 1606254] Re: Super+S activates expo plugin even on a 1x1 setup

[Group.of.nepali.translators] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Group.of.nepali.translators] [Bug 1573073] Re: When router has no ports _process_updated_router fails because the namespace does not exist

[Group.of.nepali.translators] [Bug 1630789] Please test proposed package

[Group.of.nepali.translators] [Bug 1633274] Re: Systemd-networkd crashes with core dump

[Group.of.nepali.translators] [Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

[Group.of.nepali.translators] [Bug 1635256] Re: [xenial] search domains in networkd do not get propagated to resolvconf

[Group.of.nepali.translators] [Bug 1635155] Re: ubuntu-release-upgrader crashed with AttributeError: 'ReleaseNotesViewerWebkit' object has no attribute '_on_navigation_policy_decision_requested'

[Group.of.nepali.translators] [Bug 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5

[Group.of.nepali.translators] [Bug 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5

[Group.of.nepali.translators] [Bug 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5

[Group.of.nepali.translators] [Bug 1637236] Re: New upstream microreleases 9.1.24, 9.3.15, 9.5.5

[Group.of.nepali.translators] [Bug 1443052] Re: User accounts login history showing incorrect history - patch

21 matches

Site Navigation

Mail list logo

Footer information