[Touch-packages] [Bug 1956833] Re: No GSS-SPNEGO support in jammy

[Bug Watch Updater]

** Changed in: cyrus-sasl2 (Debian)
   Status: New => Fix Released

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

Title:
  No GSS-SPNEGO support in jammy

Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  In jammy:
  root@j1:~# saslpluginviewer | head | grep SPNEGO
  root@j1:~# 

  Confirming against a windows 2016 active directory server, fully patched:
  root@j1:~# ldapwhoami -Y GSS-SPNEGO
  ldap_sasl_interactive_bind: Unknown authentication method (-6)
  additional info: SASL(-4): no mechanism available: No worthy mechs 
found

  
  gssapi (kerberos) works:
  root@j1:~# ldapwhoami -Y GSSAPI
  SASL/GSSAPI authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

  root@j1:~# klist
  Ticket cache: FILE:/tmp/krb5cc_0
  Default principal: administra...@internal.example.fake

  Valid starting ExpiresService principal
  01/08/22 22:31:48  01/09/22 08:31:48  
krbtgt/internal.example.f...@internal.example.fake
  renew until 01/09/22 22:31:45
  01/08/22 22:34:53  01/09/22 08:31:48  
ldap/win-kriet1e5elo.internal.example.fake@
  renew until 01/09/22 22:31:45
  Ticket server: 
ldap/win-kriet1e5elo.internal.example.f...@internal.example.fake

  
  In focal, GSS-SPNEGO works:
  root@f1:~# saslpluginviewer | head | grep SPNEGO
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
EXTERNAL NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS

  Confirming with ldapwhoami:
  root@f1:~# ldapwhoami -Y GSS-SPNEGO
  SASL/GSS-SPNEGO authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

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


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

[Touch-packages] [Bug 1957744] [NEW] Unable to set correct resolutions on virtual displays

[Khaled El Mously]

Public bug reported:

See
https://canonical.lightning.force.com/lightning/r/Case/5004K09qFamQAE/view
for more info

** Affects: linux-oracle (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-oracle (Ubuntu Hirsute)
 Importance: Undecided
 Status: New

** Affects: linux-oracle (Ubuntu Impish)
 Importance: Undecided
 Status: New

** Also affects: linux-oracle (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: klibc (Ubuntu)

** Also affects: linux-oracle (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: linux-oracle (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

Title:
  Unable to set correct resolutions on virtual displays

Status in linux-oracle package in Ubuntu:
  New
Status in linux-oracle source package in Hirsute:
  New
Status in linux-oracle source package in Impish:
  New

Bug description:
  See
  https://canonical.lightning.force.com/lightning/r/Case/5004K09qFamQAE/view
  for more info

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


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

[Touch-packages] [Bug 1950872] Re: package libpam0g:amd64 1.3.1-5ubuntu4.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess was killed by signal (Trace/b

[Launchpad Bug Tracker]

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

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

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

Title:
  package libpam0g:amd64 1.3.1-5ubuntu4.3 failed to install/upgrade:
  installed libpam0g:amd64 package post-installation script subprocess
  was killed by signal (Trace/breakpoint trap), core dumped

Status in pam package in Ubuntu:
  Expired

Bug description:
  just crash

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam0g:amd64 1.3.1-5ubuntu4.3
  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.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Nov 13 18:55:15 2021
  DpkgTerminalLog:
   Preparing to unpack .../libpam0g_1.3.1-5ubuntu4.3_amd64.deb ...
   Unpacking libpam0g:amd64 (1.3.1-5ubuntu4.3) over (1.3.1-5ubuntu4.2) ...
   Setting up libpam0g:amd64 (1.3.1-5ubuntu4.3) ...
   dpkg: error processing package libpam0g:amd64 (--configure):
installed libpam0g:amd64 package post-installation script subprocess was 
killed by signal (Trace/breakpoint trap), core dumped
  DuplicateSignature:
   package:libpam0g:amd64:1.3.1-5ubuntu4.3
   Setting up libpam0g:amd64 (1.3.1-5ubuntu4.3) ...
   dpkg: error processing package libpam0g:amd64 (--configure):
installed libpam0g:amd64 package post-installation script subprocess was 
killed by signal (Trace/breakpoint trap), core dumped
  ErrorMessage: installed libpam0g:amd64 package post-installation script 
subprocess was killed by signal (Trace/breakpoint trap), core dumped
  InstallationDate: Installed on 2021-11-13 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: pam
  Title: package libpam0g:amd64 1.3.1-5ubuntu4.3 failed to install/upgrade: 
installed libpam0g:amd64 package post-installation script subprocess was killed 
by signal (Trace/breakpoint trap), core dumped
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1957160] Re: BlueZ release 5.63

[Daniel van Vugt]

** CVE removed: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2021-41229

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

Title:
  BlueZ release 5.63

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  http://www.bluez.org/release-of-bluez-5-63/

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz

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


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

[Touch-packages] [Bug 1957160] Re: BlueZ release 5.63

[Launchpad Bug Tracker]

This bug was fixed in the package bluez - 5.63-0ubuntu1

---
bluez (5.63-0ubuntu1) jammy; urgency=medium

  * New upstream release 5.63 (LP: #1957160):
- Fix issue with storing IRK causing invalid read access.
- Fix issue with disconnecting due to GattCharacteristic1.MTU.
- Add support for Device{Found,Lost} of advertising monitoring.
  * Drop upstreamed patches:
- 0001-obexd-plugins-import-PBAP-ebook-support-from-upstrea.patch
- 0001-obexd-plugins-port-ebook-support-to-the-latest-EDS.patch
- CVE-2021-41229.patch
  * Refreshed patches:
- allow-using-obexd-without-systemd-in-the-user-sessio.patch

 -- Daniel van Vugt   Wed, 12 Jan 2022
18:28:06 +0800

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-41229

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

Title:
  BlueZ release 5.63

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  http://www.bluez.org/release-of-bluez-5-63/

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz

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


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

[Touch-packages] [Bug 1957181] Re: Xorg freeze

[Daniel van Vugt]

Thanks for the bug report.

It sounds like GNOME (in the mutter component) has frozen. When this
happens the cursor will still move because it is managed by the Xorg
process, but the screen contents are managed by the gnome-shell process.

Please try removing DisplayLink from the equation by unplugging your
dock or any other USB display adapter. Does the bug still occur using
only the laptop screen?

** Tags added: displaylink evdi

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

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

** Summary changed:

- Xorg freeze
+ Screen freeze

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

Title:
  Screen freeze

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When having more than one window open, e.g. Firefox and a terminal and
  then to swap between the two. The clicking with the mouse stops
  working but it still moves. For instance when I hover over text or not
  the cursor does not change. Sometimes I can still click or select text
  in the original window but the coordinates of the mouse are not where
  the cursor is displayed. Sometimes the keyboard dies too e.g. Alt+F2
  does not work. Killing XOrg (if possible) seems to revert things to a
  working state.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  Uname: Linux 5.4.0-92-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 12 15:24:16 2022
  DistUpgraded: 2020-09-07 08:54:13,457 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 1.7.0, 4.15.0-70-generic, x86_64: installed
   evdi, 1.7.0, 5.4.0-91-generic, x86_64: installed
   evdi, 1.7.0, 5.4.0-92-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Today
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225c]
  InstallationDate: Installed on 2019-02-13 (1063 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KGS5DU00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic 
root=UUID=c1172559-29d0-4c7c-bfab-574068d6d5cc ro quiet 
splash,psmouse.synaptics_intertouch=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-09-07 (492 days ago)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 10/13/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET75W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS5DU00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS5DU00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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/mutter/+bug/1957181/+subscriptions


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

[Touch-packages] [Bug 1861408] Re: firefox apparmor messages

[Launchpad Bug Tracker]

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

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

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

Title:
  firefox apparmor messages

Status in apparmor package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
  19.3.

  i see there is newer ubuntu version in
  
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
  , 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
  apparmor.

  i have not found a page for firefox bugs in linux mint sites, so i
  belive i should report here. but i have also asked about that in linux
  mint's irc and then github.

  i have enabled apparmor for firefox and see these types of messages in
  syslog:

  Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
  pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")

  Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5525.077960] audit: type=1400 audit(1580226276.440:27):
  apparmor="DENIED" operation="capable"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
  comm="firefox" capability=21  capname="sys_admin"

  Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/RealtimeKit1"
  interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
  name="org.freedesktop.RealtimeKit1" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
  member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/Private/RemoteVolumeMonitor"
  interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
  mask="send" name=":1.35" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="ListMounts2" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="LookupMount" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
  pid=15948 comm="/usr/lib/firefox/firefox "
  label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/hostname1"
  interface="org.freedesktop.DBus.Properties" member="GetAll"
  mask="send" name=":1.120" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
  peer_label="unconfined"

  Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
  member="Change" mask="send" name="ca.desrt.dconf" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
  peer_label="unconfined"

  Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
  [10131.880788] audit: type=1400 audit(1580237490.777:123):
  apparmor="DENIED" operation="open"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
  name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720
  comm="firefox" requested_mask="wrc" denied_mask="wrc" fsuid=1000
  ouid=1000

  

[Touch-packages] [Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 247.3-3ubuntu3.7

---
systemd (247.3-3ubuntu3.7) hirsute-security; urgency=medium

  * SECURITY UPDATE: systemd-tmpfiles could be made to crash.
- d/p/rm-rf-refactor-rm-rf-children-split-out-body-of-directory.patch:
  Backport upstream patch from PR#20173
- d/p/rm-rf-optionally-fsync-after-removing-directory-tree.patch:
  Backport upstream patch required for CVE-2021-3997 patches
- d/p/CVE-2021-3997-1.patch: Backport upstream patch to refactor
  rm_rf_children_inner()
- d/p/CVE-2021-3997-2.patch: Backport upstream patch to refactor
  rm_rf()
- d/p/CVE-2021-3997-3.patch: Backport upstream patch to loop over
  nested directories instead of using recursion
- CVE-2021-3997

 -- Alex Murray   Mon, 10 Jan 2022 14:56:34
+1030

** Changed in: systemd (Ubuntu Hirsute)
   Status: Won't Fix => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3997

** Changed in: systemd (Ubuntu Focal)
   Status: Won't Fix => Fix Released

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  Won't Fix
Status in systemd package in Ubuntu:
  Won't Fix
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd source package in Impish:
  Won't Fix

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and 
kernel 5.13, or kernel with this patch backported:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

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


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

[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 245.4-4ubuntu3.15

---
systemd (245.4-4ubuntu3.15) focal-security; urgency=medium

  * SECURITY UPDATE: systemd-tmpfiles could be made to crash.
- d/p/rm-rf-refactor-rm-rf-children-split-out-body-of-directory.patch:
  Backport upstream patch from PR#20173
- d/p/rm-rf-optionally-fsync-after-removing-directory-tree.patch:
  Backport upstream patch required for CVE-2021-3997 patches
- d/p/CVE-2021-3997-1.patch: Backport upstream patch to refactor
  rm_rf_children_inner()
- d/p/CVE-2021-3997-2.patch: Backport upstream patch to refactor
  rm_rf()
- d/p/CVE-2021-3997-3.patch: Backport upstream patch to loop over
  nested directories instead of using recursion
- CVE-2021-3997

 -- Alex Murray   Mon, 10 Jan 2022 15:26:38
+1030

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

Title:
  systemd-resolve segfault

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * systemd-resolved stops replying to clients on the local LAN.
   * logging segfault crashes in dmesg:
  [836786.046514] systemd-resolve[872009]: segfault at 399 ip 
0399 sp 7ffd7959a6d8 error 14 in 
systemd-resolved[556398695000+9000]
  [836786.046524] Code: Bad RIP value.
  [840887.303994] traps: systemd-resolve[877019] general protection fault 
ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4]
  [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa 
sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4]
  [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 
00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 
90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8

   * The upload backports the upstream fix
  (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute.

  [Test Plan]

   * Setup /etc/systemd/resolved.conf:
  [Resolve]
  DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 
9.9.9.9#dns.quad9.net
  DNSSEC=yes
  DNSOverTLS=opportunistic
  MulticastDNS=no
  LLMNR=no
  Cache=yes
  DNSStubListener=yes
  Domains=~.

   * wait for ~24-48 hours and observe if any crash happens

  [Where problems could occur]

   * Any regression would likely cause crashes in systemd-resolved,
  making it unresponsive to DNS network name requests to local
  applications.

  [Other Info]
   
   * Reported upstream: https://github.com/systemd/systemd/issues/18427
   * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832

  === Original description ===

  
  systemd-resolve keep crashing and it is very annoying as sometimes it 
severely interrupt normal dns resolving.

  Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6
  Typical error in dmesg:
  systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 
7ffe2fd0b758 error 15

  apport hints me that problem is related to mdns

  #3  0x7f3e903c2f11 in sd_event_dispatch () from
  /lib/systemd/libsystemd-shared-245.so

  It might be (or not) related that some hosts with mdns in my network
  have ipv6 enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119
  Uname: Linux 5.4.0-75-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  1 08:22:51 2021
  InstallationDate: Installed on 2018-12-05 (938 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic 
root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X399-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  

[Touch-packages] [Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 245.4-4ubuntu3.15

---
systemd (245.4-4ubuntu3.15) focal-security; urgency=medium

  * SECURITY UPDATE: systemd-tmpfiles could be made to crash.
- d/p/rm-rf-refactor-rm-rf-children-split-out-body-of-directory.patch:
  Backport upstream patch from PR#20173
- d/p/rm-rf-optionally-fsync-after-removing-directory-tree.patch:
  Backport upstream patch required for CVE-2021-3997 patches
- d/p/CVE-2021-3997-1.patch: Backport upstream patch to refactor
  rm_rf_children_inner()
- d/p/CVE-2021-3997-2.patch: Backport upstream patch to refactor
  rm_rf()
- d/p/CVE-2021-3997-3.patch: Backport upstream patch to loop over
  nested directories instead of using recursion
- CVE-2021-3997

 -- Alex Murray   Mon, 10 Jan 2022 15:26:38
+1030

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  Won't Fix
Status in systemd package in Ubuntu:
  Won't Fix
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd source package in Impish:
  Won't Fix

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and 
kernel 5.13, or kernel with this patch backported:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

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


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

[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 247.3-3ubuntu3.7

---
systemd (247.3-3ubuntu3.7) hirsute-security; urgency=medium

  * SECURITY UPDATE: systemd-tmpfiles could be made to crash.
- d/p/rm-rf-refactor-rm-rf-children-split-out-body-of-directory.patch:
  Backport upstream patch from PR#20173
- d/p/rm-rf-optionally-fsync-after-removing-directory-tree.patch:
  Backport upstream patch required for CVE-2021-3997 patches
- d/p/CVE-2021-3997-1.patch: Backport upstream patch to refactor
  rm_rf_children_inner()
- d/p/CVE-2021-3997-2.patch: Backport upstream patch to refactor
  rm_rf()
- d/p/CVE-2021-3997-3.patch: Backport upstream patch to loop over
  nested directories instead of using recursion
- CVE-2021-3997

 -- Alex Murray   Mon, 10 Jan 2022 14:56:34
+1030

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3997

** Changed in: systemd (Ubuntu Focal)
   Status: Confirmed => Fix Released

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

Title:
  systemd-resolve segfault

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * systemd-resolved stops replying to clients on the local LAN.
   * logging segfault crashes in dmesg:
  [836786.046514] systemd-resolve[872009]: segfault at 399 ip 
0399 sp 7ffd7959a6d8 error 14 in 
systemd-resolved[556398695000+9000]
  [836786.046524] Code: Bad RIP value.
  [840887.303994] traps: systemd-resolve[877019] general protection fault 
ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4]
  [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa 
sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4]
  [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 
00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 
90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8

   * The upload backports the upstream fix
  (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute.

  [Test Plan]

   * Setup /etc/systemd/resolved.conf:
  [Resolve]
  DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 
9.9.9.9#dns.quad9.net
  DNSSEC=yes
  DNSOverTLS=opportunistic
  MulticastDNS=no
  LLMNR=no
  Cache=yes
  DNSStubListener=yes
  Domains=~.

   * wait for ~24-48 hours and observe if any crash happens

  [Where problems could occur]

   * Any regression would likely cause crashes in systemd-resolved,
  making it unresponsive to DNS network name requests to local
  applications.

  [Other Info]
   
   * Reported upstream: https://github.com/systemd/systemd/issues/18427
   * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832

  === Original description ===

  
  systemd-resolve keep crashing and it is very annoying as sometimes it 
severely interrupt normal dns resolving.

  Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6
  Typical error in dmesg:
  systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 
7ffe2fd0b758 error 15

  apport hints me that problem is related to mdns

  #3  0x7f3e903c2f11 in sd_event_dispatch () from
  /lib/systemd/libsystemd-shared-245.so

  It might be (or not) related that some hosts with mdns in my network
  have ipv6 enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119
  Uname: Linux 5.4.0-75-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  1 08:22:51 2021
  InstallationDate: Installed on 2018-12-05 (938 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic 
root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X399-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Touch-packages] [Bug 1944436] Re: Please backport support for "close_range" syscall

[Dan Nicholson]

This causes an issue when using glib's gspawn APIs under libseccomp on
impish. It uses close_range to set CLOEXEC on some open file descriptors
and rightfully checks for ENOSYS. However, since seccomp doesn't know
about the syscall that becomes EPERM and it skips setting CLOEXEC
assuming there was a legit error in close_range. Eventually this means
that the process run by gspawn hangs because nothing is closing the file
descriptor as expected.

Debian has been shipping this backported to bullseye for a while -
https://salsa.debian.org/debian/libseccomp/-/blob/debian/bullseye/debian/patches/syscalls_add_close_range_syscall.patch.

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

Title:
  Please backport support for "close_range" syscall

Status in libseccomp package in Ubuntu:
  New

Bug description:
  Please backport support for the "close_range" syscall .. may be as
  simple as cherrypicking

  
https://github.com/seccomp/libseccomp/commit/01e5750e7c84bb14e5a5410c924bed519209db06

  from upstream. I've hit problems running buildah in a systemd-nspawn
  container, but this will probably affect people trying to run modern
  code in other container systems as well, e.g. docker.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libseccomp2 2.5.1-1ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
  Uname: Linux 5.4.0-84-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Xpra
  Date: Tue Sep 21 15:10:54 2021
  InstallationDate: Installed on 2017-01-08 (1717 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libseccomp
  UpgradeStatus: Upgraded to focal on 2021-09-02 (19 days ago)

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


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

[Touch-packages] [Bug 1957199] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[Stefano Rivera]

eric should have been upgraded before python3.8 configured

The old eric was not compatible with python3.8.

Either way, the failed byte-compilation of that file shouldn't have
crashed the postinst.

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

Title:
  package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in eric package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New

Bug description:
  failure when trying to upgrade to Ubuntu 20

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
  Uname: Linux 4.15.0-166-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jan 12 11:28:01 2022
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2015-08-26 (2330 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to focal on 2022-01-12 (0 days ago)

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


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

[Touch-packages] [Bug 1957199] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[Stefano Rivera]

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

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

Title:
  package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in eric package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New

Bug description:
  failure when trying to upgrade to Ubuntu 20

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
  Uname: Linux 4.15.0-166-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jan 12 11:28:01 2022
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2015-08-26 (2330 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to focal on 2022-01-12 (0 days ago)

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


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

[Touch-packages] [Bug 1957711] [NEW] Switching users causes system crash

[GB]

Public bug reported:

Ubuntu 21.10

gdm3:
  Installed: 41~rc-0ubuntu2
  Candidate: 41~rc-0ubuntu2
  Version table:
 *** 41~rc-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status

Steps to reproduce:

1. Log in as any user
2. In the top right of the screen, click the power icon (⏻)
3. Select [Power Off/Log Out]
4. Select [Switch User]
5. Select any user that is NOT the user which is still currently logged in
6. Operating system is now frozen, mouse and keyboard don't respond, and user 
is never logged in.
7. Pressing [CTRL] + [ALT] + [DEL] appears to cause the system to crash

Apport.log: https://pastebin.com/srFwgfAh

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

** Attachment added: "Crash log"
   
https://bugs.launchpad.net/bugs/1957711/+attachment/5553637/+files/gdm3.0.crash

** Package changed: apport (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  Switching users causes system crash

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Ubuntu 21.10

  gdm3:
Installed: 41~rc-0ubuntu2
Candidate: 41~rc-0ubuntu2
Version table:
   *** 41~rc-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status

  Steps to reproduce:

  1. Log in as any user
  2. In the top right of the screen, click the power icon (⏻)
  3. Select [Power Off/Log Out]
  4. Select [Switch User]
  5. Select any user that is NOT the user which is still currently logged in
  6. Operating system is now frozen, mouse and keyboard don't respond, and user 
is never logged in.
  7. Pressing [CTRL] + [ALT] + [DEL] appears to cause the system to crash

  Apport.log: https://pastebin.com/srFwgfAh

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


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

[Touch-packages] [Bug 1955347] Re: rsync works bad with encfs now

[Athos Ribeiro]

Hi Micouin,

The bug you linked does include a patch which is available in focal
(20.04). This means that the error you are seing is indeed caused by a
IOERR_GENERAL error. As for

> Why before rsync and encfs worked well together and not now?

would you mind describing which versions of both rsync and encfs you
were using when the previous behavior was observed? Was that still in
focal as well?

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

Title:
  rsync works bad with encfs now

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  I think rsync works bad with encfs now.

  When root uses it, rsync cannot read a directory encrypted with encfs
  by a user. More precisely, it cannot read the mounted directory, the
  virtual one where the user can read the datas.

  Until now there was only a warning like this
  "rsync: readlink_stat("/home/claude/Documents_chiffres") failed:
  Permission denied (13)"
  and the software went on working (only ignoring the content of the mounted 
directory and of course without saving this content)

  But recently there is this more:
  "IO error encountered -- skipping file deletion"
  and because of this "skipping file deletion", the software can't work 
normally. The destination gets bigger more and more because the deleted files 
in the source are not deleted in the destination.

  Thanks for reading me.
  rsync 3.1.3-8ubuntu0.1
  Description:Ubuntu 20.04.3 LTS
  Release:20.04

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


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

[Touch-packages] [Bug 1957104] Re: updating openssh-server fails, because port 22 is in use by systemd

[Athos Ribeiro]

Hi Thomas,

Thank you for taking the time to file a bug report.

The systemd service is indeed restarted throughout the package upgrade
process. This means that sshd is supposed to halt (and cease listening
on port 22) before the service is started again.

How are you starting the ssh server? Would you mind providing your
configuration file as well (make sure there is no sensitive data being
shared if you decide to do so). Providing logs will also help us
identify the issue you have been experiencing.

As for the second issue reported, regarding creation of the /run/sshd
directory when starting the service through systemd, this is actually
performed through the RuntimeDirectory directive in the ssh unit files.

Finally, would you be able to provide a reproducer for the issue?

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

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

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

Title:
  updating openssh-server fails, because port 22 is in use by systemd

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  openssh-server tries to restart itself, but openssh-server reports
  port 22 in use. This is true: systemd has taken port 22 to start sshd
  if one connects to port 22.

  two solutions:
  1. dont start sshd after installing.
 configure it without starting it afterwards.
  2. stop systemd listening on port 22
 before starting sshd, then start sshd,
 terminate it after configuring, then
 start systemd listening on port 22 again.

  Second problem:
  starting ssh.service does not check if "/run/sshd" exists. This directory has 
to be created before sshd is started. Unclear if this is an error with sshd not 
creating this directory before dropping privileges or if this has to be done 
once while installing. IMHO the first is the case.

  
  Workaround:
  systemctl stop ssh.service
  systemctl disable ssh.service
  apt upgrade
  systemctl enable ssh.service
  killall sshd
  mkdir /run/sshd
  systemctl start ssh.service

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: openssh-server 1:8.4p1-6ubuntu2.1
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Tue Jan 11 19:11:47 2022
  InstallationDate: Installed on 2021-08-18 (146 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with 
exit code 255: Missing privilege separation directory: /run/sshd
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1903567] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@447:parse_arguments:print_usage:_print_message

[Brian Murray]

** Changed in: apport (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

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

Title:
  
/usr/share/apport/apport:AttributeError:/usr/share/apport/apport@447:parse_arguments:print_usage:_print_message

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Xenial:
  Won't Fix
Status in apport source package in Bionic:
  Confirmed

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

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


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

[Touch-packages] [Bug 1867204] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:/usr/share/apport/whoopsie-upload-all@170:collect_info:process_report

[Brian Murray]

A more recent version of this bucket can be found here and here:

https://errors.ubuntu.com/problem/3adc63930455e99063ec1f77bf461d975492e9b4
https://errors.ubuntu.com/problem/6e66a508ca49b0dc586b3db41a71401cc660271f

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:FileNotFoundError:/usr/share/apport/whoopsie-upload-
  all@170:collect_info:process_report

Status in apport package in Ubuntu:
  New
Status in apport source package in Focal:
  New

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

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


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

[Touch-packages] [Bug 1947800] Re: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:r

[Brian Murray]

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

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

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:zlib.error:/usr/share/apport/whoopsie-upload-
  
all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Impish:
  Confirmed
Status in apport source package in Jammy:
  Confirmed

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

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


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

[Touch-packages] [Bug 1677781] Re: Missing dep8 tests

[Athos Ribeiro]

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: New => Triaged

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

Title:
  Missing dep8 tests

Status in cyrus-sasl2 package in Ubuntu:
  Triaged

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source cyrus-sasl2 zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/cyrus-sasl2
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3XaTAAoJEIP8BxPaZgwlJr8P/j8yn8mXWnAIiXUgHX7jBIGj
  JuMQGO5wwcfHRxOwJEOlsO/SIATUN1L1BB84anP7Bp4cfLqXonF8eKFPkEotwaf1
  3wADCH98EwLuSyJOaKXsTQHppAKdJ6UEW4jHvfhYizenEWssPfCQdg68LSGZ2enR
  wD9ZhZgjwJIpLbqDTp7ygklR0htf4ZAFq/vIcyLykT6qagVE3xC8SAgd+7tb/fYe
  4PYfqgGso/qpL0v6JL+YkCKH/aiMYV+HD45o1NcUbGdoiuUa9jpeYSSTP/9OgWpY
  nALDXe/dJZT/wz5Zv0cy6sGRh7gtjVqI0608WAM00Jp8CmFX60z4yrq/3t37wKbz
  iDQF4HyltqfCNF5oQ6xva9xAq/c2tyP8nBHzQ+ZtH/o1hyS/JdgoR38OojldyUc5
  WzcTFL+h612ZVZVNm4lqBpg/0dpEkwXTE9KczyB5kSr5VVz0WXtjU5wFxKMdZpr5
  Gq9uM+fHU4YHQqfGGZxmHFOgz7tCAyEsZEzpnPiYvoSksj3tJMkQG7FbIISltort
  CBAwLIt1hLR9g4T3p0e4ipCJf6kL/yZR3kMGhsjbDe012bTaC8ZeLG7VYmWkBaxY
  ieFMZIxmGgCq7KjDfNPh9JEmCtNgenkEOu6BszZK+gwmhL/AxVuuNRdd5OeBGy3G
  WY9JzBOc6MUi46Hh9ZN5
  =szTz
  -END PGP SIGNATURE-

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


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

[Touch-packages] [Bug 1952591] Re: Please merge kmod 29-1 (main) from Debian unstable (main)

[Brian Murray]

I uploaded this after modifying the changelog to reference this bug
number.

 $ dput kmod_29-1ubuntu1_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: /tmp/pkgs/jammy/kmod/kmod_29-1ubuntu1_source.changes: Valid signature from 
1E918B66765B3E31
Checking signature on .dsc
gpg: /tmp/pkgs/jammy/kmod/kmod_29-1ubuntu1.dsc: Valid signature from 
1E918B66765B3E31
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading kmod_29-1ubuntu1.dsc: done.
  Uploading kmod_29.orig.tar.xz: done.
  Uploading kmod_29-1ubuntu1.debian.tar.xz: done.  
  Uploading kmod_29-1ubuntu1_source.buildinfo: done.
  Uploading kmod_29-1ubuntu1_source.changes: done.
Successfully uploaded packages.


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

** Changed in: kmod (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Tags added: fr-1857

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

Title:
  Please merge kmod 29-1 (main) from Debian unstable (main)

Status in kmod package in Ubuntu:
  In Progress

Bug description:
* Merge from Debian unstable. Remaining changes:
   
  - Enable testsuite during build.  
   
  - Build with zstd compression enabled.
   
  - Install ubuntu-specific depmod.d and modprobe.d contents.

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


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

[Touch-packages] [Bug 1957455] [NEW] Failure connecting to ap setup with a mode

[Paul Larson]

Public bug reported:

One of the tests we run for the network manager snap uncovered this
problem on uc18 with network-manager 1.10 snap, but I've also been able
to reproduce it in the previous snap version, as well as with core20 and
with focal.

On a laptop with intel wifi card, we installed a fresh image (see above) and 
network-manager snap or deb as appropriate.  The most straightforward way to 
run the test we are using, for example with Ubuntu core 18:
$ sudo snap install checkbox --devmode --channel=uc18/stable

After it is installed:
$ cd /snap/checkbox18/current/providers/plainbox-provider-checkbox/bin
$ ./wifi_nmcli_test.py ap wlan0 a

NB: in the above example, replace wlan0 with the correct device if it's
something else, and replace uc18 track and checkbox18 directory as
appropriate, if you are using uc20 or focal use the uc20 track.

This test uses network-manager to create an ap, then tries to connect to
it.

Output with uc18: https://pastebin.canonical.com/p/CBFqj2Mcgr/
Output with focal: https://pastebin.canonical.com/p/4Shm6pWzpM/

This test can also run in bg mode, and works fine with that. So the test
itself works, and network-manager seems to be able to create an AP in
some mode, but it doesn't seem to work with a

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Failure connecting to ap setup with a mode

Status in network-manager package in Ubuntu:
  New

Bug description:
  One of the tests we run for the network manager snap uncovered this
  problem on uc18 with network-manager 1.10 snap, but I've also been
  able to reproduce it in the previous snap version, as well as with
  core20 and with focal.

  On a laptop with intel wifi card, we installed a fresh image (see above) and 
network-manager snap or deb as appropriate.  The most straightforward way to 
run the test we are using, for example with Ubuntu core 18:
  $ sudo snap install checkbox --devmode --channel=uc18/stable

  After it is installed:
  $ cd /snap/checkbox18/current/providers/plainbox-provider-checkbox/bin
  $ ./wifi_nmcli_test.py ap wlan0 a

  NB: in the above example, replace wlan0 with the correct device if
  it's something else, and replace uc18 track and checkbox18 directory
  as appropriate, if you are using uc20 or focal use the uc20 track.

  This test uses network-manager to create an ap, then tries to connect
  to it.

  Output with uc18: https://pastebin.canonical.com/p/CBFqj2Mcgr/
  Output with focal: https://pastebin.canonical.com/p/4Shm6pWzpM/

  This test can also run in bg mode, and works fine with that. So the
  test itself works, and network-manager seems to be able to create an
  AP in some mode, but it doesn't seem to work with a

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


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

[Touch-packages] [Bug 1957194] Re: resume from hibernation broken when resume image is autodetected another case

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
  resume from hibernation broken when resume image is autodetected
  another case

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  My issue very similar to
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297

  I am assuming that the code at about line 162 in
  `/usr/share/initramfs-tools/init` like that:

  ```
  resume=*)
  RESUME="${x#resume=}"
  case $RESUME in
  UUID=*)
  RESUME="/dev/disk/by-uuid/${RESUME#UUID=}"
  esac
  ;;
  ``` 

  Only works if user wants to set resume partition as `UUID=some` at
  file like `/etc/initramfs-tools/conf.d/resume`. But in the case when
  initramfs hook resume automatically save `UUID=some` in initrd
  `conf/conf.d/zz-resume-auto` file it doesn't matter. Including for
  operate `DEV=$(readlink -f "$resume")` correctly in
  `/usr/share/initramfs-tools/scripts/local-premount/resume`

  Therefore I decide to add similar code to `/usr/share/initramfs-
  tools/scripts/local-premount/resume` to fix an issue with resuming.

  See a patch in attachment.

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


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

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

[Dan Streetman]

** Changed in: systemd (Ubuntu Impish)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

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

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

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

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Impish:
  New
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [impact]

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

  [test case]

  TBD

  [regression potential]

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

  [scope]

  needed only for i and later

  f and earlier default to cgroupv1

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


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

[Touch-packages] [Bug 1934147] Re: systemd leaks abandoned session scopes

[Dan Streetman]

per comment 5, released for impish

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

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

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

Title:
  systemd leaks abandoned session scopes

Status in snapd:
  Invalid
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [impact]

  systemd may leak sessions, leaving empty cgroups around as well as
  abandoned session scopes.

  [test case]

  on a system where the user has a ssh key that allows noninteractive
  login to localhost, and also has noninteractive sudo, run:

  $ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost -- sleep 1;
  done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-
  reload; done

  check the sessions to see there have been leaked sessions:

  $ loginctl list-sessions

  SESSION  UID USER   SEAT TTY
1 1000 ubuntu  ttyS0
  350 1000 ubuntu  
  351 1000 ubuntu  
  360 1000 ubuntu  
  ...

  to verify the sessions were leaked, clear them out with:

  $ echo '' | sudo tee
  
/sys/fs/cgroup/unified/user.slice/user-1000.slice/session-*.scope/cgroup.events

  that should result in all the leaked sessions being cleaned up.

  [regression potential]

  issues during systemd pid1 reexec/reload, or issues while cleaning up
  sessions, including leaking sessions/cgroups

  [scope]

  this is needed for all releases

  upstream bug linked above, and upstream PR:
  https://github.com/systemd/systemd/pull/20199

  [original description]

  On a system that is monitored via telegraf I found many abandoned
  systemd session which I believe are created by a potential race where
  systemd is reloading unit files and at the same time a user is
  connecting to the system via ssh or is executing the su command.

  The simple reproducer

  $ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl
  daemon-reload & ssh localhost sleep 1 & done

  Wait > 1 second

  $ jobs -p | xargs --verbose --no-run-if-empty kill -KILL

  To clean out STOPPED jobs and

  $ systemctl status --all 2> /dev/null | grep --before-context 3
  abandoned

  will produce something similar to

     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned
  --
  ● session-273.scope - Session 273 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-274.scope - Session 274 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-30.scope - Session 30 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
  --
  ● session-302.scope - Session 302 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
  --
     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned

  The system in question is running Bionic, systemd-237-3ubuntu10.48

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


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

[Touch-packages] [Bug 1957199] [NEW] package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[S Harrington]

Public bug reported:

failure when trying to upgrade to Ubuntu 20

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: python3 3.8.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
Uname: Linux 4.15.0-166-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jan 12 11:28:01 2022
ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
InstallationDate: Installed on 2015-08-26 (2330 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: python3-defaults
Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
UpgradeStatus: Upgraded to focal on 2022-01-12 (0 days ago)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  failure when trying to upgrade to Ubuntu 20

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
  Uname: Linux 4.15.0-166-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jan 12 11:28:01 2022
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2015-08-26 (2330 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to focal on 2022-01-12 (0 days ago)

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


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

[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform

[jeremyszu]

for jammy, and verified pass on both platforms.

BTW, for jammy.

The intel-hid driver doesn't load probably caused by acpi device not found or 
other kernel/driver related issue.
FWIK, 5.13 is not final kernel for jammy.
I tried this patch with 5.14.0-oem-1018 kernel and it works as expected.

** Patch added: "lp1955997-unmask-intel-hid-for-HP-machines.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1955997/+attachment/5553604/+files/lp1955997-unmask-intel-hid-for-HP-machines.debdiff

** Changed in: oem-priority
   Status: In Progress => Confirmed

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

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Focal:
  New
Status in systemd source package in Impish:
  New
Status in systemd source package in Jammy:
  New

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

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


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

[Touch-packages] [Bug 1955347] Re: rsync works bad with encfs now

[Micouin Claude]

No. It's only this changing of behavior who makes me think of a bug.
(of rsync or of encfs?) Why before rsync and encfs worked well together
and not now?
I noticed that encfs is still working correctly when encrypting. I also
noticed that rsync is now refusing the file deletion because of the IO
error security while before he wasn't and he was going on saving, only
printing a simple warning.
But I understand perfectly that it could be a voluntary security added
in rsync and not a bug. It is better to be too careful than not enough.
Recently I’ve found a page who talks about an old bug of rsync entitled
"I/O errors other than IOERR_GENERAL should not suppress deletion"
https://bugzilla.samba.org/show_bug.cgi?id=7809
Maybe the same type of problem??
Thank you very much for reading me.


** Bug watch added: Samba Bugzilla #7809
   https://bugzilla.samba.org/show_bug.cgi?id=7809

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

Title:
  rsync works bad with encfs now

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  I think rsync works bad with encfs now.

  When root uses it, rsync cannot read a directory encrypted with encfs
  by a user. More precisely, it cannot read the mounted directory, the
  virtual one where the user can read the datas.

  Until now there was only a warning like this
  "rsync: readlink_stat("/home/claude/Documents_chiffres") failed:
  Permission denied (13)"
  and the software went on working (only ignoring the content of the mounted 
directory and of course without saving this content)

  But recently there is this more:
  "IO error encountered -- skipping file deletion"
  and because of this "skipping file deletion", the software can't work 
normally. The destination gets bigger more and more because the deleted files 
in the source are not deleted in the destination.

  Thanks for reading me.
  rsync 3.1.3-8ubuntu0.1
  Description:Ubuntu 20.04.3 LTS
  Release:20.04

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


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

[Touch-packages] [Bug 1951519] Re: ubiquity 20.04.15.17 fails to build (test_timezone)

[Brian Murray]

The package built fine so I'm setting this to 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 tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1951519

Title:
  ubiquity 20.04.15.17 fails to build (test_timezone)

Status in tzdata package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Invalid
Status in ubiquity source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Invalid
Status in ubiquity source package in Jammy:
  Fix Released

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  When trying to build ubiquity from source,

  sudo apt update
  sudo apt -y dist-upgrade
  sudo apt-get build-dep ubiquity
  sudo apt install -y fakeroot
  apt source ubiquity
  cd ubiquity-*
  dpkg-buildpackage -us -uc
  [...]
  test_has_battery (test_upower.UPowerTests) ... ok
  test_check_hostname (test_usersetup.UserSetupTests) ... ok
  test_check_username (test_usersetup.UserSetupTests) ... ok
  test_default_username (test_usersetup.UserSetupTests) ... ok
  test_default_username_strips_invalid_characters 
(test_usersetup.UserSetupTests) ... ok
  test_hostname_check (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_bogus_dns (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_exists (test_usersetup.UserSetupTests) ... ok
  test_unicode (test_usersetup.UserSetupTests) ... ok

  ==
  FAIL: test_city_entry (test_timezone.TimezoneTests)
  --
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
  return func(*args, **keywargs)
    File "/home/ark/ubiquity-20.04.15.17/tests/test_timezone.py", line 58, in 
test_city_entry
  self.assertEqual(set(results), set(expected))
  AssertionError: Items in the first set but not the second:
  ('Eastern', 'Bahamas')
  Items in the second set but not the first:
  ('Eastern', 'Canada')

  --
  Ran 89 tests in 19.319s

  FAILED (failures=1)
  xauth/Xrdb output:
  make: *** [debian/rules:228: tests] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

  It keeps failing regardless of release.

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


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

[Touch-packages] [Bug 1957194] [NEW] resume from hibernation broken when resume image is autodetected another case

[cvl-skubriev]

Public bug reported:

My issue very similar to
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297

I am assuming that the code at about line 162 in `/usr/share/initramfs-
tools/init` like that:

```
resume=*)
RESUME="${x#resume=}"
case $RESUME in
UUID=*)
RESUME="/dev/disk/by-uuid/${RESUME#UUID=}"
esac
;;
``` 

Only works if user wants to set resume partition as `UUID=some` at file
like `/etc/initramfs-tools/conf.d/resume`. But in the case when
initramfs hook resume automatically save `UUID=some` in initrd
`conf/conf.d/zz-resume-auto` file it doesn't matter. Including for
operate `DEV=$(readlink -f "$resume")` correctly in
`/usr/share/initramfs-tools/scripts/local-premount/resume`

Therefore I decide to add similar code to `/usr/share/initramfs-
tools/scripts/local-premount/resume` to fix an issue with resuming.

See a patch in attachment.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "resume.patch"
   
https://bugs.launchpad.net/bugs/1957194/+attachment/5553602/+files/resume.patch

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

Title:
  resume from hibernation broken when resume image is autodetected
  another case

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  My issue very similar to
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297

  I am assuming that the code at about line 162 in
  `/usr/share/initramfs-tools/init` like that:

  ```
  resume=*)
  RESUME="${x#resume=}"
  case $RESUME in
  UUID=*)
  RESUME="/dev/disk/by-uuid/${RESUME#UUID=}"
  esac
  ;;
  ``` 

  Only works if user wants to set resume partition as `UUID=some` at
  file like `/etc/initramfs-tools/conf.d/resume`. But in the case when
  initramfs hook resume automatically save `UUID=some` in initrd
  `conf/conf.d/zz-resume-auto` file it doesn't matter. Including for
  operate `DEV=$(readlink -f "$resume")` correctly in
  `/usr/share/initramfs-tools/scripts/local-premount/resume`

  Therefore I decide to add similar code to `/usr/share/initramfs-
  tools/scripts/local-premount/resume` to fix an issue with resuming.

  See a patch in attachment.

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


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

[Touch-packages] [Bug 1951779] Re: tempfile command removed from debianutils

[Christian Ehrhardt ]

** Tags removed: server-next
** Tags added: server-todo

** Tags added: bitesize

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

Title:
  tempfile command removed from debianutils

Status in boost1.74 package in Ubuntu:
  New
Status in bzip2 package in Ubuntu:
  New
Status in ceph package in Ubuntu:
  New
Status in grub-legacy-ec2 package in Ubuntu:
  Triaged

Bug description:
  Error when do-release-upgrade -d from 20.04.3

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.13.0-19-generic 5.13.0-19.19
  ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148
  Uname: Linux 5.4.0-90-generic x86_64
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Mon Nov 22 13:31:36 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/x-grub-legacy-ec2 exited with 
return code 127
  InstallationDate: Installed on 2018-10-01 (1147 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 8087:07e6 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
  MachineType: PAIQ EC3-BT19D4L
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic 
root=UUID=4c36d2b3-c1dd-469f-bfbf-5b7052d669d4 ro ipv6.disable=1 quiet 
reboot=pci ipv6.disable=1
  Python3Details: Error: command ['readlink', '-f', "/usr/bin/which: this 
version of `which' is deprecated; use `command -v' in scripts 
instead.\n/usr/bin/python3"] failed with exit code 1: , Error: [Errno 2] No 
such file or directory: 'Error: command [\'readlink\', \'-f\', "/usr/bin/which: 
this version of `which\' is deprecated; use `command -v\' in scripts 
instead.\\n/usr/bin/python3"] failed with exit code 1: ', python3-minimal, 
3.9.4-1build1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.04-1ubuntu48
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: grub-legacy-ec2
  Title: package linux-image-5.13.0-19-generic 5.13.0-19.19 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/x-grub-legacy-ec2 exited 
with return code 127
  UpgradeStatus: Upgraded to jammy on 2021-11-22 (0 days ago)
  dmi.bios.date: 02/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: EC3-BT19D4L
  dmi.board.vendor: PAIQ
  dmi.board.version: A1
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd02/28/2017:svnPAIQ:pnEC3-BT19D4L:pvrBIOSNameBT190003BIOSVersionA1BuildDate:rvnPAIQ:rnEC3-BT19D4L:rvrA1:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: EC3-BT19D4L
  dmi.product.sku: 18:19:28
  dmi.product.version: BIOS Name:BT190003 BIOS Version:A1 Build Date:
  dmi.sys.vendor: PAIQ

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.74/+bug/1951779/+subscriptions


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

[Touch-packages] [Bug 1956954] Re: Can't load seccomp filter

[Nino Škopac]

Dear Lucas,

I've mentioned in the SO post that I linked that the nature of the issue
is intermittent.

I would be happy to provide additional logs next time I encounter the
issue.

Could you please advise on how do I collect additional logs?

Regards,
Nino

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

Title:
  Can't load seccomp filter

Status in libseccomp package in Ubuntu:
  Incomplete

Bug description:
  After migrating from Ubuntu 20 amd64 to aarch64 I started experiencing
  "can't load seccomp filter" when doing `apt update && apt upgrade` and
  "Kernel refuses to turn on BPF filters" when using Puppeteer.

  I wrote about it more extensively here:
  https://stackoverflow.com/questions/69892137/after-a-few-days-i-can-
  no-longer-start-puppeteer-until-i-restart-the-server

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

  apt-cache policy seccomp
  ---
  seccomp:
Installed: (none)
Candidate: 2.5.1-1ubuntu1~20.04.2
Version table:
   2.5.1-1ubuntu1~20.04.2 500
  500 http://us-east-1.ec2.ports.ubuntu.com/ubuntu-ports 
focal-updates/main arm64 Packages
  500 http://ports.ubuntu.com/ubuntu-ports focal-security/main arm64 
Packages
   2.4.3-1ubuntu1 500
  500 http://us-east-1.ec2.ports.ubuntu.com/ubuntu-ports focal/main 
arm64 Packages

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


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

[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform

[jeremyszu]

This patch is for impish.
Verified pass on both HP new platforms.

** Patch added: 
"lp1955997-add-a-whitelist-to-unblock-intel-hid-on-HP-mach.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1955997/+attachment/5553585/+files/lp1955997-add-a-whitelist-to-unblock-intel-hid-on-HP-mach.debdiff

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

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Focal:
  New
Status in systemd source package in Impish:
  New
Status in systemd source package in Jammy:
  New

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

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


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

[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform

[jeremyszu]

Based on the discussion on
https://chat.canonical.com/canonical/pl/ywmmrm9d9j8cdkcwbyx6rkwqgh.

We will solve this issue by
1) maintain a whitelist on focal and impish
2) backport unmast intel-hid[1] on jammy

[1] https://github.com/systemd/systemd/pull/20219

** Patch removed: 
"lp1955997-add-a-whitelist-to-unblock-intel-hid-on-HP-machines.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1955997/+attachment/5552318/+files/lp1955997-add-a-whitelist-to-unblock-intel-hid-on-HP-machines.debdiff

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

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Focal:
  New
Status in systemd source package in Impish:
  New
Status in systemd source package in Jammy:
  New

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

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


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

[Touch-packages] [Bug 1957181] [NEW] Xorg freeze

[Simon]

Public bug reported:

When having more than one window open, e.g. Firefox and a terminal and
then to swap between the two. The clicking with the mouse stops working
but it still moves. For instance when I hover over text or not the
cursor does not change. Sometimes I can still click or select text in
the original window but the coordinates of the mouse are not where the
cursor is displayed. Sometimes the keyboard dies too e.g. Alt+F2 does
not work. Killing XOrg (if possible) seems to revert things to a working
state.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
Uname: Linux 5.4.0-92-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 12 15:24:16 2022
DistUpgraded: 2020-09-07 08:54:13,457 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 evdi, 1.7.0, 4.15.0-70-generic, x86_64: installed
 evdi, 1.7.0, 5.4.0-91-generic, x86_64: installed
 evdi, 1.7.0, 5.4.0-92-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Today
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:225c]
InstallationDate: Installed on 2019-02-13 (1063 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 20KGS5DU00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic 
root=UUID=c1172559-29d0-4c7c-bfab-574068d6d5cc ro quiet 
splash,psmouse.synaptics_intertouch=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-09-07 (492 days ago)
acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
dmi.bios.date: 10/13/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET75W (1.50 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KGS5DU00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KGS5DU00
dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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 freeze third-party-packages ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  When having more than one window open, e.g. Firefox and a terminal and
  then to swap between the two. The clicking with the mouse stops
  working but it still moves. For instance when I hover over text or not
  the cursor does not change. Sometimes I can still click or select text
  in the original window but the coordinates of the mouse are not where
  the cursor is displayed. Sometimes the keyboard dies too e.g. Alt+F2
  does not work. Killing XOrg (if possible) seems to revert things to a
  working state.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  Uname: Linux 5.4.0-92-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 12 15:24:16 2022
  DistUpgraded: 2020-09-07 08:54:13,457 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 1.7.0, 4.15.0-70-generic, x86_64: 

[Touch-packages] [Bug 1941752]

[Mail-to-wrt]

Patched exiv2 packages for Ubuntu have just been released.

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

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Fix Released
Status in exiv2 package in Ubuntu:
  Fix Released
Status in gwenview package in Ubuntu:
  Fix Released

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1956954] Re: Can't load seccomp filter

[Lucas Kanashiro]

Thanks for taking the time to report this bug and trying to make Ubuntu
better.

I am not familiar with Puppeteer but since you think this might be
related to kernel, could you please provide any system logs so we can
understand what is happening? In a regular arm64 VM I am able to run
"apt update && apt upgrade" without issues (FWIW I am not running it on
AWS).

I am setting the status of this bug to Incomplete, once you provide more
information set it back to New and we will take a look at it again.

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

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

Title:
  Can't load seccomp filter

Status in libseccomp package in Ubuntu:
  Incomplete

Bug description:
  After migrating from Ubuntu 20 amd64 to aarch64 I started experiencing
  "can't load seccomp filter" when doing `apt update && apt upgrade` and
  "Kernel refuses to turn on BPF filters" when using Puppeteer.

  I wrote about it more extensively here:
  https://stackoverflow.com/questions/69892137/after-a-few-days-i-can-
  no-longer-start-puppeteer-until-i-restart-the-server

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

  apt-cache policy seccomp
  ---
  seccomp:
Installed: (none)
Candidate: 2.5.1-1ubuntu1~20.04.2
Version table:
   2.5.1-1ubuntu1~20.04.2 500
  500 http://us-east-1.ec2.ports.ubuntu.com/ubuntu-ports 
focal-updates/main arm64 Packages
  500 http://ports.ubuntu.com/ubuntu-ports focal-security/main arm64 
Packages
   2.4.3-1ubuntu1 500
  500 http://us-east-1.ec2.ports.ubuntu.com/ubuntu-ports focal/main 
arm64 Packages

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


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

[Touch-packages] [Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else

[Sebastien Bacher]

untagging, I'm handling the SRU now

** Tags removed: rls-ii-incoming

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

Title:
  Copy from Firefox Wayland fails to be pasted anywhere else

Status in GTK+:
  Unknown
Status in firefox package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  The clipboard copies from GTK based software sometime stop working
  under wayland

  * Test Case

  - in a wayland session try to copy text between software, from firefox
  to gedit for example, it should work in a consistent manner

  alternative testcase inspired from the gitlab ticket
  - install wl-clipboard
  - use evince to open a pdf
  - select and copy some content
  - on a cmdline do 
  $ wl-paste -t TEXT
  - try to paste then in another software, gedit for example

  the copied text should be pasted

  
  * Regression potential

  The changes are in the wayland selection source so the impact should
  only be for wayland users and limited to clipboard interactions

  
  --

  
  Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on 
Wayland native

  Version   84.0.2
  Build ID  20210105180113

  Window Protocol   wayland
  Desktop Environment   gnome

  DESCRIPTION OF THE PROBLEM:

  If I copy text from a web page and try to paste it into another
  Firefox page, the text is pasted correctly.

  If I copy text from a web page and try to paste it in [gedit,
  libreoffice, thunderbird, terminal, slack (electron)] nothing happens.
  The Gnome Clipboard extension stays empty when content is copied from
  Firefox Wayland.

  Pasting *from* another app *to* Firefox works fine.

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


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

[Touch-packages] [Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else

[Sebastien Bacher]

** Description changed:

- Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS,
- on Wayland native
+ * Impact
+ 
+ The clipboard copies from GTK based software sometime stop working under
+ wayland
+ 
+ * Test Case
+ 
+ - in a wayland session try to copy text between software, from firefox
+ to gedit for example, it should work in a consistent manner
+ 
+ alternative testcase inspired from the gitlab ticket
+ - install wl-clipboard
+ - use evince to open a pdf
+ - select and copy some content
+ - on a cmdline do 
+ $ wl-paste -t TEXT
+ - try to paste then in another software, gedit for example
+ 
+ the copied text should be pasted
+ 
+ 
+ * Regression potential
+ 
+ The changes are in the wayland selection source so the impact should
+ only be for wayland users and limited to clipboard interactions
+ 
+ 
+ --
+ 
+ 
+ Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on 
Wayland native
  
  Version   84.0.2
  Build ID  20210105180113
  
  Window Protocol   wayland
  Desktop Environment   gnome
  
  DESCRIPTION OF THE PROBLEM:
  
  If I copy text from a web page and try to paste it into another Firefox
  page, the text is pasted correctly.
  
  If I copy text from a web page and try to paste it in [gedit,
  libreoffice, thunderbird, terminal, slack (electron)] nothing happens.
  The Gnome Clipboard extension stays empty when content is copied from
  Firefox Wayland.
  
  Pasting *from* another app *to* Firefox works fine.

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

Title:
  Copy from Firefox Wayland fails to be pasted anywhere else

Status in GTK+:
  Unknown
Status in firefox package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  The clipboard copies from GTK based software sometime stop working
  under wayland

  * Test Case

  - in a wayland session try to copy text between software, from firefox
  to gedit for example, it should work in a consistent manner

  alternative testcase inspired from the gitlab ticket
  - install wl-clipboard
  - use evince to open a pdf
  - select and copy some content
  - on a cmdline do 
  $ wl-paste -t TEXT
  - try to paste then in another software, gedit for example

  the copied text should be pasted

  
  * Regression potential

  The changes are in the wayland selection source so the impact should
  only be for wayland users and limited to clipboard interactions

  
  --

  
  Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on 
Wayland native

  Version   84.0.2
  Build ID  20210105180113

  Window Protocol   wayland
  Desktop Environment   gnome

  DESCRIPTION OF THE PROBLEM:

  If I copy text from a web page and try to paste it into another
  Firefox page, the text is pasted correctly.

  If I copy text from a web page and try to paste it in [gedit,
  libreoffice, thunderbird, terminal, slack (electron)] nothing happens.
  The Gnome Clipboard extension stays empty when content is copied from
  Firefox Wayland.

  Pasting *from* another app *to* Firefox works fine.

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


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

[Touch-packages] [Bug 1957160] Re: BlueZ release 5.63

[Sebastien Bacher]

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

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

Title:
  BlueZ release 5.63

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  http://www.bluez.org/release-of-bluez-5-63/

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz

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


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

[Touch-packages] [Bug 1957160] Re: BlueZ release 5.63

[Daniel van Vugt]

** Attachment added: "bluez_5.63-0ubuntu1.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1957160/+attachment/5553550/+files/bluez_5.63-0ubuntu1.debian.tar.xz

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

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

Title:
  BlueZ release 5.63

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  http://www.bluez.org/release-of-bluez-5-63/

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz

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


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

[Touch-packages] [Bug 1957160] Re: BlueZ release 5.63

[Daniel van Vugt]

** Attachment added: "bluez_5.63.orig.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1957160/+attachment/5553549/+files/bluez_5.63.orig.tar.xz

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

Title:
  BlueZ release 5.63

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  http://www.bluez.org/release-of-bluez-5-63/

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz

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


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

[Touch-packages] [Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else

[Olivier Tilloy]

Unlikely to happen for hirsute, which will be EOL on January 20.
Tagging for consideration in impish.

** Tags added: rls-ii-incoming

** Tags removed: rls-jj-incoming

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

Title:
  Copy from Firefox Wayland fails to be pasted anywhere else

Status in GTK+:
  Unknown
Status in firefox package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS,
  on Wayland native

  Version   84.0.2
  Build ID  20210105180113

  Window Protocol   wayland
  Desktop Environment   gnome

  DESCRIPTION OF THE PROBLEM:

  If I copy text from a web page and try to paste it into another
  Firefox page, the text is pasted correctly.

  If I copy text from a web page and try to paste it in [gedit,
  libreoffice, thunderbird, terminal, slack (electron)] nothing happens.
  The Gnome Clipboard extension stays empty when content is copied from
  Firefox Wayland.

  Pasting *from* another app *to* Firefox works fine.

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


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

[Touch-packages] [Bug 1957160] [NEW] BlueZ release 5.63

[Daniel van Vugt]

Public bug reported:

http://www.bluez.org/release-of-bluez-5-63/

https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Assignee: Daniel van Vugt (vanvugt)
 Status: In Progress


** Tags: jammy

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

Title:
  BlueZ release 5.63

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  http://www.bluez.org/release-of-bluez-5-63/

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.63.tar.xz

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


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

[Touch-packages] [Bug 1951519] Re: ubiquity 20.04.15.17 fails to build (test_timezone)

[Łukasz Zemczak]

Hello Ark74, or anyone else affected,

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

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

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

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

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

** Changed in: ubiquity (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  ubiquity 20.04.15.17 fails to build (test_timezone)

Status in tzdata package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Invalid
Status in ubiquity source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Invalid
Status in ubiquity source package in Jammy:
  Fix Released

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  When trying to build ubiquity from source,

  sudo apt update
  sudo apt -y dist-upgrade
  sudo apt-get build-dep ubiquity
  sudo apt install -y fakeroot
  apt source ubiquity
  cd ubiquity-*
  dpkg-buildpackage -us -uc
  [...]
  test_has_battery (test_upower.UPowerTests) ... ok
  test_check_hostname (test_usersetup.UserSetupTests) ... ok
  test_check_username (test_usersetup.UserSetupTests) ... ok
  test_default_username (test_usersetup.UserSetupTests) ... ok
  test_default_username_strips_invalid_characters 
(test_usersetup.UserSetupTests) ... ok
  test_hostname_check (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_bogus_dns (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_exists (test_usersetup.UserSetupTests) ... ok
  test_unicode (test_usersetup.UserSetupTests) ... ok

  ==
  FAIL: test_city_entry (test_timezone.TimezoneTests)
  --
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
  return func(*args, **keywargs)
    File "/home/ark/ubiquity-20.04.15.17/tests/test_timezone.py", line 58, in 
test_city_entry
  self.assertEqual(set(results), set(expected))
  AssertionError: Items in the first set but not the second:
  ('Eastern', 'Bahamas')
  Items in the second set but not the first:
  ('Eastern', 'Canada')

  --
  Ran 89 tests in 19.319s

  FAILED (failures=1)
  xauth/Xrdb output:
  make: *** [debian/rules:228: tests] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

  It keeps failing regardless of release.

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


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

[Touch-packages] [Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else

[bluppfisk]

I would also like to request a port of this fix to impish and hirsute.

I've currently worked around this by upgrading gtk+3.0 in a probably
slightly unorthodox way, but I'd much prefer if the package was offered
through the official Ubuntu impish repository.

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

Title:
  Copy from Firefox Wayland fails to be pasted anywhere else

Status in GTK+:
  Unknown
Status in firefox package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS,
  on Wayland native

  Version   84.0.2
  Build ID  20210105180113

  Window Protocol   wayland
  Desktop Environment   gnome

  DESCRIPTION OF THE PROBLEM:

  If I copy text from a web page and try to paste it into another
  Firefox page, the text is pasted correctly.

  If I copy text from a web page and try to paste it in [gedit,
  libreoffice, thunderbird, terminal, slack (electron)] nothing happens.
  The Gnome Clipboard extension stays empty when content is copied from
  Firefox Wayland.

  Pasting *from* another app *to* Firefox works fine.

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


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

[Touch-packages] [Bug 1956581] Re: make gtk 3.24.31 available in Ubuntu 21.*

[Sebastien Bacher]

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

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

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Low

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

** This bug has been marked a duplicate of bug 1913775
   Copy from Firefox Wayland fails to be pasted anywhere else

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

Title:
  make gtk 3.24.31 available in Ubuntu 21.*

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  A very annoying GTK bug (which breaks copying and pasting, the
  computer user's favourite activity) has been fixed in GTK 3.24.31.
  Unfortunately, Ubuntu 21.10 is still stuck on 3.24.30. I'd think that
  making 3.24.31 available wouldn't break much, but would help a lot of
  us out.

  Can this be 'backported' (is this the correct jargon?) or am I better
  off upgrading to Jammy Jellyfish even though it's still unstable?

  Bug: https://gitlab.gnome.org/GNOME/gtk/-/issues/4340

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


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

[Touch-packages] [Bug 1956915] Re: New bugfix release 21.2.6

[Timo Aaltonen]

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

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

Title:
  New bugfix release 21.2.6

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

Bug description:
  [Impact]

  This is the last point-release of the 21.2.x-series, we should put it
  in impish so latest bugfixes would get there, and in focal for 20.04.4
  image.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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