[Touch-packages] [Bug 1827460] Re: [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep

[Alrick Grandison]

Launching with the Kernel 4.15.0.47.50 v4.15.0-47.50 resolves the issue.
The more recent kernel (above this one) has the issue.  Seems the more
recent kernel introduces some bug that needs to be fixed.

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

Title:
  [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  My Lenovo ideapad 330 laptop with Ubuntu 18.04 sounds works fine
  initially.  However,  when I close it down (to sleep) and then return,
  all the sound disappears.  The only way to get back the sound is to
  restart the laptop.  The issue seem to start after a recent automatic
  update.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rickodesea   1545 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 22:49:12 2019
  InstallationDate: Installed on 2019-03-28 (36 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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:  gdm1139 F pulseaudio
rickodesea   1545 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7XCN29WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr7XCN29WW:bd12/18/2018:svnLENOVO:pn81D1:pvrLenovoideapad330-15IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IGM:
  dmi.product.family: ideapad 330-15IGM
  dmi.product.name: 81D1
  dmi.product.version: Lenovo ideapad 330-15IGM
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827460/+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 1827460] Re: [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep

[Daniel van Vugt]

Yes bug 1826868 sounds similar.

In this bug the error is:

[ 2601.990141] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register
0x2f0d00. -5

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

Title:
  [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  My Lenovo ideapad 330 laptop with Ubuntu 18.04 sounds works fine
  initially.  However,  when I close it down (to sleep) and then return,
  all the sound disappears.  The only way to get back the sound is to
  restart the laptop.  The issue seem to start after a recent automatic
  update.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rickodesea   1545 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 22:49:12 2019
  InstallationDate: Installed on 2019-03-28 (36 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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:  gdm1139 F pulseaudio
rickodesea   1545 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7XCN29WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr7XCN29WW:bd12/18/2018:svnLENOVO:pn81D1:pvrLenovoideapad330-15IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IGM:
  dmi.product.family: ideapad 330-15IGM
  dmi.product.name: 81D1
  dmi.product.version: Lenovo ideapad 330-15IGM
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827460/+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 1827460] Re: [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep

[Hui Wang]

Please refer to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826868. Looks like
this is a similar bug with that one. They all have geminilake hdmi audio
controller.

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

Title:
  [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  My Lenovo ideapad 330 laptop with Ubuntu 18.04 sounds works fine
  initially.  However,  when I close it down (to sleep) and then return,
  all the sound disappears.  The only way to get back the sound is to
  restart the laptop.  The issue seem to start after a recent automatic
  update.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rickodesea   1545 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 22:49:12 2019
  InstallationDate: Installed on 2019-03-28 (36 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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:  gdm1139 F pulseaudio
rickodesea   1545 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7XCN29WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr7XCN29WW:bd12/18/2018:svnLENOVO:pn81D1:pvrLenovoideapad330-15IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IGM:
  dmi.product.family: ideapad 330-15IGM
  dmi.product.name: 81D1
  dmi.product.version: Lenovo ideapad 330-15IGM
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827460/+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 1827460] Re: [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep

[Oliver Johnson]

This happens on the grounds that the PC rests with the speakers handicapped and 
the earphones controlled on. To keep this from happening separate the earphones 
before putting the machine to rest.
https://www.epsonprintersupport247.com/fix-epson-printer-offline/

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

Title:
  [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  My Lenovo ideapad 330 laptop with Ubuntu 18.04 sounds works fine
  initially.  However,  when I close it down (to sleep) and then return,
  all the sound disappears.  The only way to get back the sound is to
  restart the laptop.  The issue seem to start after a recent automatic
  update.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rickodesea   1545 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 22:49:12 2019
  InstallationDate: Installed on 2019-03-28 (36 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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:  gdm1139 F pulseaudio
rickodesea   1545 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7XCN29WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr7XCN29WW:bd12/18/2018:svnLENOVO:pn81D1:pvrLenovoideapad330-15IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IGM:
  dmi.product.family: ideapad 330-15IGM
  dmi.product.name: 81D1
  dmi.product.version: Lenovo ideapad 330-15IGM
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827460/+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 1827460] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all

[Daniel van Vugt]

I can see a few audio-related error messages in your kernel log. But
even if that wasn't true then I would still suggest this is most likely
a kernel bug.

In case the problem happens to be pulseaudio crashing, please follow
these instructions first:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

If you couldn't find any evidence of 'pulseaudio' crashing in the past
then please try some slightly older (or newer) kernels and tell us if
you find some that don't have the bug:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

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

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

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

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

** Summary changed:

- [HDA-Intel - HDA Intel PCH, playback] No sound at all
+ [Lenovo IdeaPad 330] No sound at all

** Summary changed:

- [Lenovo IdeaPad 330] No sound at all
+ [Lenovo IdeaPad 330-15IGM] No sound at all

** Summary changed:

- [Lenovo IdeaPad 330-15IGM] No sound at all
+ [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep

** Tags added: resume suspend-resume

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

Title:
  [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  My Lenovo ideapad 330 laptop with Ubuntu 18.04 sounds works fine
  initially.  However,  when I close it down (to sleep) and then return,
  all the sound disappears.  The only way to get back the sound is to
  restart the laptop.  The issue seem to start after a recent automatic
  update.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rickodesea   1545 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 22:49:12 2019
  InstallationDate: Installed on 2019-03-28 (36 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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:  gdm1139 F pulseaudio
rickodesea   1545 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7XCN29WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr7XCN29WW:bd12/18/2018:svnLENOVO:pn81D1:pvrLenovoideapad330-15IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IGM:
  dmi.product.family: ideapad 330-15IGM
  dmi.product.name: 81D1
  dmi.product.version: Lenovo ideapad 330-15IGM
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827460/+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 1827460] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all

[Alrick Grandison]

Public bug reported:

My Lenovo ideapad 330 laptop with Ubuntu 18.04 sounds works fine
initially.  However,  when I close it down (to sleep) and then return,
all the sound disappears.  The only way to get back the sound is to
restart the laptop.  The issue seem to start after a recent automatic
update.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rickodesea   1545 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu May  2 22:49:12 2019
InstallationDate: Installed on 2019-03-28 (36 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
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:  gdm1139 F pulseaudio
  rickodesea   1545 F pulseaudio
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 7XCN29WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 330-15IGM
dmi.modalias: 
dmi:bvnLENOVO:bvr7XCN29WW:bd12/18/2018:svnLENOVO:pn81D1:pvrLenovoideapad330-15IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IGM:
dmi.product.family: ideapad 330-15IGM
dmi.product.name: 81D1
dmi.product.version: Lenovo ideapad 330-15IGM
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My Lenovo ideapad 330 laptop with Ubuntu 18.04 sounds works fine
  initially.  However,  when I close it down (to sleep) and then return,
  all the sound disappears.  The only way to get back the sound is to
  restart the laptop.  The issue seem to start after a recent automatic
  update.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rickodesea   1545 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 22:49:12 2019
  InstallationDate: Installed on 2019-03-28 (36 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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:  gdm1139 F pulseaudio
rickodesea   1545 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7XCN29WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr7XCN29WW:bd12/18/2018:svnLENOVO:pn81D1:pvrLenovoideapad330-15IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IGM:
  dmi.product.family: ideapad 330-15IGM
  dmi.product.name: 81D1
  dmi.product.version: Lenovo ideapad 330-15IGM
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827194] Re: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze

[Daniel van Vugt]

Added a gst-plugins-good1.0 task, assuming the problem is related to
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstmatroska.so

** Also affects: gst-plugins-good1.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Loading a subtitled mkv file while already playing a subtitled mkv
  file makes the UI freeze

Status in gst-plugins-good1.0 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  When you have been playing a subtitled mkv file for a while and try to
  load a new subtitled mkv file in the same instance of Totem, the UI
  freezes.

  You must let the video play for a while for the problem to manifest. I
  don't know how long exactly, but ten minutes should do it. Loading
  file after file in quick succession works fine, and it doesn't happen
  if you seek forward in the file to go to a later time in the video.
  You have to actually watch the video for a while for it to happen.

  This problem has been in Totem for the past several versions of
  Ubuntu, but in 19.04 the problem has slightly changed: Totem used to
  become completely unresponsive and you had to force quit it, but in
  19.04 you can click the close button and it closes immediately. Other
  than that, the problem is the same: all you get is a frozen black
  screen.

  This problem could affect other file formats as well, but subtitled
  Matroska files is what I've personally been affected by.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: totem 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  1 11:52:22 2019
  InstallationDate: Installed on 2019-04-26 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1827194/+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 1827440] WifiSyslog.txt

[Tyler Singer-Clark]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1827440/+attachment/5261101/+files/WifiSyslog.txt

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Touch-packages] [Bug 1827440] PulseList.txt

[Tyler Singer-Clark]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1827440/+attachment/5261098/+files/PulseList.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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827440] ProcModules.txt

[Tyler Singer-Clark]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1827440/+attachment/5261097/+files/ProcModules.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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827440] Lspci.txt

[Tyler Singer-Clark]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1827440/+attachment/5261092/+files/Lspci.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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827440] Lsusb.txt

[Tyler Singer-Clark]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1827440/+attachment/5261093/+files/Lsusb.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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827440] RfKill.txt

[Tyler Singer-Clark]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1827440/+attachment/5261099/+files/RfKill.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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827440] UdevDb.txt

[Tyler Singer-Clark]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1827440/+attachment/5261100/+files/UdevDb.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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827440] ProcInterrupts.txt

[Tyler Singer-Clark]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1827440/+attachment/5261096/+files/ProcInterrupts.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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827440] ProcCpuinfoMinimal.txt

[Tyler Singer-Clark]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1827440/+attachment/5261095/+files/ProcCpuinfoMinimal.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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827440] ProcCpuinfo.txt

[Tyler Singer-Clark]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1827440/+attachment/5261094/+files/ProcCpuinfo.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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827440] IwConfig.txt

[Tyler Singer-Clark]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1827440/+attachment/5261091/+files/IwConfig.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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827440] CurrentDmesg.txt

[Tyler Singer-Clark]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1827440/+attachment/5261090/+files/CurrentDmesg.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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827440] CRDA.txt

[Tyler Singer-Clark]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1827440/+attachment/5261089/+files/CRDA.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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

[Tyler Singer-Clark]

apport information

** Tags added: apport-collected

** Description changed:

  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.
  
  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.
  
  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.
  
  Thanks!
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
+  /dev/snd/controlC0:  tyler  1562 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2019-01-09 (113 days ago)
+ InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ MachineType: LENOVO 20KHS1TG00
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-48-generic N/A
+  linux-backports-modules-4.15.0-48-generic  N/A
+  linux-firmware 1.173.5
+ Tags:  bionic
+ Uname: Linux 4.15.0-48-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 02/19/2019
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N23ET62W (1.37 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20KHS1TG00
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40697 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad X1 Carbon 6th
+ dmi.product.name: 20KHS1TG00
+ dmi.product.version: ThinkPad X1 Carbon 6th
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1827440/+attachment/5261088/+files/AlsaInfo.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/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio 

[Touch-packages] [Bug 1827440] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1827440

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827440/+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 1827440] Re: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted

[Daniel van Vugt]

I wonder if another fix similar to bug 1817263 is required?

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

** Summary changed:

- [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
+ [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

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

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827440/+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 1614976] Re: "logger -n" does not work on ubuntu 14.04.4 LTS

[bugproxy]

** Tags removed: targetmilestone-inin14044
** Tags added: targetmilestone-inin1604

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

Title:
  "logger -n" does not work on ubuntu 14.04.4 LTS

Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - SONG YANG  - 2016-07-26 01:45:14 ==
  ---Problem Description---
  "logger -n" does not work on ubuntu 14.04.4 LTS
   
  Contact Information = yang...@cn.ibm.com 
   
  ---uname output---
  Linux c910f03c17k13 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22 
15:31:44 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ppc64le kvm guest  
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   
  root@c910f03c17k13:~# cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="14.04.4 LTS, Trusty Tahr"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 14.04.4 LTS"
  VERSION_ID="14.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  root@c910f03c17k13:~# uname -a
  Linux c910f03c17k13 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22 
15:31:44 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
  root@c910f03c17k13:~# service rsyslog status
  rsyslog start/running, process 2662
  root@c910f03c17k13:~# logger -n 10.3.17.12 
"n"  

  at the same time, the specified log server 10.3.17.12  received
  nothing:

  
  root@c910f03c17k12:~# ifconfig
  eth1  Link encap:Ethernet  HWaddr 42:94:0a:03:11:0c  
inet addr:10.3.17.12  Bcast:10.255.255.255  Mask:255.0.0.0
inet6 addr: fe80::4094:aff:fe03:110c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:19229222 errors:0 dropped:13 overruns:0 frame:0
TX packets:7993543 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:6070292795 (6.0 GB)  TX bytes:23352500478 (23.3 GB)

  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:65536  Metric:1
RX packets:1565234 errors:0 dropped:0 overruns:0 frame:0
TX packets:1565234 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:6510383999 (6.5 GB)  TX bytes:6510383999 (6.5 GB)

  virbr0Link encap:Ethernet  HWaddr 86:61:a7:59:05:64  
inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
UP BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  root@c910f03c17k12:~# makeconservercf
  root@c910f03c17k12:~# semanage port -l | grep 514
  cluster_port_t tcp  5149, 40040, 50006-50008
  cluster_port_t udp  5149, 50006-50008
  rsh_port_t tcp  514
  syslog_tls_port_t  tcp  6514
  syslog_tls_port_t  udp  6514
  syslogd_port_t udp  514
  virt_port_ttcp  16509, 16514
  virt_port_tudp  16509, 16514
  root@c910f03c17k12:~# ip add show
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  2: eth0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 42:6b:0a:03:11:0c brd ff:ff:ff:ff:ff:ff
  3: eth1:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
  link/ether 42:94:0a:03:11:0c brd ff:ff:ff:ff:ff:ff
  inet 10.3.17.12/8 brd 10.255.255.255 scope global eth1
 valid_lft forever preferred_lft forever
  inet6 fe80::4094:aff:fe03:110c/64 scope link 
 valid_lft forever preferred_lft forever
  4: virbr0:  mtu 1500 qdisc noqueue state 
DOWN group default 
  link/ether 86:61:a7:59:05:64 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
 valid_lft forever preferred_lft forever
  root@c910f03c17k12:~# tcpdump -A -i eth1 port 514
  NOTHING

  == Comment: #1 - SONG YANG  - 2016-07-26 01:46:08 ==
  The logger version:
  ii  bsdutils   1:2.20.1-5.1ubuntu20.7   
ppc64el  Basic utilities from 4.4BSD-Lite

  ==

  I do see it works on 14.04.3 :

  root@ubuntu:~# logger -n 127.0.0.1 "n"

  root@ubuntu:~# cat /var/log/syslog
 

[Touch-packages] [Bug 1827428] Re: Mouse cursor left freezed copy of itself

[Daniel van Vugt]

** Tags added: cursor nvidia

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

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

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

Title:
  Mouse cursor left freezed copy of itself

Status in mutter package in Ubuntu:
  New

Bug description:
  Mouse cursor left freezed copy of itself over all the windows after
  login after lock screen. Functionality is not broken. It's just not
  aesthetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 16:10:09 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] 
[103c:8392]
  InstallationDate: Installed on 2019-04-29 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop 17-an0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8392
  dmi.board.vendor: HP
  dmi.board.version: 40.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-an0xx
  dmi.product.sku: 2FP35EA#ACB
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+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 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.

[Daniel van Vugt]

Thanks for the bug report.

Firstly, please run this command to send us more information about the
machine:

  apport-collect 1827417

and in future you can avoid that by reporting bugs using the 'ubuntu-
bug' command.

Secondly, it sounds to me that this regression would most likely have
been the result of a kernel update, as audio regressions often are. So
please try some older (or newer) kernels and see if you can find some
that don't have the bug:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

** Tags added: xenial

** Tags added: regression-update

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

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

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

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

Title:
  Ubuntu 16.04 -  EMU10K1 / CT4832 lost ability to listen stereo on
  headphones -  there is upmixed  surround only.

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have a problem - after one of the updates (sorry for being not precise - I 
can only track it back to the time I have been surely listening something on 
headphones - it has to be beginning of this year because last time I have been 
listening more on my SB Live for sure was in last one-two weeks of February 
2019 - I have suddenly lost "stereo" on my headphones.
  I have speakers connected to on-board sound card and headphones connected to 
SB Live Value for few years, so I did not mess with outputs or something - one 
day I changed Audacious output to SbLive in pavucontrol (as usually) and that 
time the sound was weirdly filtered.
  I have found that this must be "surround upmix" which I do not need and tried 
to disable it,
  enable-remixing = no and the same for "LFE remixing" in 
/etc/pulse/daemon.conf did not work.
  It does not matter what configuration I choose in pavucontrol- analog stereo 
duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog 
output" scenarios the output is the same except for "mono" (no sound at all).
  I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the 
alsa configuration for stereo but the upmix is still present.

  I have followed the old thread in Launchpad Answers:
  https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428
  =
  Hello,

  i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the 
last update I have similar problem - I have lost ability to listen stereo music 
on my Soundblaster Live Value (i use earphones).
  Even system sounds , web browser content and mp3 files are up-mixed.
  Few days ago it was no problem to choose "analag stereo output" in 
pavucontrol, now it seems that at this output have rear surround channel only 
(as I suppose, there is "stereo" but vocals are like heard from the other room 
and there is sometimes reverb as in the bathroom) :/.
  I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf 
and in the home directory configuration file without success.
  I have purged pulseaudio but with the ALSA there is the same problem, I have 
tried purging alsa and reinstalling without effect.
  So i thought that it can be emu10k1 driver specific, after digging in the 
network for solutions I have had tried adding 
"hint.emu10kx.0.multichannel_disabled " to the module configuration file 
without visible (or rather soundible ;) effect.
  I have tried to check EMU10K1 configuration with aweset, but it gives error 
message, so maybe the bad magic sits somewhere around?

  aweset
  /dev/sequencer: No such file or directory

  Once again - everything worked fine until the last update. I use
  xubuntu desktop as my machine is quite old, in despair I have
  installed unity to find the sound settings / speaker configuration etc
  and button to "disable all effects" as I have seen somewhere, but
  there were no such options.

  Help me Obi Wan Kenobi, you're my only hope...
  =

  I have next tried to follow the path from ubuntu sound troubleshooting
  guide, I have purged everything, installed back and now I'm  here
  again with this "upmix" on SBLive! Value.

  Thanks in advance for help :)
  Tom

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827417/+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 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix Released
Status in openntpd package in Ubuntu:
  Confirmed
Status in ntp source package in Xenial:
  Invalid
Status in openntpd source package in Xenial:
  Confirmed
Status in ntp source package in Zesty:
  Invalid
Status in openntpd source package in Zesty:
  Confirmed
Status in ntp source package in Artful:
  Fix Released
Status in openntpd source package in Artful:
  Confirmed
Status in ntp source package in Bionic:
  Fix Released
Status in openntpd source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * NTP has new isolation features which makes it trigger apparmor issues.
   * Those apparmor issues not only clutter the log and make other things
     less readable, they also prevent ntp from reporting its actual
     messages.
   * Fix is opening the apparmor profile to follow ntp through the
     disconnect by the isolation feature.

  [Test Case]

   * This is hard to trigger, but then also not. Which means it is not
     entirely sorted out when it triggers and when not, but the following
     does trigger it in tests of Pitti and also mine (while at the same time
     sometimes it does not - mabye I had other guests or kvm instead of lxd)

   * First install ntp in Artful (or above unless fixed)
     * Install ntp and check demsg for denies
     * Once an issue triggers instead of the error in syslog you'll see the
   apparmor Deny like:
     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
     disconnected path" error=-13 profile="/usr/sbin/ntpd"
     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
     requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  [Regression Potential]

   * We are slightly opening up the apparmor profile which is far lower risk
     than adding more constraints. So safe from that POV.

   * OTOH one could think this might be a security issue, but in fact this
     isn't a new suggestion if you take a look at [1] with an ack by Seth of
     the Security Team.

  [Other Info]

   * n/a

  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html

  

  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+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 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix Released
Status in openntpd package in Ubuntu:
  Confirmed
Status in ntp source package in Xenial:
  Invalid
Status in openntpd source package in Xenial:
  Confirmed
Status in ntp source package in Zesty:
  Invalid
Status in openntpd source package in Zesty:
  Confirmed
Status in ntp source package in Artful:
  Fix Released
Status in openntpd source package in Artful:
  Confirmed
Status in ntp source package in Bionic:
  Fix Released
Status in openntpd source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * NTP has new isolation features which makes it trigger apparmor issues.
   * Those apparmor issues not only clutter the log and make other things
     less readable, they also prevent ntp from reporting its actual
     messages.
   * Fix is opening the apparmor profile to follow ntp through the
     disconnect by the isolation feature.

  [Test Case]

   * This is hard to trigger, but then also not. Which means it is not
     entirely sorted out when it triggers and when not, but the following
     does trigger it in tests of Pitti and also mine (while at the same time
     sometimes it does not - mabye I had other guests or kvm instead of lxd)

   * First install ntp in Artful (or above unless fixed)
     * Install ntp and check demsg for denies
     * Once an issue triggers instead of the error in syslog you'll see the
   apparmor Deny like:
     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
     disconnected path" error=-13 profile="/usr/sbin/ntpd"
     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
     requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  [Regression Potential]

   * We are slightly opening up the apparmor profile which is far lower risk
     than adding more constraints. So safe from that POV.

   * OTOH one could think this might be a security issue, but in fact this
     isn't a new suggestion if you take a look at [1] with an ack by Seth of
     the Security Team.

  [Other Info]

   * n/a

  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html

  

  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+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 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix Released
Status in openntpd package in Ubuntu:
  Confirmed
Status in ntp source package in Xenial:
  Invalid
Status in openntpd source package in Xenial:
  Confirmed
Status in ntp source package in Zesty:
  Invalid
Status in openntpd source package in Zesty:
  Confirmed
Status in ntp source package in Artful:
  Fix Released
Status in openntpd source package in Artful:
  Confirmed
Status in ntp source package in Bionic:
  Fix Released
Status in openntpd source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * NTP has new isolation features which makes it trigger apparmor issues.
   * Those apparmor issues not only clutter the log and make other things
     less readable, they also prevent ntp from reporting its actual
     messages.
   * Fix is opening the apparmor profile to follow ntp through the
     disconnect by the isolation feature.

  [Test Case]

   * This is hard to trigger, but then also not. Which means it is not
     entirely sorted out when it triggers and when not, but the following
     does trigger it in tests of Pitti and also mine (while at the same time
     sometimes it does not - mabye I had other guests or kvm instead of lxd)

   * First install ntp in Artful (or above unless fixed)
     * Install ntp and check demsg for denies
     * Once an issue triggers instead of the error in syslog you'll see the
   apparmor Deny like:
     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
     disconnected path" error=-13 profile="/usr/sbin/ntpd"
     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
     requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  [Regression Potential]

   * We are slightly opening up the apparmor profile which is far lower risk
     than adding more constraints. So safe from that POV.

   * OTOH one could think this might be a security issue, but in fact this
     isn't a new suggestion if you take a look at [1] with an ack by Seth of
     the Security Team.

  [Other Info]

   * n/a

  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html

  

  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+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 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix Released
Status in openntpd package in Ubuntu:
  Confirmed
Status in ntp source package in Xenial:
  Invalid
Status in openntpd source package in Xenial:
  Confirmed
Status in ntp source package in Zesty:
  Invalid
Status in openntpd source package in Zesty:
  Confirmed
Status in ntp source package in Artful:
  Fix Released
Status in openntpd source package in Artful:
  Confirmed
Status in ntp source package in Bionic:
  Fix Released
Status in openntpd source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * NTP has new isolation features which makes it trigger apparmor issues.
   * Those apparmor issues not only clutter the log and make other things
     less readable, they also prevent ntp from reporting its actual
     messages.
   * Fix is opening the apparmor profile to follow ntp through the
     disconnect by the isolation feature.

  [Test Case]

   * This is hard to trigger, but then also not. Which means it is not
     entirely sorted out when it triggers and when not, but the following
     does trigger it in tests of Pitti and also mine (while at the same time
     sometimes it does not - mabye I had other guests or kvm instead of lxd)

   * First install ntp in Artful (or above unless fixed)
     * Install ntp and check demsg for denies
     * Once an issue triggers instead of the error in syslog you'll see the
   apparmor Deny like:
     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
     disconnected path" error=-13 profile="/usr/sbin/ntpd"
     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
     requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  [Regression Potential]

   * We are slightly opening up the apparmor profile which is far lower risk
     than adding more constraints. So safe from that POV.

   * OTOH one could think this might be a security issue, but in fact this
     isn't a new suggestion if you take a look at [1] with an ack by Seth of
     the Security Team.

  [Other Info]

   * n/a

  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html

  

  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+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 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix Released
Status in openntpd package in Ubuntu:
  Confirmed
Status in ntp source package in Xenial:
  Invalid
Status in openntpd source package in Xenial:
  Confirmed
Status in ntp source package in Zesty:
  Invalid
Status in openntpd source package in Zesty:
  Confirmed
Status in ntp source package in Artful:
  Fix Released
Status in openntpd source package in Artful:
  Confirmed
Status in ntp source package in Bionic:
  Fix Released
Status in openntpd source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * NTP has new isolation features which makes it trigger apparmor issues.
   * Those apparmor issues not only clutter the log and make other things
     less readable, they also prevent ntp from reporting its actual
     messages.
   * Fix is opening the apparmor profile to follow ntp through the
     disconnect by the isolation feature.

  [Test Case]

   * This is hard to trigger, but then also not. Which means it is not
     entirely sorted out when it triggers and when not, but the following
     does trigger it in tests of Pitti and also mine (while at the same time
     sometimes it does not - mabye I had other guests or kvm instead of lxd)

   * First install ntp in Artful (or above unless fixed)
     * Install ntp and check demsg for denies
     * Once an issue triggers instead of the error in syslog you'll see the
   apparmor Deny like:
     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
     disconnected path" error=-13 profile="/usr/sbin/ntpd"
     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
     requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  [Regression Potential]

   * We are slightly opening up the apparmor profile which is far lower risk
     than adding more constraints. So safe from that POV.

   * OTOH one could think this might be a security issue, but in fact this
     isn't a new suggestion if you take a look at [1] with an ack by Seth of
     the Security Team.

  [Other Info]

   * n/a

  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html

  

  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+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 1827354] Re: Ubuntu 18.04 Desktop reports error on startup

[Daniel van Vugt]

When you get the "error" dialog that means something crashed, so...

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

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

Title:
  Ubuntu 18.04 Desktop reports error on startup

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  david@david-OptiPlex-9010:~$ sudo lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS

  david@david-OptiPlex-9010:~$ sudo apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:11.1-1ubuntu7.2
Candidate: 1:11.1-1ubuntu7.2
Version table:
   *** 1:11.1-1ubuntu7.2 500
  500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7 500
  500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Error Log:
  [pulseaudio] bluez5-util.c: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

  david@david-OptiPlex-9010:~$ pulseaudio --version
  pulseaudio 11.1

  david@david-OptiPlex-9010:~$ pulseaudio --dump-conf
  ### Read from configuration file: /etc/pulse/daemon.conf ###
  daemonize = no
  fail = yes
  high-priority = yes
  nice-level = -11
  realtime-scheduling = yes
  realtime-priority = 5
  allow-module-loading = yes
  allow-exit = yes
  use-pid-file = yes
  system-instance = no
  local-server-type = user
  cpu-limit = no
  enable-shm = yes
  flat-volumes = no
  lock-memory = no
  exit-idle-time = 20
  scache-idle-time = 20
  dl-search-path = /usr/lib/pulse-11.1/modules
  default-script-file = /etc/pulse/default.pa
  load-default-script-file = yes
  log-target = 
  log-level = notice
  resample-method = auto
  avoid-resampling = yes
  enable-remixing = yes
  remixing-use-all-sink-channels = yes
  enable-lfe-remixing = no
  lfe-crossover-freq = 0
  default-sample-format = s16le
  default-sample-rate = 44100
  alternate-sample-rate = 48000
  default-sample-channels = 2
  default-channel-map = front-left,front-right
  default-fragments = 4
  default-fragment-size-msec = 25
  enable-deferred-volume = yes
  deferred-volume-safety-margin-usec = 1
  deferred-volume-extra-delay-usec = 0
  shm-size-bytes = 0
  log-meta = no
  log-time = no
  log-backtrace = 0
  rlimit-fsize = -1
  rlimit-data = -1
  rlimit-stack = -1
  rlimit-core = -1
  rlimit-rss = -1
  rlimit-as = -1
  rlimit-nproc = -1
  rlimit-nofile = 256
  rlimit-memlock = -1
  rlimit-locks = -1
  rlimit-sigpending = -1
  rlimit-msgqueue = -1
  rlimit-nice = 31
  rlimit-rtprio = 9
  rlimit-rttime = 20

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  2194 F pulseaudio
   /dev/snd/controlC0:  david  2194 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 20:08:51 2019
  InstallationDate: Installed on 2019-04-28 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 0KV62T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0KV62T:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Bug Watch Updater]

** Changed in: nextcloud-snap
   Status: Unknown => Fix Released

** Changed in: nextcloud-snap
   Importance: High => Unknown

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Fix Released
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  [SRU Justification]
  Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.

  [Test case]
  1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
  2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
  2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
  3. Install the iputils-ping package.
  4. ping www.freedesktop.org
  5. Confirm that the hostname does not resolve.
  6. Install the systemd package from yakkety-proposed onto the host system.
  7. ping www.freedesktop.org
  8. Confirm that the hostname does now resolve.

  [Regression potential]
  With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.

  
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 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
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+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 1827172] Re: update-rc.d: enabling or disabling S runlevel services incorrectly modifies runlevel

[Matthew Ruffell]

** Tags added: sts-sponsor

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

Title:
  update-rc.d: enabling or disabling S runlevel services incorrectly
  modifies runlevel

Status in sysvinit package in Ubuntu:
  New
Status in sysvinit source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * update-rc.d, in sysv-rc-2.88dsf-41ubuntu6.3 is broken in trusty.

   * update-rc.d incorrectly modifies symlinks when enabling or disabling
     services which are started on the "S" runlevel.

   * This can lead to services being changed from S runlevel from where they
     would be started on boot, to "0" runlevel, and are run on halt, which is
     incorrect.

   * The bug is caused by trying to use the runlevel to index into an integer
     array of runlevels. When the runlevel in question is "S", an error is
     printed

     Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line
     232.

     Perl then sets the index to default to 0, which changes the
  runlevel.

   * The fix is to check if the runlevel is "S", and if it is, set the index to
     99 which conforms with other expected usages for the "S" runlevel in the
     script. See the "startstop" and "makelinks" subroutines.

  [Test Case]

  * You can reproduce this with any service that is started on the "S"
    runlevel. We will use open-iscsi for an example.

  1) Install open-iscsi

  $ sudo apt install open-iscsi

  2) Check to see symlinks for init.d scripts are set to defaults:

  root@trusty-openiscsi:/etc# ls -l /etc/rc[0123456S].d/*iscsi*
  /etc/rc0.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
  /etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc1.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
  /etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc6.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
  /etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rcS.d/S45open-iscsi -> ../init.d/open-iscsi

  3) Use update-rc.d to enable open-iscsi service

  root@trusty-openiscsi:/etc# update-rc.d open-iscsi enable
  update-rc.d: warning: start runlevel arguments (none) do not match open-iscsi 
Default-Start values (S)
  update-rc.d: warning: stop runlevel arguments (none) do not match open-iscsi 
Default-Stop values (0 1 6)
  Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line 232.
  Enabling system startup links for /etc/init.d/open-iscsi ...
  Removing any system startup links for /etc/init.d/open-iscsi ...
  /etc/rc0.d/K81open-iscsi
  /etc/rc1.d/K81open-iscsi
  /etc/rc6.d/K81open-iscsi
  /etc/rcS.d/S45open-iscsi
  Adding system startup for /etc/init.d/open-iscsi ...
  /etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc0.d/S45open-iscsi -> ../init.d/open-iscsi

  * The problem is the "/etc/rcS.d/S45open-iscsi" symlink is incorrectly
    changed to "/etc/rc0.d/S45open-iscsi".

  * Instead, the correct behaviour is to keep the symlink in /etc/rcS.d/
    intact:

  root@trusty-openiscsi:/etc# update-rc.d open-iscsi enable
  update-rc.d: warning: start runlevel arguments (none) do not match open-iscsi 
Default-Start values (S)
  update-rc.d: warning: stop runlevel arguments (none) do not match open-iscsi 
Default-Stop values (0 1 6)
  Enabling system startup links for /etc/init.d/open-iscsi ...
  Removing any system startup links for /etc/init.d/open-iscsi ...
  /etc/rc0.d/K81open-iscsi
  /etc/rc1.d/K81open-iscsi
  /etc/rc6.d/K81open-iscsi
  /etc/rcS.d/S45open-iscsi
  Adding system startup for /etc/init.d/open-iscsi ...
  /etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rcS.d/S45open-iscsi -> ../init.d/open-iscsi

  [Regression Potential]

   * There is only one file modified, which is the update-rc.d perl script.
     Worst case scenario is that users cannot enable or disable their services,
     or a symlink is changed such that a service is started / stopped on an
     incorrect runlevel.

   * If a regression happens, any damage should be easily spotted by a
     sysadmin and can be manually repaired by making manual symlinks with
     "ln -s".

   * I have built and tested the change in a PPA, which you can find here:
 https://launchpad.net/~mruffell/+archive/ubuntu/sysvinit-testing

   * My only cause for concern is that if a regression does happen, it may 
 impact packages that run "update-rc.d  [en|dis]able" in a 
 postinstall module, although I haven't managed to find an example that
 does this, since most use the "defaults" command instead.

  [Other Info]

   * trusty is the last Ubuntu release to use sysvinit, and this bug is not
     present in newer versions since they use systemd, and the code in question

[Touch-packages] [Bug 1827440] [NEW] [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted

[Tyler Singer-Clark]

Public bug reported:

Hopefully all the necessary info is in the extra stuff that
automatically got sent.

Basically, I didn't do anything fancy, but audio recorded with my
microphone (through Skype, and arecord in the Terminal) has tons of
static and the voice is distorted or saturated.

Booting this computer on Windows doesn't have issues, so that's why I
don't think it's the computer, I think it's the OS.

Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tyler  1499 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu May  2 19:04:55 2019
InstallationDate: Installed on 2019-01-09 (113 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Mic, Internal
Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET62W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHS1TG00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KHS1TG00
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic

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

Title:
  [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Touch-packages] [Bug 1827428] Re: Mouse cursor left freezed copy of itself

[Andrei Sonin]

> What desktop environment do you use?

GNOME. From the latest Ubuntu release (19.04).

> Screenshot.

I tried to capture it by screenshot. But freezed cursor is not shown on
it. So I attach a photo. Freezed cursor is on the bottom left.

** Attachment added: "VrAmb8UYn0o.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827428/+attachment/5261036/+files/VrAmb8UYn0o.jpg

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

Title:
  Mouse cursor left freezed copy of itself

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Mouse cursor left freezed copy of itself over all the windows after
  login after lock screen. Functionality is not broken. It's just not
  aesthetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 16:10:09 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] 
[103c:8392]
  InstallationDate: Installed on 2019-04-29 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop 17-an0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8392
  dmi.board.vendor: HP
  dmi.board.version: 40.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-an0xx
  dmi.product.sku: 2FP35EA#ACB
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827428/+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 1827428] Re: Mouse cursor left freezed copy of itself

[Sebastien Bacher]

Thank you for your bug report. What desktop environment do you use?
Could you take a screenshot or screencast showing the issue?

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

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

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

Title:
  Mouse cursor left freezed copy of itself

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Mouse cursor left freezed copy of itself over all the windows after
  login after lock screen. Functionality is not broken. It's just not
  aesthetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 16:10:09 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] 
[103c:8392]
  InstallationDate: Installed on 2019-04-29 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop 17-an0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8392
  dmi.board.vendor: HP
  dmi.board.version: 40.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-an0xx
  dmi.product.sku: 2FP35EA#ACB
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827428/+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 1827427] Re: DHCP IP not obtainable if booting into Linux from suspended/hibernated/rebooted Windows

[Sebastien Bacher]

Thank you for your bug report. It does look like rather an
hardware/driver/kernel issue than a network-manager one though,
reassigning

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

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

Title:
  DHCP IP not obtainable if booting into Linux from
  suspended/hibernated/rebooted Windows

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce: boot into Windows, obtain DHCP IP. either
  hibernate PC or reboot then boot into Linux; a DHCP IP is not
  obtainable even if I power cycle my router.

  To obtain a DHCP IP in Linux on the PC, I must either fully shutdown
  Windows then cold boot into Linux, or manually reset the ethernet
  adapter with

  echo 1 > /sys/bus/pci/devices/:00:19.0/reset

  The connection then comes good.

  
  I can see various DHCPDISCOVER and network-related traffic in journalctl -f 
during the time the machine is attempting to set an address on the interface, 
periodically the "activation of network connection failed" error message 
displays.

  Other discussion online suggests setting a spoofed, different MAC on
  the interface

  I am using Ubuntu 19 and Mint Cinnamon 19.1 to test and can reproduce
  this over multiple boots. It has apparently been a longstanding bug,
  perhaps due to how Windows is setting some aspect of the ethernet
  controller for a WOL or other boot-related operation. Either way, it's
  entirely confusing. Perhaps resetting the adapter should occur if this
  situation arises, particularly in LiveUSB/LiveCD scenarios.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.16.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CasperVersion: 1.405
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 22:06:00 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE  FILENAME 
   lan1  cbe6c8b2-dab9-347f-8a1d-613294b87483  ethernet  1556833444  Thu May  2 
21:44:04 2019  yes  -999  no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
-- /etc/NetworkManager/system-connections/lan1.nmconnection
  nmcli-dev:
   DEVICE  TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID  CON-PATH 
   eno1ethernet  disconnected  limited   limited   
/org/freedesktop/NetworkManager/Devices/2  --  ----   
   lo  loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  ----
  nmcli-nm:
   RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.16.0   disconnected  started  limited   enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827427/+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 1827430] [NEW] detect 4k screen and adapt font size

[wolnosc]

Public bug reported:

By default font in TTY is very too small on 4K resolution screen,
especially on laptop.

It would be better to detect 4K and change font automatically by
Uni*-Terminus32x16 for instance.

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  detect 4k screen and adapt font size

Status in console-setup package in Ubuntu:
  New

Bug description:
  By default font in TTY is very too small on 4K resolution screen,
  especially on laptop.

  It would be better to detect 4K and change font automatically by
  Uni*-Terminus32x16 for instance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1827430/+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 1763100] Re: FONT="x/y/z" is not applied due to setupcon script bug

[wolnosc]

I confirm the bug also on Ubuntu 19.04. 
Patch on post #3 resolve the problem.

Nowadays on laptop we have more and more 4K screen, the default font in
TTY framebuffer is very too small. For people who have Xorg no starting,
TTY is unique path to fix configuration.

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

Title:
  FONT="x/y/z" is not applied due to setupcon script bug

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  apt-cache policy console-setup
  console-setup:
Installed: 1.178ubuntu1
Candidate: 1.178ubuntu1
Version table:
   *** 1.178ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  On 18.04 I wanted to set the TTY font to use a Powerline font. Despite
  being able to set the font manually it wasn't being set at boot-time.

  /etc/default/console-setup contains:

  FONT="/usr/local/share/fonts/ter-powerline-v22n.psf.gz"

  "setupcon -v -f" reported an error:

  putfont: KDFONTOP: Invalid argument

  due to passing the font filename twice:

  executing setfont -C /dev/tty1 /usr/local/share/fonts/ter-powerline-
  v22n.psf.gz /usr/local/share/fonts/ter-powerline-v22n.psf.gz.

  The problem is in /bin/setupcon where the collecting variable
  FONTFILES has the font added twice, once at the top of the for loop

  FONTFILES="$FONTFILES `findfile $fontdir $f`"

  and again at the bottom

  FONTFILES="$FONTFILES $RES"

  Removing the first assignment fixes it.

  FONTFILES=''
  echo "DEBUG: FONT=$FONT"
  if [ "$FONT" ]; then
  for f in $FONT; do
echo "DEBUG: for loop"
  FONTFILES="$FONTFILES `findfile $fontdir $f`"
  RES=`findfile $fontdir $f`
  if [ -z "$RES" ]; then
  fdec="${f%.gz}"
  RES=`findfile $fontdir $fdec`
  fi
  FONTFILES="$FONTFILES $RES"
  done
  fi
  FONTFILES=`echo $FONTFILES` # remove extra spaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1763100/+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 1827427] [NEW] DHCP IP not obtainable if booting into Linux from suspended/hibernated/rebooted Windows

[Christopher Woods]

Public bug reported:

Steps to reproduce: boot into Windows, obtain DHCP IP. either hibernate
PC or reboot then boot into Linux; a DHCP IP is not obtainable even if I
power cycle my router.

To obtain a DHCP IP in Linux on the PC, I must either fully shutdown
Windows then cold boot into Linux, or manually reset the ethernet
adapter with

echo 1 > /sys/bus/pci/devices/:00:19.0/reset

The connection then comes good.


I can see various DHCPDISCOVER and network-related traffic in journalctl -f 
during the time the machine is attempting to set an address on the interface, 
periodically the "activation of network connection failed" error message 
displays.

Other discussion online suggests setting a spoofed, different MAC on the
interface

I am using Ubuntu 19 and Mint Cinnamon 19.1 to test and can reproduce
this over multiple boots. It has apparently been a longstanding bug,
perhaps due to how Windows is setting some aspect of the ethernet
controller for a WOL or other boot-related operation. Either way, it's
entirely confusing. Perhaps resetting the adapter should occur if this
situation arises, particularly in LiveUSB/LiveCD scenarios.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: network-manager 1.16.0-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.405
CurrentDesktop: ubuntu:GNOME
Date: Thu May  2 22:06:00 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 
IwConfig:
 lono wireless extensions.
 
 eno1  no wireless extensions.
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE  FILENAME 
 lan1  cbe6c8b2-dab9-347f-8a1d-613294b87483  ethernet  1556833444  Thu May  2 
21:44:04 2019  yes  -999  no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
-- /etc/NetworkManager/system-connections/lan1.nmconnection
nmcli-dev:
 DEVICE  TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
 eno1ethernet  disconnected  limited   limited   
/org/freedesktop/NetworkManager/Devices/2  --  ----   
 lo  loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  ----
nmcli-nm:
 RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
 running  1.16.0   disconnected  started  limited   enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug disco

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

Title:
  DHCP IP not obtainable if booting into Linux from
  suspended/hibernated/rebooted Windows

Status in network-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce: boot into Windows, obtain DHCP IP. either
  hibernate PC or reboot then boot into Linux; a DHCP IP is not
  obtainable even if I power cycle my router.

  To obtain a DHCP IP in Linux on the PC, I must either fully shutdown
  Windows then cold boot into Linux, or manually reset the ethernet
  adapter with

  echo 1 > /sys/bus/pci/devices/:00:19.0/reset

  The connection then comes good.

  
  I can see various DHCPDISCOVER and network-related traffic in journalctl -f 
during the time the machine is attempting to set an address on the interface, 
periodically the "activation of network connection failed" error message 
displays.

  Other discussion online suggests setting a spoofed, different MAC on
  the interface

  I am using Ubuntu 19 and Mint Cinnamon 19.1 to test and can reproduce
  this over multiple boots. It has apparently been a longstanding bug,
  perhaps due to how Windows is setting some aspect of the ethernet
  controller for a WOL or other boot-related operation. Either way, it's
  entirely confusing. Perhaps resetting the adapter should occur if this
  situation arises, particularly in LiveUSB/LiveCD scenarios.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: 

[Touch-packages] [Bug 520546] Update Released

[Steve Langasek]

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

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

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

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Confirmed
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  In Progress
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

 On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 
script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode 
to observe the change:
 $  sudo kbd_mode -s -C /dev/tty1
 $ sudo kbd_mode -C /dev/tty1
 The keyboard is in raw (scancode) mode

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you want to update it now, run 'setupcon' from a virtual console.
     ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same (on Xenial check VT1: sudo kbd_mode -C
  /dev/tty1):

     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * The unfixed package sets the kbd mode to unicode:

     $  sudo kbd_mode
     The keyboard is in Unicode (UTF-8) mode
     $

  [Regression Potential]

   * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
   * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.

  [Original Bug Text]
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions

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

[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Launchpad Bug Tracker]

This bug was fixed in the package console-setup - 1.178ubuntu12.1

---
console-setup (1.178ubuntu12.1) disco; urgency=medium

  * Call setupcon --force only when debian-installer is active
and always redirect output to /dev/null to not block. (LP: #520546)

 -- Balint Reczey   Tue, 23 Apr 2019 13:45:00 +0200

** Changed in: console-setup (Ubuntu Disco)
   Status: Fix Committed => Fix Released

** Changed in: console-setup (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

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

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Confirmed
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  In Progress
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

 On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 
script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode 
to observe the change:
 $  sudo kbd_mode -s -C /dev/tty1
 $ sudo kbd_mode -C /dev/tty1
 The keyboard is in raw (scancode) mode

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you want to update it now, run 'setupcon' from a virtual console.
     ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same (on Xenial check VT1: sudo kbd_mode -C
  /dev/tty1):

     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * The unfixed package sets the kbd mode to unicode:

     $  sudo kbd_mode
     The keyboard is in Unicode (UTF-8) mode
     $

  [Regression Potential]

   * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
   * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.

  [Original Bug Text]
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions

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

[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Launchpad Bug Tracker]

This bug was fixed in the package console-setup - 1.178ubuntu2.9

---
console-setup (1.178ubuntu2.9) bionic; urgency=medium

  * Call setupcon --force only when debian-installer is active
and always redirect output to /dev/null to not block. (LP: #520546)

 -- Balint Reczey   Tue, 23 Apr 2019 14:04:14 +0200

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

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

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Confirmed
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  In Progress
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

 On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 
script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode 
to observe the change:
 $  sudo kbd_mode -s -C /dev/tty1
 $ sudo kbd_mode -C /dev/tty1
 The keyboard is in raw (scancode) mode

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you want to update it now, run 'setupcon' from a virtual console.
     ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same (on Xenial check VT1: sudo kbd_mode -C
  /dev/tty1):

     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * The unfixed package sets the kbd mode to unicode:

     $  sudo kbd_mode
     The keyboard is in Unicode (UTF-8) mode
     $

  [Regression Potential]

   * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
   * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.

  [Original Bug Text]
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions

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

[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Launchpad Bug Tracker]

This bug was fixed in the package console-setup - 1.178ubuntu9.2

---
console-setup (1.178ubuntu9.2) cosmic; urgency=medium

  * Call setupcon --force only when debian-installer is active
and always redirect output to /dev/null to not block. (LP: #520546)

 -- Balint Reczey   Tue, 23 Apr 2019 13:55:23 +0200

** Changed in: console-setup (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

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

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Confirmed
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  In Progress
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

 On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 
script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode 
to observe the change:
 $  sudo kbd_mode -s -C /dev/tty1
 $ sudo kbd_mode -C /dev/tty1
 The keyboard is in raw (scancode) mode

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you want to update it now, run 'setupcon' from a virtual console.
     ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same (on Xenial check VT1: sudo kbd_mode -C
  /dev/tty1):

     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * The unfixed package sets the kbd mode to unicode:

     $  sudo kbd_mode
     The keyboard is in Unicode (UTF-8) mode
     $

  [Regression Potential]

   * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
   * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.

  [Original Bug Text]
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions

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

[Touch-packages] [Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed

[Malte Hellmeier]

Exact same problem here with Ubuntu 18.04 and kernel Linux
4.18.0-16-generic.

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

Title:
  Kernel 4.9+ regression: Suspend - Freezing of tasks failed

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu
  Gnome 17.04 and since then sometimes my Laptop won't suspend when I
  close the lid. The power led does not blink like it is supposed to do
  and when I open the Laptop the lockscreen appears but freezes after a
  short time, followed by a blackscreen until eventually it reappears
  and allows me to unlock it. After that certain application can not be
  started anymore and would freeze if they were running before. These
  include Chrome, Gedit and Gnome System Monitor for example. Also my
  Laptop will not connect to my WLAN until I restart it.

  In syslog I found the line:

  "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to
  freeze, wq_busy=0):"

  According to syslog

  network-nanaeger
  whoopsie
  cups-browsed
  wpa-supplicant
  geoclue
  packagekitd
  several evolution-related processes
  goa-daemon
  gnome-software
  geary
  dropbox
  deja-dup-monitor

  are responsible.
  I tried disabling some of them, but it did not solve the problem.

  Update: I tested different Kernel versions in the last days. So far
  there were no issues with suspend/resume using Kernel 4.8 and 4.9. The
  problem is present in 4.10 and 4.11.

  Update 2: I just encountered this issue with Kernel 4.9.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 28 16:27:34 2017
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80J8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B8CN31WW(V2.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paganini
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 3 11
  dmi.modalias: 
dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311:
  dmi.product.name: 80J8
  dmi.product.version: Lenovo Yoga 3 11
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+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 1827417] [NEW] Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.

[Tomasz Grabarczyk]

Public bug reported:

Hello,

I have a problem - after one of the updates (sorry for being not precise - I 
can only track it back to the time I have been surely listening something on 
headphones - it has to be beginning of this year because last time I have been 
listening more on my SB Live for sure was in last one-two weeks of February 
2019 - I have suddenly lost "stereo" on my headphones.
I have speakers connected to on-board sound card and headphones connected to SB 
Live Value for few years, so I did not mess with outputs or something - one day 
I changed Audacious output to SbLive in pavucontrol (as usually) and that time 
the sound was weirdly filtered.
I have found that this must be "surround upmix" which I do not need and tried 
to disable it,
enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf 
did not work.
It does not matter what configuration I choose in pavucontrol- analog stereo 
duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog 
output" scenarios the output is the same except for "mono" (no sound at all).
I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the 
alsa configuration for stereo but the upmix is still present.

I have followed the old thread in Launchpad Answers:
https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428
=
Hello,

i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last 
update I have similar problem - I have lost ability to listen stereo music on 
my Soundblaster Live Value (i use earphones).
Even system sounds , web browser content and mp3 files are up-mixed.
Few days ago it was no problem to choose "analag stereo output" in pavucontrol, 
now it seems that at this output have rear surround channel only (as I suppose, 
there is "stereo" but vocals are like heard from the other room and there is 
sometimes reverb as in the bathroom) :/.
I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and 
in the home directory configuration file without success.
I have purged pulseaudio but with the ALSA there is the same problem, I have 
tried purging alsa and reinstalling without effect.
So i thought that it can be emu10k1 driver specific, after digging in the 
network for solutions I have had tried adding 
"hint.emu10kx.0.multichannel_disabled " to the module configuration file 
without visible (or rather soundible ;) effect.
I have tried to check EMU10K1 configuration with aweset, but it gives error 
message, so maybe the bad magic sits somewhere around?

aweset
/dev/sequencer: No such file or directory

Once again - everything worked fine until the last update. I use xubuntu
desktop as my machine is quite old, in despair I have installed unity to
find the sound settings / speaker configuration etc and button to
"disable all effects" as I have seen somewhere, but there were no such
options.

Help me Obi Wan Kenobi, you're my only hope...
=

I have next tried to follow the path from ubuntu sound troubleshooting
guide, I have purged everything, installed back and now I'm  here again
with this "upmix" on SBLive! Value.

Thanks in advance for help :)
Tom

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


** Tags: aoudio emu10k1 sblive stereo upmix

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

Title:
  Ubuntu 16.04 -  EMU10K1 / CT4832 lost ability to listen stereo on
  headphones -  there is upmixed  surround only.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hello,

  I have a problem - after one of the updates (sorry for being not precise - I 
can only track it back to the time I have been surely listening something on 
headphones - it has to be beginning of this year because last time I have been 
listening more on my SB Live for sure was in last one-two weeks of February 
2019 - I have suddenly lost "stereo" on my headphones.
  I have speakers connected to on-board sound card and headphones connected to 
SB Live Value for few years, so I did not mess with outputs or something - one 
day I changed Audacious output to SbLive in pavucontrol (as usually) and that 
time the sound was weirdly filtered.
  I have found that this must be "surround upmix" which I do not need and tried 
to disable it,
  enable-remixing = no and the same for "LFE remixing" in 
/etc/pulse/daemon.conf did not work.
  It does not matter what configuration I choose in pavucontrol- analog stereo 
duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog 
output" scenarios the output is the same except for "mono" (no sound at all).
  I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the 
alsa configuration for stereo but the upmix is 

[Touch-packages] [Bug 1760308] Re: Unicode input not working on Bionic with CTRL-SHIFT-U

[Bug Watch Updater]

** Changed in: ibus
   Status: Unknown => Fix Released

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

Title:
  Unicode input not working on Bionic with CTRL-SHIFT-U

Status in ibus:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus source package in Bionic:
  Fix Released

Bug description:
  I need to enter Unicode with Unicode escape codes and the Ubuntu
  prescribed way is to use CTRL-SHIFT-U and then enter some numbers to
  input.  This doesn't do anything in the Ubuntu Bionic beta.

  Potentially related the ALT-TAB window switching is delayed in
  recognizing the occurrence of the keys being pressed such that I have
  to hold ALT-TAB instead of quickly hitting both simultaneously.

  This is from a system that was upgraded from a previous Ubuntu version
  without any issues.

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  The "Affects" package may not be accurate as I don't know what the
  cause application is for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1760308/+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 1825997] Re: boot-smoke fails due to running jobs

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/366857

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

Title:
  boot-smoke fails due to running jobs

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [impact]

  boot-smoke test reboots 5 times and verifies systemd is fully started
  up after each boot, including checking if there are any running jobs
  (with list-jobs).  However, this test makes the assumption that no
  further jobs will be started after systemd reaches 'running' (or
  'degraded') state, which is a false assumption.

  [test case]

  see various boot-smoke failures in autopkgtest.ubuntu.com

  [regression potential]

  possible false-positive or false-negative autopkgtest results.

  [other info]

  The problem appears to be that systemd reaches 'running' (or
  'degraded') state, and then other systemd services are started.  This
  confuses the boot-smoke test, because it sees that 'is-system-running'
  is done, but then it sees running jobs, which fails the test.

  What is starting jobs after systemd reaches running state appears to
  be X inside the test system.  There are various services started by
  gnome-session and dbus-daemon.  Additionally, from the artifacts of
  one example:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  bionic/bionic/i386/s/systemd/20190416_171327_478f6@/artifacts.tar.gz

  the artifacts/journal.txt shows that after the boot-smoke test causes
  the reboot and then re-ssh into the system after the reboot, it only
  gives the test system 9 seconds before deciding it has failed, and
  only 4 seconds after ssh'ing into the rebooted test system.

  Another wait is needed when checking for remaining running jobs.  Or,
  the running jobs check could be removed entirely, and we can just
  trust that systemd correctly knows when it has reached
  running|degraded state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825997/+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 1825997] Re: boot-smoke fails due to running jobs

[Dan Streetman]

** Changed in: systemd (Ubuntu Eoan)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

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

Title:
  boot-smoke fails due to running jobs

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [impact]

  boot-smoke test reboots 5 times and verifies systemd is fully started
  up after each boot, including checking if there are any running jobs
  (with list-jobs).  However, this test makes the assumption that no
  further jobs will be started after systemd reaches 'running' (or
  'degraded') state, which is a false assumption.

  [test case]

  see various boot-smoke failures in autopkgtest.ubuntu.com

  [regression potential]

  possible false-positive or false-negative autopkgtest results.

  [other info]

  The problem appears to be that systemd reaches 'running' (or
  'degraded') state, and then other systemd services are started.  This
  confuses the boot-smoke test, because it sees that 'is-system-running'
  is done, but then it sees running jobs, which fails the test.

  What is starting jobs after systemd reaches running state appears to
  be X inside the test system.  There are various services started by
  gnome-session and dbus-daemon.  Additionally, from the artifacts of
  one example:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  bionic/bionic/i386/s/systemd/20190416_171327_478f6@/artifacts.tar.gz

  the artifacts/journal.txt shows that after the boot-smoke test causes
  the reboot and then re-ssh into the system after the reboot, it only
  gives the test system 9 seconds before deciding it has failed, and
  only 4 seconds after ssh'ing into the rebooted test system.

  Another wait is needed when checking for remaining running jobs.  Or,
  the running jobs check could be removed entirely, and we can just
  trust that systemd correctly knows when it has reached
  running|degraded state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825997/+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 1827286] Re: autofs - "Too many levels of symbolic links" after apt upgrade

[Jason D. Kelleher]

Looks like the issue is symlinking to a director prior to autofs
mounting it.

Everything fine...

root@numbersix:/# ssh chi uname -a
Linux chi 4.4.0-146-generic #172-Ubuntu SMP Wed Apr 3 09:00:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
root@chi:~# ls -la /home
ls: cannot access '/home': No such file or directory
root@chi:~#
root@numbersix:/# ssh chi 'ls -la /vol/*'
/vol/home:
total 8
drwxr-xr-x 1 root root  154 Apr 21 19:10 .
drwxr-xr-x 5 root root 4096 Jul  2  2018 ..
drwxr-xr-x 1 2005 2005 1070 Nov 17  2015 bethann
[trimmed]

/vol/media:
total 4
drwxr-xr-x 1 root root  128 Apr 13 18:29 .
drwxr-xr-x 5 root root 4096 Jul  2  2018 ..
[trimmed]

/vol/zhora-temp:
total 24
dr-xr-xr-x  6 root root 4096 Mar  3 08:21 .
drwxr-xr-x  5 root root 4096 Jul  2  2018 ..
[trimmed]
root@numbersix:/#


Everything works fine if the link is made after...

root@chi:/# ln -s /vol/home
root@chi:/# ls -la /home
lrwxrwxrwx 1 root root 9 May  2 12:11 /home -> /vol/home
root@chi:/#
root@chi:/# ls -la /vol/*
/vol/home:
total 8
drwxr-xr-x 1 root root  154 Apr 21 19:10 .
drwxr-xr-x 5 root root 4096 Jul  2  2018 ..
[trimmed]

/vol/media:
total 4
drwxr-xr-x 1 root root  128 Apr 13 18:29 .
drwxr-xr-x 5 root root 4096 Jul  2  2018 ..
[trimmed]

/vol/zhora-temp:
total 24
dr-xr-xr-x  6 root root 4096 Mar  3 08:21 .
drwxr-xr-x  5 root root 4096 Jul  2  2018 ..
[trimmed]
root@chi:/#

It breaks after the reboot...

root@chi:/# init 6
Connection to chi closed by remote host.
Connection to chi closed.
root@numbersix:~# root@chi:/# init 6
Connection to chi closed by remote host.
Connection to chi closed.
root@numbersix:~#

root@numbersix:~#
root@numbersix:~# ssh chi
Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-146-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

21 packages can be updated.
15 updates are security updates.

New release '18.04.2 LTS' available.
Run 'do-release-upgrade' to upgrade to it.


root@chi:~# ls -la /vol/*
ls: cannot open directory '/vol/home': Too many levels of symbolic links
/vol/media:
total 4
drwxr-xr-x 1 root root  128 Apr 13 18:29 .
drwxr-xr-x 5 root root 4096 Jul  2  2018 ..
[trimmed]

/vol/zhora-temp:
total 24
dr-xr-xr-x  6 root root 4096 Mar  3 08:21 .
drwxr-xr-x  5 root root 4096 Jul  2  2018 ..
[trimmed]
root@chi:~#


At this point, the link needs to be deleted and the VM rebooted to get back to 
a normal state - just restarting autofs won't clear it.


** Package changed: systemd (Ubuntu) => autofs5 (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/1827286

Title:
  autofs  - "Too many levels of symbolic links" after apt upgrade

Status in autofs5 package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  I moved to autofs this week as a workaround for Bug #1577575 failing
  to mount NFS entries at boot. This worked file until I ran 'apt
  upgrade' today.

  Now trying to access /vol/home mount results in the following error:

  root@chi:~# ls -la /vol/home/
  ls: cannot access '/vol/home/': Too many levels of symbolic links
  root@chi:~# 

  Oddly enough, the other two autofs entries work fine (output trimmed):
  root@chi:~# ls -la /vol/media
  total 4
  ...
  root@chi:~# 
  root@chi:~# ls -al /vol/temp/
  total 24
  ...
  root@chi:~# 

  
  I have a scratch VM I can break tonight by performing upgrades individually 
and testing after each.  Will provide that detail when available.

  
  Here is /var/log/apt/history.log

   Start-Date: 2019-05-01  17:37:00
  Commandline: apt upgrade
  Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 
1:9.10.3.dfsg.P4-8ubuntu1.14), libisccfg140:amd64 
(1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), ureadahead:amd64 
(0.100.0-19, 0.100.0-19.1), libldap-2.4-2:amd64 (2.4.42+dfsg-2ubuntu3.4, 
2.4.42+dfsg-2ubuntu3.5), libirs141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 
1:9.10.3.dfsg.P4-8ubuntu1.14), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 
1:9.10.3.dfsg.P4-8ubuntu1.14), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 
1:9.10.3.dfsg.P4-8ubuntu1.14), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 
1:9.10.3.dfsg.P4-8ubuntu1.14), passwd:amd64 (1:4.2-3.1ubuntu5.3, 
1:4.2-3.1ubuntu5.4), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12, 
1:9.10.3.dfsg.P4-8ubuntu1.14), libisc-export160:amd64 
(1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), liblwres141:amd64 
(1:9.10.3.dfsg.P4-8ubuntu1.12, 1:9.10.3.dfsg.P4-8ubuntu1.14), login:amd64 
(1:4.2-3.1ubuntu5.3, 1:4.2-3.1ubuntu5.4), iproute2:amd64 
(4.3.0-1ubuntu3.16.04.4, 4.3.0-1ubuntu3.16.04.5), bind9:amd64 
(1:9.10.3.dfsg.P4-8ubuntu1.12, 

[Touch-packages] [Bug 1824341] Re: NoAllowedOrigin cause package removal

[Anderson Luiz Alves]

unattended-upgrades=1.5ubuntu3.18.10.4 works on cosmic

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

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

Title:
  NoAllowedOrigin cause package removal

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Cosmic:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * When applying a minimal upgrade set fails raising an exception
  unattended-upgrades stops trying to install further sets and may
  remove packages left marked to remove in the dirty set.

  [Test Case]

   * Set up unattended-upgrades to always remove autoremovable packages:

 $ echo 'Unattended-Upgrade::Remove-Unused-Dependencies "false";' | sudo 
tee /etc/apt/apt.conf.d/51unattended-upgrades-remove
   * Install a package and mark it as autoremovable

 $ sudo apt install hello
 $ sudo apt-mark auto hello

   * Set up the custom package to trigger the failure with the exception when 
applying the minimal sets in a way that leaves packages to remove in the dirty 
cache. If the reporter can reproduce the issue on all releases then that's 
great, otherwise I provide an example with equivs.

   * Check if u-u still crashes
$ sudo unattended-upgrades -d

  [Regression Potential]

   * The fix is catching the raised exceptions and trying to apply next minimal 
sets. In special circumstances this could fail again for all sets or could make 
systems's state worse if the installation is already broken. I can't come up 
with an example where it would make the system's state worse because when 
packages can't be safely installed Cache.commit() is expected to fail earlier, 
thust making the system's state worse seems unlikely.
   * OTOH when upgrading a set fails this would not block the installation of 
bigger sets anymore which is a big advantage of having this fix in u-u.

  [Original Bug Text]

  unattended-upgrades remove packages that shouldn't when there is a
  NoAllowedOrigin exception.

  Version:
  unattended-upgrades=1.1ubuntu1.18.04.10
  Ubuntu 18.04.2 LTS

  Description of problem:
  We have a internal package cliente-ldap that depends on samba, when u-u check 
for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't 
clear apt.cache and it removes packages that shouldn't.

  Log that happens package removal:
  $ sudo unattended-upgrade -d
  [...]
  Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules 
smbclient
  Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  debug: call_adjusted samba-common
  debug: marked_pkg: samba: install=False, upgrade=False, delete=True
  debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 257, in call_adjusted
  self.allowed_origins)
    File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin
  raise NoAllowedOriginError()
  NoAllowedOriginError
  debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
  debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True
  debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True
  Exception:
  marking samba-common-bin for removal
  Keeping auto-removable samba-common-bin package(s) because it would also 
remove the following packages which should be kept in this step: samba-common
  marking cliente-ldap for removal
  (Reading database ... 213413 files and directories currently installed.)
  Removing cliente-ldap (1:2.17.15) ...
  marking libcephfs2 for removal
  (Reading database ... 213392 files and directories currently installed.)
  Removing libcephfs2 (12.2.11-0ubuntu0.18.04.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  marking ldap-auth-config for removal
  (Reading database ... 213386 files and directories currently installed.)
  Removing libpam-ldap:amd64 (186-4ubuntu1) ...
  Removing ldap-auth-config (0.5.3) ...
  Removing ldap-auth-client (0.5.3) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking python-samba for removal
  (Reading database ... 213332 files and directories currently installed.)
  Removing samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing samba-common-bin (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing python-samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers 

[Touch-packages] [Bug 1827396] Re: package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Secure boot

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1 Secure boot

Status in rsyslog package in Ubuntu:
  New

Bug description:
  The Log said something about this system not supporting Secure Boot.

  The hardware is a iMac model A1224.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: rsyslog 8.16.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu May  2 11:52:55 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-05 (907 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: rsyslog
  Title: package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827396/+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 1827396] [NEW] package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Secure boot

[Ricardo Sendra]

Public bug reported:

The Log said something about this system not supporting Secure Boot.

The hardware is a iMac model A1224.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: rsyslog 8.16.0-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
Uname: Linux 4.4.0-145-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Thu May  2 11:52:55 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-11-05 (907 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: rsyslog
Title: package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1 Secure boot

Status in rsyslog package in Ubuntu:
  New

Bug description:
  The Log said something about this system not supporting Secure Boot.

  The hardware is a iMac model A1224.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: rsyslog 8.16.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu May  2 11:52:55 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-11-05 (907 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.31
  SourcePackage: rsyslog
  Title: package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827396/+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 1827354] Re: Ubuntu 18.04 Desktop reports error on startup

[Sebastien Bacher]

Thank you for your bug report. Where is that error reported. Could you
take a screenshot showing the issue?

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

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

Title:
  Ubuntu 18.04 Desktop reports error on startup

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  david@david-OptiPlex-9010:~$ sudo lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS

  david@david-OptiPlex-9010:~$ sudo apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:11.1-1ubuntu7.2
Candidate: 1:11.1-1ubuntu7.2
Version table:
   *** 1:11.1-1ubuntu7.2 500
  500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7 500
  500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Error Log:
  [pulseaudio] bluez5-util.c: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

  david@david-OptiPlex-9010:~$ pulseaudio --version
  pulseaudio 11.1

  david@david-OptiPlex-9010:~$ pulseaudio --dump-conf
  ### Read from configuration file: /etc/pulse/daemon.conf ###
  daemonize = no
  fail = yes
  high-priority = yes
  nice-level = -11
  realtime-scheduling = yes
  realtime-priority = 5
  allow-module-loading = yes
  allow-exit = yes
  use-pid-file = yes
  system-instance = no
  local-server-type = user
  cpu-limit = no
  enable-shm = yes
  flat-volumes = no
  lock-memory = no
  exit-idle-time = 20
  scache-idle-time = 20
  dl-search-path = /usr/lib/pulse-11.1/modules
  default-script-file = /etc/pulse/default.pa
  load-default-script-file = yes
  log-target = 
  log-level = notice
  resample-method = auto
  avoid-resampling = yes
  enable-remixing = yes
  remixing-use-all-sink-channels = yes
  enable-lfe-remixing = no
  lfe-crossover-freq = 0
  default-sample-format = s16le
  default-sample-rate = 44100
  alternate-sample-rate = 48000
  default-sample-channels = 2
  default-channel-map = front-left,front-right
  default-fragments = 4
  default-fragment-size-msec = 25
  enable-deferred-volume = yes
  deferred-volume-safety-margin-usec = 1
  deferred-volume-extra-delay-usec = 0
  shm-size-bytes = 0
  log-meta = no
  log-time = no
  log-backtrace = 0
  rlimit-fsize = -1
  rlimit-data = -1
  rlimit-stack = -1
  rlimit-core = -1
  rlimit-rss = -1
  rlimit-as = -1
  rlimit-nproc = -1
  rlimit-nofile = 256
  rlimit-memlock = -1
  rlimit-locks = -1
  rlimit-sigpending = -1
  rlimit-msgqueue = -1
  rlimit-nice = 31
  rlimit-rtprio = 9
  rlimit-rttime = 20

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  2194 F pulseaudio
   /dev/snd/controlC0:  david  2194 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 20:08:51 2019
  InstallationDate: Installed on 2019-04-28 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A30
  dmi.board.name: 0KV62T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0KV62T:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.sku: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

[Mike Clark]

Since it's still not working on 19.04, guess that answers my question as
to whether to upgrade or not.  I've confirmed that the acpid isn't
seeing the plug in event by running:

netcat -U /var/run/acpid.socket

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

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

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

  Additional Information:

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

  What I expect to happen:

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

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

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

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

[Touch-packages] [Bug 1827391] [NEW] Japanese era Reiwa SRU

[Dimitri John Ledkov]

Public bug reported:

Japanese era  Reiwa SRU

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

** Affects: icu (Ubuntu Precise)
 Importance: Undecided
 Status: New

** Affects: icu (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: icu (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: icu (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: icu (Ubuntu Cosmic)
 Importance: Undecided
 Status: New

** Affects: icu (Ubuntu Disco)
 Importance: Undecided
 Status: New

** Affects: icu (Ubuntu Eoan)
 Importance: Undecided
 Status: New

** Also affects: icu (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: icu (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

** Also affects: icu (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: icu (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: icu (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: icu (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Japanese era  Reiwa SRU

Status in icu package in Ubuntu:
  New
Status in icu source package in Precise:
  New
Status in icu source package in Trusty:
  New
Status in icu source package in Xenial:
  New
Status in icu source package in Bionic:
  New
Status in icu source package in Cosmic:
  New
Status in icu source package in Disco:
  New
Status in icu source package in Eoan:
  New

Bug description:
  Japanese era  Reiwa SRU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1827391/+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 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails

[Dimitri John Ledkov]

Ping, does vaultlocker work, _without_ work arounds, race free on bionic
and up?

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

** Changed in: lvm2 (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/1780332

Title:
  vaultlocker does not ensure that udev is triggered to create /dev/disk
  /by-uuid/ symlink and fails

Status in vaultlocker:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Incomplete
Status in lvm2 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When an encrypted device is setup up a UUID (osd_fsid) is passed from
  the charm to be used in the cryptsetup command which accepts a UUID to
  place into the LUKS header (shown in cryptsetup luksDump ).

  
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
 
  UUID comes from osd_fsid

  
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
  # else statement is used here
   block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid

   dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS 
header
  # ...
   dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper 
decrypting it via dmcrypt

  https://github.com/openstack-
  
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56

  This UUID is visible in blkid output

  /dev/sdc: UUID="" TYPE="crypto_LUKS"

  and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
  resolution)

  
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
  ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"

  
  Where vaultlocker fails is in luks_open command (right after luks_format) 

   # cryptsetup --batch-mode --key-file - open UUID=
  crypt- --type luks

  because it tries to access /dev/disk/by-uuid/ which
  does not exist.

  This happens since udev rules are not re-triggered to create this
  symlink after a LUKS device is created.

  Solution: call the command below after luks_format before luks_open

  udevadm settle --exit-if-exists=/dev/disk/by-uuid/

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

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

[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Balint Reczey]

Verified 1.178ubuntu2.9 on Bionic:

rbalint@yogi:~/projects/deb/unattended-upgrades$ sudo kbd_mode
The keyboard is in some unknown mode
rbalint@yogi:~$ sudo apt install console-setup console-setup-linux 
keyboard-configuration
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  console-setup console-setup-linux keyboard-configuration
3 upgraded, 0 newly installed, 0 to remove and 67 not upgraded.
Need to get 1.456 kB of archives.
After this operation, 1.024 B of additional disk space will be used.
Get:1 http://mirrors.ubuntu.com/mirrors.txt Mirrorlist [171 B]
Ign:2 http://quantum-mirror.hu/mirrors/pub/ubuntu bionic-proposed/main amd64 
console-setup-linux all 1.178ubuntu2.9
Ign:4 http://ftp.fsn.hu/ubuntu bionic-proposed/main amd64 
keyboard-configuration all 1.178ubuntu2.9
Ign:3 http://mirror.niif.hu/ubuntu bionic-proposed/main amd64 console-setup all 
1.178ubuntu2.9
Ign:4 http://quantum-mirror.hu/mirrors/pub/ubuntu bionic-proposed/main amd64 
keyboard-configuration all 1.178ubuntu2.9
Ign:3 http://quantum-mirror.hu/mirrors/pub/ubuntu bionic-proposed/main amd64 
console-setup all 1.178ubuntu2.9
Get:2 http://hu.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
console-setup-linux all 1.178ubuntu2.9 [982 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
keyboard-configuration all 1.178ubuntu2.9 [369 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 console-setup 
all 1.178ubuntu2.9 [105 kB]
Fetched 1.456 kB in 1s (1.274 kB/s)
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 391247 files and directories currently installed.)
Preparing to unpack .../console-setup-linux_1.178ubuntu2.9_all.deb ...
Unpacking console-setup-linux (1.178ubuntu2.9) over (1.178ubuntu2.8) ...
Preparing to unpack .../console-setup_1.178ubuntu2.9_all.deb ...
Unpacking console-setup (1.178ubuntu2.9) over (1.178ubuntu2.8) ...
Preparing to unpack .../keyboard-configuration_1.178ubuntu2.9_all.deb ...
Unpacking keyboard-configuration (1.178ubuntu2.9) over (1.178ubuntu2.8) ...
Setting up keyboard-configuration (1.178ubuntu2.9) ...
Your console font configuration will be updated the next time your system
boots. If you want to update it now, run 'setupcon' from a virtual console.
update-initramfs: deferring update (trigger activated)
Processing triggers for systemd (237-3ubuntu10.21) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Setting up console-setup-linux (1.178ubuntu2.9) ...
Setting up console-setup (1.178ubuntu2.9) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.130ubuntu3.7) ...
update-initramfs: Generating /boot/initrd.img-4.18.0-18-generic
rbalint@yogi:~$ sudo kbd_mode
The keyboard is in some unknown mode


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

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

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

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

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Confirmed
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Committed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Committed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Committed
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  In Progress
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

 On Xenial X runs on VT7 thus 

[Touch-packages] [Bug 1827040] Re: Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04

[Tyler Hicks]

Hi Peret - Thanks for the bug report. I was browsing through the kernel
commit log and I think this bug may already be fixed by the following
commit:

 commit 916f6efae62305796e012e7c3a7884a267cbacbf
 Author: Florian Westphal 
 Date:   Wed Apr 17 02:17:23 2019 +0200

 netfilter: never get/set skb->tstamp

 https://git.kernel.org/linus/916f6efae62305796e012e7c3a7884a267cbacbf

I've built a test kernel that is 5.0.0-13.14 plus that patch. Would you
be able to test it? You can find it here:

 https://people.canonical.com/~tyhicks/lp1827040/

Thanks again!

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

Title:
  Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04

Status in iptables package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have detected that iptables does not behave in the same way as with 
previous kernel.
  Old behaviour:
  'timestart' referred to the absolute time (UTC or whatever) to start applying 
the rul
  New behaviour: 
  'timestart' refers to the offset since boot start

  It implies a migration of the old rules, and it is difficult to keep 
compatibility, as the offset is complex to behave as an absolute time.
  Is that expected? Man page suggests that the correct behaviour is the old one

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

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

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

[Mathieu Trudel-Lapierre]

** Description changed:

- * Impact
+ [Impact]
+ When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not
  
- When using a VPN the DNS requests might still be sent to a DNS server
- outside the VPN when they should not
+ [Test case]
+ 1) Set up a VPN with split tunneling:
+   a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
+   b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
+   c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".
  
- * Test case
+ 2) Connect to the VPN.
  
- Configure the system to send all the traffic to a VPN, do a name
- resolution, the request should not go to the public DNS server (to be
- checked by capturing the traffic by example with wireshark)
+ 3) Run 'systemd-resolve --status'; note the DNS servers configured:
+   a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
+   b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).
+ 
+ 4) In a separate terminal, run 'sudo tcpdump -ni 
+ port 53'; let it run.
+ 
+ 5) In a separate terminal, run 'sudo tcpdump -ni 
+ port 53'; let it run.
+ 
+ 6) In yet another terminal, issue name resolution requests using dig:
+   a) For a name known to be reachable via the public network:
+  'dig www.yahoo.com'
+   b) For a name known to be reachable only via the VPN:
+  'dig '
+ 
+ 7) Check the output of each terminal running tcpdump. When requesting
+ the public name, traffic can go through either. When requesting the
+ "private" name (behind the VPN), traffic should only be going through
+ the interface for the VPN. Additionally, ensure the IP receiving the
+ requests for the VPN name is indeed the IP address noted above for the
+ VPN's DNS server.
+ 
+ If you see no traffic showing in tcpdump output when requesting a name,
+ it may be because it is cached by systemd-resolved. Use a different name
+ you have not tried before.
  
  
- * Regression potential
- 
- The code change the handling of DNS servers when using a VPN, we should
- check that name resolution still work whne using a VPN in different
- configurations
+ [Regression potential]
+ The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations
  
  -
- 
  
  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch
  
  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local nameservers.
  
  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.
  
  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

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

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

  2) Connect to the VPN.

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

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

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

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

[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Balint Reczey]

Verified 1.178ubuntu9.2 on Cosmic:

test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode
The keyboard is in raw (scancode) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo apt install -qq 
console-setup-linux console-setup keyboard-configuration
The following packages were automatically installed and are no longer required:
  linux-headers-4.18.0-11 linux-headers-4.18.0-11-generic 
linux-image-4.18.0-11-generic linux-modules-4.18.0-11-generic 
linux-modules-extra-4.18.0-11-generic
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
  console-setup console-setup-linux keyboard-configuration
3 upgraded, 0 newly installed, 0 to remove and 41 not upgraded.
Need to get 1.456 kB of archives.
After this operation, 1.024 B of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 237847 files and directories currently installed.)
Preparing to unpack .../console-setup-linux_1.178ubuntu9.2_all.deb ...
Unpacking console-setup-linux (1.178ubuntu9.2) over (1.178ubuntu9.1) ...
Preparing to unpack .../console-setup_1.178ubuntu9.2_all.deb ...
Unpacking console-setup (1.178ubuntu9.2) over (1.178ubuntu9.1) ...
Preparing to unpack .../keyboard-configuration_1.178ubuntu9.2_all.deb ...
Unpacking keyboard-configuration (1.178ubuntu9.2) over (1.178ubuntu9.1) ...
Setting up keyboard-configuration (1.178ubuntu9.2) ...
Your console font configuration will be updated the next time your system
boots. If you want to update it now, run 'setupcon' from a virtual console.
update-initramfs: deferring update (trigger activated)
Processing triggers for systemd (239-7ubuntu10.13) ...
Processing triggers for man-db (2.8.4-2) ...
Setting up console-setup-linux (1.178ubuntu9.2) ...
Setting up console-setup (1.178ubuntu9.2) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.131ubuntu15.1) ...
update-initramfs: Generating /boot/initrd.img-4.18.0-18-generic
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode
The keyboard is in raw (scancode) mode


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

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

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

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Confirmed
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Committed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Committed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Committed
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  In Progress
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

 On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 
script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode 
to observe the change:
 $  sudo kbd_mode -s -C /dev/tty1
 $ sudo kbd_mode -C /dev/tty1
 The keyboard is in raw (scancode) mode

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you want to update it now, run 'setupcon' from a virtual console.
     ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same (on Xenial check VT1: sudo kbd_mode -C
  /dev/tty1):

     $ sudo kbd_mode
  

[Touch-packages] [Bug 1824341] Re: NoAllowedOrigin cause package removal

[Anderson Luiz Alves]

unattended-upgrades=1.1ubuntu1.18.04.7~16.04.3 works on xenial

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

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

Title:
  NoAllowedOrigin cause package removal

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Cosmic:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * When applying a minimal upgrade set fails raising an exception
  unattended-upgrades stops trying to install further sets and may
  remove packages left marked to remove in the dirty set.

  [Test Case]

   * Set up unattended-upgrades to always remove autoremovable packages:

 $ echo 'Unattended-Upgrade::Remove-Unused-Dependencies "false";' | sudo 
tee /etc/apt/apt.conf.d/51unattended-upgrades-remove
   * Install a package and mark it as autoremovable

 $ sudo apt install hello
 $ sudo apt-mark auto hello

   * Set up the custom package to trigger the failure with the exception when 
applying the minimal sets in a way that leaves packages to remove in the dirty 
cache. If the reporter can reproduce the issue on all releases then that's 
great, otherwise I provide an example with equivs.

   * Check if u-u still crashes
$ sudo unattended-upgrades -d

  [Regression Potential]

   * The fix is catching the raised exceptions and trying to apply next minimal 
sets. In special circumstances this could fail again for all sets or could make 
systems's state worse if the installation is already broken. I can't come up 
with an example where it would make the system's state worse because when 
packages can't be safely installed Cache.commit() is expected to fail earlier, 
thust making the system's state worse seems unlikely.
   * OTOH when upgrading a set fails this would not block the installation of 
bigger sets anymore which is a big advantage of having this fix in u-u.

  [Original Bug Text]

  unattended-upgrades remove packages that shouldn't when there is a
  NoAllowedOrigin exception.

  Version:
  unattended-upgrades=1.1ubuntu1.18.04.10
  Ubuntu 18.04.2 LTS

  Description of problem:
  We have a internal package cliente-ldap that depends on samba, when u-u check 
for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't 
clear apt.cache and it removes packages that shouldn't.

  Log that happens package removal:
  $ sudo unattended-upgrade -d
  [...]
  Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules 
smbclient
  Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  debug: call_adjusted samba-common
  debug: marked_pkg: samba: install=False, upgrade=False, delete=True
  debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 257, in call_adjusted
  self.allowed_origins)
    File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin
  raise NoAllowedOriginError()
  NoAllowedOriginError
  debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
  debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True
  debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True
  Exception:
  marking samba-common-bin for removal
  Keeping auto-removable samba-common-bin package(s) because it would also 
remove the following packages which should be kept in this step: samba-common
  marking cliente-ldap for removal
  (Reading database ... 213413 files and directories currently installed.)
  Removing cliente-ldap (1:2.17.15) ...
  marking libcephfs2 for removal
  (Reading database ... 213392 files and directories currently installed.)
  Removing libcephfs2 (12.2.11-0ubuntu0.18.04.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  marking ldap-auth-config for removal
  (Reading database ... 213386 files and directories currently installed.)
  Removing libpam-ldap:amd64 (186-4ubuntu1) ...
  Removing ldap-auth-config (0.5.3) ...
  Removing ldap-auth-client (0.5.3) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking python-samba for removal
  (Reading database ... 213332 files and directories currently installed.)
  Removing samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing samba-common-bin (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing python-samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) 

[Touch-packages] [Bug 1817627] Re: systemd-analyze verify reports failure

[Mark Stosberg]

This is a scary bug. I was just trying to verify the syntax of a timer
file using systemd v237. I got an error message back suggesting
something like rm -rf / was attempted to be executed instead!

   $ sudo systemd-analyze verify /etc/systemd/system/my.timer
   Attempted to remove disk file system, and we can't allow that.

Backporting this fix could help reduce the risk of heart attacks.

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

Title:
  systemd-analyze verify reports failure

Status in Ubuntu Manpage Repository:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Version 237 and 238 of systemd-analyze have a known issue:
  https://github.com/systemd/systemd/issues/8592

  When will a fix be posted?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manpage-repository/+bug/1817627/+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 1781699] Re: DHCPv6 server crashes regularly (bionic)

[Andreas Hasenack]

Thanks Alex, let's see if the patch changes after the issue is looked at
from a security perspective.

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

Title:
  DHCPv6 server crashes regularly (bionic)

Status in DHCP:
  Unknown
Status in isc-dhcp package in Ubuntu:
  Triaged
Status in isc-dhcp package in Debian:
  New
Status in isc-dhcp package in Fedora:
  Unknown

Bug description:
  The isc-dhcp-server crashes regularly on bionic, sometimes directly after 
boot, sometimes later.
  The version installed is 4.3.5-3ubuntu7.

  journalctl shows:
  Jul 14 09:35:11  dhcpd[1543]: Solicit message from 
fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x7E8EC00
  Jul 14 09:35:11  dhcpd[1543]: Advertise NA: address ::1998 
to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid 
for 8
  Jul 14 09:35:11  dhcpd[1543]: Sending Advertise to 
fe80::18eb:dfc7:17e5:c8d7 port 546
  Jul 14 09:35:12  dhcpd[1543]: Request message from 
fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x65FADB00
  Jul 14 09:35:12  dhcpd[1543]: Reply NA: address ::1998 to 
client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 
86400
  Jul 14 09:35:12  dhcpd[1543]: Sending Reply to 
fe80::18eb:dfc7:17e5:c8d7 port 546
  Jul 14 09:35:53  dhcpd[1543]: Confirm message from 
fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x5105F400
  Jul 14 09:35:53  dhcpd[1543]: Sending Reply to 
fe80::725a:b6ff:fea2:6120 port 546
  Jul 14 09:35:53  dhcpd[1543]: Rebind message from 
fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x1FEA7E00
  Jul 14 09:35:53  dhcpd[1543]: Reply NA: address ::1992 to 
client with duid 00:04:c2:47:10:e8:8b:dc:d4:a1:0a:1d:21:f2:be:20:e8:a0 iaid = 
-1230
  Jul 14 09:35:53  sh[1543]: ../../../lib/isc/heap.c:251: REQUIRE(idx 
>= 1 && idx <= heap->last) failed, back trace
  Jul 14 09:35:53  sh[1543]: #0 0x7efc458a6417 in ??
  Jul 14 09:35:53  sh[1543]: #1 0x7efc458a636a in ??
  Jul 14 09:35:53  sh[1543]: #2 0x7efc458ad4ea in ??
  Jul 14 09:35:53  sh[1543]: #3 0x55d9ee65d571 in ??
  Jul 14 09:35:53  sh[1543]: #4 0x55d9ee658701 in ??
  Jul 14 09:35:53  sh[1543]: #5 0x55d9ee65ab05 in ??
  Jul 14 09:35:53  sh[1543]: #6 0x55d9ee65bff3 in ??
  Jul 14 09:35:53  sh[1543]: #7 0x55d9ee65cafc in ??
  Jul 14 09:35:53  sh[1543]: #8 0x55d9ee678402 in ??
  Jul 14 09:35:53  sh[1543]: #9 0x55d9ee667463 in ??
  Jul 14 09:35:53  sh[1543]: #10 0x55d9ee696476 in ??
  Jul 14 09:35:53  sh[1543]: #11 0x7efc458dd73b in ??
  Jul 14 09:35:53  sh[1543]: #12 0x7efc458ccf9e in ??
  Jul 14 09:35:53  sh[1543]: #13 0x7efc458d1e60 in ??
  Jul 14 09:35:53  sh[1543]: #14 0x7efc458d2325 in ??
  Jul 14 09:35:53  sh[1543]: #15 0x55d9ee6696b0 in ??
  Jul 14 09:35:53  sh[1543]: #16 0x55d9ee61d519 in ??
  Jul 14 09:35:53  sh[1543]: #17 0x7efc454c6b97 in ??
  Jul 14 09:35:53  sh[1543]: #18 0x55d9ee61de0a in ??
  Jul 14 09:35:54  systemd[1]: isc-dhcp-server6.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 14 09:35:54  systemd[1]: isc-dhcp-server6.service: Failed with 
result 'core-dump'.

  The bug was reported to Debian independently, https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=896122.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1781699/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

[Andreas Hasenack]

Switching zsh back to incomplete, according to previous comment. Thanks
for noticing that.

** Changed in: zsh (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  Triaged
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Triaged
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in tilix package in Ubuntu:
  New
Status in ubuntu-core-meta package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Released
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1759014] Re: Netplan has no way to control DHCP client

[Michael Steffens]

Verified netplan.io 0.96-0ubuntu0.18.10.3 using

network:
version: 2
ethernets:
ens3:
dhcp4: true
dhcp4-overrides:
use-dns: false
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
match:
macaddress: fa:16:3e:09:85:54
set-name: ens3
ens4:
dhcp4: true
dhcp4-overrides:
use-routes: false
use-dns: false
route-metric: 
match:
macaddress: fa:16:3e:56:2f:d6
set-name: ens4

Routes are configured as expected, so is DNS.

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

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

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1822062] Re: Race condition on boot between cups and sssd

[Eric Desrochers]

Sponsored for D/C/B/X.

Thanks Victor !

-Eric

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  In Progress
Status in cups source package in Bionic:
  In Progress
Status in cups source package in Cosmic:
  In Progress
Status in cups source package in Disco:
  In Progress
Status in cups source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1824341] Re: NoAllowedOrigin cause package removal

[Anderson Luiz Alves]

unattended-upgrades=1.1ubuntu1.18.04.11 works on bionic.

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

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

Title:
  NoAllowedOrigin cause package removal

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Cosmic:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * When applying a minimal upgrade set fails raising an exception
  unattended-upgrades stops trying to install further sets and may
  remove packages left marked to remove in the dirty set.

  [Test Case]

   * Set up unattended-upgrades to always remove autoremovable packages:

 $ echo 'Unattended-Upgrade::Remove-Unused-Dependencies "false";' | sudo 
tee /etc/apt/apt.conf.d/51unattended-upgrades-remove
   * Install a package and mark it as autoremovable

 $ sudo apt install hello
 $ sudo apt-mark auto hello

   * Set up the custom package to trigger the failure with the exception when 
applying the minimal sets in a way that leaves packages to remove in the dirty 
cache. If the reporter can reproduce the issue on all releases then that's 
great, otherwise I provide an example with equivs.

   * Check if u-u still crashes
$ sudo unattended-upgrades -d

  [Regression Potential]

   * The fix is catching the raised exceptions and trying to apply next minimal 
sets. In special circumstances this could fail again for all sets or could make 
systems's state worse if the installation is already broken. I can't come up 
with an example where it would make the system's state worse because when 
packages can't be safely installed Cache.commit() is expected to fail earlier, 
thust making the system's state worse seems unlikely.
   * OTOH when upgrading a set fails this would not block the installation of 
bigger sets anymore which is a big advantage of having this fix in u-u.

  [Original Bug Text]

  unattended-upgrades remove packages that shouldn't when there is a
  NoAllowedOrigin exception.

  Version:
  unattended-upgrades=1.1ubuntu1.18.04.10
  Ubuntu 18.04.2 LTS

  Description of problem:
  We have a internal package cliente-ldap that depends on samba, when u-u check 
for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't 
clear apt.cache and it removes packages that shouldn't.

  Log that happens package removal:
  $ sudo unattended-upgrade -d
  [...]
  Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules 
smbclient
  Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  debug: call_adjusted samba-common
  debug: marked_pkg: samba: install=False, upgrade=False, delete=True
  debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 257, in call_adjusted
  self.allowed_origins)
    File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin
  raise NoAllowedOriginError()
  NoAllowedOriginError
  debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
  debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True
  debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True
  Exception:
  marking samba-common-bin for removal
  Keeping auto-removable samba-common-bin package(s) because it would also 
remove the following packages which should be kept in this step: samba-common
  marking cliente-ldap for removal
  (Reading database ... 213413 files and directories currently installed.)
  Removing cliente-ldap (1:2.17.15) ...
  marking libcephfs2 for removal
  (Reading database ... 213392 files and directories currently installed.)
  Removing libcephfs2 (12.2.11-0ubuntu0.18.04.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  marking ldap-auth-config for removal
  (Reading database ... 213386 files and directories currently installed.)
  Removing libpam-ldap:amd64 (186-4ubuntu1) ...
  Removing ldap-auth-config (0.5.3) ...
  Removing ldap-auth-client (0.5.3) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking python-samba for removal
  (Reading database ... 213332 files and directories currently installed.)
  Removing samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing samba-common-bin (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing python-samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  

[Touch-packages] [Bug 1827365] [NEW] ibus-setup info message contains non-human readable symbols

[Norbert]

Public bug reported:

Steps to reproduce:
1. Have Ubuntu 18.04 LTS installed
2. Launch `ibus-setup`
3. Confirm starting the daemon
4. See informational message (see screenshot)

Expected results:
* the message contains human-readable symbols

Actual results:
* the message contains strange - symbols

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: MATE
Date: Thu May  2 14:30:43 2019
InstallationDate: Installed on 2018-04-26 (370 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "ibus-setup message with - symbols"
   
https://bugs.launchpad.net/bugs/1827365/+attachment/5260869/+files/ibus-setup_info.png

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

Title:
  ibus-setup info message contains non-human readable symbols

Status in ibus package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.04 LTS installed
  2. Launch `ibus-setup`
  3. Confirm starting the daemon
  4. See informational message (see screenshot)

  Expected results:
  * the message contains human-readable symbols

  Actual results:
  * the message contains strange - symbols

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu May  2 14:30:43 2019
  InstallationDate: Installed on 2018-04-26 (370 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Balint Reczey]

Verified 1.178ubuntu12.1 on Disco:

root@MacBookAir-test:/home/rbalint# echo $DISPLAY

root@MacBookAir-test:/home/rbalint# kbd_mode -C /dev/tty1
The keyboard is in raw (scancode) mode
root@MacBookAir-test:/home/rbalint# apt install -qq console-setup-linux 
console-setup keyboard-configuration 
The following packages will be upgraded:
  console-setup console-setup-linux keyboard-configuration
3 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
Need to get 1,457 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 295554 files and directories currently installed.)
Preparing to unpack .../console-setup-linux_1.178ubuntu12.1_all.deb ...
Unpacking console-setup-linux (1.178ubuntu12.1) over (1.178ubuntu12) ...
Preparing to unpack .../console-setup_1.178ubuntu12.1_all.deb ...
Unpacking console-setup (1.178ubuntu12.1) over (1.178ubuntu12) ...
Preparing to unpack .../keyboard-configuration_1.178ubuntu12.1_all.deb ...
Unpacking keyboard-configuration (1.178ubuntu12.1) over (1.178ubuntu12) ...
Setting up keyboard-configuration (1.178ubuntu12.1) ...
Your console font configuration will be updated the next time your system
boots. If you want to update it now, run 'setupcon' from a virtual console.
update-initramfs: deferring update (trigger activated)
Setting up console-setup-linux (1.178ubuntu12.1) ...
Setting up console-setup (1.178ubuntu12.1) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for systemd (240-6ubuntu5.1) ...
Processing triggers for initramfs-tools (0.131ubuntu19) ...
update-initramfs: Generating /boot/initrd.img-5.0.0-13-generic
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
nor crypto modules. If that's on purpose, you may want to uninstall the 
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs 
integration and avoid this warning.
root@MacBookAir-test:/home/rbalint# kbd_mode -C /dev/tty1
The keyboard is in raw (scancode) mode


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

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

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

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Confirmed
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Committed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Committed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Committed
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  In Progress
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

 On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 
script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode 
to observe the change:
 $  sudo kbd_mode -s -C /dev/tty1
 $ sudo kbd_mode -C /dev/tty1
 The keyboard is in raw (scancode) mode

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you want to update it now, run 'setupcon' from a virtual console.
     ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same (on Xenial check VT1: sudo kbd_mode -C

[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client

[Michael Steffens]

Verified netplan.io 0.96-0ubuntu0.18.04.4 with the configuration from
https://bugs.launchpad.net/netplan/+bug/1759014/comments/52. Routes are
configured as expected, as is DNS.

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

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

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1740709] Re: GtkSpinButton's '+' changes width if insensitive

[Egmont Koblinger]

Can't reproduce on disco.

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

Title:
  GtkSpinButton's '+' changes width if insensitive

Status in Ubuntu theme:
  Won't Fix
Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  GtkSpinButton consists of a (typically numeric) input field, followed
  by a '-' and finally a '+' sign. The width of the '+' sign depends on
  whether it's sensitive or not. It shouldn't, it should have a constant
  width.

  Happens with Ubuntu's default Ambiance and Radiance themes. Does not
  happen with GTK+'s default Adwaita.

  Example 1: Open dconf-editor and navigate to /ca/desrt/dconf-
  editor/demo/integer-16-unsigned. Uncheck "Use default value" and use
  the +/- buttons to alter the value. As it reaches 65535, that is, the
  '+' button becomes insensitive, its width increases. Click '-' to make
  the '+' sign sensitive again, its width shrinks back.

  Example 2: Open gnome-terminal, Edit -> Profile Preferences, Scrolling
  tab, toggle the checkbox in front of "Limit scrollback to" back and
  forth. Notice how the '+' sign keeps changing width, and the "lines"
  label keeps jumping back and forth accordingly.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171115-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Dec 31 22:08:32 2017
  InstallationDate: Installed on 2016-11-09 (416 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-09-21 (100 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1740709/+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 1824111] Re: Backport packages for 18.04.3 HWE stack

[Timo Aaltonen]

** Also affects: mesa (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: libdrm (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: libclc (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: xorg-server-hwe-18.04 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: llvm-toolchain-8 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: libclc (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

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

** Changed in: llvm-toolchain-8 (Ubuntu)
   Status: New => Invalid

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

** Changed in: xorg-server-hwe-18.04 (Ubuntu)
   Status: New => Invalid

** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu)
   Status: New => Invalid

** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu)
   Status: New => Invalid

** Changed in: xserver-xorg-video-ati-hwe-18.04 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: xserver-xorg-video-amdgpu-hwe-18.04 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: llvm-toolchain-8 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: libdrm (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Backport packages for 18.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-8 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  New
Status in libdrm source package in Bionic:
  New
Status in llvm-toolchain-8 source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in xorg-server-hwe-18.04 source package in Bionic:
  New
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
  New
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
  New

Bug description:
  [Impact]

  These are needed for 18.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-8: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new minor release

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

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

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

[Touch-packages] [Bug 1825194] Proposed package upload rejected

[Robie Basak]

An upload of resolvconf to xenial-proposed has been rejected from the
upload queue for the following reason: "Needs adjustment; see
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/comments/11;.

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

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

Status in resolvconf package in Ubuntu:
  Fix Released
Status in resolvconf source package in Xenial:
  In Progress

Bug description:
  [Impact]

  The bug can lead to non-working DNS. This is a critical bug that needs
  to be fixed in the stable release.

  The patch fixes the bug by using a file lock via the flock command.

  [Test case]

  This script should eventually stop with the current version, thing
  that should not happen after applying the patch:

  while true; do
  printf "\n" | sudo resolvconf -a NetworkManager
  printf "nameserver 8.8.8.8\n" | sudo resolvconf -a networkd
  wait
  printf "nameserver 8.8.8.8\n" |
  sudo resolvconf -a NetworkManager &
  printf "\n" | sudo resolvconf -a networkd
  wait
  ping -c 1 www.google.com || break
  done

  [Regression Potential]

  The patch is small and what it does is straightforward. It has also
  been thoroughly tested. However, the effect if something is wrong
  would be not being able to resolve DNS names, which is disastrous, so
  it needs to be very well tested for the SRU.

  [Other Info]

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1827354] [NEW] Ubuntu 18.04 Desktop reports error on startup

[David White]

Public bug reported:

david@david-OptiPlex-9010:~$ sudo lsb_release -rd
Description:Ubuntu 18.04.2 LTS

david@david-OptiPlex-9010:~$ sudo apt-cache policy pulseaudio
pulseaudio:
  Installed: 1:11.1-1ubuntu7.2
  Candidate: 1:11.1-1ubuntu7.2
  Version table:
 *** 1:11.1-1ubuntu7.2 500
500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:11.1-1ubuntu7 500
500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

Error Log:
[pulseaudio] bluez5-util.c: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

david@david-OptiPlex-9010:~$ pulseaudio --version
pulseaudio 11.1

david@david-OptiPlex-9010:~$ pulseaudio --dump-conf
### Read from configuration file: /etc/pulse/daemon.conf ###
daemonize = no
fail = yes
high-priority = yes
nice-level = -11
realtime-scheduling = yes
realtime-priority = 5
allow-module-loading = yes
allow-exit = yes
use-pid-file = yes
system-instance = no
local-server-type = user
cpu-limit = no
enable-shm = yes
flat-volumes = no
lock-memory = no
exit-idle-time = 20
scache-idle-time = 20
dl-search-path = /usr/lib/pulse-11.1/modules
default-script-file = /etc/pulse/default.pa
load-default-script-file = yes
log-target = 
log-level = notice
resample-method = auto
avoid-resampling = yes
enable-remixing = yes
remixing-use-all-sink-channels = yes
enable-lfe-remixing = no
lfe-crossover-freq = 0
default-sample-format = s16le
default-sample-rate = 44100
alternate-sample-rate = 48000
default-sample-channels = 2
default-channel-map = front-left,front-right
default-fragments = 4
default-fragment-size-msec = 25
enable-deferred-volume = yes
deferred-volume-safety-margin-usec = 1
deferred-volume-extra-delay-usec = 0
shm-size-bytes = 0
log-meta = no
log-time = no
log-backtrace = 0
rlimit-fsize = -1
rlimit-data = -1
rlimit-stack = -1
rlimit-core = -1
rlimit-rss = -1
rlimit-as = -1
rlimit-nproc = -1
rlimit-nofile = 256
rlimit-memlock = -1
rlimit-locks = -1
rlimit-sigpending = -1
rlimit-msgqueue = -1
rlimit-nice = 31
rlimit-rtprio = 9
rlimit-rttime = 20

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  david  2194 F pulseaudio
 /dev/snd/controlC0:  david  2194 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu May  2 20:08:51 2019
InstallationDate: Installed on 2019-04-28 (4 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/28/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A30
dmi.board.name: 0KV62T
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0KV62T:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 9010
dmi.product.sku: OptiPlex 9010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  Ubuntu 18.04 Desktop reports error on startup

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  david@david-OptiPlex-9010:~$ sudo lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS

  david@david-OptiPlex-9010:~$ sudo apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:11.1-1ubuntu7.2
Candidate: 1:11.1-1ubuntu7.2
Version table:
   *** 1:11.1-1ubuntu7.2 500
  500 http://au.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7 500
  500 http://au.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Error Log:
  [pulseaudio] bluez5-util.c: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

  david@david-OptiPlex-9010:~$ pulseaudio --version
  pulseaudio 11.1

  david@david-OptiPlex-9010:~$ pulseaudio --dump-conf
  ### Read from configuration file: 

[Touch-packages] [Bug 1827355] Re: /usr/bin/unattended-upgrade:SystemError:try_to_upgrade:rewind_cache:mark_install:/usr/bin/unattended-upgrade@1998:main:calculate_upgradable_pkgs:try_to_upgrade:rewin

[Balint Reczey]

*** This bug is a duplicate of bug 1826157 ***
https://bugs.launchpad.net/bugs/1826157

** This bug has been marked a duplicate of bug 1826157
   unattended-upgrades: rewind_cache() may crash due to not adjusting package 
candidates

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

Title:
  /usr/bin/unattended-
  upgrade:SystemError:try_to_upgrade:rewind_cache:mark_install:/usr/bin
  /unattended-
  
upgrade@1998:main:calculate_upgradable_pkgs:try_to_upgrade:rewind_cache:mark_install

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.9, the problem page at 
https://errors.ubuntu.com/problem/356d7c0e1a5199b6d463b88a9794c912d4e0f7e2 
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/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1827355/+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 1826916] Re: MAAS uninstalls itself on unattended upgrade

[Balint Reczey]

@vorlon: Yes, but there is (was) a bug where u-u removes auto removable but not 
newly auto removable packages when an upgrade step fails and leaves a dirty 
cache behind: LP: #1824341 .
The fix is scheduled to be released for Xenial next week.

@chris.sanders: To confirm that this happened please attach the relevant part 
of:
/var/log/unattended-upgrades/unattended-upgrades.log

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

Title:
  MAAS uninstalls itself on unattended upgrade

Status in maas package in Ubuntu:
  Incomplete
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Having recently found my MAAS unresponsive I was surprised to find out
  it's because it uninstalled itself. First, how on earth does this
  happen, and second how do I go about recovering this I have several
  critical juju services deployed on a nodes that this MAAS runs and
  juju is unusable with MAAS down.

  I've just done the backup as per https://docs.maas.io/2.5/en/manage-
  backup do I just do a fresh install now and do the restore steps? Will
  this simply get removed on the next upgrade?

  
  Start-Date: 2019-04-24  06:02:09
  Commandline: /usr/bin/unattended-upgrade
  Remove: libjs-yui3-full:amd64 (3.5.1-1ubuntu3), python3-pexpect:amd64 
(4.0.1-1), python3-distro-info:amd64 (0.14build1), libwebp5:amd64 (0.4.4-1), 
python3-roman:amd64 (2.0.0-2), python3-html5lib:amd64 (0.999-4), 
squid-langpack:amd64 (20150704-1), python3-ecdsa:amd64 (0.13-2), 
python3-dnspython:amd64 (1.12.0-0ubuntu3), python3-mimeparse:amd64 
(0.1.4-1build1), libirs-export141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), 
fonts-font-awesome:amd64 (4.5.0~dfsg-1), python3-zope.interface:amd64 
(4.1.3-1build1), python3-djorm-ext-pgarray:amd64 (1.2-0ubuntu2), 
javascript-common:amd64 (11), python3-formencode:amd64 (1.3.0-0ubuntu5), 
dbconfig-pgsql:amd64 (2.0.4ubuntu1), os-prober:amd64 (1.70ubuntu3.3), 
python3-seamicroclient:amd64 (0.4.0-1ubuntu1), python3-babel:amd64 
(1.3+dfsg.1-6), docutils-common:amd64 (0.12+dfsg-1), 
python3-maas-provisioningserver:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), 
libibverbs1:amd64 (1.1.8-1.1ubuntu2), python3-sphinx:amd64 (1.3.6-2ubuntu1.1), 
libfreeipmi16:amd64 (1.4.11-1.1ubuntu4~0.16.04), libaprutil1:amd64 
(1.5.4-1build1), libipmidetect0:amd64 (1.4.11-1.1ubuntu4~0.16.04), 
python3-netaddr:amd64 (0.7.18-1), grub-common:amd64 (2.02~beta2-36ubuntu3.17), 
libirs141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), squid-common:amd64 
(3.5.12-1ubuntu7.5), authbind:amd64 (2.1.1+nmu1), freeipmi-common:amd64 
(1.4.11-1.1ubuntu4~0.16.04), python3-pam:amd64 (0.4.2-13.2ubuntu2), 
python3-pbr:amd64 (1.8.0-4ubuntu1), python3-pil:amd64 (3.1.2-0ubuntu1.1), 
python3-simplestreams:amd64 (0.1.0~bzr426-0ubuntu1.2), 
libaprutil1-dbd-sqlite3:amd64 (1.5.4-1build1), python3-netifaces:amd64 
(0.10.4-0.1build2), python3-django-maas:amd64 
(2.3.0-6434-gd354690-0ubuntu1~16.04.1), libjs-jquery:amd64 (1.11.3+dfsg-4), 
libjs-underscore:amd64 (1.7.0~dfsg-1ubuntu1), libjs-yui3-min:amd64 
(3.5.1-1ubuntu3), python3-curtin:amd64 (17.1-11-ga4c9636b-0ubuntu1~16.04.1), 
python-django-common:amd64 (1.8.7-1ubuntu5.8), python3-service-identity:amd64 
(16.0.0-2), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), librdmacm1:amd64 
(1.0.21-1), libconfig-general-perl:amd64 (2.60-1), python3-jsonschema:amd64 
(2.5.1-4), maas-common:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), 
python3-txtftp:amd64 (0.1~bzr42-0ubuntu2), apache2-data:amd64 
(2.4.18-2ubuntu3.10), python3-crochet:amd64 (1.4.0-0ubuntu2), 
python3-httplib2:amd64 (0.9.1+dfsg-1), python3-iso8601:amd64 (0.1.11-1), 
pxelinux:amd64 (3:6.03+dfsg-11ubuntu1), python3-sphinx-rtd-theme:amd64 
(0.1.9-1), python3-pyparsing:amd64 (2.0.3+dfsg1-1ubuntu0.1), libpaper1:amd64 
(1.1.24+nmu4ubuntu1), libjs-yui3-common:amd64 (3.5.1-1ubuntu3), 
python3-twisted:amd64 (16.0.0-1ubuntu0.2), python3-simplejson:amd64 
(3.8.1-1ubuntu2), ntp:amd64 (1:4.2.8p4+dfsg-3ubuntu5.9), libllvm4.0:amd64 
(1:4.0-1ubuntu1~16.04.2), libapr1:amd64 (1.5.2-3), maas-rack-controller:amd64 
(2.3.0-6434-gd354690-0ubuntu1~16.04.1), libipmiconsole2:amd64 
(1.4.11-1.1ubuntu4~0.16.04), libaprutil1-ldap:amd64 (1.5.4-1build1), 
maas-cli:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), distro-info:amd64 
(0.14build1), maas-dns:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), 
libisccfg-export140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), python3-pyvmomi:amd64 
(5.5.0-2014.1.1-3), sphinx-rtd-theme-common:amd64 (0.1.9-1), 
python3-petname:amd64 (2.0-0ubuntu1~16.04), python3-alabaster:amd64 (0.7.7-1), 
python3-maas-client:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), tgt:amd64 
(1:1.0.63-1ubuntu1.1), python3-docutils:amd64 (0.12+dfsg-1), postgresql:amd64 
(9.5+173ubuntu0.1), python3-tempita:amd64 (0.5.2-1build1), 
python3-bson-ext:amd64 (3.2-1build1), python3-convoy:amd64 (0.2.1+bzr39-1), 
maas-region-controller:amd64 

[Touch-packages] [Bug 1827355] [NEW] /usr/bin/unattended-upgrade:SystemError:try_to_upgrade:rewind_cache:mark_install:/usr/bin/unattended-upgrade@1998:main:calculate_upgradable_pkgs:try_to_upgrade:rew

[errors.ubuntu.com bug bridge]

*** This bug is a duplicate of bug 1826157 ***
https://bugs.launchpad.net/bugs/1826157

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.9, the problem page at 
https://errors.ubuntu.com/problem/356d7c0e1a5199b6d463b88a9794c912d4e0f7e2 
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/.

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


** Tags: bionic xenial

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

Title:
  /usr/bin/unattended-
  upgrade:SystemError:try_to_upgrade:rewind_cache:mark_install:/usr/bin
  /unattended-
  
upgrade@1998:main:calculate_upgradable_pkgs:try_to_upgrade:rewind_cache:mark_install

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.9, the problem page at 
https://errors.ubuntu.com/problem/356d7c0e1a5199b6d463b88a9794c912d4e0f7e2 
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/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1827355/+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 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unattended-upgrades (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  Fixing fsfreeze-hook can break unattended upgrades

Status in qemu package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Cosmic:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * If an update has a new conffile at a path that in a former version was
     a directory like
  old: /a/b/c
  new: a/b
     Here b is the new file name and was a directory in the old version.
     Then unattended upgrades breaks on installing such a package.

   * a recent qemu update has such a case and due to that triggered the
     issue in >=Bionic

   * The fix is to harden unattended upgrades to be able to handle the case
     without aborting.

  [Test Case]

  Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12
  That can be done with:
    $ time uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic
    $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic 
label=daily

  Log in and apt update & upgrade all packages, then Install the release level 
qemu in there.
    $ uvt-kvm ssh bionic-testuu
    $ sudo apt update
    $ sudo apt dist-upgrade
    $ sudo apt install unattended-upgrades
    $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7

  All before was preparation, now force the unattended upgrade to trigger the 
bug.
    $ sudo unattended-upgrade -d

  With the bug you'll find some error like:
  found pkg: qemu-guest-agent
  conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191
  current md5: f61a64ac1e48993023018fd1cff85191
  conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 
15f6ff42cbc5550a07ee21c2a471d905
  /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles 
/etc/init.d/qemu-guest-agent
  /etc/qemu/fsfreeze-hook
  found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 2057, in 
  sys.exit(main(options))
    File "/usr/bin/unattended-upgrade", line 1773, in main
  if conffile_prompt(item.destfile):
    File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt
  with open(prefix + conf_file, 'rb') as fp:
  IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'

  [Regression Potential]

   * The fix is trying to detect moved conffiles by looking for /etc/foo/foo 
when the new package ships /etc/foo and /etc/foo is not a known conffile and 
also checking the renames in the opposite direction.
  The potential regression is breaking the logic for detecting changed 
conffiles and either holding back a package for no reason or trying to install 
a package with a modified conffile on the system and aborting the upgrade in 
the middle due to the appearing conffile prompt. To avoid such regressions the 
test_conffile.py tests are extended to cover rename scenarios.

  [Other Info]

   * n/a

  ---

  As reported on 
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20
  We fixed an issue and we added workrounds since basic mv_conffile coudn't 
handle it and did all sort of upgrade tests.

  That all worked fine and moved the conffile.

  It was now reported that due to some pre-checks that unattended
  upgrades might do this might do some checks on its own.

  Next step:
  - check unattended upgrades through this change
  - check if it only affects cases were the former config was modified 
(minority) or the default file layout (majority)

  --- original report copied ---

  just wanted to add: This bug also crashes unattended-upgrade and thus
  prevents security updates on 18.04:

  root@mailin1:~# unattended-upgrade
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1998, in 
  sys.exit(main(options))
    File "/usr/bin/unattended-upgrade", line 1714, in main
  if conffile_prompt(item.destfile):
    File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt
  with open(prefix + conf_file, 'rb') as fp:
  IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'

  Basically, unattended-upgrade wants to compare old/new conffiles and
  doesn't like it when the old conffile turns out to be a directory...

  This prevents security 

[Touch-packages] [Bug 1827280] Re: unattended-upgrade fails silently in qemu VM

[Balint Reczey]

*** This bug is a duplicate of bug 1823872 ***
https://bugs.launchpad.net/bugs/1823872

** This bug has been marked a duplicate of bug 1823872
   Fixing fsfreeze-hook can break unattended upgrades

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

Title:
  unattended-upgrade fails silently in qemu VM

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Since upgrading to 1.1ubuntu1.18.04.9 on several servers (VMs) unattended 
upgrades stopped to run successfully an did not report any errors (via mail).
  If I run it manually it errors out as follows:

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2057, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1773, in main
  if conffile_prompt(item.destfile):
File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt
  with open(prefix + conf_file, 'rb') as fp:
  IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'

  This also happens with Package Version: 1.1ubuntu1.18.04.10

  Expected behavior:
  Either the the program runs without error or the cron job sends a failure 
mail. 

  Here come the logfiles, where you cannot see any errors when on
  1.1ubuntu1.18.04.9, but after manually upgrading to
  1.1ubuntu1.18.04.10 there are warnings:

  2019-05-01 20:28:13,071 INFO Initial whitelisted packages: 
  2019-05-01 20:28:13,071 INFO Starting unattended upgrades script
  2019-05-01 20:28:13,071 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic, 
o=LP-PPA-certbot-certbot,a=bionic, o=LP-PPA-ondrej-nginx-mainline,a=bionic, 
o=LP-PPA-ondrej-php,a=bionic
  2019-05-01 20:39:29,902 INFO Initial blacklisted packages: libc.* linux-.* 
.*-microcode mysql-.* mariadb-.*
  2019-05-01 20:39:29,903 INFO Initial whitelisted packages: 
  2019-05-01 20:39:29,903 INFO Starting unattended upgrades script
  2019-05-01 20:39:29,903 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic, 
o=LP-PPA-certbot-certbot,a=bionic, o=LP-PPA-ondrej-nginx-mainline,a=bionic, 
o=LP-PPA-ondrej-php,a=bionic
  2019-05-01 20:57:47,643 INFO Initial blacklisted packages: libc.* linux-.* 
.*-microcode mysql-.* mariadb-.*
  2019-05-01 20:57:47,644 INFO Initial whitelisted packages: 
  2019-05-01 20:57:47,644 INFO Starting unattended upgrades script
  2019-05-01 20:57:47,644 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic, 
o=LP-PPA-certbot-certbot,a=bionic, o=LP-PPA-ondrej-nginx-mainline,a=bionic, 
o=LP-PPA-ondrej-php,a=bionic
  2019-05-01 21:08:48,278 INFO Initial blacklisted packages: libc.* linux-.* 
.*-microcode mysql-.* mariadb-.*
  2019-05-01 21:08:48,278 INFO Initial whitelisted packages: 
  2019-05-01 21:08:48,279 INFO Starting unattended upgrades script
  2019-05-01 21:08:48,279 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic, 
o=LP-PPA-certbot-certbot,a=bionic, o=LP-PPA-ondrej-nginx-mainline,a=bionic, 
o=LP-PPA-ondrej-php,a=bionic
  2019-05-01 21:08:57,611 WARNING package libxslt1.1 upgradable but fails to be 
marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this 
may be caused by held packages.)
  2019-05-01 21:08:59,398 WARNING package ntfs-3g upgradable but fails to be 
marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this 
may be caused by held packages.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1827280/+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 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

[demon]

Came across other possible causes/solutions:

https://www.linuxquestions.org/questions/linux-networking-3/wifi-drops-
in-and-out-when-on-campus-and-at-home-4175642548/

https://github.com/systemd/systemd/issues/9748

Referencing an issue with linux's ecn setting:

default setting:
"net.ipv4.tcp_ecn=2"

changing it to:
"net.ipv4.tcp_ecn=0"


** Bug watch added: github.com/systemd/systemd/issues #9748
   https://github.com/systemd/systemd/issues/9748

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

Title:
  wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The Wifi network can't connect after the wake up from suspend. Xubuntu
  15.04

  I'll post more useful details (journalctl log) as a comment to this
  bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dbus 1.8.12-1ubuntu5
  Uname: Linux 4.0.0-04rc5-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr  2 18:18:56 2015
  InstallationDate: Installed on 2015-03-27 (5 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+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 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

[demon]

This bug is still present: Using Ubuntu 16.04.6 with upgraded kernel
v5.0.0-05-generic

syslog:

May  2 04:59:48 UbuntuHP wpa_supplicant[1879]: dbus: 
wpa_dbus_get_object_properties: failed to get 
object properties: (none) none

May  2 04:59:48 UbuntuHP wpa_supplicant[1879]: dbus: Failed to construct
signal

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

Title:
  wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The Wifi network can't connect after the wake up from suspend. Xubuntu
  15.04

  I'll post more useful details (journalctl log) as a comment to this
  bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dbus 1.8.12-1ubuntu5
  Uname: Linux 4.0.0-04rc5-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr  2 18:18:56 2015
  InstallationDate: Installed on 2015-03-27 (5 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+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 1497806] Re: Mirrored display broken in Xubuntu

[milanbb55]

For everyone who has the same problem, this solution
https://unix.stackexchange.com/questions/371793/how-to-duplicate-
desktop-in-linux-with-xrandr/371796 worked for me.

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

Title:
  Mirrored display broken in Xubuntu

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Mirrored displays is not accessible (grayed out) when trying to
  activate this feature for multi-monitor support.  I am not sure which
  specific package to nominate for this bug, but it seems to only be
  happening on systems with XFCE4 installed and running (Including
  Xubuntu, Mint, and Debian).

  It maybe an error with the package xfce4-display-settings, but I am
  not sure.

  This bug is being reported from:
  Description:  Linux Mint 17.2 Rafaela
  Release:  17.2

  Here is a copy of this Bug Report on Bugzilla:  
https://bugzilla.xfce.org/show_bug.cgi?id=11712
  This bug report also has a picture attachment which is exactly what I am 
seeing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1497806/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

[Paride Legovini]

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

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  Triaged
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Triaged
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in tilix package in Ubuntu:
  New
Status in ubuntu-core-meta package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Released
Status in zsh package in Ubuntu:
  Triaged

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1759014] Re: Netplan has no way to control DHCP client

[Roger Mårtensson]

Is it possible to get this into 18.04.3 release? Not that fond of
waiting until January 2020 for the .4 release.

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

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1827172] Re: update-rc.d: enabling or disabling S runlevel services incorrectly modifies runlevel

[Ubuntu Foundations Team Bug Bot]

The attachment "sysvinit debdiff for trusty" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

Title:
  update-rc.d: enabling or disabling S runlevel services incorrectly
  modifies runlevel

Status in sysvinit package in Ubuntu:
  New
Status in sysvinit source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * update-rc.d, in sysv-rc-2.88dsf-41ubuntu6.3 is broken in trusty.

   * update-rc.d incorrectly modifies symlinks when enabling or disabling
     services which are started on the "S" runlevel.

   * This can lead to services being changed from S runlevel from where they
     would be started on boot, to "0" runlevel, and are run on halt, which is
     incorrect.

   * The bug is caused by trying to use the runlevel to index into an integer
     array of runlevels. When the runlevel in question is "S", an error is
     printed

     Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line
     232.

     Perl then sets the index to default to 0, which changes the
  runlevel.

   * The fix is to check if the runlevel is "S", and if it is, set the index to
     99 which conforms with other expected usages for the "S" runlevel in the
     script. See the "startstop" and "makelinks" subroutines.

  [Test Case]

  * You can reproduce this with any service that is started on the "S"
    runlevel. We will use open-iscsi for an example.

  1) Install open-iscsi

  $ sudo apt install open-iscsi

  2) Check to see symlinks for init.d scripts are set to defaults:

  root@trusty-openiscsi:/etc# ls -l /etc/rc[0123456S].d/*iscsi*
  /etc/rc0.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
  /etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc1.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
  /etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc6.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
  /etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rcS.d/S45open-iscsi -> ../init.d/open-iscsi

  3) Use update-rc.d to enable open-iscsi service

  root@trusty-openiscsi:/etc# update-rc.d open-iscsi enable
  update-rc.d: warning: start runlevel arguments (none) do not match open-iscsi 
Default-Start values (S)
  update-rc.d: warning: stop runlevel arguments (none) do not match open-iscsi 
Default-Stop values (0 1 6)
  Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line 232.
  Enabling system startup links for /etc/init.d/open-iscsi ...
  Removing any system startup links for /etc/init.d/open-iscsi ...
  /etc/rc0.d/K81open-iscsi
  /etc/rc1.d/K81open-iscsi
  /etc/rc6.d/K81open-iscsi
  /etc/rcS.d/S45open-iscsi
  Adding system startup for /etc/init.d/open-iscsi ...
  /etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc0.d/S45open-iscsi -> ../init.d/open-iscsi

  * The problem is the "/etc/rcS.d/S45open-iscsi" symlink is incorrectly
    changed to "/etc/rc0.d/S45open-iscsi".

  * Instead, the correct behaviour is to keep the symlink in /etc/rcS.d/
    intact:

  root@trusty-openiscsi:/etc# update-rc.d open-iscsi enable
  update-rc.d: warning: start runlevel arguments (none) do not match open-iscsi 
Default-Start values (S)
  update-rc.d: warning: stop runlevel arguments (none) do not match open-iscsi 
Default-Stop values (0 1 6)
  Enabling system startup links for /etc/init.d/open-iscsi ...
  Removing any system startup links for /etc/init.d/open-iscsi ...
  /etc/rc0.d/K81open-iscsi
  /etc/rc1.d/K81open-iscsi
  /etc/rc6.d/K81open-iscsi
  /etc/rcS.d/S45open-iscsi
  Adding system startup for /etc/init.d/open-iscsi ...
  /etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rcS.d/S45open-iscsi -> ../init.d/open-iscsi

  [Regression Potential]

   * There is only one file modified, which is the update-rc.d perl script.
     Worst case scenario is that users cannot enable or disable their services,
     or a symlink is changed such that a service is started / stopped on an
     incorrect runlevel.

   * If a regression happens, any damage should be easily spotted by a
     sysadmin and can be manually repaired by making manual symlinks with
     "ln -s".

   * I have built and tested the change in a PPA, which you can find here:
 

[Touch-packages] [Bug 433897] Re: Console/VT font is (randomly) not set (sometimes) on some machines. Stuck with the default VGA BIOS font.

[Daniel van Vugt]

And yet the bug is in eoan.

** Tags added: eoan

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

Title:
  Console/VT font is (randomly) not set (sometimes) on some machines.
  Stuck with the default VGA BIOS font.

Status in console-setup:
  New
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  [Fix]

  [Test Case]

  [Regression Potential]

  [Original Report]
  Since the Karmic transition away from init.d scripts to upstart services has 
started, the font is no longer set at bootup. This results in unreadable user 
prompts, whenever applications output non-ascii characters to screen and it 
also affects graphic box characters used by ncurses, such as for debconf 
dialogs.

  ProblemType: Bug
  Architecture: i386
  Date: Mon Sep 21 12:51:40 2009
  DistroRelease: Ubuntu 9.10
  Package: console-setup 1.34ubuntu2
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=fi_FI.UTF-8
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
  SourcePackage: console-setup
  Uname: Linux 2.6.31-10-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/console-setup/+bug/433897/+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 1827154] Re: [wacom] gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()

[Sebastien Bacher]

** Summary changed:

- gnome-control-center crashed with SIGSEGV in 
_gdk_event_queue_handle_motion_compression()
+ [wacom] gnome-control-center crashed with SIGSEGV in 
_gdk_event_queue_handle_motion_compression()

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

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Triaged

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

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

Title:
  [wacom] gnome-control-center crashed with SIGSEGV in
  _gdk_event_queue_handle_motion_compression()

Status in gnome-control-center:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503

  ---

  [Impact]
  When I try to set the pen on my touch screen. gnome-control-center crashes.

  [Fix]
  That you can configure the pencil to later occupy it with my touch screen.

  [Test Case]
  1. Open gnome-control-center
  2. Click on Wacom tablet
  3. Press the buttons of the pencil, touching the screen
  4. gnome-control-center crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.32.1-1ubuntu5
  Uname: Linux 5.1.0-050100rc7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 30 19:28:42 2019
  InstallationDate: Installed on 2018-12-02 (149 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1827154/+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 1825186] Re: gpgv-win32 autopkgtest always fails

[Dimitri John Ledkov]

This is not a regression in any stable releases, failing tests is not a
problem at all. As release and SRU processes only consider regressions
(previously passed, now failing). Things that have always failed are
treated as such by proposed-updates and the rest of the tooling ("always
failed"). This is exactly the same as FTBFS - only regressions count,
and we have many packages that have never built on certain arches.

SRU policy, Section 2 "When", has three major categories listing in
bullet points cases that are eligible for SRU.

Which one is this SRU submitted under?

https://wiki.ubuntu.com/StableReleaseUpdates#When

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

Title:
  gpgv-win32 autopkgtest always fails

Status in gnupg package in Ubuntu:
  Invalid
Status in gnupg2 package in Ubuntu:
  Opinion
Status in gnupg source package in Xenial:
  In Progress
Status in gnupg2 source package in Bionic:
  In Progress
Status in gnupg2 source package in Cosmic:
  In Progress
Status in gnupg2 source package in Disco:
  Fix Released

Bug description:
  [impact]

  gpgv-win32 autopkgtest always fails

  [test case]

  check http://autopkgtest.ubuntu.com/packages/g/gnupg2

  or run autopkgtest manually

  note the gpgv-win32 test is skipped on ppc64el and s390x for b/c, and
  has been removed from d/t/control entirely in d

  [regression potential]

  little to none; this affects the test case only

  [other info]

  as mentioned, in disco, the gpgv-win32 test has been removed from the
  tests/control completely.  not sure if that is a better approach than
  fixing the test case.  For now, I marked this Fix Released for disco
  since it doesn't fail there (since the testcase was removed).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1825186/+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 1781699] Re: DHCPv6 server crashes regularly (bionic)

[Alex Murray]

This looks like a possible use-after-free so likely has a security
impact (at a minimum it is a denial of service due to the crash,
especially if it can be triggered remotely) - I've reported it to ISC as
such who will hopefully assign a CVE and then we can fix it as a
security update. For future reference, the RT #48804 contains a patch
that should likely be fine for Bionic
https://bugs.isc.org/Public/Ticket/Attachment/534989/331007/46719.v4_3.diff

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

Title:
  DHCPv6 server crashes regularly (bionic)

Status in DHCP:
  Unknown
Status in isc-dhcp package in Ubuntu:
  Triaged
Status in isc-dhcp package in Debian:
  New
Status in isc-dhcp package in Fedora:
  Unknown

Bug description:
  The isc-dhcp-server crashes regularly on bionic, sometimes directly after 
boot, sometimes later.
  The version installed is 4.3.5-3ubuntu7.

  journalctl shows:
  Jul 14 09:35:11  dhcpd[1543]: Solicit message from 
fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x7E8EC00
  Jul 14 09:35:11  dhcpd[1543]: Advertise NA: address ::1998 
to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid 
for 8
  Jul 14 09:35:11  dhcpd[1543]: Sending Advertise to 
fe80::18eb:dfc7:17e5:c8d7 port 546
  Jul 14 09:35:12  dhcpd[1543]: Request message from 
fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x65FADB00
  Jul 14 09:35:12  dhcpd[1543]: Reply NA: address ::1998 to 
client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 
86400
  Jul 14 09:35:12  dhcpd[1543]: Sending Reply to 
fe80::18eb:dfc7:17e5:c8d7 port 546
  Jul 14 09:35:53  dhcpd[1543]: Confirm message from 
fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x5105F400
  Jul 14 09:35:53  dhcpd[1543]: Sending Reply to 
fe80::725a:b6ff:fea2:6120 port 546
  Jul 14 09:35:53  dhcpd[1543]: Rebind message from 
fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x1FEA7E00
  Jul 14 09:35:53  dhcpd[1543]: Reply NA: address ::1992 to 
client with duid 00:04:c2:47:10:e8:8b:dc:d4:a1:0a:1d:21:f2:be:20:e8:a0 iaid = 
-1230
  Jul 14 09:35:53  sh[1543]: ../../../lib/isc/heap.c:251: REQUIRE(idx 
>= 1 && idx <= heap->last) failed, back trace
  Jul 14 09:35:53  sh[1543]: #0 0x7efc458a6417 in ??
  Jul 14 09:35:53  sh[1543]: #1 0x7efc458a636a in ??
  Jul 14 09:35:53  sh[1543]: #2 0x7efc458ad4ea in ??
  Jul 14 09:35:53  sh[1543]: #3 0x55d9ee65d571 in ??
  Jul 14 09:35:53  sh[1543]: #4 0x55d9ee658701 in ??
  Jul 14 09:35:53  sh[1543]: #5 0x55d9ee65ab05 in ??
  Jul 14 09:35:53  sh[1543]: #6 0x55d9ee65bff3 in ??
  Jul 14 09:35:53  sh[1543]: #7 0x55d9ee65cafc in ??
  Jul 14 09:35:53  sh[1543]: #8 0x55d9ee678402 in ??
  Jul 14 09:35:53  sh[1543]: #9 0x55d9ee667463 in ??
  Jul 14 09:35:53  sh[1543]: #10 0x55d9ee696476 in ??
  Jul 14 09:35:53  sh[1543]: #11 0x7efc458dd73b in ??
  Jul 14 09:35:53  sh[1543]: #12 0x7efc458ccf9e in ??
  Jul 14 09:35:53  sh[1543]: #13 0x7efc458d1e60 in ??
  Jul 14 09:35:53  sh[1543]: #14 0x7efc458d2325 in ??
  Jul 14 09:35:53  sh[1543]: #15 0x55d9ee6696b0 in ??
  Jul 14 09:35:53  sh[1543]: #16 0x55d9ee61d519 in ??
  Jul 14 09:35:53  sh[1543]: #17 0x7efc454c6b97 in ??
  Jul 14 09:35:53  sh[1543]: #18 0x55d9ee61de0a in ??
  Jul 14 09:35:54  systemd[1]: isc-dhcp-server6.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 14 09:35:54  systemd[1]: isc-dhcp-server6.service: Failed with 
result 'core-dump'.

  The bug was reported to Debian independently, https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=896122.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1781699/+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 1825448] Re: gnupg2 autopkgtest 'simple-tests' should be included in x/b/c

[Dimitri John Ledkov]

SRU policy, Section 2 "When", has three major categories listing in
bullet points cases that are eligible for SRU.

Which one is this SRU submitted under?

https://wiki.ubuntu.com/StableReleaseUpdates#When

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

Title:
  gnupg2 autopkgtest 'simple-tests' should be included in x/b/c

Status in gnupg package in Ubuntu:
  Invalid
Status in gnupg2 package in Ubuntu:
  Fix Released
Status in gnupg source package in Xenial:
  In Progress
Status in gnupg2 source package in Xenial:
  In Progress
Status in gnupg2 source package in Bionic:
  In Progress
Status in gnupg2 source package in Cosmic:
  In Progress

Bug description:
  [impact]

  b/c currently only have gpgv-win32 test, which is limited in what it
  tests and what archs it runs on.  additionally, it always fails (see
  bug 1825186).

  x currently has no tests at all for gnupg or gnupg2.

  [test case]

  run autopkgtests for gnupg2 on b/c.

  [regession potential]

  adding a testcase may result in the testcase incorrectly failing in
  the future.

  [other info]

  this test case is cherry-picked from gnupg2 in disco.

  the test case required slight modification for gnupg v1, as 'Key-Type:
  default' only works with v2.  Note that Xenial is the last release
  that carries gnupg v1; Bionic and later carry only gnupg v2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1825448/+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 1825448] Re: gnupg2 autopkgtest 'simple-tests' should be included in x/b/c

[Dan Streetman]

> Adding new autopkgtests in stable series - not good.

Uh, why?  Personal opinion?

> I feel like rejecting the series tasks of this bug report.

I'm going to undo this, and suggest that if this is, in fact, SRU
policy, the actual SRU policy needs to be updated to indicate it.

If ~ubuntu-sru decides to actually reject my gnupg/gnupg2 uploads, then
please feel free to wontfix this at that time.  Until then please leave
it open.

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

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

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

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

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

Title:
  gnupg2 autopkgtest 'simple-tests' should be included in x/b/c

Status in gnupg package in Ubuntu:
  Invalid
Status in gnupg2 package in Ubuntu:
  Fix Released
Status in gnupg source package in Xenial:
  In Progress
Status in gnupg2 source package in Xenial:
  In Progress
Status in gnupg2 source package in Bionic:
  In Progress
Status in gnupg2 source package in Cosmic:
  In Progress

Bug description:
  [impact]

  b/c currently only have gpgv-win32 test, which is limited in what it
  tests and what archs it runs on.  additionally, it always fails (see
  bug 1825186).

  x currently has no tests at all for gnupg or gnupg2.

  [test case]

  run autopkgtests for gnupg2 on b/c.

  [regession potential]

  adding a testcase may result in the testcase incorrectly failing in
  the future.

  [other info]

  this test case is cherry-picked from gnupg2 in disco.

  the test case required slight modification for gnupg v1, as 'Key-Type:
  default' only works with v2.  Note that Xenial is the last release
  that carries gnupg v1; Bionic and later carry only gnupg v2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1825448/+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 1657646] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From sthou...@in.ibm.com 2019-05-02 02:06 EDT---
Canonical , Could you confirm which release this issue could be fixed ?

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

Title:
  Missing thin-provisioning-tools prevents VG with thin pool LV from
  being (de)activated, but not its creation

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 package in Debian:
  New

Bug description:
  Creating a thin pool LV is allowed even when thin-provisioning-tools
  is not installed. But deactivating or activating that VG fails. Since
  deactivating the VG usually only happens at reboot, the user might
  fail to notice this big problem until then.

  I think the lvconvert tool, used to combine the two "thin LVs" into a
  thin pool LV, should refuse to run if thin-provisioning-tools, or the
  needed scripts, aren't installed.

  Steps to reproduce:
  root@15-89:~# vgcreate vg /dev/vdb1
    Volume group "vg" successfully created

  root@15-89:~# vgs
    VG   #PV #LV #SN Attr   VSize  VFree
    vg 1   0   0 wz--n- 40.00g 40.00g

  root@15-89:~# lvcreate -n pool0 -l 90%VG vg
    Logical volume "pool0" created.

  root@15-89:~# lvcreate -n pool0meta -l 5%VG vg
    Logical volume "pool0meta" created.

  root@15-89:~# lvs
    LVVG   Attr   LSize  Pool Origin Data%  Meta%  Move Log 
Cpy%Sync Convert
    pool0 vg   -wi-a- 36.00g
    pool0meta vg   -wi-a-  2.00g

  root@15-89:~# ll /dev/mapper/
  total 0
  drwxr-xr-x  2 root root 100 Jun 21 14:15 ./
  drwxr-xr-x 20 root root3820 Jun 21 14:15 ../
  crw---  1 root root 10, 236 Jun 21 13:15 control
  lrwxrwxrwx  1 root root   7 Jun 21 14:14 vg-pool0 -> ../dm-0
  lrwxrwxrwx  1 root root   7 Jun 21 14:15 vg-pool0meta -> ../dm-1

  root@15-89:~# lvconvert --type thin-pool --poolmetadata vg/pool0meta vg/pool0
    WARNING: Converting logical volume vg/pool0 and vg/pool0meta to pool's data 
and metadata volumes.
    THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.)
  Do you really want to convert vg/pool0 and vg/pool0meta? [y/n]: y
    Converted vg/pool0 to thin pool.

  root@15-89:~# ll /dev/mapper/
  total 0
  drwxr-xr-x  2 root root 120 Jun 21 14:15 ./
  drwxr-xr-x 20 root root3840 Jun 21 14:15 ../
  crw---  1 root root 10, 236 Jun 21 13:15 control
  lrwxrwxrwx  1 root root   7 Jun 21 14:15 vg-pool0 -> ../dm-2
  lrwxrwxrwx  1 root root   7 Jun 21 14:15 vg-pool0_tdata -> ../dm-1
  lrwxrwxrwx  1 root root   7 Jun 21 14:15 vg-pool0_tmeta -> ../dm-0
  root@15-89:~# lvs -a
    LV  VG   Attr   LSize  Pool Origin Data%  Meta%  Move Log 
Cpy%S
  ync Convert
    [lvol0_pmspare] vg   ewi---  2.00g
    pool0   vg   twi-a-tz-- 36.00g 0.00   0.01
    [pool0_tdata]   vg   Twi-ao 36.00g
    [pool0_tmeta]   vg   ewi-ao  2.00g

  If you now reboot the system, all that is gone:
  root@15-89:~# ll /dev/mapper/
  total 0
  drwxr-xr-x  2 root root  60 Jun 21 14:28 ./
  drwxr-xr-x 19 root root3760 Jun 21 14:28 ../
  crw---  1 root root 10, 236 Jun 21 14:28 control

  The same happens if you deactivate the VG (which the reboot
  undoubtedly triggers). It fails because of a missing
  /usr/sbin/thin_check which is provided by the thin-provisioning-tools
  package:

  root@15-89:~# vgchange -a n
    /usr/sbin/thin_check: execvp failed: No such file or directory
    WARNING: Integrity check of metadata for pool vg/pool0 failed.
    0 logical volume(s) in volume group "vg" now active

  root@15-89:~# ll /dev/mapper/
  total 0
  drwxr-xr-x  2 root root  60 Jun 21 14:29 ./
  drwxr-xr-x 19 root root3760 Jun 21 14:29 ../
  crw---  1 root root 10, 236 Jun 21 14:28 control

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1657646/+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 1781699] Re: DHCPv6 server crashes regularly (bionic)

[Steffen Sledz]

It is really a shame that the fix of this bug in this basic network
infrastructure package has not made it into the distributions
(especially Ubuntu) after months. :(

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

Title:
  DHCPv6 server crashes regularly (bionic)

Status in DHCP:
  Unknown
Status in isc-dhcp package in Ubuntu:
  Triaged
Status in isc-dhcp package in Debian:
  New
Status in isc-dhcp package in Fedora:
  Unknown

Bug description:
  The isc-dhcp-server crashes regularly on bionic, sometimes directly after 
boot, sometimes later.
  The version installed is 4.3.5-3ubuntu7.

  journalctl shows:
  Jul 14 09:35:11  dhcpd[1543]: Solicit message from 
fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x7E8EC00
  Jul 14 09:35:11  dhcpd[1543]: Advertise NA: address ::1998 
to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid 
for 8
  Jul 14 09:35:11  dhcpd[1543]: Sending Advertise to 
fe80::18eb:dfc7:17e5:c8d7 port 546
  Jul 14 09:35:12  dhcpd[1543]: Request message from 
fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x65FADB00
  Jul 14 09:35:12  dhcpd[1543]: Reply NA: address ::1998 to 
client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 
86400
  Jul 14 09:35:12  dhcpd[1543]: Sending Reply to 
fe80::18eb:dfc7:17e5:c8d7 port 546
  Jul 14 09:35:53  dhcpd[1543]: Confirm message from 
fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x5105F400
  Jul 14 09:35:53  dhcpd[1543]: Sending Reply to 
fe80::725a:b6ff:fea2:6120 port 546
  Jul 14 09:35:53  dhcpd[1543]: Rebind message from 
fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x1FEA7E00
  Jul 14 09:35:53  dhcpd[1543]: Reply NA: address ::1992 to 
client with duid 00:04:c2:47:10:e8:8b:dc:d4:a1:0a:1d:21:f2:be:20:e8:a0 iaid = 
-1230
  Jul 14 09:35:53  sh[1543]: ../../../lib/isc/heap.c:251: REQUIRE(idx 
>= 1 && idx <= heap->last) failed, back trace
  Jul 14 09:35:53  sh[1543]: #0 0x7efc458a6417 in ??
  Jul 14 09:35:53  sh[1543]: #1 0x7efc458a636a in ??
  Jul 14 09:35:53  sh[1543]: #2 0x7efc458ad4ea in ??
  Jul 14 09:35:53  sh[1543]: #3 0x55d9ee65d571 in ??
  Jul 14 09:35:53  sh[1543]: #4 0x55d9ee658701 in ??
  Jul 14 09:35:53  sh[1543]: #5 0x55d9ee65ab05 in ??
  Jul 14 09:35:53  sh[1543]: #6 0x55d9ee65bff3 in ??
  Jul 14 09:35:53  sh[1543]: #7 0x55d9ee65cafc in ??
  Jul 14 09:35:53  sh[1543]: #8 0x55d9ee678402 in ??
  Jul 14 09:35:53  sh[1543]: #9 0x55d9ee667463 in ??
  Jul 14 09:35:53  sh[1543]: #10 0x55d9ee696476 in ??
  Jul 14 09:35:53  sh[1543]: #11 0x7efc458dd73b in ??
  Jul 14 09:35:53  sh[1543]: #12 0x7efc458ccf9e in ??
  Jul 14 09:35:53  sh[1543]: #13 0x7efc458d1e60 in ??
  Jul 14 09:35:53  sh[1543]: #14 0x7efc458d2325 in ??
  Jul 14 09:35:53  sh[1543]: #15 0x55d9ee6696b0 in ??
  Jul 14 09:35:53  sh[1543]: #16 0x55d9ee61d519 in ??
  Jul 14 09:35:53  sh[1543]: #17 0x7efc454c6b97 in ??
  Jul 14 09:35:53  sh[1543]: #18 0x55d9ee61de0a in ??
  Jul 14 09:35:54  systemd[1]: isc-dhcp-server6.service: Main process 
exited, code=dumped, status=6/ABRT
  Jul 14 09:35:54  systemd[1]: isc-dhcp-server6.service: Failed with 
result 'core-dump'.

  The bug was reported to Debian independently, https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=896122.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1781699/+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 1827328] [NEW] ModemManager does not honor blacklisted ttys (ID_MM_DEVICE_IGNORE)

[Tommy Vestermark]

Public bug reported:

In Ubuntu 19.04 (and likely earlier) Modem Manager is installed with
filter policy 'strict' as opposed to 'default', which actually makes
Modem Manager _less_ strict regarding explicitly blacklisted ttys (see
man modemmanager).

This means that ttys, that are explicitly blacklisted from Modem Manager
by using ENV{ID_MM_DEVICE_IGNORE}="1" in its udev rule is still opened
and probed by Modem Manager although it should not.

This is a common cause of problems and frustrations for people working
with actual serial devices, e.g. within embedded development (e.g.
Arduino and the like). See https://nick.zoic.org/art/failed-to-set-dtr-
rts-systemd-modemmanager/ for an example.

A proposed solution is to change the following line in: 
/lib/systemd/system/ModemManager.service
from:
ExecStart=/usr/sbin/ModemManager --filter-policy=strict
to:
ExecStart=/usr/sbin/ModemManager --filter-policy=paranoid

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: modemmanager 1.10.0-1 [modified: 
lib/systemd/system/ModemManager.service]
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May  2 15:35:58 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-05-26 (340 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: modemmanager
UpgradeStatus: Upgraded to disco on 2019-04-18 (13 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  ModemManager does not honor blacklisted ttys (ID_MM_DEVICE_IGNORE)

Status in modemmanager package in Ubuntu:
  New

Bug description:
  In Ubuntu 19.04 (and likely earlier) Modem Manager is installed with
  filter policy 'strict' as opposed to 'default', which actually makes
  Modem Manager _less_ strict regarding explicitly blacklisted ttys (see
  man modemmanager).

  This means that ttys, that are explicitly blacklisted from Modem
  Manager by using ENV{ID_MM_DEVICE_IGNORE}="1" in its udev rule is
  still opened and probed by Modem Manager although it should not.

  This is a common cause of problems and frustrations for people working
  with actual serial devices, e.g. within embedded development (e.g.
  Arduino and the like). See https://nick.zoic.org/art/failed-to-set-
  dtr-rts-systemd-modemmanager/ for an example.

  A proposed solution is to change the following line in: 
/lib/systemd/system/ModemManager.service
  from:
  ExecStart=/usr/sbin/ModemManager --filter-policy=strict
  to:
  ExecStart=/usr/sbin/ModemManager --filter-policy=paranoid

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: modemmanager 1.10.0-1 [modified: 
lib/systemd/system/ModemManager.service]
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 15:35:58 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-26 (340 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to disco on 2019-04-18 (13 days ago)

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