date:20220718

just a side node on the findings while hunting down this issue in gdb:

on armhf I think the calling convention is that integers are passed on
registers. uint64 is not a (32bit) integer and since the value passed to
SSL_CTX_set_options was not related in any way to the value passed in
q_SSL_CTX_set_options I think uint64_t are expected to be on the stack.
I cannot tell what value is in that place/where it came from, but it
ALWAYS had bit29 set. Bit29 means disable tls1.3.

I don't know if i686 has a similar calling convention, but if not and
i686 being a little endian architecture, that systems are not affected
by this (probably the most important platform being 32bit windows)

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

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

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+subscriptions


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

[Touch-packages] [Bug 1982057] [NEW] gdebi-gtk is not installing .deb package if "Open With Gdebi" is used on right-click

2022-07-18 Thread Nikola M

Public bug reported:

In Xfce on 22.04 Xubuntu, when trying to install .deb package with "Open
With Gdebi packge Installer" right-click option while in Thunar file
manager, Gdebi-gtk just silently dies, without installing package.

If gdebi-gtk is started from CLI, and then .deb file is opened via
File>Open , then .deb package is able to be installed.

Gdebi=gtk should be able to install package with open with method and
should not die.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdebi 0.9.5.7+nmu6
ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Tue Jul 19 07:08:58 2022
PackageArchitecture: all
SourcePackage: gdebi
UpgradeStatus: Upgraded to jammy on 2022-04-29 (80 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  gdebi-gtk is not installing .deb package if "Open With Gdebi" is used
  on right-click

Status in gdebi package in Ubuntu:
  New

Bug description:
  In Xfce on 22.04 Xubuntu, when trying to install .deb package with
  "Open With Gdebi packge Installer" right-click option while in Thunar
  file manager, Gdebi-gtk just silently dies, without installing
  package.

  If gdebi-gtk is started from CLI, and then .deb file is opened via
  File>Open , then .deb package is able to be installed.

  Gdebi=gtk should be able to install package with open with method and
  should not die.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdebi 0.9.5.7+nmu6
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Jul 19 07:08:58 2022
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (80 days ago)

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


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

[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)

2022-07-18 Thread Richard Charlewood

@Nick Rosbrook (enr0n): Your suggestion
(https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/comments/10)
doesn't work on Kubuntu 22.04 fresh install, fully patched, probably
because modprobe@mtdpstore.service doesn't appear in the file. I have
tried commenting out everything that isn't a descriptor but sadly I
still can't boot.

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

Title:
  mtd device must be supplied (device name is empty)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

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


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

[Touch-packages] [Bug 1974217] Re: ibus not detecting other languages other than default english

2022-07-18 Thread Launchpad Bug Tracker

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

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

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

Title:
  ibus not detecting other languages other than default english

Status in ibus package in Ubuntu:
  Expired

Bug description:
  ibus not detecting other languages. I cannot change languages with
  ibus applet

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus 1.5.26-4
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 19 22:19:05 2022
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2022-04-26 (23 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1981995] Re: incorrect system load format

2022-07-18 Thread jjjttwkr

/usr/bin/landscape-sysinfo

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

Title:
  incorrect system load format

Status in ubuntu-meta package in Ubuntu:
  Incomplete

Bug description:
  Welcome to Ubuntu 22.04 LTS (GNU/Linux 5.15.0-1014-azure x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

System information as of Mon Jul 18 13:43:37 UTC 2022

System load:  0.60205078125 Processes: 114
Usage of /:   4.0% of 61.84GB   Users logged in:   1
Memory usage: 64%   IPv4 address for eth0: 10.0.0.4
Swap usage:   0%

=> There is 1 zombie process.

  
  0 updates can be applied immediately.

  
  Last login: Mon Jul 18 13:43:12 2022 from *
  ubuntu@server1:~$ uptime
   13:43:41 up  1:36,  4 users,  load average: 0.63, 0.18, 0.07
  ubuntu@server1:~$

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


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

[Touch-packages] [Bug 1892825] Re: update-locale not perform correctly sanity checks

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: pam (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  update-locale not perform correctly sanity checks

Status in glibc package in Ubuntu:
  Fix Released
Status in pam package in Ubuntu:
  New
Status in glibc source package in Bionic:
  Fix Released
Status in pam source package in Bionic:
  New
Status in glibc source package in Focal:
  Fix Released
Status in pam source package in Focal:
  New
Status in glibc source package in Hirsute:
  Won't Fix
Status in pam source package in Hirsute:
  New
Status in glibc source package in Impish:
  Won't Fix
Status in pam source package in Impish:
  Won't Fix

Bug description:
  [impact]
  A simple typo using the update-locale script can render a system inoperable 
without booting into single user mode or similar:

  $ sudo update-locale LANGUAGE = en_US.UTF-8
  $ sudo -s
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  [test case]
  $ cp /etc/default/locale /tmp/locale
  $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8

  "diff -u /etc/default/locale /tmp/locale" should be empty.

  $ update-locale --locale-file /tmp/locale LANGUAGE=en_US.UTF-8

  The LANGUAGE=en_US.UTF-8 line should have been replaced by
  LANGUAGE=en_GB.UTF-8.

  $ update-locale --locale-file /tmp/locale LANGUAGE

  The LANGUAGE setting is now commented out.

  [regression potential]
  Apart from the general concerns about a glibc rebuild, this is a simple 
change to a simple script. Performing the test as in the test case section is 
enough to ensure it still works.

  [original description]
  By passing wrong input as following:
   sudo update-locale LANGUAGE = en_US.UTF-8
  result is:
  ...
  #LANGUAGE=en
  =

  This "equal" sign that was added makes system completely
  unusable(can't run sudo anymore):

  bentzy@bentzy-nb:~$ sudo vim /etc/default/locale
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  Fixed it booting from installation disk and fixing corrupted
  /etc/default/locale

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: locales 2.31-0ubuntu9
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Aug 25 09:36:03 2020
  InstallationDate: Installed on 2020-08-17 (7 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1892825] Re: update-locale not perform correctly sanity checks

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: glibc (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  update-locale not perform correctly sanity checks

Status in glibc package in Ubuntu:
  Fix Released
Status in pam package in Ubuntu:
  New
Status in glibc source package in Bionic:
  Fix Released
Status in pam source package in Bionic:
  New
Status in glibc source package in Focal:
  Fix Released
Status in pam source package in Focal:
  New
Status in glibc source package in Hirsute:
  Won't Fix
Status in pam source package in Hirsute:
  New
Status in glibc source package in Impish:
  Won't Fix
Status in pam source package in Impish:
  Won't Fix

Bug description:
  [impact]
  A simple typo using the update-locale script can render a system inoperable 
without booting into single user mode or similar:

  $ sudo update-locale LANGUAGE = en_US.UTF-8
  $ sudo -s
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  [test case]
  $ cp /etc/default/locale /tmp/locale
  $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8

  "diff -u /etc/default/locale /tmp/locale" should be empty.

  $ update-locale --locale-file /tmp/locale LANGUAGE=en_US.UTF-8

  The LANGUAGE=en_US.UTF-8 line should have been replaced by
  LANGUAGE=en_GB.UTF-8.

  $ update-locale --locale-file /tmp/locale LANGUAGE

  The LANGUAGE setting is now commented out.

  [regression potential]
  Apart from the general concerns about a glibc rebuild, this is a simple 
change to a simple script. Performing the test as in the test case section is 
enough to ensure it still works.

  [original description]
  By passing wrong input as following:
   sudo update-locale LANGUAGE = en_US.UTF-8
  result is:
  ...
  #LANGUAGE=en
  =

  This "equal" sign that was added makes system completely
  unusable(can't run sudo anymore):

  bentzy@bentzy-nb:~$ sudo vim /etc/default/locale
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  Fixed it booting from installation disk and fixing corrupted
  /etc/default/locale

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: locales 2.31-0ubuntu9
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Aug 25 09:36:03 2020
  InstallationDate: Installed on 2020-08-17 (7 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1922266] Re: eth0 interface name change fails on Pi 3/3+

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: ubuntu-settings (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  eth0 interface name change fails on Pi 3/3+

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Hirsute:
  Fix Released
Status in ubuntu-settings source package in Hirsute:
  Fix Released
Status in ubuntu-meta source package in Impish:
  Fix Released
Status in ubuntu-settings source package in Impish:
  Won't Fix
Status in ubuntu-meta source package in Jammy:
  Fix Released
Status in ubuntu-settings source package in Jammy:
  Fix Released

Bug description:
  The netplan configuration in ubuntu-raspi-settings (and more widely,
  the network-config in the gadget used on the server images) fails to
  rename the internal ethernet interface on Pi 3B and 3B+ models from
  "en" to "eth0". In the netplan case this is because the
  driver matching logic doesn't handle space-separate driver matches
  (although the underlying networkd system does); in the cloud-init case
  it simply refuses to rename interfaces that aren't matched by full MAC
  address.

  The intended fix is to stop attempting to do this via netplan or
  cloud-init, and simply handle this via a networkd .link file in
  ubuntu-raspi-settings. This will require an update to the relevant
  seeds as this package is currently only pulled into ubuntu-desktop-
  raspi, not ubuntu-server-raspi.

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


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

[Touch-packages] [Bug 1932329] Re: Support compressed kernel modules in initramfs-tools and kernel

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: initramfs-tools (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  Support compressed kernel modules in initramfs-tools and kernel

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Focal:
  New
Status in initramfs-tools source package in Impish:
  Won't Fix
Status in initramfs-tools source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  In Progress

Bug description:
  --- initramfs-tools

  [Impact]

   * Initramfs-tools already supports compressed kernel modules.
  However, in focal and impish it does so inefficiently. It is always
  better to have a compressed initramfs of uncommpressed kernel modules,
  than a compressed initrd of compressed kernel modules. Thus when
  kernel module compression is turned on, it is prudent for initramfs-
  tools to pre-uncompress kernel modules when building initramfs.

  [Test Plan]

   * Compress all kernel modules with xz for a current kernel, check
  that all of them have .ko.xz extension and no .ko ones available

   * Rerun depmod

   * Update initramfs with update-initramfs -u

   * lsinitramfs contents and check that all kernel modules are present,
  and are uncompressed (.ko extension)

  [Where problems could occur]

   * This optimization for compressed kernel modules will make initramfs
  build time longer (due to decompression) whilst improving bootspeed
  (overall smaller size of the initrd).

  [Other Info]

   * Original bug report re kernel feature

  --- linux

  Symbol: MODULE_COMPRESS_ZSTD [=n]
  Type  : bool

  = Impacts to measure and observe =

  == Disk space ==

  * Inspect linux-modules-* and linux-modules-extra* deb package
  Installed-Size and Download-Size changes, i.e.

  $ apt show linux-modules-5.8.0-53-generic linux-modules-
  extra-5.8.0-53-generic  | grep -e Package: -e Size:

  Package: linux-modules-5.8.0-53-generic
  Installed-Size: 81.5 MB
  Download-Size: 15.5 MB

  Package: linux-modules-extra-5.8.0-53-generic
  Installed-Size: 215 MB
  Download-Size: 41.5 MB

  In theory, there should not be a significant change in the Download-
  size. It is desired that there is a significant reduction in
  Installed-Size. Modules take up about 300MB and normally one has upto
  three kernel version installed, resulting in about of 1GB of disk
  space that one constantly pays for.

  == Boot Speed ==

  In theory, boot speed may either improve or regress. It depends if
  disk IO is slower than decompression speed, meaning loading compressed
  modules is faster.

  Also one has to observe the changes in the initrd size. zstd(zstd)
  compression may result in slight growth, which shouldn't impact boot
  speed too much.

  = Outcomes =

  If installed size savings can be achieved without regressing bootspeed
  we should enable CONFIG_MODULE_COMPRESS_ZSTD=y by default.

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


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

[Touch-packages] [Bug 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: initramfs-tools (Ubuntu Impish)
   Status: Confirmed => Won't Fix

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

Title:
  Missing all modules for usb nics in initrd which makes PXE boot
  impossible

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  Confirmed
Status in initramfs-tools source package in Hirsute:
  Confirmed
Status in initramfs-tools source package in Impish:
  Won't Fix
Status in initramfs-tools source package in Jammy:
  Fix Released

Bug description:
  initrd taken from the live iso for PXE boot does not contain USB NIC
  drivers which makes PXE installation/netboot impossible via usb.

  This is the case on 20.04 server iso (both hwe and normal
  kernel/initrd) and desktop iso.

  "kernel/drivers/net/usb" is empty and needs to be included in the
  initramfs build.

  As most modern thin laptops lack physical rj45 ethernet this is a big
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18
  Uname: Linux 5.8.0-64-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 15 16:47:45 2021
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to focal on 2020-05-11 (552 days ago)

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


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

[Touch-packages] [Bug 1954724] Re: Removing unattended-upgrades removes ubuntu-server-minimal

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: ubuntu-meta (Ubuntu Impish)
   Status: Confirmed => Won't Fix

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

Title:
  Removing unattended-upgrades removes ubuntu-server-minimal

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Impish:
  Won't Fix
Status in ubuntu-meta source package in Jammy:
  Fix Released

Bug description:
  On Impish and later, removing unattended-upgrades also removes ubuntu-
  server-minimal due to ubuntu-server-minimal depending on unattended-
  upgrades

  $ sudo apt remove unattended-upgrades
  ...
  The following packages will be REMOVED:
    ubuntu-server-minimal unattended-upgrades
  0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.

  This behaviour has changed since ubuntu-meta 1.471 [1] when the
  ubuntu-server-minimal metapackage was introduced, declaring
  unattended-upgrades as Depends.

  [1] https://launchpadlibrarian.net/550345392/ubuntu-
  meta_1.470_1.471.diff.gz

  On Focal, there was no such behaviour on a fresh ubuntu-server
  install:

  $ sudo apt remove unattended-upgrades
  ...
  The following packages will be REMOVED:
    unattended-upgrades
  0 upgraded, 0 newly installed, 1 to remove and 9 not upgraded.

  Removing unattended-upgrades is quite popular amongst our users, and
  they should be allowed to remove the package without removing the
  ubuntu-server-minimal metapackage.

  Looking at the source package for ubuntu-meta, unattended-upgrades is
  only Depends for ubuntu-server-minimal, maybe we should simply remove
  it, or instead, change to recommends?

  $ grep -Rin "unattended-upgrades" .
  ./server-minimal-armhf:23:unattended-upgrades
  ./server-minimal-riscv64:23:unattended-upgrades
  ./server-minimal-arm64:23:unattended-upgrades
  ./server-minimal-ppc64el:23:unattended-upgrades
  ./server-minimal-s390x:24:unattended-upgrades
  ./server-minimal-amd64:23:unattended-upgrades

  $ sudo apt rdepends unattended-upgrades
  unattended-upgrades
  Reverse Depends:
    Recommends: python3-software-properties
    Recommends: ubuntu-mate-desktop
    Recommends: ubuntu-mate-core
    Depends: freedombox
    Recommends: fbx-all
    Depends: ubuntu-server-minimal

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


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

[Touch-packages] [Bug 1959912] Re: libmount: multiple user options are not supported

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: util-linux (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  libmount: multiple user options are not supported

Status in Util-Linux-ng:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in util-linux source package in Bionic:
  New
Status in util-linux source package in Focal:
  New
Status in util-linux source package in Impish:
  Won't Fix
Status in util-linux source package in Jammy:
  New

Bug description:
  Only a single user option (the first one) is taken into consideration
  when mounting a new disk regardless of the filesystem.

  # mount /dev/sdd1 /mnt/cruizer -onodev,ro,x-gdu.hide,x-gvfs-hide
  # findmnt --mtab /mnt/cruizer
  TARGET   SOURCEFSTYPE OPTIONS
  /mnt/cruizer /dev/sdd1 fusebl ro,nodev,relatime,user_id=0,group_id=0,allow_oth
  # grep /mnt/cruizer /run/mount/utab
  SRC=/dev/sdd1 TARGET=/mnt/cruizer ROOT=/ OPTS=x-gdu.hide

  Reported issues: https://github.com/util-linux/util-linux/issues/1429 and 
https://github.com/util-linux/util-linux/issues/1583
  Confirmed fix with upstream commit: 
https://github.com/util-linux/util-linux/commit/d85f45d5ddb020b9858356b4c2c91d962ac7e6d7

To manage notifications about this bug go to:
https://bugs.launchpad.net/util-linux-ng/+bug/1959912/+subscriptions


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

[Touch-packages] [Bug 1881207] Re: systemd-networkd brings eno1 up and down repeatedly

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

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

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

Title:
  systemd-networkd brings eno1 up and down repeatedly

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  Won't Fix
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix

Bug description:
  [impact]

  a system using dhcp for an interface where (1) the interface 'resets'
  itself during mtu setting (meaning it briefly drops carrier during mtu
  change), and (2) the dhcp server provides a non-standard (i.e. other
  than 1500) mtu, will continually loop changing mtu between 1500 and
  the dhcp-privded mtu.

  [test case]

  The e1000e nic is one such nic where the driver briefly drops carrier
  when changing the mtu, so this can be reproduced by creating a VM and
  setting the interface to the 'e1000e' emulated hardware. Then
  configure a dhcp server to provide dhcp service to the VM, and set the
  mtu to e.g. 9000 (anything other than the default 1500).

  When the VM runs dhcp, it will loop with:

  Feb 22 15:18:58 lp1881207-upstream systemd-networkd[992]: ens8: Gained carrier
  Feb 22 15:18:58 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv4 
address 1.2.3.133/24 via 1.2.3.1
  Feb 22 15:18:59 lp1881207-upstream systemd-networkd[992]: ens8: Lost carrier
  Feb 22 15:18:59 lp1881207-upstream systemd-networkd[992]: ens8: DHCP lease 
lost
  Feb 22 15:18:59 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv6 lease 
lost
  Feb 22 15:19:01 lp1881207-upstream systemd-networkd[992]: ens8: Gained carrier
  Feb 22 15:19:01 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv4 
address 1.2.3.133/24 via 1.2.3.1
  Feb 22 15:19:02 lp1881207-upstream systemd-networkd[992]: ens8: Lost carrier
  Feb 22 15:19:02 lp1881207-upstream systemd-networkd[992]: ens8: DHCP lease 
lost
  Feb 22 15:19:02 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv6 lease 
lost
  Feb 22 15:19:04 lp1881207-upstream systemd-networkd[992]: ens8: Gained carrier
  Feb 22 15:19:04 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv4 
address 1.2.3.133/24 via 1.2.3.1
  Feb 22 15:19:05 lp1881207-upstream systemd-networkd[992]: ens8: Lost carrier
  Feb 22 15:19:05 lp1881207-upstream systemd-networkd[992]: ens8: DHCP lease 
lost
  Feb 22 15:19:05 lp1881207-upstream systemd-networkd[992]: ens8: DHCPv6 lease 
lost

  [regression potential]

  any regression would likely involve an issue with dhcpv4 service;
  possibly not setting the mtu correctly, or possibly not completing
  dhcpv4 at all.

  [scope]

  this is not fixed upstream yet, so (once fixed upstream) it will be
  needed for b/f/g/h

  [original description]

  Running on a NUC (BOXNUC8i7BEH3).

  After updating the `systemd` package past `237-3ubuntu10.32`, I see
  the onboard NIC link being taken down / up repeatedly, as shown below
  (dates are from my original notes, but the issue remains the same
  today).

  The NIC fails to remain up, and all networking is out of action.

  Running `systemctl stop systemd-netword` stops this and leaves the NIC in an 
unknown state.
  Subsequently running `ifconfig eno1 up && dhclient eno1` allows networking to 
continue basic operation, albeit without systemd's oversight.

  My original solution was to downgrade both the `libsystemd0` and
  `systemd` packages to `237-3ubuntu10.28`.

  After attempting an `apt update && apt upgrade` again today, exactly
  the same thing is happening with `237-3ubuntu10.41`.

  Good versions:
  - 237-3ubuntu10.28
  - 237-3ubuntu10.32 (currently in use, and held)

  Bad versions:
  - 237-3ubuntu10.33
  - 237-3ubuntu10.38
  - 237-3ubuntu10.41

  dmesg:

  [  360.711367] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  360.714370] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  360.726189] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  361.733073] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  361.744146] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  366.760198] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  366.763375] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  366.776060] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  367.781718] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  367.792796] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  372.808660] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow

[Touch-packages] [Bug 1928733] Re: Starting systemd Network Service fails with "Invalid argument"

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: systemd (Ubuntu Impish)
   Status: Triaged => Won't Fix

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

Title:
  Starting systemd Network Service fails with "Invalid argument"

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Triaged
Status in systemd source package in Focal:
  Triaged
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix

Bug description:
  This server has a new install of Ubuntu 18.04 server. Sometimes
  (around 50% of the time) when it boots systemd-networkd.service
  initially fails to start with an error as below. It then tries again
  and succeeds, however other services which depend on systemd-networkd
  have already failed on the dependency by then.

  From the output of "journalctl -u systemd-networkd":

  -- Reboot --
  May 17 19:44:28 server1 systemd[1]: Starting Network Service...
  May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed to 
set up mount namespacing: Invalid argument
  May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed at 
step NAMESPACE spawning /lib/systemd/systemd-networkd: Invalid argument
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Main process 
exited, code=exited, status=226/NAMESPACE
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Failed with 
result 'exit-code'.
  May 17 19:44:30 server1 systemd[1]: Failed to start Network Service.
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Service has no 
hold-off time, scheduling restart.
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Scheduled 
restart job, restart counter is at 1.
  May 17 19:44:30 server1 systemd[1]: Stopped Network Service.
  May 17 19:44:30 server1 systemd[1]: Starting Network Service...
  May 17 19:44:30 server1 systemd-networkd[2321]: Enumeration completed
  May 17 19:44:30 server1 systemd[1]: Started Network Service.
  May 17 19:44:30 server1 systemd-networkd[2321]: eno2: IPv6 successfully 
enabled
  May 17 19:44:30 server1 systemd-networkd[2321]: eno1: Link is not managed by 
us
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not 
managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not 
managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: eno1: IPv6 successfully 
enabled
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not 
managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not 
managed by us
  May 17 19:44:31 server1 systemd-networkd[2321]: eno2: Link UP
  May 17 19:44:31 server1 systemd-networkd[2321]: eno1: Link UP
  May 17 19:44:34 server1 systemd-networkd[2321]: eno2: Gained carrier
  May 17 19:44:34 server1 systemd-networkd[2321]: eno1: Gained carrier
  May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Gained IPv6LL
  May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Configured
  May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Gained IPv6LL
  May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Configured

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.46
  ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18
  Uname: Linux 4.15.0-142-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  Date: Mon May 17 19:53:11 2021
  InstallationDate: Installed on 2021-03-18 (60 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R440
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic 
root=/dev/mapper/vg1-lv_root ro processor.max_cstate=1 intel_idle.max_cstate=0 
transparent_hugepage=never
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.9.3
  dmi.board.name: 04JN2K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias:

[Touch-packages] [Bug 1939616] Re: u-r-u should leave a breadcrumb indicating a dist-upgrade is in progress

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: update-notifier (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  u-r-u should leave a breadcrumb indicating a dist-upgrade is in
  progress

Status in apport package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in apport source package in Impish:
  New
Status in ubuntu-release-upgrader source package in Impish:
  New
Status in update-notifier source package in Impish:
  Won't Fix

Bug description:
  Looking at the source code of ubuntu-release-upgrader it looks like an
  environment variable, RELEASE_UPGRADE_IN_PROGRESS, is set when an
  upgrade is being performed. However, it would be better if there was
  an indication that other programs, e.g. apport, could use to tell
  whether or not a release upgrade was in progress.

  This came up as we saw some crash reports in the error tracker that
  didn't make sense and a possible explanation is that a release upgrade
  was in progress.

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


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

[Touch-packages] [Bug 1940715] Re: systemd-resolved restricts edns0 advertised max size to 512

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: systemd (Ubuntu Impish)
   Status: Confirmed => Won't Fix

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

Title:
  systemd-resolved restricts edns0 advertised max size to 512

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix

Bug description:
  [impact]

  when talking to upstream nameservers, systemd-resolved limits its
  advertised max packet size as 512 in its edns0 opt. However, one of
  the primary benefits of edns0 is to allow using packet sizes larger
  than 512, which is the pre-edns0 max packet size.

  this results in systemd-resolved failing to handle responses larger
  than 512 with udp/edns0, and having to fall back to tcp. This is not
  optimal (since tcp dns imposes significantly higher overhead) and may
  even cause failures, if a firewall allows udp dns but blocks tcp dns
  traffic.

  [test case]

  enable debug logging in systemd-resolved, with 'sudo systemctl edit
  systemd-resolved' and then add:

  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  then save that file and restart systemd-resolved (or reboot).

  Make sure to flush the cache and reset server features before
  reproducing:

  $ sudo resolvectl flush-caches
  $ sudo resolvectl reset-server-features

  Lookup 'toomany.ddstreet.org' and check systemd-resolved logs to see
  if it used TCP fallback or not:

  ...
  Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Reply truncated, retrying 
via TCP.
  ...
  Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Verified we get a 
response at feature level TCP from DNS server 10.202.51.1.
  Aug 24 12:17:48 lp1940715-f systemd-resolved[1199]: Added positive 
unauthenticated cache entry for toomany.ddstreet.org IN A 1799s on 
eth0/INET/10.202.51.1

  A correct lookup using larger EDNS0 response size looks like:

  ...
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Using feature level 
UDP+EDNS0 for transaction 43808.
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Using DNS server 
10.202.51.1 for transaction 43808.
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Announcing packet size 
1472 in egress EDNS(0) packet.
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Emitting UDP, link MTU is 
1500, socket MTU is 0, minimal MTU is 40
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Sending query packet with 
id 43808 of size 49.
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Processing query...
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Received dns UDP packet of 
size 689, ifindex=131, ttl=0, fragsize=0
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Processing incoming packet 
of size 689 on transaction 43808 (rcode=SUCCESS).
  Aug 24 12:28:13 lp1940715-f systemd-resolved[174]: Added positive 
unauthenticated non-confidential cache entry for toomany.ddstreet.org IN A 
1175s on eth0/INET/10.202.51.1
  ...

  [regression potential]

  failure to correctly look up dns records, or other problems while
  performing dns lookups with systemd-resolved

  [scope]

  this is needed in impish and earlier

  this is fixed in jammy at commit
  22545a74c3a24395bc6e894fe6a681deb66d434c

  this is fixed upstream by commit
  526fce97afe130f71dba3bd4646196bbb1188b82 which in included in v250, so
  this is fixed in kinetic and later

  the upstream PR is:
  https://github.com/systemd/systemd/pull/20528

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


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

[Touch-packages] [Bug 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: iptables (Ubuntu Impish)
   Status: Fix Committed => Won't Fix

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

Title:
  iptables-save -c shows incorrect counters with iptables-nft

Status in iptables package in Ubuntu:
  Fix Released
Status in iptables source package in Impish:
  Won't Fix
Status in iptables source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
  is always failing. Initially I thought it was a kernel issue, but
  debugging further I found that the reason is that with Impish we're
  using iptables-nft by default instead of iptables-legacy.

  This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
  source directory) is creating a bunch of network namespaces and
  checking the iptables counters for the defined policies, in particular
  this is the interesting part:

  check_ipt_policy_count()
  {
  ns=$1

  ip netns exec $ns iptables-save -c |grep policy | ( read c rest
  ip netns exec $ns iptables -Z
  if [ x"$c" = x'[0:0]' ]; then
  exit 0
  elif [ x"$c" = x ]; then
  echo "ERROR: No counters"
  ret=1
  exit 111
  else
  exit 1
  fi
  )
  }

  If I use iptables-nft the counters are never [0:0] as they should be,
  so the test is failing. With iptables-legacy they are [0:0] and the
  test is passing.

  [Test case]

  tools/testing/selftests/net/xfrm_policy.sh from the Linux kernel
  source code.

  [Fix]

  Apply iptables upstream commit:

  5f1fcace ("iptables-nft: fix -Z option")

  In this way also with iptables-nft the counters are reported
  correctly.

  [Regression potential]

  We may require other upstream commits now that the -Z option is
  working properly with iptables-nft.

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


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

[Touch-packages] [Bug 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: ubuntu-settings (Ubuntu Impish)
   Status: Confirmed => Won't Fix

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

Title:
  raspi 64 bit Impish image fails update-initramfs with OOM on zstd

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Impish:
  Won't Fix
Status in ubuntu-settings source package in Jammy:
  Fix Released

Bug description:
  When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit
  Impish image and nothing new installed to it, update-initramfs fails
  like so:

  Setting up linux-firmware (1.201.1) ...
  update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi
  Killed
   E: mkinitramfs failure 
zstd -q -19 -T0 137

  A simple workaround for now is to switch to the old lz4 default:

  $ sudo apt install lz4
  $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' 
/etc/initramfs-tools/initramfs.conf

  Original Workaround
  ===

  Adding a swap file to the setup allowed 'apt -f install' to run
  successfully.

  How the device was setup
  1) xzcat | dd the sdcard with the impish 64 bit server image
  2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, 
link getty@ttyGS0.service
  ) as suggested in 
https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console
  3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest 
of the 16GB flash, e2fsck, resize2fs
  4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per 
https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html
  5) boot, connect to wireless, ssh in
  6) apt update && apt upgrade
  7) observe above issue

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: linux-firmware 1.201.1
  ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14
  Uname: Linux 5.13.0-1009-raspi aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  8 19:47 seq
   crw-rw 1 root audio 116, 33 Nov  8 19:47 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.13.0-1009-raspi.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Mon Nov  8 21:00:59 2021
  Dependencies:

  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  ImageMediaBuild: 20211013
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lspci-vt: -[:00]-
  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
  PackageArchitecture: all
  PciMultimedia:

  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 
vc_mem.mem_size=0x2000  dwc_otg.lpm_enable=0 console=ttyS0,115200 
console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait 
fixrtc quiet splash modules-load=dwc2,g_serial
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux-firmware
  StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 
bcm2835_codec vc_sm_cma
  Title: package linux-firmware 1.201.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

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


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

[Touch-packages] [Bug 1950508] Re: unified cgroup incorrectly used in container on host with legacy/hybrid cgroup

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: systemd (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  unified cgroup incorrectly used in container on host with
  legacy/hybrid cgroup

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

Bug description:
  [impact]

  after systemd was changed to default to cgroupv2, any container
  started on a host that still uses legacy or hybrid cgroup mounts will
  result in a container that attempts to use unified cgroup but can't
  due to all the controllers being used as v1 in the host kernel.

  [test case]

  TBD

  [regression potential]

  container, or vm or bare metal, that incorrectly uses cgroupv1, or
  incorrect use of cgroupv2.

  [scope]

  needed only for i and later

  f and earlier default to cgroupv1

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


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

[Touch-packages] [Bug 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: systemd (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with
  linux/5.13.0-37.42

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New
Status in linux source package in Impish:
  Incomplete
Status in systemd source package in Impish:
  Won't Fix
Status in linux source package in Jammy:
  Incomplete
Status in systemd source package in Jammy:
  New

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-37.42 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz

  The "tests-in-lxd" testcase is failing with all kernels in Impish:

  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service snap-lxd-22662.mount 
---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
lxd, revision 22662...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for lxd, revision 22662.
   journal for failed service snap-snapd-15177.mount ---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
snapd, revision 15177...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for snapd, revision 15177.
  FAIL
  [...]
  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", 
line 69, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['snap-lxd-22662.mount   loaded failed fai[119 
chars]177'] != []

  First list contains 2 additional elements.
  First extra element 0:
  'snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision 
22662'

  + []
  - ['snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision '
  -  '22662',
  -  'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, 
revision '
  -  '15177']

  
  This testcase started to fail with the latest re-spin of the kernels 
(uploaded on mar-16), however the only patch applied between the previous 
kernels and the current ones is a CVE fix which is unlikely to be causing this 
failure:

  "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()"
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b

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


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

[Touch-packages] [Bug 1979244] Re: libssl-dev : Depends: libssl3 (= 3.0.2-0ubuntu1.1) but 3.0.2-0ubuntu1.2 is to be installed

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apt (Ubuntu Impish)
   Status: Fix Committed => Won't Fix

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

Title:
  libssl-dev : Depends: libssl3 (= 3.0.2-0ubuntu1.1) but
  3.0.2-0ubuntu1.2 is to be installed

Status in MySQL InnoDB Cluster Charm:
  Invalid
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Impish:
  Won't Fix
Status in apt source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Users cannot install a package, e.g. libssl-dev, if built from the same 
source as another installed update while it is phasing.

  In the example below, libssl3 3.0.2-0ubuntu1.2 update was already
  installed, this got replaced in the archive with a 3.0.2-0ubuntu1.4
  update that was phasing and the system in question was not eligible
  for it yet.

  Because the system was not eligible for openssl 3.0.2-0ubuntu1.4, it
  picked libssl-dev=3.0.2-0ubuntu1.1 from the security pocket as the
  candidate instead, which conflicts with the higher version of libssl3.

  [Approach]
  We reimplemented the phasing as part of the upgrade code path by keeping back 
any phased upgrades, as the original update-manager implementation does, and 
disabled the policy based implementation (set APT::Phase-Policy to true to 
re-enable it).

  This means that phasing only applies when upgrades are made by apt,
  and not when initiated manually by the user or as a result from a
  dependency.

  So if you have a phased upgrade 'phased', apt upgrade won't upgrade
  it, but `apt upgrade 'phased'`, like àpt install 'phased'` will -
  which is the expected behavior as the arguments should behave like
  they do in `install`.

  Packages will now appear as having "been kept back" in the upgrade
  output.

  [Test case]
  Integration tests will be provided and run as autopkgtests, testing the 
scenarios described in this issue and comment #10. This cannot necessarily be 
tested on the real archive as you need packages phasing and have an older 
version installed.

  Please see test/integration/test-phased-updates-upgrade for the
  complete tests. tl;dr is that we test each of the upgrade commands,
  with and without package arguments, and the install command with
  arguments; for a variety of scenarios:

  – simple phased update
  - a phased update that has a version in security
  - a package that gains a dependency on an installed phased package
  - a package that gains a dependency on a NEW phased package

  We test both the new implementation and the old one.

  [Regression potential]
  The solver could break trying to unwrap our mess of MarkKeep() calls where 
they conflict with other calls. I don't think it can necessarily break harder 
than now and issues can be worked around archive side if problems do pop up. 
Also people can manually work around by passing package names of phased 
upgrades to force them.

  Packages will now be installed from the -updates pocket if they have a
  newer-than-installed version in the -security pocket, rather than the
  security pocket, as we cannot switch the version. This is the same
  behavior as update-manager.

  [Example]

  libmysqlclient-dev on Jammy cannot be installed due to unmet
  dependencies

  $ apt policy libmysqlclient-dev
  libmysqlclient-dev:
    Installed: (none)
    Candidate: 8.0.29-0ubuntu0.22.04.2
    Version table:
   8.0.29-0ubuntu0.22.04.2 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   8.0.28-0ubuntu4 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages
  $ sudo 'apt-get' '--option=Dpkg::Options::=--force-confold' '--assume-yes' 
'install' 'libmysqlclient-dev'
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libssl-dev : Depends: libssl3 (= 3.0.2-0ubuntu1.1) but 3.0.2-0ubuntu1.2 is 
to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-mysql-innodb-cluster/+bug/1979244/+subscriptions


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

[Touch-packages] [Bug 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

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

this however has priority low.
additionally openssl1.1 and openssl3 are not compatible in this case if libssl 
is loaded in runtime

for 32bit this is only solvable if compiletime forces openssl version to
3 OR 1.1, but then the corresponding version MUST be loaded or someone
implements a version check in runtime. Using the q_SSL_CTX_set_options
funcion will not work in this case since the symbol is not unique

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

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

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+subscriptions


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

[Touch-packages] [Bug 1972029] Re: dhclient overriding stub-resolv.conf file on Jammy

2022-07-18 Thread Pedro Principeza

Hi, Lukas.

Thank you very much for the reply, here.  I tested the isc-dhcp-client
in the mentioned PPA on a Kinetic uvt-kvm-based VM, and with it in
place, I no longer see the stub-resolv.conf being overwritten whenever I
run `sudo dhclient`.  Indeed, I now see a `resolved-enter` enter-hook
script disabling the make_resolv_conf() execution when sd-resolved is
in.

It works! Thanks again!

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

Title:
  dhclient overriding stub-resolv.conf file on Jammy

Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in isc-dhcp source package in Jammy:
  New
Status in isc-dhcp source package in Kinetic:
  Confirmed

Bug description:
  [Issue]
  On Jammy, the stub-resolv.conf file on /run/systemd/resolve gets overwritten 
if dhclient is executed.

  While debugging this, I found the reference on LP#1889068 [0] of the
  move of `resolved` hook from dhclient-enter-hooks.d/ to dhclient-exit-
  hooks.d/, and this new hook [2] has no reference of make_resolv_conf()
  being called.

  [Reproducer]
  -
  I used a cloud-image based Jammy installation (uvt-kvm).  Once in:

  $ cat /run/system/resolve/stub-resolv.conf

  And one will see:

  nameserver 127.0.0.53
  options edns0 trust-ad
  search .

  Then:

  $ sudo dhclient
  $ cat /run/system/resolve/stub-resolv.conf

  You'll see the definition of the nameserver(s) in, and the stub IP
  address no longer there.  To revert this, a `systemctl restart
  systemd-resolved` is needed.

  [Impact]

  This is an improper way to keep nameserver(s) in *resolv* files; the
  override of the file should never happen in these circumstances.

  [Extra]
  -
  As a minor test, I copied over the dhclient-enter-hooks.d/resolved file from 
a Focal installation to a Jammy one, and the problem _does not happen_ when 
such hook is in place.

  [ . . . ]

  Let me know if further clarification is needed to proceed.  Thank you.

  BR,
  pprincipeza

  [0] https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1889068
  [1] https://paste.ubuntu.com/p/bvqPZXZZ8w/
  [2] https://paste.ubuntu.com/p/YQdG6z4WS7/

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


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

[Touch-packages] [Bug 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

2022-07-18 Thread Dmitry Shachnev

Thank you for the patch!

Qt 6 still uses unsigned long:
https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/tls/openssl/qsslsocket_openssl_symbols.cpp#n126

Can you please submit your patch to codereview.qt-project.org, or at
least file a bug at bugreports.qt.io?

We usually don't add patches that were not merged upstream.

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

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

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+subscriptions


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

[Touch-packages] [Bug 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

actually the first patch was missing something and did not compile

** Patch added: "openssl3_set_options.diff"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+attachment/5603782/+files/openssl3_set_options.diff

** Patch removed: "openssl3_set_options.patch"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+attachment/5603721/+files/openssl3_set_options.patch

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

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

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+subscriptions


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

[Touch-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

2022-07-18 Thread Ubuntu Foundations Team Bug Bot

The attachment "debdiff_nettle_3.7.3-1build2_to_3.8-0ubuntu1.diff" seems
to be a debdiff.  The ubuntu-sponsors team has been subscribed to the
bug report so that they can review and hopefully sponsor the debdiff.
If the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in nettle package in Ubuntu:
  In Progress

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

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


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

[Touch-packages] [Bug 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

2022-07-18 Thread Ubuntu Foundations Team Bug Bot

The attachment "openssl3_set_options.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

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

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+subscriptions


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

[Touch-packages] [Bug 1963767] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1963767/+attachment/5603779/+files/UdevDb.txt

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1963767/+attachment/5603780/+files/WifiSyslog.txt

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1963767/+attachment/5603781/+files/acpidump.txt

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1963767/+attachment/5603778/+files/RfKill.txt

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] PulseList.txt

apport information

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

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1963767/+attachment/5603776/+files/ProcModules.txt

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1963767/+attachment/5603772/+files/Lsusb-v.txt

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1963767/+attachment/5603775/+files/ProcInterrupts.txt

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

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

apport information

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

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] PaInfo.txt

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1963767/+attachment/5603773/+files/PaInfo.txt

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1963767/+attachment/5603771/+files/Lspci-vt.txt

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1963767/+attachment/5603770/+files/Lspci.txt

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1963767/+attachment/5603769/+files/IwConfig.txt

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] Dependencies.txt

apport information

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

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

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

apport information

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

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1963767/+attachment/5603766/+files/CRDA.txt

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1963767] Re: Microphone not working after suspend

apport information

** Tags added: wayland-session

** Description changed:

  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.
  
  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's microphone
  stops working (device is still there, but audio level is at zero all the
  time).
  
  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`
  
  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-02-15 (153 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Lsusb-t:
+  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
+  |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
+  |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
+ MachineType: Purism Librem 13 v4
+ Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=uk_UA.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-39-generic N/A
+  linux-backports-modules-5.15.0-39-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.2
+ Tags:  jammy wayland-session wayland-session
+ Uname: Linux 5.15.0-39-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/27/2022
+ dmi.bios.release: 4.15
+ dmi.bios.vendor: coreboot
+ dmi.bios.version: 4.15-Purism-3
+ dmi.board.name: Librem 13 v4
+ dmi.board.vendor: Purism
+ dmi.board.version: 1.0
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Purism
+ dmi.ec.firmware.release: 0.0
+ dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
+ dmi.product.family: Librem 13
+ dmi.product.name: Librem 13 v4
+ dmi.product.version: 1.0
+ dmi.sys.vendor: Purism

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

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

Title:
  Microphone not working after suspend

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

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2

[Touch-packages] [Bug 1930482] Re: netplan crash on ubuntu 20.04 disabling network

2022-07-18 Thread Lukas Märdian

** Tags added: rls-ff-incoming

** Changed in: netplan
   Status: New => Invalid

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

Title:
  netplan crash on ubuntu 20.04 disabling network

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

Bug description:
  On ubuntu 20.04 with netplan 0.102-0ubuntu1~20.04.2, the server loss
  both IPv4 and IPv6 address in a while with DHCP config. The are no way
  to restore network, only by rebooting the server.

  Trying to restart the server networking using "systemctl restart
  systemd-networkd" or "netplan apply" fails.

  Note: systemctl and netplay apply fails also with a netplan with
  static IP address

  The server runs on OVS in cloud.ramnode.com

  I'm pasting config, logs, netplan and restart output (IP and mac
  address are masked)

  I don't see a workaound yet, only to restart server to change the
  network configuration.

  File: 50-cloud-init.yaml
  ==
  # This file is generated from information provided by the datasource.  Changes
  # to it will not persist across an instance reboot.  To disable cloud-init's
  # network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  accept-ra: true
  dhcp4: true
  dhcp6: true
  match:
  macaddress: **:**:**:**:**:**:**
  mtu: 1500
  set-name: ens3
  =

  Syslog
  =
  2021-06-01T19:31:01.063935-04:00 server systemd[1]: Stopped Network Service.
  2021-06-01T19:31:01.066766-04:00 server systemd[1]: Starting Network 
Service...
  2021-06-01T19:31:01.161797-04:00 server systemd-networkd[2302]: 
/run/systemd/network/10-netplan-ens3.network: MTUBytes= in [Link] section and 
UseMTU= in [DHCP] section are set. Disabling UseMTU=.
  2021-06-01T19:31:01.161990-04:00 server systemd-networkd[2302]: loop3456: 
netdev ready
  2021-06-01T19:31:01.162073-04:00 server systemd-networkd[2302]: Tunnel127: 
Gained IPv6LL
  2021-06-01T19:31:01.162184-04:00 server systemd-networkd[2302]: Tunnel126: 
Gained IPv6LL
  2021-06-01T19:31:01.162275-04:00 server systemd-networkd[2302]: loop3456: 
Gained IPv6LL
  2021-06-01T19:31:01.162349-04:00 server systemd-networkd[2302]: ens3: Gained 
IPv6LL
  2021-06-01T19:31:01.164685-04:00 server systemd-networkd[2302]: Assertion 
'ifindex' failed at src/network/networkd-link.c:757, function link_get(). 
Aborting.
  2021-06-01T19:31:01.553611-04:00 server systemd[1]: systemd-networkd.service: 
Main process exited, code=dumped, status=6/ABRT
  2021-06-01T19:31:01.553796-04:00 server systemd[1]: systemd-networkd.service: 
Failed with result 'core-dump'.
  2021-06-01T19:31:01.553892-04:00 server systemd[1]: Failed to start Network 
Service.
  2021-06-01T19:31:01.553983-04:00 server systemd[1]: systemd-networkd.service: 
Scheduled restart job, restart counter is at 2.
  

  output of: netapply --debug try
  
  DEBUG:ens3 not found in {}
  DEBUG:loop3456 not found in {}
  DEBUG:Merged config:
  network:
bridges:
  loop3456:
accept-ra: false
addresses:
- 10.65.0.3/32
dhcp4: false
dhcp6: false
interfaces: []
ethernets:
  ens3:
accept-ra: true
addresses:
- XXX.XXX.XXX.XXX/24
dhcp4: false
dhcp6: true
gateway4: XXX.XXX.XXX.XXX
match:
  macaddress: **:**:**:**:**:**:**
mtu: 1500
nameservers:
  addresses:
  - 8.8.8.8
  - 8.8.4.4
  search:
  - uc.edu.ve
set-name: ens3
version: 2

  DEBUG:New interfaces: set()
  ** (generate:1484): DEBUG: 20:14:22.895: Processing input file 
/etc/netplan/50-static.yaml..
  ** (generate:1484): DEBUG: 20:14:22.895: starting new processing pass
  ** (generate:1484): DEBUG: 20:14:22.895: Processing input file 
/etc/netplan/99-local.yaml..
  ** (generate:1484): DEBUG: 20:14:22.895: starting new processing pass
  ** (generate:1484): DEBUG: 20:14:22.895: We have some netdefs, pass them 
through a final round of validation
  ** (generate:1484): DEBUG: 20:14:22.895: ens3: setting default backend to 1
  ** (generate:1484): DEBUG: 20:14:22.895: Configuration is valid
  ** (generate:1484): DEBUG: 20:14:22.895: loop3456: setting default backend to 
1
  ** (generate:1484): DEBUG: 20:14:22.895: Configuration is valid
  ** (generate:1484): DEBUG: 20:14:22.896: Generating output files..
  ** (generate:1484): DEBUG: 20:14:22.896: openvswitch: definition ens3 is not 
for us (backend 1)
  **

[Touch-packages] [Bug 1930482] Re: netplan crash on ubuntu 20.04 disabling network

2022-07-18 Thread Lukas Märdian

This hits an assert() in systemd-networkd so I'm assigning it to the
src:systemd package.

=> Assertion 'ifindex' failed at src/network/networkd-link.c:757,
function link_get(). Aborting.

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

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

Title:
  netplan crash on ubuntu 20.04 disabling network

Status in netplan:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  On ubuntu 20.04 with netplan 0.102-0ubuntu1~20.04.2, the server loss
  both IPv4 and IPv6 address in a while with DHCP config. The are no way
  to restore network, only by rebooting the server.

  Trying to restart the server networking using "systemctl restart
  systemd-networkd" or "netplan apply" fails.

  Note: systemctl and netplay apply fails also with a netplan with
  static IP address

  The server runs on OVS in cloud.ramnode.com

  I'm pasting config, logs, netplan and restart output (IP and mac
  address are masked)

  I don't see a workaound yet, only to restart server to change the
  network configuration.

  File: 50-cloud-init.yaml
  ==
  # This file is generated from information provided by the datasource.  Changes
  # to it will not persist across an instance reboot.  To disable cloud-init's
  # network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  accept-ra: true
  dhcp4: true
  dhcp6: true
  match:
  macaddress: **:**:**:**:**:**:**
  mtu: 1500
  set-name: ens3
  =

  Syslog
  =
  2021-06-01T19:31:01.063935-04:00 server systemd[1]: Stopped Network Service.
  2021-06-01T19:31:01.066766-04:00 server systemd[1]: Starting Network 
Service...
  2021-06-01T19:31:01.161797-04:00 server systemd-networkd[2302]: 
/run/systemd/network/10-netplan-ens3.network: MTUBytes= in [Link] section and 
UseMTU= in [DHCP] section are set. Disabling UseMTU=.
  2021-06-01T19:31:01.161990-04:00 server systemd-networkd[2302]: loop3456: 
netdev ready
  2021-06-01T19:31:01.162073-04:00 server systemd-networkd[2302]: Tunnel127: 
Gained IPv6LL
  2021-06-01T19:31:01.162184-04:00 server systemd-networkd[2302]: Tunnel126: 
Gained IPv6LL
  2021-06-01T19:31:01.162275-04:00 server systemd-networkd[2302]: loop3456: 
Gained IPv6LL
  2021-06-01T19:31:01.162349-04:00 server systemd-networkd[2302]: ens3: Gained 
IPv6LL
  2021-06-01T19:31:01.164685-04:00 server systemd-networkd[2302]: Assertion 
'ifindex' failed at src/network/networkd-link.c:757, function link_get(). 
Aborting.
  2021-06-01T19:31:01.553611-04:00 server systemd[1]: systemd-networkd.service: 
Main process exited, code=dumped, status=6/ABRT
  2021-06-01T19:31:01.553796-04:00 server systemd[1]: systemd-networkd.service: 
Failed with result 'core-dump'.
  2021-06-01T19:31:01.553892-04:00 server systemd[1]: Failed to start Network 
Service.
  2021-06-01T19:31:01.553983-04:00 server systemd[1]: systemd-networkd.service: 
Scheduled restart job, restart counter is at 2.
  

  output of: netapply --debug try
  
  DEBUG:ens3 not found in {}
  DEBUG:loop3456 not found in {}
  DEBUG:Merged config:
  network:
bridges:
  loop3456:
accept-ra: false
addresses:
- 10.65.0.3/32
dhcp4: false
dhcp6: false
interfaces: []
ethernets:
  ens3:
accept-ra: true
addresses:
- XXX.XXX.XXX.XXX/24
dhcp4: false
dhcp6: true
gateway4: XXX.XXX.XXX.XXX
match:
  macaddress: **:**:**:**:**:**:**
mtu: 1500
nameservers:
  addresses:
  - 8.8.8.8
  - 8.8.4.4
  search:
  - uc.edu.ve
set-name: ens3
version: 2

  DEBUG:New interfaces: set()
  ** (generate:1484): DEBUG: 20:14:22.895: Processing input file 
/etc/netplan/50-static.yaml..
  ** (generate:1484): DEBUG: 20:14:22.895: starting new processing pass
  ** (generate:1484): DEBUG: 20:14:22.895: Processing input file 
/etc/netplan/99-local.yaml..
  ** (generate:1484): DEBUG: 20:14:22.895: starting new processing pass
  ** (generate:1484): DEBUG: 20:14:22.895: We have some netdefs, pass them 
through a final round of validation
  ** (generate:1484): DEBUG: 20:14:22.895: ens3: setting default backend to 1
  ** (generate:1484): DEBUG: 20:14:22.895: Configuration is valid
  ** (generate:1484): DEBUG: 20:14:22.895: loop3456: setting default backend to 
1
  ** (generate:1484): DEBUG: 20:14:22.895: Configuration is valid

[Touch-packages] [Bug 1980805] Re: Backport packages for 20.04.5 HWE stack

2022-07-18 Thread kisak

Hi, please note that there will be minor lost functionality from mesa-
amber not being on the per-release i386 package whitelist.

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

Title:
  Backport packages for 20.04.5 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-13 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in mesa-amber package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-13 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  New
Status in mesa-amber source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: pci-id updates, some minor api updates

  mesa: a new major release, but we'll pull the final stable release of
  22.0.x series, so there shouldn't be any regressions left at that
  point

  mesa-amber: forked from mesa 21.3.x, this LTS branch keeps old DRI
  drivers that were removed from main mesa

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


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

[Touch-packages] [Bug 1965518] Re: [USB-Audio - USB Audio, recording] Recording problem

2022-07-18 Thread Sergey

Have the same problem with gigabyte b560 aorus pro

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

Title:
  [USB-Audio - USB Audio, recording] Recording problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Microphone when using built in mbo MSI Z690 Edge WiFi DDR4 audio
  Realtek ALC4080 is not recording audio. What I did found out, that the
  bar which indicates that something is recording is going up, when I
  play some sound on ubuntu, so input "thinks" it is output I think.

  If raport is somehow saying I was not using that mic at the moment,
  that is because I was using other card which I need to buy, for mic to
  temporarly work. I rechecked it before sending report, and yes, that
  original from MBO audio input is still not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity
  Date: Fri Mar 18 10:39:26 2022
  InstallationDate: Installed on 2022-03-12 (5 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed
  Symptom_Card: USB Audio - USB Audio
  Symptom_Type: None of the above
  Title: [USB-Audio - USB Audio, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z690 EDGE WIFI DDR4 (MS-7D31)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.10:bd12/13/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D31:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ690EDGEWIFIDDR4(MS-7D31):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D31
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Touch-packages] [Bug 1981995] Re: incorrect system load format

2022-07-18 Thread Aaron Rainbolt

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thank you!

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Incomplete

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

Title:
  incorrect system load format

Status in ubuntu-meta package in Ubuntu:
  Incomplete

Bug description:
  Welcome to Ubuntu 22.04 LTS (GNU/Linux 5.15.0-1014-azure x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

System information as of Mon Jul 18 13:43:37 UTC 2022

System load:  0.60205078125 Processes: 114
Usage of /:   4.0% of 61.84GB   Users logged in:   1
Memory usage: 64%   IPv4 address for eth0: 10.0.0.4
Swap usage:   0%

=> There is 1 zombie process.

  
  0 updates can be applied immediately.

  
  Last login: Mon Jul 18 13:43:12 2022 from *
  ubuntu@server1:~$ uptime
   13:43:41 up  1:36,  4 users,  load average: 0.63, 0.18, 0.07
  ubuntu@server1:~$

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


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

[Touch-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

2022-07-18 Thread Frank Heimes

Here is the debdiff for this version bump (from
3.7.3-1build2_to_3.8-0ubuntu1).

** Patch added: "debdiff_nettle_3.7.3-1build2_to_3.8-0ubuntu1.diff"
   
https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1959469/+attachment/5603732/+files/debdiff_nettle_3.7.3-1build2_to_3.8-0ubuntu1.diff

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

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

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

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in nettle package in Ubuntu:
  In Progress

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

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


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

[Touch-packages] [Bug 1972029] Re: dhclient overriding stub-resolv.conf file on Jammy

2022-07-18 Thread Lukas Märdian

I can reproduce this, did some investigation on it and I agree that this
behavior of overriding /etc/resolv.conf -> /run/systemd/resolve/stub-
resolv.conf (managed by sd-resolved) is very bad.

The sd-resolved hook was moved from
https://launchpad.net/ubuntu/+source/systemd/246-2ubuntu1 to
https://launchpad.net/ubuntu/+source/isc-dhcp/4.4.1-2.1ubuntu7 in
Groovy.

It was moved from an enter-hook to an exit-hook, too. And it looks like
the part overriding/disabling "make_resolv_conf()" got dropped and went
missing.

IIUC we could place a tiny enter-hook to disable "make_resolv_conf()" if
systemd-resolved is being used, to avoid it from overriding
/etc/resolv.conf -> /run/systemd/resolv/stub-resolv.conf, managed by sd-
resolved. Everything else seems to be working as expected.

Would you mind testing my isc-dhcp-client package from this PPA?
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4635/+packages

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

Title:
  dhclient overriding stub-resolv.conf file on Jammy

Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in isc-dhcp source package in Jammy:
  New
Status in isc-dhcp source package in Kinetic:
  Confirmed

Bug description:
  [Issue]
  On Jammy, the stub-resolv.conf file on /run/systemd/resolve gets overwritten 
if dhclient is executed.

  While debugging this, I found the reference on LP#1889068 [0] of the
  move of `resolved` hook from dhclient-enter-hooks.d/ to dhclient-exit-
  hooks.d/, and this new hook [2] has no reference of make_resolv_conf()
  being called.

  [Reproducer]
  -
  I used a cloud-image based Jammy installation (uvt-kvm).  Once in:

  $ cat /run/system/resolve/stub-resolv.conf

  And one will see:

  nameserver 127.0.0.53
  options edns0 trust-ad
  search .

  Then:

  $ sudo dhclient
  $ cat /run/system/resolve/stub-resolv.conf

  You'll see the definition of the nameserver(s) in, and the stub IP
  address no longer there.  To revert this, a `systemctl restart
  systemd-resolved` is needed.

  [Impact]

  This is an improper way to keep nameserver(s) in *resolv* files; the
  override of the file should never happen in these circumstances.

  [Extra]
  -
  As a minor test, I copied over the dhclient-enter-hooks.d/resolved file from 
a Focal installation to a Jammy one, and the problem _does not happen_ when 
such hook is in place.

  [ . . . ]

  Let me know if further clarification is needed to proceed.  Thank you.

  BR,
  pprincipeza

  [0] https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1889068
  [1] https://paste.ubuntu.com/p/bvqPZXZZ8w/
  [2] https://paste.ubuntu.com/p/YQdG6z4WS7/

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


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

[Touch-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

2022-07-18 Thread Frank Heimes

Since the symbol files are a bit tricky in this case (because the incl.
arch-specific entries), I'm uploading them here separately, too.

** Attachment added: "updated_symbols.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1959469/+attachment/5603726/+files/updated_symbols.tgz

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

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  New
Status in nettle package in Ubuntu:
  New

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

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


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

[Touch-packages] [Bug 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

this should fix the issue

this however requires openssl3.0, but that should be ok for ubuntu going
forward

** Patch added: "openssl3_set_options.patch"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+attachment/5603721/+files/openssl3_set_options.patch

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

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

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+subscriptions


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

[Touch-packages] [Bug 1981995] [NEW] incorrect system load format

2022-07-18 Thread jjjttwkr

Public bug reported:

Welcome to Ubuntu 22.04 LTS (GNU/Linux 5.15.0-1014-azure x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

  System information as of Mon Jul 18 13:43:37 UTC 2022

  System load:  0.60205078125 Processes: 114
  Usage of /:   4.0% of 61.84GB   Users logged in:   1
  Memory usage: 64%   IPv4 address for eth0: 10.0.0.4
  Swap usage:   0%

  => There is 1 zombie process.


0 updates can be applied immediately.


Last login: Mon Jul 18 13:43:12 2022 from *
ubuntu@server1:~$ uptime
 13:43:41 up  1:36,  4 users,  load average: 0.63, 0.18, 0.07
ubuntu@server1:~$

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: ubuntu => ubuntu-meta (Ubuntu)

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

Title:
  incorrect system load format

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Welcome to Ubuntu 22.04 LTS (GNU/Linux 5.15.0-1014-azure x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

System information as of Mon Jul 18 13:43:37 UTC 2022

System load:  0.60205078125 Processes: 114
Usage of /:   4.0% of 61.84GB   Users logged in:   1
Memory usage: 64%   IPv4 address for eth0: 10.0.0.4
Swap usage:   0%

=> There is 1 zombie process.

  
  0 updates can be applied immediately.

  
  Last login: Mon Jul 18 13:43:12 2022 from *
  ubuntu@server1:~$ uptime
   13:43:41 up  1:36,  4 users,  load average: 0.63, 0.18, 0.07
  ubuntu@server1:~$

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


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

[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)

2022-07-18 Thread Metalliko

Same “issue” here, system boots as expected and seem to work just fine, but 
might taque a second or two more time to boot since y notice the error, but not 
sure.
I have ‘vanilla’ 22.04 with 5.15.0-41-generic kernel.
Worth mention that besides the M2 nvme ssd from wich I boot and / is, I also 
have 2 wd hdd's in linux raid 0 so there is a /dev/md device.

$ ls /dev/md*
/dev/md0  /dev/md0p1
/dev/md:
0  0p1

Relevan mount output lines:

$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=14299692k,nr_inodes=3574923,mode=755,inode64)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=2866956k,mode=755,inode64)
/dev/nvme0n1p2 on / type ext4 (rw,relatime,errors=remount-ro,stripe=32)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=17979)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl 
(rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
none on /run/credentials/systemd-sysusers.service type ramfs 
(ro,nosuid,nodev,noexec,relatime,mode=700)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=2866952k,nr_inodes=716738,mode=700,uid=1000,gid=1000,inode64)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
portal on /run/user/1000/doc type fuse.portal 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
tmpfs on /run/snapd/ns type tmpfs 
(rw,nosuid,nodev,noexec,relatime,size=2866956k,mode=755,inode64)
/dev/nvme0n1p1 on /boot/efi type vfat 
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/md0p1 on /mnt/cipher type ext4 (rw,nosuid,nodev,relatime,stripe=256)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=2866952k,nr_inodes=716738,mode=700,uid=1000,gid=1000,inode64)

The error mesage:

$ sudo dmesg | grep mtd
[3.248501] systemd[1]: Starting Load Kernel Module mtdpstore...
[3.258680] mtd device must be supplied (device name is empty)

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

Title:
  mtd device must be supplied (device name is empty)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

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


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

[Touch-packages] [Bug 1981995] [NEW] incorrect system load format

2022-07-18 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Welcome to Ubuntu 22.04 LTS (GNU/Linux 5.15.0-1014-azure x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

  System information as of Mon Jul 18 13:43:37 UTC 2022

  System load:  0.60205078125 Processes: 114
  Usage of /:   4.0% of 61.84GB   Users logged in:   1
  Memory usage: 64%   IPv4 address for eth0: 10.0.0.4
  Swap usage:   0%

  => There is 1 zombie process.


0 updates can be applied immediately.


Last login: Mon Jul 18 13:43:12 2022 from *
ubuntu@server1:~$ uptime
 13:43:41 up  1:36,  4 users,  load average: 0.63, 0.18, 0.07
ubuntu@server1:~$

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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

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

[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)

2022-07-18 Thread Coeur Noir

Same message here on « regular » Ubuntu 22.04 installed in legacy mode
on an UEFI capable bios.

No nvme/M2 here - system on SSD + data on HDD.

See attached file for dmesg it's line 941 at [6.780126]

Wonder if « failed » messages regarding sdb later at lines 980 and
following [ 35.056956] are anyhow related ?

** Attachment added: "dmesg.txt"

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+attachment/5603717/+files/dmesg.txt

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

Title:
mtd device must be supplied (device name is empty)

Status in systemd package in Ubuntu:
Confirmed

Bug description:
After updating my 22.04 system (possibly caused by Systemd update).
And now booting, dmesg has two errors:

'mtd device must be supplied (device name is empty)'.

See line 8 and 134 in the included logfile.

The system are booting as it should though, and the system are working
like it should no errors at all.

Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
systemd?

I have an EFI mounted at boot but it isn't used because I have
installed my system in legacy BIOS mode.

Is this maybe the culprit?

I could ignore the message but it isn't nice though.

Regards

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

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

[Touch-packages] [Bug 1981807] Re: qt5-network openssl3 armhf does not support tls1.3

i think I have a trace where the issue is:
openssl3 openssl's options is a uint64_t, but in qsslsocket_openssl.cpp the 
method is  defined as 
long QSslSocketBackendPrivate::setupOpenSslOptions(QSsl::SslProtocol protocol, 
QSsl::SslOptions sslOptions)

long on 64bit platforms is 64 bit long, but on armhf (32bit) it is
32bit.

see
https://www.openssl.org/docs/man3.0/man3/SSL_CTX_set_options.html
vs
https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_set_options.html

is this already fixed in qt6? the qt5.15 openssl3 is a ubuntu backport,
right?

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

Title:
  qt5-network openssl3 armhf does not support tls1.3

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

Bug description:
  lsb_release
  Description:Ubuntu 22.04 LTS
  Release:22.04

  libqt5network5/jammy,now 5.15.3+dfsg-2 armhf
  libssl3/jammy-updates,jammy-security,now 3.0.2-0ubuntu1.6 armhf

  the qt5 armhf version shipped with ubuntu jammy has a regression in
  tls1.3 support (simply missing in runtime).

  openssl supports tls1.3, so the underlying library works.
  x86_64 is obviously not affected
  the short sample applications writes -1 on armhf, 15 on x86_64 (unknown 
protocol vs tls1.3)

  QSslSocket* s = new QSslSocket();
  QSslConfiguration cfg = s->sslConfiguration();
  cfg.setProtocol(QSsl::TlsV1_3OrLater);
  s->setSslConfiguration(cfg);
  s->connectToHostEncrypted("tls13-enabled.server",443);
  s->waitForConnected();
  printf("%d\n",s->sessionProtocol());

  marking it as security since the most secure tls protocol is not used
  on some platforms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1981807/+subscriptions


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

[Touch-packages] [Bug 1981983] [NEW] systemd-network changes MAC of interfaces belonging to a bond

2022-07-18 Thread Alex

Public bug reported:

1)
Description:Ubuntu 20.04.4 LTS
Release:20.04

2)
systemd:
Installed: 245.4-4ubuntu3.15

3) What you expected to happen
Interfaces in the bond keep their real "hardware" mac addresses. bond0 takes 
MAC from first interface of the bond when not explicitly set.

4) What happened instead
I wanted to change from ifupdown back to netplan/systemd-networkd. Thus I 
installed netplan.io, delete /etc/network/interfaces, purged ifupdown and wrote 
an yaml for netplan.

My Yaml looks as following

network:
  version: 2
  renderer: networkd
  ethernets:
   em1:
 dhcp4: false
 dhcp6: false
 optional: true
   em3:
 dhcp4: false
 dhcp6: false
 optional: true
  bonds:
  bond-new:
  interfaces: [em1, em3]
  dhcp4: true 
  dhcp6: false
  accept-ra: true
  link-local: [ ipv6 ]
  parameters:
  mode: 802.3ad
  mii-monitor-interval: 1

Netplan applies it without errors. Also, this represents the (working)
configuration I had with ifupdown.

Now when I apply this config, bond0 gets the following (random?) MAC address: 
c2:ba:f9:db:xx:xx (xx for privacy)
Also, both interfaces em1 and em3 belonging to that bond get the same MAC 
address. This actual "hardware" MAC address is obviously another. Strangely, 
all interfaces get the same MAC address:

# ip a | grep c2:ba:f9:db:ed:4b -B 1
2: em1:  mtu 1500 qdisc mq master 
bond-new state UP group default qlen 1000
link/ether c2:ba:f9:db:xx:xx brd ff:ff:ff:ff:ff:ff
4: em3:  mtu 1500 qdisc mq master 
bond-new state UP group default qlen 1000
link/ether c2:ba:f9:db:xx:xx brd ff:ff:ff:ff:ff:ff
--
8: bond-new:  mtu 1500 qdisc noqueue 
state UP group default qlen 1000
link/ether c2:ba:f9:db:xx:xx brd ff:ff:ff:ff:ff:ff

Additionally every device added to this bond will get the same MAC
address, e. g. em2:

3: em2:  mtu 1500 qdisc mq master 
bond-new state DOWN group default qlen 1000
link/ether c2:ba:f9:db:xx:xx brd ff:ff:ff:ff:ff:ff 

I already set MACAddressPolicy=none in
/lib/systemd/network/99-default.link, but it does no change this
behavior.

Removing an interface from the bond, does not revert the MAC. When I
purge netplan.io and install ifupdown, the real MAC address is set to
interfaces again.

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

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

Title:
  systemd-network changes MAC of interfaces belonging to a bond

Status in systemd package in Ubuntu:
  New

Bug description:
  1)
  Description:Ubuntu 20.04.4 LTS
  Release:20.04

  2)
  systemd:
  Installed: 245.4-4ubuntu3.15

  3) What you expected to happen
  Interfaces in the bond keep their real "hardware" mac addresses. bond0 takes 
MAC from first interface of the bond when not explicitly set.

  4) What happened instead
  I wanted to change from ifupdown back to netplan/systemd-networkd. Thus I 
installed netplan.io, delete /etc/network/interfaces, purged ifupdown and wrote 
an yaml for netplan.

  My Yaml looks as following

  network:
version: 2
renderer: networkd
ethernets:
 em1:
   dhcp4: false
   dhcp6: false
   optional: true
 em3:
   dhcp4: false
   dhcp6: false
   optional: true
bonds:
bond-new:
interfaces: [em1, em3]
dhcp4: true 
dhcp6: false
accept-ra: true
link-local: [ ipv6 ]
parameters:
mode: 802.3ad
mii-monitor-interval: 1

  Netplan applies it without errors. Also, this represents the (working)
  configuration I had with ifupdown.

  Now when I apply this config, bond0 gets the following (random?) MAC address: 
c2:ba:f9:db:xx:xx (xx for privacy)
  Also, both interfaces em1 and em3 belonging to that bond get the same MAC 
address. This actual "hardware" MAC address is obviously another. Strangely, 
all interfaces get the same MAC address:

  # ip a | grep c2:ba:f9:db:ed:4b -B 1
  2: em1:  mtu 1500 qdisc mq master 
bond-new state UP group default qlen 1000
  link/ether c2:ba:f9:db:xx:xx brd ff:ff:ff:ff:ff:ff
  4: em3:  mtu 1500 qdisc mq master 
bond-new state UP group default qlen 1000
  link/ether c2:ba:f9:db:xx:xx brd ff:ff:ff:ff:ff:ff
  --
  8: bond-new:  mtu 1500 qdisc noqueue 
state UP group default qlen 1000
  link/ether c2:ba:f9:db:xx:xx brd ff:ff:ff:ff:ff:ff

  Additionally every device added to this bond will get the same MAC
  address, e. g. em2:

  3: em2:  mtu 1500 qdisc mq master 
bond-new state DOWN group default qlen 1000
  link/ether c2:ba:f9:db:xx:xx brd ff:ff:ff:ff:ff:ff 

  I already set MACAddressPolicy=none in
  /lib/systemd/network/99-default.link, but it does no change this
  behavior.

  Removing an interface from the bond, does not revert the MAC. When I

[Touch-packages] [Bug 1972977] Re: gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query()

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #6885
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/6885

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/6885
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-shell crashed with SIGSEGV in crocus_begin_query() from
  crocus_begin_query() from crocus_end_query() from crocus_end_query()
  from tc_call_end_query()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Touch-packages] [Bug 1742269] Re: Keyboard focus not visible on popover menu entries

Thank you for reporting this bug to Ubuntu.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: ubuntu-themes
   Status: Confirmed => Won't Fix

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Keyboard focus not visible on popover menu entries

Status in Ubuntu theme:
  Won't Fix
Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  Open a popover menu with text entries, such as:

  - Files (Nautilus): "hamburger" menu on the upper right

  - Tilix: "hamburger" menu, or right-click over the terminal area, or
  Profiles -> a triangle in the left-hand sidebar

  Use the keyboard (Tab, or Up and Down) to navigate in the entries.

  When an icon entry (wherever present) is focused, it has a thin orange
  border. But when simple text (or checkbox, radiobutton) entries are
  focused, there is no visual feedback at all, you can't see which item
  is selected and hence which item would be activated by Enter or Space.

  This makes popovers pretty unusable via the keyboard.

  Does not happen with Adwaita.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171115-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Jan  9 20:54:27 2018
  InstallationDate: Installed on 2016-11-09 (425 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-09-21 (109 days ago)

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


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

[Touch-packages] [Bug 1726555] Re: Use mainstream theme solution for gnome-terminal, drop patch

Thank you for reporting this bug to Ubuntu.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: ubuntu-themes
   Status: New => Won't Fix

** Changed in: gnome-terminal (Ubuntu)
   Status: New => Won't Fix

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Use mainstream theme solution for gnome-terminal, drop patch

Status in Ubuntu theme:
  Won't Fix
Status in gnome-terminal package in Ubuntu:
  Won't Fix
Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  Ubuntu adds a patch called "0001-Add-style-classes-and-CSS-names-to-
  some-of-our-widge.patch" to gnome-terminal, and in turn Ambiance and
  Radiance themes' apps/gnome-terminal.css relies on this to get the
  desired look for the notebook widget.

  Beginning with gnome-terminal 3.20.3 / 3.22.1 this should no longer be
  necessary. It's just an additional burden to carry this patch, plus an
  unnecessary complication for those who wish to manually compile gnome-
  terminal for whatever reason.

  gnome-terminal.css should ideally be modified to use the CSS names
  provided by mainstream gnome-terminal, and once done, the gnome-
  terminal patch can be dropped.

  Upstream references:
  https://bugzilla.gnome.org/show_bug.cgi?id=765590
  https://bugzilla.gnome.org/show_bug.cgi?id=772134#c6
  https://bugzilla.gnome.org/show_bug.cgi?id=788044

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


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

[Touch-packages] [Bug 1685273] Re: Gedit/Text Editor tabs hard to distinguish under Ambiance

Thank you for reporting this bug to Ubuntu.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.


** Changed in: ubuntu-themes (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: ubuntu-themes (Ubuntu Artful)
   Status: Triaged => Won't Fix

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

Title:
  Gedit/Text Editor tabs hard to distinguish under Ambiance

Status in ubuntu-themes package in Ubuntu:
  Won't Fix
Status in ubuntu-themes source package in Artful:
  Won't Fix

Bug description:
  Under gnome-shell, it's difficult to distinguish which tab is focused.
  See the attached screenshot.

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


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

[Touch-packages] [Bug 1291939] Re: window borders are now missing meaning overlapping windows of the same type have no separation, and no separation from the background

** Tags removed: artful trusty

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

Title:
  window borders are now missing meaning overlapping windows of the same
  type have no separation, and no separation from the background

Status in Ubuntu theme:
  Confirmed
Status in Ubuntu UX:
  New
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  In the latest update all window borders have gone leading to windows
  with the same backgound having no visual separation, also with a dark
  background you can no longer tell where they end.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140312-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Thu Mar 13 11:26:33 2014
  EcryptfsInUse: Yes
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (54 days ago)

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


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

[Touch-packages] [Bug 1693158] Re: Decorations get weird when windows complete an operation

Thank you for reporting this bug to Ubuntu.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Decorations get weird when windows complete an operation

Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  While updating packages I can see this happening for a second when the
  operation finishes. The decorations (font and icons in particular)
  become weird, like if something was broken. See the screenshot to
  better understand what I mean.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170518-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed May 24 11:38:32 2017
  InstallationDate: Installed on 2017-04-28 (25 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170426)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1698050] Re: Disabled arrow buttons in Nautilus header bar are too dark

Thank you for reporting this bug to Ubuntu.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.


** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Disabled arrow buttons in Nautilus header bar are too dark

Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  Disabled arrow buttons in Nautilus header bar are too dark, under
  Gnome Shell.

  They don't look disabled as much as they look like a rendering bug, or
  look like depressed buttons.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170518-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 11:41:54 2017
  InstallationDate: Installed on 2017-05-03 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1557981] Re: Selected-Tab Hard to Distinguish in Default Ambiance Theme

** Tags removed: artful

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

Title:
  Selected-Tab Hard to Distinguish in Default Ambiance Theme

Status in Ubuntu theme:
  Confirmed
Status in Unity:
  Invalid
Status in gnome-system-monitor package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  The default Theme in Ubuntu 16.04 is called "Ambiance":
  http://neartalk.com/ss/2016-03-16_005_565x390.png

  When Gnome-System-Monitor is running under the Ambiance theme, you can barely 
distinguish which tab is selected:
  http://neartalk.com/ss/2016-03-16_003_679x497.png

  Compare this with the non-default theme called "Radiance", where the 
selected-tab (in Gnome-System-Monitor) is clearly distinguishable at a glance 
(without eye strain):
  http://neartalk.com/ss/2016-03-16_004_687x497.png

  Which package would be responsible for making the selected-tab more
  distinguishable to the eye in gnome-system-monitor under the default
  Ambiance theme?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-system-monitor 3.18.2-1
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 16 04:38:11 2016
  InstallationDate: Installed on 2016-03-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1508535] Re: Outdated Google icon in Settings > Online Accounts

** Tags removed: artful

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

Title:
  Outdated Google icon in Settings > Online Accounts

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  The Google account icon in the Accounts page uses the old white-
  lowercase-g-on-blue backing.  They updated their logo a while ago to
  use a rainbow-uppercase-G.

  We should update too.

  (I'm sure this isn't the right component, just wasn't sure where to
  put it.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1508535/+subscriptions


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

[Touch-packages] [Bug 1628474] Re: keyboard keys in GtkShortcuts should have different color than background

Thank you for reporting this bug to Ubuntu.

Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  keyboard keys in GtkShortcuts should have different color than
  background

Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  Many GNOME apps have a new Keyboard Shortcuts popup window available
  in their app menu (this feature was introduced in GTK 3.20).

  Ambiance and Radiance don't style this window correctly - there's no
  contrast between the displayed keyboard keys and the background.

  I'm attaching screenshots of evince's Keyboard Shortcuts popup
  (available in Help > Keyboard Shortcuts) with Ambiance and Adwaita.

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


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

[Touch-packages] [Bug 1693152] Re: Some icons in the decorations look overlapping

Thank you for reporting this bug to Ubuntu.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Some icons in the decorations look overlapping

Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  It seems that some icons are overlapping in the top left corner

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170518-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed May 24 11:26:05 2017
  InstallationDate: Installed on 2017-04-28 (25 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170426)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1705129] Re: Highlighted items have a white text but keep a black arrow

Thank you for reporting this bug to Ubuntu.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: ubuntu-ux
   Status: New => Invalid

** No longer affects: ubuntu-ux

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

Title:
  Highlighted items have a white text but keep a black arrow

Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  In some menus, like the one in the picture, the highlighted items have
  a white text but a black arrow. In this specific screenshot I'm
  referring to the Tool text with the black arrow on the side. I think
  it would be more consistent and visually pleasant if they could have
  the same color.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170703-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 22:56:28 2017
  InstallationDate: Installed on 2015-03-21 (850 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

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


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

[Touch-packages] [Bug 1721693] Re: Settings list separators conflict visually with list item backgrounds

Thank you for reporting this bug to Ubuntu.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: ubuntu-themes
   Status: New => Won't Fix

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Settings list separators conflict visually with list item backgrounds

Status in Ubuntu theme:
  Won't Fix
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  Settings list separators conflict visually with list item backgrounds.

  The separators should be more visually significant than the things
  they are separating, however the Ubuntu theme is using alternating
  light/dark backgrounds which drown out the separators.

  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Fri Oct  6 13:38:00 2017
  InstallationDate: Installed on 2017-05-03 (156 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1760190] Re: Useless icon themes installed

** Tags removed: artful

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

Title:
  Useless icon themes installed

Status in humanity-icon-theme package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Humanity-Dark
  LoginIcons
  Ubuntu-mono-dark
  Ubuntu-mono-light
  Hicolor

  if i switch icons from these icons nothing happening.
  I think these icons are no longer used in ubuntu.

  And DMZ-Black, DMZ-White listing in icons

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1760190/+subscriptions


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

[Touch-packages] [Bug 1720510] Re: Content sometime not display until a focus/geometry change

Thank you for reporting this bug to Ubuntu.

Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.


** Changed in: ubuntu-themes (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: gnome-software (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  Content sometime not display until a focus/geometry change

Status in GNOME Software:
  Expired
Status in gnome-software package in Ubuntu:
  Won't Fix
Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  # Test case 1:

  1. Open a new version of gnome-software/Ubuntu Software
  2. Search for soft
  3. No results are shown
  4. Do something outside the gnome-software window, e.g mouse click or focus 
on another window, and the results are shown.

  # Test case 2 (reliably reproduces issue every time):

  1. Open gnome software
  2. Install or uninstall rocketchat
  3. Close gnome software
  4. Open gnome software
  5. Search for libreoffice
  - No search results are being displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 30 09:28:37 2017
  InstallationDate: Installed on 2017-09-15 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1720510/+subscriptions


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

[Touch-packages] [Bug 1843880] Re: GtkSpinButton's context menu changes the width of '+'

Thank you for reporting this bug to Ubuntu.

Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Won't Fix

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

Title:
  GtkSpinButton's context menu changes the width of '+'

Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  GtkSpinButton consists of a (typically numeric) input field, followed
  by a '-' and finally a '+' sign. The width of the '+' sign shrinks a
  little bit when you open the right-click context menu of the input
  field. It shouldn't, it should have a constant width.

  Happens with Ubuntu's old default Ambiance and Radiance themes. Does
  not happen with Ubuntu's new default Yaru, or with GTK's default
  Adwaita.

  Example: Open gnome-terminal, right click on its terminal canvas,
  choose Preferences. You're taken to the profile's Text tab which
  contains four such widgets. Right-click on one of these input fields,
  e.g. on "80" for the initial number of columns. In addition to the
  context menu appearing, the '+' button becomes narrower, and thus the
  label on its right (e.g. "columns") shifts to the left. For some of
  the spinbuttons (the ones that stretch the window) the entire window
  also shrinks. Dismiss the context menu and it goes back to its
  previous width.

  (This is similar to former bug 1740709.)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: light-themes 19.04-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Sep 13 11:48:51 2019
  InstallationDate: Installed on 2016-11-09 (1037 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to eoan on 2019-09-08 (4 days ago)

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


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

[Touch-packages] [Bug 1981849] Re: After reboot, the screen was blank/black and unresponsive

Please try these separately:

 * Add kernel parameter: intel_iommu=igfx_off

 * Use the 'Additional Drivers' app to install an official Nvidia
driver.

** Summary changed:

- Xorg freeze
+ After reboot, the screen was blank/black and unresponsive

** Tags added: nouveau

** Package changed: xorg (Ubuntu) => linux-hwe-5.15 (Ubuntu)

** Summary changed:

- After reboot, the screen was blank/black and unresponsive
+ [nouveau] After reboot, the screen was blank/black and unresponsive using 
5.15.0-41.44~20.04.1 (but 5.13 works)

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

Title:
  [nouveau] After reboot, the screen was blank/black and unresponsive
  using 5.15.0-41.44~20.04.1 (but 5.13 works)

Status in linux-hwe-5.15 package in Ubuntu:
  New

Bug description:
  Although I filed this against X11, this might be a kernel issue.

  I upgraded packages on 7/13/22 & rebooted today (7/15/22 -- I hadn't
  noted the "reboot required pop-up).

  After reboot, the screen was blank/black and unresponsive.  Looking at
  indicator lights, I believe that the system had booted OK.  The syslog
  supports this.

  Included in the update: 
  xserver-xorg-core:amd64 2:1.20.13-1ubuntu1~20.04.3
  linux-libc-dev:amd64 5.4.0-122.138
  linux-image-5.15.0-41-generic:amd64  5.15.0-41.44~20.04.1

  Repeated attempts to boot all ended the same -- blank unresponsive
  screen.

  I could boot in recovery mode and with the 5.13 kernel (which I'm
  running now and was used for the bug report).

  > lsb_release -a
  LSB Version:  core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  Code> uname -a
  Linux turk 5.13.0-52-generic #59~20.04.1-Ubuntu SMP Thu Jun 16 21:21:28 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux
  name: focal

  Again, note that the problem occurred when booting to the 5.15 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 15 13:51:44 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Today
  GraphicsCard:
   NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Dell GM107GLM [Quadro M2000M] [1028:16d9]
  InstallationDate: Installed on 2021-10-28 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Precision 7510
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-52-generic 
root=UUID=b611bb21-5970-4191-bf68-230392700099 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2021
  dmi.bios.release: 1.25
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.25.3
  dmi.board.name: 0M91XC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 0010333
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.25.3:bd12/18/2021:br1.25:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0M91XC:rvrA00:cvnDellInc.:ct9:cvr:sku06D9:
  dmi.product.family: Precision
  dmi.product.name: Precision 7510
  dmi.product.sku: 06D9
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Fri Jul 15 10:40:20 2022
  xserver.configfile: default
  xserver.errors:
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or

[Touch-packages] [Bug 1970449] Re: GPG keys are not shown in Software and Updates

2022-07-18 Thread Heiko Hösch

Here is a working version of the AptAuth.py for Ubuntu 22.04.

The testing version of Ubuntu might have another software-properties-
version.

I just changed the subprocess.run to subprocess.Popen and added a p.close to 
end the subprocess
where it reads the keys. I left the rest as it is. I did not want to change 
more than necessary.

Other methods of this class use subprocess.run, there you don't need to end the 
subprocess, I would
say. The subprocess.run ends the subprocess automatically, I would say, but the 
subprocess.Popen
seemingly needs a manual closing of the subprocess.

** Attachment added: "AptAuth.py"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+attachment/5603680/+files/AptAuth.py

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

Title:
  GPG keys are not shown in Software and Updates

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  software-properties-gtk does not show the registered apt gpg keys in
  the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU