[Touch-packages] [Bug 1918463] Re: Text on system overlays is blank

2021-03-10 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1910938 ***
https://bugs.launchpad.net/bugs/1910938

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


** Tags added: focal

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

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

** Summary changed:

- Text on system overlays is blank
+ Text on shell elements is blank

** This bug has been marked a duplicate of bug 1910938
   Text is missing from shell panel and menus

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

Title:
  Text on shell elements is blank

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Expected behaviour: I can read text on notifications and popups in
  Ubuntu.

  Observed Behaviour: Occassionaly, system overlays lose their ability
  to show text.

  This affects the notification drawer, the sound icon, any popups, and
  the login screen.

  It can be fixed by restarting Ubuntu.

  Looks like this: 
  https://imgur.com/a/rvFuHHs

  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  
  I am unable to determine what package shows these overlays. 

  I am using the dark theme from Gnome extensions, but switching back to
  light does not fix the issue.

  
  Potentially relevant packages: 

  xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  compiz:
Installed: (none)
Candidate: 1:0.9.14.1+20.04.20200211-0ubuntu1
Version table:
   1:0.9.14.1+20.04.20200211-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe i386 Packages

  
  notify-osd:
Installed: (none)
Candidate: 0.9.35+20.04.20191129-0ubuntu1
Version table:
   0.9.35+20.04.20191129-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

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

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


[Touch-packages] [Bug 1651500] Re: [ASUS X441SA] [8086:2284] No sound at all

2021-03-10 Thread Daniel van Vugt
If you are still experiencing the problem in focal, please just open a
Terminal window and run this command:

  apport-collect 1651500

That should send us the fresh information we need.


** No longer affects: alsa-driver (Ubuntu)

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

Title:
  [ASUS X441SA] [8086:2284] No sound at all

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1. Release of ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2. version of the package
  AlsaMixer v1.1.0

  
  3. I expect to hear sound from speaker

  4. I can not any sound from speaker

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hamda  1627 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec 20 22:51:08 2016
  InstallationDate: Installed on 2016-12-15 (5 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:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hamda  1627 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X441SA.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X441SA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X441SA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1891953] Re: CVE-2019-8936

2021-03-10 Thread Avital Ostromich
Apologies for the delay on this, it fell off our radar but we're working
on the Focal+ updates now. And no need for the separate Groovy debdiff,
thanks Brian!

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

Title:
  CVE-2019-8936

Status in ntp package in Ubuntu:
  Confirmed
Status in ntp source package in Bionic:
  Fix Released
Status in ntp source package in Focal:
  Confirmed
Status in ntp source package in Groovy:
  Confirmed
Status in ntp package in Debian:
  Fix Released

Bug description:
  It was discovered that the fix for CVE-2018-7182 introduced a NULL pointer
  dereference into NTP. An attacker could use this vulnerability to cause a
  denial of service (crash).

  https://people.canonical.com/~ubuntu-
  security/cve/2019/CVE-2019-8936.html

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

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


[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers

2021-03-10 Thread Dan Streetman
** Description changed:

  (SRU template for systemd)
  
  [impact]
  
  bash (and some other shells) builtin test command -x operation fails
  
  [test case]
  
  on any affected host system, start nspawn container, e.g.:
  
  $ sudo apt install systemd-container
  $ wget 
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
  $ mkdir h
  $ cd h
  $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
  $ sudo systemd-nspawn
  
  Then from a bash shell, verify if test -x works:
  
  root@h:~# ls -l /usr/bin/gpg
  -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
  root@h:~# test -x /usr/bin/gpg || echo "fail"
  fail
  
  [regression potential]
  
  any regression would likely occur during a syscall, most likely
  faccessat2(), or during other syscalls.
  
  [scope]
  
  this is needed for b/f
  
  this is fixed upstream by commit
  bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so
  this is fixed in h
  
  this was pulled into Debian at version 246.2 in commit
  e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g
  
  in x, the entire systemd seccomp code is completely different and the
  patch doesn't apply, nor does it appear to be needed, as the problem
  doesn't reproduce in a h container under x.
+ 
+ [other info]
+ 
+ this needs fixing in libseccomp as well
  
  [original description]
  
  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:
  
  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#
  
  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  
  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #
  
  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--==
  ii  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement
  
  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.
  
  The build fails with:
  
  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
  them is required for this operation
  
  The simple Dockerfile to reproduce the error - "docker build -t foo ."
  
  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 
  
  USER root
  
  RUN apt-get update \
   && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
    && curl https://syncthing.net/release-key.txt | apt-key add -
  
  Breaking it down it this seems to be an issue that there is new
  functionality in apt/apt-key e.g. security hardening that docker
  prohibits in its containers. Running this manually works only in an
  --privileged container.
  
  So adding keys in unpriviledged container or possibly kubernetes will
  not work anymore.
  
  Flo

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

Title:
  test -x fails inside shell scripts in containers

Status in docker.io package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  Opinion
Status in libseccomp package in Ubuntu:
  Fix Committed
Status in runc package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  New
Status in glibc source package in Xenial:
  New
Status in libseccomp source package in Xenial:
  New
Status in runc source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in docker.io source package in Bionic:
  New
Status in glibc source package in Bionic:
  New
Status in libseccomp source package in Bionic:
  New
Status in runc source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in docker.io source package in Focal:
  New

[Touch-packages] [Bug 1915887] Re: systemd spams the syslog about lack of native systemd unit file

2021-03-10 Thread Bug Watch Updater
** Changed in: systemd (Debian)
   Status: Confirmed => Fix Released

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

Title:
  systemd spams the syslog about lack of native systemd unit file

Status in apport package in Ubuntu:
  Incomplete
Status in fam package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in ipfm package in Ubuntu:
  Incomplete
Status in n2n package in Ubuntu:
  Incomplete
Status in pfm package in Ubuntu:
  Incomplete
Status in shadowsocks package in Ubuntu:
  Incomplete
Status in sysfsutils package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in virtualbox package in Ubuntu:
  Incomplete
Status in xl2tpd package in Ubuntu:
  Incomplete
Status in systemd package in Debian:
  Fix Released

Bug description:
  systemd in hirsute spams the syslog file several times per second
  about services lacking native systemd unit files.  Two things should
  happen.

  1) a systemd unit file ought to be created
  2) systemd should be slowed down with regards to these messages

  Feb 17 02:02:48 ubuntu-devel kernel: [  289.794825] 
systemd-sysv-generator[7105]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:49 ubuntu-devel kernel: [  290.165351] 
systemd-sysv-generator[7126]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:49 ubuntu-devel kernel: [  291.111278] 
systemd-sysv-generator[7170]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:02:50 ubuntu-devel kernel: [  291.507164] 
systemd-sysv-generator[7199]: SysV service '/etc/init.d/n2n' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.

  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386062] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/fam' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386321] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/xl2tpd' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386742] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/ipfm' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.386767] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/shadowsocks' lacks a 
native systemd unit file. Automatically generating a unit file for 
compatibility. Please update package to include a native systemd unit file, in 
order to make it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.387281] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/virtualbox' lacks a 
native systemd unit file. Automatically generating a unit file for 
compatibility. Please update package to include a native systemd unit file, in 
order to make it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.388931] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/sysfsutils' lacks a 
native systemd unit file. Automatically generating a unit file for 
compatibility. Please update package to include a native systemd unit file, in 
order to make it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.388955] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/apport' lacks a native 
systemd unit file. Automatically generating a unit file for compatibility. 
Please update package to include a native systemd unit file, in order to make 
it more safe and robust.
  Feb 17 02:05:57 ubuntu-devel kernel: [  478.389412] 
systemd-sysv-generator[9909]: SysV service '/etc/init.d/freeradius' lacks a 
native systemd unit file. Automatically generating a unit file for 
compatibility. Please update package to include a native systemd unit file, in 
order to make it more safe and robust.

To manage 

[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers

2021-03-10 Thread Dan Streetman
** Description changed:

+ (SRU template for systemd)
+ 
  [impact]
  
  bash (and some other shells) builtin test command -x operation fails
  
  [test case]
  
  on any affected host system, start nspawn container, e.g.:
  
  $ sudo apt install systemd-container
  $ wget 
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
  $ mkdir h
  $ cd h
  $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
  $ sudo systemd-nspawn
  
  Then from a bash shell, verify if test -x works:
  
  root@h:~# ls -l /usr/bin/gpg
  -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
  root@h:~# test -x /usr/bin/gpg || echo "fail"
  fail
  
+ alternately using docker, this Dockerfile can be used with 'docker build
+ -t foo .' (taken from example in original description)
  
- alternately using docker, this Dockerfile can be used with 'docker build -t 
foo .' (taken from example in original description)
- 
- $ cat Dockerfile 
+ $ cat Dockerfile
  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 
  
  USER root
  
  RUN bash -c "test -x /bin/bash && echo ok || echo fail"
  
  [regression potential]
  
  any regression would likely occur during a syscall, most likely
  faccessat2(), or during other syscalls.
  
  [scope]
  
  this is needed for b/f
  
  this is fixed upstream by commit
  bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so
  this is fixed in h
  
  this was pulled into Debian at version 246.2 in commit
  e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g
  
  in x, the entire systemd seccomp code is completely different and the
  patch doesn't apply, nor does it appear to be needed, as the problem
  doesn't reproduce in a h container under x.
  
  [original description]
  
  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:
  
  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#
  
  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  
  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #
  
  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--==
  ii  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement
  
  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.
  
  The build fails with:
  
  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
  them is required for this operation
  
  The simple Dockerfile to reproduce the error - "docker build -t foo ."
  
  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 
  
  USER root
  
  RUN apt-get update \
   && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
    && curl https://syncthing.net/release-key.txt | apt-key add -
  
  Breaking it down it this seems to be an issue that there is new
  functionality in apt/apt-key e.g. security hardening that docker
  prohibits in its containers. Running this manually works only in an
  --privileged container.
  
  So adding keys in unpriviledged container or possibly kubernetes will
  not work anymore.
  
  Flo

** Description changed:

  (SRU template for systemd)
  
  [impact]
  
  bash (and some other shells) builtin test command -x operation fails
  
  [test case]
  
  on any affected host system, start nspawn container, e.g.:
  
  $ sudo apt install systemd-container
  $ wget 
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
  $ mkdir h
  $ cd h
  $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
  $ sudo systemd-nspawn
  
  Then from a bash shell, verify if test -x works:
  
  root@h:~# ls -l /usr/bin/gpg
  -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
  root@h:~# test -x /usr/bin/gpg 

[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers

2021-03-10 Thread Dan Streetman
** Description changed:

  [impact]
  
  bash (and some other shells) builtin test command -x operation fails
  
  [test case]
  
  on any affected host system, start nspawn container, e.g.:
  
  $ sudo apt install systemd-container
  $ wget 
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
  $ mkdir h
  $ cd h
  $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
  $ sudo systemd-nspawn
  
  Then from a bash shell, verify if test -x works:
  
  root@h:~# ls -l /usr/bin/gpg
  -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
  root@h:~# test -x /usr/bin/gpg || echo "fail"
  fail
  
+ 
+ alternately using docker, this Dockerfile can be used with 'docker build -t 
foo .' (taken from example in original description)
+ 
+ $ cat Dockerfile 
+ FROM amd64/ubuntu:hirsute
+ MAINTAINER Florian Lohoff 
+ 
+ USER root
+ 
+ RUN bash -c "test -x /bin/bash && echo ok || echo fail"
+ 
  [regression potential]
  
  any regression would likely occur during a syscall, most likely
  faccessat2(), or during other syscalls.
  
  [scope]
  
- this is needed for x/b/f
+ this is needed for b/f
  
  this is fixed upstream by commit
  bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so
  this is fixed in h
  
  this was pulled into Debian at version 246.2 in commit
  e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g
+ 
+ in x, the entire systemd seccomp code is completely different and the
+ patch doesn't apply, nor does it appear to be needed, as the problem
+ doesn't reproduce in a h container under x.
  
  [original description]
  
  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:
  
  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#
  
  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  
  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #
  
  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--==
  ii  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement
  
  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.
  
  The build fails with:
  
  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
  them is required for this operation
  
  The simple Dockerfile to reproduce the error - "docker build -t foo ."
  
  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 
  
  USER root
  
  RUN apt-get update \
   && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
    && curl https://syncthing.net/release-key.txt | apt-key add -
  
  Breaking it down it this seems to be an issue that there is new
  functionality in apt/apt-key e.g. security hardening that docker
  prohibits in its containers. Running this manually works only in an
  --privileged container.
  
  So adding keys in unpriviledged container or possibly kubernetes will
  not work anymore.
  
  Flo

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

Title:
  test -x fails inside shell scripts in containers

Status in docker.io package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  Opinion
Status in libseccomp package in Ubuntu:
  Fix Committed
Status in runc package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  New
Status in glibc source package in Xenial:
  New
Status in libseccomp source package in Xenial:
  New
Status in runc source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in docker.io source package in Bionic:
  New
Status in glibc source 

[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers

2021-03-10 Thread Dan Streetman
** Description changed:

+ [impact]
+ 
+ bash (and some other shells) builtin test command -x operation fails
+ 
+ [test case]
+ 
+ on any affected host system, start nspawn container, e.g.:
+ 
+ $ sudo apt install systemd-container
+ $ wget 
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
+ $ mkdir h
+ $ cd h
+ $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
+ $ sudo systemd-nspawn
+ 
+ Then from a bash shell, verify if test -x works:
+ 
+ root@h:~# ls -l /usr/bin/gpg
+ -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
+ root@h:~# test -x /usr/bin/gpg || echo "fail"
+ fail
+ 
+ [regression potential]
+ 
+ any regression would likely occur during a syscall, most likely
+ faccessat2(), or during other syscalls.
+ 
+ [scope]
+ 
+ this is needed for x/b/f/g
+ 
+ this is fixed upstream by commit
+ bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so
+ this is fixed in h
+ 
+ [original description]
+ 
  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:
  
  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#
  
  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  
  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #
  
  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--==
  ii  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement
  
  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.
  
  The build fails with:
  
  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
  them is required for this operation
  
  The simple Dockerfile to reproduce the error - "docker build -t foo ."
  
  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 
  
  USER root
  
  RUN apt-get update \
   && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
    && curl https://syncthing.net/release-key.txt | apt-key add -
  
  Breaking it down it this seems to be an issue that there is new
  functionality in apt/apt-key e.g. security hardening that docker
  prohibits in its containers. Running this manually works only in an
  --privileged container.
  
  So adding keys in unpriviledged container or possibly kubernetes will
  not work anymore.
  
  Flo

** Description changed:

  [impact]
  
  bash (and some other shells) builtin test command -x operation fails
  
  [test case]
  
  on any affected host system, start nspawn container, e.g.:
  
  $ sudo apt install systemd-container
  $ wget 
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
  $ mkdir h
  $ cd h
  $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
  $ sudo systemd-nspawn
  
  Then from a bash shell, verify if test -x works:
  
  root@h:~# ls -l /usr/bin/gpg
  -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
  root@h:~# test -x /usr/bin/gpg || echo "fail"
  fail
  
  [regression potential]
  
  any regression would likely occur during a syscall, most likely
  faccessat2(), or during other syscalls.
  
  [scope]
  
- this is needed for x/b/f/g
+ this is needed for x/b/f
  
  this is fixed upstream by commit
  bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so
  this is fixed in h
+ 
+ this was pulled into Debian at version 246.2 in commit
+ e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g
  
  [original description]
  
  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:
  
  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test 

[Touch-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

2021-03-10 Thread Tessa
note that I've switched to using pipewire to replace pulse, and it
doesn't have this problem. so this is definitely a pulse specific issue.
thankfully pipewire is mature enough to use full time now, and I'd
recommend folks experiencing this problem give it a shot, since it
offers pulse, alsa, and jack protocol compatibility.

https://pipewire.org/

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

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 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: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx: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/1888598/+subscriptions

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


[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2021-03-10 Thread Md Ayquassar
Yes, Ctrl +  zooms in and out.  If we believe
https://www.microsoft.com/accessories/en-ww/products/keyboards/natural-
ergonomic-keyboard-4000/b2m-00012 (though my model is not B2M-00012 but
1048) , Microsoft intended the zoom slider on the keyboard to map to
zoom in and out, too.

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

Title:
  Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103:
  Invalid argument

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel
  5.4.0-42-generic on Dell Latitude E6440.  Upon examining the output of
  journalctl -b, I see this:

  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Show Plymouth Boot Screen being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Forward Password Requests to Plymouth Directory Watch being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Set Up Additional Binary Formats being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
File System Check on Root Device being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Rebuild Hardware Database being skipped.
  Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in 
Platform Persistent Storage Archival being skipped.
  Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized
  Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 
524288, num gpu pages 524288
  Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn 
acpi driver for receiving events
  Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to 
call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
  Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to 
call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument

  "Invalid argument" means that something goes wrong there, and I don't know 
what it is.
  On my laptop, event8 seems to be keyboard-related:

  $ sudo cat /proc/bus/input/devices | grep -C 5 event8
  I: Bus=0003 Vendor=045e Product=00db Version=0111
  N: Name="Microsoft Natural® Ergonomic Keyboard 4000"
  P: Phys=usb-:00:14.0-13.1/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9
  U: Uniq=
  H: Handlers=sysrq kbd event8 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=10007 ff8007ff febeffdff3cf fffe
  B: MSC=10
  B: LED=107

  The issue report
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is
  probably related but marked as a duplicate of a no longer existing
  issue report (#1750855).

  The report
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415
  describes a similar issue for older kernels; the differences pertain
  to error message, error code, input..., and, opposed to #19 there, I
  have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine
  is not a dual-boot machine.

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

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


[Touch-packages] [Bug 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

2021-03-10 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Expect : sound from speaker
  Instead, obtain : no sound.

  
  Tried various configuration of /etc/modprobe.d/alsa-conf with :

  options snd-hda-intel model= and
  options snd-intel-dspcfg dsp_driver=3 or 1
  and systematic reboot.

  Either I get dummy output, or I get proper output detection, alsamixer
  and pavucontrol seems 100% ok, but no sound comes from the speakers.

  I'm under a dualboot with Windows 10, BIOS fast boot disabled.
  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thibauts   1522 F pulseaudio
   /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 18:10:30 2021
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp
  Symptom_Jack: Grey Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2019
  dmi.bios.release: 1.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Guinness_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF515-51T
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254

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

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


[Touch-packages] [Bug 1918458] [NEW] [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

2021-03-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Expect : sound from speaker
Instead, obtain : no sound.


Tried various configuration of /etc/modprobe.d/alsa-conf with :

options snd-hda-intel model= and
options snd-intel-dspcfg dsp_driver=3 or 1
and systematic reboot.

Either I get dummy output, or I get proper output detection, alsamixer
and pavucontrol seems 100% ok, but no sound comes from the speakers.

I'm under a dualboot with Windows 10, BIOS fast boot disabled.
Ubuntu 20.04.2 LTS

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  thibauts   1522 F pulseaudio
 /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 10 18:10:30 2021
InstallationDate: Installed on 2021-03-09 (1 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp
Symptom_Jack: Grey Speaker, Internal
Symptom_Type: Only some of outputs are working
Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback 
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/24/2019
dmi.bios.release: 1.4
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.04
dmi.board.asset.tag: Default string
dmi.board.name: Guinness_WL
dmi.board.vendor: WL
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.04
dmi.ec.firmware.release: 1.6
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
dmi.product.family: Swift 5
dmi.product.name: Swift SF515-51T
dmi.product.sku: 
dmi.product.version: V1.04
dmi.sys.vendor: Acer
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254

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


** Tags: amd64 apport-bug focal
-- 
[Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no 
sound from speakers, headphones ok
https://bugs.launchpad.net/bugs/1918458
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver in Ubuntu.

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


Re: [Touch-packages] [Bug 1913763] Re: hyperv: unable to distinguish PTP devices

2021-03-10 Thread Gauthier Jolly
Awesome, thanks

On Wed, Mar 10, 2021 at 4:15 PM Dan Streetman <1913...@bugs.launchpad.net>
wrote:

> > @rbalint or @ddstreet, do you plan to also backport this to Xenial?
>
> sure
>
> ** Tags removed: verification-needed verification-needed-bionic
> verification-needed-focal verification-needed-groovy
> ** Tags added: verification-done verification-done-bionic
> verification-done-focal verification-done-groovy
>
> --
> You received this bug notification because you are a member of Canonical
> Cloudware, which is subscribed to the bug report.
> https://bugs.launchpad.net/bugs/1913763
>
> Title:
>   hyperv: unable to distinguish PTP devices
>
> Status in systemd package in Ubuntu:
>   Fix Released
> Status in systemd source package in Bionic:
>   Fix Committed
> Status in systemd source package in Focal:
>   Fix Committed
> Status in systemd source package in Groovy:
>   Fix Committed
>
> Bug description:
>   [impact]
>
>   the /dev/ptp0 device for a hyperv instance may not be the correct,
>   hyperv-provided, ptp device.
>
>   [test case]
>
>   on some hyperv instance types, particularly those that might contain
>   passthrough network card(s) that also provide ptp, the first ptp
>   device may not be the correct one to use for ptp, e.g. there may be
>   multiple ones:
>
>   $ ls /dev/ptp*
>   /dev/ptp0 /dev/ptp1
>   $ cat /sys/class/ptp/ptp0/clock_name
>   hyperv
>   $ cat /sys/class/ptp/ptp1/clock_name
>   mlx5_p2p
>
>   the order can change across boots, so a consistent way of addressing
>   the hyperv-provided one is needed
>
>   [regression potential]
>
>   any regression would involve failure to properly create the ptp
>   symlink, or other failure while udev is processing newly detected ptp
>   device(s)
>
>   [scope]
>
>   this is needed in all releases
>
>   this was fixed upstream with the commit
>   32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
>   any release
>
>   [original description]
>
>   Hyperv provides a PTP device. On system with multiple PTP devices,
>   services like Chrony don't have a way to know which one is which.
>
>   We would like to have a udev rule to create a symlink to the hyperv
>   clock. This way, services could be configured to always use this clock
>   no matter if it is ptp0, ptp1, etc..
>
>   For example:
>
>   ```
>   SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
>   ```
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+subscriptions
>

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

Title:
  hyperv: unable to distinguish PTP devices

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [impact]

  the /dev/ptp0 device for a hyperv instance may not be the correct,
  hyperv-provided, ptp device.

  [test case]

  on some hyperv instance types, particularly those that might contain
  passthrough network card(s) that also provide ptp, the first ptp
  device may not be the correct one to use for ptp, e.g. there may be
  multiple ones:

  $ ls /dev/ptp*
  /dev/ptp0 /dev/ptp1
  $ cat /sys/class/ptp/ptp0/clock_name
  hyperv
  $ cat /sys/class/ptp/ptp1/clock_name
  mlx5_p2p

  the order can change across boots, so a consistent way of addressing
  the hyperv-provided one is needed

  [regression potential]

  any regression would involve failure to properly create the ptp
  symlink, or other failure while udev is processing newly detected ptp
  device(s)

  [scope]

  this is needed in all releases

  this was fixed upstream with the commit
  32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
  any release

  [original description]

  Hyperv provides a PTP device. On system with multiple PTP devices,
  services like Chrony don't have a way to know which one is which.

  We would like to have a udev rule to create a symlink to the hyperv
  clock. This way, services could be configured to always use this clock
  no matter if it is ptp0, ptp1, etc..

  For example:

  ```
  SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
  ```

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

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


[Touch-packages] [Bug 1918462] Re: package libbinutils:amd64 2.34-6ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur

2021-03-10 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libbinutils:amd64 2.34-6ubuntu1.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in binutils package in Ubuntu:
  New

Bug description:
  It gives error since 2 weeks in every turning on of computer

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libbinutils:amd64 2.34-6ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   linux-libc-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar 10 08:19:53 2021
  DuplicateSignature:
   package:libbinutils:amd64:2.34-6ubuntu1.1
   Setting up linux-libc-dev:amd64 (5.4.0-66.74) ...
   dpkg: error processing package libbinutils:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2020-09-28 (162 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: binutils
  Title: package libbinutils:amd64 2.34-6ubuntu1.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1918463] [NEW] Text on system overlays is blank

2021-03-10 Thread Brettins
Public bug reported:

Expected behaviour: I can read text on notifications and popups in
Ubuntu.

Observed Behaviour: Occassionaly, system overlays lose their ability to
show text.

This affects the notification drawer, the sound icon, any popups, and
the login screen.

It can be fixed by restarting Ubuntu.

Looks like this: 
https://imgur.com/a/rvFuHHs

Description:Ubuntu 20.04.2 LTS
Release:20.04


I am unable to determine what package shows these overlays. 

I am using the dark theme from Gnome extensions, but switching back to
light does not fix the issue.


Potentially relevant packages: 

xorg:
  Installed: 1:7.7+19ubuntu14
  Candidate: 1:7.7+19ubuntu14
  Version table:
 *** 1:7.7+19ubuntu14 500
500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

compiz:
  Installed: (none)
  Candidate: 1:0.9.14.1+20.04.20200211-0ubuntu1
  Version table:
 1:0.9.14.1+20.04.20200211-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://ca.archive.ubuntu.com/ubuntu focal/universe i386 Packages


notify-osd:
  Installed: (none)
  Candidate: 0.9.35+20.04.20191129-0ubuntu1
  Version table:
 0.9.35+20.04.20191129-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

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

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

Title:
  Text on system overlays is blank

Status in xorg package in Ubuntu:
  New

Bug description:
  Expected behaviour: I can read text on notifications and popups in
  Ubuntu.

  Observed Behaviour: Occassionaly, system overlays lose their ability
  to show text.

  This affects the notification drawer, the sound icon, any popups, and
  the login screen.

  It can be fixed by restarting Ubuntu.

  Looks like this: 
  https://imgur.com/a/rvFuHHs

  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  
  I am unable to determine what package shows these overlays. 

  I am using the dark theme from Gnome extensions, but switching back to
  light does not fix the issue.

  
  Potentially relevant packages: 

  xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  compiz:
Installed: (none)
Candidate: 1:0.9.14.1+20.04.20200211-0ubuntu1
Version table:
   1:0.9.14.1+20.04.20200211-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe i386 Packages

  
  notify-osd:
Installed: (none)
Candidate: 0.9.35+20.04.20191129-0ubuntu1
Version table:
   0.9.35+20.04.20191129-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

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

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


[Touch-packages] [Bug 1918462] [NEW] package libbinutils:amd64 2.34-6ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

2021-03-10 Thread Melisa Nur Kart
Public bug reported:

It gives error since 2 weeks in every turning on of computer

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libbinutils:amd64 2.34-6ubuntu1.1
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
AptOrdering:
 linux-libc-dev:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Mar 10 08:19:53 2021
DuplicateSignature:
 package:libbinutils:amd64:2.34-6ubuntu1.1
 Setting up linux-libc-dev:amd64 (5.4.0-66.74) ...
 dpkg: error processing package libbinutils:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2020-09-28 (162 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: binutils
Title: package libbinutils:amd64 2.34-6ubuntu1.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libbinutils:amd64 2.34-6ubuntu1.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in binutils package in Ubuntu:
  New

Bug description:
  It gives error since 2 weeks in every turning on of computer

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libbinutils:amd64 2.34-6ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   linux-libc-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar 10 08:19:53 2021
  DuplicateSignature:
   package:libbinutils:amd64:2.34-6ubuntu1.1
   Setting up linux-libc-dev:amd64 (5.4.0-66.74) ...
   dpkg: error processing package libbinutils:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2020-09-28 (162 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: binutils
  Title: package libbinutils:amd64 2.34-6ubuntu1.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2021-03-10 Thread Julian Andres Klode
Corrected the task for bionic as per policy (in progress means SRU
uploaded).

I'll be working on the bionic SRU tomorrow, I've just prepared SRUs for
groovy and focal for other issues, and will be cherry-picking these
patches on top of those :)

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Triaged
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

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

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2021-03-10 Thread Julian Andres Klode
** Changed in: apt (Ubuntu Bionic)
   Status: In Progress => Triaged

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Triaged
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

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

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 

[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list

2021-03-10 Thread Julian Andres Klode
For the record, we are going to roll the apt change out in groovy
shortly, but delay the LTS updates to give it some more real world
testing.

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

Title:
  interruption of dist-upgrade can leave you next release in
  sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  New
Status in ubuntu-release-upgrader source package in Bionic:
  New
Status in apt source package in Focal:
  New
Status in ubuntu-release-upgrader source package in Focal:
  New
Status in apt source package in Groovy:
  In Progress
Status in ubuntu-release-upgrader source package in Groovy:
  New
Status in apt source package in Hirsute:
  Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  Calling update() or installing packages from apt clients resets their SIGINT 
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have 
set for them.

  In case of ubuntu-release-upgrader, this results in the release
  upgrader being unable to handle interrupts after it did the initial
  update - the default libc handler will run and the program exits.

  [Test plan]

  [[apt]]
  As a standalone test for apt, we can test the following script:

  import apt
  import time

  apt.Cache().update()
  print("WAITING")
  try:
  time.sleep(1)
  except BaseException as e:
  print("Seen", repr(e))
  print("END")

  Pressing Ctrl+C while WAITING is printed should print Seen
  KeyboardInterrupt, and importantly, also the END line.

  [Where problems could occur]
  apt: This specific change removes the two lines that SIG_DFL the signal 
handlers after running scripts. AFAWCT those lines are unnecessary - the code 
that calls it temporarily sets the handlers to SIG_IGN but restores previous 
handlers at the end; it was wrongly refactored decades ago. A regression could 
occur in that those signals will now continue to be ignored if we missed a spot.

  [Original bug report]
  As a long-time-user of ?ubuntu, with apt-get as tool of choice for 
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
  In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu 
version; just all packages including new ones. Version updates had to be 
initiated manually, and I was always asked if I really wanted the new ?ubuntu 
version. Sounds appropriate.

  Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. 
I for one consider this kind of intrusive, though.
  It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a 
number of times earlier; just to *check* if the upgrade was on offer; but this 
is only a guess.

  In *any* case, a pop-up asking "Are you sure? Are you connected
  through an adequate pipe? Are you sitting with full batteries; better
  a power supply?" would be convenient; since I am using my PC for
  urgent duties, and didn't want to fiddle with unexpected upgrade bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Thu Oct  1 11:48:39 2020
  InstallationDate: Installed on 2019-03-14 (566 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
  VarLogDistupgradeAptlog:
   Log time: 2020-09-29 19:44:28.696289
   Log time: 2020-09-29 19:44:33.573481

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

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


[Touch-packages] [Bug 1917763] Re: FFE: new upstream release 21.0 and migrate to llvm 12

2021-03-10 Thread Timo Aaltonen
** Changed in: mesa (Ubuntu)
   Status: In Progress => New

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

Title:
  FFE: new upstream release 21.0 and migrate to llvm 12

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 21.0.0 will be released soon, and we still want it in 21.04. It's
  been in Debian experimental since rc1. The packaging also migrates it
  to use llvm 12.

  The risks involve graphical issues or even crashes when running more
  intense OpenGL/Vulkan apps like games. Running a desktop is a simple
  use-case and should work fine across the board. Upstream gitlab has a
  fairly extensive CI for various drivers, while Intel tests on their
  own CI. This means that any showstoppers should be shaken out already.

  We will be able to pull maybe two point-releases before hirsute is
  frozen, and then push more as an SRU.

  I've tested 21.0.0-rc's on Intel and AMD (RX 5700) and the latter too
  with some games, all good.

  packages for hirsute are available on ppa:canonical-x/x-staging

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

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


[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2021-03-10 Thread dann frazier
** Changed in: apt (Ubuntu Bionic)
   Status: Fix Released => In Progress

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  In Progress
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

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

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 

[Touch-packages] [Bug 1899878] Re: Python's test_ssl fails starting from Ubuntu 20.04

2021-03-10 Thread Kurt Roeckx
2) and 3) would never return 0, which is what the upstream OpenSSL
version returns now.

2) would make it return TLS1_VERSION for the minimum and TLS1_3_VERSION
for the maximum with default build options. If you enable SSlv3 support
at compile time, the minimum would return SSL3_VERSION. Note that there
is a TLS_MAX_VERSION define that's equal to TLS1_3_VERSION, but no such
define for the minimum.

1) would just return what is set, which is 0 upstream and for Ubuntu for
both minimum and maximum, where 0 is defined as no limit set. Debian
sets the minimum to TLS1_2_VERSION, and so returns that value. But maybe
if no limit is set (and so the value is 0), it can instead return the
minimum/maximum version that's supported at compile time.

3) Would have as effect that upstream in 1.1.1 returns TLS1_VERSION and
TLS1_3_VERSION, but TLS1_2_VERSION and TLS1_3_VERSION in 3.0. For Ubuntu
and Debian it would return TLS1_2_VERSION and TLS1_3_VERISON, since that
is what they do using a different method.

Setting the default minimum to TLS1_2_VERSION (at compile time) will
clearly fix your problem. But I think you're going to run in the same
problem with 3.0, and we should probably add a new API in 3.0 for it.

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

Title:
  Python's test_ssl fails starting from Ubuntu 20.04

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  Please take a look at https://bugs.python.org/issue41561. Developers
  who work on Python think that the issue is due to a change in Ubuntu
  20.04 that is best described by
  https://bugs.python.org/issue41561#msg378089:

  "It sounds like a Debian/Ubuntu patch is breaking an assumption. Did
  somebody report the bug with Debian/Ubuntu maintainers of OpenSSL
  already? Fedora also configures OpenSSL with minimum protocol version
  of TLS 1.2. The distribution does it in a slightly different way that
  makes the restriction discoverable and that is compatible with
  Python's test suite."

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

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


[Touch-packages] [Bug 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly

2021-03-10 Thread Sergio Durigan Junior
Unfortunately I don't know.  I would recommend commenting on the bug in
order to let upstream know that more people are affected by this
problem.  You can try posting your reproduction instructions there, and
provide more information if upstream needs it.

I am marking this bug as Triaged, although I have not reproduced it
myself.

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: openvpn (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Network Manager OpenVPN nested connections fail to setup routes
  correctly

Status in OpenVPN:
  Unknown
Status in network-manager package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Invalid

Bug description:
  Setup:
  Host lan: 192.168.0.238/24
  Host Default gw: 192.168.0.1

  ip route:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 

  
  Primary OpenVPN (check "Use this connection only for resources on its 
network"):
  server ip: public a.b.c.d
  OpenVPN Tunnel: 192.168.1.0/24
  routes pushed: 192.168.100.0/24

  First VPN works OK:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  
  Secondary OpenVPN  (check "Use this connection only for resources on its 
network"):
  server ip: private 192.168.100.10 
  OpenVPN Tunnel: 192.168.20.0/24
  routes pushed: 192.168.200.0/24

  Second VPN Connect OK, routing table is wrong:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 
  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is 
wrong, the openVPN#2 Gateway is not on the local lan

  Correct routing table using "sudo /usr/sbin/openvpn
  /path/to/config.openvpn" (same a Network Manager)

  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  It seems that Network Manager add a wrong additional route not added
  by the openvpn bin:

  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openvpn 2.4.7-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 12:44:39 2021
  InstallationDate: Installed on 2021-02-19 (13 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly

2021-03-10 Thread Riccardo Battistini
Hi, it seems the same problem, I removed the extra routing with the same
workaround ip command and the traffic flows correctly.

The upstream bug seems to be ignored, are there chances to be fixed?

Regards
Riccardo

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

Title:
  Network Manager OpenVPN nested connections fail to setup routes
  correctly

Status in OpenVPN:
  Unknown
Status in network-manager package in Ubuntu:
  Incomplete
Status in openvpn package in Ubuntu:
  Incomplete

Bug description:
  Setup:
  Host lan: 192.168.0.238/24
  Host Default gw: 192.168.0.1

  ip route:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 

  
  Primary OpenVPN (check "Use this connection only for resources on its 
network"):
  server ip: public a.b.c.d
  OpenVPN Tunnel: 192.168.1.0/24
  routes pushed: 192.168.100.0/24

  First VPN works OK:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  
  Secondary OpenVPN  (check "Use this connection only for resources on its 
network"):
  server ip: private 192.168.100.10 
  OpenVPN Tunnel: 192.168.20.0/24
  routes pushed: 192.168.200.0/24

  Second VPN Connect OK, routing table is wrong:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 
  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is 
wrong, the openVPN#2 Gateway is not on the local lan

  Correct routing table using "sudo /usr/sbin/openvpn
  /path/to/config.openvpn" (same a Network Manager)

  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  It seems that Network Manager add a wrong additional route not added
  by the openvpn bin:

  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openvpn 2.4.7-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 12:44:39 2021
  InstallationDate: Installed on 2021-02-19 (13 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1878969] Re: time-epoch never changes in SRUs

2021-03-10 Thread Dan Streetman
@xnox can you verify this bug

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

Title:
  time-epoch never changes in SRUs

Status in ubuntu-core-initramfs:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * Systems without hwclock come up with a fixed time epoch which is not 
updated in SRUs
   * Ideally booting with a newer built of systemd should move time epoch to be 
at least when systemd was last built. For example to the value of 
SOURCE_DATE_EPOCH.

  [Test Case]

   * Boot without network NTP or hwclock
   * Observe that the epoch is the same as the time when NEWS entry in the 
systemd source code was last touched.
   * Boot newer update of systemd, observe that the time epoch is at least 2020

  [Regression Potential]

   * Bad epoch, may result in unable to perform TLS connections,
  validated GPG signatures, and snapd assertions. Changing epoch to be
  more recent is desired. Some machines may rely on the fact that
  "bionic" without hwclock always comes up in year 2018. But in practice
  that is incorrect thing to do.

  [Other Info]
   
   * By default

  option('time-epoch', type : 'integer', value : '-1',
 description : 'time epoch for time clients')

  in systemd is set to the modification time of the NEW entry
  time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()

  If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
  to be compliant with the https://reproducible-
  builds.org/docs/timestamps/ specification.

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

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


[Touch-packages] [Bug 1913189] Re: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1

2021-03-10 Thread Dan Streetman
test passes now in focal:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20210309_214854_f9944@/log.gz

marking as verified for bionic as well, as 5.8 or later kernel isn't
available for bionic, and this was backported due to possible build-time
failure as explained in description

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

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

Title:
  systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8
  5.8.0-41.46~20.04.1

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  test-fs-util fails when running under 5.8 kernel

  [test case]

  see autopkgtest runs, e.g.

  amd64:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz

  [regression potential]

  any regression would likely result in incorrectly passed or failed
  build-time or autopkgtest-time test run

  [scope]

  this is needed in f and b

  this was fixed upstream with commit 5b5ce6298e which was first
  included in v247, and has already been backported to g in bug 1891527.

  while it's unlikely that the 5.8 kernel will ever officially be
  available directly in b, this test case is also run at build time, so
  if the lp build farm is ever updated to the 5.8 kernel this test case
  would begin failing during build, so the patch should be backported
  there as well.

  this isn't needed in x as the test-fs-util test isn't present there.

  [original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20210121_021134_f3c65@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20210121_090718_fa164@/log.gz

  The failing test case is:

  TEST-24-UNIT-TESTS:

  === Failed test log ===
  --- test-fs-util begin ---
  /* test_chase_symlinks */
  /* test_unlink_noerrno */
  /* test_readlink_and_make_absolute */
  /* test_var_tmp */
  /* test_dot_or_dot_dot */
  /* test_access_fd */
  /* test_touch_file */
  Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at 
src/test/test-fs-util.c:637, funct
  ion test_touch_file(). Aborting.
  --- test-fs-util end ---
  make: Leaving directory 
'/tmp/autopkgtest.KFUfZH/build.scn/src/test/TEST-24-UNIT-TESTS'
  make: *** [Makefile:4: run] Error 1

  This issue has been solved in Groovy on bug 1891527, likely the fix
  needs to be backported to systemd in Focal for the testcase to pass
  with the 5.8 kernel.

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

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


[Touch-packages] [Bug 1913763] Re: hyperv: unable to distinguish PTP devices

2021-03-10 Thread Dan Streetman
> @rbalint or @ddstreet, do you plan to also backport this to Xenial?

sure

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

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

Title:
  hyperv: unable to distinguish PTP devices

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [impact]

  the /dev/ptp0 device for a hyperv instance may not be the correct,
  hyperv-provided, ptp device.

  [test case]

  on some hyperv instance types, particularly those that might contain
  passthrough network card(s) that also provide ptp, the first ptp
  device may not be the correct one to use for ptp, e.g. there may be
  multiple ones:

  $ ls /dev/ptp*
  /dev/ptp0 /dev/ptp1
  $ cat /sys/class/ptp/ptp0/clock_name
  hyperv
  $ cat /sys/class/ptp/ptp1/clock_name
  mlx5_p2p

  the order can change across boots, so a consistent way of addressing
  the hyperv-provided one is needed

  [regression potential]

  any regression would involve failure to properly create the ptp
  symlink, or other failure while udev is processing newly detected ptp
  device(s)

  [scope]

  this is needed in all releases

  this was fixed upstream with the commit
  32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
  any release

  [original description]

  Hyperv provides a PTP device. On system with multiple PTP devices,
  services like Chrony don't have a way to know which one is which.

  We would like to have a udev rule to create a symlink to the hyperv
  clock. This way, services could be configured to always use this clock
  no matter if it is ptp0, ptp1, etc..

  For example:

  ```
  SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
  ```

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

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


[Touch-packages] [Bug 1913763] Re: hyperv: unable to distinguish PTP devices

2021-03-10 Thread Dan Streetman
root@test-f:~# dpkg -l systemd|grep systemd
ii  systemd245.4-4ubuntu3.4 amd64system and service manager
root@test-f:~# ls -l /dev/ptp*
crw--- 1 root root 246, 0 Mar 10 15:49 /dev/ptp0
crw--- 1 root root 246, 1 Mar 10 15:49 /dev/ptp1
root@test-f:~# grep . /sys/class/ptp/*/clock_name
/sys/class/ptp/ptp0/clock_name:hyperv
/sys/class/ptp/ptp1/clock_name:mlx5_p2p


ddstreet@test-f:~$ dpkg -l systemd|grep systemd
ii  systemd245.4-4ubuntu3.5 amd64system and service manager
ddstreet@test-f:~$ ls -l /dev/ptp*
crw--- 1 root root 246, 0 Mar 10 16:04 /dev/ptp0
crw--- 1 root root 246, 1 Mar 10 16:04 /dev/ptp1
lrwxrwxrwx 1 root root  4 Mar 10 16:04 /dev/ptp_hyperv -> ptp0
ddstreet@test-f:~$ grep . /sys/class/ptp/*/clock_name
/sys/class/ptp/ptp0/clock_name:hyperv
/sys/class/ptp/ptp1/clock_name:mlx5_p2p

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

Title:
  hyperv: unable to distinguish PTP devices

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [impact]

  the /dev/ptp0 device for a hyperv instance may not be the correct,
  hyperv-provided, ptp device.

  [test case]

  on some hyperv instance types, particularly those that might contain
  passthrough network card(s) that also provide ptp, the first ptp
  device may not be the correct one to use for ptp, e.g. there may be
  multiple ones:

  $ ls /dev/ptp*
  /dev/ptp0 /dev/ptp1
  $ cat /sys/class/ptp/ptp0/clock_name
  hyperv
  $ cat /sys/class/ptp/ptp1/clock_name
  mlx5_p2p

  the order can change across boots, so a consistent way of addressing
  the hyperv-provided one is needed

  [regression potential]

  any regression would involve failure to properly create the ptp
  symlink, or other failure while udev is processing newly detected ptp
  device(s)

  [scope]

  this is needed in all releases

  this was fixed upstream with the commit
  32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
  any release

  [original description]

  Hyperv provides a PTP device. On system with multiple PTP devices,
  services like Chrony don't have a way to know which one is which.

  We would like to have a udev rule to create a symlink to the hyperv
  clock. This way, services could be configured to always use this clock
  no matter if it is ptp0, ptp1, etc..

  For example:

  ```
  SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
  ```

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

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


[Touch-packages] [Bug 1913763] Re: hyperv: unable to distinguish PTP devices

2021-03-10 Thread Dan Streetman
ddstreet@test-g:~$ dpkg -l systemd|grep systemd
ii  systemd246.6-1ubuntu1.1 amd64system and service manager
ddstreet@test-g:~$ ls -l /dev/ptp*
crw--- 1 root root 246, 0 Mar 10 15:50 /dev/ptp0
crw--- 1 root root 246, 1 Mar 10 15:50 /dev/ptp1
ddstreet@test-g:~$ grep . /sys/class/ptp/*/clock_name
/sys/class/ptp/ptp0/clock_name:hyperv
/sys/class/ptp/ptp1/clock_name:mlx5_p2p


ddstreet@test-g:~$ dpkg -l systemd|grep systemd
ii  systemd246.6-1ubuntu1.2 amd64system and service manager
ddstreet@test-g:~$ ls -l /dev/ptp*
crw--- 1 root root 246, 0 Mar 10 16:07 /dev/ptp0
crw--- 1 root root 246, 1 Mar 10 16:07 /dev/ptp1
lrwxrwxrwx 1 root root  4 Mar 10 16:07 /dev/ptp_hyperv -> ptp0
ddstreet@test-g:~$ grep . /sys/class/ptp/*/clock_name
/sys/class/ptp/ptp0/clock_name:hyperv
/sys/class/ptp/ptp1/clock_name:mlx5_p2p

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

Title:
  hyperv: unable to distinguish PTP devices

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [impact]

  the /dev/ptp0 device for a hyperv instance may not be the correct,
  hyperv-provided, ptp device.

  [test case]

  on some hyperv instance types, particularly those that might contain
  passthrough network card(s) that also provide ptp, the first ptp
  device may not be the correct one to use for ptp, e.g. there may be
  multiple ones:

  $ ls /dev/ptp*
  /dev/ptp0 /dev/ptp1
  $ cat /sys/class/ptp/ptp0/clock_name
  hyperv
  $ cat /sys/class/ptp/ptp1/clock_name
  mlx5_p2p

  the order can change across boots, so a consistent way of addressing
  the hyperv-provided one is needed

  [regression potential]

  any regression would involve failure to properly create the ptp
  symlink, or other failure while udev is processing newly detected ptp
  device(s)

  [scope]

  this is needed in all releases

  this was fixed upstream with the commit
  32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
  any release

  [original description]

  Hyperv provides a PTP device. On system with multiple PTP devices,
  services like Chrony don't have a way to know which one is which.

  We would like to have a udev rule to create a symlink to the hyperv
  clock. This way, services could be configured to always use this clock
  no matter if it is ptp0, ptp1, etc..

  For example:

  ```
  SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
  ```

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

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


[Touch-packages] [Bug 1913763] Re: hyperv: unable to distinguish PTP devices

2021-03-10 Thread Dan Streetman
root@test-b:~# dpkg -l systemd|grep systemd
ii  systemd237-3ubuntu10.44 amd64system and service manager
root@test-b:~# ls -l /dev/ptp*
crw--- 1 root root 246, 0 Mar 10 15:47 /dev/ptp0
crw--- 1 root root 246, 1 Mar 10 15:47 /dev/ptp1
root@test-b:~# grep . /sys/class/ptp/*/clock_name
/sys/class/ptp/ptp0/clock_name:hyperv
/sys/class/ptp/ptp1/clock_name:mlx5_p2p


root@test-b:~# dpkg -l systemd|grep systemd
ii  systemd237-3ubuntu10.45 amd64system and service manager
root@test-b:~# ls -l /dev/ptp*
crw--- 1 root root 246, 0 Mar 10 15:53 /dev/ptp0
crw--- 1 root root 246, 1 Mar 10 15:53 /dev/ptp1
lrwxrwxrwx 1 root root  4 Mar 10 15:53 /dev/ptp_hyperv -> ptp0
root@test-b:~# grep . /sys/class/ptp/*/clock_name
/sys/class/ptp/ptp0/clock_name:hyperv
/sys/class/ptp/ptp1/clock_name:mlx5_p2p

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

Title:
  hyperv: unable to distinguish PTP devices

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [impact]

  the /dev/ptp0 device for a hyperv instance may not be the correct,
  hyperv-provided, ptp device.

  [test case]

  on some hyperv instance types, particularly those that might contain
  passthrough network card(s) that also provide ptp, the first ptp
  device may not be the correct one to use for ptp, e.g. there may be
  multiple ones:

  $ ls /dev/ptp*
  /dev/ptp0 /dev/ptp1
  $ cat /sys/class/ptp/ptp0/clock_name
  hyperv
  $ cat /sys/class/ptp/ptp1/clock_name
  mlx5_p2p

  the order can change across boots, so a consistent way of addressing
  the hyperv-provided one is needed

  [regression potential]

  any regression would involve failure to properly create the ptp
  symlink, or other failure while udev is processing newly detected ptp
  device(s)

  [scope]

  this is needed in all releases

  this was fixed upstream with the commit
  32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
  any release

  [original description]

  Hyperv provides a PTP device. On system with multiple PTP devices,
  services like Chrony don't have a way to know which one is which.

  We would like to have a udev rule to create a symlink to the hyperv
  clock. This way, services could be configured to always use this clock
  no matter if it is ptp0, ptp1, etc..

  For example:

  ```
  SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
  ```

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

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


[Touch-packages] [Bug 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly

2021-03-10 Thread Sergio Durigan Junior
Thank you for your reply, Riccardo.

I found the following upstream bug report that looks similar to yours:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/204

Can you confirm that this is the same issue?

Your setup seems a bit complex to configure locally, and given that you
said you were able to reproduce this problem on more than one version of
CentOS, I am inclined to believe that, if this is indeed an issue, it
came from upstream.

** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #204
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/204

** Also affects: openvpn via
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/204
   Importance: Unknown
   Status: Unknown

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

Title:
  Network Manager OpenVPN nested connections fail to setup routes
  correctly

Status in OpenVPN:
  Unknown
Status in network-manager package in Ubuntu:
  Incomplete
Status in openvpn package in Ubuntu:
  Incomplete

Bug description:
  Setup:
  Host lan: 192.168.0.238/24
  Host Default gw: 192.168.0.1

  ip route:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 

  
  Primary OpenVPN (check "Use this connection only for resources on its 
network"):
  server ip: public a.b.c.d
  OpenVPN Tunnel: 192.168.1.0/24
  routes pushed: 192.168.100.0/24

  First VPN works OK:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  
  Secondary OpenVPN  (check "Use this connection only for resources on its 
network"):
  server ip: private 192.168.100.10 
  OpenVPN Tunnel: 192.168.20.0/24
  routes pushed: 192.168.200.0/24

  Second VPN Connect OK, routing table is wrong:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 
  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is 
wrong, the openVPN#2 Gateway is not on the local lan

  Correct routing table using "sudo /usr/sbin/openvpn
  /path/to/config.openvpn" (same a Network Manager)

  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  It seems that Network Manager add a wrong additional route not added
  by the openvpn bin:

  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openvpn 2.4.7-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 12:44:39 2021
  InstallationDate: Installed on 2021-02-19 (13 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2021-03-10 Thread dragonhahney
Thank you, sir/madam.

On Wed, Mar 10, 2021, 6:56 AM Sancho <1871...@bugs.launchpad.net> wrote:

> ** Changed in: apt (Ubuntu Bionic)
>Status: In Progress => Fix Released
>
> --
> You received this bug notification because you are subscribed to apt in
> Ubuntu.
> Matching subscriptions: dragonhahney
> https://bugs.launchpad.net/bugs/1871268
>
> Title:
>   Installation fails due to useless immediate configuration error when
>   "Install Third-Party Drivers" is selected
>
> Status in Ubuntu CD Images:
>   Fix Released
> Status in apt package in Ubuntu:
>   Fix Released
> Status in apt source package in Bionic:
>   Fix Released
> Status in apt source package in Focal:
>   Fix Released
> Status in apt source package in Groovy:
>   Fix Released
> Status in apt package in Debian:
>   Fix Released
>
> Bug description:
>   [Impact]
>   Installations that really succeeded would then fail because APT could
> not immediately configure a package. Which is a pointless way to fail at
> that point, because everything did work out anyway.
>
>   We have two changes that help address this:
>
>   * The first one stops immediately configuring multi-arch siblings
>   (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
>   necessary, and caused all the libc6:i386 failures here.
>
>   * The second change sort of also supersedes the first one: It just
>   ignores any errors from immediate configuration, relying on the fact
>   that it's checked and rectified at a later point if there are
>   unconfigured packages (which is what made all those failures happen
>   spuriously after having successfully installed everything).
>
>   [Test case]
>   We have one test case in EIPP format in the Debian bug 973305 which was
> only helped by the second change, not the first one. Run
> /usr/lib/apt/planners < eipp.log and check there are no errors.
>
>   TODO: It's unclear if the APT from proposed installed in the live
>   session will fix the installer, needs investigation, but would make a
>   useful test case.
>
>   [Regression potential]
>   It's imaginable that we missed something somewhere and some path that
> checked for a set error doesn't check it anymore, and we report success
> when we hit an error, but it seems unlikely.
>
>   Behavior of --simulate changes. This used to fail before as well, and
>   will now only produce a warning. We don't believe that is a reason of
>   concern.
>
>   [Groovy SRU]
>   The groovy SRU is a sync of the 2.1.11 micro release from Debian
> unstable which also incorporates changes to the documentation: A typo fix,
> replacing focal with groovy in examples, and minor Dutch manual pages
> translation updates.
>
>   We do not have test cases for the documentation changes, and we do not
>   consider there to be a huge regression potential. As long as they
>   build, they should be readable - maybe some words are wrong in the
>   translation, who knows.
>
>   [Original bug report]
>   Test Case
>   1. Install Ubuntu Desktop on hardware with an nVidia card and select to
> install 3rd party drivers
>   2. Proceed with installation
>
>   The following error message is displayed in /var/log/syslog
>   /plugininstall.py: Verifying downloads ...
>   /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version:
> '9.3.0-1ubuntu2' not found."
>   /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb:
> "Version: '4.4.10-10ubuntu4' not found."
>   /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version:
> '9.3.0-1ubuntu2' not found."
>   /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version:
> '1.2.11.dfsg-2ubuntu1' not found."
>   /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version:
> '1.0.9-0ubuntu1' not found."
>   /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb:
> "Version: '1.1.3-0ubuntu1' not found."
>   /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version:
> '1.6.9-2ubuntu1' not found."
>   /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version:
> '1.3.4-0ubuntu1' not found."
>   /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb:
> "Version: '3.6.0-2ubuntu1' not found."
>   /plugininstall.py: Failed to find package object for
> /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb:
> "Version: '1.6.9-2ubuntu1' not found."
>   /plugininstall.py: Failed to find package object for
> 

[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers

2021-03-10 Thread Balint Reczey
Running "test -x ..." also fails in systemd-nspawn for systemd < 247, I think 
only the following patch needs to be SRU-d to earlier systemd versions: 
https://github.com/systemd/systemd/commit/bcf08acbffdee0d6360d3c31d268e73d0623e5dc


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

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

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

Title:
  test -x fails inside shell scripts in containers

Status in docker.io package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  Opinion
Status in libseccomp package in Ubuntu:
  Fix Committed
Status in runc package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  New
Status in glibc source package in Xenial:
  New
Status in libseccomp source package in Xenial:
  New
Status in runc source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in docker.io source package in Bionic:
  New
Status in glibc source package in Bionic:
  New
Status in libseccomp source package in Bionic:
  New
Status in runc source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in docker.io source package in Focal:
  New
Status in glibc source package in Focal:
  New
Status in libseccomp source package in Focal:
  New
Status in runc source package in Focal:
  New
Status in systemd source package in Focal:
  New
Status in docker.io source package in Groovy:
  New
Status in glibc source package in Groovy:
  New
Status in libseccomp source package in Groovy:
  New
Status in runc source package in Groovy:
  New
Status in systemd source package in Groovy:
  New
Status in docker.io source package in Hirsute:
  New
Status in glibc source package in Hirsute:
  Opinion
Status in libseccomp source package in Hirsute:
  Fix Committed
Status in runc source package in Hirsute:
  New
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:

  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#

  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail

  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #

  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--==
  ii  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement

  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.

  The build fails with:

  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
  them is required for this operation

  The simple Dockerfile to reproduce the error - "docker build -t foo ."

  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 

  USER root

  RUN apt-get update \
   && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
    && curl https://syncthing.net/release-key.txt | apt-key add -

  Breaking it down it this seems to be an issue that there is new
  functionality in apt/apt-key e.g. security hardening that docker
  prohibits in its containers. Running this manually works only in an
  --privileged container.

  So adding keys in unpriviledged container or possibly kubernetes will
  not work anymore.

  Flo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions

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

[Touch-packages] [Bug 1894172] Re: isc-dhcp-server using wrong env variable for INTERFACES

2021-03-10 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~utkarsh/ubuntu/+source/isc-dhcp/+git/isc-dhcp/+merge/399442

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

Title:
  isc-dhcp-server using wrong env variable for INTERFACES

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Bionic:
  Confirmed
Status in isc-dhcp source package in Focal:
  Confirmed
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  [Impact]

  When checking isc-dhcp-server unit file it was seen that isc-dhcp-
  server is being started by:

  ConditionPathExists=/etc/default/isc-dhcp-server
  ConditionPathExists=|/etc/ltsp/dhcpd.conf
  ConditionPathExists=|/etc/dhcp/dhcpd.conf

  [Service]
  EnvironmentFile=/etc/default/isc-dhcp-server
  RuntimeDirectory=dhcp-server
  # The leases files need to be root:dhcpd even when dropping privileges
  ExecStart=/bin/sh -ec '\
  CONFIG_FILE=/etc/dhcp/dhcpd.conf; \
  if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; 
fi; \
  [ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \
  chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \
  chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \
  exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES'

  But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and
  $INTERFACESv6.

  This causes the service to listen on all interfaces, which is what the
  user might not want. In case the user wants to use *only* IPv6 and not
  IPv4, this could maybe lead to problems as what the user intended to
  do could be really different from what the outcome turns out to be
  (because of this bug).

  The previous upload(er) forgot to mention (and split) the INTERFACES
  variable to v4 and v6 and as a result, it has been this way for so
  long.

  The SRU would split the variables into respective names, thereby
  making sure that what /etc/default/isc-dhcp-serve sets, is available
  in the respective service file.

  [Test Plan]

  To reproduce this bug, simply do the following:

  $ lxc launch ubuntu-daily:focal isc-dhcp-lp1894172-focal

  $ lxc shell isc-dhcp-lp1894172-focal

  # apt update && apt install isc-dhcp-server -y

  # grep "INTERFACES" /etc/default/isc-dhcp-server
  INTERFACESv4=""
  INTERFACESv6=""

  grep "INTERFACES" /lib/systemd/system/isc-dhcp-server.service
  exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES'

  # grep "INTERFACES" /lib/systemd/system/isc-dhcp-server6.service
  exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid 
-cf $CONFIG_FILE $INTERFACES'

  With this, it is clearly visible that even though /lib/systemd/system
  /isc-dhcp-server{,6}.service file uses the INTERFACES variable but the
  /etc/default/isc-dhcp-server defines 2 different variables,
  INTERFACESv4 and INTERFACESv6.

  After the SRU is performed, the respective services files should use
  INTERFACESv4 and INTERFACESv6 variable, instead of just INTERFACES.

  To ensure smooth upgrade of this package, we'd check if the user
  hasn't manually set a INTERFACESv{4,6} variable to workaround this
  bug. If they have, then we simply check and make sure, we use the
  correct variable.

  [Where problems could occur]

  The problem could occur if the user has manually set some different
  workaround for this bug and so the usual upgrade could break some of
  their old configuration(s).

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

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


[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2021-03-10 Thread Sancho
** Changed in: apt (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

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

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 

[Touch-packages] [Bug 1915966] Re: Please merge initramfs-tools 0.139 from Debian unstable

2021-03-10 Thread Dave Jones
Attaching revised patch with needs-root added to the new qemu-related
tests (to work around build failure:
https://launchpad.net/ubuntu/+source/initramfs-
tools/0.139ubuntu1/+build/21138158)

** Patch added: "2-1915966.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1915966/+attachment/5475404/+files/2-1915966.debdiff

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

Title:
  Please merge initramfs-tools 0.139 from Debian unstable

Status in initramfs-tools package in Ubuntu:
  Fix Committed

Bug description:
  Please merge initramfs-tools 0.139 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  shortly.

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

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


[Touch-packages] [Bug 1894172] Re: isc-dhcp-server using wrong env variable for INTERFACES

2021-03-10 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~utkarsh/ubuntu/+source/isc-dhcp/+git/isc-dhcp/+merge/399440

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

Title:
  isc-dhcp-server using wrong env variable for INTERFACES

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Bionic:
  Confirmed
Status in isc-dhcp source package in Focal:
  Confirmed
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  [Impact]

  When checking isc-dhcp-server unit file it was seen that isc-dhcp-
  server is being started by:

  ConditionPathExists=/etc/default/isc-dhcp-server
  ConditionPathExists=|/etc/ltsp/dhcpd.conf
  ConditionPathExists=|/etc/dhcp/dhcpd.conf

  [Service]
  EnvironmentFile=/etc/default/isc-dhcp-server
  RuntimeDirectory=dhcp-server
  # The leases files need to be root:dhcpd even when dropping privileges
  ExecStart=/bin/sh -ec '\
  CONFIG_FILE=/etc/dhcp/dhcpd.conf; \
  if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; 
fi; \
  [ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \
  chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \
  chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \
  exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES'

  But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and
  $INTERFACESv6.

  This causes the service to listen on all interfaces, which is what the
  user might not want. In case the user wants to use *only* IPv6 and not
  IPv4, this could maybe lead to problems as what the user intended to
  do could be really different from what the outcome turns out to be
  (because of this bug).

  The previous upload(er) forgot to mention (and split) the INTERFACES
  variable to v4 and v6 and as a result, it has been this way for so
  long.

  The SRU would split the variables into respective names, thereby
  making sure that what /etc/default/isc-dhcp-serve sets, is available
  in the respective service file.

  [Test Plan]

  To reproduce this bug, simply do the following:

  $ lxc launch ubuntu-daily:focal isc-dhcp-lp1894172-focal

  $ lxc shell isc-dhcp-lp1894172-focal

  # apt update && apt install isc-dhcp-server -y

  # grep "INTERFACES" /etc/default/isc-dhcp-server
  INTERFACESv4=""
  INTERFACESv6=""

  grep "INTERFACES" /lib/systemd/system/isc-dhcp-server.service
  exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES'

  # grep "INTERFACES" /lib/systemd/system/isc-dhcp-server6.service
  exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid 
-cf $CONFIG_FILE $INTERFACES'

  With this, it is clearly visible that even though /lib/systemd/system
  /isc-dhcp-server{,6}.service file uses the INTERFACES variable but the
  /etc/default/isc-dhcp-server defines 2 different variables,
  INTERFACESv4 and INTERFACESv6.

  After the SRU is performed, the respective services files should use
  INTERFACESv4 and INTERFACESv6 variable, instead of just INTERFACES.

  To ensure smooth upgrade of this package, we'd check if the user
  hasn't manually set a INTERFACESv{4,6} variable to workaround this
  bug. If they have, then we simply check and make sure, we use the
  correct variable.

  [Where problems could occur]

  The problem could occur if the user has manually set some different
  workaround for this bug and so the usual upgrade could break some of
  their old configuration(s).

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

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


[Touch-packages] [Bug 1894172] Re: isc-dhcp-server using wrong env variable for INTERFACES

2021-03-10 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~utkarsh/ubuntu/+source/isc-dhcp/+git/isc-dhcp/+merge/399438

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

Title:
  isc-dhcp-server using wrong env variable for INTERFACES

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Bionic:
  Confirmed
Status in isc-dhcp source package in Focal:
  Confirmed
Status in isc-dhcp source package in Groovy:
  Confirmed

Bug description:
  [Impact]

  When checking isc-dhcp-server unit file it was seen that isc-dhcp-
  server is being started by:

  ConditionPathExists=/etc/default/isc-dhcp-server
  ConditionPathExists=|/etc/ltsp/dhcpd.conf
  ConditionPathExists=|/etc/dhcp/dhcpd.conf

  [Service]
  EnvironmentFile=/etc/default/isc-dhcp-server
  RuntimeDirectory=dhcp-server
  # The leases files need to be root:dhcpd even when dropping privileges
  ExecStart=/bin/sh -ec '\
  CONFIG_FILE=/etc/dhcp/dhcpd.conf; \
  if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; 
fi; \
  [ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \
  chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \
  chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \
  exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES'

  But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and
  $INTERFACESv6.

  This causes the service to listen on all interfaces, which is what the
  user might not want. In case the user wants to use *only* IPv6 and not
  IPv4, this could maybe lead to problems as what the user intended to
  do could be really different from what the outcome turns out to be
  (because of this bug).

  The previous upload(er) forgot to mention (and split) the INTERFACES
  variable to v4 and v6 and as a result, it has been this way for so
  long.

  The SRU would split the variables into respective names, thereby
  making sure that what /etc/default/isc-dhcp-serve sets, is available
  in the respective service file.

  [Test Plan]

  To reproduce this bug, simply do the following:

  $ lxc launch ubuntu-daily:focal isc-dhcp-lp1894172-focal

  $ lxc shell isc-dhcp-lp1894172-focal

  # apt update && apt install isc-dhcp-server -y

  # grep "INTERFACES" /etc/default/isc-dhcp-server
  INTERFACESv4=""
  INTERFACESv6=""

  grep "INTERFACES" /lib/systemd/system/isc-dhcp-server.service
  exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES'

  # grep "INTERFACES" /lib/systemd/system/isc-dhcp-server6.service
  exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid 
-cf $CONFIG_FILE $INTERFACES'

  With this, it is clearly visible that even though /lib/systemd/system
  /isc-dhcp-server{,6}.service file uses the INTERFACES variable but the
  /etc/default/isc-dhcp-server defines 2 different variables,
  INTERFACESv4 and INTERFACESv6.

  After the SRU is performed, the respective services files should use
  INTERFACESv4 and INTERFACESv6 variable, instead of just INTERFACES.

  To ensure smooth upgrade of this package, we'd check if the user
  hasn't manually set a INTERFACESv{4,6} variable to workaround this
  bug. If they have, then we simply check and make sure, we use the
  correct variable.

  [Where problems could occur]

  The problem could occur if the user has manually set some different
  workaround for this bug and so the usual upgrade could break some of
  their old configuration(s).

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

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


[Touch-packages] [Bug 1917298] Re: dbus-daemon not started after reboot

2021-03-10 Thread Balint Reczey
** Also affects: dbus (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

Title:
  dbus-daemon not started after reboot

Status in dbus package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in dbus source package in Focal:
  New
Status in systemd source package in Focal:
  New

Bug description:
  In the past weeks we experienced few systems coming up without started
  dbus-daemon after reboots due to updates.

  The first occurrence happens on January 21th 2021, since this time we
  were experiencing 0 up to 2 machines with this issue on each reboot
  cycle affecting all (approx 20) Ubuntu 20.4 (Focal Fossa) LTS
  machines.

  On January 21th the machines were rebooted due to a kernel update. On
  January 19th there were updates for systemd (systemd:amd64 from
  245.4-4ubuntu3.3 undated to 245.4-4ubuntu3.4) installed.

  The Symptoms seem to be:
  ```
  root@es1:~# systemctl status dbus
  ● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: 
enabled)
   Active: inactive (dead)
  TriggeredBy: ● dbus.socket
     Docs: man:dbus-daemon(1)
  ```

  There is no `dbus-daemon` process running any more after reboot.

  The messages in /var/log/syslog:
  ```
  Feb 24 09:21:52 runner1 kernel: [   11.005391] systemd[1]: sockets.target: 
Found ordering cycle on dbus.socket/start
  [...]
  Feb 24 09:21:52 runner1 kernel: [   11.012386] systemd[1]: sockets.target: 
Job dbus.socket/start deleted to break ordering cycle starting with 
sockets.target/start
  ```

  Jounalctl output ends with the dbus-Shutdown before reboot, and it is
  not updated any more.

  When rebooting the affected machine again, this does'nt occur again,
  and the dbus-daemon is started and working again. We experienced this
  on 4 rather different machines on 6 reboot cycles across all Ubuntu
  20.4 (Focal Fossa) LTS machines till now.

  We are not experiencing this on other LTS releases than 20.4.

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

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


[Touch-packages] [Bug 1917677] Re: ubuntu: ucf tracking of valid known md5sums should be limited to only those md5sums that affect a given distro release

2021-03-10 Thread Robie Basak
See also: bug 1915547

> It is highly unlikely that the configuration file on one distro is
replaced with one that was shipped on a different one.

I think it's more likely than you say in cases that a configuration
shipped is primarily a set of boolean values and enumerations of a
limited set of strings, and the difference in distributions is mostly in
choices of those values. The extreme example would be a configuration
file that ships just one boolean setting. I think this unattended-
upgrades case is closer to that extreme example than it is to openssh's
sshd_config.

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

Title:
  ubuntu: ucf tracking of valid known md5sums   should be limited to
  only those md5sums that affect a given distro release

Status in unattended-upgrades package in Ubuntu:
  New
Status in unattended-upgrades source package in Bionic:
  New
Status in unattended-upgrades source package in Focal:
  New
Status in unattended-upgrades source package in Groovy:
  New
Status in unattended-upgrades source package in Hirsute:
  New

Bug description:
  Currently the project tracks all valid md5sums of permutations of
  50unattended-upgrades.conf in a single md5sum file that contains every
  md5sum of every historic version of all unique distros:

   50unattended-upgrades.Debian
   50unattended-upgrades.Devuan
   50unattended-upgrades.Raspbian
   50unattended-upgrades.Ubuntu

  Ultimately ucf for a given packaging release should only track the
  applicable md5sums which are expected to be seen on that particular
  distribution and release.

  For example:
 On Ubuntu Bionic: valid md5sums should be limited to the md5sum of the 
most recent Ubuntu Xenial 50unattended-upgrades.conf and the md5sums of 
previous Ubuntu Bionic releases to allow Xenial->Bionic and Bionic->Bionic 
upgrades without prompt.

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

-- 
Mailing list: https://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 1651500] Re: [ASUS X441SA] [8086:2284] No sound at all

2021-03-10 Thread W.R. Irsyad Hamda
Thank you very much for your kindness, now I have upgraded my ubuntu to
focal, but I still don't understand how to solve my problem with the code,
because I am just common user of ubuntu, I don't know about coding and
manything about ubuntu system, can you help me to solve this ?

Pada tanggal Rab, 10 Mar 2021 pukul 15.41 Po-Hsu Lin <
1651...@bugs.launchpad.net> menulis:

> Hi W.R. Irsyad Hamda,
>
> Looks like this is the fix:
>
> https://github.com/torvalds/linux/commit/216d7aebbfbe1d3361e21c3a97d1607e1c1c48cd
>
> It's been added to Bionic:
>
> https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/tree/sound/pci/hda/patch_realtek.c#n7071
>
> And Focal kernel.
>
> https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/tree/sound/pci/hda/patch_realtek.c#n7887
>
> As this bug is quite old,
> do you still need the fix in 4.4 Xenial?
> Thanks
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1651500
>
> Title:
>   [ASUS X441SA] [8086:2284] No sound at all
>
> Status in alsa-driver package in Ubuntu:
>   Confirmed
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   1. Release of ubuntu
>   Description:  Ubuntu 16.04.1 LTS
>   Release:  16.04
>
>   2. version of the package
>   AlsaMixer v1.1.0
>
>
>   3. I expect to hear sound from speaker
>
>   4. I can not any sound from speaker
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
>   Uname: Linux 4.4.0-53-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.4
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  hamda  1627 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Tue Dec 20 22:51:08 2016
>   InstallationDate: Installed on 2016-12-15 (5 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:PCH failed
>   Symptom_Card: Built-in Audio - HDA Intel PCH
>   Symptom_DevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  hamda  1627 F pulseaudio
>   Symptom_Jack: Speaker, Internal
>   Symptom_Type: No sound at all
>   Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/08/2016
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: X441SA.301
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: X441SA
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: 1.0
>   dmi.chassis.asset.tag: ATN12345678901234567
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK COMPUTER INC.
>   dmi.chassis.version: 1.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
>   dmi.product.name: X441SA
>   dmi.product.version: 1.0
>   dmi.sys.vendor: ASUSTeK COMPUTER INC.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1651500/+subscriptions
>

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

Title:
  [ASUS X441SA] [8086:2284] No sound at all

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

Bug description:
  1. Release of ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2. version of the package
  AlsaMixer v1.1.0

  
  3. I expect to hear sound from speaker

  4. I can not any sound from speaker

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hamda  1627 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec 20 22:51:08 2016
  InstallationDate: Installed on 2016-12-15 (5 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:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hamda  1627 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all
  

[Touch-packages] [Bug 1664846] Re: [Wishlist] Support for teaming driver

2021-03-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [Wishlist] Support for teaming driver

Status in netplan:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The MAAS team is supporting a customer who is using the 'teaming'
  driver rather than the 'bonding' driver. This is essentially a bonding
  driver which also delivers some additional features, and has
  additional userspace runtime control.

  Netplan should allow for bonds to be configured with the teaming
  driver in addition to the bonding driver.

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

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


[Touch-packages] [Bug 1916725] Re: Protected/Important packages are not deconfigured, require Force-LoopBreak

2021-03-10 Thread Julian Andres Klode
** Description changed:

  [Impact]
  If a package that is Protected: yes (or Important: yes), or one of it's 
dependencies, is involved in a dependency loop with Breaks, APT requires 
APT::Force-LoopBreak instead of resolving the situation directly.
+ 
+ On focal, we also introduce the actual support for protected packages to
+ enable upgrading to later releases more easily (in case a protected
+ package needs to be removed during the upgrade), and to make the
+ backport more similar to main.
  
  [Test plan]
  Run the integration test suite (the autopkgtest) :)
  
  Our test suite covers the tests for both Breaks and Conflicts.
  
  Breaks:
  
  protected-sysvinit (= 1) without dependencies is installed
  protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv
  protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2)
  
  Test: Install protected-sysvinit (= 2)
  Expected result: Unpacking protected-sysvinit (= 2) deconfigures 
protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit 
(= 2) and end up with a working system.
  
  Conflicts: As for Breaks, but the Conflicts will remove the package
  temporarily, requiring the use of APT::Force-LoopBreak option.
  
+ For focal, we also do have a test to check that the Protected field is
+ being used.
+ 
  [Where problems could occur]
  We now allow dpkg to automatically deconfigure protected packages. This 
should just make them behave like normal packages to APT's eye, but bugs I 
guess could occur somewhere in the APT/dpkg interaction (this only applies to 
releases with Protected support in dpkg, Important is not affected, it's always 
been "normal" for dpkg).
  
  During development, we accidentally simplified the patch so much that
  Conflicts did not require Force-LoopBreak for temporary removal. We
  fixed that, but it points out that there is a place where the loop break
  check happens that is a potential regression place.
+ 
+ On focal, we pass additional flags to dpkg that focal's dpkg does not
+ understand, however, we only do that if dpkg asserts it does that, so in
+ practice, this should all work fine and the code path will only be taken
+ with >=groovy dpkg.

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

Title:
  Protected/Important packages are not deconfigured, require Force-
  LoopBreak

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Triaged
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  In Progress
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  If a package that is Protected: yes (or Important: yes), or one of it's 
dependencies, is involved in a dependency loop with Breaks, APT requires 
APT::Force-LoopBreak instead of resolving the situation directly.

  On focal, we also introduce the actual support for protected packages
  to enable upgrading to later releases more easily (in case a protected
  package needs to be removed during the upgrade), and to make the
  backport more similar to main.

  [Test plan]
  Run the integration test suite (the autopkgtest) :)

  Our test suite covers the tests for both Breaks and Conflicts.

  Breaks:

  protected-sysvinit (= 1) without dependencies is installed
  protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv
  protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2)

  Test: Install protected-sysvinit (= 2)
  Expected result: Unpacking protected-sysvinit (= 2) deconfigures 
protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit 
(= 2) and end up with a working system.

  Conflicts: As for Breaks, but the Conflicts will remove the package
  temporarily, requiring the use of APT::Force-LoopBreak option.

  For focal, we also do have a test to check that the Protected field is
  being used.

  [Where problems could occur]
  We now allow dpkg to automatically deconfigure protected packages. This 
should just make them behave like normal packages to APT's eye, but bugs I 
guess could occur somewhere in the APT/dpkg interaction (this only applies to 
releases with Protected support in dpkg, Important is not affected, it's always 
been "normal" for dpkg).

  During development, we accidentally simplified the patch so much that
  Conflicts did not require Force-LoopBreak for temporary removal. We
  fixed that, but it points out that there is a place where the loop
  break check happens that is a potential regression place.

  On focal, we pass additional flags to dpkg that focal's dpkg does not
  understand, however, we only do that if dpkg asserts it does that, so
  in practice, this should all work fine and the code path will only be
  taken with >=groovy dpkg.

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


[Touch-packages] [Bug 1818713] Re: WARNING: icon cache generation failed when installing elementary-icon-theme

2021-03-10 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 962225 ***
https://bugs.launchpad.net/bugs/962225

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  WARNING: icon cache generation failed when installing elementary-icon-
  theme

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  WHen installing elementary-icon-theme, receive the message:

  gtk-update-icon-cache: The generated cache was invalid.
  WARNING: icon cache generation failed for /usr/share/icons/elementary

  
  I believe this is because there is a folder with a space in the name:

  root@howard:/usr/share/icons/elementary# find ./ -name "* *"
  ./status/48/untitled folder

  After removing that directory, the cache is created successfully:
  root@howard:/usr/share/icons/elementary# rm -rf "./status/48/untitled folder"
  root@howard:/usr/share/icons/elementary# gtk-update-icon-cache 
/usr/share/icons/elementary
  gtk-update-icon-cache: Cache file created successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1818713/+subscriptions

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


[Touch-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

2021-03-10 Thread Sergio S
This bug affects me too.
Linux laptop 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 20.04.2 LTS


I think this bug may (at least in some cases) be related to this here question: 
https://askubuntu.com/questions/1234807/no-sound-after-sleep-ubuntu-20-04 .

The solution they found involves removing the sound device and
requesting a rescan:

echo 1 > /sys/bus/pci/devices//remove
echo 1 > /sys/bus/pci/rescan

They automated this through a script such as this one:
https://github.com/GHopperMSK/configs/blob/master/bin/restart-sound

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

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 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: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx: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/1888598/+subscriptions

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


[Touch-packages] [Bug 1918410] Re: isc-dhcp-client denied by apparmor

2021-03-10 Thread Anisse Astier
I forgot to add that this is an up-to-date Ubuntu 20.04.2

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

Title:
  isc-dhcp-client denied by apparmor

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Hi, I get weird errors in the audit log, seeing dhclient is being
  denied reading its comm or the comm of one of its tasks:

  
  [1383307.827378] audit: type=1400 audit(1615367094.054:162): 
apparmor="DENIED" operation="open" profile="/{,usr/}sbin/dhclient" 
name="/proc/1095210/task/1095213/comm" pid=1095210 comm="dhclient" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0

  This might or might not be linked with the fact that I can't get an
  IPv4 on this interface. Note that it happened to other, see this
  comment:

  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1413232/comments/8

  Or even an article recommending disabling apparmor for dhclient(!):
  
https://blog.anthony-jacob.com/perte-dip-v4-sous-ubuntu-20-04-apparmor-et-dhclient/

  
  As I said, I'm not sure this is the root cause of the lack of IPv4 renewal, 
because running it manually *does* succeed in getting an IP. And running it in 
strace shows the EACCES failure:

  [pid 1095210] openat(AT_FDCWD, "/proc/self/task/1095211/comm", O_RDWRstrace: 
Process 1095211 attached
  ) = -1 EACCES (Permission non accordée)

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

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


[Touch-packages] [Bug 1918410] [NEW] isc-dhcp-client denied by apparmor

2021-03-10 Thread Anisse Astier
Public bug reported:

Hi, I get weird errors in the audit log, seeing dhclient is being denied
reading its comm or the comm of one of its tasks:


[1383307.827378] audit: type=1400 audit(1615367094.054:162): apparmor="DENIED" 
operation="open" profile="/{,usr/}sbin/dhclient" 
name="/proc/1095210/task/1095213/comm" pid=1095210 comm="dhclient" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0

This might or might not be linked with the fact that I can't get an IPv4
on this interface. Note that it happened to other, see this comment:

https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1413232/comments/8

Or even an article recommending disabling apparmor for dhclient(!):
https://blog.anthony-jacob.com/perte-dip-v4-sous-ubuntu-20-04-apparmor-et-dhclient/


As I said, I'm not sure this is the root cause of the lack of IPv4 renewal, 
because running it manually *does* succeed in getting an IP. And running it in 
strace shows the EACCES failure:

[pid 1095210] openat(AT_FDCWD, "/proc/self/task/1095211/comm", O_RDWRstrace: 
Process 1095211 attached
) = -1 EACCES (Permission non accordée)

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  isc-dhcp-client denied by apparmor

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Hi, I get weird errors in the audit log, seeing dhclient is being
  denied reading its comm or the comm of one of its tasks:

  
  [1383307.827378] audit: type=1400 audit(1615367094.054:162): 
apparmor="DENIED" operation="open" profile="/{,usr/}sbin/dhclient" 
name="/proc/1095210/task/1095213/comm" pid=1095210 comm="dhclient" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0

  This might or might not be linked with the fact that I can't get an
  IPv4 on this interface. Note that it happened to other, see this
  comment:

  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1413232/comments/8

  Or even an article recommending disabling apparmor for dhclient(!):
  
https://blog.anthony-jacob.com/perte-dip-v4-sous-ubuntu-20-04-apparmor-et-dhclient/

  
  As I said, I'm not sure this is the root cause of the lack of IPv4 renewal, 
because running it manually *does* succeed in getting an IP. And running it in 
strace shows the EACCES failure:

  [pid 1095210] openat(AT_FDCWD, "/proc/self/task/1095211/comm", O_RDWRstrace: 
Process 1095211 attached
  ) = -1 EACCES (Permission non accordée)

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

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


[Touch-packages] [Bug 875660]

2021-03-10 Thread Chain
I haven't seen it for ages, using phonon-vlc (which is the default I
guess?)

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

Title:
  PA and knotify startup race leads to wrong device selection

Status in Phonon:
  Unknown
Status in kde-runtime package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  This appears to be a regression in Oneiric.
  I'm running Kubuntu with pulseaudio.
  I have on my motherboard intel hda analog audio and my graphics card (an ATI) 
had an HDMI out; by default I like the audio to come out of the analog output 
that is the only one connected.

  Sometimes logging into KDE I find that it's decided to switch to the
  HDMI as the default; today I caught it and did an lsof /dev/snd/* and
  found:

  knotify4  2276   dg  memCHR  116,3  6691 /dev/snd/pcmC0D0p
  knotify4  2276   dg   20r   CHR 116,33  0t0 9995 /dev/snd/timer
  knotify4  2276   dg   21u   CHR  116,3  0t0 6691 /dev/snd/pcmC0D0p
  pulseaudi 2893   dg   24u   CHR  116,9  0t0 6698 /dev/snd/controlC1   


  
  pulseaudi 2893   dg   31u   CHR  116,6  0t0 6694 /dev/snd/controlC0   


  
  pulseaudi 2893   dg   38u   CHR  116,6  0t0 6694 /dev/snd/controlC0   


  

  So knotify4 has hogged the analog output, and hence pa can't get in.

  So I kill knotify4, and do a pactl exit to restart pa - but pa then
  still lists the HDMI as the default output in paman, and I can't see a
  way to get it back to default without restarting everything.

  I'm also going to subscribe this bug to kde-runtime; I'm not sure who
  is supposed to manage the race between pa startup and anything else,
  and I'm not sure if it's a kubuntu special or KDE in general.

  Dave

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: pulseaudio 1:1.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dg 4889 F pulseaudio
   /dev/snd/controlC0:  dg 4889 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfbcf8000 irq 47'
 Mixer name : 'VIA VT1708S'
 Components : 'HDA:11060397,18490397,0010'
 Controls  : 37
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 48'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  CheckboxSubmission: f2d10bd9f943a85b486a282e7840a570
  CheckboxSystem: 0531969bcfd4f03af7405c98dc94a948
  Date: Sun Oct 16 12:31:37 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to oneiric on 2011-09-24 (21 days ago)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: P55M Pro
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/10/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 875660]

2021-03-10 Thread Justin Zobel
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you
can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status
to resolved.

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

Title:
  PA and knotify startup race leads to wrong device selection

Status in Phonon:
  Unknown
Status in kde-runtime package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  This appears to be a regression in Oneiric.
  I'm running Kubuntu with pulseaudio.
  I have on my motherboard intel hda analog audio and my graphics card (an ATI) 
had an HDMI out; by default I like the audio to come out of the analog output 
that is the only one connected.

  Sometimes logging into KDE I find that it's decided to switch to the
  HDMI as the default; today I caught it and did an lsof /dev/snd/* and
  found:

  knotify4  2276   dg  memCHR  116,3  6691 /dev/snd/pcmC0D0p
  knotify4  2276   dg   20r   CHR 116,33  0t0 9995 /dev/snd/timer
  knotify4  2276   dg   21u   CHR  116,3  0t0 6691 /dev/snd/pcmC0D0p
  pulseaudi 2893   dg   24u   CHR  116,9  0t0 6698 /dev/snd/controlC1   


  
  pulseaudi 2893   dg   31u   CHR  116,6  0t0 6694 /dev/snd/controlC0   


  
  pulseaudi 2893   dg   38u   CHR  116,6  0t0 6694 /dev/snd/controlC0   


  

  So knotify4 has hogged the analog output, and hence pa can't get in.

  So I kill knotify4, and do a pactl exit to restart pa - but pa then
  still lists the HDMI as the default output in paman, and I can't see a
  way to get it back to default without restarting everything.

  I'm also going to subscribe this bug to kde-runtime; I'm not sure who
  is supposed to manage the race between pa startup and anything else,
  and I'm not sure if it's a kubuntu special or KDE in general.

  Dave

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: pulseaudio 1:1.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dg 4889 F pulseaudio
   /dev/snd/controlC0:  dg 4889 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfbcf8000 irq 47'
 Mixer name : 'VIA VT1708S'
 Components : 'HDA:11060397,18490397,0010'
 Controls  : 37
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 48'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  CheckboxSubmission: f2d10bd9f943a85b486a282e7840a570
  CheckboxSystem: 0531969bcfd4f03af7405c98dc94a948
  Date: Sun Oct 16 12:31:37 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to oneiric on 2011-09-24 (21 days ago)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: P55M Pro
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd09/10/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

2021-03-10 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

Title:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver).

  Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl.

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

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


[Touch-packages] [Bug 1918406] Re: I cannot move/resize program windows

2021-03-10 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1917926 ***
https://bugs.launchpad.net/bugs/1917926

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


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

** This bug has been marked a duplicate of bug 1917926
   Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1

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

Title:
  I cannot move/resize program windows

Status in mutter package in Ubuntu:
  New

Bug description:
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  Codename: hirsute
  Linux thinkpad 5.10.0-14-generic #15-Ubuntu SMP Fri Jan 29 15:10:03 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

  Happens with every program.

  I have updated my computer from 20.10, so not a clean install.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.39  Thu Jan 21 21:54:06 
UTC 2021
   GCC version:  gcc version 10.2.1 20210306 (Ubuntu 10.2.1-21ubuntu1)
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 10:05:55 2021
  DistUpgraded: 2021-03-09 19:16:34,361 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.39, 5.10.0-14-generic, x86_64: installed
   virtualbox, 6.1.18, 5.10.0-14-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics [17aa:22c0]
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c0]
  InstallationDate: Installed on 2021-03-06 (3 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20TJS02U00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic 
root=UUID=e8d0877a-c7f2-4640-a9b2-f935857169c2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-03-09 (0 days ago)
  dmi.bios.date: 12/21/2020
  dmi.bios.release: 1.12
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2VET27W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TJS02U00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET27W(1.12):bd12/21/2020:br1.12:efr1.7:svnLENOVO:pn20TJS02U00:pvrThinkPadP1Gen3:rvnLENOVO:rn20TJS02U00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 3
  dmi.product.name: 20TJS02U00
  dmi.product.sku: LENOVO_MT_20TJ_BU_Think_FM_ThinkPad P1 Gen 3
  dmi.product.version: ThinkPad P1 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.4-1
  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.10-3ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 

[Touch-packages] [Bug 1911030] Re: Graphical flashes on a raspi 4

2021-03-10 Thread Daniel van Vugt
I'm not seeing this bug at all in a newly installed 21.04 Pi4. Can you
please update and retest?

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

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

** Changed in: mesa (Ubuntu)
   Importance: Low => Medium

** Changed in: xorg-server (Ubuntu)
   Importance: Low => Medium

** Bug watch removed: github.com/raspberrypi/linux/issues #4080
   https://github.com/raspberrypi/linux/issues/4080

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

Title:
  Graphical flashes on a raspi 4

Status in mesa package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1918406] [NEW] I cannot move/resize program windows

2021-03-10 Thread Herbert Post
Public bug reported:

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04
Codename:   hirsute
Linux thinkpad 5.10.0-14-generic #15-Ubuntu SMP Fri Jan 29 15:10:03 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

Happens with every program.

I have updated my computer from 20.10, so not a clean install.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.39  Thu Jan 21 21:54:06 
UTC 2021
 GCC version:  gcc version 10.2.1 20210306 (Ubuntu 10.2.1-21ubuntu1)
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 10 10:05:55 2021
DistUpgraded: 2021-03-09 19:16:34,361 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 460.39, 5.10.0-14-generic, x86_64: installed
 virtualbox, 6.1.18, 5.10.0-14-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo UHD Graphics [17aa:22c0]
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c0]
InstallationDate: Installed on 2021-03-06 (3 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 20TJS02U00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic 
root=UUID=e8d0877a-c7f2-4640-a9b2-f935857169c2 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to hirsute on 2021-03-09 (0 days ago)
dmi.bios.date: 12/21/2020
dmi.bios.release: 1.12
dmi.bios.vendor: LENOVO
dmi.bios.version: N2VET27W (1.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TJS02U00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.7
dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET27W(1.12):bd12/21/2020:br1.12:efr1.7:svnLENOVO:pn20TJS02U00:pvrThinkPadP1Gen3:rvnLENOVO:rn20TJS02U00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P1 Gen 3
dmi.product.name: 20TJS02U00
dmi.product.sku: LENOVO_MT_20TJ_BU_Think_FM_ThinkPad P1 Gen 3
dmi.product.version: ThinkPad P1 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.4-1
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.10-3ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute reproducible 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/1918406

Title:
  I cannot move/resize program windows

Status in xorg package in Ubuntu:
  New

Bug description:
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  Codename: hirsute
  Linux thinkpad 5.10.0-14-generic #15-Ubuntu SMP Fri Jan 29 15:10:03 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

  Happens with every program.

  I have updated my computer from 20.10, so not a clean install.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 

[Touch-packages] [Bug 1911030] Re: Graphical flashes on a raspi 4 when software rendering is forced

2021-03-10 Thread Daniel van Vugt
Ah right, sorry. Your workaround is to force software rendering :)

** Summary changed:

- Graphical flashes on a raspi 4 when software rendering is forced
+ Graphical flashes on a raspi 4

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

Title:
  Graphical flashes on a raspi 4

Status in mesa package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

2021-03-10 Thread Daniel van Vugt
** Changed in: mesa (Ubuntu)
   Importance: Undecided => High

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

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

Status in Mutter:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver).

  Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl.

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

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


[Touch-packages] [Bug 1911030] Re: Graphical flashes on a raspi 4 when software rendering is forced

2021-03-10 Thread fossfreedom
hmm?  No this issue is with the default fkms out of the box overlay - so
nothing is forced here.

What I was also saying that the v3d overlay overcomes the flashes issue
... but only if you copy the overlay into the overlays folder as
upstream pi maintainers say should be happening with the Ubuntu kernel
anyway.

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

Title:
  Graphical flashes on a raspi 4 when software rendering is forced

Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1899878] Re: Python's test_ssl fails starting from Ubuntu 20.04

2021-03-10 Thread Christian Heimes
In upstream OpenSSL, (3) is the same as (1) for a pristine
SSL_CTX_new(TLS_method()) context.

As far as I can see, the Ubuntu patch effectively sets the minimum
version to TLS 1.2 and prevents users from setting TLS 1.0 and 1.1. I
propose that the patch also changes the value of minimum protocol on the
CTX, so (1) reports TLS1_2_VERSION as current value.

OpenSSL upstream is not going to accept a new function into 1.1.1 LTS
branch.

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

Title:
  Python's test_ssl fails starting from Ubuntu 20.04

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  Please take a look at https://bugs.python.org/issue41561. Developers
  who work on Python think that the issue is due to a change in Ubuntu
  20.04 that is best described by
  https://bugs.python.org/issue41561#msg378089:

  "It sounds like a Debian/Ubuntu patch is breaking an assumption. Did
  somebody report the bug with Debian/Ubuntu maintainers of OpenSSL
  already? Fedora also configures OpenSSL with minimum protocol version
  of TLS 1.2. The distribution does it in a slightly different way that
  makes the restriction discoverable and that is compatible with
  Python's test suite."

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

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


[Touch-packages] [Bug 1651500] Re: [ASUS X441SA] [8086:2284] No sound at all

2021-03-10 Thread Po-Hsu Lin
Hi W.R. Irsyad Hamda,

Looks like this is the fix:
https://github.com/torvalds/linux/commit/216d7aebbfbe1d3361e21c3a97d1607e1c1c48cd

It's been added to Bionic:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/tree/sound/pci/hda/patch_realtek.c#n7071

And Focal kernel.
https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/tree/sound/pci/hda/patch_realtek.c#n7887

As this bug is quite old,
do you still need the fix in 4.4 Xenial?
Thanks

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

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

Title:
  [ASUS X441SA] [8086:2284] No sound at all

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

Bug description:
  1. Release of ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2. version of the package
  AlsaMixer v1.1.0

  
  3. I expect to hear sound from speaker

  4. I can not any sound from speaker

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hamda  1627 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec 20 22:51:08 2016
  InstallationDate: Installed on 2016-12-15 (5 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:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hamda  1627 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X441SA.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X441SA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X441SA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1911030] Re: Graphical flashes on a raspi 4

2021-03-10 Thread Daniel van Vugt
I think the issue here is that you've discovered the software renderer
by choosing a dtoverlay value that wasn't supported.

So yes it's a bug, but not one we plan on devoting any time to.

** Summary changed:

- Graphical flashes on a raspi 4
+ Graphical flashes on a raspi 4 when software rendering is forced

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

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

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

Title:
  Graphical flashes on a raspi 4 when software rendering is forced

Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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