[Touch-packages] [Bug 1946235] Re: pcscd won't install due to bad dependency version

[Lars Noodén]

Ok. This was probably a bug in the update-manager that only manifested
symptoms in my case in pcscd.

I noticed the only place 'hirsute' was mentioned was in /etc/apt/ is one
file, /etc/apt/sources.list.d/system.sources there.  Once I changed all
instances of 'hirsute' to 'impish' in
/etc/apt/sources.list.d/system.sources it was possible to get pcscd
installed as normal.

So I guess this is either solved or should be relabeled as applying to
'update-manager'

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

Title:
  pcscd won't install due to bad dependency version

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  # apt install pcscd
  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:
   pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed
   qemu-block-extra : Depends: qemu-system-x86 (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-arm (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-mips (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-ppc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-sparc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-misc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-s390x (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-x86-xen (= 1:6.0+dfsg-2expubuntu1) 
but it is not going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pcscd (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Oct  6 17:15:29 2021
  InstallationDate: Installed on 2020-06-16 (477 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to impish on 2021-10-06 (0 days ago)

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


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

[Touch-packages] [Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd

[Jean-Baptiste Lallement]

There is also an additional requirement. The package must install
successfully and replace an existing file that would have been created
manually (we had to ship the file on the image for the customer since we
don't have this fix in a package yet)

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

Title:
  NTP servers from DHCP are not propagated to timesyncd

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  Network manager gets NTP servers from DHCP but do not update timesyncd to use 
it which keeps using ntp.ubuntu.com.
   
  This is a problem on private networks which do not have access to public 
internet. On this type of network the configuration of timesyncd must be 
updated manually instead of inheriting the conf from the dhcp servers.

  This can be integrated with a NM dispatcher script such as below:

  etc/NetworkManager/dispatcher.d/10-update-timesyncd for example:

  ==8<=8<=8<=8<=8<==
  #! /usr/bin/bash

  [ -n "$CONNECTION_UUID" ] || exit

  INTERFACE=$1
  ACTION=$2

  case $ACTION in
  up | dhcp4-change | dhcp6-change)
  [ -n "$DHCP4_NTP_SERVERS" ] || exit
  mkdir -p /etc/systemd/timesyncd.conf.d/
  cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  [Time]
  NTP=$DHCP4_NTP_SERVERS
  RootDistanceMaxSec=15
  EOF
  systemctl restart systemd-timesyncd
 ;;
  down)
  rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  systemctl restart systemd-timesyncd
  ;;
  esac
  ==8<=8<=8<=8<=8<==

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 28 14:08:52 2021
  InstallationDate: Installed on 2020-05-31 (393 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  RebootRequiredPkgs:
   linux-image-5.11.0-20-generic
   linux-base
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions


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

[Touch-packages] [Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd

[Jean-Baptiste Lallement]

IMHO having the fix in network-dispatcher makes more sense.

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

Title:
  NTP servers from DHCP are not propagated to timesyncd

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  Network manager gets NTP servers from DHCP but do not update timesyncd to use 
it which keeps using ntp.ubuntu.com.
   
  This is a problem on private networks which do not have access to public 
internet. On this type of network the configuration of timesyncd must be 
updated manually instead of inheriting the conf from the dhcp servers.

  This can be integrated with a NM dispatcher script such as below:

  etc/NetworkManager/dispatcher.d/10-update-timesyncd for example:

  ==8<=8<=8<=8<=8<==
  #! /usr/bin/bash

  [ -n "$CONNECTION_UUID" ] || exit

  INTERFACE=$1
  ACTION=$2

  case $ACTION in
  up | dhcp4-change | dhcp6-change)
  [ -n "$DHCP4_NTP_SERVERS" ] || exit
  mkdir -p /etc/systemd/timesyncd.conf.d/
  cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  [Time]
  NTP=$DHCP4_NTP_SERVERS
  RootDistanceMaxSec=15
  EOF
  systemctl restart systemd-timesyncd
 ;;
  down)
  rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  systemctl restart systemd-timesyncd
  ;;
  esac
  ==8<=8<=8<=8<=8<==

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 28 14:08:52 2021
  InstallationDate: Installed on 2020-05-31 (393 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  RebootRequiredPkgs:
   linux-image-5.11.0-20-generic
   linux-base
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions


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

[Touch-packages] [Bug 1946192] Re: "Press Ctrl+C to cancel all filesystem checks in process" on every boot

[Steve Langasek]

The message comes from systemd-fsckd.  Though I'm not sure why it would
be considered a bug that the message shows up briefly on the screen; we
always call systemd-fsckd, even if it quickly determines there's no work
to do and exits.

** Package changed: plymouth (Ubuntu) => systemd (Ubuntu)

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

Title:
  "Press Ctrl+C to cancel all filesystem checks in process" on every
  boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I installed Kubuntu 20.04 on Latitude 5591 laptop using flash drive.
  Installation run without any issues but now on every boot I notice a
  message "Press Ctrl+C to cancel all filesystem checks in process" on
  the Plymouth screen with Kubuntu logo. It flashes quickly and
  disappears. I've got fast NVMe drive so I cannot say for sure whether
  it runs any checks or not.

  I booted from LiveCD and performed fsck checks of all my partitions:
  fsck.vfat /dev/nvme0n1p1 (EFI partition)
  fsck.vfat /dev/nvme0n1p2 (Dell service partition, not mounted)
  e2fsck -f /dev/nvme0n1p3 (Root partition)
  e2fsck -f /dev/nvme0n1p5 (Home partition)
  These checks showed no problems.

  I changed mount counter to set periodic checks:
  sudo tune2fs -c 29 /dev/nvme0n1p3
  sudo tune2fs -c 30 /dev/nvme0n1p5
  But despite these settings this message still appears on every boot.

  Operating System: Kubuntu 20.04.3
  Kernel Version: 5.4.0-88-generic
  OS Type: 64-bit
  Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz
  Memory: 15,4 GiB of RAM

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-09 (57 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5591
  Package: plymouth 0.9.4git20200323-0ubuntu6.2
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet 
splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Tags:  focal
  TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth
  Uname: Linux 5.4.0-88-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/10/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0DVVG1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd06/10/2021:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5591
  dmi.product.sku: 0819
  dmi.sys.vendor: Dell Inc.

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


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

[Touch-packages] [Bug 1946192] [NEW] "Press Ctrl+C to cancel all filesystem checks in process" on every boot

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I installed Kubuntu 20.04 on Latitude 5591 laptop using flash drive.
Installation run without any issues but now on every boot I notice a
message "Press Ctrl+C to cancel all filesystem checks in process" on the
Plymouth screen with Kubuntu logo. It flashes quickly and disappears.
I've got fast NVMe drive so I cannot say for sure whether it runs any
checks or not.

I booted from LiveCD and performed fsck checks of all my partitions:
fsck.vfat /dev/nvme0n1p1 (EFI partition)
fsck.vfat /dev/nvme0n1p2 (Dell service partition, not mounted)
e2fsck -f /dev/nvme0n1p3 (Root partition)
e2fsck -f /dev/nvme0n1p5 (Home partition)
These checks showed no problems.

I changed mount counter to set periodic checks:
sudo tune2fs -c 29 /dev/nvme0n1p3
sudo tune2fs -c 30 /dev/nvme0n1p5
But despite these settings this message still appears on every boot.

Operating System: Kubuntu 20.04.3
Kernel Version: 5.4.0-88-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz
Memory: 15,4 GiB of RAM

---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-08-09 (57 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 5591
Package: plymouth 0.9.4git20200323-0ubuntu6.2
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet 
splash vt.handoff=7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic 
root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet 
splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
Tags:  focal
TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth
Uname: Linux 5.4.0-88-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 06/10/2021
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.0
dmi.board.name: 0DVVG1
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd06/10/2021:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5591
dmi.product.sku: 0819
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-collected bot-comment focal
-- 
"Press Ctrl+C to cancel all filesystem checks in process" on every boot
https://bugs.launchpad.net/bugs/1946192
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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 1946235] Re: pcscd won't install due to bad dependency version

[Lars Noodén]

$ apt policy pcscd libpcsclite1
pcscd:
  Installed: (none)
  Candidate: 1.9.1-1
  Version table:
 1.9.1-1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages
100 /var/lib/dpkg/status
libpcsclite1:
  Installed: 1.9.3-2
  Candidate: 1.9.3-2
  Version table:
 *** 1.9.3-2 500
500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status
 1.9.1-1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

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

Title:
  pcscd won't install due to bad dependency version

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  # apt install pcscd
  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:
   pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed
   qemu-block-extra : Depends: qemu-system-x86 (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-arm (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-mips (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-ppc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-sparc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-misc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-s390x (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-x86-xen (= 1:6.0+dfsg-2expubuntu1) 
but it is not going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pcscd (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Oct  6 17:15:29 2021
  InstallationDate: Installed on 2020-06-16 (477 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to impish on 2021-10-06 (0 days ago)

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


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

[Touch-packages] [Bug 1946196] Re: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)

[Daniel van Vugt]

I already had the fix for bug 1943189 nine days before opening this one.

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

Title:
  Additional Drivers fails with pk-client-error-quark: Cannot download
  packages whilst offline (257)

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Additional Drivers fails to install nvidia-driver-470:

Error while applying changes

pk-client-error-quark: Cannot download packages whilst offline (257)

  But the machine is ONLINE with full Internet access.

  WORKAROUND:

  sudo apt install nvidia-driver-470

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


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

[Touch-packages] [Bug 1946293] [NEW] Update slapd to include db directory in debconf

[Matt]

Public bug reported:

Add the olcDbDirectory value as a debconf setting, so the directory may
be relocated. This is especially helpful when building a container to
run slapd with multiple ldap databases using one or more volumes.

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


** Tags: feature

** Project changed: launchpad => openldap

** Project changed: openldap => openldap (Ubuntu)

** Description changed:

  Add the olcDbDirectory value as a debconf setting, so the directory may
  be relocated. This is especially helpful when building a container to
- run slapd.
+ run slapd with multiple ldap databases using one or more volumes.

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

Title:
  Update slapd to include db directory in debconf

Status in openldap package in Ubuntu:
  New

Bug description:
  Add the olcDbDirectory value as a debconf setting, so the directory
  may be relocated. This is especially helpful when building a container
  to run slapd with multiple ldap databases using one or more volumes.

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


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

[Touch-packages] [Bug 1946293] [NEW] Update slapd to include db directory in debconf

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Add the olcDbDirectory value as a debconf setting, so the directory may
be relocated. This is especially helpful when building a container to
run slapd.

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


** Tags: feature
-- 
Update slapd to include db directory in debconf
https://bugs.launchpad.net/bugs/1946293
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to openldap 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 1946286] [NEW] Merge openssh from Debian unstable for 22.04

[Bryce Harrington]

Public bug reported:

Scheduled-For: 22.12
Upstream: tbd
Debian:   1:8.4p1-6
Ubuntu:   1:8.4p1-6ubuntu2


Debian typically updates openssh every 1 months on average, but it was
last updated 21.08 and looks overdue.  Check back in on this monthly.


### New Debian Changes ###

openssh
openssh (1:8.4p1-6) unstable; urgency=medium

  [ Colin Watson ]
  * Rename ssh group to _ssh (closes: #990456).  It's only used by
ssh-agent.
  * debian/tests/regress: Don't fail cleanup if haveged isn't running.
  * Backport from upstream:
- Add includes.h to compat tests (closes: #992134, LP: #1939751).
  * Use 'command -v' in maintainer scripts rather than 'which'.

  [ Athos Ribeiro ]
  * d/systemd/ssh@.service: preserve the systemd managed runtime directory to
ensure parallel processes will not disrupt one another when halting
(LP: #1905285) (closes: #934663)

 -- Colin Watson   Thu, 19 Aug 2021 11:04:01 +0100

openssh (1:8.4p1-5) unstable; urgency=high

  * CVE-2021-28041: Fix double free in ssh-agent(1) (closes: #984940).

 -- Colin Watson   Sat, 13 Mar 2021 09:59:40 +

openssh (1:8.4p1-4) unstable; urgency=medium

  * Avoid using libmd's  even if it's installed (closes:
#982705).

 -- Colin Watson   Mon, 15 Feb 2021 10:25:17 +

openssh (1:8.4p1-3) unstable; urgency=medium

  * Backport from upstream:
- Fix `EOF: command not found` error in ssh-copy-id (closes: #975540).

 -- Colin Watson   Wed, 02 Dec 2020 10:32:23 +

openssh (1:8.4p1-2) unstable; urgency=medium

  * Revert incorrect upstream patch that claimed to fix the seccomp sandbox
on x32 but in fact broke it instead.

 -- Colin Watson   Mon, 26 Oct 2020 17:41:13 +

openssh (1:8.4p1-1) unstable; urgency=medium

  * New upstream release (https://www.openssh.com/txt/release-8.4):
- [SECURITY] ssh-agent(1): restrict ssh-agent from signing web
  challenges for FIDO/U2F keys.
- [SECURITY] ssh-keygen(1): Enable FIDO 2.1 credProtect extension when
  generating a FIDO resident key.
- ssh-keygen(1): the format of the attestation information optionally
  recorded when a FIDO key is generated has changed. It now includes the
  authenticator data needed to validate attestation signatures. 
- The API between OpenSSH and the FIDO token middleware has changed and
  the SSH_SK_VERSION_MAJOR version has been incremented as a result.
  Third-party middleware libraries must support the current API version
  (7) to work with OpenSSH 8.4.
- ssh(1), ssh-keygen(1): support for FIDO keys that require a PIN for
  each use. These keys may be generated using ssh-keygen using a new
  'verify-required' option. When a PIN-required key is used, the user
  will be prompted for a PIN to complete the signature operation.
- sshd(8): authorized_keys now supports a new 'verify-required' option
  to require FIDO signatures assert that the token verified that the
  user was present before making the signature. The FIDO protocol
  supports multiple methods for user-verification, but currently OpenSSH
  only supports PIN verification.
- sshd(8), ssh-keygen(1): add support for verifying FIDO webauthn
  signatures. Webauthn is a standard for using FIDO keys in web
  browsers. These signatures are a slightly different format to plain
  FIDO signatures and thus require explicit support.
- ssh(1): allow some keywords to expand shell-style ${ENV} environment
  variables. The supported keywords are CertificateFile, ControlPath,
  IdentityAgent and IdentityFile, plus LocalForward and RemoteForward
  when used for Unix domain socket paths.
- ssh(1), ssh-agent(1): allow some additional control over the use of
  ssh-askpass via a new $SSH_ASKPASS_REQUIRE environment variable,
  including forcibly enabling and disabling its use (closes: #368657).
- ssh(1): allow ssh_config(5)'s AddKeysToAgent keyword accept a time
  limit for keys in addition to its current flag options. Time-limited
  keys will automatically be removed from ssh-agent after their expiry
  time has passed.
- scp(1), sftp(1): allow the -A flag to explicitly enable agent
  forwarding in scp and sftp. The default remains to not forward an
  agent, even when ssh_config enables it.
- ssh(1): add a '%k' TOKEN that expands to the effective HostKey of the
  destination. This allows, e.g., keeping host keys in individual files
  using 'UserKnownHostsFile ~/.ssh/known_hosts.d/%k' (closes: #481250).
- ssh(1): add %-TOKEN, environment variable and tilde expansion to the
  UserKnownHostsFile directive, allowing the path to be completed by the
  configuration.
- ssh-keygen(1): allow 'ssh-add -d -' to read keys to be deleted from
  stdin.
- sshd(8): improve logging for MaxStartups connection throttling.  sshd
  will now log when it starts and stops throttling and periodically
  while in this state.
- ssh(1), ssh-keygen(1): 

Re: [Touch-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

[Thiago Jung Bauermann]

Hello,

I’d just like to report that I haven’t seen this problem in a while. The 
last time I see the “retry page fault” messages in my log was on August 9.

I’ve been using the ‘amdgpu/picasso*‘ files from linux-firmware commit 
c46b8c364b82 (“ice: update package file to 1.3.26.0”) so apparently this 
particular problem was recently fixed.

Which isn’t to say that I’m having a trouble-free amdgpu experience, 
unfortunately. Every week or so my laptop comes back from sleep with the 
screen and keyboard frozen (I can still ssh into it), but now the error is:

kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* 
[CRTC:67:crtc-0] flip_done timed out

But it seems to be a separate problem from the one reported in this 
particular launchpad issue. I’ll see if I can find a more appropriate 
launchpad issue and post the details there.

Thank you all for your help and support with this issue.

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

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

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


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

[Touch-packages] [Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd

[Heather Ellsworth]

I've got this setup between two vms, where the server vm is hosting
dnsmasq with ntp and the client synchronizes from the server (on a
private network). This issue of the timesync conf needing to be updated
exists in systemd-timesyncd too. But tackling the NetworkManager case as
this is the customer issue.. we could put this fix in either networkd-
dispatcher or network-manager. I've got a local build of network-manager
that drops the file in place.. but needs to be tweaked.

Should the 10-update-timesyncd file be put in place by networkd-
dispatcher or network-manager?

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

Title:
  NTP servers from DHCP are not propagated to timesyncd

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  Network manager gets NTP servers from DHCP but do not update timesyncd to use 
it which keeps using ntp.ubuntu.com.
   
  This is a problem on private networks which do not have access to public 
internet. On this type of network the configuration of timesyncd must be 
updated manually instead of inheriting the conf from the dhcp servers.

  This can be integrated with a NM dispatcher script such as below:

  etc/NetworkManager/dispatcher.d/10-update-timesyncd for example:

  ==8<=8<=8<=8<=8<==
  #! /usr/bin/bash

  [ -n "$CONNECTION_UUID" ] || exit

  INTERFACE=$1
  ACTION=$2

  case $ACTION in
  up | dhcp4-change | dhcp6-change)
  [ -n "$DHCP4_NTP_SERVERS" ] || exit
  mkdir -p /etc/systemd/timesyncd.conf.d/
  cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  [Time]
  NTP=$DHCP4_NTP_SERVERS
  RootDistanceMaxSec=15
  EOF
  systemctl restart systemd-timesyncd
 ;;
  down)
  rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  systemctl restart systemd-timesyncd
  ;;
  esac
  ==8<=8<=8<=8<=8<==

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 28 14:08:52 2021
  InstallationDate: Installed on 2020-05-31 (393 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  RebootRequiredPkgs:
   linux-image-5.11.0-20-generic
   linux-base
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions


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

[Touch-packages] [Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

[Paride Legovini]

** Also affects: rsync via
   https://github.com/WayneD/rsync/issues/236
   Importance: Unknown
   Status: Unknown

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

Title:
  rsync -u --inplace --partial -a can't resume transfer

Status in rsync:
  Unknown
Status in rsync package in Ubuntu:
  Opinion

Bug description:
  Suppose you have a file in hostA:

hostA$ ls -l /tmp/files
 -rw-rw-r-- 2 root root 563016 Jan 10 15:01 test.txt

  You download it from the hostB using:

hostB$ rsync -u --inplace --partial -a hostA::files/* .

  If the transfer is aborted, hostB will get only a partial file:

hostB$ ls -l /tmp/files
 -rw-rw-r-- 2 root root   2024 Jan 11 18:00 test.txt

  BUT the ctime/mtime of hostB/test.txt now is NEWER than hostA/test.txt(and 
mtime == ctime). So, if you run the same rsync -u command again:

hostB$ rsync -u --inplace --partial -a hostA::files/* .

  Rsync will SKIP THE FILE, because hostB/test.txt is "newer" than
  hostA/test.txt. So you CAN'T resume using rsync -u command, and you
  will think there are no differences.

  To avoid this bug, rsync must create the file with ctime=mtime=0. And
  if the file already exists before transfer, rsync -u must not change
  his current ctime/mtime. Ctime/mtime must be updated ONLY after the
  transfer was successfully completed.

  Note this is really need because there are scenarios where checksum
  comparison can't be used, only comparison by time. For example, to
  avoid deleting changes made in hostB to test.txt. Also I need to use
  --inplace.

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


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

[Touch-packages] [Bug 1945713] Re: Flaky test brotli/basic on focal amd64?

[Sergio Durigan Junior]

I spent some time trying to get to the bottom of the issue, but
unfortunately I was not able to make much progress here.

As expected, the very first thing to do here is to reproduce the bug
locally.  I tried many things:

- I built the package locally and ran autopkgtest against it.  Passed.

- I built the package inside a Focal LXD container and then ran
autopkgtest there.  Passed.

- Still inside the Focal LXD container, I tried to invoke the failing
test manually.  Passed.

- I know that Ubuntu's autopkgtest infra uses a Bionic host to run the
tests.  I created a Bionic VM, and inside it I git cloned the
development version of autopkgtest.  Then, I invoked autopkgtest against
the Focal source package for libsoup2.4, using a Focal LXD container as
the testbed.  Passed.

I ran out of ideas on what to try locally, and given that Bryce was able
to add a hint for the failure and unblock apache2, I am giving up (at
least for now).  The way I see it, a person interested in continuing
debugging this could:

- Add debugging statements to the libsoup2.4 code, upload the modified
package to a PPA, and run autopkgtests using the Ubuntu infra.  This
should be able to provide more useful information regarding the array
manipulation that's happening in the test.

- If the above doesn't work, one could try to add debugging statements
to the libglib code that's responsible for array manipulations.


Lastly, it's important to mention that this may very well be something 
unrelated to libsoup2.4/glib.  It can even be a hardware issue, who knows...

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

Title:
  Flaky test brotli/basic on focal amd64?

Status in libsoup2.4 package in Ubuntu:
  New

Bug description:
  The brotli/basic test case periodically fails.  It appears that a few
  retriggers can result in a pass:

  https://autopkgtest.ubuntu.com/packages/libs/libsoup2.4/focal/amd64

  The failures look like this in autopkgtest logs:

  ERROR:../tests/brotli-decompressor-test.c:59:test_brotli:
  assertion failed ((char*)out_bytes->data == contents): ("***\nU" ==
  "***\n")

  I've replaced most of the text with '***' to highlight the difference
  is a 'U' character appended.

  The test case is essentially doing a decompression of 'brotli-
  data/compressed.br' and comparing that it matches 'brotli-
  data/uncompressed.txt'.  I've done this manually using the brotli cli,
  and the files do indeed have the same content.  I've also built the
  package and run the test case locally in a focal lxc container on
  amd64:

  $ cd 
libsoup2.4-gu/debian/libsoup2.4-tests/usr/libexec/installed-tests/libsoup-2.4
  $ while : ; do ./brotli-decompressor-test | grep 'brotli/basic';  sleep 
0.1; done

  I left that to run several hundred cycles but no failures reported at
  all.

  There are a bunch of instances of this failure, here's a few for
  reference:

  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210602_152107_d1d56@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210531_201241_8b1be@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20200508_211619_2aec8@/log.gz

  That last link is the earliest instance I've been able to find.

  You'll notice in the second two links they also have a failure "not ok
  2 /ssl/tls-interaction", but the first link shows only the brotli
  failure.

  Interestingly, I've not found instances of this failure against other
  architectures than amd64, nor have I seen it on releases other than
  focal.  No dice from googling for bug reports or other reports of test
  failures with libsoup2.4 + brotli.

  The test's code is doing this, basically:

  SoupBrotliDecompressor *dec = soup_brotli_decompressor_new ();
  do {
  result = g_converter_convert (G_CONVERTER (dec), in_buf, 
length, out_buf, sizeof out_buf, 0,
&bytes_read, &bytes_written, 
&error);
  g_byte_array_append (out_bytes, out_buf, bytes_written);
in_buf += bytes_read;
  length -= bytes_read;

  } while (result == G_CONVERTER_CONVERTED);

  soup_brotli_decompressor's code is here:

  https://gitlab.gnome.org/GNOME/libsoup/-/blob/master/libsoup/content-
  decoder/soup-brotli-decompressor.c

  But I'm not spotting anything that would obviously cause a 'U' to be
  randomly appended sometimes.  And why 'U'?  UINT? Unknown? User error?

  There are some interesting bug reports in GNOME about brotli in
  libsoup's bug tracker (e.g. #106, #146, #119, and #193), but none that
  match this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1945713/+subscriptions


-- 
Mailing

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

[Bryce Harrington]

** Changed in: bind9 (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  Fix Released
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid
Status in avahi source package in Bionic:
  Fix Released
Status in bind9 source package in Bionic:
  Confirmed
Status in avahi source package in Cosmic:
  Fix Released
Status in bind9 source package in Cosmic:
  Won't Fix
Status in avahi package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Network connections for some users fail (in some cases a direct
  interface, in others when connecting a VPN) because the 'host' command
  to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-
  check-dns.sh never times out like it should - leaving the script
  hanging indefinitely blocking interface up and start-up. This appears
  to be a bug in host caused in some circumstances however we implement
  a workaround to call it under 'timeout' as the issue with 'host' has
  not easily been identified, and in any case acts as a fall-back.

  [Test Case]

   * Multiple people have been unable to create a reproducer on a
  generic machine (e.g. it does not occur in a VM), I have a specific
  machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM)
  by simply "ifdown br0; ifup br0" and there are clearly 10s of other
  users affected in varying circumstances that all involve the same
  symptoms but no clear test case exists. Best I can suggest is that I
  test the patch on my system to ensure it works as expected, and the
  change is only 1 line which is fairly easily auditible and
  understandable.

  [Regression Potential]

   * The change is a single line change to the shell script to call host with 
"timeout". When tested on working and non-working system this appears to 
function as expected. I believe the regression potential for this is 
subsequently low.
   * In attempt to anticipate possible issues, I checked that the timeout 
command is in the same path (/usr/bin) as the host command that is already 
called without a path, and the coreutils package (which contains timeout) is an 
Essential package. I also checked that timeout is not a built-in in bash, for 
those that have changed /bin/sh to bash (just in case).

  [Other Info]
   
   * N/A

  [Original Bug Description]

  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:11:33 2018
  InstallationDate: Installed on 2017-06-15 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: openconnect
  UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago)

To manage notifications about 

[Touch-packages] [Bug 1946235] Re: pcscd won't install due to bad dependency version

[Ludovic Rousseau]

What is the complete output of the command:
apt policy pcscd libpcsclite1

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

Title:
  pcscd won't install due to bad dependency version

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  # apt install pcscd
  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:
   pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed
   qemu-block-extra : Depends: qemu-system-x86 (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-arm (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-mips (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-ppc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-sparc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-misc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-s390x (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-x86-xen (= 1:6.0+dfsg-2expubuntu1) 
but it is not going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pcscd (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Oct  6 17:15:29 2021
  InstallationDate: Installed on 2020-06-16 (477 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to impish on 2021-10-06 (0 days ago)

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


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

[Touch-packages] [Bug 1943189] Re: [SRU] "cannot refresh whilst network offline"in plasma-discover

[Erich Eickmeyer ]

** Summary changed:

- "cannot refresh whilst network offline" bug
+ [SRU] "cannot refresh whilst network offline"in plasma-discover

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

Title:
  [SRU] "cannot refresh whilst network offline"in plasma-discover

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Focal:
  Confirmed
Status in packagekit source package in Hirsute:
  Confirmed
Status in packagekit source package in Impish:
  Fix Released

Bug description:
  [Impact]

  In Ubuntu Impish, an issue has been noted in regards to refreshing
  packages in Plasma Discover for upgrade or installation. An error
  appears upon initialization of the Discover interface:

  "cannot refresh whilst network offline"

  This will happen regardless of if a system is online or not.

  I identified a race condition in which this is occurring on systems
  where packagekitd is initialized before the network service is online.
  This was a relatively easy fix and required adding one line to the
  packagekit.service file:

  Wants=network-online.target

  This ensures that packagekitd is not initialized prior to being
  online. If the 90 second deadline isn't met, then packagekitd will
  simply not start as a background process until the user connects to
  the network and initializes it via a graphical utility, such as with
  GNOME Software or Plasma Discover, both of which initialize
  packagekitd on a user level.

  The attached patch will easily apply the fix via normal Debian
  packaging methods.

  [Test Plan]

   * Install Kubuntu or Ubuntu Studio

   * While connected to network, Run Discover

   * Discover will complain about "cannot refresh whilst offline", which
  is being communicated from PackageKit. All functionality in Discover
  is hindered from this point forward. This is due to a hung packagekitd
  process which sees the network offline, even though this is false.

  [Where problems could occur]

   * packagekitd's systemd service will time-out after 90 seconds if
  systemd finds no network, which means any update notifications will
  not automatically start until packagekitd is manually started.
  Luckily, Discover and GNOME Software both attempt to start packagekitd
  for the user when run. I'd consider this to be expected behavior for
  an offline system. The fix is mostly to prevent the false-negative of
  the system being offline when it's really not.

  [Other Info]

   * This fix has been accepted upstream by the PackageKit maintainers
  as a sane workaround for when gio misbehaves or otherwise. It's a
  decent safety net. https://github.com/PackageKit/PackageKit/pull/506

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: packagekit 1.2.2-2ubuntu1 [modified: 
lib/systemd/system/packagekit.service]
  ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1
  Uname: Linux 5.13.0-14-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Sep  9 16:34:12 2021
  InstallationDate: Installed on 2021-03-20 (172 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago)

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


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

[Touch-packages] [Bug 1945713] Re: Flaky test brotli/basic on focal amd64?

[Bryce Harrington]

hinted for now:

https://git.launchpad.net/~ubuntu-release/britney/+git/hints-
ubuntu/commit/?id=90bbdc608590c7b01f81619dae973bd8c26dd5b7

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

Title:
  Flaky test brotli/basic on focal amd64?

Status in libsoup2.4 package in Ubuntu:
  New

Bug description:
  The brotli/basic test case periodically fails.  It appears that a few
  retriggers can result in a pass:

  https://autopkgtest.ubuntu.com/packages/libs/libsoup2.4/focal/amd64

  The failures look like this in autopkgtest logs:

  ERROR:../tests/brotli-decompressor-test.c:59:test_brotli:
  assertion failed ((char*)out_bytes->data == contents): ("***\nU" ==
  "***\n")

  I've replaced most of the text with '***' to highlight the difference
  is a 'U' character appended.

  The test case is essentially doing a decompression of 'brotli-
  data/compressed.br' and comparing that it matches 'brotli-
  data/uncompressed.txt'.  I've done this manually using the brotli cli,
  and the files do indeed have the same content.  I've also built the
  package and run the test case locally in a focal lxc container on
  amd64:

  $ cd 
libsoup2.4-gu/debian/libsoup2.4-tests/usr/libexec/installed-tests/libsoup-2.4
  $ while : ; do ./brotli-decompressor-test | grep 'brotli/basic';  sleep 
0.1; done

  I left that to run several hundred cycles but no failures reported at
  all.

  There are a bunch of instances of this failure, here's a few for
  reference:

  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210602_152107_d1d56@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210531_201241_8b1be@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20200508_211619_2aec8@/log.gz

  That last link is the earliest instance I've been able to find.

  You'll notice in the second two links they also have a failure "not ok
  2 /ssl/tls-interaction", but the first link shows only the brotli
  failure.

  Interestingly, I've not found instances of this failure against other
  architectures than amd64, nor have I seen it on releases other than
  focal.  No dice from googling for bug reports or other reports of test
  failures with libsoup2.4 + brotli.

  The test's code is doing this, basically:

  SoupBrotliDecompressor *dec = soup_brotli_decompressor_new ();
  do {
  result = g_converter_convert (G_CONVERTER (dec), in_buf, 
length, out_buf, sizeof out_buf, 0,
&bytes_read, &bytes_written, 
&error);
  g_byte_array_append (out_bytes, out_buf, bytes_written);
in_buf += bytes_read;
  length -= bytes_read;

  } while (result == G_CONVERTER_CONVERTED);

  soup_brotli_decompressor's code is here:

  https://gitlab.gnome.org/GNOME/libsoup/-/blob/master/libsoup/content-
  decoder/soup-brotli-decompressor.c

  But I'm not spotting anything that would obviously cause a 'U' to be
  randomly appended sometimes.  And why 'U'?  UINT? Unknown? User error?

  There are some interesting bug reports in GNOME about brotli in
  libsoup's bug tracker (e.g. #106, #146, #119, and #193), but none that
  match this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1945713/+subscriptions


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

[Touch-packages] [Bug 1946196] Re: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)

[Leo]

I have the same problem when I try to install nvidia-driver-470 on
Ubuntu 21.10. My system was not updated, in my case I installed the OS
from 0.

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

Title:
  Additional Drivers fails with pk-client-error-quark: Cannot download
  packages whilst offline (257)

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Additional Drivers fails to install nvidia-driver-470:

Error while applying changes

pk-client-error-quark: Cannot download packages whilst offline (257)

  But the machine is ONLINE with full Internet access.

  WORKAROUND:

  sudo apt install nvidia-driver-470

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


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

[Touch-packages] [Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

[Nahuel Greco]

Reported to upstream at: https://github.com/WayneD/rsync/issues/236

** Bug watch added: github.com/WayneD/rsync/issues #236
   https://github.com/WayneD/rsync/issues/236

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

Title:
  rsync -u --inplace --partial -a can't resume transfer

Status in rsync package in Ubuntu:
  Opinion

Bug description:
  Suppose you have a file in hostA:

hostA$ ls -l /tmp/files
 -rw-rw-r-- 2 root root 563016 Jan 10 15:01 test.txt

  You download it from the hostB using:

hostB$ rsync -u --inplace --partial -a hostA::files/* .

  If the transfer is aborted, hostB will get only a partial file:

hostB$ ls -l /tmp/files
 -rw-rw-r-- 2 root root   2024 Jan 11 18:00 test.txt

  BUT the ctime/mtime of hostB/test.txt now is NEWER than hostA/test.txt(and 
mtime == ctime). So, if you run the same rsync -u command again:

hostB$ rsync -u --inplace --partial -a hostA::files/* .

  Rsync will SKIP THE FILE, because hostB/test.txt is "newer" than
  hostA/test.txt. So you CAN'T resume using rsync -u command, and you
  will think there are no differences.

  To avoid this bug, rsync must create the file with ctime=mtime=0. And
  if the file already exists before transfer, rsync -u must not change
  his current ctime/mtime. Ctime/mtime must be updated ONLY after the
  transfer was successfully completed.

  Note this is really need because there are scenarios where checksum
  comparison can't be used, only comparison by time. For example, to
  avoid deleting changes made in hostB to test.txt. Also I need to use
  --inplace.

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


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

[Touch-packages] [Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

[Nahuel Greco]

Hello Paride, 4 years have passed from my initial report, I forgot
completely about this bug :)

Fine, I will post this issue to upstream.

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

Title:
  rsync -u --inplace --partial -a can't resume transfer

Status in rsync package in Ubuntu:
  Opinion

Bug description:
  Suppose you have a file in hostA:

hostA$ ls -l /tmp/files
 -rw-rw-r-- 2 root root 563016 Jan 10 15:01 test.txt

  You download it from the hostB using:

hostB$ rsync -u --inplace --partial -a hostA::files/* .

  If the transfer is aborted, hostB will get only a partial file:

hostB$ ls -l /tmp/files
 -rw-rw-r-- 2 root root   2024 Jan 11 18:00 test.txt

  BUT the ctime/mtime of hostB/test.txt now is NEWER than hostA/test.txt(and 
mtime == ctime). So, if you run the same rsync -u command again:

hostB$ rsync -u --inplace --partial -a hostA::files/* .

  Rsync will SKIP THE FILE, because hostB/test.txt is "newer" than
  hostA/test.txt. So you CAN'T resume using rsync -u command, and you
  will think there are no differences.

  To avoid this bug, rsync must create the file with ctime=mtime=0. And
  if the file already exists before transfer, rsync -u must not change
  his current ctime/mtime. Ctime/mtime must be updated ONLY after the
  transfer was successfully completed.

  Note this is really need because there are scenarios where checksum
  comparison can't be used, only comparison by time. For example, to
  avoid deleting changes made in hostB to test.txt. Also I need to use
  --inplace.

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


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

[Touch-packages] [Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

[Paride Legovini]

Hello Nahuel,

According to your reasoning I assume the "root" issue should still
affect the versions of rsync shipped with the newer Ubuntu releases.

I agree it would be nice for the behavior you describe to be documented,
but I don't think it's worth patching the Ubuntu package for it. I
recognize we have a papercut here, but I don't think the fix for it
belongs to Ubuntu; it should instead be driven (and thus also validated)
upstream. For this reason I'm marking this bug as a Won't Fix. Should
you disagree with my assessment please comment back and set the bug
status back to New, we'll look at it again. Thanks!

** Changed in: rsync (Ubuntu)
   Status: Triaged => Opinion

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

Title:
  rsync -u --inplace --partial -a can't resume transfer

Status in rsync package in Ubuntu:
  Opinion

Bug description:
  Suppose you have a file in hostA:

hostA$ ls -l /tmp/files
 -rw-rw-r-- 2 root root 563016 Jan 10 15:01 test.txt

  You download it from the hostB using:

hostB$ rsync -u --inplace --partial -a hostA::files/* .

  If the transfer is aborted, hostB will get only a partial file:

hostB$ ls -l /tmp/files
 -rw-rw-r-- 2 root root   2024 Jan 11 18:00 test.txt

  BUT the ctime/mtime of hostB/test.txt now is NEWER than hostA/test.txt(and 
mtime == ctime). So, if you run the same rsync -u command again:

hostB$ rsync -u --inplace --partial -a hostA::files/* .

  Rsync will SKIP THE FILE, because hostB/test.txt is "newer" than
  hostA/test.txt. So you CAN'T resume using rsync -u command, and you
  will think there are no differences.

  To avoid this bug, rsync must create the file with ctime=mtime=0. And
  if the file already exists before transfer, rsync -u must not change
  his current ctime/mtime. Ctime/mtime must be updated ONLY after the
  transfer was successfully completed.

  Note this is really need because there are scenarios where checksum
  comparison can't be used, only comparison by time. For example, to
  avoid deleting changes made in hostB to test.txt. Also I need to use
  --inplace.

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


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

[Touch-packages] [Bug 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd

[Sergio Durigan Junior]

This bug doesn't apply to Impish.

** Changed in: gssproxy (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  gssproxy  crashes in libselinux.so.1 on Ubuntu 18.04 when called by
  rpc.gssd

Status in gssproxy package in Ubuntu:
  Invalid
Status in libselinux package in Ubuntu:
  Invalid
Status in gssproxy source package in Focal:
  Fix Released
Status in libselinux source package in Focal:
  Invalid
Status in gssproxy source package in Hirsute:
  Fix Released
Status in libselinux source package in Hirsute:
  Invalid

Bug description:
  [ Impact ]

  gssproxy users on Focal and Hiruste who configure the package to
  handle NFS mountpoints using Kerberos authentication will experience a
  segmentation fault when invoking the service either through systemd or
  by hand.

  [ Test Case]

  Inside a Focal LXD container:

  $ lxc launch images:ubuntu/focal gssproxy-bug1788459-focal
  $ lxc shell gssproxy-bug1788459-focal
  # apt update
  # apt install -y gssproxy nfs-kernel-server
  # cat > /etc/gssproxy/gssproxy.conf << __EOF__
  [gssproxy]
  debug = true
  debug_level = 3
  __EOF__
  # cat >> /etc/gssproxy/25-nfs-server.conf << __EOF__
  [service/nfs-server]
  mechs = krb5
  socket = /run/gssproxy.sock
  cred_store = keytab:/etc/krb5.keytab
  trusted = yes
  kernel_nfsd = yes
  euid = 0
  __EOF__
  # /usr/sbin/gssproxy --interactive --debug --debug-level=3 
--socket=/run/gssproxy.sock
  [2021/06/30 14:34:14]: Debug Enabled (level: 3) 
  [2021/06/30 14:34:14]: Keytab /etc/krb5.keytab has no content (-1765328203)
  [2021/06/30 14:34:14]: Service: nfs-server, Enckey: [ephemeral], Enctype: 18
  [2021/06/30 14:34:14]: Client [2021/06/30 14:34:14]: (/usr/sbin/gssproxy) 
[2021/06/30 14:34:14]:  connected (fd = 12)[2021/06/30 14:34:14]:  (pid = 3428) 
(uid = 0) (gid = 0)Segmentation fau
  lt (core dumped)

  [ Where problems could occur ]

  * The backported patch is simple and it is very unlikely that it will 
introduce a regression.
  * As usual, it is always risky to rebuild a package that hasn't been touched 
for more than 1 year, albeit in this case the risk is very low because the 
package is not very complex.

  [ Original Description ]

  I have apache configured to perform a kerberized NFS4 mount using
  rpc.gssd and gssproxy.

  If I request a web page that requires NFS4 access, then gssproxy
  crashes, reporting a segfault in libselinux.so.1 and the web request
  generates a 403 error.

  gssproxy[6267]: segfault at 0 ip 7f2f5bb1951a sp 7ffe861da150
  error 4 in libselinux.so.1[7f2f5bb0d000+25000]

  If I run gssproxy at debug level = 3, and then load a web page, I can
  see the uid/principal request for www-data come in from rpc.gssd:

  # gssproxy -d --debug-level=3 -i -C /etc/gssproxy

  [2018/08/22 17:51:40]: Debug Enabled (level: 3)
  [2018/08/22 17:52:06]: Client [2018/08/22 17:52:06]: (/usr/sbin/rpc.gssd) 
[2018/08/22 17:52:06]:  connected (fd = 10)[2018/08/22 17:52:06]:  (pid = 4548) 
(uid = 33) (gid = 33)Segmentation fault (core dumped)

  Since gssproxy is required to initiate kerberos principals for any
  local application services - Ubuntu 18.04 does not currently support
  running application services with NFS4 kerberos dependencies.  This
  has a fairly significant impact on anyone attempting to implement
  kerberos on Ubuntu 18.04

  Ubuntu 18.04.1 LTS
  gssproxy 0.8.0-1
  libselinux1:amd64 2.7-2build2
  libgssrpc4:amd64 1.16-2build1

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


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

[Touch-packages] [Bug 1946235] Re: pcscd won't install due to bad dependency version

[Lars Noodén]

Yes, I've done the following.

apt update
apt upgrade

However, qemu is not mentioned in any part of the output from those
steps.  Though it is installed:

$ apt-cache policy qemu-system-x86 | head -n 3
qemu-system-x86:
  Installed: 1:6.0+dfsg-2expubuntu1
  Candidate: 1:6.0+dfsg-2expubuntu1

The problems with pcscd arose after using the update-manager to move
from 21.04 to 21.10-beta.  pcscd is a dependency for another package
which is the main reason for using Ubuntu instead of another distro.
Specifically it is a smart card reader needed to interact with an
increasing number of government sites and services.

After removing qemu-block-extra, I get the following when trying to
install pcscd :

# apt install pcscd
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:
 pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

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

Title:
  pcscd won't install due to bad dependency version

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  # apt install pcscd
  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:
   pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed
   qemu-block-extra : Depends: qemu-system-x86 (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-arm (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-mips (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-ppc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-sparc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-misc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-s390x (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-x86-xen (= 1:6.0+dfsg-2expubuntu1) 
but it is not going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pcscd (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Oct  6 17:15:29 2021
  InstallationDate: Installed on 2020-06-16 (477 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to impish on 2021-10-06 (0 days ago)

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


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

[Touch-packages] [Bug 1946235] Re: pcscd won't install due to bad dependency version

[Lars Noodén]

I should add that libpcsclite1 is installed but a newer version,

# apt install libpcsclite1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libpcsclite1 is already the newest version (1.9.3-2).

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

Title:
  pcscd won't install due to bad dependency version

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  # apt install pcscd
  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:
   pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed
   qemu-block-extra : Depends: qemu-system-x86 (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-arm (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-mips (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-ppc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-sparc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-misc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-s390x (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-x86-xen (= 1:6.0+dfsg-2expubuntu1) 
but it is not going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pcscd (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Oct  6 17:15:29 2021
  InstallationDate: Installed on 2020-06-16 (477 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to impish on 2021-10-06 (0 days ago)

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


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

[Touch-packages] [Bug 1608965] Re: ssh GSSAPI rekey failure

[Paride Legovini]

Yakkety reached EOL, while Xenial is now in Extended Security
Maintenance, and this bug doesn't qualify for it, so this bug won't be
fixed in those releases.

** Changed in: openssh (Ubuntu Xenial)
   Status: Triaged => Won't Fix

** Changed in: openssh (Ubuntu Yakkety)
   Status: Triaged => Won't Fix

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

Title:
  ssh GSSAPI rekey failure

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

Bug description:
  If I have ssh set up using GSSAPI with rekeying enabled, then the
  connection fails on rekey, and tries to do host-based verification
  'mid-session'.

  Steps to reproduce:

  $ ssh -vvv server.example.com
  
  debug1: Authenticating to ssh.example.com:22 as 'user'
  
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-A/vxljAEU54gt9a48EiANQ==,gss-group1-sha1-A/vxljAEU54gt9a48EiANQ==,gss-group14-sha1-A/vxljAEU54gt9a48EiANQ==,gss-gex-sha1-bontcUwnM6aGfWCP21alxQ==,gss-group1-sha1-bontcUwnM6aGfWCP21alxQ==,gss-group14-sha1-bontcUwnM6aGfWCP21alxQ==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group1-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
  
  debug2: peer server KEXINIT proposal
  debug2: KEX algorithms: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
  
  Last login: Tue Aug 02 10:47:20 2016 from foo

  # Then do 'kinit' on the client to get a new ticket...

  debug1: need rekeying
  debug1: SSH2_MSG_KEXINIT sent
  debug1: rekeying in progress
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1
  debug2: host key algorithms: 
ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa,null
  [...]
  debug2: peer server KEXINIT proposal
  debug2: KEX algorithms: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group1-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
  [...]
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: rekeying in progress
  debug1: rekeying in progress
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:w7yxbCZNBX4d5EAgmCrFYa3XUpDjvWiDOw4/YOY9q8E
  The authenticity of host 'server.example.com (10.0.0.1)' can't be established.
  ECDSA key fingerprint is SHA256:w7yxbCZNBX4d5EAgmCrFYa3XUpDjvWiDOw4/YOY9q8E.
  Are you sure you want to continue connecting (yes/no)? 
  Host key verification failed.

  It looks like the list of KEX algorithms differs between the initial
  connection, and the rekeying.

  This behaviour seems to occur with a client running 16.04 (openssh-
  client 1:7.2p2-4ubuntu1) but not on 15.10 (openssh-client
  1:6.9p1-2ubuntu0.2).

  ssh_config is as follows:

  HashKnownHosts no
  GSSAPIAuthentication yes
  GSSAPIDelegateCredentials yes
  GSSAPIRenewalForcesRekey yes
  GSSAPITrustDNS yes
  GSSAPIKeyExchange yes
  ForwardX11 yes
  ForwardX11Trusted yes

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


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

[Touch-packages] [Bug 1618719] Re: scp1 reports ssh1 is not supported

[Paride Legovini]

Xenial is now in Extended Security Maintenance and this bug doesn't
qualify for it, so this bug won't be fixed in that release.

** Changed in: openssh (Ubuntu Xenial)
   Status: Triaged => Won't Fix

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

Title:
  scp1 reports ssh1 is not supported

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

Bug description:
  For getting ssh protocol 1 support I installed the package 
openssh-client-ssh1.
  This works with .ssh/config host entries, when omitting any "Protocol 1" 
lines, but calling "ssh1 -1 host".
  This package also has the command scp1 included, but this command doesn't 
have ssh protocol 1 support:
  > corben@ubuntu:~$ scp1 -1 host:/path/to/file .
  > ssh1 is not supported
  Is the ssh protocol 1 support not included for scp1 during compile time?

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


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

[Touch-packages] [Bug 1645002] Re: ssh sessions are not cleanly terminated on shutdown/restart with systemd

[Paride Legovini]

Xenial is now in Extended Security Maintenance and this bug doesn't
qualify for it, so the bugfix won't be SRUed there.

** Changed in: openssh (Ubuntu Xenial)
   Status: Triaged => Won't Fix

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

Title:
  ssh sessions are not cleanly terminated on shutdown/restart with
  systemd

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Won't Fix
Status in openssh source package in Yakkety:
  Fix Released
Status in openssh package in Debian:
  Fix Released

Bug description:
  In Ubuntu 16.04, a "reboot" command does not terminate the ssh
  session. This results in clients hanging, until timing out (sometimes
  as much as 120 seconds).

  This also introduces bugs to all  orchestration / automation tools which work 
over SSH, since they cannot issue their reboot equivalent for Ubuntu 16.04 
hosts. For example, have a look at this issue for Fabric:
  https://github.com/fabric/fabric/issues/1488

  The exact same bug has been fixed in Debian in version openssh/1:7.2p2-6. 
  There is a very detailed discussion in their bug tracker:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751636

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


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

[Touch-packages] [Bug 1651044] Re: ProxyDHCP replies on invalid range

[Paride Legovini]

Hi,

I had a look at [1] and AIUI this wasn't recognized as an upstream bug.
I also can't find a relevant Debian bug about this issue. The bug
description says it affected Xenial, which is now in Extended Security
Maintenance, so it's a Won't Fix there.

For >= Bionic we need confirmation from an affected user the bug is
still present and valid. Waiting for feedback I'm marking this bug
report as Incomplete.

[1] https://lists.thekelleys.org.uk/pipermail/dnsmasq-
discuss/2016q4/011010.html

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

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

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

Title:
  ProxyDHCP replies on invalid range

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 16.04, I've configured dnsmasq to reply on subnet=10.160.37.0/24, 
yet it replies even when it gets an IP on subnet=10.161.254.0/24.
  I've only seen this after clean system restart. If I restart dnsmasq later 
on, it works as expected.
  Maybe when dnsmasq starts, the network isn't up yet, and it incorrectly 
initializes some networking information? I'm using network-manager with DHCP.

  Details:
  $ egrep -rv '^#|^$' /etc/dnsmasq.*
  /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-range=10.160.37.0,proxy
  
/etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-range=192.168.67.20,192.168.67.250,8h
  /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:enable-tftp
  /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:tftp-root=/var/lib/tftpboot/
  /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-option=17,/opt/ltsp/i386
  /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-vendorclass=etherboot,Etherboot
  /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-vendorclass=pxe,PXEClient
  /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-vendorclass=ltsp,"Linux ipconfig"
  
/etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-boot=net:pxe,/ltsp/i386/pxelinux.0
  
/etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-boot=net:etherboot,/ltsp/i386/nbi.img
  /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-boot=net:ltsp,/ltsp/i386/lts.conf
  /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-option=vendor:pxe,6,2b
  /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:dhcp-no-override
  /etc/dnsmasq.d/ltsp-server-dnsmasq.conf:pxe-service=X86PC, "Boot from 
network", /ltsp/i386/pxelinux

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  2: enp2s0:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether d0:50:99:a6:bc:0a brd ff:ff:ff:ff:ff:ff
  inet 10.161.254.185/24 brd 10.161.254.255 scope global dynamic enp2s0
 valid_lft 431873sec preferred_lft 431873sec
  inet6 fe80::f363:c1e2:9cb8:d9e2/64 scope link 
 valid_lft forever preferred_lft forever

  $ sudo netstat -nap | grep dnsmasq
  [sudo] password for administrator: 
  tcp0  0 0.0.0.0:53  0.0.0.0:*   LISTEN
  843/dnsmasq 
  tcp6   0  0 :::53   :::*LISTEN
  843/dnsmasq 
  udp0  0 0.0.0.0:53  0.0.0.0:* 
  843/dnsmasq 
  udp0  0 0.0.0.0:67  0.0.0.0:* 
  843/dnsmasq 
  udp0  0 0.0.0.0:69  0.0.0.0:* 
  843/dnsmasq 
  udp0  0 0.0.0.0:40110.0.0.0:* 
  843/dnsmasq 
  udp6   0  0 :::53   :::*  
  843/dnsmasq 
  udp6   0  0 :::69   :::*  
  843/dnsmasq 
  unix  2  [ ] DGRAM15746843/dnsmasq
 

  $ grep dnsmasq /var/log/syslog | tail -n 30
  Dec 19 10:52:17 ltsp-server systemd[1]: Starting dnsmasq - A lightweight DHCP 
and caching DNS server...
  Dec 19 10:52:17 ltsp-server dnsmasq[630]: dnsmasq: syntax check OK.
  Dec 19 10:52:20 ltsp-server dnsmasq[843]: started, version 2.75 cachesize 150
  Dec 19 10:52:20 ltsp-server dnsmasq[843]: compile time options: IPv6 
GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC 
loop-detect inotify
  Dec 19 10:52:20 ltsp-server dnsmasq[843]: DNS service limited to local subnets
  Dec 19 10:52:20 ltsp-server dnsmasq-dhcp[843]: DHCP, IP range 192.168.67.20 
-- 192.168.67.250, lease time 8h
  Dec 19 10:52:20 ltsp-server dnsmasq-dhcp[843]: DHCP, proxy on subnet 
10.160.37.0
  Dec 19 10:52:20 ltsp-server dnsmasq-tftp[843]: TFTP root is /var/lib/tftpboot/
  Dec 19 10:52:20 ltsp-server dnsmasq[843]: no servers found in 
/var/run/dnsmasq/resolv.conf, wil

[Touch-packages] [Bug 1946196] Re: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)

[Andrew Enderson]

While trouble shooting something else, I used the Driver Manager in
kubuntu System Settings (which uses Additional Drivers) to uninstall the
nvidia driver (nvidia-driver-390). After finishing the trouble shooting,
I attempted to reinstall the nvidia driver via Additional Drivers, and
I'm getting this error as well.

After seeing message #1, I also attempted to launched the Discover
package manager, and Discover is reporting the error as well: Cannot
refresh cache whilst offline.

I've recently run sudo apt update && sudo apt full-upgrade, so the
system appears to be up to date.

Distributor ID: Ubuntu
Description:Ubuntu Impish Indri (development branch)
Release:21.10
Codename:   impish

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

Title:
  Additional Drivers fails with pk-client-error-quark: Cannot download
  packages whilst offline (257)

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Additional Drivers fails to install nvidia-driver-470:

Error while applying changes

pk-client-error-quark: Cannot download packages whilst offline (257)

  But the machine is ONLINE with full Internet access.

  WORKAROUND:

  sudo apt install nvidia-driver-470

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


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

[Touch-packages] [Bug 1946235] Re: pcscd won't install due to bad dependency version

[Ludovic Rousseau]

It looks like you (also) have a problem with qemu.

pcscd 1.9.1-1 is from Ubuntu 21.04. But you are using Ubuntu 21.10.
Maybe you should first use something like:
apt update
apt upgrade

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

Title:
  pcscd won't install due to bad dependency version

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  # apt install pcscd
  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:
   pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed
   qemu-block-extra : Depends: qemu-system-x86 (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-arm (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-mips (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-ppc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-sparc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-misc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-s390x (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-x86-xen (= 1:6.0+dfsg-2expubuntu1) 
but it is not going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pcscd (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Oct  6 17:15:29 2021
  InstallationDate: Installed on 2020-06-16 (477 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to impish on 2021-10-06 (0 days ago)

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


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

[Touch-packages] [Bug 1946235] Re: pcscd won't install due to bad dependency version

[Paul White]

** Package changed: ubuntu => pcsc-lite (Ubuntu)

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

Title:
  pcscd won't install due to bad dependency version

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  # apt install pcscd
  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:
   pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed
   qemu-block-extra : Depends: qemu-system-x86 (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-arm (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-mips (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-ppc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-sparc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-misc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-s390x (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
   qemu-system-x86-xen (= 1:6.0+dfsg-2expubuntu1) 
but it is not going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pcscd (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Oct  6 17:15:29 2021
  InstallationDate: Installed on 2020-06-16 (477 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to impish on 2021-10-06 (0 days ago)

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


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

[Touch-packages] [Bug 1946235] [NEW] pcscd won't install due to bad dependency version

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

# apt install pcscd
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:
 pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed
 qemu-block-extra : Depends: qemu-system-x86 (= 1:6.0+dfsg-2expubuntu1) but it 
is not going to be installed or
 qemu-system-arm (= 1:6.0+dfsg-2expubuntu1) but it 
is not going to be installed or
 qemu-system-mips (= 1:6.0+dfsg-2expubuntu1) but it 
is not going to be installed or
 qemu-system-ppc (= 1:6.0+dfsg-2expubuntu1) but it 
is not going to be installed or
 qemu-system-sparc (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
 qemu-system-misc (= 1:6.0+dfsg-2expubuntu1) but it 
is not going to be installed or
 qemu-system-s390x (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed or
 qemu-system-x86-xen (= 1:6.0+dfsg-2expubuntu1) but 
it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: pcscd (not installed)
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed Oct  6 17:15:29 2021
InstallationDate: Installed on 2020-06-16 (477 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: pcsc-lite
UpgradeStatus: Upgraded to impish on 2021-10-06 (0 days ago)

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish
-- 
pcscd won't install due to bad dependency version
https://bugs.launchpad.net/bugs/1946235
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pcsc-lite 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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Sergio Durigan Junior]

** Changed in: clamav (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1946153] Re: [Lenovo ThinkPad P1 Gen 2, Conexant CX8070, Speaker, Internal] No sound at all

[Richard Albright]

that worked

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

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

Title:
  [Lenovo ThinkPad P1 Gen 2, Conexant CX8070, Speaker, Internal] No
  sound at all

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  laptop is connected to a thinkpad thunderbolt 3 dock, sound worked
  while connect until the latest update a few days ago on 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Oct  5 16:22:29 2021
  InstallationDate: Installed on 2019-10-18 (717 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [20QTCTO1WW, Conexant CX8070, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET47W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QTCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET47W(1.34):bd08/06/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 2
  dmi.product.name: 20QTCTO1WW
  dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2
  dmi.product.version: ThinkPad P1 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 1945817] Re: Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

[Gunnar Hjalmarsson]

** Changed in: language-selector (Ubuntu)
   Status: In Progress => Fix Committed

** No longer affects: 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/1945817

Title:
  Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic

Status in language-selector package in Ubuntu:
  Fix Committed

Bug description:
  Description of problem:

  Abyssinica SIL is an old font. It's barely legible and breaks in most
  apps. Noto Serif Ethiopic, on the other hand, is a modern and well
  designed font.

  Noto Serif Ethiopic is distributed with the Open Font License, so
  packaging it won't be a problem.

  Link
  
https://fonts.google.com/noto/specimen/Noto+Serif+Ethiopic?noto.query=Amharic¬o.script=Ethi

  Version: 20.04.3

  How reproducible:
  always

  Steps to Reproduce:
  1. Pretty much using the the Amharic language anywhere on Ubuntu

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


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

[Touch-packages] [Bug 1922464] Re: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

[Mattia Rizzolo]

@seb128: would you take care of uploading that patch, or should somebody
else do it?

I'm not a core-dev, so I would still need a sponsor for the actual
upload (though I have them already), so if you have the tuits it might
just be quicker/easier if you could do it ^^

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

Title:
  GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-
  daemon.plugins.xsettings' does not contain a key named 'antialiasing'

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Focal:
  Triaged

Bug description:
  Applications running with GTK < 3.24.26 crash when running under GNOME
  40. This was fixed in GTK 3.24.26 by MR
  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3219

  Please package either current GTK 3 (3.24.28) or include the given MR
  in the current build.

  Thanks!

  Example crash:

  ```
  Starting program: /home/mjog/Projects/GNOME/geary/+build/test/test-client
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffeb8a7640 (LWP 58239)]
  [New Thread 0x7fffeb086640 (LWP 58240)]
  [New Thread 0x7fffea839640 (LWP 58241)]

  (test-client:58235): GLib-GIO-ERROR **: 10:42:55.448: Settings schema
  'org.gnome.settings-daemon.plugins.xsettings' does not contain a key
  named 'antialiasing'

  Thread 1 "test-client" received signal SIGTRAP, Trace/breakpoint trap.
  0x774a5ea7 in g_log_structured_array () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) bt
  #0  0x774a5ea7 in g_log_structured_array ()
  at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x774a62b9 in g_log_default_handler () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x774a64fe in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x774a67b3 in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x7735d9d1 in  () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  #5  0x7735e030 in  () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  #6  0x773625d1 in g_settings_get_enum () at 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #7  0x710d90ea in update_xft_settings (screen=0x55a8d810)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:404
  #8  0x710d3c7d in init_settings (screen=0x55a8d810)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:828
  #9  _gdk_wayland_screen_new (display=0x55a8a0e0)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:1320
  #10 _gdk_wayland_display_open (display_name=)
  at wayland/../../../../../gdk/wayland/gdkdisplay-wayland.c:617
  #11 0x71072635 in gdk_display_manager_open_display
  (manager=, name=0x0) at 
../../../../gdk/gdkdisplaymanager.c:462
  #12 0x76d011fb in gtk_init_check (argc=, 
argv=)
  at ../../../../gtk/gtkmain.c:1110
  #13 gtk_init_check (argc=, argv=)
  at ../../../../gtk/gtkmain.c:1102
  #14 0x76d0122d in gtk_init (argc=, argv=)
  at ../../../../gtk/gtkmain.c:1167
  #15 0x555b4854 in _vala_main (args=0x7fffdda8, args_length1=1)
  at ../test/test-client.vala:32
  #16 0x555b5213 in main (argc=1, argv=0x7fffdda8) at 
../test/test-client.vala:9
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libgtk-3-0 3.24.25-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun Apr  4 11:11:05 2021
  InstallationDate: Installed on 2018-08-13 (964 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to hirsute on 2021-04-03 (0 days ago)

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


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

[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Ian Johnson]

Also I'm not sure I agree with jdstrand's apparmor profile which
includes:

/run/snapd.socket rw,

which I don't think we want to grant to any PDF file opened with evince?

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Triaged

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

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


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

[Touch-packages] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid

[Athos Ribeiro]

Setting series as wontfix due to end of standard support. This should be
fixed from bionic and on.

** Changed in: openssh (Ubuntu Precise)
   Status: New => Won't Fix

** Changed in: openssh (Ubuntu Trusty)
   Status: New => Won't Fix

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

Title:
  openssh tests use "not valid yet" certificate from 2020, which is now
  valid

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Precise:
  Won't Fix
Status in openssh source package in Trusty:
  Won't Fix
Status in openssh source package in Xenial:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in openssh source package in Disco:
  Won't Fix
Status in openssh source package in Eoan:
  Fix Released
Status in openssh source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * regression testsuite uses 1st of January 2020 as the date in the
  future, however that is now in the past making autpkgtests fail.

  [Test Case]

   * Autopkgtest must pass

  [Regression Potential]

   * Testsuite assertion update only

  [Other Info]

  This is a staged update to be rolled up with any other openssh update
  in the future.

  fixed in debian https://tracker.debian.org/news/1092767/accepted-
  openssh-181p1-4-source-into-unstable/

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


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

[Touch-packages] [Bug 1944741] Re: HiFive Unmatched partitions are named "Unleashed"

[Alexandre Ghiti]

** Tags added: fr-1786

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

Title:
  HiFive Unmatched partitions are named "Unleashed"

Status in util-linux package in Ubuntu:
  New
Status in util-linux package in Debian:
  Confirmed

Bug description:
  Both HiFive Unleashed and HiFive Unmatched bootloaders seek for the same
  UUIDs to load the next stage bootloader: the current name makes partitions
  on Unmatched board appear as 'Unleashed'.
  
  Fix that by removing the 'Unleashed' part of the current name so that it
  fits both.

  The attached debdiff contains the patch that was merged upstream
  (https://github.com/karelzak/util-
  linux/commit/10fd91d389497d8be435cc66abbdeb2eb6ea2f07).

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


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

[Touch-packages] [Bug 1785383] Re: missing EDNS0 record confuses systemd-resolved

[Paride Legovini]

The MP got reviewed and the dnsmasq upload is currently waiting in the
Bionic unapproved queue.

Being a format 1.0 package the diff [1] looks huge at first glance, but
the real changes are actually very limited (those in the MP).

[1]
https://launchpadlibrarian.net/560828569/dnsmasq_2.79-1ubuntu0.5.diff.gz

** Merge proposal linked:
   
https://code.launchpad.net/~paride/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/409149

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

Title:
  missing EDNS0 record confuses systemd-resolved

Status in systemd:
  Fix Released
Status in dnsmasq package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in dnsmasq source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in dnsmasq source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released
Status in dnsmasq source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in dnsmasq source package in Impish:
  Fix Released
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]

  dnsmasq 2.79 and below omits EDNS0 OPT records [1] when returning an
  empty answer for a domain it is authoritative for. systemd-resolved
  seems to get confused by this in certain circumstances; when using the
  stub resolver and requesting an address for which there are no 
  records, there can sometimes be a five second hang in resolution.

  [1] https://en.wikipedia.org/wiki/Extension_Mechanisms_for_DNS

  [Test Plan]

  Test case for bionic:

  -
  IFACE=dummy0
  SUBNET=10.0.0

  ip link add $IFACE type dummy
  ifconfig $IFACE ${SUBNET}.1/24
  dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo 
--host-record=test.test,${SUBNET}.1 --server=/test/ &

  dig -t a test.test @10.0.0.1 | grep EDNS
  # returns "; EDNS ..."
  dig -t  test.test @10.0.0.1 | grep EDNS
  # again, should return "; EDNS ..." but doesn't.
  # does so with the -proposed package.
  -

  [Where problems could occur]

  Problems may occur in case a client queries dnsmasq and relies on
  EDNS0 not being available for behaving correctly. This covers cases
  where the software querying dnsmasq is buggy or misconfigured.

  [Development Fix]

  Fixed upstream in dnsmasq >= 2.80.

  [Stable Fix]

  Partial cherry-pick of upstream commit
  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78

  The cherry-pick is partial because half if it is already in the
  package .diff we have in Bionic.

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


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

[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Launchpad Bug Tracker]

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

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

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Triaged

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

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


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

[Touch-packages] [Bug 1946153] Re: [Lenovo ThinkPad P1 Gen 2, Conexant CX8070, Speaker, Internal] No sound at all

[Hui Wang]

you could have a try with '$rm ~/.config/pulse/*;reboot'.

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

Title:
  [Lenovo ThinkPad P1 Gen 2, Conexant CX8070, Speaker, Internal] No
  sound at all

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  laptop is connected to a thinkpad thunderbolt 3 dock, sound worked
  while connect until the latest update a few days ago on 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Oct  5 16:22:29 2021
  InstallationDate: Installed on 2019-10-18 (717 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [20QTCTO1WW, Conexant CX8070, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET47W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QTCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET47W(1.34):bd08/06/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 2
  dmi.product.name: 20QTCTO1WW
  dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2
  dmi.product.version: ThinkPad P1 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 1945787] Re: heimdal: fails to build, symbols don't match

[Launchpad Bug Tracker]

This bug was fixed in the package heimdal - 7.7.0+dfsg-2ubuntu2

---
heimdal (7.7.0+dfsg-2ubuntu2) impish; urgency=medium

  * Remove symbol rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226
(LP: #1945787)

 -- Heinrich Schuchardt   Fri, 01 Oct
2021 15:03:02 +0200

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

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

Title:
  heimdal: fails to build, symbols don't match

Status in heimdal package in Ubuntu:
  Fix Released

Bug description:
  heimdal 7.7.0+dfsg-2ubuntu1 fails to build with

  dpkg-gensymbols: warning: debian/libroken18-heimdal/DEBIAN/symbols doesn't 
match completely debian/libroken18-heimdal.symbols
  --- debian/libroken18-heimdal.symbols 
(libroken18-heimdal_7.7.0+dfsg-2ubuntu1_riscv64)
  +++ dpkg-gensymbolsYtlvSr   2021-10-01 12:31:59.102451503 +
  @@ -42,7 +42,7 @@
rk_cloexec_dir@HEIMDAL_ROKEN_1.0 1.4.0+git20110226
rk_cloexec_file@HEIMDAL_ROKEN_1.0 1.4.0+git20110226
rk_cloexec_socket@HEIMDAL_ROKEN_1.0 1.6~git20131117
  - rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226
  +#MISSING: 7.7.0+dfsg-2ubuntu1# rk_closefrom@HEIMDAL_ROKEN_1.0 
1.4.0+git20110226
rk_copyhostent@HEIMDAL_ROKEN_1.0 1.4.0+git20110226
rk_dns_free_data@HEIMDAL_ROKEN_1.0 1.4.0+git20110226
rk_dns_lookup@HEIMDAL_ROKEN_1.0 1.4.0+git20110226
  dh_makeshlibs: error: failing due to earlier errors

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


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

[Touch-packages] [Bug 1891799] Re: upowerd: did not recognise USB path

[Launchpad Bug Tracker]

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

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

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

Title:
  upowerd: did not recognise USB path

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  From my jouranlctl

  upowerd[1045]: did not recognise USB path
  /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy-
  USBC000:001, please report

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: upower 0.99.11-1build2
  Uname: Linux 5.8.0-050800-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Sun Aug 16 13:41:47 2020
  InstallationDate: Installed on 2020-05-11 (96 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1458336] Re: Allow users to decide which apps can display anything in the circle

[Rüdiger Kupper]

Addition to #5: Fluffychat seems to have solved how to do that: once in
a while it slips in reminders as a circle message and this message
always appears first after boot.

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

Title:
  Allow users to decide which apps can display anything in the circle

Status in Canonical System Image:
  New
Status in libusermetrics package in Ubuntu:
  Confirmed

Bug description:
  Currently a user has no control over which apps can display stuff in
  the circle. Potentially an app could show there something what a user
  do not want. It would be nice to have for example setting (like for
  notifications) which apps are allowed to use the circle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1458336/+subscriptions


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

[Touch-packages] [Bug 1946153] Re: [Lenovo ThinkPad P1 Gen 2, Conexant CX8070, Speaker, Internal] No sound at all

[Richard Albright]

so it seems this is a partial fix, system sounds are still broken, and
the gnome speaker test is still broken, but sound is working for
specific applications.  sound will work for chromium and firefox,
testing with "speaker-test -t wav -c"  also results in no sound. this
shows up as "alsa plugin speaker test" in gnome. leading me to believe
this might be something with alsa under the hood

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

Title:
  [Lenovo ThinkPad P1 Gen 2, Conexant CX8070, Speaker, Internal] No
  sound at all

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  laptop is connected to a thinkpad thunderbolt 3 dock, sound worked
  while connect until the latest update a few days ago on 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Oct  5 16:22:29 2021
  InstallationDate: Installed on 2019-10-18 (717 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [20QTCTO1WW, Conexant CX8070, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET47W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QTCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET47W(1.34):bd08/06/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 2
  dmi.product.name: 20QTCTO1WW
  dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2
  dmi.product.version: ThinkPad P1 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault

[cptX]

Hi,
I can confirm that after upgrading ubuntu 18.04 to 20.04.03 when certbot tried 
to reload the nginx it had issues. After disabling the file 
50-mod-http-perl.conf to 50-mod-http-perl.conf_bak the issue was solved!!

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

Title:
  libperl.so.5.30.0 causes nginx to segfault

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  [Steps to reproduce]

  1) launch a focal container
  $ lxc launch images:ubuntu/focal focal-1897561
  2) enter the container
  $ lxc shell focal-1897561
  3) install libnginx-mod-http-perl
  # apt-get install -y nginx-core libnginx-mod-http-perl
  4) check nginx journal
  # journalctl -fu nginx &
  5) reload nginx 2-3 times
  # systemctl reload nginx

  Eventually you will see this from the journal:

  Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web 
server and a reverse proxy server.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, 
code=dumped, status=11/SEGV
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 
(nginx) with signal SIGKILL.
  Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Failed with result 
'core-dump'.

  [Workaround]

  If libnginx-mod-http-perl is not needed, purging it and restarting
  nginx sidesteps the problem.

  [Original bug description]

  Ubuntu 20.04 LTS

  Looks that Perl 5.30 has bug that causes nginx to die, usually occurs
  after "service nginx reload"

  This looks like nginx, but it really is perl issue:
  https://github.com/Perl/perl5/issues/17154

  Fix done in 5.32 (Perl5 commit bf0) and people are asking backport
  to 5.30 to get fix also to nginx.

  Error:
  Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 
ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in 
libperl.so.5.30.0[7fbf321a5000+166000]

  Symptom: Nginx terminates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Package: perl 5.30.0-9build1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal uec-images
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

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


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

[Touch-packages] [Bug 1946153] Re: [Lenovo ThinkPad P1 Gen 2, Conexant CX8070, Speaker, Internal] No sound at all

[Richard Albright]

performed the above upgrade, it did not resolve the issue

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

Title:
  [Lenovo ThinkPad P1 Gen 2, Conexant CX8070, Speaker, Internal] No
  sound at all

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  laptop is connected to a thinkpad thunderbolt 3 dock, sound worked
  while connect until the latest update a few days ago on 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Oct  5 16:22:29 2021
  InstallationDate: Installed on 2019-10-18 (717 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [20QTCTO1WW, Conexant CX8070, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET47W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QTCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET47W(1.34):bd08/06/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P1 Gen 2
  dmi.product.name: 20QTCTO1WW
  dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2
  dmi.product.version: ThinkPad P1 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 1946196] Re: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)

[Sebastien Bacher]

The packagekit error could have been bug #1943189 , could you try if
that's still an issue?

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

Title:
  Additional Drivers fails with pk-client-error-quark: Cannot download
  packages whilst offline (257)

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Additional Drivers fails to install nvidia-driver-470:

Error while applying changes

pk-client-error-quark: Cannot download packages whilst offline (257)

  But the machine is ONLINE with full Internet access.

  WORKAROUND:

  sudo apt install nvidia-driver-470

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


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

[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Olivier Tilloy]

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

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  New
Status in evince package in Ubuntu:
  Triaged

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

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


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

[Touch-packages] [Bug 1945887] Re: org.bluez.obex.service contains unresolved '@libexecdir@'

[Daniel van Vugt]

It will be fixed in 22.04 at least:
https://git.launchpad.net/~bluetooth/bluez/commit/?h=ubuntu-
next&id=355b9c9e65f0c381aa606b9ce603f4ec70f8dc49

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

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  org.bluez.obex.service contains unresolved '@libexecdir@'

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  After upgrading a machine from Ubuntu Bionic to Ubuntu Focal
  yesterday, the following error message showed up in the syslog:

  Oct  2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760]
  Activated service 'org.bluez.obex' failed: Failed to execute program
  org.bluez.obex: No such file or directory

  Upon inspection, this was due to the fact that the service definition
  contained the line 'Exec=@libexecdir@/obexd' which could not be
  resolved (this placeholder is supposedly to be replaced at build
  time).

  Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this
  (together with 'systemctl --user daemon-reload; systemctl --user
  restart obex').

  Note that this problem should be part of *all* current versions of the
  bluez[-obexd] package, regardless of the used architecture (including
  Focal, Impish):

  % wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb
  [...]
  Länge: 217906 (213K) [application/x-debian-package]
  Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert.
  [...]
  2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« 
gespeichert [217906/217906]

  % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish
  % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service
  Exec=@libexecdir@/obexd
  % wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb
  [...]
  Länge: 160832 (157K) [application/x-debian-package]
  Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert.
  [...]
  2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« 
gespeichert [160832/160832]

  % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal
  % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service
  Exec=@libexecdir@/obexd
  %

  
  # lsb_release -rd
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  # apt-cache policy bluez-obexd
  bluez-obexd:
  [...]
   5.53-0ubuntu3.3 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  [...]

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


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

[Touch-packages] [Bug 1873920] Re: default vi on focal emits escape sequences unrecognized by bionic's terminal?

[Olivier Godart]

Hi, does somebody have a workaround? Something to add/remove in the
system vimrc config file?

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

Title:
  default vi on focal emits escape sequences unrecognized by bionic's
  terminal?

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  On ubuntu 18.04, opening the default terminal (gnome-terminal
  3.28.2-1ubuntu1~18.04.1), ssh'ing to an up-to-date ubuntu 20.04
  system, running 'vi', and pressing 'i' shows the unwelcome garbage ESC
  [>4;m.  Pressing ESC emits more garbage: ESC [>4;2m

  Focal's default vi is provided by vim.tiny via alternatives.  Oddly,
  when running vim.tiny by itself, or if you install vim and let it
  provide vi, the garbage does not appear.

  Evidently focal's vim.tiny is confused about what escape sequences
  ubu1804's Terminal accepts.

  TERM is xterm-256color.  The problem also occurs if TERM is xterm.

  There is no .vimrc.

  If I use xterm on ubuntu 18.04, all is well.  Evidently xterm accepts
  ESC[>4;m and gnome-terminal doesn't?

  I captured a session using 'script' and dumped typescript via hexdump -C. 
  In this session, I typed i, Q, and escape. Here's an excerpt
  showing the end of vi's welcome message, followed by five escape sequences
  and then the Q I typed.  The unrecognized ESC > 4;m is visible in the dump,
  followed by ESC[?25l (CURSOR OFF)

  1070  66 61 75 6c 74 1b 5b 33  34 6d 3c 45 6e 74 65 72  |fault.[34m.[m for info on|
  1090  20 74 68 69 73 1b 5b 31  3b 31 48 1b 5b 3f 32 35  | this.[1;1H.[?25|
  10a0  68 1b 5b 3f 32 30 30 34  6c 1b 5b 3e 34 3b 6d 1b  |h.[?2004l.[>4;m.|
  10b0  5b 3f 32 35 6c 51 1b 5b  38 3b 34 37 48 1b 5b 31  |[?25lQ.[8;47H.[1|

  The mystery sequence ESC [ > 4;m appears to be "Set/reset key modifier 
options, xterm",
  per https://invisible-island.net/xterm/ctlseqs/ctlseqs.html.  So it's trying
  to modify function keys, or something.

  ssh'ing in from a mac worked fine (TERM there was also xterm-256color),
  as did ssh'ing from an ubuntu 19.04 system with gnome-terminal.
  ssh'ing from another ubuntu 18.04 system exhibited the same problem.

  So it's a little family squabble between focal's vim.tiny and ubuntu
  18.04/bionic's gnome-terminal...?

  Given how long 18.04's going to be supported, this seems worth
  resolving somehow.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: vim-tiny 2:8.1.2269-1ubuntu5 [modified: 
usr/share/vim/vim81/doc/help.txt usr/share/vim/vim81/doc/tags]
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Apr 20 09:27:50 2020
  InstallationDate: Installed on 2020-01-27 (83 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1945527] Re: Update tzdata to version 2021a-2

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2021a-2ubuntu0.18.04

---
tzdata (2021a-2ubuntu0.18.04) bionic; urgency=medium

  * Merge from Debian unstable (LP: #1945527). Remaining changes:
- Restore old SystemV timezones.

 -- Brian Murray   Wed, 29 Sep 2021 12:14:22 -0700

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

Title:
  Update tzdata to version 2021a-2

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Hirsute:
  Fix Released

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Pacific/Apia

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

  [Test Case for all releases]
  1) zdump -v Pacific/Apia | grep 2021

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Pacific/Apia')); 
print(str(tz.utcoffset(datetime(2021, 9, 27'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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


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

[Touch-packages] [Bug 1945527] Re: Update tzdata to version 2021a-2

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2021a-2ubuntu0.21.04

---
tzdata (2021a-2ubuntu0.21.04) hirsute; urgency=medium

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

 -- Brian Murray   Wed, 29 Sep 2021 12:14:22 -0700

** Changed in: tzdata (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  Update tzdata to version 2021a-2

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Hirsute:
  Fix Released

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Pacific/Apia

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

  [Test Case for all releases]
  1) zdump -v Pacific/Apia | grep 2021

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Pacific/Apia')); 
print(str(tz.utcoffset(datetime(2021, 9, 27'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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


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

[Touch-packages] [Bug 1945527] Re: Update tzdata to version 2021a-2

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2021a-2ubuntu0.20.04

---
tzdata (2021a-2ubuntu0.20.04) focal; urgency=medium

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

 -- Brian Murray   Wed, 29 Sep 2021 12:14:22 -0700

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

** Changed in: tzdata (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Update tzdata to version 2021a-2

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Hirsute:
  Fix Released

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Pacific/Apia

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

  [Test Case for all releases]
  1) zdump -v Pacific/Apia | grep 2021

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Pacific/Apia')); 
print(str(tz.utcoffset(datetime(2021, 9, 27'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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


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

[Touch-packages] [Bug 1945527] Update Released

[Łukasz Zemczak]

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

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

Title:
  Update tzdata to version 2021a-2

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Hirsute:
  Fix Released

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Pacific/Apia

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

  [Test Case for all releases]
  1) zdump -v Pacific/Apia | grep 2021

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Pacific/Apia')); 
print(str(tz.utcoffset(datetime(2021, 9, 27'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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


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

[Touch-packages] [Bug 1946209] Re: evolution-alarm-notify crashed with signal 5 in _XEventsQueued()

[Document02]

I could reproduce the crash at will.

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

Title:
  evolution-alarm-notify crashed with signal 5 in _XEventsQueued()

Status in evolution-data-server package in Ubuntu:
  Incomplete

Bug description:
  Crashes when going to system setting /  Graphic tablet  / manually
  register a tablet / select Multi-device tablet pen sensor => crash

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: evolution-data-server 3.40.4-1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: KDE
  Date: Wed Oct  6 10:32:24 2021
  ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify
  ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify
  Signal: 5
  SourcePackage: evolution-data-server
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to impish on 2021-10-03 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo uinput
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1946209/+subscriptions


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

[Touch-packages] [Bug 1946209] Re: evolution-alarm-notify crashed with signal 5 in _XEventsQueued()

[Sebastien Bacher]

Thank you for your bug report. Do you get the issue every time you do
those steps or was it a one time bug?

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

** Information type changed from Private to Public

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

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

Title:
  evolution-alarm-notify crashed with signal 5 in _XEventsQueued()

Status in evolution-data-server package in Ubuntu:
  Incomplete

Bug description:
  Crashes when going to system setting /  Graphic tablet  / manually
  register a tablet / select Multi-device tablet pen sensor => crash

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: evolution-data-server 3.40.4-1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: KDE
  Date: Wed Oct  6 10:32:24 2021
  ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify
  ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify
  Signal: 5
  SourcePackage: evolution-data-server
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to impish on 2021-10-03 (3 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo uinput
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1946209/+subscriptions


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

[Touch-packages] [Bug 1922464] Re: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

[Sebastien Bacher]

snaps build is a valid reason indeed, thank you Ted!

** Changed in: gtk+3.0 (Ubuntu Focal)
   Status: Incomplete => Triaged

** Changed in: gtk+3.0 (Ubuntu Focal)
   Importance: Wishlist => High

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

Title:
  GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-
  daemon.plugins.xsettings' does not contain a key named 'antialiasing'

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Focal:
  Triaged

Bug description:
  Applications running with GTK < 3.24.26 crash when running under GNOME
  40. This was fixed in GTK 3.24.26 by MR
  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3219

  Please package either current GTK 3 (3.24.28) or include the given MR
  in the current build.

  Thanks!

  Example crash:

  ```
  Starting program: /home/mjog/Projects/GNOME/geary/+build/test/test-client
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffeb8a7640 (LWP 58239)]
  [New Thread 0x7fffeb086640 (LWP 58240)]
  [New Thread 0x7fffea839640 (LWP 58241)]

  (test-client:58235): GLib-GIO-ERROR **: 10:42:55.448: Settings schema
  'org.gnome.settings-daemon.plugins.xsettings' does not contain a key
  named 'antialiasing'

  Thread 1 "test-client" received signal SIGTRAP, Trace/breakpoint trap.
  0x774a5ea7 in g_log_structured_array () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) bt
  #0  0x774a5ea7 in g_log_structured_array ()
  at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x774a62b9 in g_log_default_handler () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x774a64fe in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x774a67b3 in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x7735d9d1 in  () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  #5  0x7735e030 in  () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  #6  0x773625d1 in g_settings_get_enum () at 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #7  0x710d90ea in update_xft_settings (screen=0x55a8d810)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:404
  #8  0x710d3c7d in init_settings (screen=0x55a8d810)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:828
  #9  _gdk_wayland_screen_new (display=0x55a8a0e0)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:1320
  #10 _gdk_wayland_display_open (display_name=)
  at wayland/../../../../../gdk/wayland/gdkdisplay-wayland.c:617
  #11 0x71072635 in gdk_display_manager_open_display
  (manager=, name=0x0) at 
../../../../gdk/gdkdisplaymanager.c:462
  #12 0x76d011fb in gtk_init_check (argc=, 
argv=)
  at ../../../../gtk/gtkmain.c:1110
  #13 gtk_init_check (argc=, argv=)
  at ../../../../gtk/gtkmain.c:1102
  #14 0x76d0122d in gtk_init (argc=, argv=)
  at ../../../../gtk/gtkmain.c:1167
  #15 0x555b4854 in _vala_main (args=0x7fffdda8, args_length1=1)
  at ../test/test-client.vala:32
  #16 0x555b5213 in main (argc=1, argv=0x7fffdda8) at 
../test/test-client.vala:9
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libgtk-3-0 3.24.25-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun Apr  4 11:11:05 2021
  InstallationDate: Installed on 2018-08-13 (964 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to hirsute on 2021-04-03 (0 days ago)

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


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

[Touch-packages] [Bug 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.

[Jerry Lee]

The .debdiff file “modemmanager_1-1.16.6-3-impish.debdiff” is attached
for impish(22.04).

The pre-built package :  https://launchpad.net/~jerry-lee-
tpe/+archive/ubuntu/packages/+packages

** Patch added: "modemmanager_1-1.16.6-3-impish.debdiff"
   
https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5531015/+files/modemmanager_1-1.16.6-3-impish.debdiff

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

Title:
  Apply upstream patches to fix problems for Foxconn and Quectel modems.

Status in OEM Priority Project:
  New
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  The following 2 modems need the ModemManager v1.16.6 suite to be patched from 
v1.18.2 to fix some problems(LP#1943774, LP#1943780):
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 

  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
 
  * for Foxconn T99W175
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9

**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154
 

  
  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  4. Using the firmware upgrading application to upgrade the modem’s firmware 
  5. Verify if the modem’s firmware upgrading is successful
  6. Reboot 
  7. Verify if the upgraded modem firmware is still working

  
  [Where problems could occur]

  The requested upstream patches are for these 2 specific modems and the status 
information.
  This should not affect existing generic functions and other modems.

  
  [Other Info]

  The firmware and the upgrading application can be downloaded from the 
following link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions


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

[Touch-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

[Daniel van Vugt]

Can someone please retest on Ubuntu 21.10?

http://cdimage.ubuntu.com/daily-live/current/

** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
   Status: Confirmed => Won't Fix

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

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

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: New => Incomplete

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

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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


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

[Touch-packages] [Bug 1946196] [NEW] Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)

[Daniel van Vugt]

Public bug reported:

Additional Drivers fails to install nvidia-driver-470:

  Error while applying changes

  pk-client-error-quark: Cannot download packages whilst offline (257)

But the machine is ONLINE with full Internet access.

WORKAROUND:

sudo apt install nvidia-driver-470

** Affects: software-properties (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: impish nvidia

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

Title:
  Additional Drivers fails with pk-client-error-quark: Cannot download
  packages whilst offline (257)

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Additional Drivers fails to install nvidia-driver-470:

Error while applying changes

pk-client-error-quark: Cannot download packages whilst offline (257)

  But the machine is ONLINE with full Internet access.

  WORKAROUND:

  sudo apt install nvidia-driver-470

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


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

[Touch-packages] [Bug 1942208] Re: The nvidia-dkms will be installed when installing nvidia driver through "Additional Drivers"

[Daniel van Vugt]

** Tags added: focal

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

Title:
  The nvidia-dkms will be installed when installing nvidia driver
  through "Additional Drivers"

Status in OEM Priority Project:
  Confirmed
Status in software-properties package in Ubuntu:
  New

Bug description:
  [steps to reproduce]
  1. Install Stock ubuntu 20.04.3 on XPS 15 9510
  2. Installing without using "Third-party packages"
  3. After installation completed, launch "Software & Updates" -> "Additional 
Drivers" -> "Using NVIDIA driver  470"
  4. dpkg -l | grep nvidia

  [Expected result]
  It should use pre-signed nvidia driver instead of dkms
  e.g. 
  linux-modules-nvidia-470-5.11.0-27-generic
  linux-modules-nvidia-470-generic-hwe-20.04
  linux-objects-nvidia-470-5.11.0-27-generic
  linux-signatures-nvidia-5.11.0-27-generic

  [Actual result]
  ii  nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 amd64 NVIDIA DKMS package

  ---

  $ lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  $ apt-cache policy software-properties-*
  software-properties-gtk:
Installed: 0.98.9.5
Candidate: 0.98.9.5
Version table:
   *** 0.98.9.5 500
  500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.98.9.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main i386 
Packages
   0.98.9 500
  500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://tw.archive.ubuntu.com/ubuntu focal/main i386 Packages
  software-properties-kde:
Installed: (none)
Candidate: (none)
Version table:
  software-properties-qt:
Installed: (none)
Candidate: 0.98.9.5
Version table:
   0.98.9.5 500
  500 http://tw.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
  500 http://tw.archive.ubuntu.com/ubuntu focal-updates/universe i386 
Packages
   0.98.9.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/universe i386 
Packages
   0.98.9 500
  500 http://tw.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  500 http://tw.archive.ubuntu.com/ubuntu focal/universe i386 Packages
  software-properties-common:
Installed: 0.98.9.5
Candidate: 0.98.9.5
Version table:
   *** 0.98.9.5 500
  500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.98.9.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main i386 
Packages
   0.98.9 500
  500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://tw.archive.ubuntu.com/ubuntu focal/main i386 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942208/+subscriptions


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

[Touch-packages] [Bug 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.

[Sebastien Bacher]

would you have an update for impish, that's where we should start

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

Title:
  Apply upstream patches to fix problems for Foxconn and Quectel modems.

Status in OEM Priority Project:
  New
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  The following 2 modems need the ModemManager v1.16.6 suite to be patched from 
v1.18.2 to fix some problems(LP#1943774, LP#1943780):
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 

  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
 
  * for Foxconn T99W175
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9

**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154
 

  
  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  4. Using the firmware upgrading application to upgrade the modem’s firmware 
  5. Verify if the modem’s firmware upgrading is successful
  6. Reboot 
  7. Verify if the upgraded modem firmware is still working

  
  [Where problems could occur]

  The requested upstream patches are for these 2 specific modems and the status 
information.
  This should not affect existing generic functions and other modems.

  
  [Other Info]

  The firmware and the upgrading application can be downloaded from the 
following link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions


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