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

2019-11-13 Thread Christian Ehrhardt 
Debian accepted my MR and 2.4.2 is there.
Unfortunately due to bug 1852389 I had to realize that I can't make it a sync 
yet.
I prepared a MP for a proper merge in 
https://code.launchpad.net/~paelzer/ubuntu/+source/libseccomp/+git/libseccomp/+merge/375472

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

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

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

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

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

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

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

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

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

-- 
Mailing list: 

[Touch-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

2019-11-13 Thread Marcin P
I have some additional observations (on regular kernel: 5.0.0-35-generic
#38~18.04.1-Ubuntu SMP Mon Nov 11 09:16:10 UTC 2019 x86_64 x86_64 x86_64
GNU/Linux):

I also have a HP docking station which has its own separated built-in
DAC. When laptop is connected to this docking station I can choose from
following sound devices:

- Digital Output (S/PDIF) - USB Audio
- Analog Output - USB Audio
- Speakers - Built-in Audio

When I don't connect headphones I can switch between these devices and
when coming back to built-in speakers the speakers usually work (however
sometimes they don't). But after connecting headphones the speakers will
never work again.

To clarify: all previous tests I did were done on laptop disconnected
from docking station.

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS

2019-11-13 Thread Tantely
Thank you Bro! it's work very well for me

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

Title:
  Hash Sum mismatch Ubuntu Server 18.04.1 LTS

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Hi,
  I'm getting weird Hashes mismatch error while trying to update Ubuntu server 
18.04.1 LTS server. The error I'm receiving is as follows.

  $ sudo apt-get update
  Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
  Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
  Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
  Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [52.2 
kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [152 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources 
[2,676 B]
  Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 
[277 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main Translation-en 
[105 kB]
  Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages [157 kB]
  Err:10 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
    Hash Sum mismatch
    Hashes of expected file:
     - Filesize:157408 [weak]
     - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
     - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak]
     - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak]
    Hashes of received file:
     - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a
     - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak]
     - MD5Sum:a33f0341357c0be32207618a14b500db [weak]
     - Filesize:157408 [weak]
    Last modification reported: Tue, 07 Aug 2018 07:15:09 +
    Release file created at: Tue, 07 Aug 2018 07:15:03 +
  Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/universe 
Translation-en [71.0 kB]
  Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 
Packages [3,772 B]
  Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse 
Translation-en [2,376 B]
  Err:14 http://download.webmin.com/download/repository sarge InRelease
    Could not connect to download.webmin.com:80 (108.60.199.109), connection 
timed out
  Fetched 329 kB in 30s (10.9 kB/s)
  Reading package lists... Done
  W: Failed to fetch 
http://download.webmin.com/download/repository/dists/sarge/InRelease  Could not 
connect to download.webmin.com:80 (108.60.199.109), connection timed out
  E: Failed to fetch 
http://archive.ubuntu.com/ubuntu/dists/bionic-updates/universe/binary-amd64/by-hash/SHA256/95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
  Hash Sum mismatch
     Hashes of expected file:
  - Filesize:157408 [weak]
  - SHA256:95fae016beb34455d4601a44c76d1823479178cbcdc58365750d4c039eecfb18
  - SHA1:ad29965fe436d84b62331a4662e5fc679103fa0d [weak]
  - MD5Sum:4375646a0495b45597e06fb3e21dbd10 [weak]
     Hashes of received file:
  - SHA256:cdb9774bad7ab6f191ce597e3139f105477428fdc2509c63fcac8e5b904e4f4a
  - SHA1:96a041a735ddb8be1b14cc214ce0f56b486b42db [weak]
  - MD5Sum:a33f0341357c0be32207618a14b500db [weak]
  - Filesize:157408 [weak]
     Last modification reported: Tue, 07 Aug 2018 07:15:09 +
     Release file created at: Tue, 07 Aug 2018 07:15:03 +
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  I have tried solution provided in search  as "removing all files in
  /var/lib/apt/lists and update again" but it doesn't work. Don't know
  how to resolve it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1785778/+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 1852399] [NEW] ?

2019-11-13 Thread Zoran Stojilovic
Public bug reported:

There is problem with video play on facebook

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 13 09:09:59 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 
Series Integrated Graphics Controller [1043:1de0]
InstallationDate: Installed on 2019-11-10 (2 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 003: ID 13d3:5a01 IMC Networks 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X540NA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=0d23bb72-2da5-41a9-b4cc-6c7a100ca090 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/22/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X540NA.311
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X540NA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540NA.311:bd08/22/2018:svnASUSTeKCOMPUTERINC.:pnX540NA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540NA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: X540NA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** 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/1852399

Title:
  ?

Status in xorg package in Ubuntu:
  New

Bug description:
  There is problem with video play on facebook

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 13 09:09:59 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 
Series Integrated Graphics Controller [1043:1de0]
  InstallationDate: Installed on 2019-11-10 (2 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540NA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=0d23bb72-2da5-41a9-b4cc-6c7a100ca090 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540NA.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540NA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 

[Touch-packages] [Bug 1835541] Re: ibus only provides non-standard UK keyboard layouts

2019-11-13 Thread Gunnar Hjalmarsson
** Bug watch added: github.com/ibus/ibus/issues #2153
   https://github.com/ibus/ibus/issues/2153

** Also affects: ibus via
   https://github.com/ibus/ibus/issues/2153
   Importance: Unknown
   Status: Unknown

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

Title:
  ibus only provides non-standard UK keyboard layouts

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Confirmed
Status in ibus package in Debian:
  Confirmed

Bug description:
  When I attempt to add my standard UK keyboard to the layouts ibus
  knows about, I cannot do so.

  (See the attached image for the list of available layouts.)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.19-4ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: i3
  Date: Fri Jul  5 10:07:41 2019
  InstallationDate: Installed on 2019-05-07 (58 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (57 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1835541/+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 1849859] Re: error when connecting to smb server

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

** Changed in: system-config-printer (Ubuntu)
   Status: New => Confirmed

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

Title:
  error when connecting to smb server

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1851385] Re: ubuntu 19.10 / print bug : requires authentication

2019-11-13 Thread Till Kamppeter
*** This bug is a duplicate of bug 1849859 ***
https://bugs.launchpad.net/bugs/1849859

** This bug has been marked a duplicate of bug 1849859
   error when connecting to smb server

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

Title:
  ubuntu 19.10 / print bug : requires authentication

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 2 computers(one laptop and one desktop) which have a dual boot
  Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a
  USB port from my modem on which my computers are connected using Wi-
  Fi.

  Since the upgrade of Ubuntu to version 19.10, I cannot print. On both
  computers I get the same message : [The printer] requires
  authentication / credentials required in order to print.

  With Ubuntu 19.04, I had absolutely no problem. I tried with a live
  USB with Ubuntu 19.04, there is no problem, the printer works. With a
  Ubuntu live 19.10, it doesn't work.

  If I plug the printer directly on a USB port on my computer, I get the
  same error message : [The printer] requires authentication /
  credentials required in order to print.

  It's the same behaviour on both computers, no I guess it must be a
  bug. Anyway I don't know which authentication I could do, with which
  ID and password ?

  Thank you very much

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 15:12:07 2019
  Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: 
smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B
  MachineType: Acer Aspire V5-571
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: Aspire V5-571
  dmi.product.name: Aspire V5-571
  dmi.product.sku: Aspire V5-571_072A_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1851385/+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 1849859] Re: error when connecting to smb server

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

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

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

Title:
  error when connecting to smb server

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1849859] Re: error when connecting to smb server

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

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

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

Title:
  error when connecting to smb server

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2

2019-11-13 Thread Adam Conrad
(eoan-amd64)root@nosferatu:~# apt-get install klibc-utils=2.0.6-1ubuntu2 
libklibc=2.0.6-1ubuntu2
(eoan-amd64)root@nosferatu:~# /sbin/losetup -vf
/dev/loop6
(eoan-amd64)root@nosferatu:~# /usr/lib/klibc/bin/losetup -vf
Loop device is /dev/loop6
loop: can't get info on device /dev/loop6: No such device or address
(eoan-amd64)root@nosferatu:~# apt-get install klibc-utils=2.0.6-1ubuntu3 
libklibc=2.0.6-1ubuntu3
(eoan-amd64)root@nosferatu:~# /sbin/losetup -vf
/dev/loop6
(eoan-amd64)root@nosferatu:~# /usr/lib/klibc/bin/losetup -vf
Loop device is /dev/loop6
/dev/loop6


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

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

Title:
  losetup -f broken in 2.0.6-1ubuntu2

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Eoan:
  Fix Committed
Status in klibc source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt,
  as main(argc) is reset to zero, after ioctl() operations in a function
  call, quite unexpectadly.

  [Test Case]

   * $ sudo /usr/lib/klibc/bin/losetup -vf
  Loop device is /dev/loop20
  loop: can't get info on device /dev/loop20: No such device or address

  is bad.

  Note that ioctl() must succeed, thus loop0 device must be configured
  to trigger the bug.

  
  [Regression Potential]

   * klibc is quite special, as it uses linux kernel headers/assembly.
  It seems like there is incompatibility between klibc sources, and
  gcc-9 with linux-5.3 when used to build userspace programmes.

   * disabling cf-protection and stack-clash-protection did not help.

   * building with gcc-8 does not exhibit the problem.

   * the workaround is quite simple in the code, keep a copy of argc to
  compare to it later in the code.

  [Other Info]

   * Original bug report

  http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz

  ...
  [   11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 
subsystem
  [   11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: 
(null)
  loop: can't get info on device /dev/loop1: No such device or address

  BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) + mkdir result
  + set -x
  + read LINE
  + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt
  ++ grep -q /rofs result/lsblk.txt
  grep: result/lsblk.txt: No such file or directory
  autopkgtest [21:45:45]: test boot: ---]
  autopkgtest [21:45:45]: test boot:  - - - - - - - - - - results - - - - - - - 
- - -
  boot FAIL non-zero exit status 2
  autopkgtest [21:45:45]:  summary
  boot FAIL non-zero exit status 2
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184/+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 1851340] Re: Ubuntu 19.10 upgrade results in invisible mouse cursor

2019-11-13 Thread John Hartley
Hi, did the following installs to try to get Wayland installed:

sudo apt install gnome-session-wayland
sudo apt install gnome-remote-desktop

Still just getting purple splash with no login;

Did "ps -ax | land"

ps -ax | grep land
 2127 tty1 Ssl+   0:00 /usr/lib/gdm3/gdm-wayland-session gnome-session 
--autostart /usr/share/gdm/greeter/autostart
 2338 ?Sl 0:00 /usr/bin/Xwayland :1024 -rootless -noreset -accessx 
-core -auth /run/user/126/.mutter-Xwaylandauth.77M8A0 -listen 4 -listen 5 
-displayfd 6
 4651 pts/0S+ 0:00 grep --color=auto land

So Xwayland appears to be started, so not sure why I am just getting
splash and no login prompt.

Thank,

John.

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

Title:
  Ubuntu 19.10 upgrade results in invisible mouse cursor

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have
  visible cursor with my Gnone desktop.

  I have found the same problem when upgrading 2 machines from Ubuntu
  19.04 -> 19.10.

  Reproducing problem is easy:

  1. Open Ubuntu Update Window
  2. Select "Upgrade"
  3. On completion of update (after reboot) cursor is no longer visible.
  4. This applies to display connected to VGA port on host with USB Keyboard + 
Mouse

  While the connected display has no visible cursor and so is usable, I
  have always used X11VNC Server to provide network GUI access. On the
  remote X11VNC display I see and can use the cursor.

  This bug report is being sent via Remote X11VNC window, as I cannot
  use the main VGA display window (due to lack of visible cursor)

  I have done search online and thought that maybe issue was with my USB
  Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
  result, no visible mouse cursor.

  I have done: "grep usb /var/log/syslog" and can see many USB events,
  including both Apple and Logitech mouse detection events.

  NOTE:

  Due to compatibility issue with X11VNC, I have disable Wayland on both
  machines by adding the following option to: /etc/gdm3/custom.conf

  WaylandEnable=false

  Regards,

  John Hartley.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 18:25:23 2019
  DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo G200eR2 [1d49:0a01]
  InstallationDate: Installed on 2018-12-17 (322 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO System x3650 M5: -[8871AC1]-
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash 
iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: -[TCE140H-2.91]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 01KN179
  dmi.board.vendor: LENOVO
  dmi.board.version: NULL
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone:
  dmi.product.family: System X
  dmi.product.name: System x3650 M5: -[8871AC1]-
  dmi.product.sku: (none)
  dmi.product.version: 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1852411] [NEW] systemd resolver not working

2019-11-13 Thread Thomas Schweikle
Public bug reported:

resolv.conf holds after boot:
nameserver 127.0.0.53
options edns0
[...]

Trying to resolve google.com just leads to nothing. Same for any address you 
try to resolve. Systemd just does not forward to the given resolver address in 
/etc/systemd/resolved.conf:
[Resolve]
DNS=172.18.8.1
#FallbackDNS=
Domains=bfs.de bfs.intern lab.bfs.de rodos.bfs.de
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#DNSOverTLS=no
#Cache=yes
#DNSStubListener=yes
#ReadEtcHosts=yes

Copying the address given vor variable DNS in /etc/systemd/resolved.conf
to nameserver in /etc/resolve.conf makes everything working immediately.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: systemd 242-7ubuntu3
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
Date: Wed Nov 13 10:23:18 2019
InstallationDate: Installed on 2019-09-09 (64 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
 LANGUAGE=de_DE
 TERM=screen
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-19-generic 
root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet 
splash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2019
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
mtime.conffile..etc.systemd.resolved.conf: 2019-09-24T10:52:27.095603

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


** Tags: amd64 apport-bug eoan

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

Title:
  systemd resolver not working

Status in systemd package in Ubuntu:
  New

Bug description:
  resolv.conf holds after boot:
  nameserver 127.0.0.53
  options edns0
  [...]

  Trying to resolve google.com just leads to nothing. Same for any address you 
try to resolve. Systemd just does not forward to the given resolver address in 
/etc/systemd/resolved.conf:
  [Resolve]
  DNS=172.18.8.1
  #FallbackDNS=
  Domains=bfs.de bfs.intern lab.bfs.de rodos.bfs.de
  #LLMNR=no
  #MulticastDNS=no
  #DNSSEC=no
  #DNSOverTLS=no
  #Cache=yes
  #DNSStubListener=yes
  #ReadEtcHosts=yes

  Copying the address given vor variable DNS in
  /etc/systemd/resolved.conf to nameserver in /etc/resolve.conf makes
  everything working immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Wed Nov 13 10:23:18 2019
  InstallationDate: Installed on 2019-09-09 (64 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-19-generic 
root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet 
splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware 

[Touch-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

2019-11-13 Thread Marcin P
** Attachment added: "alsa-info.txt.still-failed-built-in-speakers"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+attachment/5305011/+files/alsa-info.txt.still-failed-built-in-speakers

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

2019-11-13 Thread Marcin P
** Attachment added: "alsa-info.txt.success-internal-headphones"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+attachment/5305010/+files/alsa-info.txt.success-internal-headphones

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

2019-11-13 Thread Marcin P
** Attachment added: "alsa-info.txt.failed-built-in-speaker.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+attachment/5305009/+files/alsa-info.txt.failed-built-in-speaker.txt

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

2019-11-13 Thread Marcin P
I installed modified kernal:
5.0.0-34.36+conexant-codec-generic #codec SMP Tue Nov 12 22:40:14 CST 2019 
x86_64 x86_64 x86_64 GNU/Linux

After system startup there is no sound from built-in speakers.
After connecting headphones sound works correctly in headphones.
After disconnecting headphones again there is no sound from built-in speakers.

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1850127] Re: Unable to print with Brother printer since upgrade to Ubuntu 19.10

2019-11-13 Thread Till Kamppeter
As your printer is working again now and we are not able to investigate
the original problem I am closing this bug now.

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

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

Title:
  Unable to print with Brother printer since upgrade to Ubuntu 19.10

Status in cups package in Ubuntu:
  Invalid

Bug description:
  I have recently bought a new color laser printer (Brother HL-
  L8260CDW), which is connected through wLAN. It works like a charm
  under Ubuntu 19.04, but refuses to print since the upgrade to stock
  Ubuntu 19.10. I can reach it via ping and through its HTTP config page
  from the same computer.

  During my collection of relevant bug information I discovered the
  following error messages:

  1. Some print filter was unable to grep 
/etc/cups/ppd/Brother_HL_L8260CDW_series.ppd
  This file was rw for user "root" and r for group "lp", but not accessible 
to others.
  I have made it world readable for testing purposes, but I still can't 
print.

  2. I checked /var/log/syslog for app-armour errors but found none which would 
be related
  to cups and/or printing

  3. After fixing the permission issue, the new error message is "File \'\' not 
found" and
  "Unable to add document to print job.", both of which are too cryptic for 
me to dig
  further into this by myself.

  
  Attached to this bug report I send the following pieces of information:
  - output from "/usr/lib/cups/backend/snmp 10.0.0.14" (snmp.txt)
  - output from "lpinfo -v" (lpinfo.txt)
  - output from "avahi-browse -a -v -t -r" and "avahi-browse -a -v -c -r" 
(avahi.txt)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CupsErrorLog:
   E [28/Oct/2019:10:40:04 +0100] [Job 112] File \'\' not found
   E [28/Oct/2019:10:40:12 +0100] [Job 112] Unable to add document to print job.
   E [28/Oct/2019:10:45:59 +0100] [Job 113] File \'\' not found
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 10:50:05 2019
  InstallationDate: Installed on 2015-11-11 (1446 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat: device for Brother_HL_L8260CDW_series: 
implicitclass://Brother_HL_L8260CDW_series/
  MachineType: MSI MS-7982
  Papersize: a4
  PpdFiles: Brother_HL_L8260CDW_series: HL-L8260CDW series - IPP Everywhere
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=64458150-bde5-4ffc-8eb1-038fae855347 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.10
  dmi.board.asset.tag: Default string
  dmi.board.name: B150M PRO-DH (MS-7982)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.10:bd07/08/2015:svnMSI:pnMS-7982:pvr1.0:rvnMSI:rnB150MPRO-DH(MS-7982):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7982
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1850127/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

2019-11-13 Thread Hui Wang
Please remove any modle= from alsa-base.conf

Install the testing kernel and reboot, then test headphone and speaker with the 
testing kernel.
https://people.canonical.com/~hwang4/samsung-test/
(to install the testing kernel, sudo dpkg -i linux-modules-xxx.deb; sudo dpkg 
-i linux-image-xxx.deb; sudo dpkg -i linux-modules-extra-.deb)

If headphone and speaker still don't work, please run this script and
retest the headphone and speaker again.

then upload the dmesg and alsa-info.txt-with-coeff

** Attachment added: "set-coeff.sh"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5305138/+files/set-coeff.sh

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  

[Touch-packages] [Bug 1852474] [NEW] cups not printing if authentication required by server

2019-11-13 Thread Thomas Schweikle
Public bug reported:

cups does not print if servers require authenticated users to print. No
login-dialog is shown. Print jobs are on hold, waiting for
legitimization. But no legitimization dialog will be shown.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups 2.2.12-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7
Uname: Linux 5.3.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Nov 13 19:23:18 2019
InstallationDate: Installed on 2019-09-09 (65 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lpstat:
 device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: 
smb://srvmfg02-muc.bfs.de/drucker-muc
 device for Lexmark_MX310dn: implicitclass://Lexmark_MX310dn/
Lsusb:
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: VMware, Inc. VMware Virtual Platform
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd', 
'/etc/cups/ppd/Lexmark_MX310dn.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied
 grep: /etc/cups/ppd/Lexmark_MX310dn.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-22-generic 
root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet 
splash
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2019
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

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


** Tags: amd64 apport-bug eoan

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

Title:
  cups not printing if authentication required by server

Status in cups package in Ubuntu:
  New

Bug description:
  cups does not print if servers require authenticated users to print.
  No login-dialog is shown. Print jobs are on hold, waiting for
  legitimization. But no legitimization dialog will be shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7
  Uname: Linux 5.3.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Nov 13 19:23:18 2019
  InstallationDate: Installed on 2019-09-09 (65 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat:
   device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: 
smb://srvmfg02-muc.bfs.de/drucker-muc
   device for Lexmark_MX310dn: implicitclass://Lexmark_MX310dn/
  Lsusb:
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd', 
'/etc/cups/ppd/Lexmark_MX310dn.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied
   grep: /etc/cups/ppd/Lexmark_MX310dn.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-22-generic 
root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet 
splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  

[Touch-packages] [Bug 1852022] Re: casper's postponing of snap refresh broken by switch to busybox date

2019-11-13 Thread Launchpad Bug Tracker
This bug was fixed in the package casper - 1.432

---
casper (1.432) focal; urgency=medium

  * scripts/casper-helpers: pass --no-reread to sfdisk when creating the
casper-rw partition to reduce the risk of self-races (which probably only
happen in qemu-system-emulation i.e. in the autopkgtests).

 -- Michael Hudson-Doyle   Wed, 13 Nov 2019
15:07:08 +1300

** Changed in: casper (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  casper's postponing of snap refresh broken by switch to busybox date

Status in casper package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Booting the latest focal live server daily gets us this:

  Begin: Disabling snap refresh... ... date: unrecognized option 
'--iso-8601=seconds'
  BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu5) multi-call binary.

  Usage: date [OPTIONS] [+FMT] [TIME]

  Display time (using +FMT), or set time

[-s,--set] TIME Set time to TIME
-u,--utcWork in UTC (don't convert to local time)
-R,--rfc-2822   Output RFC-2822 compliant date string
-I[SPEC]Output ISO-8601 compliant date string
SPEC='date' (default) for date only,
'hours', 'minutes', or 'seconds' for date and
time to the indicated precision
-r,--reference FILE Display last modification time of FILE
-d,--date TIME  Display TIME, not 'now'
-D FMT  Use FMT for -d TIME conversion

  Recognized TIME formats:
hh:mm[:ss]
[.]MM.DD-hh:mm[:ss]
-MM-DD hh:mm[:ss]
[YY]YY]MM]DD]hh]mm[.ss]
'date TIME' form accepts MMDDhhmm[[YY]YY][.ss] instead
  done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1852022/+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 1288786] Re: pkexec does not launch graphical authentication

2019-11-13 Thread apt-ghetto
No, pkexec per default does not start a graphical application for security 
reasons.
If you want to start a graphical application with pkexec, you need a policy in 
/usr/share/polkit-1/actions.

But, nowadays, it mostly isn't necessary to start a graphical
application with elevated privileges, because there are better
alternatives.

On *buntu 18.04, synaptic does have a policy => 
https://packages.ubuntu.com/bionic/amd64/synaptic/filelist
You can start it with synaptic-pkexec. The same command is used in 
/usr/share/applications/synaptic.desktop

If it does not work and you have a policy, please check, that the
PolicyKit Authentication Agent is running (lxsession-default-apps in
section autostart) and logout/login.

I don't understand, how "su -l $other_user" is related to this bug
report?

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

Title:
  pkexec does not launch graphical authentication

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Installed Trusty Tahr Lubuntu Beta1 version and added xubuntu desktop.  In 
buth desktops, I tried to launch synaptic to install some packages.  If I try 
to launch from menu, nothing seems to happen.  From a terminal, I ran
pkexec "/usr/sbin/synaptic"
   and saw that it asks for password in the terminal window, instead of popping 
up an authentication window like previous Ubuntu version did.  That was why I 
saw no authentication request when launching from menu..  I have a 
workaround)launching from Terminal window), but this should be fixed before 
release.

  ralph@minnie:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)"
  ralph@minnie:~$ pkexec --version
  pkexec version 0.105

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1288786/+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 1852383] [NEW] system hangs on shutdown

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

On a Lenovo Yoga S940, the system always hangs on shutdown.
The screen turns black and nothing happens anymore. 
I have to keep pressed for several seconds the shutdown hardware button in 
order to actually turn it off.

I attach the journalctl output from the shutdown which present very
similar 'errors' from session to session.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7
Uname: Linux 5.3.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 13 07:03:38 2019
InstallationDate: Installed on 2019-10-09 (34 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190916)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan
-- 
system hangs on shutdown
https://bugs.launchpad.net/bugs/1852383
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

2019-11-13 Thread Sebastien Bacher
** Tags added: regression-update

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

Title:
  NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby
  a VPN connection which sets it's dns-priority to a negative value,
  which should cause the DNS server supplied by the DNS connection to be
  placed first, instead now refuses to place the DNS server into the
  resolver under any circumstance.

  Pinning the 1.10.6-2ubuntu1.1 works around the issue.

  I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

  This patch should be reverted as soon as possible to restore proper
  functionality of network manager with respect to VPN servers with DNS
  resolvers.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851407/+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 1851695] Re: DEP8 failure/regression in nspr on arm64 and armhf

2019-11-13 Thread Bryce Harrington
Debian has a patch for the issue:

https://salsa.debian.org/go-
team/packages/notary/commit/b4f024c049b916c4b81fbd1199c86c8b5dfe2934

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

Title:
  DEP8 failure/regression in nspr on arm64 and armhf

Status in notary package in Ubuntu:
  New
Status in nspr package in Ubuntu:
  Invalid
Status in notary package in Debian:
  Confirmed

Bug description:
  nspr 0.6.1~ds1-4 is failing DEP8 test in arm64 and armhf:

  
  autopkgtest [09:46:25]: test command1: /usr/bin/dh_golang_autopkgtest
  autopkgtest [09:46:25]: test command1: [---
  [info] Testing github.com/theupdateframework/notary...
  [info] Source code installed by binary package, overriding 
dh_auto_configure...
  [info] Disabling existing override_dh_auto_configure...
  dh build --builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build \
--buildsystem=golang \
--with=golang
 dh_update_autotools_config 
-O--builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build 
-O--buildsystem=golang
 dh_autoreconf 
-O--builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build 
-O--buildsystem=golang
 debian/rules override_dh_auto_configure
  make[1]: Entering directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp'
  mkdir -p "_build"
  cp -a /usr/share/gocode/src "_build"
  make[1]: Leaving directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp'
 debian/rules override_dh_auto_build
  make[1]: Entering directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp'
  dh_auto_build -- -tags "pkcs11"
cd _build && go install 
-gcflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" 
-asmflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" 
-v -p 1 -tags pkcs11 github.com/theupdateframework/notary 
github.com/theupdateframework/notary/client 
github.com/theupdateframework/notary/client/changelist 
github.com/theupdateframework/notary/cmd/escrow 
github.com/theupdateframework/notary/cmd/notary 
github.com/theupdateframework/notary/cmd/notary-server 
github.com/theupdateframework/notary/cmd/notary-signer 
github.com/theupdateframework/notary/cryptoservice 
github.com/theupdateframework/notary/passphrase 
github.com/theupdateframework/notary/proto 
github.com/theupdateframework/notary/server 
github.com/theupdateframework/notary/server/errors 
github.com/theupdateframework/notary/server/handlers 
github.com/theupdateframework/notary/server/snapshot 
github.com/theupdateframework/notary/server/storage 
github.com/theupdateframework/notary/server/timestamp 
github.com/theupdateframework/notary/signer 
github.com/theupdateframework/notary/signer/api 
github.com/theupdateframework/notary/signer/client 
github.com/theupdateframework/notary/signer/keydbstore 
github.com/theupdateframework/notary/storage 
github.com/theupdateframework/notary/storage/rethinkdb 
github.com/theupdateframework/notary/trustmanager 
github.com/theupdateframework/notary/trustmanager/remoteks 
github.com/theupdateframework/notary/trustmanager/yubikey 
github.com/theupdateframework/notary/trustpinning 
github.com/theupdateframework/notary/tuf 
github.com/theupdateframework/notary/tuf/data 
github.com/theupdateframework/notary/tuf/signed 
github.com/theupdateframework/notary/tuf/testutils 
github.com/theupdateframework/notary/tuf/testutils/interfaces 
github.com/theupdateframework/notary/tuf/testutils/keys 
github.com/theupdateframework/notary/tuf/utils 
github.com/theupdateframework/notary/tuf/validation 
github.com/theupdateframework/notary/utils 
github.com/theupdateframework/notary/version
  src/github.com/docker/distribution/digestset/set.go:9:2: cannot find package 
"github.com/opencontainers/go-digest" in any of:

/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/docker/distribution/vendor/github.com/opencontainers/go-digest
 (vendor tree)
/usr/lib/go-1.12/src/github.com/opencontainers/go-digest (from $GOROOT)

/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/opencontainers/go-digest
 (from $GOPATH)
  src/github.com/docker/distribution/blobs.go:13:2: cannot find package 
"github.com/opencontainers/image-spec/specs-go/v1" in any of:

/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/docker/distribution/vendor/github.com/opencontainers/image-spec/specs-go/v1
 (vendor tree)
/usr/lib/go-1.12/src/github.com/opencontainers/image-spec/specs-go/v1 
(from $GOROOT)

/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/opencontainers/image-spec/specs-go/v1
 (from $GOPATH)
  dh_auto_build: cd _build && go install 
-gcflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" 
-asmflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" 
-v -p 1 -tags pkcs11 github.com/theupdateframework/notary 

[Touch-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

2019-11-13 Thread Marcin P
Yes, the speakers behaves perfectly now. Thank you.

When auto-mute is enabled and I disconnect the headphones shouldn't the
global system volume be muted?

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 788167] Re: CUPS cannot print to Kerberos-authenticated SMB print queue

2019-11-13 Thread Thomas Schweikle
Same for Ubuntu 19.10 with cups 2.2.12

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

Title:
  CUPS cannot print to Kerberos-authenticated SMB print queue

Status in cups package in Ubuntu:
  Confirmed
Status in Debian:
  Fix Released

Bug description:
  Binary package hint: cups

  That was investigated on maverick (cups 1.4.4) and natty (cups 1.4.6).

  CUPS in Ubuntu cannot authenticate using Kerberos to an SMB print
  queue, such as one in an Active Directory.  This is because the smb
  backend is being invoked as user lp, and this user cannot access the
  Kerberos credential cache of the user who submitted the job.  When
  trying to print, the job is held for authentication, and a dialog
  prompting for username/password is being shown.  On Windows (and
  possibly other OS), the user would not be prompted if he has a ticket
  in the Kerberos realm (ie, "logged on to the domain") he is trying to
  print to.

  The CUPS smb backend on Ubuntu is the smbspool binary provided by
  Samba.  When run as a user, it will pick the Kerberos credential cache
  by itself and authenticate seamlessly.  Otherwise, it will read the
  KRB5CCNAME environment variable and try to use that when possible.

  There is two possible solutions to that:

  - Invoke the smb backend as root and pass it the KRB5CCNAME
  environment variable pointing to the user's Kerberos credential cache.
  CUPS execute the backend as user lp if it is world-executable, which
  is currently the case on Ubuntu.  User lp do not have the permission
  to read  the user's credential cache, hence why the smb backend would
  need to be executed as root (by removing the world-executable bit).
  Also, CUPS does not currently set KRB5CCNAME before invoking the smb
  backend (see http://www.cups.org/str.php?L3847).

  - Execute smbspool as the user submitting the job.

  
  I presume we would have the same problem with other backend that would do 
Kerberos authentication, although I do not know of a specific one.  I have only 
tested and investigated with the smb backend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/788167/+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 1609700] Re: username is not saved in openconnect connection dialog

2019-11-13 Thread Ilario Sanseverino
I too confirm the bug in Ubuntu 19.10

network-manager 1.1.20.4-2ubuntu2 amd6420.4-2ubuntu2 amd64
network-manager-openconnect 1.2.4-2ubuntu1 amd64
openconnect 8.02-1build1 amd64

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

Title:
  username is not saved in openconnect connection dialog

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in Fedora:
  Fix Released

Bug description:
  
  Hi,

  I clicked on "save passwords" but only the password is filled in
  automatically when I open the connection dialog. The "Username" field
  is empty!

  This happens for a SSLVPN configuration.

  For another VPN config (don't know which type) everything is ok.

  
  openconnect: 7.06-2build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support

2019-11-13 Thread El jinete sin cabeza
** Tags added: focal

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

Title:
  gi.repository.GLib.GError: pk-client-error-quark: could not do
  untrusted question as no klass support

Status in packagekit package in Ubuntu:
  Triaged
Status in packagekit source package in Eoan:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.98.2, the problem page at 
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  [Back trace]
  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted 
question as no klass support (8)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+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 1852383] Re: system hangs on shutdown

2019-11-13 Thread Sebastien Bacher
** Package changed: gdm3 (Ubuntu) => systemd (Ubuntu)

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

Title:
  system hangs on shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  On a Lenovo Yoga S940, the system always hangs on shutdown.
  The screen turns black and nothing happens anymore. 
  I have to keep pressed for several seconds the shutdown hardware button in 
order to actually turn it off.

  I attach the journalctl output from the shutdown which present very
  similar 'errors' from session to session.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7
  Uname: Linux 5.3.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 13 07:03:38 2019
  InstallationDate: Installed on 2019-10-09 (34 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190916)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852383/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

2019-11-13 Thread Lilian Tao
in reply to #23, @hui.wang please find the dump from window10 in
attachment.

** Attachment added: "RtHDDump-20191113.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5305169/+files/RtHDDump-20191113.txt

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

2019-11-13 Thread Martin S
dmesg output attached from #21, step 2)


** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5305171/+files/dmesg.txt

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1383 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 06:20:08 2019
  InstallationDate: Installed on 2019-11-03 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   

[Touch-packages] [Bug 1849859] Re: error when connecting to smb server

2019-11-13 Thread Till Kamppeter
For me it looks like that something changed in Samba. Printing on such a
server is done via the /usr/lib/cups/backend/smb CUPS backend which is
part of the smbclient package.

Is there no way to access the printer on the NAS via IPP?

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

Title:
  error when connecting to smb server

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

2019-11-13 Thread Martin S

Install the testing kernel and reboot, 


Couldn't boot after installing all 3 .deb's:

error: /boot/vmlinuz-5.3.0.23.25+samsung-test-generic has invalid signature
error: you need to load the kernel first

Press any key to continue...

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1383 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 06:20:08 2019
  InstallationDate: Installed on 2019-11-03 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all

[Touch-packages] [Bug 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

2019-11-13 Thread Dariusz Gadomski
Joe, I still can't reproduce your issue.
Can you please verify against what I'm trying:
1. Setup a VPN that provides DNS via DHCP
2. Connect to that VPN and verify DNS by:
$ systemd-resolve --status
(...)
Link 4 (tun0)
(...)
DNS Servers: X.X.X.X
(...)
3. Disconnect VPN and edit connection:
$ nmcli connection edit myvpn
nmcli> set ipv4.dns-priority -30
nmcli> save
$ nmcli connection show myvpn | grep dns-priority
ipv4.dns-priority:  -30
ipv6.dns-priority:  0

4. Re-connect to VPN and try to reach a name within the VPN:
$ dig some.host.in.my.vpn

I have used:
$ apt-cache policy network-manager
network-manager:
  Installed: 1.10.6-2ubuntu1.2

Please tell me in which of the steps in your case network-manager
behaves differently.

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

Title:
  NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby
  a VPN connection which sets it's dns-priority to a negative value,
  which should cause the DNS server supplied by the DNS connection to be
  placed first, instead now refuses to place the DNS server into the
  resolver under any circumstance.

  Pinning the 1.10.6-2ubuntu1.1 works around the issue.

  I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

  This patch should be reverted as soon as possible to restore proper
  functionality of network manager with respect to VPN servers with DNS
  resolvers.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851407/+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 1851349] Re: Xorg freeze

2019-11-13 Thread Pål Bergström
Didn't know what to include. It's long even if I do -d. But I found an
error with dmar. Not sure what it stands for but it led me to turn of
virtualization in BIOS. Crossing my fingers but it seems better. Though
some apps start very slow compared to 19.04 like FileZilla and FreeCAD.
Could be another thing or. Will see. The problem has been kind of
irrational.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Installed Ubuntu 19.10. A short freeze or lag occurs with the cursor
  now and then. Problem with multitasking.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 10:29:50 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-10-18 (17 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 5570
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=234e65b3-5622-44ae-9ba5-5d8a799fd811 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.4
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrX07:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851349/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

2019-11-13 Thread Hui Wang
Please do a test.

Boot with the regular kernel (5.0.0-35-generic), make sure the speakers
can work after booting, then run:

amixer sset 'Auto-Mute Mode' 'Disabled'

After that plug a headphone and unplug the headphone, does the speaker
still work?

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

2019-11-13 Thread Martin S
Hi,

1) Steps:
- Removed the option model=
- Rebooted
- turned off Secure Boot and booted with your test kernel.


Result:
No sound from speakers.
Very very quiet headphones.


2) Steps:
sudo set-coeff.sh
sudo su
echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef

Result:
No sound from speakers.
Very very quiet headphones.

alsa-info is attached.

Thanks,
Martin


** Attachment added: "alsa-info-with-coefficients-after-set-coeff.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5305170/+files/alsa-info-with-coefficients-after-set-coeff.txt

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID 

[Touch-packages] [Bug 1852411] Re: systemd resolver not working

2019-11-13 Thread Dan Streetman
what is the output of:

$ resolvectl status


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

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

Title:
  systemd resolver not working

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  resolv.conf holds after boot:
  nameserver 127.0.0.53
  options edns0
  [...]

  Trying to resolve google.com just leads to nothing. Same for any address you 
try to resolve. Systemd just does not forward to the given resolver address in 
/etc/systemd/resolved.conf:
  [Resolve]
  DNS=172.18.8.1
  #FallbackDNS=
  Domains=bfs.de bfs.intern lab.bfs.de rodos.bfs.de
  #LLMNR=no
  #MulticastDNS=no
  #DNSSEC=no
  #DNSOverTLS=no
  #Cache=yes
  #DNSStubListener=yes
  #ReadEtcHosts=yes

  Copying the address given vor variable DNS in
  /etc/systemd/resolved.conf to nameserver in /etc/resolve.conf makes
  everything working immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Wed Nov 13 10:23:18 2019
  InstallationDate: Installed on 2019-09-09 (64 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-19-generic 
root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet 
splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  mtime.conffile..etc.systemd.resolved.conf: 2019-09-24T10:52:27.095603

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852411/+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 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

2019-11-13 Thread Joe Hohertz
Did you ensure that the connection was set for "use only for resources
on the connection"? (I believe this may be ipv4.never-default=yes
setting in nmcli... and only bring it up because you do not mention it.)

I also think the negative DNS priority might be historical, no longer
needed. (I just noticed mine was set to 50, which I believe is default
for VPN connections now)

I should also note that if the never-default is set to "no"... I *will*
see the DNS server, however the routing is then incorrect as the VPN
concerned doesn't provide public routes.

So to be clear... never-default needs to be set to yes... DNS we expect
is from DHCP options sent from the VPN server, and the problem is that
you will see NO DNS servers for tun0 when you run the 'systemd-resolve
--status' command

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

Title:
  NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby
  a VPN connection which sets it's dns-priority to a negative value,
  which should cause the DNS server supplied by the DNS connection to be
  placed first, instead now refuses to place the DNS server into the
  resolver under any circumstance.

  Pinning the 1.10.6-2ubuntu1.1 works around the issue.

  I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

  This patch should be reverted as soon as possible to restore proper
  functionality of network manager with respect to VPN servers with DNS
  resolvers.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851407/+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 1852489] [NEW] [SRU] Enable support for Ussuri Cloud Archive

2019-11-13 Thread Corey Bryant
Public bug reported:

Please add support for:

   cloud-archive:ussuri
   cloud-archive:ussuri-proposed

This will also need to be SRU'd back to bionic.

[Impact]
End users have to manually enable the ussuri cloud archive pockets.

[Test case]
sudo add-apt-repository cloud-archive:ussuri
sudo add-apt-repository cloud-archive:ussuri-proposed

[Regression potential]
Limited - just a data item addition

** Affects: software-properties (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: software-properties (Ubuntu Bionic)
 Importance: High
 Status: Triaged

** Affects: software-properties (Ubuntu Focal)
 Importance: High
 Status: Triaged

** Also affects: software-properties (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: software-properties (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: software-properties (Ubuntu Focal)
   Status: New => Triaged

** Changed in: software-properties (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu Focal)
   Importance: Undecided => High

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

Title:
  [SRU] Enable support for Ussuri Cloud Archive

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Bionic:
  Triaged
Status in software-properties source package in Focal:
  Triaged

Bug description:
  Please add support for:

 cloud-archive:ussuri
 cloud-archive:ussuri-proposed

  This will also need to be SRU'd back to bionic.

  [Impact]
  End users have to manually enable the ussuri cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:ussuri
  sudo add-apt-repository cloud-archive:ussuri-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852489/+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 1849658] Re: resolved fallback to TCP fails for truncated UDP replies

2019-11-13 Thread Dan Streetman
ubuntu@lp1849658-e:~$ dpkg -l systemd|grep ii
ii  systemd242-7ubuntu3 amd64system and service manager
ubuntu@lp1849658-e:~$ dig +noanswer +noedns toomany.ddstreet.org
;; Truncated, retrying in TCP mode.

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

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

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Nov 13 21:59:23 UTC 2019
;; MSG SIZE  rcvd: 678

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

; <<>> DiG 9.11.5-P4-5.1ubuntu2-Ubuntu <<>> +noanswer +noedns 
toomany.ddstreet.org
;; global options: +cmd
;; connection timed out; no servers could be reached



ubuntu@lp1849658-e:~$ sudo systemctl restart systemd-resolved.service 
ubuntu@lp1849658-e:~$ dpkg -l systemd|grep ii
ii  systemd242-7ubuntu3.2 amd64system and service manager
ubuntu@lp1849658-e:~$ dig +noanswer +noedns toomany.ddstreet.org
;; Truncated, retrying in TCP mode.

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

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

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Nov 13 22:02:04 UTC 2019
;; MSG SIZE  rcvd: 678

ubuntu@lp1849658-e:~$ sudo resolvectl flush-caches
ubuntu@lp1849658-e:~$ dig +noanswer +noedns toomany.ddstreet.org
;; Truncated, retrying in TCP mode.

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

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

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed Nov 13 22:02:08 UTC 2019
;; MSG SIZE  rcvd: 678


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

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

Title:
  resolved fallback to TCP fails for truncated UDP replies

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

Bug description:
  [impact]

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

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

  [test case]

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

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

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

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

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

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

  [regression potential]

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

  [other info]

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

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

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

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


[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

2019-11-13 Thread Taylor Braun-Jones
My guess is that rls-bb-notfixing means this is not getting fixed in
Bionic Beaver 18.04. Really hoping a fix can make it into the 20.04 LTS
release though.

I agree with Paul - systemd-resolve is not doing what it promises to do.
>From systemd.network(5):

Both "search" and "routing-only" domains are used for routing of DNS 
queries:
look-ups for host names ending in those domains (hence also single label 
names, if
any "search domains" are listed), are routed to the DNS servers configured 
for
this interface. The domain routing logic is particularly useful on 
multi-homed
hosts with DNS servers serving particular private DNS zones on each 
interface.

The "routing-only" domain "~."  (the tilde indicating definition of a 
routing
domain, the dot referring to the DNS root domain which is the implied 
suffix of
all valid DNS names) has special effect. It causes all DNS traffic which 
does not
match another configured domain routing entry to be routed to DNS servers
specified for this interface. This setting is useful to prefer a certain 
set of
DNS servers if a link on which they are connected is available.

This setting is read by systemd-resolved.service(8). "Search domains" 
correspond
to the domain and search entries in resolv.conf(5). Domain name routing has 
no
equivalent in the traditional glibc API, which has no concept of domain name
servers limited to a specific link.

One partial workaround is to remove `[!UNAVAIL=return]` after `resolve`
in /etc/nsswitch.conf:

hosts: files mdns4_minimal [NOTFOUND=return] resolve dns myhostname

That way a traditional DNS resolution is done after systemd-resolve
fails. This works for everything I've tested so far _except_ Google
Chrome.

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

[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time

2019-11-13 Thread Dan Streetman
autopkgtest analysis for eoan:

linux-oem-osp1 tests have always failed.  ignore.

systemd tests for ppc64el have always failed for eoan.  ignore.

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

Title:
  [SRU] systemd-resolved negative caching for extended period of time

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache
  the result for very long (infinity?). I have to restart systemd-
  resolved to have the negative caching purged.

  * After SERVFAIL DNS server issue has been resolved, chromium/firefox
  still returns DNS error despite host can correctly resolve the name.

  [Test Case]

  * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s 
(See 201d995),
  however, there are several use cases on which this condition is not 
acceptable (See #5552 comments)
  and the only workaround would be to disable cache entirely or flush it , 
which isn't optimal.

  * Configure /etc/systemd/resolved.conf as follows:

  Cache=yes (default)

  * Restart systemd-resolved (systemctl restart systemd-
  resolved.service)

  * Run a host/getent command against a entry that will return SERVFAIL
  and check the journalctl output to see that the reply gets served from
  cache.

  root@systemd-disco:/home/ubuntu# host www.montemar.cl
  Host www.montemar.cl not found: 2(SERVFAIL)
  root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n
  -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 
UTC. --
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for 
 on scope dns on ens3/* now complete with 
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet 
with id 61042 on interface 1/AF_INET.
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 
6222.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query 
packet for id 53580
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for  
www.no-record.cl IN A.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache 
hit for  www.no-record.cl IN A
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < 
www.no-record.cl IN A> on scope dns on ens3/* now complete with  scope dns on ens3/.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP 
for transaction 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet 
with id 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming 
packet on transaction 22382 (rcode=SERVFAIL).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: 
SERVFAIL
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative 
entry for: www.metaklass.org IN A, cache mode set to no-negative
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for 
 on scope dns on ens3/ now complete with from network 
(unsigned).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet 
with id 31060 on interface 1/AF_INET.

  The following patch https://github.com/systemd/systemd/pull/13047
  implements the required changes.

  [Other Info]

  Note that systemd in Eoan is being upgraded to upstream 242, so I am
  not adding this to Eoan now, as I don't want to disturb the merge. If
  needed after the merge, I'll add to Eoan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1668771/+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 1831787] Re: Bogus routes after DHCP lease change

2019-11-13 Thread Dan Streetman
with dnsmasq server setup:

$ ip -4 a show ens8
3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
inet 1.2.3.1/24 scope global ens8
   valid_lft forever preferred_lft forever
$ cat /etc/dnsmasq.d/test 

interface=ens8
bind-dynamic

no-resolv
no-poll

domain=test,1.2.3.4/24
dhcp-range=test,1.2.3.100,1.2.3.199,1m
dhcp-host=52:54:00:f7:b2:99,1.2.3.50,1m


on the test system:

ubuntu@lp1831787-e:~$ dpkg -l systemd | grep ii
ii  systemd242-7ubuntu3.2 amd64system and service manager
ubuntu@lp1831787-e:~$ ip -4 a show dev ens8
3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
inet 1.2.3.50/24 brd 1.2.3.255 scope global dynamic ens8
   valid_lft 106sec preferred_lft 106sec
ubuntu@lp1831787-e:~$ ip -4 r
default via 1.2.3.1 dev ens8 proto dhcp src 1.2.3.50 metric 1024 
1.2.3.0/24 dev ens8 proto kernel scope link src 1.2.3.50 
1.2.3.1 dev ens8 proto dhcp scope link src 1.2.3.50 metric 1024 


then on dnsmasq server, change the test system addr to .60:

$ cat /etc/dnsmasq.d/test

interface=ens8
bind-dynamic

no-resolv
no-poll

domain=test,1.2.3.4/24
dhcp-range=test,1.2.3.100,1.2.3.199,1m
dhcp-host=52:54:00:f7:b2:99,1.2.3.60,1m


ubuntu@dhcp-test:~$ sudo systemctl restart dnsmasq


on test system, wait for dhcp lease to timeout:

ubuntu@lp1831787-e:~$ ip -4 a show dev ens8
3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
inet 1.2.3.60/24 brd 1.2.3.255 scope global dynamic ens8
   valid_lft 114sec preferred_lft 114sec
ubuntu@lp1831787-e:~$ ip -4 r
default via 1.2.3.1 dev ens8 proto dhcp src 1.2.3.60 metric 1024 
1.2.3.0/24 dev ens8 proto kernel scope link src 1.2.3.60 
1.2.3.1 dev ens8 proto dhcp scope link src 1.2.3.60 metric 1024 



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

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

Title:
  Bogus routes after DHCP lease change

Status in netplan:
  Invalid
Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  networkd does not remove old route(s) after DHCP address change

  [test case]

  on a system using networkd, that is connected to a network where you
  can control the addresses that the DHCP server provides, setup system
  with networkd to get address via DHCP, e.g.

  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4

  
  (re)start networkd or reboot, so the system gets an ipv4 DHCP address, and 
corresponding route to the gateway.

  
  Then on the dhcp server, change the subnet to a different subnet.  On the 
client, once its renews its DHCP address, the server will provide a new address 
in the new subnet, and the client will add a new default route to the new 
gateway address.  However, the old default route to the old gateway address 
isn't removed.

  Note this also happens without changing the entire subnet, but is more
  subtle as shown in the original description.

  [regression potential]

  this affects how networkd handles routes, so has the potential to
  leave a system with partial or incorrect networking, or no networking
  at all.  Any regression would most likely occur during networkd
  (re)start or during renewal of a DHCP lease, or when an interface is
  brought up.

  [other info]

  original description:
  ---

  
  Netplan config:

  network:
    version: 2
    renderer: networkd
    ethernets:
  eno4:
    dhcp4: no
  eno1np0:
    dhcp4: no
    addresses:
  - 172.16.0.2/24
    bridges:
  br0:
    dhcp4: yes
    interfaces:
  - eno4

  On initial boot, machine got 10.0.15.109 IP address:

  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: Configured
  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: DHCPv4 address 
10.0.15.109/23 via 10.0.15.253

  At one point, DHCP server reserver this IP address and client
  eventually picked up new IP address:

  May 03 15:01:12 ceph2 systemd-networkd[1137]: br0: DHCPv4 address
  10.0.15.128/23 via 10.0.15.253

  This resulted in IP addresses:

  # ip -o a
  1: loinet 127.0.0.1/8 scope host lo\   valid_lft forever 
preferred_lft forever
  1: loinet6 ::1/128 scope host \   valid_lft forever preferred_lft 
forever
  2: eno1np0inet 172.16.0.2/24 brd 172.16.0.255 scope global eno1np0\   
valid_lft forever preferred_lft forever
  2: eno1np0inet6 fe80::b226:28ff:fe53:56be/64 scope link \   valid_lft 
forever preferred_lft forever
  6: br0inet 10.0.15.128/23 brd 10.0.15.255 scope global dynamic br0\   
valid_lft 503sec preferred_lft 503sec
  6: br0inet6 fe80::b8d7:5eff:fe6b:62a/64 scope link \   

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

2019-11-13 Thread Dan Streetman
*** This bug is a duplicate of bug 1805183 ***
https://bugs.launchpad.net/bugs/1805183

ubuntu@lp1849608-e:~$ dpkg -l systemd|grep ii
ii  systemd242-7ubuntu3 amd64system and service manager
ubuntu@lp1849608-e:~$ sudo dhclient ens3
1496d6a9ac0e80d0d89028d430a5cd2c  
/run/systemd/resolved.conf.d/isc-dhcp-v4-ens3.conf
md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens3.conf: No such file or 
directory
bc36e352f2f891c62533a81bd3520f98  
/run/systemd/resolved.conf.d/isc-dhcp-v4-ens3.conf
md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v6-ens3.conf: No such file or 
directory
ubuntu@lp1849608-e:~$ resolvectl status | grep DNS
MulticastDNS setting: no
  DNSOverTLS setting: no
  DNSSEC setting: no
DNSSEC supported: no
  DNSSEC NTA: 10.in-addr.arpa
MulticastDNS setting: no
  DNSOverTLS setting: no
  DNSSEC setting: no
DNSSEC supported: no



ubuntu@lp1849608-e:~$ dpkg -l systemd|grep ii
ii  systemd242-7ubuntu3.2 amd64system and service manager
ubuntu@lp1849608-e:~$ sudo dhclient ens3
cmp: EOF on /tmp/tmp.inWeTd586j which is empty
ubuntu@lp1849608-e:~$ resolvectl status | grep DNS
MulticastDNS setting: no
  DNSOverTLS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 192.168.122.1
  DNS Domain: vm
  DNSSEC NTA: 10.in-addr.arpa
MulticastDNS setting: no
  DNSOverTLS setting: no
  DNSSEC setting: no
DNSSEC supported: no


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

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

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

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

Bug description:
  [impact]

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

  [test case]

  see original description below

  [regression potential]

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

  [other info]

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

  The change that originally added the &> to eoan is also being applied
  to b/d in bug 1805183, but with this fix added also.

  original description:
  ---

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

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

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

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

-- 
Mailing list: 

[Touch-packages] [Bug 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes

2019-11-13 Thread Dan Streetman
dnsmasq server conf:

domain=test,1.2.3.4/24
dhcp-range=test,1.2.3.100,1.2.3.199,1m
dhcp-option=42,1.2.3.1
#dhcp-option=121,0.0.0.0/0,1.2.3.1

test system conf:

ubuntu@lp1835581-e:~$ cat /etc/systemd/network/10-ens8.network 
[Match]
Name=ens8

[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6
Address=1.2.3.99/24



ubuntu@lp1835581-e:~$ dpkg -l systemd|grep ii
ii  systemd242-7ubuntu3 amd64system and service manager
ubuntu@lp1835581-e:~$ ip -4 a show ens8
3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
inet 1.2.3.99/24 brd 1.2.3.255 scope global ens8
   valid_lft forever preferred_lft forever
inet 1.2.3.170/24 brd 1.2.3.255 scope global secondary dynamic ens8
   valid_lft 98sec preferred_lft 98sec
ubuntu@lp1835581-e:~$ ip -4 r
default via 1.2.3.1 dev ens8 proto dhcp src 1.2.3.170 metric 1024 
1.2.3.0/24 dev ens8 proto kernel scope link src 1.2.3.99 
1.2.3.1 dev ens8 proto dhcp scope link src 1.2.3.170 metric 1024 


route src is correctly set to dhcp addr, when dnsmasq not configured with 
classless route


uncomment dnsmasq server conf classless route:

domain=test,1.2.3.4/24
dhcp-range=test,1.2.3.100,1.2.3.199,1m
dhcp-option=42,1.2.3.1
dhcp-option=121,0.0.0.0/0,1.2.3.1

reboot test system:

ubuntu@lp1835581-e:~$ ip -4 a show ens8
3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
inet 1.2.3.99/24 brd 1.2.3.255 scope global ens8
   valid_lft forever preferred_lft forever
inet 1.2.3.170/24 brd 1.2.3.255 scope global secondary dynamic ens8
   valid_lft 110sec preferred_lft 110sec
ubuntu@lp1835581-e:~$ ip -4 r
default via 1.2.3.1 dev ens8 proto dhcp metric 1024 
1.2.3.0/24 dev ens8 proto kernel scope link src 1.2.3.99 


route src incorrectly not set, when dnsmasq set to classless route



change dnsmasq server again to comment out classless route and restart it, then 
reboot test system:

ubuntu@lp1835581-e:~$ dpkg -l systemd|grep ii
ii  systemd242-7ubuntu3.2 amd64system and service manager
ubuntu@lp1835581-e:~$ ip -4 a show ens8
3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
inet 1.2.3.99/24 brd 1.2.3.255 scope global ens8
   valid_lft forever preferred_lft forever
inet 1.2.3.170/24 brd 1.2.3.255 scope global secondary dynamic ens8
   valid_lft 97sec preferred_lft 97sec
ubuntu@lp1835581-e:~$ ip -4 r
default via 1.2.3.1 dev ens8 proto dhcp src 1.2.3.170 metric 1024 
1.2.3.0/24 dev ens8 proto kernel scope link src 1.2.3.99 
1.2.3.1 dev ens8 proto dhcp scope link src 1.2.3.170 metric 1024 


re-enable classless route on server and reboot test system:

ubuntu@lp1835581-e:~$ ip -4 a show ens8
3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
inet 1.2.3.99/24 brd 1.2.3.255 scope global ens8
   valid_lft forever preferred_lft forever
inet 1.2.3.170/24 brd 1.2.3.255 scope global secondary dynamic ens8
   valid_lft 104sec preferred_lft 104sec
ubuntu@lp1835581-e:~$ ip -4 r
default via 1.2.3.1 dev ens8 proto dhcp src 1.2.3.170 metric 1024 
1.2.3.0/24 dev ens8 proto kernel scope link src 1.2.3.99 


route is correctly sourced from dhcp address



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

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

Title:
  networkd-dhcp4 does not set prefsrc for dhcp-provided classless or
  static routes

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  the systemd networkd dhcp4 client sets the prefsrc for the default
  route added when a dhcp server provides only the gateway; but if the
  dhcp server provides classless route(s), those are configured instead,
  and the prefsrc is not set for those.

  Normally this is ok, but if the dhcp client system has other
  address(es) configured on the interface using dhcp, then the src for
  packets sent through a classless/static route might not be the same as
  the address provided by the dhcp server.

  If the gateway/router provided in the dhcp classless/static route(s)
  only allows traffic from the address provided to the dhcp client, then
  traffic from the dhcp client may be dropped by the gateway/router.

  [test case]

  set up a dhcp server system (e.g. ubuntu with dnsmasq installed and
  configured) and a dhcp client system.  For example on the dhcp server,
  use this dnsmasq config:

  interface=ens8
  bind-interfaces
  domain=test,10.10.0.0/24
  dhcp-option=42,10.10.0.1
  dhcp-range=test,10.10.0.10,10.10.0.100,1h

  On the dhcp client system, use networkd config such as:

  $ 

[Touch-packages] [Bug 1852018] Re: Audio Stops Playing Briefly When Emptying Trash

2019-11-13 Thread Kashif Khan
sound card/driver :
Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
DeviceName: Onboard - Sound
Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS
Flags: bus master, fast devsel, latency 32, IRQ 143
Memory at a351 (64-bit, non-prefetchable) [size=16K]
Memory at a310 (64-bit, non-prefetchable) [size=1M]
Kernel driver in use: snd_hda_intel

I wasnt able to get any of the MP3 files to play via paplay

** Attachment added: "output of journalacl"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1852018/+attachment/5305258/+files/log.txt

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

Title:
  Audio Stops Playing Briefly When Emptying Trash

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 19.10 and encountered this issue. I had a podcast
  playing in the background on Firefox v. 70.0.1 and I was deleting some
  files. I then proceeded to empty the trash and saw that the audio
  stops briefly till the "Empty all items from Trash?" prompt shows up.

  I was able to duplicate this many times and it even occurred with
  audio on Chrome.

  The expected way for things to work would be the audio keeps on
  playing, if I just empty the trash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1852018/+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 1852018] Re: Audio Stops Playing Briefly When Emptying Trash

2019-11-13 Thread Sebastien Bacher
You should be able to try to e.g
$ paplay /usr/share/sounds/freedesktop/stereo/dialog-information.oga

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

Title:
  Audio Stops Playing Briefly When Emptying Trash

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 19.10 and encountered this issue. I had a podcast
  playing in the background on Firefox v. 70.0.1 and I was deleting some
  files. I then proceeded to empty the trash and saw that the audio
  stops briefly till the "Empty all items from Trash?" prompt shows up.

  I was able to duplicate this many times and it even occurred with
  audio on Chrome.

  The expected way for things to work would be the audio keeps on
  playing, if I just empty the trash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1852018/+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 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

2019-11-13 Thread Dariusz Gadomski
Thanks Joe.

There has to be another factor coming into play, as my setup contains
"use only for resources on its network".

$ nmcli connection show my-vpn  | grep -e ipv4.never-default -e 
ipv4.dns-priority
ipv4.dns-priority:  -30
ipv4.never-default: yes

Are you able to test this on Ubuntu 19.10?
It does not have the patch and in my tests it's consistent with what I observe 
on the patched 18.04.

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

Title:
  NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby
  a VPN connection which sets it's dns-priority to a negative value,
  which should cause the DNS server supplied by the DNS connection to be
  placed first, instead now refuses to place the DNS server into the
  resolver under any circumstance.

  Pinning the 1.10.6-2ubuntu1.1 works around the issue.

  I suspect the fix-dns-leak-lp1754671.patch has caused this regression.

  This patch should be reverted as soon as possible to restore proper
  functionality of network manager with respect to VPN servers with DNS
  resolvers.

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

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