[Touch-packages] [Bug 1972944] Re: server becomes desktop unintentionally
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libnotify (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1972944 Title: server becomes desktop unintentionally Status in libnotify package in Ubuntu: Confirmed Bug description: Ubuntu Release: 20.04 package version: 0.7.9-1ubuntu2 What happened: when libnotify4 is installed by apt, desktop environment is also installed. Explanation: I think it is fair to say that, a user of Ubuntu server don't want unintentional installation of desktop environment. The problem is discussed by others: https://github.com/ros-perception/perception_pcl/issues/355 https://gitlab.kitware.com/vtk/vtk/-/issues/18489#note_1156770 Under my research, the central reason is that, gnome-shell has been added to libnotify4's Recommended dependency in focal (Ubuntu20.04). gnome-shell should not be Recommended dependency for a pure library, causing unintentional installation. Actually, gnome-shell in libnotify4's dependency has dropped from Recommended to Suggested in jammy (Ubuntu22.04). This change should be treated as error fixing and be updated to 20.04 as well. current workaround: manually install the problematic libnotify4 in early setting >>sudo apt install libnotify4 --no-install-recommends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1972944/+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 2008733] Re: Window leak-through
Thanks for the bug report. Unfortunately your graphics packages are not from Ubuntu, they are from System76. So the bug should probably be reported to them. Although I would still be curious to see a photo or video of the issue. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/2008733 Title: Window leak-through Status in Ubuntu: Invalid Bug description: I notice that since upgrading to Ubuntu 22.04 LTS I am getting a lot of leak-through with open windows. That is when I move the mouse over a window it brings up an informational popup from a window obscured by the active window. Additionally, the active edges of the windows seem to have large boundaries around the active window. That is if I click on a window showing on the screen, but the edge is close to the active window, it will not activate the window on which I clicked. There was a little of the behavior in 20.04 when the windows edges were close, but it is extreme in 22.04 in that even with a 15 to 20 mm of the underlying window showing it will not recognize that I have selected a different active window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.0.12-76060006-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 27 12:31:43 2023 DistUpgraded: 2022-12-01 16:49:16,796 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6509] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b5a7 Chicony Electronics Co., Ltd Chicony USB 2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76, Inc. Gazelle ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.12-76060006-generic root=UUID=ac9c0a24-9264-4620-9dca-59a3e7976588 ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-12-02 (87 days ago) dmi.bios.date: 09/09/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02RSA2-1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle dmi.board.vendor: System76, Inc. dmi.board.version: gaze11 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02RSA2-1:bd09/09/2016:br5.11:svnSystem76,Inc.:pnGazelle:pvrgaze11:rvnSystem76,Inc.:rnGazelle:rvrgaze11:cvnSystem76,Inc.:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Gazelle dmi.product.sku: Not Applicable dmi.product.version: gaze11 dmi.sys.vendor: System76, Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-10-20T08:48:37.54 version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1pop0~1648761328~22.04~166056a~dev version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.4-1pop1~1675300365~22.04~6b66c01~dev version.libgl1-mesa-glx: libgl1-mesa-glx 22.3.4-1pop1~1675300365~22.04~6b66c01~dev version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 xserver.bootTime: Sat Jan 19 19:22:02 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1191 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2008733/+subscriptions -- Mailing list:
[Touch-packages] [Bug 2002445] Re: udev NIC renaming race with mlx5_core driver
** Description changed:
[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"
+ 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
+ - 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
-
+ 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
+ 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 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")
- 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 = "/home/ubuntu/.ssh/id_rsa.pub"
+ priv_path = "/home/ubuntu/.ssh/id_rsa"
- image_id = client.daily_image(release="focal")
- pub_path = "/home/ubuntu/.ssh/id_rsa.pub"
- priv_path = "/home/ubuntu/.ssh/id_rsa"
+ client.use_key(pub_path, priv_path)
- client.use_key(pub_path, priv_path)
+ base_instance = client.launch(
+ image_id=image_id,
+ instance_type="Standard_DS1_v2",
+ user_data=cloud_config.format(defer="true"),
+ )
- base_instance = client.launch(
- image_id=image_id,
- instance_type="Standard_DS1_v2",
- user_data=cloud_config.format(defer="true"),
- )
+ LOG.info(f"base instance: ssh ubuntu@{base_instance.ip}")
+ base_instance.wait()
+ LOG.info(base_instance.execute("apt cache policy systemd"))
+ snapshotted_image_id = client.snapshot(base_instance)
- LOG.info(f"base instance: ssh ubuntu@{base_instance.ip}")
- base_instance.wait()
- LOG.info(base_instance.execute("apt cache
[Touch-packages] [Bug 2002445] Re: udev NIC renaming race with mlx5_core driver
** Description changed:
[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]
- Since this is a race condition, we need to boot many instances before we see
the issue. The Ubuntu Server team will help coordinate the testing at scale to
confirm the fix.
+ 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
+
+
+ """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 = "/home/ubuntu/.ssh/id_rsa.pub"
+ priv_path = "/home/ubuntu/.ssh/id_rsa"
+
+ client.use_key(pub_path, priv_path)
+
+ base_instance = client.launch(
+ image_id=image_id,
+ instance_type="Standard_DS1_v2",
+ user_data=cloud_config.format(defer="true"),
+ )
+
+ LOG.info(f"base instance: ssh ubuntu@{base_instance.ip}")
+ base_instance.wait()
+ LOG.info(base_instance.execute("apt cache policy systemd"))
+ snapshotted_image_id = client.snapshot(base_instance)
+
+ reproducer = False
+ tries = 0
+ success_count_with_race = 0
+ success_count_no_race = 0
+ failure_count_network_delay = 0
+ failure_count_no_altnames = 0
+ TEST_SUMMARY_TMPL = """
+ - Test run complete: {tries} attempted -
+ Successes without rename race: {success_count_no_race}
+ Successes with rename race and preserved altname:
{success_count_with_race_persist_altname}
+ Failures due to network delay: {failure_count_network_delay}
+ Failures due to no altnames persisted: {failure_count_no_altnames}
+ ===
+ """
+ while tries < 10 and not reproducer:
+ tries += 1
+ new_instance = client.launch(
+ image_id=snapshotted_image_id,
+ instance_type="Standard_D8ds_v5",
+ user_data=cloud_config.format(defer="false"),
+ )
+ # breadcrumb for us pycloudlib/Azure will reuse available IPs
+ new_instance.wait()
+ blame = new_instance.execute("systemd-analyze blame").splitlines()
+ LOG.info(f"--- Attempt {tries} ssh ubuntu@{new_instance.ip} Blame:
{blame[0]}")
+ ip_addr = json.loads(new_instance.execute("ip -j addr").stdout)
+ for d in ip_addr:
+
[Touch-packages] [Bug 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Sorry to come back to this, but I'm now trying to netboot Ubuntu 22.04.2, having found the above mentioned work-around for 20.04. Something has changed: I can no longer netboot from NFSv4 by replacing /usr/lib/klibc/bin/nfsmount with an NFSv4-friendly hack. I am now getting the same error messages that nfsmount used to generate, but I have discovered that /usr/lib/klibc/bin/kinit also generates them. So I am guessing that in 22.04 kinit has taken over part of the work the nfsmount performed in 20.04. Any thoughts? I'll try to take a look at kinit tomorrow and see if I can find another work-around. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in klibc package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1954716/+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 1792811] Re: Transmission-gtk startup crash: doesn't start on 18.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: transmission (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792811 Title: Transmission-gtk startup crash: doesn't start on 18.10 Status in gtk+3.0 package in Ubuntu: Confirmed Status in transmission package in Ubuntu: Confirmed Bug description: It's impossibile to run transmission-gtk (segmentation fault). transmission-gtk 2.94 (d8e60ee44f) warning: core file may not match specified executable file. [New LWP 19206] [New LWP 19207] [New LWP 19210] [New LWP 19209] [New LWP 19211] [New LWP 19213] [New LWP 19212] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `transmission-gtk /tmp/mozilla_intilinux0/edubuntu-12.04.5-dvd-i386.iso.torrent'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fbbb9be123f in gtk_css_node_ensure_style (cssnode=0x5594cd1f1a20, current_time=current_time@entry=8576248389) at ../../../../gtk/gtkcssnode.c:987 987 ../../../../gtk/gtkcssnode.c: No such file or directory. [Current thread is 1 (Thread 0x7fbbb14c6c80 (LWP 19206))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1792811/+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 1792811] Re: Transmission-gtk startup crash: doesn't start on 18.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792811 Title: Transmission-gtk startup crash: doesn't start on 18.10 Status in gtk+3.0 package in Ubuntu: Confirmed Status in transmission package in Ubuntu: Confirmed Bug description: It's impossibile to run transmission-gtk (segmentation fault). transmission-gtk 2.94 (d8e60ee44f) warning: core file may not match specified executable file. [New LWP 19206] [New LWP 19207] [New LWP 19210] [New LWP 19209] [New LWP 19211] [New LWP 19213] [New LWP 19212] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `transmission-gtk /tmp/mozilla_intilinux0/edubuntu-12.04.5-dvd-i386.iso.torrent'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fbbb9be123f in gtk_css_node_ensure_style (cssnode=0x5594cd1f1a20, current_time=current_time@entry=8576248389) at ../../../../gtk/gtkcssnode.c:987 987 ../../../../gtk/gtkcssnode.c: No such file or directory. [Current thread is 1 (Thread 0x7fbbb14c6c80 (LWP 19206))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1792811/+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
I have confirmed this is present in Jammy. The fix is present in Kinetic and Lunar. ** Also affects: systemd (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Jammy) Status: New => Triaged ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Low -- 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: Triaged Status in systemd source package in Kinetic: Fix Released Bug 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
** Changed in: systemd (Ubuntu Lunar) Status: New => Fix Committed -- 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 Committed Status in systemd source package in Focal: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: New Status in systemd source package in Lunar: Fix Committed 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] Since this is a race condition, we need to boot many instances before we see the issue. The Ubuntu Server team will help coordinate the testing at scale to confirm the fix. [Where problems could occur] The patches effectively make it so that if a interface cannot be renamed from udev, then the new name is left as an alternative name as a fallback. If problems occur, it would be related to device renaming, and particularly related to the devices alternative names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2002445/+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 2008733] [NEW] Window leak-through
Public bug reported: I notice that since upgrading to Ubuntu 22.04 LTS I am getting a lot of leak-through with open windows. That is when I move the mouse over a window it brings up an informational popup from a window obscured by the active window. Additionally, the active edges of the windows seem to have large boundaries around the active window. That is if I click on a window showing on the screen, but the edge is close to the active window, it will not activate the window on which I clicked. There was a little of the behavior in 20.04 when the windows edges were close, but it is extreme in 22.04 in that even with a 15 to 20 mm of the underlying window showing it will not recognize that I have selected a different active window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.0.12-76060006-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 27 12:31:43 2023 DistUpgraded: 2022-12-01 16:49:16,796 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6509] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b5a7 Chicony Electronics Co., Ltd Chicony USB 2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76, Inc. Gazelle ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.12-76060006-generic root=UUID=ac9c0a24-9264-4620-9dca-59a3e7976588 ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-12-02 (87 days ago) dmi.bios.date: 09/09/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02RSA2-1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle dmi.board.vendor: System76, Inc. dmi.board.version: gaze11 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02RSA2-1:bd09/09/2016:br5.11:svnSystem76,Inc.:pnGazelle:pvrgaze11:rvnSystem76,Inc.:rnGazelle:rvrgaze11:cvnSystem76,Inc.:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Gazelle dmi.product.sku: Not Applicable dmi.product.version: gaze11 dmi.sys.vendor: System76, Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-10-20T08:48:37.54 version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1pop0~1648761328~22.04~166056a~dev version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.4-1pop1~1675300365~22.04~6b66c01~dev version.libgl1-mesa-glx: libgl1-mesa-glx 22.3.4-1pop1~1675300365~22.04~6b66c01~dev version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 xserver.bootTime: Sat Jan 19 19:22:02 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1191 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages 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/2008733 Title: Window leak-through Status in xorg package in Ubuntu: New Bug description: I notice that since upgrading to Ubuntu 22.04 LTS I am getting a lot of leak-through with open windows. That is when I move the mouse over a window it brings up an informational popup from a window obscured by the active window. Additionally, the active edges of the windows seem to have large boundaries around the active window. That is if I click on a window showing on the screen, but the edge is close to the active window, it will not
[Touch-packages] [Bug 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04
If anyone arrived here looking for a solution for Fedora, here it is: Edit /etc/crypto-policies/back-ends/opensslcnf.config Add this line before [openssl_init]: Options = UnsafeLegacyRenegotiation If you're wondering why this is needed, take your GlobalProtect portal address and check it at https://www.ssllabs.com/ssltest "There is no support for secure renegotiation" is what you're working around. I'm running Palo Alto Networks GlobalProtect 6.0.4-28 (UI version) on Fedora Linux 37 (Workstation Edition). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960268 Title: SSL handshake failed - VPN SSL broken in 22.04 Status in openssl package in Ubuntu: Expired Bug description: I'm trying to connect with global protect VPN but fails at login with: SSL handshake failed Failed to load URL https://... QtNetwork Error 6 Another VPN client does work but the rdp connection to a remote server fails with: transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session impish Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144
** Description changed: + [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 + armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz -- 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: Triaged 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 1926139] Re: dhclient: thread concurrency race leads to DHCPOFFER packets not being received
This bug was fixed in the package isc-dhcp - 4.4.1-2.1ubuntu5.20.04.5 --- isc-dhcp (4.4.1-2.1ubuntu5.20.04.5) focal; urgency=medium [ Mauricio Faria de Oliveira ] * Prevent race condition that might ignore DHCP OFFERs/ACKs when dhclient receives DHCP traffic noise. (LP: #1926139) The previous/racy behavior can be switched back on with the 'DHCP_FD_FLAGS_POKE=0' environment variable or the 'dhcp.fd_flags_poke=0' kernel cmdline option. - d/p/lp1926139-watch-socket-fd-later.patch: fix, switches. - d/apparmor/sbin.dhclient,usr.sbin.dhcpd: /proc/cmdline r. [ Steve Langasek ] * Include /etc/dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes in the initramfs. (LP: #1937110) - d/initramfs-tools/share/hooks/zz-dhclient: copy_exec it. -- Mauricio Faria de Oliveira Tue, 31 Jan 2023 19:10:35 -0300 ** Changed in: isc-dhcp (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1926139 Title: dhclient: thread concurrency race leads to DHCPOFFER packets not being received Status in bind9-libs package in Ubuntu: Won't Fix Status in isc-dhcp package in Ubuntu: Invalid Status in isc-dhcp source package in Focal: Fix Released Status in isc-dhcp source package in Jammy: Fix Released Bug description: [Impact] * Occasionally, during instance boot or machine start-up, dhclient will attempt to acquire a dhcp lease and fail, leaving the instance with no IP address and making it unreachable. * This happens about once every 100 reboots on bare metal, or affecting between ~0.3% to 2% of deployments on Azure (comment #2). * Azure uses dhclient called from cloud-init instead of systemd-networkd, and this is causing issues with larger deployments. * The logs of an affected dhclient produce the following: Listening on LPF/enp1s0/52:54:00:1c:d7:00 Sending on LPF/enp1s0/52:54:00:1c:d7:00 Sending on Socket/fallback DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... ... (omitting 20 similar lines) ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... No DHCPOFFERS received. No working leases in persistent database - sleeping. * This only impacts Focal and Jammy, where bind9-libs are multi-threaded (Bionic/earlier and Kinetic/later are single-threaded). * The actual problem is dhclient containing a thread concurrency race condition, and when the race occurs, the read socket is incorrectly/prematurely unwatched because required structures are not yet consistent, thus dhclient does not read any DHCPOFFER replies. * Detailed analysis of the issue is in comment #17. [Fix] * Prevent the race condition by starting to watch the read socket after required structures are consistent. * The fix has been tested in Azure w/ 13500 instances, and no errors have been observed (previously: 0.4%). * Anyway, in case regressions are observed, the patch introduces 2 switches to revert to previous behavior, which can be applied per-process or system-wide: - DHCP_FD_FLAGS_POKE=0 environment variable - dhcp.fd_flags_poke=0 kernel cmdline option * (Previous approaches/discussions included reverting bind9-libs to single-threaded, but we concluded it would have more regression risk than the expected [some bits in comment #8, and some internal chat], and remove exported symbols (apparently unused, but). We also considered a mutex/spinlock approach, but later found a simpler way w/ isc lib; comment #13.) [Test Plan] * Synthetic reproducer with GDB to force the race condition, and DHCP server/client/noise injection is described in comment #9. * Test with the original package (problem occurs). * Test with the modified package (problem fixed). - Set DHCP_FD_FLAGS_POKE=0 (problem occurs). - Set dhcp.fd_flags_poke=0 (problem occurs). [Regression Potential] * 1) dhclient failing to acquire DHCP leases. * 2) dhcpd is also affected by code changes, thus failures to handle DHCP lease requests also have potential for regressions. * 3) the functional change added by the fix, if a regression were to occur, would likely be an issue only under some (unknown) race condition as well, thus expected to be rare. * Note: this potentially affects Focal/Jammy on Azure as a whole, per usage of dhclient in cloud-init instead of systemd-networkd. Azure provided extensive testing for all 3
[Touch-packages] [Bug 1926139] Update Released
The verification of the Stable Release Update for isc-dhcp has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1926139 Title: dhclient: thread concurrency race leads to DHCPOFFER packets not being received Status in bind9-libs package in Ubuntu: Won't Fix Status in isc-dhcp package in Ubuntu: Invalid Status in isc-dhcp source package in Focal: Fix Released Status in isc-dhcp source package in Jammy: Fix Released Bug description: [Impact] * Occasionally, during instance boot or machine start-up, dhclient will attempt to acquire a dhcp lease and fail, leaving the instance with no IP address and making it unreachable. * This happens about once every 100 reboots on bare metal, or affecting between ~0.3% to 2% of deployments on Azure (comment #2). * Azure uses dhclient called from cloud-init instead of systemd-networkd, and this is causing issues with larger deployments. * The logs of an affected dhclient produce the following: Listening on LPF/enp1s0/52:54:00:1c:d7:00 Sending on LPF/enp1s0/52:54:00:1c:d7:00 Sending on Socket/fallback DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... ... (omitting 20 similar lines) ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... No DHCPOFFERS received. No working leases in persistent database - sleeping. * This only impacts Focal and Jammy, where bind9-libs are multi-threaded (Bionic/earlier and Kinetic/later are single-threaded). * The actual problem is dhclient containing a thread concurrency race condition, and when the race occurs, the read socket is incorrectly/prematurely unwatched because required structures are not yet consistent, thus dhclient does not read any DHCPOFFER replies. * Detailed analysis of the issue is in comment #17. [Fix] * Prevent the race condition by starting to watch the read socket after required structures are consistent. * The fix has been tested in Azure w/ 13500 instances, and no errors have been observed (previously: 0.4%). * Anyway, in case regressions are observed, the patch introduces 2 switches to revert to previous behavior, which can be applied per-process or system-wide: - DHCP_FD_FLAGS_POKE=0 environment variable - dhcp.fd_flags_poke=0 kernel cmdline option * (Previous approaches/discussions included reverting bind9-libs to single-threaded, but we concluded it would have more regression risk than the expected [some bits in comment #8, and some internal chat], and remove exported symbols (apparently unused, but). We also considered a mutex/spinlock approach, but later found a simpler way w/ isc lib; comment #13.) [Test Plan] * Synthetic reproducer with GDB to force the race condition, and DHCP server/client/noise injection is described in comment #9. * Test with the original package (problem occurs). * Test with the modified package (problem fixed). - Set DHCP_FD_FLAGS_POKE=0 (problem occurs). - Set dhcp.fd_flags_poke=0 (problem occurs). [Regression Potential] * 1) dhclient failing to acquire DHCP leases. * 2) dhcpd is also affected by code changes, thus failures to handle DHCP lease requests also have potential for regressions. * 3) the functional change added by the fix, if a regression were to occur, would likely be an issue only under some (unknown) race condition as well, thus expected to be rare. * Note: this potentially affects Focal/Jammy on Azure as a whole, per usage of dhclient in cloud-init instead of systemd-networkd. Azure provided extensive testing for all 3 approaches (mostly internal communications, and some bug comments), with ~13k instances. No issues were observed (previously: 0.4%). * Such testing scale seems to indicate that there are no regressions for dhclient to acquire DHCP leases (1), nor another race condition that hit the fix/new behavior (3). With that, apparently (2) should be OK too. * Also, so to mitigate the regression risk as much as possible,
[Touch-packages] [Bug 1926139] Re: dhclient: thread concurrency race leads to DHCPOFFER packets not being received
This bug was fixed in the package isc-dhcp - 4.4.1-2.3ubuntu2.4 --- isc-dhcp (4.4.1-2.3ubuntu2.4) jammy; urgency=medium [ Mauricio Faria de Oliveira ] * Prevent race condition that might ignore DHCP OFFERs/ACKs when dhclient receives DHCP traffic noise. (LP: #1926139) The previous/racy behavior can be switched back on with the 'DHCP_FD_FLAGS_POKE=0' environment variable or the 'dhcp.fd_flags_poke=0' kernel cmdline option. - d/p/lp1926139-watch-socket-fd-later.patch: fix, switches. - d/apparmor/sbin.dhclient,usr.sbin.dhcpd: /proc/cmdline r. [ Steve Langasek ] * Include /etc/dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes in the initramfs. (LP: #1937110) - d/initramfs-tools/share/hooks/zz-dhclient: copy_exec it. -- Mauricio Faria de Oliveira Tue, 31 Jan 2023 18:54:40 -0300 ** Changed in: isc-dhcp (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1926139 Title: dhclient: thread concurrency race leads to DHCPOFFER packets not being received Status in bind9-libs package in Ubuntu: Won't Fix Status in isc-dhcp package in Ubuntu: Invalid Status in isc-dhcp source package in Focal: Fix Released Status in isc-dhcp source package in Jammy: Fix Released Bug description: [Impact] * Occasionally, during instance boot or machine start-up, dhclient will attempt to acquire a dhcp lease and fail, leaving the instance with no IP address and making it unreachable. * This happens about once every 100 reboots on bare metal, or affecting between ~0.3% to 2% of deployments on Azure (comment #2). * Azure uses dhclient called from cloud-init instead of systemd-networkd, and this is causing issues with larger deployments. * The logs of an affected dhclient produce the following: Listening on LPF/enp1s0/52:54:00:1c:d7:00 Sending on LPF/enp1s0/52:54:00:1c:d7:00 Sending on Socket/fallback DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... ... (omitting 20 similar lines) ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ... No DHCPOFFERS received. No working leases in persistent database - sleeping. * This only impacts Focal and Jammy, where bind9-libs are multi-threaded (Bionic/earlier and Kinetic/later are single-threaded). * The actual problem is dhclient containing a thread concurrency race condition, and when the race occurs, the read socket is incorrectly/prematurely unwatched because required structures are not yet consistent, thus dhclient does not read any DHCPOFFER replies. * Detailed analysis of the issue is in comment #17. [Fix] * Prevent the race condition by starting to watch the read socket after required structures are consistent. * The fix has been tested in Azure w/ 13500 instances, and no errors have been observed (previously: 0.4%). * Anyway, in case regressions are observed, the patch introduces 2 switches to revert to previous behavior, which can be applied per-process or system-wide: - DHCP_FD_FLAGS_POKE=0 environment variable - dhcp.fd_flags_poke=0 kernel cmdline option * (Previous approaches/discussions included reverting bind9-libs to single-threaded, but we concluded it would have more regression risk than the expected [some bits in comment #8, and some internal chat], and remove exported symbols (apparently unused, but). We also considered a mutex/spinlock approach, but later found a simpler way w/ isc lib; comment #13.) [Test Plan] * Synthetic reproducer with GDB to force the race condition, and DHCP server/client/noise injection is described in comment #9. * Test with the original package (problem occurs). * Test with the modified package (problem fixed). - Set DHCP_FD_FLAGS_POKE=0 (problem occurs). - Set dhcp.fd_flags_poke=0 (problem occurs). [Regression Potential] * 1) dhclient failing to acquire DHCP leases. * 2) dhcpd is also affected by code changes, thus failures to handle DHCP lease requests also have potential for regressions. * 3) the functional change added by the fix, if a regression were to occur, would likely be an issue only under some (unknown) race condition as well, thus expected to be rare. * Note: this potentially affects Focal/Jammy on Azure as a whole, per usage of dhclient in cloud-init instead of systemd-networkd. Azure provided extensive testing for all 3 approaches
[Touch-packages] [Bug 1937110] Re: dhcp option 121 & 249
This bug was fixed in the package isc-dhcp - 4.4.1-2.1ubuntu5.20.04.5 --- isc-dhcp (4.4.1-2.1ubuntu5.20.04.5) focal; urgency=medium [ Mauricio Faria de Oliveira ] * Prevent race condition that might ignore DHCP OFFERs/ACKs when dhclient receives DHCP traffic noise. (LP: #1926139) The previous/racy behavior can be switched back on with the 'DHCP_FD_FLAGS_POKE=0' environment variable or the 'dhcp.fd_flags_poke=0' kernel cmdline option. - d/p/lp1926139-watch-socket-fd-later.patch: fix, switches. - d/apparmor/sbin.dhclient,usr.sbin.dhcpd: /proc/cmdline r. [ Steve Langasek ] * Include /etc/dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes in the initramfs. (LP: #1937110) - d/initramfs-tools/share/hooks/zz-dhclient: copy_exec it. -- Mauricio Faria de Oliveira Tue, 31 Jan 2023 19:10:35 -0300 ** Changed in: isc-dhcp (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1937110 Title: dhcp option 121 & 249 Status in subiquity: New Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Focal: Fix Released Status in isc-dhcp source package in Jammy: Fix Released Bug description: [Impact] * DHCP classless static routes aren't applied by dhclient at the initramfs (e.g., ip=dhcp). * This happens as rfc3442-classless-routes is not copied to /etc/dhcp/dhclient-exit-hooks.d/ in the initramfs. * On Jammy, if such DHCP option(s) are present in the DHCP server response, the DHCP client ignores the 'routers' option from the server, thus leaving no routes configured. * On Focal, the older code still adds 'routers', which is slightly better, but still does not add the classless static routes. [Test Plan] * Use LXD container/VMs for DHCP server/client, configure the DHCP server with option 121, and some sample classless static routes. (see comments #12/jammy and #13/focal). [Regression Potential] * Acquisition of DHCP leases/routes at initramfs with ip=dhcp. * The code/script is not new, and is exercised normally during on rootfs (ie, post-initramfs) when dhclient is run. * It's also been in the initramfs in Kinetic already, since on Aug 2022; giving it tests. [Original Description] Hello, I'm running into issues with subiquity on a cloud provider. The cloud provider is using an on-link L3 gateway. His DHCP response looks like this: OPTION: 53 ( 1) DHCP message type 5 (DHCPACK) OPTION: 54 ( 4) Server identifier 172.31.1.1 OPTION: 51 ( 4) IP address leasetime 86400 (24h) OPTION: 1 ( 4) Subnet mask 255.255.255.255 OPTION: 3 ( 4) Routers 172.31.1.1 OPTION: 6 ( 12) DNS server OPTION: 121 ( 14) Classless Static Route20ac1f010100 ... ac1f0101 .. OPTION: 249 ( 14) MSFT - Classless route20ac1f010100 ... ac1f0101 .. Im booting the subiquity process with an patched ipxe (https://github.com/ipxe/ipxe/pull/104) like this: #!ipxe kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null initrd .../initrd boot initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso Sadly subiquity is stuck with a broken network (because of missing dhcp option 121/249 support). It happens when its running the /init from the kernel right after kernel is booted, i guess even before the subiquity is started(?). After further debugging, it looks like the provided kernel 5.4.80 #90 Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc- dhclient-4.4.1 which is lacking the given options. Would be awesome if this could be fixed.. maybe just a simple busybox compile option? To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937110/+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 1937110] Update Released
The verification of the Stable Release Update for isc-dhcp has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1937110 Title: dhcp option 121 & 249 Status in subiquity: New Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Focal: Fix Released Status in isc-dhcp source package in Jammy: Fix Released Bug description: [Impact] * DHCP classless static routes aren't applied by dhclient at the initramfs (e.g., ip=dhcp). * This happens as rfc3442-classless-routes is not copied to /etc/dhcp/dhclient-exit-hooks.d/ in the initramfs. * On Jammy, if such DHCP option(s) are present in the DHCP server response, the DHCP client ignores the 'routers' option from the server, thus leaving no routes configured. * On Focal, the older code still adds 'routers', which is slightly better, but still does not add the classless static routes. [Test Plan] * Use LXD container/VMs for DHCP server/client, configure the DHCP server with option 121, and some sample classless static routes. (see comments #12/jammy and #13/focal). [Regression Potential] * Acquisition of DHCP leases/routes at initramfs with ip=dhcp. * The code/script is not new, and is exercised normally during on rootfs (ie, post-initramfs) when dhclient is run. * It's also been in the initramfs in Kinetic already, since on Aug 2022; giving it tests. [Original Description] Hello, I'm running into issues with subiquity on a cloud provider. The cloud provider is using an on-link L3 gateway. His DHCP response looks like this: OPTION: 53 ( 1) DHCP message type 5 (DHCPACK) OPTION: 54 ( 4) Server identifier 172.31.1.1 OPTION: 51 ( 4) IP address leasetime 86400 (24h) OPTION: 1 ( 4) Subnet mask 255.255.255.255 OPTION: 3 ( 4) Routers 172.31.1.1 OPTION: 6 ( 12) DNS server OPTION: 121 ( 14) Classless Static Route20ac1f010100 ... ac1f0101 .. OPTION: 249 ( 14) MSFT - Classless route20ac1f010100 ... ac1f0101 .. Im booting the subiquity process with an patched ipxe (https://github.com/ipxe/ipxe/pull/104) like this: #!ipxe kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null initrd .../initrd boot initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso Sadly subiquity is stuck with a broken network (because of missing dhcp option 121/249 support). It happens when its running the /init from the kernel right after kernel is booted, i guess even before the subiquity is started(?). After further debugging, it looks like the provided kernel 5.4.80 #90 Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc- dhclient-4.4.1 which is lacking the given options. Would be awesome if this could be fixed.. maybe just a simple busybox compile option? To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937110/+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 1937110] Re: dhcp option 121 & 249
This bug was fixed in the package isc-dhcp - 4.4.1-2.3ubuntu2.4 --- isc-dhcp (4.4.1-2.3ubuntu2.4) jammy; urgency=medium [ Mauricio Faria de Oliveira ] * Prevent race condition that might ignore DHCP OFFERs/ACKs when dhclient receives DHCP traffic noise. (LP: #1926139) The previous/racy behavior can be switched back on with the 'DHCP_FD_FLAGS_POKE=0' environment variable or the 'dhcp.fd_flags_poke=0' kernel cmdline option. - d/p/lp1926139-watch-socket-fd-later.patch: fix, switches. - d/apparmor/sbin.dhclient,usr.sbin.dhcpd: /proc/cmdline r. [ Steve Langasek ] * Include /etc/dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes in the initramfs. (LP: #1937110) - d/initramfs-tools/share/hooks/zz-dhclient: copy_exec it. -- Mauricio Faria de Oliveira Tue, 31 Jan 2023 18:54:40 -0300 ** Changed in: isc-dhcp (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1937110 Title: dhcp option 121 & 249 Status in subiquity: New Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Focal: Fix Released Status in isc-dhcp source package in Jammy: Fix Released Bug description: [Impact] * DHCP classless static routes aren't applied by dhclient at the initramfs (e.g., ip=dhcp). * This happens as rfc3442-classless-routes is not copied to /etc/dhcp/dhclient-exit-hooks.d/ in the initramfs. * On Jammy, if such DHCP option(s) are present in the DHCP server response, the DHCP client ignores the 'routers' option from the server, thus leaving no routes configured. * On Focal, the older code still adds 'routers', which is slightly better, but still does not add the classless static routes. [Test Plan] * Use LXD container/VMs for DHCP server/client, configure the DHCP server with option 121, and some sample classless static routes. (see comments #12/jammy and #13/focal). [Regression Potential] * Acquisition of DHCP leases/routes at initramfs with ip=dhcp. * The code/script is not new, and is exercised normally during on rootfs (ie, post-initramfs) when dhclient is run. * It's also been in the initramfs in Kinetic already, since on Aug 2022; giving it tests. [Original Description] Hello, I'm running into issues with subiquity on a cloud provider. The cloud provider is using an on-link L3 gateway. His DHCP response looks like this: OPTION: 53 ( 1) DHCP message type 5 (DHCPACK) OPTION: 54 ( 4) Server identifier 172.31.1.1 OPTION: 51 ( 4) IP address leasetime 86400 (24h) OPTION: 1 ( 4) Subnet mask 255.255.255.255 OPTION: 3 ( 4) Routers 172.31.1.1 OPTION: 6 ( 12) DNS server OPTION: 121 ( 14) Classless Static Route20ac1f010100 ... ac1f0101 .. OPTION: 249 ( 14) MSFT - Classless route20ac1f010100 ... ac1f0101 .. Im booting the subiquity process with an patched ipxe (https://github.com/ipxe/ipxe/pull/104) like this: #!ipxe kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null initrd .../initrd boot initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso Sadly subiquity is stuck with a broken network (because of missing dhcp option 121/249 support). It happens when its running the /init from the kernel right after kernel is booted, i guess even before the subiquity is started(?). After further debugging, it looks like the provided kernel 5.4.80 #90 Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc- dhclient-4.4.1 which is lacking the given options. Would be awesome if this could be fixed.. maybe just a simple busybox compile option? To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937110/+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 1959866] Re: lubuntu jammy - unable to submit bug via `ubuntu-bug calamares`
I don't see that you have the same issue. Your issue seems to be "firefox: not found" which is bug #1973470. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1959866 Title: lubuntu jammy - unable to submit bug via `ubuntu-bug calamares` Status in apport package in Ubuntu: New Bug description: Lubuntu jammy QA-test install on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) but it failed; calamares issue... No prob; file bug. I had issues filing bug, thus this additional report. ** BACKGROUND on the install & other report calamares bug filed as https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1959865 was filed online; then apport-collect run successfully on box. That link is now added to this report here as `apport-collect` was run during the same boot or live session as issue occurred. As noted in comment #7 (of this report) and the now provided link; a end-users filing of an install issue had me attempt a 'strange' (stupid?) install; a QA-testcase we call "install using existing partition"; https://discourse.lubuntu.me/t/testing-checklist- understanding-the-testcases/2743 where you just re-use existing partitions without format.. EXCEPT I was attempting it here with an encrypted partition... no mount or anything; just selecting in calamares)... it was this install type that no doubt led to this error. ** EXPECTED OUTCOME `ubuntu-bug calamares` and file bug report via firefox.. ** ACTUAL OUTCOME Alas `ubuntu-bug` won't work with this error --- The problem cannot be reported: Your /tmp partition has less than 32.33792 MB of free space available, which leads to problems using applications and installing updates. Please free some space. Press any key to continue... --- Full terminal session follows --- lubuntu@lubuntu:~$ ubuntu-bug calamares *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** The contents of the files attached to this report will help developers diagnose your bug more quickly. It may be possible that there is sensitive information in these files. You will be able to review these attachments before they are sent. Do you want to include these files? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y *** Problem in calamares The problem cannot be reported: Your /tmp partition has less than 32.33792 MB of free space available, which leads to problems using applications and installing updates. Please free some space. Press any key to continue... No pending crash reports. Try --help for more information. -- Note: apport-collect has NOW been run on same box; same daily ISO, but it's a later reboot/session --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: LXQt DistroRelease: Ubuntu 22.04 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) Package: apport 2.20.11-0ubuntu76 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1959866/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/437809 -- 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: Triaged Bug 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 2008699] Re: fwupd-refresh.service always fails after hibernate
> Where? /usr/lib/systemd/system/fwupd-refresh.service only has After=network.target. Perhaps that'd be the fix. Ah... this was fixed in upstream already in 1.8.5 release. https://github.com/fwupd/fwupd/commit/fe5d93f7d2712f3b708e562a5f7e9be897e04d1d ** Also affects: systemd (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Lunar) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu) ** No longer affects: systemd (Ubuntu Focal) ** No longer affects: systemd (Ubuntu Jammy) ** No longer affects: systemd (Ubuntu Kinetic) ** No longer affects: systemd (Ubuntu Lunar) ** Changed in: fwupd (Ubuntu Focal) Status: New => Won't Fix ** Changed in: fwupd (Ubuntu Lunar) Status: New => Fix Released -- 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/2008699 Title: fwupd-refresh.service always fails after hibernate Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Focal: Won't Fix Status in fwupd source package in Jammy: New Status in fwupd source package in Kinetic: New Status in fwupd source package in Lunar: Fix Released Bug description: fwupd-refresh.service unit is set to After=network.target, however, in practice, the following happens: - Desktop is active, NetworkManager is connected. - Machine is hibernated. - On wakeup, systemd will start NetworkManager then fwupd-refresh.service. There's however, a race condition there: - NetworkManager starts first. - fwupd-refresh.service is started BEFORE NetworkManager has enough time to reconnect to network. - fwupd-refresh.service fails due to lack of network. - NetworkManager connects to network a couple seconds later. The following journal logs illustrate that: Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.0438] device (wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown kernel: r8169 :06:00.0 enp6s0: Link is Down Feb 27 11:27:27 brown fwupd[2459754]: 11:27:27:0099 GLib-GObject value "1818326128" of type 'guint' is invalid or out of range for property 'kind' of type 'guint' Feb 27 11:27:27 brown acpid[2037]: client connected from 4266[0:0] Feb 27 11:27:27 brown acpid[2037]: 1 client rule loaded Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2354] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2355] manager: NetworkManager state is now CONNECTED_LOCAL Feb 27 11:27:27 brown systemd[1]: man-db.service: Deactivated successfully. Feb 27 11:27:27 brown systemd[1]: Finished Daily man-db regeneration. Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2943] device (wlp5s0): supplicant interface state: internal-starting -> disconnected Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2943] device (p2p-dev-wlp5s0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2947] Wi-Fi P2P device controlled by interface wlp5s0 created Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2949] manager: (p2p-dev-wlp5s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/232) Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2951] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2953] device (wlp5s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2956] device (p2p-dev-wlp5s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Feb 27 11:27:27 brown dbus-daemon[2047]: [system] Successfully activated service 'org.freedesktop.fwupd' Feb 27 11:27:27 brown systemd[1]: Starting Update APT News... Feb 27 11:27:27 brown systemd[1]: Started Firmware update daemon. Feb 27 11:27:27 brown systemd[1]: Starting Update the local ESM caches... Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.743: Emitting
[Touch-packages] [Bug 2008699] Re: fwupd-refresh.service always fails after hibernate
> BTW - fwupd already uses network-online.target for this unit. One could probably argue this is a systemd bug. Where? /usr/lib/systemd/system/fwupd-refresh.service only has After=network.target. Perhaps that'd be the fix. -- 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/2008699 Title: fwupd-refresh.service always fails after hibernate Status in fwupd package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: fwupd-refresh.service unit is set to After=network.target, however, in practice, the following happens: - Desktop is active, NetworkManager is connected. - Machine is hibernated. - On wakeup, systemd will start NetworkManager then fwupd-refresh.service. There's however, a race condition there: - NetworkManager starts first. - fwupd-refresh.service is started BEFORE NetworkManager has enough time to reconnect to network. - fwupd-refresh.service fails due to lack of network. - NetworkManager connects to network a couple seconds later. The following journal logs illustrate that: Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.0438] device (wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown kernel: r8169 :06:00.0 enp6s0: Link is Down Feb 27 11:27:27 brown fwupd[2459754]: 11:27:27:0099 GLib-GObject value "1818326128" of type 'guint' is invalid or out of range for property 'kind' of type 'guint' Feb 27 11:27:27 brown acpid[2037]: client connected from 4266[0:0] Feb 27 11:27:27 brown acpid[2037]: 1 client rule loaded Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2354] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2355] manager: NetworkManager state is now CONNECTED_LOCAL Feb 27 11:27:27 brown systemd[1]: man-db.service: Deactivated successfully. Feb 27 11:27:27 brown systemd[1]: Finished Daily man-db regeneration. Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2943] device (wlp5s0): supplicant interface state: internal-starting -> disconnected Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2943] device (p2p-dev-wlp5s0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2947] Wi-Fi P2P device controlled by interface wlp5s0 created Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2949] manager: (p2p-dev-wlp5s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/232) Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2951] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2953] device (wlp5s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2956] device (p2p-dev-wlp5s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Feb 27 11:27:27 brown dbus-daemon[2047]: [system] Successfully activated service 'org.freedesktop.fwupd' Feb 27 11:27:27 brown systemd[1]: Starting Update APT News... Feb 27 11:27:27 brown systemd[1]: Started Firmware update daemon. Feb 27 11:27:27 brown systemd[1]: Starting Update the local ESM caches... Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.743: Emitting ::status-changed() [idle] Feb 27 11:27:27 brown fwupdmgr[2459622]: Updating lvfs Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.750: downloading https://cdn.fwupd.org/downloads/firmware.xml.gz.jcat Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.751: Emitting ::status-changed() [downloading] Feb 27 11:27:27 brown fwupdmgr[2459622]: Downloading…: 0% Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.751: Emitting ::status-changed() [idle] Feb 27 11:27:27 brown systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE Feb 27 11:27:27 brown systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Feb 27 11:27:27 brown systemd[1]: Failed to start Refresh fwupd metadata and update motd. Feb 27 11:27:27 brown systemd[1]: apt-news.service: Deactivated successfully. Feb 27 11:27:27 brown systemd[1]: Finished Update APT News. Feb 27 11:27:28 brown wpa_supplicant[2114]: wlp5s0: Reject scan trigger since one is already pending Feb 27 11:27:29 brown ModemManager[2147]: [base-manager] couldn't check support for device
[Touch-packages] [Bug 2008699] Re: fwupd-refresh.service always fails after hibernate
https://github.com/fwupd/fwupd/issues/5590 ** Bug watch added: github.com/fwupd/fwupd/issues #5590 https://github.com/fwupd/fwupd/issues/5590 -- 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/2008699 Title: fwupd-refresh.service always fails after hibernate Status in fwupd package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: fwupd-refresh.service unit is set to After=network.target, however, in practice, the following happens: - Desktop is active, NetworkManager is connected. - Machine is hibernated. - On wakeup, systemd will start NetworkManager then fwupd-refresh.service. There's however, a race condition there: - NetworkManager starts first. - fwupd-refresh.service is started BEFORE NetworkManager has enough time to reconnect to network. - fwupd-refresh.service fails due to lack of network. - NetworkManager connects to network a couple seconds later. The following journal logs illustrate that: Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.0438] device (wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown kernel: r8169 :06:00.0 enp6s0: Link is Down Feb 27 11:27:27 brown fwupd[2459754]: 11:27:27:0099 GLib-GObject value "1818326128" of type 'guint' is invalid or out of range for property 'kind' of type 'guint' Feb 27 11:27:27 brown acpid[2037]: client connected from 4266[0:0] Feb 27 11:27:27 brown acpid[2037]: 1 client rule loaded Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2354] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2355] manager: NetworkManager state is now CONNECTED_LOCAL Feb 27 11:27:27 brown systemd[1]: man-db.service: Deactivated successfully. Feb 27 11:27:27 brown systemd[1]: Finished Daily man-db regeneration. Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2943] device (wlp5s0): supplicant interface state: internal-starting -> disconnected Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2943] device (p2p-dev-wlp5s0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2947] Wi-Fi P2P device controlled by interface wlp5s0 created Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2949] manager: (p2p-dev-wlp5s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/232) Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2951] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2953] device (wlp5s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2956] device (p2p-dev-wlp5s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Feb 27 11:27:27 brown dbus-daemon[2047]: [system] Successfully activated service 'org.freedesktop.fwupd' Feb 27 11:27:27 brown systemd[1]: Starting Update APT News... Feb 27 11:27:27 brown systemd[1]: Started Firmware update daemon. Feb 27 11:27:27 brown systemd[1]: Starting Update the local ESM caches... Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.743: Emitting ::status-changed() [idle] Feb 27 11:27:27 brown fwupdmgr[2459622]: Updating lvfs Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.750: downloading https://cdn.fwupd.org/downloads/firmware.xml.gz.jcat Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.751: Emitting ::status-changed() [downloading] Feb 27 11:27:27 brown fwupdmgr[2459622]: Downloading…: 0% Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.751: Emitting ::status-changed() [idle] Feb 27 11:27:27 brown systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE Feb 27 11:27:27 brown systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Feb 27 11:27:27 brown systemd[1]: Failed to start Refresh fwupd metadata and update motd. Feb 27 11:27:27 brown systemd[1]: apt-news.service: Deactivated successfully. Feb 27 11:27:27 brown systemd[1]: Finished Update APT News. Feb 27 11:27:28 brown wpa_supplicant[2114]: wlp5s0: Reject scan trigger since one is already pending Feb 27 11:27:29 brown ModemManager[2147]: [base-manager] couldn't check support for device '/sys/devices/pci:00/:00:01.2/:02:00.0/:03:04.0/:05:00.0': not supported by any plugin Feb 27 11:27:29
[Touch-packages] [Bug 2008699] Re: fwupd-refresh.service always fails after hibernate
BTW - fwupd already uses network-online.target for this unit. One could probably argue this is a systemd bug. > [Unit] > Description=Refresh fwupd metadata and update motd > Documentation=man:fwupdmgr(1) > After=network-online.target > > [Service] > Type=oneshot > CacheDirectory=fwupdmgr > StandardError=null > @user@ > RestrictAddressFamilies=AF_NETLINK AF_UNIX AF_INET AF_INET6 > SystemCallFilter=~@mount > ProtectKernelModules=yes > ProtectControlGroups=yes > RestrictRealtime=yes > SuccessExitStatus=2 > ExecStart=@bindir@/fwupdmgr refresh ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2008699 Title: fwupd-refresh.service always fails after hibernate Status in fwupd package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: fwupd-refresh.service unit is set to After=network.target, however, in practice, the following happens: - Desktop is active, NetworkManager is connected. - Machine is hibernated. - On wakeup, systemd will start NetworkManager then fwupd-refresh.service. There's however, a race condition there: - NetworkManager starts first. - fwupd-refresh.service is started BEFORE NetworkManager has enough time to reconnect to network. - fwupd-refresh.service fails due to lack of network. - NetworkManager connects to network a couple seconds later. The following journal logs illustrate that: Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.0438] device (wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown kernel: r8169 :06:00.0 enp6s0: Link is Down Feb 27 11:27:27 brown fwupd[2459754]: 11:27:27:0099 GLib-GObject value "1818326128" of type 'guint' is invalid or out of range for property 'kind' of type 'guint' Feb 27 11:27:27 brown acpid[2037]: client connected from 4266[0:0] Feb 27 11:27:27 brown acpid[2037]: 1 client rule loaded Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2354] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2355] manager: NetworkManager state is now CONNECTED_LOCAL Feb 27 11:27:27 brown systemd[1]: man-db.service: Deactivated successfully. Feb 27 11:27:27 brown systemd[1]: Finished Daily man-db regeneration. Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2943] device (wlp5s0): supplicant interface state: internal-starting -> disconnected Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2943] device (p2p-dev-wlp5s0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2947] Wi-Fi P2P device controlled by interface wlp5s0 created Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2949] manager: (p2p-dev-wlp5s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/232) Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2951] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2953] device (wlp5s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2956] device (p2p-dev-wlp5s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Feb 27 11:27:27 brown dbus-daemon[2047]: [system] Successfully activated service 'org.freedesktop.fwupd' Feb 27 11:27:27 brown systemd[1]: Starting Update APT News... Feb 27 11:27:27 brown systemd[1]: Started Firmware update daemon. Feb 27 11:27:27 brown systemd[1]: Starting Update the local ESM caches... Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.743: Emitting ::status-changed() [idle] Feb 27 11:27:27 brown fwupdmgr[2459622]: Updating lvfs Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.750: downloading https://cdn.fwupd.org/downloads/firmware.xml.gz.jcat Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.751: Emitting ::status-changed() [downloading] Feb 27 11:27:27 brown fwupdmgr[2459622]: Downloading…: 0% Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.751: Emitting ::status-changed() [idle] Feb 27 11:27:27 brown systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE Feb 27 11:27:27 brown systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Feb 27 11:27:27 brown systemd[1]: Failed to start Refresh fwupd metadata and
[Touch-packages] [Bug 2008469] Re: ubuntu jammy debug mirror out of sync
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-keyring (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2008469 Title: ubuntu jammy debug mirror out of sync Status in ubuntu-keyring package in Ubuntu: Confirmed Bug description: Why dose the Ubuntu debug mirror is again out of sync how should it be used in a productive environment when every month the mirror is for one week broken. libharfbuzz0b-dbgsym : Depends: libharfbuzz0b (= 2.7.4-1ubuntu3) but 2.7.4-1ubuntu3.1 is to be installed libldap-2.5-0-dbgsym : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3) but 2.5.13+dfsg-0ubuntu0.22.04.1 is to be installed libpulse0-dbgsym : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2 is to be installed libsasl2-2-dbgsym : Depends: libsasl2-2 (= 2.1.27+dfsg2-3ubuntu1) but 2.1.27+dfsg2-3ubuntu1.1 is to be installed libsdl2-2.0-0-dbgsym : Depends: libsdl2-2.0-0 (= 2.0.20+dfsg-2build1) but 2.0.20+dfsg-2ubuntu1.22.04.1 is to be installed libswresample3-dbgsym : Depends: libswresample3 (= 7:4.4.1-3ubuntu5) but 7:4.4.2-0ubuntu0.22.04.1 is to be installed libsystemd0-dbgsym : Depends: libsystemd0 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libudev1-dbgsym : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libusb-1.0-0-dbgsym : Depends: libusb-1.0-0 (= 2:1.0.25-1ubuntu1) but 2:1.0.25-1ubuntu2 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/2008469/+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 2008638] Re: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway
Proposed fix: https://github.com/canonical/apport/pull/141 ** Also affects: apport Importance: Undecided Status: New ** Changed in: apport Milestone: None => 2.27.0 ** Changed in: apport Status: New => In Progress ** Changed in: apport Importance: Undecided => Medium ** Changed in: apport Assignee: (unassigned) => Benjamin Drung (bdrung) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2008638 Title: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway Status in Apport: In Progress Status in apport package in Ubuntu: Confirmed Bug description: Had a Nautlius crash prior to this error. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: apport-gtk 2.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1201:124:38512857:2023-02-24 12:17:00.435185909 -0500:2023-02-24 12:17:01.435185909 -0500:/var/crash/_usr_bin_gnome-shell.1201.crash 640:1000:1000:90509:2023-02-26 10:18:25.277171373 -0500:2023-02-26 10:18:26.277171373 -0500:/var/crash/_usr_share_apport_apport-gtk.1000.crash 600:116:124:37:2023-02-26 10:18:21.948992294 -0500:2023-02-18 17:59:57.688578533 -0500:/var/crash/_usr_bin_nautilus.1000.uploaded 640:1000:124:14955989:2023-02-26 10:16:50.213119506 -0500:2023-02-26 10:17:03.637664041 -0500:/var/crash/_usr_bin_nautilus.1000.crash 664:1000:1000:0:2023-02-26 10:17:03.617663168 -0500:2023-02-26 10:17:03.617663168 -0500:/var/crash/_usr_bin_nautilus.1000.upload CurrentDesktop: ubuntu:GNOME Date: Sun Feb 26 10:18:26 2023 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2023-02-13 (12 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) InterpreterPath: /usr/bin/python3.11 JournalErrors: Feb 26 10:18:26 hostname systemd[2030]: update-notifier-crash.service: Failed with result 'exit-code'. Feb 26 10:18:26 hostname systemd[2030]: Failed to start Notification regarding a crash report. PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonArgs: ['/usr/share/apport/apport-gtk'] PythonDetails: N/A SourcePackage: apport Title: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2008638/+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 2008638] Re: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2008638 Title: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway Status in apport package in Ubuntu: Confirmed Bug description: Had a Nautlius crash prior to this error. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: apport-gtk 2.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1201:124:38512857:2023-02-24 12:17:00.435185909 -0500:2023-02-24 12:17:01.435185909 -0500:/var/crash/_usr_bin_gnome-shell.1201.crash 640:1000:1000:90509:2023-02-26 10:18:25.277171373 -0500:2023-02-26 10:18:26.277171373 -0500:/var/crash/_usr_share_apport_apport-gtk.1000.crash 600:116:124:37:2023-02-26 10:18:21.948992294 -0500:2023-02-18 17:59:57.688578533 -0500:/var/crash/_usr_bin_nautilus.1000.uploaded 640:1000:124:14955989:2023-02-26 10:16:50.213119506 -0500:2023-02-26 10:17:03.637664041 -0500:/var/crash/_usr_bin_nautilus.1000.crash 664:1000:1000:0:2023-02-26 10:17:03.617663168 -0500:2023-02-26 10:17:03.617663168 -0500:/var/crash/_usr_bin_nautilus.1000.upload CurrentDesktop: ubuntu:GNOME Date: Sun Feb 26 10:18:26 2023 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2023-02-13 (12 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) InterpreterPath: /usr/bin/python3.11 JournalErrors: Feb 26 10:18:26 hostname systemd[2030]: update-notifier-crash.service: Failed with result 'exit-code'. Feb 26 10:18:26 hostname systemd[2030]: Failed to start Notification regarding a crash report. PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonArgs: ['/usr/share/apport/apport-gtk'] PythonDetails: N/A SourcePackage: apport Title: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2008638/+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 1892225] Re: apport-gtk consumes 100% CPU for way too long after something crashes
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1892225 Title: apport-gtk consumes 100% CPU for way too long after something crashes Status in apport package in Ubuntu: Confirmed Bug description: Something (related to Cinnamon) crashes, so the usual popup appears telling me that something crashed, and asking me whether I wanted to send a report. I choose Send. Every time this happens, then a process called apport-gtk starts consuming 100% CPU and it goes on for several minutes, so long that I end up killing it. There's no way there is a good reason for consuming so much CPU for so long. If you need to do such an amount of processing just to generate and send a bug report, something is deeply broken. But if the operation actually had to be that computationally expensive, then you must do it in a less intensive way so that it can go on in the background, for no matter how long, without rendering me unable to use my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportLog: ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: called for pid 2405, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: executable: /usr/bin/cinnamon (command line "cinnamon --replace") ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: debug: session gdbus call: (true,) ERROR: apport (pid 2908) Wed Aug 19 18:39:34 2020: wrote report /var/crash/_usr_bin_cinnamon.1000.crash ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:110:69556:2020-08-19 18:39:33.732794284 +0200:2020-08-19 18:39:34.732794284 +0200:/var/crash/_usr_bin_cinnamon-launcher.1000.crash 640:1000:110:15432562:2020-08-19 18:39:34.466977487 +0200:2020-08-19 18:42:42.722667813 +0200:/var/crash/_usr_bin_cinnamon.1000.crash CurrentDesktop: X-Cinnamon Date: Wed Aug 19 18:42:34 2020 InstallationDate: Installed on 2013-10-11 (2503 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-07-12 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1892225/+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 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
This bug was fixed in the package libcap2 - 1:2.66-3ubuntu2 --- libcap2 (1:2.66-3ubuntu2) lunar; urgency=medium * Skip the test uns_test to fix autopkgtest on armhf. It's failing on armhf because we are using an older kernel in the armhf builders. This test succeeds on newer versions. Once we upgrade our hosts this patch can be dropped. See LP#2003892 -- Danilo Egea Gondolfo Fri, 03 Feb 2023 11:18:40 + ** Changed in: libcap2 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: Fix Released Bug description: Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by default. This option seems to break libcap2. One of the autopkgtests that is supposed to prevent an exploitation instance using capabilities fails: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+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
