[Touch-packages] [Bug 1816404] Re: on_ac_power fails if the path contains a whitespace

2019-04-20 Thread Simon Quigley
** Changed in: powermgmt-base (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  on_ac_power fails if the path contains a whitespace

Status in powermgmt-base package in Ubuntu:
  Fix Released
Status in powermgmt-base package in Debian:
  New

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 18.04.1 LTS
  Release: 18.04
  Codename: bionic
  powermgmt-base: 1.33

  on_ac_power fails if the path contains a whitespace, solution is
  attached as patch.

  before patch:
  ~# sh -x /usr/bin/on_ac_power; echo $?
  + set -e
  + OFF_LINE_P=no
  + [ -d /sys/class/power_supply/ ]
  + test -d /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery
  + test -r /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + cat /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  cat: '/sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA': No 
such file or directory
  cat: 'Rev:PAACFS00-002-R003-battery/type': No such file or directory
  + type=
  1

  after patch:
  ~# sh -x /usr/bin/on_ac_power; echo $?
  + set -e
  + OFF_LINE_P=no
  + [ -d /sys/class/power_supply/ ]
  + test -d /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery
  + test -r /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + cat /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + type=Battery
  + [ no = yes ]
  + [ -d /proc/acpi/ac_adapter ]
  + [ -r /proc/pmu/info ]
  + [ -r /proc/apm ]
  + exit 255
  255

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1816404/+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 1816361] Re: remote ssh-login impossible with openssh 7.2p2-4ubuntu2.7

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

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

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

Title:
  remote ssh-login impossible with openssh 7.2p2-4ubuntu2.7

Status in openssh package in Ubuntu:
  Expired

Bug description:
  Since upgrading to openssh 7.2p2-4ubuntu2.7 it is impossible to login
  remote. It does not matter what password is set, if you are root or
  not. Login fails in all cases.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ssh (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Feb 18 08:23:20 2019
  InstallationDate: Installed on 2012-12-12 (2258 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssh
  UpgradeStatus: Upgraded to xenial on 2013-02-11 (2197 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1816361/+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 1825695] [NEW] package python-debian 0.1.21+nmu2ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2019-04-20 Thread Nikhil Pagar
Public bug reported:

dont know details

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python-debian 0.1.21+nmu2ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-38.65somerville1-generic 3.13.11.9
Uname: Linux 3.13.0-38-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
Date: Sun Apr 21 09:43:09 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
DuplicateSignature: package:python-debian:0.1.21+nmu2ubuntu2:subprocess new 
pre-removal script returned error exit status 1
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2015-10-29 (1269 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.8
 apt  1.0.1ubuntu2.18
SourcePackage: python-debian
Title: package python-debian 0.1.21+nmu2ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package third-party-packages trusty

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

Title:
  package python-debian 0.1.21+nmu2ubuntu2 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in python-debian package in Ubuntu:
  New

Bug description:
  dont know details

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-debian 0.1.21+nmu2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-38.65somerville1-generic 3.13.11.9
  Uname: Linux 3.13.0-38-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Sun Apr 21 09:43:09 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DuplicateSignature: package:python-debian:0.1.21+nmu2ubuntu2:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-10-29 (1269 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.18
  SourcePackage: python-debian
  Title: package python-debian 0.1.21+nmu2ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1825695/+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 1825695] Re: package python-debian 0.1.21+nmu2ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2019-04-20 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 python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1825695

Title:
  package python-debian 0.1.21+nmu2ubuntu2 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in python-debian package in Ubuntu:
  New

Bug description:
  dont know details

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-debian 0.1.21+nmu2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-38.65somerville1-generic 3.13.11.9
  Uname: Linux 3.13.0-38-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Sun Apr 21 09:43:09 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DuplicateSignature: package:python-debian:0.1.21+nmu2ubuntu2:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-10-29 (1269 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.18
  SourcePackage: python-debian
  Title: package python-debian 0.1.21+nmu2ubuntu2 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1825695/+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 1825626] Re: nvLock: client timed out, taking the lock

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

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

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

Title:
  nvLock: client timed out, taking the lock

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1825626/+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 1825626] Re: nvLock: client timed out, taking the lock

2019-04-20 Thread Alex
I tried older kernel, older nvidia-driver and switching to lightdm.
Nothing helped.

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

Title:
  nvLock: client timed out, taking the lock

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1825626/+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 1825626] Re: nvLock: client timed out, taking the lock

2019-04-20 Thread Alex
I have the exact same error.
Laptop: MSI GL62M 7REX
GPU: Nvidia GeForce 1050 Ti
Started after i upgraded to 19.04

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

Title:
  nvLock: client timed out, taking the lock

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1825626/+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 1778844] Re: nvme multipath does not report path relationships

2019-04-20 Thread Steve Langasek
** Changed in: initramfs-tools (Ubuntu Bionic)
 Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Steve Langasek 
(vorlon)

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  In Progress
Status in initramfs-tools source package in Cosmic:
  In Progress
Status in initramfs-tools source package in Disco:
  Fix Released

Bug description:
  [Impact]
  initramfs created with MODULES=dep or kdump initrd won't boot a system with 
root filesystem on a multipath nvme.

  [Test case]
  Systems with nvme multipath were able to boot with the created initramfs. 
Also tested on systems with non-multipath nvme, and non nvme systems.

  [Regression potential]
  A system could fail to boot because the generated initramfs was broken. The 
code should just add modules, which is safer than removing modules or doing any 
other changes. In any case, it was tested to boot on multipath nvme, non 
multipath nvme and non nvme systems.


  -

  
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [ 

[Touch-packages] [Bug 1816404] Re: on_ac_power fails if the path contains a whitespace

2019-04-20 Thread Bug Watch Updater
** Changed in: powermgmt-base (Debian)
   Status: Unknown => New

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

Title:
  on_ac_power fails if the path contains a whitespace

Status in powermgmt-base package in Ubuntu:
  Confirmed
Status in powermgmt-base package in Debian:
  New

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 18.04.1 LTS
  Release: 18.04
  Codename: bionic
  powermgmt-base: 1.33

  on_ac_power fails if the path contains a whitespace, solution is
  attached as patch.

  before patch:
  ~# sh -x /usr/bin/on_ac_power; echo $?
  + set -e
  + OFF_LINE_P=no
  + [ -d /sys/class/power_supply/ ]
  + test -d /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery
  + test -r /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + cat /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  cat: '/sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA': No 
such file or directory
  cat: 'Rev:PAACFS00-002-R003-battery/type': No such file or directory
  + type=
  1

  after patch:
  ~# sh -x /usr/bin/on_ac_power; echo $?
  + set -e
  + OFF_LINE_P=no
  + [ -d /sys/class/power_supply/ ]
  + test -d /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery
  + test -r /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + cat /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + type=Battery
  + [ no = yes ]
  + [ -d /proc/acpi/ac_adapter ]
  + [ -r /proc/pmu/info ]
  + [ -r /proc/apm ]
  + exit 255
  255

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1816404/+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 1825679] [NEW] Delay/freeze/cpu spike when using the function/media/brightness keys in Xorg

2019-04-20 Thread Kolmar Kafran
Public bug reported:

There is a long time bug when the user press any function key or media
key om Gnome, the CPU spikes to 100%, the system freezes for some
seconds and then the key is pressed. This is particularly true when
change the screen brightness. This only happens in Xorg, Wayland is not
affected.

On Brazilian keyboard a workaround is to edit the file
`/usr/share/X11/xkb/symbols/br` and comment the line `modifier_map Mod3
{ Scroll_Lock };`

This has been affecting multiple users and has been discussed on

https://www.reddit.com/r/gnome/comments/84453o/delayfreezecpu_spike_when_using_the_functionmedia/

https://askubuntu.com/questions/1025302/media-keys-delayed-and-cause-a
-cpu-spike-to-100-on-ubuntu-17-10-with-gnome

https://askubuntu.com/questions/906723/fn-media-keys-slow-delayed-on-
ubuntu-gnome-17-04?noredirect=1=1

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Delay/freeze/cpu spike when using the function/media/brightness keys
  in Xorg

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  There is a long time bug when the user press any function key or media
  key om Gnome, the CPU spikes to 100%, the system freezes for some
  seconds and then the key is pressed. This is particularly true when
  change the screen brightness. This only happens in Xorg, Wayland is
  not affected.

  On Brazilian keyboard a workaround is to edit the file
  `/usr/share/X11/xkb/symbols/br` and comment the line `modifier_map
  Mod3 { Scroll_Lock };`

  This has been affecting multiple users and has been discussed on

  
https://www.reddit.com/r/gnome/comments/84453o/delayfreezecpu_spike_when_using_the_functionmedia/

  https://askubuntu.com/questions/1025302/media-keys-delayed-and-cause-a
  -cpu-spike-to-100-on-ubuntu-17-10-with-gnome

  https://askubuntu.com/questions/906723/fn-media-keys-slow-delayed-on-
  ubuntu-gnome-17-04?noredirect=1=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1825679/+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 1825678] [NEW] Intel wifi fails to resume after suspend

2019-04-20 Thread Syfer Polski
Public bug reported:

Yesterday my WiFi card(Intel Wireless 3165) didn't show up on resuming
the laptop from a suspend state. I rebooted a few times and found that
the situation hadn't changed. Rebooting and choosing older kernels
didn't help. I ran lspci and discovered my WiFi card was missing in the
output. I shut down the laptop assuming my WiFi card suffered a hardware
failure. In the evening, after starting up from a full shutdown, the
WiFi card worked again.

Today, the situation happened again, but I approached the debugging more
methodically. I looked at nmcli and found it still saw my wifi card but
found it unavailable. lspci could still see the Wifi card in the last
position. I analyzed dmesg output and discovered an iwlwifi crash(the
relevant part of dmesg is provided in wifi_dmesg.txt attachment).

Then, I rebooted the laptop. This didn't fix the issue and from a quick
look at lspci, the wifi card was missing again. So I repeated the
procedure that worked the previous day - full shutdown, wait 10 seconds,
then start up. This restored my WiFi card to a working state and allowed
me to file this bug report.

I will be happy to provide any further information that could read to
fixing this issue.

Additional information:

1. lsb_release -rd
Description:Peppermint 8 Eight
Release:8
Yes, that's technically not Ubuntu. However, Peppermint does not modify 
Ubuntu's kernel, and Peppermint 8 is based on Ubuntu 16.04 Xenial Xerus.

2. apt-cache policy linux-firmware
linux-firmware:
  Installed: 1.157.21
  Candidate: 1.157.21
  Version table:
 *** 1.157.21 500
500 http://pl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://pl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages
100 /var/lib/dpkg/status
 1.157 500
500 http://pl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://pl.archive.ubuntu.com/ubuntu xenial/main i386 Packages

3. I expected suspend and resume to work like they did for the last two
years

4. iwlwifi crashed and dumped its registers.

5. Inxi, in case it's useful(many other bug reporting websites ask for it):
inxi -Fz
System:Host: PiDell Kernel: 4.15.0-47-generic x86_64 (64 bit) Desktop: N/A
   Distro: Peppermint Eight
Machine:   System: Dell (portable) product: Inspiron 15 7000 Gaming
   Mobo: Dell model: 065C71 v: A00 Bios: Dell v: 1.7.0 date: 05/08/2018
CPU:   Quad core Intel Core i7-7700HQ (-HT-MCP-) cache: 6144 KB 
   clock speeds: max: 3800 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz
   4: 800 MHz 5: 800 MHz 6: 800 MHz 7: 800 MHz 8: 800 MHz
Graphics:  Card-1: Intel Device 591b
   Card-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile]
   Display Server: X.Org 1.19.6 driver: nvidia
   Resolution: 1920x1080@60.00hz
   GLX Renderer: GeForce GTX 1050 Ti/PCIe/SSE2
   GLX Version: 4.6.0 NVIDIA 396.54
Audio: Card Intel CM238 HD Audio Controller driver: snd_hda_intel
   Sound: Advanced Linux Sound Architecture v: k4.15.0-47-generic
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
   driver: r8169
   IF: enp2s0 state: down mac: 
   Card-2: Intel Wireless 3165 driver: iwlwifi
   IF: wlp3s0 state: up mac: 
Drives:HDD Total Size: 1256.3GB (27.6% used)
   ID-1: /dev/sda model: Micron_1100_SATA size: 256.1GB
   ID-2: /dev/sdb model: TOSHIBA_MQ01ABD1 size: 1000.2GB
Partition: ID-1: / size: 46G used: 38G (87%) fs: ext4 dev: /dev/sdb3
RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 51.0C mobo: N/A gpu: 48C
   Fan Speeds (in rpm): cpu: N/A
Info:  Processes: 258 Uptime: 51 min Memory: 2152.2/15906.5MB
   Client: Shell (bash) inxi: 2.2.35

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: iwlwifi xenial

** Attachment added: "dmesg log"
   
https://bugs.launchpad.net/bugs/1825678/+attachment/5257399/+files/wifi_dmesg.txt

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

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

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

Title:
  Intel wifi fails to resume after suspend

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Yesterday my WiFi card(Intel Wireless 3165) didn't show up on resuming
  the laptop from a suspend state. I rebooted a few times and found that
  the situation hadn't changed. Rebooting and choosing older kernels
  didn't help. I ran lspci and discovered my WiFi card was missing in
  the output. I 

[Touch-packages] [Bug 1825331] Re: apparmor chromium profile blocks yubikeys

2019-04-20 Thread Christian Boltz
KernLog.txt contains several ALLOWED lines for chromium, and also DENIED
lines for firefox (unrelated to this bugreport, but nevertheless we
should probably check them.

You mentioned that you got some EPERM in strace - can you please tell us
which files were affeted?

Wild guess: maybe those files were covered by "deny" rules in the
firefox profile or an abstraction. (deny rules get enforced even in
complain mode, and silence the logging.)

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

Title:
  apparmor chromium profile blocks yubikeys

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,

  some months ago (can't give a precise date) I could use all my pure
  u2f tokens, as well as Yubikey tokens with mixed apps (yubikey 4,
  yubikey neo) pretty well with chromium browser as u2f tokens.

  For some months now and since an update of the chromium-browser in
  18.04, it was working with pure u2f tokens (e.g. the blue yubikeys,
  FIDO u2f token,...), but not with regular yubikeys anymore, although
  command line tools like u2f-host worked pretty well.

  I checked the kernel messages and did not find any apparmor deny
  message or other reasons. Furthermore, the apparmor profile for
  usr.bin.chromium-browser was in complain mode only.

  Now I did again some debugging and found that the problem is gone
  after

  
  aa-disable usr.bin.chromium-browser

  
  Although the profile was in complain mode and dmesg did not show any 
forbidden actions, the strace showed some EPERM (Operation not permitted) 
errors, that's why I tried to disable aa. 

  Interestingly, this problem does not affect regular u2f tokens, just
  the yubikeys with additional functions.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apparmor-profiles 2.12-4ubuntu5.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Apr 18 11:14:22 2019
  InstallationDate: Installed on 2018-04-30 (352 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=UUID=5dca854b-2558-44a1-918d-c8380934754d ro nosplash
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1825331/+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 1825194] Re: resolvconf is racy, which leads to broken resolv.conf in parallel calls

2019-04-20 Thread Simon Quigley
Unsubscribing the Sponsors Team because there is no SRU bug template
yet.

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

Title:
  resolvconf is racy, which leads to broken resolv.conf in parallel
  calls

Status in resolvconf package in Ubuntu:
  Fix Released
Status in resolvconf source package in Xenial:
  New

Bug description:
  It has been found that simultaneous calls to resolvconf can lead to
  inconsistent content in resolv.conf. For instance, no nameservers
  while NetworkManager has one in its record (see LP: #1824395):

  $ cat /run/resolvconf/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

  $ cat /run/resolvconf/interface/NetworkManager
  nameserver 192.168.1.6
  nameserver 192.168.1.2

  This can happen easily when calling "netplan apply", which can re-
  start both networkd and NM. resolvconf is called at that point by the
  "systemd-networkd-resolvconf-update.service" service, and also
  directly by NetworkManager, which leads to the situation described
  above. This is not surprising as there is nothing preventing different
  instances of resolvconf to access the same files. This sort of
  situation can be reproduced by running in a loop commands like:

  $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo 
resolvconf -a networkd
  $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & 
printf "\n" | sudo resolvconf -a networkd

  Eventually, this leads to a resolv.conf that is not consistent with
  the last run command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

2019-04-20 Thread Norbert
Confirmed during upgrade of clean fully-updated Ubuntu MATE 18.10 to
Ubuntu MATE 19.04, so I have marked Ubuntu MATE as affected by this bug.

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

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in Ubuntu MATE:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  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.family: Virtual Machine
  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-mate/+bug/1825420/+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 1795629] Re: Intel wireless 3165 does not connect after wakeup

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

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

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

Title:
  Intel wireless 3165 does not connect after wakeup

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Suggested to report by ubuntu IRC support network as new bug.

  Wifi does not automatically reconnect when resuming from
  sleep/hibernation. Connection fails with network manager unable to
  connect three times before stopping. I am able to connect to my wifi
  network when I manually select it as a question.

  Pastebin logs running tail before sleep, then resuming:
  https://pastebin.com/21TqANaE

  Running ubuntu 18.04.01 LTS network manager 1.10.6-2ubun
  Kernel is 4.15.0-34-generic 37-Ubuntu
  linux-firmware = 1.173.1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  2 12:34:20 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-16 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH   
CONNECTION  CON-UUID  CON-PATH  
   
   wlp1s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3   
NOWTV0584A  636b6237-7bf6-4101-91a6-5c4198eb5949  
/org/freedesktop/NetworkManager/ActiveConnection/214 
   tun0tun   connected  /org/freedesktop/NetworkManager/Devices/24  
tun0ae8c1f9f-5715-45b3-9b10-511c547252c9  
/org/freedesktop/NetworkManager/ActiveConnection/216 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1   --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1795629/+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 1816404] Re: on_ac_power fails if the path contains a whitespace

2019-04-20 Thread Simon Quigley
Forwarded to Debian, to get their opinion on this.

Unsubscribing the Ubuntu Sponsors Team.

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

** Also affects: powermgmt-base (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927668
   Importance: Unknown
   Status: Unknown

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

Title:
  on_ac_power fails if the path contains a whitespace

Status in powermgmt-base package in Ubuntu:
  Confirmed
Status in powermgmt-base package in Debian:
  Unknown

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 18.04.1 LTS
  Release: 18.04
  Codename: bionic
  powermgmt-base: 1.33

  on_ac_power fails if the path contains a whitespace, solution is
  attached as patch.

  before patch:
  ~# sh -x /usr/bin/on_ac_power; echo $?
  + set -e
  + OFF_LINE_P=no
  + [ -d /sys/class/power_supply/ ]
  + test -d /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery
  + test -r /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + cat /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  cat: '/sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA': No 
such file or directory
  cat: 'Rev:PAACFS00-002-R003-battery/type': No such file or directory
  + type=
  1

  after patch:
  ~# sh -x /usr/bin/on_ac_power; echo $?
  + set -e
  + OFF_LINE_P=no
  + [ -d /sys/class/power_supply/ ]
  + test -d /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery
  + test -r /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + cat /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + type=Battery
  + [ no = yes ]
  + [ -d /proc/acpi/ac_adapter ]
  + [ -r /proc/pmu/info ]
  + [ -r /proc/apm ]
  + exit 255
  255

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1816404/+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 1825673] Re: Xorg freeze

2019-04-20 Thread Balaji Duraisamy
when will this problem fixed?

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  when ubuntu froze,keyboard,mouse key and monter all are not working

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 00:32:09 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Today
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2213]
  InstallationDate: Installed on 2019-04-01 (19 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2213
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/19/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096C11405F00050660180:rvnHewlett-Packard:rn2213:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 096C11405F00050660180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1825673/+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 1825673] [NEW] Xorg freeze

2019-04-20 Thread Balaji Duraisamy
Public bug reported:

when ubuntu froze,keyboard,mouse key and monter all are not working

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 21 00:32:09 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Today
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2213]
InstallationDate: Installed on 2019-04-01 (19 days ago)
InstallationMedia:
 
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
 Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP 15 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.23
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2213
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.35
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd09/19/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096C11405F00050660180:rvnHewlett-Packard:rn2213:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP 15 Notebook PC
dmi.product.version: 096C11405F00050660180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze 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/1825673

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  when ubuntu froze,keyboard,mouse key and monter all are not working

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 00:32:09 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Today
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2213]
  InstallationDate: Installed on 2019-04-01 (19 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade 

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

2019-04-20 Thread Simon Quigley
Uploaded to Xenial.

For future reference, the patches directory goes inside debian/

Thanks!

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

Title:
  pam_tty_audit failed in pam_open_session

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Xenial:
  In Progress
Status in pam source package in Bionic:
  Fix Released
Status in pam source package in Cosmic:
  Fix Released
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Kernel keystroke auditing via pam_tty_audit.so not working

   * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it 
failed in pam_open_session.
     It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  [Test Case]

  1) Open a shell & escalate to root
  2) Update /etc/pam.d/common-session & 
/etc/pam.d/common-session-noninteractive and add the following line directly 
after the line: "session required pam_unix.so":
  "session required pam_tty_audit.so enable=*"

  3) Start a second new shell session on the box and type a variety of commands
  4) Exit the second shell session to flush the buffer?
  5) In the root shell run "aureport -tty -i". The output should show the 
commands run in the other shell.

  [Regression Potential]

   * Low, we are simply including the missing header file and copy the
  old status as initialization of new. The fix is already found/part of
  Debian and Disco.

  [Pending SRU]

  All regressions found in Bionic and Cosmic looks like long standing
  ADT failure. Nothing has been introduce by this particular SRU.

  [Other Info]

  # Upstream fix:
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  # git describe --contains c5f829931a22c65feffee16570efdae036524bee
  Linux-PAM-1_2_0~75

  # rmadision pam
  =>  pam | 1.1.8-1ubuntu2.2   | trusty-updates   | source
  =>  pam | 1.1.8-3.2ubuntu2   | xenial   | source
  =>  pam | 1.1.8-3.2ubuntu2.1 | xenial-updates   | source
  =>  pam | 1.1.8-3.6ubuntu2   | bionic   | source
  =>  pam | 1.1.8-3.6ubuntu2   | cosmic   | source
  pam | 1.3.1-5ubuntu1 | disco| source

  [Original Description]

  Dear Maintainer.

  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2

  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2

  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting 
current audit status: Invalid argument
  May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot 
make/remove an entry for the specified session
  May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: 
disconnected by user

  -- syslog --
  May 18 14:47:03 vm audispd: node=vm type=USER_ACCT 
msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): 
pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1
  May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE 
msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set 
old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0
  May 18 14:47:03 vm audispd: node=vm type=USER_START 
msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:session_open acct="test" 

[Touch-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP laptops]

2019-04-20 Thread Bug Watch Updater
** Changed in: systemd
   Status: Unknown => 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/1726160

Title:
  On login, display rotates to wrong orientation [HP laptops]

Status in IIO Sensor Proxy:
  Fix Released
Status in systemd:
  Fix Released
Status in iio-sensor-proxy package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in iio-sensor-proxy source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Triaged
Status in iio-sensor-proxy source package in Cosmic:
  Confirmed
Status in systemd source package in Cosmic:
  Triaged
Status in iio-sensor-proxy source package in Disco:
  Invalid
Status in systemd source package in Disco:
  Fix Released

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/iio-sensor-proxy/+bug/1726160/+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 1781746] Re: [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap

2019-04-20 Thread Simon Quigley
Unsubscribing the sponsors team after Brian's comment.

** Tags removed: rls-dd-incoming
** Tags added: rls-ee-incoming

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

Title:
  [SRU] Slow startup with zram-config installed (/dev/zram0) or
  encrypted swap

Status in Default settings and artwork for Baltix OS:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 18.04 startup slowdowns for 30-120 seconds when zram swap is enabled 
(for example zram-config installed) or swap is encrypted.
  Today lots of users have SSD instead of HDD disk drives and use zram swap 
instead of swap partition or swap file, but if initrd is generated when zram 
swap is enabled then system can become "unbootable" from the user's perspective 
(Users with SSD storage doesn't wait 2 or more minutes...)

  This bug is already fixed in Debian initramfs-tools ver 0.132, please accept 
this simple 3 lines patch from Debian into Ubuntu 18.04 LTS
  
https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d

  [Test Case]
  Install zram-config package and regenerate and initrd, for example with 
  sudo update-initramfs -u

  When generating initrd I get this message in terminal:

  I: The initramfs will attempt to resume from /dev/zram0
  I: (UUID=e380356c-767e-4265-98da-8be62ad28569)
  I: Set the RESUME variable to override 
this.###.]

  So the local-premount script in initramfs was waiting for a swap
  device that was not available, until it timed out. The relevant
  message was gave up waiting for suspend/resume device.

  [Regression Potential]

  None, patch simply adds case for /dev/zram*:

  60case "$resume_auto" in
  61/dev/zram*)
  62ephemeral=true
  63;;
  64esac

  
  [Other Info]
  Manual method to disable this (as resuming from swap is not possible with an 
encrypted or zram swap): modify file /etc/initramfs-tools/conf.d/resume - add 
(or change) line
  RESUME=none
  (instead of the UUID that was here) will disable waiting for a resume device.
  and run sudo update-initramfs -u to apply the changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1781746/+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 1825668] [NEW] package initramfs-tools 0.122ubuntu8.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-04-20 Thread christian aubert
Public bug reported:

Upgrading Ubunutu 16 to 18 on Orbbec Persee.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.122ubuntu8.14
Uname: Linux 3.10.0 armv7l
NonfreeKernelModules: mali_kbase
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: armhf
Date: Sun Apr 21 00:23:51 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8.14 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2019-04-20 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package armhf third-party-packages xenial

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

Title:
  package initramfs-tools 0.122ubuntu8.14 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading Ubunutu 16 to 18 on Orbbec Persee.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.122ubuntu8.14
  Uname: Linux 3.10.0 armv7l
  NonfreeKernelModules: mali_kbase
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: armhf
  Date: Sun Apr 21 00:23:51 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.14 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2019-04-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1825668/+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 1825668] Re: package initramfs-tools 0.122ubuntu8.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-04-20 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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1825668

Title:
  package initramfs-tools 0.122ubuntu8.14 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading Ubunutu 16 to 18 on Orbbec Persee.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.122ubuntu8.14
  Uname: Linux 3.10.0 armv7l
  NonfreeKernelModules: mali_kbase
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: armhf
  Date: Sun Apr 21 00:23:51 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.14 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2019-04-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1825668/+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 1799647] Re: Patch: Add configuration for german provider winSIM

2019-04-20 Thread Simon Quigley
Unsubscribing sponsors, please submit this upstream first.

Thanks!

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

Title:
  Patch: Add configuration for german provider winSIM

Status in mobile-broadband-provider-info package in Ubuntu:
  New

Bug description:
  I was unable to contribute a patch to the upstream gnome package:
  
https://wiki.gnome.org/Projects/NetworkManager/MobileBroadband/ServiceProviders
  (They seem to have migrated their git servers away)

  I still think this little config change adds value to Ubuntu users, hence I 
am opening this issue.
  Find the patchfile attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mobile-broadband-provider-info/+bug/1799647/+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 1799364] Re: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers

2019-04-20 Thread Simon Quigley
Unsubscribing sponsors, as there seems to be disagreement with respect
to the patch's relevance.

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

Title:
  The wlan/bt hotkey doesn't work for all Dell Latitude and Precision
  computers

Status in OEM Priority Project:
  New
Status in OEM Priority Project bionic series:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * All Dell Latitude and Precision computer users can not use the
  wlan/bt hotkey.

  [Test Case]

   * Use any Dell Latitude and Precision computer to check the wlan/bt
  hotkey.

   * If you don't have the computer above, you can use the following
  command to check, and the expected output is "KEYBOARD_KEY_88=!wlan"
  instead of "KEYBOARD_KEY_88=!".

   `systemd-hwdb query
  
evdev:atkbd:dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  | grep KEYBOARD_KEY_88`

  [Regression Potential]

   * No regression

  [Other Info]

   * None

  Just install the official Ubuntu 18.10 on any Dell Latitude or
  Precision computer and press wlan/bt hotkey on the keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: systemd 239-7ubuntu10
  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: Tue Oct 23 15:37:41 2018
  InstallationDate: Installed on 2018-10-23 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 0bda:5520 Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=be88d6f2-7d21-4a3c-b384-0c5356fb9220 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.0.24
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1799364/+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 1769132] Re: ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font

2019-04-20 Thread Simon Quigley
Unsubscribing the Ubuntu Sponsors Team as there is nothing to sponsor.

Additionally, if you would like this to be in a stable release, the bug
description must follow the template, which can be found here:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

As Sebastien notes though, as this is fairly low-priority, it will
likely be included with other fixes.

Thanks!

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

Title:
  ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font

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

Bug description:
  ubuntu18.04's libfreetype6 version 2.8.1 has a bug of rendering bitmap font 
like ZFull gb, should be upgrade to version 2.9.
  I checked libfreetype 2.9 fix this bug. I post this bug in:

  https://savannah.nongnu.org/bugs/?53798

  there are some picture I grab for this bug:

  http://forum.ubuntu.org.cn/viewtopic.php?f=186=487304

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1769132/+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 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

2019-04-20 Thread John W Maynard
Can confirm this is still and issue in 19.04.

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+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 1781597] Re: [SRU] WoWLAN settings are not supported

2019-04-20 Thread Simon Quigley
Unsubscribing the Ubuntu Sponsors Team, there is nothing to sponsor.

Bump on the Bionic SRU, is that still going to happen?

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

Title:
  [SRU] WoWLAN settings are not supported

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Triaged
Status in network-manager source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  WoWLAN lets us wake up the system by sending wake packets over the
  wifi connection. This is something requested by some OEM projects, for
  bionic server images.

  NM 1.12 supports configuring this feature, so this can be achieved by
  backporting that support to 1.10 (bionic version). These are the MPs
  for cosmic and bionic:

  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468
  
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465

  [Test Case]

  First, the wifi card must support WoWLAN. This can be checked by
  running

  $ iw phy

  and searching for "WoWLAN support:" in the output. If it is supported,
  with the patch applied a connection configured with wowlan can be
  created with:

  $ sudo nmcli d wifi connect  password 
  $ sudo nmcli c modify  802-11-wireless.wake-on-wlan 8
  $ sudo nmcli c down 
  $ sudo nmcli c up 

  We can check with 'iw' that WoWLAN is active for the connection:

  $ iw phy phy0 wowlan show
  WoWLAN is enabled:
   * wake up on magic packet

  In this case we have configured the connection to wake up the system
  when a 'magic' packet is received. We can then suspend the system with

  $ sudo systemctl suspend

  And we should be able to wake the system from another device with the
  command

  $ sudo etherwake -i  

  [Regression Potential]

  Although the patch is not especially small, it is a backport of
  changes that have been merged upstream, with very little modifications
  to make it compile in 1.10. It is also a rather isolated feature that
  should not conflict with existing ones. The feature will be activated
  only if configured from the command line, so the risk of regressions
  should be small. Note also that the patch will be removed as soon as
  Ubuntu moves to NM 1.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+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 1771764] Re: Add encapsulation support to ip route

2019-04-20 Thread Simon Quigley
Please see my comment on bug 1771783 -- unsubscribing the Ubuntu
Sponsors Team.

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

Title:
  Add encapsulation support to ip route

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

Bug description:
  The following command does not work:

  $ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
  Error: "nexthop" or end of line is expected instead of "encap"

  In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
  $ ip -V
  ip utility, iproute2-ss151103

  =>
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4

  With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
  $ modprobe mpls_iptunnel
  $ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev 
ntfp2
  $ ./ip/ip r
  [snip]
  10.201.0.0/24  encap mpls  300 via 10.200.0.1 dev ntfp2

  At least, this patch is missing:
  1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+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 1771783] Re: Add support for custom protocols from rt_protos.d

2019-04-20 Thread Simon Quigley
Hello! Thank you for your contribution to Ubuntu.

If you would like this to be sponsored to Xenial, please edit the bug
description to follow the SRU bug template. More information can be
found here:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

Additionally, I see in your debdiff there are multiple areas which still need 
to be filled in, or removed. Such lines include:
+## Description: add some description
+## Origin/Author: add some origin or author
+## Bug: bug URL

I recommend you read the DEP-3 standard, which provides a standard way
to fill out such a description: https://dep-
team.pages.debian.net/deps/dep3/

I am unsubscribing the Ubuntu Sponsors Team for now, please resubscribe
us when the changes have been made.

Thank you!

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

Title:
  Add support for custom protocols from rt_protos.d

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

Bug description:
  FRR puts its own proto numbers when inserting a route, example:
  $ ip route
  [snip]
  2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

  iproute2 defines some protocols, but not all:
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

  A patch has been pushed upstream so that external applications can define 
their protocols numbers:
  719e331ff619 ("Add support for rt_protos.d")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+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 1726124] Re: DNS domain search paths not updated when VPN started

2019-04-20 Thread Mark Duncan
What does that rls-bb-notfixing tag mean?  This is just a bug that won't
be fixed?  Split tunnel DNS with openconnect is still completely broken
in 19.04 and it would be very nice to have this working.  The last
couple years of Ubuntu releases have required me to ditch systemd-
resolved in order to access my company's internal services while remote.

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Touch-packages] [Bug 1739889] Re: Compiler warning about possiable overflow in devname.c

2019-04-20 Thread Simon Quigley
Hello Michael, thank you for your contribution to Ubuntu!

A bug report in Ubuntu is not exactly the correct way to report this,
could you please try to submit it upstream?

The Ubuntu Sponsors team also only sponsors debdiffs, which has
packaging changes as well as the patch. I am unsubscribing that team for
now; please resubscribe them if this was incorrect.

Thanks again, and apologies for the delay in responding to this bug
report.

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

Title:
  Compiler warning about possiable overflow in devname.c

Status in util-linux package in Ubuntu:
  New

Bug description:
  I just compiled mount and got the following warning:

  libblkid/src/devname.c:166:29: warning: ‘%s’ directive writing up to 255 
bytes into a region of size 245 [-Wformat-overflow=]
 sprintf(path, "/sys/block/%s/slaves", de->d_name);
   ^~
  In file included from /usr/include/stdio.h:862:0,
   from libblkid/src/devname.c:16:
  /usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note: 
‘__builtin___sprintf_chk’ output between 19 and 274 bytes into a destination of 
size 256
 return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
^~
 __bos (__s), __fmt, __va_arg_pack ());
 ~ 

  Code preceding this does a length check to prevent overflow. However,
  the warning was still alarming. The attached patch switches sprintf to
  snprintf and ups the buffer size to 300. This will silence the
  compiler and support longer device names. There didn't appear to be
  any technical reason for the 256 byte limit. If there is we just get a
  different less alarming truncation warning. This also means we don't
  need the hard coded length check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1739889/+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 1691214] Re: Consider enabling --color by default

2019-04-20 Thread Simon Quigley
Bump; was this patch sent upstream? What is the status of it at the
moment?

The attached patch can't be uploaded as-is to any currently-supported
release, unsubscribing sponsors (please resubscribe when more details
are given).

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

Title:
  Consider enabling --color by default

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  The output of

  ip --color a

  looks a lot nicer to me than

  ip a

  
  If you look in /etc/skel/.bashrc you can see that we already enable color for 
other commands:
   alias ls='ls --color=auto'
   alias grep='grep --color=auto'
   alias fgrep='fgrep --color=auto'
   alias egrep='egrep --color=auto'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1691214/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-04-20 Thread Tony den Haan
It's back! Me too on Ubuntu 18.04.2 LTS.
Maybe it was package keyboard-configuration_1.178ubuntu2.8_all.deb?

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in console-setup source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in console-setup source package in Cosmic:
  New
Status in linux source package in Cosmic:
  New
Status in xorg-server source package in Cosmic:
  New
Status in console-setup source package in Disco:
  In Progress
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Confirmed
Status in console-setup source package in Eoan:
  New
Status in linux source package in Eoan:
  New
Status in xorg-server source package in Eoan:
  New

Bug description:
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1825649] [NEW] ISC DHCP client/Ubuntu fails to connect to commercial routers and code fix suggestion

2019-04-20 Thread Glen Wetzel
Public bug reported:

Linux systems (Ubuntu 16.04) fail to connect to various hotels with wifi
as a result of the DHCPDiscover message being sent by dhclient.  The
same laptop using MSWindows connects with the hotels without a problem.
This has been observed at multiple locations.

The problem was isolated by making the DHCPDiscover packet sent by
dhclient match the DHCPDiscover packet sent by MSWindows. It was found
that affecting difference was that dhclient generated a non-zero value
for the TOS UDP field.  Commenting out the setting of ip.ip_tos in
packet.c so that the field remained zero fixed the problem:

dhcp-4.4.1/common:

$ diff packet.c packet.c.orig
150c150
< //ip.ip_tos = IPTOS_LOWDELAY;
---
>   ip.ip_tos = IPTOS_LOWDELAY;

The hotel's router may have been misconfigured to interpret the TOS
field.  However, the hotel connects to MSWindows/Apple devices.  As a
result, open source systems such as Ubuntu (Linux) gain a reputation of
being unreliable.  (My wife wants/needs to use MS/Apple systems as
result)

I would like to suggest that if the default DHCP message content
generated by MSWindows/Apple adheres to standards, then the default DHCP
message content from open source systems (linux) match bit for bit.
Sniff packets and compare to verify.  Such practice would assure that
open source connectivity (linux) is no less reliable than commercial
device connectivity.

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  ISC DHCP client/Ubuntu fails to connect to commercial routers and code
  fix suggestion

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Linux systems (Ubuntu 16.04) fail to connect to various hotels with
  wifi as a result of the DHCPDiscover message being sent by dhclient.
  The same laptop using MSWindows connects with the hotels without a
  problem.  This has been observed at multiple locations.

  The problem was isolated by making the DHCPDiscover packet sent by
  dhclient match the DHCPDiscover packet sent by MSWindows. It was found
  that affecting difference was that dhclient generated a non-zero value
  for the TOS UDP field.  Commenting out the setting of ip.ip_tos in
  packet.c so that the field remained zero fixed the problem:

  dhcp-4.4.1/common:

  $ diff packet.c packet.c.orig
  150c150
  < //ip.ip_tos = IPTOS_LOWDELAY;
  ---
  >   ip.ip_tos = IPTOS_LOWDELAY;

  The hotel's router may have been misconfigured to interpret the TOS
  field.  However, the hotel connects to MSWindows/Apple devices.  As a
  result, open source systems such as Ubuntu (Linux) gain a reputation
  of being unreliable.  (My wife wants/needs to use MS/Apple systems as
  result)

  I would like to suggest that if the default DHCP message content
  generated by MSWindows/Apple adheres to standards, then the default
  DHCP message content from open source systems (linux) match bit for
  bit.  Sniff packets and compare to verify.  Such practice would assure
  that open source connectivity (linux) is no less reliable than
  commercial device connectivity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1825649/+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 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt

2019-04-20 Thread AsciiWolf
I didn't have time to look into the source code, but the problem is that
instead of having something like "Cdrom with %s", there is a new
translatable string with hardcoded version added every time a python-apt
is released for a new Ubuntu version. You could probably make the
"Ubuntu xx.yy 'Code Name'" string not translatable (I don't think anyone
actually translates this) and use it as a part of the "Cdrom with ..."
string.

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

Title:
  [RFE] Automatically update the Ubuntu version strings in python-apt

Status in Ubuntu Translations:
  New
Status in python-apt package in Ubuntu:
  New

Bug description:
  Every time there is a new Ubuntu release, some strings need to be
  manually translated although the only thing that is changing is the
  Ubuntu version and code name. Please, consider updating these strings
  automatically based on a translated template. It would help many
  translators.

  These strings are:
  Ubuntu xx.yy 'Code Name'
  Cdrom with Ubuntu xx.yy 'Code Name'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+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 1824806] Re: Network stops working after systemd update

2019-04-20 Thread Dan Streetman
> after running `systemctl stop systemd-networkd` the systemd-networkd process 
> disappears
> from my process list, but the network does not get brought down. I don't know 
> if that
> is intended behavior, but in either case it is not directly related to this 
> report.

that is systemd-networkd intended behavior.


** Changed in: systemd (Ubuntu)
   Status: Confirmed => 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/1824806

Title:
  Network stops working after systemd update

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I have four 18.04 servers that are regularly updated and have a
  bond/bridge configured via netplan. Every so often the interfaces
  themselves will have "speed changed to 0" and the server will be
  unresponsive over network. The servers are still usable via the
  console, though. I think I can confidently associate it with systemd
  updates. If I'm manually updating the servers, e.g., `apt dist-
  upgrade`, and there's a system update... the ssh session becomes
  unresponsive when updating systemd, timing of automatic security
  updates seems to coincide with it happening as well. Rebooting fixes
  the issue until the next systemd update. I've included some log
  excerpts and one of my netplan configs below. Thanks!

  syslog:
  `Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f3: Lost carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f3: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.661292] igb :04:00.3 
enp4s0f3: speed changed to 0 for port enp4s0f3
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f2: Lost carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f2: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host systemd[1]: Started Network Time Synchronization.
  Apr 9 06:39:01 stn-vm-host systemd[1]: Stopped Flush Journal to Persistent 
Storage.
  Apr 9 06:39:01 stn-vm-host systemd[1]: Stopping Flush Journal to Persistent 
Storage...
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.732487] systemd[1]: Stopping 
Journal Service...
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.732903] systemd-journald[672]: 
Received SIGTERM from PID 1 (systemd).
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.823634] igb :04:00.2 
enp4s0f2: speed changed to 0 for port enp4s0f2
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.833718] systemd[1]: Stopped 
Journal Service.
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.837652] systemd[1]: Starting 
Journal Service...
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f1: Lost carrier
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f1: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host systemd[1]: Starting Flush Journal to Persistent 
Storage...
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.912976] systemd[1]: Started 
Journal Service.
  Apr 9 06:39:01 stn-vm-host systemd[1]: Started Flush Journal to Persistent 
Storage.
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.971223] igb :04:00.1 
enp4s0f1: speed changed to 0 for port enp4s0f1
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f0: Lost carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f0: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host kernel: [1058498.109063] igb :04:00.0 
enp4s0f0: speed changed to 0 for port enp4s0f0
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: bond0: Gained carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: bond0: Configured
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: br0: Configured`

  Apt history, noting the systemd update just before the interfaces when down
  `Start-Date: 2019-04-09 06:38:55
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsystemd0:amd64 (237-3ubuntu10.15, 237-3ubuntu10.19), 
libpam-systemd:amd64 (237-3ubuntu10.15, 237-3ubuntu10.19), systemd:amd64 
(237-3ubuntu10.15, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.15, 
237-3ubuntu10.19)
  End-Date: 2019-04-09 06:39:06`

  The netplan config on this server:
  

[Touch-packages] [Bug 1824806] Re: Network stops working after systemd update

2019-04-20 Thread Dan Streetman
I marked this as 'fix released' because i believe (see last comments)
the latest systemd upgrade included patches to fix this - but if it's
still reproducable with the latest systemd release please feel free to
comment and move this back to 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/1824806

Title:
  Network stops working after systemd update

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I have four 18.04 servers that are regularly updated and have a
  bond/bridge configured via netplan. Every so often the interfaces
  themselves will have "speed changed to 0" and the server will be
  unresponsive over network. The servers are still usable via the
  console, though. I think I can confidently associate it with systemd
  updates. If I'm manually updating the servers, e.g., `apt dist-
  upgrade`, and there's a system update... the ssh session becomes
  unresponsive when updating systemd, timing of automatic security
  updates seems to coincide with it happening as well. Rebooting fixes
  the issue until the next systemd update. I've included some log
  excerpts and one of my netplan configs below. Thanks!

  syslog:
  `Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f3: Lost carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f3: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.661292] igb :04:00.3 
enp4s0f3: speed changed to 0 for port enp4s0f3
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f2: Lost carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f2: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host systemd[1]: Started Network Time Synchronization.
  Apr 9 06:39:01 stn-vm-host systemd[1]: Stopped Flush Journal to Persistent 
Storage.
  Apr 9 06:39:01 stn-vm-host systemd[1]: Stopping Flush Journal to Persistent 
Storage...
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.732487] systemd[1]: Stopping 
Journal Service...
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.732903] systemd-journald[672]: 
Received SIGTERM from PID 1 (systemd).
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.823634] igb :04:00.2 
enp4s0f2: speed changed to 0 for port enp4s0f2
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.833718] systemd[1]: Stopped 
Journal Service.
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.837652] systemd[1]: Starting 
Journal Service...
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f1: Lost carrier
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f1: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host systemd[1]: Starting Flush Journal to Persistent 
Storage...
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.912976] systemd[1]: Started 
Journal Service.
  Apr 9 06:39:01 stn-vm-host systemd[1]: Started Flush Journal to Persistent 
Storage.
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.971223] igb :04:00.1 
enp4s0f1: speed changed to 0 for port enp4s0f1
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f0: Lost carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f0: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host kernel: [1058498.109063] igb :04:00.0 
enp4s0f0: speed changed to 0 for port enp4s0f0
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: bond0: Gained carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: bond0: Configured
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: br0: Configured`

  Apt history, noting the systemd update just before the interfaces when down
  `Start-Date: 2019-04-09 06:38:55
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsystemd0:amd64 (237-3ubuntu10.15, 237-3ubuntu10.19), 
libpam-systemd:amd64 (237-3ubuntu10.15, 237-3ubuntu10.19), systemd:amd64 
(237-3ubuntu10.15, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.15, 
237-3ubuntu10.19)
  End-Date: 2019-04-09 06:39:06`

  The netplan config on this server:
  `network:
  ethernets:
  enp4s0f0:
  addresses: []
  dhcp4: false
   

[Touch-packages] [Bug 1824806] Re: Network stops working after systemd update

2019-04-20 Thread Dan Streetman
> So this may very well have been fixed by 237-3ubuntu10.20, but I don't want
> to speak for the original reporter

that's why I asked, because 10.20 included patches to prevent systemd
from removing all addresses/routes that it has config for, during
startup.  So I hoped that would fix your issue as well, which it sounds
like it has.

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

Title:
  Network stops working after systemd update

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I have four 18.04 servers that are regularly updated and have a
  bond/bridge configured via netplan. Every so often the interfaces
  themselves will have "speed changed to 0" and the server will be
  unresponsive over network. The servers are still usable via the
  console, though. I think I can confidently associate it with systemd
  updates. If I'm manually updating the servers, e.g., `apt dist-
  upgrade`, and there's a system update... the ssh session becomes
  unresponsive when updating systemd, timing of automatic security
  updates seems to coincide with it happening as well. Rebooting fixes
  the issue until the next systemd update. I've included some log
  excerpts and one of my netplan configs below. Thanks!

  syslog:
  `Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f3: Lost carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f3: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.661292] igb :04:00.3 
enp4s0f3: speed changed to 0 for port enp4s0f3
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f2: Lost carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f2: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host systemd[1]: Started Network Time Synchronization.
  Apr 9 06:39:01 stn-vm-host systemd[1]: Stopped Flush Journal to Persistent 
Storage.
  Apr 9 06:39:01 stn-vm-host systemd[1]: Stopping Flush Journal to Persistent 
Storage...
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.732487] systemd[1]: Stopping 
Journal Service...
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.732903] systemd-journald[672]: 
Received SIGTERM from PID 1 (systemd).
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.823634] igb :04:00.2 
enp4s0f2: speed changed to 0 for port enp4s0f2
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.833718] systemd[1]: Stopped 
Journal Service.
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.837652] systemd[1]: Starting 
Journal Service...
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f1: Lost carrier
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f1: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host systemd[1]: Starting Flush Journal to Persistent 
Storage...
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.912976] systemd[1]: Started 
Journal Service.
  Apr 9 06:39:01 stn-vm-host systemd[1]: Started Flush Journal to Persistent 
Storage.
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.971223] igb :04:00.1 
enp4s0f1: speed changed to 0 for port enp4s0f1
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f0: Lost carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f0: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host kernel: [1058498.109063] igb :04:00.0 
enp4s0f0: speed changed to 0 for port enp4s0f0
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: bond0: Gained carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: bond0: Configured
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: br0: Configured`

  Apt history, noting the systemd update just before the interfaces when down
  `Start-Date: 2019-04-09 06:38:55
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsystemd0:amd64 (237-3ubuntu10.15, 237-3ubuntu10.19), 
libpam-systemd:amd64 (237-3ubuntu10.15, 237-3ubuntu10.19), systemd:amd64 
(237-3ubuntu10.15, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.15, 
237-3ubuntu10.19)
  End-Date: 2019-04-09 06:39:06`

  The netplan config on this server:
  `network:
  ethernets:
  

[Touch-packages] [Bug 1690671] Re: Pointer clicks and hovering fail to have effect at the very left and top borders of screen

2019-04-20 Thread Douglas Silva
*** This bug is a duplicate of bug 1795135 ***
https://bugs.launchpad.net/bugs/1795135

** This bug has been marked a duplicate of bug 1795135
   XFCE window buttons are not clickable at the top of the screen

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

Title:
  Pointer clicks and hovering fail to have effect at the very left and
  top borders of screen

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME and Unity
  are not affected. Any DE still using gtk2 works fine. I tested 3
  different computers with Intel Graphics and they were all displaying
  the same glitch.

  It can always be reproduced. I can record a video of the issue if
  needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1690671/+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 1757375] Re: Desktop unable to Suspend when Inactive

2019-04-20 Thread Douglas Silva
No change in Disco. Still missing the entry at
"com.ubuntu.desktop.pkla".

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

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On 16.04 (XFCE session and others) and possibly later the power-
  manager is unable to suspend the system when the user is inactive. A
  PK user-agent dialog is presented for the user to authenticate first -
  and as this action occurs specifically when the user is idle and away
  the PC can end up having an unplanned loss of power when the battery
  is exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+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 1825639] [NEW] Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound.

2019-04-20 Thread Hammad R
Public bug reported:

This is the same problem in
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 and
even though I have pulseaudio 12.2 (on Xubuntu 18.10), this problem
persists (this T430 laptop has inbuilt Bluetooth).

This makes listening to music or any audio over Bluetooth almost
unbearable - while it is temporarily fixed by running `pactl suspend-
sink 1 && pactl suspend-sink 0` it soon returns. I have even updated the
BIOS but the problem persists.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bluez 5.50-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Apr 20 13:10:59 2019
InstallationDate: Installed on 2018-11-26 (144 days ago)
InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 2349G4G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=0e4c79dc-6836-4dcb-a54a-2c5842e1f6c1 ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ETB9WW (2.79 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2349G4G
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB9WW(2.79):bd02/19/2019:svnLENOVO:pn2349G4G:pvrThinkPadT430:rvnLENOVO:rn2349G4G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430
dmi.product.name: 2349G4G
dmi.product.sku: LENOVO_MT_2349
dmi.product.version: ThinkPad T430
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 24:FD:52:8C:5D:82  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:65823 acl:64 sco:0 events:9052 errors:0
TX bytes:15368368 acl:17880 sco:0 commands:101 errors:0

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Pulseaudio skips some time in the audio buffer, causing a bluetooth
  delay and crackling/clicking sound.

Status in bluez package in Ubuntu:
  New

Bug description:
  This is the same problem in
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 and
  even though I have pulseaudio 12.2 (on Xubuntu 18.10), this problem
  persists (this T430 laptop has inbuilt Bluetooth).

  This makes listening to music or any audio over Bluetooth almost
  unbearable - while it is temporarily fixed by running `pactl suspend-
  sink 1 && pactl suspend-sink 0` it soon returns. I have even updated
  the BIOS but the problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 20 13:10:59 2019
  InstallationDate: Installed on 2018-11-26 (144 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 2349G4G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=0e4c79dc-6836-4dcb-a54a-2c5842e1f6c1 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETB9WW (2.79 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349G4G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB9WW(2.79):bd02/19/2019:svnLENOVO:pn2349G4G:pvrThinkPadT430:rvnLENOVO:rn2349G4G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2349G4G
  dmi.product.sku: LENOVO_MT_2349
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 24:FD:52:8C:5D:82  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:65823 acl:64 sco:0 events:9052 errors:0
TX bytes:15368368 acl:17880 sco:0 commands:101 errors:0

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

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

[Touch-packages] [Bug 1825630] [NEW] Problem dected message pops up when I boot up

2019-04-20 Thread Lyn Griffith
Public bug reported:

The message about an unidentified problem pops up whenever I boot up and
asks me to send a problem report.  I've selected to send the report, but
nothing has changed.

When I opened the ACTIVITY LOG and selected DIAGNOSTICS, I chose the
option to view the error report.  The screen timed-out.  Firefox was
connected to the web and I have had no problems browsing for the last
several days.

I don't have a clue as to what the problem may be.

Operating System - 18.04.2 LTS

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 20 03:20:31 2019
DistUpgraded: 2018-08-15 17:02:55,988 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1494]
InstallationDate: Installed on 2017-08-03 (624 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Hewlett-Packard HP Compaq 8200 Elite CMT PC
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=0207821e-5c3d-4348-aa3e-b53f5c7cba2d ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-08-16 (247 days ago)
dmi.bios.date: 04/04/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: J01 v02.29
dmi.board.asset.tag: 2UA1311DPS
dmi.board.name: 1494
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA1311DPS
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.29:bd04/04/2016:svnHewlett-Packard:pnHPCompaq8200EliteCMTPC:pvr:rvnHewlett-Packard:rn1494:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq 8200 Elite CMT PC
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Aug 15 11:56:19 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputDell Dell USB Keyboard KEYBOARD, id 8
 inputDELL Laser Mouse MOUSE, id 9
 inputHP WMI hotkeys   KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic 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/1825630

Title:
  Problem dected message pops up when I boot up

Status in xorg package in Ubuntu:
  New

Bug description:
  The message about an unidentified problem pops up whenever I boot up
  and asks me to send a problem report.  I've selected to send the
  report, but nothing has changed.

  When I opened the ACTIVITY LOG and selected DIAGNOSTICS, I chose the
  option to view the error report.  The screen timed-out.  Firefox was
  connected to the web and I have had no problems browsing for the last
  several days.

  I don't have a clue as to what the problem may be.

  Operating System - 18.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 03:20:31 2019
  DistUpgraded: 2018-08-15 17:02:55,988 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core 

[Touch-packages] [Bug 1825628] Re: Totem not playing some files correctly (sound but no video)

2019-04-20 Thread Tim Hamilton
** Description changed:

  When played in Totem some videos will play sound but video output is a
  series of green and pink screens (see screenshot).
+ 
+ Problem appeared following update to 19.04, all files played fine under
+ previous releases.
  
  When run from the commandline Totem gives the following error.
  
  (totem:1601): Gtk-WARNING **: 20:03:46.890: Drawing a gadget with
  negative dimensions. Did you forget to allocate a size? (node slider
  owner GtkScale)
  
  See below mediainfo output for a non-working file:
  
  eneral
  Complete name: Bananas In Pyjamas The Christmas 
Tree.mp4
  Format   : MPEG-4
  Format profile   : Base Media
  Codec ID : isom (isom/iso2/avc1/mp41)
  File size: 74.2 MiB
  Duration : 12 min 0 s
  Overall bit rate : 865 kb/s
  Writing application  : Lavf57.83.100
  
  Video
  ID   : 1
  Format   : AVC
  Format/Info  : Advanced Video Codec
  Format profile   : High@L4
  Format settings  : CABAC / 4 Ref Frames
  Format settings, CABAC   : Yes
  Format settings, ReFrames: 4 frames
  Codec ID : avc1
  Codec ID/Info: Advanced Video Coding
  Duration : 12 min 0 s
  Bit rate : 729 kb/s
  Width: 1 024 pixels
  Height   : 576 pixels
  Display aspect ratio : 16:9
  Frame rate mode  : Constant
  Frame rate   : 25.000 FPS
  Color space  : YUV
  Chroma subsampling   : 4:2:0
  Bit depth: 8 bits
  Scan type: Progressive
  Bits/(Pixel*Frame)   : 0.049
  Stream size  : 62.5 MiB (84%)
  Writing library  : x264 core 157
  Encoding settings: cabac=1 / ref=3 / deblock=1:0:0 / 
analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / 
me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / 
fast_pskip=1 / chroma_qp_offset=-2 / threads=18 / lookahead_threads=3 / 
sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / 
constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 
/ weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 
/ intra_refresh=0 / rc_lookahead=40 / rc=crf / mbtree=1 / crf=22.0 / qcomp=0.60 
/ qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=1404 / vbv_bufsize=3000 / 
crf_max=0.0 / nal_hrd=none / filler=0 / ip_ratio=1.40 / aq=1:1.00
  Codec configuration box  : avcC
  
  Audio
  ID   : 2
  Format   : AAC LC
  Format/Info  : Advanced Audio Codec Low Complexity
  Codec ID : mp4a-40-2
  Duration : 12 min 0 s
  Bit rate mode: Constant
  Bit rate : 128 kb/s
  Channel(s)   : 2 channels
  Channel layout   : L R
  Sampling rate: 44.1 kHz
  Frame rate   : 43.066 FPS (1024 SPF)
  Compression mode : Lossy
  Stream size  : 11.0 MiB (15%)
  Default  : Yes
  Alternate group  : 1
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libgstreamer1.0-0 1.15.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 19:56:58 2019
  InstallationDate: Installed on 2019-02-04 (75 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

Title:
  Totem not playing some files correctly (sound but no video)

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  When played in Totem some videos will play sound but video output is a
  

[Touch-packages] [Bug 1825628] [NEW] Totem not playing some files correctly (sound but no video)

2019-04-20 Thread Tim Hamilton
Public bug reported:

When played in Totem some videos will play sound but video output is a
series of green and pink screens (see screenshot).

When run from the commandline Totem gives the following error.

(totem:1601): Gtk-WARNING **: 20:03:46.890: Drawing a gadget with
negative dimensions. Did you forget to allocate a size? (node slider
owner GtkScale)

See below mediainfo output for a non-working file:

eneral
Complete name: Bananas In Pyjamas The Christmas 
Tree.mp4
Format   : MPEG-4
Format profile   : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size: 74.2 MiB
Duration : 12 min 0 s
Overall bit rate : 865 kb/s
Writing application  : Lavf57.83.100

Video
ID   : 1
Format   : AVC
Format/Info  : Advanced Video Codec
Format profile   : High@L4
Format settings  : CABAC / 4 Ref Frames
Format settings, CABAC   : Yes
Format settings, ReFrames: 4 frames
Codec ID : avc1
Codec ID/Info: Advanced Video Coding
Duration : 12 min 0 s
Bit rate : 729 kb/s
Width: 1 024 pixels
Height   : 576 pixels
Display aspect ratio : 16:9
Frame rate mode  : Constant
Frame rate   : 25.000 FPS
Color space  : YUV
Chroma subsampling   : 4:2:0
Bit depth: 8 bits
Scan type: Progressive
Bits/(Pixel*Frame)   : 0.049
Stream size  : 62.5 MiB (84%)
Writing library  : x264 core 157
Encoding settings: cabac=1 / ref=3 / deblock=1:0:0 / 
analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / 
me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / 
fast_pskip=1 / chroma_qp_offset=-2 / threads=18 / lookahead_threads=3 / 
sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / 
constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 
/ weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 
/ intra_refresh=0 / rc_lookahead=40 / rc=crf / mbtree=1 / crf=22.0 / qcomp=0.60 
/ qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=1404 / vbv_bufsize=3000 / 
crf_max=0.0 / nal_hrd=none / filler=0 / ip_ratio=1.40 / aq=1:1.00
Codec configuration box  : avcC

Audio
ID   : 2
Format   : AAC LC
Format/Info  : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 12 min 0 s
Bit rate mode: Constant
Bit rate : 128 kb/s
Channel(s)   : 2 channels
Channel layout   : L R
Sampling rate: 44.1 kHz
Frame rate   : 43.066 FPS (1024 SPF)
Compression mode : Lossy
Stream size  : 11.0 MiB (15%)
Default  : Yes
Alternate group  : 1

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libgstreamer1.0-0 1.15.90-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 20 19:56:58 2019
InstallationDate: Installed on 2019-02-04 (75 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gstreamer1.0
UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

** Attachment added: "Screenshot from 2019-04-20 19-54-10.png"
   
https://bugs.launchpad.net/bugs/1825628/+attachment/5257249/+files/Screenshot%20from%202019-04-20%2019-54-10.png

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

Title:
  Totem not playing some files correctly (sound but no video)

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  When played in Totem some videos will 

[Touch-packages] [Bug 1825626] [NEW] nvLock: client timed out, taking the lock

2019-04-20 Thread N/A
Public bug reported:

While launching an app or performing an operation, the screen has a
certain chance to freeze for a few seconds and then recover.

[ System Info ]
Version : Ubuntu 19.04
Kernel : x86_64 Linux 5.0.0-13-generic
GPU : NVIDIA GeForce GTX 1050
Xorg version : 1:7.7+19ubuntu12
Product Name : Aspire VX5-591G (Acer)

[ Log File ]
Uploaded as an attachment

*Sorry for my not-good English.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 20 17:19:29 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
 virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
 virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
   Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
MachineType: Acer Aspire VX5-591G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/07/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.06
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Wish_KLS
dmi.board.vendor: KBL
dmi.board.version: V1.06
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.06
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
dmi.product.family: Aspire VX 15
dmi.product.name: Aspire VX5-591G
dmi.product.sku: 
dmi.product.version: V1.06
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
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 disco ubuntu

** Attachment added: "log file"
   https://bugs.launchpad.net/bugs/1825626/+attachment/5257226/+files/Xorg.0.log

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

Title:
  nvLock: client timed out, taking the lock

Status in xorg package in Ubuntu:
  New

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 

[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

2019-04-20 Thread Philipp Verpoort
*** This bug is a duplicate of bug 520546 ***
https://bugs.launchpad.net/bugs/520546

I was experiencing the same issue on KDE Neon. Interestingly, this used
to work for ages, and now suddenly popped up all of a sudden. Running
`sudo kbd_mode -s` worked for me too.

Please could an attempt be made to prevent this from happening in the
future? It's quite annoying.

Many thanks to everybody for their effort.

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in console-setup package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+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 1825620] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 24

2019-04-20 Thread Ganesh Joshi
Public bug reported:

there is 1 error

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Sat Apr 20 13:49:27 2019
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 24
InstallationDate: Installed on 2017-07-09 (649 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.10
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 24
UpgradeStatus: Upgraded to bionic on 2019-04-20 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 24

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  there is 1 error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Sat Apr 20 13:49:27 2019
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 24
  InstallationDate: Installed on 2017-07-09 (649 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.10
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 24
  UpgradeStatus: Upgraded to bionic on 2019-04-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1825620/+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 1360488] Re: software-properties-gtk does not request root permission when choosing repositories in "Other Software" tab

2019-04-20 Thread Dries
*** This bug is a duplicate of bug 1424362 ***
https://bugs.launchpad.net/bugs/1424362

I have this behaviour on Ubuntu 19.04 (upgraded from 18.10

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

Title:
  software-properties-gtk does not request root permission when choosing
  repositories in "Other Software" tab

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  1) Description:   Ubuntu 14.04.1 LTS (Ubuntu-GNOME)
  Release:  14.04 amd64

  2) software-properties-gtk:
Installed: 0.92.37.1
Candidate: 0.92.37.1
Version table:
   *** 0.92.37.1 0
  500 http://www.lug.bu.edu/mirror/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.92.36 0
  500 http://www.lug.bu.edu/mirror/ubuntu/ trusty/main amd64 Packages

  3) When checking/unchecking repositories under the "Other Software"
  tab of software-properties-gtk I expect it to prompt me for root/sudo
  password, and once accepted I can check and uncheck my repositories.

  4)  The title may not explain issue good enough so forgive me for being long 
winded just want to make sure issue is understood. This is what I experience 
when opening Software & Updates (software-properties-gtk) from app menu, and go 
to the "Other Software" tab. 
If you go to check or uncheck any of the repositories listed it does 
not let you because you don't have sudo/root privileges, that makes sense, but 
under regular Ubuntu 14.04.1 (I am currently running Ubuntu-GNOME 14.04.1) and 
you went ahead to check or uncheck a repository it would request root 
privileges at that moment by asking for the password. As long as the password 
was excepted you could then go ahead check/uncheck the repositories you want. 
In Ubuntu-GNOME it does not try and gain privilege it just darkens the list.  
If you open software-properties-gtk via terminal when you go to check/uncheck 
any repository it returns this error in terminal window: 
"ERROR:root:Authentication canceled, changes have not been saved" The only way 
you can get it to request root privileges is to hit one of the buttons below 
(Add, Edit, Remove, Add Volume). So it does not cause an issue you can not get 
around, it was just something that I noticed that happened with Ubuntu 14.04.1 
that does not with Ubuntu-GNOME 14.04.1 and probably should.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: rr272x_1x
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Aug 22 19:48:49 2014
  InstallationDate: Installed on 2014-08-20 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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