UbuntuMATE 26.04 Live ISO - Try and Install - No network functionality

ericmarceau · January 10, 2026, 5:27am

ISSUE:

During Live session, “installer” has no network set up!

During Installation, no additional actions taken by installer to establish network connection, again leaving in state with not network set up!

Note: Earlier report that issue existed for Nov 19 2025 Daily Build was not deemed “relevant” due to age of report, made in December. Hopefully, this report will receive a bit more respect being for the latest (at this time) build.

PLATFORM DETAILS

Version: Jan 9 2026 Daily Build

File listing:

-rw-rw-r-- 1 ericthered ericthered 4360919040 Jan  9 15:53  UbuntuMATE__26.04_LTS__2026-01-09__resolute-desktop-amd64.iso

Report: lsb_release -a

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu Resolute Raccoon (development branch)
Release:	26.04
Codename:	resolute

Report: uname -a

Linux OasisMidi 6.18.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC Wed Dec 17 16:14:24 UTC 2025 x86_64 GNU/Linux

Report: inxi -Fxxx

System:
  Host: OasisMidi Kernel: 6.18.0-8-generic arch: x86_64 bits: 64 compiler: gcc
    v: 15.2.0 clocksource: tsc
  Desktop: MATE v: 1.28.2 wm: marco v: 1.26.2 with: mate-panel
    tools: mate-screensaver dm: LightDM v: 1.32.0 Distro: MATE 26.04 (Resolute
    Raccoon) base: Ubuntu
Machine:
  Type: Desktop Mobo: ASUSTeK model: M4A78-E v: Rev 1.xx
    serial: <superuser required> uuid: <superuser required> Firmware: BIOS
    vendor: American Megatrends v: 2603 date: 04/13/2011
CPU:
  Info: quad core model: AMD Phenom II X4 810 bits: 64 type: MCP
    smt: <unsupported> arch: K10 rev: 2 cache: L1: 512 KiB L2: 2 MiB L3: 4 MiB
  Speed (MHz): avg: 800 min/max: 800/2600 boost: disabled cores: 1: 800
    2: 800 3: 800 4: 800 bogomips: 20869
  Flags-basic: ht lm nx pae sse sse2 sse3 sse4a svm
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] RS780D [Radeon HD 3300]
    vendor: ASUSTeK driver: radeon v: kernel arch: TeraScale ports:
    active: VGA-1 empty: DVI-D-1 bus-ID: 01:05.0 chip-ID: 1002:9614
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.21 compositor: marco v: 1.26.2 driver:
    X: loaded: radeon unloaded: fbdev,modesetting,vesa dri: r600 gpu: radeon
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1440x900 s-dpi: 96 s-size: 381x238mm (15.00x9.37")
    s-diag: 449mm (17.69")
  Monitor-1: VGA-1 mapped: VGA-0 model: HP w1707 serial: CNC918Q23B res:
    mode: 1440x900 hz: 60 scale: 100% (1) dpi: 99 size: 370x230mm (14.57x9.06")
    diag: 436mm (17.2") modes: max: 1440x900 min: 720x400
  API: EGL v: 1.5 hw: drv: amd r600 platforms: device: 0 drv: r600 device: 1
    drv: swrast gbm: drv: kms_swrast surfaceless: drv: r600 x11: drv: r600
    inactive: wayland
  API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 25.2.8-2ubuntu1
    glx-v: 1.4 direct-render: yes renderer: AMD RS780 (DRM 2.51.0 /
    6.18.0-8-generic LLVM 20.1.8) device-ID: 1002:9614
  Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] SBx00 Azalia
    driver: snd_hda_intel v: kernel bus-ID: 00:14.2 chip-ID: 1002:4383
    class-ID: 0403
  Device-2: Advanced Micro Devices [AMD/ATI] RS780 HDMI Audio [Radeon
    3000/3100 / HD 3200/3300] driver: snd_hda_intel v: kernel bus-ID: 01:05.1
    chip-ID: 1002:960f class-ID: 0403
  API: ALSA v: k6.18.0-8-generic status: kernel-api
  Server-1: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active
Network:
  Device-1: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet
    vendor: ASUSTeK driver: ATL1E v: N/A pcie: speed: 2.5 GT/s lanes: 1
    port: dc00 bus-ID: 02:00.0 chip-ID: 1969:1026 class-ID: 0200
  IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: 00:26:18:8a:b5:7a
Drives:
  Local Storage: total: 2.27 TiB used: 11.26 GiB (0.5%)
  ID-1: /dev/sda vendor: Western Digital model: WD5000AAKS-00V1A0
    size: 465.76 GiB speed: 1.5 Gb/s tech: N/A serial: WD-WMAWF0060756
    fw-rev: 1D05 scheme: GPT
  ID-2: /dev/sdb vendor: Western Digital model: WD20EZRX-00DC0B0
    size: 1.82 TiB speed: 3.0 Gb/s tech: N/A serial: WD-WCC300611350
    fw-rev: 0A80 scheme: GPT
Partition:
  ID-1: / size: 451.47 GiB used: 11.26 GiB (2.5%) fs: ext4 dev: /dev/sda2
Swap:
  ID-1: swap-1 type: file size: 3.51 GiB used: 936 KiB (0.0%) priority: -2
    file: /swap.img
Sensors:
  System Temperatures: cpu: 54.0 C mobo: 40.0 C
  Fan Speeds (rpm): cpu: 2351 case-1: 0 case-2: 0
  Power: 12v: 12.42 5v: N/A 3.3v: 3.46 vbat: N/A
Info:
  Memory: total: 4 GiB note: est. available: 3.51 GiB used: 1.68 GiB (47.9%)
  Processes: 220 Power: uptime: 20m states: freeze,mem,disk suspend: deep
    wakeups: 0 hibernate: platform Init: systemd v: 257 default: graphical
  Packages: 2059 pm: dpkg pkgs: 2048 pm: snap pkgs: 11 Compilers:
    gcc: 15.2.0 Shell: Bash v: 5.3.3 running-in: mate-terminal inxi: 3.3.40

[ EDIT: This is the post with my earlier reporting. ]

rubi1200 · January 10, 2026, 7:02am

Please file a new bug report or update an existing one, whichever is relevant.

You are welcome to share the link to the report here but the relevant parties are not coming here to check whether there are issues with development releases.

Thanks

ericmarceau · January 11, 2026, 2:21am

Thank you, @rubi1200.

First time I’ve done this formally. What should I be filing the bug under?

networking,
installer, or
live ISO?

guiverc · January 11, 2026, 2:38am

I’d probably open a terminal and look to see where the issue is..

Probably using ip link first to see if my network appears to be recognized, on the box I’m using now I see device enp0s31f6: which has a state of “UP” thus I’d continue.. Next I’d probably use ip addr to see it got an address that makes sense to me, then ip route to ensure routing appears to be correct for the network I’m on. Finally I’d probably ping 8.8.8.8 to see if I get a response, then ping google.com(ie. first ping checks [WAN] network, second ping adds DNS; you could add -c 1 too if you wanted; and if I had issues with those pings I’d go more local, eg. my ISPs IP address, then closer being my own external router). FYI: For some of my devices here they’ll be getting DHCP addresses, but for other boxes they won’t be (intentionally), and some get routed to a sink by my DHCP server which may explain why I’m doing it this way. If the ip link appeared to not recognize the network device; I’d probably have run a sudo lshw -C network next to see if it looks correct there.

If it appears my networking hardware isn’t recognized; I’d file against the kernel, ie. ubuntu-bug linux (do note the current 6.18 kernel won’t be used for that long, we’ll advance and the release will actually use 6.20 anyway)

If the networking appears correct at terminal on my exploration, but isn’t being recognized by the installer itself when you run it, I’d just use ubuntu-bug and select the installer when asked (by apport) what to file against.

If you’re recording the result on the ISO QA tracker, it will be recorded against the ISO date you say you’re running it under, but the ISO itself will be recorded when the bug has been filed on launchpad and you use ubuntu-bug from a live session (the apport tools autofill details from your live system when ubuntu-bug is run).

ericmarceau · January 11, 2026, 4:19am

Thank you, Chris, for that guidance. Here is what I was able to gather together:

COMMAND: ip link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 00:26:18:8a:b5:7a brd ff:ff:ff:ff:ff:ff
    altname enx0026188ab57a

COMMAND: ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:26:18:8a:b5:7a brd ff:ff:ff:ff:ff:ff
    altname enx0026188ab57a
    inet 192.168.0.10/24 brd 192.168.0.255 scope global dynamic noprefixroute enp2s0
       valid_lft 604116sec preferred_lft 528516sec
    inet6 fd00:8494:8c30:fac2:158:51fa:b9c7:5891/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 534741sec preferred_lft 400884sec
    inet6 fe80::fb50:4273:64f2:555b/64 scope link 
       valid_lft forever preferred_lft forever

COMMAND: ip route

default via 192.168.0.1 dev enp2s0 proto dhcp src 192.168.0.10 metric 1002 
169.254.0.0/16 dev enp2s0 scope link metric 1000 
192.168.0.0/24 dev enp2s0 proto dhcp scope link src 192.168.0.10 metric 1002

COMMAND: ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=16.9 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=16.0 ms
   * * *
64 bytes from 8.8.8.8: icmp_seq=13 ttl=117 time=11.9 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=117 time=15.1 ms
^C
--- 8.8.8.8 ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 13018ms
rtt min/avg/max/mdev = 10.154/13.827/21.110/2.739 ms

root@ubuntu-mate:/run/media/DB001_F2/home/ericthered.Downloads# ping -c1 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=16.8 ms

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 16.795/16.795/16.795/0.000 ms

COMMAND: sudo lshw -C network

  *-network                 
       description: Ethernet interface
       product: AR8121/AR8113/AR8114 Gigabit or Fast Ethernet
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: enp2s0
       version: b0
       serial: 00:26:18:8a:b5:7a
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=ATL1E driverversion=6.18.0-8-generic duplex=full firmware=L1e ip=192.168.0.10 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:18 memory:fbec0000-fbefffff ioport:dc00(size=128)

root@ubuntu-mate:/run/media/DB001_F2/home/ericthered.Downloads#

I’ve also included a few logs, hoping those would provide insights:

COMMAND: grep -i network boot.log

[  OK  ] Reached target network-pre.target - Preparation for Network.
         Starting networking.service - Raise network interfaces...
[FAILED] Failed to start networking.service - Raise network interfaces.
See 'systemctl status networking.service' for details.
         Starting networkd-dispatcher.service - Dispatcher daemon for systemd-networkd...
         Starting NetworkManager.service - Network Manager...
         Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
[  OK  ] Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
[  OK  ] Started networkd-dispatcher.service - Dispatcher daemon for systemd-networkd.
[  OK  ] Started NetworkManager.service - Network Manager.
[  OK  ] Reached target network.target - Network.
         Starting NetworkManager-wait-online.service - Network Manager Wait Online...
[  OK  ] Finished NetworkManager-wait-online.service - Network Manager Wait Online.
         Starting cloud-init-network.service - Cloud-init: Network Stage...
[  OK  ] Finished cloud-init-network.service - Cloud-init: Network Stage.
[  OK  ] Reached target network-online.target - Network is Online.

root@ubuntu-mate:/var/log#

COMMAND: grep enp2s0 syslog

2026-01-11T03:01:04.189091+00:00 ubuntu-mate ifup[1832]: Dropped protocol specifier '.link' from 'enp2s0.link'. Using 'enp2s0' (ifindex=2).
2026-01-11T03:01:04.189104+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: waiting for carrier
2026-01-11T03:01:04.189127+00:00 ubuntu-mate ifup[1822]: enp2s0: waiting for carrier
2026-01-11T03:01:04.189135+00:00 ubuntu-mate ifup[1822]: enp2s0: carrier acquired
2026-01-11T03:01:04.189139+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: carrier acquired
2026-01-11T03:01:04.189156+00:00 ubuntu-mate ifup[1822]: enp2s0: IAID 18:8a:b5:7a
2026-01-11T03:01:04.189159+00:00 ubuntu-mate ifup[1822]: enp2s0: adding address fe80::fb50:4273:64f2:555b
2026-01-11T03:01:04.189164+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: IAID 18:8a:b5:7a
2026-01-11T03:01:04.189168+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: adding address fe80::fb50:4273:64f2:555b
2026-01-11T03:01:04.189172+00:00 ubuntu-mate ifup[1822]: enp2s0: soliciting a DHCP lease
2026-01-11T03:01:04.189176+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: soliciting a DHCP lease
2026-01-11T03:01:04.189182+00:00 ubuntu-mate ifup[1822]: enp2s0: offered 192.168.0.10 from 192.168.0.1
2026-01-11T03:01:04.189186+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: offered 192.168.0.10 from 192.168.0.1
2026-01-11T03:01:04.189192+00:00 ubuntu-mate ifup[1822]: enp2s0: probing address 192.168.0.10/24
2026-01-11T03:01:04.189196+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: probing address 192.168.0.10/24
2026-01-11T03:01:04.189201+00:00 ubuntu-mate ifup[1822]: enp2s0: soliciting an IPv6 router
2026-01-11T03:01:04.189207+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: soliciting an IPv6 router
2026-01-11T03:01:04.189212+00:00 ubuntu-mate ifup[1822]: enp2s0: Router Advertisement from fe80::8694:8cff:fe30:fac2
2026-01-11T03:01:04.189218+00:00 ubuntu-mate ifup[1822]: enp2s0: adding address fd00:8494:8c30:fac2:158:51fa:b9c7:5891/64
2026-01-11T03:01:04.189222+00:00 ubuntu-mate ifup[1822]: enp2s0: adding route to fc00::/7 via fe80::8694:8cff:fe30:fac2
2026-01-11T03:01:04.189226+00:00 ubuntu-mate ifup[1822]: enp2s0: adding route to fd00:8494:8c30:fac2::/64
2026-01-11T03:01:04.189231+00:00 ubuntu-mate ifup[1822]: enp2s0: soliciting a DHCPv6 lease
2026-01-11T03:01:04.189235+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: Router Advertisement from fe80::8694:8cff:fe30:fac2
2026-01-11T03:01:04.189239+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: adding address fd00:8494:8c30:fac2:158:51fa:b9c7:5891/64
2026-01-11T03:01:04.189243+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: adding route to fc00::/7 via fe80::8694:8cff:fe30:fac2
2026-01-11T03:01:04.189247+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: adding route to fd00:8494:8c30:fac2::/64
2026-01-11T03:01:04.189251+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: soliciting a DHCPv6 lease
2026-01-11T03:01:04.189255+00:00 ubuntu-mate ifup[1849]: Dropped protocol specifier '.ra' from 'enp2s0.ra'. Using 'enp2s0' (ifindex=2).
2026-01-11T03:01:04.189265+00:00 ubuntu-mate ifup[1822]: enp2s0: leased 192.168.0.10 for 604800 seconds
2026-01-11T03:01:04.189269+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: leased 192.168.0.10 for 604800 seconds
2026-01-11T03:01:04.189275+00:00 ubuntu-mate ifup[1863]: Dropped protocol specifier '.dhcp' from 'enp2s0.dhcp'. Using 'enp2s0' (ifindex=2).
2026-01-11T03:01:04.189284+00:00 ubuntu-mate ifup[1822]: enp2s0: adding route to 192.168.0.0/24
2026-01-11T03:01:04.189288+00:00 ubuntu-mate ifup[1822]: enp2s0: adding default route via 192.168.0.1
2026-01-11T03:01:04.189292+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: adding route to 192.168.0.0/24
2026-01-11T03:01:04.189296+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: adding default route via 192.168.0.1
2026-01-11T03:01:04.189303+00:00 ubuntu-mate ifup[1767]: ifup: failed to bring up enp2s0
2026-01-11T03:01:04.189322+00:00 ubuntu-mate dhcpcd[1822]: enp2s0: removing interface
2026-01-11T03:01:04.191858+00:00 ubuntu-mate kernel: ATL1E 0000:02:00.0 enp2s0: renamed from eth0
2026-01-11T03:01:04.192399+00:00 ubuntu-mate kernel: ATL1E 0000:02:00.0 enp2s0: NIC Link is Up <1000 Mbps Full Duplex>
2026-01-11T03:01:05.310689+00:00 ubuntu-mate avahi-daemon[1960]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fd00:8494:8c30:fac2:158:51fa:b9c7:5891.
2026-01-11T03:01:05.310852+00:00 ubuntu-mate avahi-daemon[1960]: New relevant interface enp2s0.IPv6 for mDNS.
2026-01-11T03:01:05.310944+00:00 ubuntu-mate avahi-daemon[1960]: Joining mDNS multicast group on interface enp2s0.IPv4 with address 192.168.0.10.
2026-01-11T03:01:05.311023+00:00 ubuntu-mate avahi-daemon[1960]: New relevant interface enp2s0.IPv4 for mDNS.
2026-01-11T03:01:05.311485+00:00 ubuntu-mate avahi-daemon[1960]: Registering new address record for fd00:8494:8c30:fac2:158:51fa:b9c7:5891 on enp2s0.*.
2026-01-11T03:01:05.311566+00:00 ubuntu-mate avahi-daemon[1960]: Registering new address record for 192.168.0.10 on enp2s0.IPv4.
2026-01-11T03:01:06.877533+00:00 ubuntu-mate NetworkManager[2173]: <info>  [1768100466.8774] ifupdown: guessed connection type (enp2s0) = 802-3-ethernet
2026-01-11T03:01:06.877928+00:00 ubuntu-mate NetworkManager[2173]: <info>  [1768100466.8778] ifupdown: guessed connection type (enp2s0) = 802-3-ethernet
2026-01-11T03:01:07.414165+00:00 ubuntu-mate networkd-dispatcher[1973]: ERROR:Unknown state for interface NetworkctlListState(idx=2, name='enp2s0', type='ether', operational='-', administrative='unmanaged'): -
2026-01-11T03:01:09.782988+00:00 ubuntu-mate NetworkManager[2173]: <info>  [1768100469.7829] device (enp2s0): carrier: link connected
2026-01-11T03:01:09.784709+00:00 ubuntu-mate NetworkManager[2173]: <info>  [1768100469.7835] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)

root@ubuntu-mate:/var/log#

COMMAND: grep enp2s0 cloud-init.log

2026-01-11 03:00:18,970 - util.py[DEBUG]: Reading from /sys/class/net/enp2s0/address (quiet=False)
2026-01-11 03:00:18,970 - util.py[DEBUG]: Reading 18 bytes from /sys/class/net/enp2s0/address
   * * *
2026-01-11 03:00:18,972 - util.py[DEBUG]: Reading from /sys/class/net/enp2s0/carrier (quiet=False)
2026-01-11 03:00:18,972 - net[DEBUG]: Interface has no carrier: enp2s0
2026-01-11 03:00:18,972 - util.py[DEBUG]: Reading from /sys/class/net/enp2s0/dormant (quiet=False)
2026-01-11 03:00:18,972 - util.py[DEBUG]: Reading from /sys/class/net/enp2s0/address (quiet=False)
   * * *
2026-01-11 03:00:18,987 - stages.py[DEBUG]: applying net config names for {'ethernets': {'enp2s0': {'dhcp4': True, 'dhcp6': True, 'set-name': 'enp2s0', 'match': {'macaddress': '00:26:18:8a:b5:7a'}}}, 'version': 2}
   * * *
2026-01-11 03:00:19,062 - net[DEBUG]: Detected interfaces {'enp2s0': {'downable': True, 'device_id': '0x1026', 'driver': 'ATL1E', 'mac': '00:26:18:8a:b5:7a', 'name': 'enp2s0', 'up': False}, 'lo': {'downable': False, 'device_id': None, 'driver': None, 'mac': '00:00:00:00:00:00', 'name': 'lo', 'up': True}}
2026-01-11 03:00:19,062 - net[DEBUG]: no work necessary for renaming of [['00:26:18:8a:b5:7a', 'enp2s0', 'ATL1E', '0x1026']]
2026-01-11 03:00:19,063 - stages.py[INFO]: Applying network configuration from fallback bringup=False: {'ethernets': {'enp2s0': {'dhcp4': True, 'dhcp6': True, 'set-name': 'enp2s0', 'match': {'macaddress': '00:26:18:8a:b5:7a'}}}, 'version': 2}
2026-01-11 03:00:19,068 - util.py[DEBUG]: Reading from /sys/class/net/enp2s0/uevent (quiet=False)
2026-01-11 03:00:19,069 - util.py[DEBUG]: Reading 27 bytes from /sys/class/net/enp2s0/uevent
   * * *
{'config_id': 'enp2s0', 'type': 'physical', 'mac_address': '00:26:18:8a:b5:7a', 'name': 'enp2s0', 'match': {'macaddress': '00:26:18:8a:b5:7a'}, 'subnets': [{'type': 'dhcp4'}, {'type': 'dhcp6'}]}
{'enp2s0': {'dhcp4': True, 'dhcp6': True, 'set-name': 'enp2s0', 'match': {'macaddress': '00:26:18:8a:b5:7a'}}}
   * * *
2026-01-11 03:01:10,027 - stages.py[DEBUG]: applying net config names for {'ethernets': {'enp2s0': {'dhcp4': True, 'dhcp6': True, 'set-name': 'enp2s0', 'match': {'macaddress': '00:26:18:8a:b5:7a'}}}, 'version': 2}
   * * *
2026-01-11 03:01:10,036 - net[DEBUG]: Detected interfaces {'enp2s0': {'downable': False, 'device_id': '0x1026', 'driver': 'ATL1E', 'mac': '00:26:18:8a:b5:7a', 'name': 'enp2s0', 'up': True}, 'lo': {'downable': False, 'device_id': None, 'driver': None, 'mac': '00:00:00:00:00:00', 'name': 'lo', 'up': True}}
2026-01-11 03:01:10,036 - net[DEBUG]: no work necessary for renaming of [['00:26:18:8a:b5:7a', 'enp2s0', 'ATL1E', '0x1026']]

Some snapshots as well:

The Panel App icon for Network Status shows no network (contrary to what ping results seem to imply )

Attempting to reach “Google” via Firefox browser is a complete FAIL:

Opening the Network Connections function from the Panel clearly shows that there are NO ESTABLISHED CONNECTIONS:

guiverc · January 11, 2026, 5:01am

Your details looked pretty average to me until I saw this line

but it was preceded & followed by normal lines so, and prior output looked fine to me, so my mind ‘crossed’ off linux or the kernel as being a problem (but I can always be wrong!). This could be a unique feature of your networking hardware; it differs to what I expect to see on my hardware anyway.

You then added a lot more detail than I covered, and it does show issues that would grab my attention too. The fact that those are at terminal, would imply it’s not an installer problem to me either, which does explain why you asked networking or live ISO? …

When I’m unsure what package is involved, I usually look at what packages exist on the ISO for clues, eg. https://cdimage.ubuntu.com/ubuntu-mate/daily-live/current/resolute-desktop-amd64.manifest (or you can use whatever manifest matches the ISO you used; snapshot etc)… Here though I’m unsure.

Maybe another user of this site can give an opinion as to correct package, but I may pick/file against installer and record what you found… If a bug triager or developer responds, they may change the package its filed against anyway; even request you to file a new bug report against a new package (so the detail grabbed by apport tools is more useful to them), if so please don’t be annoyed by a re-file request, as it does increase chance of issue being found & fixed quickly (the developer alternative is for them to it themselves to get detail, but this won’t be useful if its specific hardware you’re using as they may get different results).

If I was in your position, and had the time, I’d likely also download/zsync the Ubuntu Desktop ISO (daily or latest snapshot) and try that… Personally I’d expect the same there, but IF it’s NOT the same then that will be really useful detail, and does confirm it’s a Ubuntu-MATE specific configuration (in my opinion) which will be helpful to solve issues. If it is the same with Ubuntu Desktop, it’ll gain more/faster developer attention possibly anyway. Report those results on the launchpad bug report too, OR you could always file another bug report & link the two report together on launchpad (mark one as duplicate of other, or at least provide links so they can be found easily and marked duplicate by a triager)

That’s my 2c anyway.

ericmarceau · January 11, 2026, 9:56pm

Thank you again, Chris!

I had downloaded an earlier Ubuntu Desktop (daily build for Dec 11 2025) and was planning to try that next.

I am really puzzled and frustrated by the fact that the Live ISO has no network, but the installed version does have network capability!

One possible hint as to the problem, but it is definitely not a direct association, in my mind …

From the Live ISO, I tried to perform grub-install to force grub onto the new installation target disk (rather than update existing grub on the non-target internal disk).

grub-install failed, reporting that it did not find a script, with the filename including the string `i386-pc, but I didn’t keep that message at the time.

Is it possible that it was referring to a missing

/boot/grub/i386-pc/modinfo.sh ?

… and could that lead to some necessary Kernel module not being loaded?

guiverc · January 12, 2026, 12:35am

Sorry, I’m no expert in grub-install, and would have to boot it up to work out what is doing, and work out a response from there.. I don’t have time/capacity to do that [currently or in the short term either].

ericmarceau · January 12, 2026, 9:27pm

I successfully installed the Ubuntu Desktop daily build for Dec 11 2025. I’ve also compiled the reports from the various commands entered to probe the system (to compare to those for UM 26.04 posted above) and offer those here

UbuntuDesktop__ProbeReports.txt

As a result, I have confirmed that …

… lack of success in establishing network function, that is recognized and usable by both

UbuntuMATE 26.04 daily build of Nov 19 2025, and
UbuntuMATE 26.04 daily build of Jan 9 2026

is both

an UbuntuMATE-specific issue, and
both a “Live ISO” and an “installer” issue

since there does not appear to be any way to re-establish networking for user-browsing during the live session, regardless of the fact that the above-reported probing seems to suggest that networking is alive and well !!!

[EDIT: Also, please refer to posting at the UbuntuMATE GitHub Issue Tracker.]

guiverc · January 15, 2026, 12:59am

Have you filed a bug report on this?? (on launchpad)

Whilst they don’t always appear (even if you correctly record your QA test install), much of the time they do, and they’re not appearing on the ISO QA tracker.

I just started an install on a dc7700 box of mine (old BIOS/legacy hardware) and networking isn’t as I’d expect it. The other box I listed on the QA tracker is more modern & uses uEFI boot.

With the installer running (and telling me I don’t have internet, but reackon I do!), a quick jump to terminal and I’m getting replies from ping 8.8.8.8 but when I tried to ping requiring DNS (eg. my ISPs connection) I’m getting name resolution errors…

I do note you included a link on the Ubuntu MATE GitHub tracker, but I’m after a Ubuntu bug tracker (ie. launchpad) so it will appear in QA reports (whilst I didn’t expect the ISO QA tracker to be used this cycle; its replacement isn’t ready as hoped, so for now it’s being used I gather; though not much by me). I do suggest you use it, or provide a link to the launchpad bug report (for me if nothing else)

(I’ve not explored the problem, am lacking time for that, but found my thumb-drive earlier today so wrote ISO & tried it & I appear to have confirmed your problem)