[Touch-packages] [Bug 1851339] Re: Add the to order tramadol 50 mg online in USA ability to check for updates

2019-11-04 Thread William Grant
** Package changed: openssh (Ubuntu) => null-and-void

** Information type changed from Public to Private

** Changed in: null-and-void
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1851339

Title:
  Add the to order tramadol 50 mg online in USA ability to check for
  updates

Status in NULL Project:
  Invalid

Bug description:
  Add the to order tramadol 50 mg online in USA call us for overnight delivery 
+1 (910) 212 - 7411 ability to check for updates
  click to buy tramadol online without prescription 
  https://riteaidpharmacy.org/product-category/buy-tramadol-online/

  ProblemType: Package,order tramadol 50 mg online in USA
  order tramadol 50 mg online in USADistroRelease: Ubuntu 19.10
  Package: openssh-server 1:8.0p1-6build1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64,order tramadol 50 mg online in USA
  ApportVersion: 2.20.11-0ubuntu8.1
  tramadol online maxico,tramadol online caneda, norx,no script required call 
us now at riteaid store
  https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1851337
  https://blueprints.launchpad.net/wxfixboot/+spec/add-check-for-update

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1851339/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851339] [NEW] Add the to order tramadol 50 mg online in USA ability to check for updates

2019-11-04 Thread John David
Private bug reported:

Add the to order tramadol 50 mg online in USA call us for overnight delivery +1 
(910) 212 - 7411 ability to check for updates
click to buy tramadol online without prescription 
https://riteaidpharmacy.org/product-category/buy-tramadol-online/

ProblemType: Package,order tramadol 50 mg online in USA
order tramadol 50 mg online in USADistroRelease: Ubuntu 19.10
Package: openssh-server 1:8.0p1-6build1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64,order tramadol 50 mg online in USA
ApportVersion: 2.20.11-0ubuntu8.1
tramadol online maxico,tramadol online caneda, norx,no script required call us 
now at riteaid store
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1851337
https://blueprints.launchpad.net/wxfixboot/+spec/add-check-for-update

** Affects: null-and-void
 Importance: Undecided
 Status: Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1851339

Title:
  Add the to order tramadol 50 mg online in USA ability to check for
  updates

Status in NULL Project:
  Invalid

Bug description:
  Add the to order tramadol 50 mg online in USA call us for overnight delivery 
+1 (910) 212 - 7411 ability to check for updates
  click to buy tramadol online without prescription 
  https://riteaidpharmacy.org/product-category/buy-tramadol-online/

  ProblemType: Package,order tramadol 50 mg online in USA
  order tramadol 50 mg online in USADistroRelease: Ubuntu 19.10
  Package: openssh-server 1:8.0p1-6build1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64,order tramadol 50 mg online in USA
  ApportVersion: 2.20.11-0ubuntu8.1
  tramadol online maxico,tramadol online caneda, norx,no script required call 
us now at riteaid store
  https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1851337
  https://blueprints.launchpad.net/wxfixboot/+spec/add-check-for-update

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1851339/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851337] Re: package openssh-server 1:8.0p1-6build1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1

2019-11-04 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1851337

Title:
  package openssh-server 1:8.0p1-6build1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I don't know.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: openssh-server 1:8.0p1-6build1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  Date: Tue Nov  5 08:22:46 2019
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2019-01-15 (293 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
sshd: no hostkeys available -- exiting.
  SourcePackage: openssh
  Title: package openssh-server 1:8.0p1-6build1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851337] [NEW] package openssh-server 1:8.0p1-6build1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1

2019-11-04 Thread Csordás Zoltán
Public bug reported:

I don't know.

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: openssh-server 1:8.0p1-6build1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
Date: Tue Nov  5 08:22:46 2019
ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2019-01-15 (293 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
sshd: no hostkeys available -- exiting.
SourcePackage: openssh
Title: package openssh-server 1:8.0p1-6build1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)

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


** Tags: amd64 apport-package eoan

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1851337

Title:
  package openssh-server 1:8.0p1-6build1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I don't know.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: openssh-server 1:8.0p1-6build1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  Date: Tue Nov  5 08:22:46 2019
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2019-01-15 (293 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
sshd: no hostkeys available -- exiting.
  SourcePackage: openssh
  Title: package openssh-server 1:8.0p1-6build1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851334] [NEW] Performance is not good system freeze a lot of time

2019-11-04 Thread manan masood
Public bug reported:

Performance is not good system freeze a lot of time I am new to Ubuntu
and don't know what to do please help

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  5 01:16:25 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee]
InstallationDate: Installed on 2019-11-04 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: HP HP Notebook
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=bef4cfb0-ebad-44d4-aad1-914b2839dba4 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81EE
dmi.board.vendor: HP
dmi.board.version: 62.36
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd10/27/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.36:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.sku: 1AP08EA#BH5
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan performance ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1851334

Title:
  Performance is not good system freeze a lot of time

Status in xorg package in Ubuntu:
  New

Bug description:
  Performance is not good system freeze a lot of time I am new to Ubuntu
  and don't know what to do please help

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 01:16:25 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee]
  InstallationDate: Installed on 2019-11-04 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Notebook
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=bef4cfb0-ebad-44d4-aad1-914b2839dba4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EE
  dmi.board.vendor: HP
  dmi.board.version: 62.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd10/27/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: 1AP08EA#BH5
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: 

[Touch-packages] [Bug 1850929] Re: python3-apport regression: missing argument in Report.add_proc_environ call

2019-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.11-0ubuntu8.2

---
apport (2.20.11-0ubuntu8.2) eoan-security; urgency=medium

  * SECURITY REGRESSION: missing argument in Report.add_proc_environ
call (LP: #1850929)
- apport/report.py: call add_proc_environ using named arguments
  and move proc_pid_dir keyword to last to keep api compatibility.

 -- Tiago Stürmer Daitx   Tue, 05 Nov 2019
02:49:27 +

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1850929

Title:
  python3-apport regression: missing argument in Report.add_proc_environ
  call

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  This is a regression in the 2.20.9-0ubuntu7.8 security update of
  apport

  # lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  Reproduce the bug:

  $ python3
  Python 3.6.8 (default, Oct  7 2019, 12:59:55) 
  [GCC 8.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import apport
  >>> import os
  >>> report = apport.Report()
  >>> report.add_proc_info(os.getpid(), extraenv=['PYTHONHOME', 'PYTHONPATH'])
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/apport/report.py", line 543, in 
add_proc_info
  self.add_proc_environ(pid, extraenv)
File "/usr/lib/python3/dist-packages/apport/report.py", line 610, in 
add_proc_environ
  env = _read_file('environ', dir_fd=proc_pid_fd).replace('\n', '\\n')
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
_read_file
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
  TypeError: argument should be integer or None, not list

  Patch below:

  # diff -u  /usr/lib/python3/dist-packages/apport/report.py 
/usr/lib/python3/dist-packages/apport/report.py.new 
  --- /usr/lib/python3/dist-packages/apport/report.py   2019-11-01 
14:16:39.375968798 +0100
  +++ /usr/lib/python3/dist-packages/apport/report.py.new   2019-11-01 
14:17:58.035128006 +0100
  @@ -540,7 +540,7 @@
   self['ProcCwd'] = os.readlink('cwd', dir_fd=proc_pid_fd)
   except OSError:
   pass
  -self.add_proc_environ(pid, extraenv)
  +self.add_proc_environ(pid, proc_pid_fd, extraenv)
   self['ProcStatus'] = _read_file('status', dir_fd=proc_pid_fd)
   self['ProcCmdline'] = _read_file('cmdline', 
dir_fd=proc_pid_fd).rstrip('\0')
   self['ProcMaps'] = _read_maps(proc_pid_fd)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3-apport 2.20.9-0ubuntu7.8
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  CrashReports: 640:1000:1004:35152:2019-11-01 14:00:47.150214442 
+0100:2019-11-01 14:00:47.150214442 +0100:/var/crash/_usr_bin_snimpy.1000.crash
  Date: Fri Nov  1 14:18:16 2019
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1850929] Re: python3-apport regression: missing argument in Report.add_proc_environ call

2019-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.1-0ubuntu2.21

---
apport (2.20.1-0ubuntu2.21) xenial-security; urgency=medium

  * SECURITY REGRESSION: missing argument in Report.add_proc_environ
call (LP: #1850929)
- apport/report.py: call add_proc_environ using named arguments
  and move proc_pid_dir keyword to last to keep api compatibility.

 -- Tiago Stürmer Daitx   Tue, 05 Nov 2019
02:49:27 +

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1850929

Title:
  python3-apport regression: missing argument in Report.add_proc_environ
  call

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  This is a regression in the 2.20.9-0ubuntu7.8 security update of
  apport

  # lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  Reproduce the bug:

  $ python3
  Python 3.6.8 (default, Oct  7 2019, 12:59:55) 
  [GCC 8.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import apport
  >>> import os
  >>> report = apport.Report()
  >>> report.add_proc_info(os.getpid(), extraenv=['PYTHONHOME', 'PYTHONPATH'])
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/apport/report.py", line 543, in 
add_proc_info
  self.add_proc_environ(pid, extraenv)
File "/usr/lib/python3/dist-packages/apport/report.py", line 610, in 
add_proc_environ
  env = _read_file('environ', dir_fd=proc_pid_fd).replace('\n', '\\n')
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
_read_file
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
  TypeError: argument should be integer or None, not list

  Patch below:

  # diff -u  /usr/lib/python3/dist-packages/apport/report.py 
/usr/lib/python3/dist-packages/apport/report.py.new 
  --- /usr/lib/python3/dist-packages/apport/report.py   2019-11-01 
14:16:39.375968798 +0100
  +++ /usr/lib/python3/dist-packages/apport/report.py.new   2019-11-01 
14:17:58.035128006 +0100
  @@ -540,7 +540,7 @@
   self['ProcCwd'] = os.readlink('cwd', dir_fd=proc_pid_fd)
   except OSError:
   pass
  -self.add_proc_environ(pid, extraenv)
  +self.add_proc_environ(pid, proc_pid_fd, extraenv)
   self['ProcStatus'] = _read_file('status', dir_fd=proc_pid_fd)
   self['ProcCmdline'] = _read_file('cmdline', 
dir_fd=proc_pid_fd).rstrip('\0')
   self['ProcMaps'] = _read_maps(proc_pid_fd)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3-apport 2.20.9-0ubuntu7.8
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  CrashReports: 640:1000:1004:35152:2019-11-01 14:00:47.150214442 
+0100:2019-11-01 14:00:47.150214442 +0100:/var/crash/_usr_bin_snimpy.1000.crash
  Date: Fri Nov  1 14:18:16 2019
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1850929] Re: python3-apport regression: missing argument in Report.add_proc_environ call

2019-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.9-0ubuntu7.9

---
apport (2.20.9-0ubuntu7.9) bionic-security; urgency=medium

  * SECURITY REGRESSION: missing argument in Report.add_proc_environ
call (LP: #1850929)
- apport/report.py: call add_proc_environ using named arguments
  and move proc_pid_dir keyword to last to keep api compatibility.

 -- Tiago Stürmer Daitx   Tue, 05 Nov 2019
02:49:27 +

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1850929

Title:
  python3-apport regression: missing argument in Report.add_proc_environ
  call

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  This is a regression in the 2.20.9-0ubuntu7.8 security update of
  apport

  # lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  Reproduce the bug:

  $ python3
  Python 3.6.8 (default, Oct  7 2019, 12:59:55) 
  [GCC 8.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import apport
  >>> import os
  >>> report = apport.Report()
  >>> report.add_proc_info(os.getpid(), extraenv=['PYTHONHOME', 'PYTHONPATH'])
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/apport/report.py", line 543, in 
add_proc_info
  self.add_proc_environ(pid, extraenv)
File "/usr/lib/python3/dist-packages/apport/report.py", line 610, in 
add_proc_environ
  env = _read_file('environ', dir_fd=proc_pid_fd).replace('\n', '\\n')
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
_read_file
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
  TypeError: argument should be integer or None, not list

  Patch below:

  # diff -u  /usr/lib/python3/dist-packages/apport/report.py 
/usr/lib/python3/dist-packages/apport/report.py.new 
  --- /usr/lib/python3/dist-packages/apport/report.py   2019-11-01 
14:16:39.375968798 +0100
  +++ /usr/lib/python3/dist-packages/apport/report.py.new   2019-11-01 
14:17:58.035128006 +0100
  @@ -540,7 +540,7 @@
   self['ProcCwd'] = os.readlink('cwd', dir_fd=proc_pid_fd)
   except OSError:
   pass
  -self.add_proc_environ(pid, extraenv)
  +self.add_proc_environ(pid, proc_pid_fd, extraenv)
   self['ProcStatus'] = _read_file('status', dir_fd=proc_pid_fd)
   self['ProcCmdline'] = _read_file('cmdline', 
dir_fd=proc_pid_fd).rstrip('\0')
   self['ProcMaps'] = _read_maps(proc_pid_fd)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3-apport 2.20.9-0ubuntu7.8
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  CrashReports: 640:1000:1004:35152:2019-11-01 14:00:47.150214442 
+0100:2019-11-01 14:00:47.150214442 +0100:/var/crash/_usr_bin_snimpy.1000.crash
  Date: Fri Nov  1 14:18:16 2019
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851325] Re: libneon27 has problems with MS IIS 7.5 WebDAV

2019-11-04 Thread Ubuntu Foundations Team Bug Bot
The attachment "Patch to add translate f headers." seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to neon27 in Ubuntu.
https://bugs.launchpad.net/bugs/1851325

Title:
  libneon27 has problems with MS IIS 7.5 WebDAV

Status in neon27 package in Ubuntu:
  New

Bug description:
  libneon doesn't work with Microsoft's IIS 7.5 WebDAV implementation, because 
there is an extra translate:f header added.
  This is not just for MS's implementation, other WebDAV servers apparently 
added it too.
  https://docs.oracle.com/cd/E19146-01/821-1828/gczya/index.html
  
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-wdvse/501879f9-3875-4d7a-ab88-3cecab440034

  The docs say that IF the client doesn't send the header, the server should 
send back a URI to the resource, like a redirect, at least I think so.
  But, MS's implementation doesn't.  Instead it just returns a "server error 
500".

  This happens to me ONLY with files that have no extension.
  Example: using the WebDAV cadaver client, I can get "readme.txt",but I can't 
get a file called "config" (eg the config file in a .git folder).

  I used Burp Suite to inspect the HTTPS comms with the server and
  discovered the translate header.I tested with curl and sure enough it
  worked with the header.

  curl -H "translate: f" --insecure --proxy 127.0.0.1:8080 --user "user:pass" 
https://the.host.name/folder/project.git/config
  WORKED
  Without the -H "translate: f", the curl call did not work.

  The translate header seems to be added to just about every call to the
  WebDAV server, except HEAD.

  Attached is a patch that fixes up libneon, and that fixes cadaver and other 
such clients.
  I had to make an additional patch for davfs2 as it builds the requests 
without using neon's basic API.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libneon27-gnutls 0.30.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177
  Uname: Linux 4.4.0-148-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Nov  5 11:55:14 2019
  InstallationDate: Installed on 2015-12-15 (1420 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151128
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.utf8
   SHELL=/bin/bash
  SourcePackage: neon27
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink

2019-11-04 Thread Launchpad Bug Tracker
[Expired for gdb (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gdb (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1818918

Title:
  gdb doesn't search in debug-file-directory for .gnu_debugaltlink

Status in gdb package in Ubuntu:
  Expired

Bug description:
  As far as I can tell gdb version 8.2.90 isn't searching the debug-
  file-directory, which I set, for the '.gnu_debugaltlink' which is in
  the debug symbols. Here's the error I'm seeing:

  Type "apropos word" to search for commands related to "word".
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
  could not find '.gnu_debugaltlink' file for 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
  (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)

  Here's part of an strace of what's going on behind the scenes:

  lstat("/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
 {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 
  openat(AT_FDCWD, 
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

  This is the only time "/usr/lib/debug" is searched, generally
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox/usr/lib/debug/" is used. I'll attach the full strace though.

  For completeness here's the gdb command I'm using:

  Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
  /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
  --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
  prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
  --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
  -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
  dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox//usr/bin/gnome-calculator"' --ex 'core-file
  /tmp/apport_core_1b6dn6np'

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851325] [NEW] libneon27 has problems with MS IIS 7.5 WebDAV

2019-11-04 Thread edice
Public bug reported:

libneon doesn't work with Microsoft's IIS 7.5 WebDAV implementation, because 
there is an extra translate:f header added.
This is not just for MS's implementation, other WebDAV servers apparently added 
it too.
https://docs.oracle.com/cd/E19146-01/821-1828/gczya/index.html
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-wdvse/501879f9-3875-4d7a-ab88-3cecab440034

The docs say that IF the client doesn't send the header, the server should send 
back a URI to the resource, like a redirect, at least I think so.
But, MS's implementation doesn't.  Instead it just returns a "server error 500".

This happens to me ONLY with files that have no extension.
Example: using the WebDAV cadaver client, I can get "readme.txt",but I can't 
get a file called "config" (eg the config file in a .git folder).

I used Burp Suite to inspect the HTTPS comms with the server and
discovered the translate header.I tested with curl and sure enough it
worked with the header.

curl -H "translate: f" --insecure --proxy 127.0.0.1:8080 --user "user:pass" 
https://the.host.name/folder/project.git/config
WORKED
Without the -H "translate: f", the curl call did not work.

The translate header seems to be added to just about every call to the
WebDAV server, except HEAD.

Attached is a patch that fixes up libneon, and that fixes cadaver and other 
such clients.
I had to make an additional patch for davfs2 as it builds the requests without 
using neon's basic API.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libneon27-gnutls 0.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177
Uname: Linux 4.4.0-148-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Nov  5 11:55:14 2019
InstallationDate: Installed on 2015-12-15 (1420 days ago)
InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151128
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.utf8
 SHELL=/bin/bash
SourcePackage: neon27
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug rosa third-party-packages

** Patch added: "Patch to add translate f headers."
   
https://bugs.launchpad.net/bugs/1851325/+attachment/5302889/+files/neon_translate_f.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to neon27 in Ubuntu.
https://bugs.launchpad.net/bugs/1851325

Title:
  libneon27 has problems with MS IIS 7.5 WebDAV

Status in neon27 package in Ubuntu:
  New

Bug description:
  libneon doesn't work with Microsoft's IIS 7.5 WebDAV implementation, because 
there is an extra translate:f header added.
  This is not just for MS's implementation, other WebDAV servers apparently 
added it too.
  https://docs.oracle.com/cd/E19146-01/821-1828/gczya/index.html
  
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-wdvse/501879f9-3875-4d7a-ab88-3cecab440034

  The docs say that IF the client doesn't send the header, the server should 
send back a URI to the resource, like a redirect, at least I think so.
  But, MS's implementation doesn't.  Instead it just returns a "server error 
500".

  This happens to me ONLY with files that have no extension.
  Example: using the WebDAV cadaver client, I can get "readme.txt",but I can't 
get a file called "config" (eg the config file in a .git folder).

  I used Burp Suite to inspect the HTTPS comms with the server and
  discovered the translate header.I tested with curl and sure enough it
  worked with the header.

  curl -H "translate: f" --insecure --proxy 127.0.0.1:8080 --user "user:pass" 
https://the.host.name/folder/project.git/config
  WORKED
  Without the -H "translate: f", the curl call did not work.

  The translate header seems to be added to just about every call to the
  WebDAV server, except HEAD.

  Attached is a patch that fixes up libneon, and that fixes cadaver and other 
such clients.
  I had to make an additional patch for davfs2 as it builds the requests 
without using neon's basic API.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libneon27-gnutls 0.30.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177
  Uname: Linux 4.4.0-148-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Nov  5 11:55:14 2019
  InstallationDate: Installed on 2015-12-15 (1420 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151128
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.utf8
   SHELL=/bin/bash
  SourcePackage: neon27
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1851322] [NEW] VPN auto-connect is not working

2019-11-04 Thread Mathieu Tarral
Public bug reported:

Hi,

This is a duplicate of bug:
https://bugs.launchpad.net/network-manager/+bug/1718931

It is marked as fixed, but the feature is still broken for me.

I configured my Wifi connection to automatically connect to a VPN, but it only 
works if I manually
connect to the Wifi via NetworkManager.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: network-manager 1.20.4-2ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  5 04:07:00 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-09-26 (39 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager
 Importance: Undecided
 Status: New

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

** Attachment added: "Video recorded at boot time, right after login, where the 
Wifi connexion fails because of the VPN auto-connect being broken"
   
https://bugs.launchpad.net/bugs/1851322/+attachment/5302868/+files/vpn-auto-connect.webm

** Also affects: network-manager
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1851322

Title:
  VPN auto-connect is not working

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  This is a duplicate of bug:
  https://bugs.launchpad.net/network-manager/+bug/1718931

  It is marked as fixed, but the feature is still broken for me.

  I configured my Wifi connection to automatically connect to a VPN, but it 
only works if I manually
  connect to the Wifi via NetworkManager.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 04:07:00 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-26 (39 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

2019-11-04 Thread jules dusablon
I don't see how this is "invalid". This is a bad pulseaudio behaviour
that can consistently be reproduced on upgrade from 18.04 to 19.10.
Obviously, I'm also affected by it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1850887

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

2019-11-04 Thread jules dusablon
@Daniel van Vugt (vanvugt): the switch-on-connect is indeed an
intentional design choice that works well to switch inputs on detection.
A power event should _not_ be a trigger for this.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1850887

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1849785] Re: FTBFS on i386/ppc64/s390x (Eoan+Focal)

2019-11-04 Thread Bug Watch Updater
** Changed in: libseccomp
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1849785

Title:
  FTBFS on i386/ppc64/s390x (Eoan+Focal)

Status in libseccomp:
  Fix Released
Status in libseccomp package in Ubuntu:
  Triaged
Status in libseccomp source package in Eoan:
  Triaged

Bug description:
  Due to the python 3.8 transition in focal this was rebuilt but fails atm.
  => 
https://launchpadlibrarian.net/448119198/buildlog_ubuntu-focal-s390x.libseccomp_2.4.1-0ubuntu0.19.10.4_BUILDING.txt.gz

  The simulations fail in this case:
   batch name: 36-sim-ipc_syscalls
   test mode:  c
   test type:  bpf-sim
  Test 36-sim-ipc_syscalls%%001-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%002-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%003-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%004-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%005-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%006-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%007-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%008-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%009-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%010-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%011-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%012-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%013-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%014-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%015-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%016-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%017-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%018-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%019-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%020-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%021-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%022-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%023-1 result:   ERROR 36-sim-ipc_syscalls rc=14
  Test 36-sim-ipc_syscalls%%024-1 result:   ERROR 36-sim-ipc_syscalls rc=14
   test mode:  c
   test type:  bpf-valgrind
  Test 36-sim-ipc_syscalls%%025-1 result:   FAILURE 36-sim-ipc_syscalls 
rc=14
   batch name: 37-sim-ipc_syscalls_be
   test mode:  c
   test type:  bpf-sim
   test arch:  s390

  
   batch name: 37-sim-ipc_syscalls_be
   test mode:  c
   test type:  bpf-sim
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%001-1 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%002-1 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%003-1 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%004-1 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%005-1 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%006-1 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%007-1 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%008-1 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%009-1 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%010-1 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%011-1 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test arch:  s390
  Test 37-sim-ipc_syscalls_be%%012-1 result:   ERROR 37-sim-ipc_syscalls_be 
rc=14
   test mode:  c
   test type:  bpf-valgrind
  Test 37-sim-ipc_syscalls_be%%013-1 result:   FAILURE 
37-sim-ipc_syscalls_be rc=14

  
  It is always the s390x test - even when running on i386/ppc64
  On x86_64 this test succeeds:

  Test 36-sim-ipc_syscalls%%025-1 result:   SUCCESS
   batch name: 37-sim-ipc_syscalls_be
   test mode:  c
   test type:  bpf-sim
   test arch:  s390

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1798840] Re: Night Light is not functioning

2019-11-04 Thread MegaBrutal
** Tags added: eoan

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1798840

Title:
  Night Light is not functioning

Status in gnome-control-center package in Ubuntu:
  Expired
Status in wayland package in Ubuntu:
  New

Bug description:
  Night Light is not shading/filtering the screen anymore after the update to 
Cosmic (Ubuntu 18.10) from Bionic (Ubuntu 18.04 LTS).
  It still appears as an option and all the settings work, but the feature 
itself isn't filtering out blue light from the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 11:03:28 2018
  InstallationDate: Installed on 2018-08-17 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798840/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1798840] Re: Night Light is not functioning

2019-11-04 Thread MegaBrutal
Now I found out that it depends on whether I login with Xorg or Wayland.
Night Light works with Xorg, but doesn't with Wayland.
I honestly don't remember whether I was running Disco with Xorg or Wayland, 
most probably I just went with the default. My guess is that Disco used Xorg by 
default and Eoan changed to Wayland, that's why I thought it's broken with the 
upgrade.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1798840

Title:
  Night Light is not functioning

Status in gnome-control-center package in Ubuntu:
  Expired
Status in wayland package in Ubuntu:
  New

Bug description:
  Night Light is not shading/filtering the screen anymore after the update to 
Cosmic (Ubuntu 18.10) from Bionic (Ubuntu 18.04 LTS).
  It still appears as an option and all the settings work, but the feature 
itself isn't filtering out blue light from the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 19 11:03:28 2018
  InstallationDate: Installed on 2018-08-17 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798840/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851300] Re: Xubuntu 18.04 passwd file in etc displays passwd unencrypted

2019-11-04 Thread Colin Watson
This is certainly nothing to do with base-passwd: while it populates
initial system accounts in /etc/passwd, it doesn't deal with managing
entries there that correspond to user accounts.

** Changed in: base-passwd (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-passwd in Ubuntu.
https://bugs.launchpad.net/bugs/1851300

Title:
  Xubuntu 18.04 passwd file in etc displays passwd unencrypted

Status in base-passwd package in Ubuntu:
  Invalid
Status in pam package in Ubuntu:
  Incomplete
Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have a workshop where I provide mostly Ubuntu community editions in
  computers and help people coming with computers already setup with a
  *buntu version. A lady came to me as she couldn't master her computer,
  (there is someone in town who installs Ubuntu editions without
  teaching his clients how to deal with their machines).

  She has an Ubuntu Xfce (Xubuntu) 18.04.x which is what she currently
  uses, especially as she doesn't know how to boot to the othe OS. :s

  So I chrooted from a live to recreate her Xubuntu user passwd, and oh
  surprise! The /etc/passwd file was showing her password in plain text,
  unencrypted. (I could read it easily, it was her family name!).

  I have not had the time to dig further, check other editions and
  versions exept the ones I use, however I think, as it has happend in
  the paste, the persons in charge should look into it and check all
  recent Ubuntu and community versions editions (if relevant).

  Thanks for your work!

  Best regards,
  Mélodie

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1851300/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1847638] Re: initramfs-tools tests depend on linux-image-generic, not available on i386

2019-11-04 Thread Adam Conrad
** Summary changed:

- initramfs-tools-core fails to install on i386 
+ initramfs-tools tests depend on linux-image-generic, not available on i386

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1847638

Title:
  initramfs-tools tests depend on linux-image-generic, not available on
  i386

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Autopkgtest fails on i386 due to kmod pulling in linux-image-
  generic:i386 , but it does not exist anymore in Eoan.

  http://autopkgtest.ubuntu.com/packages/i/initramfs-tools/eoan/i386

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/i/initramfs-tools/20191009_203931_515d7@/log.gz
 :
  ...
  Broken autopkgtest-satdep:i386 Depends on linux-image-generic:i386 < none @un 
H >
Removing autopkgtest-satdep:i386 because I can't find 
linux-image-generic:i386
  Done
  ...

  Manual testing:

  ubuntu@autopkgtest:/initramfs-tools-0.133ubuntu10$ sudo apt install 
initramfs-tools-core
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  initramfs-tools-core is already the newest version (0.133ubuntu10).
  initramfs-tools-core set to manually installed.
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   autopkgtest-satdep : Depends: linux-image-generic but it is not installable
Depends: qemu-system
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).
  ubuntu@autopkgtest:/initramfs-tools-0.133ubuntu10$ sudo apt install kmod
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  kmod is already the newest version (26-1ubuntu1).
  kmod set to manually installed.
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   autopkgtest-satdep : Depends: linux-image-generic but it is not installable
Depends: qemu-system
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1847638/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851300] Re: Xubuntu 18.04 passwd file in etc displays passwd unencrypted

2019-11-04 Thread Seth Arnold
I've selected the most likely packages to be involved, based on a guess.
Without knowing how the user attempted to set their password though,
this is going to be pretty impossible to track down.

/etc/passwd hasn't had passwords stored in it by default for something
like 25 years. My best guess at the moment is some vastly inappropriate
tool was used somewhere along the way (with suspicion leaning towards
web-based 'consoles').

If you can figure out how this happened (or better yet, tell us how to
recreate it), please do report back and mark the bug New again.

Thanks

** Information type changed from Private Security to Public Security

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

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

** Changed in: base-passwd (Ubuntu)
   Status: New => Incomplete

** Changed in: pam (Ubuntu)
   Status: New => Incomplete

** Changed in: shadow (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-passwd in Ubuntu.
https://bugs.launchpad.net/bugs/1851300

Title:
  Xubuntu 18.04 passwd file in etc displays passwd unencrypted

Status in base-passwd package in Ubuntu:
  Incomplete
Status in pam package in Ubuntu:
  Incomplete
Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have a workshop where I provide mostly Ubuntu community editions in
  computers and help people coming with computers already setup with a
  *buntu version. A lady came to me as she couldn't master her computer,
  (there is someone in town who installs Ubuntu editions without
  teaching his clients how to deal with their machines).

  She has an Ubuntu Xfce (Xubuntu) 18.04.x which is what she currently
  uses, especially as she doesn't know how to boot to the othe OS. :s

  So I chrooted from a live to recreate her Xubuntu user passwd, and oh
  surprise! The /etc/passwd file was showing her password in plain text,
  unencrypted. (I could read it easily, it was her family name!).

  I have not had the time to dig further, check other editions and
  versions exept the ones I use, however I think, as it has happend in
  the paste, the persons in charge should look into it and check all
  recent Ubuntu and community versions editions (if relevant).

  Thanks for your work!

  Best regards,
  Mélodie

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1851300/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1672822] Re: sound only coming from left speaker on acer predator (fresh install)

2019-11-04 Thread Sergei Shutov
** Also affects: pulseaudio
   Importance: Undecided
   Status: New

** No longer affects: pulseaudio

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1672822

Title:
  sound only coming from left speaker on acer predator (fresh install)

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: Ubuntu  16.10 and a fresh install of 17.04 and even
  fedora F25-WORK-x86_64-20170228 via live usb

  Device: acer predator: G9-593-7757 15,6"/i7-7700/32 GB RAM/512 GB
  SSD/1 TB HDD/GTX1070

  expected: sound comes out of both left and right speaker and the
  subwoofer

  what happened instead:
  Sound only comes out of the left speaker or subwoofer.

  More system information:

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  audio chip (on motherboard): VGA Chip nVidia N17E-G2-A1 GP104-725-A1

  note that that is only 1 device, one would expect several here.

  I attempted to fix this by modifying the /etc/pulse/deamon.conf into the 
following:
  # This file is part of PulseAudio.
  #
  # PulseAudio is free software; you can redistribute it and/or modify
  # it under the terms of the GNU Lesser General Public License as published by
  # the Free Software Foundation; either version 2 of the License, or
  # (at your option) any later version.
  #
  # PulseAudio is distributed in the hope that it will be useful, but
  # WITHOUT ANY WARRANTY; without even the implied warranty of
  # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  # General Public License for more details.
  #
  # You should have received a copy of the GNU Lesser General Public License
  # along with PulseAudio; if not, see .

  ## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
  ## more information. Default values are commented out.  Use either ; or # for
  ## commenting.

  ; daemonize = no
  ; fail = yes
  ; allow-module-loading = yes
  ; allow-exit = yes
  ; use-pid-file = yes
  ; system-instance = no
  ; local-server-type = user
  ; enable-shm = yes
  ; enable-memfd = yes
  ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
  ; lock-memory = no
  ; cpu-limit = no

  ; high-priority = yes
  ; nice-level = -11

  ; realtime-scheduling = yes
  ; realtime-priority = 5

  ; exit-idle-time = 20
  ; scache-idle-time = 20

  ; dl-search-path = (depends on architecture)

  ; load-default-script-file = yes
  ; default-script-file = /etc/pulse/default.pa

  ; log-target = auto
  ; log-level = notice
  ; log-meta = no
  ; log-time = no
  ; log-backtrace = 0

  ; resample-method = speex-float-1
  ; enable-remixing = yes
   enable-lfe-remixing = yes
  ; lfe-crossover-freq = 0

  flat-volumes = no

  ; rlimit-fsize = -1
  ; rlimit-data = -1
  ; rlimit-stack = -1
  ; rlimit-core = -1
  ; rlimit-as = -1
  ; rlimit-rss = -1
  ; rlimit-nproc = -1
  ; rlimit-nofile = 256
  ; rlimit-memlock = -1
  ; rlimit-locks = -1
  ; rlimit-sigpending = -1
  ; rlimit-msgqueue = -1
  ; rlimit-nice = 31
  ; rlimit-rtprio = 9
  ; rlimit-rttime = 20

  ; default-sample-format = s16le
  ; default-sample-rate = 44100
  ; alternate-sample-rate = 48000
  default-sample-channels = 3
  default-channel-map = front-left,front-right,lfe

  ; default-fragments = 4
  ; default-fragment-size-msec = 25

  ; enable-deferred-volume = yes
  deferred-volume-safety-margin-usec = 1
  ; deferred-volume-extra-delay-usec = 0

  but this did not work. I also tried various other permutations to see
  if changing the order of  front-left,front-right,lfe would work but it
  did not. I also tried to see if it would work in fedora but the same
  problem occurred there. When on ubuntu 16.10 at first only the
  subwoofer seemed to be working and altering the file only the left
  speaker was working. On ubuntu 17.04 only the left speaker was working
  regardless of how I altered the above file.

  
  Note that the speakers work perfectly fine on windows 10. 

  Looking around online there seem to be a lot of problems with acer
  predator laptops and sound on ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1672822/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1744328] Re: libfreebl3.so should be public, not in the nss subdir

2019-11-04 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/nss/+git/nss/+merge/375115

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1744328

Title:
  libfreebl3.so should be public, not in the nss subdir

Status in nss package in Ubuntu:
  Fix Released
Status in nss package in Debian:
  New

Bug description:
  Hi,
  I tried to move the chrony dependency from tomcrypt to libnss to avoid 
universe dependencies.
  While doing so I found that libfreebl3 is not "normally" linkable being 
outside the normal ld paths.

  E.g. sample program
  #include 
  #include 
  #include 
  int main(int argc, char **argv) {
  NSSLOWHASH_Begin(NSSLOWHASH_NewContext(NSSLOW_Init(), HASH_AlgSHA512));
  return 0;
  }

  Build:
  gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wmissing-prototypes -Wall -pthread -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/nss -I/usr/include/nspr -o docheck docheck.c -lfreebl3 
-Wl,-Bsymbolic-functions -Wl,-z,relro -v -Wl,-v -L/usr/lib/x86_64-linux-gnu/nss

  Then:
  ldd docheck
  will give you
  libfreebl3.so => not found

  Obviously a link into /usr/lib/x86_64-linux-gnu/ fixes the issue but
  needs some more consideration if that is the thing we want (there
  might be a reason it is where it is).

  Note: Required to go on with the chrony MIR which is rather urgent to
  be sorted out as it has a lot of other dependencies that need to be
  adapted.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1837734] Re: libnss3 reads fips_enabled flag and automatically switches to FIPS mode

2019-11-04 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/nss/+git/nss/+merge/375115

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1837734

Title:
  libnss3 reads fips_enabled flag and automatically switches to FIPS
  mode

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Xenial:
  Won't Fix
Status in nss source package in Bionic:
  Fix Committed
Status in nss source package in Disco:
  Fix Committed
Status in nss source package in Eoan:
  Fix Released

Bug description:
  [IMPACT]
  nss is not a FIPS certified library. On a machine running FIPS enabled 
kernel, the library by default goes into FIPS mode if 
/proc/sys/crypto/fips_enabled=1. This is an untested configuration and since 
libnss3 is not a certified library we propose disabling reading the 
'fips_enabled' flag and therefore switching the library automatically into FIPS 
mode. 

  The proposed patch disables reading the /proc/sys/crypto/fips_enabled
  flag. The users of the library however can force nss into FIPS mode
  via an environment variable. We plan to leave it as is so as not to
  regress existing users who may be using it.

  The issue impacts libnss3 versions in eoan, disco, bionic and xenial.

  lsb_release -rd
  Description:  Ubuntu Eoan Ermine (development branch)
  Release: 19.10

  Version: 2:3.45-1ubuntu1

  lsb_release -rd
  Description: Ubuntu Disco Dingo
  Release: 19.04

  Version: 2:3.42-1ubuntu2

  lsb_release -rd
  Description:  Ubuntu Bionic Beaver
  Release:  18.04

  Version: 2:3.35-2ubuntu2.3

  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Version: 2:3.28.4-0ubuntu0.16.04

  [FIX]
  This fix proposes to disable libnss3 reading proc/sys/crypto/fips_enabled. We 
only want fips certified modules reading this file and running in fips mode. 
libnss3 is not one of our fips certified modules, so should not be reading this 
along with our fips certified modules to determine whether to run in fips mode.

  Users who do want to run the library in FIPS mode can do so by using
  the environment variable "NSS_FIPS". We propose to leave it as is so
  as not to regress anyone using this. The user who is using this option
  should be doing so with the awareness.

  [TEST]
  Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in 
FIPS mode. With the patch fix no crashes were observed when launching firefox 
browser.
  Without the patch fix, firefox crashes.

  Tested on a xenial and bionic desktop ISO running non-FIPS generic
  kernel. With the patch fix, firefox worked as expected and no changes
  were observed.

  [REGRESSION POTENTIAL]
  The regression potential for this is small. A FIPS kernel is required to
  create /proc/sys/crypto/fips_enabled and it is not available in standard 
ubuntu archive. For users forcing FIPS through environment variable, nothing 
has changed.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

2019-11-04 Thread NeoTheThird
** Tags added: eoan

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1574120

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in pm-utils package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1574120/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

2019-11-04 Thread Bruno Well Dantas Morais
This bug affects me too.
Commenting the "load-module module-switch-on-connect" line didn't work for me 
though.

I posted originally here:
https://askubuntu.com/questions/1185903/why-cant-i-set-a-default-output-audio-device-in-ubuntu-19-10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1850887

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1850293] Re: libep11 depends on old libssl for disco/eoan/focal

2019-11-04 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1850293

Title:
  libep11 depends on old libssl for disco/eoan/focal

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  Invalid

Bug description:
  If using the newest version of libep11_2.1.0-8_s390x.deb with
  Disco/Eoan/Focal 
  downloaded from 
  http://public.dhe.ibm.com/security/cryptocards/pciecc3/EP11/2.1.0/

  Following problem occur.:
  libep11 : Depends: libssl1.0.0 but it is not installable 

  rmadison --arch=s390x libssl1.0.0
   libssl1.0.0 | 1.0.2g-1ubuntu4| xenial  | s390x
   libssl1.0.0 | 1.0.2g-1ubuntu4.15 | xenial-security | s390x
   libssl1.0.0 | 1.0.2g-1ubuntu4.15 | xenial-updates  | s390x
   libssl1.0.0 | 1.0.2n-1ubuntu5| bionic  | s390x
   libssl1.0.0 | 1.0.2n-1ubuntu5.3  | bionic-security | s390x
   libssl1.0.0 | 1.0.2n-1ubuntu5.3  | bionic-updates  | s390x

  $ rmadison --arch=s390x libssl1.1
   libssl1.1 | 1.1.0g-2ubuntu4  | bionic  | s390x
   libssl1.1 | 1.1.1-1ubuntu2.1~18.04.4 | bionic-security | s390x
   libssl1.1 | 1.1.1-1ubuntu2.1~18.04.4 | bionic-updates  | s390x
   libssl1.1 | 1.1.1b-1ubuntu2  | disco   | s390x
   libssl1.1 | 1.1.1b-1ubuntu2.4| disco-updates   | s390x
   libssl1.1 | 1.1.1c-1ubuntu4  | eoan| s390x
   libssl1.1 | 1.1.1c-1ubuntu4  | focal   | s390x 

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  11:58:56 AM: $ sudo apt install ./libep11_2.1.0-8_s390x.deb
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'libep11' instead of './libep11_2.1.0-8_s390x.deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libep11 : Depends: libssl1.0.0 but it is not installable
  E: Unable to correct problems, you have held broken packages.
  ubuntu@s1lp15:~$ sudo apt install ./libep11-dev_2.1.0-8_s390x.deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'libep11-dev' instead of './libep11-dev_2.1.0-8_s390x.deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libep11-dev : Depends: libep11 (= 2.1.0-8) but it is not installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1850293/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851257] Re: Apport to have launcher Icon and Start GUI for new users

2019-11-04 Thread ianp5a
** Description changed:

  REASON: To encourage bug reporting and reduce the amount of special knowledge 
required to file bugs, make the ubuntu-bug command discoverable, and more 
non-IT user friendly.
  Knowledge of the right package, the URL to search packages, the URL to report 
bugs and the URL with documentation on how to report bugs is needed today and 
should be integrated.
- Also to ensure Apport is used to gather system information automatically, 
rather than the user filing a manual report without this data. 
+ Also to ensure Apport is used to gather system information automatically, 
rather than the user filing a manual report without this data.
  
- Minimal Requirement: 
- 1) Add a launcher ICON with a clear name like "Bug Report Tool" 
+ Minimal Requirement:
+ 1) Add a launcher ICON with a clear name like "Bug Report Tool"
  2) The icon starts a small GUI that triggers the ubuntu-bug dialog as today.
-  
+ 
  On this single panel GUI are 5 items:
-  a) Package selection button: The user interactively selects a window of the 
application, to find it's package name. Same as with "ubuntu-bug-w"
-  b) Package Selection by type: A navigator to find the package where no 
application window is running. E.G. For desktop panels, menus, or apps that 
won't start. (users often fail here otherwise)
-  c) Package search field: If the above items don't work, or the user knows 
the package name, a search field like on https://packages.ubuntu.com can solve 
this.
-  d) Help Button. URL link to Reporting Bugs Documentation
-  e) Start/Send button: This starts the rest of the ubuntu-bug dialog as 
today. If no package was selected the Apport dialog begins as today and offers 
it's choices as usual.
+  a) Package selection button: The user interactively selects a window of the 
application, to find it's package name. Same as with "ubuntu-bug-w"
+  b) Package Selection by type: A navigator to find the package where no 
application window is running. E.G. For desktop panels, menus, or apps that 
won't start. (users often fail here otherwise)
+  c) Package search field: If the above items don't work, or the user knows 
the package name, a search field like on https://packages.ubuntu.com can solve 
this.
+  d) Help Button. URL link to Reporting Bugs Documentation
+  e) Start/Send button: This starts the rest of the ubuntu-bug dialog as 
today. If no package was selected the Apport dialog begins as today and offers 
it's choices as usual.
  
- Barrier: Finding the package is a problem to normal users. Many do not know 
what a package is. Even if they know it, a Launchpad search often does not find 
it. 
+ Barrier: Finding the package is a problem to normal users. Many do not know 
what a package is. Even if they know it, a Launchpad search often does not find 
it.
  EG Blender Snap on Kubuntu works OK, but the Blender Eaon-Universe has a 
missing library. Neither search for Kubuntu or Blender finds the package.
- EG: 'ubuntu-bugs' was not found on search on Launchpad or 
"packages.ubuntu.com". People would not guess Apport.
+ EG: 'ubuntu-bugs' was not found on search on Launchpad or 
"packages.ubuntu.com". People would not guess Apport. Even searching apport on 
packages.ubuntu.com does not find apport package!!
  EG: The command line is not familiar to non-IT users, so "dpkg -l" is 
unknown. It was mentioned on Alan Popes 1:12h video on bug reporting, listing 
many of the difficulties and tricks required:
  https://www.youtube.com/watch?time_continue=2427=68ImDFjiq28
  
  Bugs from non-IT users are underreported due to these barriers. Meaning
  they end up having a very different experience of Ubuntu than the
  experienced users, who might wonder why.
  
  ADDITIONS to this requirement:
  a) If you make a wrong selection in the apport choices, add new "Next/Back" 
buttons to allow options to be changed. Today you have to exit and start all 
over again.
  b) If the bug belongs upstream or at another bug tracker, forward the bug to 
the correct place automatically. The user cannot know where to post it. The Bug 
reporting tool should be a one-stop shop.
  c) If b) is too much work, add a help information and a URL to guide the user 
to report the bug in the best possible place.

** Description changed:

  REASON: To encourage bug reporting and reduce the amount of special knowledge 
required to file bugs, make the ubuntu-bug command discoverable, and more 
non-IT user friendly.
  Knowledge of the right package, the URL to search packages, the URL to report 
bugs and the URL with documentation on how to report bugs is needed today and 
should be integrated.
  Also to ensure Apport is used to gather system information automatically, 
rather than the user filing a manual report without this data.
  
  Minimal Requirement:
  1) Add a launcher ICON with a clear name like "Bug Report Tool"
  2) The icon starts a small GUI that triggers the ubuntu-bug dialog as today.
  
  On this single panel GUI are 5 items:
   a) 

[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2019-11-04 Thread Frank Heimes
** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1790098

Title:
  vlan created on bond fails auto activation on updating parent network
  bond

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  Auto activation of Vlan created over network-bond fails if bond is 
deactivated and reactivated.
   
  Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar 
Deshpande(manda...@in.ibm.com) 
   
  ---uname output---
  Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Created a network bond with static IP address (and no IPv6 address); 
active backup mode; ARP polling; single slave.

  2. Created a VLAN using said network bond with static IPv4 address
  (and no IPv6 address).

  3. Can ping from the appliance to a target on both links (the parent
  bond and the VLAN).

  4. Switched to another slave for the created bond

  5. Can still ping from the appliance to a target via the parent bond;
  however, cannot ping to the target via the VLAN.

  =
  Detailed steps:

  1. Initial setup:
  
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  2. Create Netwrok-bond with one slave:
  
  root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 
ipv4.method disabled ipv6.method ignore
  Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully 
added.

  root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1
  Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) 
successfully added.
  root@S36MANDAR:~# nmcli con up bond-slave-enc1d40
  Connection successfully activated (D-Bus active path: 
/org/freedesktop/NetworkManager/ActiveConnection/18)
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40 
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  3. Create vlan over mybond1:
  ===
  root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname 
vlanbond.100 dev mybond1 id 100  ipv4.method disabled ipv6.method ignore
  Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully 
added.
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE
   
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40   
   
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80   
   
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00   
   
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1   
   
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  
vlanbond.100 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --
   

  4. Reactivate bond : 
  =
  root@S36MANDAR:~# nmcli con up mybond1
  Connection successfully activated (master waiting for slaves) (D-Bus active 
path: /org/freedesktop/NetworkManager/ActiveConnection/30)

  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  enc1d40 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  --  
  encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e  ethernet  --  
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  --  

  As is seen, vlan(vlanbond.100) did not get activated

  Now, if manually I make vlan connection up, it gets 

[Touch-packages] [Bug 1851257] [NEW] Apport to have launcher Icon and Start GUI for new users

2019-11-04 Thread ianp5a
Public bug reported:

REASON: To encourage bug reporting and reduce the amount of special knowledge 
required to file bugs, make the ubuntu-bug command discoverable, and more 
non-IT user friendly.
Knowledge of the right package, the URL to search packages, the URL to report 
bugs and the URL with documentation on how to report bugs is needed today and 
should be integrated.
Also to ensure Apport is used to gather system information automatically, 
rather than the user filing a manual report without this data. 

Minimal Requirement: 
1) Add a launcher ICON with a clear name like "Bug Report Tool" 
2) The icon starts a small GUI that triggers the ubuntu-bug dialog as today.
 
On this single panel GUI are 5 items:
 a) Package selection button: The user interactively selects a window of the 
application, to find it's package name. Same as with "ubuntu-bug-w"
 b) Package Selection by type: A navigator to find the package where no 
application window is running. E.G. For desktop panels, menus, or apps that 
won't start. (users often fail here otherwise)
 c) Package search field: If the above items don't work, or the user knows the 
package name, a search field like on https://packages.ubuntu.com can solve this.
 d) Help Button. URL link to Reporting Bugs Documentation
 e) Start/Send button: This starts the rest of the ubuntu-bug dialog as today. 
If no package was selected the Apport dialog begins as today and offers it's 
choices as usual.

Barrier: Finding the package is a problem to normal users. Many do not know 
what a package is. Even if they know it, a Launchpad search often does not find 
it. 
EG Blender Snap on Kubuntu works OK, but the Blender Eaon-Universe has a 
missing library. Neither search for Kubuntu or Blender finds the package.
EG: 'ubuntu-bugs' was not found on search on Launchpad or 
"packages.ubuntu.com". People would not guess Apport.
EG: The command line is not familiar to non-IT users, so "dpkg -l" is unknown. 
It was mentioned on Alan Popes 1:12h video on bug reporting, listing many of 
the difficulties and tricks required:
https://www.youtube.com/watch?time_continue=2427=68ImDFjiq28

Bugs from non-IT users are underreported due to these barriers. Meaning
they end up having a very different experience of Ubuntu than the
experienced users, who might wonder why.

ADDITIONS to this requirement:
a) If you make a wrong selection in the apport choices, add new "Next/Back" 
buttons to allow options to be changed. Today you have to exit and start all 
over again.
b) If the bug belongs upstream or at another bug tracker, forward the bug to 
the correct place automatically. The user cannot know where to post it. The Bug 
reporting tool should be a one-stop shop.
c) If b) is too much work, add a help information and a URL to guide the user 
to report the bug in the best possible place.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1851257

Title:
  Apport to have launcher Icon and Start GUI for new users

Status in apport package in Ubuntu:
  New

Bug description:
  REASON: To encourage bug reporting and reduce the amount of special knowledge 
required to file bugs, make the ubuntu-bug command discoverable, and more 
non-IT user friendly.
  Knowledge of the right package, the URL to search packages, the URL to report 
bugs and the URL with documentation on how to report bugs is needed today and 
should be integrated.
  Also to ensure Apport is used to gather system information automatically, 
rather than the user filing a manual report without this data. 

  Minimal Requirement: 
  1) Add a launcher ICON with a clear name like "Bug Report Tool" 
  2) The icon starts a small GUI that triggers the ubuntu-bug dialog as today.
   
  On this single panel GUI are 5 items:
   a) Package selection button: The user interactively selects a window of the 
application, to find it's package name. Same as with "ubuntu-bug-w"
   b) Package Selection by type: A navigator to find the package where no 
application window is running. E.G. For desktop panels, menus, or apps that 
won't start. (users often fail here otherwise)
   c) Package search field: If the above items don't work, or the user knows 
the package name, a search field like on https://packages.ubuntu.com can solve 
this.
   d) Help Button. URL link to Reporting Bugs Documentation
   e) Start/Send button: This starts the rest of the ubuntu-bug dialog as 
today. If no package was selected the Apport dialog begins as today and offers 
it's choices as usual.

  Barrier: Finding the package is a problem to normal users. Many do not know 
what a package is. Even if they know it, a Launchpad search often does not find 
it. 
  EG Blender Snap on Kubuntu works OK, but the Blender Eaon-Universe has a 
missing library. Neither search for Kubuntu or Blender finds 

[Touch-packages] [Bug 1850293] Re: libep11 depends on old libssl for disco/eoan/focal

2019-11-04 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2019-11-04 10:47 EDT---
Upcoming version of libep11 will fix that problem. This version will coming 
soon.

** Tags removed: severity-high
** Tags added: severity-medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1850293

Title:
  libep11 depends on old libssl for disco/eoan/focal

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in openssl package in Ubuntu:
  Invalid

Bug description:
  If using the newest version of libep11_2.1.0-8_s390x.deb with
  Disco/Eoan/Focal 
  downloaded from 
  http://public.dhe.ibm.com/security/cryptocards/pciecc3/EP11/2.1.0/

  Following problem occur.:
  libep11 : Depends: libssl1.0.0 but it is not installable 

  rmadison --arch=s390x libssl1.0.0
   libssl1.0.0 | 1.0.2g-1ubuntu4| xenial  | s390x
   libssl1.0.0 | 1.0.2g-1ubuntu4.15 | xenial-security | s390x
   libssl1.0.0 | 1.0.2g-1ubuntu4.15 | xenial-updates  | s390x
   libssl1.0.0 | 1.0.2n-1ubuntu5| bionic  | s390x
   libssl1.0.0 | 1.0.2n-1ubuntu5.3  | bionic-security | s390x
   libssl1.0.0 | 1.0.2n-1ubuntu5.3  | bionic-updates  | s390x

  $ rmadison --arch=s390x libssl1.1
   libssl1.1 | 1.1.0g-2ubuntu4  | bionic  | s390x
   libssl1.1 | 1.1.1-1ubuntu2.1~18.04.4 | bionic-security | s390x
   libssl1.1 | 1.1.1-1ubuntu2.1~18.04.4 | bionic-updates  | s390x
   libssl1.1 | 1.1.1b-1ubuntu2  | disco   | s390x
   libssl1.1 | 1.1.1b-1ubuntu2.4| disco-updates   | s390x
   libssl1.1 | 1.1.1c-1ubuntu4  | eoan| s390x
   libssl1.1 | 1.1.1c-1ubuntu4  | focal   | s390x 

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  11:58:56 AM: $ sudo apt install ./libep11_2.1.0-8_s390x.deb
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'libep11' instead of './libep11_2.1.0-8_s390x.deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libep11 : Depends: libssl1.0.0 but it is not installable
  E: Unable to correct problems, you have held broken packages.
  ubuntu@s1lp15:~$ sudo apt install ./libep11-dev_2.1.0-8_s390x.deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'libep11-dev' instead of './libep11-dev_2.1.0-8_s390x.deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libep11-dev : Depends: libep11 (= 2.1.0-8) but it is not installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1850293/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851244] Re: setfacl shows wrong message: "Invalid argument" when the problem is about existance of username

2019-11-04 Thread Paul White
** Package changed: ubuntu => acl (Ubuntu)

** Tags added: bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to acl in Ubuntu.
https://bugs.launchpad.net/bugs/1851244

Title:
  setfacl shows wrong message: "Invalid argument" when the problem is
  about existance of username

Status in acl package in Ubuntu:
  New

Bug description:
  in Ubuntu 18.04 the following command has a wrong output as shown:
  #sudo setfacl -d -m u:apache:rwx /var/www/
  setfacl: Option -m: Invalid argument near character 3

  But the exact problem is about username which should be for example in this 
case: www-data
  Output of setacl is supposed to be something like: "the user apache does not 
exist"

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851244] [NEW] setfacl shows wrong message: "Invalid argument" when the problem is about existance of username

2019-11-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

in Ubuntu 18.04 the following command has a wrong output as shown:
#sudo setfacl -d -m u:apache:rwx /var/www/
setfacl: Option -m: Invalid argument near character 3

But the exact problem is about username which should be for example in this 
case: www-data
Output of setacl is supposed to be something like: "the user apache does not 
exist"

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

-- 
setfacl shows wrong message: "Invalid argument" when the problem is about 
existance of username
https://bugs.launchpad.net/bugs/1851244
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to acl in Ubuntu.

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1831252] Re: panic=-1 is completely ignored by the initrd causing unexpected behaviour

2019-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.122ubuntu8.16

---
initramfs-tools (0.122ubuntu8.16) xenial; urgency=medium

  * Add support for panic=-1 value (LP: #1831252)

 -- Julian Andres Klode   Mon, 07 Oct 2019 12:53:35
+0200

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1831252

Title:
  panic=-1 is completely ignored by the initrd causing unexpected
  behaviour

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in initramfs-tools source package in Disco:
  Fix Released
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  in Ubuntu Core we default to using panic=-1 on the kernel command line 
(documented at [1]) to speed up the auto-rollback mechanism of the kernel. on a 
kernel level this works just fine and the system reboots immediately ...

  when in the initramfs during boot and a panic occurs, no reboot
  happens at all, the initrd spawns a shell regardless of the panic=
  value ...

  
  [Test case]

  Before booting change root=$foo to root=x$foo - this will make it
  panic. Then test that

  1) "panic=-1" causes an immediate reboot
  2) "panic=5" waits 5 seconds
  3) no "panic" drops you to a shell

  [Regression potential]
  This adds some very specific checks for -1 in places that use ${panic}, as 
such the regression potential is somewhat limited. If there were a regression, 
it could be a syntax error (causing boot to fail) or a sleep not working 
correctly (causing sleep to, well, not sleep) - but that's unrealistic.

  
  [Other info]
  this is caused by a filter in  /usr/share/initramfs-tools/init

  panic=*)
  panic="${x#panic=}"
  case ${panic} in
  *[![:digit:].]*)
  panic=
  ;;
  esac
  ;;

  this function only lets positive values through, else panic= simply
  gets unset

  the panic() function itself is also not capable of handling negative
  values, it has a sleep call that interprets negative values as
  commandline options instead of simply ignoring a negative sleep time
  [2] (line 11).

  the filter in the init script should allow the -1 value (to comply
  with the kernel documentation and behaviour) and the panic() function
  should properly skip the sleep call when a negative value for panic=
  is set.

  [1] 
https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931
  [2] https://paste.ubuntu.com/p/mswD8Cd869/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1831252] Re: panic=-1 is completely ignored by the initrd causing unexpected behaviour

2019-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.130ubuntu3.9

---
initramfs-tools (0.130ubuntu3.9) bionic; urgency=medium

  * Add support for panic=-1 value (LP: #1831252)

 -- Julian Andres Klode   Mon, 07 Oct 2019 12:53:35
+0200

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1831252

Title:
  panic=-1 is completely ignored by the initrd causing unexpected
  behaviour

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in initramfs-tools source package in Disco:
  Fix Released
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  in Ubuntu Core we default to using panic=-1 on the kernel command line 
(documented at [1]) to speed up the auto-rollback mechanism of the kernel. on a 
kernel level this works just fine and the system reboots immediately ...

  when in the initramfs during boot and a panic occurs, no reboot
  happens at all, the initrd spawns a shell regardless of the panic=
  value ...

  
  [Test case]

  Before booting change root=$foo to root=x$foo - this will make it
  panic. Then test that

  1) "panic=-1" causes an immediate reboot
  2) "panic=5" waits 5 seconds
  3) no "panic" drops you to a shell

  [Regression potential]
  This adds some very specific checks for -1 in places that use ${panic}, as 
such the regression potential is somewhat limited. If there were a regression, 
it could be a syntax error (causing boot to fail) or a sleep not working 
correctly (causing sleep to, well, not sleep) - but that's unrealistic.

  
  [Other info]
  this is caused by a filter in  /usr/share/initramfs-tools/init

  panic=*)
  panic="${x#panic=}"
  case ${panic} in
  *[![:digit:].]*)
  panic=
  ;;
  esac
  ;;

  this function only lets positive values through, else panic= simply
  gets unset

  the panic() function itself is also not capable of handling negative
  values, it has a sleep call that interprets negative values as
  commandline options instead of simply ignoring a negative sleep time
  [2] (line 11).

  the filter in the init script should allow the -1 value (to comply
  with the kernel documentation and behaviour) and the panic() function
  should properly skip the sleep call when a negative value for panic=
  is set.

  [1] 
https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931
  [2] https://paste.ubuntu.com/p/mswD8Cd869/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1790098] Update Released

2019-11-04 Thread Łukasz Zemczak
The verification of the Stable Release Update for network-manager has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1790098

Title:
  vlan created on bond fails auto activation on updating parent network
  bond

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  Auto activation of Vlan created over network-bond fails if bond is 
deactivated and reactivated.
   
  Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar 
Deshpande(manda...@in.ibm.com) 
   
  ---uname output---
  Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Created a network bond with static IP address (and no IPv6 address); 
active backup mode; ARP polling; single slave.

  2. Created a VLAN using said network bond with static IPv4 address
  (and no IPv6 address).

  3. Can ping from the appliance to a target on both links (the parent
  bond and the VLAN).

  4. Switched to another slave for the created bond

  5. Can still ping from the appliance to a target via the parent bond;
  however, cannot ping to the target via the VLAN.

  =
  Detailed steps:

  1. Initial setup:
  
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  2. Create Netwrok-bond with one slave:
  
  root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 
ipv4.method disabled ipv6.method ignore
  Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully 
added.

  root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1
  Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) 
successfully added.
  root@S36MANDAR:~# nmcli con up bond-slave-enc1d40
  Connection successfully activated (D-Bus active path: 
/org/freedesktop/NetworkManager/ActiveConnection/18)
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40 
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  3. Create vlan over mybond1:
  ===
  root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname 
vlanbond.100 dev mybond1 id 100  ipv4.method disabled ipv6.method ignore
  Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully 
added.
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE
   
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40   
   
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80   
   
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00   
   
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1   
   
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  
vlanbond.100 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --
   

  4. Reactivate bond : 
  =
  root@S36MANDAR:~# nmcli con up mybond1
  Connection successfully activated (master waiting for slaves) (D-Bus active 
path: /org/freedesktop/NetworkManager/ActiveConnection/30)

  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  enc1d40 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 

[Touch-packages] [Bug 1825946] Update Released

2019-11-04 Thread Łukasz Zemczak
The verification of the Stable Release Update for network-manager has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1825946

Title:
  'nm' autopkgtest fails due to GI stderr output

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

Bug description:
  [impact]

  'nm' testcase contains:
  from gi.repository import NetworkManager, NMClient, GLib  


 

  which generates output to stderr:
  /tmp/autopkgtest.naU0ts/build.riU/src/debian/tests/nm:23: PyGIWarning: 
NetworkManager was imported without specifying a version first. Use 
gi.require_version('NetworkManager', '1.0') before import to ensure that the 
right version gets loaded.

  the gi.require_version call has already been added to cosmic and
  disco.

  [test case]

  see http://autopkgtest.ubuntu.com/packages/network-manager bionic test
  results.

  [other info]

  this only fails intermittently, but the failure is clearly not an
  actual problem.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1825946] Re: 'nm' autopkgtest fails due to GI stderr output

2019-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.2

---
network-manager (1.10.6-2ubuntu1.2) bionic; urgency=medium

  [ Till Kamppeter ]
  * debian/tests/nm: Add gi.require_version() calls for NetworkManager
and NMClient to avoid stderr output which fails the test. (LP: #1825946)

  [ Dariusz Gadomski ]
  * d/p/fix-dns-leak-lp1754671.patch: backport of DNS leak fix. (LP: #1754671)
  * d/p/lp1790098.patch: retry activating devices when the parent becomes
managed. (LP: #1790098)

 -- Dariusz Gadomski   Sat, 07 Sep 2019
16:10:59 +0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1825946

Title:
  'nm' autopkgtest fails due to GI stderr output

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

Bug description:
  [impact]

  'nm' testcase contains:
  from gi.repository import NetworkManager, NMClient, GLib  


 

  which generates output to stderr:
  /tmp/autopkgtest.naU0ts/build.riU/src/debian/tests/nm:23: PyGIWarning: 
NetworkManager was imported without specifying a version first. Use 
gi.require_version('NetworkManager', '1.0') before import to ensure that the 
right version gets loaded.

  the gi.require_version call has already been added to cosmic and
  disco.

  [test case]

  see http://autopkgtest.ubuntu.com/packages/network-manager bionic test
  results.

  [other info]

  this only fails intermittently, but the failure is clearly not an
  actual problem.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1754671] Update Released

2019-11-04 Thread Łukasz Zemczak
The verification of the Stable Release Update for network-manager has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
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:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond

2019-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.2

---
network-manager (1.10.6-2ubuntu1.2) bionic; urgency=medium

  [ Till Kamppeter ]
  * debian/tests/nm: Add gi.require_version() calls for NetworkManager
and NMClient to avoid stderr output which fails the test. (LP: #1825946)

  [ Dariusz Gadomski ]
  * d/p/fix-dns-leak-lp1754671.patch: backport of DNS leak fix. (LP: #1754671)
  * d/p/lp1790098.patch: retry activating devices when the parent becomes
managed. (LP: #1790098)

 -- Dariusz Gadomski   Sat, 07 Sep 2019
16:10:59 +0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1790098

Title:
  vlan created on bond fails auto activation on updating parent network
  bond

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  Auto activation of Vlan created over network-bond fails if bond is 
deactivated and reactivated.
   
  Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar 
Deshpande(manda...@in.ibm.com) 
   
  ---uname output---
  Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Created a network bond with static IP address (and no IPv6 address); 
active backup mode; ARP polling; single slave.

  2. Created a VLAN using said network bond with static IPv4 address
  (and no IPv6 address).

  3. Can ping from the appliance to a target on both links (the parent
  bond and the VLAN).

  4. Switched to another slave for the created bond

  5. Can still ping from the appliance to a target via the parent bond;
  however, cannot ping to the target via the VLAN.

  =
  Detailed steps:

  1. Initial setup:
  
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  2. Create Netwrok-bond with one slave:
  
  root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 
ipv4.method disabled ipv6.method ignore
  Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully 
added.

  root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1
  Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) 
successfully added.
  root@S36MANDAR:~# nmcli con up bond-slave-enc1d40
  Connection successfully activated (D-Bus active path: 
/org/freedesktop/NetworkManager/ActiveConnection/18)
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40 
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --  

  3. Create vlan over mybond1:
  ===
  root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname 
vlanbond.100 dev mybond1 id 100  ipv4.method disabled ipv6.method ignore
  Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully 
added.
  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE
   
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40   
   
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80   
   
  enc8f00 2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00   
   
  mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond  mybond1   
   
  vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e  vlan  
vlanbond.100 
  enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --
   

  4. Reactivate bond : 
  =
  root@S36MANDAR:~# nmcli con up mybond1
  Connection successfully activated (master waiting for slaves) (D-Bus active 
path: /org/freedesktop/NetworkManager/ActiveConnection/30)

  root@S36MANDAR:~# nmcli c s
  NAMEUUID  TYPE  DEVICE  
  enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  

[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.2

---
network-manager (1.10.6-2ubuntu1.2) bionic; urgency=medium

  [ Till Kamppeter ]
  * debian/tests/nm: Add gi.require_version() calls for NetworkManager
and NMClient to avoid stderr output which fails the test. (LP: #1825946)

  [ Dariusz Gadomski ]
  * d/p/fix-dns-leak-lp1754671.patch: backport of DNS leak fix. (LP: #1754671)
  * d/p/lp1790098.patch: retry activating devices when the parent becomes
managed. (LP: #1790098)

 -- Dariusz Gadomski   Sat, 07 Sep 2019
16:10:59 +0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754671

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
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:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1831252] Re: panic=-1 is completely ignored by the initrd causing unexpected behaviour

2019-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.131ubuntu19.2

---
initramfs-tools (0.131ubuntu19.2) disco; urgency=medium

  * Add support for panic=-1 value (LP: #1831252)

 -- Julian Andres Klode   Mon, 07 Oct 2019 12:46:48
+0200

** Changed in: initramfs-tools (Ubuntu Disco)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1831252

Title:
  panic=-1 is completely ignored by the initrd causing unexpected
  behaviour

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in initramfs-tools source package in Disco:
  Fix Released
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  in Ubuntu Core we default to using panic=-1 on the kernel command line 
(documented at [1]) to speed up the auto-rollback mechanism of the kernel. on a 
kernel level this works just fine and the system reboots immediately ...

  when in the initramfs during boot and a panic occurs, no reboot
  happens at all, the initrd spawns a shell regardless of the panic=
  value ...

  
  [Test case]

  Before booting change root=$foo to root=x$foo - this will make it
  panic. Then test that

  1) "panic=-1" causes an immediate reboot
  2) "panic=5" waits 5 seconds
  3) no "panic" drops you to a shell

  [Regression potential]
  This adds some very specific checks for -1 in places that use ${panic}, as 
such the regression potential is somewhat limited. If there were a regression, 
it could be a syntax error (causing boot to fail) or a sleep not working 
correctly (causing sleep to, well, not sleep) - but that's unrealistic.

  
  [Other info]
  this is caused by a filter in  /usr/share/initramfs-tools/init

  panic=*)
  panic="${x#panic=}"
  case ${panic} in
  *[![:digit:].]*)
  panic=
  ;;
  esac
  ;;

  this function only lets positive values through, else panic= simply
  gets unset

  the panic() function itself is also not capable of handling negative
  values, it has a sleep call that interprets negative values as
  commandline options instead of simply ignoring a negative sleep time
  [2] (line 11).

  the filter in the init script should allow the -1 value (to comply
  with the kernel documentation and behaviour) and the panic() function
  should properly skip the sleep call when a negative value for panic=
  is set.

  [1] 
https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931
  [2] https://paste.ubuntu.com/p/mswD8Cd869/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1831252] Update Released

2019-11-04 Thread Łukasz Zemczak
The verification of the Stable Release Update for initramfs-tools has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1831252

Title:
  panic=-1 is completely ignored by the initrd causing unexpected
  behaviour

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in initramfs-tools source package in Disco:
  Fix Released
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  in Ubuntu Core we default to using panic=-1 on the kernel command line 
(documented at [1]) to speed up the auto-rollback mechanism of the kernel. on a 
kernel level this works just fine and the system reboots immediately ...

  when in the initramfs during boot and a panic occurs, no reboot
  happens at all, the initrd spawns a shell regardless of the panic=
  value ...

  
  [Test case]

  Before booting change root=$foo to root=x$foo - this will make it
  panic. Then test that

  1) "panic=-1" causes an immediate reboot
  2) "panic=5" waits 5 seconds
  3) no "panic" drops you to a shell

  [Regression potential]
  This adds some very specific checks for -1 in places that use ${panic}, as 
such the regression potential is somewhat limited. If there were a regression, 
it could be a syntax error (causing boot to fail) or a sleep not working 
correctly (causing sleep to, well, not sleep) - but that's unrealistic.

  
  [Other info]
  this is caused by a filter in  /usr/share/initramfs-tools/init

  panic=*)
  panic="${x#panic=}"
  case ${panic} in
  *[![:digit:].]*)
  panic=
  ;;
  esac
  ;;

  this function only lets positive values through, else panic= simply
  gets unset

  the panic() function itself is also not capable of handling negative
  values, it has a sleep call that interprets negative values as
  commandline options instead of simply ignoring a negative sleep time
  [2] (line 11).

  the filter in the init script should allow the -1 value (to comply
  with the kernel documentation and behaviour) and the panic() function
  should properly skip the sleep call when a negative value for panic=
  is set.

  [1] 
https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931
  [2] https://paste.ubuntu.com/p/mswD8Cd869/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831252/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1850929] Re: python3-apport regression: missing argument in Report.add_proc_environ call

2019-11-04 Thread Sebastien Bacher
** Tags added: rls-bb-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1850929

Title:
  python3-apport regression: missing argument in Report.add_proc_environ
  call

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  This is a regression in the 2.20.9-0ubuntu7.8 security update of
  apport

  # lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  Reproduce the bug:

  $ python3
  Python 3.6.8 (default, Oct  7 2019, 12:59:55) 
  [GCC 8.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import apport
  >>> import os
  >>> report = apport.Report()
  >>> report.add_proc_info(os.getpid(), extraenv=['PYTHONHOME', 'PYTHONPATH'])
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/apport/report.py", line 543, in 
add_proc_info
  self.add_proc_environ(pid, extraenv)
File "/usr/lib/python3/dist-packages/apport/report.py", line 610, in 
add_proc_environ
  env = _read_file('environ', dir_fd=proc_pid_fd).replace('\n', '\\n')
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
_read_file
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
  TypeError: argument should be integer or None, not list

  Patch below:

  # diff -u  /usr/lib/python3/dist-packages/apport/report.py 
/usr/lib/python3/dist-packages/apport/report.py.new 
  --- /usr/lib/python3/dist-packages/apport/report.py   2019-11-01 
14:16:39.375968798 +0100
  +++ /usr/lib/python3/dist-packages/apport/report.py.new   2019-11-01 
14:17:58.035128006 +0100
  @@ -540,7 +540,7 @@
   self['ProcCwd'] = os.readlink('cwd', dir_fd=proc_pid_fd)
   except OSError:
   pass
  -self.add_proc_environ(pid, extraenv)
  +self.add_proc_environ(pid, proc_pid_fd, extraenv)
   self['ProcStatus'] = _read_file('status', dir_fd=proc_pid_fd)
   self['ProcCmdline'] = _read_file('cmdline', 
dir_fd=proc_pid_fd).rstrip('\0')
   self['ProcMaps'] = _read_maps(proc_pid_fd)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3-apport 2.20.9-0ubuntu7.8
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  CrashReports: 640:1000:1004:35152:2019-11-01 14:00:47.150214442 
+0100:2019-11-01 14:00:47.150214442 +0100:/var/crash/_usr_bin_snimpy.1000.crash
  Date: Fri Nov  1 14:18:16 2019
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1849608] Re: systemd resolv should separate the output of stdout and stderr

2019-11-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu Eoan)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1849608

Title:
  systemd resolv should separate the output of stdout and stderr

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  dhclient fails to notify resolved about DNS servers due to bash-
  specific redirect inside 'resolved' hook script

  [test case]

  see original description below

  [regression potential]

  any regression would likely cause resolved not to be aware of
  dhclient-provided dns servers

  [other info]

  This is needed only in Eoan and later; X/B/D do not have the bash-
  specific redirect '&>' in their hook file.

  original description:
  ---

  
  The file /etc/dhcp/dhclient-enter-hooks.d/resolved
  provided by systemd (242-7ubuntu3) causes the dhclient failing to get DNS due 
to systemd-resolved is not run.
  This issue can be reproduced on Ubuntu Eoan:
  ==
  root@eoan:~# dhclient -v
  Internet Systems Consortium DHCP Client 4.4.1
  Copyright 2004-2018 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens224/00:0c:29:92:d4:da
  Sending on   LPF/ens224/00:0c:29:92:d4:da
  Listening on LPF/ens192/00:0c:29:92:d4:d0
  Sending on   LPF/ens192/00:0c:29:92:d4:d0
  Listening on LPF/ens160/00:0c:29:92:d4:c6
  Sending on   LPF/ens160/00:0c:29:92:d4:c6
  Sending on   Socket/fallback
  DHCPDISCOVER on ens224 to 255.255.255.255 port 67 interval 3 (xid=0x6d9fb33d)
  DHCPDISCOVER on ens192 to 255.255.255.255 port 67 interval 3 (xid=0xeb8fda26)
  DHCPREQUEST for 192.168.120.4 on ens160 to 255.255.255.255 port 67 
(xid=0x6d39545d)
  DHCPACK of 192.168.120.4 from 192.168.120.254 (xid=0x5d54396d)
  RTNETLINK answers: File exists
  d41d8cd98f00b204e9800998ecf8427e  
/run/systemd/resolved.conf.d/isc-dhcp-v4-ens160.conf
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens160.conf: No such file or 
directory
  5025823d750dda1f3f15e306c4a0afce  
/run/systemd/resolved.conf.d/isc-dhcp-v4-ens160.conf
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens160.conf: No such file or 
directory
  bound to 192.168.120.4 -- renewal in 111 seconds.
  root@eoan:~# resolvectl status |grep DNS
  MulticastDNS setting: no
    DNSOverTLS setting: no
    DNSSEC setting: no
  DNSSEC supported: no
    DNSSEC NTA: 10.in-addr.arpa
  MulticastDNS setting: no
    DNSOverTLS setting: no
    DNSSEC setting: no
  DNSSEC supported: no
  MulticastDNS setting: no
    DNSOverTLS setting: no
    DNSSEC setting: no
  DNSSEC supported: no
  MulticastDNS setting: no
    DNSOverTLS setting: no
    DNSSEC setting: no
  DNSSEC supported: no
  ==

  Attached please find the patch for this. The output for md5sum in the
  hook file resolv should separate the stdout and stderr so it won't
  compare the wrong data.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 372364] Re: move vim-tiny to / filesystem?

2019-11-04 Thread Bug Watch Updater
** Changed in: vim (Debian)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/372364

Title:
  move vim-tiny to / filesystem?

Status in vim package in Ubuntu:
  Triaged
Status in vim package in Debian:
  Fix Released

Bug description:
  I've noticed a few times now that nano is the default editor in
  Ubuntu, which I can to a certain extent understand because of the
  learning curve of the vi editor. However, I do believe the vi editor
  is specified in the posix standard as part of the Unix command set.

  As a Linux/Unix educator, I tell my students that vi is the one editor
  that they can depend on to be available on all Unix systems.
  Unfortunately, ubuntu is no longer a Unix system by _this_ definition
  :-(

  Please include a statically compiled vi-clone in the base-install in
  /bin/vi to fix this problem!

  thank you!

  /Simon

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1850009] Re: Issue with detecting new state in dhclient-enter-hooks.d/resolved

2019-11-04 Thread Balint Reczey
*** This bug is a duplicate of bug 1849608 ***
https://bugs.launchpad.net/bugs/1849608

** This bug has been marked a duplicate of bug 1849608
   systemd resolv should separate the output of stdout and stderr

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1850009

Title:
  Issue with detecting new state in dhclient-enter-hooks.d/resolved

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 19.10 I noticed that resolving hostnames stopped
  working.

  Quick release, which package and version info:

  root@caret:~# lsb_release -r
  Release:19.10
  root@caret:~# dpkg -S /etc/dhcp/dhclient-enter-hooks.d/resolved
  systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved
  root@caret:~# apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  
  The file /etc/resolv.conf was pointing to the local instance of 
systemd-resolved however there was no search line, indicating something wasn't 
quite right.

  Restarting the systemd-resolved service did recreate /etc/resolv.conf
  with expected search line.

  After much debugging, I've worked out what was going wrong.

  The dhcp hook file /etc/dhcp/dhclient-enter-hooks.d/resolved has a bug
  in the resolver state change logic.

  This may also impact on tickets 1805183, 1832050, 1832053 and maybe
  others.

  When doing the md5sum of the old and new state, the command is wrong.
  It isn't sending STDOUT (and optionally STDERR) to the temp file but
  rather putting the md5sum command into the background and then
  creating an empty file for both states. Which obviously isn't
  different, so systemd-resolved doesn't restart.

  Quick diff of a working version (I'm not capturing STDERR but one can
  with "2>&1")

  === BEGIN PATCH ===
  *** .brk-resolved-20191027  2019-10-27 11:19:56.210069032 +1030
  --- resolved2019-10-27 11:30:17.156381734 +1030
  ***
  *** 30,36 
  mkdir -p $statedir

  oldstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf &> $oldstate
  if [ -n "$new_domain_name_servers" ] ; then
  cat <$statedir/isc-dhcp-v4-$interface.conf
[Resolve]
  --- 30,36 
  mkdir -p $statedir

  oldstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf > $oldstate
  if [ -n "$new_domain_name_servers" ] ; then
  cat <$statedir/isc-dhcp-v4-$interface.conf
[Resolve]
  ***
  *** 55,61 
  fi

  newstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf &> $newstate
  if ! cmp $oldstate $newstate; then
  systemctl try-reload-or-restart systemd-resolved.service
  fi
  --- 55,61 
  fi

  newstate="$(mktemp)"
  !   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf > $newstate
  if ! cmp $oldstate $newstate; then
  systemctl try-reload-or-restart systemd-resolved.service
  fi
  ===  END  PATCH ===

  Also, the script removes the script removes the $oldstate file but
  doesn't remove the $newstate file.

  Not sure how this made it through QA testing... But breaking DHCP
  client shouldn't happen like this.

  ivan.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 27 11:48:33 2019
  InstallationDate: Installed on 2017-04-21 (918 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  IpRoute:
   default via 172.16.1.14 dev enp0s5 
   150.101.89.32/28 dev enp0s5 scope link 
   169.254.0.0/16 dev enp0s5 scope link metric 1000 
   172.16.1.0/24 dev enp0s5 proto kernel scope link src 172.16.1.120
  IwConfig:
   lono wireless extensions.
   
   enp0s5no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=vt100
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)
  nmcli-con:
   
  nmcli-dev:
   DEVICE  TYPE  STATE  

[Touch-packages] [Bug 1851229] [NEW] device_list:268: no soundcards found

2019-11-04 Thread Harris Mulbah
Public bug reported:

Couldn't play my music because gstreamer wasn't installed. After
installation of gstreamer music can play but can't be heard. System
settings have dummy output as the selected sound card.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
Uname: Linux 3.13.0-170-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Mon Nov  4 11:33:59 2019
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1851229

Title:
  device_list:268: no soundcards found

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Couldn't play my music because gstreamer wasn't installed. After
  installation of gstreamer music can play but can't be heard. System
  settings have dummy output as the selected sound card.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Nov  4 11:33:59 2019
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851229/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851143] Re: X11 session all commands ignored.

2019-11-04 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1850969 ***
https://bugs.launchpad.net/bugs/1850969

** This bug has been marked a duplicate of bug 1850969
   x11 session all mouse or keyboard action ignored

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1851143

Title:
  X11 session all commands ignored.

Status in xorg package in Ubuntu:
  New

Bug description:
  Starting the x11 session I'm able to open the terminal, just once, so I was 
able to file this bug.
  After that any action, with mouse or keyboard are ignored. This is to 
document bug #1850969

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  3 16:40:23 2019
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2019-10-30 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191030)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=1210135d-e0e3-467e-9083-5f35bd1d110d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

2019-11-04 Thread Miroslav Matějů
I’ve tested version 8.1-0ubuntu3.2 from ubuntu-proposed on my Xubuntu
18.04.3 x86_64 from both the command line and Qt Creator and the problem
has not appeared.

I am also setting verification-done because no other supported releases
seem affected.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1848200

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
  on breakpoint when running a 32-bit application (on 64-bit Ubuntu).

  [Test Case]
  This can be reproduced with a simple “hello world” program:

  $ cat hello.c
  #include 
  int main()
  {
     // printf() displays the string inside quotation
     printf("Hello, World!");
     return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  [Regression Risk]
  Test case ran on arm64 and regression tested using the above test case on 
amd64, i386 and s390x.

  This regression was fixed on the upstream gdb-8.1 branch within a few
  weeks of the breakage back in May 2018. Since then there have been no
  other fixes in this area on that branch, implying this fixed the issue
  and there were no further regressions discovered.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851225] Re: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-11-04 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1851225

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.3 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  During installation of upgrade to version 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
  Uname: Linux 4.4.0-166-generic i686
  .var.log.apt.history.log:
   
  ApportVersion: 2.20.1-0ubuntu2.20
  Architecture: i386
  Date: Mon Nov  4 11:03:07 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-12-05 (2159 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.3 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to xenial on 2019-11-04 (0 days ago)
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 2019-04-30T12:03:15

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1851225/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1849608] Re: systemd resolv should separate the output of stdout and stderr

2019-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 243-3ubuntu1

---
systemd (243-3ubuntu1) focal; urgency=medium

  [ Dan Streetman ]
  * Fix resolved fallback to TCP (LP: #1849658)
Author: Dan Streetman
File: 
debian/patches/resolved-set-stream-type-during-DnsStream-creation.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f1ee30b13c9d2d34968b09ce620f3bc24a1a78c7
  * Separate stderr and stdout of /etc/dhcp/dhclient-enter-hooks.d/resolved
(LP: #1849608)
Author: Dan Streetman
File: debian/extra/dhclient-enter-resolved-hook

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fec4d6d026488a1d32ad9dceef18d9ea9c8acbda

  [ Balint Reczey ]
  * Merge to Ubuntu from Debian experimental
  * Refresh patches:
- Dropped changes:
  * udevadm trigger: do not propagate EACCES and ENODEV.
File: 
debian/patches/udevadm-trigger-do-not-propagate-EACCES-and-ENODEV.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=334e3fdc904de05105c78763c88220c1976d1946
  * Pass personality test even when i386 userland runs on amd64 kernel
File: 
debian/patches/debian/UBUNTU-test-Pass-personality-test-even-when-i386-userland-runs-o.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=42e0bfc426f19430f6768ef4922a9531a345765f

systemd (243-3) experimental; urgency=medium

  * Import patches from v243-stable branch (up to ef677436aa)

 -- Balint Reczey   Wed, 30 Oct 2019 15:19:33 +0100

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1849608

Title:
  systemd resolv should separate the output of stdout and stderr

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  New
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  dhclient fails to notify resolved about DNS servers due to bash-
  specific redirect inside 'resolved' hook script

  [test case]

  see original description below

  [regression potential]

  any regression would likely cause resolved not to be aware of
  dhclient-provided dns servers

  [other info]

  This is needed only in Eoan and later; X/B/D do not have the bash-
  specific redirect '&>' in their hook file.

  original description:
  ---

  
  The file /etc/dhcp/dhclient-enter-hooks.d/resolved
  provided by systemd (242-7ubuntu3) causes the dhclient failing to get DNS due 
to systemd-resolved is not run.
  This issue can be reproduced on Ubuntu Eoan:
  ==
  root@eoan:~# dhclient -v
  Internet Systems Consortium DHCP Client 4.4.1
  Copyright 2004-2018 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/ens224/00:0c:29:92:d4:da
  Sending on   LPF/ens224/00:0c:29:92:d4:da
  Listening on LPF/ens192/00:0c:29:92:d4:d0
  Sending on   LPF/ens192/00:0c:29:92:d4:d0
  Listening on LPF/ens160/00:0c:29:92:d4:c6
  Sending on   LPF/ens160/00:0c:29:92:d4:c6
  Sending on   Socket/fallback
  DHCPDISCOVER on ens224 to 255.255.255.255 port 67 interval 3 (xid=0x6d9fb33d)
  DHCPDISCOVER on ens192 to 255.255.255.255 port 67 interval 3 (xid=0xeb8fda26)
  DHCPREQUEST for 192.168.120.4 on ens160 to 255.255.255.255 port 67 
(xid=0x6d39545d)
  DHCPACK of 192.168.120.4 from 192.168.120.254 (xid=0x5d54396d)
  RTNETLINK answers: File exists
  d41d8cd98f00b204e9800998ecf8427e  
/run/systemd/resolved.conf.d/isc-dhcp-v4-ens160.conf
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens160.conf: No such file or 
directory
  5025823d750dda1f3f15e306c4a0afce  
/run/systemd/resolved.conf.d/isc-dhcp-v4-ens160.conf
  md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens160.conf: No such file or 
directory
  bound to 192.168.120.4 -- renewal in 111 seconds.
  root@eoan:~# resolvectl status |grep DNS
  MulticastDNS setting: no
    DNSOverTLS setting: no
    DNSSEC setting: no
  DNSSEC supported: no
    DNSSEC NTA: 10.in-addr.arpa
  MulticastDNS setting: no
    DNSOverTLS setting: no
    DNSSEC setting: no
  DNSSEC supported: no
  MulticastDNS setting: no
    DNSOverTLS setting: no
    DNSSEC setting: no
  DNSSEC supported: no
  MulticastDNS setting: no
    DNSOverTLS setting: no
    DNSSEC setting: no
  DNSSEC supported: no
  ==

  Attached please find the patch for this. The output for md5sum in the
  hook file resolv should separate the stdout and stderr so it won't
  compare the wrong data.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1849658] Re: resolved fallback to TCP fails for truncated UDP replies

2019-11-04 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 243-3ubuntu1

---
systemd (243-3ubuntu1) focal; urgency=medium

  [ Dan Streetman ]
  * Fix resolved fallback to TCP (LP: #1849658)
Author: Dan Streetman
File: 
debian/patches/resolved-set-stream-type-during-DnsStream-creation.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f1ee30b13c9d2d34968b09ce620f3bc24a1a78c7
  * Separate stderr and stdout of /etc/dhcp/dhclient-enter-hooks.d/resolved
(LP: #1849608)
Author: Dan Streetman
File: debian/extra/dhclient-enter-resolved-hook

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fec4d6d026488a1d32ad9dceef18d9ea9c8acbda

  [ Balint Reczey ]
  * Merge to Ubuntu from Debian experimental
  * Refresh patches:
- Dropped changes:
  * udevadm trigger: do not propagate EACCES and ENODEV.
File: 
debian/patches/udevadm-trigger-do-not-propagate-EACCES-and-ENODEV.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=334e3fdc904de05105c78763c88220c1976d1946
  * Pass personality test even when i386 userland runs on amd64 kernel
File: 
debian/patches/debian/UBUNTU-test-Pass-personality-test-even-when-i386-userland-runs-o.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=42e0bfc426f19430f6768ef4922a9531a345765f

systemd (243-3) experimental; urgency=medium

  * Import patches from v243-stable branch (up to ef677436aa)

 -- Balint Reczey   Wed, 30 Oct 2019 15:19:33 +0100

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1849658

Title:
  resolved fallback to TCP fails for truncated UDP replies

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  for DNS UDP replies larger than 512 bytes, fallback to TCP is used.
  For example 'host toomany.ddstreet.org'.

  Due to a bug in resolved in refcounting DNS stream types, the refcount
  underflows for type 0 streams (which resolved uses to talk to upstream
  nameservers), resulting in resolved being unable to fallback to TCP to
  handle truncated UDP replies.

  [test case]

  ubuntu@sf247344-upstream:~$ dig +noanswer +noedns toomany.ddstreet.org
  ;; Truncated, retrying in TCP mode.

  ; <<>> DiG 9.11.3-1ubuntu1.9-Ubuntu <<>> +noanswer +noedns 
toomany.ddstreet.org
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2683
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 40, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;toomany.ddstreet.org.IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Thu Oct 24 11:40:29 UTC 2019
  ;; MSG SIZE  rcvd: 678

  ubuntu@sf247344-upstream:~$ sudo resolvectl flush-caches
  ubuntu@sf247344-upstream:~$ dig +noanswer +noedns toomany.ddstreet.org

  ; <<>> DiG 9.11.3-1ubuntu1.9-Ubuntu <<>> +noanswer +noedns 
toomany.ddstreet.org
  ;; global options: +cmd
  ;; connection timed out; no servers could be reached

  [regression potential]

  very low, as this only properly sets the stream type in the DnsStream
  object; any regression would be a failure to be able to use TCP for
  DNS requests or replies.

  [other info]

  https://github.com/systemd/systemd/pull/13838

  The commit adding stream types is not present in x/b, so this is
  needed only for disco and later.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851225] [NEW] package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-11-04 Thread Kai Nehm
Public bug reported:

During installation of upgrade to version 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.3
ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
Uname: Linux 4.4.0-166-generic i686
.var.log.apt.history.log:
 
ApportVersion: 2.20.1-0ubuntu2.20
Architecture: i386
Date: Mon Nov  4 11:03:07 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-12-05 (2159 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.3 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: Upgraded to xenial on 2019-11-04 (0 days ago)
mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 2019-04-30T12:03:15

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1851225

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.3 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  During installation of upgrade to version 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
  Uname: Linux 4.4.0-166-generic i686
  .var.log.apt.history.log:
   
  ApportVersion: 2.20.1-0ubuntu2.20
  Architecture: i386
  Date: Mon Nov  4 11:03:07 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-12-05 (2159 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.3 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to xenial on 2019-11-04 (0 days ago)
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 2019-04-30T12:03:15

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1851225/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851128] Re: Stylus Use leads to Crash Application in Wayland Sessions

2019-11-04 Thread Axel
Yes, that's exactly what I am doing. There is a work-around.

To have it in Wayland is a matter of comfort since I try to stay on
Wayland. It will be the future, right?

Thanks again.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1851128

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  There is an issue in gtk. In Wayland sessions the use of a stylus
  leads to crash of the application. It is apparently fixed in Gnome
  gtk.

  When asking what should I do I got the answer that I should ask the
  ubuntu gtk maintainers to  backport <
  https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
  , which I do
  here and now.

  Best regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1851128/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851128] Re: Stylus Use leads to Crash Application in Wayland Sessions

2019-11-04 Thread Sebastien Bacher
You will get notified by comments on this ticket when there is an update
available, meanwhile you could perhaps go back to use the default X11
session which shouldn't have the issue?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1851128

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  There is an issue in gtk. In Wayland sessions the use of a stylus
  leads to crash of the application. It is apparently fixed in Gnome
  gtk.

  When asking what should I do I got the answer that I should ask the
  ubuntu gtk maintainers to  backport <
  https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
  , which I do
  here and now.

  Best regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1851128/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851128] Re: Stylus Use leads to Crash Application in Wayland Sessions

2019-11-04 Thread Axel
Thank you very much.

In which time-frame can I expect the fix being on my machine?
And how do I notice, can I check that it is here?

Sorry again for these questions, but I need to learn a lot how this
system works.

Best regards

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1851128

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  There is an issue in gtk. In Wayland sessions the use of a stylus
  leads to crash of the application. It is apparently fixed in Gnome
  gtk.

  When asking what should I do I got the answer that I should ask the
  ubuntu gtk maintainers to  backport <
  https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
  , which I do
  here and now.

  Best regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1851128/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851128] Re: Stylus Use leads to Crash Application in Wayland Sessions

2019-11-04 Thread Sebastien Bacher
Thanks, we will backport it with the next upload, that's not a priority
since wayland is not our default session though

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1851128

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  There is an issue in gtk. In Wayland sessions the use of a stylus
  leads to crash of the application. It is apparently fixed in Gnome
  gtk.

  When asking what should I do I got the answer that I should ask the
  ubuntu gtk maintainers to  backport <
  https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
  , which I do
  here and now.

  Best regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1851128/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1851128] Re: Stylus Use leads to Crash Application in Wayland Sessions

2019-11-04 Thread Axel
I'm using Ubuntu 19.10 Eoan Ermine.

Sorry I did not mention that.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1851128

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  There is an issue in gtk. In Wayland sessions the use of a stylus
  leads to crash of the application. It is apparently fixed in Gnome
  gtk.

  When asking what should I do I got the answer that I should ask the
  ubuntu gtk maintainers to  backport <
  https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
  , which I do
  here and now.

  Best regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1851128/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp