[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Kai-Heng Feng]

Thanks for verification.

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

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

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

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

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

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

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

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Touch-packages] [Bug 1877793] Re: [Inspiron 13-5378, Realtek ALC3253, Speaker, Internal] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [Inspiron 13-5378, Realtek ALC3253, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Is a duplicate of bug 1877766

  On installation 16.04 LTS there is sound. Also sound in windows. But
  as soon as Ubuntu updates, no sound.

  Tried 18 LTS no sound

  Tried 20 LTS - sound comes back

  But I want to stick with 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-99.100~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1556 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat May  9 22:26:24 2020
  InstallationDate: Installed on 2020-05-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1556 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 13-5378, Realtek ALC3253, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.28.0
  dmi.board.name: 05C3PP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.28.0:bd05/10/2019:svnDellInc.:pnInspiron13-5378:pvr:rvnDellInc.:rn05C3PP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 13-5378
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1880266] Re: console-setup defaults prevent using automatic highdpi fonts

[Dimitri John Ledkov]

** Package changed: linux (Ubuntu) => console-setup (Ubuntu)

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

Title:
  console-setup defaults prevent using automatic highdpi fonts

Status in console-setup package in Ubuntu:
  Incomplete

Bug description:
  console-setup defaults prevent using automatic highdpi fonts

  Kernel has built-in Terminus fonts, at multiple sizes, and it picks
  font based on screen resolution, including selecting high-dpi version
  of the font.

  The autogenerated default of FONTFACE=VGA and FONTSIZE=16 for Lat15
  results in tiny font getting set on high-dpi laptops. Dropping this
  setting, makes fonts to be of correct size on highdpi screens.

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

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

[Touch-packages] [Bug 1880266] [NEW] console-setup defaults prevent using automatic highdpi fonts

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

console-setup defaults prevent using automatic highdpi fonts

Kernel has built-in Terminus fonts, at multiple sizes, and it picks font
based on screen resolution, including selecting high-dpi version of the
font.

The autogenerated default of FONTFACE=VGA and FONTSIZE=16 for Lat15
results in tiny font getting set on high-dpi laptops. Dropping this
setting, makes fonts to be of correct size on highdpi screens.

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

-- 
console-setup defaults prevent using automatic highdpi fonts
https://bugs.launchpad.net/bugs/1880266
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to console-setup 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 1868415] Re: Dell l322x Touchpad click drag doesn't work

[Launchpad Bug Tracker]

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

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

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

Title:
  Dell l322x Touchpad click drag doesn't work

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I've upgraded (fresh installation) my OS from 14.04 to 18.04. And everything 
but the touchpad seems to work properly. 
  When i try to drag and drop something or selecting some text seems dead. I 
tried to do the same things with an external mouse and it works well.
   

  > sudo libinput measure touchpad-pressure
  [sudo] password di matteog: 
  Using CyPS/2 Cypress Trackpad: /dev/input/event6

  Ready for recording data.
  Pressure range used: 30:25
  Palm pressure range used: 130
  Place a single finger on the touchpad to measure pressure values.
  Ctrl+C to exit

  Sequence 116 pressure: min:  46 max:  95 avg:  84 median:  89 tags: down
  Sequence 117 pressure: min:  29 max:  97 avg:  67 median:  86 tags: down
  Sequence 118 pressure: min:  25 max:  50 avg:  41 median:  44 tags: down
  Sequence 119 pressure: min:  13 max:  14 avg:  13 median:  14 tags:
  Sequence 120 pressure: min:  28 max:  31 avg:  29 median:  31 tags: down
  Sequence 121 pressure: min:  15 max:  33 avg:  26 median:  29 tags: down
  Sequence 122 pressure: min:  37 max:  82 avg:  66 median:  73 tags: down
  Sequence 123 pressure: min:  63 max:  94 avg:  83 median:  89 tags: down
  Sequence 124 pressure: min:  66 max: 137 avg: 118 median: 126 tags: down palm
  Sequence 125 pressure: min:  47 max:  73 avg:  63 median:  68 tags: down
  Sequence 126 pressure: min:  33 max:  66 avg:  55 median:  58 tags: down
  Sequence 127 pressure: min:  32 max: 100 avg:  81 median:  91 tags: down
  Sequence 128 pressure: min:  44 max:  86 avg:  72 median:  78 tags: down
  Sequence 129 pressure: min:  62 max: 108 avg:  95 median: 103 tags: down
  Sequence 130 pressure: min:  72 max: 131 avg: 118 median: 124 tags: down palm
  Sequence 131 pressure: min:  52 max: 112 avg:  96 median: 103 tags: down
  Sequence 132 pressure: min:  44 max: 101 avg:  83 median:  88 tags: down
  Sequence 133 pressure: min: 150 max: 150 avg: 150 median: 150 tags: down palm
  Traceback (most recent call last):
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
299, in 
  main(sys.argv)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
289, in main
  loop(device)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
246, in loop
  handle_event(device, event)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
233, in handle_event
  handle_abs(device, event)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
224, in handle_abs
  print("\r{}".format(s))
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
105, in __str__
  return self._str_state() if self.is_active else self._str_summary()
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
114, in _str_summary
  self.avg(),
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
96, in avg
  return int(sum([p.pressure for p in self.points])/len(self.points))
  ZeroDivisionError: division by zero

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

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

[Touch-packages] [Bug 1880262] Re: package ibus 1.5.22-2ubuntu2 failed to install/upgrade: installed ibus package pre-removal script subprocess returned error exit status 127

[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 ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1880262

Title:
  package ibus 1.5.22-2ubuntu2 failed to install/upgrade: installed ibus
  package pre-removal script subprocess returned error exit status 127

Status in ibus package in Ubuntu:
  New

Bug description:
  Was installing Xubuntu Desktop via tasksel

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 22 23:29:17 2020
  DuplicateSignature:
   package:ibus:1.5.22-2ubuntu2
   Removing ibus (1.5.22-2ubuntu2) ...
   /var/lib/dpkg/info/ibus.prerm: 7: dconf: not found
   dpkg: error processing package ibus (--remove):
installed ibus package pre-removal script subprocess returned error exit 
status 127
  ErrorMessage: installed ibus package pre-removal script subprocess returned 
error exit status 127
  InstallationDate: Installed on 2020-05-21 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ibus
  Title: package ibus 1.5.22-2ubuntu2 failed to install/upgrade: installed ibus 
package pre-removal script subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1880262] [NEW] package ibus 1.5.22-2ubuntu2 failed to install/upgrade: installed ibus package pre-removal script subprocess returned error exit status 127

[Wingfung Yuen]

Public bug reported:

Was installing Xubuntu Desktop via tasksel

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: ibus 1.5.22-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri May 22 23:29:17 2020
DuplicateSignature:
 package:ibus:1.5.22-2ubuntu2
 Removing ibus (1.5.22-2ubuntu2) ...
 /var/lib/dpkg/info/ibus.prerm: 7: dconf: not found
 dpkg: error processing package ibus (--remove):
  installed ibus package pre-removal script subprocess returned error exit 
status 127
ErrorMessage: installed ibus package pre-removal script subprocess returned 
error exit status 127
InstallationDate: Installed on 2020-05-21 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: ibus
Title: package ibus 1.5.22-2ubuntu2 failed to install/upgrade: installed ibus 
package pre-removal script subprocess returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package ibus 1.5.22-2ubuntu2 failed to install/upgrade: installed ibus
  package pre-removal script subprocess returned error exit status 127

Status in ibus package in Ubuntu:
  New

Bug description:
  Was installing Xubuntu Desktop via tasksel

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 22 23:29:17 2020
  DuplicateSignature:
   package:ibus:1.5.22-2ubuntu2
   Removing ibus (1.5.22-2ubuntu2) ...
   /var/lib/dpkg/info/ibus.prerm: 7: dconf: not found
   dpkg: error processing package ibus (--remove):
installed ibus package pre-removal script subprocess returned error exit 
status 127
  ErrorMessage: installed ibus package pre-removal script subprocess returned 
error exit status 127
  InstallationDate: Installed on 2020-05-21 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ibus
  Title: package ibus 1.5.22-2ubuntu2 failed to install/upgrade: installed ibus 
package pre-removal script subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1876055] Re: SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base

[Mathew Hodson]

** Tags added: upgrade-software-version

** Changed in: libseccomp (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial
  for newer syscalls for core20 base

Status in libseccomp package in Ubuntu:
  New

Bug description:
  [Impact]

  snap-confine from snapd uses libseccomp to filter various system calls
  for confinement. The current version in eoan/bionic/xenial (2.4.1) is
  missing knowledge of various system calls for various architectures.
  As such this causes strange issues like python snaps segfaulting
  (https://github.com/snapcore/core20/issues/48) or the inadvertent
  denial of system calls which should be permitted by the base policy
  (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal-
  arm64/17237).

  libseccomp in groovy is using the latest upstream base release (2.4.3)
  plus it includes a patch to add some missing aarch64 system calls
  (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633).

  SRUing this version back to older stable releases allows libseccomp to
  operate correctly on all supported architectures.

  
  [Test Case]

  libseccomp includes a significant unit test suite that is run during
  the build and as part of autopkgtests. To verify the new aarch64
  system calls are resolved as expected the scmp_sys_resolver command
  can be used as well:

  $ scmp_sys_resolver -a aarch64 getrlimit
  163

  (whereas in the current version in focal this returns -10180 as
  libseccomp was not aware of this system-call at compile-time).

  As part of this SRU, the test suite in libseccomp has been patched to
  include a local copy of the architecture-specific kernel headers from
  the 5.4 kernel in focal *for all releases*, so that all system calls
  which are defined for the 5.4 kernel are known about *for the
  libseccomp test suite*. This allows all unit tests to pass on older
  releases as well and defaults the build to fail on unit test failures
  (whereas currently in xenial this has been overridden to ignore
  failures).

  
  [Regression Potential]

  This has a low regression potential due to significant testing with
  many packages that depend on libseccomp (lxc, qemu, snapd, apt, man
  etc) and none have shown any regression using this new version.

  Any possible regressions may include applications now seeing correct
  system call resolution whereas previously this would have failed, and
  so perhaps previous failures (which were erroneous) will now be
  permitted. However, this was always permitted previously by the policy
  anyway but just denied due to this bug so it is not a true regression
  as such.

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

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

[Touch-packages] [Bug 1879087] Re: dbus errors, frequent roaming and unstable connectivity

[Mathew Hodson]

** Changed in: wpa (Ubuntu Focal)
   Importance: Undecided => High

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

Title:
  dbus errors, frequent roaming and unstable connectivity

Status in wpa package in Ubuntu:
  Fix Committed
Status in wpa source package in Focal:
  Incomplete

Bug description:
  * Impact
  extra roaming events are been generated

  * Test case
  check the output of `journalctl -lu wpa_supplicant`, it should have warnings
  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  the roaming events should not be too frequent

  * Regression potential
  check that wifi connection keep working correctly

  --

  When using this version of wpa_supplicant with my company
  WPA2-Enterprise wireless setup, I'm experiencing far too frequent
  roaming events (even when not moving around) accompanied by hiccups in
  connectivity. I also see these messages in the wpa_supplicant log:

  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property RoamTime in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property SessionLength in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  Having done a little research, at least the dbus errors seem to be
  fixed by this commit upstream:

  
https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756

  So I built a version of wpa_supplicant including this particular patch
  and installed on my machine. Apart from solving the dbus errors
  completely, it seems to have had a positive impact on the frequent
  roaming and unstable connectivity as well (I've run for a day with no
  burst of roaming events at all, where they used to happen every few
  minutes most of the time.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat May 16 16:47:27 2020
  InstallationDate: Installed on 2020-05-12 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Mathew Hodson]

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

** This bug is no longer a duplicate of bug 1875252
   Ubuntu 20.04 LTS update causing no sound coming from built-in speakers 
** This bug has been marked a duplicate of bug 1876065
   After unplug headphones and plug them again no sound can be heard

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

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

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

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

  The Intel sound card is not getting detected.

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

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

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

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

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

[Touch-packages] [Bug 1877580] Re: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at all

[Mathew Hodson]

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

** This bug is no longer a duplicate of bug 1879939
   Audio stopped working after 5.4.0-31 kernel update
** This bug has been marked a duplicate of bug 1876065
   After unplug headphones and plug them again no sound can be heard

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

Title:
  [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After upgrade from 19.10 to 20.04 (xubuntu) I've lost the sound on the 
headphones.
  The internal loud speakers works ok when the headphones are not plugged in.

  More specifically:
  If I open the pavucontrol without the headphones plugged in I see that is 
correctly mentioning the output as Port: "Speakers (plugged-in)" and everything 
works ok, I have sound from the speakers.

  The moment I plug in the headphones, for a fraction of a second I can
  hear sound on the headphones, and then the output port switches to
  "headphones" which is the moment I lose the sound.

  The fraction that I hear the sound is when the jack is half-inserted
  and I get the sound on one channel only. When is fully inserted, the
  computer detects it and makes the switch.

  I've tried also in alsamixer all possibilities I could imagine,
  playing with mute/unmute and gain of each channel, with no success

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bnv1312 F pulseaudio
bnv   21367 F alsamixer
   /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri May  8 15:41:08 2020
  InstallationDate: Installed on 2019-08-08 (274 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bnv1312 F pulseaudio
bnv   21367 F alsamixer
   /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1877580] Re: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at all

[Johannes]

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

** This bug is no longer a duplicate of bug 1879989
   "Failed to play sound: No such driver"  ubuntu 20.04
** This bug has been marked a duplicate of bug 1879939
   Audio stopped working after 5.4.0-31 kernel update

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

Title:
  [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After upgrade from 19.10 to 20.04 (xubuntu) I've lost the sound on the 
headphones.
  The internal loud speakers works ok when the headphones are not plugged in.

  More specifically:
  If I open the pavucontrol without the headphones plugged in I see that is 
correctly mentioning the output as Port: "Speakers (plugged-in)" and everything 
works ok, I have sound from the speakers.

  The moment I plug in the headphones, for a fraction of a second I can
  hear sound on the headphones, and then the output port switches to
  "headphones" which is the moment I lose the sound.

  The fraction that I hear the sound is when the jack is half-inserted
  and I get the sound on one channel only. When is fully inserted, the
  computer detects it and makes the switch.

  I've tried also in alsamixer all possibilities I could imagine,
  playing with mute/unmute and gain of each channel, with no success

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bnv1312 F pulseaudio
bnv   21367 F alsamixer
   /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri May  8 15:41:08 2020
  InstallationDate: Installed on 2019-08-08 (274 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bnv1312 F pulseaudio
bnv   21367 F alsamixer
   /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1877580] Re: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at all

[Johannes]

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

** This bug has been marked a duplicate of bug 1879989
   "Failed to play sound: No such driver"  ubuntu 20.04

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

Title:
  [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After upgrade from 19.10 to 20.04 (xubuntu) I've lost the sound on the 
headphones.
  The internal loud speakers works ok when the headphones are not plugged in.

  More specifically:
  If I open the pavucontrol without the headphones plugged in I see that is 
correctly mentioning the output as Port: "Speakers (plugged-in)" and everything 
works ok, I have sound from the speakers.

  The moment I plug in the headphones, for a fraction of a second I can
  hear sound on the headphones, and then the output port switches to
  "headphones" which is the moment I lose the sound.

  The fraction that I hear the sound is when the jack is half-inserted
  and I get the sound on one channel only. When is fully inserted, the
  computer detects it and makes the switch.

  I've tried also in alsamixer all possibilities I could imagine,
  playing with mute/unmute and gain of each channel, with no success

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bnv1312 F pulseaudio
bnv   21367 F alsamixer
   /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri May  8 15:41:08 2020
  InstallationDate: Installed on 2019-08-08 (274 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bnv1312 F pulseaudio
bnv   21367 F alsamixer
   /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1880222] Re: ubuntu bionic-backports Hash Sum mismatch

[Seth Arnold]

Are you still having trouble with this file?

If you still have this file:
/var/lib/apt/lists/partial/us.archive.ubuntu.com_ubuntu_dists_bionic-backports_Contents-i386.gz
can you determine from looking at it if it looks remotely close to what was 
expected?

The usual cause of this problem is ISP-deployed transparent caches, it
might be worth looking into various websites for "am I behind a proxy?".
I've seen apt-cacher-ng cause this problem too, but that was seven years
ago.

The version of this file I retrieved a few minutes ago from all four
archive mirrors that I can reach were identical, and matched what the
Release file says they should match.

Thanks

** Information type changed from Private Security to Public Security

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

** Changed in: update-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  ubuntu bionic-backports Hash Sum mismatch

Status in apt package in Ubuntu:
  Incomplete
Status in update-manager package in Ubuntu:
  Incomplete

Bug description:
  # apt-get update
  (proceeded normally until...)
  Err:24 http://us.archive.ubuntu.com/ubuntu bionic-backports i386 Contents 
(deb)
Hash Sum mismatch
Hashes of expected file:
 - Filesize:724924 [weak]
 - SHA256:d59f30b35a9fd0f52922cbf3a4bf1f0713e816a209cca57bac1dbc56af3c9a77
 - SHA1:0d1e53232da2c41febc6cccecfc4000f930c3450 [weak]
 - MD5Sum:dfa1f7010a23b70c967aef7600ebd49f [weak]
Hashes of received file:
 - SHA256:1c97d900fc3b9168c38bf870b1dd7c71be88ff72e0751c1551b8129c8de98740
 - SHA1:a725025e50c3ebd60dd16058594340b4ca9c97e2 [weak]
 - MD5Sum:925bb2a78f81a2dc9b4269a6f5e9ece5 [weak]
 - Filesize:90948 [weak]
Release file created at: Fri, 22 May 2020 16:49:51 +
  Fetched 254 MB in 51s (5,014 kB/s)
  Reading package lists... Done
  E: Failed to fetch 
store:/var/lib/apt/lists/partial/us.archive.ubuntu.com_ubuntu_dists_bionic-backports_Contents-i386.gz
  Hash Sum mismatch
 Hashes of expected file:
  - Filesize:724924 [weak]
  - SHA256:d59f30b35a9fd0f52922cbf3a4bf1f0713e816a209cca57bac1dbc56af3c9a77
  - SHA1:0d1e53232da2c41febc6cccecfc4000f930c3450 [weak]
  - MD5Sum:dfa1f7010a23b70c967aef7600ebd49f [weak]
 Hashes of received file:
  - SHA256:1c97d900fc3b9168c38bf870b1dd7c71be88ff72e0751c1551b8129c8de98740
  - SHA1:a725025e50c3ebd60dd16058594340b4ca9c97e2 [weak]
  - MD5Sum:925bb2a78f81a2dc9b4269a6f5e9ece5 [weak]
  - Filesize:90948 [weak]
 Release file created at: Fri, 22 May 2020 16:49:51 +
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.

  $ apt-get -v
  apt 1.6.12ubuntu0.1 (amd64)

  Also, Software Updater (version 1:18.04.11.12) after hitting "Install" gives 
pop-up:
  "Requires installation of untrusted packages
   This requires installing packages from unauthenticated sources."
  Only options: "Settings..." and "OK"
  And it is not OK; I have not configured any unauthenticated sources!

  This occurs when enabling updates from Ubuntu Base (but not Security
  updates).

  I expected to not get such errors and updating to occur normally.

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

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

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

[Touch-packages] [Bug 1879087] Re: dbus errors, frequent roaming and unstable connectivity

[Steve Langasek]

> the roaming events should not be too frequent

That's not an objective test case.  Please provide a clear test case
that anyone should be able to follow to determine whether this bug has
been fixed.

** Description changed:

  * Impact
  extra roaming events are been generated
  
  * Test case
- check the wpa_supplicant log, it should have warnings
+ check the output of `journalctl -lu wpa_supplicant`, it should have warnings
  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  
  the roaming events should not be too frequent
  
  * Regression potential
  check that wifi connection keep working correctly
- 
  
  --
  
  When using this version of wpa_supplicant with my company
  WPA2-Enterprise wireless setup, I'm experiencing far too frequent
  roaming events (even when not moving around) accompanied by hiccups in
  connectivity. I also see these messages in the wpa_supplicant log:
  
  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property RoamTime in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property SessionLength in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  
  Having done a little research, at least the dbus errors seem to be fixed
  by this commit upstream:
  
  
https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756
  
  So I built a version of wpa_supplicant including this particular patch
  and installed on my machine. Apart from solving the dbus errors
  completely, it seems to have had a positive impact on the frequent
  roaming and unstable connectivity as well (I've run for a day with no
  burst of roaming events at all, where they used to happen every few
  minutes most of the time.)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat May 16 16:47:27 2020
  InstallationDate: Installed on 2020-05-12 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

** Also affects: wpa (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

Title:
  dbus errors, frequent roaming and unstable connectivity

Status in wpa package in Ubuntu:
  Fix Committed
Status in wpa source package in Focal:
  Incomplete

Bug description:
  * Impact
  extra roaming events are been generated

  * Test case
  check the output of `journalctl -lu wpa_supplicant`, it should have warnings
  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  the roaming events should not be too frequent

  * Regression potential
  check that wifi connection keep working correctly

  --

  When using this version of wpa_supplicant with my company
  WPA2-Enterprise wireless setup, I'm experiencing far too frequent
  roaming events (even when not moving around) accompanied by hiccups in
  connectivity. I also see these messages in the wpa_supplicant log:

  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property RoamTime in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property SessionLength in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  Having done a little research, at least the dbus errors seem to be
  fixed by this commit upstream:

  
https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756

  So I built a version of wpa_supplicant including this particular patch
  and installed on my machine. Apart from solving the dbus errors
  completely, it seems to have had a positive impact on the frequent
  roaming and unstable connectivity as well (I've run for a day with no
  burst of roaming events at all, where they used to happen every few
  minutes most of the time.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat May 16 16:47:27 2020
  InstallationDate: Installed on 2020-05-12 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 

[Touch-packages] [Bug 1880258] [NEW] Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise

[MarcH]

Public bug reported:

I normally don't like this, but it's a one-character change so it's
easier to start with the solution:

diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
--- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf  
+++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
@@ -1,2 +1,2 @@
 [connectivity]
-uri=http://connectivity-check.ubuntu.com/
+uri=http://connectivity-check.ubuntu.com./

Making this name absolute instead of relative avoids spurious
resolutions of "connectivity-check.ubuntu.com.your_domain." This removes
a fair amount of NXDOMAIN error noise in journalctl.


Observing the issue and the fix requires 3 terminals:

1. tcpdump -i any 'port domain'
2. journalctl --boot -u systemd-resolved -f

3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
 => observe the NXDOMAIN noise over a couple few minutes
 
Now make the hostname absolute with the trailing dot above and run:
   systemctl reload NetworkManager
Wait 1 min for things to stabilize. Test again:

nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
 => observe non-zero but significantly reduced NXDOMAIN noise over a couple few 
minutes

Originally reported at https://askubuntu.com/a/1242611/117217

Plenty of people annoyed by NXDOMAIN warnings, just Google it.

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

Title:
  Add trailing dot to make connectivity-check.ubuntu.com. absolute and
  reduce NXDOMAIN warning noise

Status in systemd package in Ubuntu:
  New

Bug description:
  I normally don't like this, but it's a one-character change so it's
  easier to start with the solution:

  diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf  
  +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  @@ -1,2 +1,2 @@
   [connectivity]
  -uri=http://connectivity-check.ubuntu.com/
  +uri=http://connectivity-check.ubuntu.com./

  Making this name absolute instead of relative avoids spurious
  resolutions of "connectivity-check.ubuntu.com.your_domain." This
  removes a fair amount of NXDOMAIN error noise in journalctl.

  
  Observing the issue and the fix requires 3 terminals:

  1. tcpdump -i any 'port domain'
  2. journalctl --boot -u systemd-resolved -f

  3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe the NXDOMAIN noise over a couple few minutes
   
  Now make the hostname absolute with the trailing dot above and run:
 systemctl reload NetworkManager
  Wait 1 min for things to stabilize. Test again:

  nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe non-zero but significantly reduced NXDOMAIN noise over a couple 
few minutes

  Originally reported at https://askubuntu.com/a/1242611/117217

  Plenty of people annoyed by NXDOMAIN warnings, just Google it.

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

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

[Touch-packages] [Bug 1875558] Re: [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

[Steve Langasek]

Hello Corentin, or anyone else affected,

Accepted libproxy into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libproxy/0.4.15-10ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libproxy (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  [SRU] libproxy1-plugin-gsettings triggers a lot of warnings

Status in libproxy package in Ubuntu:
  Fix Released
Status in libproxy source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * The proxy configuration from GSettings is not getting exported and
  thus is not used by libproxy-enabled applications.

   * Many GLib applications are now throwing critical messages in the
  logs when running. This is escpecially true for WebKitGtk applications
  which are throwing one message by subprocess.

  [Test Case]

   * Open a WebKitGtk application such as Epiphany (GNOME Web) with the
  terminal and see the critical messages

  GLib-GObject-WARNING **: 09:00:09.217:
  ../../../gobject/gsignal.c:2617: signal 'changed::' is invalid for
  instance '0x55b923a6b430' of type 'GSettings'

  [Regression Potential]

   * No regression is to expect from this patch

  [Other Info]
   
   * The patch is already in debian experimental and is available since 
0.4.15-12

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

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

[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Andycds]

After I enabled "Proposed" and update pulseaudio, the problems seems to
be fixed.

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

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

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

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

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

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

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Touch-packages] [Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content

[Brian Murray]

** Tags added: rls-gg-incoming

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

Title:
  apport-unpack: ValueError: ['UserGroups'] has no binary content

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged

Bug description:
  When running apport-unpack to get at a core dump

  laney@raleigh> sudo apport-unpack 
_usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz
  [sudo] password for laney: 
  Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 73, in 
  pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in 
extract_keys
  [item for item, element in b64_block.items() if element is False])
  ValueError: ['UserGroups'] has no binary content
  laney@raleigh> apport-cli --version
  2.16.2

  It's not terrible, because most files are unpacked (those which sort
  before UserGroups, I guess).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.16.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportLog:
   
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 10:09:26 2015
  InstallationDate: Installed on 2012-10-07 (876 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)

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

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

[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[A M]

(I'm not using Ubuntu for my desktop but I'have had the same problem. I'm 
running Pulseaudio 13 built with enable_bluez5_native_headset and Bluez 5.54)
Solved it by adding headset=native forthe module module-bluetooth-discover in 
default.pa :
 load-module module-bluetooth-discover headset=native
in ~/.pulse/default.pa  (or /etc/pulse/default.pa)
then restarting pulseaudio with pulseaudio -k
Since Pulseaudio 11.0 has ofono support, "headset=auto" option enabled by 
default, 

pactl list shows that both profiles with available: yes

Generally when using VoIP application automatically switch bluetooth
profile to HSP works , but when not or when switch back to A2DP need to
be done annually (for me, Blueman does the job with a few clicks).

Sound with HSP profile isn't very good and HFP doesn't seems to work as
I haven't setup phonesimp (ref
https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Bluetooth/
)

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

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

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

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

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

[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit

[Brian Murray]

** Also affects: procps (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955697
   Importance: Unknown
   Status: Unknown

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

Title:
  pgrep reports error "cannot allocate" when run without stack limit

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

Bug description:
  If you have no stack limit (ulimit -S -s unlimited), any pgrep call
  will fail with an error:

  > pgrep vim
  pgrep: cannot allocate 4611686018427387903 bytes

  If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is
  very slow:

  > time pgrep vim
  2196
  real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444

  The relevant upstream bug report could be: 
https://gitlab.com/procps-ng/procps/-/issues/152
  Archlinux bug report: https://bugs.archlinux.org/task/66093

  procps:
Installed: 2:3.3.16-1ubuntu2
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

[Touch-packages] [Bug 1867390] Re: Update libarchive to 3.4.2

[Brian Murray]

3.4.2-1 is now available in groovy which will become Ubuntu 20.10. I'll
open a task for Ubuntu 20.04 LTS (focal) though.

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

** Also affects: libarchive (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: libarchive (Ubuntu Focal)
   Status: New => Triaged

** Changed in: libarchive (Ubuntu Focal)
   Importance: Undecided => Wishlist

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

Title:
  Update libarchive to 3.4.2

Status in libarchive package in Ubuntu:
  Fix Released
Status in libarchive source package in Focal:
  Triaged
Status in libarchive package in Debian:
  New

Bug description:
  Please update libarchive to 3.4.2, also fixes LP: #1814109.

  The bug and security fixes outweighs the new features added in 3.4.1
  and 3.4.2.

  https://github.com/libarchive/libarchive/releases

  Libarchive 3.4.2 is a feature and security release.

  New features:

  support for atomic file extraction (bsdtar -x --safe-writes) (#1289)
  support for mbed TLS (PolarSSL) (#1301)

  Important bugfixes:

  security fixes in RAR5 reader (#1280 #1326)
  compression buffer fix in XAR writer (#1317)
  fix uname and gname longer than 32 characters in PAX writer (#1319)
  fix segfault when archiving hard links in ISO9660 and XAR writers (#1325)
  fix support for extracting 7z archive entries with Delta filter (fixes LP: 
#1814109) (#987)

  Libarchive 3.4.1 is a feature and security release.

  New features:

  Unicode filename support for reading lha/lzh archives
  New pax write option "xattrhdr"

  Important bugfixes:

  security fixes in wide string processing (#1276 #1298)
  security fixes in RAR5 reader (#1212 #1217 #1296)
  security fixes and optimizations to write filter logic (#351)
  security fix related to use of readlink(2) (1dae5a5)
  sparse file handling fixes (#1218 #1260)

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

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

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

[Guilherme G. Piccoli]

List of somewhat duplicate bugs:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/120375
(after comment #74)

https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/251164
(propose some alternative solutions we can think about, like failure hooks)

https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/659899

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003309
(partially related)

blog post: feeding.cloud.geek.nz/posts/the-perils-of-raid-and-full-disk-
encryption-on-ubuntu

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

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

Status in cryptsetup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in mdadm package in Ubuntu:
  Confirmed

Bug description:
  Description will be saved for further SRU template, the details of the
  issue will be exposed in comments

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

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

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

[Guilherme G. Piccoli]

Not a debdiff - I found easier to just add the patches as in my local
git repository of the packages.

** Patch added: "cryptroot patch"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879980/+attachment/5375734/+files/0001-d-initramfs-cryptroot-script-Allow-some-retries-on-l.patch

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

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

Status in cryptsetup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in mdadm package in Ubuntu:
  Confirmed

Bug description:
  Description will be saved for further SRU template, the details of the
  issue will be exposed in comments

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

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

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

[Guilherme G. Piccoli]

** Patch added: "mdadm patch"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879980/+attachment/5375736/+files/0001-script.local-block-Improve-last-resort-mechanism.patch

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

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

Status in cryptsetup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in mdadm package in Ubuntu:
  Confirmed

Bug description:
  Description will be saved for further SRU template, the details of the
  issue will be exposed in comments

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

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

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

[Guilherme G. Piccoli]

** Patch added: "initramfs-tools patch"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879980/+attachment/5375735/+files/0001-scripts-local-Allow-local-block-looping-as-Debian.patch

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

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

Status in cryptsetup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in mdadm package in Ubuntu:
  Confirmed

Bug description:
  Description will be saved for further SRU template, the details of the
  issue will be exposed in comments

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

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

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

[Guilherme G. Piccoli]

The issue basically is about a failure in mounting root if we have a
stacked setup of LUKS on top of RAID1, when RAID1 is degraded (like a
member missing). What happens in detail is a conjuncture of factors
leading to this problem:

(a) The initramfs script for cryptroot currently is present in two
initram stages: local-top and local-block. Problem is that if the script
fails on local-top phase, it panics and opens a console, not allowing
the boot process to continue. In this case, subsequent scripts are not
executed automatically.

(b) The mdadm initramfs script to mount degraded arrays runs on local-
block stage. It provides a heuristic that tries a regular array assemble
for (2/3*ROOTDELAY) times, and then it assembles the array as degraded,
in which is called the "poor man last resort" mechanism.

So, the first and far more serious issue is cryptroot early fail at
local-top phase. So an idea I've implemented to fix this was to allow
some retries on local-block stage, given local-block should loop for a
while running its scripts (at least according to documentation and
Debian's initramfs code). But guess what ?

(c) In Ubuntu, we have wait-on-root, which aims to speed-up the boot, in
my shallow understanding. Basically, we have wait-for-root consuming
almost all the ROOTDELAY time (30s as default, if not specified), and
local-block scripts run only once. Except...mdadm, which has the
previously mentioned heuristic of running 2/3*ROOTDELAY times. And for
that, we have a hack on initramfs-tools to cope with mdadm (!), as per
commit: salsa.debian.org/kernel-team/initramfs-tools/-/commit/033c948bb0
.

So, to fix the cryptroot inability to mount root device on top a
degraded RAID1 is a matter of coordinate mdadm and cryptroot, and (if my
approach is taken), loop on local-block. Below are the steps I took to
circumvent this long-term issue:

1) Allows cryptsetup to retry on local-block stage, relying in a
heuristic based on ROOTDELAY (we try 1/4*ROOTDELAY times) and on
initramfs looping at local-block phase.

2) Reduce the heuristic frequency on mdadm, in order it doesn't "beat"
the cryptroot attempts, i.e., cryptroot must execute more times. for
this, we reduced the heuristic for 1/5*ROOTDELAY.

3) Make local-block on Ubuntu loop again, but still rely on wait-for-
root in a first step; also, I removed that mdadm heinous hack from
initramfs-tools, it works without...that...if local-block loops.

Below I'll submit groovy debdiffs to gather reviews on my approach. Also, a PPA 
with packages built, in case somebody else wanna give them a try: 
https://launchpad.net/~gpiccoli/+archive/ubuntu/lp1879980
Thanks,


Guilherme

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

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

Status in cryptsetup package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in mdadm package in Ubuntu:
  Confirmed

Bug description:
  Description will be saved for further SRU template, the details of the
  issue will be exposed in comments

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

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Ryan Harper]

systemd debdiff with a fix to skip creating /dev/disk/by-uuid for bcache
backing, caching devices.

** Patch added: "lp1861941-skip-bcache-links.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+attachment/5375730/+files/lp1861941-skip-bcache-links.debdiff

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in bcache-tools source package in Focal:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  New
Status in systemd source package in Focal:
  Invalid
Status in bcache-tools source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  New
Status in systemd source package in Groovy:
  Invalid

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

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

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

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

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

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

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

[Touch-packages] [Bug 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux

[Bryce Harrington]

Can you explain the configuration process for saslauthd with slapd?  Or
a copy of your config file would do.

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

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

Title:
  apparmor profile denied for saslauthd: /run/saslauthd/mux

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  When using slapd with saslauthd the processes communicate via the
  {,/var}/run/saslauthd/mux socket (this is the default location for the
  saslauthd server from the sasl2-bin package in the
  /etc/default/saslauthd config), but the apparmor profile for
  usr.sbin.slapd does not allow access to this socket/file.

  Syslog message:
  apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd" 
name="/run/saslauthd/mux" pid=1880
  4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0

  
  Please add the following line to  /etc/apparmor.d/usr.sbin.slapd:
  /{,var/}run/saslauthd/mux rw,

  
  Ubuntu version: Ubuntu 14.04.4 LTS
  slapd version: 2.4.31-1+nmu2ubu

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

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Ryan Harper]

Updated test to be a bit more resilient.

** Attachment added: "test-bcache-byuuid-links-fixed.sh"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941/+attachment/5375723/+files/test-bcache-byuuid-links-fixed.sh

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in bcache-tools source package in Focal:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  New
Status in systemd source package in Focal:
  Invalid
Status in bcache-tools source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  New
Status in systemd source package in Groovy:
  Invalid

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

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

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

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

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

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

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Ryan Harper]

Tarball of a source package with a fix for this issue:

bcache-tools_1.0.8.orig.tar.gz
bcache-tools_1.0.8-4ubuntu1_amd64.build
bcache-tools_1.0.8-4ubuntu1_amd64.buildinfo
bcache-tools_1.0.8-4ubuntu1_amd64.changes
bcache-tools_1.0.8-4ubuntu1_amd64.deb
bcache-tools_1.0.8-4ubuntu1.debian.tar.xz
bcache-tools_1.0.8-4ubuntu1.dsc
bcache-tools_1.0.8-4ubuntu1_source.build
bcache-tools_1.0.8-4ubuntu1_source.buildinfo
bcache-tools_1.0.8-4ubuntu1_source.changes
bcache-tools-dbgsym_1.0.8-4ubuntu1_amd64.ddeb
bcache-tools-debdiff-1.0.8-4_to_1.0.8-4ubuntu1


** Attachment added: "bcache-tools-fix-lp1861941.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941/+attachment/5375721/+files/bcache-tools-fix-lp1861941.tar.gz

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in bcache-tools source package in Focal:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  New
Status in systemd source package in Focal:
  Invalid
Status in bcache-tools source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  New
Status in systemd source package in Groovy:
  Invalid

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

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

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

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

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

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

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Ryan Harper]

debdiff of the changes

** Attachment added: "bcache-tools-debdiff-1.0.8-4_to_1.0.8-4ubuntu1"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941/+attachment/5375722/+files/bcache-tools-debdiff-1.0.8-4_to_1.0.8-4ubuntu1

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in bcache-tools source package in Focal:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  New
Status in systemd source package in Focal:
  Invalid
Status in bcache-tools source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  New
Status in systemd source package in Groovy:
  Invalid

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

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

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

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

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

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

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

[Touch-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

[Guilherme G. Piccoli]

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

Sorry, dup of LP #1573095.

** This bug has been marked a duplicate of bug 1573095
   Cloud images fail to boot when a serial port is not available

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

Title:
  machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel get stucks at boot if console=ttyS* is specified in the kernel
  cmdline and that serial HW isn't available on the system.

  Reproduced with:
  4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next 
(mainline)

  Removing the non-existent 'console=ttyS*' parameter fixes the
  situation.

  I tested it using KVM/qemu, but it has been brought to my attention
  that it was reproducible in VMware as well.

  I think it is safe to say that it is unlikely to be specifics to a
  certain virtualization technology type.

  Didn't test on baremetal yet.

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

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

[Touch-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

[Guilherme G. Piccoli]

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

Eric, I'll close this LP as dup of #1879987 - seems it's the same issue.
I'll try also the Debian release top see what's different there...we can
comment in the other bug about Debian status and what are the
differences.

Thanks,


Guilherme

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

Title:
  machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel get stucks at boot if console=ttyS* is specified in the kernel
  cmdline and that serial HW isn't available on the system.

  Reproduced with:
  4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next 
(mainline)

  Removing the non-existent 'console=ttyS*' parameter fixes the
  situation.

  I tested it using KVM/qemu, but it has been brought to my attention
  that it was reproducible in VMware as well.

  I think it is safe to say that it is unlikely to be specifics to a
  certain virtualization technology type.

  Didn't test on baremetal yet.

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

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

[Touch-packages] [Bug 1879768] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@162:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad

[Brian Murray]

The fix that was used for
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866347, found in
apport's focal branch r2748, works around this by not creating a crash
address signature if ProcMaps contains a "Permission denied" error.
However, I now wonder why permission was denied.

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

Title:
  /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport
  /whoopsie-upload-
  
all@162:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache

Status in apport package in Ubuntu:
  Confirmed

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, the problem page at 
https://errors.ubuntu.com/problem/273e9176fa4ab3b0cd738b3fa4e782fabc3957a4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

[Stefano Dall'Agata]

I tried installing a printer via GUI after the last suggested commands.
Then I gave the commands:

~$  ls -l /var/log/cups/*
-rw-r- 1 root adm 5058 mag 22 21:37 /var/log/cups/access_log
-rw-r- 1 root adm 1962 mag 20 00:00 /var/log/cups/access_log.1
-rw-r- 1 root adm 7883 mag 18 22:52 /var/log/cups/access_log.2.gz
-rw-r- 1 root adm  642 mag 22 21:36 /var/log/cups/error_log
-rw-r- 1 root adm  458 mag 20 00:00 /var/log/cups/error_log.1
-rw-r- 1 root adm 2352 mag 18 18:53 /var/log/cups/error_log.2.gz

~$ lpinfo -v
file cups-brf:/
network beh
network ipps
network ipp
network socket
network lpd
network https
direct hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
serial serial:/dev/ttyS0?baud=115200
network http
direct hpfax
network 
dnssd://HP%20DeskJet%203630%20series%20%5B9B20BB%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-f439099b20bb
network socket://192.168.1.249:9100
network ipp://HP%20DeskJet%203630%20series%20%5B9B20BB%5D._ipp._tcp.local/

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

[Stefano Dall'Agata]

stefano@stefano-Lenovo-G50-30:~$ lpadmin -p DJ3630 -E -v 
ipp://DeskJet%203630%20series%20%5BCN8AM7H3230658%5D._ipp._tcp.local/ -m 
everywhere
lpadmin: Unable to connect to "stefano-Lenovo-G50-30.local:6": Argomento 
non valido

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

[Till Kamppeter]

Could you try:

lpadmin -p DJ3630 -E -v
ipp://DeskJet%203630%20series%20%5BCN8AM7H3230658%5D._ipp._tcp.local/ -m
everywhere

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

[Stefano Dall'Agata]

~$  sudo apt install --reinstall printer-driver-hpcups 
printer-driver-postscript-hp libsane-hpaio hplip-gui hplip hplip-data libhpmud0
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze   
Lettura informazioni sullo stato... Fatto
Pacchetti suggeriti:
  hplip-doc
I seguenti pacchetti NUOVI saranno installati:
  hplip hplip-data hplip-gui libsane-hpaio printer-driver-postscript-hp
0 aggiornati, 5 installati, 2 reinstallati, 0 da rimuovere e 25 non aggiornati.
È necessario scaricare 1.122 kB/8.271 kB di archivi.
Dopo quest'operazione, verranno occupati 14,3 MB di spazio su disco.
Scaricamento di:1 http://it.archive.ubuntu.com/ubuntu focal/main amd64 
printer-driver-postscript-hp amd64 3.20.3+dfsg0-2 [1.122 kB]
Recuperati 1.122 kB in 1s (2.204 kB/s)  
Selezionato il pacchetto hplip-data non precedentemente selezionato.
(Lettura del database... 226807 file e directory attualmente installati.)
Preparativi per estrarre .../0-hplip-data_3.20.3+dfsg0-2_all.deb...
Estrazione di hplip-data (3.20.3+dfsg0-2)...
Selezionato il pacchetto libsane-hpaio:amd64 non precedentemente selezionato.
Preparativi per estrarre .../1-libsane-hpaio_3.20.3+dfsg0-2_amd64.deb...
Estrazione di libsane-hpaio:amd64 (3.20.3+dfsg0-2)...
Selezionato il pacchetto hplip non precedentemente selezionato.
Preparativi per estrarre .../2-hplip_3.20.3+dfsg0-2_amd64.deb...
Estrazione di hplip (3.20.3+dfsg0-2)...
Selezionato il pacchetto hplip-gui non precedentemente selezionato.
Preparativi per estrarre .../3-hplip-gui_3.20.3+dfsg0-2_all.deb...
Estrazione di hplip-gui (3.20.3+dfsg0-2)...
Preparativi per estrarre .../4-libhpmud0_3.20.3+dfsg0-2_amd64.deb...
Estrazione di libhpmud0:amd64 (3.20.3+dfsg0-2) su (3.20.3+dfsg0-2)...
Preparativi per estrarre .../5-printer-driver-hpcups_3.20.3+dfsg0-2_amd64.deb...
Estrazione di printer-driver-hpcups (3.20.3+dfsg0-2) su (3.20.3+dfsg0-2)...
Selezionato il pacchetto printer-driver-postscript-hp non precedentemente selezi
onato.
Preparativi per estrarre .../6-printer-driver-postscript-hp_3.20.3+dfsg0-2_amd64
.deb...
Estrazione di printer-driver-postscript-hp (3.20.3+dfsg0-2)...
Configurazione di hplip-data (3.20.3+dfsg0-2)...
Configurazione di printer-driver-postscript-hp (3.20.3+dfsg0-2)...
Configurazione di libhpmud0:amd64 (3.20.3+dfsg0-2)...
Configurazione di libsane-hpaio:amd64 (3.20.3+dfsg0-2)...
Configurazione di printer-driver-hpcups (3.20.3+dfsg0-2)...
Configurazione di hplip (3.20.3+dfsg0-2)...
Creating/updating hplip user account...
Configurazione di hplip-gui (3.20.3+dfsg0-2)...
Elaborazione dei trigger per bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu2)...
Rebuilding /usr/share/applications/bamf-2.index...
Elaborazione dei trigger per desktop-file-utils (0.24-1ubuntu2)...
Elaborazione dei trigger per mime-support (3.64ubuntu1)...
Elaborazione dei trigger per cups (2.3.1-9ubuntu1.1)...
Elaborazione dei trigger per gnome-menus (3.36.0-1ubuntu1)...
Elaborazione dei trigger per libc-bin (2.31-0ubuntu9)...
Elaborazione dei trigger per man-db (2.9.1-1)...
Elaborazione dei trigger per dbus (1.12.16-2ubuntu2)...

stefano@stefano-Lenovo-G50-30:~$ lpadmin -x DeskJet_3630
stefano@stefano-Lenovo-G50-30:~$lpadmin -x HP_DeskJet_3630_series
stefano@stefano-Lenovo-G50-30:~$ lpstat -v
lpstat: Nessuna destinazione aggiunta.


~$ lpadmin -p DJ3630 -E -v 
ipp://HP%20DeskJet%203630%20series%20%5B9B20BB%5D._ipp._tcp.local/ -m everywhere
lpadmin: Unable to connect to "HPF439099B20BB.local:631": Operazione ora in 
corso

There is no driver for any printer.

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  

[Touch-packages] [Bug 1875927] Re: add support for phys_port_name attribute in Xenial/16.04LTS

[Eric Desrochers]

** Changed in: systemd (Ubuntu Xenial)
   Status: In Progress => Won't Fix

** Changed in: systemd (Ubuntu Xenial)
 Assignee: Eric Desrochers (slashd) => (unassigned)

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

Title:
  add support for phys_port_name attribute in Xenial/16.04LTS

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Won't Fix

Bug description:
  [Impact]
  In Xenial/16.04LTS, one can't generate network interface name from 
"phys_port_name" attribute.

  "phys_port_name" indicates the interface physical port name within the
  NIC.

  [Test Case]

  Check that udev (systemd-udevd) provides the phys_port_name property
  Tests should be done on kernel versions: v4.15 (HWE)

  # cat /sys/class/net//phys_port_name
  yyy

  Look if interface name contains the 'phys_port_name':

  $ ip link show
  
  3: ens3nyyy:  ...
  

  [Regression Potential]

  * This piece of code is already in place in Bionic (systemd) and late.
  AFAICT, nothing has been reported since then with regards to this feature.

  * phys_port_name kernel support has been introduced in v4.1, but none
  of the current v4.4 Xenial kernel drivers uses it (minus rocker which
  is a test bed software switch for devel work on switchdev, it has no
  real function)

  # Xenial - kernel v4.4
  config-4.4.0-142-generic:# CONFIG_NET_SWITCHDEV is not set

  No drivers uses the phys_port_name method at all + NET_SWITCHDEV is
  not even turned on.

  # Xenial HWE - kernel v4.15
  config-4.15.0-99-generic:CONFIG_NET_SWITCHDEV=y

  Meaning if a regression arise, it will be limited to the HWE kernel (v4.15) 
and to the "Ethernet switch device driver model (switchdev)":
  mlx5
  mlxsw
  bnxt
  sfc (solarflar)

  --
  drivers/net/ethernet:
  --
  broadcom/bnxt/bnxt_vfr.c: .ndo_get_phys_port_name = 
bnxt_vf_rep_get_phys_port_name
  broadcom/bnxt/bnxt.c: .ndo_get_phys_port_name = bnxt_get_phys_port_name
  cavium/liquidio/lio_vf_rep.c: .ndo_get_phys_port_name = 
lio_vf_rep_phys_port_name,
  mellanox/mlx5/core/en_rep.c:  .ndo_get_phys_port_name  = 
mlx5e_rep_get_phys_port_name,
  mellanox/mlxsw/switchx2.c:.ndo_get_phys_port_name = 
mlxsw_sx_port_get_phys_port_name,
  mellanox/mlxsw/spectrum.c:.ndo_get_phys_port_name = 
mlxsw_sp_port_get_phys_port_name,
  netronome/nfp/nfp_net_repr.c: .ndo_get_phys_port_name = 
nfp_port_get_phys_port_name,
  netronome/nfp/nfp_net_common.c:   .ndo_get_phys_port_name = 
nfp_port_get_phys_port_name,
  rocker/rocker_main.c: .ndo_get_phys_port_name = 
rocker_port_get_phys_port_name,
  sfc/efx.c:.ndo_get_phys_port_name = efx_get_phys_port_name,
  --

  # On other more specific kernels the regression potential can be
  expanded to virtio-net driver as well.

  # cloud-init may taint the result as it renames switchdev(s) after
  systemd at first initialization (even without the phys_port_name
  support) as follows:

  (Testing on a sfc card / server deployed by MAAS)

  syslog:May 20 22:12:43 OBFUSCATED_HOST kernel: [ 36.199674] sfc :08:00.1 
ens1f1: renamed from eth1 ## systemd
  syslog:May 20 22:12:43 OBFUSCATED_HOST kernel: [ 37.128236] sfc :08:00.0 
ens1f0: renamed from eth0 ## systemd

  syslog:May 20 22:12:43 OBFUSCATED_HOST kernel: [ 84.653460] sfc :08:00.0 
ens1f0np0: renamed from ens1f0 ## cloud-init
  syslog:May 20 22:12:43 OBFUSCATED_HOST kernel: [ 84.697177] sfc :08:00.1 
ens1f1np1: renamed from ens1f1 ## cloud-init

  cloud-init.log:2020-05-20 22:04:53,980 - util.py[DEBUG]: Running command 
['ip', 'link', 'set', 'ens1f0', 'name', 'ens1f0np0'] with allowed return codes 
[0] (shell=False, capture=True)
  cloud-init.log:2020-05-20 22:04:54,016 - util.py[DEBUG]: Running command 
['ip', 'link', 'set', 'ens1f1', 'name', 'ens1f1np1'] with allowed return codes 
[0] (shell=False, capture=True)

  systemd:
  ... OBFUSCATED_HOST systemd[1]: sys-subsystem-net-devices-ens1f1.device: Dev 
sys-subsystem-net-devices-ens1f1.device appeared twice with different sysfs 
paths /sys/devices/pci:00/:00:03.0/:08:00.1/net/ens1f1 and 
/sys/devices/pci:00/:00:03.0/:08:00.1/net/ens1f1np1

  # 1 concern was raise here by ddstreet:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1875927/comments/1

  Here's the result of the test I have performed:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1875927/comments/5

  This change indeed rename existing switchdev interfaces to add the
  'phys_port_name' (if any) into it. I'm afraid this will be a non-
  acceptable behaviour change in stable release and won't be SRU'able.

  More discussion on this topic to come 

  [Other informations]
  
https://github.com/systemd/systemd/commit/4887b656c22af059d4e833de7b56544f24951184
  https://github.com/systemd/systemd/pull/4506

  [Original Description]

  It has been brought to 

[Touch-packages] [Bug 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

[Sergio Durigan Junior]

** Merge proposal unlinked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/apparmor/+git/apparmor/+merge/383796

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

Title:
  /proc/sys/kernel/random/boot_id rule missing from
  abstractions/nameservice

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  On a default Focal install, systemd is used when looking up passwd and
  group information:

  # grep systemd /etc/nsswitch.conf
  passwd: files systemd
  group:  files systemd

  Daemons confined by Apparmor that also query those "databases" will
  cause this Apparmor denial:

  audit: type=1400 audit(1586825456.411:247): apparmor="DENIED"
  operation="open" namespace="root//lxd-fb1_"
  profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id"
  pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100

  Many daemons confined by Apparmor also happen to downgrade their
  privileges so they always end up looking up user/group information.

  To fix this problem, we had to backport an upstream patch which adds
  new directives to the 'nameservices' apparmor profile.

  [Test Case]

  In order to reproduce the bug, one can:

  1) launch a Focal container (named fb1 here)
  $ lxc launch images:ubuntu/focal fb1

  2) setup apparmor inside the container (already done on official Ubuntu 
images)
  $ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y

  3) install bind9
  $ lxc exec fb1 -- apt install bind9 -y

  4) check kernel logs for DENIED
  $ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F 
'profile="/usr/sbin/named"'

  or, depending on how logging is configured:

  $ dmesg | grep 'apparmor="DENIED"' | grep -F
  'profile="/usr/sbin/named"'

  Step 4, should not return anything. Because systemd is involved in the
  user/group lookups, it currently returns the following:

  audit: type=1400 audit(1586826072.115:266): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:267): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:268): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:269): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:270): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100

  [Regression Potential]

  In order to fix this issue, 3 separate patches had to be backported.
  They are simple and self-contained, especially two of them, whose
  purposes are to add the definition of the @{run} variable and then to
  add a trailing slash at the end of the "/run" pathname.

  The other patch, albeit very simple, adds three statements to the
  'nameservice' profile in order to let processes access (read-only)
  files under "/run/systemd/userdb" and
  "/proc/sys/kernel/random/boot_id".  After thinking about the possible
  cases, the only possible problem I could envision was for a program
  that, not being able to access some of these files before, will now be
  able to do that and therefore exercise a part of its codebase which
  was not being used, possibly uncovering latent bugs in this software.
  But this is not a regression of apparmor per se.

  [Original Description]

  (Description and Test Case were moved above)

  # Workaround

  1) remove systemd from nsswitch.conf
  $ lxc exec fb1 -- sed -i 's/ systemd$/ # systemd/' /etc/nsswitch.conf
  2) restart named
  $ lxc exec fb1 -- service named restart
  3) notice no more denials in kernel logs

  # Additional information

  root@fb1:~# apt-cache policy apparmor
  apparmor:
    Installed: 2.13.3-7ubuntu4
    Candidate: 2.13.3-7ubuntu4
    Version table:
   *** 2.13.3-7ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  root@fb1:~# uname -a
  Linux fb1 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Ryan Harper]

OK.

I've reviewed the kernel code, and there are no unexpected changes w.r.t
the CACHED_UUID change event.  So I don't think we will need any kernel
changes which is good.

With the small change to the 60-persistent-storage.rules to not attempt
to create a /dev/disk/by-uuid symlink for the backing device; instead we
want to only create a /dev/bcache/by-uuid symlink to the bcacheN device
(that is associated with the backing device).

# by-label/by-uuid links (filesystem metadata), skip bcache backing,caching 
devices, handled in 69-bcache.rules
ENV{ID_FS_TYPE}=="bcache", GOTO="skip_fs_uuid_enc"
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", 
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_LABEL_ENC}=="?*", 
SYMLINK+="disk/by-label/$env{ID_FS_LABEL_ENC}"
LABEL="skip_fs_uuid_enc"

And then with my previously proposed changed to 69-bcache.rules in place

https://github.com/g2p/bcache-tools/pull/29/files

The test-case works just fine.

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in bcache-tools source package in Focal:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  New
Status in systemd source package in Focal:
  Invalid
Status in bcache-tools source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  New
Status in systemd source package in Groovy:
  Invalid

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

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

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

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

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

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

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

[Touch-packages] [Bug 1880209] Re: slapd configuration does not ask for olcbackend and doesn't add one. Has to be added by hand.

[Andreas Hasenack]

Just fixed, it might take a few minutes or hours to update on the site.

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

Title:
  slapd configuration does not ask for olcbackend and doesn't add one.
  Has to be added by hand.

Status in Ubuntu Server Guide:
  Fix Released
Status in openldap package in Ubuntu:
  New

Bug description:
  Installing slapd and ldap-utils results in missing backend

  dn: olcBackend={0}mdb,cn=config

  the installer skips the installation step. Has to be added by
  ldpamodify.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: slapd 2.4.49+dfsg-2ubuntu1.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CNConfig:
   Error: command ['pkexec', '/usr/bin/ldapsearch', '-Q', '-LLL', '-Y 
EXTERNAL', '-H ldapi:///', '-b cn=config'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  CasperMD5CheckResult: skip
  Date: Fri May 22 18:27:59 2020
  InstallationDate: Installed on 2020-04-20 (32 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200417)
  SourcePackage: openldap
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1880209] Re: slapd configuration does not ask for olcbackend and doesn't add one. Has to be added by hand.

[Andreas Hasenack]

Oh, I can fix that. Let me add a server-guide task.

** Also affects: serverguide
   Importance: Undecided
   Status: New

** Changed in: serverguide
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: serverguide
   Importance: Undecided => Low

** Changed in: serverguide
   Status: New => Fix Released

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

Title:
  slapd configuration does not ask for olcbackend and doesn't add one.
  Has to be added by hand.

Status in Ubuntu Server Guide:
  Fix Released
Status in openldap package in Ubuntu:
  New

Bug description:
  Installing slapd and ldap-utils results in missing backend

  dn: olcBackend={0}mdb,cn=config

  the installer skips the installation step. Has to be added by
  ldpamodify.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: slapd 2.4.49+dfsg-2ubuntu1.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CNConfig:
   Error: command ['pkexec', '/usr/bin/ldapsearch', '-Q', '-LLL', '-Y 
EXTERNAL', '-H ldapi:///', '-b cn=config'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  CasperMD5CheckResult: skip
  Date: Fri May 22 18:27:59 2020
  InstallationDate: Installed on 2020-04-20 (32 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200417)
  SourcePackage: openldap
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1880209] Re: slapd configuration does not ask for olcbackend and doesn't add one. Has to be added by hand.

[Mario Mech]

I was just following the documentation on https://ubuntu.com/server/docs
/service-ldap and there it is present. It still was on 19.10. So I was
just wondering. Sorry!

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

Title:
  slapd configuration does not ask for olcbackend and doesn't add one.
  Has to be added by hand.

Status in openldap package in Ubuntu:
  New

Bug description:
  Installing slapd and ldap-utils results in missing backend

  dn: olcBackend={0}mdb,cn=config

  the installer skips the installation step. Has to be added by
  ldpamodify.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: slapd 2.4.49+dfsg-2ubuntu1.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CNConfig:
   Error: command ['pkexec', '/usr/bin/ldapsearch', '-Q', '-LLL', '-Y 
EXTERNAL', '-H ldapi:///', '-b cn=config'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  CasperMD5CheckResult: skip
  Date: Fri May 22 18:27:59 2020
  InstallationDate: Installed on 2020-04-20 (32 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200417)
  SourcePackage: openldap
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1880209] [NEW] slapd configuration does not ask for olcbackend and doesn't add one. Has to be added by hand.

[Ryan Tandy]

On Fri, May 22, 2020 at 04:34:52PM -, Mario Mech wrote:
>Installing slapd and ldap-utils results in missing backend
>
>dn: olcBackend={0}mdb,cn=config
>
>the installer skips the installation step. Has to be added by
>ldpamodify.

This was done intentionally as it's much more common to configure things 
per-database than per-backend. What do you need the backend entry for, 
and why is it a problem to add it yourself? Thanks.

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

Title:
  slapd configuration does not ask for olcbackend and doesn't add one.
  Has to be added by hand.

Status in openldap package in Ubuntu:
  New

Bug description:
  Installing slapd and ldap-utils results in missing backend

  dn: olcBackend={0}mdb,cn=config

  the installer skips the installation step. Has to be added by
  ldpamodify.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: slapd 2.4.49+dfsg-2ubuntu1.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CNConfig:
   Error: command ['pkexec', '/usr/bin/ldapsearch', '-Q', '-LLL', '-Y 
EXTERNAL', '-H ldapi:///', '-b cn=config'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  CasperMD5CheckResult: skip
  Date: Fri May 22 18:27:59 2020
  InstallationDate: Installed on 2020-04-20 (32 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200417)
  SourcePackage: openldap
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1880209] [NEW] slapd configuration does not ask for olcbackend and doesn't add one. Has to be added by hand.

[Mario Mech]

Public bug reported:

Installing slapd and ldap-utils results in missing backend

dn: olcBackend={0}mdb,cn=config

the installer skips the installation step. Has to be added by
ldpamodify.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: slapd 2.4.49+dfsg-2ubuntu1.2
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CNConfig:
 Error: command ['pkexec', '/usr/bin/ldapsearch', '-Q', '-LLL', '-Y EXTERNAL', 
'-H ldapi:///', '-b cn=config'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
 Error executing command as another user: Not authorized
 
 This incident has been reported.
CasperMD5CheckResult: skip
Date: Fri May 22 18:27:59 2020
InstallationDate: Installed on 2020-04-20 (32 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
SourcePackage: openldap
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apparmor apport-bug focal

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

Title:
  slapd configuration does not ask for olcbackend and doesn't add one.
  Has to be added by hand.

Status in openldap package in Ubuntu:
  New

Bug description:
  Installing slapd and ldap-utils results in missing backend

  dn: olcBackend={0}mdb,cn=config

  the installer skips the installation step. Has to be added by
  ldpamodify.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: slapd 2.4.49+dfsg-2ubuntu1.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CNConfig:
   Error: command ['pkexec', '/usr/bin/ldapsearch', '-Q', '-LLL', '-Y 
EXTERNAL', '-H ldapi:///', '-b cn=config'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  CasperMD5CheckResult: skip
  Date: Fri May 22 18:27:59 2020
  InstallationDate: Installed on 2020-04-20 (32 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200417)
  SourcePackage: openldap
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

[Simon Déziel]

After pulling apparmor 2.13.3-7ubuntu5.1 from focal-proposed:

Get:18 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 apparmor 
amd64 2.13.3-7ubuntu5.1 [494 kB]
...
Unpacking apparmor (2.13.3-7ubuntu5.1) over (2.13.3-7ubuntu5) ...
Setting up libapparmor1:amd64 (2.13.3-7ubuntu5.1) ...
Setting up apt-utils (2.0.3) ...
Setting up apparmor (2.13.3-7ubuntu5.1) ...
Installing new version of config file /etc/apparmor.d/abstractions/nameservice 
...
Reloading AppArmor profiles 
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
...

I'm happy to report the bug is fixed, thanks so much!

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

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

Title:
  /proc/sys/kernel/random/boot_id rule missing from
  abstractions/nameservice

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  On a default Focal install, systemd is used when looking up passwd and
  group information:

  # grep systemd /etc/nsswitch.conf
  passwd: files systemd
  group:  files systemd

  Daemons confined by Apparmor that also query those "databases" will
  cause this Apparmor denial:

  audit: type=1400 audit(1586825456.411:247): apparmor="DENIED"
  operation="open" namespace="root//lxd-fb1_"
  profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id"
  pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100

  Many daemons confined by Apparmor also happen to downgrade their
  privileges so they always end up looking up user/group information.

  To fix this problem, we had to backport an upstream patch which adds
  new directives to the 'nameservices' apparmor profile.

  [Test Case]

  In order to reproduce the bug, one can:

  1) launch a Focal container (named fb1 here)
  $ lxc launch images:ubuntu/focal fb1

  2) setup apparmor inside the container (already done on official Ubuntu 
images)
  $ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y

  3) install bind9
  $ lxc exec fb1 -- apt install bind9 -y

  4) check kernel logs for DENIED
  $ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F 
'profile="/usr/sbin/named"'

  or, depending on how logging is configured:

  $ dmesg | grep 'apparmor="DENIED"' | grep -F
  'profile="/usr/sbin/named"'

  Step 4, should not return anything. Because systemd is involved in the
  user/group lookups, it currently returns the following:

  audit: type=1400 audit(1586826072.115:266): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:267): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:268): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:269): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:270): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100

  [Regression Potential]

  In order to fix this issue, 3 separate patches had to be backported.
  They are simple and self-contained, especially two of them, whose
  purposes are to add the definition of the @{run} variable and then to
  add a trailing slash at the end of the "/run" pathname.

  The other patch, albeit very simple, adds three statements to the
  'nameservice' profile in order to let processes access (read-only)
  files under "/run/systemd/userdb" and
  "/proc/sys/kernel/random/boot_id".  After thinking about the possible
  cases, the only possible problem I could envision was for a program
  that, not being able to access some of these files before, will now be
  able to do that and therefore exercise a part of its codebase which
  was not being used, possibly uncovering latent bugs in this software.
  But this is not a regression of apparmor per se.

  [Original Description]

  (Description and Test Case were moved above)

  # Workaround

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

[Serhiy Zahoriya]

You need to either execute these commands after upgrade and _before_
rebooting or chroot from a LiveUSB boot.

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

Title:
  LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting
  for device /dev/mapper/s5lp8--v g-home

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed

Bug description:
  After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no 
longer mounted.
  During boot the console shows Timed out waiting for device 
/dev/mapper/s5lp8--vg-home

  Please see the attached dist-upgrade logs and console output for more
  detail.

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

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

[Touch-packages] [Bug 1879206] Re: cups hplip not install printer

[Till Kamppeter]

Please

- Remove the .snap of HPLIP, it is experimental

- Remove any HPLIP version installed directly from HP

- Re-install Ubuntu's HPLIP via the command:

  sudo apt install --reinstall printer-driver-hpcups printer-driver-
postscript-hp libsane-hpaio hplip-gui hplip hplip-data libhpmud0

  Please post the output of this command here.

- Remove your current print queues with the commands:

  lpadmin -x DeskJet_3630
  lpadmin -x HP_DeskJet_3630_series

- Unplug the printer from USB and re-plug it. Does a new print queue get
created ("lpstat -v" should show it)? Can you print using this queue?

- Could you create a driverless print queue (this queue does not use
HPLIP but common, manufacturer-independent communication protocols of
the printer)? Use the command

  lpadmin -p DJ3630 -E -v
ipp://HP%20DeskJet%203630%20series%20%5B9B20BB%5D._ipp._tcp.local/ -m
everywhere

  Can you print with this print queue?

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

[veribaka]

I too tried to upgrade from 18.04 and ended up with a busybox, Ubuntu
not finding my vg. Not sure how to enter those commands from a busybox
Steve.

Re-imaging the device with 18.04 for the time being.

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

Title:
  LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting
  for device /dev/mapper/s5lp8--v g-home

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed

Bug description:
  After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no 
longer mounted.
  During boot the console shows Timed out waiting for device 
/dev/mapper/s5lp8--vg-home

  Please see the attached dist-upgrade logs and console output for more
  detail.

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

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

[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit

[Sven Hartrumpf]

Archlinux fixed this bug today, now in testing stage. Any news for
Ubuntu?

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

Title:
  pgrep reports error "cannot allocate" when run without stack limit

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  If you have no stack limit (ulimit -S -s unlimited), any pgrep call
  will fail with an error:

  > pgrep vim
  pgrep: cannot allocate 4611686018427387903 bytes

  If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is
  very slow:

  > time pgrep vim
  2196
  real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444

  The relevant upstream bug report could be: 
https://gitlab.com/procps-ng/procps/-/issues/152
  Archlinux bug report: https://bugs.archlinux.org/task/66093

  procps:
Installed: 2:3.3.16-1ubuntu2
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

[Touch-packages] [Bug 1870359] Autopkgtest regression report (network-manager/1.22.10-1ubuntu2.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted network-manager (1.22.10-1ubuntu2.1) 
for focal have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#network-manager

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  * Regression potential
  the change is only updating the iptables binary location, there shouldn't be 
any code impact out of having the command working on systems without usrmerge 
when it was not before

  -

  
  I have a machine with a wired network connection and a wifi card. I've been 
using the machine as a wireless router and server in my house. I've attached a 
screenshot of the Wi-Fi network settings. It looks as expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100
   169.254.0.0/16 dev eth0 scope link metric 1000
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:

  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

[Eric Desrochers]

I tested with debian buster and I wasn't able to reproduce (w/o quiet
parameter)

I'm not yet too sure if it's a pure initramfs-tools or something
introduced by a package hooks.

I first thought that plymouth could have beeb a potential candidate, but
I disabled it and even purge it and problem persisted.

- Eric

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

Title:
  machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel get stucks at boot if console=ttyS* is specified in the kernel
  cmdline and that serial HW isn't available on the system.

  Reproduced with:
  4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next 
(mainline)

  Removing the non-existent 'console=ttyS*' parameter fixes the
  situation.

  I tested it using KVM/qemu, but it has been brought to my attention
  that it was reproducible in VMware as well.

  I think it is safe to say that it is unlikely to be specifics to a
  certain virtualization technology type.

  Didn't test on baremetal yet.

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

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

[Touch-packages] [Bug 1880198] [NEW] Ubuntu as bluetooth speaker - volume on bluetooth client ignored

[Krister]

Public bug reported:

I'm using my 20.04 system as a media center. It's got a bluetooth
adapter plugged into a USB port. I can connect to the system with my
phone and ipad as an A2DP source and play music.

The problem is that the volume on the source device is not respected

When the volume on the source device goes to 0, the sound is muted as
expected, but any other volume on the source device leads to the same
volume on the Ubuntu server. The only way to adjust the volume is from
the server.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  kodi   1455 F pulseaudio
 /dev/snd/controlC0:  kodi   1455 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 22 16:42:57 2020
InstallationDate: Installed on 2015-09-30 (1695 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2404
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H97M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2404:bd03/04/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


** Tags: amd64 apport-bug focal wayland-session

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

Title:
  Ubuntu as bluetooth speaker - volume on bluetooth client ignored

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm using my 20.04 system as a media center. It's got a bluetooth
  adapter plugged into a USB port. I can connect to the system with my
  phone and ipad as an A2DP source and play music.

  The problem is that the volume on the source device is not respected

  When the volume on the source device goes to 0, the sound is muted as
  expected, but any other volume on the source device leads to the same
  volume on the Ubuntu server. The only way to adjust the volume is from
  the server.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kodi   1455 F pulseaudio
   /dev/snd/controlC0:  kodi   1455 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 22 16:42:57 2020
  InstallationDate: Installed on 2015-09-30 (1695 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2404
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2404:bd03/04/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1879211] Re: Charging my cellphone through usb breaks internet connection.

[Tomás Zubiri]

Sensible. If that were the case, a solution would rely in the capacity
of the network manager to detect that the new route does not work,(and
that the previous one did)

My naïve solution would be to ping a reliable server (I use 8.8.8.8) and
delete the new route if it timesout.

Additionally, if the new cabled connection were successful initially,
but later stopped working, shouldn't the network fallback to the
previous connection? A similar thing already happens when multiple dns
servers are specified.

2 functionalities failed for this bug to occur. (a third one if you
count my phone presenting itself as a router when it can't do that, but
that's not within Ubuntu's jurisdiction... is it?)

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

Title:
  Charging my cellphone through usb breaks internet connection.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I don't know what package is responsible for this. I entered iptables
  because the ip command was not recognized as a package.

  I use the ip route to debug internet problems. Here it is before plugging my 
cellphone through usb:
  #ip route
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  Here it is after I plug my cellphone
  #ip route
  default via 192.168.42.129 dev enp0s20f0u1 proto dhcp metric 100 
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.42.0/24 dev enp0s20f0u1 proto kernel scope link src 192.168.42.114 
metric 100 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  So my computer is trying to access all ips using my cellphone as a
  router, which of course fails.

  the command "sudo ip route del default" followed by "sudo ip route add
  default via 192.168.0.1 dev wlp2s0" restores my connection.

  Thank you for your attention. I'm available to answer any questions
  and fix this bug. Reporting this bug was already effort diverted from
  my other tasks, so let's make this count no matter how deep it cuts.

  P.S: I went ahead and marked this bug as a security vulnerability
  because I can think of ways this can be exploited, especially if the
  cellphone can trigger the bug and route traffic so that the user
  doesn't suspect it. If you feel the security impact is small and that
  there are other more important security issues, feel free to unmark it
  and we can deal with it's usability impact, which is probably more
  impactful.

  Regards,
  Tomás.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iptables 1.6.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 22:59:02 2020
  InstallationDate: Installed on 2019-02-08 (464 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1880190] [NEW] No sound after suspend/resume

[Hélio Márcio Filho]

Public bug reported:

After suspend the system while Spotify was playing when I resumed again
my output device was gone.

Instead of "Speakers - Built in Audio" was "Dummy Output". I had to run
"pulseaudio -k" to put audio working again.

More info:

Ubuntu Ubuntu 20.04 LTS
Spotify: Version 1.1.26.501.gbe11e53b-15 (installed via snap).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  helio 19185 F pulseaudio
 /dev/snd/pcmC0D0p:   helio 19185 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 22 14:36:21 2020
InstallationDate: Installed on 2020-05-05 (16 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/14/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.0
dmi.board.name: 0V736W
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd05/14/2019:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn0V736W:rvrA01:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7560
dmi.product.sku: 0782
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  No sound after suspend/resume

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After suspend the system while Spotify was playing when I resumed
  again my output device was gone.

  Instead of "Speakers - Built in Audio" was "Dummy Output". I had to
  run "pulseaudio -k" to put audio working again.

  More info:

  Ubuntu Ubuntu 20.04 LTS
  Spotify: Version 1.1.26.501.gbe11e53b-15 (installed via snap).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  helio 19185 F pulseaudio
   /dev/snd/pcmC0D0p:   helio 19185 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 22 14:36:21 2020
  InstallationDate: Installed on 2020-05-05 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0V736W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd05/14/2019:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn0V736W:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7560
  dmi.product.sku: 0782
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

[Julian Andres Klode]

There are two things:

- On servers, ubuntu-server depends on mdadm, so removing mdadm also
removes ubuntu-server package, which means it's not really supported

- In general, the installers don't offer installing like that.

I don't know why we did not have a task for xenial.

** Description changed:

  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.
  
  [Test case]
  
- 1. Install server with subiquity to LVM
+ 1. Install server to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
- 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv
+ 5. Run lvconvert -m1 --type raid1 ubuntu-vg/ubuntu-lv
  
  Reboot and check that it still boots.
  
  6. Remove mdadm
  7. Upgrade to lvm2 from proposed
  
  Reboot and check that it still boots.
  
  8. Downgrade lvm2 to release
  
  Reboot and check that it fails to boot
  
  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.
  
  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.
  
  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!
  
  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it to
  be a temporary workaround and I'll get the new 4.2.0 kernel work with
  Wily in days.

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Released
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/ubuntu-lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

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

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

[Touch-packages] [Bug 1880182] [NEW] HDMI port is not working

[Ghassan]

Public bug reported:

hdmi port is not working.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
Uname: Linux 4.15.0-101-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 22 15:26:04 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 rtl8821ce, v5.5.2_34066.20200325, 4.15.0-101-generic, x86_64: installed
 rtl8821ce, v5.5.2_34066.20200325, 4.15.0-99-generic, x86_64: installed
 virtualbox, 5.2.34, 4.15.0-101-generic, x86_64: installed
 virtualbox, 5.2.34, 4.15.0-99-generic, x86_64: installed
 wireguard, 1.0.20200506, 4.15.0-101-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:5079]
InstallationDate: Installed on 2020-04-02 (50 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20RD004FMH
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic 
root=/dev/mapper/username--vg-root ro quiet splash
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/29/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R16ET21W (1.07 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20RD004FMH
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR16ET21W(1.07):bd11/29/2019:svnLENOVO:pn20RD004FMH:pvrThinkPadE15:rvnLENOVO:rn20RD004FMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E15
dmi.product.name: 20RD004FMH
dmi.product.version: ThinkPad E15
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101+git2005200630.bf602a~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005220730.685e79~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2~git2005220730.685e79~oibaf~b
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.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+git2004151930.384539~oibaf~b
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git2005151930.5ca3ac~oibaf~b
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.16+git2004030730.5444ca~oibaf~b

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


** Tags: amd64 apport-bug bionic third-party-packages 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/1880182

Title:
  HDMI port is not working

Status in xorg package in Ubuntu:
  New

Bug description:
  hdmi port is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 22 15:26:04 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821ce, v5.5.2_34066.20200325, 4.15.0-101-generic, x86_64: installed
   rtl8821ce, v5.5.2_34066.20200325, 4.15.0-99-generic, x86_64: installed
   virtualbox, 5.2.34, 4.15.0-101-generic, x86_64: installed
   virtualbox, 5.2.34, 4.15.0-99-generic, x86_64: installed
   wireguard, 1.0.20200506, 4.15.0-101-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:5079]
  InstallationDate: Installed on 2020-04-02 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20RD004FMH
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic 
root=/dev/mapper/username--vg-root ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R16ET21W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20RD004FMH
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR16ET21W(1.07):bd11/29/2019:svnLENOVO:pn20RD004FMH:pvrThinkPadE15:rvnLENOVO:rn20RD004FMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E15
  dmi.product.name: 20RD004FMH
  

[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

[MegaBrutal]

Sorry, I didn't actually test Focal and Groovy.

Xenial will be supported for about a year, so I think it worth to fix it
there as well; however it's relative what worth to fix and what not, as
most users probably left Xenial behind already or applied a workaround
if they were ever affected by this issue. On the other hand it can be a
real pain if you don't know about this and just happen to convert your
root LV to raid1 and then your system doesn't boot.

"The supported configuration for raid1 is mdadm after all, not removing
mdadm and the meta packages that depend on it and using lvm's raid
support."

I don't know where LVM over DM-RAID is defined as the "supported
configuration" as opposed to RAID1 over LVM. I always thought about them
as equal alternatives for slightly different use cases. My rule of thumb
is when you can afford to get identical sized disks and mirror
everything, go with LVM over DM-RAID. If you can't guarantee to have
identical sized disks and need a more dynamic solution, then RAID1 over
LVM (i.e. using LVM's raid1 support) is more suitable. I recommend the
former in productive server environments and the latter in smaller SOHO,
home servers and personal computers. If one of my disks goes bye-bye, I
wouldn't want to reinstall my system or lose my documents, so I have my
/ and /home LVs in raid1. However I couldn't care less about my Steam
library because I can just re-download the games anytime, so I don't
have it mirrored, as I'd rather not want it to use twice the precious
disk space.

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Released
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

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

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

[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path

[Francis Ginther]

** Tags added: id-5ec69c5a5bc4156ecefb75a0

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

Title:
  ssh can't call a binary from a snap without the full path

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Groovy:
  Fix Released
Status in openssh source package in Groovy:
  Confirmed
Status in pam source package in Groovy:
  Confirmed
Status in snapd source package in Groovy:
  Confirmed

Bug description:
  ssh can't call a binary from a snap, it will only work using the full
  path.

  Let's say I have the hello snap installed in 192.168.122.24. Then:

  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio@192.168.122.24's password:
  bash: hello: command not found
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio@192.168.122.24's password:
  Hello, world!

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

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

[Touch-packages] [Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home

[Francis Ginther]

** Tags added: id-5ec6a06d9ddd891b690ef2e4

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

Title:
  LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting
  for device /dev/mapper/s5lp8--v g-home

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed

Bug description:
  After upgrading an LPAR configured with LVM from 18.04 to 20.04 /home is no 
longer mounted.
  During boot the console shows Timed out waiting for device 
/dev/mapper/s5lp8--vg-home

  Please see the attached dist-upgrade logs and console output for more
  detail.

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

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

[Touch-packages] [Bug 1876600] Re: cookie overruns can cause org.freedesktop.systemd1 dbus to hang

[Heitor Alves de Siqueira]

Validated systemd 237-3ubuntu10.41 from bionic-proposed, according to
test case from bug description:

ubuntu@systemd-cookie-bionic:~$ dpkg -l systemd | grep systemd
ii  systemd237-3ubuntu10.41 amd64system and service manager
ubuntu@systemd-cookie-bionic:~$ gcc -Wall test.c -o cookie -lsystemd -g
ubuntu@systemd-cookie-bionic:~$ gdb --batch --command=test.gdb --args ./cookie
Breakpoint 1 at 0xe61: file test.c, line 38.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
(15s) cookie: 0x0001reply-cookie: 0x0001

Breakpoint 1, print_unit_path (bus=0x55757290) at test.c:38
38  r = sd_bus_message_new_method_call(bus, ,
$1 = 0x1
$2 = 0xff00
(15s) cookie: 0x8000reply-cookie: 0x8000
(29s) cookie: 0x8001reply-cookie: 0x8001
(43s) cookie: 0x8002reply-cookie: 0x8002


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

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

Title:
  cookie overruns can cause org.freedesktop.systemd1 dbus to hang

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Long-running services overflow the sd_bus->cookie counter, causing further 
communication with org.freedesktop.systemd1 to stall.

  [Description]
  Systemd dbus messages include a "cookie" value to uniquely identify them in 
their bus context. This value is obtained from the bus header, and incremented 
for each exchanged message in the same bus object. For services that run for 
longer periods of time and keep communicating through dbus, it's possible to 
overflow the cookie value, causing further messages to the 
org.freedesktop.systemd1 dbus to fail. This can lead to these services becoming 
unresponsive, as they get stuck trying to communicate with invalid bus cookie 
values.

  This issue has been fixed upstream by the commit below:
  -  sd-bus: deal with cookie overruns (1f82f5bb4237)

  $ git describe --contains 1f82f5bb4237
  v242-rc1~228

  $ rmadison systemd
   systemd | 229-4ubuntu4 | xenial  | source, ...
   systemd | 229-4ubuntu21.27 | xenial-security | source, ...
   systemd | 229-4ubuntu21.27 | xenial-updates  | source, ...
   systemd | 229-4ubuntu21.28 | xenial-proposed | source, ...
   systemd | 237-3ubuntu10| bionic  | source, ...
   systemd | 237-3ubuntu10.38 | bionic-security | source, ...
   systemd | 237-3ubuntu10.39 | bionic-updates  | source, ...
   systemd | 237-3ubuntu10.40 | bionic-proposed | source, ... <
   systemd | 242-7ubuntu3 | eoan| source, ...

  Releases starting with Eoan already have this fix.

  [Test Case]
  There doesn't seem to be an easy test case for this, as the cookie values 
start at zero and won't overflow until (1<<32). There have been reports from 
users hitting this on Kubernetes clusters continuously running for longer 
periods (~5 months).
  Using GDB, we can construct an artificial test case to test the cookie 
overflow. The test case below performs the following steps:

  1. Create a new system bus object through sd_bus_default_system()
  2. Allocate and append a new method_call message to the bus
  3. Send the message through sd_bus_call()
  4. Handle the response message and free up the message objects

  It's essentially the example code from the
  sd_bus_message_new_method_call() manpage, with minor modifications:
  this is done continuously, to keep incrementing the bus cookie value.
  We step in with GDB when it reaches 0x1, and set its value to
  0xff00 which then causes the test program to fail shortly
  afterwards. An example test run of an impacted system:

  ubuntu@bionic:~$ gcc -Wall test.c -o cookie -lsystemd -g
  ubuntu@bionic:~$ gdb --batch --command=test.gdb --args ./cookie
  Breakpoint 1 at 0xe61: file test.c, line 38.
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  (16s) cookie: 0x0001reply-cookie: 0x0001

  Breakpoint 1, print_unit_path (bus=0x55757290) at test.c:38
  38  r = sd_bus_message_new_method_call(bus, ,
  $1 = 0x1
  $2 = 0xff00
  Call failed: Operation not supported
  Sleeping and retrying...
  Call failed: Invalid argument
  Assertion 'm->n_ref > 0' failed at 
../src/libsystemd/sd-bus/bus-message.c:934, function sd_bus_message_unref(). 
Aborting.

  Program received signal SIGABRT, Aborted.
  __GI_raise (sig=sig@entry=0x6) at ../sysdeps/unix/sysv/linux/raise.c:51
  51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.

  To compile and debug the 

[Touch-packages] [Bug 1878517] Re: please apply bash 5.0 patch 17

[Francis Ginther]

** Tags added: id-5ec6a2b21639eb7938a123eb

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

Title:
  please apply bash 5.0 patch 17

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

Bug description:
  I am using Ubuntu 20.04 for development and has hit a bug in bash 5.0
  patch 16.

  I can't reproduce it in pure bash, but with bats from
  https://github.com/bats-core/bats-core/ it is very easy to repro:

  ```
  # cat << EOF > ya.bats
  check() {
echo "check $@"
ls -l /proc/self/fd
  }

  @test "here file" {
check -p <(echo "hey")
false
  }
  EOF

  $ bats ya.bats
  ```

  Normally the output should contain the line

 lr-x-- 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918]

  which is a result of a "here file" created by bash via <(echo "hey").

  In my testing, about 50% of runs don't have /dev/fd/63 listed.

  I found out this is a manifest of a bug introduced in bash 5.0 patch
  16 (see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-016)

  The bug is fixed in 5.0 patch 17 (see
  http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-017).

  Please update bash to patchlevel 17.

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

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

[Touch-packages] [Bug 1774843] Re: apport python exception for python versions which python-apt is not built on

[Bart Goeman]

Łukasz's remark on focal: +1

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

Title:
  apport python exception for python versions which python-apt is not
  built on

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in python3.7 package in Ubuntu:
  Invalid
Status in python3.8 package in Ubuntu:
  Invalid
Status in apport source package in Bionic:
  Fix Committed
Status in python3.7 source package in Bionic:
  Won't Fix
Status in python3.8 source package in Bionic:
  Won't Fix
Status in apport source package in Eoan:
  Fix Committed
Status in python3.7 source package in Eoan:
  Won't Fix
Status in python3.8 source package in Eoan:
  Won't Fix
Status in apport source package in Focal:
  Invalid
Status in python3.7 source package in Focal:
  Invalid
Status in python3.8 source package in Focal:
  Invalid

Bug description:
  [Impact]
  apport's python crash handler runs for every installed version of python e.g. 
on Ubuntu 18.04 LTS it will run for crashes with python3.6 or python3.7 as an 
interpreter. However, python apt modules are only available for the the 
supported version of python so the crash handler generates an exception which 
is annoying.

  [Test Case]
  1) Install the non-default version of python3 e.g. python3.7 on Ubuntu 18.04 
LTS.
  2) Run 'python3.7 -c 'print hello' and observe a Traceback re apt_pkg not 
being found.

  With the version of python3-apport from -proposed you'll not receive
  the Traceback from step # 2.

  [Regression Potential]
  Its possible the crash handler change is incorrect so it should be confirmed 
that we still get python crashes about the system version of python. One way to 
do this is to run 'apport-cli coreutils < /dev/null'.

  [NOTE]
  It isn't necessary to fix this in Ubuntu 20.04 LTS, as there is only 
python3.8 available, so I haven't.

  [Original Description]
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  This exception handler has a dependency on apt_pkg, which is a binary that is 
not compatible with python3.7 it seems (you can't import it, see below)

  As a result, whenever I run a python3.7 script and run into an exception 
(which happens often when writing code), I get an additional exception in the 
exception handler + a copy of the original exception, so three stacktraces in 
total.
  A solution would be to only install the exception hook for the system python  
i.e. python3.6

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

  apport: 2.20.9-0ubuntu7
  python-apt: 1.6.0
  python3.7: 3.7.0~b3-1

  Demo with a trivial error:
  $ python3 -c 'print hello'
    File "", line 1
  print hello
    ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  $ python3.7 -c 'print hello'
    File "", line 1
  print hello
    ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  Error in sys.excepthook:
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
  from apport.fileutils import likely_packaged, get_recent_crashes
    File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

  from apport.report import Report
    File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
  import apport.fileutils
    File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

  from apport.packaging_impl import impl as packaging
    File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in 

  import apt
    File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
  import apt_pkg
  ModuleNotFoundError: No module named 'apt_pkg'

  Original exception was:
    File "", line 1
  print hello
    ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  Python 3.6.5 (default, Apr  1 2018, 05:46:30)
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >>> import apt_pkg
  >>> apt_pkg.__file__
  '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so'
  >>>

  Python 3.7.0b3 (default, Mar 30 2018, 04:35:22)
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >> import apt_pkg
  Traceback (most recent call last):
    File "", line 1, in 
  ModuleNotFoundError: No module named 'apt_pkg'

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

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

[Touch-packages] [Bug 1879751] Re: ALSA sees my intel soundcards but pulseaudio does not. Error is : "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1/m

[Phil Macias]

Thank you, but didn't help. "debuild" and plain old make failed:

...
  CCLD alsa-mixer-path-test
/usr/bin/ld: ./.libs/libalsa-util.so: undefined reference to 
`snd_use_case_parse_ctl_elem_id'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:6955: alsa-mixer-path-test] Error 1
make[3]: Leaving directory '/root/DEV/pulseaudio-13.99.1/src'
make[2]: *** [Makefile:5401: all] Error 2
make[2]: Leaving directory '/root/DEV/pulseaudio-13.99.1/src'
make[1]: *** [Makefile:833: all-recursive] Error 1
make[1]: Leaving directory '/root/DEV/pulseaudio-13.99.1'
make: *** [Makefile:648: all] Error 2


# ~/DEV/pulseaudio-13.99.1# dpkg -l | grep libasound
ii  libasound2:amd64   1.2.2-2.1
  amd64shared library for ALSA applications
ii  libasound2:i3861.2.2-2.1
  i386 shared library for ALSA applications
ii  libasound2-data1.2.2-2.1
  all  Configuration files and profiles for ALSA drivers
ii  libasound2-dev:amd64   1.2.2-2.1
  amd64shared library for ALSA applications -- development files
ii  libasound2-plugins:amd64   1.2.2-1ubuntu1   
  amd64ALSA library additional plugins
rc  libasound2-plugins:i3861.2.2-1ubuntu1   
  i386 ALSA library additional plugins

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

Title:
  ALSA sees my intel soundcards but pulseaudio does not.  Error is :
  "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-
  card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined
  symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9"

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  ALSA sees my intel soundcards but pulseaudio does not.

  'pavucontrol' sees only a "Dummy" device.

  #journalctl|grep pulse' gives "pulseaudio[18489]: Failed to open
  module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so:
  /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol:
  snd_use_case_parse_ctl_elem_id, version ALSA_0.9"

  Making pulseaudio from source fixes the problem/

  (Linux CF-C2CQAZXCM 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29
  14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux 20.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  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/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 20 12:48:07 2020
  InstallationDate: Installed on 2015-04-29 (1848 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-05-05 (15 days ago)
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.00L21
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: CFC2-2
  dmi.board.vendor: Panasonic Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Panasonic Corporation
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.00L21:bd09/12/2018:svnPanasonicCorporation:pnCF-C2CQAZXCM:pvr002:rvnPanasonicCorporation:rnCFC2-2:rvr1:cvnPanasonicCorporation:ct10:cvr001:
  dmi.product.family: CFC2-2
  dmi.product.name: CF-C2CQAZXCM
  dmi.product.sku: CF-C2CQAZXCM
  dmi.product.version: 002
  dmi.sys.vendor: Panasonic Corporation
  mtime.conffile..etc.init.d.apport: 2020-02-26T22:18:45

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

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

[Touch-packages] [Bug 1774843] Re: apport python exception for python versions which python-apt is not built on

[Bart Goeman]

Verified on Ubuntu 19.10
on 19.10 python3-apt is built for pyton3.7, the system python for 19.10
so i tested against python3.8 from universe.

bart@DH170:~$ apt-cache policy python3-apport
python3-apport:
  Geïnstalleerd: 2.20.11-0ubuntu8.9
  Kandidaat: 2.20.11-0ubuntu8.9
  Versietabel:
 *** 2.20.11-0ubuntu8.9 400
400 http://nl.archive.ubuntu.com/ubuntu eoan-proposed/main amd64 
Packages
400 http://nl.archive.ubuntu.com/ubuntu eoan-proposed/main i386 Packages
100 /var/lib/dpkg/status
 2.20.11-0ubuntu8.8 500
500 http://nl.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages
500 http://nl.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages
500 http://nl.archive.ubuntu.com/ubuntu eoan-security/main amd64 
Packages
500 http://nl.archive.ubuntu.com/ubuntu eoan-security/main i386 Packages
 2.20.11-0ubuntu8 500
500 http://nl.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
500 http://nl.archive.ubuntu.com/ubuntu eoan/main i386 Packages


bart@DH170:~$ python3.7 -c 'import apt_pkg'
bart@DH170:~$ python3.8 -c 'import apt_pkg'
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'apt_pkg'
bart@DH170:~$ python3.8 -c 'print hello'
  File "", line 1
print hello
  ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)?

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

Title:
  apport python exception for python versions which python-apt is not
  built on

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in python3.7 package in Ubuntu:
  Invalid
Status in python3.8 package in Ubuntu:
  Invalid
Status in apport source package in Bionic:
  Fix Committed
Status in python3.7 source package in Bionic:
  Won't Fix
Status in python3.8 source package in Bionic:
  Won't Fix
Status in apport source package in Eoan:
  Fix Committed
Status in python3.7 source package in Eoan:
  Won't Fix
Status in python3.8 source package in Eoan:
  Won't Fix
Status in apport source package in Focal:
  Invalid
Status in python3.7 source package in Focal:
  Invalid
Status in python3.8 source package in Focal:
  Invalid

Bug description:
  [Impact]
  apport's python crash handler runs for every installed version of python e.g. 
on Ubuntu 18.04 LTS it will run for crashes with python3.6 or python3.7 as an 
interpreter. However, python apt modules are only available for the the 
supported version of python so the crash handler generates an exception which 
is annoying.

  [Test Case]
  1) Install the non-default version of python3 e.g. python3.7 on Ubuntu 18.04 
LTS.
  2) Run 'python3.7 -c 'print hello' and observe a Traceback re apt_pkg not 
being found.

  With the version of python3-apport from -proposed you'll not receive
  the Traceback from step # 2.

  [Regression Potential]
  Its possible the crash handler change is incorrect so it should be confirmed 
that we still get python crashes about the system version of python. One way to 
do this is to run 'apport-cli coreutils < /dev/null'.

  [NOTE]
  It isn't necessary to fix this in Ubuntu 20.04 LTS, as there is only 
python3.8 available, so I haven't.

  [Original Description]
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  This exception handler has a dependency on apt_pkg, which is a binary that is 
not compatible with python3.7 it seems (you can't import it, see below)

  As a result, whenever I run a python3.7 script and run into an exception 
(which happens often when writing code), I get an additional exception in the 
exception handler + a copy of the original exception, so three stacktraces in 
total.
  A solution would be to only install the exception hook for the system python  
i.e. python3.6

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

  apport: 2.20.9-0ubuntu7
  python-apt: 1.6.0
  python3.7: 3.7.0~b3-1

  Demo with a trivial error:
  $ python3 -c 'print hello'
    File "", line 1
  print hello
    ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  $ python3.7 -c 'print hello'
    File "", line 1
  print hello
    ^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  Error in sys.excepthook:
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
  from apport.fileutils import likely_packaged, get_recent_crashes
    File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

  from apport.report import Report
    File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
  import apport.fileutils
    File 

[Touch-packages] [Bug 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

[Timo Aaltonen]

Hello Simon, or anyone else affected,

Accepted apparmor into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apparmor/2.13.3-7ubuntu5.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apparmor (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  /proc/sys/kernel/random/boot_id rule missing from
  abstractions/nameservice

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  On a default Focal install, systemd is used when looking up passwd and
  group information:

  # grep systemd /etc/nsswitch.conf
  passwd: files systemd
  group:  files systemd

  Daemons confined by Apparmor that also query those "databases" will
  cause this Apparmor denial:

  audit: type=1400 audit(1586825456.411:247): apparmor="DENIED"
  operation="open" namespace="root//lxd-fb1_"
  profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id"
  pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100

  Many daemons confined by Apparmor also happen to downgrade their
  privileges so they always end up looking up user/group information.

  To fix this problem, we had to backport an upstream patch which adds
  new directives to the 'nameservices' apparmor profile.

  [Test Case]

  In order to reproduce the bug, one can:

  1) launch a Focal container (named fb1 here)
  $ lxc launch images:ubuntu/focal fb1

  2) setup apparmor inside the container (already done on official Ubuntu 
images)
  $ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y

  3) install bind9
  $ lxc exec fb1 -- apt install bind9 -y

  4) check kernel logs for DENIED
  $ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F 
'profile="/usr/sbin/named"'

  or, depending on how logging is configured:

  $ dmesg | grep 'apparmor="DENIED"' | grep -F
  'profile="/usr/sbin/named"'

  Step 4, should not return anything. Because systemd is involved in the
  user/group lookups, it currently returns the following:

  audit: type=1400 audit(1586826072.115:266): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:267): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:268): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:269): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100
  audit: type=1400 audit(1586826072.115:270): apparmor="DENIED" 
operation="open" namespace="root//lxd-fb1_" 
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 
comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100

  [Regression Potential]

  In order to fix this issue, 3 separate patches had to be backported.
  They are simple and self-contained, especially two of them, whose
  purposes are to add the definition of the @{run} variable and then to
  add a trailing slash at the end of the "/run" 

[Touch-packages] [Bug 1879702] Re: The software properties screen freezes when I update the software cache

[Uygar Demir Koç]

I saved the output of 'journalctl -b 0' to a file. It's in the
attachments.

** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1879702/+attachment/5375608/+files/journalctl.log

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

Title:
  The software properties screen freezes when I update the software
  cache

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  I am currently using Ubuntu 20.04, but I had the same problem in
  19.10. When I make changes to the software resources, when closing the
  program, "Update the software cache?" I come across the question. If I
  say yes, it updates the cache but the window freezes. It cannot be
  closed in any way.

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

  
  'apt-cache policy software-properties':
  software-properties:
Installed: (none)
Candidate: (none)
Release schedule:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.9
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 16:08:11 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2017-06-10 (1075 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  Python3Details: /usr/local/bin/python3.7, Python 3.7.2, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to focal on 2020-05-11 (8 days ago)

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

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

[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Rajasekharan N]

I am an affected soul. See bug 1876238 and bug 1878327 which were marked
as duplicate.

I had earlier tested the patch from Kai-Heng Feng's (kaihengfeng) PPA,
and it was working fine.

I had enabled to receive Pre-released updates. I downloaded the proposed
update (1:13.99.1-1ubuntu3.3), applied it, and tested the update.

The internal speakers, both the headphone jacks and the internal mic,
all are working fine now.

Unplugged the headphones and plugged them again and again. Sound can be
heard.

Sound is getting automatically redirected to the headphones when
connected to jack interfaces and back to the internal speakers when
headphones are unplugged.

Tested/tried multiple times and is working fine every time.

Thank you.

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

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

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

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

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

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

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

[Timo Aaltonen]

Hello Krister, or anyone else affected,

Accepted network-manager into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.22.10-1ubuntu2.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: network-manager (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  * Regression potential
  the change is only updating the iptables binary location, there shouldn't be 
any code impact out of having the command working on systems without usrmerge 
when it was not before

  -

  
  I have a machine with a wired network connection and a wifi card. I've been 
using the machine as a wireless router and server in my house. I've attached a 
screenshot of the Wi-Fi network settings. It looks as expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100
   169.254.0.0/16 dev eth0 scope link metric 1000
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:

  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

[Julian Andres Klode]

That's certainly incorrect, lvm2 was fixed in focal (and hence groovy).
That only leaves xenial, but updating xenial close to its EOL for
something as unusual as this seems unneccessary. The supported
configuration for raid1 is mdadm after all, not removing mdadm and the
meta packages that depend on it and using lvm's raid support.

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Released
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server with subiquity to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

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

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

[Touch-packages] [Bug 1880126] [NEW] After resume from suspend the desktop image is broken

[thomick]

Public bug reported:

Wheb you resume from suspend Ubuntu 20.04 and unlock your session, the
desktop image is corrupted as shown on screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: nvidia wl
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 22 11:43:37 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-31-generic, x86_64: installed
 nvidia-340, 340.108, 5.4.0-29-generic, x86_64: installed
 nvidia-340, 340.108, 5.4.0-31-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation G98M [GeForce 9200M GS] [10de:06e8] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company G98M [GeForce 9200M GS] [103c:3629]
InstallationDate: Installed on 2020-04-27 (24 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=2bd6e5fb-c1e4-4103-902e-36c3fd5ea356 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/10/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3629
dmi.board.vendor: Quanta
dmi.board.version: 18.3E
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd07/10/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnQuanta:rn3629:rvr18.3E:cvnQuanta:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.sku: NG735EA#ABZ
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal ubuntu

** Attachment added: "Snímek obrazovky pořízený 2020-05-22 11-45-16.png"
   
https://bugs.launchpad.net/bugs/1880126/+attachment/5375575/+files/Sn%C3%ADmek%20obrazovky%20po%C5%99%C3%ADzen%C3%BD%202020-05-22%2011-45-16.png

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

Title:
  After resume from suspend the desktop image is broken

Status in xorg package in Ubuntu:
  New

Bug description:
  Wheb you resume from suspend Ubuntu 20.04 and unlock your session, the
  desktop image is corrupted as shown on screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia wl
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics 

[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

[Timo Aaltonen]

Hello hugh, or anyone else affected,

Accepted pulseaudio into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.8 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: pulseaudio (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

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

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

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

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

  [Expected result]
  Can detect external headset

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

  [Regression Potential]
  Low.

  [Failure rate]
  100%

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

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

[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Timo Aaltonen]

Hello Roman, or anyone else affected,

Accepted pulseaudio into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.3 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags removed: verification-failed verification-failed-focal
** Tags added: verification-needed verification-needed-focal

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

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

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

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

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

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

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Touch-packages] [Bug 1879211] Re: Charging my cellphone through usb breaks internet connection.

[Sebastien Bacher]

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  Charging my cellphone through usb breaks internet connection.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I don't know what package is responsible for this. I entered iptables
  because the ip command was not recognized as a package.

  I use the ip route to debug internet problems. Here it is before plugging my 
cellphone through usb:
  #ip route
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  Here it is after I plug my cellphone
  #ip route
  default via 192.168.42.129 dev enp0s20f0u1 proto dhcp metric 100 
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.42.0/24 dev enp0s20f0u1 proto kernel scope link src 192.168.42.114 
metric 100 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  So my computer is trying to access all ips using my cellphone as a
  router, which of course fails.

  the command "sudo ip route del default" followed by "sudo ip route add
  default via 192.168.0.1 dev wlp2s0" restores my connection.

  Thank you for your attention. I'm available to answer any questions
  and fix this bug. Reporting this bug was already effort diverted from
  my other tasks, so let's make this count no matter how deep it cuts.

  P.S: I went ahead and marked this bug as a security vulnerability
  because I can think of ways this can be exploited, especially if the
  cellphone can trigger the bug and route traffic so that the user
  doesn't suspect it. If you feel the security impact is small and that
  there are other more important security issues, feel free to unmark it
  and we can deal with it's usability impact, which is probably more
  impactful.

  Regards,
  Tomás.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iptables 1.6.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 22:59:02 2020
  InstallationDate: Installed on 2019-02-08 (464 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and "Build-in speaker" appears "unplugged/unavailable"

[kffiatek]

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

For me, upgrading from groovy helped
Add and uncomment lines to sources.list

#deb http://pl.archive.ubuntu.com/ubuntu/ groovy main restricted universe 
multiverse
#deb http://pl.archive.ubuntu.com/ubuntu/ groovy-backports main restricted 
universe multiverse
#deb http://pl.archive.ubuntu.com/ubuntu/ groovy-security main restricted 
universe multiverse
#deb http://pl.archive.ubuntu.com/ubuntu/ groovy-updates main restricted 
universe multiverse
#deb http://pl.archive.ubuntu.com/ubuntu/ groovy-proposed main restricted 
universe multiverse


apt update

apt install libpulse0/groovy-proposed
apt install pulseaudio/groovy-proposed

! comment out those lines in sources.list again
! run apt update again
! do not upgrade your ubuntu when groovy repositories are turned on

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

Title:
  [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and
  "Build-in speaker" appears "unplugged/unavailable"

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and 
"Build-in speaker" appears "unplugged/unavaiable". I can change it in volume 
control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and 
sound does play, but after each reboot computer changes to Digital Stereo 
IEC985 and do not play sound until changed again.
  I did reinstall of alsa and pulse according to some forums but this didn't 
work.
  Before upgrade everything always worked out of the box since 2009 on this 
computer. I know it's a little old but it works excellent! Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kwiatek1472 F pulseaudio
   /dev/snd/controlC0:  kwiatek1472 F pulseaudio
   /dev/snd/pcmC0D0c:   kwiatek1472 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kwiatek1472 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr 30 09:25:27 2020
  InstallationDate: Installed on 2020-02-25 (64 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kwiatek1472 F pulseaudio
   /dev/snd/controlC0:  kwiatek1472 F pulseaudio
   /dev/snd/pcmC0D0c:   kwiatek1472 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kwiatek1472 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: XPS L501X
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1880095] Re: Keyboard entry stopped working

[Daniel van Vugt]

When the problem happens can you still operate anything with the mouse?

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

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

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

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

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

Title:
  Keyboard entry stopped working

Status in compiz package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I was toggling between text entry languages when the keyboard entry
  suddenly stopped working. Even the onscreen keyboard was not able to
  entry any keys.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-input-all (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:07: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri May 22 09:18:07 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1080] [1462:3362]
  InstallationDate: Installed on 2012-03-23 (2981 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Fri May 22 09:13:46 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.8-2ubuntu2

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

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

[Touch-packages] [Bug 1880095] [NEW] Keyboard entry stopped working

[Vadim Peretokin]

Public bug reported:

I was toggling between text entry languages when the keyboard entry
suddenly stopped working. Even the onscreen keyboard was not able to
entry any keys.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-input-all (not installed)
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:07: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri May 22 09:18:07 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 435.21, 5.4.0-31-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] 
[1462:3362]
InstallationDate: Installed on 2012-03-23 (2981 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F11
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS ELITE
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X570 AORUS ELITE
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Fri May 22 09:13:46 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.8-2ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 focal possible-manual-nvidia-install 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/1880095

Title:
  Keyboard entry stopped working

Status in xorg package in Ubuntu:
  New

Bug description:
  I was toggling between text entry languages when the keyboard entry
  suddenly stopped working. Even the onscreen keyboard was not able to
  entry any keys.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-input-all (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:07: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 

[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[kilroy]

Fresh install of Ubuntu 20.04 with a TT BH060 (TaoTronics):

Device E8:AB:FA:*:*:* (public)
Name: TAOTRONICS SoundSurge 60
Alias: TAOTRONICS SoundSurge 60
Class: 0x00240418
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: bluetooth:v000Apd

Also, kernel messages (hundreds):
[149342.549626] Bluetooth: hci0: SCO packet for unknown connection handle 0
[149342.549628] Bluetooth: hci0: SCO packet for unknown connection handle 12289

Switching to HSP/HFP just deactivates it completely. Only A2DP works as
expected.

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

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

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

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

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

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