[Touch-packages] [Bug 2010924] Re: MT7921K --> BLE funktion don't working
It's the kernel driver itself: mt7921 It's missing BLE support for this device. On Windows BLE is working. I really don't know witch one is the driver for bluetooth function for this device, because it's Wi-fi + BT 5.2 combo. Found in AMD Wi-Fi 6E RZ608 (MediaTek MT7921K) In this MB: X570S AORUS ELITE AX (rev. 1.1) And this wi-fi + BT combo are found in all new MB with integrated wi-fi + BT combos. ** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2010924 Title: MT7921K --> BLE funktion don't working Status in bluez package in Ubuntu: New Bug description: Hi, i have MT7921K BT chip that BLE function is not working with linux, but normal BT is working. I try several distros and some live-iso and get same effect. BLE just not working with this device. I have other BT adapters and BLE is working for them. This is a probe for my PC: https://linux-hardware.org/?probe=969ab4279f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2010924/+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 2010924] [NEW] MT7921K --> BLE funktion don't working
You have been subscribed to a public bug: Hi, i have MT7921K BT chip that BLE function is not working with linux, but normal BT is working. I try several distros and some live-iso and get same effect. BLE just not working with this device. I have other BT adapters and BLE is working for them. This is a probe for my PC: https://linux-hardware.org/?probe=969ab4279f ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- MT7921K --> BLE funktion don't working https://bugs.launchpad.net/bugs/2010924 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez 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 2011270] Re: Printing intermittenly fails -- autodetected network printer
** Package changed: ubuntu => xorg (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/2011270 Title: Printing intermittenly fails -- autodetected network printer Status in xorg package in Ubuntu: New Bug description: It appears that print jobs passed to the auto-detected printer "adding" wizard do not always succeed. See in these error messages how hpcups is passed a null object to print. It's unclear what the interactions is between the auto-discovery gnome(?) applet, the hpcups system, and dbus. The net effect is that a print job is sent to the printer defined here, and it just gets stuck in "stopped". With no error message or way for the user to resolve the issue. I'm not sure where to begin debugging ... Error messages in question : Mar 10 16:44:17 semiauto dbus-daemon[680]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.1929' (uid=1000 pid=485631 comm="gnome-control-center printers" label="unconfined") (using servicehelper) Mar 10 16:44:17 semiauto dbus-daemon[680]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism' Mar 10 16:44:25 semiauto google-chrome.desktop[496973]: Warning: disabling flag --expose_wasm due to conflicting flags Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 79: unable to open /var/lib/hp/hplip.state: No such file or directory Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 129: validate_plugin_version() Failed to get Plugin version from [/var/lib/hp/hplip.state] Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 173: Plugin version is not matching Mar 10 16:44:34 semiauto hpcups[515382]: prnt/hpcups/HPCupsFilter.cpp 505: m_Job initialization failed with error = 48 Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 244: Invalid Library handler pLibHandler = NULL. Mar 10 16:45:01 semiauto CRON[515541]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Mar 10 16:45:09 semiauto gnome-shell[333439]: Window manager warning: Ping serial 447743079 was reused for window W713, previous use was for window 0xc00014. Mar 10 16:45:20 semiauto systemd[4596]: vte-spawn-4d0c2df5-8c91-461c-ac5d-b95a2bc252a9.scope: Consumed 33.860s CPU time. Mar 10 16:45:20 semiauto gnome-shell[333439]: JS ERROR: TypeError: this.actor is null#012_syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:138:25#012onStopped@resource:///org/gnome/shell/ui/windowManager.js:150:35#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:316:60#012_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1596:21#012onStopped@resource:///org/gnome/shell/ui/windowManager.js:1564:39#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22#012_easeActor/<@resource:///org/gnome/shell/ui/environment.js:239:64 Mar 10 16:45:23 semiauto dbus-daemon[680]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.1929' (uid=1000 pid=485631 comm="gnome-control-center printers" label="unconfined") (using servicehelper) Mar 10 16:45:23 semiauto systemd[4596]: app-gnome-virtualbox-495654.scope: Consumed 11min 33.878s CPU time. Mar 10 16:45:23 semiauto dbus-daemon[680]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism' Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Settings.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Calculator.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Characters' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Notes.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Successfully activated service 'org.gnome.Settings.SearchProvider' Make and model auto-reported is: "HP LaserJet Professional m1217nfw MFP, hpcups 3.22.6, requires proprietary plugin" yes, it has commas. URI is reported as: dnssd://HP%20LaserJet%20Professional%20M1217nfw%20MFP._pdl-datastream._tcp.local/ and "location" is aparrently blank. I can troubleshoot further. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package:
[Touch-packages] [Bug 2011279] [NEW] xorg
Public bug reported: 桌面标不显示，右键菜单加载不完整 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 07:57:08 2023 DistUpgraded: 2022-11-12 11:37:26,280 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.85.05, 6.1.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22ca] Subsystem: Lenovo TU117M [GeForce MX450] [17aa:22ca] InstallationDate: Installed on 2022-01-02 (432 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) MachineType: LENOVO 20W0005VCD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=b4c00f4f-589b-42e2-b402-7ea8b75191a7 ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2022-11-12 (118 days ago) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.54 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET54W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0005VCD dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET54W(1.54):bd11/21/2022:br1.54:efr1.42:svnLENOVO:pn20W0005VCD:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005VCD:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0005VCD dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.6-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 lunar possible-manual-nvidia-install reproducible single-occurrence 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/2011279 Title: xorg Status in xorg package in Ubuntu: New Bug description: 桌面标不显示，右键菜单加载不完整 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 11 07:57:08 2023 DistUpgraded: 2022-11-12 11:37:26,280 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: nvidia/525.85.05, 6.1.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22ca] Subsystem: Lenovo TU117M [GeForce MX450] [17aa:22ca] InstallationDate: Installed on 2022-01-02 (432 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) MachineType: LENOVO 20W0005VCD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-16-generic root=UUID=b4c00f4f-589b-42e2-b402-7ea8b75191a7 ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2022-11-12 (118 days ago) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.54 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET54W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0005VCD dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Touch-packages] [Bug 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144
To proceed with this SRU, I would like to have some analysis of what makes this an armhf-only failure. Is it to do with the fact that armhf autopkgtests run in a container and others do not? If so, it seems to me that a more correct fix for the test is to detect that we're running in a container instead of querying the arch. ** Changed in: systemd (Ubuntu Focal) Status: Triaged => Incomplete -- 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/1991285 Title: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in linux source package in Focal: New Status in systemd source package in Focal: Incomplete Bug description: [Impact] The armhf autopkgtests currently fail in Focal due to this, and failures are not marked as regressions. This limits our ability to catch other regressions on armhf. [Test Plan] The boot-and-services autopkgtest should not fail on armhf. Specifically, the test_no_failed test should ignore systemd-remount-fs.service failures on armhf only. [Where problems could occur] The fix is limited to the boot-and-services autopkgtest, so there is limited risk. Any bugs would show up in that test. [Original Description] This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-128.144 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 2000880] Re: systemd-networkd: ActivationPolicy ignored in VLANs
Hello Craig, or anyone else affected, Accepted systemd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.8 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: systemd (Ubuntu Jammy) Status: Triaged => 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/2000880 Title: systemd-networkd: ActivationPolicy ignored in VLANs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] The ActivationPolicy property in .network files is ignored for VLANs. [Test Plan] * On a Jammy machine with an interface named ens3, create the following configs: $ cat > /etc/systemd/network/10-vlan18.netdev << EOF [NetDev] Name=vlan18 Kind=vlan [VLAN] Id=18 EOF $ cat > /etc/systemd/network/20-vlan18.network << EOF [Match] Name=vlan18 [Network] Address=10.10.1.1/24 [Link] ActivationPolicy=manual EOF $ cat > /etc/systemd/network/30-ens3.network << EOF [Match] Name=ens3 [Network] DHCP=ipv4 VLAN=vlan18 EOF * Reboot the machine * On an affected machine, the vlan18@ens3 interface will have a configured IP at boot, despite the ActivationPolicy=manual setting in /etc/systemd/network/20-vlan18.network. On a patched machine, the interface should not have a configured IP. [Where problems could occur] The patch adds a condition where a netdev is not yet ready to be created. Specifically, it makes sure stacked netdevs are not created before their underlying link is activated. If we saw any problems, it would be related to netdev creation. [Original Description] This has been fixed upstream, see Upstream bug: https://github.com/systemd/systemd/issues/22593 Any chance of a backport of the fix to 22.04? Fix: https://github.com/systemd/systemd-stable/pull/211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000880/+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 2002445] Re: udev NIC renaming race with mlx5_core driver
Hello Nick, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.8 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: systemd (Ubuntu Jammy)
Status: Triaged => Fix Committed
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2002445
Title:
udev NIC renaming race with mlx5_core driver
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Triaged
Status in systemd source package in Jammy:
Fix Committed
Status in systemd source package in Kinetic:
Fix Committed
Status in systemd source package in Lunar:
Fix Released
Bug description:
[Impact]
On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core
driver's own configuration of subordinate interfaces. When the kernel wins this
race, the device cannot be renamed as udev has attempted, and this causes
systemd-network-online.target to timeout waiting for links to be configured.
This ultimately results in boot being delayed by about 2 minutes.
[Test Plan]
Repeated launches of Standard_D8ds_v5 instance types will generally hit this
race around 1 in 10 runs. Create a vm snapshot with updated systemd from
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated
systemd. Assert not failure in cloud-init status and no 2 minute delay in
network-online.target.
To check for failure symptom:
- Assert that network-online.target isn't the longest pole from
systemd-analyze blame.
To assert success condition during net rename busy race:
- assert when "eth1" is still the primary device name, that two altnames
are listed (preserving the altname due to the primary NIC rename being hit.
Sample script uses pycloudlib to create modified base image for test
and launches 100 VMs of type Standard_D8ds_v5, counting both successes
and any failures seen.
#!/usr/bin/env python3
# This file is part of pycloudlib. See LICENSE file for license information.
"""Basic examples of various lifecycle with an Azure instance."""
import logging
import json
import pycloudlib
LOG = logging.getLogger()
base_cfg = """#cloud-config
ssh-import-id: [chad.smith, enr0n]
"""
apt_cfg = """
# Add developer PPA
apt:
sources:
systemd-testing:
source: "deb [allow-insecure=yes]
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
# upgrade systemd after cloud-init is nearly done
runcmd:
- apt install systemd udev -y --allow-unauthenticated
"""
debug_systemd_cfg = """
# Create systemd-udev debug override.conf in base image
write_files:
- path: /etc/systemd/system/systemd-networkd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
- path: /etc/systemd/system/systemd-udevd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
LogRateLimitIntervalSec=0
"""
cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
cloud_config2 = base_cfg + debug_systemd_cfg
def debug_systemd_image_launch_overlake_v5_with_snapshot():
"""Test overlake v5 timeouts
test procedure:
- Launch base focal image
- enable ppa:enr0n/systemd-245 and systemd/udev debugging
- cloud-init clean --logs && deconfigure waalinux agent before shutdown
- snapshot a base image
- launch v5 system from snapshot
- check systemd-analyze for expected timeout
"""
client = pycloudlib.Azure(tag="azure")
image_id = client.daily_image(release="focal")
pub_path =
[Touch-packages] [Bug 2004478] Re: systemd-networkd's dhcp4 client ignores local subnet routes
Hello Tuetuopay, or anyone else affected, Accepted systemd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.8 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: systemd (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2004478 Title: systemd-networkd's dhcp4 client ignores local subnet routes Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: Fix Committed Bug description: [Impact] If a DHCP server pushes down a local subnet route with a null gateway, the systemd-networkd DHCP client does not correctly install the route. Instead, the route is ignored. [Test Plan] Taken from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004478/comments/2. * Start a Jammy LXD container: $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash * Create a veth pair: $ ip link add veth0 up type veth peer name veth1 $ ip addr add 172.20.0.1/24 dev veth0 $ cat > /etc/netplan/60-veth1.yaml
[Touch-packages] [Bug 2009502] Re: Enable /dev/sgx_vepc access for the group 'sgx'
Hello Pedro, or anyone else affected, Accepted systemd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.8 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. ** Description changed: [ Impact ] - On systems where Intel SGX is available, access to a specific devide + On systems where Intel SGX is available, access to a specific device node (/dev/sgx_vepc) must be enforced, with a specific permission (0660) and group (sgx). This allows KVM-based virtual machines to use such feature (the SGX "enclaves") in a proper fashion. Without this, a manual udev rule needs to be created. - [ Test Plan ] As the patch itself only tailors the permissions/group to the device node, in a system with Intel-SGX enabled, merely `ls -la` against the device node should show if the permissions and group are seen as expected. - [ Where problems could occur ] N/A. This seems to be a very straightforward inclusion, very specific to access enablement to the SGX reserved memory used for hosting enclaves. [ Other Info ] - + N/A. ** Changed in: systemd (Ubuntu Jammy) Status: Triaged => 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/2009502 Title: Enable /dev/sgx_vepc access for the group 'sgx' Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Bug description: [ Impact ] On systems where Intel SGX is available, access to a specific device node (/dev/sgx_vepc) must be enforced, with a specific permission (0660) and group (sgx). This allows KVM-based virtual machines to use such feature (the SGX "enclaves") in a proper fashion. Without this, a manual udev rule needs to be created. [ Test Plan ] As the patch itself only tailors the permissions/group to the device node, in a system with Intel-SGX enabled, merely `ls -la` against the device node should show if the permissions and group are seen as expected. [ Where problems could occur ] N/A. This seems to be a very straightforward inclusion, very specific to access enablement to the SGX reserved memory used for hosting enclaves. [ Other Info ] N/A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009502/+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 2011270] [NEW] Printing intermittenly fails -- autodetected network printer
You have been subscribed to a public bug: It appears that print jobs passed to the auto-detected printer "adding" wizard do not always succeed. See in these error messages how hpcups is passed a null object to print. It's unclear what the interactions is between the auto-discovery gnome(?) applet, the hpcups system, and dbus. The net effect is that a print job is sent to the printer defined here, and it just gets stuck in "stopped". With no error message or way for the user to resolve the issue. I'm not sure where to begin debugging ... Error messages in question : Mar 10 16:44:17 semiauto dbus-daemon[680]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.1929' (uid=1000 pid=485631 comm="gnome-control-center printers" label="unconfined") (using servicehelper) Mar 10 16:44:17 semiauto dbus-daemon[680]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism' Mar 10 16:44:25 semiauto google-chrome.desktop[496973]: Warning: disabling flag --expose_wasm due to conflicting flags Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 79: unable to open /var/lib/hp/hplip.state: No such file or directory Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 129: validate_plugin_version() Failed to get Plugin version from [/var/lib/hp/hplip.state] Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 173: Plugin version is not matching Mar 10 16:44:34 semiauto hpcups[515382]: prnt/hpcups/HPCupsFilter.cpp 505: m_Job initialization failed with error = 48 Mar 10 16:44:34 semiauto hpcups[515382]: common/utils.c 244: Invalid Library handler pLibHandler = NULL. Mar 10 16:45:01 semiauto CRON[515541]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Mar 10 16:45:09 semiauto gnome-shell[333439]: Window manager warning: Ping serial 447743079 was reused for window W713, previous use was for window 0xc00014. Mar 10 16:45:20 semiauto systemd[4596]: vte-spawn-4d0c2df5-8c91-461c-ac5d-b95a2bc252a9.scope: Consumed 33.860s CPU time. Mar 10 16:45:20 semiauto gnome-shell[333439]: JS ERROR: TypeError: this.actor is null#012_syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:138:25#012onStopped@resource:///org/gnome/shell/ui/windowManager.js:150:35#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:316:60#012_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1596:21#012onStopped@resource:///org/gnome/shell/ui/windowManager.js:1564:39#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22#012_easeActor/<@resource:///org/gnome/shell/ui/environment.js:239:64 Mar 10 16:45:23 semiauto dbus-daemon[680]: [system] Activating service name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.1929' (uid=1000 pid=485631 comm="gnome-control-center printers" label="unconfined") (using servicehelper) Mar 10 16:45:23 semiauto systemd[4596]: app-gnome-virtualbox-495654.scope: Consumed 11min 33.878s CPU time. Mar 10 16:45:23 semiauto dbus-daemon[680]: [system] Successfully activated service 'org.opensuse.CupsPkHelper.Mechanism' Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Settings.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Calculator.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Characters' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Activating service name='org.gnome.Notes.SearchProvider' requested by ':1.23' (uid=1000 pid=333439 comm="/usr/bin/gnome-shell" label="unconfined") Mar 10 16:45:57 semiauto dbus-daemon[332938]: [session uid=1000 pid=332938] Successfully activated service 'org.gnome.Settings.SearchProvider' Make and model auto-reported is: "HP LaserJet Professional m1217nfw MFP, hpcups 3.22.6, requires proprietary plugin" yes, it has commas. URI is reported as: dnssd://HP%20LaserJet%20Professional%20M1217nfw%20MFP._pdl-datastream._tcp.local/ and "location" is aparrently blank. I can troubleshoot further. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop:
[Touch-packages] [Bug 2002445] Re: udev NIC renaming race with mlx5_core driver
Hello Nick, or anyone else affected,
Accepted systemd into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/251.4-1ubuntu7.2 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-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. 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: systemd (Ubuntu Kinetic)
Status: Triaged => Fix Committed
** Tags added: verification-needed verification-needed-kinetic
--
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/2002445
Title:
udev NIC renaming race with mlx5_core driver
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Triaged
Status in systemd source package in Jammy:
Triaged
Status in systemd source package in Kinetic:
Fix Committed
Status in systemd source package in Lunar:
Fix Released
Bug description:
[Impact]
On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core
driver's own configuration of subordinate interfaces. When the kernel wins this
race, the device cannot be renamed as udev has attempted, and this causes
systemd-network-online.target to timeout waiting for links to be configured.
This ultimately results in boot being delayed by about 2 minutes.
[Test Plan]
Repeated launches of Standard_D8ds_v5 instance types will generally hit this
race around 1 in 10 runs. Create a vm snapshot with updated systemd from
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated
systemd. Assert not failure in cloud-init status and no 2 minute delay in
network-online.target.
To check for failure symptom:
- Assert that network-online.target isn't the longest pole from
systemd-analyze blame.
To assert success condition during net rename busy race:
- assert when "eth1" is still the primary device name, that two altnames
are listed (preserving the altname due to the primary NIC rename being hit.
Sample script uses pycloudlib to create modified base image for test
and launches 100 VMs of type Standard_D8ds_v5, counting both successes
and any failures seen.
#!/usr/bin/env python3
# This file is part of pycloudlib. See LICENSE file for license information.
"""Basic examples of various lifecycle with an Azure instance."""
import logging
import json
import pycloudlib
LOG = logging.getLogger()
base_cfg = """#cloud-config
ssh-import-id: [chad.smith, enr0n]
"""
apt_cfg = """
# Add developer PPA
apt:
sources:
systemd-testing:
source: "deb [allow-insecure=yes]
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
# upgrade systemd after cloud-init is nearly done
runcmd:
- apt install systemd udev -y --allow-unauthenticated
"""
debug_systemd_cfg = """
# Create systemd-udev debug override.conf in base image
write_files:
- path: /etc/systemd/system/systemd-networkd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
- path: /etc/systemd/system/systemd-udevd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
LogRateLimitIntervalSec=0
"""
cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
cloud_config2 = base_cfg + debug_systemd_cfg
def debug_systemd_image_launch_overlake_v5_with_snapshot():
"""Test overlake v5 timeouts
test procedure:
- Launch base focal image
- enable ppa:enr0n/systemd-245 and systemd/udev debugging
- cloud-init clean --logs && deconfigure waalinux agent before shutdown
- snapshot a base image
- launch v5 system from snapshot
- check systemd-analyze for expected timeout
"""
client = pycloudlib.Azure(tag="azure")
image_id = client.daily_image(release="focal")
pub_path =
[Touch-packages] [Bug 2004478] Re: systemd-networkd's dhcp4 client ignores local subnet routes
Hello Tuetuopay, or anyone else affected, Accepted systemd into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/251.4-1ubuntu7.2 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- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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: systemd (Ubuntu Kinetic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- 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/2004478 Title: systemd-networkd's dhcp4 client ignores local subnet routes Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Fix Committed Bug description: [Impact] If a DHCP server pushes down a local subnet route with a null gateway, the systemd-networkd DHCP client does not correctly install the route. Instead, the route is ignored. [Test Plan] Taken from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004478/comments/2. * Start a Jammy LXD container: $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash * Create a veth pair: $ ip link add veth0 up type veth peer name veth1 $ ip addr add 172.20.0.1/24 dev veth0 $ cat > /etc/netplan/60-veth1.yaml
[Touch-packages] [Bug 2009034] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2009034/+attachment/5653695/+files/ThreadStacktrace.txt ** Tags added: apport-failed-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2009034 Title: subiquity subcommand crash on apt hash mismatch Status in openssh package in Ubuntu: Invalid Status in subiquity package in Ubuntu: Triaged Bug description: QA Testing daily build 20230302 install failed. Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False) Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False) Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: finish: cmd-in-target: FAIL: curtin command in-target ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: openssh-client 1:9.0p1-1ubuntu8 Uname: Linux 5.19.0-21-generic x86_64 Architecture: amd64 Date: Thu Mar 2 12:13:28 2023 ExecutablePath: /usr/bin/ssh-keygen ExecutableTimestamp: 1666713463 ProcCmdline: ssh-keygen -t rsa -b 4096 -N -f /tmp/snapd3272526883/rsa.key -m PEM ProcCwd: / ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) Signal: 7 SourcePackage: openssh UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2009034/+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 2009034] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/2009034/+attachment/5653694/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2009034 Title: subiquity subcommand crash on apt hash mismatch Status in openssh package in Ubuntu: Invalid Status in subiquity package in Ubuntu: Triaged Bug description: QA Testing daily build 20230302 install failed. Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False) Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False) Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: finish: cmd-in-target: FAIL: curtin command in-target ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: openssh-client 1:9.0p1-1ubuntu8 Uname: Linux 5.19.0-21-generic x86_64 Architecture: amd64 Date: Thu Mar 2 12:13:28 2023 ExecutablePath: /usr/bin/ssh-keygen ExecutableTimestamp: 1666713463 ProcCmdline: ssh-keygen -t rsa -b 4096 -N -f /tmp/snapd3272526883/rsa.key -m PEM ProcCwd: / ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) Signal: 7 SourcePackage: openssh UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2009034/+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 2009034] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2009034/+attachment/5653693/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2009034 Title: subiquity subcommand crash on apt hash mismatch Status in openssh package in Ubuntu: Invalid Status in subiquity package in Ubuntu: Triaged Bug description: QA Testing daily build 20230302 install failed. Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False) Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False) Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: finish: cmd-in-target: FAIL: curtin command in-target ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: openssh-client 1:9.0p1-1ubuntu8 Uname: Linux 5.19.0-21-generic x86_64 Architecture: amd64 Date: Thu Mar 2 12:13:28 2023 ExecutablePath: /usr/bin/ssh-keygen ExecutableTimestamp: 1666713463 ProcCmdline: ssh-keygen -t rsa -b 4096 -N -f /tmp/snapd3272526883/rsa.key -m PEM ProcCwd: / ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) Signal: 7 SourcePackage: openssh UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2009034/+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 2009034] subiquity subcommand crash on apt hash mismatch
StacktraceTop: mulx4x_internal () at crypto/bn/x86_64-mont5.s:2273 bn_sqr8x_internal () at crypto/bn/x86_64-mont5.s:1760 ?? () ?? () ?? () -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2009034 Title: subiquity subcommand crash on apt hash mismatch Status in openssh package in Ubuntu: Invalid Status in subiquity package in Ubuntu: Triaged Bug description: QA Testing daily build 20230302 install failed. Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False) Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False) Mar 02 06:24:14 ubuntu subiquity_log.3098[12985]: finish: cmd-in-target: FAIL: curtin command in-target ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: openssh-client 1:9.0p1-1ubuntu8 Uname: Linux 5.19.0-21-generic x86_64 Architecture: amd64 Date: Thu Mar 2 12:13:28 2023 ExecutablePath: /usr/bin/ssh-keygen ExecutableTimestamp: 1666713463 ProcCmdline: ssh-keygen -t rsa -b 4096 -N -f /tmp/snapd3272526883/rsa.key -m PEM ProcCwd: / ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) Signal: 7 SourcePackage: openssh UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2009034/+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 2009756] Re: backups fail since latest rsync security update
Great, I'll release the updates monday morning. Thanks for testing! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009756 Title: backups fail since latest rsync security update Status in backintime package in Ubuntu: Fix Released Status in rsync package in Ubuntu: New Status in backintime source package in Jammy: In Progress Status in rsync source package in Jammy: New Status in backintime source package in Kinetic: In Progress Status in rsync source package in Kinetic: New Status in backintime source package in Lunar: Fix Released Status in rsync source package in Lunar: New Bug description: Backintime uses rsync to perform updates. Unfortunately there is an incompatibility between the currently released version of backintime and rsync >= 3.2.4 (see https://github.com/bit- team/backintime/issues/1247) Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke backintime backups. The symptom is an error message like this: Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22 /tmp/tmpxilwcwk4/ u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262"" returns 3 | rsync: change_dir#3 "/data/home/user//"./backintime/switch/aurelien/1" failed: No such file or directory (2) The workaround described in the GitHub issue works (passing `--old- args` to rsync), but maybe it would be better if the backintime package did this automatically? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: backintime-common 1.2.1-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 8 23:19:02 2023 InstallationDate: Installed on 2021-06-23 (623 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: backintime UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+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 2009756] Re: backups fail since latest rsync security update
Looks good now, works for me on jammy. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009756 Title: backups fail since latest rsync security update Status in backintime package in Ubuntu: Fix Released Status in rsync package in Ubuntu: New Status in backintime source package in Jammy: In Progress Status in rsync source package in Jammy: New Status in backintime source package in Kinetic: In Progress Status in rsync source package in Kinetic: New Status in backintime source package in Lunar: Fix Released Status in rsync source package in Lunar: New Bug description: Backintime uses rsync to perform updates. Unfortunately there is an incompatibility between the currently released version of backintime and rsync >= 3.2.4 (see https://github.com/bit- team/backintime/issues/1247) Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke backintime backups. The symptom is an error message like this: Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22 /tmp/tmpxilwcwk4/ u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262"" returns 3 | rsync: change_dir#3 "/data/home/user//"./backintime/switch/aurelien/1" failed: No such file or directory (2) The workaround described in the GitHub issue works (passing `--old- args` to rsync), but maybe it would be better if the backintime package did this automatically? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: backintime-common 1.2.1-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 8 23:19:02 2023 InstallationDate: Installed on 2021-06-23 (623 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: backintime UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+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 1741775] Re: bad symlink "/etc/resolvconf/resolv.conf.d/original"
resolvconf has been removed from Ubuntu in 22.10 and later in favor of the systemd-resolved implementation, so this bug is fixed for later releases. Installing resolvconf in 22.04 is also discouraged. ** Changed in: resolvconf (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1741775 Title: bad symlink "/etc/resolvconf/resolv.conf.d/original" Status in resolvconf package in Ubuntu: Fix Released Bug description: Ubuntu 17.10 amd_64 resolvconf 1.79ubuntu8 The symlink at "/etc/resolvconf/resolv.conf.d/original" points to "../run/systemd/resolve/stub-resolv.conf". This is a broken link as the relative path does not exist. This causes resolvconf to improperly (re-)generate "/run/resolvconf/resolv.conf". The link should probably instead point to the absolute path "/run/systemd/resolve/stub- resolv.conf". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1741775/+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 2009808] Re: Doesn't display the correct livepatch service status
** Merge proposal linked: https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/438710 -- 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/2009808 Title: Doesn't display the correct livepatch service status Status in software-properties package in Ubuntu: Triaged Status in ubuntu-advantage-tools package in Ubuntu: In Progress Bug description: Starting a focal VM which didn't get updated the livepatch icon in the panel shows an orange warning and the popdown display a string saying it hit an error fetching the status $ canonical-livepatch status last check: 58 seconds ago kernel: 5.15.0-56.62~20.04.1-generic server check-in: failed: livepatch check failed: unauthorized patch state: ✗ kernel version not supported The software-properties tab doesn't give any clue about that though, maybe it should? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2009808/+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 2009918] Re: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/lib/x86_64-linux-gnu/dri/vm
** Changed in: mesa (Ubuntu)
Status: Incomplete => New
--
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/2009918
Title:
package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de
« ./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une
nouvelle version: Aucun espace disponible sur le périphérique
Status in mesa package in Ubuntu:
New
Bug description:
Running inside a VM (KVM) from a remastered ISO
The screen also show some artifacts horizontal dotted lines which disappear
after a second or two.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5json: {
CasperVersion: 1.445.1
CompositorRunning: None
Date: Fri Mar 10 08:21:08 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
ExtraDebuggingInterest: No
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
InstallationDate: Installed on 2022-02-22 (380 days ago)
InstallationMedia:
LiveMediaBuild: Systemback Live (MobiOffice) - Release amd64
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper
initrd=/casper/initrd.gz quiet splash
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
SourcePackage: mesa
Title: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-focal
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-focal
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009918/+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 2009918] Re: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/lib/x86_64-linux-gnu/dri/vm
Indeed that's the French translation of "No space left on the device".
As I explained in the comments, I have remastered an ISO (of 20.04) to
connect to my professional workspace (VPN Cisco AnyConnect and Citrix),
because I don't want those 2 closed source things to mess up with my
environment.
I am using that ISO inside a VM, via KVM/QEMU.
So the "bug" would be that mesa would try to install anything. That
obviously could fail considering the ISO runs in AUFS mode, and the
operation on system file is somehow restricted even more due to the
read-only part of the mount.
It does not happen all the times. Sometimes, it works just fine, does
not complain or spit out any error and does not display any artifacts.
Other times, I get the error.
This is anyway very low priority, it is not really a big deal, I just ignore
the errors and artifacts when they happen!
--
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/2009918
Title:
package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de
« ./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une
nouvelle version: Aucun espace disponible sur le périphérique
Status in mesa package in Ubuntu:
Incomplete
Bug description:
Running inside a VM (KVM) from a remastered ISO
The screen also show some artifacts horizontal dotted lines which disappear
after a second or two.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5json: {
CasperVersion: 1.445.1
CompositorRunning: None
Date: Fri Mar 10 08:21:08 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
ExtraDebuggingInterest: No
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
InstallationDate: Installed on 2022-02-22 (380 days ago)
InstallationMedia:
LiveMediaBuild: Systemback Live (MobiOffice) - Release amd64
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper
initrd=/casper/initrd.gz quiet splash
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
SourcePackage: mesa
Title: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-focal
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-focal
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this
[Touch-packages] [Bug 2009808] Re: Doesn't display the correct livepatch service status
Hi Nathan, I suggest that if you see "status" == "warning" then look at the "warning.code" field. That will be a short string unique to the warning situation that won't change. It will be different for different warnings in the future, though currently the only warning is the one presented in my comment above. So I suggest you keep a translatable string for each known "warning.code" and look up that string based on the code field. If you don't have a string for a certain code, then you can fallback to "warning.message" (or "description_override" if it exists) as you see fit. These will always be english but at least will be human readable strings for the situation. -- 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/2009808 Title: Doesn't display the correct livepatch service status Status in software-properties package in Ubuntu: Triaged Status in ubuntu-advantage-tools package in Ubuntu: In Progress Bug description: Starting a focal VM which didn't get updated the livepatch icon in the panel shows an orange warning and the popdown display a string saying it hit an error fetching the status $ canonical-livepatch status last check: 58 seconds ago kernel: 5.15.0-56.62~20.04.1-generic server check-in: failed: livepatch check failed: unauthorized patch state: ✗ kernel version not supported The software-properties tab doesn't give any clue about that though, maybe it should? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2009808/+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 1923464] Re: ideally should boot rootfs from a matching hard drive
My understanding is that this has not been addressed yet. We need to actually make use of that data even if UEFI gives us that. ** Changed in: initramfs-tools (Ubuntu) Status: Invalid => New ** 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/1923464 Title: ideally should boot rootfs from a matching hard drive Status in cloud-images: Invalid Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: New Status in systemd package in Ubuntu: New Status in u-boot package in Ubuntu: Invalid Status in u-boot-menu package in Ubuntu: Invalid Status in grub2 source package in Impish: Invalid Status in initramfs-tools source package in Impish: Invalid Status in systemd source package in Impish: Invalid Status in u-boot source package in Impish: Invalid Status in u-boot-menu source package in Impish: Invalid Bug description: Ideally we should strive to boot rootfs from a matching hard drive. I.e. if we are booting rootfs by UUID, we should try to find the one that came from the same drive as where ESP (UEFI) came from, or u-boot spl / u-boot got loaded from (loader1/loader2). Such that for example, when booted from external usb stick, rootfs from there is mounted. Or when booted from internal drive whilst a dd backup is attached over usb, rootfs is loaded from the internal drive not from the usb attached backup. This would need: * u-boot to export the drive it loaded extlinux.conf / bootscript from, and pass it on kernel command line * grub to export the device UUID it got loaded from (from the BootServices EFI table) and pass it on the kernel command line or via runtime EFI variable * sdboot already does that I believe, but not sure if initramfs-tools consumes the sdboot provided information * initramfs-tools to consume above and sort the discovered devices based on that, when deciding what to mount as rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1923464/+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 2009808] Re: Doesn't display the correct livepatch service status
Should it display the message as whatever UA gives us in its description field (here, "Current kernel is not supported") or do we want to write our own message? The former would render the solution untranslatable, correct? -- 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/2009808 Title: Doesn't display the correct livepatch service status Status in software-properties package in Ubuntu: Triaged Status in ubuntu-advantage-tools package in Ubuntu: In Progress Bug description: Starting a focal VM which didn't get updated the livepatch icon in the panel shows an orange warning and the popdown display a string saying it hit an error fetching the status $ canonical-livepatch status last check: 58 seconds ago kernel: 5.15.0-56.62~20.04.1-generic server check-in: failed: livepatch check failed: unauthorized patch state: ✗ kernel version not supported The software-properties tab doesn't give any clue about that though, maybe it should? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2009808/+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 1923464] Re: ideally should boot rootfs from a matching hard drive
** Changed in: cloud-images Status: New => Invalid ** Changed in: grub2 (Ubuntu) Status: New => Invalid ** Changed in: grub2 (Ubuntu Impish) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools (Ubuntu Impish) Status: New => Invalid ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu Impish) Status: New => Invalid ** Changed in: u-boot (Ubuntu) Status: New => Invalid ** Changed in: u-boot (Ubuntu Impish) Status: New => Invalid ** Changed in: u-boot-menu (Ubuntu) Status: New => Invalid ** Changed in: u-boot-menu (Ubuntu Impish) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923464 Title: ideally should boot rootfs from a matching hard drive Status in cloud-images: Invalid Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Invalid Status in u-boot-menu package in Ubuntu: Invalid Status in grub2 source package in Impish: Invalid Status in initramfs-tools source package in Impish: Invalid Status in systemd source package in Impish: Invalid Status in u-boot source package in Impish: Invalid Status in u-boot-menu source package in Impish: Invalid Bug description: Ideally we should strive to boot rootfs from a matching hard drive. I.e. if we are booting rootfs by UUID, we should try to find the one that came from the same drive as where ESP (UEFI) came from, or u-boot spl / u-boot got loaded from (loader1/loader2). Such that for example, when booted from external usb stick, rootfs from there is mounted. Or when booted from internal drive whilst a dd backup is attached over usb, rootfs is loaded from the internal drive not from the usb attached backup. This would need: * u-boot to export the drive it loaded extlinux.conf / bootscript from, and pass it on kernel command line * grub to export the device UUID it got loaded from (from the BootServices EFI table) and pass it on the kernel command line or via runtime EFI variable * sdboot already does that I believe, but not sure if initramfs-tools consumes the sdboot provided information * initramfs-tools to consume above and sort the discovered devices based on that, when deciding what to mount as rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1923464/+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 2009756] Re: backups fail since latest rsync security update
I have fixed the typo, and have uploaded new packages to the PPA listed above. I've run a successful backup with them on both jammy and kinetic. Could you please confirm they fix the issue for you? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009756 Title: backups fail since latest rsync security update Status in backintime package in Ubuntu: Fix Released Status in rsync package in Ubuntu: New Status in backintime source package in Jammy: In Progress Status in rsync source package in Jammy: New Status in backintime source package in Kinetic: In Progress Status in rsync source package in Kinetic: New Status in backintime source package in Lunar: Fix Released Status in rsync source package in Lunar: New Bug description: Backintime uses rsync to perform updates. Unfortunately there is an incompatibility between the currently released version of backintime and rsync >= 3.2.4 (see https://github.com/bit- team/backintime/issues/1247) Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke backintime backups. The symptom is an error message like this: Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22 /tmp/tmpxilwcwk4/ u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262"" returns 3 | rsync: change_dir#3 "/data/home/user//"./backintime/switch/aurelien/1" failed: No such file or directory (2) The workaround described in the GitHub issue works (passing `--old- args` to rsync), but maybe it would be better if the backintime package did this automatically? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: backintime-common 1.2.1-3ubuntu0.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 8 23:19:02 2023 InstallationDate: Installed on 2021-06-23 (623 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: backintime UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+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 2009706] Re: rsync 3.1.2-2.1ubuntu1.6 breaks compatibility with unison 2.48.4-1ubuntu1 on Bionic
That appears to work around the problem, yes, changing them to. copyprog = rsync -a -A -X --rsh=ssh --inplace --compress --old-args copyprogrest = rsync -a -A -X --rsh=ssh --partial --inplace --compress --old-args -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2009706 Title: rsync 3.1.2-2.1ubuntu1.6 breaks compatibility with unison 2.48.4-1ubuntu1 on Bionic Status in rsync package in Ubuntu: New Status in unison package in Ubuntu: New Bug description: Rsync 3.1.2-2.1ubuntu1.6, when used by Unison using the copyprog option in Unison, produces an error message and fails to sync files. Rsync 3.1.2-2.1ubuntu1 succeeds in syncing files. I believe Rsync 3.1.2-2.1ubuntu1.5 succeeded but I no longer have the .deb file to test with. Steps to reproduce: Create a unison profile similar to the one given below, to sync a folder between a local machine and a remote ssh server. Both client and server need the same Ubuntu and Unison versions, and I used unpassphrased SSH keys for authentication. Place a test file in the folder to be synced, then run 'unison profilename'. Note that I have redacted domains in the below. Unison profile: label = Test Profile root = /root/unison-test root = ssh://fs2b.our.domain.org.uk//root/unison-test # run repeatedly and fully automatically auto = true batch = true copyonconflict = true #repeat = 60 # the copy program must be manually specified in order to sync ACLs copythreshold=0 copyprog = rsync -a -A -X --rsh=ssh --inplace --compress copyprogrest = rsync -a -A -X --rsh=ssh --partial --inplace --compress # general settings group = true owner = true #path = sharedfolder #path = users perms = -1 sortbysize = true times = true Unison output with rsync 3.1.2-2.1ubuntu1.6 root@fs72a:~# unison fs2b_unisontest -debug all [startup] Preferences: ui = graphic host = server = false prefsdocs = false doc = version = false silent = false dumbtty = false testserver = false rest = fs2b_unisontest showprev = false selftest = false confirmmerge = false retry = 0 repeat = contactquietly = false key = label = Syncs P and S drives between fs72a and fs2a expert = false height = 15 auto = true maxthreads = 0 maxsizethreshold = -1 prefer = force = sortnewfirst = false sortbysize = true keeptempfilesaftermerge = false diff = diff -u CURRENT2 CURRENT1 copyonconflict = true backupdir = maxbackups = 2 backups = false backupsuffix = backupprefix = .bak.$VERSION. backuploc = central copymax = 1 copyquoterem = default copythreshold = 0 copyprogrest = rsync -a -A -X --rsh=ssh --partial --inplace --compress copyprog = rsync -a -A -X --rsh=ssh --inplace --compress rsync = true fastcheck = default ignorelocks = false dumparchives = false showarchive = false rootsName = ignorearchives = false fastercheckUNSAFE = false fat = false allHostsAreRunningWindows = false someHostIsRunningWindows = false confirmbigdel = true batch = true root = ssh://fs2b.our.domain.org.uk//root/unison-test root = /root/unison-test killserver = false halfduplex = false stream = true addversionno = false servercmd = sshargs = rshargs = rshcmd = rsh sshcmd = ssh xferbycopying = true sshversion = clientHostName = fs72a ignoreinodenumbers = false links-aux = true links = default times = true group = true owner = true numericids = false dontchmod = false perms = -1 watch = true rsrc-aux = false rsrc = default maxerrors = 1 unicodeCS = false unicodeEnc = false unicode = default someHostIsInsensitive = false ignorecase = default timers = false terse = false logfile = /root/.unison/unison.log log = true debugtimes = false debug = all addprefsto = Contacting server... [remote] Shell connection: ssh (ssh, fs2b.our.domain.org.uk, -e, none, unison, -server) [globals] Checking path '' for expansions Connected [//fs2b//root/unison-test -> //fs72a//root/unison-test] [startup] Roots: /root/unison-test ssh://fs2b.our.domain.org.uk//root/unison-test i.e. /root/unison-test ssh://fs2b.our.domain.org.uk//root/unison-test i.e. (in canonical order) /root/unison-test //fs2b//root/unison-test [props] Setting permission mask to (7 and ) [stasher] initBackupsLocal [stasher] d = / [stasher] Prefix and suffix regexps for backup filenames have been updated [server: stasher] initBackupsLocal [server: stasher] d = / [server: stasher] Prefix and suffix regexps for backup filenames have been updated Looking for changes [ui] temp: Globals.paths = [update] Loading archive from /root/.unison/areaa7785bb2204bed0cb7af3360b3c323 [update] Setting archive for
[Touch-packages] [Bug 2009918] Re: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/lib/x86_64-linux-gnu/dri/vm
Aucun espace disponible sur le périphérique
->
No space left on the device
So it looks you are low in free space on disk, is that correct?
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
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/2009918
Title:
package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de
« ./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une
nouvelle version: Aucun espace disponible sur le périphérique
Status in mesa package in Ubuntu:
Incomplete
Bug description:
Running inside a VM (KVM) from a remastered ISO
The screen also show some artifacts horizontal dotted lines which disappear
after a second or two.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5json: {
CasperVersion: 1.445.1
CompositorRunning: None
Date: Fri Mar 10 08:21:08 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
ExtraDebuggingInterest: No
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
InstallationDate: Installed on 2022-02-22 (380 days ago)
InstallationMedia:
LiveMediaBuild: Systemback Live (MobiOffice) - Release amd64
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper
initrd=/casper/initrd.gz quiet splash
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
SourcePackage: mesa
Title: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-focal
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-focal
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009918/+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 2004241] Re: Update to glib >= 2.75.1
** 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 glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2004241 Title: Update to glib >= 2.75.1 Status in glib2.0 package in Ubuntu: Fix Released Bug description: Update to glib >= 2.75.1 because that's what mutter 44 now requires. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+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 2007623] Re: Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main)
This bug was fixed in the package grilo-plugins - 0.3.15-2ubuntu1 --- grilo-plugins (0.3.15-2ubuntu1) lunar; urgency=medium * Merge from Debian unstable (LP: #2007623). Remaining change: - Split package into -base and -extra (Closes: #805609) grilo-plugins (0.3.15-2) unstable; urgency=medium * debian/control: - Stop recommending dleyna-server (Closes: #1030125). - Update Standards-Version to 4.6.2 (no changes). * debian/copyright: - Update copyright years. -- Amin Bandali Thu, 16 Feb 2023 19:20:02 -0500 ** Changed in: grilo-plugins (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 grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/2007623 Title: Merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main) Status in grilo-plugins package in Ubuntu: Fix Released Bug description: Please merge grilo-plugins 0.3.15-2 (universe) from Debian unstable (main) Changelog entries since current lunar version 0.3.15-1ubuntu1: grilo-plugins (0.3.15-2) unstable; urgency=medium * debian/control: - Stop recommending dleyna-server (Closes: #1030125). - Update Standards-Version to 4.6.2 (no changes). * debian/copyright: - Update copyright years. -- Alberto Garcia Tue, 31 Jan 2023 16:45:49 +0100 Remaining differences with grilo-plugins from Debian unstable: - Split package into -base and -extra (Closes: #805609) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/2007623/+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 2009918] [NEW] package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/lib/x86_64-linux-gnu/dri/
Public bug reported:
Running inside a VM (KVM) from a remastered ISO
The screen also show some artifacts horizontal dotted lines which disappear
after a second or two.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5json: {
CasperVersion: 1.445.1
CompositorRunning: None
Date: Fri Mar 10 08:21:08 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
ExtraDebuggingInterest: No
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
InstallationDate: Installed on 2022-02-22 (380 days ago)
InstallationMedia:
LiveMediaBuild: Systemback Live (MobiOffice) - Release amd64
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper
initrd=/casper/initrd.gz quiet splash
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
SourcePackage: mesa
Title: package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-focal
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-focal
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package focal ubuntu
--
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/2009918
Title:
package libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 failed to
install/upgrade: impossible de créer un lien symbolique de secours de
« ./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une
nouvelle version: Aucun espace disponible sur le périphérique
Status in mesa package in Ubuntu:
New
Bug description:
Running inside a VM (KVM) from a remastered ISO
The screen also show some artifacts horizontal dotted lines which disappear
after a second or two.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5json: {
CasperVersion: 1.445.1
CompositorRunning: None
Date: Fri Mar 10 08:21:08 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: impossible de créer un lien symbolique de secours de «
./usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so » avant d'installer une nouvelle
version: Aucun espace disponible sur le périphérique
ExtraDebuggingInterest: No
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card
