[Touch-packages] [Bug 1972790] Re: Can't connect to hotspot created on ubuntu

[Incompetent]

My temporary workaround for this is to downgrade wpasupplicant-2.10 to
wpasupplicant-2.9. It seems there is an issue with the new wpasupplicant
package

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1972977] Re: gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query()

[Daniel van Vugt]

I agree... it's just desktop team policy requested by seb128.

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

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

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

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

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

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


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

[Touch-packages] [Bug 1983000] Re: IDK

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => 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/1983000

Title:
  IDK

Status in Ubuntu:
  Incomplete

Bug description:
  IDK

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Thu Jul 28 00:08:14 2022
  DistUpgraded: 2022-06-04 14:01:52,153 DEBUG /openCache(), new cache size 77115
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2021-04-26 (457 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP EliteBook 850 G1
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic 
root=UUID=92e691d6-a214-4b1a-9cf6-48a28f570055 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2022-06-04 (53 days ago)
  dmi.bios.date: 07/13/2017
  dmi.bios.release: 1.40
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.40
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 21.89
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.40:bd07/13/2017:br1.40:efr21.89:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:skuG4M89US#ABA:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G1
  dmi.product.sku: G4M89US#ABA
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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/+bug/1983000/+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 1958055] Re: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)

[Seth Arnold]

I'm a bit surprised ubuntu-bug shows a GUI when run under sudo at all. I
think I'd expect the usual X11 "no cookies" failure to connect.

Running X programs as another user is bound to be trouble. Perhaps
ubuntu-bug should quit immediately if it detects running via sudo, su,
etc things?

Thanks

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

Title:
  sudo apport-kde is in a different design (stripped
  XDG_CURRENT_DESKTOP)

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  Running ubuntu-bug as normal user has the correct theme (see
  screenshots attached to bug #1881640), but running "sudo ubuntu-bug"
  has a different, non-matching theme (see attached screenshot).

  This problem can be reproduce by running a KDE application on Ubuntu
  Desktop (GNOME):

  1. Launch ubuntu-22.04-desktop-amd64.iso
  2. Install apport-kde
  3. Run: /usr/share/apport/apport-kde -f
  4. Run: sudo /usr/share/apport/apport-kde -f
  5. Compare both windows. They have different icons and font size.

  Same result with KDE:

  1. Use kubuntu-22.04-desktop-amd64.iso
  2. Run ubuntu-bug -f
  3. Run: sudo ubuntu-bug -f

  [Analysis]

  Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme,
  but XDG_CURRENT_DESKTOP is not in the list of environment variables to
  preserve (and not in env_keep in /etc/sudoers).

  [Workaround]

  Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo
  XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde
  -f

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:04:24 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1958055/+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 1022858] Re: Guest session asks for a password after switching users

[martinr]

I'm still experiencing this problem in 22.04. Are there any updates on when it 
gets fixed?
Guest accounts are very useful.

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

Title:
  Guest session asks for a password after switching users

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When I switch back to an already open guest session from my user
  account, I find that the guest session is locked and it asks for the
  Guest password (which obviously there isn't because it's a guest
  session!).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-session-bin 3.2.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Jul 10 09:54:55 2012
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: 
assertion `gconf_valid_key (dirname, NULL)' failed
  --- 
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  Package: lightdm 1.2.1-0ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Tags:  precise running-unity
  Uname: Linux 3.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1022858/+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 1982545] Re: FTBFS on riscv64

[Alexandre Ghiti]

** Bug watch added: Debian Bug tracker #1015835
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015835

** Also affects: curl (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015835
   Importance: Unknown
   Status: Unknown

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

Title:
  FTBFS on riscv64

Status in curl package in Ubuntu:
  New
Status in curl package in Debian:
  Unknown

Bug description:
  As can be seen here [1], the build on riscv64 fails now that we use
  gcc12 with the following error:

  libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Werror-implicit-function-declaration -Wno-system-headers 
-Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/curl 
slist_wc.o tool_binmode.o tool_bname.o tool_cb_dbg.o tool_cb_hdr.o 
tool_cb_prg.o tool_cb_rea.o tool_cb_see.o tool_cb_wrt.o tool_cfgable.o 
tool_dirhie.o tool_doswin.o tool_easysrc.o tool_filetime.o tool_findfile.o 
tool_formparse.o tool_getparam.o tool_getpass.o tool_help.o tool_helpers.o 
tool_hugehelp.o tool_libinfo.o tool_listhelp.o tool_main.o tool_msgs.o 
tool_operate.o tool_operhlp.o tool_panykey.o tool_paramhlp.o tool_parsecfg.o 
tool_progress.o tool_strdup.o tool_setopt.o tool_sleep.o tool_urlglob.o 
tool_util.o tool_vms.o tool_writeout.o tool_writeout_json.o tool_xattr.o 
../lib/strtoofft.o ../lib/timediff.o ../lib/nonblock.o ../lib/warnless.o 
../lib/curl_ctype.o ../lib/curl_multibyte.o ../lib/version_win32.o 
../lib/dynbuf.o  ../lib/.libs/libcurl.so -lssl -lcrypto -lz
  /usr/bin/ld: ../lib/.libs/libcurl.so: undefined reference to 
`__atomic_exchange_1'
  collect2: error: ld returned 1 exit status
  make[4]: *** [Makefile:991: curl] Error 1

  There exists a bug report and a fix for that upstream here:
  https://github.com/curl/curl/pull/9061

  I'm currently building a package with this patch here [2].

  [1] 
https://launchpadlibrarian.net/612746451/buildlog_ubuntu-kinetic-riscv64.curl_7.84.0-2_BUILDING.txt.gz
  [2] 
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13822857/+listing-archive-extra

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


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

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

[Brian Murray]

** Bug watch added: Debian Bug tracker #980788
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980788

** Also affects: initramfs-tools (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980788
   Importance: Unknown
   Status: Unknown

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

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

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed

[Tired Sysadmin]

I see the same "could not execute" error on a fresh 22.04 Jammy system,
when installing the 'sssd' metapackage.  The install ends with:


Created symlink /etc/systemd/system/sssd.service.wants/sssd-autofs.socket → 
/lib/systemd/system/sssd-autofs.socket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-nss.socket → 
/lib/systemd/system/sssd-nss.socket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-pam-priv.socket → 
/lib/systemd/system/sssd-pam-priv.socket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-pam.socket → 
/lib/systemd/system/sssd-pam.socket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-ssh.socket → 
/lib/systemd/system/sssd-ssh.socket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-sudo.socket → 
/lib/systemd/system/sssd-sudo.socket.
Created symlink /etc/systemd/system/multi-user.target.wants/sssd.service → 
/lib/systemd/system/sssd.service.
sssd-autofs.service is a disabled or a static unit, not starting it.
sssd-nss.service is a disabled or a static unit, not starting it.
sssd-pam.service is a disabled or a static unit, not starting it.
sssd-ssh.service is a disabled or a static unit, not starting it.
sssd-sudo.service is a disabled or a static unit, not starting it.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.
Setting up sssd-proxy (2.6.3-1ubuntu3.1) ...
Setting up sssd-ad-common (2.6.3-1ubuntu3.1) ...
Created symlink /etc/systemd/system/sssd.service.wants/sssd-pac.socket → 
/lib/systemd/system/sssd-pac.socket.
sssd-pac.service is a disabled or a static unit, not starting it.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.
Setting up sssd-krb5-common (2.6.3-1ubuntu3.1) ...
Setting up libsmbclient:amd64 (2:4.15.5~dfsg-0ubuntu5.1) ...
Setting up sssd-krb5 (2.6.3-1ubuntu3.1) ...
Setting up sssd-ldap (2.6.3-1ubuntu3.1) ...
Setting up sssd-ad (2.6.3-1ubuntu3.1) ...
Setting up sssd-ipa (2.6.3-1ubuntu3.1) ...
Setting up sssd (2.6.3-1ubuntu3.1) ...


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

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

Title:
  error: too early for operation, device not yet seeded or device model
  not acknowledged Install failed

Status in launchpad-buildd:
  New
Status in init-system-helpers package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565

  New deb-systemd-invoke added functionality for systemd v250 which
  ubuntu does not have yet. But it also appears to break postinst calls
  to deb-systemd-invoke, at least as seen during snap builds in lxd
  containers operated by launchpad-buildd.

  I wonder if there is a regression in new code, or new systemd, which
  may warrant a revert.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+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 1983046] [NEW] Incorrect username for systemd-journal-upload.service

[Tom Cameron]

Public bug reported:

Starting the systemd-journal-upload service fails. The username
specified in the Ubuntu systemd-journal-upload.service does not exist
after the systemd-journal-remote package is installed.


Ubuntu systemd-journal-upload.service:

User=systemd-journal-upload


Corrent systemd-journal-upload.service:

User=systemd-journal-remote

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: systemd-journal-remote 249.11-0ubuntu3.4
ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Jul 28 17:44:06 2022
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: systemd
UpgradeStatus: Upgraded to jammy on 2022-07-28 (0 days ago)
modified.conffile..etc.systemd.journal-upload.conf: [modified]
mtime.conffile..etc.systemd.journal-upload.conf: 2022-07-28T07:02:44.608776

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


** Tags: amd64 apport-bug jammy

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

Title:
  Incorrect username for systemd-journal-upload.service

Status in systemd package in Ubuntu:
  New

Bug description:
  Starting the systemd-journal-upload service fails. The username
  specified in the Ubuntu systemd-journal-upload.service does not exist
  after the systemd-journal-remote package is installed.

  
  Ubuntu systemd-journal-upload.service:

  User=systemd-journal-upload


  Corrent systemd-journal-upload.service:

  User=systemd-journal-remote

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd-journal-remote 249.11-0ubuntu3.4
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Jul 28 17:44:06 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: Upgraded to jammy on 2022-07-28 (0 days ago)
  modified.conffile..etc.systemd.journal-upload.conf: [modified]
  mtime.conffile..etc.systemd.journal-upload.conf: 2022-07-28T07:02:44.608776

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1983046/+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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

[Launchpad Bug Tracker]

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

---
livecd-rootfs (2.771) kinetic; urgency=medium

  [ Steve Langasek ]
  * Drop support for building i386 images aside from the launchpad builder
images.
  * Remove fwupd from the cloud images.  LP: #1981109.

  [ Michael Hudson-Doyle ]
  * Fix some issues with the netboot tarballs:
- Include the signed shim (oops).
- Make the kernel path on disk and in the bootloader config match (more
  oops).
- Make paths more architecture dependent as the code in grubnetXXX.efi to
  probe a platform dependent path first doesn't work.

  [ Alexandre Ghiti ]
  * Install wpasupplicant by default as for now, most of the RISC-V boards
embed a Wifi chipset (LP: #1983008)

 -- Steve Langasek   Mon, 25 Jul 2022
12:49:28 -0700

** Changed in: livecd-rootfs (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  server image pulls in ModemManager via fwupd, consumes 25MiB RAM in
  every container

Status in fwupd package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  New
Status in fwupd source package in Jammy:
  Invalid
Status in livecd-rootfs source package in Jammy:
  Triaged
Status in modemmanager source package in Jammy:
  New
Status in ubuntu-meta source package in Jammy:
  New

Bug description:
  Looking at memory utilization in a pristine Ubuntu lxd container (top
  -o RES), I see that ModemManager is running, which I was surprised to
  see is present at all in the stock image.

  Tracking this I find that fwupd depends on libmm-glib0, which in turn
  Recommends: modemmanager.

  Libraries in general should not recommend daemons, so it's possible
  this should be fixed by libmm-glib0 dropping this Recommends.  It
  certainly doesn't seem to be a deliberate decision by the Server Team
  to have modemmanager installed and running by default on all systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1897932] Re: systemd-repart not packaged

[Luca Boccassi]

** Description changed:

  [Impact]
  
  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?
  
  The bug reporter would like to use it in their new raspberry pi images
  where they don't have cloud-init installed. The reporter is already
  using systemd-growfs, but they are missing the nice partition resizing
  part (so are using cloud-initramfs-growroot).
  
  Furthermore, in the mkosi image builder
  (https://github.com/systemd/mkosi), the systemd/mkosi developers would
  like to start using systemd-repart for partitioning. Unfortunately,
  they're currently blocked on this because 22.04 doesn't ship systemd-
  repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
  and will do so until the next Ubuntu LTS is released. If we have to wait
  for the next LTS to be released, we'll have to wait for a considerable
  amount of time before we're able to start using systemd-repart.
  
  Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
  as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
  be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.
  
  [Test Plan]
  This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.
  
  [Where problems could occur]
  Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.
  
  Given that there's no risk involved with enabling systemd-repart, and
  given the useful features it provides, the systemd/mkosi developers
  would like to request that systemd-repart be enabled in Ubuntu and
  backported to Jammy so that they can start adopting it in mkosi.
+ 
+ Runtime behavior of existing components is not affected by the build
+ config change.

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

Title:
  systemd-repart not packaged

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?

  The bug reporter would like to use it in their new raspberry pi images
  where they don't have cloud-init installed. The reporter is already
  using systemd-growfs, but they are missing the nice partition resizing
  part (so are using cloud-initramfs-growroot).

  Furthermore, in the mkosi image builder
  (https://github.com/systemd/mkosi), the systemd/mkosi developers would
  like to start using systemd-repart for partitioning. Unfortunately,
  they're currently blocked on this because 22.04 doesn't ship systemd-
  repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
  and will do so until the next Ubuntu LTS is released. If we have to
  wait for the next LTS to be released, we'll have to wait for a
  considerable amount of time before we're able to start using systemd-
  repart.

  Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
  as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
  be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.

  [Test Plan]
  This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.

  [Where problems could occur]
  Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.

  Given that there's no risk involved with enabling systemd-repart, and
  given the useful features it provides, the systemd/mkosi developers
  would like to request that systemd-repart be enabled in Ubuntu and
 

[Touch-packages] [Bug 1897932] Re: systemd-repart not packaged

[Lukas Märdian]

** Tags added: rls-jj-incoming

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

Title:
  systemd-repart not packaged

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?

  The bug reporter would like to use it in their new raspberry pi images
  where they don't have cloud-init installed. The reporter is already
  using systemd-growfs, but they are missing the nice partition resizing
  part (so are using cloud-initramfs-growroot).

  Furthermore, in the mkosi image builder
  (https://github.com/systemd/mkosi), the systemd/mkosi developers would
  like to start using systemd-repart for partitioning. Unfortunately,
  they're currently blocked on this because 22.04 doesn't ship systemd-
  repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
  and will do so until the next Ubuntu LTS is released. If we have to
  wait for the next LTS to be released, we'll have to wait for a
  considerable amount of time before we're able to start using systemd-
  repart.

  Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
  as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
  be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.

  [Test Plan]
  This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.

  [Where problems could occur]
  Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.

  Given that there's no risk involved with enabling systemd-repart, and
  given the useful features it provides, the systemd/mkosi developers
  would like to request that systemd-repart be enabled in Ubuntu and
  backported to Jammy so that they can start adopting it in mkosi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+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 1897932] Re: systemd-repart not packaged

[Luca Boccassi]

** Description changed:

  [Impact]
  
  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?
  
- The bug reporter would like to use it in our new raspberry pi images
+ The bug reporter would like to use it in their new raspberry pi images
  where they don't have cloud-init installed. The reporter is already
  using systemd-growfs, but they are missing the nice partition resizing
  part (so are using cloud-initramfs-growroot).
  
  Furthermore, in the mkosi image builder
  (https://github.com/systemd/mkosi), the systemd/mkosi developers would
  like to start using systemd-repart for partitioning. Unfortunately,
  they're currently blocked on this because 22.04 doesn't ship systemd-
  repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
  and will do so until the next Ubuntu LTS is released. If we have to wait
  for the next LTS to be released, we'll have to wait for a considerable
  amount of time before we're able to start using systemd-repart.
  
  Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
  as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
  be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.
  
  [Test Plan]
  This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.
  
  [Where problems could occur]
  Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.
  
  Given that there's no risk involved with enabling systemd-repart, and
  given the useful features it provides, the systemd/mkosi developers
  would like to request that systemd-repart be enabled in Ubuntu and
  backported to Jammy so that they can start adopting it in mkosi.

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

Title:
  systemd-repart not packaged

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?

  The bug reporter would like to use it in their new raspberry pi images
  where they don't have cloud-init installed. The reporter is already
  using systemd-growfs, but they are missing the nice partition resizing
  part (so are using cloud-initramfs-growroot).

  Furthermore, in the mkosi image builder
  (https://github.com/systemd/mkosi), the systemd/mkosi developers would
  like to start using systemd-repart for partitioning. Unfortunately,
  they're currently blocked on this because 22.04 doesn't ship systemd-
  repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
  and will do so until the next Ubuntu LTS is released. If we have to
  wait for the next LTS to be released, we'll have to wait for a
  considerable amount of time before we're able to start using systemd-
  repart.

  Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
  as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
  be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.

  [Test Plan]
  This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.

  [Where problems could occur]
  Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.

  Given that there's no risk involved with enabling systemd-repart, and
  given the useful features it provides, the systemd/mkosi developers
  would like to request that systemd-repart be enabled in Ubuntu and
  backported to Jammy

[Touch-packages] [Bug 1943441] Re: lxc: lxc-test-parse-config-file failure (expected value and retrieved value do not match)

[Cory Todd]

Failing with 2022.07.11/focal/linux-fips/5.4.0-1058.66

parse_config_file.c: 63: set_get_compare_clear_save_load: expected value 
"system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key 
"lxc.selinux.context" do not match
parse_config_file.c: 49: set_get_compare_clear_save_load: failed to set config 
item "lxc.seccomp.profile" to "/some/seccomp/file"
parse_config_file.c: 580: main: lxc.seccomp.profile

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

Title:
  lxc: lxc-test-parse-config-file failure (expected value and retrieved
  value do not match)

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Focal:
  New
Status in lxc source package in Impish:
  Confirmed

Bug description:
  I'm getting the following error with the lxc kernel autotest on
  impish:

  08:46:04 DEBUG| parse_config_file.c: 60: set_get_compare_clear_save_load: 
expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for 
config key "lxc.selinux.context" do not match
  08:46:04 DEBUG|
  08:46:04 DEBUG| parse_config_file.c: 382: main: lxc.selinux.context
  08:46:06 INFO | ERRORubuntu_lxc.lxc-test-parse-config-file
ubuntu_lxc.lxc-test-parse-config-filetimestamp=1631090766localtime=Sep 
08 08:46:06Command  failed, rc=1, Command returned non-zero exit status
* Command:
/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file
Exit status: 1
Duration: 0.0550210475922

stderr:
parse_config_file.c: 60: set_get_compare_clear_save_load: expected value 
"system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key 
"lxc.selinux.context" do not match

parse_config_file.c: 382: main: lxc.selinux.context

  I haven't investigated very much, but it looks like a
  (mis)configuration change / issue. Does it ring any bell? Otherwise
  I'll investigate more.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943441/+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 1980804] Re: New bugfix release 22.0.5

[Timo Aaltonen]

tested on Intel Kaby Lake (gen9) and AMD Radeon 520 Mobile, no issues
found

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

Title:
  New bugfix release 22.0.5

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

Bug description:
  [Impact]

  This is the last point-release of the 22.0.x-series, we should put it
  in jammy so latest bugfixes would get there, and in focal for 20.04.5
  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/1980804/+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 1897932] Re: systemd-repart not packaged

[Luca Boccassi]

debdiff enabling systemd repart in the jammy/devel branch

** Patch added: "systemd_repart.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+attachment/5605761/+files/systemd_repart.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/1897932

Title:
  systemd-repart not packaged

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?

  The bug reporter would like to use it in our new raspberry pi images
  where they don't have cloud-init installed. The reporter is already
  using systemd-growfs, but they are missing the nice partition resizing
  part (so are using cloud-initramfs-growroot).

  Furthermore, in the mkosi image builder
  (https://github.com/systemd/mkosi), the systemd/mkosi developers would
  like to start using systemd-repart for partitioning. Unfortunately,
  they're currently blocked on this because 22.04 doesn't ship systemd-
  repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
  and will do so until the next Ubuntu LTS is released. If we have to
  wait for the next LTS to be released, we'll have to wait for a
  considerable amount of time before we're able to start using systemd-
  repart.

  Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
  as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
  be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.

  [Test Plan]
  This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.

  [Where problems could occur]
  Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.

  Given that there's no risk involved with enabling systemd-repart, and
  given the useful features it provides, the systemd/mkosi developers
  would like to request that systemd-repart be enabled in Ubuntu and
  backported to Jammy so that they can start adopting it in mkosi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+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 1958055] Re: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)

[Dimitri John Ledkov]

i wonder if things work fine if called with pkexec.

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

Title:
  sudo apport-kde is in a different design (stripped
  XDG_CURRENT_DESKTOP)

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  Running ubuntu-bug as normal user has the correct theme (see
  screenshots attached to bug #1881640), but running "sudo ubuntu-bug"
  has a different, non-matching theme (see attached screenshot).

  This problem can be reproduce by running a KDE application on Ubuntu
  Desktop (GNOME):

  1. Launch ubuntu-22.04-desktop-amd64.iso
  2. Install apport-kde
  3. Run: /usr/share/apport/apport-kde -f
  4. Run: sudo /usr/share/apport/apport-kde -f
  5. Compare both windows. They have different icons and font size.

  Same result with KDE:

  1. Use kubuntu-22.04-desktop-amd64.iso
  2. Run ubuntu-bug -f
  3. Run: sudo ubuntu-bug -f

  [Analysis]

  Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme,
  but XDG_CURRENT_DESKTOP is not in the list of environment variables to
  preserve (and not in env_keep in /etc/sudoers).

  [Workaround]

  Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo
  XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde
  -f

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:04:24 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1958055/+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 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.

[Julian Andres Klode]

Please note that this is not the test plan documented in the bug. But
glad this worked for you, I was not sure it was still reproducible,
hence why there's a solver dump based test case in the regression test
suite.

But your test is valid too, the test suite still needs to pass, but
failure to pass would block SRU either way, so I'll keep the tags as
done.

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

Title:
  Installing libudev1 on a new Jammy installation uninstalls many
  packages.

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Jammy:
  Fix Committed
Status in apt source package in Kinetic:
  In Progress

Bug description:
  [Impact]
  On an Ubuntu 22.04 desktop system created using the current installation 
image without enabling package updates over the network, installing the package 
libudev1 results in a large number of critical packages being removed and 
rendering the system essentially unusable.

  [Test plan]
  Comprehensive regression test suite validating a full solver dump with the 
issue is run as autopkgtest.

  [Where problems could occur]
  We could break other things from resolving. The solver is a bit finicky. 
Hopefully this is isolated enough.

  [Other info]

  https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile 
which also demonstrates the issue.
  Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, 
and then running `apt install libudev1` in the generated image results in

  The following packages will be REMOVED:
    libnss-systemd libpam-systemd systemd-timesyncd udev
  The following packages will be upgraded:
    libudev1

  This is completely prevented by ensuring that updates are installed
  from the jammy-updates repository before installing any additional
  packages and that is almost certainly the correct thing to do. But
  this is a punishing result for such a mistake.

  I would expect the installation to either force the upgrade of the
  other systemd packages or refuse to install libudev1 at the incorrect
  version relative to the other systemd packages until the system is
  upgraded.

  We found this out via a user report for ROS 2 Humble which is
  releasing on top of Ubuntu 22.04 next week:
  https://github.com/ros2/ros2/issues/1272

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974196/+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 1980804] Re: New bugfix release 22.0.5

[Timo Aaltonen]

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

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

Title:
  New bugfix release 22.0.5

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

Bug description:
  [Impact]

  This is the last point-release of the 22.0.x-series, we should put it
  in jammy so latest bugfixes would get there, and in focal for 20.04.5
  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/1980804/+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 1897932] Re: systemd-repart not packaged

[Luca Boccassi]

The upstream systemd developers team would like to request to enable
systemd-repart in Jammy in the next proposed-updates. MR:
https://code.launchpad.net/~bluca/ubuntu/+source/systemd/+git/systemd/+merge/427557

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

Title:
  systemd-repart not packaged

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?

  The bug reporter would like to use it in our new raspberry pi images
  where they don't have cloud-init installed. The reporter is already
  using systemd-growfs, but they are missing the nice partition resizing
  part (so are using cloud-initramfs-growroot).

  Furthermore, in the mkosi image builder
  (https://github.com/systemd/mkosi), the systemd/mkosi developers would
  like to start using systemd-repart for partitioning. Unfortunately,
  they're currently blocked on this because 22.04 doesn't ship systemd-
  repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
  and will do so until the next Ubuntu LTS is released. If we have to
  wait for the next LTS to be released, we'll have to wait for a
  considerable amount of time before we're able to start using systemd-
  repart.

  Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
  as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
  be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.

  [Test Plan]
  This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.

  [Where problems could occur]
  Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.

  Given that there's no risk involved with enabling systemd-repart, and
  given the useful features it provides, the systemd/mkosi developers
  would like to request that systemd-repart be enabled in Ubuntu and
  backported to Jammy so that they can start adopting it in mkosi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+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 283115] Re: Gimp: toolbox windows can't be minimized

[Guruprasad]

Fixed the upstream bug URL

** Changed in: gimp
   Importance: Low => Unknown

** Changed in: gimp
   Status: Fix Released => Unknown

** Changed in: gimp
 Remote watch: GNOME Bug Tracker #556896 => bugzilla.gnome.org/ #586664

** Bug watch added: bugzilla.gnome.org/ #556896
   https://bugzilla.gnome.org/show_bug.cgi?id=556896

** Changed in: gimp
 Remote watch: bugzilla.gnome.org/ #586664 => bugzilla.gnome.org/ #556896

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

Title:
  Gimp: toolbox windows can't be minimized

Status in The Gimp:
  Unknown
Status in GTK+:
  Unknown
Status in gimp package in Ubuntu:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  gimp 2.6 in intrepid:
  it is impossible to minimize toolbar windows; they have only a x-Button to 
close

  ideally, these windows should be minimized automatically when the
  (last) Gimp image window is minimized

  Update
  While waiting, I designed some sort of workaround :
  Gnome>System>Preferences>Windows>Double-click titlebar>Roll up

To manage notifications about this bug go to:
https://bugs.launchpad.net/gimp/+bug/283115/+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 1477584] Re: package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Pavan K]

Please close the ticket. I have not seen the issue in later versions of
Ubuntu.

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

Title:
  package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in rsyslog package in Ubuntu:
  Incomplete

Bug description:
  Identified the issue after upgrade to 15.04 from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: rsyslog 7.4.4-1ubuntu14
  ProcVersionSignature: Ubuntu 3.16.0-43.58-generic 3.16.7-ckt13
  Uname: Linux 3.16.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Thu Jul 23 14:34:45 2015
  DuplicateSignature: package:rsyslog:7.4.4-1ubuntu14:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-07-12 (11 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: rsyslog
  Title: package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1477584/+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 1802483] Update Released

[Łukasz Zemczak]

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

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

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  Fix Released
Status in libnotify source package in Bionic:
  Fix Committed
Status in libnotify source package in Focal:
  Fix Committed
Status in libnotify source package in Jammy:
  Fix Released

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems.

  

  [ Impact ]

  Icons sonuds and desktop files referenced by a snapped app using
  notifications aren't exposed to the desktop in absolute paths

  [ Test case ]

  Build the test snap (or install it from the attached files to this bug):
    git clone https://github.com/3v1n0/notify-send-test-snap
    snapcraft prime
    snap try prime

  To use the pre-built snap 
(https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7)
    snap install --dangerous notify-send-test-snap_*.snap

  Check that icons are shown when launching:
    notify-send-test-snap
    notify-send-test-snap.image-path
notify-send-test-snap.image-uri

  Ensure that desktop entry is correctly sent, monitoring the dbus
  session:

   In a terminal:
     dbus-monitor --session --monitor 
"interface='org.freedesktop.Notifications'"

   In the other:
     notify-send-test-snap.desktop-entry
     notify-send-test-snap.desktop-entry-explicit-id
     notify-send-test-snap.desktop-entry-explicit-file-name
     notify-send-test-snap.desktop-entry-explicit-path
     notify-send-test-snap.desktop-entry-explicit-uri
     notify-send-test-snap.desktop-entry-explicit-snapped-uri

  The
   `desktop-entry` value sent to dbus should be either:
     - A `notify-send-test-snap_`-prefixed desktop ID
     - A .desktop file path (readable from both inside and outside the snap)
     - A .desktop file uri (readable from both inside and outside the snap)

  [ Regression potential ]

  Normal applications that are run with a SNAP environment variable set,
  might use wrong paths for files or desktop file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace

[Launchpad Bug Tracker]

This bug was fixed in the package libnotify - 0.7.9-3ubuntu5.22.04.1

---
libnotify (0.7.9-3ubuntu5.22.04.1) jammy; urgency=medium

  * debian: Update references as per ubuntu/jammy branching
  * debian/patches: Exit with an error if showing notification fails
(LP: #1970647)
  * debian/patches: Handle file paths, uris and desktop-ID's in Snapped apps
(LP: #1802483)

 -- Marco Trevisan (Treviño)   Wed, 27 Apr 2022
23:23:22 +0200

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

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

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  Fix Released
Status in libnotify source package in Bionic:
  Fix Committed
Status in libnotify source package in Focal:
  Fix Committed
Status in libnotify source package in Jammy:
  Fix Released

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems.

  

  [ Impact ]

  Icons sonuds and desktop files referenced by a snapped app using
  notifications aren't exposed to the desktop in absolute paths

  [ Test case ]

  Build the test snap (or install it from the attached files to this bug):
    git clone https://github.com/3v1n0/notify-send-test-snap
    snapcraft prime
    snap try prime

  To use the pre-built snap 
(https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7)
    snap install --dangerous notify-send-test-snap_*.snap

  Check that icons are shown when launching:
    notify-send-test-snap
    notify-send-test-snap.image-path
notify-send-test-snap.image-uri

  Ensure that desktop entry is correctly sent, monitoring the dbus
  session:

   In a terminal:
     dbus-monitor --session --monitor 
"interface='org.freedesktop.Notifications'"

   In the other:
     notify-send-test-snap.desktop-entry
     notify-send-test-snap.desktop-entry-explicit-id
     notify-send-test-snap.desktop-entry-explicit-file-name
     notify-send-test-snap.desktop-entry-explicit-path
     notify-send-test-snap.desktop-entry-explicit-uri
     notify-send-test-snap.desktop-entry-explicit-snapped-uri

  The
   `desktop-entry` value sent to dbus should be either:
     - A `notify-send-test-snap_`-prefixed desktop ID
     - A .desktop file path (readable from both inside and outside the snap)
     - A .desktop file uri (readable from both inside and outside the snap)

  [ Regression potential ]

  Normal applications that are run with a SNAP environment variable set,
  might use wrong paths for files or desktop file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1897932] Re: systemd-repart not packaged

[Christian Ehrhardt ]

I was asked to add a Jammy task, I did so - the details and if that will
be done is up to your consideration/discussion/decision.

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

Title:
  systemd-repart not packaged

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?

  The bug reporter would like to use it in our new raspberry pi images
  where they don't have cloud-init installed. The reporter is already
  using systemd-growfs, but they are missing the nice partition resizing
  part (so are using cloud-initramfs-growroot).

  Furthermore, in the mkosi image builder
  (https://github.com/systemd/mkosi), the systemd/mkosi developers would
  like to start using systemd-repart for partitioning. Unfortunately,
  they're currently blocked on this because 22.04 doesn't ship systemd-
  repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
  and will do so until the next Ubuntu LTS is released. If we have to
  wait for the next LTS to be released, we'll have to wait for a
  considerable amount of time before we're able to start using systemd-
  repart.

  Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
  as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
  be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.

  [Test Plan]
  This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.

  [Where problems could occur]
  Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.

  Given that there's no risk involved with enabling systemd-repart, and
  given the useful features it provides, the systemd/mkosi developers
  would like to request that systemd-repart be enabled in Ubuntu and
  backported to Jammy so that they can start adopting it in mkosi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+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 1897932] Re: systemd-repart not packaged

[Luca Boccassi]

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

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

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

Title:
  systemd-repart not packaged

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?

  The bug reporter would like to use it in our new raspberry pi images
  where they don't have cloud-init installed. The reporter is already
  using systemd-growfs, but they are missing the nice partition resizing
  part (so are using cloud-initramfs-growroot).

  Furthermore, in the mkosi image builder
  (https://github.com/systemd/mkosi), the systemd/mkosi developers would
  like to start using systemd-repart for partitioning. Unfortunately,
  they're currently blocked on this because 22.04 doesn't ship systemd-
  repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
  and will do so until the next Ubuntu LTS is released. If we have to
  wait for the next LTS to be released, we'll have to wait for a
  considerable amount of time before we're able to start using systemd-
  repart.

  Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
  as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
  be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.

  [Test Plan]
  This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.

  [Where problems could occur]
  Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.

  Given that there's no risk involved with enabling systemd-repart, and
  given the useful features it provides, the systemd/mkosi developers
  would like to request that systemd-repart be enabled in Ubuntu and
  backported to Jammy so that they can start adopting it in mkosi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+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 1897932] Re: systemd-repart not packaged

[Christian Ehrhardt ]

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

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

Title:
  systemd-repart not packaged

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?

  The bug reporter would like to use it in our new raspberry pi images
  where they don't have cloud-init installed. The reporter is already
  using systemd-growfs, but they are missing the nice partition resizing
  part (so are using cloud-initramfs-growroot).

  Furthermore, in the mkosi image builder
  (https://github.com/systemd/mkosi), the systemd/mkosi developers would
  like to start using systemd-repart for partitioning. Unfortunately,
  they're currently blocked on this because 22.04 doesn't ship systemd-
  repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
  and will do so until the next Ubuntu LTS is released. If we have to
  wait for the next LTS to be released, we'll have to wait for a
  considerable amount of time before we're able to start using systemd-
  repart.

  Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
  as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
  be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.

  [Test Plan]
  This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.

  [Where problems could occur]
  Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.

  Given that there's no risk involved with enabling systemd-repart, and
  given the useful features it provides, the systemd/mkosi developers
  would like to request that systemd-repart be enabled in Ubuntu and
  backported to Jammy so that they can start adopting it in mkosi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+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 1970647] Update Released

[Łukasz Zemczak]

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

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

Title:
  notify-send exit code doesn't match result

Status in libnotify package in Ubuntu:
  Fix Released
Status in libnotify source package in Focal:
  Fix Committed
Status in libnotify source package in Jammy:
  Fix Released

Bug description:
  No error exit code is returned by notify-send on failure

  [ Test case ]

  1. Run:
     env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error
  2. In a terminal "error" should be printed

  [ Regression potential ]

  Programs relying on notify-send may have errors when they did not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1970647/+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 1970647] Re: notify-send exit code doesn't match result

[Launchpad Bug Tracker]

This bug was fixed in the package libnotify - 0.7.9-3ubuntu5.22.04.1

---
libnotify (0.7.9-3ubuntu5.22.04.1) jammy; urgency=medium

  * debian: Update references as per ubuntu/jammy branching
  * debian/patches: Exit with an error if showing notification fails
(LP: #1970647)
  * debian/patches: Handle file paths, uris and desktop-ID's in Snapped apps
(LP: #1802483)

 -- Marco Trevisan (Treviño)   Wed, 27 Apr 2022
23:23:22 +0200

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

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

Title:
  notify-send exit code doesn't match result

Status in libnotify package in Ubuntu:
  Fix Released
Status in libnotify source package in Focal:
  Fix Committed
Status in libnotify source package in Jammy:
  Fix Released

Bug description:
  No error exit code is returned by notify-send on failure

  [ Test case ]

  1. Run:
     env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error
  2. In a terminal "error" should be printed

  [ Regression potential ]

  Programs relying on notify-send may have errors when they did not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1970647/+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 1980239] Re: Update gstreamer to 1.20.3

[Launchpad Bug Tracker]

This bug was fixed in the package gst-plugins-good1.0 - 1.20.3-0ubuntu1

---
gst-plugins-good1.0 (1.20.3-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1980239)

 -- Jeremy Bicha   Wed, 29 Jun 2022 09:59:39 -0400

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

Title:
  Update gstreamer to 1.20.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-bad1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-good1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Jammy:
  In Progress
Status in gst-python1.0 source package in Jammy:
  Won't Fix
Status in gst-rtsp-server1.0 source package in Jammy:
  In Progress
Status in gstreamer-editing-services1.0 source package in Jammy:
  Incomplete
Status in gstreamer-vaapi source package in Jammy:
  Triaged
Status in gstreamer1.0 source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  Since Ubuntu 22.04 LTS's release with gstreamer 1.20.1, there have been two 
bugfix stable releases. 

  https://gstreamer.freedesktop.org/releases/1.20/#1.20.2
  https://gstreamer.freedesktop.org/releases/1.20/#1.20.3

  Test Case 1
  ---
  We now run upstream's test suite for most gstreamer components at build time 
and fail the build for errors on our key desktop architectures, amd64 & arm64.

  Ensure the builds succeeed.

  Test Case 2
  ---
  Play a variety of videos in Totem. Play a variety of audio tracks in 
Rhythmbox. Try to stream audio and/or video. Try to install a missing codec.

  In all cases, make sure that everything which worked before still
  works.

  What Could Go Wrong
  ---
  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1980239/+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 1980239] Update Released

[Łukasz Zemczak]

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

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

Title:
  Update gstreamer to 1.20.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-bad1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-good1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Jammy:
  In Progress
Status in gst-python1.0 source package in Jammy:
  Won't Fix
Status in gst-rtsp-server1.0 source package in Jammy:
  In Progress
Status in gstreamer-editing-services1.0 source package in Jammy:
  Incomplete
Status in gstreamer-vaapi source package in Jammy:
  Triaged
Status in gstreamer1.0 source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  Since Ubuntu 22.04 LTS's release with gstreamer 1.20.1, there have been two 
bugfix stable releases. 

  https://gstreamer.freedesktop.org/releases/1.20/#1.20.2
  https://gstreamer.freedesktop.org/releases/1.20/#1.20.3

  Test Case 1
  ---
  We now run upstream's test suite for most gstreamer components at build time 
and fail the build for errors on our key desktop architectures, amd64 & arm64.

  Ensure the builds succeeed.

  Test Case 2
  ---
  Play a variety of videos in Totem. Play a variety of audio tracks in 
Rhythmbox. Try to stream audio and/or video. Try to install a missing codec.

  In all cases, make sure that everything which worked before still
  works.

  What Could Go Wrong
  ---
  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1980239/+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 1980239] Re: Update gstreamer to 1.20.3

[Launchpad Bug Tracker]

This bug was fixed in the package gst-plugins-bad1.0 - 1.20.3-0ubuntu1

---
gst-plugins-bad1.0 (1.20.3-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1980239)

 -- Jeremy Bicha   Wed, 29 Jun 2022 09:50:26 -0400

** Changed in: gst-plugins-good1.0 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Update gstreamer to 1.20.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-bad1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-good1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Jammy:
  In Progress
Status in gst-python1.0 source package in Jammy:
  Won't Fix
Status in gst-rtsp-server1.0 source package in Jammy:
  In Progress
Status in gstreamer-editing-services1.0 source package in Jammy:
  Incomplete
Status in gstreamer-vaapi source package in Jammy:
  Triaged
Status in gstreamer1.0 source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  Since Ubuntu 22.04 LTS's release with gstreamer 1.20.1, there have been two 
bugfix stable releases. 

  https://gstreamer.freedesktop.org/releases/1.20/#1.20.2
  https://gstreamer.freedesktop.org/releases/1.20/#1.20.3

  Test Case 1
  ---
  We now run upstream's test suite for most gstreamer components at build time 
and fail the build for errors on our key desktop architectures, amd64 & arm64.

  Ensure the builds succeeed.

  Test Case 2
  ---
  Play a variety of videos in Totem. Play a variety of audio tracks in 
Rhythmbox. Try to stream audio and/or video. Try to install a missing codec.

  In all cases, make sure that everything which worked before still
  works.

  What Could Go Wrong
  ---
  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1980239/+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 1980239] Re: Update gstreamer to 1.20.3

[Launchpad Bug Tracker]

This bug was fixed in the package gstreamer1.0 - 1.20.3-0ubuntu1

---
gstreamer1.0 (1.20.3-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1980239)

 -- Jeremy Bicha   Thu, 30 Jun 2022 09:26:38 -0400

** Changed in: gst-plugins-bad1.0 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Update gstreamer to 1.20.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-bad1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-good1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Jammy:
  In Progress
Status in gst-python1.0 source package in Jammy:
  Won't Fix
Status in gst-rtsp-server1.0 source package in Jammy:
  In Progress
Status in gstreamer-editing-services1.0 source package in Jammy:
  Incomplete
Status in gstreamer-vaapi source package in Jammy:
  Triaged
Status in gstreamer1.0 source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  Since Ubuntu 22.04 LTS's release with gstreamer 1.20.1, there have been two 
bugfix stable releases. 

  https://gstreamer.freedesktop.org/releases/1.20/#1.20.2
  https://gstreamer.freedesktop.org/releases/1.20/#1.20.3

  Test Case 1
  ---
  We now run upstream's test suite for most gstreamer components at build time 
and fail the build for errors on our key desktop architectures, amd64 & arm64.

  Ensure the builds succeeed.

  Test Case 2
  ---
  Play a variety of videos in Totem. Play a variety of audio tracks in 
Rhythmbox. Try to stream audio and/or video. Try to install a missing codec.

  In all cases, make sure that everything which worked before still
  works.

  What Could Go Wrong
  ---
  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1980239/+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 1980239] Re: Update gstreamer to 1.20.3

[Launchpad Bug Tracker]

This bug was fixed in the package gst-libav1.0 - 1.20.3-0ubuntu1

---
gst-libav1.0 (1.20.3-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1980239)

 -- Jeremy Bicha   Wed, 29 Jun 2022 09:32:37 -0400

** Changed in: gst-libav1.0 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** Changed in: gstreamer1.0 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Update gstreamer to 1.20.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-bad1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-good1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Jammy:
  In Progress
Status in gst-python1.0 source package in Jammy:
  Won't Fix
Status in gst-rtsp-server1.0 source package in Jammy:
  In Progress
Status in gstreamer-editing-services1.0 source package in Jammy:
  Incomplete
Status in gstreamer-vaapi source package in Jammy:
  Triaged
Status in gstreamer1.0 source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  Since Ubuntu 22.04 LTS's release with gstreamer 1.20.1, there have been two 
bugfix stable releases. 

  https://gstreamer.freedesktop.org/releases/1.20/#1.20.2
  https://gstreamer.freedesktop.org/releases/1.20/#1.20.3

  Test Case 1
  ---
  We now run upstream's test suite for most gstreamer components at build time 
and fail the build for errors on our key desktop architectures, amd64 & arm64.

  Ensure the builds succeeed.

  Test Case 2
  ---
  Play a variety of videos in Totem. Play a variety of audio tracks in 
Rhythmbox. Try to stream audio and/or video. Try to install a missing codec.

  In all cases, make sure that everything which worked before still
  works.

  What Could Go Wrong
  ---
  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1980239/+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 1923541] Re: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'

[Benjamin Drung]

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

Probably this KeyError was never fixed (the changelog entry for version
2.20.11-0ubuntu65 talks about something else). So I mark this bug as
duplicate of bug #1964828.

** This bug has been marked a duplicate of bug 1964828
   /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'

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

Title:
  /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError:
  'CasperMD5json'

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Hirsute:
  Fix Released

Bug description:
  Currently running 21.04, apport version is 2.20.11-0ubuntu62 .

  When I try to fill a bug, I see:

  $ ubuntu-bug  network-manager
  ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info
  apport.hookutils.attach_casper_md5check(report,
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1002, in 
attach_casper_md5check
  del report['CasperMD5json']
File "/usr/lib/python3.9/collections/__init__.py", line 1064, in __delitem__
  del self.data[key]
  KeyError: 'CasperMD5json'

  
  It's not crashing the bug reporting itself, but it looks wrong to have a 
stacktrace on the command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1923541/+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 1979347] Update Released

[Łukasz Zemczak]

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

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

Title:
  SRU pygobject 3.42.1, including fix for the append function

Status in pygobject package in Ubuntu:
  Fix Released
Status in pygobject source package in Jammy:
  Fix Released

Bug description:
  >> Impact <<

  Applications crash when they call the append function to append data
  to stores.

  >> Test plan <<

  When executing the attached bug.py script,

  - With the fix: A dummy window with a text field is mapped.

  - Without the fix: An error message is raised and no window is mapped.

  >> Regression potential <<

  Since this includes a new upstream release, by looking at the NEWS
  file ,
  regressions could show up:

  - On programs which use ListStore and Treeview. Additionally, those
  changes should not affect GTK2 or GTK3.

  - As leaks, given the replace of g_error by g_critical by
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1979347/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29

[Andrea Righi]

** Also affects: network-manager (Ubuntu Kinetic)
   Importance: Undecided
   Status: Invalid

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Invalid

** Also affects: urfkill (Ubuntu Kinetic)
   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/1971418

Title:
  network-manager/1.36.4-2ubuntu1 ADT test failure with
  linux/5.15.0-28.29

Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid
Status in urfkill package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Released
Status in network-manager source package in Jammy:
  Invalid
Status in urfkill source package in Jammy:
  New
Status in linux source package in Kinetic:
  Invalid
Status in network-manager source package in Kinetic:
  Invalid
Status in urfkill source package in Kinetic:
  New

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

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1979347] Re: SRU pygobject 3.42.1, including fix for the append function

[Launchpad Bug Tracker]

This bug was fixed in the package pygobject - 3.42.1-0ubuntu1

---
pygobject (3.42.1-0ubuntu1) jammy; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release (fixes LP: #1979347)
  * Drop python3.10 patch: applied in new release

 -- Nathan Pratta Teodosio   Thu, 23 Jun
2022 12:56:55 -0300

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

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

Title:
  SRU pygobject 3.42.1, including fix for the append function

Status in pygobject package in Ubuntu:
  Fix Released
Status in pygobject source package in Jammy:
  Fix Released

Bug description:
  >> Impact <<

  Applications crash when they call the append function to append data
  to stores.

  >> Test plan <<

  When executing the attached bug.py script,

  - With the fix: A dummy window with a text field is mapped.

  - Without the fix: An error message is raised and no window is mapped.

  >> Regression potential <<

  Since this includes a new upstream release, by looking at the NEWS
  file ,
  regressions could show up:

  - On programs which use ListStore and Treeview. Additionally, those
  changes should not affect GTK2 or GTK3.

  - As leaks, given the replace of g_error by g_critical by
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1979347/+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 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.

[vishnunaini]

We have tested the proposed patched version 2.4.7 against the current
release version 2.4.5 posted at the above launchpad link via bug
reproduction and general package installation process via standard cli
and via python bindings and have no adverse observations.

We have also tested against a package we built from the accepted source
and the upstream salsa.debian.org source

Test environment:
root@test100:/home/sre# lsb_release -a
Distributor ID: Ubuntu
Description:Ubuntu 22.04 LTS
Release:22.04
Codename:   jammy

Test Cases for both versions 2.4.5 and 2.4.7:
1. Manual APT Bash CLI
2. SaltStack 3004.2 via APT Python bindings

Current release version 2.4.5:

root@test100:/home/user# apt --version
apt 2.4.5 (amd64)
root@test100:/home/user# dpkg -l | grep apt
ii  apt   2.4.5 
 amd64commandline package manager
ii  apt-utils 2.4.5 
 amd64package management related utility programs
ii  libapt-pkg6.0:amd64   2.4.5 
 amd64package management runtime library
ii  libpcap0.8:amd64  1.10.1-4build1
 amd64system interface for user-level packet capture
ii  python-apt-common 2.3.0ubuntu2  
 all  Python interface to libapt-pkg (locales)
ii  python3-apt   2.3.0ubuntu2  
 amd64Python 3 interface to libapt-pkg

root@cor-uefitest100:/home/sre# apt install libudev1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  busybox-initramfs cryptsetup finalrd gir1.2-packagekitglib-1.0 
initramfs-tools-bin klibc-utils libappstream4 libdw1 libglib2.0-bin 
libgstreamer1.0-0 libisns0 libklibc libnetplan0 libopeniscsiusr 
libpackagekit-glib2-18 libplymouth5
  libpolkit-agent-1-0 libpolkit-gobject-1-0 libsgutils2-2 libstemmer0d liburcu8 
libxmlb2 python3-software-properties sg3-utils
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libnetplan0
The following packages will be REMOVED:
  cloud-init cloud-initramfs-copymods cloud-initramfs-dyn-netconf 
cryptsetup-initramfs dbus-user-session friendly-recovery initramfs-tools 
initramfs-tools-core kpartx libnss-systemd libpam-systemd mdadm multipath-tools 
netplan.io open-iscsi
  overlayroot packagekit packagekit-tools pkexec plymouth 
plymouth-theme-ubuntu-text policykit-1 polkitd sg3-utils-udev 
software-properties-common ubuntu-minimal ubuntu-server ubuntu-standard udev
The following packages will be upgraded:
  libnetplan0 libudev1
2 upgraded, 0 newly installed, 29 to remove and 35 not upgraded.
Need to get 166 kB of archives.
After this operation, 22.4 MB disk space will be freed.
Do you want to continue? [Y/n]

Proposed release version 2.4.7:
root@test101:/home/user/apt# apt install ./apt_2.4.7_amd64.deb 
./libapt-pkg6.0_2.4.7_amd64.deb ./apt-utils_2.4.7_amd64.deb

root@test101:/home/user/apt# apt --version
apt 2.4.7 (amd64)

root@test101:/home/user/apt# dpkg -l | grep apt
ii  apt   2.4.7 
 amd64commandline package manager
ii  apt-utils 2.4.7 
 amd64package management related utility programs
ii  libapt-pkg6.0:amd64   2.4.7 
 amd64package management runtime library
ii  libpcap0.8:amd64  1.10.1-4build1
 amd64system interface for user-level packet capture
ii  python-apt-common 2.3.0ubuntu2  
 all  Python interface to libapt-pkg (locales)
ii  python3-apt   2.3.0ubuntu2  
 amd64Python 3 interface to libapt-pkg

root@test101:/home/user/apt# apt install libudev1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  libnss-systemd libpam-systemd libsystemd0 systemd systemd-sysv udev
Suggested packages:
  systemd-container libtss2-esys-3.0.2-0 libtss2-mu0 libtss2-rc0
The following packages will be upgraded:
  libnss-systemd libpam-systemd libsystemd0 libudev1 systemd systemd-sysv udev
7 upgraded, 0 newly installed, 0 to remove and 44 not upgraded.
Need to get 6875 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libnss-systemd 
amd64 249.11-0ubuntu3.4 [133 kB]
Get:2 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 libsystemd0 
amd64 2

[Touch-packages] [Bug 1897932] Re: systemd-repart not packaged

[Luca Boccassi]

** Description changed:

+ [Impact]
+ 
  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?
  
- I'd like to use it in our new raspberry pi images where we don't have
- cloud-init installed. We're already using systemd-growfs, but we are
- missing the nice partition resizing part (so are using cloud-initramfs-
- growroot).
+ The bug reporter would like to use it in our new raspberry pi images
+ where they don't have cloud-init installed. The reporter is already
+ using systemd-growfs, but they are missing the nice partition resizing
+ part (so are using cloud-initramfs-growroot).
  
- Could you please consider enabling it? In another binary package - so it
- can have extra deps - would be just fine by me.
+ Furthermore, in the mkosi image builder
+ (https://github.com/systemd/mkosi), the systemd/mkosi developers would
+ like to start using systemd-repart for partitioning. Unfortunately,
+ they're currently blocked on this because 22.04 doesn't ship systemd-
+ repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
+ and will do so until the next Ubuntu LTS is released. If we have to wait
+ for the next LTS to be released, we'll have to wait for a considerable
+ amount of time before we're able to start using systemd-repart.
+ 
+ Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
+ as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
+ be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.
+ 
+ [Test Plan]
+ This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.
+ 
+ [Where problems could occur]
+ Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.
+ 
+ Given that there's no risk involved with enabling systemd-repart, and
+ given the useful features it provides, the systemd/mkosi developers
+ would like to request that systemd-repart be enabled in Ubuntu and
+ backported to Jammy so that they can start adopting it in mkosi.

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

Title:
  systemd-repart not packaged

Status in systemd package in Ubuntu:
  Triaged
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
  Ubuntu/Debian packages of systemd - probably because it has an extra
  dependency?

  The bug reporter would like to use it in our new raspberry pi images
  where they don't have cloud-init installed. The reporter is already
  using systemd-growfs, but they are missing the nice partition resizing
  part (so are using cloud-initramfs-growroot).

  Furthermore, in the mkosi image builder
  (https://github.com/systemd/mkosi), the systemd/mkosi developers would
  like to start using systemd-repart for partitioning. Unfortunately,
  they're currently blocked on this because 22.04 doesn't ship systemd-
  repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy
  and will do so until the next Ubuntu LTS is released. If we have to
  wait for the next LTS to be released, we'll have to wait for a
  considerable amount of time before we're able to start using systemd-
  repart.

  Being able to use systemd-repart will allow the systemd/mkosi developers to 
take advantage of its improved interface compared to sfdisk,
  as well as its builtin protections against race conditions surrounding the 
use of loop devices. The systemd/mkosi developers expect to
  be able to get rid of some nasty loop device failure in mkosi by using 
systemd-repart.

  [Test Plan]
  This is a missing extra executable. Once enabled it has self-tests in the 
build-time unit tests, and also a regression test in the autopkgtest 'upstream' 
suite.

  [Where problems could occur]
  Shipping systemd-repart will come with no additional risk. While there is a 
systemd-repart.service that runs on boot, it's configured to not do anything if 
no config files are shipped with the system or provided by the user. As such, 
the service, if enabled, will effectively be a noop. Aside from the service, 
there's the CLI tool systemd-repart and the accompanying man pages that will be 
shipped as part of the systemd package.

  Given that

[Touch-packages] [Bug 1742912] Re: Please confine guest sessions again

[martinr]

Please be aware when configuring app-armor of the Firefox snap, that breaks the 
guest-account experience in Xubuntu 22.04 LTS with Firefox version: 102.0.1 
(64-bit), Mozilla Firefox Snap for Ubuntu canonical-002-1.0.
See Bug #1981881 .

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

Title:
  Please confine guest sessions again

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  This is a continuation of LP: #1663157 where as a workaround for the
  guest session not being confined the session got disabled. This bug
  tracks the fix for proper confinement.

  Original bug report text:

  
  Processes launched under a lightdm guest session are not confined by the 
/usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 
17.04, and Ubuntu Artful (current dev release). The processes are unconfined.

  The simple test case is to log into a guest session, launch a terminal
  with ctrl-alt-t, and run the following command:

   $ cat /proc/self/attr/current

  Expected output, as seen in Ubuntu 16.04 LTS, is:

   /usr/lib/lightdm/lightdm-guest-session (enforce)

  Running the command inside of an Ubuntu 16.10 and newer guest session
  results in:

   unconfined

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1742912/+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 1881640] Re: apport-kde: Some window asks with empty text

[Benjamin Drung]

This bug is fixed in Ubuntu 22.04. Apport will show following question
there:

Your display manager log files may help developers diagnose the bug, but
may contain sensitive information such as your hostname. Do you want to
include these logs in your bug report?

** Tags added: bionic

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

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

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

Title:
  apport-kde: Some window asks with empty text

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  [Testcase]

  1. Launch Kubuntu (e.g. kubuntu-20.04.4-desktop-amd64.iso)
  2. Open a terminal and run: ubuntu-bug -f
  3. "What kind of problem[...]" -> select first entry
  4. "What display problem[...]" -> select last entry
  5. You will get question window just asking "text"

  [Original report]

  Some window asks with empty text.

  1. in terminal run ubuntu-bug -f
  2. Select other problem
  3. Select i dont know
  4. comes up windows asking "text" and options Yes / No

  Other examples in other bugs with this example. Bug #1958054 and Bug
  #1958055

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportLog: Error: [Errno 13] Permission denied: '/var/log/apport.log'
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports: 640:1001:125:4063351:2020-06-01 21:05:01.891745699 
+0300:2020-06-01 21:04:59.835739474 
+0300:/var/crash/_usr_share_code_code.1001.crash
  CurrentDesktop: KDE
  Date: Mon Jun  1 21:09:41 2020
  InstallationDate: Installed on 2020-03-10 (83 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200310)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881640/+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 1967965] Re: apport-kde: "Other problem" and "Display" options are swapped

[Benjamin Drung]

This bug goes back at least to Ubuntu 20.04 (focal).

** Description changed:

+ [Testcase]
+ 
+ 1. Run: /usr/share/apport/apport-kde -f
+ 2. Select "Display (X.org)" and click OK
+ 3. Then a window asking "What display problem do you observe?" should be 
presented.
+ 
+ [Original report]
+ 
  When attempting to report
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967963 I was unable
  to use `ubuntu-bug firefox`, so I just ran `ubuntu-bug`. However doing
  so gave me a menu with unrelated option (as expected) and an "Other
  problem..." option. I assumed this was for generic other bugs, as I
  think is reasonable; however, it brings me to a menu that only makes
  sense for display-related bugs. I think this text should be changed to
  note that; perhaps "Other display problem...".
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
-  640:1000:124:13488049:2022-03-30 13:20:08.905176436 -0500:2022-03-30 
13:20:07.977480154 -0500:/var/crash/_usr_bin_telegram-desktop.1000.crash
-  640:0:124:755694:2022-03-30 13:17:26.598466630 -0500:2022-03-30 
13:17:26.258453989 -0500:/var/crash/_usr_libexec_udisks2_udisksd.0.crash
+  640:1000:124:13488049:2022-03-30 13:20:08.905176436 -0500:2022-03-30 
13:20:07.977480154 -0500:/var/crash/_usr_bin_telegram-desktop.1000.crash
+  640:0:124:755694:2022-03-30 13:17:26.598466630 -0500:2022-03-30 
13:17:26.258453989 -0500:/var/crash/_usr_libexec_udisks2_udisksd.0.crash
  CurrentDesktop: KDE
  Date: Tue Apr  5 19:58:56 2022
  InstallationDate: Installed on 2022-03-30 (6 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/usr/bin/zsh
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/usr/bin/zsh
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: apport (Ubuntu)
   Status: New => Triaged

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

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

** Also affects: apport (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

** Also affects: apport
   Importance: Undecided
   Status: New

** Changed in: apport
   Importance: Undecided => High

** Changed in: apport
   Status: New => Triaged

** Changed in: apport
Milestone: None => 2.23.0

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

Title:
  apport-kde: "Other problem" and "Display" options are swapped

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Focal:
  New
Status in apport source package in Jammy:
  New

Bug description:
  [Testcase]

  1. Run: /usr/share/apport/apport-kde -f
  2. Select "Display (X.org)" and click OK
  3. Then a window asking "What display problem do you observe?" should be 
presented.

  [Original report]

  When attempting to report
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967963 I was
  unable to use `ubuntu-bug firefox`, so I just ran `ubuntu-bug`.
  However doing so gave me a menu with unrelated option (as expected)
  and an "Other problem..." option. I assumed this was for generic other
  bugs, as I think is reasonable; however, it brings me to a menu that
  only makes sense for display-related bugs. I think this text should be
  changed to note that; perhaps "Other display problem...".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1000:124:13488049:2022-03-30 13:20:08.905176436 -0500:2022-03-30 
13:20:07.977480154 -0500:/var/crash/_usr_bin_telegram-desktop.1000.crash
   640:0:124:755694:2022-03-30 13:17:26.598466630 -0500:2022-03-30 
13:17:26.258453989 -0500:/var/crash/_usr_libexec_udisks2_udisksd.0.crash
  CurrentDesktop: KDE
  Date: Tue Apr  5 19:58:56 2022
  InstallationDate: Installed on 2022-03-30 (6 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage noti

[Touch-packages] [Bug 1881640] Re: apport-kde: Some window asks with empty text

[Benjamin Drung]

** Summary changed:

- Some window asks with empty text
+ apport-kde: Some window asks with empty text

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

Title:
  apport-kde: Some window asks with empty text

Status in apport package in Ubuntu:
  New

Bug description:
  [Testcase]

  1. Launch Kubuntu (e.g. kubuntu-20.04.4-desktop-amd64.iso)
  2. Open a terminal and run: ubuntu-bug -f
  3. "What kind of problem[...]" -> select first entry
  4. "What display problem[...]" -> select last entry
  5. You will get question window just asking "text"

  [Original report]

  Some window asks with empty text.

  1. in terminal run ubuntu-bug -f
  2. Select other problem
  3. Select i dont know
  4. comes up windows asking "text" and options Yes / No

  Other examples in other bugs with this example. Bug #1958054 and Bug
  #1958055

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportLog: Error: [Errno 13] Permission denied: '/var/log/apport.log'
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports: 640:1001:125:4063351:2020-06-01 21:05:01.891745699 
+0300:2020-06-01 21:04:59.835739474 
+0300:/var/crash/_usr_share_code_code.1001.crash
  CurrentDesktop: KDE
  Date: Mon Jun  1 21:09:41 2020
  InstallationDate: Installed on 2020-03-10 (83 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200310)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881640/+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 1967965] Re: apport-kde: "Other problem" and "Display" options are swapped

[Benjamin Drung]

The important bit here is that only apport-kde, but not apport-gtk is
affected. Then it is easily reproducible and simple to fix: The order of
items is reversed.

** Summary changed:

- "Other problem" and "Display" options are swapped
+ apport-kde: "Other problem" and "Display" options are swapped

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

Title:
  apport-kde: "Other problem" and "Display" options are swapped

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Focal:
  New
Status in apport source package in Jammy:
  New

Bug description:
  [Testcase]

  1. Run: /usr/share/apport/apport-kde -f
  2. Select "Display (X.org)" and click OK
  3. Then a window asking "What display problem do you observe?" should be 
presented.

  [Original report]

  When attempting to report
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967963 I was
  unable to use `ubuntu-bug firefox`, so I just ran `ubuntu-bug`.
  However doing so gave me a menu with unrelated option (as expected)
  and an "Other problem..." option. I assumed this was for generic other
  bugs, as I think is reasonable; however, it brings me to a menu that
  only makes sense for display-related bugs. I think this text should be
  changed to note that; perhaps "Other display problem...".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1000:124:13488049:2022-03-30 13:20:08.905176436 -0500:2022-03-30 
13:20:07.977480154 -0500:/var/crash/_usr_bin_telegram-desktop.1000.crash
   640:0:124:755694:2022-03-30 13:17:26.598466630 -0500:2022-03-30 
13:17:26.258453989 -0500:/var/crash/_usr_libexec_udisks2_udisksd.0.crash
  CurrentDesktop: KDE
  Date: Tue Apr  5 19:58:56 2022
  InstallationDate: Installed on 2022-03-30 (6 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1967965/+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 1881640] Re: Some window asks with empty text

[Benjamin Drung]

** Description changed:

- Some window asks with empty text
- in terminal ubuntu-bug
- Select other problem
- Select i dont know
- comes up windows asking "text" and options Yes / No
+ [Testcase]
+ 
+ 1. Launch Kubuntu (e.g. kubuntu-20.04.4-desktop-amd64.iso)
+ 2. Open a terminal and run: ubuntu-bug -f
+ 3. "What kind of problem[...]" -> select first entry
+ 4. "What display problem[...]" -> select last entry
+ 5. You will get question window just asking "text"
+ 
+ [Original report]
+ 
+ Some window asks with empty text.
+ 
+ 1. in terminal run ubuntu-bug -f
+ 2. Select other problem
+ 3. Select i dont know
+ 4. comes up windows asking "text" and options Yes / No
  
  Other examples in other bugs with this example. Bug #1958054 and Bug
  #1958055
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportLog: Error: [Errno 13] Permission denied: '/var/log/apport.log'
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports: 640:1001:125:4063351:2020-06-01 21:05:01.891745699 
+0300:2020-06-01 21:04:59.835739474 
+0300:/var/crash/_usr_share_code_code.1001.crash
  CurrentDesktop: KDE
  Date: Mon Jun  1 21:09:41 2020
  InstallationDate: Installed on 2020-03-10 (83 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200310)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Some window asks with empty text

Status in apport package in Ubuntu:
  New

Bug description:
  [Testcase]

  1. Launch Kubuntu (e.g. kubuntu-20.04.4-desktop-amd64.iso)
  2. Open a terminal and run: ubuntu-bug -f
  3. "What kind of problem[...]" -> select first entry
  4. "What display problem[...]" -> select last entry
  5. You will get question window just asking "text"

  [Original report]

  Some window asks with empty text.

  1. in terminal run ubuntu-bug -f
  2. Select other problem
  3. Select i dont know
  4. comes up windows asking "text" and options Yes / No

  Other examples in other bugs with this example. Bug #1958054 and Bug
  #1958055

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportLog: Error: [Errno 13] Permission denied: '/var/log/apport.log'
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports: 640:1001:125:4063351:2020-06-01 21:05:01.891745699 
+0300:2020-06-01 21:04:59.835739474 
+0300:/var/crash/_usr_share_code_code.1001.crash
  CurrentDesktop: KDE
  Date: Mon Jun  1 21:09:41 2020
  InstallationDate: Installed on 2020-03-10 (83 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200310)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881640/+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 1958054] Re: Somekind text asking "Text" Yes / No

[Benjamin Drung]

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

This bug is a duplicate of bug #1881640

** This bug has been marked a duplicate of bug 1881640
   Some window asks with empty text

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

Title:
  Somekind text asking "Text" Yes / No

Status in apport package in Ubuntu:
  New

Bug description:
  Somekind text asking "Text" Yes / No
  Bug #1881640
  Sudo ubuntu-bug with "Text" Bug #1958055

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:01:48 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1958054/+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 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.

[Łukasz Zemczak]

Hello nuclearsandwich, or anyone else affected,

Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.7 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-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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: apt (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  Installing libudev1 on a new Jammy installation uninstalls many
  packages.

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Jammy:
  Fix Committed
Status in apt source package in Kinetic:
  In Progress

Bug description:
  [Impact]
  On an Ubuntu 22.04 desktop system created using the current installation 
image without enabling package updates over the network, installing the package 
libudev1 results in a large number of critical packages being removed and 
rendering the system essentially unusable.

  [Test plan]
  Comprehensive regression test suite validating a full solver dump with the 
issue is run as autopkgtest.

  [Where problems could occur]
  We could break other things from resolving. The solver is a bit finicky. 
Hopefully this is isolated enough.

  [Other info]

  https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile 
which also demonstrates the issue.
  Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, 
and then running `apt install libudev1` in the generated image results in

  The following packages will be REMOVED:
    libnss-systemd libpam-systemd systemd-timesyncd udev
  The following packages will be upgraded:
    libudev1

  This is completely prevented by ensuring that updates are installed
  from the jammy-updates repository before installing any additional
  packages and that is almost certainly the correct thing to do. But
  this is a punishing result for such a mistake.

  I would expect the installation to either force the upgrade of the
  other systemd packages or refuse to install libudev1 at the incorrect
  version relative to the other systemd packages until the system is
  upgraded.

  We found this out via a user report for ROS 2 Humble which is
  releasing on top of Ubuntu 22.04 next week:
  https://github.com/ros2/ros2/issues/1272

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974196/+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 1964828] Re: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'

[Benjamin Drung]

** Description changed:

+ [Test Plan]
+ 
+ 1. Launch the Ubuntu installer (i.e. ubuntu-22.04-desktop-amd64.iso)
+ 2. Select "Try Ubuntu"
+ 3. Open a terminal
+ 4. Run: ubuntu-bug -f
+ 5. Select "installer" and click on OK
+ 6. Click on "abort" when ask for the password
+ 7. The terminal should not show a stacktrace
+ 
+ [Orinial report]
+ 
  ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
  Traceback (most recent call last):
-   File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in 
_run_hook
- symb['add_info'](report, ui)
-   File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info
- apport.hookutils.attach_casper_md5check(report,
-   File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in 
attach_casper_md5check
- check = json.loads(report['CasperMD5json'])
-   File "/usr/lib/python3.10/collections/__init__.py", line 1102, in 
__getitem__
- raise KeyError(key)
+   File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in 
_run_hook
+ symb['add_info'](report, ui)
+   File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info
+ apport.hookutils.attach_casper_md5check(report,
+   File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in 
attach_casper_md5check
+ check = json.loads(report['CasperMD5json'])
+   File "/usr/lib/python3.10/collections/__init__.py", line 1102, in 
__getitem__
+ raise KeyError(key)
  KeyError: 'CasperMD5json'
  kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module 
"colorreload-gtk-module"
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity 22.04.7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperVersion: 1.467
  CurrentDesktop: KDE
  Date: Mon Mar 14 21:22:23 2022
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220314)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError:
  'CasperMD5json'

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Jammy:
  Fix Committed

Bug description:
  [Test Plan]

  1. Launch the Ubuntu installer (i.e. ubuntu-22.04-desktop-amd64.iso)
  2. Select "Try Ubuntu"
  3. Open a terminal
  4. Run: ubuntu-bug -f
  5. Select "installer" and click on OK
  6. Click on "abort" when ask for the password
  7. The terminal should not show a stacktrace

  [Orinial report]

  ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in 
_run_hook
  symb['add_info'](report, ui)
    File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info
  apport.hookutils.attach_casper_md5check(report,
    File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in 
attach_casper_md5check
  check = json.loads(report['CasperMD5json'])
    File "/usr/lib/python3.10/collections/__init__.py", line 1102, in 
__getitem__
  raise KeyError(key)
  KeyError: 'CasperMD5json'
  kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module 
"colorreload-gtk-module"
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity 22.04.7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperVersion: 1.467
  CurrentDesktop: KDE
  Date: Mon Mar 14 21:22:23 2022
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220314)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1981697] Re: KDC: weak crypto in default settings

[Andreas Hasenack]

This was fixed in Kinetic with
https://launchpad.net/ubuntu/+source/krb5/1.20-1

krb5 (1.20-1) unstable; urgency=medium

  * New Upstream Version
  * Do not specify master key type to avoid weak crypto, Closes: #1009927

 -- Sam Hartman   Fri, 22 Jul 2022 16:32:38 -0600

** Also affects: krb5 (Ubuntu Kinetic)
   Importance: Medium
   Status: Confirmed

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

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

Title:
  KDC: weak crypto in default settings

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Jammy:
  Triaged
Status in krb5 source package in Kinetic:
  Fix Released
Status in krb5 package in Debian:
  Fix Released

Bug description:
  Default setting in /etc/krb5kdc/kdc.conf, as installed from krb5-kdc in 
Ubuntu 22.04 Server:
  master_key_type = des3-hmac-sha1

  3DES was deprecated by NIST in 2017, i.e. give years ago! Reference:
  https://csrc.nist.gov/News/2017/Update-to-Current-Use-and-Deprecation-
  of-TDEA . This should not be a default since a very long time, and
  particularly not for new installations. If a compatibility with out-
  of-date installations is necessary, this should be explicitly made be
  the administrator.

  SHA-1 was deprecated as well, in 2011, i.e. eleven years ago!
  Reference:
  https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-131a.pdf
  .

  A reasonable default would probably be:
  master_key_type = aes256-cts-hmac-sha384-192

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: krb5-kdc 1.19.2-2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul 14 12:34:22 2022
  InstallationDate: Installed on 2022-05-30 (45 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  SourcePackage: krb5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1981697/+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 1958055] Re: sudo apport-kde is in a different design

[Benjamin Drung]

Re-assigning this ticket to sudo. IMO XDG_CURRENT_DESKTOP should be
added to the list of environment variables to preserve, e.g. by adding
it to env_keep in /etc/sudoers.

** Description changed:

  Running ubuntu-bug as normal user has the correct theme (see screenshots
  attached to bug #1881640), but running "sudo ubuntu-bug" has a
  different, non-matching theme (see attached screenshot).
  
  This problem can be reproduce by running a KDE application on Ubuntu
  Desktop (GNOME):
  
  1. Launch ubuntu-22.04-desktop-amd64.iso
  2. Install apport-kde
  3. Run: /usr/share/apport/apport-kde -f
  4. Run: sudo /usr/share/apport/apport-kde -f
  5. Compare both windows. They have different icons and font size.
+ 
+ Same result with KDE:
+ 
+ 1. Use kubuntu-22.04-desktop-amd64.iso
+ 2. Run ubuntu-bug -f
+ 3. Run: sudo ubuntu-bug -f
  
  [Workaround]
  
  Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo
  XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde -f
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:04:24 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Running ubuntu-bug as normal user has the correct theme (see screenshots
  attached to bug #1881640), but running "sudo ubuntu-bug" has a
  different, non-matching theme (see attached screenshot).
  
  This problem can be reproduce by running a KDE application on Ubuntu
  Desktop (GNOME):
  
  1. Launch ubuntu-22.04-desktop-amd64.iso
  2. Install apport-kde
  3. Run: /usr/share/apport/apport-kde -f
  4. Run: sudo /usr/share/apport/apport-kde -f
  5. Compare both windows. They have different icons and font size.
  
  Same result with KDE:
  
  1. Use kubuntu-22.04-desktop-amd64.iso
  2. Run ubuntu-bug -f
  3. Run: sudo ubuntu-bug -f
+ 
+ [Analysis]
+ 
+ Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme,
+ but XDG_CURRENT_DESKTOP is not in the list of environment variables to
+ preserve (and not in env_keep in /etc/sudoers).
  
  [Workaround]
  
  Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo
  XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde -f
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:04:24 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- sudo apport-kde is in a different design
+ sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)

** Package changed: apport (Ubuntu) => sudo (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/1958055

Title:
  sudo apport-kde is in a different design (stripped
  XDG_CURRENT_DESKTOP)

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  Running ubuntu-bug as normal user has the correct theme (see
  screenshots attached to bug #1881640), but running "sudo ubuntu-bug"
  has a different, non-matching theme (see attached screenshot).

  This problem can be reproduce by running a KDE application on Ubuntu
  Desktop (GNOME):

  1. Launch ubuntu-22.04-desktop-amd64.iso
  2. Install apport-kde
  3. Run: /usr/share/apport/apport-kde -f
  4. Run: sudo /usr/share/apport/apport-kde -f
  5. Compare both windows. They have different icons and font size.

  Same result with KDE:

  1. Use kubuntu-22.04-desktop-amd64.iso
  2. Run ubuntu-bug -f
  3. Run: sudo ubuntu-bug -f

  [Analysis]

  Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme,
  but XDG_CURRENT_DESKTOP is not in the list of environment variables to
  preserve (and not in env_keep in /etc/sudoers).

  [Workaround]

  Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo
  XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde
  -f

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:04:2

[Touch-packages] [Bug 1958055] Re: sudo apport-kde is in a different design (stripped XDG_CURRENT_DESKTOP)

[Launchpad Bug Tracker]

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

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

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

Title:
  sudo apport-kde is in a different design (stripped
  XDG_CURRENT_DESKTOP)

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  Running ubuntu-bug as normal user has the correct theme (see
  screenshots attached to bug #1881640), but running "sudo ubuntu-bug"
  has a different, non-matching theme (see attached screenshot).

  This problem can be reproduce by running a KDE application on Ubuntu
  Desktop (GNOME):

  1. Launch ubuntu-22.04-desktop-amd64.iso
  2. Install apport-kde
  3. Run: /usr/share/apport/apport-kde -f
  4. Run: sudo /usr/share/apport/apport-kde -f
  5. Compare both windows. They have different icons and font size.

  Same result with KDE:

  1. Use kubuntu-22.04-desktop-amd64.iso
  2. Run ubuntu-bug -f
  3. Run: sudo ubuntu-bug -f

  [Analysis]

  Qt needs XDG_CURRENT_DESKTOP to be set to determine the correct theme,
  but XDG_CURRENT_DESKTOP is not in the list of environment variables to
  preserve (and not in env_keep in /etc/sudoers).

  [Workaround]

  Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo
  XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde
  -f

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:04:24 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1958055/+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 1958055] Re: sudo apport-kde is in a different design

[Benjamin Drung]

** Description changed:

- Text Bug #1881640 one design
- Text sudo Bug #1958054 another design
- Here adding screenshot of sudo ubuntu-bug design
+ Running ubuntu-bug as normal user has the correct theme (see screenshots
+ attached to bug #1881640), but running "sudo ubuntu-bug" has a
+ different, non-matching theme (see attached screenshot).
+ 
+ This problem can be reproduce by running a KDE application on Ubuntu
+ Desktop (GNOME):
+ 
+ 1. Launch ubuntu-22.04-desktop-amd64.iso
+ 2. Install apport-kde
+ 3. Run: /usr/share/apport/apport-kde -f
+ 4. Run: sudo /usr/share/apport/apport-kde -f
+ 5. Compare both windows. They have different icons and font size.
+ 
+ [Workaround]
+ 
+ Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo
+ XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde -f
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:04:24 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

** Tags removed: i386
** Tags added: jammy

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

Title:
  sudo apport-kde is in a different design

Status in apport package in Ubuntu:
  New

Bug description:
  Running ubuntu-bug as normal user has the correct theme (see
  screenshots attached to bug #1881640), but running "sudo ubuntu-bug"
  has a different, non-matching theme (see attached screenshot).

  This problem can be reproduce by running a KDE application on Ubuntu
  Desktop (GNOME):

  1. Launch ubuntu-22.04-desktop-amd64.iso
  2. Install apport-kde
  3. Run: /usr/share/apport/apport-kde -f
  4. Run: sudo /usr/share/apport/apport-kde -f
  5. Compare both windows. They have different icons and font size.

  [Workaround]

  Prevent sudo from dropping XDG_CURRENT_DESKTOP by running: sudo
  XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP /usr/share/apport/apport-kde
  -f

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:04:24 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1958055/+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 1958055] Re: sudo ubuntu-bug is in a different design

[Benjamin Drung]

** Summary changed:

- Sudo ubuntu-bug is in different design. Added screenshots
+ sudo ubuntu-bug is in a different design

** Summary changed:

- sudo ubuntu-bug is in a different design
+ sudo apport-kde is in a different design

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

Title:
  sudo apport-kde is in a different design

Status in apport package in Ubuntu:
  New

Bug description:
  Text Bug #1881640 one design
  Text sudo Bug #1958054 another design
  Here adding screenshot of sudo ubuntu-bug design

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157
  Uname: Linux 5.4.0-94-generic i686
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Jan 16 05:04:24 2022
  InstallationDate: Installed on 2022-01-15 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1958055/+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 1899638] Re: ubuntu-bug won't show GUI window in pure wayland-sessions

[Benjamin Drung]

I cannot reproduce your problem and neither find a problem in the code.

Running "env -u DISPLAY ubuntu-bug -w apport" on a fresh Ubuntu 22.04
installation (with GNOME and wayland) opens apport-gtk correctly.
Neither killing Xwayland nor only setting WAYLAND_DISPLAY by running
"env -i WAYLAND_DISPLAY=wayland-0 ubuntu-bug -w apport" did change
anything (note: apport-gtk crashed in the latter case, but it was
called).

Supporting WAYLAND_DISPLAY as alternative was implemented in bug
#1418766 long time ago.

Can you reproduce your problem? What environment are you in?

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

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

Title:
  ubuntu-bug won't show GUI window in pure wayland-sessions

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  In case only `WAYLAND_DISPLAY` env variable is set (but no `DISPLAY`
  as XWayland is disabled), ubuntu-bug won't show its window, even
  though GTK will use the Wayland backend.

  Test case, in an Ubuntu wayland session:
   - Run:
env -u DISPLAY ubuntu-bug -w apport

  
  You will get:

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ...

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (5.9 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): S

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  92%

  *** To continue, you must visit the following URL:

https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/.. ?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  marco@marco-virtual-machine:~$ Error: no DISPLAY environment variable 
specified
  ^C

  ---

  So, ubuntu-bug should both consider `DISPLAY` and `WAYLAND_DISPLAY` to
  be enough to use a graphical session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu49
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports: 640:1000:125:21823957:2020-10-13 15:15:42.354004383 
+0200:2020-10-13 15:15:43.354004383 
+0200:/var/crash/_usr_bin_gnome-shell.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 13 15:22:34 2020
  InstallationDate: Installed on 2020-10-13 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899638/+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 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.

[Julian Andres Klode]

** Changed in: apt (Ubuntu Jammy)
Milestone: None => ubuntu-22.04.1

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

Title:
  Installing libudev1 on a new Jammy installation uninstalls many
  packages.

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Jammy:
  In Progress
Status in apt source package in Kinetic:
  In Progress

Bug description:
  [Impact]
  On an Ubuntu 22.04 desktop system created using the current installation 
image without enabling package updates over the network, installing the package 
libudev1 results in a large number of critical packages being removed and 
rendering the system essentially unusable.

  [Test plan]
  Comprehensive regression test suite validating a full solver dump with the 
issue is run as autopkgtest.

  [Where problems could occur]
  We could break other things from resolving. The solver is a bit finicky. 
Hopefully this is isolated enough.

  [Other info]

  https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile 
which also demonstrates the issue.
  Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, 
and then running `apt install libudev1` in the generated image results in

  The following packages will be REMOVED:
    libnss-systemd libpam-systemd systemd-timesyncd udev
  The following packages will be upgraded:
    libudev1

  This is completely prevented by ensuring that updates are installed
  from the jammy-updates repository before installing any additional
  packages and that is almost certainly the correct thing to do. But
  this is a punishing result for such a mistake.

  I would expect the installation to either force the upgrade of the
  other systemd packages or refuse to install libudev1 at the incorrect
  version relative to the other systemd packages until the system is
  upgraded.

  We found this out via a user report for ROS 2 Humble which is
  releasing on top of Ubuntu 22.04 next week:
  https://github.com/ros2/ros2/issues/1272

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974196/+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 1978125] Re: apt ignoring pin/block/hold files in preferences.d for snapd

[Julian Andres Klode]

** No longer affects: apt (Ubuntu Impish)

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

Title:
  apt ignoring pin/block/hold files in preferences.d for snapd

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Jammy:
  Fix Released
Status in apt source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Negative pins are overridden by a pin of 1 if the package is phasing and "not 
for us", which suddenly makes packages installable that were effectively 
blocklisted by the negative pin, overriding user settings

  [Test plan]
  Integration tests covers the fix for this. The fix is not enabled by default 
as the implementation was changed for bug 1979244, however the new 
implementation also tests that.

  These tests are run during autopkgtest.

  To test with the new implementation, create an update that pulls in a
  phasing package that is pinned -1 and make sure it's not being
  installed. I did not add a test for that case as the new
  implementation only works by keeping back packages, so it by
  definition can't suddenly cause a package to be allowed.

  [Where problems could occur]
  This specific bit is not enabled anymore, but for the sake of it, it is 
implemented as a ceiling for the pin, so any other pin will be limited to 1 if 
the package is considered a "not-for-us" phasing package. So problems could 
occur there.

  For the new phasing implementation, see bug 1979244.

  [Original bug report]
  Did some upgrades on a new box on 22.04, and had previously removed snapd and 
BLOCKED via a file in /etc/apt/preferences.d/

  And this upgrade cycle REINSTALLED snapd! and the stupid FF snap! Had
  to repurge it again!

  I had done this previously, and it appears that apt or something is
  IGNORING any pin/holds of snapd

  I use preferences.d files as using:
  sudo apt-mark hold snapd

  This has never worked on any package, ever...

  I have:
  /etc/apt/preferences.d$ cat snapd

  Package: snapd
  Pin: origin *
  Pin-Priority: -1

  And that previously resulted in an error on apt in any attempt to
  install snapd, including using -s... NOW it will still attempt to
  install snapd!

  I've tried several variants of this as well, which other 22.04 and
  20.04 boxes have, same on 22.04, it will allow snapd install!

  Did sudo apt-get update, apt update several times, rebooted several
  times, had various levels of the Pin-Priority from -1 to -, still
  will attempt to install snapd, versus the expected error

  sudo apt-get -s install snapd

  Expected error: Reading package lists... Done Building dependency tree
  Reading state information... Done Package snapd is not available, but is 
referred to by another package. This may mean that the package is missing, has 
been obsoleted, or is only available from another source

  E: Package 'snapd' has no installation candidate

  20.04 boxes still seem to fail correctly with this pin file,.

  Checking my BASE VM IMAGE of 22.04 and this still works there, as its
  not been touched, this pin file blocks snapd from installing as
  expected... this is apt 2.3.15, updated one is 2.4.5

  If I pick ANY OTHER RANDOM PACKAGE out and use the same pin/block
  file, and change the name to that package, it blocks it from
  installing! Anything but snapd this works for!

  1)$ lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  2)  sudo apt-cache policy apt
  apt:
    Installed: 2.4.5
    Candidate: 2.4.5
    Version table:
   *** 2.4.5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  What I expect to happen? HONOR MY BLOCK on snapd! It works for any
  random package chosen, EXCEPT snadp!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1978125/+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 1944712] Re: systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1

[Lukas Märdian]

Closing this bug for systemd, as it's not relevant anymore IMO and is a
red herring in proposed-migration.

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

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

Title:
  systemd/237-3ubuntu10.52 ADT test failure with linux-
  aws-5.4/5.4.0-1057.60~18.04.1

Status in linux-aws-5.4 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux-aws-5.4/5.4.0-1057.60~18.04.1 on bionic. Whether this
  is caused by the dep8 tests of the tested source or the kernel has yet
  to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/s/systemd/20210923_022411_52338@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.4/+bug/1944712/+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 1972977] Re: gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query()

[Timo Aaltonen]

I find it confusing to move a bug 'fix committed' when it's only in
upstream master. Kinetic will get 22.2.x, and it'll have this (hasn't
branched yet).

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

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

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Fix Committed

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

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


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

[Touch-packages] [Bug 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.

[Julian Andres Klode]

** Changed in: apt (Ubuntu Jammy)
   Status: Confirmed => In Progress

** Description changed:

- On an Ubuntu 22.04 desktop system created using the current installation
- image without enabling package updates over the network, installing the
- package libudev1 results in a large number of critical packages being
- removed and rendering the system essentially unusable.
+ [Impact]
+ On an Ubuntu 22.04 desktop system created using the current installation 
image without enabling package updates over the network, installing the package 
libudev1 results in a large number of critical packages being removed and 
rendering the system essentially unusable.
+ 
+ [Test plan]
+ Comprehensive regression test suite validating a full solver dump with the 
issue is run as autopkgtest.
+ 
+ [Where problems could occur]
+ We could break other things from resolving. The solver is a bit finicky. 
Hopefully this is isolated enough.
+ 
+ [Other info]
  
  https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile 
which also demonstrates the issue.
  Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, 
and then running `apt install libudev1` in the generated image results in
  
  The following packages will be REMOVED:
-   libnss-systemd libpam-systemd systemd-timesyncd udev
+   libnss-systemd libpam-systemd systemd-timesyncd udev
  The following packages will be upgraded:
-   libudev1
+   libudev1
  
- 
- This is completely prevented by ensuring that updates are installed from the 
jammy-updates repository before installing any additional packages and that is 
almost certainly the correct thing to do. But this is a punishing result for 
such a mistake.
+ This is completely prevented by ensuring that updates are installed from
+ the jammy-updates repository before installing any additional packages
+ and that is almost certainly the correct thing to do. But this is a
+ punishing result for such a mistake.
  
  I would expect the installation to either force the upgrade of the other
  systemd packages or refuse to install libudev1 at the incorrect version
  relative to the other systemd packages until the system is upgraded.
  
  We found this out via a user report for ROS 2 Humble which is releasing
  on top of Ubuntu 22.04 next week:
  https://github.com/ros2/ros2/issues/1272

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

Title:
  Installing libudev1 on a new Jammy installation uninstalls many
  packages.

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Jammy:
  In Progress
Status in apt source package in Kinetic:
  In Progress

Bug description:
  [Impact]
  On an Ubuntu 22.04 desktop system created using the current installation 
image without enabling package updates over the network, installing the package 
libudev1 results in a large number of critical packages being removed and 
rendering the system essentially unusable.

  [Test plan]
  Comprehensive regression test suite validating a full solver dump with the 
issue is run as autopkgtest.

  [Where problems could occur]
  We could break other things from resolving. The solver is a bit finicky. 
Hopefully this is isolated enough.

  [Other info]

  https://github.com/tfoote/udevdebug/blob/main/Dockerfile is a Dockerfile 
which also demonstrates the issue.
  Building the image, which will install udev 249.11-0ubuntu3 and init 1.62, 
and then running `apt install libudev1` in the generated image results in

  The following packages will be REMOVED:
    libnss-systemd libpam-systemd systemd-timesyncd udev
  The following packages will be upgraded:
    libudev1

  This is completely prevented by ensuring that updates are installed
  from the jammy-updates repository before installing any additional
  packages and that is almost certainly the correct thing to do. But
  this is a punishing result for such a mistake.

  I would expect the installation to either force the upgrade of the
  other systemd packages or refuse to install libudev1 at the incorrect
  version relative to the other systemd packages until the system is
  upgraded.

  We found this out via a user report for ROS 2 Humble which is
  releasing on top of Ubuntu 22.04 next week:
  https://github.com/ros2/ros2/issues/1272

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974196/+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 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

[Pedro Ribeiro]

Got it, thanks for the explanation.

At least we know the overwrite doesn't happen, which removes the
potential security issue out of the equation.

To be honest I'm not completely convinced it was exploitable, but I'm
not convinced it wasn't either, so better play it safe and patch it out.
The side effects on other apps are unfortunate, but like you say, it's
up to the apps to manage errors coming from gdk-pixbuf.

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
   - PCManFM, LXDE's file manager which straight up crashes
   - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
   - Eye of GNOME (eog) triggers the segfault in syslog
   - Eye of MATE (eom) segfaults

   * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.

  [Where problems could occur]

   * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.

   * It is possible, and has happened in the past (which has been
  patched) that other bad GIFs can cause other crashes.

   * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems

   * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs

  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.

  [Other Info]

   * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
   * Files attached are examples or crashes
   * Again, all apps using gdk-pixbuf are affected
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
   * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190
   * 
https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+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 1978125] Update Released

[Łukasz Zemczak]

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

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

Title:
  apt ignoring pin/block/hold files in preferences.d for snapd

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Impish:
  Fix Committed
Status in apt source package in Jammy:
  Fix Released
Status in apt source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Negative pins are overridden by a pin of 1 if the package is phasing and "not 
for us", which suddenly makes packages installable that were effectively 
blocklisted by the negative pin, overriding user settings

  [Test plan]
  Integration tests covers the fix for this. The fix is not enabled by default 
as the implementation was changed for bug 1979244, however the new 
implementation also tests that.

  These tests are run during autopkgtest.

  To test with the new implementation, create an update that pulls in a
  phasing package that is pinned -1 and make sure it's not being
  installed. I did not add a test for that case as the new
  implementation only works by keeping back packages, so it by
  definition can't suddenly cause a package to be allowed.

  [Where problems could occur]
  This specific bit is not enabled anymore, but for the sake of it, it is 
implemented as a ceiling for the pin, so any other pin will be limited to 1 if 
the package is considered a "not-for-us" phasing package. So problems could 
occur there.

  For the new phasing implementation, see bug 1979244.

  [Original bug report]
  Did some upgrades on a new box on 22.04, and had previously removed snapd and 
BLOCKED via a file in /etc/apt/preferences.d/

  And this upgrade cycle REINSTALLED snapd! and the stupid FF snap! Had
  to repurge it again!

  I had done this previously, and it appears that apt or something is
  IGNORING any pin/holds of snapd

  I use preferences.d files as using:
  sudo apt-mark hold snapd

  This has never worked on any package, ever...

  I have:
  /etc/apt/preferences.d$ cat snapd

  Package: snapd
  Pin: origin *
  Pin-Priority: -1

  And that previously resulted in an error on apt in any attempt to
  install snapd, including using -s... NOW it will still attempt to
  install snapd!

  I've tried several variants of this as well, which other 22.04 and
  20.04 boxes have, same on 22.04, it will allow snapd install!

  Did sudo apt-get update, apt update several times, rebooted several
  times, had various levels of the Pin-Priority from -1 to -, still
  will attempt to install snapd, versus the expected error

  sudo apt-get -s install snapd

  Expected error: Reading package lists... Done Building dependency tree
  Reading state information... Done Package snapd is not available, but is 
referred to by another package. This may mean that the package is missing, has 
been obsoleted, or is only available from another source

  E: Package 'snapd' has no installation candidate

  20.04 boxes still seem to fail correctly with this pin file,.

  Checking my BASE VM IMAGE of 22.04 and this still works there, as its
  not been touched, this pin file blocks snapd from installing as
  expected... this is apt 2.3.15, updated one is 2.4.5

  If I pick ANY OTHER RANDOM PACKAGE out and use the same pin/block
  file, and change the name to that package, it blocks it from
  installing! Anything but snapd this works for!

  1)$ lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  2)  sudo apt-cache policy apt
  apt:
    Installed: 2.4.5
    Candidate: 2.4.5
    Version table:
   *** 2.4.5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  What I expect to happen? HONOR MY BLOCK on snapd! It works for any
  random package chosen, EXCEPT snadp!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1978125/+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 1978125] Re: apt ignoring pin/block/hold files in preferences.d for snapd

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.4.6

---
apt (2.4.6) jammy; urgency=medium

  * (Temporarily) Rewrite phased updates using a keep-back approach
(LP: #1979244)
  * policy: Do not override negative pins with 1 due to phasing (LP: #1978125)
  * Point branch to 2.4.y and use jammy in gitlab-ci

 -- Julian Andres Klode   Thu, 30 Jun 2022 15:33:22
+0200

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

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

Title:
  apt ignoring pin/block/hold files in preferences.d for snapd

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Impish:
  Fix Committed
Status in apt source package in Jammy:
  Fix Released
Status in apt source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Negative pins are overridden by a pin of 1 if the package is phasing and "not 
for us", which suddenly makes packages installable that were effectively 
blocklisted by the negative pin, overriding user settings

  [Test plan]
  Integration tests covers the fix for this. The fix is not enabled by default 
as the implementation was changed for bug 1979244, however the new 
implementation also tests that.

  These tests are run during autopkgtest.

  To test with the new implementation, create an update that pulls in a
  phasing package that is pinned -1 and make sure it's not being
  installed. I did not add a test for that case as the new
  implementation only works by keeping back packages, so it by
  definition can't suddenly cause a package to be allowed.

  [Where problems could occur]
  This specific bit is not enabled anymore, but for the sake of it, it is 
implemented as a ceiling for the pin, so any other pin will be limited to 1 if 
the package is considered a "not-for-us" phasing package. So problems could 
occur there.

  For the new phasing implementation, see bug 1979244.

  [Original bug report]
  Did some upgrades on a new box on 22.04, and had previously removed snapd and 
BLOCKED via a file in /etc/apt/preferences.d/

  And this upgrade cycle REINSTALLED snapd! and the stupid FF snap! Had
  to repurge it again!

  I had done this previously, and it appears that apt or something is
  IGNORING any pin/holds of snapd

  I use preferences.d files as using:
  sudo apt-mark hold snapd

  This has never worked on any package, ever...

  I have:
  /etc/apt/preferences.d$ cat snapd

  Package: snapd
  Pin: origin *
  Pin-Priority: -1

  And that previously resulted in an error on apt in any attempt to
  install snapd, including using -s... NOW it will still attempt to
  install snapd!

  I've tried several variants of this as well, which other 22.04 and
  20.04 boxes have, same on 22.04, it will allow snapd install!

  Did sudo apt-get update, apt update several times, rebooted several
  times, had various levels of the Pin-Priority from -1 to -, still
  will attempt to install snapd, versus the expected error

  sudo apt-get -s install snapd

  Expected error: Reading package lists... Done Building dependency tree
  Reading state information... Done Package snapd is not available, but is 
referred to by another package. This may mean that the package is missing, has 
been obsoleted, or is only available from another source

  E: Package 'snapd' has no installation candidate

  20.04 boxes still seem to fail correctly with this pin file,.

  Checking my BASE VM IMAGE of 22.04 and this still works there, as its
  not been touched, this pin file blocks snapd from installing as
  expected... this is apt 2.3.15, updated one is 2.4.5

  If I pick ANY OTHER RANDOM PACKAGE out and use the same pin/block
  file, and change the name to that package, it blocks it from
  installing! Anything but snapd this works for!

  1)$ lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  2)  sudo apt-cache policy apt
  apt:
    Installed: 2.4.5
    Candidate: 2.4.5
    Version table:
   *** 2.4.5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  What I expect to happen? HONOR MY BLOCK on snapd! It works for any
  random package chosen, EXCEPT snadp!

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


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

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

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 2.4.6

---
apt (2.4.6) jammy; urgency=medium

  * (Temporarily) Rewrite phased updates using a keep-back approach
(LP: #1979244)
  * policy: Do not override negative pins with 1 due to phasing (LP: #1978125)
  * Point branch to 2.4.y and use jammy in gitlab-ci

 -- Julian Andres Klode   Thu, 30 Jun 2022 15:33:22
+0200

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  We test both the new implementation and the old one.

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

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

  [Example]

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-m

[Touch-packages] [Bug 1979244] Update Released

[Łukasz Zemczak]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  We test both the new implementation and the old one.

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

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

  [Example]

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/char