[Touch-packages] [Bug 1906420] Re: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author)
Note also that we can't consider DING for inclusion in Ubuntu 20.04 focal because to render in Wayland sessions it requires mutter 3.38 or later. -- 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/1906420 Title: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author) Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: By default, Ubuntu installs the Gnome extension "Desktop Icons" [1] (by rastersoft). Unfortunately, this extension is now unmaintained, is problematic, and leads to several bugs, including but not limited to Bug #1901150 and Bug #1813441. The same author has created, and continues to maintain, the far superior "Desktop Icons NG (DING)" [2]. It solves a number of problems including the two aforementioned bugs. It's possible to disable, but not uninstall, "Desktop Icons", and then to install "Desktop Icons NG (DING)". I did this a while ago with great results. If Canonical replaces the former with the latter, not only will Ubuntu be using a better desktop manager, but also it will be able clear all related bugs at a stroke. This is a simple, cheap, quick and effective solution that will let the devs concentrate on more important tasks. Please give this serious consideration. More information: Ubuntu 20.04.1 LTS 64-bit Gnome version 3.36.3 [1] https://extensions.gnome.org/extension/1465/desktop-icons/ [2] https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1906420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools
We are prioritizing people being able to easily activate Ubuntu Advantage/Ubuntu Pro more than people who worry about 2.6 MB. People who activate Ubuntu Advantage are generally paying customers. Those paying customers make Ubuntu better for all of us by helping to fund a lot of the work done in Ubuntu. Respectfully, I don't think there's any benefit to me continuing to explain why we made this decision. -- 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/1930914 Title: ubuntu-minimal depends on ubuntu-advantage-tools Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: This is counter to #1566183 There is no reason to enforce desktop users who manage machine on their own to install ubuntu-advantage- tools, especially when this is 'minimal' version. This should include only essential packages to make the OS functional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-minimal 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106 Uname: Linux 5.4.0-73-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 4 18:54:56 2021 InstallationDate: Installed on 2020-01-29 (491 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964839] [NEW] software-properties-gtk crashes if APT::Periodic::Upgrade-Package-Lists="3"
Public bug reported:
Changing `APT::Periodic::Update-Package-Lists` to a value not in the
data model `model_updates_interval` in `/usr/share/software-
properties/gtkbuilder/main.ui` calls an invalid method, crashing the
program.
```
$ cat /etc/apt/apt.conf.d/10periodic
APT::Periodic::Update-Package-Lists "3";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::AutocleanInterval "0";
APT::Periodic::Unattended-Upgrade "0";
$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 231, in __init__
self.init_auto_update()
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 310, in init_auto_update
self.combobox_update_interval.append_text(_("Every %s days")
AttributeError: 'ComboBox' object has no attribute 'append_text'
```
Occurs in:
```
$ lsb_release -rd
Description:Ubuntu 21.04
Release:21.04
$ apt-cache policy software-properties-gtk
software-properties-gtk:
Installed: 0.99.10.2
Candidate: 0.99.10.2
Version table:
*** 0.99.10.2 500
500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/main amd64
Packages
500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/main i386
Packages
100 /var/lib/dpkg/status
0.99.10 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu hirsute/main i386 Packages
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1964839
Title:
software-properties-gtk crashes if APT::Periodic::Upgrade-Package-
Lists="3"
Status in software-properties package in Ubuntu:
New
Bug description:
Changing `APT::Periodic::Update-Package-Lists` to a value not in the
data model `model_updates_interval` in `/usr/share/software-
properties/gtkbuilder/main.ui` calls an invalid method, crashing the
program.
```
$ cat /etc/apt/apt.conf.d/10periodic
APT::Periodic::Update-Package-Lists "3";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::AutocleanInterval "0";
APT::Periodic::Unattended-Upgrade "0";
$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 231, in __init__
self.init_auto_update()
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 310, in init_auto_update
self.combobox_update_interval.append_text(_("Every %s days")
AttributeError: 'ComboBox' object has no attribute 'append_text'
```
Occurs in:
```
$ lsb_release -rd
Description: Ubuntu 21.04
Release: 21.04
$ apt-cache policy software-properties-gtk
software-properties-gtk:
Installed: 0.99.10.2
Candidate: 0.99.10.2
Version table:
*** 0.99.10.2 500
500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/main amd64
Packages
500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/main i386
Packages
100 /var/lib/dpkg/status
0.99.10 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu hirsute/main i386 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1964839/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools
So how would you like to identify and mark computers eligible for extended support without user interaction ? And if user interaction is required why can't you use the same launch method for installing extended support ? And why installing 2.6Mbyes of logic on _all_ ubuntu instead of simple eligibility check script which would do further job only if required ? On Mon, Mar 14, 2022 at 10:36 PM Jeremy Bicha <1930...@bugs.launchpad.net> wrote: > Because you don't need to use apt-get to use Ubuntu. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1930914 > > Title: > ubuntu-minimal depends on ubuntu-advantage-tools > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+subscriptions > > -- 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/1930914 Title: ubuntu-minimal depends on ubuntu-advantage-tools Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: This is counter to #1566183 There is no reason to enforce desktop users who manage machine on their own to install ubuntu-advantage- tools, especially when this is 'minimal' version. This should include only essential packages to make the OS functional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-minimal 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106 Uname: Linux 5.4.0-73-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 4 18:54:56 2021 InstallationDate: Installed on 2020-01-29 (491 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964794] Re: Faulty linux-firmware upgrade
*** This bug is a duplicate of bug 1964814 *** https://bugs.launchpad.net/bugs/1964814 I have the same issue on update of 22.04 today. sudo apt install --reinstall linux-firmware Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be upgraded: linux-firmware 1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. 1 not fully installed or removed. Need to get 0 B/238 MB of archives. After this operation, 24.9 MB of additional disk space will be used. (Reading database ... 243441 files and directories currently installed.) Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic update-initramfs: Generating /boot/initrd.img-5.15.0-18-generic Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Cheers Spart -- 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/1964794 Title: Faulty linux-firmware upgrade Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Can't upgrade the package: Préparation du dépaquetage de .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Dépaquetage de linux-firmware (20220314.gitcd01f857-0ubuntu1) sur (20220302.gitee0667aa-0ubuntu1) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack) : impossible d'ouvrir « /lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new »: Aucun fichier ou dossier de ce type Aucun rapport « apport » n'a été créé car le message d'erreur rapporte un problème sur le système local update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic update-initramfs: Generating /boot/initrd.img-5.15.0-18-generic Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
> I have update ongoing on esm-infa-staging for it just to clarify, if the systemd patch isn't added to the actual main (currently closed) xenial-updates repo, it won't be very much help to anyone wanting to create new xenial containers on jammy. So, just patching systemd in the esm repo likely is not enough - especially if the prebuilt LXD container images don't pick up the ESM version of systemd. -- 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/1962332 Title: xenial systemd fails to start if cgroup2 is mounted Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Bug description: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. [workaround] On Jammy host edit default kernel command line to include systemd.unified_cgroup_hierarchy=false update your bootloader configuration; and reboot then hybrid cgroups will be on the host, and one can launch xenial container then. [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, so this is fixed already in b and later. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. [other info] An alternative appears to be to change the host system back to using the 'hybrid' cgroup, however that obviously is awful and would remove the benefits of cgroup v2 from the host system, and force all containers on the host system to also use the 'hybrid' cgroup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4
Thanks for reporting this bug.
As Seth said, it seems unlikely that this is ssh's fault. I don't have
an easy way to use virtualbox/packer here, so I'm wondering if you could
either provide more info (as Seth also requested) or an out-of-the-box
way to reproduce what you're seeing (i.e., without involving third-party
applications).
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1964642
Title:
Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
but can connect to Ubuntu 20.4
Status in openssh package in Ubuntu:
New
Bug description:
Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a
Windows 10 host with Packer 1.5.6, using an unattended installation.
The Packer command was:
"boot_command": [
" ",
"autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
""
],
The user-data file was:
#cloud-config
autoinstall:
version: 1
identity:
realname: mclibre
hostname: ubuntu
password:
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
username: mclibre
locale: es_ES.UTF-8
keyboard:
layout: es
network:
network:
version: 2
ethernets:
ens33: {dhcp4: true, dhcp-identifier: mac}
ssh:
install-server: true
late-commands:
- sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/'
/target/etc/dhcp/dhclient.conf
- 'sed -i "s/dhcp4: true/&\n dhcp-identifier: mac/"
/target/etc/netplan/00-installer-config.yaml'
Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using
packer 1.5.6 but Packer can't create the image because once the installation is
done, after rebooting the SSH server does not answer (the packer log error
says: SSH handshake err: Timeout during SSH handshake).
I have tried with the last version of Packer, Packer 1.8.0, and the result is
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server
20.4.1, .2, .3 or .4 image.
I can provide as much aditional information as you want.
Thanking you in advance,
Bartolome Sintes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools
Because you don't need to use apt-get to use Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1930914 Title: ubuntu-minimal depends on ubuntu-advantage-tools Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: This is counter to #1566183 There is no reason to enforce desktop users who manage machine on their own to install ubuntu-advantage- tools, especially when this is 'minimal' version. This should include only essential packages to make the OS functional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-minimal 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106 Uname: Linux 5.4.0-73-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 4 18:54:56 2021 InstallationDate: Installed on 2020-01-29 (491 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964794] Re: Faulty linux-firmware upgrade
*** This bug is a duplicate of bug 1964814 *** https://bugs.launchpad.net/bugs/1964814 ** This bug has been marked a duplicate of bug 1964814 linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 -- 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/1964794 Title: Faulty linux-firmware upgrade Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Can't upgrade the package: Préparation du dépaquetage de .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Dépaquetage de linux-firmware (20220314.gitcd01f857-0ubuntu1) sur (20220302.gitee0667aa-0ubuntu1) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack) : impossible d'ouvrir « /lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new »: Aucun fichier ou dossier de ce type Aucun rapport « apport » n'a été créé car le message d'erreur rapporte un problème sur le système local update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic update-initramfs: Generating /boot/initrd.img-5.15.0-18-generic Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow
** Changed in: initramfs-tools (Ubuntu) Importance: Medium => High -- 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/1958148 Title: mkinitramfs is too slow Status in initramfs-tools package in Ubuntu: Confirmed Bug description: On the Nezha board creating an initrd takes more than 1 hour. The compression level -19 for zstd is unwisely chosen. Here are durations and compression results for an SiFive Unmatched board with four cores using zstd: -T0 -1 => 13.92s, 136298155 bytes -T0 -2 => 15.73s, 131717830 bytes -T0 -3 => 26.11s, 127434653 bytes -T0 -4 => 29.31s, 126924540 bytes -T0 -5 => 36.44s, 125296557 bytes -T0 -6 => 39.36s, 124781669 bytes -T0 -7 => 46.56s, 116200665 bytes -T0 -8 => 51.95s, 113172941 bytes -T0 -9 => 55.89s, 112835937 bytes -T0 -10 => 61.32s, 108326876 bytes -T0 -11 => 64.32s, 108115060 bytes -T0 -12 => 76.37s, 108016478 bytes -T0 -13 => 148.99s, 109121308 bytes -T0 -14 => 156.58s, 108908574 bytes -T0 -15 => 228.64s, 109213554 bytes -T0 -16 => 380.26s, 107260643 bytes -T0 -17 => 453.36s, 103679714 bytes -T0 -18 => 714.79s, 100402249 bytes -T0 -19 => 1046.58s, 100188713 bytes Compression level between -2 to -10 offer a good compromise between CPU time and compression results. Ideally there would be a parameter that we could pass to mkinitfs. But for as fast solution we should simply replace -19 by -9 in mkinitramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
SRU justification provides and added to the bug description.
** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * zlib: compressBound() returns an incorrect result on IBM z15 hardware.
+
+ * Passing the result of compressBound() to compress() results
+ in an error code.
+
+ * This is because compressBound() is not adjusted for DFLTCC.
+
+ [Fix]
+
+ * Adjust compressBound() for DFLTCC like it's already done
+ for deflateBound().
+
+ * Since zlib project does not accept patches at the moment,
+ the fix has been integrated into the DFLTCC pull request:
+ https://github.com/madler/zlib/pull/410
+ The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
+
+ * The fix extracted out of the above is:
+
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
+
+ [Test Plan]
+
+ * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
+ with Ubuntu Server 21.10 (or 22.04).
+
+ * A test can be done based on the following C test program:
+ #include
+ #include
+ #include
+ int main() {
+ Bytef in_buf[128], out_buf[1024];
+ for (size_t i = 0; i < sizeof(in_buf); i++)
+ in_buf[i] = rand();
+ uLongf dest_len = compressBound(sizeof(in_buf));
+ assert(dest_len <= sizeof(out_buf));
+ int ret = compress(out_buf, _len,
+ in_buf, sizeof(in_buf));
+ assert(ret == Z_OK);
+ }
+
+ * The test needs to be done by IBM, due to the requirements
+ for the special z15 hardware.
+
+ [Where problems could occur]
+
+ * If the adjustment of compressBound() for DFLTCC is done
+ erroneously the issue can still be present or in worst case
+ even affect Z systems other than z15 only.
+
+ * The crc table can be broken, in case the endian detection
+ or the register initialization is done wrong.
+
+ * The compression can become errorneous with the new changes,
+ e.g. in compressBound.
+
+ * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
+ (incl. the bit definitions), may cause various and unforseen defects.
+
+ * Any build time issues that might have been introduced by this patch
+ can be identified by a test build; this was done and is available here:
+ https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
+
+ [Other Info]
+
+ * Only impish and jammy are affected.
+ __
+
Description: zlib: compressBound() returns an incorrect result on z15
Symptom: Passing the result of compressBound() to compress()
-results in an error code.
+ results in an error code.
Problem: compressBound() is not adjusted for DFLTCC.
Solution: Adjust compressBound() for DFLTCC like it's already done
-for deflateBound(). Since zlib project does not accept
-patches at the moment, the fix has been integrated into
-the DFLTCC pull request:
-https://github.com/madler/zlib/pull/410
-The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
+ for deflateBound(). Since zlib project does not accept
+ patches at the moment, the fix has been integrated into
+ the DFLTCC pull request:
+ https://github.com/madler/zlib/pull/410
+ The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
Reproduction: z15 only:
-#include
-#include
-#include
-int main() {
-Bytef in_buf[128], out_buf[1024];
-for (size_t i = 0; i < sizeof(in_buf); i++)
-in_buf[i] = rand();
-uLongf dest_len = compressBound(sizeof(in_buf));
-assert(dest_len <= sizeof(out_buf));
-int ret = compress(out_buf, _len,
- in_buf, sizeof(in_buf));
-assert(ret == Z_OK);
-}
+ #include
+ #include
+ #include
+ int main() {
+ Bytef in_buf[128], out_buf[1024];
+ for (size_t i = 0; i < sizeof(in_buf); i++)
+ in_buf[i] = rand();
+ uLongf dest_len = compressBound(sizeof(in_buf));
+ assert(dest_len <= sizeof(out_buf));
+ int ret = compress(out_buf, _len,
+ in_buf, sizeof(in_buf));
+ assert(ret == Z_OK);
+ }
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on IBM z Systems:
New
Status in zlib
[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4
Yeah it seems unlikely to be ssh to me -- can you ping the machine? does
virtualbox networking do interfaces that can ping? Does virtualbox offer
a 'console view' that you can use to debug the system?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1964642
Title:
Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
but can connect to Ubuntu 20.4
Status in openssh package in Ubuntu:
New
Bug description:
Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a
Windows 10 host with Packer 1.5.6, using an unattended installation.
The Packer command was:
"boot_command": [
" ",
"autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
""
],
The user-data file was:
#cloud-config
autoinstall:
version: 1
identity:
realname: mclibre
hostname: ubuntu
password:
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
username: mclibre
locale: es_ES.UTF-8
keyboard:
layout: es
network:
network:
version: 2
ethernets:
ens33: {dhcp4: true, dhcp-identifier: mac}
ssh:
install-server: true
late-commands:
- sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/'
/target/etc/dhcp/dhclient.conf
- 'sed -i "s/dhcp4: true/&\n dhcp-identifier: mac/"
/target/etc/netplan/00-installer-config.yaml'
Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using
packer 1.5.6 but Packer can't create the image because once the installation is
done, after rebooting the SSH server does not answer (the packer log error
says: SSH handshake err: Timeout during SSH handshake).
I have tried with the last version of Packer, Packer 1.8.0, and the result is
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server
20.4.1, .2, .3 or .4 image.
I can provide as much aditional information as you want.
Thanking you in advance,
Bartolome Sintes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964794] Re: Faulty linux-firmware upgrade
I have the same issue (although error messages in English): $ sudo apt install --reinstall linux-firmware Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: gnome-screenshot libegl-mesa0:i386 libegl1:i386 libgles2:i386 libicu67:i386 libopengl0 libopengl0:i386 Use 'sudo apt autoremove' to remove them. The following packages will be upgraded: linux-firmware 1 to upgrade, 0 to newly install, 0 to remove and 168 not to upgrade. 152 not fully installed or removed. Need to get 0 B/238 MB of archives. After this operation, 24.9 MB of additional disk space will be used. (Reading database ... 334963 files and directories currently installed.) Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-18-generic update-initramfs: Generating /boot/initrd.img-5.15.0-17-generic Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I double checked the deb file and there's a /lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin file. Perhaps the issue might be that /lib/firmware/ath11k/WCN6855/hw2.1/regdb.bin is a symlink to this file in the same archive and during unpacking there's the issue described in: https://raphaelhertzog.com/2011/07/18/deciphering-one-of-dpkg-weirdest- errors-unable-to-open-pathtofoo-dpkg-new/ -- 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/1964794 Title: Faulty linux-firmware upgrade Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Can't upgrade the package: Préparation du dépaquetage de .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Dépaquetage de linux-firmware (20220314.gitcd01f857-0ubuntu1) sur (20220302.gitee0667aa-0ubuntu1) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack) : impossible d'ouvrir « /lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new »: Aucun fichier ou dossier de ce type Aucun rapport « apport » n'a été créé car le message d'erreur rapporte un problème sur le système local update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic update-initramfs: Generating /boot/initrd.img-5.15.0-18-generic Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup
Today I tried flatpak version of PulseEffects and it's work for me. Only issue with autostart, but fixed with manually added autostart entry: /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=pulseeffects com.github.wwmm.pulseeffects --gapplication-service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1948882 Title: PulseEffects does not properly initialize on startup Status in d-conf package in Ubuntu: Confirmed Status in pulseeffects package in Ubuntu: New Bug description: In KUbuntu 21.10, PulseEffects no longer initializes its effects chain on startup. I usually use only Equalizer, so when I log into KDE, this equalizer does not get activated. To ativate it I need (i) start PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This is rarher annoying sequence that I have to repeat each time I login. Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just worked immediately after logging in, without any additional actions. I would expect the same behaviour in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseeffects 4.8.4-1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 27 02:56:47 2021 InstallationDate: Installed on 2017-04-03 (1667 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pulseeffects UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15
If this needs SRU'ing to impish please update the bug description
accordingly. I've sponsored this for Jammy.
** Changed in: zlib (Ubuntu Jammy)
Status: New => In Progress
** Changed in: zlib (Ubuntu Jammy)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Brian Murray
(brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on IBM z Systems:
New
Status in zlib package in Ubuntu:
In Progress
Status in zlib source package in Impish:
New
Status in zlib source package in Jammy:
In Progress
Bug description:
Description: zlib: compressBound() returns an incorrect result on z15
Symptom: Passing the result of compressBound() to compress()
results in an error code.
Problem: compressBound() is not adjusted for DFLTCC.
Solution: Adjust compressBound() for DFLTCC like it's already done
for deflateBound(). Since zlib project does not accept
patches at the moment, the fix has been integrated into
the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
Reproduction: z15 only:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, _len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1405452] Re: Typo in man page ("introduce a much improvement mechanism")
** Changed in: wpa (Debian)
Status: New => Fix Released
--
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/1405452
Title:
Typo in man page ("introduce a much improvement mechanism")
Status in One Hundred Papercuts:
Fix Released
Status in wpa package in Ubuntu:
Fix Released
Status in wpa package in Debian:
Fix Released
Bug description:
"introduce a much improvement mechanism" should be "introduce a much
improved mechanism".
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: wpasupplicant 2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 24 16:19:30 2014
InstallationDate: Installed on 2014-12-19 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1405452/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1963904] Re: /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup
** Changed in: packagekit (Ubuntu Jammy) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: packagekit (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1963904 Title: /usr/libexec/packagekitd:11:__strcmp_avx2:AptCacheFile::resolvePkgID:AptIntf::resolvePackageIds:backend_get_details_thread:pk_backend_job_thread_setup Status in packagekit package in Ubuntu: In Progress Status in packagekit source package in Jammy: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.2.5-2ubuntu1, the problem page at https://errors.ubuntu.com/problem/e43a7af1acb9c04a2066e00f2785c7c200145bcc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1963904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964794] Re: Faulty linux-firmware upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1964794 Title: Faulty linux-firmware upgrade Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Can't upgrade the package: Préparation du dépaquetage de .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Dépaquetage de linux-firmware (20220314.gitcd01f857-0ubuntu1) sur (20220302.gitee0667aa-0ubuntu1) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack) : impossible d'ouvrir « /lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new »: Aucun fichier ou dossier de ce type Aucun rapport « apport » n'a été créé car le message d'erreur rapporte un problème sur le système local update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic update-initramfs: Generating /boot/initrd.img-5.15.0-18-generic Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959531] Re: PCI/internal sound card (chtnau8824) not detected updating from 5.11.0-27-generic to kernel 5.13.0-27-generic (Dummy output)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1959531 Title: PCI/internal sound card (chtnau8824) not detected updating from 5.11.0-27-generic to kernel 5.13.0-27-generic (Dummy output) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I was running Ubuntu 20.04 flawlessly, but when I got an update from the kernel 5.11 to the 5.13, then I got the dummy output and no sound comes out from my speakers or mic. I made a fresh install without updating and I got the sound back. When I update the issue comes back. The same problem occurs in other distros with the 5.13 kernel and with the 5.15 as well. I've seen occur in Pop!_OS both 20.04 and 21.10 and in Ubuntu 21.10 with the related kernels. No troubleshooting fixed the issue. When my sound was working the name of my audio device was chtnau8824. I tried inxi -A and got this output: Audio: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit driver: N/A Sound Server: ALSA v: k5.13.0-27-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolff 1337 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 30 20:46:48 2022 InstallationDate: Installed on 2022-01-30 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2018 dmi.bios.release: 8.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8.17 dmi.board.asset.tag: Default string dmi.board.name: PC024 dmi.board.vendor: MULTILASER dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MULTILASER dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/15/2018:br8.17:svnMULTILASER:pnPC024:pvr1:rvnMULTILASER:rnPC024:rvr1.0:cvnMULTILASER:ct10:cvr1:skuPN20170328466: dmi.product.family: EMI30P3S5M122L24B303T0C00W1H2G0G0A0C0P1C0D0C1801M0N1X1WOS dmi.product.name: PC024 dmi.product.sku: PN20170328466 dmi.product.version: 1 dmi.sys.vendor: MULTILASER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1959531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted
I have update ongoing on esm-infa-staging for it, but without consider these issues Dimitri pointed, so, with the clean patch pointed here. It would be nice if any of you folks could give a test on it. Also adding other folks from security to this discussion with better background. Also, tips on how to test it would be nice. I was trying lxc image export with a systemd updated and a non systemd update xenial, but hadn't any luck as both work as the same if you lxc import into a jammy from .tar.gz image exported. -- 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/1962332 Title: xenial systemd fails to start if cgroup2 is mounted Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Bug description: [impact] now that jammy has moved to using unified cgroup2, containers started on jammy must also use unified cgroup2 (since the cgroup subsystems can only be mounted as v1 or v2 throughout the entire system, including inside containers). However, the systemd in xenial does not include support for cgroup2, and doesn't recognize its magic (added in upstream commit 099619957a0), so it fails to start completely. [workaround] On Jammy host edit default kernel command line to include systemd.unified_cgroup_hierarchy=false update your bootloader configuration; and reboot then hybrid cgroups will be on the host, and one can launch xenial container then. [test case] create a jammy system, that has unified cgroup2 mounted. Then: $ lxc launch ubuntu:xenial test-x ... $ lxc shell test-x (inside xenial container): $ mv /sbin/init /sbin/init.old $ cat > /sbin/init <+a q Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems, freezing. Freezing execution. [regression potential] any regression would likely break xenial containers from starting at all, or cause cgroup-related problems with systemd starting and/or managing services. [scope] this is needed only for xenial. However, as xenial is out of standard support, this would need to be an exception. this is fixed upstream with commit 099619957a0 (and possibly others - needs closer investigation and testing) which is first included in v230, so this is fixed already in b and later. this is not needed - by default - for trusty because upstart is used there; however, I think it's possible to change trusty over to use systemd instead of upstart. But since trusty is out of standard support, and it doesn't fail by default, it doesn't seem like it should be fixed. [other info] An alternative appears to be to change the host system back to using the 'hybrid' cgroup, however that obviously is awful and would remove the benefits of cgroup v2 from the host system, and force all containers on the host system to also use the 'hybrid' cgroup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964682] Re: IBus not starting properly at login to wayland with gnome-shell 42
systemd in Build-Depends seems to be it. Thanks Mitsuya and Jeremy! Uploaded again and keeping my fingers crossed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1964682 Title: IBus not starting properly at login to wayland with gnome-shell 42 Status in gnome-shell package in Ubuntu: Invalid Status in ibus package in Ubuntu: In Progress Bug description: To get to the state in the bug summary I did: 1. Installed Ubuntu via the 220312 ISO 2. Made sure that all packages were updated 3. Installed ibus-libpinyin, re-logged in, and added "Intelligent Pinyin" to the input sources 4. Enabled -proposed 5. Run this command: sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 libmutter-10-0 mutter-common 6. Rebooted Now, once logged in, gnome-shell does not include "Intelligent Pinyin" in the input source menu. Several expected processes are missing: $ ps aux | grep ibus gunnar 3057 0.0 0.0 232404 7984 ?Sl 20:05 0:00 ibus-daemon --panel disable -r --xim gunnar 3076 0.0 0.0 157280 6228 ?Sl 20:05 0:00 /usr/libexec/ibus-memconf gunnar 5117 0.0 0.0 24492 2776 pts/0S+ 20:06 0:00 grep --color=auto ibus If I start ibus-setup it shows the attached dialog. From there I can click "Yes" and successfully start IBus that way, and then it works as expected. Note that im-config is not involved. Nowadays, on GNOME desktops, we rely completely on the GNOME mechanisms for starting and configuring IBus. One thought is that ibus upstream has not released since August 20. Can it possibly be that some unreleased upstream ibus commits are needed for gnome-shell 42? https://github.com/ibus/ibus/commits/master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools
Why 'apt-get install ubuntu-extended-support' or similar isn't considered simple there and you prefer to redefine meaning of 'minimal' instead ? -- 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/1930914 Title: ubuntu-minimal depends on ubuntu-advantage-tools Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: This is counter to #1566183 There is no reason to enforce desktop users who manage machine on their own to install ubuntu-advantage- tools, especially when this is 'minimal' version. This should include only essential packages to make the OS functional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-minimal 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106 Uname: Linux 5.4.0-73-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 4 18:54:56 2021 InstallationDate: Installed on 2020-01-29 (491 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964808] [NEW] Wifi keeps disconnecting
Public bug reported: I have a box with 802-11n and I run into a problem with my Lenovo laptop : - when I change the wifi password, it connects immediately and works well - the next time (for example after switching the airplane mode on and off), it fails and the network manager keeps asking me the password again and again Please notice that I have no problem with other wifi access points (when going in other places with my laptop), and my box works well with every other devices (ubuntu laptops, android phones) but mine ! My laptop runs an updated 20.04.4, but the problem first came when I was on 21.04. I then made a fresh install of 21.10 and then a fresh install on 20.04 just to make sure the kernel was not involved. Even tried the last Intel Clear Linux without success. As a workaround, I tried to stop and restart wpa_supplicant: sudo systemctl disable --now wpa_supplicant.service sudo systemctl enable --now wpa_supplicant.service but this did not solve the problem. I also contacted the support of my ISP and they made a clear reset of my box without success. Here is what I see in dmesg : [ 4203.366374] wlp4s0: authenticate with e4:9e:12:8c:8e:1a [ 4203.374010] wlp4s0: send auth to e4:9e:12:8c:8e:1a (try 1/3) [ 4203.378464] wlp4s0: authenticated [ 4203.383534] wlp4s0: associate with e4:9e:12:8c:8e:1a (try 1/3) [ 4203.387408] wlp4s0: RX AssocResp from e4:9e:12:8c:8e:1a (capab=0x1411 status=0 aid=6) [ 4203.391628] wlp4s0: associated [ 4203.399358] wlp4s0: deauthenticating from e4:9e:12:8c:8e:1a by local choice (Reason: 17=IE_DIFFERENT) And here is the restult of lspci : 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-V (rev 21) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 88) 05:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1964808 Title: Wifi keeps disconnecting Status in network-manager package in Ubuntu: New Bug description: I have a box with 802-11n and I run into a problem with my Lenovo laptop : - when I change the wifi password, it connects immediately and works well - the next time (for example after switching the airplane mode on and off), it fails and the network manager keeps asking me the password again and again Please notice that I have no problem with other wifi access points (when going in other places with my laptop), and my box works well with every other devices (ubuntu laptops, android phones) but mine ! My laptop runs an updated 20.04.4, but the problem first came when I was on 21.04. I then made a fresh install of 21.10 and then a fresh install on 20.04 just to make sure the kernel was not involved. Even tried the last Intel Clear Linux without success. As a workaround, I tried to stop and restart wpa_supplicant: sudo systemctl disable --now wpa_supplicant.service sudo systemctl enable --now wpa_supplicant.service but this did not solve the problem. I also contacted the support of my ISP and they made a clear reset of my box without success. Here is what I see in dmesg : [ 4203.366374] wlp4s0: authenticate with e4:9e:12:8c:8e:1a [ 4203.374010] wlp4s0: send auth to e4:9e:12:8c:8e:1a (try 1/3) [ 4203.378464] wlp4s0: authenticated [ 4203.383534] wlp4s0: associate with e4:9e:12:8c:8e:1a (try 1/3) [
[Touch-packages] [Bug 1964682] Re: IBus not starting properly at login to wayland with gnome-shell 42
Yes, I expect a Build-Depends on systemd will fix the build problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1964682 Title: IBus not starting properly at login to wayland with gnome-shell 42 Status in gnome-shell package in Ubuntu: Invalid Status in ibus package in Ubuntu: In Progress Bug description: To get to the state in the bug summary I did: 1. Installed Ubuntu via the 220312 ISO 2. Made sure that all packages were updated 3. Installed ibus-libpinyin, re-logged in, and added "Intelligent Pinyin" to the input sources 4. Enabled -proposed 5. Run this command: sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 libmutter-10-0 mutter-common 6. Rebooted Now, once logged in, gnome-shell does not include "Intelligent Pinyin" in the input source menu. Several expected processes are missing: $ ps aux | grep ibus gunnar 3057 0.0 0.0 232404 7984 ?Sl 20:05 0:00 ibus-daemon --panel disable -r --xim gunnar 3076 0.0 0.0 157280 6228 ?Sl 20:05 0:00 /usr/libexec/ibus-memconf gunnar 5117 0.0 0.0 24492 2776 pts/0S+ 20:06 0:00 grep --color=auto ibus If I start ibus-setup it shows the attached dialog. From there I can click "Yes" and successfully start IBus that way, and then it works as expected. Note that im-config is not involved. Nowadays, on GNOME desktops, we rely completely on the GNOME mechanisms for starting and configuring IBus. One thought is that ibus upstream has not released since August 20. Can it possibly be that some unreleased upstream ibus commits are needed for gnome-shell 42? https://github.com/ibus/ibus/commits/master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964803] Re: packagekitd crashed with SIGSEGV in pkgSourceList::AddVolatileFile()
*** This bug is a duplicate of bug 1916035 *** https://bugs.launchpad.net/bugs/1916035 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1916035, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1964803/+attachment/5568722/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1964803/+attachment/5568724/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1964803/+attachment/5568727/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1964803/+attachment/5568728/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1964803/+attachment/5568729/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1964803/+attachment/5568730/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1964803/+attachment/5568731/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1916035 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1964803 Title: packagekitd crashed with SIGSEGV in pkgSourceList::AddVolatileFile() Status in packagekit package in Ubuntu: New Bug description: MDATP crashes while increasing the loglevel ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-2ubuntu1 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 CasperMD5CheckResult: pass Date: Mon Mar 14 17:29:14 2022 ExecutablePath: /usr/libexec/packagekitd InstallationDate: Installed on 2022-02-11 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220211) ProcCmdline: /usr/libexec/packagekitd ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/sh SegvAnalysis: Segfault happened at: 0x7f7611e26d05 <_ZN13pkgSourceList15AddVolatileFileEP12pkgIndexFile+21>: mov 0x18(%rdi),%rsi PC (0x7f7611e26d05) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rsi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: packagekit StacktraceTop: pkgSourceList::AddVolatileFile(pkgIndexFile*) () from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 pkgSourceList::AddVolatileFile(std::__cxx11::basic_string, std::allocator > const&, std::vector, std::allocator >, std::allocator, std::allocator > > >*) () from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 AptIntf::init(char**) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so ?? () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so ?? () Title: packagekitd crashed with SIGSEGV in pkgSourceList::AddVolatileFile() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1964803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools
People must be allowed to upgrade their Ubuntu LTS install to get the 10 years of Extended Security Maintenance support offered by Ubuntu Advantage or Ubuntu Pro. This needs to work easily for everyone running Ubuntu. That is done with ubuntu-advantage-tools so that's why it's installed and not intended to be removed. The information collection you are referring to is not handled by ubuntu-advantage-tools. You would need to file a separate bug about that issue, preferably with a test case of what isn't working correctly. -- 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/1930914 Title: ubuntu-minimal depends on ubuntu-advantage-tools Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: This is counter to #1566183 There is no reason to enforce desktop users who manage machine on their own to install ubuntu-advantage- tools, especially when this is 'minimal' version. This should include only essential packages to make the OS functional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-minimal 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106 Uname: Linux 5.4.0-73-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 4 18:54:56 2021 InstallationDate: Installed on 2020-01-29 (491 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962780] Re: During install "error processing package libglib2.0-0:i386"
** Changed in: glib2.0 (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962780 Title: During install "error processing package libglib2.0-0:i386" Status in glib2.0 package in Ubuntu: Confirmed Bug description: Installing the update for libglib2.0-0:i386 fails on two different computers. Output follows for the update. The errors are near the bottom. Other requested info is at the bottom. (Reading database ... 446385 files and directories currently installed.) Preparing to unpack .../0-libc6-i386_2.31-0ubuntu9.7_amd64.deb ... Unpacking libc6-i386 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ... Replaced by files in installed package libc6:i386 (2.31-0ubuntu9.3) ... Preparing to unpack .../1-libc6-dev_2.31-0ubuntu9.7_amd64.deb ... Unpacking libc6-dev:amd64 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ... Preparing to unpack .../2-libc-dev-bin_2.31-0ubuntu9.7_amd64.deb ... Unpacking libc-dev-bin (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ... Preparing to unpack .../3-libc6-dbg_2.31-0ubuntu9.7_amd64.deb ... Unpacking libc6-dbg:amd64 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ... Preparing to unpack .../4-libc6_2.31-0ubuntu9.7_i386.deb ... De-configuring libc6:amd64 (2.31-0ubuntu9.3) ... Unpacking libc6:i386 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ... Preparing to unpack .../5-libc6_2.31-0ubuntu9.7_amd64.deb ... Unpacking libc6:amd64 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ... Setting up libc6:amd64 (2.31-0ubuntu9.7) ... (Reading database ... 446385 files and directories currently installed.) Preparing to unpack .../locales_2.31-0ubuntu9.7_all.deb ... Unpacking locales (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ... Preparing to unpack .../libc-bin_2.31-0ubuntu9.7_amd64.deb ... Unpacking libc-bin (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ... Setting up libc-bin (2.31-0ubuntu9.7) ... (Reading database ... 446385 files and directories currently installed.) Preparing to unpack .../libgtk-3-common_3.24.20-0ubuntu1.1_all.deb ... Unpacking libgtk-3-common (3.24.20-0ubuntu1.1) over (3.24.20-0ubuntu1) ... Setting up libgtk-3-common (3.24.20-0ubuntu1.1) ... (Reading database ... 446385 files and directories currently installed.) Preparing to unpack .../libgail-3-0_3.24.20-0ubuntu1.1_amd64.deb ... Unpacking libgail-3-0:amd64 (3.24.20-0ubuntu1.1) over (3.24.20-0ubuntu1) ... Preparing to unpack .../libgtk-3-0_3.24.20-0ubuntu1.1_amd64.deb ... Unpacking libgtk-3-0:amd64 (3.24.20-0ubuntu1.1) over (3.24.20-0ubuntu1) ... dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libc6 (>= 2.28); however: Package libc6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libc6 (>= 2.28); however: Package libc6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libc6 (>= 2.28); however: Package libc6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libc6 (>= 2.28); however: Package libc6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed No apport report written because MaxReports is reached already and this goes on for a VERY long time! It hangs the package manager! Full output is attached. I am using Linux Mint 20.3 ralph@toumeya:~/Desktop$ sudo apt-cache policy libglib2.0-0:i386 libglib2.0-0:i386: Installed: 2.64.6-1~ubuntu20.04.4 Candidate: 2.64.6-1~ubuntu20.04.4 Version table: *** 2.64.6-1~ubuntu20.04.4 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 2.64.6-1~ubuntu20.04.3 500 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 2.64.2-1~fakesync1 500 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages ralph@toumeya:~/Desktop$ I expect the install to occur with NO errors! Questions?? Drop me a note! I have been using Debian distributions for 15+ years. Ralph To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1962780/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1964682] Re: IBus not starting properly at login to wayland with gnome-shell 42
Hi, > No package 'systemd' found Simply, is it because ibus version 1.5.26 now requires systemd? https://github.com/ibus/ibus/pull/2377 - Salsa CI: it seems that systemd is not installed (just docker instance?) - PPA builder: systemd is installed - Local: normally systemd is installed I don't know if this fix is necessary for Ubuntu as well, but if im- config handles it well, it may be possible to build with the "--disable- systemd-services" option. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1964682 Title: IBus not starting properly at login to wayland with gnome-shell 42 Status in gnome-shell package in Ubuntu: Invalid Status in ibus package in Ubuntu: In Progress Bug description: To get to the state in the bug summary I did: 1. Installed Ubuntu via the 220312 ISO 2. Made sure that all packages were updated 3. Installed ibus-libpinyin, re-logged in, and added "Intelligent Pinyin" to the input sources 4. Enabled -proposed 5. Run this command: sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 libmutter-10-0 mutter-common 6. Rebooted Now, once logged in, gnome-shell does not include "Intelligent Pinyin" in the input source menu. Several expected processes are missing: $ ps aux | grep ibus gunnar 3057 0.0 0.0 232404 7984 ?Sl 20:05 0:00 ibus-daemon --panel disable -r --xim gunnar 3076 0.0 0.0 157280 6228 ?Sl 20:05 0:00 /usr/libexec/ibus-memconf gunnar 5117 0.0 0.0 24492 2776 pts/0S+ 20:06 0:00 grep --color=auto ibus If I start ibus-setup it shows the attached dialog. From there I can click "Yes" and successfully start IBus that way, and then it works as expected. Note that im-config is not involved. Nowadays, on GNOME desktops, we rely completely on the GNOME mechanisms for starting and configuring IBus. One thought is that ibus upstream has not released since August 20. Can it possibly be that some unreleased upstream ibus commits are needed for gnome-shell 42? https://github.com/ibus/ibus/commits/master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964794] [NEW] Faulty linux-firmware upgrade
Public bug reported: Can't upgrade the package: Préparation du dépaquetage de .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Dépaquetage de linux-firmware (20220314.gitcd01f857-0ubuntu1) sur (20220302.gitee0667aa-0ubuntu1) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack) : impossible d'ouvrir « /lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new »: Aucun fichier ou dossier de ce type Aucun rapport « apport » n'a été créé car le message d'erreur rapporte un problème sur le système local update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic update-initramfs: Generating /boot/initrd.img-5.15.0-18-generic Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: ath11k firmware jammy upgrade-software-version ** Tags added: jammy ** Tags added: ath11k firmware ** Tags added: upgrade-software-version -- 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/1964794 Title: Faulty linux-firmware upgrade Status in initramfs-tools package in Ubuntu: New Bug description: Can't upgrade the package: Préparation du dépaquetage de .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Dépaquetage de linux-firmware (20220314.gitcd01f857-0ubuntu1) sur (20220302.gitee0667aa-0ubuntu1) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack) : impossible d'ouvrir « /lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new »: Aucun fichier ou dossier de ce type Aucun rapport « apport » n'a été créé car le message d'erreur rapporte un problème sur le système local update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic update-initramfs: Generating /boot/initrd.img-5.15.0-18-generic Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961425] Re: 22.04: FTBFS due to test failure
Just noticed that version 0.8.0-2ubuntu2 ( https://launchpad.net/ubuntu/+source/capnproto/0.8.0-2ubuntu2 ) landed at the start of the month. This version has a patch that fixes the string issue; renameat2 issue remains, but it won't trigger unless building (and running the unit tests) from a ZFS volume. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to capnproto in Ubuntu. https://bugs.launchpad.net/bugs/1961425 Title: 22.04: FTBFS due to test failure Status in The Ubuntu-power-systems project: New Status in capnproto package in Ubuntu: Confirmed Bug description: Hi, capnproto 0.8.0-2ubuntu1 fails on ppc64el : https://launchpad.net/ubuntu/+source/capnproto/0.8.0-2ubuntu1/+build/23090234/+files/buildlog_ubuntu-jammy-ppc64el.capnproto_0.8.0-2ubuntu1_BUILDING.txt.gz Lowering optimization (O3->O2) level makes the failing test pass, for instance adding export DEB_CXXFLAGS_MAINT_APPEND=-O1 export DEB_CXXFLAGS_MAINT_STRIP=-O3 in debian/rules. For the time being that can be the way to go as 0.9.1-2 from Debian Experimental builds fine on Jammy by default with O3. F. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1961425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964682] Re: IBus not starting properly at login to wayland with gnome-shell 42
Yeah, I too think it looks like bug fixes only. But there is a problem: Salsa's pipeline shows a build failure: https://salsa.debian.org/debian/ibus/-/pipelines/358170 But since I already had built successfully in a jammy PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus/+packages and also built successfully locally on Debian testing, I decided to take a chance and uploaded anyway. Proved to not be very wise: https://buildd.debian.org/status/package.php?p=ibus I will need some help to figure out what the problem is. (There is of course the option to upload it directly to Ubuntu as -0ubuntu1 for now. But I feel it would be safer to make the build succeed on Debian first so the Debian side gets involved.) ** Changed in: ibus (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1964682 Title: IBus not starting properly at login to wayland with gnome-shell 42 Status in gnome-shell package in Ubuntu: Invalid Status in ibus package in Ubuntu: In Progress Bug description: To get to the state in the bug summary I did: 1. Installed Ubuntu via the 220312 ISO 2. Made sure that all packages were updated 3. Installed ibus-libpinyin, re-logged in, and added "Intelligent Pinyin" to the input sources 4. Enabled -proposed 5. Run this command: sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 libmutter-10-0 mutter-common 6. Rebooted Now, once logged in, gnome-shell does not include "Intelligent Pinyin" in the input source menu. Several expected processes are missing: $ ps aux | grep ibus gunnar 3057 0.0 0.0 232404 7984 ?Sl 20:05 0:00 ibus-daemon --panel disable -r --xim gunnar 3076 0.0 0.0 157280 6228 ?Sl 20:05 0:00 /usr/libexec/ibus-memconf gunnar 5117 0.0 0.0 24492 2776 pts/0S+ 20:06 0:00 grep --color=auto ibus If I start ibus-setup it shows the attached dialog. From there I can click "Yes" and successfully start IBus that way, and then it works as expected. Note that im-config is not involved. Nowadays, on GNOME desktops, we rely completely on the GNOME mechanisms for starting and configuring IBus. One thought is that ibus upstream has not released since August 20. Can it possibly be that some unreleased upstream ibus commits are needed for gnome-shell 42? https://github.com/ibus/ibus/commits/master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools
>It is required for the Ubuntu product to work as intended so we're not going >to make it optional. Could you make it clear what means 'as intended' ? As most users are not interested in this, are you bound by some state actor to track users ? This would be clear signal for users to search for alternative distro. -- 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/1930914 Title: ubuntu-minimal depends on ubuntu-advantage-tools Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: This is counter to #1566183 There is no reason to enforce desktop users who manage machine on their own to install ubuntu-advantage- tools, especially when this is 'minimal' version. This should include only essential packages to make the OS functional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-minimal 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106 Uname: Linux 5.4.0-73-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 4 18:54:56 2021 InstallationDate: Installed on 2020-01-29 (491 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Description changed: + [Impact] + + * In order to use the microk8s snap in Ubuntu Core, one currently needs + to be root. This is far from optimal, since normally (on desktop and + server installations) this is not necessary. + + * This make it hard to provide consistent documentation on microk8s + across all supported device, if we have to take the "sudo" command into + account, and how file permissions for generated files might be affected. + + + [Test Plan] + + The issue can be reproduced on Ubuntu Core 18, 20 and 22. The steps are + as following (replace "" with the actual path of your Ubuntu + Core image file: + + qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \ + -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ + -device virtio-net-pci,netdev=mynet0 \ + -drive file=,format=raw + + + + + Original bug description + + Currently doing something like: - sudo usermod -a -G snap_microk8s dbeamonte + sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with - usermod: /etc/group.15965: Read-only file system + usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" Status in shadow package in Ubuntu: New Status in shadow source package in Bionic: New Status in shadow source package in Focal: New Status in shadow source package in Impish: Won't Fix Status in shadow source package in Jammy: New Bug description: [Impact] * In order to use the microk8s snap in Ubuntu Core, one currently needs to be root. This is far from optimal, since normally (on desktop and server installations) this is not necessary. * This make it hard to provide consistent documentation on microk8s across all supported device, if we have to take the "sudo" command into account, and how file permissions for generated files might be affected. [Test Plan] The issue can be reproduced on Ubuntu Core 18, 20 and 22. The steps are as following (replace "" with the actual path of your Ubuntu Core image file: qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=,format=raw Original bug description Currently doing something like: sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
Marking as Invalid for Impish, since the issue only happens with a read- only rootfs like we use in Ubuntu Core, and UC is only based on LTS releases. ** Changed in: shadow (Ubuntu Impish) Status: New => Won't Fix ** Changed in: shadow (Ubuntu Impish) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" Status in shadow package in Ubuntu: New Status in shadow source package in Bionic: New Status in shadow source package in Focal: New Status in shadow source package in Impish: Won't Fix Status in shadow source package in Jammy: New Bug description: Currently doing something like: sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906420] Re: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author)
The Desktop Icons NG extension is installed by default in Ubuntu 21.10. ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => 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/1906420 Title: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author) Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: By default, Ubuntu installs the Gnome extension "Desktop Icons" [1] (by rastersoft). Unfortunately, this extension is now unmaintained, is problematic, and leads to several bugs, including but not limited to Bug #1901150 and Bug #1813441. The same author has created, and continues to maintain, the far superior "Desktop Icons NG (DING)" [2]. It solves a number of problems including the two aforementioned bugs. It's possible to disable, but not uninstall, "Desktop Icons", and then to install "Desktop Icons NG (DING)". I did this a while ago with great results. If Canonical replaces the former with the latter, not only will Ubuntu be using a better desktop manager, but also it will be able clear all related bugs at a stroke. This is a simple, cheap, quick and effective solution that will let the devs concentrate on more important tasks. Please give this serious consideration. More information: Ubuntu 20.04.1 LTS 64-bit Gnome version 3.36.3 [1] https://extensions.gnome.org/extension/1465/desktop-icons/ [2] https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1906420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools
@wontfix, install motd-news-config if you need to configure that file. It's installed by default on Ubuntu Server; I don't believe it's needed on Ubuntu Desktop. Sorry, ubuntu-advantage-tools is required to allow people to use Ubuntu Advantage or Ubuntu Pro. It is required for the Ubuntu product to work as intended so we're not going to make it optional. ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1930914 Title: ubuntu-minimal depends on ubuntu-advantage-tools Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: This is counter to #1566183 There is no reason to enforce desktop users who manage machine on their own to install ubuntu-advantage- tools, especially when this is 'minimal' version. This should include only essential packages to make the OS functional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-minimal 1.450.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106 Uname: Linux 5.4.0-73-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 4 18:54:56 2021 InstallationDate: Installed on 2020-01-29 (491 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1956124] Re: wpasupplicant is a required package for most desktop metapackages
I believe businesses can create their own metapackages or have other ways of providing system images. Not having wifi connectivity is a critical bug for most people. Without internet connectivity, it is really difficult to install the package you need to get Wi-Fi working. There are laptops without ethernet ports now. Therefore, I'm closing this bug. ** No longer affects: wpasupplicant (Ubuntu) ** Changed in: ubuntu-meta (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1956124 Title: wpasupplicant is a required package for most desktop metapackages Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: Many people and business not use or require wireless internet or WiFi encryption on many types of machines. They may actively not want their business or institutional environment to have access to WiFi at all where manual hardware removal is too much effort. Requiring these packages significantly increases the effort required to ensure their desires are enforced. For hobbyists or students using wired ARM or x86 boards, such requirements increase the footprint on sometimes small eMMC or SD storage devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1956124/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1956125] Re: wireless-tools is a required package for most desktop metapackages
Closing for the same reasons as LP: #1956124 ** No longer affects: wireless-tools (Ubuntu) ** Changed in: ubuntu-meta (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1956125 Title: wireless-tools is a required package for most desktop metapackages Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: Many people and business not use or require wireless internet or communication on many types of machines. They may actively not want their business or institutional environment to have access to WiFi at all where manual hardware removal is too much effort. Requiring these packages significantly increases the effort required to ensure their desires are enforced. For hobbyists or students using wired ARM or x86 boards, such requirements increase the footprint on sometimes small eMMC or SD storage devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1956125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1956123] Re: yelp help browser is a required package for most desktop metapackages
The help browser is required for the Help menu button to work in many of our GNOME apps. I don't see any practical benefit to users to not have this package installed. ** No longer affects: yelp (Ubuntu) ** Changed in: ubuntu-meta (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1956123 Title: yelp help browser is a required package for most desktop metapackages Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: It should be a recommends based on function and current date alone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1956123/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962638] Re: Ubuntu dock overlaps programs after resume from screen blank
** Package changed: ubuntu-meta (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1962638 Title: Ubuntu dock overlaps programs after resume from screen blank Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu-desktop: Installed: 1.472 Candidate: 1.472 Version table: *** 1.472 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen - The Ubuntu dock should be displayed next to a program after resume from screen blank. 4) What happened instead - The Ubuntu dock overlaps the program when resuming from screen blank. I have to click "Restore Down" and then "Maximize" so that the dock is displayed next to the program, rather than over the top of it. It doesn't happen on every resume from screen blank, it happens randomly and it happens on different programs. I have "Auto-hide the Dock" disabled. Please see screenshot for an example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1962638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964682] Re: IBus not starting properly at login to wayland with gnome-shell 42
Gunnar, that new release sounds like bug fixes to me. There are several other bug fixes in that release we need anyway. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1964682 Title: IBus not starting properly at login to wayland with gnome-shell 42 Status in gnome-shell package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: To get to the state in the bug summary I did: 1. Installed Ubuntu via the 220312 ISO 2. Made sure that all packages were updated 3. Installed ibus-libpinyin, re-logged in, and added "Intelligent Pinyin" to the input sources 4. Enabled -proposed 5. Run this command: sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 libmutter-10-0 mutter-common 6. Rebooted Now, once logged in, gnome-shell does not include "Intelligent Pinyin" in the input source menu. Several expected processes are missing: $ ps aux | grep ibus gunnar 3057 0.0 0.0 232404 7984 ?Sl 20:05 0:00 ibus-daemon --panel disable -r --xim gunnar 3076 0.0 0.0 157280 6228 ?Sl 20:05 0:00 /usr/libexec/ibus-memconf gunnar 5117 0.0 0.0 24492 2776 pts/0S+ 20:06 0:00 grep --color=auto ibus If I start ibus-setup it shows the attached dialog. From there I can click "Yes" and successfully start IBus that way, and then it works as expected. Note that im-config is not involved. Nowadays, on GNOME desktops, we rely completely on the GNOME mechanisms for starting and configuring IBus. One thought is that ibus upstream has not released since August 20. Can it possibly be that some unreleased upstream ibus commits are needed for gnome-shell 42? https://github.com/ibus/ibus/commits/master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958284] Re: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec
Any updates on this? -- 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/1958284 Title: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: Confirmed Bug description: With systemd v245 as shipped with 20.04, the shutdown sequence does not use the value of `DefaultTimeoutStopSec` to wait for remaining processes, it instead uses the compiled in default of 90s. This is most visible with services that use `KillMode=process` (docker, k8s, k3s, etc...), especially if the remaining processes do not handle `SIGTERM` or choose to ignore it. For example: ``` [ OK ] Finished Reboot. [ OK ] Reached target Reboot. [ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim, containerd-shim, containerd-shim, fluent-bit --- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower value --- ``` The bug has been fixed upstream here: https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22 Marc was kind enough to package the patch for 20.04 so I could test it (https://launchpad.net/~mdeslaur/+archive/ubuntu/testing/+sourcepub/13210617/+listing- archive-extra) and with that package, I can confirm that it indeed fixes the issue. Here's a few github issues I stumbled upon while trying to debug this, along with a short writeup of the workaround I ended up using: - https://github.com/moby/moby/issues/41831 - https://github.com/k3s-io/k3s/issues/2400 - https://github.com/systemd/systemd/issues/16991 - https://raby.sh/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html Of course, it would be much better if all the processes would properly handle `SIGTERM`, but having a way to enforce a maximum wait time at shutdown is a decent workaround. Given that the patch is relatively simple, would it be possible to add it the package for 20.04? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958284/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Patch added: "debdiff for Bionic" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568639/+files/0001-Bionic-patch-for-LP-1959375.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" Status in shadow package in Ubuntu: New Status in shadow source package in Bionic: New Status in shadow source package in Focal: New Status in shadow source package in Impish: New Status in shadow source package in Jammy: New Bug description: Currently doing something like: sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964682] Re: IBus not starting properly at login to wayland with gnome-shell 42
Upstream just released ibus 1.5.26. I tested it in jammy, and it proved to solve this issue. I'm about to upload to unstable. Maybe somebody can decide if it can be considered a bug fix release which can be synced without a FFe request: https://github.com/ibus/ibus/releases/tag/1.5.26 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1964682 Title: IBus not starting properly at login to wayland with gnome-shell 42 Status in gnome-shell package in Ubuntu: New Status in ibus package in Ubuntu: New Bug description: To get to the state in the bug summary I did: 1. Installed Ubuntu via the 220312 ISO 2. Made sure that all packages were updated 3. Installed ibus-libpinyin, re-logged in, and added "Intelligent Pinyin" to the input sources 4. Enabled -proposed 5. Run this command: sudo apt install gnome-shell gnome-shell-common gir1.2-mutter-10 libmutter-10-0 mutter-common 6. Rebooted Now, once logged in, gnome-shell does not include "Intelligent Pinyin" in the input source menu. Several expected processes are missing: $ ps aux | grep ibus gunnar 3057 0.0 0.0 232404 7984 ?Sl 20:05 0:00 ibus-daemon --panel disable -r --xim gunnar 3076 0.0 0.0 157280 6228 ?Sl 20:05 0:00 /usr/libexec/ibus-memconf gunnar 5117 0.0 0.0 24492 2776 pts/0S+ 20:06 0:00 grep --color=auto ibus If I start ibus-setup it shows the attached dialog. From there I can click "Yes" and successfully start IBus that way, and then it works as expected. Note that im-config is not involved. Nowadays, on GNOME desktops, we rely completely on the GNOME mechanisms for starting and configuring IBus. One thought is that ibus upstream has not released since August 20. Can it possibly be that some unreleased upstream ibus commits are needed for gnome-shell 42? https://github.com/ibus/ibus/commits/master To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964764] Re: packagekitd crashed with SIGSEGV in AptCacheFile::resolvePkgID()
*** This bug is a duplicate of bug 1964559 *** https://bugs.launchpad.net/bugs/1964559 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1964559, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1964764/+attachment/5568626/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1964764/+attachment/5568628/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1964764/+attachment/5568631/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1964764/+attachment/5568632/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1964764/+attachment/5568633/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1964764/+attachment/5568634/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1964764/+attachment/5568635/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1964559 ** Information type changed from Private Security to Public Security ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1964764 Title: packagekitd crashed with SIGSEGV in AptCacheFile::resolvePkgID() Status in packagekit package in Ubuntu: New Bug description: packagekitd crashed with SIGSEGV in AptCacheFile::resolvePkgID() ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-2ubuntu1 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 CasperMD5CheckResult: fail Date: Mon Mar 14 17:53:10 2022 ExecutablePath: /usr/libexec/packagekitd InstallationDate: Installed on 2022-03-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220310) ProcCmdline: /usr/libexec/packagekitd ProcEnviron: LANG=zh_CN.UTF-8 LANGUAGE=zh_CN:zh PATH=(custom, no user) SHELL=/bin/sh SegvAnalysis: Segfault happened at: 0x7fe6a5063e0e <__strcmp_sse2_unaligned+30>: movdqu (%rdi),%xmm1 PC (0x7fe6a5063e0e) ok source "(%rdi)" (0x7fe7226b66dc) not located in a known VMA region (needed readable region)! destination "%xmm1" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: packagekit StacktraceTop: AptCacheFile::resolvePkgID(char const*) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so AptIntf::resolvePackageIds(char**, unsigned long) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so ?? () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so ?? () g_tree_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: packagekitd crashed with SIGSEGV in AptCacheFile::resolvePkgID() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1964764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup
After a recent daily update Pulseeffects just stopped working entirely (literal silence from the PE(apps) stream). No idea if this is related to this bug in any way. Difficult to say which package update was responsible for that, seemingly nothing obviously related. I tried to upgrade the system to the current development realese of 22.04, and the same the issue remains. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1948882 Title: PulseEffects does not properly initialize on startup Status in d-conf package in Ubuntu: Confirmed Status in pulseeffects package in Ubuntu: New Bug description: In KUbuntu 21.10, PulseEffects no longer initializes its effects chain on startup. I usually use only Equalizer, so when I log into KDE, this equalizer does not get activated. To ativate it I need (i) start PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This is rarher annoying sequence that I have to repeat each time I login. Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just worked immediately after logging in, without any additional actions. I would expect the same behaviour in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseeffects 4.8.4-1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 27 02:56:47 2021 InstallationDate: Installed on 2017-04-03 (1667 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pulseeffects UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964763] [NEW] QtChooser doesn't support qt6
Public bug reported: qtchooser doesn't run qt6 applications because it doesn't have a qt6.conf/6.conf file yet. In order to work, it must have two files `/usr/lib/x86_64-linux- gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux- gnu/qtchooser/6.conf` with this content: ``` /usr/lib/qt6/bin /usr/lib/x86_64-linux-gnu ``` Without it, lupdate, lrelease, and any other qt6 tools show this error: `could not find a Qt installation of ''` ** Affects: qtchooser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtchooser in Ubuntu. https://bugs.launchpad.net/bugs/1964763 Title: QtChooser doesn't support qt6 Status in qtchooser package in Ubuntu: New Bug description: qtchooser doesn't run qt6 applications because it doesn't have a qt6.conf/6.conf file yet. In order to work, it must have two files `/usr/lib/x86_64-linux- gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux- gnu/qtchooser/6.conf` with this content: ``` /usr/lib/qt6/bin /usr/lib/x86_64-linux-gnu ``` Without it, lupdate, lrelease, and any other qt6 tools show this error: `could not find a Qt installation of ''` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1964763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Patch added: "debdiff for Jammy" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568614/+files/0001-Jammy-changes-for-LP-1797786.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" Status in shadow package in Ubuntu: New Status in shadow source package in Bionic: New Status in shadow source package in Focal: New Status in shadow source package in Impish: New Status in shadow source package in Jammy: New Bug description: Currently doing something like: sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Patch removed: "debdiff for Focal" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568607/+files/0001-Add-automatic-detection-of-extrausers-for-usermod-G.patch ** Patch added: "debdiff for Focal" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568613/+files/0001-Add-automatic-detection-of-extrausers-for-usermod-G.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" Status in shadow package in Ubuntu: New Status in shadow source package in Bionic: New Status in shadow source package in Focal: New Status in shadow source package in Impish: New Status in shadow source package in Jammy: New Bug description: Currently doing something like: sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Patch removed: "Patch for focal" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568568/+files/0001-Add-automatic-detection-of-extrausers-for-usermod-G.patch ** Patch added: "debdiff for Focal" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568607/+files/0001-Add-automatic-detection-of-extrausers-for-usermod-G.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" Status in shadow package in Ubuntu: New Status in shadow source package in Bionic: New Status in shadow source package in Focal: New Status in shadow source package in Impish: New Status in shadow source package in Jammy: New Bug description: Currently doing something like: sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
I tested a newer version of the patch that Michael sent me, and I verify that it works properly :-) I'm attaching it here; it includes changes to the 1015_add_zsys_support.patch, but that's only as a result of a quilt refresh, since the patch did not apply cleanly anymore (since src/usermod.c was modified in our patch before). I've been testing this on Focal. ** Patch added: "Patch for focal" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568568/+files/0001-Add-automatic-detection-of-extrausers-for-usermod-G.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" Status in shadow package in Ubuntu: New Status in shadow source package in Bionic: New Status in shadow source package in Focal: New Status in shadow source package in Impish: New Status in shadow source package in Jammy: New Bug description: Currently doing something like: sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1964741] Re: date command produces "invalid date" on day of DST change when calculating a time between 02:00 and 02:59
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1964741 Title: date command produces "invalid date" on day of DST change when calculating a time between 02:00 and 02:59 Status in coreutils package in Ubuntu: New Bug description: When calculating a timestamp for a time between 02:00 and 02:59 in some locales, date will report "invalid date". This only occurs if the system time is currently during the day that standard time transitions to daylight time. Example: OS Version information: Distributor ID: Ubuntu Description:Ubuntu 20.04.4 LTS Release:20.04 Codename: focal System Locale is: America/Chicago System time the command was issued: Sun 13 Mar 2022 10:15:18 PM CDT Command issued: date +%s -d 'tomorrow 02:50' System Response: date: invalid date 'tomorrow 02:50' If the command issued is changed such that the calculated time is anything other than a time between 02:00 and 02:59 the output is normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1964741/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
