[Touch-packages] [Bug 1876238] Re: [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to 20.04 LTS Focal

[Hui Wang]

*** This bug is a duplicate of bug 1875252 ***
https://bugs.launchpad.net/bugs/1875252

this is a duplicate bug of #1875252, please help collect the log
according to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/comments/5

thx.

** This bug has been marked a duplicate of bug 1875252
   Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

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

Title:
  [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal
  Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to
  20.04 LTS Focal

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal speakers were working fine until I upgraded the system from
  19.10 LTS to 20.04 LTS on April 23, 2020.

  Uninstalled and reinstalled alsamixer and pavucontrol, but of no use.

  Killed pavucontrol and reloaded alsamixer numerous times, but of no
  use. (`pulseaudio -k && sudo alsa force-reload`)

  Waited for two kernel updates, but of no use. Presently on 5.4.0-29.

  Tried upgrading the kernel even up to 5.6, but of no use.

  The Intel sound card is not getting detected.

  Tried every trick like adding "options snd-hda-intel dmic_detect=0" in
  the /etc/modprobe.d/alsa-base.conf, but of no use.

  Out of the two external audio output sockets for headphone, one is
  working. So I can either connect a headphone or an external speaker to
  this jack to tide over the crisis for the time being.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj   10952 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  1 09:54:23 2020
  InstallationDate: Installed on 2016-12-20 (1227 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj   10952 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-26T17:25:43.583147

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876238/+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 1876238] [NEW] [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to 20.04 LTS Focal

[Rajasekharan N]

Public bug reported:

Internal speakers were working fine until I upgraded the system from
19.10 LTS to 20.04 LTS on April 23, 2020.

Uninstalled and reinstalled alsamixer and pavucontrol, but of no use.

Killed pavucontrol and reloaded alsamixer numerous times, but of no use.
(`pulseaudio -k && sudo alsa force-reload`)

Waited for two kernel updates, but of no use. Presently on 5.4.0-29.

Tried upgrading the kernel even up to 5.6, but of no use.

The Intel sound card is not getting detected.

Tried every trick like adding "options snd-hda-intel dmic_detect=0" in
the /etc/modprobe.d/alsa-base.conf, but of no use.

Out of the two external audio output sockets for headphone, one is
working. So I can either connect a headphone or an external speaker to
this jack to tide over the crisis for the time being.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  raj   10952 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May  1 09:54:23 2020
InstallationDate: Installed on 2016-12-20 (1227 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  raj   10952 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/27/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-26T17:25:43.583147

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


** Tags: amd64 apport-bug focal

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

Title:
  [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal
  Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to
  20.04 LTS Focal

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal speakers were working fine until I upgraded the system from
  19.10 LTS to 20.04 LTS on April 23, 2020.

  Uninstalled and reinstalled alsamixer and pavucontrol, but of no use.

  Killed pavucontrol and reloaded alsamixer numerous times, but of no
  use. (`pulseaudio -k && sudo alsa force-reload`)

  Waited for two kernel updates, but of no use. Presently on 5.4.0-29.

  Tried upgrading the kernel even up to 5.6, but of no use.

  The Intel sound card is not getting detected.

  Tried every trick like adding "options snd-hda-intel dmic_detect=0" in
  the /etc/modprobe.d/alsa-base.conf, but of no use.

  Out of the two external audio output sockets for headphone, one is
  working. So I can either connect a headphone or an external speaker to
  this jack to tide over the crisis for the time being.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj   10952 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  1 09:54:23 2020
  InstallationDate: Installed on 2016-12-20 (1227 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj   10952 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1876237] [NEW] QDesktopServices::openUrl() fails when called on local files from within a snap

[James Henstridge]

Public bug reported:

This is something we might want to fix to help people who build snaps
based on Focal's Qt.

The QGenericUnixServices implementation of openUrl() passes an O_PATH
file descriptor to xdg-desktop-portal when it detects it is running
under snap confinement.  This is rejected because xdg-desktop-portal
expects an O_RDONLY file descriptor, leading to the operation failing.
More details are available in the upstream bug report I filed:

https://bugreports.qt.io/browse/QTBUG-83939

This originated from a report on the Snapcraft forum here:

https://forum.snapcraft.io/t/xdg-open-or-gvfs-open-qdesktopservices-
openurl-file-somelocation-file-txt-wont-open-the-file/16824?u=jamesh

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  QDesktopServices::openUrl() fails when called on local files from
  within a snap

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  This is something we might want to fix to help people who build snaps
  based on Focal's Qt.

  The QGenericUnixServices implementation of openUrl() passes an O_PATH
  file descriptor to xdg-desktop-portal when it detects it is running
  under snap confinement.  This is rejected because xdg-desktop-portal
  expects an O_RDONLY file descriptor, leading to the operation failing.
  More details are available in the upstream bug report I filed:

  https://bugreports.qt.io/browse/QTBUG-83939

  This originated from a report on the Snapcraft forum here:

  https://forum.snapcraft.io/t/xdg-open-or-gvfs-open-qdesktopservices-
  openurl-file-somelocation-file-txt-wont-open-the-file/16824?u=jamesh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1876237/+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 1876228] Re: screen goes blank for few seconds when there is new audio activity

[Daniel van Vugt]

Seems there's a growing list of these bugs. Bug 1875254 is in progress
but see also: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=ice-
lake-flicker

** Tags added: ice-lake-flicker

** Summary changed:

- screen goes blank for few seconds when there is new audio activity
+ [Ice Lake] screen goes blank for few seconds when there is new audio activity

** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)

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

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

Title:
  [Ice Lake] screen goes blank for few seconds when there is new audio
  activity

Status in linux package in Ubuntu:
  New

Bug description:
  I noticed this after installing 20.04.
  At the beginning of new audio activity (playing video or generting system 
sounds eg. terminal bell) screen goes blank for few seconds.I can also 
reproduce it by opening settings in gnome and going to audio section.

  The pulseadio in -vvv mode is attached around one of these events.
  This might not be entirely a pulseadio issue, so appreciate a pointer on how 
to narrow it down to the source of the issue.

  More info:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3
    Candidate: 1:13.99.1-1ubuntu3
    Version table:
   *** 1:13.99.1-1ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  -H
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demystifier   4382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-23 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876228/+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 1876219] Re: iris driver for old cpu

[Chenxi Wu]

** Package changed: ubuntu => mesa (Ubuntu)

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

Title:
  iris driver for old cpu

Status in mesa package in Ubuntu:
  New

Bug description:
  I am not completely sure where I should file the bug. I am using
  Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the
  default graphics driver, which results in crashes in multiple apps
  including guvcview and calibre. Setting
  MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but
  is it true that iris does not support older generations of Intel CPUs?
  If it is the case would it be possible to revert to i965 in those
  circumstances? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1876219/+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 1876219] [NEW] iris driver for old cpu

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I am not completely sure where I should file the bug. I am using Lubuntu
20.04 with lxqt, and since the upgrade to 20.04 iris is the default
graphics driver, which results in crashes in multiple apps including
guvcview and calibre. Setting MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the
problem. I am not sure but is it true that iris does not support older
generations of Intel CPUs? If it is the case would it be possible to
revert to i965 in those circumstances? Thanks!

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


** Tags: bot-comment
-- 
iris driver for old cpu
https://bugs.launchpad.net/bugs/1876219
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mesa in Ubuntu.

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

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

[Hossein Lotfi]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1876228/+attachment/5364292/+files/CurrentDmesg.txt

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

Title:
  screen goes blank for few seconds when there is new audio activity

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I noticed this after installing 20.04.
  At the beginning of new audio activity (playing video or generting system 
sounds eg. terminal bell) screen goes blank for few seconds.I can also 
reproduce it by opening settings in gnome and going to audio section.

  The pulseadio in -vvv mode is attached around one of these events.
  This might not be entirely a pulseadio issue, so appreciate a pointer on how 
to narrow it down to the source of the issue.

  More info:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3
    Candidate: 1:13.99.1-1ubuntu3
    Version table:
   *** 1:13.99.1-1ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  -H
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demystifier   4382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-23 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876228/+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 1876228] PulseList.txt

[Hossein Lotfi]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1876228/+attachment/5364296/+files/PulseList.txt

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

Title:
  screen goes blank for few seconds when there is new audio activity

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I noticed this after installing 20.04.
  At the beginning of new audio activity (playing video or generting system 
sounds eg. terminal bell) screen goes blank for few seconds.I can also 
reproduce it by opening settings in gnome and going to audio section.

  The pulseadio in -vvv mode is attached around one of these events.
  This might not be entirely a pulseadio issue, so appreciate a pointer on how 
to narrow it down to the source of the issue.

  More info:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3
    Candidate: 1:13.99.1-1ubuntu3
    Version table:
   *** 1:13.99.1-1ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  -H
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demystifier   4382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-23 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876228/+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 1876228] ProcEnviron.txt

[Hossein Lotfi]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1876228/+attachment/5364295/+files/ProcEnviron.txt

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

Title:
  screen goes blank for few seconds when there is new audio activity

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I noticed this after installing 20.04.
  At the beginning of new audio activity (playing video or generting system 
sounds eg. terminal bell) screen goes blank for few seconds.I can also 
reproduce it by opening settings in gnome and going to audio section.

  The pulseadio in -vvv mode is attached around one of these events.
  This might not be entirely a pulseadio issue, so appreciate a pointer on how 
to narrow it down to the source of the issue.

  More info:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3
    Candidate: 1:13.99.1-1ubuntu3
    Version table:
   *** 1:13.99.1-1ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  -H
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demystifier   4382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-23 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876228/+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 1876228] ProcCpuinfoMinimal.txt

[Hossein Lotfi]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1876228/+attachment/5364294/+files/ProcCpuinfoMinimal.txt

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

Title:
  screen goes blank for few seconds when there is new audio activity

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I noticed this after installing 20.04.
  At the beginning of new audio activity (playing video or generting system 
sounds eg. terminal bell) screen goes blank for few seconds.I can also 
reproduce it by opening settings in gnome and going to audio section.

  The pulseadio in -vvv mode is attached around one of these events.
  This might not be entirely a pulseadio issue, so appreciate a pointer on how 
to narrow it down to the source of the issue.

  More info:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3
    Candidate: 1:13.99.1-1ubuntu3
    Version table:
   *** 1:13.99.1-1ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  -H
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demystifier   4382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-23 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876228/+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 1876228] Dependencies.txt

[Hossein Lotfi]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1876228/+attachment/5364293/+files/Dependencies.txt

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

Title:
  screen goes blank for few seconds when there is new audio activity

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I noticed this after installing 20.04.
  At the beginning of new audio activity (playing video or generting system 
sounds eg. terminal bell) screen goes blank for few seconds.I can also 
reproduce it by opening settings in gnome and going to audio section.

  The pulseadio in -vvv mode is attached around one of these events.
  This might not be entirely a pulseadio issue, so appreciate a pointer on how 
to narrow it down to the source of the issue.

  More info:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3
    Candidate: 1:13.99.1-1ubuntu3
    Version table:
   *** 1:13.99.1-1ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  -H
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demystifier   4382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-23 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876228/+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 1876228] Re: screen goes blank for few seconds when there is new audio activity

[Hossein Lotfi]

apport information

** Tags added: apport-collected

** Description changed:

  I noticed this after installing 20.04.
  At the beginning of new audio activity (playing video or generting system 
sounds eg. terminal bell) screen goes blank for few seconds.I can also 
reproduce it by opening settings in gnome and going to audio section.
  
  The pulseadio in -vvv mode is attached around one of these events.
  This might not be entirely a pulseadio issue, so appreciate a pointer on how 
to narrow it down to the source of the issue.
  
  More info:
  
  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3
    Candidate: 1:13.99.1-1ubuntu3
    Version table:
   *** 1:13.99.1-1ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  
  -H
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  demystifier   4382 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-04-23 (7 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ Package: pulseaudio 1:13.99.1-1ubuntu3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
+ Tags:  focal
+ Uname: Linux 5.4.0-28-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 02/26/2020
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.0.7
+ dmi.board.name: 077Y9N
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: XPS
+ dmi.product.name: XPS 13 9300
+ dmi.product.sku: 096D
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1876228/+attachment/5364291/+files/AlsaInfo.txt

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

Title:
  screen goes blank for few seconds when there is new audio activity

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I noticed this after installing 20.04.
  At the beginning of new audio activity (playing video or generting system 
sounds eg. terminal bell) screen goes blank for few seconds.I can also 
reproduce it by opening settings in gnome and going to audio section.

  The pulseadio in -vvv mode is attached around one of these events.
  This might not be entirely a pulseadio issue, so appreciate a pointer on how 
to narrow it down to the source of the issue.

  More info:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3
    Candidate: 1:13.99.1-1ubuntu3
    Version table:
   *** 1:13.99.1-1ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  -H
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demystifier   4382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-23 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876228/+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 1876230] Re: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED

[Matthew Ruffell]

Attached is a debdiff for Bionic

** Patch added: "liburcu debdiff for Bionic"
   
https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/1876230/+attachment/5364290/+files/lp1876230_bionic.debdiff

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

Title:
  liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address
  performance problems with MEMBARRIER_CMD_SHARED

Status in liburcu package in Ubuntu:
  Fix Released
Status in liburcu source package in Bionic:
  In Progress

Bug description:
  [Impact]

  In Linux 4.3, a new syscall was defined, called "membarrier". This
  systemcall was defined specifically for use in userspace-rcu (liburcu)
  to speed up the fast path / reader side of the library. The original
  implementation in Linux 4.3 only supported the MEMBARRIER_CMD_SHARED
  subcommand of the membarrier syscall.

  MEMBARRIER_CMD_SHARED executes a memory barrier on all threads from
  all processes running on the system. When it exits, the userspace
  thread which called it is guaranteed that all running threads share
  the same world view in regards to userspace addresses which are
  consumed by readers and writers.

  The problem with MEMBARRIER_CMD_SHARED is system calls made in this
  fashion can block, since it deploys a barrier across all threads in a
  system, and some other threads can be waiting on blocking operations,
  and take time to reach the barrier.

  In Linux 4.14, this was addressed by adding the
  MEMBARRIER_CMD_PRIVATE_EXPEDITED command to the membarrier syscall. It
  only targets threads which share the same mm as the thread calling the
  membarrier syscall, aka, threads in the current process, and not all
  threads / processes in the system.

  Calls to membarrier with the MEMBARRIER_CMD_PRIVATE_EXPEDITED command
  are guaranteed non-blocking, due to using inter-processor interrupts
  to implement memory barriers.

  Because of this, membarrier calls that use
  MEMBARRIER_CMD_PRIVATE_EXPEDITED are much faster than those that use
  MEMBARRIER_CMD_SHARED.

  Since Bionic uses a 4.15 kernel, all kernel requirements are met, and
  this SRU is to enable support for MEMBARRIER_CMD_PRIVATE_EXPEDITED in
  the liburcu package.

  This brings the performance of the liburcu library back in line to
  where it was in Trusty, as this particular user has performance
  problems upon upgrading from Trusty to Bionic.

  [Test]

  Testing performance is heavily dependant on the application which
  links against liburcu, and the workload which it executes.

  A test package is available in the following ppa:
  https://launchpad.net/~mruffell/+archive/ubuntu/sf276198-test

  For the sake of testing, we can use the benchmarks provided in the
  liburcu source code. Download a copy of the source code for liburcu
  either from the repos or from github:

  $ pull-lp-source liburcu bionic
  # OR
  $ git clone https://github.com/urcu/userspace-rcu.git
  $ git checkout v0.10.1 # version in bionic

  Build the code:

  $ ./bootstrap
  $ ./configure
  $ make

  Go into the tests/benchmark directory

  $ cd tests/benchmark

  From there, you can run benchmarks for the four main usages of
  liburcu: urcu, urcu-bp, urcu-signal and urcu-mb.

  On a 8 core machine, 6 threads for readers and 2 threads for writers,
  with a 10 second runtime, execute:

  $ ./test_urcu 6 2 10
  $ ./test_urcu_bp 6 2 10
  $ ./test_urcu_signal 6 2 10
  $ ./test_urcu_mb 6 2 10

  Results:

  ./test_urcu 6 2 10
  0.10.1-1: 17612527667 reads, 268 writes, 17612527935 ops
  0.10.1-1ubuntu1: 14988437247 reads, 810069 writes, 14989247316 ops

  $ ./test_urcu_bp 6 2 10
  0.10.1-1: 1177891079 reads, 1699523 writes, 1179590602 ops
  0.10.1-1ubuntu1: 13230354737 reads, 575314 writes, 13230930051 ops

  $ ./test_urcu_signal 6 2 10
  0.10.1-1: 20128392417 reads, 6859 writes, 20128399276 ops
  0.10.1-1ubuntu1: 20501430707 reads, 6890 writes, 20501437597 ops

  $ ./test_urcu_mb 6 2 10
  0.10.1-1: 627996563 reads, 5409563 writes, 633406126 ops
  0.10.1-1ubuntu1: 653194752 reads, 4590020 writes, 657784772 ops

  The SRU only changes behaviour for urcu and urcu-bp, since they are
  the only "flavours" of liburcu which the patches change. From a pure
  ops standpoint:

  $ ./test_urcu 6 2 10
  17612527935 ops
  14989247316 ops

  $ ./test_urcu_bp 6 2 10
  1179590602 ops
  13230930051 ops

  We see that this particular benchmark workload, test_urcu sees extra
  performance overhead with MEMBARRIER_CMD_PRIVATE_EXPEDITED, which is
  explained by the extra impact that it has on the slowpath, and the
  extra amount of writes it did during my benchmark.

  The real winner in this benchmark workload is test_urcu_bp, which sees
  a 10x performance increase with MEMBARRIER_CMD_PRIVATE_EXPEDITED. Some
  of this may be down to the 3x less writes it did during my benchmark.

  Again, these benchmarks are indicative only are very 

[Touch-packages] [Bug 1876228] Re: screen goes blank for few seconds when there is new audio activity

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1876228

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Tags added: focal

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

Title:
  screen goes blank for few seconds when there is new audio activity

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I noticed this after installing 20.04.
  At the beginning of new audio activity (playing video or generting system 
sounds eg. terminal bell) screen goes blank for few seconds.I can also 
reproduce it by opening settings in gnome and going to audio section.

  The pulseadio in -vvv mode is attached around one of these events.
  This might not be entirely a pulseadio issue, so appreciate a pointer on how 
to narrow it down to the source of the issue.

  More info:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3
    Candidate: 1:13.99.1-1ubuntu3
    Version table:
   *** 1:13.99.1-1ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  -H

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876228/+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 1876170] Re: Monitor setups including portrait orinted monitors cause horizontal resolution to increase

[Daniel van Vugt]

I experienced the same weird unwanted screen panning with the Nvidia-440
driver today. But in my case only a single monitor is connected.

I suspect the new fractional scaling feature might be related. I was
able to fix it by deleting ~/.config/monitors.xml though next time it
happens I will be sure to analyse the file and see what's wrong it it.


** Tags added: multimonitor nvidia

** Summary changed:

- Monitor setups including portrait orinted monitors cause horizontal 
resolution to increase
+ [nvidia] Monitor setups including portrait orinted monitors cause horizontal 
resolution to increase

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440
(Ubuntu)

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

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: 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/1876170

Title:
  [nvidia] Monitor setups including portrait orinted monitors cause
  horizontal resolution to increase

Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  With a multi-monitor setup that includes one portrait oriented screen,
  most of the time several of the monitors end up with extended
  horizontal resolution to the right, resulting in panning when you move
  the mouse, as well as overlap between the screen areas.

  I can occasionally make it behave after some enabling, disabling and
  orientation changes of the monitors, but seemingly only if I have them
  all in a row and don't have the portrait one furthest to the right.

  Attempted setup that breaks:
   ---
  |1920x1080  |
  |nvidia egpu|1080|
   --- --- ---|x   |
  |2560x1440  |1920x1080  |1920x1080  |1920|
  |laptop internal|nvidia egpu|nvidia egpu|egpu|
  |   |--- --- 
   --- 

  Also attached screenshot that should illustrate the issue well.

  I can't tell for sure if this is an xorg issue or a nvidia one, I did
  look at both arandr and nvidia-settings and in neither can I see
  anything amiss.

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 30 20:18:43 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
   NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU104 [GeForce RTX 2070 SUPER] [1043:8727]
  InstallationDate: Installed on 2020-04-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20L5CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5CTO1WW
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: 

[Touch-packages] [Bug 1876230] [NEW] liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED

[Matthew Ruffell]

Public bug reported:

[Impact]

In Linux 4.3, a new syscall was defined, called "membarrier". This
systemcall was defined specifically for use in userspace-rcu (liburcu)
to speed up the fast path / reader side of the library. The original
implementation in Linux 4.3 only supported the MEMBARRIER_CMD_SHARED
subcommand of the membarrier syscall.

MEMBARRIER_CMD_SHARED executes a memory barrier on all threads from all
processes running on the system. When it exits, the userspace thread
which called it is guaranteed that all running threads share the same
world view in regards to userspace addresses which are consumed by
readers and writers.

The problem with MEMBARRIER_CMD_SHARED is system calls made in this
fashion can block, since it deploys a barrier across all threads in a
system, and some other threads can be waiting on blocking operations,
and take time to reach the barrier.

In Linux 4.14, this was addressed by adding the
MEMBARRIER_CMD_PRIVATE_EXPEDITED command to the membarrier syscall. It
only targets threads which share the same mm as the thread calling the
membarrier syscall, aka, threads in the current process, and not all
threads / processes in the system.

Calls to membarrier with the MEMBARRIER_CMD_PRIVATE_EXPEDITED command
are guaranteed non-blocking, due to using inter-processor interrupts to
implement memory barriers.

Because of this, membarrier calls that use
MEMBARRIER_CMD_PRIVATE_EXPEDITED are much faster than those that use
MEMBARRIER_CMD_SHARED.

Since Bionic uses a 4.15 kernel, all kernel requirements are met, and
this SRU is to enable support for MEMBARRIER_CMD_PRIVATE_EXPEDITED in
the liburcu package.

This brings the performance of the liburcu library back in line to where
it was in Trusty, as this particular user has performance problems upon
upgrading from Trusty to Bionic.

[Test]

Testing performance is heavily dependant on the application which links
against liburcu, and the workload which it executes.

A test package is available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf276198-test

For the sake of testing, we can use the benchmarks provided in the
liburcu source code. Download a copy of the source code for liburcu
either from the repos or from github:

$ pull-lp-source liburcu bionic
# OR
$ git clone https://github.com/urcu/userspace-rcu.git
$ git checkout v0.10.1 # version in bionic

Build the code:

$ ./bootstrap
$ ./configure
$ make

Go into the tests/benchmark directory

$ cd tests/benchmark

>From there, you can run benchmarks for the four main usages of liburcu:
urcu, urcu-bp, urcu-signal and urcu-mb.

On a 8 core machine, 6 threads for readers and 2 threads for writers,
with a 10 second runtime, execute:

$ ./test_urcu 6 2 10
$ ./test_urcu_bp 6 2 10
$ ./test_urcu_signal 6 2 10
$ ./test_urcu_mb 6 2 10

Results:

./test_urcu 6 2 10
0.10.1-1: 17612527667 reads, 268 writes, 17612527935 ops
0.10.1-1ubuntu1: 14988437247 reads, 810069 writes, 14989247316 ops

$ ./test_urcu_bp 6 2 10
0.10.1-1: 1177891079 reads, 1699523 writes, 1179590602 ops
0.10.1-1ubuntu1: 13230354737 reads, 575314 writes, 13230930051 ops

$ ./test_urcu_signal 6 2 10
0.10.1-1: 20128392417 reads, 6859 writes, 20128399276 ops
0.10.1-1ubuntu1: 20501430707 reads, 6890 writes, 20501437597 ops

$ ./test_urcu_mb 6 2 10
0.10.1-1: 627996563 reads, 5409563 writes, 633406126 ops
0.10.1-1ubuntu1: 653194752 reads, 4590020 writes, 657784772 ops

The SRU only changes behaviour for urcu and urcu-bp, since they are the
only "flavours" of liburcu which the patches change. From a pure ops
standpoint:

$ ./test_urcu 6 2 10
17612527935 ops
14989247316 ops

$ ./test_urcu_bp 6 2 10
1179590602 ops
13230930051 ops

We see that this particular benchmark workload, test_urcu sees extra
performance overhead with MEMBARRIER_CMD_PRIVATE_EXPEDITED, which is
explained by the extra impact that it has on the slowpath, and the extra
amount of writes it did during my benchmark.

The real winner in this benchmark workload is test_urcu_bp, which sees a
10x performance increase with MEMBARRIER_CMD_PRIVATE_EXPEDITED. Some of
this may be down to the 3x less writes it did during my benchmark.

Again, these benchmarks are indicative only are very "random".
Performance is really dependant on the application which links against
liburcu and its workload.

[Regression Potential]

This SRU changes the behaviour of the following libraries which
applications link against: -lurcu and -lurcu-bp. Behaviour is not
changed in the rest: -lurcu-qsbr, -lucru-signal and -lucru-mb.

On Bionic, liburcu will call the membarrier syscall in urcu and urcu-bp.
This does not change. What is changing is the semantics of that syscall,
from MEMBARRIER_CMD_SHARED to MEMBARRIER_CMD_PRIVATE_EXPEDITED. The
changed code is all run in kernel space and resides in the kernel. These
commits simply change the parameters which are supplied to the
membarrier syscall from liburcu.

I have run the testsuite that comes with the Bionic source code, and
"make 

[Touch-packages] [Bug 1876119] Re: xinit won't start without root privileges

[Daniel van Vugt]

It seems to work well with Intel graphics. Though I have seen similar
problems with the Nvidia driver in the past so this might be specific to
your amdgpu driver...

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

** Summary changed:

- xinit won't start without root privileges
+ [amdgpu] xinit won't start without root privileges

** Tags added: amdgpu

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

Title:
  [amdgpu] xinit won't start without root privileges

Status in xinit package in Ubuntu:
  New

Bug description:
  When attempting to start xinit as a regular user, I simply get the
  error I don't have access rights to /dev/tty0

  Even setting setuid and setgid bits on /usr/bin/Xorg or chmod 666 on
  /dev/tty0 doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Apr 30 14:43:26 2020
  DistUpgraded: 2020-04-30 09:29:06,278 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon R5 Graphics 
[1002:1871]
  InstallationDate: Installed on 2019-12-21 (130 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  Lsusb:
   Bus 001 Device 003: ID 041e:324d Creative Technology, Ltd 
   Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Root Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HPE ProLiant MicroServer Gen10
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=dd6b3468-5d78-4b6e-960c-d9e3e418d8dc ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-04-30 (0 days ago)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Default string
  dmi.board.name: ProLiant MicroServer Gen10
  dmi.board.vendor: HPE
  dmi.board.version: 871721-001
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: HPE
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/02/2018:svnHPE:pnProLiantMicroServerGen10:pvrRevB:rvnHPE:rnProLiantMicroServerGen10:rvr871721-001:cvnHPE:ct1:cvrDefaultstring:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen10
  dmi.product.sku: 873830-421
  dmi.product.version: Rev B
  dmi.sys.vendor: HPE
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1876119/+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 1876228] Re: screen goes blank for few seconds when there is new audio activity

[Hossein Lotfi]

pactl list output is attached

** Attachment added: "pactl-list.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876228/+attachment/5364288/+files/pactl-list.txt

** Description changed:

- I noticed this after installing 20.04. 
- At the beginning of new audio activity (playing video or getting system 
sounds) screen goes blank for few seconds.I can also reproduce it by opening 
settings in gnome and going to audio section. 
+ I noticed this after installing 20.04.
+ At the beginning of new audio activity (playing video or generting system 
sounds eg. terminal bell) screen goes blank for few seconds.I can also 
reproduce it by opening settings in gnome and going to audio section.
  
- 
- The pulseadio in -vvv mode is attached around one of these events. 
- This might not be entirely a pulseadio issue, so appreciate a pointer on how 
to narrow it down to the source of the issue. 
+ The pulseadio in -vvv mode is attached around one of these events.
+ This might not be entirely a pulseadio issue, so appreciate a pointer on how 
to narrow it down to the source of the issue.
  
  More info:
  
  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  $ apt-cache policy pulseaudio
  pulseaudio:
-   Installed: 1:13.99.1-1ubuntu3
-   Candidate: 1:13.99.1-1ubuntu3
-   Version table:
-  *** 1:13.99.1-1ubuntu3 500
- 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1:13.99.1-1ubuntu3
+   Candidate: 1:13.99.1-1ubuntu3
+   Version table:
+  *** 1:13.99.1-1ubuntu3 500
+ 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  -H

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

Title:
  screen goes blank for few seconds when there is new audio activity

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I noticed this after installing 20.04.
  At the beginning of new audio activity (playing video or generting system 
sounds eg. terminal bell) screen goes blank for few seconds.I can also 
reproduce it by opening settings in gnome and going to audio section.

  The pulseadio in -vvv mode is attached around one of these events.
  This might not be entirely a pulseadio issue, so appreciate a pointer on how 
to narrow it down to the source of the issue.

  More info:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3
    Candidate: 1:13.99.1-1ubuntu3
    Version table:
   *** 1:13.99.1-1ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  -H

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876228/+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 1876228] [NEW] screen goes blank for few seconds when there is new audio activity

[Hossein Lotfi]

Public bug reported:

I noticed this after installing 20.04.
At the beginning of new audio activity (playing video or generting system 
sounds eg. terminal bell) screen goes blank for few seconds.I can also 
reproduce it by opening settings in gnome and going to audio section.

The pulseadio in -vvv mode is attached around one of these events.
This might not be entirely a pulseadio issue, so appreciate a pointer on how to 
narrow it down to the source of the issue.

More info:

$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04
$ apt-cache policy pulseaudio
pulseaudio:
  Installed: 1:13.99.1-1ubuntu3
  Candidate: 1:13.99.1-1ubuntu3
  Version table:
 *** 1:13.99.1-1ubuntu3 500
500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

-H

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

** Attachment added: "pulsaudio-log.txt"
   
https://bugs.launchpad.net/bugs/1876228/+attachment/5364287/+files/pulsaudio-log.txt

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

Title:
  screen goes blank for few seconds when there is new audio activity

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I noticed this after installing 20.04.
  At the beginning of new audio activity (playing video or generting system 
sounds eg. terminal bell) screen goes blank for few seconds.I can also 
reproduce it by opening settings in gnome and going to audio section.

  The pulseadio in -vvv mode is attached around one of these events.
  This might not be entirely a pulseadio issue, so appreciate a pointer on how 
to narrow it down to the source of the issue.

  More info:

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  $ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3
    Candidate: 1:13.99.1-1ubuntu3
    Version table:
   *** 1:13.99.1-1ubuntu3 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  -H

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876228/+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 1876171] Re: Falla en la barra de tareas

[Daniel van Vugt]

I have seen this bug before in other peoples' screenshots but it's never
been discussed itself...

It looks like it might be caused by your gnome-shell extension(s).
Please uninstall all extensions, restart, and then tell us if the
problem persists.

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (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/1876171

Title:
  Falla en la barra de tareas

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  la barra de tareas esta desfasada y en ocasiones provoca problemas
  para cerrar o minimizar una ventana. solo es estético. las letras
  estan fuera de la barra de tareas. saludos

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 30 14:01:53 2020
  DistUpgraded: 2020-04-30 08:36:59,642 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1854]
  InstallationDate: Installed on 2019-09-28 (215 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 003: ID 05c8:0348 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 240 G1 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=39b4235a-82d9-40c7-9f0a-9e5d96bc5839 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-30 (0 days ago)
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.3A
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.2A
  dmi.chassis.asset.tag: 5CG3374CS4
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.3A:bd06/13/2013:svnHewlett-Packard:pnHP240G1NotebookPC:pvr088013305B1610110:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP 240 G1 Notebook PC
  dmi.product.sku: E1Z19LT#ABM
  dmi.product.version: 088013305B1610110
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2019-10-06T16:32:19.326556
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876171/+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 1876211] Re: Bluetooth connection to headset works for volume buttons but not tests

[Daniel van Vugt]

*** This bug is a duplicate of bug 1866194 ***
https://bugs.launchpad.net/bugs/1866194

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1866194, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1866194
   External audio device shows up in the sound output options but the sound 
keeps being emitted from the internal laptop speaker, or none at all.

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

Title:
  Bluetooth connection to headset works for volume buttons but not tests

Status in bluez package in Ubuntu:
  New

Bug description:
  bluetooth worked fine under 19.10.
   Now, when bluetooth connects to my headset, I can hear noises from the 
increase/ decrease volume keys, but the "test" for Output Device in Sound 
settings makes sound on my laptop, not the headset.
   And all applications send sound to the laptop, not the headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 30 19:39:09 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-11-26 (156 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20BX001PUS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=e4714fe0-a682-44bc-b1ba-4cb61352bb03 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to focal on 2020-04-26 (4 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX001PUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX001PUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001PUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BX001PUS
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:53:60:42:C0:97  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:22321 acl:74 sco:0 events:1206 errors:0
TX bytes:257018 acl:319 sco:0 commands:403 errors:0
  syslog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1876211/+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 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  QEMU/KVM display is garbled when booting from kernel EFI stub due to
  missing bochs-drm module

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1872863

  [Impact]

  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.

  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.

  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled
  in LP #1378648 due to bochs-drm causing problems in a PowerKVM
  machine. This problem appears to be fixed now, and bochs-drm has been
  re-enabled for Disco and up, in LP #1795857 and has been proven safe.

  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.

  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.

  [Fix]

  I noticed on Focal, if you boot, the framebuffer is initially efifb:

  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device

  This soon changes to bochs-drm about a second later:

  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48

  On bionic, the framebuffer never changes from efifb, since the bochs-
  drm kernel module is not built, and it is also present on the module
  banlist in /etc/modprobe.d/blacklist-framebuffer.conf

  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.

  [Testcase]

  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In
  the "Overview" tab, enable EFI by setting the firmware to "UEFI
  x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd".

  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do a "apt update" and "apt upgrade", to ensure you
  have grub2 2.02-2ubuntu8.15 installed.

  Shut the VM down, and set the video device to VGA. Or VGA=std if you
  use the QEMU command line.

  Start the VM up, and the screen will be garbled. See attached picture.

  If you install my test packages, which are available here:

  

[Touch-packages] [Bug 1861757] Re: Missing libgcc_s.so.1 decrypting partition on boot

[Bug Watch Updater]

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

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

Title:
  Missing libgcc_s.so.1 decrypting partition on boot

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  On focal with -proposed repo enabled. Updated all packages and
  rebooted. Upon entering the LUKS passphrase for disk decryption I get
  the following message, and cannot boot:

"libgcc_s.so.1 must be installed for pthread_cancel to work"

  Booting with the previous kernel works.

  Found this question with an identical issue:
  https://askubuntu.com/questions/1190687/ubuntu-19-10-missing-lib-gcc-
  so-1-after-kernel-update, which points to "/usr/share/initramfs-
  tools/hooks/cryptroot" being unable to find that lib. It was looking
  in "/lib/x86_64-linux-gnu/", but libgcc_s.so.1 is not there, but at
  "/usr/lib/" and "/usr/lib/x86_64-linux-gnu/". Temporarily fixed by
  copying the file to "/lib/x86_64-linux-gnu/" and regenerating the
  initramdisk.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgcc1 1:10-20200202-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16
  Uname: Linux 5.4.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Feb  4 00:05:48 2020
  InstallationDate: Installed on 2019-09-23 (133 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917)
  SourcePackage: gcc-10
  UpgradeStatus: Upgraded to focal on 2020-01-24 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861757/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

[Hui Wang]

I don't know that.

Maybe there is some necessary fixup in the -26 kernel but not in  the
-25 kernel. After the -27 is ready, I will build a testing kernel based
on -26 kernel, then you could test -26 testing kernel, if it has boot
issues, you could choose the -27 kernel to boot then.

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+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 1875985] Re: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4

[Hui Wang]

*** This bug is a duplicate of bug 1875916 ***
https://bugs.launchpad.net/bugs/1875916

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

** This bug has been marked a duplicate of bug 1875916
   upgrading to 4.15.0-99-generic breaks the sound and the trackpad

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

Title:
  [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all
  after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  VERSION="18.04.4 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.4 LTS"

  Running it in the flavour of Xubuntu.

  Just like in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916 my sound
  stopped working with the new kernel "4.15.0-99-generic #100-Ubuntu SMP
  Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux".

  Rebooting into "4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46
  UTC 2020 x86_64 x86_64 x86_64 GNU/Linux" sound works again.

  With 4.15.0-99-generic I do see a signal on the meters of the
  sound/volume control app, but physically there is no sound on either
  internal speakers nor on the headphones.

  
  With 4.15.0-96-generic everything is back to normal.

  My touchpad is working though (#1875916 seems to suggest that the
  touchpad stops working with 4.15.0-99-generic).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rkm1814 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 29 23:45:15 2020
  InstallationDate: Installed on 2016-10-20 (1287 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rkm1814 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-08-31 (607 days ago)
  dmi.bios.date: 05/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.03.00
  dmi.board.name: 0RJ0RW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.03.00:bd05/26/2016:svnDellInc.:pnInspiron13-5368:pvr:rvnDellInc.:rn0RJ0RW:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-5368
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875985/+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 1876211] [NEW] Bluetooth connection to headset works for volume buttons but not tests

[Christopher Barrington-Leigh]

Public bug reported:

bluetooth worked fine under 19.10.
 Now, when bluetooth connects to my headset, I can hear noises from the 
increase/ decrease volume keys, but the "test" for Output Device in Sound 
settings makes sound on my laptop, not the headset.
 And all applications send sound to the laptop, not the headset.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 30 19:39:09 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-11-26 (156 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20BX001PUS
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=e4714fe0-a682-44bc-b1ba-4cb61352bb03 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to focal on 2020-04-26 (4 days ago)
dmi.bios.date: 09/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET66WW (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BX001PUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX001PUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001PUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T450s
dmi.product.name: 20BX001PUS
dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: DC:53:60:42:C0:97  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:22321 acl:74 sco:0 events:1206 errors:0
TX bytes:257018 acl:319 sco:0 commands:403 errors:0
syslog:

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


** Tags: amd64 apport-bug focal

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

Title:
  Bluetooth connection to headset works for volume buttons but not tests

Status in bluez package in Ubuntu:
  New

Bug description:
  bluetooth worked fine under 19.10.
   Now, when bluetooth connects to my headset, I can hear noises from the 
increase/ decrease volume keys, but the "test" for Output Device in Sound 
settings makes sound on my laptop, not the headset.
   And all applications send sound to the laptop, not the headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 30 19:39:09 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-11-26 (156 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20BX001PUS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=e4714fe0-a682-44bc-b1ba-4cb61352bb03 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to focal on 2020-04-26 (4 days ago)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET66WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX001PUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX001PUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001PUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BX001PUS
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:53:60:42:C0:97  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:22321 acl:74 sco:0 events:1206 errors:0
TX bytes:257018 acl:319 sco:0 commands:403 errors:0
  syslog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1876211/+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 1876206] [NEW] Printer cannot be set up

[stephan]

Public bug reported:

Printer cannot be set up as long as the package ippusbxd is installed
The problem affects all makes

Only to be solved with sudo apt purge ippusbxd

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

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

Title:
  Printer cannot be set up

Status in ifupdown package in Ubuntu:
  New

Bug description:
  Printer cannot be set up as long as the package ippusbxd is installed
  The problem affects all makes

  Only to be solved with sudo apt purge ippusbxd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1876206/+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 1876197] [NEW] Xubuntu 20.04 Guest Session Logout Fails

[Graham Jenkins]

Public bug reported:

I've edited "/usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf" so
that it now has "allow-guest=true". And I'm now able to login to a Guest
Session.

But when I attempt to logout I get:

Receiver error while trying to log out
GDBus.Error.org .. Type of message "(yb)", does not match expected type "(b)"

This occurs on both of the Xubuntu 20.04 machines I have, and also on a
Virtualbox guest.

lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04

apt-cache policy lightdm
lightdm:
  Installed: 1.30.0-0ubuntu3.1
  Candidate: 1.30.0-0ubuntu3.1
  Version table:
 *** 1.30.0-0ubuntu3.1 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

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


** Tags: focal lightdm

** Tags added: focal lightdm

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

Title:
  Xubuntu 20.04 Guest Session Logout Fails

Status in lightdm package in Ubuntu:
  New

Bug description:
  I've edited "/usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf"
  so that it now has "allow-guest=true". And I'm now able to login to a
  Guest Session.

  But when I attempt to logout I get:

  Receiver error while trying to log out
  GDBus.Error.org .. Type of message "(yb)", does not match expected type "(b)"

  This occurs on both of the Xubuntu 20.04 machines I have, and also on
  a Virtualbox guest.

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  apt-cache policy lightdm
  lightdm:
Installed: 1.30.0-0ubuntu3.1
Candidate: 1.30.0-0ubuntu3.1
Version table:
   *** 1.30.0-0ubuntu3.1 500
  500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1876197/+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 1876195] [NEW] /var is filed with errors logs (from network) until it is over 60 Gb sized

[Baptiste Jolaine]

Public bug reported:

Hello,
I installed Ubuntu 20.04 a few days ago, at release.
Yesterday I got a warning about low remaining space on disk. Unable to access 
my files I restarted my computer.
Ubuntu failed to boot and I got the code :

[10.688299] ccp :0a:00.2: sev command 0x4 timed out, disabling PSP
[10.688353] cpp :0a:00.2: SEV: failed to get status. Error: 0x0

I started Ubuntu with Advanced options and try repair my packages. It warned me 
I had not enough space to do that so I deleted part of my files in root mode, 
which allowed me to restart.
I ran the disk analyser which show me I had a 60 gigabytes /var directory.
ls -lSh /var/log command show :

total 50G
-rw-r-  1 syslogadm  50G avril 29 23:53 syslog
-rw-r-  1 syslogadm  21M avril 29 23:38 kern.log
-rw-r-  1 syslogadm  13M avril 26 00:00 kern.log.1
-rw-r-  1 syslogadm 4,5M avril 29 00:00 syslog.1
-rw-r-  1 syslogadm 1,3M avril 25 00:00 syslog.5.gz
-rw-r--r--  1 root  root1,2M avril 29 19:18 dpkg.log
-rw-r-  1 syslogadm 795K avril 28 00:00 syslog.2.gz
-rw-rw-r--  1 root  utmp286K avril 24 00:20 lastlog
-rw-r-  1 syslogadm 279K avril 26 00:00 syslog.4.gz
-rw-r-  1 syslogadm 134K avril 27 00:00 syslog.3.gz
-rw-r--r--  1 root  root102K avril 23 09:33 
bootstrap.log
-rw-r--r--  1 root  adm  92K avril 29 23:37 dmesg
-rw-r--r--  1 root  adm  92K avril 29 23:20 dmesg.0
-rw-r-  1 syslogadm  80K avril 25 23:30 auth.log.1
-rw-r--r--  1 root  root 57K avril 29 20:15 
Xorg.1.log.old
-rw---  1 root  root 54K avril 29 23:37 boot.log
-rw---  1 root  root 45K avril 25 00:00 boot.log.4
-rw-r-  1 syslogadm  44K avril 29 23:39 auth.log
-rw-r--r--  1 root  root 39K avril 29 23:38 Xorg.1.log
-rw-r--r--  1 root  root 38K avril 29 23:38 Xorg.0.log
-rw-r--r--  1 root  root 38K avril 29 00:28 
alternatives.log
-rw-r--r--  1 root  root 32K avril 24 00:20 faillog
-rw-rw-r--  1 root  utmp 22K avril 29 23:38 wtmp
-rw---  1 root  root 21K avril 29 00:00 boot.log.1
-rw-r--r--  1 root  adm  21K avril 29 20:21 dmesg.2.gz
-rw-r--r--  1 root  adm  21K avril 29 23:18 dmesg.1.gz
-rw-r--r--  1 root  adm  21K avril 29 20:16 dmesg.4.gz
-rw-r--r--  1 root  adm  21K avril 29 20:19 dmesg.3.gz
-rw-r--r--  1 root  root 17K avril 29 23:20 
Xorg.0.log.old
-rw-r--r--  1 root  root 11K avril 24 02:46 
fontconfig.log
-rw---  1 root  root 11K avril 27 00:00 boot.log.2
-rw---  1 root  root 11K avril 26 00:00 boot.log.3
-rw-r-  1 root  adm 6,1K avril 28 23:06 apport.log.1
drwxr-xr-x  2 root  root4,0K avril 29 19:18 apt
drwxr-xr-x  2 root  root4,0K avril 29 00:00 cups
drwxr-xr-x  2 root  root4,0K avril 29 23:23 dist-upgrade
drwx--x--x  2 root  gdm 4,0K oct.   7  2019 gdm3
drwxr-xr-x  3 root  root4,0K avril 23 09:36 hp
drwxr-xr-x  2 root  root4,0K avril 23 21:31 installer
drwxr-sr-x+ 3 root  systemd-journal 4,0K avril 23 21:39 journal
drwxr-xr-x  2 root  root4,0K sept.  5  2019 openvpn
drwx--  2 root  root4,0K avril 23 09:32 private
drwx--  2 speech-dispatcher root4,0K janv. 19 19:26 
speech-dispatcher
drwxr-x---  2 root  adm 4,0K avril 24 13:46 
unattended-upgrades
-rw-rw-r--  1 root  tistus  1,2K avril 29 23:20 
gpu-manager-switch.log
-rw-r--r--  1 root  root1,2K avril 29 23:37 
gpu-manager.log
-rw-r-  1 root  adm  363 avril 24 22:48 
apport.log.2.gz
-rw-r-  1 root  adm0 avril 29 23:20 apport.log
-rw-rw  1 root  utmp   0 avril 23 09:32 btmp
-rw---  1 root  root   0 avril 23 09:33 
ubuntu-advantage.log

syslog became syslog.1 after a restart but is still 50G

I paste the result of command sudo tail -150 /var/log/syslog.1 in the file 
TraceSyslog1.txt
And the result of the command sudo  journalctl -n5000 >TraceJournal.txt is the 
file TraceJournal.txt

In logs I found numerous network problems such as :
Server returned error NXDOMAIN, 

[Touch-packages] [Bug 1876195] Re: /var is filed with errors logs (from network) until it is over 60 Gb sized

[Baptiste Jolaine]

** Attachment added: "sudo tail -150 /var/log/syslog.1"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1876195/+attachment/5364199/+files/TraceSyslog1.txt

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

Title:
  /var is filed with errors logs (from network) until it is over 60 Gb
  sized

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello,
  I installed Ubuntu 20.04 a few days ago, at release.
  Yesterday I got a warning about low remaining space on disk. Unable to access 
my files I restarted my computer.
  Ubuntu failed to boot and I got the code :

  [10.688299] ccp :0a:00.2: sev command 0x4 timed out, disabling PSP
  [10.688353] cpp :0a:00.2: SEV: failed to get status. Error: 0x0

  I started Ubuntu with Advanced options and try repair my packages. It warned 
me I had not enough space to do that so I deleted part of my files in root 
mode, which allowed me to restart.
  I ran the disk analyser which show me I had a 60 gigabytes /var directory.
  ls -lSh /var/log command show :

  total 50G
  -rw-r-  1 syslogadm  50G avril 29 23:53 syslog
  -rw-r-  1 syslogadm  21M avril 29 23:38 kern.log
  -rw-r-  1 syslogadm  13M avril 26 00:00 kern.log.1
  -rw-r-  1 syslogadm 4,5M avril 29 00:00 syslog.1
  -rw-r-  1 syslogadm 1,3M avril 25 00:00 
syslog.5.gz
  -rw-r--r--  1 root  root1,2M avril 29 19:18 dpkg.log
  -rw-r-  1 syslogadm 795K avril 28 00:00 
syslog.2.gz
  -rw-rw-r--  1 root  utmp286K avril 24 00:20 lastlog
  -rw-r-  1 syslogadm 279K avril 26 00:00 
syslog.4.gz
  -rw-r-  1 syslogadm 134K avril 27 00:00 
syslog.3.gz
  -rw-r--r--  1 root  root102K avril 23 09:33 
bootstrap.log
  -rw-r--r--  1 root  adm  92K avril 29 23:37 dmesg
  -rw-r--r--  1 root  adm  92K avril 29 23:20 dmesg.0
  -rw-r-  1 syslogadm  80K avril 25 23:30 auth.log.1
  -rw-r--r--  1 root  root 57K avril 29 20:15 
Xorg.1.log.old
  -rw---  1 root  root 54K avril 29 23:37 boot.log
  -rw---  1 root  root 45K avril 25 00:00 boot.log.4
  -rw-r-  1 syslogadm  44K avril 29 23:39 auth.log
  -rw-r--r--  1 root  root 39K avril 29 23:38 Xorg.1.log
  -rw-r--r--  1 root  root 38K avril 29 23:38 Xorg.0.log
  -rw-r--r--  1 root  root 38K avril 29 00:28 
alternatives.log
  -rw-r--r--  1 root  root 32K avril 24 00:20 faillog
  -rw-rw-r--  1 root  utmp 22K avril 29 23:38 wtmp
  -rw---  1 root  root 21K avril 29 00:00 boot.log.1
  -rw-r--r--  1 root  adm  21K avril 29 20:21 dmesg.2.gz
  -rw-r--r--  1 root  adm  21K avril 29 23:18 dmesg.1.gz
  -rw-r--r--  1 root  adm  21K avril 29 20:16 dmesg.4.gz
  -rw-r--r--  1 root  adm  21K avril 29 20:19 dmesg.3.gz
  -rw-r--r--  1 root  root 17K avril 29 23:20 
Xorg.0.log.old
  -rw-r--r--  1 root  root 11K avril 24 02:46 
fontconfig.log
  -rw---  1 root  root 11K avril 27 00:00 boot.log.2
  -rw---  1 root  root 11K avril 26 00:00 boot.log.3
  -rw-r-  1 root  adm 6,1K avril 28 23:06 
apport.log.1
  drwxr-xr-x  2 root  root4,0K avril 29 19:18 apt
  drwxr-xr-x  2 root  root4,0K avril 29 00:00 cups
  drwxr-xr-x  2 root  root4,0K avril 29 23:23 
dist-upgrade
  drwx--x--x  2 root  gdm 4,0K oct.   7  2019 gdm3
  drwxr-xr-x  3 root  root4,0K avril 23 09:36 hp
  drwxr-xr-x  2 root  root4,0K avril 23 21:31 installer
  drwxr-sr-x+ 3 root  systemd-journal 4,0K avril 23 21:39 journal
  drwxr-xr-x  2 root  root4,0K sept.  5  2019 openvpn
  drwx--  2 root  root4,0K avril 23 09:32 private
  drwx--  2 speech-dispatcher root4,0K janv. 19 19:26 
speech-dispatcher
  drwxr-x---  2 root  adm 4,0K avril 24 13:46 
unattended-upgrades
  -rw-rw-r--  1 root  tistus  1,2K avril 29 23:20 
gpu-manager-switch.log
  -rw-r--r--  1 root  root1,2K avril 29 23:37 
gpu-manager.log
  -rw-r-  1 root  adm  363 

[Touch-packages] [Bug 1876170] Re: Monitor setups including portrait orinted monitors cause horizontal resolution to increase

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Monitor setups including portrait orinted monitors cause horizontal
  resolution to increase

Status in xorg package in Ubuntu:
  New

Bug description:
  With a multi-monitor setup that includes one portrait oriented screen,
  most of the time several of the monitors end up with extended
  horizontal resolution to the right, resulting in panning when you move
  the mouse, as well as overlap between the screen areas.

  I can occasionally make it behave after some enabling, disabling and
  orientation changes of the monitors, but seemingly only if I have them
  all in a row and don't have the portrait one furthest to the right.

  Attempted setup that breaks:
   ---
  |1920x1080  |
  |nvidia egpu|1080|
   --- --- ---|x   |
  |2560x1440  |1920x1080  |1920x1080  |1920|
  |laptop internal|nvidia egpu|nvidia egpu|egpu|
  |   |--- --- 
   --- 

  Also attached screenshot that should illustrate the issue well.

  I can't tell for sure if this is an xorg issue or a nvidia one, I did
  look at both arandr and nvidia-settings and in neither can I see
  anything amiss.

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 30 20:18:43 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
   NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU104 [GeForce RTX 2070 SUPER] [1043:8727]
  InstallationDate: Installed on 2020-04-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20L5CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5CTO1WW
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  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.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

[Wittawat Jitkrittum]

okay. I just restored to my original Hdmi.conf.  "options snd-intel-
dspcfg dsp_driver=1" in alsa-base.conf still commented out.

Now the -25 kernel v3 does not boot anymore. I am confused now. I could
boot in #15. It is supposed to be the same setting. I got stuck at a
black screen. But if I select -26 in the Grub menu (keeping other config
files the same), then it could boot easily.

I suspect that somehow a filesystem check is triggered at boot time, and
maybe that filesystem checking process hangs. Just my pure guess. Are
you aware of this in the new Ubuntu 20.04?

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+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 1876170] [NEW] Monitor setups including portrait orinted monitors cause horizontal resolution to increase

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

With a multi-monitor setup that includes one portrait oriented screen,
most of the time several of the monitors end up with extended horizontal
resolution to the right, resulting in panning when you move the mouse,
as well as overlap between the screen areas.

I can occasionally make it behave after some enabling, disabling and
orientation changes of the monitors, but seemingly only if I have them
all in a row and don't have the portrait one furthest to the right.

Attempted setup that breaks:
 ---
|1920x1080  |
|nvidia egpu|1080|
 --- --- ---|x   |
|2560x1440  |1920x1080  |1920x1080  |1920|
|laptop internal|nvidia egpu|nvidia egpu|egpu|
|   |--- --- 
 --- 

Also attached screenshot that should illustrate the issue well.

I can't tell for sure if this is an xorg issue or a nvidia one, I did
look at both arandr and nvidia-settings and in neither can I see
anything amiss.

lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 30 20:18:43 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
 NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. TU104 [GeForce RTX 2070 SUPER] [1043:8727]
InstallationDate: Installed on 2020-04-30 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 20L5CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET56W (1.31 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
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.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal resolution ubuntu
-- 
Monitor setups including portrait orinted monitors cause horizontal resolution 
to increase
https://bugs.launchpad.net/bugs/1876170
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1821810] Re: gdebi crashes when trying to install packages

[Junaid Ahmed]

There's no indication of this bug's ever being fixed. The workaround is
always launching Gdebi through Terminal. Run-

sudo -i gedit /usr/share/applications/gdebi.desktop

make it read:-

[Desktop Entry]
Name=GDebi Package Installer
GenericName=Package Installer
Comment=Install and view software packages
Exec=sudo -i gdebi-gtk %f
Icon=gnome-mime-application-x-deb
Terminal=false
Type=Application
Categories=System;
MimeType=application/vnd.debian.binary-package;
NotShowIn=KDE;
X-Ubuntu-Gettext-Domain=gdebi
StartupNotify=true
Keywords=package;apt;dpkg;install

SAVE the file.

Now try right-clicking a .deb and selecting "Open with > GDebi Package
Installer"

Thanks to user Mark-pcnetspec on bug #1760910

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

Title:
  gdebi crashes when trying to install packages

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  When I try to install some deb packages gdebi disapears. It does not
  show me any error report. It will just disapear from my screen.

  Lubuntu 18.4 LTS
  gdebi 0.9.5.7+nmu2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdebi 0.9.5.7+nmu2
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Mar 26 23:30:04 2019
  InstallationDate: Installed on 2019-03-18 (8 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1821810/+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 1876171] [NEW] Falla en la barra de tareas

[victor manuel nevarez guerrero]

Public bug reported:

la barra de tareas esta desfasada y en ocasiones provoca problemas para
cerrar o minimizar una ventana. solo es estético. las letras estan fuera
de la barra de tareas. saludos

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 30 14:01:53 2020
DistUpgraded: 2020-04-30 08:36:59,642 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1854]
InstallationDate: Installed on 2019-09-28 (215 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 003: ID 05c8:0348 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP 240 G1 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=39b4235a-82d9-40c7-9f0a-9e5d96bc5839 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-30 (0 days ago)
dmi.bios.date: 06/13/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.3A
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1854
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 64.2A
dmi.chassis.asset.tag: 5CG3374CS4
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.3A:bd06/13/2013:svnHewlett-Packard:pnHP240G1NotebookPC:pvr088013305B1610110:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN
dmi.product.name: HP 240 G1 Notebook PC
dmi.product.sku: E1Z19LT#ABM
dmi.product.version: 088013305B1610110
dmi.sys.vendor: Hewlett-Packard
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2019-10-06T16:32:19.326556
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal ubuntu

** Attachment added: "error en la barra de tareas"
   
https://bugs.launchpad.net/bugs/1876171/+attachment/5364148/+files/Captura%20de%20pantalla%20de%202020-04-30%2014-03-15.png

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

Title:
  Falla en la barra de tareas

Status in xorg package in Ubuntu:
  New

Bug description:
  la barra de tareas esta desfasada y en ocasiones provoca problemas
  para cerrar o minimizar una ventana. solo es estético. las letras
  estan fuera de la barra de tareas. saludos

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 30 14:01:53 2020
  DistUpgraded: 2020-04-30 08:36:59,642 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) 

[Touch-packages] [Bug 1876145] Re: Unable to scroll list of sessions by mouse wheel or keyboard

[Norbert]

** Also affects: arctica-greeter (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unable to scroll list of sessions by mouse wheel or keyboard

Status in arctica-greeter package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in lightdm-gtk-greeter package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed with many desktop sessions
  2. Boot the machine
  3. Try to specify graphical user session on the LightDM greeter screen by 
mouse or by keyboard

  Expected results:
  * the list of graphical sessions may be scrolled by mouse and/or by keyboard

  Actual results:
  * it is impossible to view all graphical sessions and scroll to one of them 
using keyboard and/or mouse (on the attached screenshot it is impossible to 
view sessions below Dwm).

  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: lightdm 1.30.0-0ubuntu3.1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Deepin
  Date: Thu Apr 30 19:48:12 2020
  InstallationDate: Installed on 2020-04-22 (7 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   allow-guest=false
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1876145/+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 1876152] [NEW] dstat warnings on install

[John Bartoszewski]

Public bug reported:

Upon installing dstat I received this warning/error:

 Setting up dstat (0.7.4-6) ...
/usr/share/dstat/dstat_mysql_keys.py:41: SyntaxWarning: 'str' object is not 
callable; perhaps you missed a comma?
  if op.debug > 1: print('%s: exception' (self.filename, e))
/usr/share/dstat/dstat_squid.py:48: SyntaxWarning: 'str' object is not 
callable; perhaps you missed a comma?
  if op.debug > 1: print('%s: exception' (self.filename, e))


basic dstat functions still operate

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


** Tags: focal

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

Title:
  dstat warnings on install

Status in libtool package in Ubuntu:
  New

Bug description:
  Upon installing dstat I received this warning/error:

   Setting up dstat (0.7.4-6) ...
  /usr/share/dstat/dstat_mysql_keys.py:41: SyntaxWarning: 'str' object is not 
callable; perhaps you missed a comma?
if op.debug > 1: print('%s: exception' (self.filename, e))
  /usr/share/dstat/dstat_squid.py:48: SyntaxWarning: 'str' object is not 
callable; perhaps you missed a comma?
if op.debug > 1: print('%s: exception' (self.filename, e))

  
  basic dstat functions still operate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/1876152/+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 1875985] Re: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4

[A. van Gompel]

Same issue here on a Dell Inspiron 13-7378 (ALC3253).

Audio was working fine on the previous kernel (4.15.0-96-lowlatency) and
after update to 4.15.0-99-lowlatency there is no sound from the internal
speaker and also the mic is not working. The sound works fine on an
external USB device (plantronics P610).

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

Title:
  [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all
  after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  VERSION="18.04.4 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.4 LTS"

  Running it in the flavour of Xubuntu.

  Just like in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916 my sound
  stopped working with the new kernel "4.15.0-99-generic #100-Ubuntu SMP
  Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux".

  Rebooting into "4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46
  UTC 2020 x86_64 x86_64 x86_64 GNU/Linux" sound works again.

  With 4.15.0-99-generic I do see a signal on the meters of the
  sound/volume control app, but physically there is no sound on either
  internal speakers nor on the headphones.

  
  With 4.15.0-96-generic everything is back to normal.

  My touchpad is working though (#1875916 seems to suggest that the
  touchpad stops working with 4.15.0-99-generic).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rkm1814 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 29 23:45:15 2020
  InstallationDate: Installed on 2016-10-20 (1287 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rkm1814 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-08-31 (607 days ago)
  dmi.bios.date: 05/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.03.00
  dmi.board.name: 0RJ0RW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.03.00:bd05/26/2016:svnDellInc.:pnInspiron13-5368:pvr:rvnDellInc.:rn0RJ0RW:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-5368
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875985/+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 1876143] Re: Ubuntu 20.04 gnome online accounts, webkit crashes when using nvidia-driver-390

[Sebastien Bacher]

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: gnome-online-accounts (Ubuntu)
   Status: New => Invalid

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

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

Title:
  Ubuntu 20.04 gnome online accounts, webkit crashes when using nvidia-
  driver-390

Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in webkit2gtk package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 20.04 LTS today, and tried to add google and facebook 
account.
  Webkit crashes, and loading stops.
  When using open-source nvidia driver it works..

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwebkit2gtk-4.0-37 2.28.2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 30 18:41:23 2020
  InstallationDate: Installed on 2020-04-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: webkit2gtk
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1876143/+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 1876145] [NEW] Unable to scroll list of sessions by mouse wheel or keyboard

[Norbert]

Public bug reported:

Steps to reproduce:
1. Have Ubuntu 20.04 LTS installed with many desktop sessions
2. Boot the machine
3. Try to specify graphical user session on the LightDM greeter screen by mouse 
or by keyboard

Expected results:
* the list of graphical sessions may be scrolled by mouse and/or by keyboard

Actual results:
* it is impossible to view all graphical sessions and scroll to one of them 
using keyboard and/or mouse (on the attached screenshot it is impossible to 
view sessions below Dwm).

ProblemType: Bug
DistroRelease: Ubuntu Kylin 20.04
Package: lightdm 1.30.0-0ubuntu3.1 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
Uname: Linux 5.4.0-28-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Deepin
Date: Thu Apr 30 19:48:12 2020
InstallationDate: Installed on 2020-04-22 (7 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
LightdmConfig:
 [Seat:*]
 autologin-guest=false
 allow-guest=false
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: lightdm-gtk-greeter (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "unable to scroll the list of graphical sessions in the 
LightDM greeter"
   
https://bugs.launchpad.net/bugs/1876145/+attachment/5364080/+files/lightdm-login.png

** Also affects: lightdm-gtk-greeter (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unable to scroll list of sessions by mouse wheel or keyboard

Status in lightdm package in Ubuntu:
  New
Status in lightdm-gtk-greeter package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed with many desktop sessions
  2. Boot the machine
  3. Try to specify graphical user session on the LightDM greeter screen by 
mouse or by keyboard

  Expected results:
  * the list of graphical sessions may be scrolled by mouse and/or by keyboard

  Actual results:
  * it is impossible to view all graphical sessions and scroll to one of them 
using keyboard and/or mouse (on the attached screenshot it is impossible to 
view sessions below Dwm).

  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: lightdm 1.30.0-0ubuntu3.1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Deepin
  Date: Thu Apr 30 19:48:12 2020
  InstallationDate: Installed on 2020-04-22 (7 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   allow-guest=false
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1876145/+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 1876147] [NEW] libtool-doc missing libtool.html

[John Bartoszewski]

Public bug reported:

I am posting this as a bug to libtool but the package is libtool-doc

When installing doc-base I I received this error/warning:
Processing triggers for doc-base (0.10.9) ...
Processing 2 added doc-base files...
Error in `/usr/share/doc-base/libtool-doc', line 9: all `Format' sections are 
invalid.
Note: `install-docs --verbose --check file_name' may give more details about 
the above error.

Running: install-docs --verbose --check /usr/share/doc-base/libtool-doc
I got:

Warning in `/usr/share/doc-base/libtool-doc', line 9: file 
`/usr/share/doc/libtool-doc/libtool.html' does not exist.
Error in `/usr/share/doc-base/libtool-doc', line 9: all `Format' sections are 
invalid.
/usr/share/doc-base/libtool-doc: Fatal error found, the file won't be 
registered.

A search for which package owns /usr/share/doc-base/libtool-doc
apt-file search /usr/share/doc-base/libtool-doc
libtool-doc: /usr/share/doc-base/libtool-doc

Line 9 in /usr/share/doc-base/libtool-doc is;
Index: /usr/share/doc/libtool-doc/libtool.html

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

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

Title:
  libtool-doc missing libtool.html

Status in libtool package in Ubuntu:
  New

Bug description:
  I am posting this as a bug to libtool but the package is libtool-doc

  When installing doc-base I I received this error/warning:
  Processing triggers for doc-base (0.10.9) ...
  Processing 2 added doc-base files...
  Error in `/usr/share/doc-base/libtool-doc', line 9: all `Format' sections are 
invalid.
  Note: `install-docs --verbose --check file_name' may give more details about 
the above error.

  Running: install-docs --verbose --check /usr/share/doc-base/libtool-doc
  I got:

  Warning in `/usr/share/doc-base/libtool-doc', line 9: file 
`/usr/share/doc/libtool-doc/libtool.html' does not exist.
  Error in `/usr/share/doc-base/libtool-doc', line 9: all `Format' sections are 
invalid.
  /usr/share/doc-base/libtool-doc: Fatal error found, the file won't be 
registered.

  A search for which package owns /usr/share/doc-base/libtool-doc
  apt-file search /usr/share/doc-base/libtool-doc
  libtool-doc: /usr/share/doc-base/libtool-doc

  Line 9 in /usr/share/doc-base/libtool-doc is;
  Index: /usr/share/doc/libtool-doc/libtool.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/1876147/+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 1876143] [NEW] Ubuntu 20.04 gnome online accounts, webkit crashes when using nvidia-driver-390

[Alexander Vinbæk Strand]

Public bug reported:

I installed Ubuntu 20.04 LTS today, and tried to add google and facebook 
account.
Webkit crashes, and loading stops.
When using open-source nvidia driver it works..

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libwebkit2gtk-4.0-37 2.28.2-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 30 18:41:23 2020
InstallationDate: Installed on 2020-04-30 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: webkit2gtk
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug focal

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-online-accounts (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- gnome online accounts, webkit crashes when using nvidia-driver-390
+ Ubuntu 20.04 gnome online accounts, webkit crashes when using 
nvidia-driver-390

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

Title:
  Ubuntu 20.04 gnome online accounts, webkit crashes when using nvidia-
  driver-390

Status in gnome-online-accounts package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 20.04 LTS today, and tried to add google and facebook 
account.
  Webkit crashes, and loading stops.
  When using open-source nvidia driver it works..

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwebkit2gtk-4.0-37 2.28.2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 30 18:41:23 2020
  InstallationDate: Installed on 2020-04-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: webkit2gtk
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1876143/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Balint Reczey]

** Tags added: rls-gg-incoming

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed-5.4 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861941/+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 1845245] Re: Behaviour change in systemd 243 breaks netplan.io ethernets autopkgtest

[Balint Reczey]

*** This bug is a duplicate of bug 1860926 ***
https://bugs.launchpad.net/bugs/1860926

Yes, indeed.
Including the change from LP: #1860926 the reverts can be dropped.
https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-groovy-drop-net-reverts
As I wrote in LP: #1860926 I'd like to include your fix in the next upload to 
Groovy even if upstream would like to find a different solution.


** Changed in: netplan.io (Ubuntu)
   Status: New => Invalid

** This bug has been marked a duplicate of bug 1860926
   Ubuntu 20.04  Systemd fails to configure bridged network

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

Title:
  Behaviour change in systemd 243 breaks netplan.io ethernets
  autopkgtest

Status in netplan.io package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  The commit introducing the regression is this one:

  commit bd08ce56156751d58584a44e766ef61340cdae2d
  Author: Yu Watanabe 
  Date:   Mon Apr 15 17:34:00 2019 +0900

  network: prevent interfaces to be initialized multiple times

  When a uevent is received during the relevant interface is in
  LINK_STATE_PENDING, then the interface may be initialized twice.
  To prevent that, this introduces LINK_STATE_INITIALIZED.

  
  I'll triage further and possibly revert the change in the next 243-based 
upload.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1845245/+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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

[Balint Reczey]

@ddstreet Regarding the fix IMO the proposed fix makes sense and makes
systemd more robust. I'd like to add it in Ubuntu even if upstream would
like to stick to a more fragile default to notice bugs earlier.

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Confirmed

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [regression potential]

  Any regression would likely involve incorrectly configured network
  after an interface carrier gain/loss.

  [scope]

  This is needed for Focal, Eoan, and Bionic.

  While this only reproduces at boot for Focal, the general loss of
  configuration on carrier loss even when ConfigureWithoutCarrier=true
  is reproducable on all releases except Xenial, which does not have the
  ConfigureWithoutCarrier= parameter.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.

  systemctl restart systemd-networkd resolved the issue and a

  systemctl status 

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

[Balint Reczey]

Forwarded to upstream via https://github.com/systemd/systemd/pull/15619
. (Thanks @ddstreet!)

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Confirmed

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [regression potential]

  Any regression would likely involve incorrectly configured network
  after an interface carrier gain/loss.

  [scope]

  This is needed for Focal, Eoan, and Bionic.

  While this only reproduces at boot for Focal, the general loss of
  configuration on carrier loss even when ConfigureWithoutCarrier=true
  is reproducable on all releases except Xenial, which does not have the
  ConfigureWithoutCarrier= parameter.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.

  systemctl restart systemd-networkd resolved the issue and a

  systemctl status systemd-network producessystemd-networkd.service - Network 
Service
   Loaded: loaded 

[Touch-packages] [Bug 1876122] [NEW] SRU the current 3.36.2 stable update

[Sebastien Bacher]

Public bug reported:

* Impact
That's the current GNOME stable update, including some fixes and translation 
updates
https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

* Test case

The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Check that the calendar integration in GNOME and gnome-calendar is
working, also test evolution with an email account.

* Regression potential

There is no specific change or feature to test in the upgrade

** Affects: evolution-data-server (Ubuntu)
 Importance: Low
 Status: Fix Released

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

Title:
  SRU the current 3.36.2 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1876122/+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 1876124] [NEW] SRU the current 3.36.2 stable update

[Sebastien Bacher]

Public bug reported:

* Impact
That's the current GNOME stable update, including some fixes and translation 
updates
https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

* Test case

The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Check that the calendar integration in GNOME and gnome-calendar is
working, also test evolution with an email account.

* Regression potential

There is no specific change or feature to test in the upgrade

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Invalid

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

Title:
  SRU the current 3.36.2 stable update

Status in evolution-data-server package in Ubuntu:
  Invalid

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1876124/+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 1876122] Re: SRU the current 3.36.2 stable update

[Sebastien Bacher]

https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/3.36.2-1

** Changed in: evolution-data-server (Ubuntu)
   Importance: Undecided => Low

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Fix Released

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

Title:
  SRU the current 3.36.2 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1876122/+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 1876125] [NEW] SRU the current 3.36.2 stable update

[Sebastien Bacher]

Public bug reported:

* Impact
That's the current GNOME stable update, including some fixes and translation 
updates
https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

* Test case

The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Check that the calendar integration in GNOME and gnome-calendar is
working, also test evolution with an email account.

* Regression potential

There is no specific change or feature to test in the upgrade

** Affects: evolution-data-server (Ubuntu)
 Importance: Low
 Status: Fix Released

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

Title:
  SRU the current 3.36.2 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1876125/+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 1876125] Re: SRU the current 3.36.2 stable update

[Sebastien Bacher]

https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/3.36.2-1

** Changed in: evolution-data-server (Ubuntu)
   Importance: Undecided => Low

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Fix Released

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

Title:
  SRU the current 3.36.2 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1876125/+subscriptions

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

[Touch-packages] [Bug 1851695] Re: DEP8 failure/regression in nspr on arm64 and armhf

[Paride Legovini]

Fix released in Focal with version 0.6.1~ds2-5.

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

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

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

Status in notary package in Ubuntu:
  Fix Released
Status in nspr package in Ubuntu:
  Invalid
Status in notary package in Debian:
  Fix Released

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

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

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

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

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

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

[Touch-packages] [Bug 1870932] Re: ssh-add -L incorrectly reports a failure when successfully retrieving an empty identity list

[Paride Legovini]

Hi Kike, I'm marking this bug report as Invalid, per your request.
Thanks for taking the time to file it!

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

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

Title:
  ssh-add -L incorrectly reports a failure when successfully retrieving
  an empty identity list

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Example of behavior:

  ```
  mikemol@kaylee:~$ ssh-add -L
  The agent has no identities.
  mikemol@kaylee:~$ echo $?
  1
  mikemol@kaylee:~$
  ```

  I expected an exit code of 0 if the agent was running. I don't need
  the list of identities; I'm trying to validate that the agent is
  running, accessible, and operational.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-client 1:7.6p1-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.15.0-69.78-generic 4.15.18
  Uname: Linux 4.15.0-69-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 10:38:25 2020
  InstallationDate: Installed on 2018-12-16 (475 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1870932/+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 1876119] [NEW] xinit won't start without root privileges

[Toni Melisma]

Public bug reported:

When attempting to start xinit as a regular user, I simply get the error
I don't have access rights to /dev/tty0

Even setting setuid and setgid bits on /usr/bin/Xorg or chmod 666 on
/dev/tty0 doesn't work.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Apr 30 14:43:26 2020
DistUpgraded: 2020-04-30 09:29:06,278 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev 87) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon R5 Graphics 
[1002:1871]
InstallationDate: Installed on 2019-12-21 (130 days ago)
InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 001 Device 003: ID 041e:324d Creative Technology, Ltd 
 Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Root Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HPE ProLiant MicroServer Gen10
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=dd6b3468-5d78-4b6e-960c-d9e3e418d8dc ro
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-04-30 (0 days ago)
dmi.bios.date: 03/02/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.asset.tag: Default string
dmi.board.name: ProLiant MicroServer Gen10
dmi.board.vendor: HPE
dmi.board.version: 871721-001
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 1
dmi.chassis.vendor: HPE
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/02/2018:svnHPE:pnProLiantMicroServerGen10:pvrRevB:rvnHPE:rnProLiantMicroServerGen10:rvr871721-001:cvnHPE:ct1:cvrDefaultstring:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen10
dmi.product.sku: 873830-421
dmi.product.version: Rev B
dmi.sys.vendor: HPE
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug false-gpu-hang focal freeze ubuntu

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

Title:
  xinit won't start without root privileges

Status in xorg package in Ubuntu:
  New

Bug description:
  When attempting to start xinit as a regular user, I simply get the
  error I don't have access rights to /dev/tty0

  Even setting setuid and setgid bits on /usr/bin/Xorg or chmod 666 on
  /dev/tty0 doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Apr 30 14:43:26 2020
  DistUpgraded: 2020-04-30 09:29:06,278 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon R5 Graphics 
[1002:1871]
  InstallationDate: Installed on 2019-12-21 (130 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  Lsusb:
   Bus 001 Device 003: ID 041e:324d Creative Technology, Ltd 
   Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Root Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HPE ProLiant MicroServer Gen10
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=dd6b3468-5d78-4b6e-960c-d9e3e418d8dc ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-04-30 (0 days ago)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: 

[Touch-packages] [Bug 1875256] Re: Broken upgrade from Kubuntu 18.04 to Kubuntu 20.04

[Brian Murray]

** Package changed: ubuntu-release-upgrader (Ubuntu) => apt (Ubuntu)

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

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

Title:
  Broken upgrade from Kubuntu 18.04 to Kubuntu 20.04

Status in apt package in Ubuntu:
  New

Bug description:
  As title says, after upgrading i've seen that Ksysguard was missing,
  also lm-sensors that i use to monitor, i tried to install them but
  i've got apt kind of stuck because lots of dependencies missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Mon Apr 27 01:20:23 2020
  InstallationDate: Installed on 2017-01-16 (1196 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1875256/+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 1876056] Re: No automatic switch to headset microphone on connect

[Egbert van der Wal]

No, that seems to be an actual regression. The thing I'm reporting turns
out to be an intentional configuration issue related to limitations of
the hardware / jack detection.

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

Title:
  No automatic switch to headset microphone on connect

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On my Dell XPS 7590, when I plugin a headset with a 4-pin-connector,
  the audio OUTPUT automatically switches from the speakers in the
  laptop to the headset. However, the audio INPUT does not switch from
  the microphone in the laptop to the microphone in the headset.

  Using for example pavucontrol, I can switch to the microphone manually
  on the tab 'input devices' - on that tab Port will be on 'Internal
  Microphone' and I can set it to 'Headset Microphone'.

  What's even more confusing is that when I unplug the headset, both
  input AND output switch back to internal automatically and the port on
  the 'Input Devices'.

  This is on Ubuntu 19.10 with kernel 5.4.28-050428-generic (but I also
  see the same issue on kernel 5.3.0-48) and pulseaudio
  1:13.0-1ubuntu1.1.

  If any more information is needed, let me know.

  inxi -F:

  System:Host: idefixpsie Kernel: 5.4.28-050428-generic x86_64 bits: 64 
Desktop: KDE Plasma 5.16.5 
 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: Dell product: XPS 15 7590 v: N/A serial: 
 
 Mobo: Dell model: 0VYV0G v: A00 serial:  UEFI: Dell 
v: 1.5.0 date: 12/25/2019 
  Battery:   ID-1: BAT0 charge: 77.7 Wh condition: 87.4/97.0 Wh (90%) 
  CPU:   Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP 
L2 cache: 12.0 MiB 
 Speed: 4029 MHz max: 4500 MHz Core speeds (MHz): 1: 4213 2: 4160 
3: 4229 4: 4210 5: 4224 6: 4163 7: 4280 8: 4189 
 9: 4291 10: 4198 11: 4149 12: 4188 
  Graphics:  Device-1: Intel UHD Graphics 630 driver: i915 v: kernel 
 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: 
fbdev,vesa resolution: 3840x2160~60Hz 
 OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 
GT2) v: 4.5 Mesa 19.2.8 
  Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.28-050428-generic 
  Network:   Device-1: Intel driver: iwlwifi 
 IF: wlan0 state: up mac: 5c:80:b6:7a:2c:45 
 IF-ID-1: docker0 state: down mac: 02:42:90:4c:31:a2 
  Drives:Local Storage: total: 953.87 GiB used: 67.58 GiB (7.1%) 
 ID-1: /dev/nvme0n1 model: SSDPEMKF010T8 NVMe INTEL 1024GB size: 
953.87 GiB 
  Partition: ID-1: / size: 496.44 GiB used: 67.27 GiB (13.6%) fs: ext4 dev: 
/dev/dm-1 
 ID-2: /boot size: 704.5 MiB used: 288.4 MiB (40.9%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-3: swap-1 size: 6.61 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/dm-2 
  Sensors:   System Temperatures: cpu: 47.0 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 346 Uptime: 2d 17h 51m Memory: 31.12 GiB used: 9.08 GiB 
(29.2%) Shell: bash inxi: 3.0.36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056/+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 1875256] [NEW] Broken upgrade from Kubuntu 18.04 to Kubuntu 20.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

As title says, after upgrading i've seen that Ksysguard was missing,
also lm-sensors that i use to monitor, i tried to install them but i've
got apt kind of stuck because lots of dependencies missing.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.18
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Mon Apr 27 01:20:23 2020
InstallationDate: Installed on 2017-01-16 (1196 days ago)
InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug dist-upgrade focal
-- 
Broken upgrade from Kubuntu 18.04 to Kubuntu 20.04
https://bugs.launchpad.net/bugs/1875256
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apt in Ubuntu.

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

[Touch-packages] [Bug 1875828] Re: [HDA-Intel - HDA Intel PCH, playback] Hum problem

[Adrian Jones]

uname -rs keeps returning the Linux 5.4.0-28-generic despite having
upgraded the kernel to either of the solutions you mentioned.. it says
it has upgraded successfully then after the reboot returns the same
variant.

This is the sort of problem I would have expected from a beta release
and most certainly not a LTS

I know this is done with volunteers but as a basic user I should not
have to be replacing kernels ...   I'm still not sure why I am trying to
replace a kernel when the Gnome variant is still not updating ..  are
they the one and the same? if they are why are they on different
variants? if they aren't then what I am doing tinkering with the kernel?

there is no clear place that outlines the relationships between the
various components .. its just assumed knowledge!

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Hum problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On upgrading from Ubuntu 18LTS  to 20.04LTS I find that if I stop
  playing sound 5 seconds after stopping any correctly playing sounds
  (video / music / radio / system ) a loud hum starts in both speakers.
  This is volume independent.  Before the speakers would just turn off
  automatically and go into standby mode.

  expected action...stop playing a sound and speakers go
  silent

  current action ..   stop playing a sound and 5 seconds later
  speakers go from silent to a loud volume independent hum

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adrian 2706 F pulseaudio
   /dev/snd/pcmC0D0p:   adrian 2706 F...m pulseaudio
   /dev/snd/controlC1:  adrian 2706 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 10:13:38 2020
  InstallationDate: Installed on 2018-05-20 (709 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] (SB1570 SB 
Audigy Fx) - HDA Creative
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago)
  dmi.bios.date: 11/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: 7438200-003
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd11/07/2017:svnNOVATECHLTD:pnMBB-71004:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-71004
  dmi.product.sku: MBB-71004
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875828/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

[hugh chao]

@Kai,

Please help to take a look on #18,
then let's decide next step, thanks.

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1875684] Re: Can't connect to Pulseaudio after user change on Lubuntu 20.04

[Sebastien Bacher]

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

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

Title:
  Can't connect to Pulseaudio after user change on Lubuntu 20.04

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On fresh install of Lubuntu 20.04:
  - First login after Computer startup, no sound problem.
  - User Account logout and login to another account => Very often, the sound 
is off (with a prohibited sign instead of the speaker in the dashboard).
  And the status of Pulse audio is "connecting" when I call pavucontrol.

  The way to get the sound again is to lauch pulseaudio in a terminal or to 
reboot the computer.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maryline   2909 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-24 (5 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/13/2006
  dmi.bios.vendor: IBM
  dmi.bios.version: 2EKT37AUS
  dmi.board.name: IBM
  dmi.board.vendor: IBM
  dmi.chassis.asset.tag: �
  dmi.chassis.type: 4
  dmi.chassis.vendor: IBM
  dmi.modalias: 
dmi:bvnIBM:bvr2EKT37AUS:bd06/13/2006:svnIBM:pn9210WD5:pvrThinkCentreM52:rvnIBM:rnIBM:rvr:cvnIBM:ct4:cvr:
  dmi.product.name: 9210WD5
  dmi.product.version: ThinkCentre M52
  dmi.sys.vendor: IBM
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-04-24T17:22:11.318971

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875684/+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 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters

[Christian Reis]

Note that same udevd rule exists as far back as 16.04 LTS:

ubuntu@xenial-test:~$ md5sum /lib/udev/rules.d/40-vm-hotadd.rules
d8569b53b5bd1874a86b743b82a2a5b4  /lib/udev/rules.d/40-vm-hotadd.rules

ubuntu@focal-test:~$ md5sum /usr/lib/udev/rules.d/40-vm-hotadd.rules
d8569b53b5bd1874a86b743b82a2a5b4  /usr/lib/udev/rules.d/40-vm-hotadd.rules

There is a previous bug,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457 which
addressed a different symptom but may be related.

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

Title:
  40-vm-hotadd.rules attempts to set non-existent sysfs parameters

Status in systemd package in Ubuntu:
  New

Bug description:
  In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
  tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
  resulting in warnings such as:

  Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
  /usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
  ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
  argument

  Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
  removed, or something else. This behavior is present on systems
  upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
  first reboot of the VM.

  udev: 245.4-4ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[Carmen]

I have the same issue with Anker Soundcore Life p2, the microphone doesnt work, 
as i can't connect them in HSP/HFP mode. I get the following error:
 [pulseaudio] module-bluez5-device.c: Refused to switch profile to 
headset_head_unit: Not connected
I use Ubuntu 18.04 and run out of ideas on what to do to get over that

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+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 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed

[Pali]

"Automatically switch to HSP/HFP when an application is requesting to
record the microphone. When it stops, revert back to A2DP."

Pulseaudio is already doing this for applications which registers to
pulseaudio with "phone" media role, what VOIP applications should do.

You can test it with command line application parec which put on stdout
recorded microphone stream:

$ parec --property=media.role=phone

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

Title:
  Add automatic switching to HSP/HFP from A2DP when a mic is needed

Status in PulseAudio:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1875684] ProcCpuinfoMinimal.txt

[Tos]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1875684/+attachment/5363976/+files/ProcCpuinfoMinimal.txt

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

Title:
  Can't connect to Pulseaudio after user change on Lubuntu 20.04

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On fresh install of Lubuntu 20.04:
  - First login after Computer startup, no sound problem.
  - User Account logout and login to another account => Very often, the sound 
is off (with a prohibited sign instead of the speaker in the dashboard).
  And the status of Pulse audio is "connecting" when I call pavucontrol.

  The way to get the sound again is to lauch pulseaudio in a terminal or to 
reboot the computer.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maryline   2909 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-24 (5 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/13/2006
  dmi.bios.vendor: IBM
  dmi.bios.version: 2EKT37AUS
  dmi.board.name: IBM
  dmi.board.vendor: IBM
  dmi.chassis.asset.tag: �
  dmi.chassis.type: 4
  dmi.chassis.vendor: IBM
  dmi.modalias: 
dmi:bvnIBM:bvr2EKT37AUS:bd06/13/2006:svnIBM:pn9210WD5:pvrThinkCentreM52:rvnIBM:rnIBM:rvr:cvnIBM:ct4:cvr:
  dmi.product.name: 9210WD5
  dmi.product.version: ThinkCentre M52
  dmi.sys.vendor: IBM
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-04-24T17:22:11.318971

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875684/+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 1875684] ProcEnviron.txt

[Tos]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1875684/+attachment/5363977/+files/ProcEnviron.txt

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

Title:
  Can't connect to Pulseaudio after user change on Lubuntu 20.04

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On fresh install of Lubuntu 20.04:
  - First login after Computer startup, no sound problem.
  - User Account logout and login to another account => Very often, the sound 
is off (with a prohibited sign instead of the speaker in the dashboard).
  And the status of Pulse audio is "connecting" when I call pavucontrol.

  The way to get the sound again is to lauch pulseaudio in a terminal or to 
reboot the computer.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maryline   2909 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-24 (5 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/13/2006
  dmi.bios.vendor: IBM
  dmi.bios.version: 2EKT37AUS
  dmi.board.name: IBM
  dmi.board.vendor: IBM
  dmi.chassis.asset.tag: �
  dmi.chassis.type: 4
  dmi.chassis.vendor: IBM
  dmi.modalias: 
dmi:bvnIBM:bvr2EKT37AUS:bd06/13/2006:svnIBM:pn9210WD5:pvrThinkCentreM52:rvnIBM:rnIBM:rvr:cvnIBM:ct4:cvr:
  dmi.product.name: 9210WD5
  dmi.product.version: ThinkCentre M52
  dmi.sys.vendor: IBM
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-04-24T17:22:11.318971

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875684/+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 1872145] Re: explicit key offered after all agent keys, auth can fail before explicit key used

[Christian Ehrhardt ]

@RCJ - can you help by testing the PPA that I provided and chime in on
the upstream discussion to get things moving a bit better - just to show
that people would really care about this feature.

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

Title:
  explicit key offered after all agent keys, auth can fail before
  explicit key used

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged
Status in openssh package in Debian:
  New

Bug description:
  A user creates an ssh key and specifies it on the cmdline with 'ssh -i
  new_key user@host'.  The connection fails with the message "Too many
  authentication failures" displayed to the user.

  This would lead the user to believe that they failed to put the public
  portion of the new key on the destination and it will probably be hard
  for the average user to debug this.

  The root of this issue is that the user has a number of keys in
  ~/.ssh/ registered with their ssh agent.  The ssh command is offering
  each of these keys from the agent to the remote system before trying
  the explicit key from the command line.  There are enough agent keys
  to reach the failure limit (usually 5 keys) with the remote before
  they get to the explicit key.

  The solution today for the user is to head down into the ssh_config
  man page to find '-o IdentitiesOnly=yes' to skip the agent keys and
  only use the specified key.  But they're unlikely to do this because
  '-i' in the ssh man page doesn't suggest this and they'd only look for
  this if they actually understood the root cause of the problem, which
  is a bit cruel.

  We should consider changing the order of the keys offered to the
  remote to use explicit keys first followed by agent keys.  It would
  seem to me that this would honor the users intent of explicitly
  specifying a key to use.

  The current order makes this difficult for anyone fielding a user's
  authentication failure report as they must double check that ssh
  managed to actually try the key the user specified before it raised an
  error message about authentication failures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1872145/+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 1875684] CurrentDmesg.txt

[Tos]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1875684/+attachment/5363974/+files/CurrentDmesg.txt

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

Title:
  Can't connect to Pulseaudio after user change on Lubuntu 20.04

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On fresh install of Lubuntu 20.04:
  - First login after Computer startup, no sound problem.
  - User Account logout and login to another account => Very often, the sound 
is off (with a prohibited sign instead of the speaker in the dashboard).
  And the status of Pulse audio is "connecting" when I call pavucontrol.

  The way to get the sound again is to lauch pulseaudio in a terminal or to 
reboot the computer.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maryline   2909 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-24 (5 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/13/2006
  dmi.bios.vendor: IBM
  dmi.bios.version: 2EKT37AUS
  dmi.board.name: IBM
  dmi.board.vendor: IBM
  dmi.chassis.asset.tag: �
  dmi.chassis.type: 4
  dmi.chassis.vendor: IBM
  dmi.modalias: 
dmi:bvnIBM:bvr2EKT37AUS:bd06/13/2006:svnIBM:pn9210WD5:pvrThinkCentreM52:rvnIBM:rnIBM:rvr:cvnIBM:ct4:cvr:
  dmi.product.name: 9210WD5
  dmi.product.version: ThinkCentre M52
  dmi.sys.vendor: IBM
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-04-24T17:22:11.318971

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875684/+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 1875684] Dependencies.txt

[Tos]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1875684/+attachment/5363975/+files/Dependencies.txt

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

Title:
  Can't connect to Pulseaudio after user change on Lubuntu 20.04

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On fresh install of Lubuntu 20.04:
  - First login after Computer startup, no sound problem.
  - User Account logout and login to another account => Very often, the sound 
is off (with a prohibited sign instead of the speaker in the dashboard).
  And the status of Pulse audio is "connecting" when I call pavucontrol.

  The way to get the sound again is to lauch pulseaudio in a terminal or to 
reboot the computer.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maryline   2909 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-24 (5 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/13/2006
  dmi.bios.vendor: IBM
  dmi.bios.version: 2EKT37AUS
  dmi.board.name: IBM
  dmi.board.vendor: IBM
  dmi.chassis.asset.tag: �
  dmi.chassis.type: 4
  dmi.chassis.vendor: IBM
  dmi.modalias: 
dmi:bvnIBM:bvr2EKT37AUS:bd06/13/2006:svnIBM:pn9210WD5:pvrThinkCentreM52:rvnIBM:rnIBM:rvr:cvnIBM:ct4:cvr:
  dmi.product.name: 9210WD5
  dmi.product.version: ThinkCentre M52
  dmi.sys.vendor: IBM
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-04-24T17:22:11.318971

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875684/+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 1875684] Re: Can't connect to Pulseaudio after user change on Lubuntu 20.04

[Tos]

apport information

** Tags added: apport-collected

** Description changed:

  On fresh install of Lubuntu 20.04:
  - First login after Computer startup, no sound problem.
  - User Account logout and login to another account => Very often, the sound 
is off (with a prohibited sign instead of the speaker in the dashboard).
  And the status of Pulse audio is "connecting" when I call pavucontrol.
  
- The way to get the sound again is to lauch pulseaudio in a terminal or
- to reboot the computer.
+ The way to get the sound again is to lauch pulseaudio in a terminal or to 
reboot the computer.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  maryline   2909 F pulseaudio
+ CasperMD5CheckResult: skip
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-04-24 (5 days ago)
+ InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ Package: pulseaudio 1:13.99.1-1ubuntu3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ Tags:  focal
+ Uname: Linux 5.4.0-26-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 06/13/2006
+ dmi.bios.vendor: IBM
+ dmi.bios.version: 2EKT37AUS
+ dmi.board.name: IBM
+ dmi.board.vendor: IBM
+ dmi.chassis.asset.tag: �
+ dmi.chassis.type: 4
+ dmi.chassis.vendor: IBM
+ dmi.modalias: 
dmi:bvnIBM:bvr2EKT37AUS:bd06/13/2006:svnIBM:pn9210WD5:pvrThinkCentreM52:rvnIBM:rnIBM:rvr:cvnIBM:ct4:cvr:
+ dmi.product.name: 9210WD5
+ dmi.product.version: ThinkCentre M52
+ dmi.sys.vendor: IBM
+ modified.conffile..etc.pulse.default.pa: [modified]
+ mtime.conffile..etc.pulse.default.pa: 2020-04-24T17:22:11.318971

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1875684/+attachment/5363973/+files/AlsaInfo.txt

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

Title:
  Can't connect to Pulseaudio after user change on Lubuntu 20.04

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On fresh install of Lubuntu 20.04:
  - First login after Computer startup, no sound problem.
  - User Account logout and login to another account => Very often, the sound 
is off (with a prohibited sign instead of the speaker in the dashboard).
  And the status of Pulse audio is "connecting" when I call pavucontrol.

  The way to get the sound again is to lauch pulseaudio in a terminal or to 
reboot the computer.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maryline   2909 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-24 (5 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/13/2006
  dmi.bios.vendor: IBM
  dmi.bios.version: 2EKT37AUS
  dmi.board.name: IBM
  dmi.board.vendor: IBM
  dmi.chassis.asset.tag: �
  dmi.chassis.type: 4
  dmi.chassis.vendor: IBM
  dmi.modalias: 
dmi:bvnIBM:bvr2EKT37AUS:bd06/13/2006:svnIBM:pn9210WD5:pvrThinkCentreM52:rvnIBM:rnIBM:rvr:cvnIBM:ct4:cvr:
  dmi.product.name: 9210WD5
  dmi.product.version: ThinkCentre M52
  dmi.sys.vendor: IBM
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-04-24T17:22:11.318971

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875684/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

[Hui Wang]

Looks like this SRU introduced a regression in the focal and a couple of
related bugs are filed by ubuntu 20.04 users (at least most of Dell
machines will be affected):

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249
https://bugs.launchpad.net/bugs/1873384
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875032
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875714

Although this SRU is based on my work of Jan 2019
(https://lists.freedesktop.org/archives/pulseaudio-
discuss/2019-January/030761.html), it has been a long time, I already
forgot the detail about my patches.

So Kaiheng and Hugh, please take a look at this issue again, maybe the
regression was already in my original patches or maybe your rebasement
on focal introduced the regression.

thx.

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1876056] Re: No automatic switch to headset microphone on connect

[Hui Wang]

Please take a look at #1876065, maybe they have the same rootcause. But
you mentioned pulseaudio 1:13.0-1ubuntu1.1, so I didn't duplicate your
bug to that one.

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

Title:
  No automatic switch to headset microphone on connect

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On my Dell XPS 7590, when I plugin a headset with a 4-pin-connector,
  the audio OUTPUT automatically switches from the speakers in the
  laptop to the headset. However, the audio INPUT does not switch from
  the microphone in the laptop to the microphone in the headset.

  Using for example pavucontrol, I can switch to the microphone manually
  on the tab 'input devices' - on that tab Port will be on 'Internal
  Microphone' and I can set it to 'Headset Microphone'.

  What's even more confusing is that when I unplug the headset, both
  input AND output switch back to internal automatically and the port on
  the 'Input Devices'.

  This is on Ubuntu 19.10 with kernel 5.4.28-050428-generic (but I also
  see the same issue on kernel 5.3.0-48) and pulseaudio
  1:13.0-1ubuntu1.1.

  If any more information is needed, let me know.

  inxi -F:

  System:Host: idefixpsie Kernel: 5.4.28-050428-generic x86_64 bits: 64 
Desktop: KDE Plasma 5.16.5 
 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: Dell product: XPS 15 7590 v: N/A serial: 
 
 Mobo: Dell model: 0VYV0G v: A00 serial:  UEFI: Dell 
v: 1.5.0 date: 12/25/2019 
  Battery:   ID-1: BAT0 charge: 77.7 Wh condition: 87.4/97.0 Wh (90%) 
  CPU:   Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP 
L2 cache: 12.0 MiB 
 Speed: 4029 MHz max: 4500 MHz Core speeds (MHz): 1: 4213 2: 4160 
3: 4229 4: 4210 5: 4224 6: 4163 7: 4280 8: 4189 
 9: 4291 10: 4198 11: 4149 12: 4188 
  Graphics:  Device-1: Intel UHD Graphics 630 driver: i915 v: kernel 
 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: 
fbdev,vesa resolution: 3840x2160~60Hz 
 OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 
GT2) v: 4.5 Mesa 19.2.8 
  Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.28-050428-generic 
  Network:   Device-1: Intel driver: iwlwifi 
 IF: wlan0 state: up mac: 5c:80:b6:7a:2c:45 
 IF-ID-1: docker0 state: down mac: 02:42:90:4c:31:a2 
  Drives:Local Storage: total: 953.87 GiB used: 67.58 GiB (7.1%) 
 ID-1: /dev/nvme0n1 model: SSDPEMKF010T8 NVMe INTEL 1024GB size: 
953.87 GiB 
  Partition: ID-1: / size: 496.44 GiB used: 67.27 GiB (13.6%) fs: ext4 dev: 
/dev/dm-1 
 ID-2: /boot size: 704.5 MiB used: 288.4 MiB (40.9%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-3: swap-1 size: 6.61 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/dm-2 
  Sensors:   System Temperatures: cpu: 47.0 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 346 Uptime: 2d 17h 51m Memory: 31.12 GiB used: 9.08 GiB 
(29.2%) Shell: bash inxi: 3.0.36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056/+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 1875697] Re: drop fix-ldap-distribution.patch?

[Andreas Hasenack]

I'm adding this to my list of delta to drop in this cycle.

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

Title:
  drop fix-ldap-distribution.patch?

Status in openldap package in Ubuntu:
  Triaged
Status in openldap source package in Focal:
  Triaged

Bug description:
  Hi,

  In version 2.4.49+dfsg-3 I fixed a bug where the version was missing
  from the -V output in OpenLDAP programs:
  .

  At the same time, I've patched it to display the package version
  there, instead of the upstream version:

  # slapd -VV
  @(#) $OpenLDAP: slapd 2.4.49+dfsg-4 (Apr 15 2020 04:33:16) $
Debian OpenLDAP Maintainers 

  If showing the distro version here fulfills the same requirements as
  the fix-ldap-distribution.patch, then maybe that patch can be dropped?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1875697/+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 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Hui Wang]

Looks like the fix of this bug (https://bugs.launchpad.net/oem-
priority/+bug/1869819) introduced this regression.

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1875714] Re: No sound from headphones

[Hui Wang]

*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065

will fix it in the ubuntu pulseaudio.


** This bug has been marked a duplicate of bug 1876065
   After unplug headphones and plug them again no sound can be heard

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

Title:
  No sound from headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi,

  I upgraded to focal and since then I have the following problems with
  my audio on my laptop:

  1. If I start my laptop with my headphones pluged-in I initially have
  sound from my headphones, If I unplug my headphones speakers work
  normally. But when insert my headphone again the sound stops from the
  speakers but I have no sound from my headphones. To "fix" the problem
  I have to go to the kde systemsettings and in "audio" settings in the
  advanced tab change the profile to something else and then restore the
  option.

  If I start the laptop WITHOUT the headphones pluged-in then everything
  works as it should. I have deleted the ~./config/pulse folder but it
  changes nothing.

  2. If the computer starts WITHOUT headphones and the computer goes
  into hibernation when it wakes I get a static noise from the speakers
  (although the headphones are plugined-in) I have to reboot the
  computer in order to fix this.

  Kind Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Apr 28 21:37:41 2020
  InstallationDate: Installed on 2018-11-22 (523 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to focal on 2020-04-26 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875714/+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 1875032] Re: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at all

[Hui Wang]

*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065

will fix it in the ubuntu pulseaudio.


** This bug has been marked a duplicate of bug 1876065
   After unplug headphones and plug them again no sound can be heard

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

Title:
  [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This problem only occurs when I plug my headphone and choose Headphone in 
option.
  If I choose Headset, though plugging either headphone or headset, it works 
perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prm1856 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 20:05:01 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  InstallationDate: Installed on 2018-09-28 (575 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prm1856 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at 
all
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 05/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.13.0
  dmi.board.name: 03NJH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.13.0:bd05/29/2019:svnDellInc.:pnVostro3470:pvr:rvnDellInc.:rn03NJH0:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3470
  dmi.product.sku: 0869
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875032/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

[Hui Wang]

[ 14.652221] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0
This message is common on all machine with sof driver, so we could ignore it.

According to dmesg in the #15, the kernel driver already worked. you
could run "aplay -l" to check (sorry, not alsa -l).

So after update the Hdmi.conf, your audio should work. and there is no
errors anymore in the dmesg of #17. I have no idea why it stuck at a
black screen.

-25 kernel is based on the ubuntu 5.4.0-25-generic kernel, so it lacks
the fix in the -26 kernel, maybe the brightness adjustment fix is in the
-26 kernel.

So if you restore the Hdmi.conf, your -25 kernel could login?

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+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 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones

[Hui Wang]

*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065

Will fix it in the ubuntu pluseaudio.


** This bug has been marked a duplicate of bug 1876065
   After unplug headphones and plug them again no sound can be heard

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

Title:
  [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No
  sound output from earphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is
  no sound output when you plug an earphone/headset. The built-in
  speakers, on the other hand, are working properly. This is a laptop,
  Dell Inspiron 11 3162.

  I checked volume levels with alsamixer, I played with the device
  selection in the Pulseaudio mixer application, but nothing worked. I
  also tested Firefox (playing a YouTube video) and system sounds. None
  of them worked. The audio test made by apport-bug played no sound
  through the earphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 26 18:12:06 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.

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

[Adrian Jones]

thank you for helping but that means nothing to me ...

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Hum problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On upgrading from Ubuntu 18LTS  to 20.04LTS I find that if I stop
  playing sound 5 seconds after stopping any correctly playing sounds
  (video / music / radio / system ) a loud hum starts in both speakers.
  This is volume independent.  Before the speakers would just turn off
  automatically and go into standby mode.

  expected action...stop playing a sound and speakers go
  silent

  current action ..   stop playing a sound and 5 seconds later
  speakers go from silent to a loud volume independent hum

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adrian 2706 F pulseaudio
   /dev/snd/pcmC0D0p:   adrian 2706 F...m pulseaudio
   /dev/snd/controlC1:  adrian 2706 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 10:13:38 2020
  InstallationDate: Installed on 2018-05-20 (709 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] (SB1570 SB 
Audigy Fx) - HDA Creative
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago)
  dmi.bios.date: 11/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: 7438200-003
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd11/07/2017:svnNOVATECHLTD:pnMBB-71004:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-71004
  dmi.product.sku: MBB-71004
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875828/+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 1873384] Re: [Dell Inspiron 5577] Headphone has no sound out

[Hui Wang]

*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065

will fix it in the ubuntu pulseaudio.


** This bug has been marked a duplicate of bug 1876065
   After unplug headphones and plug them again no sound can be heard

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

Title:
  [Dell Inspiron 5577] Headphone has no sound out

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Computer:
  Dell inspiron 15 5577 Gaming
  intel i5 7300HQ version
  System:
  Kubuntu 20.04
  Bug:
  Plug-in headphone has no sound out, meanwhile computer's speaker is okay when 
unplugged the headphone.
  Additional information:
  Headphone is okay when kubuntu 18.04.3 is installed on the computer.
  Alsamixer is checked and headphone are not mute.
  Headphone plugin state can be correctly detected, and speaker can 
automatically mute until headphone unplugged.
  External usb soundcard is usable with headphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.12
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 17 11:14:43 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash nomodeset ---
  InstallationDate: Installed on 2020-04-16 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sherlockholmes   1242 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-16 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416)
  MachineType: Dell Inc. Inspiron 5577
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic 
root=UUID=18303cc3-5e85-4677-8bca-60324bae9608 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-24-generic N/A
   linux-backports-modules-5.4.0-24-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 090HMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn090HMC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5577
  dmi.product.sku: 07E1
  dmi.product.version: 1.1.3
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873384/+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 1876056] Re: No automatic switch to headset microphone on connect

[Egbert van der Wal]

@seb128 yes you are right. The explanation there makes a lot of sense -
after some experimentation I found that the headset mic becomes
available no matter whether I plugin a headphones or a headset, so it
doesn't actually detect the presence of a microphone, it just happens
that something is plugged in.

However, that issue also mentions:

> Ubuntu solves this by popping up a GUI that asks what you plugged in.

This seems like a sane thing to do in this situation. As I'm using
Kubuntu and not Ubuntu, where should this feature be requested?

For the time being, I added the two suggested sections to
/usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf

[Jack Headphone Mic]
state.plugged = no
state.unplugged = unknown

[Jack Headset Mic]
state.plugged = no
state.unplugged = unknown

This works beautifully. But now, indeed, when I plug in a regular
headset without a microphone it will still switch making me effectively
muted.

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

Title:
  No automatic switch to headset microphone on connect

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On my Dell XPS 7590, when I plugin a headset with a 4-pin-connector,
  the audio OUTPUT automatically switches from the speakers in the
  laptop to the headset. However, the audio INPUT does not switch from
  the microphone in the laptop to the microphone in the headset.

  Using for example pavucontrol, I can switch to the microphone manually
  on the tab 'input devices' - on that tab Port will be on 'Internal
  Microphone' and I can set it to 'Headset Microphone'.

  What's even more confusing is that when I unplug the headset, both
  input AND output switch back to internal automatically and the port on
  the 'Input Devices'.

  This is on Ubuntu 19.10 with kernel 5.4.28-050428-generic (but I also
  see the same issue on kernel 5.3.0-48) and pulseaudio
  1:13.0-1ubuntu1.1.

  If any more information is needed, let me know.

  inxi -F:

  System:Host: idefixpsie Kernel: 5.4.28-050428-generic x86_64 bits: 64 
Desktop: KDE Plasma 5.16.5 
 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: Dell product: XPS 15 7590 v: N/A serial: 
 
 Mobo: Dell model: 0VYV0G v: A00 serial:  UEFI: Dell 
v: 1.5.0 date: 12/25/2019 
  Battery:   ID-1: BAT0 charge: 77.7 Wh condition: 87.4/97.0 Wh (90%) 
  CPU:   Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP 
L2 cache: 12.0 MiB 
 Speed: 4029 MHz max: 4500 MHz Core speeds (MHz): 1: 4213 2: 4160 
3: 4229 4: 4210 5: 4224 6: 4163 7: 4280 8: 4189 
 9: 4291 10: 4198 11: 4149 12: 4188 
  Graphics:  Device-1: Intel UHD Graphics 630 driver: i915 v: kernel 
 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: 
fbdev,vesa resolution: 3840x2160~60Hz 
 OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 
GT2) v: 4.5 Mesa 19.2.8 
  Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.28-050428-generic 
  Network:   Device-1: Intel driver: iwlwifi 
 IF: wlan0 state: up mac: 5c:80:b6:7a:2c:45 
 IF-ID-1: docker0 state: down mac: 02:42:90:4c:31:a2 
  Drives:Local Storage: total: 953.87 GiB used: 67.58 GiB (7.1%) 
 ID-1: /dev/nvme0n1 model: SSDPEMKF010T8 NVMe INTEL 1024GB size: 
953.87 GiB 
  Partition: ID-1: / size: 496.44 GiB used: 67.27 GiB (13.6%) fs: ext4 dev: 
/dev/dm-1 
 ID-2: /boot size: 704.5 MiB used: 288.4 MiB (40.9%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-3: swap-1 size: 6.61 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/dm-2 
  Sensors:   System Temperatures: cpu: 47.0 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 346 Uptime: 2d 17h 51m Memory: 31.12 GiB used: 9.08 GiB 
(29.2%) Shell: bash inxi: 3.0.36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056/+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 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Launchpad Bug Tracker]

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

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

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1875828] Re: [HDA-Intel - HDA Intel PCH, playback] Hum problem

[Hui Wang]

For example, to install mainline kernel 5.2-rc6:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc6/

or mainline kernel 5.0: https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.0

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Hum problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On upgrading from Ubuntu 18LTS  to 20.04LTS I find that if I stop
  playing sound 5 seconds after stopping any correctly playing sounds
  (video / music / radio / system ) a loud hum starts in both speakers.
  This is volume independent.  Before the speakers would just turn off
  automatically and go into standby mode.

  expected action...stop playing a sound and speakers go
  silent

  current action ..   stop playing a sound and 5 seconds later
  speakers go from silent to a loud volume independent hum

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adrian 2706 F pulseaudio
   /dev/snd/pcmC0D0p:   adrian 2706 F...m pulseaudio
   /dev/snd/controlC1:  adrian 2706 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 10:13:38 2020
  InstallationDate: Installed on 2018-05-20 (709 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] (SB1570 SB 
Audigy Fx) - HDA Creative
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago)
  dmi.bios.date: 11/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: 7438200-003
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd11/07/2017:svnNOVATECHLTD:pnMBB-71004:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-71004
  dmi.product.sku: MBB-71004
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875828/+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 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed

[kay]

I also have issues with "HSP/HFP" profile detection in apps. I have to
close an app, then manually switch profile to "HSP/HFP", then start an
app. Only then I can use microphone.

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

Title:
  Add automatic switching to HSP/HFP from A2DP when a mic is needed

Status in PulseAudio:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

[Wittawat Jitkrittum]

* Tried your Hdmi.conf. It turns out that the system did not even boot.
It did not bring me to the usual Ubuntu login GUI screen. I got stuck at
a black screen with the message

[ 14.652221] sof-audio-pci :00:1f.3: error: no reply expected,
received 0x0

* So I forced reboot and selected 5.4.0-26-generic instead, hoping that
it might boot up so I don't need to use some recovery USB. Indeed, it
did boot up.

* As I understand it, dmesg.0 is the dmesg from the previous session. So
I am attaching it here. I hope this is the right dmesg log that
corresponds to the session that gave me the sof-audio-pci error above.

Thanks

** Attachment added: "dmesg.0"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+attachment/5363958/+files/dmesg.0

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+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 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed

[t-m]

Just to clear out what the intended behavior should be:

Automatically switch to HSP/HFP when an application is requesting to
record the microphone. When it stops, revert back to A2DP.

This is how this works in other operating systems so this is what we
should aim for also in here. A2DP with a microphone is wishful thinking
and should not be pursued after.

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

Title:
  Add automatic switching to HSP/HFP from A2DP when a mic is needed

Status in PulseAudio:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed

[t-m]

Can you please describe how can I enable automatic switching?

Using Bose QC35 and fresh Ubuntu 20.04. I need to manually set the
profile when calling with MS Teasm, Google Meet, Zoom etc.

This works in Windows and MacOS perfectly so it is supported by the
device.

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

Title:
  Add automatic switching to HSP/HFP from A2DP when a mic is needed

Status in PulseAudio:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

[Wittawat Jitkrittum]

Before I try your Hdmi.conf, I am attaching my one 
(/usr/share/alsa/ucm2/sof-hda-dsp/Hdmi.conf
) in case it is relevant.

** Attachment added: "Hdmi.conf"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+attachment/5363943/+files/Hdmi.conf

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

[Wittawat Jitkrittum]

Thanks for the update.
• Removed the previous kernel with sudo dpkg -r --force-all 
linux-image-unsigned-5.4.0-25-generic
• Downloaded and installed v3 with sudo dpkg -i *.dev. Got

--
Processing triggers for linux-image-unsigned-5.4.0-25-generic 
(5.4.0-25.29+skiphdmiv3) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.4.0-25-generic
ACPI disabled in this kernel, not building module.
Error!  The /var/lib/dkms/acpi-call/1.1.0/5.4.0-25-generic/x86_64/dkms.conf for 
module acpi-call includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch.  This indicates that it should not be built.
Error! Your kernel headers for kernel 5.4.0-25-generic cannot be found.
Please install the linux-headers-5.4.0-25-generic package,
or use the --kernelsourcedir option to tell DKMS where it's located
-

• Anyway, I proceeded. Comment out "options snd-intel-dspcfg dsp_driver=1
" in alsa-base.conf. And rebooted.
* No sound. "Dummy output" on pavucontrol
* Attaching full dmesg log and alsa-info: 
http://alsa-project.org/db/?f=8c55fd41cbd662c08dd8a21bf8d73817dbb8b7d2
* alsa -l: the -l flag is not a valid option for alsa command on my system. 

 
wittawat@omen:~$ inxi -Ax
Audio: Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard driver: 
sof-audio-pci bus ID: 00:1f.3 
   Device-2: NVIDIA TU106 High Definition Audio vendor: Hewlett-Packard 
driver: snd_hda_intel v: kernel 
   bus ID: 01:00.1 
   Sound Server: ALSA v: k5.4.0-25-generic 


* This report is based on Hdmi.conf on my machine. I can try Hdmi.conf
that you sent. Will post again.

* By the way, in all versions of the 5.4.0-25 kernel you sent, I could
not change the brightness of my display. I guess there is something to
do with ACPI.

Thanks.


** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+attachment/5363942/+files/dmesg_5.4.0-25_v3.log

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+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 1875684] Re: Can't connect to Pulseaudio after user change on Lubuntu 20.04

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:

  apport-collect 1875684

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Can't connect to Pulseaudio after user change on Lubuntu 20.04

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  On fresh install of Lubuntu 20.04:
  - First login after Computer startup, no sound problem.
  - User Account logout and login to another account => Very often, the sound 
is off (with a prohibited sign instead of the speaker in the dashboard).
  And the status of Pulse audio is "connecting" when I call pavucontrol.

  The way to get the sound again is to lauch pulseaudio in a terminal or
  to reboot the computer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875684/+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 1876068] [NEW] DeprecationWarning: an integer is required

[Laurent Bonnaud]

Public bug reported:

Hi,

when I use ubuntu-bug to report a bug, I see the following python
deprecation warning:

$ ubuntu-bug apport-kde
/usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required 
(got type float).  Implicit conversion to integers using __int__ is deprecated, 
and may be removed in a future version of Python.
  progress.setValue(value * 1000)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apport-kde 2.20.11-0ubuntu27
Uname: Linux 5.6.7-050607-generic x86_64
ApportLog:
 
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu Apr 30 11:16:12 2020
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  DeprecationWarning: an integer is required

Status in apport package in Ubuntu:
  New

Bug description:
  Hi,

  when I use ubuntu-bug to report a bug, I see the following python
  deprecation warning:

  $ ubuntu-bug apport-kde
  /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required 
(got type float).  Implicit conversion to integers using __int__ is deprecated, 
and may be removed in a future version of Python.
progress.setValue(value * 1000)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport-kde 2.20.11-0ubuntu27
  Uname: Linux 5.6.7-050607-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Apr 30 11:16:12 2020
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1876068/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem

[Hui Wang]

Please test v3 kernel:
https://people.canonical.com/~hwang4/25skipi915/v3/

I guess v3 kernel will work successfully, after boot up, you could run
alsa -l to check if there is valid sound card.

and pulseaudio will have an error on your machine, so if the kernel has
no error, please backup /usr/share/alsa/ucm2/sof-hda-dsp/Hdmi.conf, and
I uploaded a new Hdmi.conf in
https://people.canonical.com/~hwang4/25skipi915/v3/, please copy this
file  /usr/share/alsa/ucm2/sof-hda-dsp/

then reboot.

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+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 1876035] Re: Consider making '-o Acquire::Retries=3' the default for 'apt-get update/install/dist-upgrade'

[Sebastien Bacher]

** Tags added: champagne

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

Title:
  Consider making '-o Acquire::Retries=3' the default for 'apt-get
  update/install/dist-upgrade'

Status in apt package in Ubuntu:
  New

Bug description:
  Hi,

  We operate archive.ubuntu.com as well as mirrors of it in various
  places. We're getting reports of various CI/CD jobs failing. Sometimes
  due to routing issues, issues with overloaded servers/VMs hosting
  archive, etc.

  Any chance we can make '-o Acquire::Retries=3' the default for 'apt-
  get update/install/dist-upgrade'? Preferably with a randomised skew
  between retries.

  Also, any chance of having apt-get retry with different IPs/hosts
  returned from the DNS lookup? (e.g. for archive.ubuntu.com -
  91.189.88.142, 91.189.88.152, ...).

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876035/+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 1876071] [NEW] text cursor is moved to start of line even if in login prompt

[Norbert]

Public bug reported:

Steps to reproduce:
1. Have Ubuntu 20.04 LTS installed
2. Switch to text tty with ++
3. Enter login, press 

Expected results:
* after pressing  the cursor is located next to ":" in "Password:"

Actual results:
* after pressing  the cursor is moved in the beginning of the line with 
"Password:"
* in some case the cursor is located at the first symbol of hostname like in 
the attached screenshot

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Apr 30 12:33:12 2020
InstallationDate: Installed on 2020-04-24 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=e3b26c22-1835-445d-955d-9221190a83ed ro quiet splash
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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

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


** Tags: amd64 apport-bug focal

** Attachment added: "cursor is located on the first letter of the hostname"
   https://bugs.launchpad.net/bugs/1876071/+attachment/5363922/+files/login.png

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

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

Title:
  text cursor is moved to start of line even if in login prompt

Status in systemd package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Switch to text tty with ++
  3. Enter login, press 

  Expected results:
  * after pressing  the cursor is located next to ":" in "Password:"

  Actual results:
  * after pressing  the cursor is moved in the beginning of the line 
with "Password:"
  * in some case the cursor is located at the first symbol of hostname like in 
the attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Apr 30 12:33:12 2020
  InstallationDate: Installed on 2020-04-24 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=e3b26c22-1835-445d-955d-9221190a83ed ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: 

[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Daniel van Vugt]

** Tags added: focal

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1876056] Re: No automatic switch to headset microphone on connect

[Sebastien Bacher]

Could be the same as
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/194

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

Title:
  No automatic switch to headset microphone on connect

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On my Dell XPS 7590, when I plugin a headset with a 4-pin-connector,
  the audio OUTPUT automatically switches from the speakers in the
  laptop to the headset. However, the audio INPUT does not switch from
  the microphone in the laptop to the microphone in the headset.

  Using for example pavucontrol, I can switch to the microphone manually
  on the tab 'input devices' - on that tab Port will be on 'Internal
  Microphone' and I can set it to 'Headset Microphone'.

  What's even more confusing is that when I unplug the headset, both
  input AND output switch back to internal automatically and the port on
  the 'Input Devices'.

  This is on Ubuntu 19.10 with kernel 5.4.28-050428-generic (but I also
  see the same issue on kernel 5.3.0-48) and pulseaudio
  1:13.0-1ubuntu1.1.

  If any more information is needed, let me know.

  inxi -F:

  System:Host: idefixpsie Kernel: 5.4.28-050428-generic x86_64 bits: 64 
Desktop: KDE Plasma 5.16.5 
 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: Dell product: XPS 15 7590 v: N/A serial: 
 
 Mobo: Dell model: 0VYV0G v: A00 serial:  UEFI: Dell 
v: 1.5.0 date: 12/25/2019 
  Battery:   ID-1: BAT0 charge: 77.7 Wh condition: 87.4/97.0 Wh (90%) 
  CPU:   Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP 
L2 cache: 12.0 MiB 
 Speed: 4029 MHz max: 4500 MHz Core speeds (MHz): 1: 4213 2: 4160 
3: 4229 4: 4210 5: 4224 6: 4163 7: 4280 8: 4189 
 9: 4291 10: 4198 11: 4149 12: 4188 
  Graphics:  Device-1: Intel UHD Graphics 630 driver: i915 v: kernel 
 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: 
fbdev,vesa resolution: 3840x2160~60Hz 
 OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 
GT2) v: 4.5 Mesa 19.2.8 
  Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.28-050428-generic 
  Network:   Device-1: Intel driver: iwlwifi 
 IF: wlan0 state: up mac: 5c:80:b6:7a:2c:45 
 IF-ID-1: docker0 state: down mac: 02:42:90:4c:31:a2 
  Drives:Local Storage: total: 953.87 GiB used: 67.58 GiB (7.1%) 
 ID-1: /dev/nvme0n1 model: SSDPEMKF010T8 NVMe INTEL 1024GB size: 
953.87 GiB 
  Partition: ID-1: / size: 496.44 GiB used: 67.27 GiB (13.6%) fs: ext4 dev: 
/dev/dm-1 
 ID-2: /boot size: 704.5 MiB used: 288.4 MiB (40.9%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-3: swap-1 size: 6.61 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/dm-2 
  Sensors:   System Temperatures: cpu: 47.0 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 346 Uptime: 2d 17h 51m Memory: 31.12 GiB used: 9.08 GiB 
(29.2%) Shell: bash inxi: 3.0.36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056/+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 1875985] Re: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => 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/1875985

Title:
  [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all
  after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  VERSION="18.04.4 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.4 LTS"

  Running it in the flavour of Xubuntu.

  Just like in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916 my sound
  stopped working with the new kernel "4.15.0-99-generic #100-Ubuntu SMP
  Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux".

  Rebooting into "4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46
  UTC 2020 x86_64 x86_64 x86_64 GNU/Linux" sound works again.

  With 4.15.0-99-generic I do see a signal on the meters of the
  sound/volume control app, but physically there is no sound on either
  internal speakers nor on the headphones.

  
  With 4.15.0-96-generic everything is back to normal.

  My touchpad is working though (#1875916 seems to suggest that the
  touchpad stops working with 4.15.0-99-generic).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rkm1814 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 29 23:45:15 2020
  InstallationDate: Installed on 2016-10-20 (1287 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rkm1814 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-08-31 (607 days ago)
  dmi.bios.date: 05/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.03.00
  dmi.board.name: 0RJ0RW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.03.00:bd05/26/2016:svnDellInc.:pnInspiron13-5368:pvr:rvnDellInc.:rn0RJ0RW:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-5368
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875985/+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 1876056] Re: No automatic switch to headset microphone on connect

[Sebastien Bacher]

Thank you for your bug report, could you report it upstream on
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/ ?

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

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #194
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/194

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

Title:
  No automatic switch to headset microphone on connect

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On my Dell XPS 7590, when I plugin a headset with a 4-pin-connector,
  the audio OUTPUT automatically switches from the speakers in the
  laptop to the headset. However, the audio INPUT does not switch from
  the microphone in the laptop to the microphone in the headset.

  Using for example pavucontrol, I can switch to the microphone manually
  on the tab 'input devices' - on that tab Port will be on 'Internal
  Microphone' and I can set it to 'Headset Microphone'.

  What's even more confusing is that when I unplug the headset, both
  input AND output switch back to internal automatically and the port on
  the 'Input Devices'.

  This is on Ubuntu 19.10 with kernel 5.4.28-050428-generic (but I also
  see the same issue on kernel 5.3.0-48) and pulseaudio
  1:13.0-1ubuntu1.1.

  If any more information is needed, let me know.

  inxi -F:

  System:Host: idefixpsie Kernel: 5.4.28-050428-generic x86_64 bits: 64 
Desktop: KDE Plasma 5.16.5 
 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: Dell product: XPS 15 7590 v: N/A serial: 
 
 Mobo: Dell model: 0VYV0G v: A00 serial:  UEFI: Dell 
v: 1.5.0 date: 12/25/2019 
  Battery:   ID-1: BAT0 charge: 77.7 Wh condition: 87.4/97.0 Wh (90%) 
  CPU:   Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP 
L2 cache: 12.0 MiB 
 Speed: 4029 MHz max: 4500 MHz Core speeds (MHz): 1: 4213 2: 4160 
3: 4229 4: 4210 5: 4224 6: 4163 7: 4280 8: 4189 
 9: 4291 10: 4198 11: 4149 12: 4188 
  Graphics:  Device-1: Intel UHD Graphics 630 driver: i915 v: kernel 
 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: 
fbdev,vesa resolution: 3840x2160~60Hz 
 OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 
GT2) v: 4.5 Mesa 19.2.8 
  Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel 
 Sound Server: ALSA v: k5.4.28-050428-generic 
  Network:   Device-1: Intel driver: iwlwifi 
 IF: wlan0 state: up mac: 5c:80:b6:7a:2c:45 
 IF-ID-1: docker0 state: down mac: 02:42:90:4c:31:a2 
  Drives:Local Storage: total: 953.87 GiB used: 67.58 GiB (7.1%) 
 ID-1: /dev/nvme0n1 model: SSDPEMKF010T8 NVMe INTEL 1024GB size: 
953.87 GiB 
  Partition: ID-1: / size: 496.44 GiB used: 67.27 GiB (13.6%) fs: ext4 dev: 
/dev/dm-1 
 ID-2: /boot size: 704.5 MiB used: 288.4 MiB (40.9%) fs: ext4 dev: 
/dev/nvme0n1p2 
 ID-3: swap-1 size: 6.61 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/dm-2 
  Sensors:   System Temperatures: cpu: 47.0 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 346 Uptime: 2d 17h 51m Memory: 31.12 GiB used: 9.08 GiB 
(29.2%) Shell: bash inxi: 3.0.36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056/+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 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Roman Konieczny]

Forgot to add my system details:

Dell Lattitude E5570.

Sound card:
  product: 100 Series/C230 Series Chipset Family HD Audio Controller
  vendor: Intel Corporation

System: Ubuntu Budgie 20.04 with pulseaudio version 13.99.1.

Linux 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1876065] [NEW] After unplug headphones and plug them again no sound can be heard

[Roman Konieczny]

Public bug reported:

After startup with headset plugged in they play sound nicely - no issue.
When they are unplugged, the sound is switched to the speaker (laptop) -
all good. However, when I plug the headset back there is no sound. I see
the app on pavucontrol, the volume is fine - everything looks fine
except there is no sound. I dumped output of "pactl list" command on
startup (headset plugged), after unplugging the headset, and when it is
plugged back. From the comparison of these outputs, it looks like the
source has got muted after the headset is plugged.

Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

Attached three outputs:
headset-in.txt - after startup with headset plugged - all fine.
headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
headset-back.txt - after plugged headset back - no sound.

Any help greatly appreciated.

Regards,
Roman

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

** Attachment added: "pa-issue.tar.gz"
   
https://bugs.launchpad.net/bugs/1876065/+attachment/5363918/+files/pa-issue.tar.gz

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1875828] Re: [HDA-Intel - HDA Intel PCH, playback] Hum problem

[Adrian Jones]

sorry but how do I change the kernel?   revert back totally to 18.04 ??

20 seems highly unstable with the copy/paste failure as well ..

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Hum problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On upgrading from Ubuntu 18LTS  to 20.04LTS I find that if I stop
  playing sound 5 seconds after stopping any correctly playing sounds
  (video / music / radio / system ) a loud hum starts in both speakers.
  This is volume independent.  Before the speakers would just turn off
  automatically and go into standby mode.

  expected action...stop playing a sound and speakers go
  silent

  current action ..   stop playing a sound and 5 seconds later
  speakers go from silent to a loud volume independent hum

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adrian 2706 F pulseaudio
   /dev/snd/pcmC0D0p:   adrian 2706 F...m pulseaudio
   /dev/snd/controlC1:  adrian 2706 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 10:13:38 2020
  InstallationDate: Installed on 2018-05-20 (709 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] (SB1570 SB 
Audigy Fx) - HDA Creative
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago)
  dmi.bios.date: 11/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: 7438200-003
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd11/07/2017:svnNOVATECHLTD:pnMBB-71004:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-71004
  dmi.product.sku: MBB-71004
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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