Cannot port existing snap to core 22

apdw · February 3, 2024, 6:40pm

I am porting my existing core 20 snap to core 22 but have bumped into a serious issue: it seems impossible to download jammy elements for inclusion into my snap.

Full details of the error are below,

Many thanks in advance

Alan

snapcraft.yaml:

name: photonotebook
title: PhotoNoteBook
version: "3.0.1"
summary: A digital photography library manager and notebook 
license: Proprietary
description: PhotoNoteBook is a digital photograph library manager enabling collections of images and the making of notes and memo's for the collections and the photographs. 
icon: photonotebook.png 

confinement: strict
grade: stable
base: core22

# this line enables LZO compression for the snap and speed up first start time - hopefully!
compression: lzo
 
apps:
  photonotebook:
    command: bin/photonotebook
    extensions:
      - gnome
      
    plugs: [home, unity7,  opengl, network, removable-media, optical-drive ,desktop, desktop-legacy, gsettings, x11, wayland]
     
parts:
  photonotebook:
    plugin: dump
    source: ./photonotebook/
    stage-packages: 
     - libgif7
     - liblcms2-2
     
architectures:
  - build-on: [amd64]

The error output to terminal is lacking “newlines” and is very difficult to read… I

Snapping photonotebook
Launching instance... :: Creating new base instance from remote - (8.0s)                           ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
Launching instance... :: Creating new base instance from remote | (9.0s)                           ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
Launching instance... :: Creating new base instance from remote \ (9.3s)                           ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
craft-providers error: Failed to update apt cache.e from remote                                    
* Command that failed: 'lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 apt-get update'
* Command exit code: 100
* Command output: b'Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]\nGet:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]\nGet:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]\nGet:4 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1395 kB]\nGet:5 http://archive.ubuntu.com/ubuntu jammy/main Translation-en [510 kB]\nGet:6 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [129 kB]\nGet:7 http://archive.ubuntu.com/ubuntu jammy/restricted Translation-en [18.6 kB]\nGet:8 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [14.1 MB]\nGet:9 http://archive.ubuntu.com/ubuntu jammy/universe Translation-en [5652 kB]\nGet:10 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [217 kB]\nGet:11 http://archive.ubuntu.com/ubuntu jammy/multiverse Translation-en [112 kB]\nGet:12 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1325 kB]\nGet:13 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [268 kB]\nGet:14 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [1342 kB]\nGet:15 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en [220 kB]\nGet:16 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1042 kB]\nGet:17 http://archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [235 kB]\nGet:18 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [42.1 kB]\nGet:19 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse Translation-en [10.1 kB]\nGet:20 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [41.7 kB]\nGet:21 http://archive.ubuntu.com/ubuntu jammy-backports/main Translation-en [10.5 kB]\nGet:22 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [24.2 kB]\nGet:23 http://archive.ubuntu.com/ubuntu jammy-backports/universe Translation-en [16.5 kB]\nIgn:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\nIgn:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\nIgn:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\nErr:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n  Could not connect to security.ubuntu.com:80 (91.189.88.142), connection timed out\nFetched 27.2 MB in 37s (730 kB/s)\nReading package lists...\n'
* Command standard error output: b"ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.\nE: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease  Could not connect to security.ubuntu.com:80 (91.189.88.142), connection timed out\nE: Some index files failed to download. They have been ignored, or old ones used instead.\n"

The “full execution log”

2024-02-03 18:12:19.105 Starting Snapcraft 8.0.2
2024-02-03 18:12:19.106 lifecycle command: 'pack', arguments: Namespace(destructive_mode=False, use_lxd=True, debug=True, enable_manifest=False, manifest_image_information=None, bind_ssh=False, build_for=None, http_proxy=None, https_proxy=None, ua_token=None, enable_experimental_ua_services=False, enable_experimental_plugins=False, enable_experimental_extensions=False, enable_developer_debug=False, enable_experimental_target_arch=False, target_arch=None, provider=None, directory=None, output=None)
2024-02-03 18:12:19.106 command: pack, arguments: Namespace(destructive_mode=False, use_lxd=True, debug=True, enable_manifest=False, manifest_image_information=None, bind_ssh=False, build_for=None, http_proxy=None, https_proxy=None, ua_token=None, enable_experimental_ua_services=False, enable_experimental_plugins=False, enable_experimental_extensions=False, enable_developer_debug=False, enable_experimental_target_arch=False, target_arch=None, provider=None, directory=None, output=None)
2024-02-03 18:12:19.117 CPU count (from process affinity): 8
2024-02-03 18:12:19.117 Invalid SNAPCRAFT_MAX_PARALLEL_BUILD_COUNT ''
2024-02-03 18:12:19.117 Running on amd64 for amd64
2024-02-03 18:12:19.118 CRAFT_ARCH_TRIPLET is deprecated, use CRAFT_ARCH_TRIPLET_BUILD_{ON|FOR}
2024-02-03 18:12:19.118 CRAFT_ARCH_TRIPLET is deprecated, use CRAFT_ARCH_TRIPLET_BUILD_{ON|FOR}
2024-02-03 18:12:19.118 CRAFT_ARCH_TRIPLET is deprecated, use CRAFT_ARCH_TRIPLET_BUILD_{ON|FOR}
2024-02-03 18:12:19.118 CRAFT_ARCH_TRIPLET is deprecated, use CRAFT_ARCH_TRIPLET_BUILD_{ON|FOR}
2024-02-03 18:12:19.120 Checking build provider availability
2024-02-03 18:12:19.125 Retrieved snap config: {}
2024-02-03 18:12:19.125 Using provider 'lxd' passed as an argument.
2024-02-03 18:12:19.256 Executing on host: lxc --project default profile show local:default
2024-02-03 18:12:19.359 Using hostname 'snapcraft-photonotebook-on-amd64-for-amd64-45114395'
2024-02-03 18:12:19.359 Launching instance...
2024-02-03 18:12:19.359 Executing on host: lxc remote list --format=yaml
2024-02-03 18:12:19.481 Remote 'craft-com.ubuntu.cloud-buildd' already exists.
2024-02-03 18:12:19.481 Executing on host: lxc project list local: --format=yaml
2024-02-03 18:12:19.587 Set LXD instance name to 'snapcraft-photonotebook-on-amd64-for-amd64-45114395'
2024-02-03 18:12:19.588 Checking for instance 'snapcraft-photonotebook-on-amd64-for-amd64-45114395' in project 'snapcraft' in remote 'local'
2024-02-03 18:12:19.588 Executing on host: lxc --project snapcraft list local: --format=yaml
2024-02-03 18:12:19.748 Instance 'snapcraft-photonotebook-on-amd64-for-amd64-45114395' does not exist.
2024-02-03 18:12:19.748 Set LXD instance name to 'base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc'
2024-02-03 18:12:19.748 Checking for base instance 'base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc' in project 'snapcraft' in remote 'local'
2024-02-03 18:12:19.748 Executing on host: lxc --project snapcraft list local: --format=yaml
2024-02-03 18:12:19.876 Checking validity of instance 'base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc'.
2024-02-03 18:12:19.876 Executing on host: lxc --project snapcraft info local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc
2024-02-03 18:12:19.996 Executing on host: lxc --project snapcraft info local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc
2024-02-03 18:12:20.137 Executing on host: lxc --project snapcraft config get local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.status
2024-02-03 18:12:20.229 Instance 'base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc' is not ready (State: RUNNING, Status: PREPARING)
2024-02-03 18:12:20.229 Executing on host: lxc --project snapcraft config get local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.pid
2024-02-03 18:12:20.322 Instance is not valid: Instance is not ready.
Instance 'base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc' is not ready and the process (pid 74871) that created the instance is inactive.
2024-02-03 18:12:20.322 Base instance 'base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc' is not valid. Deleting base instance.
2024-02-03 18:12:20.322 Executing on host: lxc --project snapcraft delete local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc --force
2024-02-03 18:12:23.004 Creating new instance from remote
2024-02-03 18:12:23.004 Creating new base instance from remote
2024-02-03 18:12:23.004 Creating new base instance from image 'core22' from remote 'craft-com.ubuntu.cloud-buildd'
2024-02-03 18:12:23.004 Executing on host: lxc --project snapcraft info local:
2024-02-03 18:12:23.133 Executing on host: lxc --project snapcraft launch craft-com.ubuntu.cloud-buildd:core22 local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc --config 'raw.idmap=both 1000 0' --config security.syscalls.intercept.mknod=true --config user.craft_providers.status=STARTING --config user.craft_providers.timer=2024-02-03T18:12:23.133399+00:00 --config user.craft_providers.pid=77849
2024-02-03 18:12:30.507 Successfully launched instance base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc.
2024-02-03 18:12:30.507 Executing on host: lxc --project snapcraft config get local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.status
2024-02-03 18:12:30.589 Setting up base instance 'base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc'
2024-02-03 18:12:30.589 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.status PREPARING
2024-02-03 18:12:30.964 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.timer 2024-02-03T18:12:30.964278+00:00
2024-02-03 18:12:30.965 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 test -f /etc/craft-instance.conf
2024-02-03 18:12:31.281 Executing on host: lxc --project snapcraft file push /tmp/tmprdqobgln local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc/etc/craft-instance.conf --mode=0644
2024-02-03 18:12:31.537 Set instance timer to '2024-02-03T18:12:30.964278+00:00'
2024-02-03 18:12:31.627 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 chown root:root /etc/craft-instance.conf
2024-02-03 18:12:31.819 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 cat /etc/os-release
2024-02-03 18:12:31.992 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 test -f /etc/craft-instance.conf
2024-02-03 18:12:32.256 Executing on host: lxc --project snapcraft file pull local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc/etc/craft-instance.conf /home/alan/tmpje0v031p.tmp-craft/tmpi1fr30v8
2024-02-03 18:12:32.351 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 test -f /etc/craft-instance.conf
2024-02-03 18:12:32.616 Executing on host: lxc --project snapcraft file pull local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc/etc/craft-instance.conf /home/alan/tmpe5f2l05s.tmp-craft/tmpgw04a24l
2024-02-03 18:12:32.730 Executing on host: lxc --project snapcraft file push /tmp/tmp0gciavun local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc/etc/craft-instance.conf --mode=0644
2024-02-03 18:12:32.835 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 chown root:root /etc/craft-instance.conf
2024-02-03 18:12:33.143 No cache path set, not mounting cache directories.
2024-02-03 18:12:33.143 Executing on host: lxc --project snapcraft file push /tmp/tmpy0_lbv_n local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc/etc/environment --mode=0644
2024-02-03 18:12:33.243 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 chown root:root /etc/environment
2024-02-03 18:12:33.443 Executing on host: lxc --project snapcraft file push /tmp/tmpx_6eti_h local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc/etc/apt/apt.conf.d/20auto-upgrades --mode=0644
2024-02-03 18:12:33.547 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 chown root:root /etc/apt/apt.conf.d/20auto-upgrades
2024-02-03 18:12:33.762 Waiting for environment to be ready...
2024-02-03 18:12:33.762 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 systemctl is-system-running
2024-02-03 18:12:33.962 Executing on host: lxc --project snapcraft file push /tmp/tmpinmhiis3 local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc/etc/hostname --mode=0644
2024-02-03 18:12:34.059 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 chown root:root /etc/hostname
2024-02-03 18:12:34.247 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 hostname -F /etc/hostname
2024-02-03 18:12:34.443 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
2024-02-03 18:12:34.540 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.timer 2024-02-03T18:12:34.540604+00:00
2024-02-03 18:12:34.631 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 systemctl enable systemd-resolved
2024-02-03 18:12:34.834 Set instance timer to '2024-02-03T18:12:34.540604+00:00'
2024-02-03 18:12:34.959 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 systemctl restart systemd-resolved
2024-02-03 18:12:35.239 Executing on host: lxc --project snapcraft file push /tmp/tmp88blij_k local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc/etc/systemd/network/10-eth0.network --mode=0644
2024-02-03 18:12:35.363 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 chown root:root /etc/systemd/network/10-eth0.network
2024-02-03 18:12:35.566 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 systemctl enable systemd-networkd
2024-02-03 18:12:35.896 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 systemctl restart systemd-networkd
2024-02-03 18:12:36.333 Waiting for networking to be ready...
2024-02-03 18:12:36.334 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 getent hosts snapcraft.io
2024-02-03 18:12:36.514 Executing on host: lxc --project snapcraft file push /tmp/tmplsg5zdxg local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc/etc/apt/apt.conf.d/00no-recommends --mode=0644
2024-02-03 18:12:36.607 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 chown root:root /etc/apt/apt.conf.d/00no-recommends
2024-02-03 18:12:36.795 Executing on host: lxc --project snapcraft file push /tmp/tmpqom00unx local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc/etc/apt/apt.conf.d/00update-errors --mode=0644
2024-02-03 18:12:36.919 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 chown root:root /etc/apt/apt.conf.d/00update-errors
2024-02-03 18:12:37.123 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 apt-get update
2024-02-03 18:12:37.837 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.timer 2024-02-03T18:12:37.837396+00:00
2024-02-03 18:12:38.041 Set instance timer to '2024-02-03T18:12:37.837396+00:00'
2024-02-03 18:12:41.044 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.timer 2024-02-03T18:12:41.044212+00:00
2024-02-03 18:12:43.127 Set instance timer to '2024-02-03T18:12:41.044212+00:00'
2024-02-03 18:12:46.129 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.timer 2024-02-03T18:12:46.128881+00:00
2024-02-03 18:12:47.441 Set instance timer to '2024-02-03T18:12:46.128881+00:00'
2024-02-03 18:12:50.445 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.timer 2024-02-03T18:12:50.444883+00:00
2024-02-03 18:12:50.629 Set instance timer to '2024-02-03T18:12:50.444883+00:00'
2024-02-03 18:12:53.633 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.timer 2024-02-03T18:12:53.632921+00:00
2024-02-03 18:12:53.832 Set instance timer to '2024-02-03T18:12:53.632921+00:00'
2024-02-03 18:12:56.835 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.timer 2024-02-03T18:12:56.835755+00:00
2024-02-03 18:12:57.155 Set instance timer to '2024-02-03T18:12:56.835755+00:00'
2024-02-03 18:13:00.159 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.timer 2024-02-03T18:13:00.158838+00:00
2024-02-03 18:13:00.392 Set instance timer to '2024-02-03T18:13:00.158838+00:00'
2024-02-03 18:13:03.393 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.timer 2024-02-03T18:13:03.392924+00:00
2024-02-03 18:13:03.594 Set instance timer to '2024-02-03T18:13:03.392924+00:00'
2024-02-03 18:13:06.597 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.timer 2024-02-03T18:13:06.597324+00:00
2024-02-03 18:13:06.833 Set instance timer to '2024-02-03T18:13:06.597324+00:00'
2024-02-03 18:13:09.836 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.timer 2024-02-03T18:13:09.836225+00:00
2024-02-03 18:13:10.041 Set instance timer to '2024-02-03T18:13:09.836225+00:00'
2024-02-03 18:13:13.045 Executing on host: lxc --project snapcraft config set local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc user.craft_providers.timer 2024-02-03T18:13:13.045046+00:00
2024-02-03 18:13:13.267 Set instance timer to '2024-02-03T18:13:13.045046+00:00'
2024-02-03 18:13:15.505 Executing in container: lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 bash -c 'exec 3<> /dev/tcp/snapcraft.io/443'
2024-02-03 18:13:15.724 craft-providers error: Failed to update apt cache.
* Command that failed: 'lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v40--fd08e731c976fdc7c5bc -- env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin SNAPCRAFT_MANAGED_MODE=1 apt-get update'
* Command exit code: 100
* Command output: b'Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]\nGet:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]\nGet:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]\nGet:4 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1395 kB]\nGet:5 http://archive.ubuntu.com/ubuntu jammy/main Translation-en [510 kB]\nGet:6 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [129 kB]\nGet:7 http://archive.ubuntu.com/ubuntu jammy/restricted Translation-en [18.6 kB]\nGet:8 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [14.1 MB]\nGet:9 http://archive.ubuntu.com/ubuntu jammy/universe Translation-en [5652 kB]\nGet:10 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [217 kB]\nGet:11 http://archive.ubuntu.com/ubuntu jammy/multiverse Translation-en [112 kB]\nGet:12 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1325 kB]\nGet:13 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [268 kB]\nGet:14 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [1342 kB]\nGet:15 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en [220 kB]\nGet:16 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1042 kB]\nGet:17 http://archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [235 kB]\nGet:18 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [42.1 kB]\nGet:19 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse Translation-en [10.1 kB]\nGet:20 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [41.7 kB]\nGet:21 http://archive.ubuntu.com/ubuntu jammy-backports/main Translation-en [10.5 kB]\nGet:22 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [24.2 kB]\nGet:23 http://archive.ubuntu.com/ubuntu jammy-backports/universe Translation-en [16.5 kB]\nIgn:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\nIgn:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\nIgn:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\nErr:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n  Could not connect to security.ubuntu.com:80 (91.189.88.142), connection timed out\nFetched 27.2 MB in 37s (730 kB/s)\nReading package lists...\n'
* Command standard error output: b"ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.\nE: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease  Could not connect to security.ubuntu.com:80 (91.189.88.142), connection timed out\nE: Some index files failed to download. They have been ignored, or old ones used instead.\n"

apdw · February 4, 2024, 11:21am

Further to the errors when creating the snap, running the snap locally shows these curious errors that do not occur on the Windows version of the app:

Sun Feb 04 11:17 => photonotebook
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
Gtk-Message: 11:17:44.105: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.

(java:85884): Gtk-CRITICAL **: 11:17:47.049: gtk_window_resize: assertion 'width > 0' failed

Has anyone seen this kind of error before? Does anyone know if this is an issue buried in the JAVAFX or GTK modules?

Googling around StackOverflow shows that these errors used to be found several years ago and some bugfixes are hinted at, but I cannot find anything more recent.

cheers Alan

ogra · February 4, 2024, 12:29pm

Do you have docker installed? It is known to break networking for other container tools with the way it mangles your host setup… this shows especially when used on the same machine with lxd

The nocsd errors are caused by a massively gross hack unity7 uses for client side window decorations by hacking it into preloading instead of providing a properly patched gtk3 version instead… there was discussion about this on discourse.ubuntu.com and it is known that it will break quite a few graphical snaps

apdw · February 4, 2024, 1:16pm

Hi Ogra,

thanks for getting back to me.

I don’t have docker installed so I don’t think that could be the issue. As for Unity 7 …

cheers Alan

apdw · February 6, 2024, 1:10pm

More on the above! Reading that lxd can cause network related issues I forced a core22 build to use multipass rather than lxd. The key resulting errors are very similar to the lxd build. the key ones seem to be:

craft-providers error: Failed to update apt cache.                                                 
* Command that failed: 'multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- apt-get update'

and:

Ign:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n
Ign:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n
Ign:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n
Err:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n
Could not connect to security.ubuntu.com:80 (91.189.88.142), connection timed out\n

Error 12 on the log below looks like it may be important! I hope someone out there has a clue, because I don’t!

It may not be relevant, but I cannot get a response to a ping of http://security.ubuntu.com :

ping  http://security.ubuntu.com
ping: http://security.ubuntu.com: Name or service not known

A full execution log is available below.

A Core 20 build with the appropriate gnome extension builds fine.

cheers Alan

2024-02-06 12:38:30.548 Starting Snapcraft 8.0.2
2024-02-06 12:38:30.548 Raw pre-parsed sysargs: args={'help': False, 'verbose': False, 'quiet': False, 'verbosity': 'trace', 'version': False, 'trace': False} filtered=[]
2024-02-06 12:38:30.548 Using default command: 'pack'
2024-02-06 12:38:30.548 General parsed sysargs: command='pack' args=[]
2024-02-06 12:38:30.550 Command parsed sysargs: Namespace(destructive_mode=False, use_lxd=False, debug=False, enable_manifest=False, manifest_image_information=None, bind_ssh=False, build_for=None, http_proxy=None, https_proxy=None, ua_token=None, enable_experimental_ua_services=False, enable_experimental_plugins=False, enable_experimental_extensions=False, enable_developer_debug=False, enable_experimental_target_arch=False, target_arch=None, provider=None, directory=None, output=None)
2024-02-06 12:38:30.550 lifecycle command: 'pack', arguments: Namespace(destructive_mode=False, use_lxd=False, debug=False, enable_manifest=False, manifest_image_information=None, bind_ssh=False, build_for=None, http_proxy=None, https_proxy=None, ua_token=None, enable_experimental_ua_services=False, enable_experimental_plugins=False, enable_experimental_extensions=False, enable_developer_debug=False, enable_experimental_target_arch=False, target_arch=None, provider=None, directory=None, output=None)
2024-02-06 12:38:30.550 command: pack, arguments: Namespace(destructive_mode=False, use_lxd=False, debug=False, enable_manifest=False, manifest_image_information=None, bind_ssh=False, build_for=None, http_proxy=None, https_proxy=None, ua_token=None, enable_experimental_ua_services=False, enable_experimental_plugins=False, enable_experimental_extensions=False, enable_developer_debug=False, enable_experimental_target_arch=False, target_arch=None, provider=None, directory=None, output=None)
2024-02-06 12:38:30.561 Created build plan:
  build-on: amd64 build-for: amd64
2024-02-06 12:38:30.561 CPU count (from process affinity): 8
2024-02-06 12:38:30.561 Invalid SNAPCRAFT_MAX_PARALLEL_BUILD_COUNT ''
2024-02-06 12:38:30.562 Running on amd64 for amd64
2024-02-06 12:38:30.563 CRAFT_ARCH_TRIPLET is deprecated, use CRAFT_ARCH_TRIPLET_BUILD_{ON|FOR}
2024-02-06 12:38:30.563 CRAFT_ARCH_TRIPLET is deprecated, use CRAFT_ARCH_TRIPLET_BUILD_{ON|FOR}
2024-02-06 12:38:30.564 CRAFT_ARCH_TRIPLET is deprecated, use CRAFT_ARCH_TRIPLET_BUILD_{ON|FOR}
2024-02-06 12:38:30.564 CRAFT_ARCH_TRIPLET is deprecated, use CRAFT_ARCH_TRIPLET_BUILD_{ON|FOR}
2024-02-06 12:38:30.565 Checking build provider availability
2024-02-06 12:38:30.571 Retrieved snap config: {'provider': 'multipass'}
2024-02-06 12:38:30.571 Using provider 'multipass' from snap config.
2024-02-06 12:38:30.571 Executing on host: multipass version
2024-02-06 12:38:30.706 Using hostname 'snapcraft-photonotebook-on-amd64-for-amd64-45114395'
2024-02-06 12:38:30.707 Launching instance...
2024-02-06 12:38:30.707 Executing on host: multipass list --format json
2024-02-06 12:38:30.902 Executing on host: multipass start snapcraft-photonotebook-on-amd64-for-amd64-45114395
2024-02-06 12:38:31.027 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- test -f /etc/craft-instance.conf
2024-02-06 12:38:31.292 Executing on host: multipass transfer snapcraft-photonotebook-on-amd64-for-amd64-45114395:/etc/craft-instance.conf /home/alan/tmpvb83v0ur.tmp-craft/tmpi2jvoop9
2024-02-06 12:38:31.496 Cleaning incompatible instance 'snapcraft-photonotebook-on-amd64-for-amd64-45114395' (reason: instance is marked as not setup).
2024-02-06 12:38:31.497 Executing on host: multipass delete snapcraft-photonotebook-on-amd64-for-amd64-45114395 --purge
2024-02-06 12:38:35.050 Executing on host: multipass launch snapcraft:22.04 --name snapcraft-photonotebook-on-amd64-for-amd64-45114395 --cpus 2 --memory 2G --disk 64G
2024-02-06 12:39:25.901 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- test -f /etc/craft-instance.conf
2024-02-06 12:39:26.166 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-06 12:39:26.416 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.qopZFOhlog
2024-02-06 12:39:26.623 Created temporary file '/tmp/tmp.qopZFOhlog' inside instance.
2024-02-06 12:39:26.859 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.qopZFOhlog
2024-02-06 12:39:27.089 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.qopZFOhlog
2024-02-06 12:39:27.323 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.qopZFOhlog /etc/craft-instance.conf
2024-02-06 12:39:27.545 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- cat /etc/os-release
2024-02-06 12:39:27.764 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- test -f /etc/craft-instance.conf
2024-02-06 12:39:28.029 Executing on host: multipass transfer snapcraft-photonotebook-on-amd64-for-amd64-45114395:/etc/craft-instance.conf /home/alan/tmpjxbswmqr.tmp-craft/tmpn70mptyn
2024-02-06 12:39:28.246 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- test -f /etc/craft-instance.conf
2024-02-06 12:39:28.512 Executing on host: multipass transfer snapcraft-photonotebook-on-amd64-for-amd64-45114395:/etc/craft-instance.conf /home/alan/tmpqahjcr9o.tmp-craft/tmpolj4sngr
2024-02-06 12:39:28.737 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-06 12:39:28.943 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.gfD5QqM3ag
2024-02-06 12:39:29.150 Created temporary file '/tmp/tmp.gfD5QqM3ag' inside instance.
2024-02-06 12:39:29.452 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.gfD5QqM3ag
2024-02-06 12:39:29.655 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.gfD5QqM3ag
2024-02-06 12:39:29.882 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.gfD5QqM3ag /etc/craft-instance.conf
2024-02-06 12:39:30.122 No cache path set, not mounting cache directories.
2024-02-06 12:39:30.123 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-06 12:39:30.334 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.OtOUQEb9wx
2024-02-06 12:39:30.558 Created temporary file '/tmp/tmp.OtOUQEb9wx' inside instance.
2024-02-06 12:39:30.800 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.OtOUQEb9wx
2024-02-06 12:39:31.015 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.OtOUQEb9wx
2024-02-06 12:39:31.241 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.OtOUQEb9wx /etc/environment
2024-02-06 12:39:31.462 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-06 12:39:31.661 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.amTSUJmPNp
2024-02-06 12:39:31.878 Created temporary file '/tmp/tmp.amTSUJmPNp' inside instance.
2024-02-06 12:39:32.100 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.amTSUJmPNp
2024-02-06 12:39:32.311 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.amTSUJmPNp
2024-02-06 12:39:32.526 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.amTSUJmPNp /etc/apt/apt.conf.d/20auto-upgrades
2024-02-06 12:39:32.729 Waiting for environment to be ready...
2024-02-06 12:39:32.730 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- systemctl is-system-running
2024-02-06 12:39:32.943 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-06 12:39:33.157 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.yyRMbQbevI
2024-02-06 12:39:33.377 Created temporary file '/tmp/tmp.yyRMbQbevI' inside instance.
2024-02-06 12:39:33.589 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.yyRMbQbevI
2024-02-06 12:39:33.806 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.yyRMbQbevI
2024-02-06 12:39:34.036 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.yyRMbQbevI /etc/hostname
2024-02-06 12:39:34.269 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- hostname -F /etc/hostname
2024-02-06 12:39:34.489 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
2024-02-06 12:39:34.693 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- systemctl enable systemd-resolved
2024-02-06 12:39:35.078 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- systemctl restart systemd-resolved
2024-02-06 12:39:35.370 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-06 12:39:35.582 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.3ML968cs76
2024-02-06 12:39:35.794 Created temporary file '/tmp/tmp.3ML968cs76' inside instance.
2024-02-06 12:39:36.008 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.3ML968cs76
2024-02-06 12:39:36.230 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.3ML968cs76
2024-02-06 12:39:36.433 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.3ML968cs76 /etc/systemd/network/10-eth0.network
2024-02-06 12:39:36.660 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- systemctl enable systemd-networkd
2024-02-06 12:39:37.075 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- systemctl restart systemd-networkd
2024-02-06 12:39:37.346 Waiting for networking to be ready...
2024-02-06 12:39:37.346 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- getent hosts snapcraft.io
2024-02-06 12:39:37.582 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-06 12:39:37.819 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.CshdGwDC0e
2024-02-06 12:39:38.033 Created temporary file '/tmp/tmp.CshdGwDC0e' inside instance.
2024-02-06 12:39:38.248 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.CshdGwDC0e
2024-02-06 12:39:38.454 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.CshdGwDC0e
2024-02-06 12:39:38.670 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.CshdGwDC0e /etc/apt/apt.conf.d/00no-recommends
2024-02-06 12:39:38.891 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-06 12:39:39.093 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.6CdlKrrkJI
2024-02-06 12:39:39.317 Created temporary file '/tmp/tmp.6CdlKrrkJI' inside instance.
2024-02-06 12:39:39.972 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.6CdlKrrkJI
2024-02-06 12:39:40.182 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.6CdlKrrkJI
2024-02-06 12:39:40.408 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.6CdlKrrkJI /etc/apt/apt.conf.d/00update-errors
2024-02-06 12:39:40.618 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- apt-get update
2024-02-06 12:40:18.793 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- bash -c 'exec 3<> /dev/tcp/snapcraft.io/443'
2024-02-06 12:40:19.055 craft-providers error: Failed to update apt cache.
* Command that failed: 'multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- apt-get update'
* Command exit code: 100
* Command output: b'Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]\n
Get:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]\n
Get:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]\n
Get:4 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1,395 kB]\n
Get:5 http://archive.ubuntu.com/ubuntu jammy/main Translation-en [510 kB]\n
Get:6 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [129 kB]\n
Get:7 http://archive.ubuntu.com/ubuntu jammy/restricted Translation-en [18.6 kB]\n
Get:8 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [14.1 MB]\n
Get:9 http://archive.ubuntu.com/ubuntu jammy/universe Translation-en [5,652 kB]\n
Get:10 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [217 kB]\n
Get:11 http://archive.ubuntu.com/ubuntu jammy/multiverse Translation-en [112 kB]\n
Ign:12 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages\n
Ign:13 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en\n
Ign:14 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages\n
Ign:15 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en\n
Get:16 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1,043 kB]\n
Get:17 http://archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [235 kB]\n
Get:18 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [42.1 kB]\n
Get:19 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse Translation-en [10.1 kB]\n
Get:20 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [41.7 kB]\n
Get:21 http://archive.ubuntu.com/ubuntu jammy-backports/main Translation-en [10.5 kB]\n
Get:22 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [24.2 kB]\n
Get:23 http://archive.ubuntu.com/ubuntu jammy-backports/universe Translation-en [16.5 kB]\n
Get:12 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1,327 kB]\n
Err:12 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages\n
  File has unexpected size (1325500 != 1327396). Mirror sync in progress? [IP: 91.189.91.82 80]\n
    Hashes of expected file:\n   - Filesize:1327396 [weak]\n   - SHA256:58cbf7ca2a92cc139dd8a8609a567fc92d0797a1891b6532280fc3844e196f7a\n
       - SHA1:eead23ef84a770277f26596124ec3a7a7d60b669 [weak]\n
          - MD5Sum:26c5eeb3e6ac157ef48999327f2ffe80 [weak]\n
            Release file created at: Tue, 06 Feb 2024 12:06:35 +0000\n
Get:13 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [268 kB]\n
Get:14 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [1,346 kB]\n
Get:15 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en [220 kB]\n
Ign:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n
Ign:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n
Ign:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n
Err:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n
  Could not connect to security.ubuntu.com:80 (91.189.88.142), connection timed out\n
  Fetched 25.9 MB in 37s (694 kB/s)\nReading package lists...\n'
* Command standard error output: b"ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.\n
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease  Could not connect to security.ubuntu.com:80 (91.189.88.142), connection timed out\n
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-amd64/Packages.xz  File has unexpected size (1325500 != 1327396). Mirror sync in progress? [IP: 91.189.91.82 80]\n
   Hashes of expected file:\n    - Filesize:1327396 [weak]\n
       - SHA256:58cbf7ca2a92cc139dd8a8609a567fc92d0797a1891b6532280fc3844e196f7a\n
           - SHA1:eead23ef84a770277f26596124ec3a7a7d60b669 [weak]\n
               - MD5Sum:26c5eeb3e6ac157ef48999327f2ffe80 [weak]\n
Release file created at: Tue, 06 Feb 2024 12:06:35 +0000\n
E: Some index files failed to download. They have been ignored, or old ones used instead.\n"
2024-02-06 12:40:19.055 Full execution log: '/home/alan/.local/state/snapcraft/log/snapcraft-20240206-123830.547345.log'```

mr_cal · February 6, 2024, 3:14pm

I’m curious that the LXD and Multipass instances cannot reach security.ubuntu.com for core22 snaps. It appears they have network connectivity (they can reach archive.ubuntu.com and are able to run exec 3<> /dev/tcp/snapcraft.io/443). I don’t see any proxy envvars being passed into the instances.

What happens if you just launch an instance and run apt update?

multipass launch jammy --name test-env
multipass shell test-env
sudo apt update

P.S. You need to run ping security.ubuntu.com not ping http://security.ubuntu.com. Can you try that inside the instance as well?

apdw · February 6, 2024, 3:43pm

Hi Mr Cal,

did as you suggested, following is terminal output:

Tue Feb 06 15:36 => multipass shell test-env
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
Welcome to Ubuntu 22.04.3 LTS (GNU/Linux 5.15.0-92-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/pro

  System information as of Tue Feb  6 15:37:40 GMT 2024

  System load:  0.515625          Processes:             93
  Usage of /:   29.4% of 4.67GB   Users logged in:       0
  Memory usage: 20%               IPv4 address for ens3: 10.117.122.8
  Swap usage:   0%


Expanded Security Maintenance for Applications is not enabled.

0 updates can be applied immediately.

Enable ESM Apps to receive additional future security updates.
See https://ubuntu.com/esm or run: sudo pro status


The list of available updates is more than a week old.
To check for new updates run: sudo apt update

To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

ubuntu@test-env:~$ sudo apt update
Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Get:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]           
Get:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]              
Get:4 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1395 kB]             
Get:5 http://archive.ubuntu.com/ubuntu jammy/main Translation-en [510 kB]             
Get:6 http://archive.ubuntu.com/ubuntu jammy/main amd64 c-n-f Metadata [30.3 kB]                    
Get:7 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [129 kB]                     
Get:8 http://archive.ubuntu.com/ubuntu jammy/restricted Translation-en [18.6 kB]                    
Get:9 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 c-n-f Metadata [488 B]                
Get:10 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [14.1 MB]                     
Get:11 http://archive.ubuntu.com/ubuntu jammy/universe Translation-en [5652 kB]                     
Get:12 http://archive.ubuntu.com/ubuntu jammy/universe amd64 c-n-f Metadata [286 kB]                
Get:13 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [217 kB]                    
Get:14 http://archive.ubuntu.com/ubuntu jammy/multiverse Translation-en [112 kB]                    
Get:15 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 c-n-f Metadata [8372 B]              
Get:16 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1327 kB]                 
Get:17 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [268 kB]                  
Get:18 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 c-n-f Metadata [16.1 kB]           
Get:19 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [1346 kB]           
Get:20 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en [220 kB]            
Get:21 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 c-n-f Metadata [520 B]       
Get:22 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1043 kB]             
Get:23 http://archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [235 kB]              
Get:24 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 c-n-f Metadata [22.1 kB]       
Get:25 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [42.1 kB]           
Get:26 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse Translation-en [10.1 kB]           
Get:27 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 c-n-f Metadata [472 B]       
Get:28 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [41.7 kB]               
Get:29 http://archive.ubuntu.com/ubuntu jammy-backports/main Translation-en [10.5 kB]               
Get:30 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 c-n-f Metadata [388 B]           
Get:31 http://archive.ubuntu.com/ubuntu jammy-backports/restricted amd64 c-n-f Metadata [116 B]     
Get:32 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [24.2 kB]           
Get:33 http://archive.ubuntu.com/ubuntu jammy-backports/universe Translation-en [16.5 kB]           
Get:34 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 c-n-f Metadata [644 B]       
Get:35 http://archive.ubuntu.com/ubuntu jammy-backports/multiverse amd64 c-n-f Metadata [116 B]     
Ign:36 http://security.ubuntu.com/ubuntu jammy-security InRelease                                   
Ign:36 http://security.ubuntu.com/ubuntu jammy-security InRelease
Ign:36 http://security.ubuntu.com/ubuntu jammy-security InRelease
Err:36 http://security.ubuntu.com/ubuntu jammy-security InRelease
  Could not connect to security.ubuntu.com:80 (91.189.88.142), connection timed out
Fetched 27.6 MB in 37s (739 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease  Could not connect to security.ubuntu.com:80 (91.189.88.142), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.
ubuntu@test-env:~$

Looks like a similar problem

Ping:

Tue Feb 06 15:41 => ping security.ubuntu.com
PING security.ubuntu.com (91.189.88.142) 56(84) bytes of data.

^C
--- security.ubuntu.com ping statistics ---
59 packets transmitted, 0 received, 100% packet loss, time 59382ms

it doesn’t return from the ping without a Ctrl C!

cheers and thanks! Alan

apdw · February 6, 2024, 5:45pm

Hi Mr Cal,

More data:

Tue Feb 06 17:28 => multipass find
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
Image                       Aliases           Version          Description
core                        core16            20200818         Ubuntu Core 16
core18                                        20211124         Ubuntu Core 18
core20                                        20230119         Ubuntu Core 20
core22                                        20230717         Ubuntu Core 22
20.04                       focal             20240129.1       Ubuntu 20.04 LTS
22.04                       jammy,lts         20240126         Ubuntu 22.04 LTS
23.10                       mantic            20240206         Ubuntu 23.10
daily:24.04                 noble,devel       20240129         Ubuntu 24.04 LTS
appliance:adguard-home                        20200812         Ubuntu AdGuard Home Appliance
appliance:mosquitto                           20200812         Ubuntu Mosquitto Appliance
appliance:nextcloud                           20200812         Ubuntu Nextcloud Appliance
appliance:openhab                             20200812         Ubuntu openHAB Home Appliance
appliance:plexmediaserver                     20200812         Ubuntu Plex Media Server Appliance

Blueprint                   Aliases           Version          Description
anbox-cloud-appliance                         latest           Anbox Cloud Appliance
charm-dev                                     latest           A development and testing environment for charmers
docker                                        0.4              A Docker environment with Portainer and related tools
jellyfin                                      latest           Jellyfin is a Free Software Media System that puts you in control of managing and streaming your media.
minikube                                      latest           minikube is local Kubernetes
ros-noetic                                    0.1              A development and testing environment for ROS Noetic.
ros2-humble                                   0.1              A development and testing environment for ROS 2 Humble.

NB I seem to have a docker image in multipass! Is this important?

More:

Tue Feb 06 17:29 => multipass info
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
Name:           snapcraft-photonotebook
State:          Stopped
Snapshots:      0
IPv4:           --
Release:        --
Image hash:     e260a4a72e46 (Ubuntu 20.04 LTS)
CPU(s):         --
Load:           --
Disk usage:     --
Memory usage:   --
Mounts:         /home/alan/IdeaProjects/PhotoNoteBook-V3/snapLinux => /root/project
                    UID map: 1000:0
                    GID map: 1000:0

Name:           snapcraft-photonotebook-on-amd64-for-amd64-45114395
State:          Running
Snapshots:      0
IPv4:           10.117.122.117
Release:        Ubuntu 22.04.3 LTS
Image hash:     cdfc9dfd8bbb (Ubuntu 22.04 LTS)
CPU(s):         2
Load:           0.00 0.00 0.00
Disk usage:     1.2GiB out of 61.9GiB
Memory usage:   103.6MiB out of 1.9GiB
Mounts:         --

Name:           test-env
State:          Running
Snapshots:      0
IPv4:           10.117.122.8
Release:        Ubuntu 22.04.3 LTS
Image hash:     9f8a0d84b81a (Ubuntu 22.04 LTS)
CPU(s):         1
Load:           0.00 0.00 0.00
Disk usage:     1.6GiB out of 4.8GiB
Memory usage:   174.6MiB out of 951.9MiB
Mounts:         --

I don’t know if this helps! cheers Alan

mr_cal · February 7, 2024, 2:00pm

Thanks, rather than a Snapcraft issue, this is looking like a broader networking issue with accessing security.ubuntu.com (since it’s occurring in LXD and Multipass environments created by Snapcraft and in a Multipass environment not created Snapcraft).

Are you able to ping that URL from the machine where you are running Snapcraft? Are you going through any sort of firewall, proxy, or VPN?

apdw · February 7, 2024, 5:06pm

Hi Mr Cal,

tried a ping from my host OS, results as follows:

Wed Feb 07 17:09 => ping security.ubuntu.com
PING security.ubuntu.com (91.189.88.142) 56(84) bytes of data.
^C
--- security.ubuntu.com ping statistics ---
26 packets transmitted, 0 received, 100% packet loss, time 25576ms

Wed Feb 07 17:09 =>

I have to Crtl C for it to return.

My network rig here is a standard home wifi router, no VPN , external firewall or proxy. I have no problems with a core 20 build of the same snap.

Cheers and thanks Alan

mr_cal · February 7, 2024, 6:59pm

Interesting. I’m not sure why you wouldn’t be able to reach security.ubuntu.com on your host system without any special networking setup.

I don’t see the IP address that is resolved on your system (91.189.88.142). I get different set of addresses:

> host security.ubuntu.com
security.ubuntu.com has address 91.189.91.82
security.ubuntu.com has address 91.189.91.81
security.ubuntu.com has address 185.125.190.39
security.ubuntu.com has address 91.189.91.83
security.ubuntu.com has address 185.125.190.36
security.ubuntu.com has IPv6 address 2620:2d:4002:1::102
security.ubuntu.com has IPv6 address 2620:2d:4000:1::16
security.ubuntu.com has IPv6 address 2620:2d:4002:1::101
security.ubuntu.com has IPv6 address 2620:2d:4000:1::19
security.ubuntu.com has IPv6 address 2620:2d:4002:1::103

It might be worth flushing your DNS cache and trying again. Perhaps it’s an issue with the DNS server you are using?

apdw · February 8, 2024, 11:22am

Hi Mr Cal,

tried that, no difference. I also rebooted my wifi router, buit no change. I added some extra dns servers as follows:

sudo mkdir /etc/systemd/resolved.conf.d/
sudo nano /etc/systemd/resolved.conf.d/dns_servers.conf

and added the following to the file

[Resolve]
DNS=8.8.8.8 1.1.1.1

and reset the system with:

sudo systemctl restart systemd-resolved

as per AskUbuntu at https://askubuntu.com/questions/1406827/how-to-set-dns-on-ubuntu-22-04-when-you-have-no-netplan-config

I ran the hosts command:

Thu Feb 08 11:07 => host security.ubuntu.com
security.ubuntu.com has address 91.189.88.142
Thu Feb 08 11:13 =>

still the same DNS resolution.

WHOIS query on this IP address reveals:

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://apps.db.ripe.net/docs/HTML-Terms-And-Conditions

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '91.189.88.0 - 91.189.95.255'

% Abuse contact for '91.189.88.0 - 91.189.95.255' is 'email@canonical.com'

inetnum:        91.189.88.0 - 91.189.95.255
netname:        CANONICAL-CORE
country:        GB
org:            ORG-CGL14-RIPE
admin-c:        CAN-RIPE
tech-c:         CAN-RIPE
status:         ASSIGNED PI
mnt-by:         RIPE-NCC-END-MNT
mnt-by:         uk-canonical-1-mnt
mnt-by:         CANONICAL-MNT
mnt-routes:     CANONICAL-MNT
mnt-domains:    CANONICAL-MNT
created:        2007-01-25T15:15:07Z
last-modified:  2023-07-27T09:57:02Z
source:         RIPE

organisation:   ORG-CGL14-RIPE
org-name:       Canonical Group Limited
country:        GB
org-type:       LIR
address:        5 New Street Square
address:        EC4A 3TW
address:        London
address:        UNITED KINGDOM
phone:          +44 20 7630 2400
admin-c:        JF7136-RIPE
admin-c:        JT2256-RIPE
tech-c:         JT2256-RIPE
tech-c:         JF7136-RIPE
abuse-c:        AR34067-RIPE
mnt-ref:        uk-canonical-1-mnt
mnt-ref:        CANONICAL-MNT
mnt-by:         RIPE-NCC-HM-MNT
mnt-by:         uk-canonical-1-mnt
mnt-ref:        RIPE-NCC-HM-MNT
created:        2015-11-02T10:21:03Z
last-modified:  2023-12-13T08:04:59Z
source:         RIPE # Filtered

role:           Canonical Ltd Admin
address:        1 Circular Road
address:        Douglas
address:        Isle of Man
address:        IM1 1AF
admin-c:        JT2256-RIPE
admin-c:        JF7136-RIPE
admin-c:        NM1806-RIPE
tech-c:         JT2256-RIPE
tech-c:         JF7136-RIPE
tech-c:         NM1806-RIPE
nic-hdl:        CAN-RIPE
mnt-by:         CANONICAL-MNT
created:        2008-03-31T14:32:55Z
last-modified:  2020-06-24T15:34:35Z
source:         RIPE # Filtered

% Information related to '91.189.88.0/24AS41231'

route:          91.189.88.0/24
descr:          Canonical Route Object
origin:         AS41231
mnt-by:         CANONICAL-MNT
created:        2013-02-20T23:08:09Z
last-modified:  2013-02-20T23:08:09Z
source:         RIPE

% This query was served by the RIPE Database Query Service version 1.109.1 (BUSA)

I don’t know if this helps, but the IP address resolved seems to be in the correct block for Canonical. cheers and thanks Alan

apdw · February 8, 2024, 12:34pm

Some small advance. I looked into DNS issues around 22.04 and thgere seems to be the potential for conflict between Network Manager and resolve.conf First:

sudo gedit /etc/systemd/resolved.conf.d/dns_servers.conf

adding the lines to the file

[Resolve]
DNS=8.8.8.8 1.1.1.1

I then did the following

sudo rm -f /etc/resolv.conf
sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf

and rebooted.

Using the hosts command I now have the following resolutions:

Thu Feb 08 11:55 => host security.ubuntu.com
security.ubuntu.com has address 91.189.91.81
security.ubuntu.com has address 185.125.190.39
security.ubuntu.com has address 185.125.190.36
security.ubuntu.com has address 91.189.91.82
security.ubuntu.com has address 91.189.91.83
security.ubuntu.com has IPv6 address 2620:2d:4002:1::102
security.ubuntu.com has IPv6 address 2620:2d:4002:1::101
security.ubuntu.com has IPv6 address 2620:2d:4000:1::16
security.ubuntu.com has IPv6 address 2620:2d:4002:1::103
security.ubuntu.com has IPv6 address 2620:2d:4000:1::19
Thu Feb 08 11:56 =>

but ping fails:

Thu Feb 08 12:11 => ping security.ubuntu.com
PING security.ubuntu.com (91.189.88.142) 56(84) bytes of data.
^C
--- security.ubuntu.com ping statistics ---
11 packets transmitted, 0 received, 100% packet loss, time 10222ms

Thu Feb 08 12:11 =>

the two resolve.conf files contain:

nameserver 8.8.8.8
nameserver 1.1.1.1
nameserver 192.168.1.254
search home

making the core 22 based snap fails as before. What we seem to have here is a know networking issue for 22 where Netplan was introduced. Apparently there needs to be network config files for each virtual and real OS, and there are conflicts between the various network control systems if not configured properly.

See https://askubuntu.com/questions/1406630/hostnames-cannot-be-resolved-after-upgrading-to-22-04 for some info.

I will investigate! cheers Alan

ogra · February 8, 2024, 1:14pm

resolvconf has been deprecated ages ago … i wonder how you got it installed on a 22.04 system, Ubuntu uses systemd-resolved exclusively since 20.04, having resolveconf installed on such a system will surely cause issues as each of them will step on each others toes (though your actual issue does not seem DNS related at all, since it resolves, but your ping does not get through then, but if you have resolvconf installed there might be other networking bits that are incorrectly installed on this machine too)

apdw · February 8, 2024, 3:18pm

Hi Ogra,

this is a 16 to 18 to 20 to 22 LTS upgrade machine, so who knows what’s leftover!!

Since my mods I ran the snapcraft against core22 and got a different set of network errors, which I’ll post shortly.

Cheers and Thanks!

Alan

apdw · February 8, 2024, 3:32pm

Hi, I ran the snapcraft against the core22 again and I seem to have a different set of error messages: the system seems to be trying and failing to communiucate with security.ubuntu.com on an IPV6 as well as an IPV4 address. Here’s the log …

2024-02-08 13:20:45.835 Raw pre-parsed sysargs: args={'help': False, 'verbose': False, 'quiet': False, 'verbosity': 'trace', 'version': False, 'trace': False} filtered=[]
2024-02-08 13:20:45.835 Using default command: 'pack'
2024-02-08 13:20:45.835 General parsed sysargs: command='pack' args=[]
2024-02-08 13:20:45.836 Command parsed sysargs: Namespace(destructive_mode=False, use_lxd=False, debug=False, enable_manifest=False, manifest_image_information=None, bind_ssh=False, build_for=None, http_proxy=None, https_proxy=None, ua_token=None, enable_experimental_ua_services=False, enable_experimental_plugins=False, enable_experimental_extensions=False, enable_developer_debug=False, enable_experimental_target_arch=False, target_arch=None, provider=None, directory=None, output=None)
2024-02-08 13:20:45.837 lifecycle command: 'pack', arguments: Namespace(destructive_mode=False, use_lxd=False, debug=False, enable_manifest=False, manifest_image_information=None, bind_ssh=False, build_for=None, http_proxy=None, https_proxy=None, ua_token=None, enable_experimental_ua_services=False, enable_experimental_plugins=False, enable_experimental_extensions=False, enable_developer_debug=False, enable_experimental_target_arch=False, target_arch=None, provider=None, directory=None, output=None)
2024-02-08 13:20:45.837 command: pack, arguments: Namespace(destructive_mode=False, use_lxd=False, debug=False, enable_manifest=False, manifest_image_information=None, bind_ssh=False, build_for=None, http_proxy=None, https_proxy=None, ua_token=None, enable_experimental_ua_services=False, enable_experimental_plugins=False, enable_experimental_extensions=False, enable_developer_debug=False, enable_experimental_target_arch=False, target_arch=None, provider=None, directory=None, output=None)
2024-02-08 13:20:45.847 Created build plan:
  build-on: amd64 build-for: amd64
2024-02-08 13:20:45.847 CPU count (from process affinity): 8
2024-02-08 13:20:45.847 Invalid SNAPCRAFT_MAX_PARALLEL_BUILD_COUNT ''
2024-02-08 13:20:45.847 Running on amd64 for amd64
2024-02-08 13:20:45.848 CRAFT_ARCH_TRIPLET is deprecated, use CRAFT_ARCH_TRIPLET_BUILD_{ON|FOR}
2024-02-08 13:20:45.848 CRAFT_ARCH_TRIPLET is deprecated, use CRAFT_ARCH_TRIPLET_BUILD_{ON|FOR}
2024-02-08 13:20:45.849 CRAFT_ARCH_TRIPLET is deprecated, use CRAFT_ARCH_TRIPLET_BUILD_{ON|FOR}
2024-02-08 13:20:45.849 CRAFT_ARCH_TRIPLET is deprecated, use CRAFT_ARCH_TRIPLET_BUILD_{ON|FOR}
2024-02-08 13:20:45.850 Checking build provider availability
2024-02-08 13:20:45.855 Retrieved snap config: {'provider': 'multipass'}
2024-02-08 13:20:45.855 Using provider 'multipass' from snap config.
2024-02-08 13:20:45.856 Executing on host: multipass version
2024-02-08 13:20:45.983 Using hostname 'snapcraft-photonotebook-on-amd64-for-amd64-45114395'
2024-02-08 13:20:45.983 Launching instance...
2024-02-08 13:20:45.983 Executing on host: multipass list --format json
2024-02-08 13:20:46.231 Executing on host: multipass launch snapcraft:22.04 --name snapcraft-photonotebook-on-amd64-for-amd64-45114395 --cpus 2 --memory 2G --disk 64G
2024-02-08 13:21:37.147 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- test -f /etc/craft-instance.conf
2024-02-08 13:21:37.412 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-08 13:21:37.656 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.yVRLGKfebA
2024-02-08 13:21:37.878 Created temporary file '/tmp/tmp.yVRLGKfebA' inside instance.
2024-02-08 13:21:38.097 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.yVRLGKfebA
2024-02-08 13:21:38.332 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.yVRLGKfebA
2024-02-08 13:21:38.555 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.yVRLGKfebA /etc/craft-instance.conf
2024-02-08 13:21:38.772 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- cat /etc/os-release
2024-02-08 13:21:38.984 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- test -f /etc/craft-instance.conf
2024-02-08 13:21:39.249 Executing on host: multipass transfer snapcraft-photonotebook-on-amd64-for-amd64-45114395:/etc/craft-instance.conf /home/alan/tmpjk2fyfwy.tmp-craft/tmp26fyhn4e
2024-02-08 13:21:39.473 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- test -f /etc/craft-instance.conf
2024-02-08 13:21:39.738 Executing on host: multipass transfer snapcraft-photonotebook-on-amd64-for-amd64-45114395:/etc/craft-instance.conf /home/alan/tmpzfjzrwmi.tmp-craft/tmpam5qb2ey
2024-02-08 13:21:39.952 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-08 13:21:40.167 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.YQDKzCrB8W
2024-02-08 13:21:40.388 Created temporary file '/tmp/tmp.YQDKzCrB8W' inside instance.
2024-02-08 13:21:40.596 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.YQDKzCrB8W
2024-02-08 13:21:40.803 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.YQDKzCrB8W
2024-02-08 13:21:41.014 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.YQDKzCrB8W /etc/craft-instance.conf
2024-02-08 13:21:41.224 No cache path set, not mounting cache directories.
2024-02-08 13:21:41.224 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-08 13:21:41.442 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.Y623EUcxO0
2024-02-08 13:21:41.674 Created temporary file '/tmp/tmp.Y623EUcxO0' inside instance.
2024-02-08 13:21:41.888 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.Y623EUcxO0
2024-02-08 13:21:42.116 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.Y623EUcxO0
2024-02-08 13:21:42.345 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.Y623EUcxO0 /etc/environment
2024-02-08 13:21:42.556 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-08 13:21:42.763 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.VHftsuwI84
2024-02-08 13:21:43.000 Created temporary file '/tmp/tmp.VHftsuwI84' inside instance.
2024-02-08 13:21:43.240 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.VHftsuwI84
2024-02-08 13:21:43.468 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.VHftsuwI84
2024-02-08 13:21:43.687 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.VHftsuwI84 /etc/apt/apt.conf.d/20auto-upgrades
2024-02-08 13:21:43.918 Waiting for environment to be ready...
2024-02-08 13:21:43.918 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- systemctl is-system-running
2024-02-08 13:21:44.128 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-08 13:21:44.347 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.nhaBTt8YoQ
2024-02-08 13:21:44.556 Created temporary file '/tmp/tmp.nhaBTt8YoQ' inside instance.
2024-02-08 13:21:44.762 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.nhaBTt8YoQ
2024-02-08 13:21:44.959 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.nhaBTt8YoQ
2024-02-08 13:21:45.156 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.nhaBTt8YoQ /etc/hostname
2024-02-08 13:21:45.379 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- hostname -F /etc/hostname
2024-02-08 13:21:45.600 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
2024-02-08 13:21:45.832 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- systemctl enable systemd-resolved
2024-02-08 13:21:46.243 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- systemctl restart systemd-resolved
2024-02-08 13:21:46.554 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-08 13:21:46.761 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.d3n6ct10ZW
2024-02-08 13:21:46.984 Created temporary file '/tmp/tmp.d3n6ct10ZW' inside instance.
2024-02-08 13:21:47.190 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.d3n6ct10ZW
2024-02-08 13:21:47.412 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.d3n6ct10ZW
2024-02-08 13:21:47.639 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.d3n6ct10ZW /etc/systemd/network/10-eth0.network
2024-02-08 13:21:47.871 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- systemctl enable systemd-networkd
2024-02-08 13:21:48.270 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- systemctl restart systemd-networkd
2024-02-08 13:21:48.552 Waiting for networking to be ready...
2024-02-08 13:21:48.552 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- getent hosts snapcraft.io
2024-02-08 13:21:48.776 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-08 13:21:49.000 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.MvqlNdlz51
2024-02-08 13:21:49.228 Created temporary file '/tmp/tmp.MvqlNdlz51' inside instance.
2024-02-08 13:21:49.459 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.MvqlNdlz51
2024-02-08 13:21:49.700 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.MvqlNdlz51
2024-02-08 13:21:49.913 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.MvqlNdlz51 /etc/apt/apt.conf.d/00no-recommends
2024-02-08 13:21:50.135 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mktemp
2024-02-08 13:21:50.348 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown ubuntu:ubuntu /tmp/tmp.eUoTceDFPX
2024-02-08 13:21:50.579 Created temporary file '/tmp/tmp.eUoTceDFPX' inside instance.
2024-02-08 13:21:50.863 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chown root:root /tmp/tmp.eUoTceDFPX
2024-02-08 13:21:51.088 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- chmod 0644 /tmp/tmp.eUoTceDFPX
2024-02-08 13:21:51.312 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- mv /tmp/tmp.eUoTceDFPX /etc/apt/apt.conf.d/00update-errors
2024-02-08 13:21:51.536 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- apt-get update
2024-02-08 13:22:29.937 Executing on host: multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- bash -c 'exec 3<> /dev/tcp/snapcraft.io/443'
2024-02-08 13:22:30.188 craft-providers error: Failed to update apt cache.
* Command that failed: 'multipass exec snapcraft-photonotebook-on-amd64-for-amd64-45114395 -- sudo -H -- apt-get update'
* Command exit code: 100
* Command output: b'Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]\n
Get:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]\n
Get:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]\n
Get:4 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1,395 kB]\n
Get:5 http://archive.ubuntu.com/ubuntu jammy/main Translation-en [510 kB]\n
Get:6 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [129 kB]\n
Get:7 http://archive.ubuntu.com/ubuntu jammy/restricted Translation-en [18.6 kB]\n
Get:8 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [14.1 MB]\n
Get:9 http://archive.ubuntu.com/ubuntu jammy/universe Translation-en [5,652 kB]\n
Get:10 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [217 kB]\n
Get:11 http://archive.ubuntu.com/ubuntu jammy/multiverse Translation-en [112 kB]\n
Get:12 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1,362 kB]\n
Get:13 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [271 kB]\n
Get:14 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [1,404 kB]\n
Get:15 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en [231 kB]\n
Get:16 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1,043 kB]\n
Get:17 http://archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [235 kB]\n
Get:18 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [42.1 kB]\n
Get:19 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse Translation-en [10.1 kB]\n
Get:20 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [41.7 kB]\n
Get:21 http://archive.ubuntu.com/ubuntu jammy-backports/main Translation-en [10.5 kB]\n
Get:22 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [24.2 kB]\n
Get:23 http://archive.ubuntu.com/ubuntu jammy-backports/universe Translation-en [16.5 kB]\n
Ign:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n
Ign:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n
Ign:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n
Err:24 http://security.ubuntu.com/ubuntu jammy-security InRelease\n
  Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::16). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::19). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:80 (91.189.88.142), connection timed out\nFetched 27.3 MB in 37s (732 kB/s)\n
Reading package lists...\n'
* Command standard error output: b"ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.\n
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease  Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::16). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::19). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:80 (91.189.88.142), connection timed out\n
E: Some index files failed to download. They have been ignored, or old ones used instead.\n"

host and ping security.ubuntu.com. Ping now works!

Thu Feb 08 13:22 => host security.ubuntu.com
security.ubuntu.com has address 91.189.91.83
security.ubuntu.com has address 185.125.190.39
security.ubuntu.com has address 91.189.91.81
security.ubuntu.com has address 91.189.91.82
security.ubuntu.com has address 185.125.190.36
security.ubuntu.com has IPv6 address 2620:2d:4000:1::19
security.ubuntu.com has IPv6 address 2620:2d:4002:1::101
security.ubuntu.com has IPv6 address 2620:2d:4002:1::103
security.ubuntu.com has IPv6 address 2620:2d:4000:1::16
security.ubuntu.com has IPv6 address 2620:2d:4002:1::102
Thu Feb 08 15:25 => ping security.ubuntu.com
PING security.ubuntu.com(ubuntu-mirror-3.ps6.canonical.com (2620:2d:4002:1::103)) 56 data bytes
64 bytes from ubuntu-mirror-3.ps6.canonical.com (2620:2d:4002:1::103): icmp_seq=1 ttl=50 time=137 ms
64 bytes from ubuntu-mirror-3.ps6.canonical.com (2620:2d:4002:1::103): icmp_seq=2 ttl=50 time=83.6 ms
64 bytes from ubuntu-mirror-3.ps6.canonical.com (2620:2d:4002:1::103): icmp_seq=3 ttl=50 time=84.0 ms
64 bytes from ubuntu-mirror-3.ps6.canonical.com (2620:2d:4002:1::103): icmp_seq=4 ttl=50 time=83.0 ms
^Z
[1]+  Stopped                 ping security.ubuntu.com
Thu Feb 08 15:26 =>

I need to repeat some of the tests advised by Mr Cal yesterday.

Cheers and Thanks

Alan

apdw · February 8, 2024, 3:56pm

Hi,

following on from Mr Cal’s advice I created another mutipass test environment, and tried host and ping commands:

ubuntu@test-env2:~$ host security.ubuntu.com
security.ubuntu.com has address 91.189.88.142
security.ubuntu.com has IPv6 address 2620:2d:4000:1::19
security.ubuntu.com has IPv6 address 2620:2d:4002:1::103
security.ubuntu.com has IPv6 address 2620:2d:4002:1::102
security.ubuntu.com has IPv6 address 2620:2d:4000:1::16
security.ubuntu.com has IPv6 address 2620:2d:4002:1::101
ubuntu@test-env2:~$ ping security.ubuntu.com
PING security.ubuntu.com (91.189.88.142) 56(84) bytes of data.
^Z
[1]+  Stopped                 ping security.ubuntu.com
ubuntu@test-env2:~$ cd /etc/hosts

running apt-get update in the test env gives:

ubuntu@test-env2:~$ sudo apt-get update
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Get:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]            
Get:4 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [14.1 MB]         
Get:5 http://archive.ubuntu.com/ubuntu jammy/universe Translation-en [5652 kB]                     
Get:6 http://archive.ubuntu.com/ubuntu jammy/universe amd64 c-n-f Metadata [286 kB]                
Get:7 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [217 kB]                    
Get:8 http://archive.ubuntu.com/ubuntu jammy/multiverse Translation-en [112 kB]                    
Get:9 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 c-n-f Metadata [8372 B]              
Get:10 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1362 kB]                
Get:11 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [271 kB]                 
Get:12 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [1404 kB]          
Get:13 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en [231 kB]           
Get:14 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1043 kB]            
Get:15 http://archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [235 kB]             
Get:16 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 c-n-f Metadata [22.1 kB]      
Get:17 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [42.1 kB]          
Get:18 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse Translation-en [10.1 kB]          
Get:19 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 c-n-f Metadata [472 B]      
Get:20 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [41.7 kB]              
Get:21 http://archive.ubuntu.com/ubuntu jammy-backports/main Translation-en [10.5 kB]              
Get:22 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 c-n-f Metadata [388 B]          
Get:23 http://archive.ubuntu.com/ubuntu jammy-backports/restricted amd64 c-n-f Metadata [116 B]    
Get:24 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [24.2 kB]          
Get:25 http://archive.ubuntu.com/ubuntu jammy-backports/universe Translation-en [16.5 kB]          
Get:26 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 c-n-f Metadata [644 B]      
Get:27 http://archive.ubuntu.com/ubuntu jammy-backports/multiverse amd64 c-n-f Metadata [116 B]    
Ign:28 http://security.ubuntu.com/ubuntu jammy-security InRelease                                  
Ign:28 http://security.ubuntu.com/ubuntu jammy-security InRelease
Ign:28 http://security.ubuntu.com/ubuntu jammy-security InRelease
Err:28 http://security.ubuntu.com/ubuntu jammy-security InRelease
  Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::19). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::16). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:80 (91.189.88.142), connection timed out
Fetched 25.3 MB in 37s (678 kB/s)
Reading package lists... Done
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease  Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::19). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:80 (2620:2d:4000:1::16). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:80 (91.189.88.142), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.
ubuntu@test-env2:~$

Its picking up the incorrect IPV4 address from somewhere. Where do these virtual OS’s get their network config from? If I can find that, I may be able to fix this.

cheers and thanks Alan

apdw · February 8, 2024, 5:25pm

Hi! In desperation I installed NetworkManager snap, tried a config viewing commands. Tried to ping from my test-env2 multipass environment but there was no change.

Rebooted, now everything is fine. My snap has snapped on core 22 with no error. I do not know why!

ubuntu@test-env2:~$ ping security.ubuntu.com
PING security.ubuntu.com (91.189.91.81) 56(84) bytes of data.
64 bytes from ubuntu-mirror-1.ps6.canonical.com (91.189.91.81): icmp_seq=1 ttl=49 time=84.4 ms
64 bytes from ubuntu-mirror-1.ps6.canonical.com (91.189.91.81): icmp_seq=2 ttl=49 time=82.8 ms
64 bytes from ubuntu-mirror-1.ps6.canonical.com (91.189.91.81): icmp_seq=3 ttl=49 time=82.5 ms
64 bytes from ubuntu-mirror-1.ps6.canonical.com (91.189.91.81): icmp_seq=4 ttl=49 time=82.9 ms
64 bytes from ubuntu-mirror-1.ps6.canonical.com (91.189.91.81): icmp_seq=5 ttl=49 time=82.7 ms
^Z
[1]+  Stopped                 ping security.ubuntu.com

ubuntu@test-env2:~$ host security.ubuntu.com
security.ubuntu.com has address 91.189.91.83
security.ubuntu.com has address 91.189.91.81
security.ubuntu.com has address 185.125.190.36
security.ubuntu.com has address 185.125.190.39
security.ubuntu.com has address 91.189.91.82
security.ubuntu.com has IPv6 address 2620:2d:4000:1::16
security.ubuntu.com has IPv6 address 2620:2d:4000:1::19
security.ubuntu.com has IPv6 address 2620:2d:4002:1::103
security.ubuntu.com has IPv6 address 2620:2d:4002:1::102
security.ubuntu.com has IPv6 address 2620:2d:4002:1::101
ubuntu@test-env2:~$

from the older test environment there are similar successful results.

Thanks for all your help Mr Cal and Ogra!

cheers Alan

mr_cal · February 8, 2024, 8:01pm

Glad to hear you figured it out!

apdw · February 9, 2024, 10:12am

Thanks Mr Cal!

I’m not sure “figured it out” is the most appropriate term! More “hacked around in desperation”!

cheers

Alan