date:20201019

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

** This bug has been marked a duplicate of bug 1899289
   Computer freezes and the fan will start going really hard

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  The computer freezes the fan speeds up and the screen goes to a black
  screen showing the operations the computer is doing before it shuts
  down

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-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.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 01:00:24 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Razer USA Ltd. UHD Graphics 630 (Mobile) [1a58:2001]
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:2001]
  MachineType: Razer Blade
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=dd0ac3c7-c88c-4b4a-90ea-b9a430d6e2c3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2019
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.02
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.02:bd05/21/2019:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.sku: RZ09-02705E75
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer
  version.compiz: compiz N/A
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

Re: [Touch-packages] [Bug 1900481] Re: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card

2020-10-19 Thread x31eq

On 20/10/2020, Daniel van Vugt <1900...@bugs.launchpad.net> wrote:
> Actually, more likely the problem is that you have the Jack audio daemon
> installed. It might be stealing the audio devices from PulseAudio.
>
> Please try uninstalling 'jackd'.

I tried both: I removed jackd and deleted my local PulseAudio
configuration and rebooted and the problem is still there.

I remember changing a PulseAudio setting to allow different users on
the same desktop to use sound.  I can't remember how I did it, but
could that be a global setting that's causing a problem?

>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1900481
>
> Title:
>   [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect
>   card
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Following upgrade to 20.04, I have no audio.  My output device is
>   "Dummy Output".  I chose one audio device to report against: none are
>   detected.  All this may be obvious from the auto-detected diagnostics.
>   It was working in 18.04
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: pulseaudio 1:13.99.1-1ubuntu3.7
>   ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
>   Uname: Linux 5.4.0-51-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.9
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
> '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
> '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code
> 1:
>   CasperMD5CheckResult: skip
>   CurrentDesktop: MATE
>   Date: Mon Oct 19 19:43:52 2020
>   InstallationDate: Installed on 2018-05-05 (897 days ago)
>   InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64
> (20180505)
>   SourcePackage: pulseaudio
>   Symptom: audio
>   Symptom_Card: HDA-Intel - HDA Intel MID
>   Symptom_Jack: Mic, Top
>   Title: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect
> card
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/25/2010
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A10
>   dmi.board.name: 030DMJ
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A10
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: A10
>   dmi.modalias:
> dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn030DMJ:rvrA10:cvnDellInc.:ct8:cvrA10:
>   dmi.product.name: Vostro 3300
>   dmi.product.sku: To be filled by O.E.M.
>   dmi.product.version: A10
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1900481/+subscriptions
>

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

Title:
  [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect
  card

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following upgrade to 20.04, I have no audio.  My output device is
  "Dummy Output".  I chose one audio device to report against: none are
  detected.  All this may be obvious from the auto-detected diagnostics.
  It was working in 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Oct 19 19:43:52 2020
  InstallationDate: Installed on 2018-05-05 (897 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180505)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel MID
  Symptom_Jack: Mic, Top
  Title: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 030DMJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn030DMJ:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Vostro 3300
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list:

[Touch-packages] [Bug 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15

2020-10-19 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: New => 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/1899621

Title:
  [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on
  z15

Status in Release Notes for Ubuntu:
  New
Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  In Progress
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  Description:   zlib: inflateSyncPoint() returns an incorrect result on z15
  Symptom:   Certain rsync builds fail with "error in rsync protocol data
     stream" on z15.
  Problem:   inflateSyncPoint() does not take into account the hardware
     compression state and returns an incorrect result.
  Solution:  Make inflateSyncPoint() fail if the hardware compression is on.
     The hardware does not provide enough information in order to
     implement this function.

  [Impact]

   * Certain rsync builds fail with "error in rsync protocol data
  stream" on z15.

   * On ubuntu, rsync normally uses zstd or lz4. But when rsync is
  forced to use non-default zlib compression (-z flag) it uses
  inflateSyncPoint() API. This can also happen when rsync on the the
  other end doesn't support zstd & lz4.

   * inflateSyncPoint() does not take into account the hardware
  compression state and returns an incorrect result.

   * Make inflateSyncPoint() fail if the hardware compression is on. The
  hardware does not provide enough information in order to implement
  this function.

   * Above makes rsync to succeed, when zlib uses hardware compression.

  [Test Case]

  Reproduction:  z15 only: printf 1 >1 && rsync -z 1 2

  [Regression Potential]

   * inflateSyncPoint API is rarely used. Scanning codesearch, there is
  a lot of false positives due to embedded copies of zlib in all the
  things. I do see that both rsync and backuppc-rsync use it. It used
  during a safety check to ensure that algorithm is not at a sync point
  (or that cannot be determined). Nonetheless, returning error is a
  safer implementation for this API call.

  [Other Info]

   * This is a regression introduced by adding & enabling zlib hw
  acceleration by default on z15; and discovering using rsync that one
  API is implemented incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899621/+subscriptions

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

[Touch-packages] [Bug 1900649] [NEW] Xorg crash

2020-10-19 Thread Russell Cape

Public bug reported:

The computer freezes the fan speeds up and the screen goes to a black
screen showing the operations the computer is doing before it shuts down

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-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.80.02  Wed Sep 23 01:13:39 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 20 01:00:24 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Razer USA Ltd. UHD Graphics 630 (Mobile) [1a58:2001]
 NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:2001]
MachineType: Razer Blade
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=dd0ac3c7-c88c-4b4a-90ea-b9a430d6e2c3 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2019
dmi.bios.vendor: Razer
dmi.bios.version: 01.02
dmi.board.name: DANA_MB
dmi.board.vendor: Razer
dmi.chassis.type: 10
dmi.chassis.vendor: Razer
dmi.modalias: 
dmi:bvnRazer:bvr01.02:bd05/21/2019:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
dmi.product.family: 1A582001 Razer Blade
dmi.product.name: Blade
dmi.product.sku: RZ09-02705E75
dmi.product.version: 1.04
dmi.sys.vendor: Razer
version.compiz: compiz N/A
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug crash focal 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/1900649

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  The computer freezes the fan speeds up and the screen goes to a black
  screen showing the operations the computer is doing before it shuts
  down

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-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.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 01:00:24 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Razer USA Ltd. UHD Graphics 630 (Mobile) [1a58:2001]
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile]

[Touch-packages] [Bug 1900640] [NEW] Ubuntu 20.04 has no capability of surrounding-text feature

2020-10-19 Thread Nattapong Sirilappanich

Public bug reported:

I recently upgrade my Ubuntu LTS from 18.04 to 20.04.
After the upgrade, I failed to type Thai text with any combining character in 
some apps.
The log contains this error message:
`gnome-shell[2076]: (google-chrome-stable:2069): IBUS-WARNING **: 09:07:10.843: 
google-chrome-stable has no capability of surrounding-text feature`
`gnome-terminal-[2589]: gnome-terminal-server has no capability of 
surrounding-text feature`

Expected behavior: Capable of typing any Thai character in any app.
Actual behavior: Only few apps support typing Thai character, e.g. Firefox, 
Gnome Text Editor.

Step to reproduce:
1. Boot up the machine.
2. Open Google Chrome.
3. Switch keyboard layout to `Thai (LibThai)`
4. Type Thai text "กิน" which is equals to following keystroke "dbo" but with 
Thai keyboard layout.


Current workaround:
Whenever you want to type Thai switch 
1. Open `Gnome Text Editor`
2. Switch keyboard layout to `Thai (LibThai)`
3. Switch to Chrome
4. Type Thai

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


** Tags: im thai

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

Title:
  Ubuntu 20.04 has no capability of surrounding-text feature

Status in ibus package in Ubuntu:
  New

Bug description:
  I recently upgrade my Ubuntu LTS from 18.04 to 20.04.
  After the upgrade, I failed to type Thai text with any combining character in 
some apps.
  The log contains this error message:
  `gnome-shell[2076]: (google-chrome-stable:2069): IBUS-WARNING **: 
09:07:10.843: google-chrome-stable has no capability of surrounding-text 
feature`
  `gnome-terminal-[2589]: gnome-terminal-server has no capability of 
surrounding-text feature`

  Expected behavior: Capable of typing any Thai character in any app.
  Actual behavior: Only few apps support typing Thai character, e.g. Firefox, 
Gnome Text Editor.

  Step to reproduce:
  1. Boot up the machine.
  2. Open Google Chrome.
  3. Switch keyboard layout to `Thai (LibThai)`
  4. Type Thai text "กิน" which is equals to following keystroke "dbo" but with 
Thai keyboard layout.

  
  Current workaround:
  Whenever you want to type Thai switch 
  1. Open `Gnome Text Editor`
  2. Switch keyboard layout to `Thai (LibThai)`
  3. Switch to Chrome
  4. Type Thai

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

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

[Touch-packages] [Bug 1900481] Re: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card

Actually, more likely the problem is that you have the Jack audio daemon
installed. It might be stealing the audio devices from PulseAudio.

Please try uninstalling 'jackd'.

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

Title:
  [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect
  card

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following upgrade to 20.04, I have no audio.  My output device is
  "Dummy Output".  I chose one audio device to report against: none are
  detected.  All this may be obvious from the auto-detected diagnostics.
  It was working in 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Oct 19 19:43:52 2020
  InstallationDate: Installed on 2018-05-05 (897 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180505)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel MID
  Symptom_Jack: Mic, Top
  Title: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 030DMJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn030DMJ:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Vostro 3300
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1900481] Re: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card

Sounds like bug 1866194 but you also seem to have the fix for that.
Regardless, please try:

  cd ~/.config
  rm -rf pulse

and then reboot.


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

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

Title:
  [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect
  card

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following upgrade to 20.04, I have no audio.  My output device is
  "Dummy Output".  I chose one audio device to report against: none are
  detected.  All this may be obvious from the auto-detected diagnostics.
  It was working in 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Oct 19 19:43:52 2020
  InstallationDate: Installed on 2018-05-05 (897 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180505)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel MID
  Symptom_Jack: Mic, Top
  Title: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 030DMJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn030DMJ:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Vostro 3300
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

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

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

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

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] Xorg freeze

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

** Changed in: ubuntu
Status: Invalid => 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/1900466

Title:
[radeon] Xorg freeze

Status in Ubuntu:
Incomplete

Bug description:

Release Ubuntu 18.04

When I type apt-cache policy pkgname
Unable to locate package pkgname

Expceted to Happen: not freeze or crash

What happened instead: it crashed

Graphics: ATI RV515
Processor: Intel® Core™2 CPU T7200 @ 2.00GHz × 2
Gnome: 3.28.1

I am restoring this old Lenovo T60.
I just installed a 512GB SSD drive
4GB of Ram
Intel duo 2 core T7200 64 bit processor

Single booting: only Ubuntu is on this machine.

It took me several installation attempts. Initially after installing
Ubuntu I would only see a purple screen with stripes but nothing would
come on.

Finally I installed it and Ubuntu started. I am using the laptop to
file this bug report.

Now I have the issue of completely random freezes/crashes while using the
console, or firefox or even other apps.
Completely random.

The cursor does not move, I open any random app and the screen goes
black where the app window should be.

The only way out is to reboot the machine.

A few times I actually had to reinstall the 0S from the CD install.

You probably will find records as I must have done this tens of times
since last night.

Please help me.
Thank you

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 19 09:31:34 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400]
[1002:7145] (prog-if 00 [VGA controller])
Subsystem: Lenovo Thinkpad T60 model 2007 [17aa:2006]
MachineType: LENOVO 2007Z22
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic
root=UUID=0718074d-db39-4731-aac6-36e1ece0157e ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETE3WW (2.23 )
dmi.board.name: 2007Z22
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn2007Z22:pvrThinkPadT60:rvnLENOVO:rn2007Z22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T60
dmi.product.name: 2007Z22
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage

[Touch-packages] [Bug 1900288] Re: package bluez 5.48-0ubuntu3.4 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

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

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 1769800, 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 1769800
   package bluez failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1 ["Unable to get on D-Bus"]

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

Title:
  package bluez 5.48-0ubuntu3.4 failed to install/upgrade: installed
  bluez package post-installation script subprocess returned error exit
  status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  i am not sure about the error . I am a newbie !

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.4
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  Date: Sat Oct 17 13:18:02 2020
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-10-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=df534ee1-f125-4822-a2d1-8898bc6ee8ce ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12ubuntu0.1
  SourcePackage: bluez
  Title: package bluez 5.48-0ubuntu3.4 failed to install/upgrade: installed 
bluez package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 MAX (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd04/20/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2MAX(MS-7B84):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 11:11:11:11:11:11  ACL MTU: 940:4  SCO MTU: 48:10
UP RUNNING PSCAN ISCAN 
RX bytes:119303 acl:61 sco:1816 events:1828 errors:0
TX bytes:734416 acl:1404 sco:1667 commands:190 errors:0

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

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

[Touch-packages] [Bug 1769800] Re: package bluez failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ["Unable to get on D-Bus"]

** Tags added: bionic

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

Title:
  package bluez failed to install/upgrade: subprocess installed post-
  installation script returned error exit status 1 ["Unable to get on
  D-Bus"]

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  error occurred at initial boot-up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Mon May  7 18:10:42 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-02-05 (91 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Precision M2400
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=bfcb572e-5cce-49d0-8b64-5ca3d710e894 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0U698R
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/08/2009:svnDellInc.:pnPrecisionM2400:pvr:rvnDellInc.:rn0U698R:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M2400
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:22:5F:B6:8C:FB  ACL MTU: 1021:8  SCO MTU: 64:8
DOWN 
RX bytes:607 acl:0 sco:0 events:39 errors:0
TX bytes:3303 acl:0 sco:0 commands:39 errors:0

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

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

[Touch-packages] [Bug 1900135] Re: Bluetooth headsets (mostly Sony) are not working HSP/HFP mode

** Summary changed:

- Bluetooth headsets are not working HSP/HFP mode
+ Bluetooth headsets (mostly Sony) are not working HSP/HFP mode

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

Title:
  Bluetooth headsets (mostly Sony) are not working HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sony WH-1000XM2 and Taotronics SoundLiberty 53 are both not working in
  headset mode, but do in A2DP mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marc   2635 F pulseaudio
   /dev/snd/controlC0:  marc   2635 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 16 13:06:42 2020
  InstallationDate: Installed on 2020-06-13 (124 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.07.23
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P7xxTM1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.07.23:bd04/09/2019:svnNotebook:pnP7xxTM1:pvrNotApplicable:rvnNotebook:rnP7xxTM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P7xxTM1
  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/bluez/+bug/1900135/+subscriptions

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

[Touch-packages] [Bug 1899019] Re: Typo in UDisks action

2020-10-19 Thread Seth Arnold

Hello Kevin, thanks for the excellent GHSL-2020-161 report. Given that
the polkit rules are intentional, if ancient, and the udisks2 team
doesn't want to treat the symlink finding as a security bug, I'm going
to open this publicly and mark it wontfix, to reflect what's likely
going to happen for our currently released systems.

I do hope upstream handles the symlink discovery eventually but I can
appreciate why they wouldn't want to handle it as a security issue.

Thanks

** Information type changed from Private Security to Public Security

** Changed in: policykit-desktop-privileges (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Typo in UDisks action

Status in policykit-desktop-privileges package in Ubuntu:
  Won't Fix

Bug description:
  It appears that com.ubuntu.desktop.pkla contains a typo in the UDisks
  section:

  [Mounting, checking, etc. of internal drives]
  Identity=unix-group:admin;unix-group:sudo
  
Action=org.freedesktop.udisks.filesystem-*;org.freedesktop.udisks.drive-ata-smart*;org.freedesktop.udisks2.filesystem-mount-system;org.freedesktop.udisks2.encrypted-unlock-system;org.freedesktop.udisks2.filesystem-fstab;
  ResultActive=yes

  Notice that the first two actions contain the string "udisks", rather
  than "udisks2", which appears to be a typo.

  However, the typo is actually a lucky accident because it is
  preventing a vulnerability in UDisks from being exploited. The
  vulnerable code in UDisks is protected by the `org.freedesktop.udisks2
  .filesystem-take-ownership` polkit action, so it will become
  accessible if the typo is fixed. I have separately reported the UDisks
  vulnerability to the maintainers of UDisks. I have attached a copy of
  that report for your information.

  I would recommend removing the first two actions from this file. Since
  they don't currently work, presumably nobody will miss them if they
  are removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1899019/+subscriptions

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

[Touch-packages] [Bug 1892290] Re: PXE load Focal initrd.img-5.4.0-42-generic always timeout

2020-10-19 Thread cleary

Thanks! and also for the tip on `mknetdir` - I will be checking it out!

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

Title:
  PXE load Focal initrd.img-5.4.0-42-generic always timeout

Status in grub2 package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  PXE booting Focal initrd always gets a timeout, but PXE booting Bionic initrd 
works
  error: timeout reading `initrd.img-5.4.0-42-generic'.

  grub.cfg
  
  menuentry "boot_iscsi"  {
  linux vmlinuz-5.4.0-42-generic  ...
  initrd initrd.img-5.4.0-42-generic
  }

  grub, kernel and initrd get from Focal boot dir
  $ cp /usr/lib/grub/arm64-efi-signed/grubnetaa64.efi.signed 
~/tftproot/grubaa64.efi
  $ cp /boot/vmlinuz-5.4.0-42-generic  ~/tftproot/
  $ cp /boot/initrd.img-5.4.0-42-generic ~/tftproot/

  hardware
  
  Real aarch64 server or qemu-system-aarch64 machine

  software
  
  $ apt search grub-efi-arm64
  Sorting... Done
  Full Text Search... Done
  grub-efi-arm64/focal-updates,focal-security,now 2.04-1ubuntu26.2 arm64 
[installed]
GRand Unified Bootloader, version 2 (ARM64 UEFI version)

  grub-efi-arm64-bin/focal-updates,focal-security,now 2.04-1ubuntu26.2 arm64 
[installed,automatic]
GRand Unified Bootloader, version 2 (ARM64 UEFI modules)

  grub-efi-arm64-dbg/focal-updates,focal-security 2.04-1ubuntu26.2 arm64
GRand Unified Bootloader, version 2 (ARM64 UEFI debug files)

  grub-efi-arm64-signed/focal-updates,focal-security,now 
1.142.4+2.04-1ubuntu26.2 arm64 [installed]
GRand Unified Bootloader, version 2 (EFI-ARM64 version, signed)

  grub-efi-arm64-signed-template/focal-updates,focal-security 2.04-1ubuntu26.2 
arm64
GRand Unified Bootloader, version 2 (ARM64 UEFI signing template)

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal
  $ uname -a
  Linux j12-d05-07 5.4.0-42-generic #1 SMP Tue Jul 7 02:48:00 GMT 2020 aarch64 
aarch64 aarch64 GNU/Linux

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

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

[Touch-packages] [Bug 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15

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

---
zlib (1:1.2.11.dfsg-2ubuntu4) groovy; urgency=medium

  * Cherrypick update of s390x hw acceleration #410 pull request patch,
which corrects inflateSyncPoint() return value to always gracefully
fail when hw acceleration is in use. This fixes rsync failure with
zlib compression on hw accelerated s390x. LP: #1899621

 -- Dimitri John Ledkov   Thu, 15 Oct 2020 11:01:38
+0100

** Changed in: zlib (Ubuntu Groovy)
   Status: In Progress => 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/1899621

Title:
  [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on
  z15

Status in Release Notes for Ubuntu:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  In Progress
Status in zlib source package in Groovy:
  Fix Released

Bug description:
  Description:   zlib: inflateSyncPoint() returns an incorrect result on z15
  Symptom:   Certain rsync builds fail with "error in rsync protocol data
     stream" on z15.
  Problem:   inflateSyncPoint() does not take into account the hardware
     compression state and returns an incorrect result.
  Solution:  Make inflateSyncPoint() fail if the hardware compression is on.
     The hardware does not provide enough information in order to
     implement this function.

  [Impact]

   * Certain rsync builds fail with "error in rsync protocol data
  stream" on z15.

   * On ubuntu, rsync normally uses zstd or lz4. But when rsync is
  forced to use non-default zlib compression (-z flag) it uses
  inflateSyncPoint() API. This can also happen when rsync on the the
  other end doesn't support zstd & lz4.

   * inflateSyncPoint() does not take into account the hardware
  compression state and returns an incorrect result.

   * Make inflateSyncPoint() fail if the hardware compression is on. The
  hardware does not provide enough information in order to implement
  this function.

   * Above makes rsync to succeed, when zlib uses hardware compression.

  [Test Case]

  Reproduction:  z15 only: printf 1 >1 && rsync -z 1 2

  [Regression Potential]

   * inflateSyncPoint API is rarely used. Scanning codesearch, there is
  a lot of false positives due to embedded copies of zlib in all the
  things. I do see that both rsync and backuppc-rsync use it. It used
  during a safety check to ensure that algorithm is not at a sync point
  (or that cannot be determined). Nonetheless, returning error is a
  safer implementation for this API call.

  [Other Info]

   * This is a regression introduced by adding & enabling zlib hw
  acceleration by default on z15; and discovering using rsync that one
  API is implemented incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899621/+subscriptions

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

[Touch-packages] [Bug 1900436] Re: new upstream release 2020b

This bug was fixed in the package tzdata - 2020b-1ubuntu1

---
tzdata (2020b-1ubuntu1) groovy; urgency=medium

  * Merge from Debian unstable (LP: #1900436). Remaining changes:
- Ship ICU timezone data files which are utilized by php and update them
  to 2020b.

tzdata (2020b-1) unstable; urgency=medium

  * New upstream version, affecting the following past and future
timestamps:
- Revised predictions for Morocco's changes starting in 2023.
- Macquarie Island has stayed in sync with Tasmania since 2011.
- Casey, Antarctica is at +08 in winter and +11 in summer since 2018.
  * Update German debconf translation, by Helge Kreutzmann.  Closes:
#960783.
  * Update Dutch debconf translation, by Frans Spiesschaert.  Closes:
#963007.
  * Update Portuguese debconf translation, by Rui Branco.  Closes:
#871051.
  * Update debian/upstream/signing-key.asc.
  * Get rid of old SystemV timezones, as this has been fully removed
upstream. Convert existing configuration to the "new" America/*
names.
  * Drop pacificnew support, it has been removed upstream.

 -- Brian Murray   Mon, 19 Oct 2020 10:18:46 -0700

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

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

Title:
  new upstream release 2020b

Status in tzdata package in Ubuntu:
  Fix Released

Bug description:
  There is a new upstream release of tzdata, 2020b, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Canada's Yukon changes to -07 on 2020-11-01.
  - Casey, Antarctica is at +08 in winter and +11 in summer.
  - Correct several transitions for Hungary for 1918/1983.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

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

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

[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink

** Changed in: apport
   Status: In Progress => Fix Released

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

Title:
  gdb doesn't search in debug-file-directory for .gnu_debugaltlink

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  New
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  As far as I can tell gdb version 8.2.90 isn't searching the debug-
  file-directory, which I set, for the '.gnu_debugaltlink' which is in
  the debug symbols. Here's the error I'm seeing:

  Type "apropos word" to search for commands related to "word".
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
  Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
  could not find '.gnu_debugaltlink' file for 
/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
  (No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)

  Here's part of an strace of what's going on behind the scenes:

  lstat("/srv/vms/apport-sandbox-dir/Ubuntu 
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
 {st_mode=S_IFREG|0644, st_size=839744, ...}) = 0 
  openat(AT_FDCWD, 
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

  This is the only time "/usr/lib/debug" is searched, generally
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox/usr/lib/debug/" is used. I'll attach the full strace though.

  For completeness here's the gdb command I'm using:

  Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
  /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
  --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
  prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
  --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
  19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
  /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
  -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
  dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
  "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
  sandbox//usr/bin/gnome-calculator"' --ex 'core-file
  /tmp/apport_core_1b6dn6np'

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

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

Re: [Touch-packages] [Bug 1900436] Re: new upstream release 2020b

On Mon, Oct 19, 2020 at 08:44:04PM -, Sebastien Bacher wrote:
> Unsure which serie is targetted there but the default format change in
> the new version is triggering a libglib issue which was fixed in
> https://gitlab.gnome.org/GNOME/glib/-/commit/6ec67cd3 so that's
> something to resolve with the update

For Groovy I'm under the impression this is fixed with glib2.0 version
2.66.1-2.

--
Brian Murray

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

Title:
  new upstream release 2020b

Status in tzdata package in Ubuntu:
  In Progress

Bug description:
  There is a new upstream release of tzdata, 2020b, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Canada's Yukon changes to -07 on 2020-11-01.
  - Casey, Antarctica is at +08 in winter and +11 in summer.
  - Correct several transitions for Hungary for 1918/1983.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

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

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

[Touch-packages] [Bug 1900436] Re: new upstream release 2020b

Unsure which serie is targetted there but the default format change in
the new version is triggering a libglib issue which was fixed in
https://gitlab.gnome.org/GNOME/glib/-/commit/6ec67cd3 so that's
something to resolve with the update

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

Title:
  new upstream release 2020b

Status in tzdata package in Ubuntu:
  In Progress

Bug description:
  There is a new upstream release of tzdata, 2020b, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Canada's Yukon changes to -07 on 2020-11-01.
  - Casey, Antarctica is at +08 in winter and +11 in summer.
  - Correct several transitions for Hungary for 1918/1983.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

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

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

[Touch-packages] [Bug 1893798] Re: Wired interface fails after random uptime and then cannot bring back up

thank you for your bug report, the issue is likely with the driver
rather than the software stack though

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

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

Title:
  Wired interface fails after random uptime and then cannot bring back
  up

Status in linux package in Ubuntu:
  New

Bug description:
  I'm on 20.04, on a Dell XPS 9730.  Upon boot, the wired connection
  comes up fine but, after a seemingly random time, the interface fails.
  If I watch the NetworkManager journal and try and switch the interface
  off and then back on in Gnome Control Panel, the interface keeps
  timing out:

  
  Sep 01 10:40:58 mia NetworkManager[3198]:   [1598971258.0049] device 
(enxd89ef3f04d55): Activation: starting connection 'Port Replicator' 
(e1c0084e-2246-3a09-81c2-9916d22812f8)
  Sep 01 10:40:58 mia NetworkManager[3198]:   [1598971258.0054] audit: 
op="connection-activate" uuid="e1c0084e-2246-3a09-81c2-9916d22812f8" name="Port 
Replicator" pid=6219 uid=1000 result="success"
  Sep 01 10:40:58 mia NetworkManager[3198]:   [1598971258.0060] device 
(enxd89ef3f04d55): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:40:58 mia NetworkManager[3198]:   [1598971258.0082] device 
(enxd89ef3f04d55): state change: prepare -> config (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:40:58 mia NetworkManager[3198]:   [1598971258.0114] device 
(enxd89ef3f04d55): state change: config -> ip-config (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:40:58 mia NetworkManager[3198]:   [1598971258.0130] dhcp4 
(enxd89ef3f04d55): activation: beginning transaction (timeout in 45 seconds)
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7420] dhcp4 
(enxd89ef3f04d55): request timed out
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7420] dhcp4 
(enxd89ef3f04d55): state changed unknown -> timeout
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7421] device 
(enxd89ef3f04d55): state change: ip-config -> failed (reason 
'ip-config-unavailable', sys-iface-state: 'managed')
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7433] device 
(enxd89ef3f04d55): Activation: failed for connection 'Port Replicator'
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7436] device 
(enxd89ef3f04d55): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7820] dhcp4 
(enxd89ef3f04d55): canceled DHCP transaction
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7821] dhcp4 
(enxd89ef3f04d55): state changed timeout -> done
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7894] policy: 
auto-activating connection 'Port Replicator' 
(e1c0084e-2246-3a09-81c2-9916d22812f8)
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7906] device 
(enxd89ef3f04d55): Activation: starting connection 'Port Replicator' 
(e1c0084e-2246-3a09-81c2-9916d22812f8)
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7907] device 
(enxd89ef3f04d55): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7912] device 
(enxd89ef3f04d55): state change: prepare -> config (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7917] device 
(enxd89ef3f04d55): state change: config -> ip-config (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7920] dhcp4 
(enxd89ef3f04d55): activation: beginning transaction (timeout in 45 seconds)
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7414] dhcp4 
(enxd89ef3f04d55): request timed out
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7416] dhcp4 
(enxd89ef3f04d55): state changed unknown -> timeout
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7418] device 
(enxd89ef3f04d55): state change: ip-config -> failed (reason 
'ip-config-unavailable', sys-iface-state: 'managed')
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7466] device 
(enxd89ef3f04d55): Activation: failed for connection 'Port Replicator'
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7474] device 
(enxd89ef3f04d55): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7700] dhcp4 
(enxd89ef3f04d55): canceled DHCP transaction
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7700] dhcp4 
(enxd89ef3f04d55): state changed timeout -> done
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7753] policy: 
auto-activating connection 'Port Replicator' 
(e1c0084e-2246-3a09-81c2-9916d22812f8)
  Sep 01 10:42:28 mia NetworkManager[3198]:

[Touch-packages] [Bug 1900481] Re: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card

2020-10-19 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect
  card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Following upgrade to 20.04, I have no audio.  My output device is
  "Dummy Output".  I chose one audio device to report against: none are
  detected.  All this may be obvious from the auto-detected diagnostics.
  It was working in 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Oct 19 19:43:52 2020
  InstallationDate: Installed on 2018-05-05 (897 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180505)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel MID
  Symptom_Jack: Mic, Top
  Title: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 030DMJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn030DMJ:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Vostro 3300
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1900481] [NEW] [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card

You have been subscribed to a public bug:

Following upgrade to 20.04, I have no audio.  My output device is "Dummy
Output".  I chose one audio device to report against: none are detected.
All this may be obvious from the auto-detected diagnostics.  It was
working in 18.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.7
ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
Uname: Linux 5.4.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Mon Oct 19 19:43:52 2020
InstallationDate: Installed on 2018-05-05 (897 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180505)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel MID
Symptom_Jack: Mic, Top
Title: [Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/25/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 030DMJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A10
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A10
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3300:pvrA10:rvnDellInc.:rn030DMJ:rvrA10:cvnDellInc.:ct8:cvrA10:
dmi.product.name: Vostro 3300
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: A10
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal
-- 
[Vostro 3300, IDT 92HD81B1X5, Mic, Top] Pulseaudio fails to detect card
https://bugs.launchpad.net/bugs/1900481
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio 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 1900466] Re: Xorg freeze

2020-10-19 Thread Giuseppe Grillea

It has now worked for the last 4 hours.
Froze only once with black screen.
I had to plug it off and restart.
But now seems to work fine.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  
  Release Ubuntu 18.04

  When I type apt-cache policy pkgname 
   Unable to locate package pkgname

  Expceted to Happen: not freeze or crash

  
  What happened instead: it crashed 

  
  Graphics: ATI RV515
  Processor: Intel® Core™2 CPU T7200 @ 2.00GHz × 2
  Gnome: 3.28.1


  
  I am restoring this old Lenovo T60.
  I just installed a 512GB SSD drive
  4GB of Ram
  Intel duo 2 core T7200 64 bit processor

  Single booting: only Ubuntu is on this machine.

  It took me several installation attempts. Initially after installing
  Ubuntu I would only see a purple screen with stripes but nothing would
  come on.

  Finally I installed it and Ubuntu started. I am using the laptop to
  file this bug report.

  Now I have the issue of completely random freezes/crashes while using the 
console, or firefox or even other apps.
  Completely random.

  The cursor does not move, I open any random app and the screen goes
  black where the app window should be.

  The only way out is to reboot the machine.

  A few times I actually had to reinstall the 0S from the CD install.

  You probably will find records as I must have done this tens of times
  since last night.

  Please help me.
  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 19 09:31:34 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] 
[1002:7145] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Thinkpad T60 model 2007 [17aa:2006]
  MachineType: LENOVO 2007Z22
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=0718074d-db39-4731-aac6-36e1ece0157e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 2007Z22
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn2007Z22:pvrThinkPadT60:rvnLENOVO:rn2007Z22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T60
  dmi.product.name: 2007Z22
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

2020-10-19 Thread Giuseppe Grillea

Correction 
Package: xorg 1:7.7+19ubuntu7

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  
  Release Ubuntu 18.04

  When I type apt-cache policy pkgname 
   Unable to locate package pkgname

  Expceted to Happen: not freeze or crash

  
  What happened instead: it crashed 

  
  Graphics: ATI RV515
  Processor: Intel® Core™2 CPU T7200 @ 2.00GHz × 2
  Gnome: 3.28.1


  
  I am restoring this old Lenovo T60.
  I just installed a 512GB SSD drive
  4GB of Ram
  Intel duo 2 core T7200 64 bit processor

  Single booting: only Ubuntu is on this machine.

  It took me several installation attempts. Initially after installing
  Ubuntu I would only see a purple screen with stripes but nothing would
  come on.

  Finally I installed it and Ubuntu started. I am using the laptop to
  file this bug report.

  Now I have the issue of completely random freezes/crashes while using the 
console, or firefox or even other apps.
  Completely random.

  The cursor does not move, I open any random app and the screen goes
  black where the app window should be.

  The only way out is to reboot the machine.

  A few times I actually had to reinstall the 0S from the CD install.

  You probably will find records as I must have done this tens of times
  since last night.

  Please help me.
  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 19 09:31:34 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] 
[1002:7145] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Thinkpad T60 model 2007 [17aa:2006]
  MachineType: LENOVO 2007Z22
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=0718074d-db39-4731-aac6-36e1ece0157e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 2007Z22
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn2007Z22:pvrThinkPadT60:rvnLENOVO:rn2007Z22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T60
  dmi.product.name: 2007Z22
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

2020-10-19 Thread Timo Aaltonen

bad as in broken

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  
  Release Ubuntu 18.04

  When I type apt-cache policy pkgname 
   Unable to locate package pkgname

  Expceted to Happen: not freeze or crash

  
  What happened instead: it crashed 

  
  Graphics: ATI RV515
  Processor: Intel® Core™2 CPU T7200 @ 2.00GHz × 2
  Gnome: 3.28.1


  
  I am restoring this old Lenovo T60.
  I just installed a 512GB SSD drive
  4GB of Ram
  Intel duo 2 core T7200 64 bit processor

  Single booting: only Ubuntu is on this machine.

  It took me several installation attempts. Initially after installing
  Ubuntu I would only see a purple screen with stripes but nothing would
  come on.

  Finally I installed it and Ubuntu started. I am using the laptop to
  file this bug report.

  Now I have the issue of completely random freezes/crashes while using the 
console, or firefox or even other apps.
  Completely random.

  The cursor does not move, I open any random app and the screen goes
  black where the app window should be.

  The only way out is to reboot the machine.

  A few times I actually had to reinstall the 0S from the CD install.

  You probably will find records as I must have done this tens of times
  since last night.

  Please help me.
  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 19 09:31:34 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] 
[1002:7145] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Thinkpad T60 model 2007 [17aa:2006]
  MachineType: LENOVO 2007Z22
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=0718074d-db39-4731-aac6-36e1ece0157e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 2007Z22
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn2007Z22:pvrThinkPadT60:rvnLENOVO:rn2007Z22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T60
  dmi.product.name: 2007Z22
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

2020-10-19 Thread Timo Aaltonen

sound like you have bad hardware

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  
  Release Ubuntu 18.04

  When I type apt-cache policy pkgname 
   Unable to locate package pkgname

  Expceted to Happen: not freeze or crash

  
  What happened instead: it crashed 

  
  Graphics: ATI RV515
  Processor: Intel® Core™2 CPU T7200 @ 2.00GHz × 2
  Gnome: 3.28.1


  
  I am restoring this old Lenovo T60.
  I just installed a 512GB SSD drive
  4GB of Ram
  Intel duo 2 core T7200 64 bit processor

  Single booting: only Ubuntu is on this machine.

  It took me several installation attempts. Initially after installing
  Ubuntu I would only see a purple screen with stripes but nothing would
  come on.

  Finally I installed it and Ubuntu started. I am using the laptop to
  file this bug report.

  Now I have the issue of completely random freezes/crashes while using the 
console, or firefox or even other apps.
  Completely random.

  The cursor does not move, I open any random app and the screen goes
  black where the app window should be.

  The only way out is to reboot the machine.

  A few times I actually had to reinstall the 0S from the CD install.

  You probably will find records as I must have done this tens of times
  since last night.

  Please help me.
  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 19 09:31:34 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] 
[1002:7145] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Thinkpad T60 model 2007 [17aa:2006]
  MachineType: LENOVO 2007Z22
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=0718074d-db39-4731-aac6-36e1ece0157e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 2007Z22
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn2007Z22:pvrThinkPadT60:rvnLENOVO:rn2007Z22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T60
  dmi.product.name: 2007Z22
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1899621] Comment bridged from LTC Bugzilla

2020-10-19 Thread bugproxy

--- Comment From i...@de.ibm.com 2020-10-19 13:57 EDT---
Will 1.2.11.dfsg-2ubuntu4 ultimately go into both 20.04 and 20.10? If yes, then 
everything is OK.

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

Title:
  [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on
  z15

Status in Release Notes for Ubuntu:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  In Progress
Status in zlib source package in Groovy:
  In Progress

Bug description:
  Description:   zlib: inflateSyncPoint() returns an incorrect result on z15
  Symptom:   Certain rsync builds fail with "error in rsync protocol data
     stream" on z15.
  Problem:   inflateSyncPoint() does not take into account the hardware
     compression state and returns an incorrect result.
  Solution:  Make inflateSyncPoint() fail if the hardware compression is on.
     The hardware does not provide enough information in order to
     implement this function.

  [Impact]

   * Certain rsync builds fail with "error in rsync protocol data
  stream" on z15.

   * On ubuntu, rsync normally uses zstd or lz4. But when rsync is
  forced to use non-default zlib compression (-z flag) it uses
  inflateSyncPoint() API. This can also happen when rsync on the the
  other end doesn't support zstd & lz4.

   * inflateSyncPoint() does not take into account the hardware
  compression state and returns an incorrect result.

   * Make inflateSyncPoint() fail if the hardware compression is on. The
  hardware does not provide enough information in order to implement
  this function.

   * Above makes rsync to succeed, when zlib uses hardware compression.

  [Test Case]

  Reproduction:  z15 only: printf 1 >1 && rsync -z 1 2

  [Regression Potential]

   * inflateSyncPoint API is rarely used. Scanning codesearch, there is
  a lot of false positives due to embedded copies of zlib in all the
  things. I do see that both rsync and backuppc-rsync use it. It used
  during a safety check to ensure that algorithm is not at a sync point
  (or that cannot be determined). Nonetheless, returning error is a
  safer implementation for this API call.

  [Other Info]

   * This is a regression introduced by adding & enabling zlib hw
  acceleration by default on z15; and discovering using rsync that one
  API is implemented incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899621/+subscriptions

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

[Touch-packages] [Bug 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15

2020-10-19 Thread Frank Heimes

1.2.11.dfsg-2ubuntu4 is the latest package that incl. the patch

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

Title:
  [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on
  z15

Status in Release Notes for Ubuntu:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  In Progress
Status in zlib source package in Groovy:
  In Progress

Bug description:
  Description:   zlib: inflateSyncPoint() returns an incorrect result on z15
  Symptom:   Certain rsync builds fail with "error in rsync protocol data
     stream" on z15.
  Problem:   inflateSyncPoint() does not take into account the hardware
     compression state and returns an incorrect result.
  Solution:  Make inflateSyncPoint() fail if the hardware compression is on.
     The hardware does not provide enough information in order to
     implement this function.

  [Impact]

   * Certain rsync builds fail with "error in rsync protocol data
  stream" on z15.

   * On ubuntu, rsync normally uses zstd or lz4. But when rsync is
  forced to use non-default zlib compression (-z flag) it uses
  inflateSyncPoint() API. This can also happen when rsync on the the
  other end doesn't support zstd & lz4.

   * inflateSyncPoint() does not take into account the hardware
  compression state and returns an incorrect result.

   * Make inflateSyncPoint() fail if the hardware compression is on. The
  hardware does not provide enough information in order to implement
  this function.

   * Above makes rsync to succeed, when zlib uses hardware compression.

  [Test Case]

  Reproduction:  z15 only: printf 1 >1 && rsync -z 1 2

  [Regression Potential]

   * inflateSyncPoint API is rarely used. Scanning codesearch, there is
  a lot of false positives due to embedded copies of zlib in all the
  things. I do see that both rsync and backuppc-rsync use it. It used
  during a safety check to ensure that algorithm is not at a sync point
  (or that cannot be determined). Nonetheless, returning error is a
  safer implementation for this API call.

  [Other Info]

   * This is a regression introduced by adding & enabling zlib hw
  acceleration by default on z15; and discovering using rsync that one
  API is implemented incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899621/+subscriptions

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

[Touch-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset

2020-10-19 Thread Darin Miller

This bug is back again in Kubuntu 20.10.  Should I start a new bug?  I
can attach pactl output for both the good and bad states if it would
help.  When is issue occurs, aplay -l shows the problem device and
killing PA fixes the problem.

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

Title:
  pulseaudio doesn't detect (new) USB headset

Status in alsa-lib package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

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

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

[Touch-packages] [Bug 1900466] [NEW] Xorg freeze

2020-10-19 Thread Giuseppe Grillea

Public bug reported:


Release Ubuntu 18.04

When I type apt-cache policy pkgname 
 Unable to locate package pkgname

Expceted to Happen: not freeze or crash


What happened instead: it crashed 


Graphics: ATI RV515
Processor: Intel® Core™2 CPU T7200 @ 2.00GHz × 2
Gnome: 3.28.1


I am restoring this old Lenovo T60.
I just installed a 512GB SSD drive
4GB of Ram
Intel duo 2 core T7200 64 bit processor

Single booting: only Ubuntu is on this machine.

It took me several installation attempts. Initially after installing
Ubuntu I would only see a purple screen with stripes but nothing would
come on.

Finally I installed it and Ubuntu started. I am using the laptop to file
this bug report.

Now I have the issue of completely random freezes/crashes while using the 
console, or firefox or even other apps.
Completely random.

The cursor does not move, I open any random app and the screen goes
black where the app window should be.

The only way out is to reboot the machine.

A few times I actually had to reinstall the 0S from the CD install.

You probably will find records as I must have done this tens of times
since last night.

Please help me.
Thank you

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 19 09:31:34 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] 
[1002:7145] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Thinkpad T60 model 2007 [17aa:2006]
MachineType: LENOVO 2007Z22
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=0718074d-db39-4731-aac6-36e1ece0157e ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ETE3WW (2.23 )
dmi.board.name: 2007Z22
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn2007Z22:pvrThinkPadT60:rvnLENOVO:rn2007Z22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T60
dmi.product.name: 2007Z22
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  
  Release Ubuntu 18.04

  When I type apt-cache policy pkgname 
   Unable to locate package pkgname

  Expceted to Happen: not freeze or crash

  
  What happened instead: it crashed 

  
  Graphics: ATI RV515
  Processor: Intel® Core™2 CPU T7200 @ 2.00GHz × 2
  Gnome: 3.28.1


  
  I am restoring this old Lenovo T60.
  I just installed a 512GB SSD drive
  4GB of Ram
  Intel duo 2 core T7200 64 bit processor

  Single booting: only Ubuntu is on this machine.

  It took me several installation attempts. Initially after installing
  Ubuntu I would only see a purple screen with stripes but nothing would
  come on.

  Finally I installed it and Ubuntu started. I am using the laptop to
  file this bug report.

  Now I have the issue of completely random freezes/crashes while using the 
console, or firefox or even other apps.
  Completely random.

  The cursor does not move, I open any random app and the screen goes
  black where the app window should be.

  The only way out is to reboot the machine.

  A few times I actually had to reinstall the 0S from the CD install.

  You probably

[Touch-packages] [Bug 1900134] Re: package ubuntu-minimal 1.450.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2020-10-19 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package ubuntu-minimal 1.450.2 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  not installing samba while we typing sudo apt-get install samba

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-minimal 1.450.2
  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
  Date: Fri Oct 16 17:22:45 2020
  DuplicateSignature:
   package:ubuntu-minimal:1.450.2
   Setting up libibverbs1:amd64 (28.0-1ubuntu1) ...
   dpkg: error processing package ubuntu-minimal (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ubuntu-meta
  Title: package ubuntu-minimal 1.450.2 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1900134] Re: package ubuntu-minimal 1.450.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2020-10-19 Thread Eduardo Barretto

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package ubuntu-minimal 1.450.2 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  not installing samba while we typing sudo apt-get install samba

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-minimal 1.450.2
  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
  Date: Fri Oct 16 17:22:45 2020
  DuplicateSignature:
   package:ubuntu-minimal:1.450.2
   Setting up libibverbs1:amd64 (28.0-1ubuntu1) ...
   dpkg: error processing package ubuntu-minimal (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ubuntu-meta
  Title: package ubuntu-minimal 1.450.2 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

** Description changed:

- The Ubuntu Error Tracker has been receiving reports about a problem
- regarding apport.  This problem was most recently seen with package
- version 2.20.11-0ubuntu27.10, the problem page at
- https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e
- contains more details, including versions of packages affected,
- stacktrace or traceback, and individual crash reports.
+ Impact
+ --
+ apport is crashing for some users when a crash file is created about an 
executable which has been deleted.
+ 
+ Test Case
+ -
+ While you won't get a Traceback (because there is a location for apport to 
print its usages message) with the following test case you will see apport 
usage printed:
+ 
+  $ PYTHONPATH=/home/bdmurray/source-trees/apport/trunk data/apport '8219' 
'11' '0' '1' '8219' '!usr!bin!yes' '(deleted)'
+ usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d 
DUMP_MODE] [-P [GLOBAL_PID]]
+ 
+ With the fixed version of apport you'll see no such usage message.
+ 
+ Regression Potential
+ 
+ Because new code is being added its possible that the python syntax could be 
bad which would result in another crash, so careful review the code.
+ 
+ Original Description
+ 
+ The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu27.10, the problem page at 
https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  
  Traceback (most recent call last):
    File "/usr/share/apport/apport", line 451, in 
  options = parse_arguments()
    File "/usr/share/apport/apport", line 396, in parse_arguments
  parser.print_usage()
    File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
  self._print_message(self.format_usage(), file)
    File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message
  file.write(message)
  AttributeError: 'NoneType' object has no attribute 'write'
  
  After working on https://bugs.launchpad.net/apport/+bug/1732962, the error 
tracker started throwing the error above.
  it appears that print_usage is called and throwing an error because in this 
context (called with core_pattern) apport doesn't have an stdout or stderr. 
after looking at traces it seems the kernel is adding 'deleted' to the name of 
the process which cause argument parsing to fail.
  
  The fix below from bdmurray seems to fix it.
  https://paste.ubuntu.com/p/pVKNP9kWP4/
  
  There is report of this issue in Focal, Bionic and 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/1899195

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  In Progress
Status in apport source package in Bionic:
  In Progress
Status in apport source package in Focal:
  In Progress

Bug description:
  Impact
  --
  apport is crashing for some users when a crash file is created about an 
executable which has been deleted.

  Test Case
  -
  While you won't get a Traceback (because there is a location for apport to 
print its usages message) with the following test case you will see apport 
usage printed:

   $ PYTHONPATH=/home/bdmurray/source-trees/apport/trunk data/apport '8219' 
'11' '0' '1' '8219' '!usr!bin!yes' '(deleted)'
  usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d 
DUMP_MODE] [-P [GLOBAL_PID]]

  With the fixed version of apport you'll see no such usage message.

  Regression Potential
  
  Because new code is being added its possible that the python syntax could be 
bad which would result in another crash, so careful review the code.

  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu27.10, the problem page at 
https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.

  Traceback (most recent call last):
    File "/usr/share/apport/apport", line 451, in 
  options = parse_arguments()
    File "/usr/share/apport/apport", line 396, in parse_arguments
  parser.print_usage()
    File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
  self._print_message(self.format_usage(), file)
    File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message
  file.write(message)
  AttributeError: 'NoneType' object

[Touch-packages] [Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

** Changed in: apport (Ubuntu Focal)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: apport (Ubuntu Bionic)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: apport (Ubuntu Focal)
   Status: Triaged => In Progress

** Changed in: apport (Ubuntu Bionic)
   Status: Triaged => In Progress

** Changed in: apport (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: apport (Ubuntu Xenial)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  In Progress
Status in apport source package in Bionic:
  In Progress
Status in apport source package in Focal:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with package
  version 2.20.11-0ubuntu27.10, the problem page at
  https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e
  contains more details, including versions of packages affected,
  stacktrace or traceback, and individual crash reports.

  Traceback (most recent call last):
    File "/usr/share/apport/apport", line 451, in 
  options = parse_arguments()
    File "/usr/share/apport/apport", line 396, in parse_arguments
  parser.print_usage()
    File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage
  self._print_message(self.format_usage(), file)
    File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message
  file.write(message)
  AttributeError: 'NoneType' object has no attribute 'write'

  After working on https://bugs.launchpad.net/apport/+bug/1732962, the error 
tracker started throwing the error above.
  it appears that print_usage is called and throwing an error because in this 
context (called with core_pattern) apport doesn't have an stdout or stderr. 
after looking at traces it seems the kernel is adding 'deleted' to the name of 
the process which cause argument parsing to fail.

  The fix below from bdmurray seems to fix it.
  https://paste.ubuntu.com/p/pVKNP9kWP4/

  There is report of this issue in Focal, Bionic and xenial

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

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

[Touch-packages] [Bug 1899621] Comment bridged from LTC Bugzilla

2020-10-19 Thread bugproxy

--- Comment From i...@de.ibm.com 2020-10-19 11:38 EDT---
zlib1g_1.2.11.dfsg-2ubuntu4_s390x.deb passes all of my tests.

1:1.2.11.dfsg-2ubuntu1.1 though looks old (Thu, 20 Aug 2020) - am I
missing something?

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

Title:
  [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on
  z15

Status in Release Notes for Ubuntu:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  In Progress
Status in zlib source package in Groovy:
  In Progress

Bug description:
  Description:   zlib: inflateSyncPoint() returns an incorrect result on z15
  Symptom:   Certain rsync builds fail with "error in rsync protocol data
     stream" on z15.
  Problem:   inflateSyncPoint() does not take into account the hardware
     compression state and returns an incorrect result.
  Solution:  Make inflateSyncPoint() fail if the hardware compression is on.
     The hardware does not provide enough information in order to
     implement this function.

  [Impact]

   * Certain rsync builds fail with "error in rsync protocol data
  stream" on z15.

   * On ubuntu, rsync normally uses zstd or lz4. But when rsync is
  forced to use non-default zlib compression (-z flag) it uses
  inflateSyncPoint() API. This can also happen when rsync on the the
  other end doesn't support zstd & lz4.

   * inflateSyncPoint() does not take into account the hardware
  compression state and returns an incorrect result.

   * Make inflateSyncPoint() fail if the hardware compression is on. The
  hardware does not provide enough information in order to implement
  this function.

   * Above makes rsync to succeed, when zlib uses hardware compression.

  [Test Case]

  Reproduction:  z15 only: printf 1 >1 && rsync -z 1 2

  [Regression Potential]

   * inflateSyncPoint API is rarely used. Scanning codesearch, there is
  a lot of false positives due to embedded copies of zlib in all the
  things. I do see that both rsync and backuppc-rsync use it. It used
  during a safety check to ensure that algorithm is not at a sync point
  (or that cannot be determined). Nonetheless, returning error is a
  safer implementation for this API call.

  [Other Info]

   * This is a regression introduced by adding & enabling zlib hw
  acceleration by default on z15; and discovering using rsync that one
  API is implemented incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899621/+subscriptions

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

[Touch-packages] [Bug 1893798] Re: Wired interface fails after random uptime and then cannot bring back up

2020-10-19 Thread Joseph Borg

Done some more digging into this and I have a feeling it's to do with
IPv6.  The interface gets several IPv6 addresses assigned (not sure if
this is an issue).  If I turn off IPv6 support, for this interface, in
the Gnome Settings window, the interface recovers and stays up.

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

Title:
  Wired interface fails after random uptime and then cannot bring back
  up

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm on 20.04, on a Dell XPS 9730.  Upon boot, the wired connection
  comes up fine but, after a seemingly random time, the interface fails.
  If I watch the NetworkManager journal and try and switch the interface
  off and then back on in Gnome Control Panel, the interface keeps
  timing out:

  
  Sep 01 10:40:58 mia NetworkManager[3198]:   [1598971258.0049] device 
(enxd89ef3f04d55): Activation: starting connection 'Port Replicator' 
(e1c0084e-2246-3a09-81c2-9916d22812f8)
  Sep 01 10:40:58 mia NetworkManager[3198]:   [1598971258.0054] audit: 
op="connection-activate" uuid="e1c0084e-2246-3a09-81c2-9916d22812f8" name="Port 
Replicator" pid=6219 uid=1000 result="success"
  Sep 01 10:40:58 mia NetworkManager[3198]:   [1598971258.0060] device 
(enxd89ef3f04d55): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:40:58 mia NetworkManager[3198]:   [1598971258.0082] device 
(enxd89ef3f04d55): state change: prepare -> config (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:40:58 mia NetworkManager[3198]:   [1598971258.0114] device 
(enxd89ef3f04d55): state change: config -> ip-config (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:40:58 mia NetworkManager[3198]:   [1598971258.0130] dhcp4 
(enxd89ef3f04d55): activation: beginning transaction (timeout in 45 seconds)
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7420] dhcp4 
(enxd89ef3f04d55): request timed out
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7420] dhcp4 
(enxd89ef3f04d55): state changed unknown -> timeout
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7421] device 
(enxd89ef3f04d55): state change: ip-config -> failed (reason 
'ip-config-unavailable', sys-iface-state: 'managed')
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7433] device 
(enxd89ef3f04d55): Activation: failed for connection 'Port Replicator'
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7436] device 
(enxd89ef3f04d55): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7820] dhcp4 
(enxd89ef3f04d55): canceled DHCP transaction
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7821] dhcp4 
(enxd89ef3f04d55): state changed timeout -> done
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7894] policy: 
auto-activating connection 'Port Replicator' 
(e1c0084e-2246-3a09-81c2-9916d22812f8)
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7906] device 
(enxd89ef3f04d55): Activation: starting connection 'Port Replicator' 
(e1c0084e-2246-3a09-81c2-9916d22812f8)
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7907] device 
(enxd89ef3f04d55): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7912] device 
(enxd89ef3f04d55): state change: prepare -> config (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7917] device 
(enxd89ef3f04d55): state change: config -> ip-config (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:41:43 mia NetworkManager[3198]:   [1598971303.7920] dhcp4 
(enxd89ef3f04d55): activation: beginning transaction (timeout in 45 seconds)
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7414] dhcp4 
(enxd89ef3f04d55): request timed out
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7416] dhcp4 
(enxd89ef3f04d55): state changed unknown -> timeout
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7418] device 
(enxd89ef3f04d55): state change: ip-config -> failed (reason 
'ip-config-unavailable', sys-iface-state: 'managed')
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7466] device 
(enxd89ef3f04d55): Activation: failed for connection 'Port Replicator'
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7474] device 
(enxd89ef3f04d55): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7700] dhcp4 
(enxd89ef3f04d55): canceled DHCP transaction
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7700] dhcp4 
(enxd89ef3f04d55): state changed timeout -> done
  Sep 01 10:42:28 mia NetworkManager[3198]:   [1598971348.7753] policy: 
auto-activating connection

[Touch-packages] [Bug 1900288] Re: package bluez 5.48-0ubuntu3.4 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

2020-10-19 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package bluez 5.48-0ubuntu3.4 failed to install/upgrade: installed
  bluez package post-installation script subprocess returned error exit
  status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  i am not sure about the error . I am a newbie !

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.4
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  Date: Sat Oct 17 13:18:02 2020
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-10-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=df534ee1-f125-4822-a2d1-8898bc6ee8ce ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12ubuntu0.1
  SourcePackage: bluez
  Title: package bluez 5.48-0ubuntu3.4 failed to install/upgrade: installed 
bluez package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 MAX (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd04/20/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2MAX(MS-7B84):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 11:11:11:11:11:11  ACL MTU: 940:4  SCO MTU: 48:10
UP RUNNING PSCAN ISCAN 
RX bytes:119303 acl:61 sco:1816 events:1828 errors:0
TX bytes:734416 acl:1404 sco:1667 commands:190 errors:0

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

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

[Touch-packages] [Bug 1900288] Re: package bluez 5.48-0ubuntu3.4 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

2020-10-19 Thread Eduardo Barretto

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package bluez 5.48-0ubuntu3.4 failed to install/upgrade: installed
  bluez package post-installation script subprocess returned error exit
  status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  i am not sure about the error . I am a newbie !

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.4
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  Date: Sat Oct 17 13:18:02 2020
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-10-16 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. MS-7B84
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=df534ee1-f125-4822-a2d1-8898bc6ee8ce ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12ubuntu0.1
  SourcePackage: bluez
  Title: package bluez 5.48-0ubuntu3.4 failed to install/upgrade: installed 
bluez package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-M2 MAX (MS-7B84)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd04/20/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-M2MAX(MS-7B84):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B84
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 11:11:11:11:11:11  ACL MTU: 940:4  SCO MTU: 48:10
UP RUNNING PSCAN ISCAN 
RX bytes:119303 acl:61 sco:1816 events:1828 errors:0
TX bytes:734416 acl:1404 sco:1667 commands:190 errors:0

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

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

[Touch-packages] [Bug 1899852] Re: Cannot assign requested address: AH00072: make_sock: could not bind to address

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it
helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

Title:
   Cannot assign requested address: AH00072: make_sock: could not bind
  to address

Status in apache2 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hello,

  Let's first list my configuration items:
  * apache2 2.4.29-1ubuntu4.14
  * release: Ubuntu 18.04.5 LTS

  Upon reboot, the following message is seen in apache2.service logs:

  -- Unit apache2.service has begun starting up.
  Oct 14 12:18:32 SERVER apachectl[3833]: (99)Cannot assign requested address: 
AH00072: make_sock: could not bind to address [REDACTED IPV6.33]:443
  Oct 14 12:18:32 SERVER apachectl[3833]: no listening sockets available, 
shutting down
  Oct 14 12:18:32 SERVER apachectl[3833]: AH00015: Unable to open logs
  Oct 14 12:18:32 SERVER apachectl[3833]: Action 'start' failed.
  Oct 14 12:18:32 SERVER apachectl[3833]: The Apache error log may have more 
information.
  Oct 14 12:18:33 SERVER systemd[1]: apache2.service: Control process exited, 
code=exited status=1
  Oct 14 12:18:33 SERVER systemd[1]: apache2.service: Failed with result 
'exit-code'.
  Oct 14 12:18:33 SERVER systemd[1]: Failed to start The Apache HTTP Server.

  The apache2 configuration is using the ipv4 and ipv6 present on the server:
  /etc/apache2/ports.conf:Listen :443
  /etc/apache2/ports.conf:Listen :443
  /etc/apache2/ports.conf:Listen [REDACTED IPV6::33]:443
  /etc/apache2/ports.conf:Listen [REDACTED IPV6::35]:443

  and the /etc/network/interfaces looks like this (no netplan):
  # Additional IPs that are used to serve https traffic for
  # releases.ubuntu.com so that archive doesn't respond on 443.
  auto bond0:1
  iface bond0:1 inet static
  address .247/32
  # Using up/down to avoid LP:1347246.
  up /sbin/ip addr add REDACTED IPV6::33/128 dev $IFACE preferred_lft 0
  down /bin/ip addr del REDACTED IPV6::33/128 dev $IFACE preferred_lft 0

  # Additional IPs that are used to serve *.clouds.archive.ubuntu.com
  # with HTTPProtocolOptions unsafe, which is needed to work around
  # cloud-init bug LP:1868232 (cRT#125271).
  auto bond0:2
  iface bond0:2 inet static
  address .245/32
  # Using up/down to avoid LP:1347246.
  up /sbin/ip addr add REDACTED IPV6::35/128 dev $IFACE preferred_lft 0
  down /bin/ip addr del REDACTED IPV6::35/128 dev $IFACE preferred_lft 0

  I was surprised that the apache2.service does not contain a
  After=network-online.target

  $ systemctl show apache2.service | grep -E '(Wants|Require|After|Before)'
  RemainAfterExit=no
  Requires=system.slice sysinit.target -.mount
  Before=multi-user.target shutdown.target
  After=basic.target sysinit.target systemd-journald.socket system.slice 
network.target nss-lookup.target systemd-tmpfiles-setup.service 
remote-fs.target -.mount
  RequiresMountsFor=/var/tmp /tmp

  $ systemctl show network.target | grep "^After"
  After=network-pre.target ifup@bond0.service ifup@ens2f0.service 
ifup@ens2f1.service systemd-resolved.service ufw.service networking.service 
systemd-networkd.service

  So I was wondering if the "ifup@bond0" was enough as a dependency
  here, to be sure to have the ipv6 up and running or if we would need
  something like "ifup@bond0:2" and "ifup@bond0:1" as part of the list
  of the services in the network.target "After" list.

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

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

[Touch-packages] [Bug 1899852] Re: Cannot assign requested address: AH00072: make_sock: could not bind to address

Now to your actual question of "how to order after a given bond interface", 
that is actually a systemd-networkd/systemd question (reminder question, not a 
bug - so not a bug report actually).

I'll add bug tasks but think they are incomplete as that is a
config/consulting question more than anything else.

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

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

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

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

Title:
   Cannot assign requested address: AH00072: make_sock: could not bind
  to address

Status in apache2 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hello,

  Let's first list my configuration items:
  * apache2 2.4.29-1ubuntu4.14
  * release: Ubuntu 18.04.5 LTS

  Upon reboot, the following message is seen in apache2.service logs:

  -- Unit apache2.service has begun starting up.
  Oct 14 12:18:32 SERVER apachectl[3833]: (99)Cannot assign requested address: 
AH00072: make_sock: could not bind to address [REDACTED IPV6.33]:443
  Oct 14 12:18:32 SERVER apachectl[3833]: no listening sockets available, 
shutting down
  Oct 14 12:18:32 SERVER apachectl[3833]: AH00015: Unable to open logs
  Oct 14 12:18:32 SERVER apachectl[3833]: Action 'start' failed.
  Oct 14 12:18:32 SERVER apachectl[3833]: The Apache error log may have more 
information.
  Oct 14 12:18:33 SERVER systemd[1]: apache2.service: Control process exited, 
code=exited status=1
  Oct 14 12:18:33 SERVER systemd[1]: apache2.service: Failed with result 
'exit-code'.
  Oct 14 12:18:33 SERVER systemd[1]: Failed to start The Apache HTTP Server.

  The apache2 configuration is using the ipv4 and ipv6 present on the server:
  /etc/apache2/ports.conf:Listen :443
  /etc/apache2/ports.conf:Listen :443
  /etc/apache2/ports.conf:Listen [REDACTED IPV6::33]:443
  /etc/apache2/ports.conf:Listen [REDACTED IPV6::35]:443

  and the /etc/network/interfaces looks like this (no netplan):
  # Additional IPs that are used to serve https traffic for
  # releases.ubuntu.com so that archive doesn't respond on 443.
  auto bond0:1
  iface bond0:1 inet static
  address .247/32
  # Using up/down to avoid LP:1347246.
  up /sbin/ip addr add REDACTED IPV6::33/128 dev $IFACE preferred_lft 0
  down /bin/ip addr del REDACTED IPV6::33/128 dev $IFACE preferred_lft 0

  # Additional IPs that are used to serve *.clouds.archive.ubuntu.com
  # with HTTPProtocolOptions unsafe, which is needed to work around
  # cloud-init bug LP:1868232 (cRT#125271).
  auto bond0:2
  iface bond0:2 inet static
  address .245/32
  # Using up/down to avoid LP:1347246.
  up /sbin/ip addr add REDACTED IPV6::35/128 dev $IFACE preferred_lft 0
  down /bin/ip addr del REDACTED IPV6::35/128 dev $IFACE preferred_lft 0

  I was surprised that the apache2.service does not contain a
  After=network-online.target

  $ systemctl show apache2.service | grep -E '(Wants|Require|After|Before)'
  RemainAfterExit=no
  Requires=system.slice sysinit.target -.mount
  Before=multi-user.target shutdown.target
  After=basic.target sysinit.target systemd-journald.socket system.slice 
network.target nss-lookup.target systemd-tmpfiles-setup.service 
remote-fs.target -.mount
  RequiresMountsFor=/var/tmp /tmp

  $ systemctl show network.target | grep "^After"
  After=network-pre.target ifup@bond0.service ifup@ens2f0.service 
ifup@ens2f1.service systemd-resolved.service ufw.service networking.service 
systemd-networkd.service

  So I was wondering if the "ifup@bond0" was enough as a dependency
  here, to be sure to have the ipv6 up and running or if we would need
  something like "ifup@bond0:2" and "ifup@bond0:1" as part of the list
  of the services in the network.target "After" list.

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

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

[Touch-packages] [Bug 1900436] Re: new upstream release 2020b

** Summary changed:

- new upstream release 2020c
+ new upstream release 2020b

** Description changed:

- There is a new upstream release of tzdata, 2020c, which includes the
+ There is a new upstream release of tzdata, 2020b, which includes the
  following:
  
-   * New upstream release, affecting past and future timestamps:
- - Fiji starts DST on 2020-12-20.
- - Canada's Yukon changes to -07 on 2020-11-01.
- - Casey, Antarctica is at +08 in winter and +11 in summer.
- - Correct several transitions for Hungary for 1918/1983.
+   * New upstream release, affecting past and future timestamps:
+ - Canada's Yukon changes to -07 on 2020-11-01.
+ - Casey, Antarctica is at +08 in winter and +11 in summer.
+ - Correct several transitions for Hungary for 1918/1983.
  
  Verification is done with 'zdump'. The first timezone that gets changed
  in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This
  is compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

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

Title:
  new upstream release 2020b

Status in tzdata package in Ubuntu:
  In Progress

Bug description:
  There is a new upstream release of tzdata, 2020b, which includes the
  following:

    * New upstream release, affecting past and future timestamps:
  - Canada's Yukon changes to -07 on 2020-11-01.
  - Casey, Antarctica is at +08 in winter and +11 in summer.
  - Correct several transitions for Hungary for 1918/1983.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

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

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

[Touch-packages] [Bug 1900008] Re: Sessions of screen does not keep running in background

Thanks Axel,
I think I didn't closed a terminal windows with anything other but CTRL+D for 
years (which is an implicit call to exit), but you are absolutely right. It 
could be "click on the X on the window decoration to close the terminal".
Thanks for making me see that ... :-)

@Gustavo - never the less please speak up what exactly is-done/happens
in your case as we are still making assumptions.

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

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

Title:
  Sessions of screen does not keep running in background

Status in screen package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In a new fresh installed 20.04, when I use screen command and close
  the terminal (not closing screen sesion), then I can't recover it with
  screen -x, since does not exist. I can only recover screen sesion if
  the original terminal running screen is not being closed.

  For some reason, this is closing screen session of that user:

  Oct 15 13:32:45 pc-caja2 systemd[1]: session-66.scope: Succeeded.
  Oct 15 13:32:45 pc-caja2 systemd[1]: Stopped Session 66 of user usuario.

  This does not happen in an upgraded system from 18.04 to 20.04.

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

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

[Touch-packages] [Bug 1900436] Re: new upstream release 2020c

** Changed in: tzdata (Ubuntu)
   Status: New => In Progress

** Changed in: tzdata (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  new upstream release 2020c

Status in tzdata package in Ubuntu:
  In Progress

Bug description:
  There is a new upstream release of tzdata, 2020c, which includes the
  following:

* New upstream release, affecting past and future timestamps:
  - Fiji starts DST on 2020-12-20.
  - Canada's Yukon changes to -07 on 2020-11-01.
  - Casey, Antarctica is at +08 in winter and +11 in summer.
  - Correct several transitions for Hungary for 1918/1983.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

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

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

[Touch-packages] [Bug 1900436] [NEW] new upstream release 2020c

Public bug reported:

There is a new upstream release of tzdata, 2020c, which includes the
following:

  * New upstream release, affecting past and future timestamps:
- Fiji starts DST on 2020-12-20.
- Canada's Yukon changes to -07 on 2020-11-01.
- Casey, Antarctica is at +08 in winter and +11 in summer.
- Correct several transitions for Hungary for 1918/1983.

Verification is done with 'zdump'. The first timezone that gets changed
in the updated package is dumped with "zdump -v
$region/$timezone_that_changed" (this needed to be greped for in
/usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This
is compared to the same output after the updated package got installed.
If those are different the verification is considered done.

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

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

Title:
  new upstream release 2020c

Status in tzdata package in Ubuntu:
  New

Bug description:
  There is a new upstream release of tzdata, 2020c, which includes the
  following:

* New upstream release, affecting past and future timestamps:
  - Fiji starts DST on 2020-12-20.
  - Canada's Yukon changes to -07 on 2020-11-01.
  - Casey, Antarctica is at +08 in winter and +11 in summer.
  - Correct several transitions for Hungary for 1918/1983.

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with "zdump -v
  $region/$timezone_that_changed" (this needed to be greped for in
  /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".]
  This is compared to the same output after the updated package got
  installed. If those are different the verification is considered done.

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

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

[Touch-packages] [Bug 1900135] Re: Bluetooth headsets are not working HSP/HFP mode

2020-10-19 Thread Rory Powell

@vanvugt I see:

Switch from HSP/HSF -> A2DP:

Oct 19 13:05:28 rpowell-pc rtkit-daemon[1007]: Supervising 1 threads of 1 
processes of 1 users.
Oct 19 13:05:28 rpowell-pc rtkit-daemon[1007]: Successfully made thread 8627 of 
process 982 owned by '1000' RT at priority 5.
Oct 19 13:05:28 rpowell-pc rtkit-daemon[1007]: Supervising 2 threads of 1 
processes of 1 users.
Oct 19 13:05:28 rpowell-pc gsd-media-keys[2212]: Unable to get default sink
Oct 19 13:05:28 rpowell-pc gsd-media-keys[2212]: Unable to get default source

Switch from A2DP to HSP/HSF:

Oct 19 13:05:39 rpowell-pc rtkit-daemon[1007]: Supervising 1 threads of 1 
processes of 1 users.
Oct 19 13:05:39 rpowell-pc rtkit-daemon[1007]: Successfully made thread 8631 of 
process 982 owned by '1000' RT at priority 5.
Oct 19 13:05:39 rpowell-pc rtkit-daemon[1007]: Supervising 2 threads of 1 
processes of 1 users.
Oct 19 13:05:39 rpowell-pc gsd-media-keys[2212]: Unable to get default sink

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

Title:
  Bluetooth headsets are not working HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sony WH-1000XM2 and Taotronics SoundLiberty 53 are both not working in
  headset mode, but do in A2DP mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  marc   2635 F pulseaudio
   /dev/snd/controlC0:  marc   2635 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 16 13:06:42 2020
  InstallationDate: Installed on 2020-06-13 (124 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.07.23
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P7xxTM1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.07.23:bd04/09/2019:svnNotebook:pnP7xxTM1:pvrNotApplicable:rvnNotebook:rnP7xxTM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P7xxTM1
  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/bluez/+bug/1900135/+subscriptions

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

[Touch-packages] [Bug 1870260] Re: initramfs unpacking failed: Decoding failed", message appears on boot up.

2020-10-19 Thread Digital Learner

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

I have a new PC - Windows 10 dual boot with POP_OS!. Sadly I was not
enamoured with PopOS and its offering so having used a mac for years for
Web Development (Ruby) I decided to make a switch to Linux (not having
used it for some 5-10 years).

I downloaded the 20.04 Fossa image, flashed a USB drive (that had been
previously used for Pop_OS!), and went into machine bios to start the
installation process.

Sadly I get this error [0.313120] Initramfs unpacking failed: Decoding
failed.

I have zero ideas as to how to follow the instructions on here about
fixing the image when I am on a totally different OS, and this is meant
to be a clean install.

I don't even get to the live CD options to try this.

Have I done something wrong in downloading this?

I can see there are some bugs registered for this, but it seems no fix
yet in the iso images that are downloaded.

I'm reasonably technical, so happy to try things.

I don't really want to go through the pain of an upgrade by installing
an older version of Ubuntu or Mint. Nor do I really want to move to
Fedora.

I did try all of these out in VM's before deciding to go with Ubuntu,
following my not so great experience with Pop_OS!

Any help as to how to fix during install from USB-Stick booted is
appreciated

Thanks

MDL

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

Title:
  initramfs unpacking failed: Decoding failed", message appears on boot
  up.

Status in linux package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  OS : Ubuntu 20.04(20200401)

  Problem: "initramfs unpacking failed: Decoding failed", message
  appears on boot up

  solution: 
If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to 
COMPRESS=gzip 
  then the error is fixing .

  Expected solution:
  This but in there from a long time I have seen this from 
Ubuntu 18.04,19.04,19.10
  now in 20.04 So please fix it or change it from lz4 to gzip.
  an early reply is highly appreciated 
  Thank you .
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tamal  1451 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD 
Camera
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15-da0xxx
  Package: ubuntu-meta
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=29f895bf-ab7b-4df8-8e9a-c277376a2685 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84A6
  dmi.board.vendor: HP
  dmi.board.version: 80.43
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd11/29/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-da0xxx
  dmi.product.sku: 5AY34PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1900414] [NEW] sudo[5580]: root : problem with defaults entries ; TTY=unknown ; PWD=/root ; USER=navycat ;

2020-10-19 Thread navycat

Public bug reported:

sudo[5580]: root : problem with defaults entries ; TTY=unknown ; PWD=/root 
; USER=navycat ;
sudo[11487]:  navycat : problem with defaults entries ; TTY=pts/0 ; 
PWD=/home/navycat ; USER=root ;

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: sudo 1.9.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
Uname: Linux 5.8.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Oct 19 13:03:37 2020
InstallationDate: Installed on 2020-10-07 (11 days ago)
InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
SourcePackage: sudo
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy

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

Title:
  sudo[5580]: root : problem with defaults entries ; TTY=unknown ;
  PWD=/root ; USER=navycat ;

Status in sudo package in Ubuntu:
  New

Bug description:
  sudo[5580]: root : problem with defaults entries ; TTY=unknown ; 
PWD=/root ; USER=navycat ;
  sudo[11487]:  navycat : problem with defaults entries ; TTY=pts/0 ; 
PWD=/home/navycat ; USER=root ;

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: sudo 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 13:03:37 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1900098] Re: software-properties-gtk fails to open with error

Thank you for your bug report. Could you add your journalctl log from a session 
where you had the issue? ('journalctl -b ' get you the log from 'n' system 
restart ago)
Did the command install packages that were missing? If so do you have any idea 
where those were not installed?

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

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

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

Title:
  software-properties-gtk fails to open with error

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  When trying to open software-properties-gtk  via Terminal (via GUI:
  “Settings & Livepatch”) the following error is returned in the
  terminal and software-properties-gtk does not open.

  ERROR:dbus.proxies:Introspect error on :1.121:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 211, in __init__
  self.backend.Reload();
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
  return self._proxy_method(*args, **keywords)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
  return self._connection.call_blocking(self._named_service,
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in 
call_blocking
  reply_message = self.send_message_with_reply_and_block(
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name :1.121 was not provided by any .service files

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.9.2
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 16 08:17:15 2020
  InstallationDate: Installed on 2020-10-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1900098/+subscriptions

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

[Touch-packages] [Bug 1891987] Re: epson stylus photo rx560 is detected, added, but when printing, task is ending up immediatelly with success

2020-10-19 Thread Till Kamppeter

I think best is that you go through all applicable parts of

https://wiki.ubuntu.com/DebuggingPrintingProblems

Especially I need

- How is your printer connected (USB, network)
- All info about the healthiness of the connection (see the USB and network 
connection sections)
- The PPD file(s) of your print queues (in /etc/cups/ppd/)
- Thew CUPS error_log (in debug mode) from an execution of a print job
- Input files you tried to print without success

The output of the command

driverless

(to see whether there are alternative approaches to use the printer)

Please attach all logs, files, ... one by one, do not compress them and
do not package them together (so one can navigate through everything of
the bug report inside the browser).

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

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

Title:
  epson stylus photo rx560 is detected, added, but when printing, task
  is ending up immediatelly with success

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Tried with both manufacturer and gutenprint driver:

  1. plug an epson stylus photo rx560 via usb
  2. add the driver (manufacturer first, retried with gutenprint) autodetected 
our gtk ubuntu specific application.
  3. Tried to print with multiple apps: the task is queued and then immediately 
terminated with success. Nothing is printed.

  
  $ lsmod | grep usb
  usb_storage77824  1 uas
  usblp  24576  0
  btusb  57344  0
  btrtl  24576  1 btusb
  btbcm  16384  1 btusb
  btintel24576  1 btusb
  bluetooth 581632  31 btrtl,btintel,btbcm,bnep,btusb,rfcomm
  usbhid 57344  0
  hid   131072  2 usbhid,hid_generic

  Logs when adding the printer:
  $ tail -f /var/log/syslog 
  Aug 18 09:36:00 casanier kernel: [ 2570.342143] usb 1-1: new high-speed USB 
device number 10 using xhci_hcd
  Aug 18 09:36:00 casanier kernel: [ 2570.501144] usb 1-1: New USB device 
found, idVendor=04b8, idProduct=0827, bcdDevice= 1.00
  Aug 18 09:36:00 casanier kernel: [ 2570.501150] usb 1-1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Aug 18 09:36:00 casanier kernel: [ 2570.501154] usb 1-1: Product: USB2.0 
MFP(Hi-Speed)
  Aug 18 09:36:00 casanier kernel: [ 2570.501157] usb 1-1: Manufacturer: EPSON
  Aug 18 09:36:00 casanier kernel: [ 2570.501159] usb 1-1: SerialNumber: 
LH1010609180813040
  Aug 18 09:36:00 casanier kernel: [ 2570.514421] usblp 1-1:1.1: usblp0: USB 
Bidirectional printer dev 10 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0827
  Aug 18 09:36:00 casanier kernel: [ 2570.516384] usb-storage 1-1:1.2: USB Mass 
Storage device detected
  Aug 18 09:36:00 casanier kernel: [ 2570.516676] scsi host5: usb-storage 
1-1:1.2
  Aug 18 09:36:00 casanier systemd[1]: Started Configure Plugged-In Printer.
  Aug 18 09:36:00 casanier udev-configure-printer: add usb-001-010
  Aug 18 09:36:00 casanier udev-configure-printer: device devpath is 
/devices/pci:00/:00:14.0/usb1/1-1
  Aug 18 09:36:00 casanier udev-configure-printer: Device already handled
  Aug 18 09:36:00 casanier systemd[1]: configure-printer@usb-001-010.service: 
Main process exited, code=exited, status=1/FAILURE
  Aug 18 09:36:00 casanier systemd[1]: configure-printer@usb-001-010.service: 
Failed with result 'exit-code'.
  Aug 18 09:36:01 casanier kernel: [ 2571.538832] scsi 5:0:0:0: Direct-Access   
  EPSONStylus Storage   1.00 PQ: 0 ANSI: 2
  Aug 18 09:36:01 casanier kernel: [ 2571.539702] sd 5:0:0:0: Attached scsi 
generic sg0 type 0
  Aug 18 09:36:01 casanier kernel: [ 2571.545241] sd 5:0:0:0: Power-on or 
device reset occurred
  Aug 18 09:36:01 casanier kernel: [ 2571.601212] sd 5:0:0:0: [sda] Attached 
SCSI removable disk
  ^C
  $ ls -l /dev/usb/lp0 
  crw-rw 1 root lp 180, 0 août  18 09:36 /dev/usb/lp0
  $ ls -l /dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 août  18 08:53 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   1 août  18 08:53 /dev/bus/usb/001/002
  crw-rw-r--  1 root root189,   2 août  18 08:53 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 août  18 08:53 /dev/bus/usb/001/004
  crw-rw  1 root plugdev 189,   4 août  18 08:53 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 août  18 08:53 /dev/bus/usb/001/006
  crw-rw-r--+ 1 root lp  189,   9 août  18 09:36 /dev/bus/usb/001/010
  crw-rw-r--  1 root root189, 128 août  18 08:53 /dev/bus/usb/002/001
  $ sudo usb_printerid /dev/usb/lp0
  GET_DEVICE_ID string:
  MFG:EPSON;CMD:ESCPL2,BDC,D4,D4PX,ESCPR1;MDL:Stylus Photo 
RX560;CLS:PRINTER;DES:EPSON Stylus Photo RX560;
  $ lpinfo -v
  file cups-brf:/
  network socket
  network lpd
  network http
  network beh
  network https
  network ipp
  direct hp
  network ipps
  direct

[Touch-packages] [Bug 1900396] Re: netstat man-page does not explain -t|--tcp, -u|--udp or -w|--raw

2020-10-19 Thread Hans Joachim Desserud

** Tags added: manpage

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

Title:
  netstat man-page does not explain -t|--tcp, -u|--udp or -w|--raw

Status in net-tools package in Ubuntu:
  New

Bug description:
  I tried looking up `netstat -tlnp` on https://explainshell.com, but
  there was no explanation for `-t`. It turns out that at least
  `-t|--tcp`, `-u|--udp` and `-w|--raw` aren't documented in the man-
  page
  (http://manpages.ubuntu.com/manpages/precise/en/man8/netstat.8.html).

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

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

[Touch-packages] [Bug 1900133] Re: PCI/no sound at all since last updating

Thank you for your bug report. What packages did you upgrade exactly?
(you can find the record in /var/log/apt

Could include the out of this command?
$ journalctl -b 0

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

Title:
  PCI/no sound at all since last updating

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  My last updating a few hours ago was quite different than usual.
  Since then, many things are not working properly on my computer :
  - my desktop is very strange (files have lost their appearance or doesn't 
appear at all)
  -there is no more sound at all : if I try to play a mp3 file or on the 
internet
  (I checked the settings of course)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 16 13:28:11 2020
  InstallationDate: Installed on 2015-07-16 (1918 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to focal on 2020-10-16 (0 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 03QA
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 300E4A/300E5A/300E7A/3430EA/3530EA
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr03QA:bd12/14/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4A/300E5A/300E7A/3430EA/3530EA:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300E4A/300E5A/300E7A/3430EA/3530EA:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: 300E4A/300E5A/300E7A/3430EA/3530EA
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Touch-packages] [Bug 1744328] Re: libfreebl3.so should be public, not in the nss subdir

FYI since comment #6 not a lot happened in Debian other than other bugs
being merged.

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

Title:
  libfreebl3.so should be public, not in the nss subdir

Status in nss package in Ubuntu:
  Fix Released
Status in nss package in Debian:
  New

Bug description:
  Hi,
  I tried to move the chrony dependency from tomcrypt to libnss to avoid 
universe dependencies.
  While doing so I found that libfreebl3 is not "normally" linkable being 
outside the normal ld paths.

  E.g. sample program
  #include 
  #include 
  #include 
  int main(int argc, char **argv) {
  NSSLOWHASH_Begin(NSSLOWHASH_NewContext(NSSLOW_Init(), HASH_AlgSHA512));
  return 0;
  }

  Build:
  gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-Wmissing-prototypes -Wall -pthread -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/nss -I/usr/include/nspr -o docheck docheck.c -lfreebl3 
-Wl,-Bsymbolic-functions -Wl,-z,relro -v -Wl,-v -L/usr/lib/x86_64-linux-gnu/nss

  Then:
  ldd docheck
  will give you
  libfreebl3.so => not found

  Obviously a link into /usr/lib/x86_64-linux-gnu/ fixes the issue but
  needs some more consideration if that is the thing we want (there
  might be a reason it is where it is).

  Note: Required to go on with the chrony MIR which is rather urgent to
  be sorted out as it has a lot of other dependencies that need to be
  adapted.

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

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

[Touch-packages] [Bug 1897965] Re: pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is valid for hw:0)

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

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

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

Title:
  pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is
  valid for hw:0)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  No sound after login.

  $ LC_ALL=C systemctl --user status pulseaudio.service
  * pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-09-30 22:46:51 EEST; 8min ago
  TriggeredBy: * pulseaudio.socket
     Main PID: 1088 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   |-1088 /usr/bin/pulseaudio --daemonize=no --log-target=journal
   `-1126 /usr/libexec/pulse/gsettings-helper

  Sep 30 22:46:51 p5q3 systemd[1080]: Starting Sound Service...
  Sep 30 22:46:51 p5q3 pulseaudio[1088]: No UCM verb is valid for hw:0
  Sep 30 22:46:51 p5q3 systemd[1080]: Started Sound Service.
  Sep 30 22:46:52 p5q3 pulseaudio[1088]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_01_00.1" 
card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes 
fixed_laten>
  Sep 30 22:47:11 p5q3 pulseaudio[1088]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': 
timed out (service_start_timeout=25000ms)

  Workaround found: 'pulseaudio -k' seems solves the problem, sound
  appears and working well, but some errors still present:

  $ LC_ALL=C systemctl --user status pulseaudio.service
  * pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-09-30 22:55:49 EEST; 7min ago
  TriggeredBy: * pulseaudio.socket
     Main PID: 12198 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   |-12198 /usr/bin/pulseaudio --daemonize=no --log-target=journal
   `-12212 /usr/libexec/pulse/gsettings-helper

  Sep 30 22:55:49 p5q3 systemd[1080]: Starting Sound Service...
  Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:1
  Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:0
  Sep 30 22:55:49 p5q3 systemd[1080]: Started Sound Service.
  Sep 30 22:56:14 p5q3 pulseaudio[12198]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  Uname: Linux 5.8.12-050812-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 1088 F pulseaudio
    eugene 1092 F pipewire-media-
   /dev/snd/controlC1:  eugene 1092 F pipewire-media-
   /dev/snd/seq:eugene 1087 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Sep 30 22:50:58 2020
  InstallationDate: Installed on 2019-04-13 (536 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-09-06 (23 days ago)
  dmi.bios.date: 06/11/2010
  dmi.bios.release: 11.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q3
  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.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897965/+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 1897965] Re: pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is valid for hw:0)

** Summary changed:

- pulseaudio: Failed to load module "module-alsa-card"
+ pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is valid 
for hw:0)

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

Title:
  pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is
  valid for hw:0)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  No sound after login.

  $ LC_ALL=C systemctl --user status pulseaudio.service
  * pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-09-30 22:46:51 EEST; 8min ago
  TriggeredBy: * pulseaudio.socket
     Main PID: 1088 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   |-1088 /usr/bin/pulseaudio --daemonize=no --log-target=journal
   `-1126 /usr/libexec/pulse/gsettings-helper

  Sep 30 22:46:51 p5q3 systemd[1080]: Starting Sound Service...
  Sep 30 22:46:51 p5q3 pulseaudio[1088]: No UCM verb is valid for hw:0
  Sep 30 22:46:51 p5q3 systemd[1080]: Started Sound Service.
  Sep 30 22:46:52 p5q3 pulseaudio[1088]: Failed to load module 
"module-alsa-card" (argument: "device_id="1" name="pci-_01_00.1" 
card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes 
fixed_laten>
  Sep 30 22:47:11 p5q3 pulseaudio[1088]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': 
timed out (service_start_timeout=25000ms)

  Workaround found: 'pulseaudio -k' seems solves the problem, sound
  appears and working well, but some errors still present:

  $ LC_ALL=C systemctl --user status pulseaudio.service
  * pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-09-30 22:55:49 EEST; 7min ago
  TriggeredBy: * pulseaudio.socket
     Main PID: 12198 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   |-12198 /usr/bin/pulseaudio --daemonize=no --log-target=journal
   `-12212 /usr/libexec/pulse/gsettings-helper

  Sep 30 22:55:49 p5q3 systemd[1080]: Starting Sound Service...
  Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:1
  Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:0
  Sep 30 22:55:49 p5q3 systemd[1080]: Started Sound Service.
  Sep 30 22:56:14 p5q3 pulseaudio[12198]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.1-1ubuntu11
  Uname: Linux 5.8.12-050812-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 1088 F pulseaudio
    eugene 1092 F pipewire-media-
   /dev/snd/controlC1:  eugene 1092 F pipewire-media-
   /dev/snd/seq:eugene 1087 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Sep 30 22:50:58 2020
  InstallationDate: Installed on 2019-04-13 (536 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-09-06 (23 days ago)
  dmi.bios.date: 06/11/2010
  dmi.bios.release: 11.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q3
  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.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1900404] Re: pulseaudio[2032]: No UCM verb is valid for hw:0

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

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 1897965, 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 1897965
   pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is valid 
for hw:0)

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

Title:
  pulseaudio[2032]: No UCM verb is valid for hw:0

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  pulseaudio[2032]: No UCM verb is valid for hw:1
  pulseaudio[2032]: No UCM verb is valid for hw:0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/pcmC0D0p:   navycat2032 F...m pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 11:57:52 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  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: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

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

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

[Touch-packages] [Bug 1900404] Re: pulseaudio[2032]: No UCM verb is valid for hw:0

2020-10-19 Thread navycat

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

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

Title:
  pulseaudio[2032]: No UCM verb is valid for hw:0

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  pulseaudio[2032]: No UCM verb is valid for hw:1
  pulseaudio[2032]: No UCM verb is valid for hw:0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/pcmC0D0p:   navycat2032 F...m pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 11:57:52 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  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: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

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

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

[Touch-packages] [Bug 1900404] [NEW] pulseaudio[2032]: No UCM verb is valid for hw:0

2020-10-19 Thread navycat

Public bug reported:

pulseaudio[2032]: No UCM verb is valid for hw:1
pulseaudio[2032]: No UCM verb is valid for hw:0

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
Uname: Linux 5.8.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  navycat2032 F pulseaudio
 /dev/snd/controlC0:  navycat2032 F pulseaudio
 /dev/snd/pcmC0D0p:   navycat2032 F...m pulseaudio
 /dev/snd/controlC1:  navycat2032 F pulseaudio
CasperMD5CheckResult: skip
Date: Mon Oct 19 11:57:52 2020
InstallationDate: Installed on 2020-10-07 (11 days ago)
InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2018
dmi.bios.release: 4.6
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: 150-SE-E789
dmi.board.vendor: EVGA
dmi.board.version: Patsburg
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
dmi.product.family: X86 AT
dmi.product.name: MODEL_NAME
dmi.product.sku: PROJECT_SUB_TAG
dmi.product.version: BASE_BOARD_VERSION
dmi.sys.vendor: BASE_BOARD_MANUFACTURER

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


** Tags: amd64 apport-bug groovy

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

Title:
  pulseaudio[2032]: No UCM verb is valid for hw:0

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  pulseaudio[2032]: No UCM verb is valid for hw:1
  pulseaudio[2032]: No UCM verb is valid for hw:0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/pcmC0D0p:   navycat2032 F...m pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 11:57:52 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  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: 150-SE-E789
  dmi.board.vendor: EVGA
  dmi.board.version: Patsburg
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
  dmi.product.family: X86 AT
  dmi.product.name: MODEL_NAME
  dmi.product.sku: PROJECT_SUB_TAG
  dmi.product.version: BASE_BOARD_VERSION
  dmi.sys.vendor: BASE_BOARD_MANUFACTURER

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

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

[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-10-19 Thread WATTIAU

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

Same issue for me to..

Kernel : version 5.4.0-51-generic
OS : Ubuntu 20.04.1 LTS
Machine : Dell Vostro 5490
Headset : Sennheiser HD 4.50 BTNC

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Touch-packages] [Bug 1900396] [NEW] netstat man-page does not explain -t|--tcp, -u|--udp or -w|--raw

2020-10-19 Thread Morten Siebuhr

Public bug reported:

I tried looking up `netstat -tlnp` on https://explainshell.com, but
there was no explanation for `-t`. It turns out that at least
`-t|--tcp`, `-u|--udp` and `-w|--raw` aren't documented in the man-page
(http://manpages.ubuntu.com/manpages/precise/en/man8/netstat.8.html).

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

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

Title:
  netstat man-page does not explain -t|--tcp, -u|--udp or -w|--raw

Status in net-tools package in Ubuntu:
  New

Bug description:
  I tried looking up `netstat -tlnp` on https://explainshell.com, but
  there was no explanation for `-t`. It turns out that at least
  `-t|--tcp`, `-u|--udp` and `-w|--raw` aren't documented in the man-
  page
  (http://manpages.ubuntu.com/manpages/precise/en/man8/netstat.8.html).

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

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

[Touch-packages] [Bug 1899857] Re: [SRU] alsa-lib: support the enum value settings both in "" and in ''