[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
** Description changed: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to - the end of the upgrade, I got an „Oh, no! [something, I do not remember] - and the system cannot recover. Call the system administrator” message - after a red FAILED in the terminal. The system administrator is myself, + the end of the upgrade, I got an „Oh, no! Something has gone wrong and + the system cannot recover. Call the system administrator” message after + a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half our to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: - default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 - 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 - 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown + default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 + 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 + 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.45.90 connected started full enabled enabled enabled missing enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.45.90 connected started full enabled enabled enabled missing enabled ** Tags added: network-manager -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: New Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half our to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600
[Touch-packages] [Bug 2055037] Re: My screen radomly starts flickering
There are lots of amdgpu errors in your system log, so let's start there. ** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2055037 Title: My screen radomly starts flickering Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: Hello, I recently installed Ubuntu 22.04.4 on a Lenovo V145-15AST laptop. Randomly, the screen will start flickering. I have found that pulling the power cable out sometimes solves the issue ! But even so, with the power cable out the screen can still start flickering. It's completely random, but very distracting. I am treating this as a bug as I have looked at the options in "Settings > Screen Display" and non of those seem to make any difference. Also I previously tried to install Linux Mint 21.3 and in that case, while booting from the usb stick, I got the welcome to linux mint menu which allows me various options and I select "Start Linux Mint" After that the spinning mint logo appears, then a small mouse pointer on a black screen then the screen goes into some sort of error, a black screen with a few lines at the top. Selecting "Start linux mint in compatability mode" does boot to mint but then the trackpad does not work. I have included this reference to Linux Mint as I believe mint is based on Ubuntu. Many thanks, Nick. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 09:33:11 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:39ec] Subsystem: Lenovo Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [17aa:39ec] InstallationDate: Installed on 2024-02-24 (1 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: LENOVO 81MT ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=e078d5fc-6eaf-4e92-9388-969fa8b6f6db ro 1915.enable_psr=0 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2021 dmi.bios.release: 2.27 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN27WW(V2.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.27 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN27WW(V2.06):bd01/12/2021:br2.27:efr2.27:svnLENOVO:pn81MT:pvrLenovoV145-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2055037/+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 2055105] Re: please merge cron 3.0pl1-184 from debian unstable
** Merge proposal linked: https://code.launchpad.net/~vpa1977/ubuntu/+source/cron/+git/cron/+merge/461317 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/2055105 Title: please merge cron 3.0pl1-184 from debian unstable Status in cron package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/2055105/+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 2055105] [NEW] please merge cron 3.0pl1-184 from debian unstable
Public bug reported: tracking bug ** Affects: cron (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/2055105 Title: please merge cron 3.0pl1-184 from debian unstable Status in cron package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/2055105/+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 2054925] Autopkgtest regression report (debootstrap/1.0.126+nmu1ubuntu0.7)
All autopkgtests for the newly accepted debootstrap (1.0.126+nmu1ubuntu0.7) for jammy have finished running. The following regressions have been reported in tests triggered by the package: debuerreotype/0.14-1 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#debootstrap [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: In Progress Status in debootstrap source package in Jammy: Fix Committed Status in base-files source package in Mantic: New Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mksbuild - pbuilder whatever chroot management tool it has - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2030684] Re: tzname[1] empty after tzset() with env TZ="UTC"
** Also affects: php8.3 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: php8.3 (Ubuntu)
Status: New => Triaged
--
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/2030684
Title:
tzname[1] empty after tzset() with env TZ="UTC"
Status in django-mailman3 package in Ubuntu:
Fix Released
Status in php8.2 package in Ubuntu:
Triaged
Status in php8.3 package in Ubuntu:
Triaged
Status in postgresql-15 package in Ubuntu:
Fix Released
Status in python-django package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata package in Debian:
Fix Released
Bug description:
The following program prints different output when run with tzdata
2023c-7ubuntu1 from mantic, versus tzdata 2023c-8ubuntu1 from mantic-
proposed:
root@mantic:~# cat bug.c
#include
#include
#include
#include
#include
int main(void) {
int r;
r = setenv("TZ", ":UTC", 1);
if (r < 0) {
printf("Failed to set TZ env var: %s\n", strerror(errno));
return 1;
}
tzset();
printf("timezone = %lu, daylight = %d\n", timezone, daylight);
printf("tzname[0] = %s, tzname[1] = %s\n", tzname[0], tzname[1]);
}
root@mantic:~# gcc bug.c
root@mantic:~# ./a.out
timezone = 0, daylight = 0
tzname[0] = UTC, tzname[1] = UTC
root@mantic:~# apt-cache policy tzdata
tzdata:
Installed: 2023c-7ubuntu1
Candidate: 2023c-7ubuntu1
Version table:
*** 2023c-7ubuntu1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
100 /var/lib/dpkg/status
If I install tzdata from mantic-proposed, I get different output:
root@mantic:~# vi /etc/apt/sources.list
root@mantic:~# apt update && apt install tzdata
Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease
Hit:2 http://security.ubuntu.com/ubuntu mantic-security InRelease
Get:3 http://archive.ubuntu.com/ubuntu mantic-proposed InRelease [118 kB]
Hit:4 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
Hit:5 http://archive.ubuntu.com/ubuntu mantic-backports InRelease
Get:6 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages
[35.9 kB]
Get:7 http://archive.ubuntu.com/ubuntu mantic-proposed/main Translation-en
[14.8 kB]
Get:8 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 DEP-11
Metadata [2376 B]
Get:9 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 c-n-f
Metadata [1004 B]
Get:10 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted amd64
Packages [15.9 kB]
Get:11 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted
Translation-en [3564 B]
Get:12 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted amd64
c-n-f Metadata [336 B]
Fetched 192 kB in 1s (324 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
72 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@mantic:~# apt install tzdata=2023c-8ubuntu1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer
required:
libefiboot1 libefivar1
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
tzdata
1 upgraded, 0 newly installed, 0 to remove and 72 not upgraded.
Need to get 269 kB of archives.
After this operation, 142 kB disk space will be freed.
Get:1 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 tzdata all
2023c-8ubuntu1 [269 kB]
Fetched 269 kB in 0s (867 kB/s)
Preconfiguring packages ...
(Reading database ... 39935 files and directories currently installed.)
Preparing to unpack .../tzdata_2023c-8ubuntu1_all.deb ...
Unpacking tzdata (2023c-8ubuntu1) over (2023c-7ubuntu1) ...
Setting up tzdata (2023c-8ubuntu1) ...
Current default time zone: 'Etc/UTC'
Local time is now: Mon Aug 7 21:18:35 UTC 2023.
Universal Time is now: Mon Aug 7 21:18:35 UTC 2023.
Run 'dpkg-reconfigure tzdata' if you wish to change it.
Scanning processes...
Scanning candidates...
Restarting services...
Service restarts being deferred:
systemctl restart systemd-logind.service
systemctl restart unattended-upgrades.service
[Touch-packages] [Bug 1887655] Re: unattended-upgrades triggers reboot despite configuration
Also seeing this issue on 20.04. Same behaviour as above (occurence is
random and the symptoms and log information is the same).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1887655
Title:
unattended-upgrades triggers reboot despite configuration
Status in unattended-upgrades package in Ubuntu:
Confirmed
Bug description:
I've been having problems with my Ubuntu machine suddenly rebooting
without any warning. To my knowledge Ubuntu Desktop is not supposed
to reboot without warning by default.
I believe this is being triggered by unattended-upgrades
unattended-upgrades 2.3 (amd64)
Ubuntu Desktop:
Description: Ubuntu 20.04 LTS
Release: 20.04
One pattern that emerges is that the reboot happens right after
unattended-upgrades completes successfully. There are multiple
examples in my /var/log/syslog, but all show "unattended-
upgrades.service: Succeeded." the same second everything begins to
shut down, with nothing for a minute or two prior. Example:
Jul 15 11:17:01 pc systemd[2065]: Starting Notification regarding a new
release of Ubuntu...
Jul 15 11:17:14 pc charon: 08[IKE] sending keep alive to 10.10.10.10[4500]
Jul 15 11:17:22 pc check-new-release-gtk[71843]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:30: PyGIWarning: Gtk was
imported without specifying a version first. Use gi.require_version('Gtk'
, '3.0') before import to ensure that the right version gets loaded.
Jul 15 11:17:22 pc check-new-release-gtk[71843]: from gi.repository import
Gtk
Jul 15 11:17:22 pc check-new-release-gtk[71843]: WARNING:root:timeout
reached, exiting
Jul 15 11:17:22 pc systemd[2065]: update-notifier-release.service: Succeeded.
Jul 15 11:17:22 pc systemd[2065]: Finished Notification regarding a new
release of Ubuntu.
Jul 15 11:17:48 pc mysql-workbench[33350]: gtk_tree_view_unref_tree_helper:
assertion 'node != NULL' failed
Jul 15 11:17:54 pc charon: 09[IKE] sending keep alive to 10.10.10.10[4500]
Jul 15 11:18:03 pc systemd[1]: unattended-upgrades.service: Succeeded.
Jul 15 11:18:03 pc systemd[1]: Stopping Session 3 of user philip.
Jul 15 11:18:03 pc systemd[1]: Removed slice
system-clean\x2dmount\x2dpoint.slice.
Jul 15 11:18:03 pc systemd[1]: Removed slice system-getty.slice.
Jul 15 11:18:03 pc systemd[1]: Removed slice system-modprobe.slice.
Jul 15 11:18:03 pc systemd[1]: Stopped target Block Device Preparation for
/dev/mapper/ubuntu.
Jul 15 11:18:03 pc systemd[2065]: Stopped target GNOME Wayland Session
(session: gnome).
From memory I've never edited the contents of /etc/apt/apt.conf.d/ and
the configuration for unattended upgrades claims to be default (NOT to
reboot):
$ grep -irnC4 reboot /etc/apt/apt.conf.d/
/etc/apt/apt.conf.d/50unattended-upgrades-88-// Do automatic removal of
unused packages after the upgrade
/etc/apt/apt.conf.d/50unattended-upgrades-89-// (equivalent to apt-get
autoremove)
/etc/apt/apt.conf.d/50unattended-upgrades-90-//Unattended-Upgrade::Remove-Unused-Dependencies
"false";
/etc/apt/apt.conf.d/50unattended-upgrades-91-
/etc/apt/apt.conf.d/50unattended-upgrades:92:// Automatically reboot *WITHOUT
CONFIRMATION* if
/etc/apt/apt.conf.d/50unattended-upgrades:93:// the file
/var/run/reboot-required is found after the upgrade
/etc/apt/apt.conf.d/50unattended-upgrades:94://Unattended-Upgrade::Automatic-Reboot
"false";
/etc/apt/apt.conf.d/50unattended-upgrades-95-
/etc/apt/apt.conf.d/50unattended-upgrades:96:// Automatically reboot even if
there are users currently logged in
/etc/apt/apt.conf.d/50unattended-upgrades:97:// when
Unattended-Upgrade::Automatic-Reboot is set to true
/etc/apt/apt.conf.d/50unattended-upgrades:98://Unattended-Upgrade::Automatic-Reboot-WithUsers
"true";
/etc/apt/apt.conf.d/50unattended-upgrades-99-
/etc/apt/apt.conf.d/50unattended-upgrades:100:// If automatic reboot is
enabled and needed, reboot at the specific
/etc/apt/apt.conf.d/50unattended-upgrades-101-// time instead of immediately
/etc/apt/apt.conf.d/50unattended-upgrades-102-// Default: "now"
/etc/apt/apt.conf.d/50unattended-upgrades:103://Unattended-Upgrade::Automatic-Reboot-Time
"02:00";
/etc/apt/apt.conf.d/50unattended-upgrades-104-
/etc/apt/apt.conf.d/50unattended-upgrades-105-// Use apt bandwidth limit
feature, this example limits the download
/etc/apt/apt.conf.d/50unattended-upgrades-106-// speed to 70kb/sec
/etc/apt/apt.conf.d/50unattended-upgrades-107-//Acquire::http::Dl-Limit "70";
journalctl -u unattended-upgrades
Jul 10 07:52:31 PC systemd[1]: Started Unattended Upgrades Shutdown.
Jul 14 10:03:03 PC systemd[1]: unattended-upgrades.service: Succeeded.
-- Reboot --
Jul 14 10:04:11 PC systemd[1]: Started Unattended Upgrades Shutdown.
Jul 15 11:18:03 PC systemd[1]: unattended-upgrades.service: Succeeded.
[Touch-packages] [Bug 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."
Also, the various packages here have a similar error message but the error is probably caused by different things. This is a generic error message from init-system-helpers. Now, with that said, I agree init-system-helpers should be more verbose when this error happens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2003756 Title: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142." Status in init-system-helpers package in Ubuntu: Triaged Status in krb5 package in Ubuntu: Triaged Bug description: I have a fresh install of Ubuntu Server 22.04.01 LTS. After installing the server and running all updates, I run the following command: apt -y install slapd ldap-utils schema2ldif sasl2-bin libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc This will be installing krb5-kdc 1.19.2-2. This is in preparation for setting up an OpenLDAP server, a Kerberos server with an LDAP backend, and saslauthd for pass-through authentication. krb5-kdc was auto-selected when running the steps in the guide here in my development environment: https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend When installing that, I get the following in the output: Setting up krb5-kdc (1.19.2-2) ... Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service → /lib/systemd/system/krb5-kdc.service. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I do get the prompts for the realm, kdc, and admin server hostnames, and they are reflected in /etc/krb5.conf. If I then run the following: dpkg-reconfigure krb5-kdc I am prompted for whether I want the package to create the Kerberos KDC configuration automatically, and when I say yes, it then repeats the following error: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I cannot find any further debug in the syslog or anything to indicate what the root cause is; the list of packages here are all installed together on a separate development server where I experimented with the configuration I will be deploying here in production so I don't think it's incompatible packages in the install list, but I am open to feedback on that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."
netvicious or Dan, do you have the AMI that you used to produce that error with proftpd-core? I also tried reproduction on ami-0dffe9017aa8424a2 in eu-north-1 and was not able to reproduce that failure. I just booted a fresh t3.micro instance with the above AMI, then proceeded to run `apt update -y && apt install -y proftpd`. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/2003756 Title: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142." Status in init-system-helpers package in Ubuntu: Triaged Status in krb5 package in Ubuntu: Triaged Bug description: I have a fresh install of Ubuntu Server 22.04.01 LTS. After installing the server and running all updates, I run the following command: apt -y install slapd ldap-utils schema2ldif sasl2-bin libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc This will be installing krb5-kdc 1.19.2-2. This is in preparation for setting up an OpenLDAP server, a Kerberos server with an LDAP backend, and saslauthd for pass-through authentication. krb5-kdc was auto-selected when running the steps in the guide here in my development environment: https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend When installing that, I get the following in the output: Setting up krb5-kdc (1.19.2-2) ... Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service → /lib/systemd/system/krb5-kdc.service. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I do get the prompts for the realm, kdc, and admin server hostnames, and they are reflected in /etc/krb5.conf. If I then run the following: dpkg-reconfigure krb5-kdc I am prompted for whether I want the package to create the Kerberos KDC configuration automatically, and when I say yes, it then repeats the following error: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. I cannot find any further debug in the syslog or anything to indicate what the root cause is; the list of packages here are all installed together on a separate development server where I experimented with the configuration I will be deploying here in production so I don't think it's incompatible packages in the install list, but I am open to feedback on that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2054924] Re: color emoji are broken with fontconfig 2.15
The workaround detailed upstream works for me - removing /etc/fonts/conf.d/70-no-bitmaps.conf and re-generating your fonts cache. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2054924 Title: color emoji are broken with fontconfig 2.15 Status in Fontconfig: Fix Released Status in fontconfig package in Ubuntu: Triaged Status in fonts-noto-color-emoji package in Ubuntu: Triaged Status in fontconfig package in Debian: New Bug description: The Noto Color Emoji font is no longer used to show emoji. Many emoji no longer show and the few that do are not in color. To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/2054924/+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 2053207] Re: glib requires gobject-introspection >= 1.78.1-13
** Changed in: glib2.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/2053207 Title: glib requires gobject-introspection >= 1.78.1-13 Status in glib2.0 package in Ubuntu: Fix Released Status in gobject-introspection package in Ubuntu: Fix Released Bug description: glib2.0 2.79.1-1 requires gobject-introspection >= 1.78.13 to migrate out of noble-proposed before or at the same as glib2.0. I'm filing this bug to explain why glib2.0 isn't migrating despite the excuses page saying "Will attempt migration" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+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 2052295] Re: autopkgtest unshare-qemuwrapper failing on amd64
This has been fixed in sbuild 0.85.6 via https://salsa.debian.org/debian/sbuild/-/merge_requests/57 ** Changed in: sbuild (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cpio in Ubuntu. https://bugs.launchpad.net/bugs/2052295 Title: autopkgtest unshare-qemuwrapper failing on amd64 Status in cpio package in Ubuntu: Fix Released Status in sbuild package in Ubuntu: Fix Released Status in cpio source package in Noble: Fix Released Status in sbuild source package in Noble: Fix Released Status in cpio package in Debian: Fix Released Bug description: While watching Noble openssh migration, I saw this test failing and marking amd64 as regression. Log : https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- noble/noble/amd64/s/sbuild/20240201_000224_2a4c6@/log.gz Relevant part of the log: 1565s Chrooting into /tmp/mmdebstrap.bsT6cbiWIs/ 1565s Setting up cpio (2.15+dfsg-1) ... 1565s update-alternatives: error: alternative path /bin/mt-gnu doesn't exist 1565s dpkg: error processing package cpio (--configure): 1565s installed cpio package post-installation script subprocess returned error exit status 2 It can be reproduced locally, too. The most recent test working is from 01/08/2024: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/s/sbuild/20240108_203545_af566@/log.gz The cpio version in the immediately log above is lower. The same (working) part is: 2188s Chrooting into /tmp/mmdebstrap.qSEp1fU8f3/ 2188s Setting up cpio (2.14+dfsg-1) ... 2188s update-alternatives: using /bin/mt-gnu to provide /bin/mt (mt) in auto mode cpio diff : https://launchpadlibrarian.net/709448424/cpio_2.14+dfsg-1_2.15+dfsg-1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/2052295/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
This bug was fixed in the package ghostwriter - 23.08.5+ds-0ubuntu1 --- ghostwriter (23.08.5+ds-0ubuntu1) noble; urgency=medium * New upstream release (23.08.5) ghostwriter (23.08.4+ds-0ubuntu2) noble; urgency=medium * Add apparmor profile to fix userns. (LP: #2046844) -- Scarlett Moore Thu, 22 Feb 2024 09:31:12 -0700 ** Changed in: ghostwriter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2052318] Re: pycountry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned exit code 13
** Changed in: pycountry (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iso-codes in Ubuntu.
https://bugs.launchpad.net/bugs/2052318
Title:
pycountry: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.12 3.11" returned exit code 13
Status in iso-codes package in Ubuntu:
Fix Released
Status in pycountry package in Ubuntu:
Fix Released
Status in pycountry package in Debian:
Fix Released
Bug description:
Imported from Debian bug http://bugs.debian.org/1060934:
Source: pycountry
Version: 23.12.11+ds1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # The data provided by the iso-codes package is not within this
> # source package; reassemble the sources
> # poetry insists on real files not strange out-of-module symlinks when
> # building, but we want to end up with symlinks back to iso-codes
> # in the package
> echo "# AUTOGENERATED FROM d/rules" >> debian/links
> # json databases
> mkdir -p src/pycountry/databases
> for f in /usr/share/iso-codes/json/iso*; do \
> src="$f"; \
> part=`echo "$f" | sed s@/usr/share/iso-codes/json/@@ | tr -d _`; \
> srcdest=src/pycountry/databases/"$part"; \
> debdest=usr/lib/python3/dist-packages/pycountry/databases/"$part"; \
> cp "$src" "$srcdest"; \
> echo "$src" "$debdest" >> debian/links; \
> done
> # locales data
> mkdir -p src/pycountry/locales
> dpkg -L iso-codes | \
> grep /usr/share/locale/ | \
> xargs dirname | \
> uniq | \
> sed "s@/usr/share/locale/@@" | \
> xargs -I{} -n1 mkdir -p src/pycountry/locales/{}
> for f in `dpkg -L iso-codes | grep /usr/share/locale/`; do \
> if [ -f "$f" ]; then \
> src="$f"; \
> part=`echo "$f" | sed "s@/usr/share/locale/@@;s@iso_@iso@"`; \
> srcdest=src/pycountry/locales/"$part"; \
> debdest=/usr/lib/python3/dist-packages/pycountry/locales/"$part"; \
> cp "$src" "$srcdest"; \
> echo "$src" "$debdest" >> debian/links; \
> fi; \
> done
> echo "RECONSTRUCTED PACKAGE:"
> RECONSTRUCTED PACKAGE:
> find src/pycountry
> src/pycountry
> src/pycountry/db.py
> src/pycountry/__init__.py
> src/pycountry/tests
> src/pycountry/tests/test_general.py
> src/pycountry/databases
> src/pycountry/databases/iso3166-2.json
> src/pycountry/databases/iso15924.json
> src/pycountry/databases/iso3166-1.json
> src/pycountry/databases/iso639-5.json
> src/pycountry/databases/iso639-3.json
> src/pycountry/databases/iso3166-3.json
> src/pycountry/databases/iso639-2.json
> src/pycountry/databases/iso4217.json
> src/pycountry/py.typed
> src/pycountry/locales
> src/pycountry/locales/wa
> src/pycountry/locales/wa/LC_MESSAGES
> src/pycountry/locales/wa/LC_MESSAGES/iso3166-1.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso3166.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso639-2.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso3166-2.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso639-3.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso639.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso3166-3.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso639_3.mo
> src/pycountry/locales/wa/LC_MESSAGES/iso3166_2.mo
> src/pycountry/locales/chr
> src/pycountry/locales/chr/LC_MESSAGES
> src/pycountry/locales/chr/LC_MESSAGES/iso3166-1.mo
> src/pycountry/locales/chr/LC_MESSAGES/iso3166.mo
> src/pycountry/locales/gv
> src/pycountry/locales/gv/LC_MESSAGES
> src/pycountry/locales/gv/LC_MESSAGES/iso3166-1.mo
> src/pycountry/locales/gv/LC_MESSAGES/iso3166.mo
> src/pycountry/locales/en
> src/pycountry/locales/en/LC_MESSAGES
> src/pycountry/locales/en/LC_MESSAGES/iso3166-2.mo
> src/pycountry/locales/en/LC_MESSAGES/iso3166_2.mo
> src/pycountry/locales/ka
> src/pycountry/locales/ka/LC_MESSAGES
> src/pycountry/locales/ka/LC_MESSAGES/iso3166-1.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso4217.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639-5.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso3166.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639-2.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso3166-2.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639-3.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639_5.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso15924.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso3166-3.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso639_3.mo
> src/pycountry/locales/ka/LC_MESSAGES/iso3166_2.mo
> src/pycountry/locales/tt@iqtelif
> src/pycountry/locales/tt@iqtelif/LC_MESSAGES
> src/pycountry/locales/tt@iqtelif/LC_MESSAGES/iso3166-1.mo
>
[Touch-packages] [Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
Hello Åka, or anyone else affected, Accepted debootstrap into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debootstrap/1.0.126+nmu1ubuntu0.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: debootstrap (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: In Progress Status in debootstrap source package in Jammy: Fix Committed Status in base-files source package in Mantic: New Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mksbuild - pbuilder whatever chroot management tool it has - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
I confirmed that the resulting target dir of debootstrap in Jammy (with patch/MERGED_USR=no) and Mantic is the same, with a comparison of `ls -lR` (normalized for Month/Day/Time fields). ... Test command for Jammy (patched) and Mantic: # debootstrap --arch=amd64 --variant=minbase --keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg noble /tmp/nobletest http://archive.ubuntu.com/ubuntu Dir listing for Jammy (patched) and Mantic: deboostrap-jammy # ls -lR /tmp/nobletest/ > list.jammy deboostrap-mantic # ls -lR /tmp/nobletest/ > list.mantic Normalization and comparison: $ sed -i 's/[A-Z][a-z][a-z] .[0-9] [0-9][0-9]:[0-9][0-9]/DATETIME/' list.jammy list.mantic $ diff -U0 list.jammy list.mantic --- list.jammy 2024-02-26 19:39:49.102864808 -0300 +++ list.mantic 2024-02-26 19:39:49.114864569 -0300 @@ -76 +76 @@ --rw-r--r-- 1 root root 18 DATETIME hostname +-rw-r--r-- 1 root root 19 DATETIME hostname @@ -7093 +7093 @@ --rw-r--r-- 1 root root 60238 DATETIME bootstrap.log +-rw-r--r-- 1 root root 60045 DATETIME bootstrap.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: In Progress Status in debootstrap source package in Jammy: In Progress Status in base-files source package in Mantic: New Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mksbuild - pbuilder whatever chroot management tool it has - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
Slrry I can make this clearer too by adding a mantic task and marking it as fix released. ** Also affects: base-files (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: debootstrap (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: debootstrap (Ubuntu Mantic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: In Progress Status in debootstrap source package in Jammy: In Progress Status in base-files source package in Mantic: New Status in debootstrap source package in Mantic: Fix Released Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mksbuild - pbuilder whatever chroot management tool it has - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
TL;DR: The fix is not needed on Mantic.
This is just to expand a bit on the brief note in '[Where problems could
occur]' ("moved to merging post-extraction"), for clarity.
The code in `scripts/gutsy` (used for noble) is different between Mantic
and Jammy with regards to the order of package extraction and usr-merge
setup, in first_stage_install().
The issue happens in Jammy because usr-merge setup runs _before_
extraction (thus extraction of base-files fails as the
/{bin,lib,lib64,sbin} symlinks already exist):
setup_merged_usr
extract $required
But it doesn't happen in Mantic because usr-merge setup runs _after_
extraction (thus extraction of base-files works as the symlinks don't
yet exist):
extract $required
merge_usr
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/2054925
Title:
Debootstrap fails for Noble with base-files 13ubuntu7
Status in base-files package in Ubuntu:
Won't Fix
Status in debootstrap package in Ubuntu:
Fix Released
Status in debootstrap source package in Focal:
In Progress
Status in debootstrap source package in Jammy:
In Progress
Bug description:
[Impact]
The last couple of days, I have been unable to run a successful debootstrap
for Noble Numbat.
Apparently this is caused by the addition of symlinks (/bin, /lib,
/lib64 and /sbin) in base-files 13ubuntu7. According to
debootstrap.log, it fails to extract said symlinks because they
already exist at that point.
This can be reproduced on build hosts running Jammy Jellyfish against
any up-to-date Ubuntu public archive mirror as of today.
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
# apt-cache policy debootstrap
debootstrap:
Installed: 1.0.126+nmu1ubuntu0.5
Candidate: 1.0.126+nmu1ubuntu0.5
Version table:
*** 1.0.126+nmu1ubuntu0.5 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
100 /var/lib/dpkg/status
1.0.126+nmu1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
Attached shell output of two runs of debootstrap. First run uses
mirror archive.ubuntu.com (which as of this report serves base-files
version 13ubuntu7), and second run uses a local custom mirror (which
serves base-files 13ubuntu6). First run fails, second run succeeds.
[Test plan]
Successfully for each of focal, jammy, mantic, noble
- debootstrap
- mksbuild
- pbuilder whatever chroot management tool it has
- ubuntu-image, if we can pull debootstrap from proposed for this
as well as
- debootstrap noble --merged-usr
[Where problems could occur]
We do not anticipate any regressions as we replace the previous *) case for
usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the
new solution will only impact noble and onward.
That said, this is a different approach than mantic and newer take,
and a different approach than Debian takes, where they moved to
merging post-extraction, even in stable releases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
The iso from today, Ubuntu-MATE 24.04 LTS "Noble Numbat" - Daily amd64 (20240226) has just installed perfectly in KVM with no problem booting to a full GUI. It seems that the arctica-greeter difficulty has been overcome. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: Invalid Status in lightdm package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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 2055088] Re: debian/control incorrectly installs gnome-session dependencies in ubuntu-budgie
** Merge proposal linked: https://code.launchpad.net/~fossfreedom/ubuntu/+source/software-properties/+git/software-properties/+merge/461293 -- 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/2055088 Title: debian/control incorrectly installs gnome-session dependencies in ubuntu-budgie Status in software-properties package in Ubuntu: New Bug description: d/control is used on the official gtk desktops such as budgie. budgie-desktop for noble now uses budgie-session instead of gnome- session. software-properties needs an update to its dependency list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2055088/+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 2055088] [NEW] debian/control incorrectly installs gnome-session dependencies in ubuntu-budgie
Public bug reported: d/control is used on the official gtk desktops such as budgie. budgie-desktop for noble now uses budgie-session instead of gnome- session. software-properties needs an update to its dependency list ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: noble ** Tags added: noble -- 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/2055088 Title: debian/control incorrectly installs gnome-session dependencies in ubuntu-budgie Status in software-properties package in Ubuntu: New Bug description: d/control is used on the official gtk desktops such as budgie. budgie-desktop for noble now uses budgie-session instead of gnome- session. software-properties needs an update to its dependency list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2055088/+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 2055055] Re: unmkinitramfs: wrong and unneeded count= in a dd call
The attachment "dd-count.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2055055 Title: unmkinitramfs: wrong and unneeded count= in a dd call Status in initramfs-tools package in Ubuntu: New Bug description: Speaking about this line in unmkinitramfs: 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes 2> /dev/null | dd's block size is 512 by default. iflag=skip_bytes does not change that. Both $end and $start are byte-offsets. Hence the count is ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. Anyways, the script just works because the count is unneeded: dd's output is piped into cpio which stops on the first end-of-archive marker, no matter how much data it is fed with. I think it is the best to just drop the count option (the patch is attached). If there is still a need to explicitly limit data fed to cpio, dd is impractical in this case. The only way to count= in bytes is bs=1, which makes dd extremely slow on lengthy data chunks. For example ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded uncompressed cpio archives of such sizes: 77312 7200768 78615040 A combo of dd+head could be used intead to skip and count respectively: 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | head -c$((end - start)) | Or even tail+head: 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) | To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+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 2055065] [NEW] Please merge kbd 2.6.4-2 (main) from Debian unstable
Public bug reported: TODO ** Affects: kbd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/2055065 Title: Please merge kbd 2.6.4-2 (main) from Debian unstable Status in kbd package in Ubuntu: New Bug description: TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/2055065/+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 2049555] Re: [SOF - sof-bytcht rt5640, playback] fails after a while
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/2049555 Title: [SOF - sof-bytcht rt5640, playback] fails after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: Playing music or watching videos for couple minutes, like on Youtube. Sound will be cracked with long beep. And player will be stopped. But if I reload the page, sound will be resumed again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 16 22:44:25 2024 InstallationDate: Installed on 2024-01-14 (1 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller - Intel HDMI/DP LPE Audio Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [SOF - sof-bytcht rt5640, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Gummi CHT dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd11/20/2015:br1.10:svnAcer:pnAspireSW3-016P:pvrV1.10:rvnAcer:rnGummiCHT:rvrV1.10:cvnAcer:ct9:cvrChassisVersion:skuAspireSwitch10E_106E_1.10: dmi.product.family: CHT-CR dmi.product.name: Aspire SW3-016P dmi.product.sku: Aspire Switch 10 E_106E_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2049555/+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 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
Thanks for the update, Matthew. We're looking forward to getting this fix from Ubuntu. My team patched our version the e2fsprogs package from Focal about a year ago, before we submitted the fix upstream. Since that patch, we haven't had any re-occurrences of the problem. It used to show up about 4-5 times a day for us. Glad that the fix is working in your tests as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: In Progress Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: In Progress Status in e2fsprogs source package in Jammy: In Progress Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: In Progress Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2055055] Re: unmkinitramfs: wrong and unneeded count= in a dd call
Just found out, aside for skip_bytes iflag, there is also count_bytes one. So another fix count be: 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes,count_bytes 2> /dev/null | ** Description changed: Speaking about this line in unmkinitramfs: - 113: dd < "$initramfs" skip=$start count=$((end - start)) + 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes 2> /dev/null | - - dd's block size is 512 by default. iflag=skip_bytes does not change that. Both $end and $start are byte-offsets. Hence the count is ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. + dd's block size is 512 by default. iflag=skip_bytes does not change + that. Both $end and $start are byte-offsets. Hence the count is + ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. Anyways, the script just works because the count is unneeded: dd's output is piped into cpio which stops on the first end-of-archive marker, no matter how much data it is fed with. I think it is the best to just drop the count option (the patch is attached). + If there is still a need to explicitly limit data fed to cpio, dd is + impractical in this case. The only way to count= in bytes is bs=1, which + makes dd extremely slow on lengthy data chunks. For example + ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded + uncompressed cpio archives of such sizes: - If there is still a need to explicitly limit data fed to cpio, dd is impractical in this case. The only way to count= in bytes is bs=1, which makes dd extremely slow on lengthy data chunks. For example ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded uncompressed cpio archives of such sizes: - - 77312 - 7200768 - 78615040 + 77312 + 7200768 + 78615040 A combo of dd+head could be used intead to skip and count respectively: - 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | - head -c$((end - start)) + 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | + head -c$((end - start)) | Or even tail+head: - 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) + 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) | -- 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/2055055 Title: unmkinitramfs: wrong and unneeded count= in a dd call Status in initramfs-tools package in Ubuntu: New Bug description: Speaking about this line in unmkinitramfs: 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes 2> /dev/null | dd's block size is 512 by default. iflag=skip_bytes does not change that. Both $end and $start are byte-offsets. Hence the count is ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. Anyways, the script just works because the count is unneeded: dd's output is piped into cpio which stops on the first end-of-archive marker, no matter how much data it is fed with. I think it is the best to just drop the count option (the patch is attached). If there is still a need to explicitly limit data fed to cpio, dd is impractical in this case. The only way to count= in bytes is bs=1, which makes dd extremely slow on lengthy data chunks. For example ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded uncompressed cpio archives of such sizes: 77312 7200768 78615040 A combo of dd+head could be used intead to skip and count respectively: 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | head -c$((end - start)) | Or even tail+head: 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) | To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+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 2055054] Re: package udev 249.11-0ubuntu3.12 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
** Package changed: ubuntu => systemd (Ubuntu) ** Tags removed: need-duplicate-check -- 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/2055054 Title: package udev 249.11-0ubuntu3.12 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Following this problem, the computer can still be used. However, after the lock screen goes into effect due to inactivity, the following attempt to login fails. After entering the system password, the screen just sits there and no login occurs. The only way to get out of this situation is to powerdown the computer which creates other problems with files that had remained opened. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.15.0-97.107-generic 5.15.136 Uname: Linux 5.15.0-97-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.snapd-desktop-integration.rules 70-snap.quadrapassel.rules 70-snap.tetris.rules 70-snap.gimp.rules 70-snap.gnome-calculator.rules 70-snap.firefox.rules 70-snap.snap-store.rules 70-snap.core.rules 70-snap.freecell-solitaire.rules 70-snap.warble.rules Date: Sun Feb 25 17:49:07 2024 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-12-01 (1548 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: systemd Title: package udev 249.11-0ubuntu3.12 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-22 (552 days ago) dmi.bios.date: 10/03/2013 dmi.bios.release: 15.41 dmi.bios.vendor: Insyde dmi.bios.version: F.29 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181D dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 52.24 dmi.modalias: dmi:bvnInsyde:bvrF.29:bd10/03/2013:br15.41:efr52.24:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr078F1020572620100:rvnHewlett-Packard:rn181D:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:skuA3F79AV: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.sku: A3F79AV dmi.product.version: 078F1020572620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055054/+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 2055055] [NEW] unmkinitramfs: wrong and unneeded count= in a dd call
Public bug reported: Speaking about this line in unmkinitramfs: 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes 2> /dev/null | dd's block size is 512 by default. iflag=skip_bytes does not change that. Both $end and $start are byte-offsets. Hence the count is ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. Anyways, the script just works because the count is unneeded: dd's output is piped into cpio which stops on the first end-of-archive marker, no matter how much data it is fed with. I think it is the best to just drop the count option (the patch is attached). If there is still a need to explicitly limit data fed to cpio, dd is impractical in this case. The only way to count= in bytes is bs=1, which makes dd extremely slow on lengthy data chunks. For example ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded uncompressed cpio archives of such sizes: 77312 7200768 78615040 A combo of dd+head could be used intead to skip and count respectively: 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | head -c$((end - start)) Or even tail+head: 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Patch added: "dd-count.patch" https://bugs.launchpad.net/bugs/2055055/+attachment/5749511/+files/dd-count.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2055055 Title: unmkinitramfs: wrong and unneeded count= in a dd call Status in initramfs-tools package in Ubuntu: New Bug description: Speaking about this line in unmkinitramfs: 113: dd < "$initramfs" skip=$start count=$((end - start)) iflag=skip_bytes 2> /dev/null | dd's block size is 512 by default. iflag=skip_bytes does not change that. Both $end and $start are byte-offsets. Hence the count is ($end-$start) blocks or ($end-$start)*512 bytes which is wrong. Anyways, the script just works because the count is unneeded: dd's output is piped into cpio which stops on the first end-of-archive marker, no matter how much data it is fed with. I think it is the best to just drop the count option (the patch is attached). If there is still a need to explicitly limit data fed to cpio, dd is impractical in this case. The only way to count= in bytes is bs=1, which makes dd extremely slow on lengthy data chunks. For example ubuntu-23.10.1-desktop-amd64.iso contains initrd with embedded uncompressed cpio archives of such sizes: 77312 7200768 78615040 A combo of dd+head could be used intead to skip and count respectively: 113: dd < "$initramfs" skip=$start iflag=skip_bytes 2> /dev/null | head -c$((end - start)) Or even tail+head: 113: tail -c+$((start+1)) "$initramfs" | head -c$((end - start)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2055055/+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 2036127] Re: Restarting `systemd-networkd` looses unmanaged bridged parents
@enr0n, yes, I did restart systemd-networkd after creating /etc/systemd/network/10-netplan-vlan1.network.d/keep_master.conf. If you want to reproduce, the steps outlined in the bug descriptions should provide you with a simple reproducer. -- 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/2036127 Title: Restarting `systemd-networkd` looses unmanaged bridged parents Status in systemd package in Ubuntu: Invalid Bug description: My home network comprises many VLANs managed by `systemd- networkd`/`netplan`. Those VLANs are then used as parent interfaces for LXD networks. Whenever `systemd-networkd` is restarted (i.e: post- update), my whole network breaks because all the unmanaged bridges lose their parent devices. Another way to see it is that `systemd- networkd` undoes the `master` setting of those VLAN devices. Here is a simplified reproducer: 1. Create a `vlan1` device $ lxc launch ubuntu:22.04 networkd-bug Creating networkd-bug Starting networkd-bug $ lxc file push - networkd-bug/etc/netplan/99-vlan1.yaml << EOF network: version: 2 vlans: vlan1: id: 1 link: eth0 EOF $ lxc exec networkd-bug -- netplan apply 2. Manually create a bridge and join `vlan1` to it $ lxc exec networkd-bug -- ip link add br0 type bridge $ lxc exec networkd-bug -- ip link set vlan1 master br0 $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 3. Restart `systemd-networkd` $ lxc exec networkd-bug -- systemctl restart systemd-networkd 4. Notice `vlan1` lost it's master config $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 Ideally, `vlan1` should retain it's `master` setting and I wouldn't loose connectivity :) Additional information: # apt-cache policy systemd netplan.io iproute2 systemd: Installed: 249.11-0ubuntu3.9 Candidate: 249.11-0ubuntu3.9 Version table: *** 249.11-0ubuntu3.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 249.11-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages netplan.io: Installed: 0.105-0ubuntu2~22.04.3 Candidate: 0.105-0ubuntu2~22.04.3 Version table: *** 0.105-0ubuntu2~22.04.3 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.104-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages iproute2: Installed: 5.15.0-1ubuntu2 Candidate: 5.15.0-1ubuntu2 Version table: *** 5.15.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status # lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 # uname -a Linux networkd-bug 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036127/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
** Description changed: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] - Successfully - - debootstrap focal - - debootstrap jammy - - debootstrap mantic - - debootstrap noble + Successfully for each of focal, jammy, mantic, noble + - debootstrap + - mksbuild + - pbuilder whatever chroot management tool it has + - ubuntu-image, if we can pull debootstrap from proposed for this + + as well as + - debootstrap noble --merged-usr - both in buildd and normal variant, also specifically for noble, - --merged-usr should be ignored. [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: In Progress Status in debootstrap source package in Jammy: In Progress Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully for each of focal, jammy, mantic, noble - debootstrap - mksbuild - pbuilder whatever chroot management tool it has - ubuntu-image, if we can pull debootstrap from proposed for this as well as - debootstrap noble --merged-usr [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging
[Touch-packages] [Bug 2055054] [NEW] package udev 249.11-0ubuntu3.12 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
You have been subscribed to a public bug: Following this problem, the computer can still be used. However, after the lock screen goes into effect due to inactivity, the following attempt to login fails. After entering the system password, the screen just sits there and no login occurs. The only way to get out of this situation is to powerdown the computer which creates other problems with files that had remained opened. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.15.0-97.107-generic 5.15.136 Uname: Linux 5.15.0-97-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.snapd-desktop-integration.rules 70-snap.quadrapassel.rules 70-snap.tetris.rules 70-snap.gimp.rules 70-snap.gnome-calculator.rules 70-snap.firefox.rules 70-snap.snap-store.rules 70-snap.core.rules 70-snap.freecell-solitaire.rules 70-snap.warble.rules Date: Sun Feb 25 17:49:07 2024 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-12-01 (1548 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: systemd Title: package udev 249.11-0ubuntu3.12 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-22 (552 days ago) dmi.bios.date: 10/03/2013 dmi.bios.release: 15.41 dmi.bios.vendor: Insyde dmi.bios.version: F.29 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181D dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 52.24 dmi.modalias: dmi:bvnInsyde:bvrF.29:bd10/03/2013:br15.41:efr52.24:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr078F1020572620100:rvnHewlett-Packard:rn181D:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion:skuA3F79AV: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.sku: A3F79AV dmi.product.version: 078F1020572620100 dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- package udev 249.11-0ubuntu3.12 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 https://bugs.launchpad.net/bugs/2055054 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823171] Re: systemd-resolve hides DS records in explicit queries
** Changed in: systemd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1823171 Title: systemd-resolve hides DS records in explicit queries Status in systemd package in Ubuntu: New Bug description: When querying for DS resource records on a DNSSEC signed domain using dig, the DS records are not shown when the system is using systemd- resolve. Run: dig +short DS ripe.net Expected: something like 40991 8 2 D8D3C88263D58930A8B5FE16427130AB84CA73A4988385B2F4B121A7 2E5299A6 Actual result: no output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.15 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 4 14:14:06 2019 MachineType: MSI MS-7A70 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=/dev/mapper/system-slash ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.80 dmi.board.asset.tag: Default string dmi.board.name: B250M PRO-VDH (MS-7A70) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd07/03/2018:svnMSI:pnMS-7A70:pvr2.0:rvnMSI:rnB250MPRO-VDH(MS-7A70):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7A70 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823171/+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 2036127] Re: Restarting `systemd-networkd` looses unmanaged bridged parents
This path is wrong: /etc/systemd/network/99-netplan- vlan1.network.d/keep_master.conf. It should in fact be etc/systemd/network/10-netplan-vlan1.network.d/keep_master.conf. Did you restart systemd-networkd afterward? -- 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/2036127 Title: Restarting `systemd-networkd` looses unmanaged bridged parents Status in systemd package in Ubuntu: Invalid Bug description: My home network comprises many VLANs managed by `systemd- networkd`/`netplan`. Those VLANs are then used as parent interfaces for LXD networks. Whenever `systemd-networkd` is restarted (i.e: post- update), my whole network breaks because all the unmanaged bridges lose their parent devices. Another way to see it is that `systemd- networkd` undoes the `master` setting of those VLAN devices. Here is a simplified reproducer: 1. Create a `vlan1` device $ lxc launch ubuntu:22.04 networkd-bug Creating networkd-bug Starting networkd-bug $ lxc file push - networkd-bug/etc/netplan/99-vlan1.yaml << EOF network: version: 2 vlans: vlan1: id: 1 link: eth0 EOF $ lxc exec networkd-bug -- netplan apply 2. Manually create a bridge and join `vlan1` to it $ lxc exec networkd-bug -- ip link add br0 type bridge $ lxc exec networkd-bug -- ip link set vlan1 master br0 $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 3. Restart `systemd-networkd` $ lxc exec networkd-bug -- systemctl restart systemd-networkd 4. Notice `vlan1` lost it's master config $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 Ideally, `vlan1` should retain it's `master` setting and I wouldn't loose connectivity :) Additional information: # apt-cache policy systemd netplan.io iproute2 systemd: Installed: 249.11-0ubuntu3.9 Candidate: 249.11-0ubuntu3.9 Version table: *** 249.11-0ubuntu3.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 249.11-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages netplan.io: Installed: 0.105-0ubuntu2~22.04.3 Candidate: 0.105-0ubuntu2~22.04.3 Version table: *** 0.105-0ubuntu2~22.04.3 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.104-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages iproute2: Installed: 5.15.0-1ubuntu2 Candidate: 5.15.0-1ubuntu2 Version table: *** 5.15.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status # lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 # uname -a Linux networkd-bug 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036127/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Merge proposal linked: https://code.launchpad.net/~p-pisati/britney/+git/hints-ubuntu/+merge/461043 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Committed Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
** Changed in: debootstrap (Ubuntu Focal) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: In Progress Status in debootstrap source package in Jammy: In Progress Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully - debootstrap focal - debootstrap jammy - debootstrap mantic - debootstrap noble - debootstrap noble --merged-usr both in buildd and normal variant, also specifically for noble, --merged-usr should be ignored. [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2054916]
Thanks for taking the time to report this bug and helping to make Ubuntu better. Since the package referred to in this bug is in universe or multiverse, it is community maintained. If you are able, I suggest coordinating with upstream and posting a debdiff for this issue. When a debdiff is available, members of the security team will review it and publish the package. See the following link for more information: https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures ** Tags added: community-security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2054916 Title: CVE-2022-44640 affects the version of heimdal on ubuntu 22.04 - could it be updated? Status in heimdal package in Ubuntu: Triaged Bug description: I am running ubuntu 22.04. The version of heimdal installed (7.7.0) is vunerable to CVE-2022-44640, which is categorised as critical by some (crowdstrike falcon at least). Is is possible to upgrade it to some non-vulnerable version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2054916/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: Triaged Status in debootstrap source package in Jammy: In Progress Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully - debootstrap focal - debootstrap jammy - debootstrap mantic - debootstrap noble - debootstrap noble --merged-usr both in buildd and normal variant, also specifically for noble, --merged-usr should be ignored. [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2054681] Re: Merge console-setup (1.226) from Debian
A ppa build is available in ppa:xypron/console-setup. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/2054681 Title: Merge console-setup (1.226) from Debian Status in console-setup package in Ubuntu: New Bug description: In Debian console-setup (1.226) is available. It should be merged into Noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2054681/+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 2054681] Re: Merge console-setup (1.226) from Debian
Merge request https://code.launchpad.net/~xypron/ubuntu/+source/console-setup/+git/console-setup/+merge/461248 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/2054681 Title: Merge console-setup (1.226) from Debian Status in console-setup package in Ubuntu: New Bug description: In Debian console-setup (1.226) is available. It should be merged into Noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2054681/+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 2054916] Re: CVE-2022-44640 affects the version of heimdal on ubuntu 22.04 - could it be updated?
In Debian, this was fixed in 7.7.0+dfsg-2+deb11u1 in bullseye(-security) - i.e., 7.7.0+dfsg-2 was still affeected. 7.7.0+dfsg-3 includes a fix for a different CVE: heimdal (7.7.0+dfsg-3) unstable; urgency=high * Fix CVE-2021-3671: A null pointer de-reference was found in the way samba kerberos server handled missing sname in TGS-REQ. Closes: #996586. * Fix autoconf 2.7 issues In focal, this was fixed in 7.7.0+dfsg-1ubuntu1.3 on Wed, 11 Jan 2023 * SECURITY UPDATE: invalid free - debian/patches/CVE-2022-44640.patch: relocates a call to fprintf and parameters when calling it in decode_type() in lib/asn1/gen_decode.c and add a call to fprintf in free_type() in lib/asn1/gen_free.c. - CVE-2022-44640 In jammy, we have 7.7.0+dfsg-3ubuntu1. As mentioned above, 7.7.0+dfsg-3 does not include the fix for the mentioned CVE. Moreover, our delta in this release is just former delta being carried by the merge: heimdal (7.7.0+dfsg-3ubuntu1) jammy; urgency=medium * Merge with Debian unstable (LP: #1946860). Remaining changes: - Disable lto, to regain dep on roken, otherwise dependencies on amd64 are different to i386 resulting in different files on amd64 and i386. LP #1934936 - Remove symbol rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 (LP #1945787) Therefore, this does seem to still be affected by the CVE, as reported. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3671 ** Changed in: heimdal (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2054916 Title: CVE-2022-44640 affects the version of heimdal on ubuntu 22.04 - could it be updated? Status in heimdal package in Ubuntu: Triaged Bug description: I am running ubuntu 22.04. The version of heimdal installed (7.7.0) is vunerable to CVE-2022-44640, which is categorised as critical by some (crowdstrike falcon at least). Is is possible to upgrade it to some non-vulnerable version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2054916/+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 2023322]
Bug driver 470, Nvidia GTX 650 W dniu 26.02.2024 o 04:06, Craig pisze: > (In reply to Michael Catanzaro from comment #62) >> Hi Craig and Thomas (and Emil if you're still around): if you're still >> encountering problems with NVIDIA graphics, please report new a bug and >> leave a comment here linking to the new bug. > My problem was on legacy nvidia driver, and newer versions wouldn't even > start. But I now know a workaround (GSK_RENDERER=cairo) and don't expect > there will be a fix for my old driver anyway. > https://gitlab.gnome.org/GNOME/gtk/-/issues/5858 > ** Attachment added: "Zrzut ekranu z 2024-02-26 14-51-55.png" https://bugs.launchpad.net/bugs/2023322/+attachment/5749476/+files/Zrzut%20ekranu%20z%202024-02-26%0A%2014-51-55.png ** Attachment added: "Zrzut ekranu z 2024-02-26 14-52-37.png" https://bugs.launchpad.net/bugs/2023322/+attachment/5749477/+files/Zrzut%20ekranu%20z%202024-02-26%0A%2014-52-37.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: GTK internal browser does not render with Nvidia drivers Status in Webkit: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Invalid Status in webkit2gtk package in Debian: Fix Released Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window
[Touch-packages] [Bug 2045096] Re: Error in network definition: Invalid MAC address 'random'
** Changed in: netplan Status: In Progress => Fix Committed -- 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/2045096 Title: Error in network definition: Invalid MAC address 'random' Status in netplan: Fix Committed Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: netplan dose not understand the 'random' key word in 'Cloned MAC address' set by networkmanager. ``` /etc/netplan/90-NM-X.yaml:9:19: Error in network definition: Invalid MAC address 'random', must be XX:XX:XX:XX:XX:XX or XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX macaddress: "random" ^ ``` netplan Version 0.107-5ubuntu2 network-manager Version 1.44.2-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2045096/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
** Description changed: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully + - debootstrap focal - debootstrap jammy - debootstrap mantic - debootstrap noble both in buildd and normal variant. [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. ** Description changed: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully - debootstrap focal - debootstrap jammy - debootstrap mantic - debootstrap noble - both in buildd and normal variant. + both in buildd and normal variant, also specifically for noble, + --merged-usr should be ignored. [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. ** Description changed: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5
[Touch-packages] [Bug 2023322]
(In reply to Michael Catanzaro from comment #62) > Hi Craig and Thomas (and Emil if you're still around): if you're still > encountering problems with NVIDIA graphics, please report new a bug and > leave a comment here linking to the new bug. My problem was on legacy nvidia driver, and newer versions wouldn't even start. But I now know a workaround (GSK_RENDERER=cairo) and don't expect there will be a fix for my old driver anyway. https://gitlab.gnome.org/GNOME/gtk/-/issues/5858 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: GTK internal browser does not render with Nvidia drivers Status in Webkit: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Invalid Status in webkit2gtk package in Debian: Fix Released Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated
[Touch-packages] [Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
** Changed in: debootstrap (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 base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: Triaged Status in debootstrap source package in Jammy: In Progress Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully - debootstrap focal - debootstrap jammy - debootstrap mantic - debootstrap noble both in buildd and normal variant. [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than mantic and newer take, and a different approach than Debian takes, where they moved to merging post-extraction, even in stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+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 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7
** Description changed: - The last couple of days, I have been unable to run a successful - debootstrap for Noble Numbat. + [Impact] + The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: - Installed: 1.0.126+nmu1ubuntu0.5 - Candidate: 1.0.126+nmu1ubuntu0.5 - Version table: - *** 1.0.126+nmu1ubuntu0.5 500 - 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages - 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages - 100 /var/lib/dpkg/status - 1.0.126+nmu1 500 - 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages - 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages - + Installed: 1.0.126+nmu1ubuntu0.5 + Candidate: 1.0.126+nmu1ubuntu0.5 + Version table: + *** 1.0.126+nmu1ubuntu0.5 500 + 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages + 100 /var/lib/dpkg/status + 1.0.126+nmu1 500 + 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. + + [Test plan] + Successfully + - debootstrap jammy + - debootstrap mantic + - debootstrap noble + + both in buildd and normal variant. + + [Where problems could occur] + We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. + + That said, this is a different approach than mantic and newer take, and + a different approach than Debian takes, where they moved to merging + post-extraction, even in stable releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2054925 Title: Debootstrap fails for Noble with base-files 13ubuntu7 Status in base-files package in Ubuntu: Won't Fix Status in debootstrap package in Ubuntu: Fix Released Status in debootstrap source package in Focal: Triaged Status in debootstrap source package in Jammy: Triaged Bug description: [Impact] The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat. Apparently this is caused by the addition of symlinks (/bin, /lib, /lib64 and /sbin) in base-files 13ubuntu7. According to debootstrap.log, it fails to extract said symlinks because they already exist at that point. This can be reproduced on build hosts running Jammy Jellyfish against any up-to-date Ubuntu public archive mirror as of today. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy # apt-cache policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.5 Candidate: 1.0.126+nmu1ubuntu0.5 Version table: *** 1.0.126+nmu1ubuntu0.5 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages Attached shell output of two runs of debootstrap. First run uses mirror archive.ubuntu.com (which as of this report serves base-files version 13ubuntu7), and second run uses a local custom mirror (which serves base-files 13ubuntu6). First run fails, second run succeeds. [Test plan] Successfully - debootstrap jammy - debootstrap mantic - debootstrap noble both in buildd and normal variant. [Where problems could occur] We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward. That said, this is a different approach than
[Touch-packages] [Bug 2055037] [NEW] My screen radomly starts flickering
Public bug reported: Hello, I recently installed Ubuntu 22.04.4 on a Lenovo V145-15AST laptop. Randomly, the screen will start flickering. I have found that pulling the power cable out sometimes solves the issue ! But even so, with the power cable out the screen can still start flickering. It's completely random, but very distracting. I am treating this as a bug as I have looked at the options in "Settings > Screen Display" and non of those seem to make any difference. Also I previously tried to install Linux Mint 21.3 and in that case, while booting from the usb stick, I got the welcome to linux mint menu which allows me various options and I select "Start Linux Mint" After that the spinning mint logo appears, then a small mouse pointer on a black screen then the screen goes into some sort of error, a black screen with a few lines at the top. Selecting "Start linux mint in compatability mode" does boot to mint but then the trackpad does not work. I have included this reference to Linux Mint as I believe mint is based on Ubuntu. Many thanks, Nick. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 09:33:11 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:39ec] Subsystem: Lenovo Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [17aa:39ec] InstallationDate: Installed on 2024-02-24 (1 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: LENOVO 81MT ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=e078d5fc-6eaf-4e92-9388-969fa8b6f6db ro 1915.enable_psr=0 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2021 dmi.bios.release: 2.27 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN27WW(V2.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.27 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN27WW(V2.06):bd01/12/2021:br2.27:efr2.27:svnLENOVO:pn81MT:pvrLenovoV145-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2055037 Title: My screen radomly starts flickering Status in xorg package in Ubuntu: New Bug description: Hello, I recently installed Ubuntu 22.04.4 on a Lenovo V145-15AST laptop. Randomly, the screen will start flickering. I have found that pulling the power cable out sometimes solves the issue ! But even so, with the power cable out the screen can still start flickering. It's completely random, but very distracting. I am treating this as a bug as I have looked at the options in "Settings > Screen Display" and non of those seem to make any difference. Also I previously tried to install Linux Mint 21.3 and in that case, while booting from the usb stick, I got the welcome to linux mint menu which allows me various options and I select "Start Linux Mint" After that the spinning mint logo appears, then a small mouse pointer on a black screen then the screen goes into
[Touch-packages] [Bug 2054902] Re: apport test error: /bin/bash not found
** Also affects: apport
Importance: Undecided
Status: New
** Changed in: apport
Importance: Undecided => High
** Changed in: apport
Milestone: None => 2.28.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2054902
Title:
apport test error: /bin/bash not found
Status in Apport:
New
Status in apport package in Ubuntu:
New
Bug description:
This looks like fallout from the completion of usrmerge.
https://autopkgtest.ubuntu.com/packages/apport
=== FAILURES
===
367s ___ T.test_get_file_package
367s
367s self =
367s
367s def test_get_file_package(self):
367s """get_file_package() on installed files."""
367s > self.assertEqual(impl.get_file_package("/bin/bash"), "bash")
367s E AssertionError: None != 'bash'
367s
367s tests/integration/test_packaging_apt_dpkg.py:158: AssertionError
367s ___ T.test_get_files
___
367s
367s self =
367s
367s def test_get_files(self):
367s """get_files()."""
367s self.assertRaises(ValueError, impl.get_files, "nonexisting")
367s > self.assertIn("/bin/bash", impl.get_files("bash"))
367s E AssertionError: '/bin/bash' not found in ['/.', '/etc',
'/etc/bash.bashrc', '/etc/skel', '/etc/skel/.bash_logout', '/etc/skel/.bashrc',
'/etc/skel/.profile', '/usr', '/usr/bin', '/usr/bin/bash', '/usr/bin/bashbug',
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2054902/+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 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
** Changed in: policykit-1 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054716 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: Confirmed Bug description: I was working on recreating bug 2054319 and did so by modifying my /etc/apt/sources.list file from jammy to noble and installing polkit and all its dependencies. bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic linux-headers-6.5.0-14-generic linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic linux-modules-extra-6.2.0-36-generic linux-modules-extra-6.5.0-14-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 libzstd1 locales systemd systemd-dev systemd-oomd systemd-resolved systemd-sysv systemd-timesyncd udev Suggested packages: glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container systemd-homed systemd-userdbd systemd-boot libqrencode4 libtss2-rc0 Recommended packages: libnss-nis libnss-nisplus The following NEW packages will be installed: libduktape207 libsystemd-shared systemd-dev systemd-resolved The following packages will be upgraded: gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 libzstd1 locales pkexec policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev 26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded. Need to get 34.9 MB of archives. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Feb 22 08:46:48 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-02 (112 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+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 2054851] Re: [radeon] gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference()
As a workaround, if anyone needs it, i can get into GUI using recovery mode (no driver loaded) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2054851 Title: [radeon] gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference() Status in Mesa: New Status in mesa package in Ubuntu: Confirmed Bug description: Idont know ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Feb 23 10:38:05 2024 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-10-01 (146 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CO.UTF-8 LANGUAGE=es_CO:es PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.3-1ubuntu1 Signal: 11 SignalName: SIGSEGV SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2054851/+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 2054609] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2054609/+attachment/5749433/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2054609 Title: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1 Status in ntp package in Ubuntu: New Bug description: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2024-02-25 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64+intel-iot (20230316.2) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p15+dfsg-1ubuntu2 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-fips root=UUID=f8b9334a-bf79-4a19-8e05-461a4c1a2e4c ro quiet splash fips=1 vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-97.107+fips1-fips 5.15.136 Tags: wayland-session jammy third-party-packages Uname: Linux 5.15.0-97-fips x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/2054609/+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 2054609] Re: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1
apport information ** Tags added: apport-collected third-party-packages wayland-session ** Description changed: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.3 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2024-02-25 (0 days ago) + InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64+intel-iot (20230316.2) + NtpStatus: ntpq: read: Connection refused + Package: ntp 1:4.2.8p15+dfsg-1ubuntu2 + PackageArchitecture: amd64 + ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-fips root=UUID=f8b9334a-bf79-4a19-8e05-461a4c1a2e4c ro quiet splash fips=1 vt.handoff=7 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.15.0-97.107+fips1-fips 5.15.136 + Tags: wayland-session jammy third-party-packages + Uname: Linux 5.15.0-97-fips x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: ".etc.apparmor.d.usr.sbin.ntpd.txt" https://bugs.launchpad.net/bugs/2054609/+attachment/5749430/+files/.etc.apparmor.d.usr.sbin.ntpd.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2054609 Title: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1 Status in ntp package in Ubuntu: New Bug description: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2024-02-25 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64+intel-iot (20230316.2) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p15+dfsg-1ubuntu2 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-fips root=UUID=f8b9334a-bf79-4a19-8e05-461a4c1a2e4c ro quiet splash fips=1 vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-97.107+fips1-fips 5.15.136 Tags: wayland-session jammy third-party-packages Uname: Linux 5.15.0-97-fips x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/2054609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 2054609] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/2054609/+attachment/5749432/+files/KernLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2054609 Title: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1 Status in ntp package in Ubuntu: New Bug description: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2024-02-25 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64+intel-iot (20230316.2) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p15+dfsg-1ubuntu2 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-fips root=UUID=f8b9334a-bf79-4a19-8e05-461a4c1a2e4c ro quiet splash fips=1 vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-97.107+fips1-fips 5.15.136 Tags: wayland-session jammy third-party-packages Uname: Linux 5.15.0-97-fips x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/2054609/+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 2054609] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2054609/+attachment/5749431/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2054609 Title: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1 Status in ntp package in Ubuntu: New Bug description: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2024-02-25 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64+intel-iot (20230316.2) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p15+dfsg-1ubuntu2 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-97-fips root=UUID=f8b9334a-bf79-4a19-8e05-461a4c1a2e4c ro quiet splash fips=1 vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-97.107+fips1-fips 5.15.136 Tags: wayland-session jammy third-party-packages Uname: Linux 5.15.0-97-fips x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/2054609/+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 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
** Changed in: ubuntu-z-systems Status: Opinion => 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/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in cloud-images: New Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in irqbalance package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1833322/+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 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
I've added a section to the release notes summing this up and linking back here and to some of the past links. ** Changed in: ubuntu-release-notes Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in cloud-images: New Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Opinion Status in irqbalance package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1833322/+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 2054941] Re: Chromium does not print out, although printer is visible
** Also affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2054941 Title: Chromium does not print out, although printer is visible Status in chromium-browser package in Ubuntu: New Status in cups package in Ubuntu: New Bug description: Firefox from snap prints OK, but not Chromium. Interesting thing is that printer is visible, but printout is never coming out from the printer, if it is printed from Chromium. I have this problem for longer time, maybe half a year or more. Here are some outputs which could be useful: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy $ uname -v #107-Ubuntu SMP Wed Feb 7 13:26:48 UTC 2024 $ cups.lpstat -p printer HP_LaserJet_Professional_M1132_MFP is idle. enabled since Sun Feb 25 21:20:34 2024 Could not create job on the system's CUPS daemon - No such file or directory $ lpstat -v device for HP_LaserJet_Professional_M1132_MFP: hp:/usb/HP_LaserJet_Professional_M1132_MFP?serial=0XXX $ cups.lpstat -p printer HP_LaserJet_Professional_M1132_MFP is idle. enabled since Sun Feb 25 21:23:45 2024 Could not create job on the system's CUPS daemon - No such file or directory $ snap list | grep cups cups 2.4.7-3 1024 latest/stable openprinting** - $ snap connections cups InterfacePlug Slot Notes avahi-controlcups:avahi-control:avahi-control - cups chromium:cups cups:cups - cups-control - cups:cups-control - cups-control cups:cups-host:cups-control - home cups:home :home - network cups:network :network - network-bind cups:network-bind :network-bind - network-manager-observe cups:network-manager-observe :network-manager-observe - raw-usb cups:raw-usb :raw-usb - system-files cups:etc-cups :system-files - $ ps aux | grep cups-proxyd root7618 0.0 0.1 241736 3300 ?Sl 19:59 0:01 cups-proxyd /var/snap/cups/common/run/cups.sock /var/run/cups/cups.sock -l --logdir /var/snap/cups/1024/var/log This is interesting part of log from /var/log/cups/error_log: E [25/Feb/2024:19:52:33 +0100] [Client 168] Returning IPP client-error-not-possible for CUPS-Create-Local-Printer (ipp://localhost/) from localhost. W [25/Feb/2024:20:55:05 +0100] Notifier for subscription 502 (dbus://) went away, retrying! W [25/Feb/2024:20:55:05 +0100] Notifier for subscription 503 (dbus://) went away, retrying! W [25/Feb/2024:20:55:05 +0100] Notifier for subscription 505 (dbus://) went away, retrying! W [25/Feb/2024:20:55:05 +0100] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054941/+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
