[Touch-packages] [Bug 214786] Re: Apple USB ISO keyboard has incorrectly swapped keys

[Pedro A. Aranda]

I'm having this issue with a Spanish USB Mac keyboard. Is it really so
difficult to detect when you have a Mac keyboard connected and/or
disconnected? Can't anything be done with hotplug, udev, etc. ?

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

Title:
  Apple USB ISO keyboard has incorrectly swapped keys

Status in Mactel Support:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading kernel to version 2.6.24-12.22 two keys are now
  swapped on my Apple USB aluminium keyboard with danish layout. Now the
  keys "<" and "½" are swapped and no longer matches the actual print on
  the keycaps.

  The error is isolated to the following commit:
  http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
  hardy.git;a=commitdiff;h=efb3031b446d441dca5b10619503ac0bba7f9748

  This commit introduced a key swapping for all "ISO" type Apple
  keyboards. In my case this swapping is incorrect, and generally it
  seems like a very bad idea to perform hard coded locale specific key
  mapping in kernel space as this is also done several places in user
  space.

  The included patch reverts the behavior to the default that matches
  the keycap printing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mactel-support/+bug/214786/+subscriptions

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

[Touch-packages] [Bug 1888558] Re: VLC is using up to 2 GB of RAM just to play a regular 720px HD video

[Launchpad Bug Tracker]

[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  VLC is using up to 2 GB of RAM just to play a regular 720px HD video

Status in mesa package in Ubuntu:
  Expired

Bug description:
  On my computer running Ubuntu 20.04 and XFCE desktop, The VLC GUI
  player is using an increasing amount of memory as time progressed. The
  video is a typical H.264 movie (MP4 file format). I have let the
  application sit for a few days, and here is the usage of RAM as the
  days went by:

  Date   Time(EDT) VSIZE   RSS
  2020-07-19 20:19:162848984455148
  2020-07-20 13:09:063307736926156
  2020-07-22 13:18:054487464   2059848

  The process itself was started on:
  Sat Jul 18 21:41:24 2020

  I was playing the video only for about ~5 minutes when the program
  started, then let the program sit idle for a few days. Today I found
  that it consumed 2GB RSS as shown above!

  I am reporting this issue to see if something in my system is messing
  up VLC memory usage. In an older laptop, trying to play the same file
  (with VLC version 2.0.3) has its memory consumption starting at just
  under 190M.

  
  Wirawan

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: vlc 3.0.9.2-1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Jul 22 13:19:21 2020
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1898569] Re: laptop screen blank after reboot

[Daniel van Vugt]

Since this is an old release I suggest the fastest way forward here will
be for you to install Ubuntu 20.04.1 instead. It's better supported and
has more fixes than 18.04.

  https://ubuntu.com/download/desktop


** Tags added: dual-gpu hybrid nvidia

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

** Summary changed:

- laptop screen blank after reboot
+ [modeset + nvidia] Laptop screen blank after reboot

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

** Summary changed:

- [modeset + nvidia] Laptop screen blank after reboot
+ [modeset + nvidia + lightdm] Laptop screen blank after reboot

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

Title:
  [modeset + nvidia + lightdm] Laptop screen blank after reboot

Status in lightdm package in Ubuntu:
  New
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  connected to external monitor. After a reboot the laptop screen is
  blank. Can't find a consistent way to get it back.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.66  Wed Aug 12 19:42:48 
UTC 2020
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Oct  5 15:50:47 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.66, 5.4.0-47-generic, x86_64: installed
   nvidia, 450.66, 5.4.0-48-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:11c9]
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 
1050 Mobile] [1462:11c9]
  InstallationDate: Installed on 2020-06-03 (123 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Micro-Star International Co., Ltd. GP72 7RD
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro nouveau.modeset=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1799IMS.324
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1799
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1799IMS.324:bd03/23/2018:svnMicro-StarInternationalCo.,Ltd.:pnGP727RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1799:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GP
  dmi.product.name: GP72 7RD
  dmi.product.sku: 1799.3
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Oct  5 15:30:42 2020

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

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

[Touch-packages] [Bug 1898646] Re: Ubuntu 20.04 without sound with Via 1705 chipset

[Daniel van Vugt]

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

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 1793640, 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 1793640
   Pulseaudio fails to detect sound card, while timidity is installed

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

Title:
  Ubuntu 20.04 without sound with Via 1705 chipset

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  working very well with ubuntu 18.04 during two years with the chipset Via 
1705,upgrade to ubuntu 20.04 sound do not work. Without sound, only appear 
ficticius in configuration without any device detected.
  We do all the steps indicated in the link 
https://help.ubuntu.com/community/SoundTroubleshootingProcedure but don't 
resolved.
  We like of Ubuntu 20.04, please need a solution. Thanks.

  Estimados, trabajamos muy bien con el Ubuntu 18.04 durante dos añoscon el 
chip Via 1705 sin problemas, com un sonido refinado em caja de sonido 
Harman/Kardon, lamentablemente al actualizar para Ubuntu 20,04 el sonido no se 
escucha, intentamos todos los pasos indicados en el link 
https://help.ubuntu.com/community/SoundTroubleshootingProcedure, pero no 
resolvio.
  Nos agradó el nuevo Ubuntu 20.04, por favor una solución para no desistir de 
este. Gracias.

  Bom, para que fique bem claro, este é um equipamento com o que
  trabalho em varias regiões, por isso se houver algum colegas que
  entenda um destes idiomas, agradeceria uma solução, trabalhamos
  durante dois anos com um chipset Via 1705 num Ubuntu 18.04, ao
  atualizar para a nova versão Ubuntu 20.04 nos deparamos em que o som
  não funciona, a placa não é detectada pelo painel GUI das
  configurações do Gnome, e pelo terminal o pulseaudio não funciona.
  Favor indicar uma solução pois o resto do sistema está estável e
  funcionando, não queremos desistir da atualização. Obrigado

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  timidity935 F timidity
   /dev/snd/pcmC0D0p:   timidity935 F...m timidity
   /dev/snd/seq:timidity935 F timidity
   /dev/snd/timer:  timidity935 f timidity
  CasperMD5CheckResult: skip
  Date: Mon Oct  5 22:31:16 2020
  InstallationDate: Installed on 2018-10-27 (709 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to focal on 2020-10-03 (2 days ago)
  dmi.bios.date: 06/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81H3-M4
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/30/2014:svnECS:pnH81H3-M4:pvr1.0:rvnECS:rnH81H3-M4:rvr1.0:cvnECS:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H81H3-M4
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS

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

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

[Touch-packages] [Bug 1898563] Re: Xorg freeze

[Daniel van Vugt]

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.

** Tags added: radeon

** Summary changed:

- Xorg freeze
+ [radeon] Screen freeze

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

** Changed in: 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/1898563

Title:
  [radeon] Screen freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Every day I have the same problem - my pc (system updated to Ubuntu 20.04) 
screen (internet browser Brave) when I work in internet pages simply frozen, 
mouse and keyboard stopped working , I tried command (Crl+Alt+Del) but it did 
not help, and I have manually to reboot the pc (pressing the button). 
  By the way - it happened only after I upgraded to Ubuntu 20.04 - when I was 
on Ubuntu 18 I've never seen such problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  5 17:01:42 2020
  DistUpgraded: 2020-10-01 17:22:40,616 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
 Subsystem: Dell Caicos XTX [Radeon HD 8490 / R5 235X OEM] [1028:2120]
  InstallationDate: Installed on 2020-04-27 (161 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=d70267c9-bd6d-4ed6-a98a-085d6f7fb757 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-10-01 (3 days ago)
  dmi.bios.date: 07/31/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: A320M-HDV R4.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  xserver.bootTime: Sat Jun  6 18:08:10 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: radeon

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

-- 

[Touch-packages] [Bug 1898646] [NEW] Ubuntu 20.04 without sound with Via 1705 chipset

[Marcelo Smacom]

Public bug reported:

working very well with ubuntu 18.04 during two years with the chipset Via 
1705,upgrade to ubuntu 20.04 sound do not work. Without sound, only appear 
ficticius in configuration without any device detected.
We do all the steps indicated in the link 
https://help.ubuntu.com/community/SoundTroubleshootingProcedure but don't 
resolved.
We like of Ubuntu 20.04, please need a solution. Thanks.

Estimados, trabajamos muy bien con el Ubuntu 18.04 durante dos añoscon el chip 
Via 1705 sin problemas, com un sonido refinado em caja de sonido Harman/Kardon, 
lamentablemente al actualizar para Ubuntu 20,04 el sonido no se escucha, 
intentamos todos los pasos indicados en el link 
https://help.ubuntu.com/community/SoundTroubleshootingProcedure, pero no 
resolvio.
Nos agradó el nuevo Ubuntu 20.04, por favor una solución para no desistir de 
este. Gracias.

Bom, para que fique bem claro, este é um equipamento com o que trabalho
em varias regiões, por isso se houver algum colegas que entenda um
destes idiomas, agradeceria uma solução, trabalhamos durante dois anos
com um chipset Via 1705 num Ubuntu 18.04, ao atualizar para a nova
versão Ubuntu 20.04 nos deparamos em que o som não funciona, a placa não
é detectada pelo painel GUI das configurações do Gnome, e pelo terminal
o pulseaudio não funciona. Favor indicar uma solução pois o resto do
sistema está estável e funcionando, não queremos desistir da
atualização. Obrigado

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.7
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  timidity935 F timidity
 /dev/snd/pcmC0D0p:   timidity935 F...m timidity
 /dev/snd/seq:timidity935 F timidity
 /dev/snd/timer:  timidity935 f timidity
CasperMD5CheckResult: skip
Date: Mon Oct  5 22:31:16 2020
InstallationDate: Installed on 2018-10-27 (709 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to focal on 2020-10-03 (2 days ago)
dmi.bios.date: 06/30/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81H3-M4
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/30/2014:svnECS:pnH81H3-M4:pvr1.0:rvnECS:rnH81H3-M4:rvr1.0:cvnECS:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: H81H3-M4
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: ECS

** Affects: pulseaudio (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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1898646

Title:
  Ubuntu 20.04 without sound with Via 1705 chipset

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  working very well with ubuntu 18.04 during two years with the chipset Via 
1705,upgrade to ubuntu 20.04 sound do not work. Without sound, only appear 
ficticius in configuration without any device detected.
  We do all the steps indicated in the link 
https://help.ubuntu.com/community/SoundTroubleshootingProcedure but don't 
resolved.
  We like of Ubuntu 20.04, please need a solution. Thanks.

  Estimados, trabajamos muy bien con el Ubuntu 18.04 durante dos añoscon el 
chip Via 1705 sin problemas, com un sonido refinado em caja de sonido 
Harman/Kardon, lamentablemente al actualizar para Ubuntu 20,04 el sonido no se 
escucha, intentamos todos los pasos indicados en el link 
https://help.ubuntu.com/community/SoundTroubleshootingProcedure, pero no 
resolvio.
  Nos agradó el nuevo Ubuntu 20.04, por favor una solución para no desistir de 
este. Gracias.

  Bom, para que fique bem claro, este é um equipamento com o que
  trabalho em varias regiões, por isso se houver algum colegas que
  entenda um destes idiomas, agradeceria uma solução, trabalhamos
  durante dois anos com um chipset Via 1705 num Ubuntu 18.04, ao
  atualizar para a nova versão Ubuntu 20.04 nos deparamos em que o som
  não funciona, a placa não é detectada pelo painel GUI das
  configurações do Gnome, e pelo terminal o pulseaudio não funciona.
  Favor indicar uma solução pois o resto do sistema está estável e
  funcionando, não queremos desistir da 

[Touch-packages] [Bug 1898059] Re: [POSITIVO BGH] Repeated sound constantly, and some cracky noise sometimes

[Daniel van Vugt]

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

** Summary changed:

- [POSITIVO BGH] Repeated sound constantly, and some cracky noise sometimes
+ [POSITIVO BGH] Repeated sound constantly, and some cracky noise sometimes (in 
kernel 5.4.0-48.52, but 5.8.13 works)

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

Title:
  [POSITIVO BGH] Repeated sound constantly, and some cracky noise
  sometimes (in kernel 5.4.0-48.52, but 5.8.13 works)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I watch youtube videos or hear music in for example spotify or
  anywhere, usually the sounds of what I am playing is heared twice like
  some kind of echo.

  Also, sometimes there is a cracky sound while hearing. I don't know
  what may cause this and that's why I'm reporting this bug. (Before I
  had Linux Mint and that didn't happen, but I prefer Ubuntu so if
  possible I would like a solution, thank you).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bata340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  1 11:19:48 2020
  InstallationDate: Installed on 2020-08-12 (49 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio Interno - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   oct 01 09:19:13 BataBGH dbus-daemon[788]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.28' (uid=1000 pid= comm="/usr/bin/pulseaudio 
--daemonize=no --log-target=jo" label="unconfined")
   oct 01 09:19:15 BataBGH dbus-daemon[788]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.34' 
(uid=1000 pid= comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" 
label="unconfined")
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_SpeakerTestPulseStderr: W r i t e   e r r o r :   - 3 2 , B r o k e n 
  p i p e
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [POSITIVO BGH, Realtek ALC269VB, Speaker, Internal] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2011
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 1.04.00.IF.Test01
  dmi.board.name: POSITIVO BGH
  dmi.board.vendor: POSITIVO BGH
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: POSITIVO BGH
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.04.00.IF.Test01:bd08/18/2011:svnPOSITIVOBGH:pnPOSITIVOBGH:pvrNotApplicable:rvnPOSITIVOBGH:rnPOSITIVOBGH:rvrNotApplicable:cvnPOSITIVOBGH:ct9:cvrN/A:
  dmi.product.name: POSITIVO BGH
  dmi.product.sku: 1234567890
  dmi.product.version: Not Applicable
  dmi.sys.vendor: POSITIVO BGH

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

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

[Touch-packages] [Bug 1898447] Re: HDMI sound output disappears after sleep

[Daniel van Vugt]

** This bug is no longer a duplicate of bug 1888598
   pulseaudio has is buggy with hdmi audio and sleep/wake

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

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER

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

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

[Touch-packages] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

[Mauricio Faria de Oliveira]

Hey Alex, thank you very much for your prompt review.

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

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  In Progress
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  In Progress
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends its execution, we execute
  at least once more time cryptsetup. In an ideal world we should loop
  on local-block as Debian's initramfs (in a way to remove hardcoded
  mdadm/cryptsetup mentions from initramfs-tools code), but this would
  be really a big change, non-SRUable probably. I plan to work that for
  future Ubuntu releases.

  [Test case]
  * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to 
create a RAID1 volume and an encrypted root on top of it.

  * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table
  from one of the RAID members. Reboot and it will fail to mount rootfs
  and continue boot process.

  * If using the initramfs-toos/cryptsetup patches hereby proposed, the
  rootfs can be mounted normally.

  [Regression potential]

  * There are potential for regressions, since this is a change in 2
  boot components. The patches were designed in a way to keep the
  regular case working, it changes the failure case which is not
  currently working anyway.

  * A modification in the behavior of cryptsetup was introduced: right
  now, if we fail the password 3 times (the default maximum attempts),
  the script doesn't "panic" and drop to a shell immediately; instead it
  runs once more (or twice, if mdadm is installed) before failing. This
  is a minor change given the benefit of the being able to mount rootfs
  in a degraded RAID1 scenario.

  * Other potential regressions could show-up as boot problems, but the
  change in initramfs-tools specifically is not invasive, it just may
  delay boot time a bit, given we now run cryptsetup multiple times on
  local-block, with 1 sec delays between executions.

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

[Tim Wetzel]

Sorry to say that I tried to install from images from both May and June
of this year, obviously 20.04. Both failed with the same crash. And,
like you, I need nvidia and other specific drivers.

Even if you can get past the crash, other changes that have been made since 
mid-September are wreaking havoc also: 
-there are problems with the new compression algorithm for initramfs
-there are issues with startup hanging with a spinning Ubuntu logo, forcing 
hard power down
-there are issues with startup going into suspend as soon as the login password 
is entered

I too hope that this gets solved soon.

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

Re: [Touch-packages] [Bug 1898059] Re: [POSITIVO BGH] Repeated sound constantly, and some cracky noise sometimes

[Bata340]

Seems as if it solved the problem. Thank you!

On Thu, Oct 1, 2020 at 11:10 PM Daniel van Vugt <1898...@bugs.launchpad.net>
wrote:

> This might be a problem in the kernel driver. Please test a newer kernel
> by downloading all of these:
>
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.13/amd64/linux-
> headers-5.8.13-050813-generic_5.8.13-050813.202010011235_amd64.deb
> 
>
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.13/amd64/linux-
> headers-5.8.13-050813_5.8.13-050813.202010011235_all.deb
> 
>
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.13/amd64/linux-
> image-
> unsigned-5.8.13-050813-generic_5.8.13-050813.202010011235_amd64.deb
>
> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.13/amd64/linux-
> modules-5.8.13-050813-generic_5.8.13-050813.202010011235_amd64.deb
> 
>
> and then install them all together with:
>
>   sudo dpkg -i *.deb
>
> and reboot.
>
>
> ** Summary changed:
>
> - Repeated sound constantly, and some cracky noise sometimes
> + [POSITIVO BGH] Repeated sound constantly, and some cracky noise sometimes
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1898059
>
> Title:
>   [POSITIVO BGH] Repeated sound constantly, and some cracky noise
>   sometimes
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   When I watch youtube videos or hear music in for example spotify or
>   anywhere, usually the sounds of what I am playing is heared twice like
>   some kind of echo.
>
>   Also, sometimes there is a cracky sound while hearing. I don't know
>   what may cause this and that's why I'm reporting this bug. (Before I
>   had Linux Mint and that didn't happen, but I prefer Ubuntu so if
>   possible I would like a solution, thank you).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: pulseaudio 1:13.99.1-1ubuntu3.5
>   ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
>   Uname: Linux 5.4.0-48-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.8
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  bata340 F pulseaudio
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Oct  1 11:19:48 2020
>   InstallationDate: Installed on 2020-08-12 (49 days ago)
>   InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
> (20200731)
>   SourcePackage: pulseaudio
>   Symptom: audio
>   Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH
> successful
>   Symptom_Card: Audio Interno - HDA Intel PCH
>   Symptom_Jack: Speaker, Internal
>   Symptom_PulseAudioLog:
>oct 01 09:19:13 BataBGH dbus-daemon[788]: [system] Activating via
> systemd: service name='org.freedesktop.RealtimeKit1'
> unit='rtkit-daemon.service' requested by ':1.28' (uid=1000 pid=
> comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo"
> label="unconfined")
>oct 01 09:19:15 BataBGH dbus-daemon[788]: [system] Activating via
> systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested
> by ':1.34' (uid=1000 pid= comm="/usr/bin/pulseaudio --daemonize=no
> --log-target=jo" label="unconfined")
>   Symptom_PulsePlaybackTest: PulseAudio playback test failed
>   Symptom_SpeakerTestPulseStderr: W r i t e   e r r o r :   - 3 2 , B r o
> k e n   p i p e
>   Symptom_Type: Underruns, dropouts, or "crackling" sound
>   Title: [POSITIVO BGH, Realtek ALC269VB, Speaker, Internal] Underruns,
> dropouts or crackling sound
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/18/2011
>   dmi.bios.vendor: Phoenix Technologies LTD
>   dmi.bios.version: 1.04.00.IF.Test01
>   dmi.board.name: POSITIVO BGH
>   dmi.board.vendor: POSITIVO BGH
>   dmi.board.version: Not Applicable
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: POSITIVO BGH
>   dmi.chassis.version: N/A
>   dmi.modalias:
> dmi:bvnPhoenixTechnologiesLTD:bvr1.04.00.IF.Test01:bd08/18/2011:svnPOSITIVOBGH:pnPOSITIVOBGH:pvrNotApplicable:rvnPOSITIVOBGH:rnPOSITIVOBGH:rvrNotApplicable:cvnPOSITIVOBGH:ct9:cvrN/A:
>   dmi.product.name: POSITIVO BGH
>   dmi.product.sku: 1234567890
>   dmi.product.version: Not Applicable
>   dmi.sys.vendor: POSITIVO BGH
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898059/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded 

[Touch-packages] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

[Alex Murray]

I can't see any potential security impact from this - yes it will now do
another round of asking for passwords but 9 tries doesn't really help
(from an attacker point-of-view) any more than 6 tries assuming this is
a long passphrase - so consider this an ACK from the security team.

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

Title:
  Fail to boot with LUKS on top of RAID1 if the array is broken/degraded

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in mdadm package in Ubuntu:
  Opinion
Status in cryptsetup source package in Xenial:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in mdadm source package in Xenial:
  Won't Fix
Status in cryptsetup source package in Bionic:
  In Progress
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in mdadm source package in Bionic:
  Opinion
Status in cryptsetup source package in Focal:
  In Progress
Status in initramfs-tools source package in Focal:
  Fix Released
Status in mdadm source package in Focal:
  Opinion
Status in cryptsetup source package in Groovy:
  Fix Released
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in mdadm source package in Groovy:
  Opinion
Status in cryptsetup package in Debian:
  New

Bug description:
  [Impact]
  * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu 
is currently unable to decrypt the rootfs if the array gets degraded, like for 
example if one of the array's members gets removed.

  * The problem has 2 main aspects: first, cryptsetup initramfs script
  attempts to decrypt the array only in the local-top boot stage, and in
  case it fails, it gives-up and show user a shell (boot is aborted).

  * Second, mdadm initramfs script that assembles degraded arrays
  executes later on boot, in the local-block stage. So, in a stacked
  setup of encrypted root on top of RAID, if the RAID is degraded,
  cryptsetup fails early in the boot, preventing mdadm to assemble the
  degraded array.

  * The hereby proposed solution has 2 components: first, cryptsetup
  script is modified to allow a gentle failure on local-top stage, then
  it retries for a while (according to a heuristic based on ROOTDELAY
  with minimum of 30 executions) in a later stage (local-block). This
  gives time to other initramfs scripts to run, like mdadm in local-
  block stage. And this is meant to work this way according to
  initramfs-tools documentation (although Ubuntu changed it a bit with
  wait-for-root, hence we stopped looping on local-block, see next
  bullet).

  * Second, initramfs-tools was adjusted - currently, it runs for a
  while the mdadm local-block script, in order to assemble the arrays in
  a non-degraded mode. We extended this approach to also execute
  cryptsetup, in a way that after mdadm ends its execution, we execute
  at least once more time cryptsetup. In an ideal world we should loop
  on local-block as Debian's initramfs (in a way to remove hardcoded
  mdadm/cryptsetup mentions from initramfs-tools code), but this would
  be really a big change, non-SRUable probably. I plan to work that for
  future Ubuntu releases.

  [Test case]
  * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to 
create a RAID1 volume and an encrypted root on top of it.

  * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table
  from one of the RAID members. Reboot and it will fail to mount rootfs
  and continue boot process.

  * If using the initramfs-toos/cryptsetup patches hereby proposed, the
  rootfs can be mounted normally.

  [Regression potential]

  * There are potential for regressions, since this is a change in 2
  boot components. The patches were designed in a way to keep the
  regular case working, it changes the failure case which is not
  currently working anyway.

  * A modification in the behavior of cryptsetup was introduced: right
  now, if we fail the password 3 times (the default maximum attempts),
  the script doesn't "panic" and drop to a shell immediately; instead it
  runs once more (or twice, if mdadm is installed) before failing. This
  is a minor change given the benefit of the being able to mount rootfs
  in a degraded RAID1 scenario.

  * Other potential regressions could show-up as boot problems, but the
  change in initramfs-tools specifically is not invasive, it just may
  delay boot time a bit, given we now run cryptsetup multiple times on
  local-block, with 1 sec delays between executions.

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

[Winston Fan]

Hit the same issue on 6th Oct 2020.

I downloaded the latest ISO from Ubuntu official website and created my
bootable USB to install the latest 20.04 version.

The crash happened towards the end of installation, 80% in progress.

My PC specs:
AMD Ryzen X3700
NVIDIA RTX 2080Ti, Gigabyte
Kingston A2000 1TG M.2 NVME SSD
RAM 64GB

The File system I chose during partitioning is:
Btrfs
Mount Point: /

Hopefully this issue will be solved soon.

For now, what should I do?
reinstall the Ubuntu 20.04?

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1898641] Re: ls does not show directory

[xaviering]

Sorry, i should have think twice before submitting these. It's not a
bug, but a normal behaviour.

** Information type changed from Public to Private

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

Title:
  ls does not show directory

Status in coreutils package in Ubuntu:
  Invalid

Bug description:
  Hello,

  ls does not report directory. and echo does not expand to file. See
  picture in attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: coreutils 8.28-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  6 00:54:59 2020
  InstallationDate: Installed on 2020-04-09 (179 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1898641] Re: ls does not show directory

[Daniel Letzeisen]

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

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

Title:
  ls does not show directory

Status in coreutils package in Ubuntu:
  Invalid

Bug description:
  Hello,

  ls does not report directory. and echo does not expand to file. See
  picture in attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: coreutils 8.28-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  6 00:54:59 2020
  InstallationDate: Installed on 2020-04-09 (179 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1898641] Re: ls does not show directory

[xaviering]

Sorry, I should have think twice before sending the bug. It's not a bug
and a normal behaviour. Please, does not take it into consideration.

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

Title:
  ls does not show directory

Status in coreutils package in Ubuntu:
  Invalid

Bug description:
  Hello,

  ls does not report directory. and echo does not expand to file. See
  picture in attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: coreutils 8.28-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  6 00:54:59 2020
  InstallationDate: Installed on 2020-04-09 (179 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1898641] [NEW] ls does not show directory

[xaviering]

Public bug reported:

Hello,

ls does not report directory. and echo does not expand to file. See
picture in attachment.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: coreutils 8.28-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  6 00:54:59 2020
InstallationDate: Installed on 2020-04-09 (179 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: coreutils (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-bug bionic

** Attachment added: "shell session screenshot"
   
https://bugs.launchpad.net/bugs/1898641/+attachment/5418104/+files/Screenshot%202020-10-06%20at%2000.14.20.png

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

Title:
  ls does not show directory

Status in coreutils package in Ubuntu:
  Invalid

Bug description:
  Hello,

  ls does not report directory. and echo does not expand to file. See
  picture in attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: coreutils 8.28-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  6 00:54:59 2020
  InstallationDate: Installed on 2020-04-09 (179 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1898447] Re: HDMI sound output disappears after sleep

[Umayr Saghir]

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

I took a look at those bugs and I'm not sure they are exact duplicates,
it's not clear if https://bugs.launchpad.net/bugs/1888598 is describing
a disappearance of the option to select the HDMI audio output, which is
what I'm seeing.

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

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER

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

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

[Touch-packages] [Bug 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers

[Daniel Letzeisen]

The problem is at a deeper level than pulseaudio. Removing it is generally a 
bad idea. If you need to reset the users settings:
rm -r ~/.config/pulse*

[  176.438897] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x202f0600
[  176.439057] snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last 
cmd=0x1270700

The best fix I have found for ^this is to go into the BIOS and disable
the audio. Save and reboot. Then go back into the BIOS and enable the
audio. Save and 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/1898603

Title:
  Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected
  as output, not speakers

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound
  output is detected as "headphones" instead of Speakers when this
  laptop doesn't even have any headphones connected at all... reverting
  to a prior kernel fixes the problem and then the output is correctly
  Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and
  the Mint Linux support chat said I should file a bug for this because
  this kernel broke something.

  See attached detailed log reports for more info...

  Thanks team!!!

  Best Regards,

  -Avery Tarasov
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chr0meice2   2656 F pulseaudio
   /dev/snd/controlC0:  chr0meice2   2656 F pulseaudio
   /dev/snd/pcmC0D0c:   chr0meice2   2656 F...m pulseaudio
   /dev/snd/pcmC0D0p:   chr0meice2   2656 F...m pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-10-05 (0 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  ulyana
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/01/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_96_97Ex,Rx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P95_96_97Ex,Rx
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers

[Avery Tarasov]

I uninstalled pulseaudio completely and even with just alsa alone
couldn't get audio to play, just a heads up.  Maybe did something wrong
but gave it a shot

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

Title:
  Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected
  as output, not speakers

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound
  output is detected as "headphones" instead of Speakers when this
  laptop doesn't even have any headphones connected at all... reverting
  to a prior kernel fixes the problem and then the output is correctly
  Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and
  the Mint Linux support chat said I should file a bug for this because
  this kernel broke something.

  See attached detailed log reports for more info...

  Thanks team!!!

  Best Regards,

  -Avery Tarasov
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chr0meice2   2656 F pulseaudio
   /dev/snd/controlC0:  chr0meice2   2656 F pulseaudio
   /dev/snd/pcmC0D0c:   chr0meice2   2656 F...m pulseaudio
   /dev/snd/pcmC0D0p:   chr0meice2   2656 F...m pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-10-05 (0 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  ulyana
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/01/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_96_97Ex,Rx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P95_96_97Ex,Rx
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers

[Avery Tarasov]

Hey Daniel, thanks for the heroic quick reply.  I did not have apport
installed by default but I installed it via apt-get and ran the command
and successfully gave authorization for one week

Someone in mint linux IRC thinks could be Pulse Audio issue because that
app shows Speakers (unavailable) in the GUI app.  I literally just
updated my pulse audio to the latest version and rebooted and the sound
still doesn't work from Speakers.

Please let me know if need any other data or to run command.

Best Regards,

-Avery

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

Title:
  Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected
  as output, not speakers

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound
  output is detected as "headphones" instead of Speakers when this
  laptop doesn't even have any headphones connected at all... reverting
  to a prior kernel fixes the problem and then the output is correctly
  Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and
  the Mint Linux support chat said I should file a bug for this because
  this kernel broke something.

  See attached detailed log reports for more info...

  Thanks team!!!

  Best Regards,

  -Avery Tarasov
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chr0meice2   2656 F pulseaudio
   /dev/snd/controlC0:  chr0meice2   2656 F pulseaudio
   /dev/snd/pcmC0D0c:   chr0meice2   2656 F...m pulseaudio
   /dev/snd/pcmC0D0p:   chr0meice2   2656 F...m pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-10-05 (0 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  ulyana
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/01/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_96_97Ex,Rx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P95_96_97Ex,Rx
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1732962] Re: apport uses sys.argv instead of named arguments

[Matthieu Clemenceau]

Verification completed on both bionic and xenial using proposed pockets

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

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

Title:
  apport uses sys.argv instead of named arguments

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Won't Fix
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Cosmic:
  Won't Fix
Status in apport source package in Disco:
  Fix Released

Bug description:
  SRU Description

  [Impact]
  data/apport which processes core files expects a certain quantity of 
arguments in a specific order. This ended up causing an issue with some 
security updates where we were trying to support a new version of apport on a 
host system and one inside a container.
  This SRU for xenial and bionic based on the work made in cosmic enabled 
proper handling of named argument.
  Note that this is disabled for now on ALL series

  [Test Case]
  No real test here since apport general behavior should be unchanged Just to 
check that the feature is disable, /proc/sys/kernel/core_pattern
  content should remain unchanged :

  $> cat /proc/sys/kernel/core_pattern
  |/usr/share/apport/apport %p %s %c %d %P %E

  [Regression Potential]
  The new feature is not enabled so the regression risk is fairly low. this 
will take place in a future coordinated SRU across all LTS but in the meanwhile 
we can make sure that there's no regression by making sure apport still behave 
properly. starting and killing xeyes should trigger apport normal operation and 
start apport.
  $> xeyes &
  $> kill -SEGV $!

  End SRU Description

  data/apport which processes core files expects a certain quantity of
  arguments in a specific order. This ended up causing an issue with
  some security updates where we were trying to support a new version of
  apport on a host system and one inside a container.  Here's something
  of an example:

  347 # Normal startup
  348 if len(sys.argv) not in (5, 6):
  349 try:
  350 print('Usage: %s [global pid]' % sys.argv[0])
  351 print('The core dump is read from stdin.')

  We could not maintain backwards compatibility because "global pid" is
  an optional argument and "dump mode" was a new argument. So if there
  were five arguments its possible the last one was "dump mode" (no
  global pid) or "global pid" (no support for dump mode).

  Its possible to use strings in /proc/sys/kernel/core_pattern so we
  could use those and have apport accept named arguments e.g:

  $ cat /proc/sys/kernel/core_pattern
  |/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d 
--global-pid=%P

  ['/home/bdmurray/source-trees/apport/artful/data/apport', '--
  pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global-
  pid=5870']

  Tyler said "that's probably a nice cleanup to make no matter what
  because the magic arg ordering is dangerous".

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

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

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

[Avery Tarasov]

apport information

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

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

Title:
  Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected
  as output, not speakers

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound
  output is detected as "headphones" instead of Speakers when this
  laptop doesn't even have any headphones connected at all... reverting
  to a prior kernel fixes the problem and then the output is correctly
  Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and
  the Mint Linux support chat said I should file a bug for this because
  this kernel broke something.

  See attached detailed log reports for more info...

  Thanks team!!!

  Best Regards,

  -Avery Tarasov
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chr0meice2   2656 F pulseaudio
   /dev/snd/controlC0:  chr0meice2   2656 F pulseaudio
   /dev/snd/pcmC0D0c:   chr0meice2   2656 F...m pulseaudio
   /dev/snd/pcmC0D0p:   chr0meice2   2656 F...m pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-10-05 (0 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  ulyana
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/01/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_96_97Ex,Rx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P95_96_97Ex,Rx
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

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

[Avery Tarasov]

apport information

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

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

Title:
  Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected
  as output, not speakers

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound
  output is detected as "headphones" instead of Speakers when this
  laptop doesn't even have any headphones connected at all... reverting
  to a prior kernel fixes the problem and then the output is correctly
  Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and
  the Mint Linux support chat said I should file a bug for this because
  this kernel broke something.

  See attached detailed log reports for more info...

  Thanks team!!!

  Best Regards,

  -Avery Tarasov
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chr0meice2   2656 F pulseaudio
   /dev/snd/controlC0:  chr0meice2   2656 F pulseaudio
   /dev/snd/pcmC0D0c:   chr0meice2   2656 F...m pulseaudio
   /dev/snd/pcmC0D0p:   chr0meice2   2656 F...m pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-10-05 (0 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  ulyana
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/01/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_96_97Ex,Rx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P95_96_97Ex,Rx
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers

[Avery Tarasov]

apport information

** Tags added: apport-collected ulyana

** Description changed:

  Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound
  output is detected as "headphones" instead of Speakers when this laptop
  doesn't even have any headphones connected at all... reverting to a
  prior kernel fixes the problem and then the output is correctly
  Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and
  the Mint Linux support chat said I should file a bug for this because
  this kernel broke something.
  
  See attached detailed log reports for more info...
  
  Thanks team!!!
  
  Best Regards,
  
  -Avery Tarasov
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.9
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  chr0meice2   2656 F pulseaudio
+  /dev/snd/controlC0:  chr0meice2   2656 F pulseaudio
+  /dev/snd/pcmC0D0c:   chr0meice2   2656 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   chr0meice2   2656 F...m pulseaudio
+ CasperMD5CheckResult: skip
+ DistroRelease: Linux Mint 20
+ InstallationDate: Installed on 2020-10-05 (0 days ago)
+ InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: alsa-driver (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ Tags:  ulyana
+ Uname: Linux 5.4.0-48-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 10/01/2019
+ dmi.bios.vendor: INSYDE Corp.
+ dmi.bios.version: 1.07.13
+ dmi.board.asset.tag: Tag 12345
+ dmi.board.name: P95_96_97Ex,Rx
+ dmi.board.vendor: Notebook
+ dmi.board.version: Not Applicable
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Notebook
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
+ dmi.product.family: Not Applicable
+ dmi.product.name: P95_96_97Ex,Rx
+ dmi.product.sku: Not Applicable
+ dmi.product.version: Not Applicable
+ dmi.sys.vendor: Notebook

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

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

Title:
  Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected
  as output, not speakers

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound
  output is detected as "headphones" instead of Speakers when this
  laptop doesn't even have any headphones connected at all... reverting
  to a prior kernel fixes the problem and then the output is correctly
  Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and
  the Mint Linux support chat said I should file a bug for this because
  this kernel broke something.

  See attached detailed log reports for more info...

  Thanks team!!!

  Best Regards,

  -Avery Tarasov
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chr0meice2   2656 F pulseaudio
   /dev/snd/controlC0:  chr0meice2   2656 F pulseaudio
   /dev/snd/pcmC0D0c:   chr0meice2   2656 F...m pulseaudio
   /dev/snd/pcmC0D0p:   chr0meice2   2656 F...m pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Linux Mint 20
  InstallationDate: Installed on 2020-10-05 (0 days ago)
  InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: alsa-driver (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  ulyana
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/01/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_96_97Ex,Rx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 

[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

[bernd]

Is not installing third party drivers during OS installation and doing
an apt-get update/upgrade and installing third party drivers at this
point a suitable workaround? Would this work?

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

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers

[Daniel Letzeisen]

Please run the following command to gather the audio logs (I think Mint has 
apport):
apport-collect 1898603

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

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

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

Title:
  Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected
  as output, not speakers

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound
  output is detected as "headphones" instead of Speakers when this
  laptop doesn't even have any headphones connected at all... reverting
  to a prior kernel fixes the problem and then the output is correctly
  Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and
  the Mint Linux support chat said I should file a bug for this because
  this kernel broke something.

  See attached detailed log reports for more info...

  Thanks team!!!

  Best Regards,

  -Avery Tarasov

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

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

[Touch-packages] [Bug 1898603] [NEW] Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound
output is detected as "headphones" instead of Speakers when this laptop
doesn't even have any headphones connected at all... reverting to a
prior kernel fixes the problem and then the output is correctly
Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and
the Mint Linux support chat said I should file a bug for this because
this kernel broke something.

See attached detailed log reports for more info...

Thanks team!!!

Best Regards,

-Avery Tarasov

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

-- 
Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, 
not speakers
https://bugs.launchpad.net/bugs/1898603
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver 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 1892643] Re: [SRU] Update libgweather to 3.36.1

[Amr Ibrahim]

** Attachment added: "libgweather_3.36.0-1_3.36.1-1~ubuntu20.04.1.diff.gz"
   
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/1892643/+attachment/5417988/+files/libgweather_3.36.0-1_3.36.1-1~ubuntu20.04.1.diff.gz

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

Title:
  [SRU] Update libgweather to 3.36.1

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Focal:
  New
Status in libgweather package in Debian:
  Unknown

Bug description:
  [Impact]

  libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36.

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions.

  Sometimes the current weather is not available because the NOAA
  weather servers aren't working correctly. Version 3.36.1 fixes the
  unavailability of current temperature in some locations.

  
  [Test case]

  Make sure that gnome-weather is still working properly and the weather
  in gnome-shell is shown when gnome-weather is installed.

  
  [Regression potential]

  The regression potential is low since the changes in version 3.36.1
  are small.

  
  [Other]

  libgweather 3.36.1 has been successfully built as a no-change backport
  from Groovy to Focal in my PPA and runs fine:

  
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather_filter=published_filter=

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 19:05:21 2020
  InstallationDate: Installed on 2020-04-26 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1892643] Re: [SRU] Update libgweather to 3.36.1

[Amr Ibrahim]

Please either sponsor the attached diff or from my PPA mentioned above.

** Patch added: "libgweather_3.36.0-1_3.36.1-1~ubuntu20.04.1.diff"
   
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/1892643/+attachment/5417986/+files/libgweather_3.36.0-1_3.36.1-1~ubuntu20.04.1.diff

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

Title:
  [SRU] Update libgweather to 3.36.1

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Focal:
  New
Status in libgweather package in Debian:
  Unknown

Bug description:
  [Impact]

  libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36.

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions.

  Sometimes the current weather is not available because the NOAA
  weather servers aren't working correctly. Version 3.36.1 fixes the
  unavailability of current temperature in some locations.

  
  [Test case]

  Make sure that gnome-weather is still working properly and the weather
  in gnome-shell is shown when gnome-weather is installed.

  
  [Regression potential]

  The regression potential is low since the changes in version 3.36.1
  are small.

  
  [Other]

  libgweather 3.36.1 has been successfully built as a no-change backport
  from Groovy to Focal in my PPA and runs fine:

  
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather_filter=published_filter=

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 19:05:21 2020
  InstallationDate: Installed on 2020-04-26 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1880193] Re: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.

[Michael Andreev]

Thank you a lot for this investigation, I'll try to reproduce with these
parameters and with new version on this week.

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

Title:
  autofs: Assertion 'set_remove(iterator->links, link) == link' failed
  at src/shared/userdb.c:314, function userdb_on_query_reply().
  Aborting.

Status in autofs package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in autofs source package in Focal:
  Triaged
Status in systemd source package in Focal:
  Triaged

Bug description:
  autofs has a periodic error on mounting shares in Ubuntu 20.04 (it happens 
about 1 time out of 5):
  "Assertion 'set_remove(iterator->links, link) == link' failed at 
src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.
  Aborted (core dumped)"


  `autofs.service` restart (or `automount` app restart) fixes this
  issue. However if some of home dirs (like `Desktop` or `Documents`)
  are mounted by `autofs`, user can't login into Ubuntu Desktop
  Environment (PC freezes on login with black screen). Since this error
  can prevent user log in, it might be considered as critical bug.


  It happens both in `autofs` systemd service and by direct execution of
  `automount` app (`automount -f -d` command).


  May be it's an underlying error in `systemd` library (I found the
  line, mentioned in error, in its source codes).


  This issue has place in Ubuntu 20.04 (it works correctly in Ubuntu
  18.04):

  > lsb_release -rd
  Description: Ubuntu 20.04 LTS
  Release: 20.04


  Packages versions:

  > apt-cache policy autofs systemd
  autofs:
Installed: 5.1.6-2
Candidate: 5.1.6-2
Version table:
   *** 5.1.6-2 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  systemd:
Installed: 245.4-4ubuntu3
Candidate: 245.4-4ubuntu3
Version table:
   *** 245.4-4ubuntu3 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status


  Steps to reproduce:
  1. Ubuntu 20.04 clean install
  2. `apt install realmd sssd sssd-tools libnss-sss libpam-sss adcli 
samba-common-bin`
  3. `realm join DOMAIN.NAME`
  4. Enable makehomedir by command: `pam-auth-update`
  5. `apt install cifs-utils`
  6. `apt install autofs`
  7. Add next line inside [domain/DOMAIN.EXT] section into /etc/sssd/sssd.conf: 
`krb5_ccname_template = FILE:%d/krb5cc_%U`
  8. Reboot
  9. Login as domain user and try to open directory, mounted by `autofs` (in my 
configuration shares are provided by AD).
  10. `autofs.service` stops with the error above about 1 time out of 5 (not 
always).

  Found workaround:
  Add `Restart=always` into `[Service]` section in 
`/lib/systemd/system/autofs.service` file (in other words configure 
auto-restart on failures for autofs service).


  Attachments:
  1. Full log of `automount -f -d` command.

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

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

[Touch-packages] [Bug 1726856] Re: ufw does not start automatically at boot

[Jamie Strandboge]

@Muhammad - can you run:

$ sudo /usr/share/ufw/check-requirements

and paste the results?

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Invalid
Status in ufw package in Ubuntu:
  Invalid
Status in ufw source package in Xenial:
  Invalid
Status in ufw source package in Bionic:
  Invalid
Status in ufw source package in Cosmic:
  Invalid
Status in ufw source package in Disco:
  Invalid

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

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

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

[Touch-packages] [Bug 1898593] [NEW] Fix sphinx doc building

[Andreas Hasenack]

Public bug reported:

This basically the same bug as #1894907, but there I decided to disable
docs rebuilding, after checking that none of the patches were against
the docs source.

Furthermore, we should probably fix these lintian issues:

E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/developer.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/download.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/genindex.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/getsasl.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/index.html You may use the libjs-mathjax package. 
(https://cdn.mathjax.org/mathjax/latest/mathjax.js)
E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/operations.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/packager.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/search.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/setup.html You may use the libjs-mathjax package. 
(https://cdn.mathjax.org/mathjax/latest/mathjax.js)
E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/support.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
E: cyrus-sasl2 source: source-is-missing doc/html/_static/jquery.js line length 
is 32014 characters (>512)
E: cyrus-sasl2 source: source-is-missing doc/html/_static/js/modernizr.min.js   
E: cyrus-sasl2 source: source-is-missing doc/html/_static/underscore.js line 
length is 519 characters (>512)
E: cyrus-sasl2 source: source-is-missing 
docsrc/exts/themes/cyrus/static/js/modernizr.min.js
E: cyrus-sasl2 source: source-is-missing 
docsrc/exts/themes/sphinx_rtd_theme/static/js/modernizr.min.js

** Affects: cyrus-sasl2 (Ubuntu)
 Importance: Medium
 Status: Triaged

** Summary changed:

- Build docs with sphinx
+ Fix sphinx doc building

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: New => Triaged

** Changed in: cyrus-sasl2 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Fix sphinx doc building

Status in cyrus-sasl2 package in Ubuntu:
  Triaged

Bug description:
  This basically the same bug as #1894907, but there I decided to
  disable docs rebuilding, after checking that none of the patches were
  against the docs source.

  Furthermore, we should probably fix these lintian issues:

  E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/developer.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
  E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/download.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
  E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/genindex.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
  E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/getsasl.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
  E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/index.html You may use the libjs-mathjax package. 
(https://cdn.mathjax.org/mathjax/latest/mathjax.js)
  E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/operations.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
  E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/packager.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
  E: cyrus-sasl2-doc: privacy-breach-uses-embedded-file 
usr/share/doc/cyrus-sasl2-doc/search.html You may use the libjs-mathjax 
package. (https://cdn.mathjax.org/mathjax/latest/mathjax.js)
  E: 

[Touch-packages] [Bug 1894907] Re: FTBFS with sphinx 3.2

[Andreas Hasenack]

I filed https://bugs.launchpad.net/ubuntu/+source/cyrus-
sasl2/+bug/1898593 to properly fix the doc building with sphinx.

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

Title:
  FTBFS with sphinx 3.2

Status in Cyrus-sasl2:
  New
Status in cyrus-sasl2 package in Ubuntu:
  Triaged
Status in cyrus-sasl2 package in Debian:
  New

Bug description:
  cyrus-sasl2 ships with a sphinx extension to build its documentation,
  and this extension was based on a very old sphinx version. It no
  longer builds with sphinx 3.2.1 from groovy, failing in several
  places:

  a) "NoUri"
  Extension error:
  Could not import extension sphinxlocal.builders.manpage (exception: cannot 
import name 'NoUri' from 'sphinx.environment' 
(/usr/lib/python3/dist-packages/sphinx/environment/__init__.py))
  make[2]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2
  make[2]: Leaving directory 
'/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal'
  make[1]: *** [Makefile:686: all-recursive] Error 1
  make[1]: Leaving directory 
'/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal'
  make: *** [Makefile:556: all] Error 2

  Debian has a bug report already at https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=955095

  b) MACRO_DEF
  Extension error:
  Could not import extension sphinxlocal.builders.manpage (exception: cannot 
import name 'MACRO_DEF' from 'sphinx.writers.manpage' 
(/usr/lib/python3/dist-packages/sphinx/writers/manpage.py))
  make[4]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2
  make[4]: Leaving directory 
'/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal'
  make[3]: *** [Makefile:686: all-recursive] Error 1
  make[3]: Leaving directory 
'/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal'
  make[2]: *** [Makefile:556: all] Error 2
  make[2]: Leaving directory 
'/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal'
  dh_auto_build: error: cd build-heimdal && make -j4 
sasldir=/usr/lib/x86_64-linux-gnu/sasl2 returned exit code 2
  make[1]: *** [debian/rules:164: override_dh_auto_build] Error 25
  make[1]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2'
  make: *** [debian/rules:122: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/1894907/+subscriptions

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

[Touch-packages] [Bug 1898590] Re: Verify DNS fingerprints not working

[Andreas Tauscher]

ssh version is OpenSSH_8.2p1 Ubuntu-4ubuntu0.1, OpenSSL 1.1.1f  31 Mar
2020

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

Title:
  Verify DNS fingerprints not working

Status in openssh package in Ubuntu:
  New

Bug description:
  When setting in /etc/ssh/ssh_config VerifyHostKeyDNS to yes the fingerprints 
are fetched, but the result is always:
  debug1: found n insecure fingerprints in DNS
  With dig +dnssec -tsshfp hostname the result is ok: ad flg is set.

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

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

[Touch-packages] [Bug 1898590] [NEW] Verify DNS fingerprints not working

[Andreas Tauscher]

Public bug reported:

When setting in /etc/ssh/ssh_config VerifyHostKeyDNS to yes the fingerprints 
are fetched, but the result is always:
debug1: found n insecure fingerprints in DNS
With dig +dnssec -tsshfp hostname the result is ok: ad flg is set.

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

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

Title:
  Verify DNS fingerprints not working

Status in openssh package in Ubuntu:
  New

Bug description:
  When setting in /etc/ssh/ssh_config VerifyHostKeyDNS to yes the fingerprints 
are fetched, but the result is always:
  debug1: found n insecure fingerprints in DNS
  With dig +dnssec -tsshfp hostname the result is ok: ad flg is set.

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

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

[Touch-packages] [Bug 1898569] [NEW] laptop screen blank after reboot

[Allan Jones]

Public bug reported:

connected to external monitor. After a reboot the laptop screen is
blank. Can't find a consistent way to get it back.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.66  Wed Aug 12 19:42:48 
UTC 2020
 GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
CompositorRunning: None
Date: Mon Oct  5 15:50:47 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 450.66, 5.4.0-47-generic, x86_64: installed
 nvidia, 450.66, 5.4.0-48-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:11c9]
   Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 1050 
Mobile] [1462:11c9]
InstallationDate: Installed on 2020-06-03 (123 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: Micro-Star International Co., Ltd. GP72 7RD
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
 TERM=xterm-256color
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=/dev/mapper/ubuntu--vg-root ro nouveau.modeset=0
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1799IMS.324
dmi.board.asset.tag: Default string
dmi.board.name: MS-1799
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1799IMS.324:bd03/23/2018:svnMicro-StarInternationalCo.,Ltd.:pnGP727RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1799:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
dmi.product.family: GP
dmi.product.name: GP72 7RD
dmi.product.sku: 1799.3
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Oct  5 15:30:42 2020

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  laptop screen blank after reboot

Status in xorg package in Ubuntu:
  New

Bug description:
  connected to external monitor. After a reboot the laptop screen is
  blank. Can't find a consistent way to get it back.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.66  Wed Aug 12 19:42:48 
UTC 2020
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: 

[Touch-packages] [Bug 1886215] Re: Strange Apple keyboard behaviour (Spanish layout)

[Gunnar Hjalmarsson]

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

** This bug has been marked a duplicate of bug 214786
   Apple USB ISO keyboard has incorrectly swapped keys

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

Title:
  Strange Apple keyboard behaviour (Spanish layout)

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  I have an Apple Aluminium keyboard with Spanish/Castillian layout
  connected to my laptop:

  lsusb output:

  ...
  Bus 002 Device 006: ID 05ac:0221 Apple, Inc. Aluminum Keyboard (ISO)
  Bus 002 Device 004: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
  ...

  I'm running Focal:

  cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  I want to enable the regular Spanish keyboard layout for the laptop's
  internal keyboard and the Macintosh layout for the Apple Aluminum
  keyboard.

  When I press the key to the left of 'z' which should be '<' and I have
  the layout, I see the right key being highlighted but I get 'º' on the
  terminal

  Likewise, when I press the key to the left of '1', I see it correctly
  highlighted but I get a '<' instead of a 'º'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1886215/+subscriptions

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

[Touch-packages] [Bug 1886215] Re: Strange Apple keyboard behaviour (Spanish layout)

[Gunnar Hjalmarsson]

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

Check out this Ask Ubuntu question for a way to handle Apple devices:

https://askubuntu.com/q/843590

But please note, though, that such an entry in /etc/default/keyboard
would switch the keys for your built-in keyboard too.

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

Title:
  Strange Apple keyboard behaviour (Spanish layout)

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  I have an Apple Aluminium keyboard with Spanish/Castillian layout
  connected to my laptop:

  lsusb output:

  ...
  Bus 002 Device 006: ID 05ac:0221 Apple, Inc. Aluminum Keyboard (ISO)
  Bus 002 Device 004: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
  ...

  I'm running Focal:

  cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  I want to enable the regular Spanish keyboard layout for the laptop's
  internal keyboard and the Macintosh layout for the Apple Aluminum
  keyboard.

  When I press the key to the left of 'z' which should be '<' and I have
  the layout, I see the right key being highlighted but I get 'º' on the
  terminal

  Likewise, when I press the key to the left of '1', I see it correctly
  highlighted but I get a '<' instead of a 'º'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1886215/+subscriptions

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

[Touch-packages] [Bug 1886215] Re: Strange Apple keyboard behaviour (Spanish layout)

[Adolfo Jayme]

just guessing a package to associate this report with

** Package changed: ubuntu => xkeyboard-config (Ubuntu)

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

Title:
  Strange Apple keyboard behaviour (Spanish layout)

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  I have an Apple Aluminium keyboard with Spanish/Castillian layout
  connected to my laptop:

  lsusb output:

  ...
  Bus 002 Device 006: ID 05ac:0221 Apple, Inc. Aluminum Keyboard (ISO)
  Bus 002 Device 004: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
  ...

  I'm running Focal:

  cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

  I want to enable the regular Spanish keyboard layout for the laptop's
  internal keyboard and the Macintosh layout for the Apple Aluminum
  keyboard.

  When I press the key to the left of 'z' which should be '<' and I have
  the layout, I see the right key being highlighted but I get 'º' on the
  terminal

  Likewise, when I press the key to the left of '1', I see it correctly
  highlighted but I get a '<' instead of a 'º'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1886215/+subscriptions

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

[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug

[Alistair Cunningham]

This still happens after upgrading to Ubuntu 20.10:

grep: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
grep: /usr/share/apport/symptoms/installation.py: No such file or directory
grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory
qgrep: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
grep: /usr/share/apport/symptoms/installation.py: No such file or directory
grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

Note that that I have the following alias set for ls:

alias ls='ls -N --color=yes --time-style=long-iso'

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

Title:
  Tab completion warnings with ubuntu-bug

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

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

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

[Touch-packages] [Bug 1886215] [NEW] Strange Apple keyboard behaviour (Spanish layout)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have an Apple Aluminium keyboard with Spanish/Castillian layout
connected to my laptop:

lsusb output:

...
Bus 002 Device 006: ID 05ac:0221 Apple, Inc. Aluminum Keyboard (ISO)
Bus 002 Device 004: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
...

I'm running Focal:

cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"

I want to enable the regular Spanish keyboard layout for the laptop's
internal keyboard and the Macintosh layout for the Apple Aluminum
keyboard.

When I press the key to the left of 'z' which should be '<' and I have
the layout, I see the right key being highlighted but I get 'º' on the
terminal

Likewise, when I press the key to the left of '1', I see it correctly
highlighted but I get a '<' instead of a 'º'

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


** Tags: aluminum focal keyboard macintosh
-- 
Strange Apple keyboard behaviour (Spanish layout)
https://bugs.launchpad.net/bugs/1886215
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xkeyboard-config 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 1898563] [NEW] Xorg freeze

[Olena Chuchak]

Public bug reported:

Every day I have the same problem - my pc (system updated to Ubuntu 20.04) 
screen (internet browser Brave) when I work in internet pages simply frozen, 
mouse and keyboard stopped working , I tried command (Crl+Alt+Del) but it did 
not help, and I have manually to reboot the pc (pressing the button). 
By the way - it happened only after I upgraded to Ubuntu 20.04 - when I was on 
Ubuntu 18 I've never seen such problems.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  5 17:01:42 2020
DistUpgraded: 2020-10-01 17:22:40,616 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
   Subsystem: Dell Caicos XTX [Radeon HD 8490 / R5 235X OEM] [1028:2120]
InstallationDate: Installed on 2020-04-27 (161 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=d70267c9-bd6d-4ed6-a98a-085d6f7fb757 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-10-01 (3 days ago)
dmi.bios.date: 07/31/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.30
dmi.board.name: A320M-HDV R4.0
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Sat Jun  6 18:08:10 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
xserver.video_driver: radeon

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


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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Every day I have the same problem - my pc (system updated to Ubuntu 20.04) 
screen (internet browser Brave) when I work in internet pages simply frozen, 
mouse and keyboard stopped working , I tried command (Crl+Alt+Del) but it did 
not help, and I have manually to reboot the pc (pressing the button). 
  By the way - it happened only after I upgraded to Ubuntu 20.04 - when I was 
on Ubuntu 18 I've never seen such problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  5 17:01:42 2020
  DistUpgraded: 2020-10-01 17:22:40,616 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 

[Touch-packages] [Bug 1100326] Re: Location requested by websites should be able to use GPS/mobile positioning

[Launchpad Bug Tracker]

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  Location requested by websites should be able to use GPS/mobile
  positioning

Status in Chromium Browser:
  Fix Committed
Status in Mozilla Firefox:
  Unknown
Status in GeoClue:
  Won't Fix
Status in WebKit:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in geoclue-2.0 package in Ubuntu:
  Fix Released
Status in geoclue-providers package in Ubuntu:
  Invalid

Bug description:
  It would be nice if location requested by websites could use location
  found from GPS or GSM/CDMA positioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1100326/+subscriptions

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

[Touch-packages] [Bug 1100326] Re: Location requested by websites should be able to use GPS/mobile positioning

[Launchpad Bug Tracker]

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

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

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

Title:
  Location requested by websites should be able to use GPS/mobile
  positioning

Status in Chromium Browser:
  Fix Committed
Status in Mozilla Firefox:
  Unknown
Status in GeoClue:
  Won't Fix
Status in WebKit:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in geoclue-2.0 package in Ubuntu:
  Fix Released
Status in geoclue-providers package in Ubuntu:
  Invalid

Bug description:
  It would be nice if location requested by websites could use location
  found from GPS or GSM/CDMA positioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1100326/+subscriptions

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

[Touch-packages] [Bug 1723822] Re: uncaught TypeError triggers ValueError

[Sebastien Bacher]

** Changed in: nautilus (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  uncaught TypeError triggers ValueError

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  $ ubuntu-bug nautilus
  ERROR: hook /usr/share/apport/package-hooks/source_nautilus.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
  TypeError: add_info() takes 1 positional argument but 2 were given

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 203, in 
_run_hook
  symb['add_info'](report)
File "/usr/share/apport/package-hooks/source_nautilus.py", line 23, in 
add_info
  report["usr_lib_nautilus"] = package_versions(*sorted(plugin_packages))
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 785, in 
package_versions
  map(max, [map(len, t) for t in zip(*versions)])
  ValueError: not enough values to unpack (expected 2, got 0)
  This tool has been deprecated, use 'gio open' instead.
  See 'gio help open' for more info.

  $ Created new window in existing browser session.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashReports:
   640:121:119:20593327:2017-10-14 08:49:43.994080376 -0700:2017-10-14 
08:49:24.682136558 -0700:/var/crash/_usr_bin_gnome-shell.121.crash
   640:0:119:712257:2017-10-13 22:55:49.843941428 -0700:2017-10-13 
22:55:48.723911385 -0700:/var/crash/_usr_lib_udisks2_udisksd.0.crash
   640:1000:119:432238:2017-10-14 07:48:01.498643348 -0700:2017-10-14 
07:48:00.714643372 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.crash
   664:1000:119:0:2017-10-13 19:55:40.447393054 -0700:2017-10-13 
19:55:40.447393054 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.upload
   600:112:119:0:2017-10-13 19:55:42.247460153 -0700:2017-10-13 
19:55:42.247460153 -0700:/var/crash/_usr_lib_gvfs_gvfsd-mtp.1000.uploaded
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 17:52:08 2017
  InstallationDate: Installed on 2017-10-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1895710] Re: Die Paketliste oder die Statusdatei konnte nicht eingelesen oder geöffnet werden.

[Julian Andres Klode]

It's not clear to me how you ended up with wrong permissions on those
files, so I'm afraid without a way to reproduce this, there's not much
we can do here.

** Package changed: update-manager (Ubuntu) => apt (Ubuntu)

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

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

Title:
  Die Paketliste oder die Statusdatei konnte nicht eingelesen oder
  geöffnet werden.

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  The following message popped up:
  Bitte melden Sie einen Fehler im Paket »update-manager« und fügen Sie die 
folgende Fehlermeldung an den Fehlerbericht an:
  E:can not open 
/var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_focal-updates_InRelease - 
fopen (13: Keine Berechtigung), E:Die Paketliste oder die Statusdatei konnte 
nicht eingelesen oder geöffnet werden.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: update-manager 1:20.04.10.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Aptdaemon:
   
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 15 19:00:28 2020
  InstallationDate: Installed on 2020-08-01 (45 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1895710] [NEW] Die Paketliste oder die Statusdatei konnte nicht eingelesen oder geöffnet werden.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The following message popped up:
Bitte melden Sie einen Fehler im Paket »update-manager« und fügen Sie die 
folgende Fehlermeldung an den Fehlerbericht an:
E:can not open 
/var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_focal-updates_InRelease - 
fopen (13: Keine Berechtigung), E:Die Paketliste oder die Statusdatei konnte 
nicht eingelesen oder geöffnet werden.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: update-manager 1:20.04.10.1
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Aptdaemon:
 
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 15 19:00:28 2020
InstallationDate: Installed on 2020-08-01 (45 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal
-- 
Die Paketliste oder die Statusdatei konnte nicht eingelesen oder geöffnet 
werden.
https://bugs.launchpad.net/bugs/1895710
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 1895134] Re: [Ffe] openexr

[Gianfranco Costamagna]

** Changed in: openexr (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [Ffe] openexr

Status in openexr package in Ubuntu:
  Fix Released

Bug description:
  Openexr in Ubuntu is dated 2018, and suffers from lots of bugs, fixed
  in the last two years by upstream.

  Also some security fixes have been added in the Ubuntu packaging, but
  they are now superseeded by

  the new upstream changes.

  The sync will bring the package again in a good shape, and I already
  prepared the transition in bileto, with no issues and no regressions
  in buildability.

  the changes between 2.3.0 and 2.5.3 are listed here
  
https://github.com/AcademySoftwareFoundation/openexr/blob/master/CHANGES.md#version-240-september-19-2019

  and the bileto/autopkgtests are here:
  https://bileto.ubuntu.com/#/ticket/4246

  (note: kio-extras has a missing b-d in proposed pocket, unrelated to
  this)

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

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

[Touch-packages] [Bug 1893170] Re: [Ubuntu 20.10] zlib: DFLTCC compression level switching issues

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  [Ubuntu 20.10] zlib: DFLTCC compression level switching issues

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  Fix Released
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * This SRU fixes a combination of multiple issues:

   * zlib DFLTCC compression level switching can corrupt data because
  hardware and software compression states become desynchronized. (LP
  1893170)

   * Since zlib is not working on all s390x system configurations
  support for switching between software and hardware compression is
  required especially for Java. (LP 1882494)

   * zlib on s390x may produce incomplete raw streams (but not
  gzip/zlib). (LP 1889059)

  [Test Case]

   * Since especially DFLTCC requires a s390x generation z15 or LinuxONE
  III the tests need to be done by IBM.

   * IBM has a set of tests available, that exercise public zlib APIs by
  calling them in different sequences with different buffer sizes and
  flush modes.

  * Partially these come from the IBM z/OS team, who developed their own
  zlib support for the hardware accelerator, and partially they are
  developed by the IBM Linux team based on issues encountered during
  development as well as fuzzing.

  * IBM also uses the zlib-ng test-suite as well as squash and stress-
  ng.

   * Compress data using zlib/DFLTCC with different compression level
  and verify state and if data got corrupted or not. (LP 1893170)

   * On a system with patched zlib package, switch between hardware and
  software compression and use zlib via the java.util.zip package
  (http://java.sun.com/developer/technicalArticles/Programming/compression/).
  (LP 1882494)

  * On a z15 system with hardware acceleration compression (DFLTCC)
  enabled, create a raw (negative windowBits value) stream with zlib.
  Then check if EOBS is missing or truncated. (LP 1889059)

  [Regression Potential]

   * There is a certain risk for regressions with the modifications that
  are introduced by the four LP bugs.

   * In case the package fails entirely, it will have (in worst case) an
  impact on all zlib, gzip and DFLTCC compression/decompression
  functions, that are very wide spread (gzip, tar cfz, everything with
  zlib) in Linux and would virtually make the system unusable.

   * If potential issues are limited to hardware assisted compression
  (which is more likely, since these patches are mostly about hw
  assisted compression), then issues would be limited to systems that
  provide this feature (latest s390x generation only).

  * A switch back to software got introduced (by setting DFLTCC=0
  environment variable) that will help to mitigate a potential negative
  impact of the hw assisted compression.

   * Only the latest s390x generation (z15 and LinuxONE III) supports
  hardware assisted DFLTCC and is potentially affected.

   * A patched test package was made available and got successfully
  tested by IBM. All four bugs were finally considered as solved with
  zlib (1:1.2.11.dfsg-2ubuntu2~ppa2) available here:
  
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=zlib

  __

  Description:   zlib: DFLTCC compression level switching issues
  Symptom:   Switching compression levels corrupts data
  Problem:   Hardware and software compression states become desynchronized.
  Solution:  Improve compression state synchronization. Since zlib project
     does not accept patches at the moment, the fix has been
     integrated into the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is 992a7afc3edfa511dff0650d1c545b11bf64e655.
  Reproduction:  Not possible with popular command line tools. The issues were
     discovered using example_call_fuzzer from:
     https://github.com/iii-i/zlib-ng/tree/fuzz/test/fuzz/

  This needs also be applied against 20.04 !

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

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

[Touch-packages] [Bug 1882494] Re: [UBUNTU 20.04] zlib not working on all s390x systems configurations

[Frank Heimes]

Updating the status of this ticket to Fix Released because it is now
fixed based on LP 1893170.

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

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  [UBUNTU 20.04] zlib not working on all s390x systems configurations

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Eoan:
  Won't Fix
Status in zlib source package in Focal:
  Fix Released
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  Pull request (https://github.com/madler/zlib/pull/410) and tagged
  https://github.com/iii-i/zlib/tree/dfltcc-20200511.

  The new code contains the following improvements:
  * Added support for switching between software and hardware compression.
  * Added --dfltcc configure flag (the old way of building it still works).

  Switching between software and hardware compression is not simply a
  nice-to-have feature, but is actually required by Java - that's why we
  are requesting an update.

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

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

[Touch-packages] [Bug 1889059] Re: [Ubuntu 20.04] zlib on s390x may produce incomplete raw (but not gzip/zlib) streams

[Frank Heimes]

Updating the status of this ticket to Fix Released because it is now
fixed based on LP 1893170.

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

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  [Ubuntu 20.04] zlib on s390x may produce incomplete raw (but not
  gzip/zlib) streams

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  Fix Released
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  zlib on s390x may produce incomplete raw (but not gzip/zlib) streams

  ---uname output---
  Linux t35lp56.lnxne.boe 5.8.0-20200703.rc3.git0.52a479d42203.300.fc31.s390x 
#1 SMP Fri Jul 3 00:46:20 CEST 2020 s390x s390x s390x GNU/Linux
   
  Machine Type = z15 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Create a raw (negative windowBits value) stream with zlib. EOBS might be 
missing or truncated.


  This affects all distro levels that contain hardware acceleration
  (DFLTCC) patch. I've attached the preliminary fix.

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

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

[Touch-packages] [Bug 1874925] Re: Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

[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/1874925

Title:
  Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone doesn't show up as an audio source.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  addyess   106482 F pulseaudio
   /dev/snd/controlC1:  addyess   106482 F pulseaudio
   /dev/snd/controlC0:  addyess   106482 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 24 16:56:54 2020
  InstallationDate: Installed on 2019-11-05 (171 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.13
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 8LK66UA#ABA
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1898522] [NEW] Comet Lake PCH-LP cAVS (Audio, Voice, Speech) | Ubuntu 20.04

[lavistam]

Public bug reported:

Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

I have the same problem as this thread. Unfortunately I don't have
dmic_detect in the config files.

Here it my information. The laptop is a Lenovo X1 Extreme Gen3

I have a new laptop and my mic isnt recoginzed by ubuntu (18.04 or
20.04)

$ uname -r
5.4.66-050466-generic

I've been playing with settings to try to get:

snd_hda_intel

to work, and then got lost trying to replace it with sof-firmware per:

https://askubuntu.com/questions/1203799/internal-microphone-not-
detected-lenovo-carbon-x1-7th-gen-ubuntu-19

and also

https://mathieularose.com/ubuntu-19-10-on-lenovo-thinkpad-x1-carbon-7th-
gen/

Currently commented blacklist like so:

```
# blacklist snd_hda_intel
# blacklist snd_soc_skl
```

Which allows my speakers, but not my mic

If I uncomment, I can't see either. I have a thinkpad dock, so some
"mic" is identified through the thunderbolt dock, when I unplug it, I
have no mic recognized

```
ls -l /lib/firmware/intel/sof-tplg/
total 1664
-rw-r--r-- 1 root   root   33227 Aug 19 15:17 sof-apl-da7219.tplg
-rw-r--r-- 1 root   root   23311 Aug 19 15:17 sof-apl-demux-pcm512x.tplg
-rw-r--r-- 1 root   root   10295 Aug 19 15:17 sof-apl-dmic-2ch.tplg
-rw-r--r-- 1 root   root   10431 Aug 19 15:17 sof-apl-dmic-4ch.tplg
-rw-r--r-- 1 root   root   10295 Aug 19 15:17 sof-apl-dmic-a2ch-b2ch.tplg
-rw-r--r-- 1 root   root   10363 Aug 19 15:17 sof-apl-dmic-a2ch-b4ch.tplg
-rw-r--r-- 1 root   root5223 Aug 19 15:17 sof-apl-dmic-a2ch.tplg
-rw-r--r-- 1 root   root   10363 Aug 19 15:17 sof-apl-dmic-a4ch-b2ch.tplg
-rw-r--r-- 1 root   root5223 Aug 19 15:17 sof-apl-dmic-b2ch.tplg
-rw-r--r-- 1 root   root6743 Aug 19 15:17 sof-apl-eq-dmic.tplg
-rw-r--r-- 1 root   root7223 Aug 19 15:17 sof-apl-eq-pcm512x.tplg
-rw-r--r-- 1 root   root9019 Aug 19 15:17 sof-apl-keyword-detect.tplg
-rw-r--r-- 1 root   root   38003 Aug 19 15:17 sof-apl-nocodec.tplg
-rw-r--r-- 1 root   root5127 Aug 19 15:17 sof-apl-pcm512x-nohdmi.tplg
-rw-r--r-- 1 root   root   25031 Aug 19 15:17 sof-apl-pcm512x.tplg
-rw-r--r-- 1 root   root   19815 Aug 19 15:17 sof-apl-rt298.tplg
-rw-r--r-- 1 root   root5791 Aug 19 15:17 sof-apl-src-50khz-pcm512x.tplg
-rw-r--r-- 1 root   root   11623 Aug 19 15:17 sof-apl-src-dmic.tplg
-rw-r--r-- 1 root   root5791 Aug 19 15:17 sof-apl-src-pcm512x.tplg
-rw-r--r-- 1 root   root   43619 Aug 19 15:17 sof-apl-tdf8532.tplg
-rw-r--r-- 1 root   root5127 Aug 19 15:17 sof-apl-wm8804.tplg
-rw-r--r-- 1 root   root   12579 Aug 19 15:17 sof-bdw-rt286.tplg
lrwxrwxrwx 1 root   root  18 Aug 19 15:17 sof-bdw-rt5640.tplg -> 
sof-bdw-rt286.tplg
-rw-r--r-- 1 root   root   13371 Aug 19 15:17 sof-byt-da7213.tplg
-rw-r--r-- 1 root   root   13107 Aug 19 15:17 sof-byt-nocodec.tplg
lrwxrwxrwx 1 root   root  19 Aug 19 15:17 sof-byt-rt5640.tplg -> 
sof-byt-da7213.tplg
lrwxrwxrwx 1 root   root  19 Aug 19 15:17 sof-byt-rt5645.tplg -> 
sof-byt-da7213.tplg
lrwxrwxrwx 1 root   root  19 Aug 19 15:17 sof-byt-rt5651.tplg -> 
sof-byt-da7213.tplg
lrwxrwxrwx 1 root   root  19 Aug 19 15:17 sof-byt-rt5682.tplg -> 
sof-byt-da7213.tplg
-rw-r--r-- 1 root   root   13371 Aug 19 15:17 sof-cht-max98090.tplg
lrwxrwxrwx 1 root   root  20 Aug 19 15:17 sof-cht-nocodec.tplg -> 
sof-byt-nocodec.tplg
-rw-r--r-- 1 root   root7927 Aug 19 15:17 sof-cht-rt5682.tplg
-rw-r--r-- 1 root   root Aug 19 15:17 sof-cht-src-50khz-pcm512x.tplg
-rw-r--r-- 1 root   root   34187 Aug 19 15:17 
sof-cml-demux-rt5682-max98357a.tplg
-rw-r--r-- 1 root   root   29283 Aug 19 15:17 sof-cml-demux-rt5682.tplg
-rw-r--r-- 1 root   root   39787 Aug 19 15:17 sof-cml-rt1011-rt5682.tplg
-rw-r--r-- 1 root   root   34883 Aug 19 15:17 sof-cml-rt5682-kwd.tplg
-rw-r--r-- 1 root   root   39787 Aug 19 15:17 sof-cml-rt5682-max98357a.tplg
-rw-r--r-- 1 root   root   31123 Aug 19 15:17 sof-cml-rt5682.tplg
-rw-r--r-- 1 root   root   32719 Aug 19 15:17 sof-cml-rt700.tplg
-rw-r--r-- 1 root   root   34411 Aug 19 15:17 
sof-cml-rt711-rt1308-mono-rt715.tplg
-rw-r--r-- 1 root   root   39295 Aug 19 15:17 sof-cml-rt711-rt1308-rt715.tplg
-rw-r--r-- 1 root   root   26751 Aug 19 15:17 sof-cml-src-rt5682.tplg
-rw-r--r-- 1 root   root   25715 Aug 19 15:17 sof-cnl-nocodec.tplg
-rw-r--r-- 1 root   root   11335 Aug 19 15:17 sof-cnl-rt274.tplg
-rw-r--r-- 1 root   root   43555 Aug 19 15:17 sof-glk-da7219-kwd.tplg
-rw-r--r-- 1 root   root   34831 Aug 19 15:17 sof-glk-da7219.tplg
-rw-r--r-- 1 root   root   33967 Aug 19 15:17 sof-glk-rt5682.tplg
-rw-r--r-- 1 root   root   48091 Aug 19 15:17 sof-hda-generic-1ch.tplg
-rw-r--r-- 1 root   root   45375 Aug 19 15:17 sof-hda-generic-2ch.tplg
-rw-r--r-- 1 root   root   48227 Aug 19 15:17 sof-hda-generic-3ch.tplg
-rw-r--r-- 1 root   root   45511 Aug 19 15:17 sof-hda-generic-4ch.tplg
-rw-r--r-- 1 root   root   28723 Aug 19 15:17 sof-hda-generic-idisp-2ch.tplg
-rw-r--r-- 1 root   root   28859 Aug 19 15:17 sof-hda-generic-idisp-4ch.tplg
-rw-r--r-- 1 root   root   16135 Aug 19 

[Touch-packages] [Bug 1874925] Re: Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

[lavistam]

I have the same problem as this thread. Unfortunately I don't have
dmic_detect in the config files.

Here it my information. The laptop is a Lenovo X1 Extreme Gen3

I have a new laptop and my mic isnt recoginzed by ubuntu (18.04 or
20.04)

$ uname -r
5.4.66-050466-generic

I've been playing with settings to try to get:

snd_hda_intel

to work, and then got lost trying to replace it with sof-firmware per:

https://askubuntu.com/questions/1203799/internal-microphone-not-
detected-lenovo-carbon-x1-7th-gen-ubuntu-19

and also

https://mathieularose.com/ubuntu-19-10-on-lenovo-thinkpad-x1-carbon-7th-
gen/

Currently commented blacklist like so:

```
# blacklist snd_hda_intel
# blacklist snd_soc_skl
```

Which allows my speakers, but not my mic

If I uncomment, I can't see either. I have a thinkpad dock, so some
"mic" is identified through the thunderbolt dock, when I unplug it, I
have no mic recognized

```
ls -l /lib/firmware/intel/sof-tplg/
total 1664
-rw-r--r-- 1 root   root   33227 Aug 19 15:17 sof-apl-da7219.tplg
-rw-r--r-- 1 root   root   23311 Aug 19 15:17 sof-apl-demux-pcm512x.tplg
-rw-r--r-- 1 root   root   10295 Aug 19 15:17 sof-apl-dmic-2ch.tplg
-rw-r--r-- 1 root   root   10431 Aug 19 15:17 sof-apl-dmic-4ch.tplg
-rw-r--r-- 1 root   root   10295 Aug 19 15:17 sof-apl-dmic-a2ch-b2ch.tplg
-rw-r--r-- 1 root   root   10363 Aug 19 15:17 sof-apl-dmic-a2ch-b4ch.tplg
-rw-r--r-- 1 root   root5223 Aug 19 15:17 sof-apl-dmic-a2ch.tplg
-rw-r--r-- 1 root   root   10363 Aug 19 15:17 sof-apl-dmic-a4ch-b2ch.tplg
-rw-r--r-- 1 root   root5223 Aug 19 15:17 sof-apl-dmic-b2ch.tplg
-rw-r--r-- 1 root   root6743 Aug 19 15:17 sof-apl-eq-dmic.tplg
-rw-r--r-- 1 root   root7223 Aug 19 15:17 sof-apl-eq-pcm512x.tplg
-rw-r--r-- 1 root   root9019 Aug 19 15:17 sof-apl-keyword-detect.tplg
-rw-r--r-- 1 root   root   38003 Aug 19 15:17 sof-apl-nocodec.tplg
-rw-r--r-- 1 root   root5127 Aug 19 15:17 sof-apl-pcm512x-nohdmi.tplg
-rw-r--r-- 1 root   root   25031 Aug 19 15:17 sof-apl-pcm512x.tplg
-rw-r--r-- 1 root   root   19815 Aug 19 15:17 sof-apl-rt298.tplg
-rw-r--r-- 1 root   root5791 Aug 19 15:17 sof-apl-src-50khz-pcm512x.tplg
-rw-r--r-- 1 root   root   11623 Aug 19 15:17 sof-apl-src-dmic.tplg
-rw-r--r-- 1 root   root5791 Aug 19 15:17 sof-apl-src-pcm512x.tplg
-rw-r--r-- 1 root   root   43619 Aug 19 15:17 sof-apl-tdf8532.tplg
-rw-r--r-- 1 root   root5127 Aug 19 15:17 sof-apl-wm8804.tplg
-rw-r--r-- 1 root   root   12579 Aug 19 15:17 sof-bdw-rt286.tplg
lrwxrwxrwx 1 root   root  18 Aug 19 15:17 sof-bdw-rt5640.tplg -> 
sof-bdw-rt286.tplg
-rw-r--r-- 1 root   root   13371 Aug 19 15:17 sof-byt-da7213.tplg
-rw-r--r-- 1 root   root   13107 Aug 19 15:17 sof-byt-nocodec.tplg
lrwxrwxrwx 1 root   root  19 Aug 19 15:17 sof-byt-rt5640.tplg -> 
sof-byt-da7213.tplg
lrwxrwxrwx 1 root   root  19 Aug 19 15:17 sof-byt-rt5645.tplg -> 
sof-byt-da7213.tplg
lrwxrwxrwx 1 root   root  19 Aug 19 15:17 sof-byt-rt5651.tplg -> 
sof-byt-da7213.tplg
lrwxrwxrwx 1 root   root  19 Aug 19 15:17 sof-byt-rt5682.tplg -> 
sof-byt-da7213.tplg
-rw-r--r-- 1 root   root   13371 Aug 19 15:17 sof-cht-max98090.tplg
lrwxrwxrwx 1 root   root  20 Aug 19 15:17 sof-cht-nocodec.tplg -> 
sof-byt-nocodec.tplg
-rw-r--r-- 1 root   root7927 Aug 19 15:17 sof-cht-rt5682.tplg
-rw-r--r-- 1 root   root Aug 19 15:17 sof-cht-src-50khz-pcm512x.tplg
-rw-r--r-- 1 root   root   34187 Aug 19 15:17 
sof-cml-demux-rt5682-max98357a.tplg
-rw-r--r-- 1 root   root   29283 Aug 19 15:17 sof-cml-demux-rt5682.tplg
-rw-r--r-- 1 root   root   39787 Aug 19 15:17 sof-cml-rt1011-rt5682.tplg
-rw-r--r-- 1 root   root   34883 Aug 19 15:17 sof-cml-rt5682-kwd.tplg
-rw-r--r-- 1 root   root   39787 Aug 19 15:17 sof-cml-rt5682-max98357a.tplg
-rw-r--r-- 1 root   root   31123 Aug 19 15:17 sof-cml-rt5682.tplg
-rw-r--r-- 1 root   root   32719 Aug 19 15:17 sof-cml-rt700.tplg
-rw-r--r-- 1 root   root   34411 Aug 19 15:17 
sof-cml-rt711-rt1308-mono-rt715.tplg
-rw-r--r-- 1 root   root   39295 Aug 19 15:17 sof-cml-rt711-rt1308-rt715.tplg
-rw-r--r-- 1 root   root   26751 Aug 19 15:17 sof-cml-src-rt5682.tplg
-rw-r--r-- 1 root   root   25715 Aug 19 15:17 sof-cnl-nocodec.tplg
-rw-r--r-- 1 root   root   11335 Aug 19 15:17 sof-cnl-rt274.tplg
-rw-r--r-- 1 root   root   43555 Aug 19 15:17 sof-glk-da7219-kwd.tplg
-rw-r--r-- 1 root   root   34831 Aug 19 15:17 sof-glk-da7219.tplg
-rw-r--r-- 1 root   root   33967 Aug 19 15:17 sof-glk-rt5682.tplg
-rw-r--r-- 1 root   root   48091 Aug 19 15:17 sof-hda-generic-1ch.tplg
-rw-r--r-- 1 root   root   45375 Aug 19 15:17 sof-hda-generic-2ch.tplg
-rw-r--r-- 1 root   root   48227 Aug 19 15:17 sof-hda-generic-3ch.tplg
-rw-r--r-- 1 root   root   45511 Aug 19 15:17 sof-hda-generic-4ch.tplg
-rw-r--r-- 1 root   root   28723 Aug 19 15:17 sof-hda-generic-idisp-2ch.tplg
-rw-r--r-- 1 root   root   28859 Aug 19 15:17 sof-hda-generic-idisp-4ch.tplg
-rw-r--r-- 1 root   root   16135 Aug 19 15:17 sof-hda-generic-idisp.tplg
-rw-r--r-- 1 root   root   32787 Aug 

[Touch-packages] [Bug 1866194] Update Released

[Łukasz Zemczak]

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

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

Title:
  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.

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  Selected audio output device in Settings is ignored after upgrading to
  Ubuntu 20.04.

  [Test Case]

  Start with an older version of Ubuntu like 19.04 or 19.10 and upgrade
  to 20.04. When done, attempt to connect a Bluetooth or USB audio
  device and use it via Settings.

  [Regression Potential]

  Unknown/low. The fix is from upstream and has already been released to
  Ubuntu 20.10 without any problems. Only worth noting it works by
  detecting and removing audio configurations made via older versions of
  PulseAudio. So upon upgrading some old settings may be reset to
  defaults, but the idea is that's less bad than audio devices being
  unusable (this bug).

  [Original Bug Report]

  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1866194] Re: 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.

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.7

---
pulseaudio (1:13.99.1-1ubuntu3.7) focal; urgency=medium

  [Daniel van Vugt]
  * Added d/p/git_config_upgrade.patch to resolve incorrect audio
device selection (LP: #1866194).
  * Refreshed patches:
- d/p/0001-alsa-mixer-Recognize-USB-audio-jack-mixer.patch
- d/p/0036-device-port-queue-CARD-CHANGE-event-before-update-de.patch
- d/p/0700-modules-add-snappy-policy-module.patch
- d/p/gitlab_jack_identifier.patch

  [Kai-Heng Feng]
  * d/p/0001-alsa-mixer-Add-support-for-HP-Thunderbolt-Dock.patch
  * d/p/0002-alsa-mixer-Expand-comments-in-the-HP-Thunderbolt-Doc.patch
Add profile-sets for HP Thunderbolt Dock (LP: #1894606)

 -- Kai-Heng Feng   Fri, 25 Sep 2020
13:00:28 +0800

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

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

Title:
  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.

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  Selected audio output device in Settings is ignored after upgrading to
  Ubuntu 20.04.

  [Test Case]

  Start with an older version of Ubuntu like 19.04 or 19.10 and upgrade
  to 20.04. When done, attempt to connect a Bluetooth or USB audio
  device and use it via Settings.

  [Regression Potential]

  Unknown/low. The fix is from upstream and has already been released to
  Ubuntu 20.10 without any problems. Only worth noting it works by
  detecting and removing audio configurations made via older versions of
  PulseAudio. So upon upgrading some old settings may be reset to
  defaults, but the idea is that's less bad than audio devices being
  unusable (this bug).

  [Original Bug Report]

  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1893170] Re: [Ubuntu 20.10] zlib: DFLTCC compression level switching issues

[Launchpad Bug Tracker]

This bug was fixed in the package zlib - 1:1.2.11.dfsg-2ubuntu1.1

---
zlib (1:1.2.11.dfsg-2ubuntu1.1) focal; urgency=medium

  * Update d/patches/410.patch to current state to fix issues with hardware
accelerated zlib on new s390x machines. LP: #1893170

 -- Michael Hudson-Doyle   Thu, 20 Aug 2020
11:52:59 +1200

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

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

Title:
  [Ubuntu 20.10] zlib: DFLTCC compression level switching issues

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  Fix Released
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * This SRU fixes a combination of multiple issues:

   * zlib DFLTCC compression level switching can corrupt data because
  hardware and software compression states become desynchronized. (LP
  1893170)

   * Since zlib is not working on all s390x system configurations
  support for switching between software and hardware compression is
  required especially for Java. (LP 1882494)

   * zlib on s390x may produce incomplete raw streams (but not
  gzip/zlib). (LP 1889059)

  [Test Case]

   * Since especially DFLTCC requires a s390x generation z15 or LinuxONE
  III the tests need to be done by IBM.

   * IBM has a set of tests available, that exercise public zlib APIs by
  calling them in different sequences with different buffer sizes and
  flush modes.

  * Partially these come from the IBM z/OS team, who developed their own
  zlib support for the hardware accelerator, and partially they are
  developed by the IBM Linux team based on issues encountered during
  development as well as fuzzing.

  * IBM also uses the zlib-ng test-suite as well as squash and stress-
  ng.

   * Compress data using zlib/DFLTCC with different compression level
  and verify state and if data got corrupted or not. (LP 1893170)

   * On a system with patched zlib package, switch between hardware and
  software compression and use zlib via the java.util.zip package
  (http://java.sun.com/developer/technicalArticles/Programming/compression/).
  (LP 1882494)

  * On a z15 system with hardware acceleration compression (DFLTCC)
  enabled, create a raw (negative windowBits value) stream with zlib.
  Then check if EOBS is missing or truncated. (LP 1889059)

  [Regression Potential]

   * There is a certain risk for regressions with the modifications that
  are introduced by the four LP bugs.

   * In case the package fails entirely, it will have (in worst case) an
  impact on all zlib, gzip and DFLTCC compression/decompression
  functions, that are very wide spread (gzip, tar cfz, everything with
  zlib) in Linux and would virtually make the system unusable.

   * If potential issues are limited to hardware assisted compression
  (which is more likely, since these patches are mostly about hw
  assisted compression), then issues would be limited to systems that
  provide this feature (latest s390x generation only).

  * A switch back to software got introduced (by setting DFLTCC=0
  environment variable) that will help to mitigate a potential negative
  impact of the hw assisted compression.

   * Only the latest s390x generation (z15 and LinuxONE III) supports
  hardware assisted DFLTCC and is potentially affected.

   * A patched test package was made available and got successfully
  tested by IBM. All four bugs were finally considered as solved with
  zlib (1:1.2.11.dfsg-2ubuntu2~ppa2) available here:
  
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=zlib

  __

  Description:   zlib: DFLTCC compression level switching issues
  Symptom:   Switching compression levels corrupts data
  Problem:   Hardware and software compression states become desynchronized.
  Solution:  Improve compression state synchronization. Since zlib project
     does not accept patches at the moment, the fix has been
     integrated into the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is 992a7afc3edfa511dff0650d1c545b11bf64e655.
  Reproduction:  Not possible with popular command line tools. The issues were
     discovered using example_call_fuzzer from:
     https://github.com/iii-i/zlib-ng/tree/fuzz/test/fuzz/

  This needs also be applied against 20.04 !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893170/+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 1893170] Update Released

[Łukasz Zemczak]

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

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

Title:
  [Ubuntu 20.10] zlib: DFLTCC compression level switching issues

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  Fix Released
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * This SRU fixes a combination of multiple issues:

   * zlib DFLTCC compression level switching can corrupt data because
  hardware and software compression states become desynchronized. (LP
  1893170)

   * Since zlib is not working on all s390x system configurations
  support for switching between software and hardware compression is
  required especially for Java. (LP 1882494)

   * zlib on s390x may produce incomplete raw streams (but not
  gzip/zlib). (LP 1889059)

  [Test Case]

   * Since especially DFLTCC requires a s390x generation z15 or LinuxONE
  III the tests need to be done by IBM.

   * IBM has a set of tests available, that exercise public zlib APIs by
  calling them in different sequences with different buffer sizes and
  flush modes.

  * Partially these come from the IBM z/OS team, who developed their own
  zlib support for the hardware accelerator, and partially they are
  developed by the IBM Linux team based on issues encountered during
  development as well as fuzzing.

  * IBM also uses the zlib-ng test-suite as well as squash and stress-
  ng.

   * Compress data using zlib/DFLTCC with different compression level
  and verify state and if data got corrupted or not. (LP 1893170)

   * On a system with patched zlib package, switch between hardware and
  software compression and use zlib via the java.util.zip package
  (http://java.sun.com/developer/technicalArticles/Programming/compression/).
  (LP 1882494)

  * On a z15 system with hardware acceleration compression (DFLTCC)
  enabled, create a raw (negative windowBits value) stream with zlib.
  Then check if EOBS is missing or truncated. (LP 1889059)

  [Regression Potential]

   * There is a certain risk for regressions with the modifications that
  are introduced by the four LP bugs.

   * In case the package fails entirely, it will have (in worst case) an
  impact on all zlib, gzip and DFLTCC compression/decompression
  functions, that are very wide spread (gzip, tar cfz, everything with
  zlib) in Linux and would virtually make the system unusable.

   * If potential issues are limited to hardware assisted compression
  (which is more likely, since these patches are mostly about hw
  assisted compression), then issues would be limited to systems that
  provide this feature (latest s390x generation only).

  * A switch back to software got introduced (by setting DFLTCC=0
  environment variable) that will help to mitigate a potential negative
  impact of the hw assisted compression.

   * Only the latest s390x generation (z15 and LinuxONE III) supports
  hardware assisted DFLTCC and is potentially affected.

   * A patched test package was made available and got successfully
  tested by IBM. All four bugs were finally considered as solved with
  zlib (1:1.2.11.dfsg-2ubuntu2~ppa2) available here:
  
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=zlib

  __

  Description:   zlib: DFLTCC compression level switching issues
  Symptom:   Switching compression levels corrupts data
  Problem:   Hardware and software compression states become desynchronized.
  Solution:  Improve compression state synchronization. Since zlib project
     does not accept patches at the moment, the fix has been
     integrated into the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is 992a7afc3edfa511dff0650d1c545b11bf64e655.
  Reproduction:  Not possible with popular command line tools. The issues were
     discovered using example_call_fuzzer from:
     https://github.com/iii-i/zlib-ng/tree/fuzz/test/fuzz/

  This needs also be applied against 20.04 !

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

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

[Touch-packages] [Bug 1894606] Update Released

[Łukasz Zemczak]

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

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

Title:
  [SRU] Add profile-set for HP Thunderbolt Dock

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  HP Thunderbolt Dock has a USB audio device provides headset connector 
functionality. The Dock can also attach an optional USB audio module. Since 
they are both USB audio device, the input/output names are the same and it 
confuses user.

  [Fix]
  Add PulseAudio profile-sets for each USB device with different monikers.

  The merge request is already approved by maintainer, will be merged after 
14.0 release:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/353

  [Test]
  With profile-set applied, two different USB audio device on HP TBT Dock have 
distinctive names.

  [Regression Potential]
  Currently I can't think of any regression risk, as this SRU only adds new 
profile-sets and description translation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894606/+subscriptions

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

[Touch-packages] [Bug 1894606] Re: [SRU] Add profile-set for HP Thunderbolt Dock

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu3.7

---
pulseaudio (1:13.99.1-1ubuntu3.7) focal; urgency=medium

  [Daniel van Vugt]
  * Added d/p/git_config_upgrade.patch to resolve incorrect audio
device selection (LP: #1866194).
  * Refreshed patches:
- d/p/0001-alsa-mixer-Recognize-USB-audio-jack-mixer.patch
- d/p/0036-device-port-queue-CARD-CHANGE-event-before-update-de.patch
- d/p/0700-modules-add-snappy-policy-module.patch
- d/p/gitlab_jack_identifier.patch

  [Kai-Heng Feng]
  * d/p/0001-alsa-mixer-Add-support-for-HP-Thunderbolt-Dock.patch
  * d/p/0002-alsa-mixer-Expand-comments-in-the-HP-Thunderbolt-Doc.patch
Add profile-sets for HP Thunderbolt Dock (LP: #1894606)

 -- Kai-Heng Feng   Fri, 25 Sep 2020
13:00:28 +0800

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

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

Title:
  [SRU] Add profile-set for HP Thunderbolt Dock

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  HP Thunderbolt Dock has a USB audio device provides headset connector 
functionality. The Dock can also attach an optional USB audio module. Since 
they are both USB audio device, the input/output names are the same and it 
confuses user.

  [Fix]
  Add PulseAudio profile-sets for each USB device with different monikers.

  The merge request is already approved by maintainer, will be merged after 
14.0 release:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/353

  [Test]
  With profile-set applied, two different USB audio device on HP TBT Dock have 
distinctive names.

  [Regression Potential]
  Currently I can't think of any regression risk, as this SRU only adds new 
profile-sets and description translation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894606/+subscriptions

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

[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[rahul]

Ubuntu 20.04 user, can confirm this bug.

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1884514] Re: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

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

Title:
  [FFe][20.10 FEAT] zlib/gzip hardware compression enablement

Status in Ubuntu on IBM z Systems:
  In Progress
Status in gzip package in Ubuntu:
  Triaged
Status in zlib package in Ubuntu:
  Triaged

Bug description:
  [Feature Freeze Exception]

  1. Feature:

  The latest s390x hardware comes with a new concept for hardware
  assisted compression/decompression, based on a 'Next Accelerator
  Function unit' (NXU). This is an on-chip concept, a co-processor for
  compression available to all cores on the same chip. It provides
  functions as normal 'problem state' instructions (in other words user
  space instructions that are directly consumable by libraries and
  applications) and supports DEFLATE compliant compression/decompression
  + GZIP CRC/ZLIB Adler.

  To enable this hardware support for zlib and gzip, zlib needs to be compiled 
with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e".
  The value of 0x7e enables hardware compression for the compression levels 1-6 
(out of 0-9).
  There is a significant business value of having the enablement active by 
default, since tests on a system with 4 IFLs and hardware compression enabled 
this way offered (especially for DEFLATE as best case) a speed up of more than 
40x.

  2. Changes

  Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro
  during build of zlib and gzip.

  3. Regression risk

  The concept is new and comes with IBM z15 and LinuxONE III only and is with 
that specific and limited to s390x.
  Hence a potential regressions of this late addition would be limited to s390x 
and there again with the above changes to zlib (and gzip).
  In case of unforeseen issues with the NXU hardware component, a fallback to 
software is done.
  On top a modified zlib package was build and made available in a PPA for 
further testing.
  This change should have been included earlier, but was blocked by other zlib 
tickets/bugs that needed to be fixed and integrated first (like LP 1893170), 
hence this request for late addition.
  __

  HW Compression need to be enabled with Default-Compression-Level 6.

  Adding following CFLAGS attributes during build of zlib and gzip
  "-DDFLTCC_LEVEL_MASK=0x7e"

  CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure

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

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

[Touch-packages] [Bug 1898512] Re: [System Product Name, Nvidia GPU 93 HDMI/DP, Digital Out, HDMI] fails after a while

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  [System Product Name, Nvidia GPU 93 HDMI/DP, Digital Out, HDMI] fails
  after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I'm using ubuntu 20.04, I recently upgraded from 18.

  I have nvidia video card, connected to HDMI TV which outputs sound.

  I think the sound will not work sometimes after boot up, sometimes it
  does work.

  But it definitely does not work when ubuntu goes to idle. As soon as
  ubuntu goes to idle and screen starts to fade, sound will disappear.

  Funny enough, if I play a game from emulator MAME, MAME game will
  bring sound back, and all my youtube and other games sound will work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  5 14:24:09 2020
  InstallationDate: Installed on 2018-09-08 (758 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: TU106 High Definition Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulseAudioLog:
   Oct 05 12:14:37 stormrage-System-Product-Name dbus-daemon[874]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.31' (uid=121 pid=1175 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
   Oct 05 12:14:38 stormrage-System-Product-Name pulseaudio[1175]: No UCM verb 
is valid for hw:0
   Oct 05 12:14:38 stormrage-System-Product-Name dbus-daemon[874]: [system] 
Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' 
requested by ':1.36' (uid=121 pid=1175 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   Oct 05 12:14:38 stormrage-System-Product-Name pulseaudio[1175]: No UCM verb 
is valid for hw:2
  Symptom_Type: Sound works for a while, then breaks
  Title: [System Product Name, Nvidia GPU 93 HDMI/DP, Digital Out, HDMI] fails 
after a while
  UpgradeStatus: Upgraded to focal on 2020-10-03 (1 days ago)
  dmi.bios.date: 08/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1903
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS V GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1903:bd08/19/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1898512] [NEW] [System Product Name, Nvidia GPU 93 HDMI/DP, Digital Out, HDMI] fails after a while

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm using ubuntu 20.04, I recently upgraded from 18.

I have nvidia video card, connected to HDMI TV which outputs sound.

I think the sound will not work sometimes after boot up, sometimes it
does work.

But it definitely does not work when ubuntu goes to idle. As soon as
ubuntu goes to idle and screen starts to fade, sound will disappear.

Funny enough, if I play a game from emulator MAME, MAME game will bring
sound back, and all my youtube and other games sound will work.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  5 14:24:09 2020
InstallationDate: Installed on 2018-09-08 (758 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: TU106 High Definition Audio Controller - HDA NVidia
Symptom_Jack: Digital Out, HDMI
Symptom_PulseAudioLog:
 Oct 05 12:14:37 stormrage-System-Product-Name dbus-daemon[874]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.31' (uid=121 pid=1175 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
 Oct 05 12:14:38 stormrage-System-Product-Name pulseaudio[1175]: No UCM verb is 
valid for hw:0
 Oct 05 12:14:38 stormrage-System-Product-Name dbus-daemon[874]: [system] 
Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' 
requested by ':1.36' (uid=121 pid=1175 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
 Oct 05 12:14:38 stormrage-System-Product-Name pulseaudio[1175]: No UCM verb is 
valid for hw:2
Symptom_Type: Sound works for a while, then breaks
Title: [System Product Name, Nvidia GPU 93 HDMI/DP, Digital Out, HDMI] fails 
after a while
UpgradeStatus: Upgraded to focal on 2020-10-03 (1 days ago)
dmi.bios.date: 08/19/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1903
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MAXIMUS V GENE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1903:bd08/19/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug focal
-- 
[System Product Name, Nvidia GPU 93 HDMI/DP, Digital Out, HDMI] fails after a 
while
https://bugs.launchpad.net/bugs/1898512
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver 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 1895405] Re: Bluetooth mouse does not work in Ubuntu 16.04

[Daniel van Vugt]

Ubuntu 16.04 is a few years old now. In case the problem has already
been fixed, please try booting Ubuntu 20.04.1 from USB:

  https://ubuntu.com/download/desktop

and tell us if it has the same issue.

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

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

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

Title:
  Bluetooth mouse does not work in Ubuntu 16.04

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1. Submitted bug report
  2. Manufactuere of mous is Windows surface mouse pink
  3. Mouse is connected via bluetooth
  4. Mouse uses trackpad
  5. Mouse has 1 physical button, can press on left side or right side of 
button for different functions
  6. Using Ubuntu 16.04

  Wireless bluetooth mouse does not work in Ubuntu 16.04 but works in my
  standard Windows 10 OS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-117.118~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-117-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep 12 13:21:38 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Device [103c:82c1]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:82c1]
  InstallationDate: Installed on 2020-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 
(20200806)
  Lsusb:
   Bus 002 Device 002: ID 125f:0001 A-DATA Technology Co., Ltd. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 064e:3401 Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic 
root=UUID=94a7e873-47e3-4c72-af71-ef0c3fb72af1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.39
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 82C1
  dmi.board.vendor: HP
  dmi.board.version: 09.42
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.39:bd11/12/2018:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn82C1:rvr09.42:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Spectre x360 Convertible
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Sep 12 13:15:30 2020
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1898186] Re: Qualcomm Atheros Communications AR3011 USB 0cf3:3005 Bluetooth headset stopped connecting

[Daniel van Vugt]

At the time the bug was created, rfkill showed this (from the above
attachments):

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1898186/+attachment/5416565/+files/rfkill.txt

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

Title:
  Qualcomm Atheros Communications AR3011 USB 0cf3:3005 Bluetooth headset
  stopped connecting

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1. expected to connect the stereo headset via Bluetooth as usual. 
  2. Headset stopped connecting 
  3. Updated again, checked the headset on Android. It works on Android, but 
not in Ubuntu. - after a recent system update (1-3 years ago), the stereo 
headset stopped connecting.

  maybe something related
  #295012 Bluetooth ALSA Crash with Skype

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  2 16:41:55 2020
  InstallationDate: Installed on 2020-05-02 (152 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire V5-571G
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=17fd49fa-ba18-4d43-b4ca-a3ad62753fd3 ro zswap.enabled=1 quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.17
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571G
  dmi.board.vendor: Acer
  dmi.board.version: V2.17
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.17
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.17:bd02/27/2013:svnAcer:pnAspireV5-571G:pvrV2.17:rvnAcer:rnAspireV5-571G:rvrV2.17:cvnAcer:ct9:cvrV2.17:
  dmi.product.family: Aspire V5-571G
  dmi.product.name: Aspire V5-571G
  dmi.product.sku: Aspire V5-571G_072D_2.17
  dmi.product.version: V2.17
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E0:91:53:65:99:10  ACL MTU: 1022:8  SCO MTU: 121:3
UP RUNNING PSCAN ISCAN 
RX bytes:18789 acl:40 sco:0 events:408 errors:0
TX bytes:2538 acl:36 sco:0 commands:135 errors:0

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

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

[Touch-packages] [Bug 1898447] Re: HDMI sound output disappears after sleep

[Daniel van Vugt]

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

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 1898447

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

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

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER

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

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

[Touch-packages] [Bug 1898447] Re: HDMI sound output disappears after sleep

[Daniel van Vugt]

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

Actually this sounds like bug 1888598. But see also bug 1895665.

** This bug has been marked a duplicate of bug 1888598
   pulseaudio has is buggy with hdmi audio and sleep/wake

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

Title:
  HDMI sound output disappears after sleep

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am using an Nvidia graphics card with HDMI output. The sound output
  choice for HDMI is missing from either pavucontrol or the GNOME
  settings sound settings after waking the computer up from sleep.
  Running `pacmd list-cards` does show the HDMI sound output listed. I
  can bring the output back as a choice if I run `pulseaudio -k`, but I
  will lose the choice to select this output if I put the computer to
  sleep, leaving me only with the S/PDIF output from my motherboard.

  I didnt see this issue prior to what I suspect was an `apt upgrade`.

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Kernel: 5.4.0-48-generic
  Desktop Environment: GNOME 3.36.3

  pulseaudio:
    Installed: 1:13.99.1-1ubuntu3.6
    Candidate: 1:13.99.1-1ubuntu3.6
    Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Hardware Info:
  CPU: AMD Ryzen 9 3950x
  GPU: Nvidia RTX 2080ti (Driver 450.66 )
  Motherboard: Gigabyte X570 AORUS MASTER

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

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