[Group.of.nepali.translators] [Bug 1990450] Re: Show potential Ubuntu Pro updates and apt news messages

[Sebastien Bacher]

@Chris, you are right, the focal SRU including those changes moved to
updates, Brian changed the status back to 'fix commited' in comment #94
probably because the .changes included more entries that it should have.
I'm setting focal back to fix released and the new .changes from .20 is
correct to not include a reference to this bug


** Changed in: update-manager (Ubuntu Focal)
   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/1990450

Title:
  Show potential Ubuntu Pro updates and apt news messages

Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Committed
Status in update-manager source package in Bionic:
  Fix Committed
Status in update-manager source package in Focal:
  Fix Released
Status in update-manager source package in Jammy:
  Fix Released
Status in update-manager source package in Kinetic:
  Fix Released
Status in update-manager source package in Lunar:
  Won't Fix
Status in update-manager source package in Mantic:
  Won't Fix
Status in update-manager source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Show the Ubuntu Pro (aka Ubuntu Advantage) updates that would be enabled if 
you attached this machine. This information is not currently shown.

  The new revision also update the reference to the Software Properties'
  Livepatch tab which doesn't exist anymore since bug #2003527 and was
  replaced by Ubuntu Pro.

  There is also a new section 'News' showing the apt-news messages if
  there are any available and some layout changes to accommodate for the
  new section

  [Test Case]
  1. Do fresh install of Ubuntu with available updates
  2. Check there are updates available by running:
  $ pro security-status
  Note that updates are only available for older LTS releases.
  If there are no Pro specific updates available, install any package listed in 
https://esm.ubuntu.com/apps/ubuntu/dists/jammy-apps-security/main/binary-amd64/Packages
 (without attaching your machine!)
  3. Open update-manager

  -> There should be a 'Ubuntu Pro security updates (Enable in
  Settings...)' section at the bottom of the updates list showing
  disabled and including under it the name of the packages that would be
  available if pro was enabled

  4. start software-properties, go to the ubuntu pro tab and attach to a pro 
account
  5. close software-properties and restart update-manager

  -> There should be a 'Ubuntu Pro security updates' section at the
  bottom of the updates list showing enabled and including under it
  packages updated provided by pro that can be installed

  6. Check the top of the update-manager dialog

  If there is a message available on the server
  $ curl https://motd.ubuntu.com/aptnews.json
  with a timestamp older than one month

  then a 'news' section should be displayed including the message

  if there isn't a recent post on the server it can be tested locally
  with the steps from #31

  [Regression Potential]
  Possibility of introducing new bugs.

  The new livepatch->ubuntu pro string change will not be translated
  until the next language pack refresh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1990450/+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 2029473] Re: Backport Ubuntu Pro to Xenial

[Sebastien Bacher]

** Description changed:

+ * Impact
+ 
+ We want desktop integration with Ubuntu Pro
+ 
+ * Test case
+ 
+ - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
+ $ pro status
+ and `$ pro detach` if needed
+ 
+ - $ software-properties-gtk
+ -> the list of tabs should include an 'Ubuntu Pro' one
+ 
+ The Ubuntu Pro tab should state 'This machine is not covered by an
+ Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have
+ other controls inactive
+ 
+ - click 'Enable Ubuntu Pro'
+ -> A dialog 'Enable Ubuntu Pro' opens
+ -> the first option 'Enter code on ubuntu.com/pro/attach' is selected
+ -> a pincode is displayed under the option
+ 
+ - go to http//ubuntu.com/pro/attach and enter the pincode
+ -> after some seconds the software-properties UI should update and display a 
green mark and 'Valid token' label on the right of the pincode
+ 
+ - click 'Confirm'
+ -> you should get an authentification prompt
+ 
+ - enter your password
+ -> a spinner starts animating instead of the 'Valid token' label
+ -> once the attachment job is done the dialog is autoclosed
+ -> the UI should now state 'Ubuntu Pro support is enabled', under Security 
'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled
+ (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools)
+ 
+ - check that the '$ pro status' output matches the UI one
+ 
+ - try enabling/disable options
+ -> verify that the 'pro status' change accordingly
+ 
+ - Click 'Disable Ubuntu Pro'
+ -> you get asked for confirmation and password
+ -> confirm that the UI is back to the original state and that 'pro status' 
confirm the system isn't attached to Ubuntu Pro anymore
+ 
+ - Go through the testcase again but selecting the 'Or add token
+ manually' option, the steps should be similar
+ 
+ * Regression Potential
+ 
+ There could be problems in the UI
+ The new service could be not working as expected
+ Strings are new and currently have no translations
+ 
+ The livepatch checkbox is also inactive because the current update-
+ notifier version in xenial doesn't include livepatch support
+ 
+ 
+ -
+ 
  Ubuntu Pro enables extended support for 10 years for long term support
  Ubuntu series. Xenial is therefore currently also supported under Ubuntu
  Pro.
  
  Xenial's software-properties-gtk, however, doesn't have the Ubuntu Pro
  functionality that exists in Bionic, Focal etc.
  
  Thus this request to backport the Ubuntu Pro functionality to Xenial.
  
  This depends on LP:2029089.

** Changed in: software-properties (Ubuntu)
   Status: New => Fix Released

** Changed in: software-properties (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/2029473

Title:
  Backport Ubuntu Pro to Xenial

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  Fix Committed

Bug description:
  * Impact

  We want desktop integration with Ubuntu Pro

  * Test case

  - ensure that the machine isn't attached to ubuntu pro (otherwise the screen 
would not be displayed) and is online
  $ pro status
  and `$ pro detach` if needed

  - $ software-properties-gtk
  -> the list of tabs should include an 'Ubuntu Pro' one

  The Ubuntu Pro tab should state 'This machine is not covered by an
  Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and
  have other controls inactive

  - click 'Enable Ubuntu Pro'
  -> A dialog 'Enable Ubuntu Pro' opens
  -> the first option 'Enter code on ubuntu.com/pro/attach' is selected
  -> a pincode is displayed under the option

  - go to http//ubuntu.com/pro/attach and enter the pincode
  -> after some seconds the software-properties UI should update and display a 
green mark and 'Valid token' label on the right of the pincode

  - click 'Confirm'
  -> you should get an authentification prompt

  - enter your password
  -> a spinner starts animating instead of the 'Valid token' label
  -> once the attachment job is done the dialog is autoclosed
  -> the UI should now state 'Ubuntu Pro support is enabled', under Security 
'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled
  (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools)

  - check that the '$ pro status' output matches the UI one

  - try enabling/disable options
  -> verify that the 'pro status' change accordingly

  - Click 'Disable Ubuntu Pro'
  -> you get asked for confirmation and password
  -> confirm that the UI is back to the original state and that 'pro status' 
confirm the system isn't attached to Ubuntu Pro anymore

  - Go through the testcase again but selecting the 'Or add token
  manually' option, the steps 

[Group.of.nepali.translators] [Bug 1769991] Re: [16.04] Unable to import OpenVPN configuration into Network Manager

[Sebastien Bacher]

** Changed in: network-manager-openvpn (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: network-manager-openvpn (Ubuntu Xenial)
   Importance: Undecided => Low

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

Title:
  [16.04] Unable to import OpenVPN configuration into Network Manager

Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager-openvpn source package in Xenial:
  Won't Fix

Bug description:
  In 16.04, it is currently not possible to import OpenVPN
  configurations.  Specifically, imports fail with the error of:

  The file 'filename.ovpn' could not be read or does not contain
  recognized VPN connection information.

  Error: Key file contains line 'client' which is not a key-value pair,
  group, or comment.

  --

  An example configuration that fails to import is as follows (with some
  critical components excluded, like a proper remote address, or a
  proper x509 name); this is a config that otherwise works with a Sophos
  XG Firewall-based SSL VPN system

  client
  dev tun
  persist-tun
  persist-key
  proto tcp
  verify-x509-name ""
  route remote_host 255.255.255.255 net_gateway
  resolv-retry infinite
  remote 1.2.3.4 8443 tcp
  ca ca.crt
  cert client.crt
  key client.key
  auth-user-pass
  cipher AES-256-CBC
  auth SHA512
  comp-lzo no
  route-delay 4
  verb 3
  reneg-sec 0

  --

  This same exact configuration works with a direct call of `openvpn
  ./filename.ovpn`.

  Why Network Manager is unable to parse or import the OpenVPN
  configuration is beyond my ability to comprehend.

  Note that the same configuration made by hand in the new VPN window
  works fine, but the import function fails.  (Which is a pretty severe
  bug)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-openvpn 1.1.93-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  8 14:59:54 2018
  InstallationDate: Installed on 2016-12-20 (503 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1769991/+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 1880832] Re: [SRU] backport wslu 2.3.6-0ubuntu1 to all current supported releases

[Sebastien Bacher]

** Changed in: wslu (Ubuntu Bionic)
   Status: New => Won't Fix

** Changed in: wslu (Ubuntu Xenial)
   Status: New => Won't Fix

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

Title:
  [SRU] backport wslu 2.3.6-0ubuntu1 to all current supported releases

Status in wslu package in Ubuntu:
  Fix Released
Status in wslu source package in Xenial:
  Won't Fix
Status in wslu source package in Bionic:
  Won't Fix
Status in wslu source package in Eoan:
  Won't Fix

Bug description:
  [Impact]

  The package is already released in focal/groovy but it still affects
  eoan/bionic/xenial, a SRU is needed.

  [Test Case]

   * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates
   * Run the autopktest in a WSL environment where the user name contains space.
   * Verify the other individual bugs fixed by the SRU.

  [Regression Potential]

  * There is a issue on #1877016 which is already addressed in the next
  release, but I hope to SRU the current packages in order to prevent
  future issues when SRUing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1880832/+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 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable

[Sebastien Bacher]

** Changed in: wslu (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

** Changed in: wslu (Ubuntu Bionic)
   Status: Confirmed => Won't Fix

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

Title:
  ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env
  variable

Status in wslu package in Ubuntu:
  Fix Released
Status in wslu source package in Xenial:
  Won't Fix
Status in wslu source package in Bionic:
  Won't Fix
Status in wslu source package in Focal:
  Fix Released
Status in wslu source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This affects all wslu tools on all releases. When PATH do not include
  Windows path, the all tools will complain that reg.exe is not found.

  [Test Case]

   * Add appendWindowsPath = false under [interop] section in /etc/wsl.conf 
file, and restart the distribution
   * run any wslu tool (like wslfetch)
   * "/mnt/c/Windows/System32/reg.exe: Permission denied" should not be shown

  [Regression Potential]

  * For future release of wslu 3.1.0 proposed, huge refactoring will be
  needed.

  [Original Bug Report]

  ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env
  variable

  $ wslfetch
  /usr/bin/wslfetch: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 108: reg.exe: command not found
  /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied
  /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied

    ./+o+-  Windows 10 Linux Subsystem
    y. 'yy+ rafaeldtinoco@lenovo
    .;//+/h yyo BUILD:
     .++ .:/++/-.`sss/` BRANCH:
   .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS
  o:+o+:++. `'-/ooo+\   KERNEL: Linux 4.4.0-18362-Microsoft
     .:+o:+o/.  `+sssooo+\  UPTIME: 0d 2h 6m
    .++/+ +oo+o:` \sssooo;
   /+++//+: oo+o
   \+/+o+++ o++o   ydddhh+
    .++.o+ +oo+:` /dddhhh;
     .+.o+oo:.   odd+
  \+.++o+o` -.:ohdh+
   `:o+++  oyo++os:
     .o: .syhhh'.oo++o.
     /osyyy.+++\
     ` +oo+++o:/
    `oo++'`

  After :

  echo $PATH
  
/snap/bin:/snap/sbin:/mnt/c/windows/system32/:/home/rafaeldtinoco/work/sources/upstream/ubuntu-dev-tools/:/usr/lib/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/home/rafaeldtinoco/work/sources/bzr/ubuntu-archive-tools:/home/rafaeldtinoco/work/sources/upstream/lxd/bin:.

  $ wslfetch

    ./+o+-  Windows 10 Linux Subsystem
    y. 'yy+ rafaeldtinoco@lenovo
    .;//+/h yyo BUILD:18363
     .++ .:/++/-.`sss/` BRANCH:   19h1_release
   .:++o: `\/:---:/-RELEASE:  Ubuntu 20.04 LTS
  o:+o+:++. `'-/ooo+\   KERNEL:   Linux 4.4.0-18362-Microsoft
     .:+o:+o/.  `+sssooo+\  UPTIME:   0d 2h 19m
    .++/+ +oo+o:` \sssooo;
   /+++//+: oo+o
   \+/+o+++ o++o   ydddhh+
    .++.o+ +oo+:` 

[Group.of.nepali.translators] [Bug 1883920] Re: ubuntu logo in wslfetch needs update

[Sebastien Bacher]

** Changed in: wslu (Ubuntu Bionic)
   Status: New => Won't Fix

** Changed in: wslu (Ubuntu Xenial)
   Status: New => Won't Fix

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

Title:
  ubuntu logo in wslfetch needs update

Status in wslu package in Ubuntu:
  Fix Released
Status in wslu source package in Xenial:
  Won't Fix
Status in wslu source package in Bionic:
  Won't Fix
Status in wslu source package in Focal:
  Fix Released
Status in wslu source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This affects all wslu tools on all releases. The Ubuntu branding is
  the outdated version:
  https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-1814.png

  [Test Case]

   * Install Ubuntu WSL and install this fix.
   * run wslfetch command.
   * new logo should be shown like the following: 
https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-18111946.png

  [Regression Potential]

  * This patch just update the logo of wslfetch to the proper current
  Ubuntu logo. Potential regressions would be a result of the patch
  having typo that caused error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883920/+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 1883924] Re: Ubuntu.exe will not be detected properly if other LTS version is installed

[Sebastien Bacher]

** Changed in: wslu (Ubuntu Xenial)
 Assignee: Patrick Wu (callmepk) => (unassigned)

** Changed in: wslu (Ubuntu Bionic)
 Assignee: Patrick Wu (callmepk) => (unassigned)

** Changed in: wslu (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: wslu (Ubuntu Bionic)
   Status: New => Won't Fix

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

Title:
  Ubuntu.exe will not be detected properly if other LTS version is
  installed

Status in wslu package in Ubuntu:
  Fix Released
Status in wslu source package in Xenial:
  Won't Fix
Status in wslu source package in Bionic:
  Won't Fix
Status in wslu source package in Focal:
  Fix Released
Status in wslu source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This affects all wslu tools on all releases when using from the Ubuntu
  app from Microsoft Store. When other LTS version of app is installed
  from Microsoft Store, baseexec generated by wslu on Ubuntu app will
  not be using ubuntu.exe but other LTS release apps (such as
  ubuntu1804.exe)

  [Test Case]

   * Install Ubuntu and Ubuntu 18.04 LTS from Microsoft Store.
   * run any wslu tools (like wslfetch --help)
   * Verify that ~/.config/wslu/baseexec contains the path to ubuntu.exe

  [Regression Potential]

  This patch will try to regenerate  ~/.config/wslu/baseexec when trying
  to execute any wslu commands (like wslfetch). Potential regressions
  would be a result of  ~/.config/wslu/baseexec not regenerated
  properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883924/+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 1431513] Re: Properly handle dismissal of first run shortcut overlay

[Sebastien Bacher]

** Changed in: unity (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity (Ubuntu Xenial)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

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

Title:
  Properly handle dismissal of first run shortcut overlay

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity source package in Xenial:
  Won't Fix

Bug description:
  A stop gap workaround has been put in place for bug #1313597, but the
  proper fix is to use the input::Monitor when it merges.  See
  https://code.launchpad.net/~3v1n0/unity/lockscreen-grabbing

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1431513/+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 1322769] Re: 14.04 LTS AMD64 Password/Keyboard Lockup after Unity Lock Timeout with VirtualBox VMs Running

[Sebastien Bacher]

** Changed in: unity (Ubuntu)
   Status: In Progress => Confirmed

** Changed in: unity (Ubuntu Xenial)
   Status: In Progress => Confirmed

** Changed in: unity
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity/7.2
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity (Ubuntu Xenial)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

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

Title:
  14.04 LTS AMD64 Password/Keyboard Lockup after Unity Lock Timeout with
  VirtualBox VMs Running

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Confirmed
Status in unity source package in Xenial:
  Won't Fix

Bug description:
  I have replicated this bug on two different laptops, one at work
  running mulitple monitors, one at home running a single monitor.

  Symptom: When the Unity System Settings Lock Screen Settings activate,
  and I notice the screen has gone blank and locked, I re-activate the
  keyboard (usually left CRTL) and the 14.04 LTS Login Screen appears.

  In all cases the keyboard is locked out and non-responsive, I can
  click on the password box for my account and anything I type no longer
  appears. I have to select "Switch Account" option with the mouse to
  get a new login screen for my account and I can log in.

  In some cases both the keyboard and the mouse input is locked out and
  non-responsive. I can not select "Switch Account" and must power off
  the laptop which of course is dangerous for the file systems of both
  Windows VMs that are running and the host/14.04 LTS file system.  I
  have already corrupted the Windows VM file systems and had to repair
  while testing this bug for repeatability.

  Both laptops run the AMD64 version of Ubuntu 14.04 LTS.
  Both have built in Intel Integrated Graphics, one laptop with the older 
Ironlake, one with the newer ivy bridge.

  Both are running Oracle VirtualBox but different version:

  1. Home is running the Ubuntu 14.04 Repository version of Oracle VirtualBox 
(Currently 4.3.10_Ubuntu r93012)
  2. Work is running the Oracle downloadable AMD64 version of Oracle VirtualBox 
Currently 4.3.12
  3. Both have the respective Oracle Virtual Box Extensions installed for 
4.3.10 and 4.3.12
  3. Both are running Windows 7 64 VMs

  Both 14.04 LTS have the following System Settings for Lock Screen:
  Brightness slider - All the way left
  Dim screen to save power - Checked
  Lock - Switch to ON position
  Lock Screen after: 5 minutes
  Require my password when weking form suspend - Checked

  
  I have tested this with both a VM running (no other running applications were 
tested) and with no apps running (fresh boot and login into 14.04 LTS unity 
desktops).

  1. On fresh boot with no apps running the lock screen activates (after
  5 min of no activity) and when I re-activate the laptops (usually
  pressing left CTRL on keyboard) I get the login screen and can enter
  my password successfully and the Unity desktop is presented.

  2. On fresh boot with a Windows 7 VM running the lock screen activates
  (after 5 min of no activity) and when I re-activate the laptops
  (usually pressing the left CTRL on the keyboard) I get the login
  screen and the keyboard is locked and non-responsive and I can not log
  into my account.

  Variations on 2. I can not enter password but I can use CTRL-ALT-F1, etc. to 
switch to TTY and gain access to system.
  Variations on 2. I can not enter password and can not use CTRL-ALT-F1, etc. 
the entire keyboard appears locked out, but I can use mouse and select Switch 
Account to force a new login screen to appear and the keyboard now works to 
enter password.
  Variations on 2. I can not enter password and can not use CTRL-ALT-F1, etc. 
and I can not use the mouse, the entire input interfaces appear locked out and 
I have to power off the laptops to restart and be able to log in to Unity again.

  If I turn Lock: Off but leave Turn Screen off when inactive for 5
  minutes set. If I have a VM running or no apps running, after 5
  minutes the screen dims. I re-activate the system by pressing a key on
  the keyboard (usually the left CTRL key) and the Unity desktop re-
  appears.

  This bug only seems to occur when the Lock/Require Password when
  waking from suspend is active.

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


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

[Group.of.nepali.translators] [Bug 1366801] Re: Border in count emblem in alt+tab switcher is misaligned

[Sebastien Bacher]

** Changed in: unity (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

** Changed in: unity
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** Changed in: unity (Ubuntu Xenial)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

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

Title:
  Border in count emblem in alt+tab switcher is misaligned

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity source package in Xenial:
  Won't Fix

Bug description:
  See the attached screenshot, there seems to be a shift of the emblem
  background, as well as vertical misalignment of the text.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140904-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Sep  8 14:59:38 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1366801/+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 918489] Re: duplicity allows a new, different passphrase if an archive cache exists

[Sebastien Bacher]

Upstream closed the duplicity task without details so let's assume it's
fixed in the current version and Ubuntu serie

** Changed in: duplicity (Ubuntu Yakkety)
   Status: Confirmed => Won't Fix

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

** Changed in: deja-dup (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: deja-dup (Ubuntu Bionic)
   Status: New => Triaged

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

** Changed in: duplicity (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

** Changed in: duplicity (Ubuntu Bionic)
   Status: New => Won't Fix

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

Title:
  duplicity allows a new, different passphrase if an archive cache
  exists

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released
Status in deja-dup source package in Trusty:
  Fix Released
Status in duplicity source package in Trusty:
  Won't Fix
Status in deja-dup source package in Xenial:
  Fix Released
Status in duplicity source package in Xenial:
  Won't Fix
Status in deja-dup source package in Yakkety:
  Fix Released
Status in duplicity source package in Yakkety:
  Won't Fix
Status in deja-dup source package in Bionic:
  Triaged
Status in duplicity source package in Bionic:
  Won't Fix

Bug description:
  when doing a backup for the first time, dejadup verifies your
  passphrase by having you enter it twice.

  on future incremental backups it doesn't need to do this because
  entering the wrong password will result in the backup failing.

  with the periodic 'full' backups that happen from time to time,
  however, any password will be accepted.

  this can lead to a situation where you accidentally type the wrong
  password once and are left in a situation where you don't know what
  you typed and have no way to get your files (or do another incremental
  backup on top of it).

  i think this is what happened to me recently.

  clearly, the fix is to explicitly verify the passphrase is correct
  when doing a new full backup.  this may be a duplicity bug.

  === Ubuntu deja-dup SRU information ===

  [impact]
  Users may unwittingly re-set their backup password and not be able to restore 
their data.

  [test case]
  - $ deja-dup-preferences # set up a dummy backup
  - $ deja-dup --backup # complete first encrypted full backup
  - $ rename 's/\.2016/\.2000/' /path/to/test/backup/*
  - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/*
  - $ deja-dup --backup # second backup, enter the wrong password
  - $ deja-dup --restore # try to restore with original password

  [regression potential]
  Should be limited?  The fix is to delete the duplicity cache files, which 
ought to be safe to delete.

  It's possible if a full backup is being resumed, we might delete the
  current progress.  That is a better bug to have than this bug, though.
  A more complicated patch would need to be investigated to prevent
  that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/918489/+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 1934199] Re: Switch from Livepatch service to UA client

[Sebastien Bacher]

** Changed in: software-properties (Ubuntu Hirsute)
   Status: New => Won't Fix

** Changed in: software-properties (Ubuntu Bionic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: software-properties (Ubuntu Xenial)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Switch from Livepatch service to UA client

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Hirsute:
  Won't Fix
Status in software-properties source package in Impish:
  Won't Fix

Bug description:
  software-properties currently uses a HTTP over Unix domain socket
  service from the livepatch snap to get the status and enable/disable
  it. This service is being deprecated with the 'ua' command line tool
  now providing this functionality. software-properties also installed
  the snap to gain access to this service. This is no longer required as
  the 'ua' tool does this.

  (*) The Livepatch service is a HTTP over Unix domain service running
  on livepatchd.sock inside the livepatch snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+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 1934199] Re: Switch from Livepatch service to UA client

[Sebastien Bacher]

it's not going to be ready for impish

** Changed in: software-properties (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  Switch from Livepatch service to UA client

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Hirsute:
  New
Status in software-properties source package in Impish:
  Won't Fix

Bug description:
  software-properties currently uses a HTTP over Unix domain socket
  service from the livepatch snap to get the status and enable/disable
  it. This service is being deprecated with the 'ua' command line tool
  now providing this functionality. software-properties also installed
  the snap to gain access to this service. This is no longer required as
  the 'ua' tool does this.

  (*) The Livepatch service is a HTTP over Unix domain service running
  on livepatchd.sock inside the livepatch snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+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 1641308] Re: Partitions display wrong in gnome -disks - ok in gparted

[Sebastien Bacher]

** Changed in: parted (Ubuntu Xenial)
   Status: Triaged => Won't Fix

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

Title:
  Partitions display wrong in gnome -disks - ok in gparted

Status in parted package in Ubuntu:
  Fix Released
Status in parted source package in Xenial:
  Won't Fix
Status in parted source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  gnome-disk-utility sometime displays the wrong partitons informations

  
  * Test case

  On a system with an extended partition start gparted, close it and
  start gnome-disk-utility, the layout displayed should be correct

  
  * Regression potential
  check that partitions handling is still working correctly in g-d-u

  

  The partitions displayed by gnome-disk-utility are wrong. When i use
  gparted the partitions displayed are correct.

  The display became wrong after i deleted 1 partition from the disk
  using gnome-disk-utility.

  Here is a screenshot of the 2 tools vision of the same disk:
  http://pasteboard.co/PjWpqeNzi.png

  Here is the fdisk:
  hippo@hippo-camp:~$ sudo fdisk -l
  [sudo] password for hippo:
  Disk /dev/sdc: 465,8 GiB, 500107862016 bytes, 976773168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x1c0966b0

  Device Boot Start   End   Sectors   Size Id Type
  /dev/sdc1  *   63 758587953 758587891 361,7G  7 HPFS/NTFS/exFAT
  /dev/sdc3   758589438 903041023 144451586  68,9G  5 Extended
  /dev/sdc5   758589440 903041023 144451584  68,9G 83 Linux

  hippo@hippo-camp:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  gnome-disk-utility:
    Installed: 3.18.3.1-1ubuntu1
    Candidate: 3.18.3.1-1ubuntu1
    Version table:
   *** 3.18.3.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  gparted:
    Installed: 0.25.0-1
    Candidate: 0.25.0-1
    Version table:
   *** 0.25.0-1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  I get *very nervous* when tools that have write access to partitions
  can't display them properly.

  Good hunt
  Matt

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Nov 12 12:16:39 2016
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2016-10-11 (31 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1641308/+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 1912168] Re: please merge ppp 2.4.9 for 21.04 and then consider ipv6 default fix for SRU

[Sebastien Bacher]

Thank you for the report, we reviewed it in our team meeting but the 
description lacks details on why it should be considered as an issue important 
enough to be considered a rls issue and targetted to older series. Could you 
provide some rational on why you believe it's high importance?
Until we get more details we are rejecting the nomination since it sounds like 
a standard merge required and bugfix

** No longer affects: ppp (Ubuntu Xenial)

** No longer affects: ppp (Ubuntu Bionic)

** No longer affects: ppp (Ubuntu Focal)

** No longer affects: ppp (Ubuntu Groovy)

** Changed in: ppp (Ubuntu)
   Importance: Undecided => Low

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

** Tags removed: rls-hh-incoming
** Tags added: rls-hh-notfixing

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

Title:
  please merge ppp 2.4.9 for 21.04 and then consider ipv6 default fix
  for SRU

Status in ppp package in Ubuntu:
  Triaged

Bug description:
  Hi,
  due to this ML on devel-discuss [1] I realized that there is a new version 
that should be merged for Ubuntu 21.04 - and probably later [2] be 
considered/discussed for an SRU
  That new version is in Debian now [3] and I think it would be great to get 
that merged/synced.

  I guess ppp might be out-of-focus today, therefore per [4] I'm also
  pinging the Desktop team hoping this will help to get a look at it.

  [1]: 
https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2021-January/018916.html
  [2]: 
https://github.com/paulusmack/ppp/pull/145/commits/0678d3bf69116af58b00fbc64bd4185acb4d5c37
  [3]: https://tracker.debian.org/news/1217613/ppp-249-11-migrated-to-testing/
  [4]: http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1912168/+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 1880832] Re: [SRU] backport wslu 2.3.6-0ubuntu1 to all current supported releases

[Sebastien Bacher]

https://bugs.launchpad.net/ubuntu/+source/wslu/2.3.6-0ubuntu3

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

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

Title:
  [SRU] backport wslu 2.3.6-0ubuntu1 to all current supported releases

Status in wslu package in Ubuntu:
  Fix Released
Status in wslu source package in Xenial:
  New
Status in wslu source package in Bionic:
  New
Status in wslu source package in Eoan:
  New

Bug description:
  [Impact]

  The package is already released in focal/groovy but it still affects
  eoan/bionic/xenial, a SRU is needed.

  [Test Case]

   * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates
   * Run the autopktest in a WSL environment where the user name contains space.
   * Verify the other individual bugs fixed by the SRU.

  [Regression Potential]

  * There is a issue on #1877016 which is already addressed in the next
  release, but I hope to SRU the current packages in order to prevent
  future issues when SRUing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1880832/+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 1882244] Re: GnuTLS Session Ticket Key Vulnerability

[Sebastien Bacher]

https://launchpad.net/ubuntu/+source/gnutls28/3.6.13-4ubuntu2

** Changed in: gnutls28 (Ubuntu Groovy)
   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/1882244

Title:
  GnuTLS Session Ticket Key Vulnerability

Status in gnutls28 package in Ubuntu:
  Fix Released
Status in gnutls28 source package in Xenial:
  Invalid
Status in gnutls28 source package in Bionic:
  Invalid
Status in gnutls28 source package in Eoan:
  Fix Released
Status in gnutls28 source package in Focal:
  Fix Released
Status in gnutls28 source package in Groovy:
  Fix Released

Bug description:
  Dear Launchpad Team,

  A security vulnerability affects versions 3.x of GnuTLS:

  https://gnutls.org/security-new.html#GNUTLS-SA-2020-06-03

  I noticed this problem on Ubuntu 16 and Ubuntu 18 operating systems.
  In particular, on Ubuntu 16 last version of libgnutls30 is 3.4.10, whereas on 
Ubuntu 18 it is 3.5.18.

  Please provide an update.

  I thank you in advance.

  Kind regards,

  it0001

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1882244/+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 1604036] Re: Upgrade printer-driver-ptouch to support Brother QL-570

[Sebastien Bacher]

** Tags removed: upgrade-software-version

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

** Changed in: hwdata (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/1604036

Title:
  Upgrade printer-driver-ptouch to support Brother QL-570

Status in hwdata package in Ubuntu:
  Fix Released
Status in ptouch-driver package in Ubuntu:
  Fix Released
Status in usbutils package in Ubuntu:
  Fix Released
Status in hwdata source package in Xenial:
  New
Status in ptouch-driver source package in Xenial:
  Triaged
Status in usbutils source package in Xenial:
  New

Bug description:
  Please, upgrade printer-driver-ptouch to support Brother QL-570
  P-touch Label Printer. See https://bitbucket.org/philpem/printer-
  driver-ptouch/issues/2/negativeprint-and-cutmedia-jobend-doesnt
  (motivate maintainers of printer-driver-ptouch to bump their version
  number and release a version that supports QL-570) and also upgrade
  usbutils to include https://usb-ids.gowdy.us/read/UD/04f9/2028

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1604036/+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 1781428] Re: please enable snap mediation support

[Sebastien Bacher]

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

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

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

Title:
  please enable snap mediation support

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

Bug description:
  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.

  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all
  connected clients (snaps or not), record by classic snaps (see bug
  1787324) and record by strict mode snaps if either the pulseaudio or
  new-in-snapd-2.41 audio-record interfaces were connected. With this
  change, snapd is in a position to migrate snaps to the new audio-
  playback and audio-record interfaces and properly mediate audio
  recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-
  interface-deprecation/13418).

  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not,
  whether the pulseaudio or audio-record interfaces are connected.
  Adjusting pulseaudio in the manner does not require coordination with
  any release of snapd. It does need a newer version of snapd-glib,
  which was recently updated to 1.49 in the last SRU.

  [Test Case]

  IMPORTANT: if updating pulseaudio while the session is running, either
  need to reboot for the test or kill pulseaudio so it can restart with
  the new snap policy

  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For confined, non-snap applications:
  $ sudo apt-get install evince

  $ aa-exec -p /usr/bin/evince -- paplay
  /usr/share/sounds/alsa/Noise.wav && echo yes

  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes

  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes

  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic

  $ snap run --shell test-snapd-classic-confinement

  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)

  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  $ exit # out of snap run --shell

  For strict snaps with pulseaudio:
  $ sudo snap install test-snapd-pulseaudio --edge

  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -

  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/

  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes

  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)

  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes

  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes

  For strict snaps with audio-playback/audio-record:
  $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04
  $ sudo snap install test-snapd-audio-record --edge

  $ snap connections test-snapd-audio-record  # record not connected
  Interface   PlugSlot 

[Group.of.nepali.translators] [Bug 1570110] Re: evolution crashed with SIGSEGV, while pasting from clipboard

[Sebastien Bacher]

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

** Changed in: webkitgtk (Ubuntu Trusty)
 Assignee: Sebastien Bacher (seb128) => (unassigned)

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

Title:
  evolution crashed with SIGSEGV, while pasting from clipboard

Status in WebKit:
  Fix Released
Status in webkitgtk package in Ubuntu:
  Fix Released
Status in webkitgtk source package in Trusty:
  Won't Fix
Status in webkitgtk source package in Xenial:
  Fix Released

Bug description:
  * Impact
  some webkitgtk consumers like the evolution composer hit segfault issues

  * Test case
  - Click New > Compose Email Message
  - Enter any email address in 'To:'
  - Enter anything into 'Subject"
  - Go to any webpage, and highlight a few lines
  - Click 'ctrl c'
  - Place cursor into the body of the open Compose Message window
  - Click 'ctrl v'

  * Regression potential
  it's a webkit update so could impact other clients of the library, check that 
the html rendering in those

  

  Guys,

   Evolution on Xenial crashes most of times that I want to copy and
  paste stuff into Mail composer window.

   From what I'm seeing, if the stuff inside of the clipboard is
  formatted, with big fonts, tables, etc, it crashes.

   The workaround is to use "Diodon" to paste into Evolution without any
  formatting, or, to open an vim session on Terminal, paste into it
  first, then, copy it again from vim, and paste into Evolution, this
  way, it doesn't crash.

   Looks very easy to reproduce!

  Cheers!
  Thiago

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: evolution 3.18.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Apr 13 18:35:02 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2016-01-30 (74 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160130)
  ProcCmdline: evolution
  SegvAnalysis:
   Segfault happened at: 0x7f9bdaf3d949:cmpq   $0x0,0x18(%rax)
   PC (0x7f9bdaf3d949) ok
   source "$0x0" ok
   destination "0x18(%rax)" (0x654e2073656d696c) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libwebkitgtk-3.0.so.0
  Title: evolution crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit-open-source/+bug/1570110/+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 1831827] Re: Update to 1.48

[Sebastien Bacher]

Not going to be SRUed to cosmic which is neither nor a LTS nor the
current stable version

** Changed in: snapd-glib (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  Update to 1.48

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Xenial:
  Triaged
Status in snapd-glib source package in Bionic:
  Triaged
Status in snapd-glib source package in Cosmic:
  Won't Fix
Status in snapd-glib source package in Disco:
  Triaged
Status in snapd-glib source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  A newer snapd-glib is available that adds support for new features in snapd. 
snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates

  [Test Case]
  The reverse depends of snapd-glib should continue to function, this is 
currently:
  - gnome-software
  - gnome-initial-setup
  - pulseaudio

  [Regression Potential]
  Any new release has a risk of introducing bugs, this is mitigated by 
automatic regression tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1831827/+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 1806697] Re: Status of interface connections not properly updated in the UI

[Sebastien Bacher]

Not going to be SRUed to cosmic which is neither nor a LTS nor the
current stable version

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  Status of interface connections not properly updated in the UI

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Triaged
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Triaged
Status in gnome-software source package in Eoan:
  Fix Released

Bug description:
  Steps to reproduce the problem:
  1. Go to the Chromium snap store page by e.g. right clicking on its icon and 
selecting Show details and then the specific app.
  2. Press the Permissions button.
  3. Press/slide the Read/write files on removable storage devices slider.
  4. Close the permissions and the store window.
  5. Reopen the windows.
  6. The permission should be enabled, but it isn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1806697/+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 1819558] Re: Snap interfaces: openvswitch interface has typo

[Sebastien Bacher]

Not going to be SRUed to cosmic which is neither nor a LTS nor the
current stable version

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Snap interfaces: openvswitch interface has typo

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Fix Committed

Bug description:
  Typo'd as openvtswitch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1819558/+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 1818920] Re: Snap without icons use old asset

[Sebastien Bacher]

Not going to be SRUed to cosmic which is neither nor a LTS nor the
current stable version

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Snap without icons use old asset

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software uses an outdated icon for snaps without icons.

  [Test Case]
  1. Open GNOME Software
  2. Look for a snap that has a default icon (e.g. youtube-dl)

  Expected behaviour:
  - The new icon is shown (grey circle with lines)

  Observed behaviour:
  - The old icon is shown (grey origami bird snapcraft logo)

  [Regression Potential]
  Low, this is just an asset change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1818920/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

[Sebastien Bacher]

** No longer affects: gnome-characters (Ubuntu)

** No longer affects: gnome-characters (Ubuntu Bionic)

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

Status in Poppler:
  New
Status in fonts-noto-cjk package in Ubuntu:
  New
Status in gucharmap package in Ubuntu:
  New
Status in icu package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in mozc package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in poppler-data package in Ubuntu:
  New
Status in unicode-data package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Xenial:
  New
Status in gucharmap source package in Xenial:
  New
Status in icu source package in Xenial:
  New
Status in libreoffice source package in Xenial:
  Fix Released
Status in libreoffice-l10n source package in Xenial:
  Fix Released
Status in mozc source package in Xenial:
  Fix Released
Status in openjdk-8 source package in Xenial:
  New
Status in poppler-data source package in Xenial:
  New
Status in unicode-data source package in Xenial:
  New
Status in fonts-noto-cjk source package in Bionic:
  New
Status in gucharmap source package in Bionic:
  New
Status in icu source package in Bionic:
  New
Status in libreoffice source package in Bionic:
  Fix Released
Status in libreoffice-l10n source package in Bionic:
  Fix Released
Status in mozc source package in Bionic:
  Fix Released
Status in openjdk-8 source package in Bionic:
  New
Status in poppler-data source package in Bionic:
  New
Status in unicode-data source package in Bionic:
  New
Status in fonts-noto-cjk source package in Cosmic:
  New
Status in gnome-characters source package in Cosmic:
  New
Status in gucharmap source package in Cosmic:
  New
Status in icu source package in Cosmic:
  New
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released
Status in mozc source package in Cosmic:
  Fix Released
Status in openjdk-8 source package in Cosmic:
  New
Status in poppler-data source package in Cosmic:
  New
Status in unicode-data source package in Cosmic:
  New
Status in fonts-noto-cjk source package in Disco:
  New
Status in gnome-characters source package in Disco:
  New
Status in gucharmap source package in Disco:
  New
Status in icu source package in Disco:
  New
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released
Status in mozc source package in Disco:
  Fix Released
Status in openjdk-8 source package in Disco:
  New
Status in poppler-data source package in Disco:
  New
Status in unicode-data source package in Disco:
  New

Bug description:
  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）

  This is the meta bug to track packages that need fixes; which packages
  have already been SRUd to previous releases, how to prioritize the
  work needed, and general test cases for verifying that things are
  working as expected.

  [Impact]
  Users who run Ubuntu in Japanese.

  [Test cases]

  == Date conversion ==

  On applications that support writing dates in long form, or with
  symbols to denote era (either in X00.00.00 format or in GG1G5G1G
  format  (G- glyph; X- character):

  1) Enable date formatting in each of the above formats that are supported 
(long form or symbols)
  2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" 
or "R1.05.01"
  3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" 
or "H31.4.30"

  == Date output ==

  1) Set date to 2019/05/01
  2) Output date; verify that the year it is displayed as "令和元年"
  3) Set date to 2019/04/30
  4) Output date; verify that the year is diplayed as "平成31年"

  === Displaying formatted year for Japanese era with glibc ===

  Run:
  LC_ALL=ja_JP.utf8 date +%EY -d 20190430   # previous era (should still work 
as before SRUs)
  or
  LC_ALL=ja_JP.utf8 date +%EY -d 20190501   # new era (should now correctly 
display the new era)

  == Character maps / font support ==

  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:

   - SQUARE ERA NAME HEISEI:  ㍻
   - SQUARE ERA NAME REIWA:   令和 (in a single glyph)

  Display of the Reiwa square glyph is font-specific; it may show simply
  as a empty square or a square with hex characters. If that is the
  case, the unicode data supports the new character, but the selected
  font does not include the new glyph.

  == Typing / input methods ==

[Group.of.nepali.translators] [Bug 1819558] Re: Snap interfaces: openvswitch interface has typo

[Sebastien Bacher]

Looks like the issue was fixed in eoan but not mentioned in the changelog of 
the upload
http://launchpadlibrarian.net/423619607/gnome-software_3.30.6-2ubuntu3_3.30.6-2ubuntu5.diff.gz

** Changed in: gnome-software (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Snap interfaces: openvswitch interface has typo

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed
Status in gnome-software source package in Disco:
  Fix Committed

Bug description:
  Typo'd as openvtswitch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1819558/+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 1754671] Re: Full-tunnel VPN DNS leakage regression

[Sebastien Bacher]

We are not going to do cosmic/n-m changes at this point, best to upgrade
to Disco if you need that issue resolved

** Changed in: network-manager (Ubuntu Bionic)
 Assignee: Olivier Tilloy (osomon) => Till Kamppeter (till-kamppeter)

** Changed in: network-manager (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed
Status in network-manager source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Sebastien Bacher]

Ok, let's forget about that SRU, it's a priority anymore and it would
need work, deleting the protobuf buggy upload from xenial-proposed

** Changed in: protobuf (Ubuntu Xenial)
   Status: Fix Committed => Won't Fix

** Changed in: pymacaroons (Ubuntu Xenial)
   Status: Fix Committed => Won't Fix

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  Fix Released
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pymacaroons package in Ubuntu:
  Fix Released
Status in httmock source package in Xenial:
  Won't Fix
Status in protobuf source package in Xenial:
  Won't Fix
Status in py-macaroon-bakery source package in Xenial:
  Won't Fix
Status in pymacaroons source package in Xenial:
  Won't Fix
Status in httmock source package in Artful:
  Fix Released
Status in protobuf source package in Artful:
  Fix Released
Status in py-macaroon-bakery source package in Artful:
  Won't Fix
Status in pymacaroons source package in Artful:
  Won't Fix

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for protobuf: $ python3 -c "import google.protobuf"
  - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly

  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+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 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Sebastien Bacher]

httmock was in xenial/NEW but I'm going to reject it, the livepatch UI
work changed since that bug was started and we are not targetting Xenial
anymore at this point, the SRU has been sitting there for over a year so
I'm just going to wontfix for now and delete the uploads from xenial-
proposed

** Changed in: httmock (Ubuntu Xenial)
   Status: In Progress => Won't Fix

** Changed in: py-macaroon-bakery (Ubuntu Xenial)
   Status: In Progress => Won't Fix

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  Fix Released
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pymacaroons package in Ubuntu:
  Fix Released
Status in httmock source package in Xenial:
  Won't Fix
Status in protobuf source package in Xenial:
  Won't Fix
Status in py-macaroon-bakery source package in Xenial:
  Won't Fix
Status in pymacaroons source package in Xenial:
  Won't Fix
Status in httmock source package in Artful:
  Fix Released
Status in protobuf source package in Artful:
  Fix Released
Status in py-macaroon-bakery source package in Artful:
  Won't Fix
Status in pymacaroons source package in Artful:
  Won't Fix

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for protobuf: $ python3 -c "import google.protobuf"
  - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly

  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+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 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts

[Sebastien Bacher]

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => 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/1162475

Title:
  [hostnamed] Changing hostname doesn't update /etc/hosts

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Xenial:
  New
Status in systemd source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  New
Status in gnome-control-center package in Debian:
  Fix Released

Bug description:
  GUI
  ---
  1a. Run sudo gnome-control-center, or...
  1b. Save the gnome-control-center.pkla from 
https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556
 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run 
gnome-control-center as an admin user

  2. Enter the Details panel
  3. The "Device name" (hostname) text field should be editable; change the 
text to something else.
  4. The hostname is updated instantly which can be verified by looking in 
/etc/hostname. However /etc/hosts/ is not updated.

  Command line
  
  hostnamectl set-hostname

  The hostnamed documentation at 
http://www.freedesktop.org/wiki/Software/systemd/hostnamed says
  "To properly handle name lookups with changing local hostnames without having 
to edit /etc/hosts for them we recommend using hostnamed in combination with 
nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ "

  Without /etc/hosts being handled correctly, the hostnamed integration
  is only half-working.


  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 31 08:52:57 2013
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1162475/+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 1830022] Re: DirtyCleanInterval should be 0 by default

[Sebastien Bacher]

** No longer affects: cups (Ubuntu Xenial)

** No longer affects: cups (Ubuntu Bionic)

** No longer affects: cups (Ubuntu Cosmic)

** No longer affects: cups (Ubuntu Disco)

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

Title:
  DirtyCleanInterval should be 0 by default

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Please consider changing DirtyCleanInterval value to 0 as default.

  Otherwise if cupsd crashes due to (e.g. OOM killer) under a heavy
  workload even hundreds of jobs may be lost. This concern is backed up
  by a real-life scenario and leaves the client sending thousands of
  jobs unaware that many of them are lost during a crash.

  After cupsd gets restarted it rewinds it's job counter to the last
  cached and continues unaware about the jobs accepted and lost.

  Having DirtyCleanInterval set to 0 will cause some performance impact,
  but not significant under lighter workloads and a completely justified
  price for reliability under heavy workloads.

  Test scenario:
  1. sudo apt install printer-driver-cups-pdf
  2. while [ 1 ]; do lp -d PDF somepdf.pdf; done;
  3. # on other terminal
 kill -9 $(pidof cupsd)
  4. Note last job number and wait for cupsd to be restarted by systemd.
  5. Once accepting jobs is resumend the job counter is rewound.

  Expected behavior:
  Accepted jobs are queued for processing.

  Actual behavior:
  Some accepted jobs are lost.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+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 1746598] Re: [MIR] libnfs

[Sebastien Bacher]

** No longer affects: libnfs (Ubuntu Xenial)

** No longer affects: libnfs (Ubuntu Cosmic)

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

Title:
  [MIR] libnfs

Status in libnfs package in Ubuntu:
  Fix Released
Status in libnfs source package in Bionic:
  New

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  gvfs 1.24 added an NFS backend 3 years ago. It was enabled in Debian a year 
ago, but we can't enable it in Ubuntu until libnfs is promoted to main.

  The Ubuntu bug for this feature to be enabled in gvfs is LP: #1637988

  qemu-block-extra could also enable libnfs support.

  Security
  
  No known CVEs.

  https://security-tracker.debian.org/tracker/source-package/libnfs
  https://launchpad.net/ubuntu/+source/libnfs/+cve

  Quality assurance
  =
  - Desktop Packages team is subscribed.
  - dh_auto_test runs but the tests shipped by upstream cant'b be run at build 
time since they modify the system.
  - Autopkgtests are added in 3.0.0-1, running upstream's test suite which 
includes running tests with valgrind, too.

  https://bugs.launchpad.net/ubuntu/+source/libnfs
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libnfs
  https://github.com/sahlberg/libnfs/issues

  https://autopkgtest.ubuntu.com/packages/libn/libnfs (failing, never passed:
  see https://bugs.debian.org/921578 )

  https://ci.debian.net/packages/libn/libnfs/ (tests aren't run in
  Debian because they request machine isolation which isn't implemented
  there yet)

  Dependencies
  
  No universe binary dependencies

  Standards compliance
  
  3.9.8, debhelper compat 9, dh7 simple rules

  Maintenance
  ===
  Actively maintained:
  https://github.com/sahlberg/libnfs

  Not team maintained in Debian.
  https://tracker.debian.org/pkg/libnfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598/+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 1769991] Re: [16.04] Unable to import OpenVPN configuration into Network Manager

[Sebastien Bacher]

Deleting the bionic line since it lacks enough details to be acted on at
this point and has no owner, if you want to suggest it to be reviewed
for that target best to tag it rls-bb-incoming so the team owning the
package can review and decide if that's an item they want to own (which
is blocking not the case until it has the required details to be worked
on)

** No longer affects: network-manager-openvpn (Ubuntu Bionic)

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

Title:
  [16.04] Unable to import OpenVPN configuration into Network Manager

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

Bug description:
  In 16.04, it is currently not possible to import OpenVPN
  configurations.  Specifically, imports fail with the error of:

  The file 'filename.ovpn' could not be read or does not contain
  recognized VPN connection information.

  Error: Key file contains line 'client' which is not a key-value pair,
  group, or comment.

  --

  An example configuration that fails to import is as follows (with some
  critical components excluded, like a proper remote address, or a
  proper x509 name); this is a config that otherwise works with a Sophos
  XG Firewall-based SSL VPN system

  client
  dev tun
  persist-tun
  persist-key
  proto tcp
  verify-x509-name ""
  route remote_host 255.255.255.255 net_gateway
  resolv-retry infinite
  remote 1.2.3.4 8443 tcp
  ca ca.crt
  cert client.crt
  key client.key
  auth-user-pass
  cipher AES-256-CBC
  auth SHA512
  comp-lzo no
  route-delay 4
  verb 3
  reneg-sec 0

  --

  This same exact configuration works with a direct call of `openvpn
  ./filename.ovpn`.

  Why Network Manager is unable to parse or import the OpenVPN
  configuration is beyond my ability to comprehend.

  Note that the same configuration made by hand in the new VPN window
  works fine, but the import function fails.  (Which is a pretty severe
  bug)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-openvpn 1.1.93-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  8 14:59:54 2018
  InstallationDate: Installed on 2016-12-20 (503 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1769991/+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 1617535] Re: geoip.ubuntu.com does not utilize HTTPS

[Sebastien Bacher]

** Changed in: ubuntu-geoip (Ubuntu Artful)
   Status: Triaged => Won't Fix

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

Title:
  geoip.ubuntu.com does not utilize HTTPS

Status in ubuntu-geoip package in Ubuntu:
  Fix Released
Status in ubuntu-geoip source package in Trusty:
  Triaged
Status in ubuntu-geoip source package in Xenial:
  Triaged
Status in ubuntu-geoip source package in Artful:
  Won't Fix

Bug description:
  Impact
  --
  It's better to use https where we can. There were concerns about location 
leakage for users using a proxy (such as Tor).

  Test Case
  -

  Regression Potential
  
  As long as Canonical maintains https://geoip.ubuntu.com, things should be 
fine here. Minimal fix.

  
  Original Bug Report
  ---
  geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This 
can potentially be utilized by nation state adversaries to compromise user 
privacy. This service is called multiple times per day by the OS in order to 
track users.

  $ nc -zv geoip.ubuntu.com 80
  Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded!

  $ nc -zv -w 3 geoip.ubuntu.com 443
  nc: connect to geoip.ubuntu.com port 443 (tcp) timed out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Sebastien Bacher]

** Changed in: network-manager (Ubuntu Yakkety)
   Status: Triaged => Won't Fix

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Won't Fix

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1683445] Re: E6430 brightness control not working

[Sebastien Bacher]

** Changed in: unity-settings-daemon (Ubuntu Zesty)
   Status: Triaged => Won't Fix

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

Title:
  E6430 brightness control not working

Status in GNOME Settings Daemon:
  Fix Released
Status in Nouveau Xorg driver:
  Won't Fix
Status in OEM Priority Project:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Confirmed
Status in gnome-settings-daemon source package in Zesty:
  Fix Released
Status in unity-settings-daemon source package in Zesty:
  Won't Fix

Bug description:
  Impact
  --
  It looks like GNOME's brightness control simply used the first backlight 
device it saw instead of one currently in use. This meant that the brightness 
control would not work on some computers with multiple GPUs.

  Test Case
  -
  From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
  Restart.
  Does the brightness control now work correctly?

  Regression Potential
  
  This looks like a minimal fix for this issue. It was accepted as part of 
gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be upgrading to.

  Original Bug Report
  ---
  The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source 
Nouveau driver shows the brightness slider moving but does not affect the 
brightness.

  When using the kernel boot option acpi_backlight=vendor , the
  brightness control works.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 20:00:56 2017
  HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
  InstallationDate: Installed on 2017-04-10 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Latitude E6430
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1683445/+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 1767784] Re: [regression] output device not recognized anymore since update 1:8.0-0ubuntu3.9

[Sebastien Bacher]

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

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

Title:
  [regression] output device not recognized anymore since update
  1:8.0-0ubuntu3.9

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

Bug description:
  SRU Document:

  [Impact]

  The 1:8.0-0ubuntu3.9 introduced a new problem on the machines which do
  not have internal speaker on them. With the 1:8.0-0ubuntu3.8, even
  there is no internal speaker and nothing plugged in the audio jack,
  the profile is still set available, then the active profile is analog-
  stereo; while with the 1:8.0-0ubuntu3.9, the profile is set to
  unavailable, and the active profile is off, after users plug sth in
  the audio jack, the active profile will not switch automatically, need
  users to switch manually, this change is unfriendly to users.

  [Test Case]

  On the machines without internal speaker, open sound-setting and check
  if there is some output devices in the UI, and play sound from the UI.
  Under 1:8.0-0ubuntu3.9 there is no output device, and can't play
  sound; under 1:8.0-0ubuntu3.8 there is output device, and can play
  sound.

  [Regression Potential]

  This is a revert, after reverting, the content of pulseaudio is
  exactly same as 1:8.0-0ubuntu3.8

  [Other Info]

  none

  
  Since the update 1:8.0-0ubuntu3.8 to 1:8.0-0ubuntu3.9 , pulseaudio is not 
showing anymore my soundcard.

  https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9

  The command "pacmd list-sinks" only shows a dummy output

  When running on a fresh install of ubuntu 16.04, the sound is ok.
  When updating the install with locking the following files to version 
1:8.0-0ubuntu3 the sound keeps working:
  libpulse0:amd64
  libpulse-mainloop-glib0:amd64
  libpulse-dev:amd64
  pulseaudio-module-x11:amd64
  pulseaudio-module-bluetooth:amd64
  pulseaudio-utils:amd64

  When updating to 1:8.0-0ubuntu3.9, I just get a "dummy output".

  I tried running the following versions of Ubuntu (live usb), and get the same 
issue (no need to update to get the problem)
  17.04
  17.10
  18.04

  I attached the result of command "pactl list"
  I have also generated logs during the boot but I don't know how to attach 
multiple files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784/+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 1637984] Re: Disks shows all mounted snaps

[Sebastien Bacher]

** Changed in: udisks2 (Ubuntu Bionic)
   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/1637984

Title:
  Disks shows all mounted snaps

Status in GNOME Disks:
  Fix Released
Status in gnome-disk-utility package in Ubuntu:
  Fix Released
Status in udisks2 package in Ubuntu:
  Fix Released
Status in gnome-disk-utility source package in Xenial:
  Fix Released
Status in udisks2 source package in Xenial:
  Won't Fix
Status in gnome-disk-utility source package in Artful:
  Fix Released
Status in udisks2 source package in Artful:
  Won't Fix
Status in gnome-disk-utility source package in Bionic:
  Fix Released
Status in udisks2 source package in Bionic:
  Fix Released

Bug description:
  * Impact
  In 16.04 and later any installed snaps show as loop devices in Disks.

  * Test Case
  - install a snap
  - open gnome-disks
  -> the snap shouldn't be listed on the left pane as a device

  * Regression potential
  Check that all your existing disks are still listed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1637984/+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 1751280] Re: Backport fix for url from upstream

[Sebastien Bacher]

https://bugs.launchpad.net/ubuntu/+source/fwupd/1.0.6-2

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

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

Title:
  Backport fix for url from upstream

Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd source package in Xenial:
  Triaged

Bug description:
  Upstream has updated the url for downloads to be more future proof.

  Please backport this fix for 16.04:

  
https://github.com/hughsie/fwupd/commit/cbb228c7c34c99cfe98caf13f4699731535c65e5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1751280/+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 1637984] Re: Disks shows all mounted snaps

[Sebastien Bacher]

** Also affects: gnome-disk-utility (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: udisks2 (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: gnome-disk-utility (Ubuntu Bionic)
   Importance: High
 Assignee: Andrea Azzarone (azzar1)
   Status: In Progress

** Also affects: udisks2 (Ubuntu Bionic)
   Importance: High
 Assignee: Andrea Azzarone (azzar1)
   Status: In Progress

** Also affects: gnome-disk-utility (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: gnome-disk-utility (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: gnome-disk-utility (Ubuntu Artful)
   Importance: Undecided => High

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

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

** Changed in: udisks2 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: gnome-disk-utility (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: udisks2 (Ubuntu Artful)
   Status: New => Won't Fix

** Changed in: udisks2 (Ubuntu Xenial)
   Status: New => Won't Fix

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

Title:
  Disks shows all mounted snaps

Status in GNOME Disks:
  Fix Released
Status in gnome-disk-utility package in Ubuntu:
  Fix Committed
Status in udisks2 package in Ubuntu:
  Fix Committed
Status in gnome-disk-utility source package in Xenial:
  New
Status in udisks2 source package in Xenial:
  Won't Fix
Status in gnome-disk-utility source package in Artful:
  New
Status in udisks2 source package in Artful:
  Won't Fix
Status in gnome-disk-utility source package in Bionic:
  Fix Committed
Status in udisks2 source package in Bionic:
  Fix Committed

Bug description:
  In 16.04 and later any installed snaps show as loop devices in Disks.

  While it is indeed a loop device I think it would be tidier if we
  could not show the snaps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1637984/+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 1716359] Re: Unplugging headset with audio panel open mutes internal mic

[Sebastien Bacher]

** Also affects: unity-control-center (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/1716359

Title:
  Unplugging headset with audio panel open mutes internal mic

Status in OEM Priority Project:
  Confirmed
Status in unity-control-center package in Ubuntu:
  In Progress
Status in unity-control-center source package in Xenial:
  New

Bug description:
  
  Impact
  ==
  This is required by OEM team.

  Test Case
  =
  1. Open System Settings -> Sound -> select the input tab
  2. Plug headset and select Headset on Unknown Audio Device dialog.
  3. Check external mic is working
  4. Adjust the internal microphone volume.(Just change the volume value.)
  5. Adjust headset input volume around 100% in Input tab from Sound settings
  6. Unplug headset
  7. Check internet mic status

  Make sure the internal mic is not muted.

  Regression Potential
  ===
  - Make sure that plugging/unplugging headphones does the correct thing.
  - Make sure that manually selecting an headphone actually switch mic.
  - Please also check that output sound works too.

  Original Bug Report
  ===
  This bug was reported by our OEM team, I'm opening this public bug.

  The internal microphone is muted after he headset is unplugged when the 
System Settings is running.
  We can not reproduce this bug when closed the System Settings window before 
unplugged the headset.

  Reproduce steps:
  1. Open System Settings -> Sound -> select the input tab
  2. Plug headset and select Headset on Unknown Audio Device dialog.
  3. Check external mic is working
  4. Adjust the internal microphone volume.(Just change the volume value.)
  5. Adjust headset input volume around 100% in Input tab from Sound settings
  6. Unplug headset
  7. Check internet mic status

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1716359/+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 1703827] Re: ubuntu-support-status return "TypeError: not enough arguments for format string" due to bad translations

[Sebastien Bacher]

** Also affects: language-pack-gd (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ubuntu-support-status return "TypeError: not enough arguments for
  format string" due to bad translations

Status in Ubuntu Translations:
  New
Status in language-pack-gd package in Ubuntu:
  New
Status in language-pack-it package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  Triaged
Status in language-pack-gd source package in Xenial:
  New
Status in language-pack-it source package in Xenial:
  New
Status in update-manager source package in Xenial:
  Confirmed

Bug description:
  in Ubuntu 16.04.2 LTS fresh install no upgrade from other ubuntu version. 
update-manager version 16.04.6.
  Running command:
  ubuntu-support-status
  Return only the error:
  "
  Traceback (most recent call last):
File "/usr/bin/ubuntu-support-status", line 151, in 
  'time' : time})
  TypeError: not enough arguments for format string
  "

  Solution is to add a space in line 151 before " , so the line was:
  print(_("You have %(num)s packages (%(percent).1f%%) supported until 
%(time)s") % {
  and become:
  print(_("You have %(num)s packages (%(percent).1f%%) supported until %(time)s 
") % {

  Notice the space after %(time)s.

  Best regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1703827/+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 1703827] Re: ubuntu-support-status return "TypeError: not enough arguments for format string" due to bad translations

[Sebastien Bacher]

** Also affects: ubuntu-translations
   Importance: Undecided
   Status: New

** Also affects: language-pack-it (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ubuntu-support-status return "TypeError: not enough arguments for
  format string" due to bad translations

Status in Ubuntu Translations:
  New
Status in language-pack-it package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  Triaged
Status in language-pack-it source package in Xenial:
  New
Status in update-manager source package in Xenial:
  Confirmed

Bug description:
  in Ubuntu 16.04.2 LTS fresh install no upgrade from other ubuntu version. 
update-manager version 16.04.6.
  Running command:
  ubuntu-support-status
  Return only the error:
  "
  Traceback (most recent call last):
File "/usr/bin/ubuntu-support-status", line 151, in 
  'time' : time})
  TypeError: not enough arguments for format string
  "

  Solution is to add a space in line 151 before " , so the line was:
  print(_("You have %(num)s packages (%(percent).1f%%) supported until 
%(time)s") % {
  and become:
  print(_("You have %(num)s packages (%(percent).1f%%) supported until %(time)s 
") % {

  Notice the space after %(time)s.

  Best regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1703827/+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 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

[Sebastien Bacher]

** Also affects: pulseaudio (Ubuntu Artful)
   Importance: High
 Assignee: Daniel van Vugt (vanvugt)
   Status: Fix Released

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

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

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

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

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

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

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1539209/+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 1589535] Re: nm-applet silently timesout on long 'WPA/WPA2 Personal' password input

[Sebastien Bacher]

** Also affects: network-manager-applet (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  nm-applet silently timesout on long 'WPA/WPA2 Personal' password input

Status in Network Manager Applet:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Xenial:
  New

Bug description:
  1)
  ouroumov@Edge:~/Desktop$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2)
  apt-cache policy is unable to locate the package.

  3)
  Upon entering a long WPA/WPA2 Personal password after clicking the network 
icon in the top right panel, the connection should be added to network-manager, 
even if typing the password takes a while.

  4)
  If typing the password takes longer than ~25 seconds, upon clicking the 
"Connect" button in the password prompt dialog: nothing happens

  Steps to reproduce:

  - Install Ubuntu MATE 16.04 LTS (possibly other Ubuntu flavours using 
nm-applet too)
  - Run normal post-install full system update and reboot
  - Click the network icon in the top right corner of the default panel layout
  - Select from the Wi-Fi network list a network using WPA/WPA2 Personal
  - Enter the password, wait 30 seconds to click 'connect'

  Note:

  While this issue might seem trivial (using 'System -> Preferences ->
  Internet and Network -> Network Connections' allows one to correctly
  save the password) (and quickly copy/pasting the password from a text
  file works too) it is a serious usability problem for many people in
  France.

  The default home router Wi-Fi setup in France is WPA/WPA2 Personal
  with a random 26-character hexadecimal password. It takes a while to
  type.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1589535/+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 1610005] Re: Remove gtk3's versioned dependency of on adwaita-icon-theme

[Sebastien Bacher]

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Fix Committed

** Also affects: gtk+3.0 (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/1610005

Title:
  Remove gtk3's versioned dependency of on adwaita-icon-theme

Status in Lubuntu Artwork:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Xenial:
  New

Bug description:
  Impact
  ===
  libgtk-3-common depends on adwaita-icon-theme (>= ${gnome:Version}). For 
xenial, this is adwaita-icon-theme >= 3.18.

  This causes 2 problems. One is that we have to remember to upload a
  new version of adwaita-icon-theme before we upload a new version of
  GTK3. Otherwise, the new version of adwaita-icon-theme becomes
  unbuildable because adwaita-icon-theme depends on GTK3 to build but
  GTK3 is uninstallable because the dependency can't be satisfied yet.
  This can be worked around (it happened this week with 3.20 in yakkety)
  but it's not good.

  The other is that Lubuntu doesn't want to install adwaita-icon-theme
  but instead install lubuntu-icon-theme as a replacement by setting
  Provides: adwaita-icon-theme. According to Debian policy, that doesn't
  work if something has a versioned dependency on the provided package.

  https://www.debian.org/doc/debian-policy/ch-
  relationships.html#s-virtual

  The versioned dependency was removed in Debian svn: 
  
https://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/gtk%2B3.0/debian/control.in?r1=49406=49410

  Test case
  =
  Since the xenial daily images use -proposed, check here whether 
adwaita-icon-theme is installed a day or two after the gtk update has been 
pushed to xenial-proposed:

  http://cdimage.ubuntu.com/lubuntu/xenial/daily-live/current/xenial-
  desktop-amd64.manifest

  Regression potential
  
  If in fact, lubuntu-icon-theme does not include some of the icons in 
adwaita-icon-theme, there will be missing icons in apps that try to use those 
icons.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-common 3.18.9-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug  4 18:55:25 2016
  InstallationDate: Installed on 2016-07-31 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-artwork/+bug/1610005/+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 1568829] Re: nm-applet icon not showing when /proc is mounted with hidepid!=0

[Sebastien Bacher]

The fixed version is in yakkety and there is a SRU waiting in the review
queue which includes that change

** Package changed: network-manager-applet (Ubuntu) => network-manager
(Ubuntu)

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Aron Xu (happyaron)

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: network-manager (Ubuntu Xenial)
 Assignee: (unassigned) => Aron Xu (happyaron)

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

Title:
  nm-applet icon not showing when /proc is mounted with hidepid!=0

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

Bug description:
  Steps to reproduce:

  1. (Re-)mount /proc with hidepid=1 (or =2)
  2. Restart nm-applet

  nm-applet's icon does not reappear after the restart. This used to
  work with version 1.0.

  
  Original bug description:

  Since I upgraded to -proposed network-manager and network-manager-gnome 
versions, nm-applet no longer works.
  Manually starting it on a console give:

  $ nm-applet

  (nm-applet:6250): nm-applet-WARNING **: 
GDBus.Error:org.freedesktop.NetworkManager.AgentManager.PermissionDenied: 
Unable to determine request sender and UID.
  (nm-applet:6250): libnm-CRITICAL **: nm_client_get_nm_running: assertion 
'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_get_state: assertion 
'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_networking_get_enabled: 
assertion 'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_get_enabled: 
assertion 'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_wireless_hardware_get_enabled: 
assertion 'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_get_enabled: assertion 
'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_wwan_hardware_get_enabled: 
assertion 'NM_IS_CLIENT (client)' failed
  (nm-applet:6250): libnm-CRITICAL **: nm_client_get_devices: assertion 
'NM_IS_CLIENT (client)' failed

  What's odd is the NM and NM-gnome base versions are not identical:

  $ apt-cache policy network-manager network-manager-gnome
  network-manager:
    Installed: 1.1.93-0ubuntu1
    Candidate: 1.1.93-0ubuntu1
    Version table:
   *** 1.1.93-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.4-0ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  network-manager-gnome:
    Installed: 1.1.93-1ubuntu1
    Candidate: 1.1.93-1ubuntu1
    Version table:
   *** 1.1.93-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.10-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-gnome 1.1.93-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 11 08:16:59 2016
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 1:
   (process:7301): nmcli-CRITICAL **: Error: Could not create NMClient object: 
Unable to authenticate request..
  nmcli-dev:
   Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 1:
   (process:7297): nmcli-CRITICAL **: Error: Could not create NMClient object: 
Unable to authenticate request..
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1568829/+subscriptions

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

[Group.of.nepali.translators] [Bug 1595707] Re: [SRU]crash in nmc_find_connection

[Sebastien Bacher]

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=767987
   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/1595707

Title:
  [SRU]crash in nmc_find_connection

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  New

Bug description:
  [Impact]

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1595707/+subscriptions

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

[Group.of.nepali.translators] [Bug 1576308] Re: gsettings doesn't work with snap confinement

[Sebastien Bacher]

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

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

Title:
  gsettings doesn't work with snap confinement

Status in snapd package in Ubuntu:
  Fix Committed
Status in snapd source package in Xenial:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Committed

Bug description:
  Work is needed there, see
  
https://wiki.ubuntu.com/SecurityTeam/Specifications/ApplicationConfinement#GSettings.2Fdconf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1576308/+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 1572661] Re: Ubuntu Gnome Bug -evolution translation

[Sebastien Bacher]

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

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

Title:
  Ubuntu Gnome Bug -evolution translation

Status in evolution package in Ubuntu:
  Invalid
Status in evolution source package in Xenial:
  Triaged

Bug description:
  * Impact
  evolution is not translated

  * Test case
  start evolution under a non english locale, it should be translated

  * Regression potential
  none, that's a small packaging change to add translations to the deb

  -

  Ubuntu Gnome 16.04 RC

  Evolution is not translated in another language. It is in english
  only.

  Affects at least french (canadian), Norwegian (Bokmål) and german
  (seen on a Google Plus post :

  https://plus.google.com/+UbuntuGNOMEorg/posts/bsFL3SLf6ot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1572661/+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 1592134] Re: [SRU] dh-make writes debian/source/format to debian/outfile

[Sebastien Bacher]

Thanks, I updated the changelog to target xenial/use a ~xenial1 version
and put your name as uploader and added the SRU bug reference and
uploaded

** Also affects: dh-make (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: dh-make (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: dh-make (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: dh-make (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/1592134

Title:
  [SRU] dh-make writes debian/source/format to debian/outfile

Status in dh-make package in Ubuntu:
  Fix Committed
Status in dh-make source package in Xenial:
  Fix Committed
Status in dh-make package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Running dh_make generates debian/source/format, but writes it to
  debian/outfile.

  [Test Case]

   * Download a source package via apt-get source or pull-lp-source
   * Delete the debian directory
   * Run dh_make

  [Regression Potential]

   * Risk of regression is low, the fix is two characters, and already
  available in Yakkety Yak

  [Other Info]

   * Debian bug report is here: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=813937

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-make/+bug/1592134/+subscriptions

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

[Group.of.nepali.translators] [Bug 1586491] Re: Volume up and down keys no longer autorepeat

[Sebastien Bacher]

** Also affects: unity (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/1586491

Title:
  Volume up and down keys no longer autorepeat

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

Bug description:
  After upgrading to unity and compiz in xenial-proposed my volume up
  and down keys stopped autorepeating, which seems to be fallout from
  the fix for
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1572241

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160526.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 27 13:45:30 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9]
  InstallationDate: Installed on 2016-01-06 (141 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: LENOVO 3443CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=1f36140c-def2-49da-a1f8-0e14cfc2d84c ro quiet splash 
intel_pstate=disable vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
  Identifier  "Configured Video Device"
  Driver "intel"
  Option "TearFree" "true" 
   EndSection
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET93WW (2.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3443CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET93WW(2.53):bd02/04/2013:svnLENOVO:pn3443CTO:pvrThinkPadX1Carbon:rvnLENOVO:rn3443CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3443CTO
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri May 27 13:17:21 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 898 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1586491/+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 1580254] Re: Cannot change accounts images

[Sebastien Bacher]

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

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

Title:
  Cannot change accounts images

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

Bug description:
  HOW TO REPRODUCE:
  1. Go to "System Settings -> User Accounts"
  2. Click on the user image at the left of the user name, and select a new 
image.

  RESULT:
  Image isn't changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 10 18:28:06 2016
  InstallationDate: Installed on 2016-05-02 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1580254/+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 1571574] Re: 3G (WWAN) icon missing in network-manager-applet

[Sebastien Bacher]

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

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=766709
   Importance: Unknown
   Status: Unknown

** Changed in: network-manager-applet (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: network-manager-applet (Ubuntu)
   Status: Incomplete => New

** Changed in: network-manager-applet (Ubuntu Xenial)
   Status: Incomplete => New

** Changed in: network-manager-applet
   Importance: Undecided => Unknown

** Changed in: network-manager-applet
   Status: New => Unknown

** Changed in: network-manager-applet
 Remote watch: None => GNOME Bug Tracker #766709

** No longer affects: network-manager

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

Title:
  3G (WWAN) icon missing in network-manager-applet

Status in Network Manager Applet:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  New
Status in network-manager-applet source package in Xenial:
  New

Bug description:
  After establishing a 3G connection, the icon shown in system tray
  should be a 3G indicator to indicate that 3G is connected.

  However, in Xenial there is no 3G icon at all.
  After 3G connection is established, it remains as the previous icon displayed.
  (e.g. 
  If no other connection was established before 3G connection was made, then 
the icon is a "hollow fan shape" after connecting to 3G.
  If wifi was connected before 3G connection was made, then the icon after 3G 
connection shows a wifi icon.)

  network-manager: 1.1.93-0ubuntu3
  OS: Xenial daily (2016 Apr. 15)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1571574/+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 1565267] Re: Gnome Calendar has white corners

[Sebastien Bacher]

https://launchpad.net/ubuntu/+source/gnome-calendar/3.20.2-0ubuntu1

** Also affects: gnome-calendar (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: gnome-calendar (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: gnome-calendar (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: gnome-calendar (Ubuntu Xenial)
   Importance: High => Low

** Changed in: gnome-calendar (Ubuntu)
   Importance: Medium => Low

** Changed in: gnome-calendar (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Gnome Calendar has white corners

Status in GNOME Calendar:
  Fix Released
Status in Ubuntu theme:
  New
Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Xenial:
  In Progress

Bug description:
  * Impact

  the gnome-calendar window corners don't look right (white squares
  instead of rounded)

  * Test case
  start gnome-calendar under unity and look at the windows corner, they should 
be rounded. The update also include a bugfix new revesion so make sure calendar 
events are correctly listed and that the calendar works correctly

  * Regression potential
  the update has only small bugfixes and should be safe but keep an eye for new 
issues

  --

  Gnome Calendar still looks like it is not using the proper CSD that
  other Gnome apps do (maps, weather, etc.) nor does it look like a
  patched Unity app.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-calendar 3.19.92-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr  2 07:12:41 2016
  InstallationDate: Installed on 2016-03-27 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calendar/+bug/1565267/+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 1580254] Re: Cannot change accounts images

[Sebastien Bacher]

It's a regression from
https://launchpad.net/ubuntu/+source/accountsservice/0.6.40-2ubuntu12

seems like those are needed

"  yes
  yes"

** Also affects: unity-control-center (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: unity-control-center (Ubuntu)
   Importance: Low => High

** Changed in: unity-control-center (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: unity-control-center (Ubuntu)
   Status: Triaged => In Progress

** Changed in: unity-control-center (Ubuntu Xenial)
   Status: New => In Progress

** Package changed: unity-control-center (Ubuntu) => accountsservice
(Ubuntu)

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

Title:
  Cannot change accounts images

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

Bug description:
  HOW TO REPRODUCE:
  1. Go to "System Settings -> User Accounts"
  2. Click on the user image at the left of the user name, and select a new 
image.

  RESULT:
  Image isn't changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 10 18:28:06 2016
  InstallationDate: Installed on 2016-05-02 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1580254/+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 1576726] Re: [SRU]network-manager

[Sebastien Bacher]

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: network-manager-applet (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager-applet (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu Xenial)
 Assignee: (unassigned) => Aron Xu (happyaron)

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Committed

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Aron Xu (happyaron)

** Changed in: network-manager-applet (Ubuntu)
 Assignee: (unassigned) => Aron Xu (happyaron)

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

Title:
  [SRU]network-manager

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager-applet package in Ubuntu:
  New
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager-applet source package in Xenial:
  New

Bug description:
  [Impact]
  Xenial was released with upstream beta2 version of network-manager to keep in 
time for the release schedule, and upstream stable release has been made so 
it's time to update to it.

  [Testcase]
  After upgrading the package, user should still be able to connect to networks 
like Ethernet, Wi-Fi and VPNs.

  [Regression Potential]
  Potential of causing regression is relatively small because there is not big 
changes made during beta2 -> stable process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576726/+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 254584] Re: Activating -proposed should need a confirmation with a proper warning

[Sebastien Bacher]

software-properties (0.96.18) xenial; urgency=medium

  * Create a new tab for developer options and move the proposed source to it.
Since those updates can create issues they shouldn't be too easy to enable
nor listed with the standard recommended sources.

** Changed in: software-properties (Ubuntu Xenial)
   Status: Triaged => Fix Released

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

Title:
  Activating -proposed should need a confirmation with a proper warning

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  Fix Released

Bug description:
  The GUI is mainly intended for use by normal users. Using the proposed
  repository may cause problems and is therefore not recommended for the
  broad mayority of users. The normal user should not be able to
  activate this repository by just a single click.

  We need a proper warning, explaining what -proposed is, requiring
  confirmation by the user.

  For example:

  "Proposed is intended for people willing to test updates before the
  reach a wider audience. Are you sure you want to activate -proposed?"

  : "The “When
  checking for updates, check for:” menu should contain options for “All
  updates” (the default, -security + -updates + -backports), “Security
  and recommended updates” (-security + -updates), and “Security updates
  only” (-security) (fixing bug 887079). If your current update config
  does not match one of those three options (for example, if you have
  opted in to -proposed), there should be a fourth, checked, option:
  “Custom”, and this option should persist until you close System
  Settings. (UI for configuring -proposed should be provided by the
  Ubuntu Contributor Console.)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/254584/+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 1536208] Re: Can no longer find dlna server after upgrade from 15.10 to 16.04

[Sebastien Bacher]

the issue was with gssdp and the difference in guest was probably just
random timing one

** Package changed: dleyna-server (Ubuntu Xenial) => gssdp (Ubuntu
Xenial)

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

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

** Changed in: gssdp (Ubuntu Xenial)
 Assignee: Iain Lane (laney) => (unassigned)

** Changed in: grilo-plugins (Ubuntu Xenial)
 Assignee: Iain Lane (laney) => (unassigned)

** Changed in: rhythmbox (Ubuntu Xenial)
 Assignee: Iain Lane (laney) => (unassigned)

** Changed in: grilo-plugins (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: grilo-plugins (Ubuntu Xenial)
   Importance: Undecided => High

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

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

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

Title:
  Can no longer find dlna server after upgrade from 15.10 to 16.04

Status in grilo-plugins package in Ubuntu:
  Invalid
Status in gssdp package in Ubuntu:
  Fix Committed
Status in rhythmbox package in Ubuntu:
  Invalid
Status in grilo-plugins source package in Xenial:
  Invalid
Status in gssdp source package in Xenial:
  Fix Committed
Status in rhythmbox source package in Xenial:
  Invalid

Bug description:
  From irc:
  08:28 < jdstrand> Laney: question for you-- just otoh, can you think of a 
reason why dlna wouldn't work on xenial in rhythmbox any more when it has the 
same upstream version as wily (and the Ubuntu delta didn't have any relevant 
changes), grilo is the same as wily and grilo-plugins only has one irrelevant 
change over wily?
  08:29 < jdstrand> (it the dleyna code in grilo that handles this afaik)
  08:30 < jdstrand> Laney: the dlna server just doesn't show up any more (but 
daap still does)
  08:33 < jdstrand> I have both forked-daapd and minidlna exporting 
  08:33 < jdstrand> and rhythmbox used to see both on wily. on xenial, it only 
sees daap

  This may be a bug in grilo or grilo-plugins since, AIUI, it is the
  dleyna code in grilo-plugins that handles this. It appears that grilo
  relies on dleyna-server and dleyna-server isn't able to find the
  server any more. I tried on a separate wily install and it wasn't able
  to find it.

  Coming up with a reproducer was more difficult than I thought it would
  be.

  1. minidlna server setup
  $ sudo apt-get install minidlna

  Adjust /etc/minidlna.conf to have:
  media_dir=A,/path/to/some/music/files

  I believe everything else can be left as defaults.

  2. rhythmbox setup
  $ sudo apt-get install grilo-plugins-0.2-extra rhythmbox-plugins dleyna-server

  stop and start rhythmbox

  go into Tools/Plugins and check Grilo media browser

  This was all I needed to do initially for it to start working. Now it
  now longer works. Android devices and 'kodi' from Ubuntu can find and
  use it fine. Using d-feet and going to 'com.intel.dleyna-server' and
  into com.intel.dLeynaServer.Manager and looking at 'GetServers'
  returns nothing. Looking at Rescan() triggers traffic (as seen with
  tcpcump) with the server (ie, there are responses). Looking at an
  strace of /usr/lib/dleyna-server/dleyna-server-service shows it got a
  response from the minidlna server. I guess the problem is in dleyna-
  server. There is a new upstream version (0.5), but it is newer than
  what is in Debian.

  Apparently minidlna is installed in Netgear devices and other places
  and is quite popular.

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