[Touch-packages] [Bug 2045570] Re: dnsmasq crash when no servers in resolv.conf
confirm the proposed package does fix the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2045570 Title: dnsmasq crash when no servers in resolv.conf Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Jammy: Fix Committed Bug description: [ Impact ] dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever the file is updated. When that happens and for some reason there were no "nameserver" declarations in the updated file, dnsmasq can crash. Here is a log of a reproducer: $ dig +short @127.0.0.1 ubuntu.com ;; communications error to 127.0.0.1#53: timed out ;; communications error to 127.0.0.1#53: connection refused ;; communications error to 127.0.0.1#53: connection refused ;; no servers could be reached We can see the startup, then when resolv.conf is read again and no nameservers were found, and the crash: Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: started, version 2.86 cachesize 150 Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: DNS service limited to local subnets Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: reading /etc/resolv.conf Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: using nameserver 10.0.100.1#53 Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: read /etc/hosts - 7 addresses Jan 03 13:57:13 j-dnsmasq-2045570 systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. Jan 03 13:58:01 j-dnsmasq-2045570 dnsmasq[1507]: no servers found in /etc/resolv.conf, will retry Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process exited, code=dumped, status=11/SEGV Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with result 'core-dump'. dnsmasq has provisions for this situation, we can see that in the 13:58:01 message where it says it will retry, but due to this bug, it crashes instead. The problem was introduced[1] in version 2.86, and fixed in 2.87, so only jammy is affected. 1. https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=patch;h=d290630d31f4517ab26392d00753d1397f9a4114;hp=d2ad5dc073aaacaf22b117f16106282a73586803 The commit message says: """ This problem was introduced in 2.86. """ And indeed, I wasn't able to crash 2.80 shipped in focal. [ Test Plan ] It might take a few tries to reproduce the bug, but here is the general outline. Also keep in mind that it's important to use a DNS name that isn't cached already by a previous query. # Create a jammy lxd container lxc launch ubuntu-daily:jammy j-dnsmasq-2045570 # Enter the container lxc shell j-dnsmasq-2045570 # From now on, all commands should be executed in the container. # Install dnsmasq, and disable systemd-resolved apt update && apt install -y dnsmasq # Disable systemd-resolved, and start dnsmasq systemctl disable --now systemd-resolved systemctl enable --now dnsmasq # In one terminal inside the container, watch the dnsmasq logs: journalctl -u dnsmasq.service -f # In another terminal, remove /etc/resolv.conf and create a new one, empty rm /etc/resolv.conf echo "nameserver 1.1.1.1" > /etc/resolv.conf # restart dnsmasq systemctl restart dnsmasq.service # Perform a dns query dig @127.0.0.1 +short linux.com # Comment the namserver directive in resolv.conf echo "#nameserver 1.1.1.1" > /etc/resolv.conf # Observe in the dnsmasq logs that it notices the change with a message like: Jan 03 14:14:51 j-dnsmasq-2045570 dnsmasq[2274]: no servers found in /etc/resolv.conf, will retry # Perform a *different* DNS query dig @127.0.0.1 +short ubuntu.com # Observe in the dnsmasq logs that it crashes. Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process exited, code=dumped, status=11/SEGV Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with result 'core-dump'. If it doesn't crash right away, repeat these steps a few times, but using a different domain name each time: - add "nameserver 127.0.0.1" to /etc/resolv.conf - observe that dnsmasq notices the change to the file - perform a query for some random domain using "dig @127.0.0.1 +short " - remove "nameserver" from /etc/resolv.conf, observe that dnsmasq noticed the change - perform a query for another random domain The fixed version from proposed will not crash. That last query with no "nameserver" lines in resolv.conf won't work, but it won't crash the server. [ Where problems could occur ] This is doing some pointer/memory manipulation that could introduce memory leaks or other crashes. In fact, this is exactly
[Touch-packages] [Bug 2043579] Re: initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2
I hit this in mantic on 2024-01-19, so seems to still be an issue: https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/armhf/i/initramfs-tools/20240119_180724_10d3d@/log.gz ** Changed in: cryptsetup (Ubuntu) Status: Invalid => New ** Changed in: initramfs-tools (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2043579 Title: initramfs-tools autopkgtest fails on armhf: stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 Status in cryptsetup package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Bug description: The autopkgtest of initramfs-tools fails on armhf on noble: ``` qemu-ata-onlySKIP Test lists explicitly supported architectures, but the current architecture armhf isn't listed. unit-tests PASS qemu-klibc FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-busybox FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-virtio-only FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-separate-usrFAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-panic-shell FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 qemu-net-dnsmasq FAIL stderr: cryptsetup: ERROR: Couldn't resolve device /dev/sda2 ``` The /usr/sbin/mkinitramfs call in build_initramfs() has following output: ``` cryptsetup: ERROR: Couldn't resolve device /dev/sda2 cryptsetup: WARNING: Couldn't determine root device copying from directory /tmp/autopkgtest.g0n4ix/autopkgtest_tmp/initramfs-test.qV8LgntBoK/rootdir ``` The two cryptsetup log lines are printed by /usr/share/initramfs- tools/hooks/cryptroot (which comes from cryptsetup-initramfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2043579/+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 2051407] [NEW] qemu-net autopkgtest fails: Failed to send exit request: Resource temporarily unavailable
Public bug reported:
This log shows initramfs-tools' qemu-net test failing on arm64. Here's
the relevant portion:
https://autopkgtest.ubuntu.com/results/autopkgtest-
mantic/mantic/arm64/i/initramfs-tools/20240119_214255_431f3@/log.gz
[...]
5482s no valid interfaces found
5482s exiting due to oneshot
5482s no interfaces have a carrier
5482s exiting due to oneshot
5482s dhcpcd exited
5482s dhcpcd_fork_cb: truncated read 0 (expected 4)
5492s [ 839.627776] virtio_net virtio1 lan0: renamed from eth0 (while UP)
5492s [ 839.806177] virtio_net virtio2 lan1: renamed from eth1 (while UP)
5544s no such user dhcpcd
5544s dhcpcd-10.0.2 starting
5544s dev: loaded udev
5557s DUID 00:03:00:01:52:54:00:65:43:21
5557s lan0: IAID 00:65:43:21
5557s lan1: IAID 00:12:34:56
5557s lan1: soliciting a DHCP lease
5558s lan1: offered 10.0.2.15 from 10.0.2.2
5558s lan1: probing address 10.0.2.15/24
5558s lan0: soliciting a DHCP lease
5558s lan0: offered 10.0.3.15 from 10.0.3.2
5558s lan0: probing address 10.0.3.15/24
5567s lan1: leased 10.0.2.15 for 86400 seconds
5567s lan1: adding route to 10.0.2.0/24
5567s lan1: adding default route via 10.0.2.2
5569s lan1: Setting hostname: goulash
5571s exiting due to oneshot
5579s dhcpcd exited
5579s dhcpcd_fork_cb: truncated read 0 (expected 4)
5590s Begin: Running /scripts/init-bottom ... Failed to send exit request:
Resource temporarily unavailable
5658s done.
5661s /init: line 386: can't open /root/dev/console: no such file
5661s [ 1009.213600] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0100
I compared this to this successful test log:
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/arm64/i/initramfs-tools/20240116_053535_e8fd8@/log.gz
They test output looks about the same, up until:
5590s Begin: Running /scripts/init-bottom ... Failed to send exit
request: Resource temporarily unavailable.
I believe that error message is coming from /usr/share/initramfs-
tools/scripts/init-bottom/udev. That file does this:
-START-
#!/bin/sh -e
... usual boilerplate ...
# Stop udevd, we'll miss a few events while we run init, but we catch up
udevadm control --exit
# move the /dev tmpfs to the rootfs; fall back to util-linux mount that does
# not understand -o move
mount -n -o move /dev "${rootmnt:?}/dev" || mount -n --move /dev
"${rootmnt}/dev"
-END-
`udevadm control --exit` tries to send an exit request to udev over a
control socket. "Resource temporarily unavailable" means that it
received an -EAGAIN when it tried to do so. udev_ctrl_send() doesn't
check for an -EAGAIN, so this is fatal. Since the script is `set -e`, it
fails to continue and therefore /dev never gets moved over.
Observations:
- The QEMU instance in the failed test ran much slower than the
successful one. The successful one made it to userspace in about 6
seconds, where the failed one took 63.
- Not all QEMU instance boots in this run took that long - the others
took 30-45s. So it's not like the QEMU version or guest kernel are
always slow.
- The failed instance emits "Failed to wait for daemon to reply:
Connection timed out" early on. I'm guessing that this is from the
`udevadm` calls in init-top/udev - likely the `udevadm settle`, since it
is the only one with a `|| true` to ignore errors. Perhaps this is an
early sign that something is wrong with systemd-udevd. Here's that
snippet:
---START---
[ 63.075129] Run /init as init process
Loading, please wait...
Starting systemd-udevd version 253.5-1ubuntu6.1
[ 233.675459] hrtimer: interrupt took 10193008 ns
Failed to wait for daemon to reply: Connection timed out
Begin: Loading essential drivers ... [ 576.182017] raid6: neonx8 gen() 210
MB/s
[ 576.261515] raid6: neonx4 gen() 244 MB/s
---END---
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2051407
Title:
qemu-net autopkgtest fails: Failed to send exit request: Resource
temporarily unavailable
Status in initramfs-tools package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
This log shows initramfs-tools' qemu-net test failing on arm64. Here's
the relevant portion:
https://autopkgtest.ubuntu.com/results/autopkgtest-
mantic/mantic/arm64/i/initramfs-tools/20240119_214255_431f3@/log.gz
[...]
5482s no valid interfaces found
5482s exiting due to oneshot
5482s no interfaces have a carrier
5482s exiting due to oneshot
5482s dhcpcd exited
5482s dhcpcd_fork_cb: truncated read 0 (expected 4)
5492s [ 839.627776] virtio_net virtio1 lan0: renamed from eth0 (while UP)
5492s [
[Touch-packages] [Bug 2051405] [NEW] ProtectHome setting in debian/rsyslog.service isn't understood by systemd
Public bug reported: Small bug introduced in commit e175f5c3668adc1c65f66efb61f70060569c9fe8 https://git.launchpad.net/ubuntu/+source/rsyslog/commit/?id=e175f5c3668adc1c65f66efb61f70060569c9fe8 which changed the rsyslog.service line of ProtectHome=yes to ProtectHome=readonly Systemd doesn't understand "readonly" https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html and will mention in its journal: systemd[1]: /lib/systemd/system/rsyslog.service:24: Failed to parse protect home value, ignoring: readonly Quickfix: just needs a hyphen on line 24 to read 'read-only' ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2051405 Title: ProtectHome setting in debian/rsyslog.service isn't understood by systemd Status in rsyslog package in Ubuntu: New Bug description: Small bug introduced in commit e175f5c3668adc1c65f66efb61f70060569c9fe8 https://git.launchpad.net/ubuntu/+source/rsyslog/commit/?id=e175f5c3668adc1c65f66efb61f70060569c9fe8 which changed the rsyslog.service line of ProtectHome=yes to ProtectHome=readonly Systemd doesn't understand "readonly" https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html and will mention in its journal: systemd[1]: /lib/systemd/system/rsyslog.service:24: Failed to parse protect home value, ignoring: readonly Quickfix: just needs a hyphen on line 24 to read 'read-only' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2051405/+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 2049318] Re: [SRU] free(): double free detected in tcache 2
I can confirm iptables from jammy-proposed have fixed the bug for me. Tests done as mentioned in testplan: 1. create nft rule: sudo nft -f -
[Touch-packages] [Bug 2051398] [NEW] [BPO] PackageKit/1.2.5 from jammy
Public bug reported: I would like that someone makes a backport for PackageKit 1.2.7 for Ubuntu 22.04 LTS in order to solve https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=910365 i.e. https://github.com/PackageKit/PackageKit/issues/284. I.e. to remove duplicates in GNOME Software Center due to the error in PackageKit. Can this modification be applied also on the version 1.2.5 to solve the problem? How to test whether the Ubuntu package for mantic can be installed on jammy without dependency problems, and does that version work on jammy if there is any action needed from my side? I was redirected here from https://answers.launchpad.net/ubuntu/+source/packagekit/+question/709115. ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Description changed: I would like that someone makes a backport for PackageKit 1.2.7 for Ubuntu 22.04 LTS in order to solve https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=910365 i.e. https://github.com/PackageKit/PackageKit/issues/284. I.e. to remove duplicates in GNOME Software Center due to the error in PackageKit. Can this modification be applied also on the version 1.2.5 to solve the problem? How to test whether the Ubuntu package for mantic can be installed on jammy without dependency problems, and does that version work on jammy if there is any action needed from my side? + + I was redirected here from + https://answers.launchpad.net/ubuntu/+source/packagekit/+question/709115. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2051398 Title: [BPO] PackageKit/1.2.5 from jammy Status in packagekit package in Ubuntu: New Bug description: I would like that someone makes a backport for PackageKit 1.2.7 for Ubuntu 22.04 LTS in order to solve https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=910365 i.e. https://github.com/PackageKit/PackageKit/issues/284. I.e. to remove duplicates in GNOME Software Center due to the error in PackageKit. Can this modification be applied also on the version 1.2.5 to solve the problem? How to test whether the Ubuntu package for mantic can be installed on jammy without dependency problems, and does that version work on jammy if there is any action needed from my side? I was redirected here from https://answers.launchpad.net/ubuntu/+source/packagekit/+question/709115. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2051398/+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 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04
Tested in a VM and could not duplicate the issue using a fully upgraded 22.04 install and using `do-release-upgrade -d` from the terminal to upgrade to Noble Numbat (future 24.04) in order to see the terminal output. The only issue I noticed is that it tried to pull-in chromium from the snap store (??), but that would be an issue related to ubuntu-release- upgrader and is a known issue there. The issue described in this bug report did not occur. Looking at Kubuntu's analogous fix (https://git.launchpad.net/~kubuntu- packagers/kubuntu-packaging/+git/kubuntu- settings/commit/?h=kubuntu_lunar_archive=ea776d7a69057b6c30ae8bceaa21393eec47cbad) which was done at around the same time as https://git.launchpad.net/ubuntustudio-default- settings/commit/?id=4bdc9d5b9ac18cf0aa5035646e4b4016faa62d3d, in fact, within a couple weeks of each other, they are nearly identical. With that in mind, and the fact that neither fix currently warrants a "Conflicts:" line which would cause even more problems as we would *never* want to conflict with fontconfig, I'm more than willing to bet the original poster in askubuntu.com didn't have a fully-updated system prior to attempting an upgrade. With that in mind, I will have to re-close this as invalid as the fix was already done prior to 23.04's release and this isn't even a bug. Thanks for the report, though! ** Changed in: ubuntustudio-default-settings (Ubuntu) Status: New => Invalid -- 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/2051313 Title: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04 Status in fontconfig package in Ubuntu: Invalid Status in ubuntustudio-default-settings package in Ubuntu: Invalid Bug description: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my computer. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Not my computer. 3) What you expected to happen The AskUbuntu user's upgrade from 22.04 to 24.04 to complete successfully. 4) What happened instead The upgrade failed and they posted to AskUbuntu. # Copy of their question body After an upgrade to ``` Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release: 24.04 Codename:noble ``` apt won't update bcs of unmet dependencies. ``` The following packages have unmet dependencies: libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1) libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` I've tried: ``` apt --fix-broken install ``` ``` dpkg: error processing archive /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package ubuntustudio-default-settings 22.04.26.3 dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Errors were encountered while processing: /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` # Copy of workaround in my answer body The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel- rgb.conf` out of `ubuntustudio-default-settings` ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default- settings/filelist), [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default- settings/filelist)) and into [`fontconfig- config`](https://packages.ubuntu.com/noble/all/fontconfig- config/filelist). The `ubuntustudio-default-settings` package needs to be updated first but the maintainers forgot to add an automatic `Conflicts:` line. You can retry installing the package in the correct order by running `sudo apt install --upgrade ubuntustudio-default-settings`. If that does not work, you need to forcibly reinstall things in the correct order: ```bash
[Touch-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04
Ok, upon further inspection, I'm switching this back to "new" simply because it has not been "confirmed" by more than one person. The original reporter is not the person filing the bug, which means this needs to be "confirmed" by someone other than the reporter. Furthermore, LP: #2005124 doesn't apply here as it was a completely separate issue. The reason I was a little hesitant is because it looked like, mostly based on the askubuntu question, the person was legitimately asking for support not filing a bug report. Launchpad is for bug reports, not support questions, unless it's on the support tracker. This part (bugs.launchpad.net) is the bug tracker. Either way, I apologize for my earlier response as I shouldn't be punishing people for pointing out problems where they might exist. I'm testing right now. -- 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/2051313 Title: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04 Status in fontconfig package in Ubuntu: Invalid Status in ubuntustudio-default-settings package in Ubuntu: New Bug description: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my computer. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Not my computer. 3) What you expected to happen The AskUbuntu user's upgrade from 22.04 to 24.04 to complete successfully. 4) What happened instead The upgrade failed and they posted to AskUbuntu. # Copy of their question body After an upgrade to ``` Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release: 24.04 Codename:noble ``` apt won't update bcs of unmet dependencies. ``` The following packages have unmet dependencies: libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1) libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` I've tried: ``` apt --fix-broken install ``` ``` dpkg: error processing archive /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package ubuntustudio-default-settings 22.04.26.3 dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Errors were encountered while processing: /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` # Copy of workaround in my answer body The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel- rgb.conf` out of `ubuntustudio-default-settings` ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default- settings/filelist), [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default- settings/filelist)) and into [`fontconfig- config`](https://packages.ubuntu.com/noble/all/fontconfig- config/filelist). The `ubuntustudio-default-settings` package needs to be updated first but the maintainers forgot to add an automatic `Conflicts:` line. You can retry installing the package in the correct order by running `sudo apt install --upgrade ubuntustudio-default-settings`. If that does not work, you need to forcibly reinstall things in the correct order: ```bash sudo -i apt update apt download ubuntustudio-default-settings apt download fontconfig-config # Temporarily force-uninstall only ubuntustudio-default-settings # so that we DON'T uninstall ubuntustudio-desktop dpkg --force-all -r ubuntustudio-default-settings dpkg --force-all -i ./fontconfig-config_* dpkg --force-all -i ./ubuntustudio-default-settings_* dpkg --configure -a apt --fix-broken install apt upgrade apt dist-upgrade ``` # Analysis Please apply an analogous fix. Where I mentioned `Conflicts:` on AskUbuntu, a `Pre-Depends:` may be necessary instead as I read somewhere on
[Touch-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04
** Changed in: ubuntustudio-default-settings (Ubuntu) Status: Invalid => New -- 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/2051313 Title: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04 Status in fontconfig package in Ubuntu: Invalid Status in ubuntustudio-default-settings package in Ubuntu: New Bug description: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my computer. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Not my computer. 3) What you expected to happen The AskUbuntu user's upgrade from 22.04 to 24.04 to complete successfully. 4) What happened instead The upgrade failed and they posted to AskUbuntu. # Copy of their question body After an upgrade to ``` Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release: 24.04 Codename:noble ``` apt won't update bcs of unmet dependencies. ``` The following packages have unmet dependencies: libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1) libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` I've tried: ``` apt --fix-broken install ``` ``` dpkg: error processing archive /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package ubuntustudio-default-settings 22.04.26.3 dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Errors were encountered while processing: /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` # Copy of workaround in my answer body The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel- rgb.conf` out of `ubuntustudio-default-settings` ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default- settings/filelist), [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default- settings/filelist)) and into [`fontconfig- config`](https://packages.ubuntu.com/noble/all/fontconfig- config/filelist). The `ubuntustudio-default-settings` package needs to be updated first but the maintainers forgot to add an automatic `Conflicts:` line. You can retry installing the package in the correct order by running `sudo apt install --upgrade ubuntustudio-default-settings`. If that does not work, you need to forcibly reinstall things in the correct order: ```bash sudo -i apt update apt download ubuntustudio-default-settings apt download fontconfig-config # Temporarily force-uninstall only ubuntustudio-default-settings # so that we DON'T uninstall ubuntustudio-desktop dpkg --force-all -r ubuntustudio-default-settings dpkg --force-all -i ./fontconfig-config_* dpkg --force-all -i ./ubuntustudio-default-settings_* dpkg --configure -a apt --fix-broken install apt upgrade apt dist-upgrade ``` # Analysis Please apply an analogous fix. Where I mentioned `Conflicts:` on AskUbuntu, a `Pre-Depends:` may be necessary instead as I read somewhere on Launchpad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2051313/+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 2051367] Re: [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/2051367 Title: [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: When using 2 external monitors via a dual HDMI adapter plugged on the usb-c port, when i go to play sound at all, 1 of the external monitors is always selected as the default output device when this should still be the laptop internal speakers. Annoying as hell to have to go into the settings everytime i switch the laptop on and there is no sound on sound output. It would be great if you could fix it so it leaves its always "laptop internal speakers" as default. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-92.102-generic 5.15.131 Uname: Linux 5.15.0-92-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: smiler 7478 F pulseaudio /dev/snd/pcmC2D0c: smiler 7478 F...m pulseaudio /dev/snd/controlC1: smiler 7478 F pulseaudio /dev/snd/controlC0: smiler 7478 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 14:17:02 2024 InstallationDate: Installed on 2022-02-04 (720 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Renoir Radeon High Definition Audio Controller - HD-Audio Generic Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2021 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN25WW(V1.11) 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: IdeaPad 5 14ARE05 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrDTCN25WW(V1.11):bd09/14/2021:br1.25:efr1.25:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad514ARE05:skuLENOVO_MT_81YM_BU_idea_FM_IdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051367/+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 2051367] [NEW] [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem
You have been subscribed to a public bug: When using 2 external monitors via a dual HDMI adapter plugged on the usb-c port, when i go to play sound at all, 1 of the external monitors is always selected as the default output device when this should still be the laptop internal speakers. Annoying as hell to have to go into the settings everytime i switch the laptop on and there is no sound on sound output. It would be great if you could fix it so it leaves its always "laptop internal speakers" as default. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-92.102-generic 5.15.131 Uname: Linux 5.15.0-92-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: smiler 7478 F pulseaudio /dev/snd/pcmC2D0c: smiler 7478 F...m pulseaudio /dev/snd/controlC1: smiler 7478 F pulseaudio /dev/snd/controlC0: smiler 7478 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 14:17:02 2024 InstallationDate: Installed on 2022-02-04 (720 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Renoir Radeon High Definition Audio Controller - HD-Audio Generic Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2021 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN25WW(V1.11) 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: IdeaPad 5 14ARE05 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrDTCN25WW(V1.11):bd09/14/2021:br1.25:efr1.25:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad514ARE05:skuLENOVO_MT_81YM_BU_idea_FM_IdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- [81YM, ATI R6xx HDMI, Digital Out, HDMI] Playback problem https://bugs.launchpad.net/bugs/2051367 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 400409] Re: RS is readonly
This issue is fixed in Ubuntu 20.04 and later releases.
As Ubuntu 18.04 and all earlier releases no longer receive standard
support after 2023-06, the fix won't be available in those Ubuntu
releases through standard channels. If you want to have it fixed via
Ubuntu LTS, please directly consult with Ubuntu LTS persons.
As a result, marking this bug as fix released.
** Changed in: mawk (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
https://bugs.launchpad.net/bugs/400409
Title:
RS is readonly
Status in mawk package in Ubuntu:
Fix Released
Bug description:
Binary package hint: mawk
System: Ubuntu 8.04.1
mawk version: 1.3.3-11ubuntu2
Running the following in bash:
for ((i = 1; i <= 10; ++i)); do echo -ne "$i\0"; done | awk 'BEGIN {RS =
"\0"}; END {print NR}'
Gives: 1
Expected: 10
mawk does not care what RS is set to.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/400409/+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 2051346] Re: No longer preseed LXD snap to allow for LXD 5.20 release
If the impact on first-time start is acceptable by the server team (which seems to be the case), this looks like a reasonable ask. -- 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/2051346 Title: No longer preseed LXD snap to allow for LXD 5.20 release Status in ubuntu-meta package in Ubuntu: New Bug description: With LXD 5.20 there is a license change to AGPL and it has been decided to no longer seed the snap in Ubuntu 24.04 and later and instead seed the lxd-installer package instead. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346/+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 2051358] Re: Start of systemd service on physical network devices using a udev rule has stopped working
** Description changed:
Hi everyone,
We have an issue with latest version of systemd on Ubuntu 22.04
(249.11-0ubuntu3.12).
We have a udev rule running a service (custom wpa supplicant) on physical
wired network devices that is not working during boot process anymore.
- The same rule works fine with a usb dongle I unplug and plug back after the
machine has started.
-
- A colleague has rebuilt systemd package by reverting below patch and
- everything started working again
-
- core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
- File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch
-
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
-
- This is causing an issue to access network when the machine is starting.
+ The same rule works fine with a usb dongle when I unplug it and plug it back
after the machine has started.
```
ACTION=="add|move", SUBSYSTEM=="net", TAG+="systemd", ENV{DEVTYPE}!="wlan",
DEVPATH!="/devices/virtual/*",\
- ENV{SYSTEMD_WANTS}+="supplicant-wired@$name.service"
+ ENV{SYSTEMD_WANTS}+="supplicant-wired@$name.service"
```
+
+ A colleague has rebuilt systemd package by reverting below patch and
+ everything started working again:
+
+ core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
+ File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch
+
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
+
+ This is causing us an issue to access network when the machine is
+ starting.
+
Does above patch requires a change in the udev rule we are using ?
Thanks in advance for your help.
--
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/2051358
Title:
Start of systemd service on physical network devices using a udev rule
has stopped working
Status in systemd package in Ubuntu:
New
Bug description:
Hi everyone,
We have an issue with latest version of systemd on Ubuntu 22.04
(249.11-0ubuntu3.12).
We have a udev rule running a service (custom wpa supplicant) on physical
wired network devices that is not working during boot process anymore.
The same rule works fine with a usb dongle when I unplug it and plug it back
after the machine has started.
```
ACTION=="add|move", SUBSYSTEM=="net", TAG+="systemd", ENV{DEVTYPE}!="wlan",
DEVPATH!="/devices/virtual/*",\
ENV{SYSTEMD_WANTS}+="supplicant-wired@$name.service"
```
A colleague has rebuilt systemd package by reverting below patch and
everything started working again:
core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
This is causing us an issue to access network when the machine is
starting.
Does above patch requires a change in the udev rule we are using ?
Thanks in advance for your help.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2051358/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
regression fix is in, so this can be marked as verified ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
tested on my hw, works as planned -- 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/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2051358] [NEW] Start of systemd service on physical network devices using a udev rule has stopped working
Public bug reported:
Hi everyone,
We have an issue with latest version of systemd on Ubuntu 22.04
(249.11-0ubuntu3.12).
We have a udev rule running a service (custom wpa supplicant) on physical wired
network devices that is not working during boot process anymore.
The same rule works fine with a usb dongle I unplug and plug back after the
machine has started.
A colleague has rebuilt systemd package by reverting below patch and
everything started working again
core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
This is causing an issue to access network when the machine is starting.
```
ACTION=="add|move", SUBSYSTEM=="net", TAG+="systemd", ENV{DEVTYPE}!="wlan",
DEVPATH!="/devices/virtual/*",\
ENV{SYSTEMD_WANTS}+="supplicant-wired@$name.service"
```
Does above patch requires a change in the udev rule we are using ?
Thanks in advance for your help.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2051358
Title:
Start of systemd service on physical network devices using a udev rule
has stopped working
Status in systemd package in Ubuntu:
New
Bug description:
Hi everyone,
We have an issue with latest version of systemd on Ubuntu 22.04
(249.11-0ubuntu3.12).
We have a udev rule running a service (custom wpa supplicant) on physical
wired network devices that is not working during boot process anymore.
The same rule works fine with a usb dongle I unplug and plug back after the
machine has started.
A colleague has rebuilt systemd package by reverting below patch and
everything started working again
core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
This is causing an issue to access network when the machine is
starting.
```
ACTION=="add|move", SUBSYSTEM=="net", TAG+="systemd", ENV{DEVTYPE}!="wlan",
DEVPATH!="/devices/virtual/*",\
ENV{SYSTEMD_WANTS}+="supplicant-wired@$name.service"
```
Does above patch requires a change in the udev rule we are using ?
Thanks in advance for your help.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2051358/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2051346] [NEW] No longer preseed LXD snap to allow for LXD 5.20 release
Public bug reported: With LXD 5.20 there is a license change to AGPL and it has been decided to no longer seed the snap in Ubuntu 24.04 and later and instead seed the lxd-installer package instead. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n60 ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Description changed: With LXD 5.20 there is a license change to AGPL and it has been decided - to no longer seed the snap in Ubuntu 22.04 and later and instead seed + to no longer seed the snap in Ubuntu 24.04 and later and instead seed the lxd-installer package instead. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n60 -- 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/2051346 Title: No longer preseed LXD snap to allow for LXD 5.20 release Status in ubuntu-meta package in Ubuntu: New Bug description: With LXD 5.20 there is a license change to AGPL and it has been decided to no longer seed the snap in Ubuntu 24.04 and later and instead seed the lxd-installer package instead. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346/+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 2051346] Re: No longer preseed LXD snap to allow for LXD 5.20 release
** Merge proposal linked: https://code.launchpad.net/~philroche/ubuntu-seeds/+git/ubuntu/+merge/459502 -- 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/2051346 Title: No longer preseed LXD snap to allow for LXD 5.20 release Status in ubuntu-meta package in Ubuntu: New Bug description: With LXD 5.20 there is a license change to AGPL and it has been decided to no longer seed the snap in Ubuntu 24.04 and later and instead seed the lxd-installer package instead. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
GA kernel doesn't support DG2, oem-6.1 was the first one, hwe-6.2 does too and works more or less fine (doesn't suffer from this issue) -- 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/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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
