[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Khaled El Mously]

Hi @Eric - thanks for the follow-up and sorry for the delayed reply.

> I don't see this piece of code in the klibc upstream project[0]

Are you referring to the piece of code that I am suggesting as a fix? If
so, it makes sense that it doesn't exist elsewhere, which is why I am
suggesting it be incorporated into klibc. I have checked upstream klibc
2.0.4 which is the version that Bionic uses and it applies cleanly
there.

I am not sure that it would help us to get the fix upstreamed in a new
version of klibc since the problem is only affecting Bionic, and Bionic
uses klibc 2.0.4 + some Ubuntu changes. I assumed we can just add the
additional fix as another Ubuntu-specific change on top ?

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

Title:
  ipconfig does not honour user-requested timeouts in some cases

Status in klibc package in Ubuntu:
  New
Status in klibc source package in Bionic:
  New

Bug description:
  ** SRU TEMPLATE DRAFT **

  [Impact]

  
  [Test Plan]

  
  [Where problems could occur]

  
  [Other Info]

  
  [Original Description]

  In some cases, ipconfig can take longer than the user-specified
  timeouts, causing unexpected delays.

  in main.c, in function loop(), the process can go into
  process_timeout_event() (or process_receive_event() ) and if it
  encounters an error situation, will set an attempt to "try again
  later" at time equal now + 10 seconds by setting

  s->expire = now + 10;

  This can happen at any time during the main event loop, which can end
  up extending the user-specified timeout if "now + 10" is greater than
  "start_time + user-specified-timeout".

  I believe a patch like the following is needed to avoid this problem:

  --- a/usr/kinit/ipconfig/main.c
  +++ b/usr/kinit/ipconfig/main.c
  @@ -437,6 +437,13 @@ static int loop(void)

  if (timeout > s->expire - now.tv_sec)
  timeout = s->expire - now.tv_sec;
  +
  +   /* Compensate for already-lost time */
  +   gettimeofday(&now, NULL);
  +   if (now.tv_sec + timeout > start + loop_timeout) {
  +   timeout = loop_timeout - (now.tv_sec - start);
  +   printf("Lowered timeout to match user request 
= (%d s) \n", timeout);
  +   }
  }

  I believe the current behaviour is buggy. This is confirmed when the
  following line is executed:

  if (loop_timeout >= 0 &&
  now.tv_sec - start >= loop_timeout) {
  printf("IP-Config: no response after %d "
     "secs - giving up\n", loop_timeout);
  rc = -1;
  goto bail;
  }

  'loop_timeout' is the user-specified time-out. With a value of 2, in
  case of error, this line prints:

  IP-Config: no response after 2 secs - giving up

  So it thinks that it waited 2 seconds - however, in reality it had
  actually waited for 10 seconds.

  The suggested code-change ensures that the timeout that is actually
  used never exceeds the user-specified timeout.

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


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

[Touch-packages] [Bug 1951214] Re: ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets data

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1951214

** Tags added: iso-testing

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

Title:
  ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets
  data

Status in apport package in Ubuntu:
  New

Bug description:
  This has been reported before on Ubuntu Community Hub, but I want/need
  a bug report filed on launchpad to report/track on iso.qa.ubuntu.com

  On a `ubuntu-bug` or apport opening up a bug report; a gedit window
  opens with

  ---
  
  
OpenID transaction in progress
  
  
  https://login.launchpad.net/+openid"; method="post" 
accept-charset="UTF-8" enctype="application/x-www-form-urlencoded">http://openid.net/extensions/sreg/1.1"/>https://launchpad.net/+openid-callback?starting_url=https%3A%2F%2Fbugs.launchpad.net%2Fsubiquity%2F%2Bfilebug%2Ff55a6274-4767-11ec-a1ce-d485646cd9a4%3Ffield.title%3Dinstall%2Bfailed%2Bcrashed%2Bwith%2BCalledProcessError&janrain_nonce=2021-11-17T05%3A34%3A05Zo24b46"/>https://launchpad.net/"/>http://specs.openid.net/auth/2.0/identifier_select"/>http://specs.openid.net/auth/2.0"/>http://specs.openid.net/auth/2.0/identifier_select"/>
  
  var elements = document.forms[0].elements;
  for (var i = 0; i < elements.length; i++) {
elements[i].style.display = "none";
  }
  
  
  
  ---

  this is detail that belongs in `firefox` and not `gedit` ... ie. bug.

  This issue is NOT new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu73
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: called for pid 2593, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable: 
/snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer (command line 
"/snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer")
   ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable does not 
belong to a package, ignoring
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465+canary3.3
  CrashReports:
   644:0:0:30:2021-11-17 16:33:08.496906043 +1100:2021-11-17 16:33:08.496906043 
+1100:/var/crash/1637127188.494807005.install_fail.meta
   640:0:0:726809:2021-11-17 16:33:41.277731657 +1100:2021-11-17 
16:33:42.277731657 +1100:/var/crash/1637127188.494807005.install_fail.crash
   644:0:0:0:2021-11-17 16:33:45.953817607 +1100:2021-11-17 16:33:45.953817607 
+1100:/var/crash/1637127188.494807005.install_fail.upload
   600:116:123:5:2021-11-17 16:48:24.898416884 +1100:2021-11-17 
16:33:45.953817607 +1100:/var/crash/1637127188.494807005.install_fail.uploaded
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 17 16:52:32 2021
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1951214] [NEW] ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets data

[Chris Guiver]

Public bug reported:

This has been reported before on Ubuntu Community Hub, but I want/need a
bug report filed on launchpad to report/track on iso.qa.ubuntu.com

On a `ubuntu-bug` or apport opening up a bug report; a gedit window
opens with

---


  OpenID transaction in progress


https://login.launchpad.net/+openid"; method="post" 
accept-charset="UTF-8" enctype="application/x-www-form-urlencoded">http://openid.net/extensions/sreg/1.1"/>https://launchpad.net/+openid-callback?starting_url=https%3A%2F%2Fbugs.launchpad.net%2Fsubiquity%2F%2Bfilebug%2Ff55a6274-4767-11ec-a1ce-d485646cd9a4%3Ffield.title%3Dinstall%2Bfailed%2Bcrashed%2Bwith%2BCalledProcessError&janrain_nonce=2021-11-17T05%3A34%3A05Zo24b46"/>https://launchpad.net/"/>http://specs.openid.net/auth/2.0/identifier_select"/>http://specs.openid.net/auth/2.0"/>http://specs.openid.net/auth/2.0/identifier_select"/>

var elements = document.forms[0].elements;
for (var i = 0; i < elements.length; i++) {
  elements[i].style.display = "none";
}



---

this is detail that belongs in `firefox` and not `gedit` ... ie. bug.

This issue is NOT new.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu73
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportLog:
 ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: called for pid 2593, signal 
11, core limit 0, dump mode 1
 ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable: 
/snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer (command line 
"/snap/ubuntu-desktop-installer/171/bin/ubuntu_desktop_installer")
 ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: executable does not belong 
to a package, ignoring
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465+canary3.3
CrashReports:
 644:0:0:30:2021-11-17 16:33:08.496906043 +1100:2021-11-17 16:33:08.496906043 
+1100:/var/crash/1637127188.494807005.install_fail.meta
 640:0:0:726809:2021-11-17 16:33:41.277731657 +1100:2021-11-17 
16:33:42.277731657 +1100:/var/crash/1637127188.494807005.install_fail.crash
 644:0:0:0:2021-11-17 16:33:45.953817607 +1100:2021-11-17 16:33:45.953817607 
+1100:/var/crash/1637127188.494807005.install_fail.upload
 600:116:123:5:2021-11-17 16:48:24.898416884 +1100:2021-11-17 
16:33:45.953817607 +1100:/var/crash/1637127188.494807005.install_fail.uploaded
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 17 16:52:32 2021
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug iso-testing jammy uec-images

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

Title:
  ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets
  data

Status in apport package in Ubuntu:
  New

Bug description:
  This has been reported before on Ubuntu Community Hub, but I want/need
  a bug report filed on launchpad to report/track on iso.qa.ubuntu.com

  On a `ubuntu-bug` or apport opening up a bug report; a gedit window
  opens with

  ---
  
  
OpenID transaction in progress
  
  
  https://login.launchpad.net/+openid"; method="post" 
accept-charset="UTF-8" enctype="application/x-www-form-urlencoded">http://openid.net/extensions/sreg/1.1"/>https://launchpad.net/+openid-callback?starting_url=https%3A%2F%2Fbugs.launchpad.net%2Fsubiquity%2F%2Bfilebug%2Ff55a6274-4767-11ec-a1ce-d485646cd9a4%3Ffield.title%3Dinstall%2Bfailed%2Bcrashed%2Bwith%2BCalledProcessError&janrain_nonce=2021-11-17T05%3A34%3A05Zo24b46"/>https://launchpad.net/"/>http://specs.openid.net/auth/2.0/identifier_select"/>http://specs.openid.net/auth/2.0"/>http://specs.openid.net/auth/2.0/identifier_select"/>
  
  var elements = document.forms[0].elements;
  for (var i = 0; i < elements.length; i++) {
elements[i].style.display = "none";
  }
  
  
  
  ---

  this is detail that belongs in `firefox` and not `gedit` ... ie. bug.

  This issue is NOT new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu73
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 2820) Wed Nov 17 16:33:33 2021: called for pid 2593, 
signal 11, core limit 0, du

[Touch-packages] [Bug 1943990] Re: After updating systemd packages to 245.4-4ubuntu3.13 and libvirt packages to 6.0.0-0ubuntu8.14, it is no longer possible to start kvm virtual machines

[Launchpad Bug Tracker]

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

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

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

Title:
  After updating systemd packages to 245.4-4ubuntu3.13 and libvirt
  packages to 6.0.0-0ubuntu8.14, it is no longer possible to start kvm
  virtual machines

Status in systemd package in Ubuntu:
  Expired

Bug description:
  # systemctl status systemd-machined.service 
  ● systemd-machined.service - Virtual Machine and Container Registration 
Service
   Loaded: loaded (/lib/systemd/system/systemd-machined.service; static; 
vendor preset: enabled)
   Active: inactive (dead)
 Docs: man:systemd-machined.service(8)
   https://www.freedesktop.org/wiki/Software/systemd/machined

  Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual 
Machine and Container Registration Service.
  Sep 17 15:40:42 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job 
systemd-machined.service/start failed with result 'dependency'.
  Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual 
Machine and Container Registration Service.
  Sep 17 15:42:26 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job 
systemd-machined.service/start failed with result 'dependency'.
  Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual 
Machine and Container Registration Service.
  Sep 17 16:02:55 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job 
systemd-machined.service/start failed with result 'dependency'.
  Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: Dependency failed for Virtual 
Machine and Container Registration Service.
  Sep 17 16:04:39 MGL1-SRV-0006 systemd[1]: systemd-machined.service: Job 
systemd-machined.service/start failed with result 'dependency'.

  Trying to start a virtual machine from openstack, it defines the
  machine, but is not able to execute it.

  I used to have libvirt apparmor errors, but disabling libvirt in apparmor 
didn't solve the problem:
  [   27.785713] audit: type=1400 audit(1631888214.441:67): apparmor="DENIED" 
operation="capable" profile="libvirtd" pid=4817 comm="libvirtd" capability=17  
capname="sys_rawio"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd-container 245.4-4ubuntu3.11
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Sep 17 16:23:39 2021
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1854621] Re: ubuntu 20.04 daily boots with no (or warped) background, selecting other background has warped wallpaper

[Chris Guiver]

Ubuntu jammy daily ISO (canary) used in LIVE mode on same box
- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

machine operates perfectly though.  Background today was only BLACK (no
wallpaper), none showed with 6 attempts to change, but all BLACK is
possibly better than glitchy/warped.

The bug today could be described as incapable of changing wallpaper on
box.  I'm doing boot tests today & will very on next boot that I can
change wallpaper (ie. I believe related to video card)

** Tags added: jammy

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

Title:
  ubuntu 20.04 daily boots with no (or warped) background, selecting
  other background has warped wallpaper

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 daily - verified (check disc for defects) prior to boot.
  dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  On booting, the 20.04 daily has no background when desktop is loaded?
  (ie. top panel is there, dock on left side on black screen)

  When changing background (to any already installed), they are warped
  when selected and made the bacground as if corrupted (but small image
  where selection is made looks valid).


  This issue may relate to video card  [radeon]

  ubuntu@ubuntu:~$ sudo lshw -C video
*-display:0   
 description: VGA compatible controller
 product: RV516 [Radeon X1300/X1550 Series]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e 
ioport:dc00(size=256) memory:c-d
*-display:1 UNCLAIMED
 description: Display controller
 product: RV516 [Radeon X1300/X1550 Series] (Secondary)
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0.1
 bus info: pci@:01:00.1
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress bus_master cap_list
 configuration: latency=0
 resources: memory:fe9f-fe9f

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.440
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  CasperVersion: 1.432
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:58:33 2019
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1951142] Re: Windows change position after screen flashes in Wayland

[Daniel van Vugt]

Thanks for the bug report.

Please open the Extensions app (from package gnome-shell-extension-
prefs) and temporarily disable all extensions. Now does the bug still
happen?

If the bug is still happening without extensions then next please live
boot Ubuntu 21.10 from USB and tell us if you experience a similar
problem there: https://ubuntu.com/download/desktop

If the bug is still happening in 21.10 then next please report it to the
developers at: https://gitlab.gnome.org/GNOME/mutter/issues

** Tags added: amdgpu dual-gpu i915

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

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Windows change position after screen flashes in Wayland
+ App window jumps between monitors when not even being used

** Tags removed: amdgpu dual-gpu i915
** Tags added: multimonitor

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  App window jumps between monitors when not even being used

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

Bug description:
  When using the Wayland session, the screen will sometimes randomly
  flash (usually after opening an application). After the screen
  flashes, the open windows will often end up in different positions or
  in different monitors. Video of the issue is attached.

  Expected Behavior: For the LibreOffice window to stay on the right
  monitor and to not change size or position.

  Actual Behavior: The LibreOffice window opens to the right after I
  open Lollypop.

  This issue doesn't exclusively happen while LibreOffice or when
  opening Lollypop, however, opening Lollypop is one of the most
  predictable ways to trigger the bug. The majority of the time, the bug
  occurs in the middle of regular use without me triggering anything.

  
  I'm using a dual monitor set-up, with a 2560X1080 monitor at 1x scaling 
hooked up to a 4K Hi-DPI laptop screen at 2x scaling.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 16 11:22:32 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:08ac]
 Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
  InstallationDate: Installed on 2020-11-18 (362 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Precision 5530 2-in-1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.10
  dmi.board.name: 02TH5P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:br1.11:svnDellInc.:pnPrecision55302-in-1:pvr:sku08AC:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5530 2-in-1
  dmi.product.sku: 08AC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.719.3

---
livecd-rootfs (2.719.3) hirsute; urgency=medium

  [ Thomas Bechtold ]
  * magic-proxy: Replace http.client with urllib calls. live-build/auto/build:
change iptables calls to query rules and quickly check that connectivity
works after transparent proxy has been installed. (LP: #1917920)
  * magic-proxy: fix TypeError when trying to call get_uri() (LP: #1944906)

 -- Brian Murray   Thu, 21 Oct 2021 11:17:58 -0700

** Changed in: livecd-rootfs (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 iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1917920

Title:
  magic-proxy broke with iptables 1.8.7-1ubuntu2

Status in launchpad-buildd:
  Invalid
Status in iptables package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in iptables source package in Bionic:
  Invalid
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in lxd source package in Bionic:
  Invalid
Status in iptables source package in Focal:
  Invalid
Status in livecd-rootfs source package in Focal:
  Fix Released
Status in lxd source package in Focal:
  Invalid
Status in iptables source package in Hirsute:
  Invalid
Status in livecd-rootfs source package in Hirsute:
  Fix Released
Status in lxd source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  The fixes for this bug (including the fixes for LP:#1944906) need to be 
backported to hirsute, focal and bionic) to be able to re-enable  the 
"repo-snapshot-stamp" feature for image builds. That feature is important to 
get consistent image builds (means the same set of packages included in the 
different images) when doing multiple builds (eg. for AWS, Azure and GCE).

  [Test Plan]
  - build a livecd-rootfs image with the changes for every series in a PPA
  - Do build an image with the livecd-rootfs from the PPA and enable the 
repo-snapshot-stamp feature
  - Check that the build did not fail or hang

  [Where problems could occur]
  The codepath that will be changed is only executed in livecd-rootfs if the 
repo-snapshot-stamp feature is enabled. And that feature is currently broken so 
it shouldn't be enabled anywhere.

  [Original description]

  when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic
  proxy stopped working in livecd-rootfs.

  It does very simple thing:

  iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner
  daemon -j REDIRECT --to 8080

  inside hirsute lxd container, with quite high privileges, in a bionic
  VM, running 4.15 kernel.

  With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound
  connectivity the very first http networking command after the above
  call would just hang indefinitely.

  However, if one does this instead:

  iptables -vv -t nat -S
  iptables-legacy -vv -t nat -S
  iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon 
-j REDIRECT --to 8080

  somehow magically everything starts to work fine.

  weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+subscriptions


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

[Touch-packages] [Bug 1896251] Re: rsync --delete-missing-args fails with "error: protocol incompatibility"

[Launchpad Bug Tracker]

This bug was fixed in the package rsync - 3.1.2-2.1ubuntu1.2

---
rsync (3.1.2-2.1ubuntu1.2) bionic; urgency=medium

  * d/p/allow-missing-parent-dir-delete-missing-args.patch:
Fix error caused by files being deleted having a missing parent
directory. Thanks to Wayne Davison .
(LP: #1896251)

 -- Lena Voytek   Thu, 28 Oct 2021 09:38:50
-0700

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

Title:
  rsync --delete-missing-args fails with "error: protocol
  incompatibility"

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Xenial:
  Won't Fix
Status in rsync source package in Bionic:
  Fix Released
Status in rsync source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Rsync crashes when using --delete-missing-args on a file with a
  missing parent folder.

  Backporting this fix will allow users to delete missing source args
  when some files in the list have missing parent folders without
  interruption.

  This is fixed by patching in an upstream commit that allows files with
  missing parent folders to be handled without aborting.

  [Test Plan]

  # lxc launch images:ubuntu/focal builder
  # lxc exec builder bash
  # apt update
  # apt dist-upgrade
  # apt install -y rsync
  # mkdir -p a/1 b/1; echo "/1/2/3" > list
  # rsync --dry-run --stats -Pav --delete-missing-args --files-from=list a b

  * This should crash with exit code 2 after printing the following:

  building file list ...
   0 files...
  file has vanished: "/root/a/1/2"
  2 files to consider
  ABORTING due to invalid path from sender: 1/2/3
  rsync error: protocol incompatibility (code 2) at generator.c(1278) 
[generator=3.1.3]

  [Where problems could occur]

  Since the remove operation will now continue when files in the list
  have missing parent folders, other errors and warnings with different
  behaviors could arise instead.

  A warning that may arise the most often in these situations is the
  following:

  warning: some files vanished before they could be transferred (code
  24) at main.c(1207) [sender=3.1.3]

  This appears at the end of the above test case with the new code. The
  behavior is expected, but it may cause regressions due to changes in
  the output of certain use cases.

  [Original Description]

  Running

 rsync --delete-missing-args --files-from=...

  fails with error message like

  ABORTING due to invalid path from sender: dir1/dir2/dir3
  rsync error: protocol incompatibility (code 2) at generator.c(1271) 
[generator=3.1.2]

  if the listed directories are trying to delete full subtree of files.

  According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has
  been fixed in version 3.2.2.

  See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334

  Could you update the rsync package or backport the fix?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rsync 3.1.2-2.1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55
  Uname: Linux 5.4.0-47-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep 18 18:27:53 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-01-05 (621 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1896251] Re: rsync --delete-missing-args fails with "error: protocol incompatibility"

[Launchpad Bug Tracker]

This bug was fixed in the package rsync - 3.1.3-8ubuntu0.1

---
rsync (3.1.3-8ubuntu0.1) focal; urgency=medium

  * d/p/allow-missing-parent-dir-delete-missing-args.patch:
Fix error caused by files being deleted having a missing parent
directory. Thanks to Wayne Davison .
(LP: #1896251)

 -- Lena Voytek   Thu, 28 Oct 2021 09:36:35
-0700

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

** Changed in: rsync (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 rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1896251

Title:
  rsync --delete-missing-args fails with "error: protocol
  incompatibility"

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Xenial:
  Won't Fix
Status in rsync source package in Bionic:
  Fix Released
Status in rsync source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Rsync crashes when using --delete-missing-args on a file with a
  missing parent folder.

  Backporting this fix will allow users to delete missing source args
  when some files in the list have missing parent folders without
  interruption.

  This is fixed by patching in an upstream commit that allows files with
  missing parent folders to be handled without aborting.

  [Test Plan]

  # lxc launch images:ubuntu/focal builder
  # lxc exec builder bash
  # apt update
  # apt dist-upgrade
  # apt install -y rsync
  # mkdir -p a/1 b/1; echo "/1/2/3" > list
  # rsync --dry-run --stats -Pav --delete-missing-args --files-from=list a b

  * This should crash with exit code 2 after printing the following:

  building file list ...
   0 files...
  file has vanished: "/root/a/1/2"
  2 files to consider
  ABORTING due to invalid path from sender: 1/2/3
  rsync error: protocol incompatibility (code 2) at generator.c(1278) 
[generator=3.1.3]

  [Where problems could occur]

  Since the remove operation will now continue when files in the list
  have missing parent folders, other errors and warnings with different
  behaviors could arise instead.

  A warning that may arise the most often in these situations is the
  following:

  warning: some files vanished before they could be transferred (code
  24) at main.c(1207) [sender=3.1.3]

  This appears at the end of the above test case with the new code. The
  behavior is expected, but it may cause regressions due to changes in
  the output of certain use cases.

  [Original Description]

  Running

 rsync --delete-missing-args --files-from=...

  fails with error message like

  ABORTING due to invalid path from sender: dir1/dir2/dir3
  rsync error: protocol incompatibility (code 2) at generator.c(1271) 
[generator=3.1.2]

  if the listed directories are trying to delete full subtree of files.

  According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has
  been fixed in version 3.2.2.

  See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334

  Could you update the rsync package or backport the fix?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rsync 3.1.2-2.1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55
  Uname: Linux 5.4.0-47-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep 18 18:27:53 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-01-05 (621 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1896251] Update Released

[Chris Halse Rogers]

The verification of the Stable Release Update for rsync 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 rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1896251

Title:
  rsync --delete-missing-args fails with "error: protocol
  incompatibility"

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Xenial:
  Won't Fix
Status in rsync source package in Bionic:
  Fix Committed
Status in rsync source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Rsync crashes when using --delete-missing-args on a file with a
  missing parent folder.

  Backporting this fix will allow users to delete missing source args
  when some files in the list have missing parent folders without
  interruption.

  This is fixed by patching in an upstream commit that allows files with
  missing parent folders to be handled without aborting.

  [Test Plan]

  # lxc launch images:ubuntu/focal builder
  # lxc exec builder bash
  # apt update
  # apt dist-upgrade
  # apt install -y rsync
  # mkdir -p a/1 b/1; echo "/1/2/3" > list
  # rsync --dry-run --stats -Pav --delete-missing-args --files-from=list a b

  * This should crash with exit code 2 after printing the following:

  building file list ...
   0 files...
  file has vanished: "/root/a/1/2"
  2 files to consider
  ABORTING due to invalid path from sender: 1/2/3
  rsync error: protocol incompatibility (code 2) at generator.c(1278) 
[generator=3.1.3]

  [Where problems could occur]

  Since the remove operation will now continue when files in the list
  have missing parent folders, other errors and warnings with different
  behaviors could arise instead.

  A warning that may arise the most often in these situations is the
  following:

  warning: some files vanished before they could be transferred (code
  24) at main.c(1207) [sender=3.1.3]

  This appears at the end of the above test case with the new code. The
  behavior is expected, but it may cause regressions due to changes in
  the output of certain use cases.

  [Original Description]

  Running

 rsync --delete-missing-args --files-from=...

  fails with error message like

  ABORTING due to invalid path from sender: dir1/dir2/dir3
  rsync error: protocol incompatibility (code 2) at generator.c(1271) 
[generator=3.1.2]

  if the listed directories are trying to delete full subtree of files.

  According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has
  been fixed in version 3.2.2.

  See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334

  Could you update the rsync package or backport the fix?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rsync 3.1.2-2.1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55
  Uname: Linux 5.4.0-47-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep 18 18:27:53 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-01-05 (621 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

Re: [Touch-packages] [Bug 1921518] Re: OpenSSL "double free" error

[Brian Murray]

On Tue, Nov 16, 2021 at 03:24:21PM -, Vladimir Sokolovsky wrote:
> The fix was verified for wget and curl.
> Thanks a lot.
> 
> When these new packages will be added to "updates" repository?

There is a minimum aging period of 7 days in -proposed and shortly after
that they will migrate to -updates. (Provided that day isn't a Friday.)

--
Brian Murray

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

Title:
  OpenSSL "double free" error

Status in openssl package in Ubuntu:
  Incomplete
Status in wget package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  Incomplete
Status in wget source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  openssl config file is being loaded twice, causing engines to be loaded twice 
if specified therein, causing double free errors and other strange behavior.

  [Test plan]
  Run the command of the package being tested in

  gdb  -ex "break CONF_modules_load_file" -ex "run" --args

  and make sure it only breaks one.

  Regression test:

  In default Ubuntu configuration, either no openssl configuration is provided, 
or it contains no settings that affect wget. This code path changes how/when 
openssl configuration is loaded and used by openssl. One should verify that:
  1) wget continues to work without openssl.cnf
  2) wget continues to work with stock ubuntu unmodified openssl.cnf
  3) wget continue to honor and use custom TLS settings that one may have 
specified in openssl.cnf (for example custom engine)

  
  [Where problems could occur]

  wget: This is an upstream change that changes initialization and is in
  use in later releases. Since it mostly removes an unneeded call to the
  load file function, a regression could be a config file being ignored,
  but it seems unlikely given the use in later releases

  
  [Original bug report]
  "double free" error is seen when using curl utility. Error is from 
libcrypto.so which is part of the OpenSSL package. This happens only when 
OpenSSL is configured to use a dynamic engine.

  OpenSSL version is 1.1.1f

  The issue is not encountered if
  http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead.

  OpenSSL can be configured to use a dynamic engine by editing the
  default openssl config file which is located at '/etc/ssl/openssl.cnf'
  on Ubuntu systems.

  On Bluefield systems, config diff to enable PKA dynamic engine, is as
  below:

  +openssl_conf = conf_section
  +
   # Extra OBJECT IDENTIFIER info:
   #oid_file  = $ENV::HOME/.oid
   oid_section= new_oids

  +[ conf_section ]
  +engines = engine_section
  +
  +[ engine_section ]
  +bf = bf_section
  +
  +[ bf_section ]
  +engine_id=pka
  +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so
  +init=0
  +

  engine_id above refers to dynamic engine name/identifier.
  dynamic_path points to the .so file for the dynamic engine.

  # curl -O https://tpo.pe/pathogen.vim

  double free or corruption (out)

  Aborted (core dumped)

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


-- 
Mailing list: https://launchpad.net/~touch-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?

[Allen McIntosh]

Now that I think of it, that's qualitatively no different than running
"vim.tiny"...

-- 
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 1873920] Re: default vi on focal emits escape sequences unrecognized by bionic's terminal?

[Allen McIntosh]

Workaround:

ex file

visual
("visual" can be abbreviated as "vi")

-- 
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 1591490] Re: Please backport apt 1.0.9.2ubuntu2 from utopic (to fix do-release-upgrade)

[Dan Streetman]

** Changed in: trusty-backports
   Status: New => Won't Fix

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

Title:
  Please backport apt 1.0.9.2ubuntu2 from utopic (to fix do-release-
  upgrade)

Status in trusty-backports:
  Won't Fix
Status in apt package in Ubuntu:
  Confirmed

Bug description:
  For me (and apparently many others), upgrading Ubuntu Trusty LTS to
  Ubuntu Xenial LTS fails because do-release-upgrade bails out because
  of apt error messages like this:

  
  Unknown Multi-Arch type 'no' for package 'kwin'
  Unknown Multi-Arch type 'no' for package 'kwin-dev'
  Unknown Multi-Arch type 'no' for package 'kwin-wayland'
  Unknown Multi-Arch type 'no' for package 'kwin-x11'
  Unknown Multi-Arch type 'no' for package 'libkf5sysguard-dev'

  Unknown Multi-Arch type 'no' for package 'compiz-core'
  Unknown Multi-Arch type 'no' for package 'compiz-gnome'
  Unknown Multi-Arch type 'no' for package 'libxapian-dev'

  
  It is caused by Debian bug #759099 [1] fixed in apt 1.0.7. Therefore I'm 
requesting a backport of "apt" to trusty.

  In the title I've suggested 1.0.9 from utopic - a more recent version
  might be fine too but when I tried to build the wily version on my
  local machine it couldn't because the g++ requirement had moved on too
  far.

  
  [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759099

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1591490/+subscriptions


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

[Touch-packages] [Bug 1285783] Re: Right panel has a transparent background

[Dan Streetman]

** Changed in: trusty-backports
   Status: New => Won't Fix

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

Title:
  Right panel has a transparent background

Status in trusty-backports:
  Won't Fix
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Launching gnome-tweak-tool and choosing a category on the left panel
  makes the right panel transparent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1285783/+subscriptions


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

[Touch-packages] [Bug 326217] Re: QT libraries in hardy broken because of backports

[Dan Streetman]

** Changed in: hardy-backports
   Status: Incomplete => Won't Fix

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

Title:
  QT libraries in hardy broken because of backports

Status in Hardy Backports:
  Won't Fix
Status in qt4-x11 package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: libqt4-core

  Hello,

  there is an uncompatibility in the current LTS release Hardy Heron.
  Several packages (like qt4-core, qt4-gui etc) are in 4.3.4 version but
  some others (libqt4-dbg, libqt4-doc...) are backported and in version
  4.4.0.

  And this is big problem. For example I am unable to develop with QT4
  because I need all of the modules (core, bui, dbg, doc, xml, webkit
  etc) and this cannot be done because of dependencies:

  The following packages have unmet dependencies:
libqt4-help: Depends: libqt4-sql (= 4.4.0-1ubuntu5~hardy1) but 
4.3.4-0ubuntu3 is to be installed

  Solution: backport all QT4 libraries (version 4.4.0). Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hardy-backports/+bug/326217/+subscriptions


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

[Touch-packages] [Bug 313960] Re: Please update dnsmasq hardy packages to version 2.46

[Dan Streetman]

** Changed in: hardy-backports
   Status: New => Won't Fix

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

Title:
  Please update dnsmasq hardy packages to version 2.46

Status in Hardy Backports:
  Won't Fix
Status in dnsmasq package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: dnsmasq

  Hello,

  Dnsmasq has added support for CNAME directives in the config file starting 
with version 2.46.
  This version is not available in Hardy, while I believe a LTS release should 
deserve this improvement.
  All alternatives require (to my knowledge) heavier configuration and / or 
demand more on resources.
  Switching to bind in order to use CNAME or compiling dnsmasq2.46 from source 
should be considered nontrivial/discourage for the average/beginning user.

  How about relasing a package for v2.46 in backports ?

  Regards,

  Dr. Moe

To manage notifications about this bug go to:
https://bugs.launchpad.net/hardy-backports/+bug/313960/+subscriptions


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

[Touch-packages] [Bug 792301] Re: Ericsson F5521gw 3G module for Lenovo not using optimal kernel module

[Dan Streetman]

** Changed in: lucid-backports
   Status: New => Won't Fix

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

Title:
  Ericsson F5521gw 3G module for Lenovo not using optimal kernel module

Status in Lucid Backports:
  Won't Fix
Status in ModemManager:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: modemmanager

  The Ericsson F5521gw 3G module should use the usb_ncm kernel module
  (/dev/usb0) for connecting for optimal speed and CPU usage (important
  for HSPA+ connections). Modemmanager needs to be told this for the usb
  ID 0bdb:1911 (currently only 0bdb:190d supported).

  See the attached patch already in current version of modemmanager:

  
http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=0b757465ffe6108066d32312ab4e895c372c8f72

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: modemmanager 0.4+git.20110124t203624.00b6cce-2ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-9.43-generic-pae 2.6.38.4
  Uname: Linux 2.6.38-9-generic-pae i686
  Architecture: i386
  Date: Fri Jun  3 12:41:25 2011
  ProcEnviron:
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, user)
   LANG=nb_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to natty on 2011-04-29 (35 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lucid-backports/+bug/792301/+subscriptions


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

[Touch-packages] [Bug 865907] Re: Please backport tracker to Oneiric

[Dan Streetman]

** Changed in: oneiric-backports
   Status: New => Won't Fix

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

Title:
  Please backport tracker to Oneiric

Status in Oneiric Backports:
  Won't Fix
Status in tracker package in Ubuntu:
  Invalid

Bug description:
  Tracker 0.12 is the latest stable release of GNOME's search engine. It
  is needed for GNOME Documents. I've tested version 12.6-1 by letting
  it index my home directory and I ran some searches. The indexed
  documents showed up in GNOME Documents as they were supposed to.

  Build log: https://launchpadlibrarian.net/81619551/buildlog_ubuntu-
  oneiric-amd64.tracker_0.12.3-1~ppa1_BUILDING.txt.gz

  Tracker 0.12 has been in the GNOME 3 PPA for a month now (since
  October 5). I've been running it on my computer for a month and I've
  not seen a single complaint about it not working.
  
https://launchpad.net/~gnome3-team/+archive/gnome3/+builds?build_text=tracker&build_state=all

To manage notifications about this bug go to:
https://bugs.launchpad.net/oneiric-backports/+bug/865907/+subscriptions


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

[Touch-packages] [Bug 1946847] Re: Merge bridge-utils from Debian unstable for 22.04

[Bryce Harrington]

[No new version yet available from Debian]

** Changed in: bridge-utils (Ubuntu)
   Status: New => Incomplete

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

Title:
  Merge bridge-utils from Debian unstable for 22.04

Status in bridge-utils package in Ubuntu:
  Incomplete

Bug description:
  Upstream: 1.7.1
  Debian:   1.7-1
  Ubuntu:   1.7-1ubuntu2

  Debian typically updates bridge-utils every 4 months on average, but
  it was last updated 21.02 and looks overdue.  Check back in on this
  monthly.

  ### New Debian Changes ###

  bridge-utils (1.7-1) unstable; urgency=medium

    * New upstream version.
  Only messages related changes and compilation fixes.
    * Remove preserve_gcc_flags patch (in upstream now).
    * Bump standards, no change needed.
    * Clarify portprio and fix example.
    * Update upstream url.
    * Fix NEWS versioning of last entry :-?

   -- Santiago Garcia Mantinan   Wed, 24 Feb 2021
  12:34:03 +0100

  bridge-utils (1.6-6) unstable; urgency=medium

    * Fix IPv6 address getting assigned on hotplug devices.
  Closes: #980752.
    * Fix waiting so that DAD works again. Closes: #982943.
    * Move mac setting before brctl addif to ensure mac setting.
  Closes: #980856.
    * Update documentation and add examples. Closes: #765098.
    * Update manpages. Closes: #981253.
    * Add a note on MTU settings. Closes: #292088.
    * Hook also on down to recreate the bridge so that multiple
  stanzas work Ok on ifdown. Closes: #319832.

   -- Santiago Garcia Mantinan   Tue, 16 Feb 2021
  13:29:04 +0100

  bridge-utils (1.6-5) unstable; urgency=low

    * Overload bridge_hw to allow do specify an interface as well as the
  MAC address. Closes: #966244.
    * Change man page for bridge-utils-interfaces and news fileto document
  this overloading.

   -- Santiago Garcia Mantinan   Fri, 22 Jan 2021
  11:08:47 +0100

  bridge-utils (1.6-4) unstable; urgency=low

    * Add en* to the device regex so that all catches them. Closes: #966319.
    * Document MAC address changes on news. Closes: #980505.

   -- Santiago Garcia Mantinan   Thu, 21 Jan 2021
  10:51:31 +0100

  bridge-utils (1.6-3) unstable; urgency=medium

    * Support VLAN aware setups where we need vlan filtering.
  Thanks Benedikt Spranger for the patch. Closes: #950879.
    * Clarify on manual page that stp will get IPv6 lost. Closes: #736336.
    * Add a 1 second sleep if hw address needs to be changed. Closes: #945466.

   -- Santiago Garcia Mantinan   Thu, 30 Apr 2020
  10:06:38 +0200

  bridge-utils (1.6-2) unstable; urgency=medium

    * Bump Standards-Version.
    * Preserve gcc flags set when building the lib.

   -- Santiago Garcia Mantinan   Mon, 28 Jan 2019
  00:25:14 +0100

  bridge-utils (1.6-1) unstable; urgency=low

    * New upstream version.
    * Change default back to not hotplug. Closes: #892277.
    * Allow mtu to be set on the bridge by propagating it to the bridged
  interfaces. Closes: #661711.
    * Remove kernel headers from the package.

   -- Santiago Garcia Mantinan   Tue, 15 Jan 2019
  13:18:33 +0100

  bridge-utils (1.5-16) unstable; urgency=medium

    * Don't set dev globally at bridge-utils.sh. Closes: #873086.

   -- Santiago Garcia Mantinan   Sun, 08 Apr 2018
  23:06:30 +0200

  bridge-utils (1.5-15) unstable; urgency=medium

    * Fix substrings on interfaces. Closes: #873087.
    * Make it lintian clean sticking to 1.0 source format for now.
  No time to properly comment all the patches right now.

   -- Santiago Garcia Mantinan   Fri, 02 Mar 2018
  22:08:20 +0100

  bridge-utils (1.5-14) unstable; urgency=low

    * Fix a problem with some vlan interfaces not being created.

   -- Santiago Garcia Mantinan   Mon, 26 Jun 2017
  17:48:37 +0200

  bridge-utils (1.5-13) unstable; urgency=low

    * Fix a hardcoded interface name on bridge-utils.sh. Closes:
  #854841.

   -- Santiago Garcia Mantinan   Sat, 11 Feb 2017
  00:16:45 +0100

  bridge-utils (1.5-12) unstable; urgency=medium

    * Add vlan support so that old setups using vlans as ports don't
  break.

   -- Santiago Garcia Mantinan   Sun, 22 Jan 2017
  00:23:50 +0100

  ### Old Ubuntu Delta ###

  bridge-utils (1.7-1ubuntu2) impish; urgency=medium

    * No-change rebuild to build packages with zstd compression.

   -- Matthias Klose   Thu, 07 Oct 2021 12:09:41 +0200

  bridge-utils (1.7-1ubuntu1) impish; urgency=low

    * Merge from Debian unstable. Remaining changes:
  - Don't call ifup from bridge-network-interface, instead just call brctl
    and let udev/upstart bring the interface up.
  - debian/ifupdown.sh: Handle bridge params which use port and value
  - debian/bridge-utils-interface.5:
    + Update max, default value for path cost
    + Update unsettable gcint value for newer kernels

   -- Steve Langasek   Wed, 17 Mar 2021
  12

[Touch-packages] [Bug 1951154] Re: 2FA application can’t work properly because secrets portal isn't responding

[Sebastien Bacher]

** No longer affects: python-keyring (Ubuntu)

** No longer affects: libsecret (Ubuntu)

** No longer affects: gnome-keyring (Ubuntu)

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

Title:
  2FA application can’t work properly because secrets portal isn't
  responding

Status in Ubuntu MATE:
  New
Status in flatpak package in Ubuntu:
  New
Status in xdg-desktop-portal-gtk package in Ubuntu:
  New

Bug description:
  Flatpak application installed from flathub has problem with secrets
  portal.

  Please take a look at this issue on github here:

  https://github.com/jhaygood86/mauborgne/issues/22

  I’m not able to import any file using this 2FA application.

  Distributor ID: Ubuntu
  Description:  Ubuntu 21.10
  Release:  21.10
  Codename: impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1951154/+subscriptions


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

[Touch-packages] [Bug 1946898] Re: Merge rsync from Debian unstable for 22.04

[Bryce Harrington]

rsync (3.2.3-8ubuntu1) jammy; urgency=medium

  * Merge with Debian unstable. Remaining changes:
- debian/rules: add --disable-asm configure flag. The only asm
  implementation is available for md5 on x86_64, however it is no-op,
  because we built with OpenSSL which has optimized md5
  implementation. Furthermore, linking noop md5 asm on x86_64 results in
  rsync binary not getting marked as CET compatible, because the noop
  md5 asm is not marked as CET compatible. Thus building without noop
  md5 asm, results in rsync gaining CET.

 -- Bryce Harrington   Mon, 01 Nov 2021 16:05:43
-0700


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

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

Title:
  Merge rsync from Debian unstable for 22.04

Status in rsync package in Ubuntu:
  Fix Released

Bug description:
  Upstream: 3.2.3
  Debian:   3.2.3-8
  Ubuntu:   3.2.3-4ubuntu1

  Debian does new releases regularly, so it's likely there will be newer
  versions available before FF that we can pick up if this merge is done
  later in the cycle.

  ### New Debian Changes ###

  rsync (3.2.3-8) unstable; urgency=medium

    * debian/patches:
  - manpage_upstream_fixes.patch: Import multiple upstream patches to fix
    manpage.
  - copy-devices.diff: Add missing manpage changes to patch
  - CVE-2020-14387.patch: Add Forwarded DEP3 field to point to upstream 
patch
  - fix_delay_updates.patch: Refresh patch
  - fix_mkpath.patch: New upstream patch to fix an edge case on --mkpath
  - fix_rsync-ssl_RSYNC_SSL_CERT_feature.patch: New upstream patch
  - fix_sparse_inplace.patch: New upstream patch to fix --sparse + --inplace
    options
  - update_rrsync_options.patch: New upstream patch to update rrsync options

   -- Samuel Henrique   Sat, 25 Sep 2021 17:38:16
  +0100

  rsync (3.2.3-7) unstable; urgency=medium

    * Bump Standards-Version to 4.6.0
    * d/p/workaround_glibc_lchmod_regression.patch: New patch from upstream
  (closes: #994543)
    * debian/rsync.NEWS: Fix typo in last entry

   -- Samuel Henrique   Sat, 18 Sep 2021 00:25:13
  +0100

  rsync (3.2.3-6) unstable; urgency=medium

    * d/t/upstream-tests: Suppress stderr warnings from the build
  process

   -- Samuel Henrique   Sun, 12 Sep 2021 18:22:57
  +0100

  rsync (3.2.3-5) unstable; urgency=medium

    [ 刘建强 ]
    * Set the rsync.service not to start automatically after installation,
  the rsyncd.conf configuration file needs to be configured by the user
  before the service can start

    [ Samuel Henrique ]
    * Re-add upstream patch for --copy-devices, the --write-devices option is
  not fully equivalent (closes: #992215)
    * d/rsync.docs: Add NEWS.md file (previously named NEWS) (closes: #993697)
    * d/p/fix_delay_updates.patch: New patch from upstream (closes: #992231)

   -- Samuel Henrique   Sun, 12 Sep 2021 17:25:37
  +0100

  rsync (3.2.3-4) unstable; urgency=medium

    [ Helmut Grohne ]
    * d/p/fix_ftcbfs_configure.patch: New patch to fix FTCBFS (closes: #971285)

    [ Samuel Henrique ]
    * Bump Standards-Version to 4.5.1

   -- Samuel Henrique   Tue, 02 Feb 2021 23:08:54
  +

  rsync (3.2.3-3) unstable; urgency=high

    * d/p/CVE-2020-14387.patch: New patch to fix an openssl related CVE
  (closes: #969530, CVE-2020-14387)

   -- Samuel Henrique   Sat, 19 Dec 2020 12:48:33
  +

  rsync (3.2.3-2) unstable; urgency=medium

    [ Sergio Durigan Junior ]
    * Make the autopkgtests cross-friendly.
  Thanks to Steve Langasek 

   -- Samuel Henrique   Wed, 26 Aug 2020 21:23:57
  +0100

  rsync (3.2.3-1) unstable; urgency=medium

    * New upstream version 3.2.3
    * debian/patches:
  - time-limit.diff: Remove patch, applied upstream now
  - disable_reconfigure_req.diff: Refresh patch and dep3 headers
  - perl_shebang.patch: Update patch
  - fix_bwlimit_0.patch: Remove patch, applied upstream

   -- Samuel Henrique   Sun, 09 Aug 2020 13:41:10
  +0100

  rsync (3.2.2-2) unstable; urgency=medium

    * d/p/fix_bwlimit_0.patch: New upstream patch to fix bwlimit=0
  (closes: #964587)

   -- Samuel Henrique   Fri, 10 Jul 2020 18:35:21
  +0100

  rsync (3.2.2-1) unstable; urgency=medium

    * New upstream version 3.2.2
    * d/rsync.install: Install rsync-no-vanished (closes: #353697)

   -- Samuel Henrique   Mon, 06 Jul 2020 19:01:52
  +0100

  rsync (3.2.1-1) unstable; urgency=medium

    * New upstream version 3.2.1
    * Remove patches applied upstream:

  ### Old Ubuntu Delta ###

  rsync (3.2.3-4ubuntu1) impish; urgency=low

    * Merge from Debian unstable. Remaining changes:
  - debian/rules: add --disable-asm configure flag. The only asm
    implementation is available for md5 on x86_64, however it is no-op,
    because we built with OpenSSL which has optimize

[Touch-packages] [Bug 1951154] Re: 2FA application can’t work properly because secrets portal isn't responding

[Norbert]

Could you please add some comments how this is related to Ubuntu MATE?

Please run

apport-collect 1951154

to add necessary information.

** Tags added: impish

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

** Also affects: xdg-desktop-portal-gtk (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: gnome-keyring (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: python-keyring (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  2FA application can’t work properly because secrets portal isn't
  responding

Status in Ubuntu MATE:
  New
Status in flatpak package in Ubuntu:
  New
Status in gnome-keyring package in Ubuntu:
  New
Status in libsecret package in Ubuntu:
  New
Status in python-keyring package in Ubuntu:
  New
Status in xdg-desktop-portal-gtk package in Ubuntu:
  New

Bug description:
  Flatpak application installed from flathub has problem with secrets
  portal.

  Please take a look at this issue on github here:

  https://github.com/jhaygood86/mauborgne/issues/22

  I’m not able to import any file using this 2FA application.

  Distributor ID: Ubuntu
  Description:  Ubuntu 21.10
  Release:  21.10
  Codename: impish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1951154/+subscriptions


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

[Touch-packages] [Bug 1951161] [NEW] Please merge shadow 1:4.8.1-2 (main) from Debian unstable

[William Wilson]

Public bug reported:

This merge is necessary because there are changes present in Ubuntu that
are not present in Debian.

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

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

Title:
  Please merge shadow 1:4.8.1-2 (main) from Debian unstable

Status in shadow package in Ubuntu:
  New

Bug description:
  This merge is necessary because there are changes present in Ubuntu
  that are not present in Debian.

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


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

[Touch-packages] [Bug 1791958] Re: iptables-restore is missing -w option

[Dan Streetman]

Hello,

the backports process has recently been updated, please see the new 
documentation:
https://wiki.ubuntu.com/UbuntuBackports

I'm closing this bug, but please feel free to open a new bug (or reopen
this bug) using the new process, if appropriate.


** Changed in: bionic-backports
   Status: New => Won't Fix

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

Title:
  iptables-restore is missing -w option

Status in Bionic Backports:
  Won't Fix
Status in iptables package in Ubuntu:
  Confirmed

Bug description:
  For CRIU we need to have iptables version 1.6.2 which includes the
  '-w' option in iptables-restore.

  This is a request to update iptables to 1.6.2 in 18.10 and if possible
  backport the necessary changes to 18.04.

  The CRIU project gets right now many bug reports (mostly in the
  combination LXD + CRIU) due to the missing '-w' option in iptables-
  restore. Especially as 18.04 will be around for some time it would be
  good to have iptables-restore available with '-w'.

  This is one example bug report: https://github.com/checkpoint-
  restore/criu/issues/551

  But not only CRIU would benefit from this change. It seems also
  problematic with Kubernetes:
  https://github.com/kubernetes/kubernetes/pull/60978

  So if possible, please update iptables to 1.6.2 (or backport changes)
  to support -w in iptables-restore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bionic-backports/+bug/1791958/+subscriptions


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

[Touch-packages] [Bug 1949205] Re: Volume group "vgubuntu" not found when parition encrypted in LUKS

[Matthieu Clemenceau]

** Tags added: rls-ff-incoming

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

Title:
  Volume group "vgubuntu" not found when parition encrypted in LUKS

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I wonder whether that is correct LVM starts before LUKS disk decryption. 
Becuase of that the client see the message of non existing vgubuntu.
  Not sure whether that is expected behaviour.

  boot.log attached. And screenshot.

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


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

[Touch-packages] [Bug 1951155] [NEW] export i fails to work in bash

[ytxmobile]

Public bug reported:

I ran the following commands:
```
# In parent shell
export a=1
export i=2
bash # open child shell
# In child shell
echo $a # 1
echo $i # (empty)
exit
```

This bug happens when exporting the "i" variable from parent shell to child 
shell.
I have not tested what other variable names would trigger this bug.

* My OS: Ubuntu 20.04 LTS
* Bash version (running `bash --version`):
```
GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
```

I have also tested in the `sh` shell and did not see the problem:
```
# In parent shell
export a=1
export i=2
sh # open child shell
# In child shell
echo $a # 1
echo $i # 2
exit
```

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


** Tags: export

** Description changed:

  Try to run the following commands:
  ```
  # In parent shell
  export a=1
  export i=2
  bash # open child shell
  # In child shell
  echo $a # 1
  echo $i # (empty)
+ exit
  ```
  
  This bug happens when exporting the "i" variable from parent shell to child 
shell.
  I have not tested what other variable names would trigger this bug.
  
  * My OS: Ubuntu 20.04 LTS
  * Bash version (running `bash --version`):
  ```
  GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
  Copyright (C) 2019 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  
  This is free software; you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  ```
+ 
+ I have also tested in the `sh` shell and did not see the problem:
+ ```
+ # In parent shell
+ export a=1
+ export i=2
+ sh # open child shell
+ # In child shell
+ echo $a # 1
+ echo $i # 2
+ exit
+ ```

** Description changed:

- Try to run the following commands:
+ I ran the following commands:
  ```
  # In parent shell
  export a=1
  export i=2
  bash # open child shell
  # In child shell
  echo $a # 1
  echo $i # (empty)
  exit
  ```
  
  This bug happens when exporting the "i" variable from parent shell to child 
shell.
  I have not tested what other variable names would trigger this bug.
  
  * My OS: Ubuntu 20.04 LTS
  * Bash version (running `bash --version`):
  ```
  GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
  Copyright (C) 2019 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  
  This is free software; you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  ```
  
  I have also tested in the `sh` shell and did not see the problem:
  ```
  # In parent shell
  export a=1
  export i=2
  sh # open child shell
  # In child shell
  echo $a # 1
  echo $i # 2
  exit
  ```

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

Title:
  export i fails to work in bash

Status in bash package in Ubuntu:
  New

Bug description:
  I ran the following commands:
  ```
  # In parent shell
  export a=1
  export i=2
  bash # open child shell
  # In child shell
  echo $a # 1
  echo $i # (empty)
  exit
  ```

  This bug happens when exporting the "i" variable from parent shell to child 
shell.
  I have not tested what other variable names would trigger this bug.

  * My OS: Ubuntu 20.04 LTS
  * Bash version (running `bash --version`):
  ```
  GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
  Copyright (C) 2019 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 

  This is free software; you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  ```

  I have also tested in the `sh` shell and did not see the problem:
  ```
  # In parent shell
  export a=1
  export i=2
  sh # open child shell
  # In child shell
  echo $a # 1
  echo $i # 2
  exit
  ```

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


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

[Touch-packages] [Bug 1788060] Re: du program crashes on /var/lib

[Bert JW Regeer]

Coming back to this years later because I am running into this issue as
well, and wanted to provide some additional information:

At this time it seems to be crashing when it attempts to traverse from
/var/lib into lxcfs:

openat(4, "lxcfs", 
O_RDONLY|O_NOCTTY|O_NONBLOCK|O_NOFOLLOW|O_CLOEXEC|O_DIRECTORY) = 3
fstat(3, {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
fcntl(3, F_GETFL)   = 0x38800 (flags 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_NOFOLLOW|O_DIRECTORY)
fcntl(3, F_SETFD, FD_CLOEXEC)   = 0
newfstatat(4, "lxcfs", {st_mode=S_IFDIR|0755, st_size=0, ...}, 
AT_SYMLINK_NOFOLLOW) = 0
fstatfs(4, {f_type=XFS_SB_MAGIC, f_bsize=4096, f_blocks=1160704, 
f_bfree=1014059, f_bavail=1014059, f_files=2326528, f_ffree=2321112, 
f_fsid={val=[64771, 0]}, f_namelen=255, f_frsize=4096, 
f_flags=ST_VALID|ST_RELATIME}) = 0
fcntl(3, F_DUPFD_CLOEXEC, 3)= 5
getdents(3, /* 4 entries */, 32768) = 104
getdents(3, /* 0 entries */, 32768) = 0
close(3)= 0
newfstatat(5, "proc", {st_mode=S_IFDIR|0555, st_size=0, ...}, 
AT_SYMLINK_NOFOLLOW) = 0
openat(5, "proc", 
O_RDONLY|O_NOCTTY|O_NONBLOCK|O_NOFOLLOW|O_CLOEXEC|O_DIRECTORY) = 3
fstat(3, {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
fcntl(3, F_GETFL)   = 0x38800 (flags 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_NOFOLLOW|O_DIRECTORY)
fcntl(3, F_SETFD, FD_CLOEXEC)   = 0
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [], 8) = 0
getpid()= 16911
gettid()= 16911
tgkill(16911, 16911, SIGABRT)   = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
--- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=16911, si_uid=0} ---
+++ killed by SIGABRT (core dumped) +++
Aborted (core dumped)

I've attached the file with the crash from /var/crash.

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=457348k,nr_inodes=114337,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=97968k,mode=755)
/dev/mapper/vg_root-lv_root on / type xfs (rw,relatime,attr2,inode64,noquota)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup 
(rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=25,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=17576)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/nvme0n1p1 on /boot type ext4 (rw,relatime,data=ordered)
/dev/mapper/vg_root-lv_tmp on /tmp type xfs (rw,relatime,attr2,inode64,noquota)
/dev/mapper/vg_root-lv_var on /var type xfs (rw,relatime,attr2,inode64,noquota)
/dev/mapper/vg_root-lv_home on /home type xfs 
(rw,relatime,attr2,inode64,noquota)
/dev/mapper/vg_root-lv_log on /var/log type xfs 
(rw,relatime,attr2,inode64,noquota)
/dev/mapper/vg_root-lv_audit on /var/log/audit type xfs 
(rw,relatime,attr2,inode64,noquota)
lxcfs on /var/lib/lxcfs type fuse.lxcfs 
(rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=97964k,mode=700,uid=1000,gid=1000)

[Touch-packages] [Bug 1951142] [NEW] Windows change position after screen flashes in Wayland

[Patrick Garraud]

Public bug reported:

When using the Wayland session, the screen will sometimes randomly flash
(usually after opening an application). After the screen flashes, the
open windows will often end up in different positions or in different
monitors. Video of the issue is attached.

Expected Behavior: For the LibreOffice window to stay on the right
monitor and to not change size or position.

Actual Behavior: The LibreOffice window opens to the right after I open
Lollypop.

This issue doesn't exclusively happen while LibreOffice or when opening
Lollypop, however, opening Lollypop is one of the most predictable ways
to trigger the bug. The majority of the time, the bug occurs in the
middle of regular use without me triggering anything.


I'm using a dual monitor set-up, with a 2560X1080 monitor at 1x scaling hooked 
up to a 4K Hi-DPI laptop screen at 2x scaling.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 16 11:22:32 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 630 [1028:08ac]
   Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac]
InstallationDate: Installed on 2020-11-18 (362 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Precision 5530 2-in-1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2020
dmi.bios.release: 1.11
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.10
dmi.board.name: 02TH5P
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:br1.11:svnDellInc.:pnPrecision55302-in-1:pvr:sku08AC:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5530 2-in-1
dmi.product.sku: 08AC
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

** Attachment added: "Video of the bug occuring"
   
https://bugs.launchpad.net/bugs/1951142/+attachment/5541229/+files/Wayland%20Bug.webm

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

Title:
  Windows change position after screen flashes in Wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  When using the Wayland session, the screen will sometimes randomly
  flash (usually after opening an application). After the screen
  flashes, the open windows will often end up in different positions or
  in different monitors. Video of the issue is attached.

  Expected Behavior: For the LibreOffice window to stay on the right
  monitor and to not change size or position.

  Actual Behavior: The LibreOffice window opens to the right after I
  open Lollypop.

  This issue doesn't exclusively happen while LibreOffice or when
  opening Lollypop, however, opening Lollypop is one of the most
  predictable ways to trigger the bug. The majority of the time, the bug
  occurs in the middle of regular use without me triggering anything.

  
  I'm using a dual monitor set-up, with a 2560X1080 monitor at 1x scaling 
hooked up to a 4K Hi-DPI laptop screen at 2x scaling.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 16 11:22:32 2021
  DistUpgraded: Fresh install

[Touch-packages] [Bug 1938983] Re: missing modules after 5.11.0-25-generic update

[Juerg Haefliger]

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

** This bug has been marked a duplicate of bug 1939986
   Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads 
i915

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

Title:
  missing modules after 5.11.0-25-generic update

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

Bug description:
  After updating to kernel 5.11.0-25-generic wireless driver failed to 
recognize WiFi card.
  Possible reasons/symptoms:
  $ sudo update-initramfs -u -k all
  update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
  W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module 
i915
  W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for 
module i915
  update-initramfs: Generating /boot/initrd.img-5.8.0-63-generic

  $ lsb_release -a
  LSB Version:  core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  July2021
  Release:  20.04
  Codename: focal

  Workaround: connected Ethernet. (Inconvenient)

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


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

[Touch-packages] [Bug 989961] Re: no gmake symlink created

[Heinrich Schuchardt]

Package make-dfsg - 4.3-4.1ubuntu2 is available in ppa:xypron/merge-
from-debian

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

Title:
  no gmake symlink created

Status in make-dfsg package in Ubuntu:
  Triaged

Bug description:
  Some, albeit older or proprietary software, expects a gmake symlink
  for gnu make.  Can this be provided?

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


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

[Touch-packages] [Bug 1946213] Re: strongswan: Fail to build against OpenSSL 3.0

[Bug Watch Updater]

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

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

Title:
  strongswan: Fail to build against OpenSSL 3.0

Status in OpenSSL:
  Fix Released
Status in strongSwan:
  New
Status in openssl package in Ubuntu:
  New
Status in strongswan package in Ubuntu:
  New

Bug description:
  Hello,

  As part of a rebuild against OpenSSL3, this package failed to build on one or
  several architectures. You can find the details of the rebuild at 

  https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html

  or for the amd64 failed build, directly at

  
https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22099394/+files/buildlog_ubuntu-
  impish-amd64.strongswan_5.9.1-1ubuntu3.0~ssl3ppa1.1_BUILDING.txt.gz

  We're planning to transition to OpenSSL 3.0 for the 22.04 release, and 
consider
  this issue as blocking for this transition.

  You can find general migration informations at
  https://www.openssl.org/docs/manmaster/man7/migration_guide.html
  For your tests, you can build against libssl-dev as found in the PPA
  schopin/openssl-3.0.0

  The issue looks fixed upstream on master:
  
https://github.com/strongswan/strongswan/commit/72e5b3b7022ad14b245565a5aadcd097106af168

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


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

[Touch-packages] [Bug 1951018] Re: No ability to discern IPv4 vs IPv6 rules through Python

[Kevin Tate]

I now realize that I may have submitted this bug to the wrong location.
Should I submit this to the UFW source site (https://launchpad.net/ufw)
or is it alright to keep it here?

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

Title:
  No ability to discern IPv4 vs IPv6 rules through Python

Status in ufw package in Ubuntu:
  New

Bug description:
  Version: ufw 0.36
  Ubuntu Version: 20.04.3 LTS

  There doesn't appear to be a Python method for accessing IPv4 and IPv6
  rules in a distinguishable manner.

  In the source code (root/src/backend.py) there is an object that
  stores IPv4 and IPv6 rules in separate lists. Those lists are then
  accessed with the following method:

  def get_rules(self):
  '''Return list of all rules'''
  return self.rules + self.rules6

  The issue with this is that the returned list doesn't contain an
  indication of what IP version each item corresponds to and would
  display something like the following.

  1 allow 22/tcp
  2 allow 80
  3 allow 443
  4 allow 22/tcp
  5 allow 80
  6 allow 443

  I don't currently see a way to distinguish between IPv4 and IPv6 rules other 
than accessing the lists in the backend object directly (but I don't think this 
is best practice). E.g.:
  rules_ipv4 = backend.rules
  rules_ipv6 = backend.rules6

  One possible fix would be to add functions that return only the IPv4 or IPv6 
rules. E.g.:
  def get_rules_ipv4(self):
  '''Return list of all ipv4 rules'''
  return self.rules
  def get_rules_ipv6(self):
  '''Return list of all ipv6 rules'''
  return self.rules6

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


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

[Touch-packages] [Bug 1921518] Re: OpenSSL "double free" error

[Vladimir Sokolovsky]

The fix was verified for wget and curl.
Thanks a lot.

When these new packages will be added to "updates" repository?

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

Title:
  OpenSSL "double free" error

Status in openssl package in Ubuntu:
  Incomplete
Status in wget package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  Incomplete
Status in wget source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  openssl config file is being loaded twice, causing engines to be loaded twice 
if specified therein, causing double free errors and other strange behavior.

  [Test plan]
  Run the command of the package being tested in

  gdb  -ex "break CONF_modules_load_file" -ex "run" --args

  and make sure it only breaks one.

  Regression test:

  In default Ubuntu configuration, either no openssl configuration is provided, 
or it contains no settings that affect wget. This code path changes how/when 
openssl configuration is loaded and used by openssl. One should verify that:
  1) wget continues to work without openssl.cnf
  2) wget continues to work with stock ubuntu unmodified openssl.cnf
  3) wget continue to honor and use custom TLS settings that one may have 
specified in openssl.cnf (for example custom engine)

  
  [Where problems could occur]

  wget: This is an upstream change that changes initialization and is in
  use in later releases. Since it mostly removes an unneeded call to the
  load file function, a regression could be a config file being ignored,
  but it seems unlikely given the use in later releases

  
  [Original bug report]
  "double free" error is seen when using curl utility. Error is from 
libcrypto.so which is part of the OpenSSL package. This happens only when 
OpenSSL is configured to use a dynamic engine.

  OpenSSL version is 1.1.1f

  The issue is not encountered if
  http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead.

  OpenSSL can be configured to use a dynamic engine by editing the
  default openssl config file which is located at '/etc/ssl/openssl.cnf'
  on Ubuntu systems.

  On Bluefield systems, config diff to enable PKA dynamic engine, is as
  below:

  +openssl_conf = conf_section
  +
   # Extra OBJECT IDENTIFIER info:
   #oid_file  = $ENV::HOME/.oid
   oid_section= new_oids

  +[ conf_section ]
  +engines = engine_section
  +
  +[ engine_section ]
  +bf = bf_section
  +
  +[ bf_section ]
  +engine_id=pka
  +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so
  +init=0
  +

  engine_id above refers to dynamic engine name/identifier.
  dynamic_path points to the .so file for the dynamic engine.

  # curl -O https://tpo.pe/pathogen.vim

  double free or corruption (out)

  Aborted (core dumped)

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


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

[Touch-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915

[Juerg Haefliger]

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

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

Title:
  Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it
  loads i915

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  I can see that the linux-firmware is missing firmware files, in Ubuntu
  20.04.1 LTS, for initramfs, when it loads i915.

  Package: linux-firmware 1.187.15
  It contains the following files, for the module i915:
  i915/tgl_dmc_ver2_04.bin  2019-09-13  installed
  i915/tgl_dmc_ver2_06.bin  2020-03-04  installed
  i915/tgl_dmc_ver2_08.bin  2020-08-13  installed
  i915/tgl_guc_35.2.0.bin   2019-11-06  installed
  i915/tgl_huc_7.0.12.bin   2020-03-04  installed
  i915/tgl_huc_7.0.3.bin2019-11-06  installed

  Package: linux-firmware
  MUST at least contain the following files, for the module i915:
  i915/tgl_huc_7.5.0.bin2020-08-13  i915: Add HuC 
firwmare v7.5.0 for TGL
  as the module asks for it, during 'update-initramfs', to avoid:
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  But it COULD also contain : 
  i915/tgl_dmc_ver2_12.bin  2021-07-28  i915: Add v2.12 DMC for TGL
  i915/tgl_guc_49.0.1.bin   2020-11-24  i915: Add GuC firmware 
v49.0.1 for all platforms
  i915/tgl_guc_62.0.0.bin   2021-06-29  firmware/i915/guc: Add 
GuC v62.0.0 for all platforms
  i915/tgl_huc_7.9.3.bin2021-06-29  firmware/i915/guc: Add 
HuC v7.9.3 for TGL & DG1

  Source: 
  $ modprobe --show-depends --ignore-install i915
  ...
  insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko 

  $ modinfo -F firmware 
/lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko
  ...
  i915/tgl_dmc_ver2_08.bin
  i915/tgl_guc_35.2.0.bin
  i915/tgl_huc_7.5.0.bin

  Actual result:
  $ sudo update-initramfs -u
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  
  Expected result:
  No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915

  
  Info : INTEL Repository of firmware:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.15
  ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46
  Uname: Linux 5.10.0-1038-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  1699 F pulseaudio
   /dev/snd/pcmC0D0p:   chris  1699 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Aug 15 14:46:47 2021
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54
  InstallationDate: Installed on 2021-08-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem 
root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1038-oem N/A
   linux-backports-modules-5.10.0-1038-oem  N/A
   linux-firmware   1.187.15
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2021
  dmi.bios.release: 3.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.0.4
  dmi.board.name: 08607K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.0.4:bd07/16/2021:br3.0:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

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


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

[Touch-packages] [Bug 1950484] Re: Adding an admin user a Gnome Control Center should set the right groups

[Sebastien Bacher]

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  Adding an admin user a Gnome Control Center should set the right
  groups

Status in accountsservice package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Currently when installing Ubuntu , the default admin belongs to
  several essential groups :

  adm cdrom sudo dip plugdev lpadmin lxd sambashare

  
  But when adding a user from GCC , the new admin user will only belong to : 

  
  sudo 

  
  This leads that the second admin cannot add printers and so on...

  This is observed on a clean 20.04.3 install

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


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

[Touch-packages] [Bug 989961] Re: no gmake symlink created

[Heinrich Schuchardt]

** Tags added: fr-1860

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

Title:
  no gmake symlink created

Status in make-dfsg package in Ubuntu:
  Triaged

Bug description:
  Some, albeit older or proprietary software, expects a gmake symlink
  for gnu make.  Can this be provided?

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


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

[Touch-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915

[Juerg Haefliger]

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

Title:
  Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it
  loads i915

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  I can see that the linux-firmware is missing firmware files, in Ubuntu
  20.04.1 LTS, for initramfs, when it loads i915.

  Package: linux-firmware 1.187.15
  It contains the following files, for the module i915:
  i915/tgl_dmc_ver2_04.bin  2019-09-13  installed
  i915/tgl_dmc_ver2_06.bin  2020-03-04  installed
  i915/tgl_dmc_ver2_08.bin  2020-08-13  installed
  i915/tgl_guc_35.2.0.bin   2019-11-06  installed
  i915/tgl_huc_7.0.12.bin   2020-03-04  installed
  i915/tgl_huc_7.0.3.bin2019-11-06  installed

  Package: linux-firmware
  MUST at least contain the following files, for the module i915:
  i915/tgl_huc_7.5.0.bin2020-08-13  i915: Add HuC 
firwmare v7.5.0 for TGL
  as the module asks for it, during 'update-initramfs', to avoid:
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  But it COULD also contain : 
  i915/tgl_dmc_ver2_12.bin  2021-07-28  i915: Add v2.12 DMC for TGL
  i915/tgl_guc_49.0.1.bin   2020-11-24  i915: Add GuC firmware 
v49.0.1 for all platforms
  i915/tgl_guc_62.0.0.bin   2021-06-29  firmware/i915/guc: Add 
GuC v62.0.0 for all platforms
  i915/tgl_huc_7.9.3.bin2021-06-29  firmware/i915/guc: Add 
HuC v7.9.3 for TGL & DG1

  Source: 
  $ modprobe --show-depends --ignore-install i915
  ...
  insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko 

  $ modinfo -F firmware 
/lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko
  ...
  i915/tgl_dmc_ver2_08.bin
  i915/tgl_guc_35.2.0.bin
  i915/tgl_huc_7.5.0.bin

  Actual result:
  $ sudo update-initramfs -u
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  
  Expected result:
  No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915

  
  Info : INTEL Repository of firmware:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.15
  ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46
  Uname: Linux 5.10.0-1038-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  1699 F pulseaudio
   /dev/snd/pcmC0D0p:   chris  1699 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Aug 15 14:46:47 2021
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54
  InstallationDate: Installed on 2021-08-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem 
root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1038-oem N/A
   linux-backports-modules-5.10.0-1038-oem  N/A
   linux-firmware   1.187.15
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2021
  dmi.bios.release: 3.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.0.4
  dmi.board.name: 08607K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.0.4:bd07/16/2021:br3.0:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

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


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

[Touch-packages] [Bug 1921518] Re: OpenSSL "double free" error

[Julian Andres Klode]

I have done preliminary analysis of the grep and filed additional bugs
for

- bind9 and bind9-libs (LP: #1951097)
- freeradius (LP: #1951099)
- librabbitmq (LP: #1951102)

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

Title:
  OpenSSL "double free" error

Status in openssl package in Ubuntu:
  Incomplete
Status in wget package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  Incomplete
Status in wget source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  openssl config file is being loaded twice, causing engines to be loaded twice 
if specified therein, causing double free errors and other strange behavior.

  [Test plan]
  Run the command of the package being tested in

  gdb  -ex "break CONF_modules_load_file" -ex "run" --args

  and make sure it only breaks one.

  Regression test:

  In default Ubuntu configuration, either no openssl configuration is provided, 
or it contains no settings that affect wget. This code path changes how/when 
openssl configuration is loaded and used by openssl. One should verify that:
  1) wget continues to work without openssl.cnf
  2) wget continues to work with stock ubuntu unmodified openssl.cnf
  3) wget continue to honor and use custom TLS settings that one may have 
specified in openssl.cnf (for example custom engine)

  
  [Where problems could occur]

  wget: This is an upstream change that changes initialization and is in
  use in later releases. Since it mostly removes an unneeded call to the
  load file function, a regression could be a config file being ignored,
  but it seems unlikely given the use in later releases

  
  [Original bug report]
  "double free" error is seen when using curl utility. Error is from 
libcrypto.so which is part of the OpenSSL package. This happens only when 
OpenSSL is configured to use a dynamic engine.

  OpenSSL version is 1.1.1f

  The issue is not encountered if
  http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead.

  OpenSSL can be configured to use a dynamic engine by editing the
  default openssl config file which is located at '/etc/ssl/openssl.cnf'
  on Ubuntu systems.

  On Bluefield systems, config diff to enable PKA dynamic engine, is as
  below:

  +openssl_conf = conf_section
  +
   # Extra OBJECT IDENTIFIER info:
   #oid_file  = $ENV::HOME/.oid
   oid_section= new_oids

  +[ conf_section ]
  +engines = engine_section
  +
  +[ engine_section ]
  +bf = bf_section
  +
  +[ bf_section ]
  +engine_id=pka
  +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so
  +init=0
  +

  engine_id above refers to dynamic engine name/identifier.
  dynamic_path points to the .so file for the dynamic engine.

  # curl -O https://tpo.pe/pathogen.vim

  double free or corruption (out)

  Aborted (core dumped)

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


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

[Touch-packages] [Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18

[Alberto Mardegan]

Thanks Lukas! It's very likely that there are several issues in this
area, because while I can confirm that your latest image fixes the
reproducer I pasted before (in the Google cloud, too), the spread test
failure is still reproducible with the "tests/main/services-disabled-
kept-happy" test.

I need to have a closer look at this test case, to understand what exact
steps snapd is taking, and see if we can again find a reproducer without
involving snapd.

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

Title:
  systemd randomly fails to activate mount units in Ubuntu Core 18

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  Since a month or so, we've been seeing random failures in our snapd
  spread tests where systemd could not start the mount unit associated
  with a snap because of a failed dependency.

  The issue is described in the comments to PR
  https://github.com/snapcore/snapd/pull/10935, but I'll summarize it
  here.

  When starting a snap, snapd creates a mount unit to mount the snap's
  squashfs (the template is
  
https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205).
  The snapd asks systemd to reload the configuration, and starts the
  mount unit.

  The failure we've observed is that sometimes systemd decides to stop
  our mount unit (search for "Unmounting Mount unit for test-snapd-svc-
  flip-flop" in the attached log), and then tries to reactivate it
  again, and at that point it fails.

  When I asked for help, Lukas pointed out that the latest update
  contains a patch that is related to reload handling and mount units:
  
http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz
  (the patch itself is better visible at
  
https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656).
  When looking at the systemd git log, though, I noticed another patch
  that was applied shortly after this one, which also seems related but
  was not backported:
  
https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0

  Since the stopping of our mount unit happens immediately after a
  systemd reload, it actually seems very likely that the inclusion of
  f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what
  causes our woes (though, indeed, the issue is not reliably
  reproducible, so we cannot be sure).

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


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

[Touch-packages] [Bug 1946213] Re: strongswan: Fail to build against OpenSSL 3.0

[Bug Watch Updater]

** Changed in: strongswan
   Status: Unknown => New

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

Title:
  strongswan: Fail to build against OpenSSL 3.0

Status in OpenSSL:
  New
Status in strongSwan:
  New
Status in openssl package in Ubuntu:
  New
Status in strongswan package in Ubuntu:
  New

Bug description:
  Hello,

  As part of a rebuild against OpenSSL3, this package failed to build on one or
  several architectures. You can find the details of the rebuild at 

  https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html

  or for the amd64 failed build, directly at

  
https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22099394/+files/buildlog_ubuntu-
  impish-amd64.strongswan_5.9.1-1ubuntu3.0~ssl3ppa1.1_BUILDING.txt.gz

  We're planning to transition to OpenSSL 3.0 for the 22.04 release, and 
consider
  this issue as blocking for this transition.

  You can find general migration informations at
  https://www.openssl.org/docs/manmaster/man7/migration_guide.html
  For your tests, you can build against libssl-dev as found in the PPA
  schopin/openssl-3.0.0

  The issue looks fixed upstream on master:
  
https://github.com/strongswan/strongswan/commit/72e5b3b7022ad14b245565a5aadcd097106af168

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


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

[Touch-packages] [Bug 1921515] Re: `SyntaxError` when byte-compiling during `do-release-upgrade` to hirsute

[Marcel Waldvogel]

For me, this happened when installing `pypy3` on hirsute.

running pypy3 rtupdate hooks for 7.3
Failed to byte-compile 
/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py:   
File "/
usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", line 
436
def __init__(self, sourceslist=None, /, files=None):
 ^
SyntaxError: invalid syntax (expected ')')

The problem seems to be that `python3-software-properties` expects
Python>=3.8 (the `/` syntax only became available then, see
https://www.python.org/dev/peps/pep-0570/). However, pypy3 as packaged
with hirsute (7.3.5) only supports Python 3.7. Upgrading to pypy 7.3.6
(https://www.pypy.org/posts/2021/10/pypy-v736-release.html), announced
as supporting Python 3.8, probably would solve this problem.

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

Title:
  `SyntaxError` when byte-compiling during `do-release-upgrade` to
  hirsute

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  When performing a `do-release-upgrade -d` on my groovy system, I saw:

  Setting up python3-software-properties (0.99.8) ...
  Failed to byte-compile 
/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py:   
File 
"/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", 
line 436
  def __init__(self, sourceslist=None, /, files=None):
   ^
  SyntaxError: invalid syntax (expected ')')

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


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

[Touch-packages] [Bug 1921515] Re: `SyntaxError` when byte-compiling during `do-release-upgrade` to hirsute

[Launchpad Bug Tracker]

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

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

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

Title:
  `SyntaxError` when byte-compiling during `do-release-upgrade` to
  hirsute

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  When performing a `do-release-upgrade -d` on my groovy system, I saw:

  Setting up python3-software-properties (0.99.8) ...
  Failed to byte-compile 
/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py:   
File 
"/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", 
line 436
  def __init__(self, sourceslist=None, /, files=None):
   ^
  SyntaxError: invalid syntax (expected ')')

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


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

[Touch-packages] [Bug 1950461] Re: gnome-remote-desktop is not installed by default

[Daniel van Vugt]

I think these are the dependencies that are arguably too weak, causing
remote desktop to not work in minimal installs:

gnome-shell recommends gnome-remote-desktop
pipewire-bin recommends pipewire-media-session

** Changed in: gnome-shell (Ubuntu)
   Importance: Low => Wishlist

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Low => Wishlist

** Changed in: gnome-shell (Ubuntu)
   Status: Opinion => Triaged

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

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

** Summary changed:

- gnome-remote-desktop is not installed by default
+ gnome-remote-desktop is not installed in a minimal Ubuntu install

** Summary changed:

- gnome-remote-desktop is not installed in a minimal Ubuntu install
+ gnome-remote-desktop is not installed in a "minimal" Ubuntu install

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

Title:
  gnome-remote-desktop is not installed in a "minimal" Ubuntu install

Status in gnome-shell package in Ubuntu:
  Triaged
Status in pipewire package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 21.10 - minimal install on a fresh machine

  apt install vino

  Open the gnome settings dialog and go to the Sharing tab. I would
  expect to see the screen sharing slider but it is not there.

  Searching around I found a suggestion to use Ubunutu with Xorg but
  this makes no difference.

  This behaviour is also present in 21.04.

  I have put gnome-control-center as the package at fault as this is
  ultimately where I observe the issue but it may be that during the
  install of vino makes the gnome configuration change and this step is
  missed.

  I have enquired on askubuntu and reddit but have not received a
  response so decided to report this

  gnome-control-center 1:40.0-1ubuntu5 is installed
  vino 3.22.0-6ubuntu3

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


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

[Touch-packages] [Bug 1946213] Re: strongswan: Fail to build against OpenSSL 3.0

[Paride Legovini]

Issue #735 has been closed as it's actually an OpenSSL bug (and we
already have a task for that). I'm making this track #759 instead.

** Changed in: strongswan
   Status: New => Unknown

** Changed in: strongswan
 Remote watch: github.com/strongswan/strongswan/issues #753 => 
github.com/strongswan/strongswan/issues #759

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

Title:
  strongswan: Fail to build against OpenSSL 3.0

Status in OpenSSL:
  New
Status in strongSwan:
  Unknown
Status in openssl package in Ubuntu:
  New
Status in strongswan package in Ubuntu:
  New

Bug description:
  Hello,

  As part of a rebuild against OpenSSL3, this package failed to build on one or
  several architectures. You can find the details of the rebuild at 

  https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html

  or for the amd64 failed build, directly at

  
https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22099394/+files/buildlog_ubuntu-
  impish-amd64.strongswan_5.9.1-1ubuntu3.0~ssl3ppa1.1_BUILDING.txt.gz

  We're planning to transition to OpenSSL 3.0 for the 22.04 release, and 
consider
  this issue as blocking for this transition.

  You can find general migration informations at
  https://www.openssl.org/docs/manmaster/man7/migration_guide.html
  For your tests, you can build against libssl-dev as found in the PPA
  schopin/openssl-3.0.0

  The issue looks fixed upstream on master:
  
https://github.com/strongswan/strongswan/commit/72e5b3b7022ad14b245565a5aadcd097106af168

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


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

[Touch-packages] [Bug 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context

[Jean-Baptiste Lallement]

Verification

Mesa 21.0.3-0ubuntu0.3~20.04.4 has been tested on 2 systems and it fixes
the issue. Marking as verification-done.

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

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

Title:
  [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context

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

Bug description:
  [Description]
  This is a request to backport this fix from mesa 21.1 to focal-updates which 
is affecting users of WSL:

  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87

  This cached stale pointer is causing various chromium applications
  (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU
  is enabled in WSLg. We’re getting incredibly unlucky because a glx
  drawable is being freed and reallocated with exactly the same heap
  pointers during a resize, which is causing Mesa to think the new
  drawable is already fully initialized when binded to the context, but
  it is not true and only because the new drawable is matching the old
  stale pointer for the previously freed drawable… and as a result the
  context remain invalid and the app is unable to present.

  With the push of WDDMv3 drivers which expose vGPU in WSL, the number
  of users hitting this issue is increasing.

  [Test Case]
  On Windows 11 with WSLg and Ubuntu 20.04

  1. Verify that hardware acceleration is enable either with glxinfo -B or in 
edge with edge://gpu
  2. Install and launch chrome, edge or vscode
  3. Resize the windows repeatedly

  Verification:
  The app must not crash or hang.

  [What could go wrong]

  The patch resets two pointers to NULL in dri_unbind_context(), which
  is correct for that function and can't regress anything else.

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


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

[Touch-packages] [Bug 1946213] Re: strongswan: Fail to build against OpenSSL 3.0

[Paride Legovini]

With openssl 3.0.0-1ubuntu1~ppa2 the ed25519_fail issue is fixed, but we
then hit another (unrelated) test failure. I reported it upstream here:

https://github.com/strongswan/strongswan/issues/759


** Bug watch added: github.com/strongswan/strongswan/issues #759
   https://github.com/strongswan/strongswan/issues/759

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

Title:
  strongswan: Fail to build against OpenSSL 3.0

Status in OpenSSL:
  New
Status in strongSwan:
  New
Status in openssl package in Ubuntu:
  New
Status in strongswan package in Ubuntu:
  New

Bug description:
  Hello,

  As part of a rebuild against OpenSSL3, this package failed to build on one or
  several architectures. You can find the details of the rebuild at 

  https://people.canonical.com/~schopin/rebuilds/openssl-3.0.0-impish.html

  or for the amd64 failed build, directly at

  
https://launchpad.net/~schopin/+archive/ubuntu/openssl-3.0.0/+build/22099394/+files/buildlog_ubuntu-
  impish-amd64.strongswan_5.9.1-1ubuntu3.0~ssl3ppa1.1_BUILDING.txt.gz

  We're planning to transition to OpenSSL 3.0 for the 22.04 release, and 
consider
  this issue as blocking for this transition.

  You can find general migration informations at
  https://www.openssl.org/docs/manmaster/man7/migration_guide.html
  For your tests, you can build against libssl-dev as found in the PPA
  schopin/openssl-3.0.0

  The issue looks fixed upstream on master:
  
https://github.com/strongswan/strongswan/commit/72e5b3b7022ad14b245565a5aadcd097106af168

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


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