[Desktop-packages] [Bug 2033259] Re: netplan.script crashed with AttributeError in __getitem__(): /usr/bin/python3: undefined symbol: netplan_get_id_from_nm_filename

[Danilo Egea Gondolfo]

We started to see a different error since netplan.io 0.107 landed in
jammy-proposed:

ModuleNotFoundError: No module named 'netplan._netplan_cffi'

https://errors.ubuntu.com/problem/fae8a1deccaf9b2c8aac5d038dfbe8ab9ea9d506

The root cause is probably the same.
Phasing is paused for netplan.io 0.107.1-3ubuntu0.22.04.1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2033259

Title:
  netplan.script crashed with AttributeError in __getitem__():
  /usr/bin/python3: undefined symbol: netplan_get_id_from_nm_filename

Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in netplan.io source package in Noble:
  Confirmed
Status in network-manager source package in Noble:
  New
Status in netplan.io source package in Oracular:
  Confirmed
Status in network-manager source package in Oracular:
  Fix Released

Bug description:
  ubuntu desktop (mantic) live test on dell optiplex 780
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  exploring the /var/crash/ directory I noticed this report; nothing had
  appeared on screen, so just filed it with `ubuntu-bug`.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: netplan.io 0.106.1-8
  Uname: Linux 6.3.0-7-generic x86_64
  Architecture: amd64
  Date: Mon Aug 28 08:12:32 2023
  ExecutablePath: /usr/share/netplan/netplan.script
  ExecutableTimestamp: 1684343476
  InterpreterPath: /usr/bin/python3.11
  ProcCmdline: /usr/bin/python3 /usr/sbin/netplan generate
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  PythonArgs: ['/usr/sbin/netplan', 'generate']
  SourcePackage: netplan.io
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033259/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2080489] Re: Network Manager stops functioning on Ubuntu 24.04

[Danilo Egea Gondolfo]

That sounds bad.

Does any other command work?

Do you see any zombie () process in "ps aux"?

Does it hang forever? If you wait, let's say, 2 minutes, does it
unblock?

I'm asking this because there is one known issue with netplan that can
cause some commands to hang when the problem happens (and Network
Manager calls netplan).

Have you made any changes to your /etc/nsswitch.conf file? I'm asking
because setting "systemd" as the first option for "password" and/or
"group" is one of the things that triggers the problem.

If all the above is OK, I'd suggest trying to boot with a previous
kernel version. Maybe a recent kernel update is causing the problem.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2080489

Title:
  Network Manager stops functioning on Ubuntu 24.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 24.04 about a month ago on a Asus Vivobook. Soon
  after the NetworkManager started misbehaving, with all connections to
  the internet becoming idle now and then. When this event happens the
  only way to restore internet access is to reboot the system. If
  initially these events were occasional, they now take place 3 or 4
  times per day, often after signing in from the lock screen.

  So far I was not able to verify whether NetworkManager is actually
  crashing, the Settings programme reports "NetworkManager not running"
  (see attached image). However, in the command line `systemctl` reports
  an active service:

  ```
  $ systemctl status NetworkManager
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled>
   Active: active (running) since Sun 2024-08-27 18:21:44 WEST; 2h 18min a>
     Docs: man:NetworkManager(8)
     Main PID: 1149 (NetworkManager)
    Tasks: 4 (limit: 18646)
   Memory: 12.2M (peak: 28.6M)
  CPU: 836ms
   CGroup: /system.slice/NetworkManager.service
   └─1149 /usr/sbin/NetworkManager --no-daemon

  ago 27 19:34:08 Symbolic NetworkManager[1149]:   [1724006048.8961] man>
  ago 27 19:34:08 Symbolic NetworkManager[1149]:   [1724006048.8965] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1482] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1484] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1488] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1488] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1489] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.2049] dev>
  ago 27 20:33:50 Symbolic NetworkManager[1149]:   [1724009630.5340] man>
  ago 27 20:33:50 Symbolic NetworkManager[1149]:   [1724009630.5344] dev>
  ```

  But if I try to restart the service, the command line just hangs up:

  ```
  $ ping 1.1.1.1
  ping: connect: Network is unreachable

  $ sudo systemctl restart NetworkManager

  ```

  Also from `ifconfig` there is no response:

  ```
  $ ifconfig -a

  ```

  Please let me know if there is further useful information I can
  report.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2080489/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2080489] Re: Network Manager stops functioning on Ubuntu 24.04

[Danilo Egea Gondolfo]

Thanks for the logs.

It might not be a problem with Network Manager. It's indeed not crashing
nor emitting errors.

I missed the part from your bug description where you said that
"ifconfig" hangs when the problem happens. That points to some issue in
the kernel or driver.

You can also try the command "ip link show" (ifconfig is kind of
deprecated). When the problem starts, does it also hang? If not, does it
show the wireless interface?

Also, when the problem starts, do you see error messages from the driver
(mt7921e I believe) or any network related errors (stack traces for
example) in the logs from "dmesg"?

You can check that with "sudo dmesg".

Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2080489

Title:
  Network Manager stops functioning on Ubuntu 24.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 24.04 about a month ago on a Asus Vivobook. Soon
  after the NetworkManager started misbehaving, with all connections to
  the internet becoming idle now and then. When this event happens the
  only way to restore internet access is to reboot the system. If
  initially these events were occasional, they now take place 3 or 4
  times per day, often after signing in from the lock screen.

  So far I was not able to verify whether NetworkManager is actually
  crashing, the Settings programme reports "NetworkManager not running"
  (see attached image). However, in the command line `systemctl` reports
  an active service:

  ```
  $ systemctl status NetworkManager
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled>
   Active: active (running) since Sun 2024-08-27 18:21:44 WEST; 2h 18min a>
     Docs: man:NetworkManager(8)
     Main PID: 1149 (NetworkManager)
    Tasks: 4 (limit: 18646)
   Memory: 12.2M (peak: 28.6M)
  CPU: 836ms
   CGroup: /system.slice/NetworkManager.service
   └─1149 /usr/sbin/NetworkManager --no-daemon

  ago 27 19:34:08 Symbolic NetworkManager[1149]:   [1724006048.8961] man>
  ago 27 19:34:08 Symbolic NetworkManager[1149]:   [1724006048.8965] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1482] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1484] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1488] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1488] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1489] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.2049] dev>
  ago 27 20:33:50 Symbolic NetworkManager[1149]:   [1724009630.5340] man>
  ago 27 20:33:50 Symbolic NetworkManager[1149]:   [1724009630.5344] dev>
  ```

  But if I try to restart the service, the command line just hangs up:

  ```
  $ ping 1.1.1.1
  ping: connect: Network is unreachable

  $ sudo systemctl restart NetworkManager

  ```

  Also from `ifconfig` there is no response:

  ```
  $ ifconfig -a

  ```

  Please let me know if there is further useful information I can
  report.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2080489/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2080489] Re: Network Manager stops functioning on Ubuntu 24.04

[Danilo Egea Gondolfo]

Also, it would be helpful if you could attach the full journal for
NetworkManager:

journalctl -u NetworkManager > networkmanager.log

Or at least the parts where you see a crash or errors.

Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2080489

Title:
  Network Manager stops functioning on Ubuntu 24.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 24.04 about a month ago on a Asus Vivobook. Soon
  after the NetworkManager started misbehaving, with all connections to
  the internet becoming idle now and then. When this event happens the
  only way to restore internet access is to reboot the system. If
  initially these events were occasional, they now take place 3 or 4
  times per day, often after signing in from the lock screen.

  So far I was not able to verify whether NetworkManager is actually
  crashing, the Settings programme reports "NetworkManager not running"
  (see attached image). However, in the command line `systemctl` reports
  an active service:

  ```
  $ systemctl status NetworkManager
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled>
   Active: active (running) since Sun 2024-08-27 18:21:44 WEST; 2h 18min a>
     Docs: man:NetworkManager(8)
     Main PID: 1149 (NetworkManager)
    Tasks: 4 (limit: 18646)
   Memory: 12.2M (peak: 28.6M)
  CPU: 836ms
   CGroup: /system.slice/NetworkManager.service
   └─1149 /usr/sbin/NetworkManager --no-daemon

  ago 27 19:34:08 Symbolic NetworkManager[1149]:   [1724006048.8961] man>
  ago 27 19:34:08 Symbolic NetworkManager[1149]:   [1724006048.8965] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1482] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1484] dev>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1488] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1488] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.1489] dhc>
  ago 27 19:34:09 Symbolic NetworkManager[1149]:   [1724006049.2049] dev>
  ago 27 20:33:50 Symbolic NetworkManager[1149]:   [1724009630.5340] man>
  ago 27 20:33:50 Symbolic NetworkManager[1149]:   [1724009630.5344] dev>
  ```

  But if I try to restart the service, the command line just hangs up:

  ```
  $ ping 1.1.1.1
  ping: connect: Network is unreachable

  $ sudo systemctl restart NetworkManager

  ```

  Also from `ifconfig` there is no response:

  ```
  $ ifconfig -a

  ```

  Please let me know if there is further useful information I can
  report.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2080489/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2077515] Re: Network Manager applet shows back-slash escapes for non-latin characters

[Danilo Egea Gondolfo]

Thank you for confirming the new package fixed the problem for you (and
sorry for the inconvenience ;))

It should land in -updates in the next few days.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/2077515

Title:
  Network Manager applet shows back-slash escapes for non-latin
  characters

Status in netplan.io package in Ubuntu:
  Fix Committed
Status in network-manager-applet package in Ubuntu:
  Invalid

Bug description:
  Network Manager applet shows Non-Latin characters escaped with back-slash and 
octets.
  This occurs in the applet drop-down for connecting to a network.
  This occurs in the applet drop-down for connecting to a VPN.
  This occurs in the edit-connections pop-up window.
  This occurs in the edit-network window when opening a previously created 
network connection with Non-Latin characters in the name.

  This started occurring in Xubuntu 24.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2077515/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2077515] Re: Network Manager applet shows back-slash escapes for non-latin characters

[Danilo Egea Gondolfo]

I forgot to mention that you'll need to restart Network Manager after
updating netplan.io.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/2077515

Title:
  Network Manager applet shows back-slash escapes for non-latin
  characters

Status in netplan.io package in Ubuntu:
  Fix Committed
Status in network-manager-applet package in Ubuntu:
  Invalid

Bug description:
  Network Manager applet shows Non-Latin characters escaped with back-slash and 
octets.
  This occurs in the applet drop-down for connecting to a network.
  This occurs in the applet drop-down for connecting to a VPN.
  This occurs in the edit-connections pop-up window.
  This occurs in the edit-network window when opening a previously created 
network connection with Non-Latin characters in the name.

  This started occurring in Xubuntu 24.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2077515/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2077515] Re: Network Manager applet shows back-slash escapes for non-latin characters

[Danilo Egea Gondolfo]

Hello,

This is related to a regression in netplan.io caused by a security fix.

The fix for this regression is in the -proposed pocket for 24.04 [1].

Can you install the update from -proposed [2] and let us know if it
fixes the problem for you? You might need to delete the connections with
bad names and create them again.


[1] - https://launchpad.net/ubuntu/+source/netplan.io/1.0.1-1ubuntu2~24.04.1
[2] - https://wiki.ubuntu.com/Testing/EnableProposed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/2077515

Title:
  Network Manager applet shows back-slash escapes for non-latin
  characters

Status in netplan.io package in Ubuntu:
  New
Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  Network Manager applet shows Non-Latin characters escaped with back-slash and 
octets.
  This occurs in the applet drop-down for connecting to a network.
  This occurs in the applet drop-down for connecting to a VPN.
  This occurs in the edit-connections pop-up window.
  This occurs in the edit-network window when opening a previously created 
network connection with Non-Latin characters in the name.

  This started occurring in Xubuntu 24.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2077515/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

[Danilo Egea Gondolfo]

I can confirm this is an issue, although it's not caused by Network
Manager so I'll go ahead and set it as invalid.

After trying to do a "do-release-upgrade -d" from a brand new
installation of Jammy 22.04.4, gnome-shell crashed and interrupted the
upgrade.

After that, this is what "dpkg --list | grep systemd" looks like:

ii  dbus-user-session 1.14.10-4ubuntu4  
   amd64simple interprocess messaging system (systemd --user 
integration)
ii  gnome-logs42.0-1
   amd64viewer for the systemd journal
ii  libnss-systemd:amd64  249.11-0ubuntu3.12
   amd64nss module providing dynamic user and group name 
resolution
ii  libpam-systemd:amd64  249.11-0ubuntu3.12
   amd64system and service manager - PAM module
ii  libsystemd-shared:amd64   255.4-1ubuntu8
   amd64systemd shared private library
ii  libsystemd0:amd64 255.4-1ubuntu8
   amd64systemd utility library
ii  networkd-dispatcher   2.1-2ubuntu0.22.04.2  
   all  Dispatcher service for systemd-networkd connection 
status changes
ii  python3-systemd   235-1build4   
   amd64Python 3 bindings for systemd
ii  systemd   255.4-1ubuntu8
   amd64system and service manager
ii  systemd-dev   255.4-1ubuntu8
   all  systemd development files
ii  systemd-hwe-hwdb  249.11.5  
   all  udev rules for hardware enablement (HWE)
ii  systemd-oomd  249.11-0ubuntu3.12
   amd64Userspace out-of-memory (OOM) killer
ii  systemd-sysv  249.11-0ubuntu3.12
   amd64system and service manager - SysV links
ii  systemd-timesyncd 255.4-1ubuntu8
   amd64minimalistic service to synchronize local time with NTP 
servers


and /etc/resolv.conf is a broken link as systemd-resolved is not installed and 
/run/systemd/resolve doesn't exist:

/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf



** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2055012

Title:
  When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

Status in network-manager package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
  the end of the upgrade, I got an „Oh, no! Something has gone wrong and
  the system cannot recover. Call the system administrator” message
  after a red FAILED in the terminal. The system administrator is
  myself, because my computer is a personal one. Hard reset, same error,
  Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish
  the update with dpkg. While dpkg was upgrading, it printed an error
  message for every WiFi connection:

  „[Failed] Failed to migrate [I do not remember, something with
  /etc/netplan]”

  It took at least one and a half hour to find the solution on Ask
  Ubuntu. The problem was: /etc/resolv.conf became a broken link, along
  with systemd-resolve.service. I needed to remove both of them and
  write a new resolv.conf to fix the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 08:21:02 2024
  InstallationDate: Installed on 2023-07-05 (236 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2

[Desktop-packages] [Bug 2060241] Re: prosposed migration audit 1:3.1.2-2.1build1 vs network-manager 1.46.0-1ubuntu1

[Danilo Egea Gondolfo]

Probably fixed in the last network-manager upload:

debian/tests/control: add Depends: python3-gi for nm_netplan.py (LP:
#2060221)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2060241

Title:
  prosposed migration audit 1:3.1.2-2.1build1 vs network-manager
  1.46.0-1ubuntu1

Status in audit package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  The autopkgest for network-manager fail due to the missing module dependency:
  
  3988s autopkgtest [18:31:02]: test nm_netplan.py: [---
  3988s Traceback (most recent call last):
  3988s   File 
"/tmp/autopkgtest.Q1jKoU/build.9D4/src/debian/tests/nm_netplan.py", line 18, in 

  3988s import gi
  3988s ModuleNotFoundError: No module named 'gi'
  3988s autopkgtest [18:31:02]: test nm_netplan.py: ---]
  3989s autopkgtest [18:31:03]: test nm_netplan.py:  - - - - - - - - - - 
results - - - - - - - - - -
  3989s nm_netplan.pyFAIL non-zero exit status 1
  ---
  [1]

  
  [1] 
https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/amd64/n/network-manager/20240404_183130_7a1cc@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/2060241/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Danilo Egea Gondolfo]

Please refer to https://lists.ubuntu.com/archives/ubuntu-
devel/2024-March/042954.html for more information about the current
state of upgrades.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2059651

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2055148] Re: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan

[Danilo Egea Gondolfo]

So, I believe the best solution here would be to add options to DNS
addresses, similar to what we do with IP addresses. Something like this

nameservers:
  addresses:
- 1.2.3.4:
sni: domain
port: 1234
interface: eth123
- 1.1.1.1

with this we'd fully support both Network Manager and networkd backends.

Right now NM seems to support only the SNI parameter (1.2.3.4#domain)
but networkd supports more:

"111.222.333.444:9953%ifname#example.com" for IPv4 and
"[:::]:9953%ifname#example.com" for IPv6.

Alternatively, to keep things simpler, we could just accept the string
1.2.3.4#domain (and possibly the full notation used by networkd too).

What do you think, Lukas?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2055148

Title:
  NetworkManager connections with an explicit DoT (DNS over TLS) are not
  supported with Netplan

Status in netplan:
  New
Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From: https://discourse.ubuntu.com/t/blog-netplan-developer-
  diaries/35932/11

  Hi all,

  NetworkManager connections with an explicit DoT (DNS over TLS)
  configuration are not supported with Netplan, but NetworkManager does
  feed back the DoT DNS info with server address and Server Name
  Indication (SNI) in the form server_address#SNI, e.g.
  1.2.3.4#dns.myhome.com as nameserver addresses to Netplan. As a
  result, subsequent Netplan config applications fail because DNS
  servers don’t have the expected dotted decimal (IPv4) or colon’ed hex
  (IPv6) form.

  ```
  nmcli> describe ipv4.dns

  === [dns] ===
  [NM property description]
  Array of IP addresses of DNS servers. For DoT (DNS over TLS), the SNI server 
name can be specified by appending "#example.com" to the IP address of the DNS 
server. This currently only has effect when using systemd-resolved.
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2055148/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2055148] Re: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan

[Danilo Egea Gondolfo]

I can confirm the problem. Here is a reproducer:

# nmcli con add ifname dummy0 type dummy ipv4.dns 1.1.1.1#lxd
Error: Failed to add 'dummy-dummy0' connection: Message recipient disconnected 
from message bus without replying

This is the crash related to this issue:

Mar 15 09:46:40 noble-vm NetworkManager[7091]: 
/etc/netplan/90-NM-2116bb84-fa09-461a-a923-e04bc2648898.yaml:8:9: Error in 
network definition: malformed address '1.1.1.1#lxd', must be X.X.X.X or 
X:X:X:X:X:X:X:X
Mar 15 09:46:40 noble-vm NetworkManager[7091]: - 1.1.1.1#lxd
Mar 15 09:46:40 noble-vm NetworkManager[7091]: ^
Mar 15 09:46:40 noble-vm NetworkManager[7051]:  [1710496000.8273] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
Mar 15 09:46:40 noble-vm NetworkManager[7051]: **
Mar 15 09:46:40 noble-vm NetworkManager[7051]: 
nm:ERROR:src/core/settings/plugins/keyfile/nms-keyfile-writer.c:551:_internal_write_connection:
 assertion failed: (unreachable)
Mar 15 09:46:40 noble-vm NetworkManager[7051]: Bail out! 
nm:ERROR:src/core/settings/plugins/keyfile/nms-keyfile-writer.c:551:_internal_write_connection:
 assertion failed: (unreachable)
Mar 15 09:46:40 noble-vm systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
Mar 15 09:46:40 noble-vm systemd[1]: NetworkManager.service: Failed with result 
'core-dump'.
Mar 15 09:46:41 noble-vm systemd[1]: NetworkManager.service: Scheduled restart 
job, restart counter is at 1.
Mar 15 09:46:41 noble-vm systemd[1]: Starting NetworkManager.service - Network 
Manager...


I also noticed another crash already reported here 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490

Mar 15 09:45:30 noble-vm systemd[1]: Stopping NetworkManager.service - Network 
Manager...
Mar 15 09:45:30 noble-vm NetworkManager[6790]:   [1710495930.0746] caught 
SIGTERM, shutting down normally.
Mar 15 09:45:30 noble-vm NetworkManager[6790]: **
Mar 15 09:45:30 noble-vm NetworkManager[6790]: 
nm:ERROR:src/core/nm-policy.c:2937:dispose: assertion failed: 
(!c_list_is_empty(&priv->policy_auto_activate_lst_head))
Mar 15 09:45:30 noble-vm NetworkManager[6790]: Bail out! 
nm:ERROR:src/core/nm-policy.c:2937:dispose: assertion failed: 
(!c_list_is_empty(&priv->policy_auto_activate_lst_head))
Mar 15 09:45:30 noble-vm NetworkManager[6790]:   [1710495930.0751] 
exiting (success)
Mar 15 09:45:31 noble-vm systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
Mar 15 09:45:31 noble-vm systemd[1]: NetworkManager.service: Failed with result 
'core-dump'.
Mar 15 09:45:31 noble-vm systemd[1]: Starting NetworkManager.service - Network 
Manager...


** Tags added: foundations-todo

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2055148

Title:
  NetworkManager connections with an explicit DoT (DNS over TLS) are not
  supported with Netplan

Status in netplan:
  New
Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From: https://discourse.ubuntu.com/t/blog-netplan-developer-
  diaries/35932/11

  Hi all,

  NetworkManager connections with an explicit DoT (DNS over TLS)
  configuration are not supported with Netplan, but NetworkManager does
  feed back the DoT DNS info with server address and Server Name
  Indication (SNI) in the form server_address#SNI, e.g.
  1.2.3.4#dns.myhome.com as nameserver addresses to Netplan. As a
  result, subsequent Netplan config applications fail because DNS
  servers don’t have the expected dotted decimal (IPv4) or colon’ed hex
  (IPv6) form.

  ```
  nmcli> describe ipv4.dns

  === [dns] ===
  [NM property description]
  Array of IP addresses of DNS servers. For DoT (DNS over TLS), the SNI server 
name can be specified by appending "#example.com" to the IP address of the DNS 
server. This currently only has effect when using systemd-resolved.
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2055148/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2046436] Re: Ubuntu won't boot after enabling jumbo packets on network device

[Danilo Egea Gondolfo]

Hi,

If you press ESC when the splash screen shows up, do you see the
console? We need to know where it's getting stuck to better understand
the problem.

If you manage to see the console during boot, can you describe what you
see?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046436

Title:
  Ubuntu won't boot after enabling jumbo packets on network device

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop 23.10
  Asrock IMB-X1714 main board, with Intel I226V and I226LM ethernet controllers
  network-manager 1.44.2-1ubuntu1.2

  When enabling jumbo packets on a wired network device by setting MTU
  to 9000, Ubuntu will not boot anymore. The Ubuntu splash screen, with
  rotating wheel, appears, at a lower resolution than ordinary, but
  freezes after a few seconds.

  I can only revert this by disabling the ethernet devices in BIOS.
  After that Ubuntu will boot normally. I can then manually edit the
  .yaml configuration files in /etc/netplan to disable jumbo packets
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 14 11:04:19 2023
  IfupdownConfig:
   
  InstallationDate: Installed on 2023-12-13 (1 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  IpRoute:
   default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.208 metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.208 metric 
100
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled missing  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2046436/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses

[Danilo Egea Gondolfo]

Hi Martin, thanks so much for your bug report.

I can confirm it's a problem in libnetplan. I created a small fix for it
https://github.com/canonical/netplan/pull/428


** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => High

** Changed in: netplan.io (Ubuntu)
   Status: New => Confirmed

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158

Title:
  Updating wireguard-peer.allowed-ips gets wrong default netmask for
  IPv6 addresses

Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  In https://cockpit-project.org/ we have an integration test for
  NM+wireguard integration. That test starts with an IPv4-only
  connection:

  # cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
  network:
    version: 2
    tunnels:
  wg0:
    renderer: NetworkManager
    addresses:
    - "10.0.0.2/24"
    mode: "wireguard"
    port: 51820
    keys:
  private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
    peers:
    - keys:
    public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
  allowed-ips:
  - "10.0.0.1/32"
    networkmanager:
  uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
  name: "con-wg0"
  passthrough:
    ipv6.addr-gen-mode: "default"
    ipv6.method: "disabled"
    ipv6.ip6-privacy: "-1"
    proxy._: ""

  which gets rendered as

  # cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
  [connection]
  id=con-wg0
  type=wireguard
  uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
  interface-name=wg0

  [wireguard]
  private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
  listen-port=51820

  [wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
  allowed-ips=10.0.0.1/32;

  [ipv4]
  method=manual
  address1=10.0.0.2/24

  [ipv6]
  #Netplan: passthrough override
  method=disabled
  #Netplan: passthrough setting
  addr-gen-mode=default

  [proxy]

  Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
  "2001::1"]. Notably the addresses do *not* have a netmask, neither in
  the original config nor that update. Unfortunately that update cannot
  be done on the CLI:

  # nmcli con modify con-wg0 
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips" 
"2001::1"
  Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not 
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].

  So it has to happen via D-Bus:

  
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
  wg0","t":"s"},"interface-
  
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
  slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
  port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
  key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
  ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
  
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
  
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
  search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
  
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
  data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
  search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
  data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
  auto-dns":{"v":false,"t":"b"},"ignore-auto-
  routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]

  But this generates a wrong "/32" default netmask in the netplan config
  for the IPv6 address:

  allowed-ips:
  - "10.0.0.1/32"
  - "2001::1/32"

  On Fedora, with NM's default .nmconnection files, such a netmask is
  not added on this call. The netplan backend should do that (not
  second-guessing NM) or at least default to /128 for an IPv6 address.

  Doing this D-Bus call with `busctl` is a nuisance. If you need a
  reproducer at this level, I can spend an hour or so trying to stitch
  it together, but I hope your unit tests make this easier somehow.

  This was fine until 22.10, but with NM's new "netplan by default"
  backend this regressed.

  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so

[Desktop-packages] [Bug 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses

[Danilo Egea Gondolfo]

** Tags added: foundations-todo

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158

Title:
  Updating wireguard-peer.allowed-ips gets wrong default netmask for
  IPv6 addresses

Status in netplan.io package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  In https://cockpit-project.org/ we have an integration test for
  NM+wireguard integration. That test starts with an IPv4-only
  connection:

  # cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
  network:
    version: 2
    tunnels:
  wg0:
    renderer: NetworkManager
    addresses:
    - "10.0.0.2/24"
    mode: "wireguard"
    port: 51820
    keys:
  private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
    peers:
    - keys:
    public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
  allowed-ips:
  - "10.0.0.1/32"
    networkmanager:
  uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
  name: "con-wg0"
  passthrough:
    ipv6.addr-gen-mode: "default"
    ipv6.method: "disabled"
    ipv6.ip6-privacy: "-1"
    proxy._: ""

  which gets rendered as

  # cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
  [connection]
  id=con-wg0
  type=wireguard
  uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
  interface-name=wg0

  [wireguard]
  private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
  listen-port=51820

  [wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
  allowed-ips=10.0.0.1/32;

  [ipv4]
  method=manual
  address1=10.0.0.2/24

  [ipv6]
  #Netplan: passthrough override
  method=disabled
  #Netplan: passthrough setting
  addr-gen-mode=default

  [proxy]

  Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
  "2001::1"]. Notably the addresses do *not* have a netmask, neither in
  the original config nor that update. Unfortunately that update cannot
  be done on the CLI:

  # nmcli con modify con-wg0 
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips" 
"2001::1"
  Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not 
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].

  So it has to happen via D-Bus:

  
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
  wg0","t":"s"},"interface-
  
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
  slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
  port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
  key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
  ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
  
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
  
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
  search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
  
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
  data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
  search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
  data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
  auto-dns":{"v":false,"t":"b"},"ignore-auto-
  routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]

  But this generates a wrong "/32" default netmask in the netplan config
  for the IPv6 address:

  allowed-ips:
  - "10.0.0.1/32"
  - "2001::1/32"

  On Fedora, with NM's default .nmconnection files, such a netmask is
  not added on this call. The netplan backend should do that (not
  second-guessing NM) or at least default to /128 for an IPv6 address.

  Doing this D-Bus call with `busctl` is a nuisance. If you need a
  reproducer at this level, I can spend an hour or so trying to stitch
  it together, but I hope your unit tests make this easier somehow.

  This was fine until 22.10, but with NM's new "netplan by default"
  backend this regressed.

  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2046158/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses

[Danilo Egea Gondolfo]

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158

Title:
  Updating wireguard-peer.allowed-ips gets wrong default netmask for
  IPv6 addresses

Status in netplan.io package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  In https://cockpit-project.org/ we have an integration test for
  NM+wireguard integration. That test starts with an IPv4-only
  connection:

  # cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
  network:
    version: 2
    tunnels:
  wg0:
    renderer: NetworkManager
    addresses:
    - "10.0.0.2/24"
    mode: "wireguard"
    port: 51820
    keys:
  private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
    peers:
    - keys:
    public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
  allowed-ips:
  - "10.0.0.1/32"
    networkmanager:
  uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
  name: "con-wg0"
  passthrough:
    ipv6.addr-gen-mode: "default"
    ipv6.method: "disabled"
    ipv6.ip6-privacy: "-1"
    proxy._: ""

  which gets rendered as

  # cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
  [connection]
  id=con-wg0
  type=wireguard
  uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
  interface-name=wg0

  [wireguard]
  private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
  listen-port=51820

  [wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
  allowed-ips=10.0.0.1/32;

  [ipv4]
  method=manual
  address1=10.0.0.2/24

  [ipv6]
  #Netplan: passthrough override
  method=disabled
  #Netplan: passthrough setting
  addr-gen-mode=default

  [proxy]

  Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
  "2001::1"]. Notably the addresses do *not* have a netmask, neither in
  the original config nor that update. Unfortunately that update cannot
  be done on the CLI:

  # nmcli con modify con-wg0 
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips" 
"2001::1"
  Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not 
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].

  So it has to happen via D-Bus:

  
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
  wg0","t":"s"},"interface-
  
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
  slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
  port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
  key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
  ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
  
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
  
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
  search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
  
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
  data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
  search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
  data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
  auto-dns":{"v":false,"t":"b"},"ignore-auto-
  routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]

  But this generates a wrong "/32" default netmask in the netplan config
  for the IPv6 address:

  allowed-ips:
  - "10.0.0.1/32"
  - "2001::1/32"

  On Fedora, with NM's default .nmconnection files, such a netmask is
  not added on this call. The netplan backend should do that (not
  second-guessing NM) or at least default to /128 for an IPv6 address.

  Doing this D-Bus call with `busctl` is a nuisance. If you need a
  reproducer at this level, I can spend an hour or so trying to stitch
  it together, but I hope your unit tests make this easier somehow.

  This was fine until 22.10, but with NM's new "netplan by default"
  backend this regressed.

  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2046158/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2044270] Re: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10

[Danilo Egea Gondolfo]

Hello, thanks for your bug report.

Can you collect and attach the Network Manager's systemd journal?

You can get it with "journalctl -u NetworkManager > network-manager.log"

It will help us to identify the problem.

Thank you!

** Changed in: network-manager (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2044270

Title:
  Wi-Fi connection lost and reestablished every 3 minutes after upgrade
  from Lubuntu 22.10 to 23.10

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  In Lubuntu 22.10 (Kinetic) Wi-Fi connection on my laptop was stable. A
  couple of days ago I upgraded Lubuntu (installed it afresh) to 23.10
  (Mantic Minotaur). Now the connection is lost every couple of minutes
  and reestablished again in 3-20 seconds automatically. The same issue
  with two different internet providers (two different routers).

  Network manager version as told by command "apt-cache policy network-
  manager" is 1.44.2-1ubuntu1.2.

  My laptop model is Digma CITI E401.

  sudo lshw -class network
*-network 
 description: Wireless interface
 physical id: e
 bus info: mmc@2:0001:1
 logical name: wlan0
 serial: 80:5e:4f:02:97:70
 capabilities: ethernet physical wireless
 configuration: broadcast=yes driver=rtl8723bs 
driverversion=6.5.0-13-generic ip=192.168.0.13 multicast=yes wireless=IEEE 
802.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044270/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor

[Danilo Egea Gondolfo]

Hi,

I can't find anything wrong in your configuration. And that makes me
wonder if you have another YAML with the same wg0 interface in it. We
recently fixed a bug in Network Manager that was leading to duplication
in the configuration. You might have been affected by this bug when you
upgraded to Mantic.

If you grep /etc/netplan by the interface name, do you see more than one
file? Something like this "sudo grep wg0 /etc/netplan/*". If you find
the same interface in more than one file, try to remove them and create
the connection again using the GUI. The problem might be that you have
multiple YAMLs with the same interface. Netplan will merge them in a
single configuration and the result might be a broken config.

Let me know if it helps.

Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2044014

Title:
  networkmanager crashes on configuring wireguard connection via nm-
  connection-editor

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  when configuring a new wireguard connection both via nm-connection-editor and 
the settings app, NetworkManager crashes and restarts, with the error message 
"Message recipient disconnected from message bus without replying".
  Currently, I'm unable to add wireguard connections at all.
  Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule 
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821

  Ubuntu 23.10
  network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64
  netplan.io/now 0.107-5ubuntu1~ppa3

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 20 20:10:40 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-15 (2015 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via  dev enp0s31f6 proto dhcp src  metric 100
   /24 dev enp0s31f6 proto kernel scope link src  metric 
100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago)
  http_proxy: http://:3128
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
disabled  missing  disabled
  no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor

[Danilo Egea Gondolfo]

Hi Sebastian, thanks for your bug report.

I can see the following error in your syslog.log:

 [1700508393.5530] BUG: the profile cannot be stored in keyfile
format without becoming unusable: invalid connection: ipv4.dns: This
property is not allowed for "method=disabled"

What steps did you follow to setup the connection? I want to understand
how you managed to set the ipv4.dns property with ipv4.method set to
disabled using the GUI interface.


May I ask you to watch the Network Manager's journal while you reproduce the 
crash and add the relevant part of the logs here?

journalctl -u NetworkManager.service -f


Also, you will probably find a YAML in /etc/netplan that was created for the 
problematic connection. Can you find it, remove all the keys and IPs from it, 
and paste it here?

I'm running netplan.io 0.107-5ubuntu0.1 and I can create Wireguard
connections just fine. But maybe you are using some settings that's
triggering another bug that we are not aware of.

Thank you.

** Changed in: network-manager (Ubuntu)
   Status: New => Triaged

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2044014

Title:
  networkmanager crashes on configuring wireguard connection via nm-
  connection-editor

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  when configuring a new wireguard connection both via nm-connection-editor and 
the settings app, NetworkManager crashes and restarts, with the error message 
"Message recipient disconnected from message bus without replying".
  Currently, I'm unable to add wireguard connections at all.
  Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule 
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821

  Ubuntu 23.10
  network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64
  netplan.io/now 0.107-5ubuntu1~ppa3

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 20 20:10:40 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-15 (2015 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via  dev enp0s31f6 proto dhcp src  metric 100
   /24 dev enp0s31f6 proto kernel scope link src  metric 
100
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago)
  http_proxy: http://:3128
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
disabled  missing  disabled
  no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2023183] Re: network-manager autokpgtest failure (nm.py)

[Danilo Egea Gondolfo]

As far as I can see, the only tests failing now are related to
differences in MAC addresses on veth interfaces. I created an MP to
address these failures. See more details in the related MP.

** Also affects: network-manager (Ubuntu Noble)
   Importance: Undecided
   Status: Confirmed

** Also affects: network-manager (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu Mantic)
   Status: New => Confirmed

** Changed in: network-manager (Ubuntu Lunar)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu Mantic)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu Noble)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2023183

Title:
  network-manager autokpgtest failure (nm.py)

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Lunar:
  Confirmed
Status in network-manager source package in Mantic:
  Confirmed
Status in network-manager source package in Noble:
  Confirmed

Bug description:
  This fails only on arm64.

  https://autopkgtest.ubuntu.com/results/autopkgtest-
  lunar/lunar/arm64/n/network-manager/20230522_141200_71ac4@/log.gz

  To be determined if there is a bug in the package or linux kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2023183/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2023183] Re: network-manager autokpgtest failure (nm.py)

[Danilo Egea Gondolfo]

** Merge proposal linked:
   
https://code.launchpad.net/~danilogondolfo/network-manager/+git/network-manager/+merge/454594

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2023183

Title:
  network-manager autokpgtest failure (nm.py)

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Lunar:
  Confirmed
Status in network-manager source package in Mantic:
  Confirmed
Status in network-manager source package in Noble:
  Confirmed

Bug description:
  This fails only on arm64.

  https://autopkgtest.ubuntu.com/results/autopkgtest-
  lunar/lunar/arm64/n/network-manager/20230522_141200_71ac4@/log.gz

  To be determined if there is a bug in the package or linux kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2023183/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2040153] Re: Network Manager will not remove Netplan YAMLs when connections are deleted

[Danilo Egea Gondolfo]

The autopkgtest failures on arm64 are not related to these changes and
it's happening for a while now. So they are not regressions.

I'm running network-manager from proposed on my main machine and the
problem is resolved.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2040153

Title:
  Network Manager will not remove Netplan YAMLs when connections are
  deleted

Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  In Progress
Status in netplan.io source package in Mantic:
  Invalid
Status in network-manager source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  Desktop users, or any users with YAML files in /usr/lib/netplan, can't delete
  Network Manager connections persistently. That means that, when the 
connection is
  deliberately deleted by the user, it will re-appear when the system is 
rebooted or
  netplan apply is executed.

  This is happening because the systemd service unit is setting the property 
"ProtectSystem"
  to true. Because of that, /usr is being presented to the Network Manager 
daemon as read-only.
  When connections are deleted, libnetplan will try to open its YAML files with 
writing permissions
  and will fail for files from /usr/lib/netplan. Even if the user hasn't added 
any files there manually,
  the file /usr/lib/netplan/00-network-manager-all.yaml will be installed by 
the package ubuntu-settings.

  This issue is fixed by allow-listing /usr/lib/netplan with 
ReadWritePaths=/usr/lib/netplan in systemd
  so the Network Manager's daemon will be able to write to that directory.

  This upload also improves the autopkgtests related to Netplan. Network 
Manager will be
  started by systemd, which ensures we are testing in the same environment 
conditions
  used by a desktop installation. It also adds a few more instances of 
connections deletions so
  we can test a bit more that YAML files are being removed. It also adds all 
the dependencies
  required by the test script (which sadly was causing the nm_netplan.py tests 
to be skipped).

  [ Test Plan ]

  Launch a new Mantic VM:

  $ lxc launch ubuntu:mantic --vm

  Install network-manager and ubuntu-settings:

  # apt install network-manager ubuntu-settings

  Run Netplan

  # netplan apply

  Create a dummy connection via nmcli:

  # nmcli con add type dummy connection.interface-name dummy0

  Check a new YAML will be created in /etc/netplan

  Delete the connection with nmcli

  # nmcli con del dummy-dummy0

  Check the YAML WAS NOT removed from /etc/netplan

  You will see the error below in the NetworkManager's journal

  netplan_delete_connection: Cannot write output state: Read-only file
  system

  Add the PPA containing the fix and run the same test described above

  # add-apt-repository ppa:danilogondolfo/network-manager
  # apt update
  # apt upgrade

  Check that the YAML will be created when the connection is added and
  deleted and the connection is removed.

  [ Where problems could occur ]

  As the only change is a relaxation of the restrictions applied by systemd on 
the environment where Network Manager
  runs, we are not expecting any regression.

  As for the changes in the autopkgtest related to Netplan, they are
  passing on all architectures.

  Autopkgtests

  amd64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/amd64/n/network-manager/20231023_175203_b2798@/log.gz
  ppc64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/ppc64el/n/network-manager/20231023_182332_f0497@/log.gz
  s390x - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/s390x/n/network-manager/20231023_190810_ced8d@/log.gz
  arm64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/arm64/n/network-manager/20231024_084542_ac017@/log.gz
  armhf - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/armhf/n/network-manager/20231024_083545_ac017@/log.gz

  [ Other Info ]

  
  --- Original description ---

  When a connection is deleted using any NM facility, libnetplan is
  failing to delete the YAML file. Because of that, the connection will
  be recreated when "netplan generate" runs again.

  This is probably being caused by a combination of two things. First,
  the NM's systemd unit has this setting "ProtectSystem=true", which
  will mount /usr as read-only for NM. Second, we migrated the default
  "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1].
  When libnetplan tries to open this file for writing, the open system
  fails with EROFS:

  ---
  22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", 
O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system)
  22517 write(2, "ne

[Desktop-packages] [Bug 2040153] Re: Network Manager will not remove Netplan YAMLs when connections are deleted

[Danilo Egea Gondolfo]

** Description changed:

+ [ Impact ]
+ 
+ Desktop users, or any users with YAML files in /usr/lib/netplan, can't delete
+ Network Manager connections persistently. That means that, when the 
connection is
+ deliberately deleted by the user, it will re-appear when the system is 
rebooted or
+ netplan apply is executed.
+ 
+ This is happening because the systemd service unit is setting the property 
"ProtectSystem"
+ to true. Because of that, /usr is being presented to the Network Manager 
daemon as read-only.
+ When connections are deleted, libnetplan will try to open its YAML files with 
writing permissions
+ and will fail for files from /usr/lib/netplan. Even if the user hasn't added 
any files there manually,
+ the file /usr/lib/netplan/00-network-manager-all.yaml will be installed by 
the package ubuntu-settings.
+ 
+ This issue is fixed by allow-listing /usr/lib/netplan with 
ReadWritePaths=/usr/lib/netplan in systemd
+ so the Network Manager's daemon will be able to write to that directory.
+ 
+ This upload also improves the autopkgtests related to Netplan. Network 
Manager will be
+ started by systemd, which ensures we are testing in the same environment 
conditions
+ used by a desktop installation. It also adds a few more instances of 
connections deletions so
+ we can test a bit more that YAML files are being removed. It also adds all 
the dependencies
+ required by the test script (which sadly was causing the nm_netplan.py tests 
to be skipped).
+ 
+ [ Test Plan ]
+ 
+ Launch a new Mantic VM:
+ 
+ $ lxc launch ubuntu:mantic --vm
+ 
+ Install network-manager and ubuntu-settings:
+ 
+ # apt install network-manager ubuntu-settings
+ 
+ Run Netplan
+ 
+ # netplan apply
+ 
+ Create a dummy connection via nmcli:
+ 
+ # nmcli con add type dummy connection.interface-name dummy0
+ 
+ Check a new YAML will be created in /etc/netplan
+ 
+ Delete the connection with nmcli
+ 
+ # nmcli con del dummy-dummy0
+ 
+ Check the YAML WAS NOT removed from /etc/netplan
+ 
+ You will see the error below in the NetworkManager's journal
+ 
+ netplan_delete_connection: Cannot write output state: Read-only file
+ system
+ 
+ Add the PPA containing the fix and run the same test described above
+ 
+ # add-apt-repository ppa:danilogondolfo/network-manager
+ # apt update
+ # apt upgrade
+ 
+ Check that the YAML will be created when the connection is added and
+ deleted and the connection is removed.
+ 
+ [ Where problems could occur ]
+ 
+ As the only change is a relaxation of the restrictions applied by systemd on 
the environment where Network Manager
+ runs, we are not expecting any regression.
+ 
+ As for the changes in the autopkgtest related to Netplan, they are
+ passing on all architectures.
+ 
+ Autopkgtests
+ 
+ amd64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/amd64/n/network-manager/20231023_175203_b2798@/log.gz
+ ppc64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/ppc64el/n/network-manager/20231023_182332_f0497@/log.gz
+ s390x - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/s390x/n/network-manager/20231023_190810_ced8d@/log.gz
+ arm64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/arm64/n/network-manager/20231024_084542_ac017@/log.gz
+ armhf - 
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/armhf/n/network-manager/20231024_083545_ac017@/log.gz
+ 
+ [ Other Info ]
+ 
+ 
+ --- Original description ---
+ 
  When a connection is deleted using any NM facility, libnetplan is
  failing to delete the YAML file. Because of that, the connection will be
  recreated when "netplan generate" runs again.
  
  This is probably being caused by a combination of two things. First, the
  NM's systemd unit has this setting "ProtectSystem=true", which will
  mount /usr as read-only for NM. Second, we migrated the default
  "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1].
  When libnetplan tries to open this file for writing, the open system
  fails with EROFS:
  
  ---
  22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", 
O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system)
  22517 write(2, "netplan_delete_connection: Canno"..., 76) = 76
  ---
  
- 
  [1] - https://launchpad.net/ubuntu/+source/ubuntu-settings/23.10.1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2040153

Title:
  Network Manager will not remove Netplan YAMLs when connections are
  deleted

Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged
Status in netplan.io source package in Mantic:
  Invalid
Status in network-manager source package in Mantic:
  Triaged

Bug description:
  [ Impact ]

  De

[Desktop-packages] [Bug 2040153] [NEW] Network Manager will not remove Netplan YAMLs when connections are deleted

[Danilo Egea Gondolfo]

Public bug reported:

When a connection is deleted using any NM facility, libnetplan is
failing to delete the YAML file. Because of that, the connection will be
recreated when "netplan generate" runs again.

This is probably being caused by a combination of two things. First, the
NM's systemd unit has this setting "ProtectSystem=true", which will
mount /usr as read-only for NM. Second, we migrated the default
"00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1].
When libnetplan tries to open this file for writing, the open system
fails with EROFS:

---
22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", 
O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system)
22517 write(2, "netplan_delete_connection: Canno"..., 76) = 76
---


[1] - https://launchpad.net/ubuntu/+source/ubuntu-settings/23.10.1

** Affects: netplan.io (Ubuntu)
 Importance: Critical
 Status: Triaged

** Affects: network-manager (Ubuntu)
 Importance: Critical
 Status: Triaged

** Affects: netplan.io (Ubuntu Mantic)
 Importance: Critical
 Status: Triaged

** Affects: network-manager (Ubuntu Mantic)
 Importance: Critical
 Status: Triaged


** Tags: foundations-todo

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: network-manager (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: netplan.io (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Changed in: netplan.io (Ubuntu Mantic)
   Importance: Undecided => Critical

** Changed in: network-manager (Ubuntu Mantic)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2040153

Title:
  Network Manager will not remove Netplan YAMLs when connections are
  deleted

Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged
Status in netplan.io source package in Mantic:
  Triaged
Status in network-manager source package in Mantic:
  Triaged

Bug description:
  When a connection is deleted using any NM facility, libnetplan is
  failing to delete the YAML file. Because of that, the connection will
  be recreated when "netplan generate" runs again.

  This is probably being caused by a combination of two things. First,
  the NM's systemd unit has this setting "ProtectSystem=true", which
  will mount /usr as read-only for NM. Second, we migrated the default
  "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1].
  When libnetplan tries to open this file for writing, the open system
  fails with EROFS:

  ---
  22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", 
O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system)
  22517 write(2, "netplan_delete_connection: Canno"..., 76) = 76
  ---

  
  [1] - https://launchpad.net/ubuntu/+source/ubuntu-settings/23.10.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2040153/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2038811] Re: NetworkManager crashes when updating wpa-eap connections

[Danilo Egea Gondolfo]

I'm working on the SRU of a couple of fixes for Netplan. This ticket is
being user for the SRU
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039825

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2038811

Title:
  NetworkManager crashes when updating wpa-eap connections

Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
network-manager.  This problem was most recently seen with package version 
1.44.2-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/0185fff02c2976262de9f862e539829420f9c737 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2038811/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status

[Danilo Egea Gondolfo]

hm Ok, in this case, the problem was the suffix actually:

root@mantic:/etc/NetworkManager/system-connections# nmcli con load 
/etc/NetworkManager/system-connections/UPTOWN.guests
Could not load file '/etc/NetworkManager/system-connections/UPTOWN.guests'
root@mantic:/etc/NetworkManager/system-connections# mv 
/etc/NetworkManager/system-connections/UPTOWN.guests 
/etc/NetworkManager/system-connections/UPTOWN
root@mantic:/etc/NetworkManager/system-connections# nmcli con load 
/etc/NetworkManager/system-connections/UPTOWN
root@mantic:/etc/NetworkManager/system-connections# nmcli con show
NAMEUUID  TYPE  DEVICE
netplan-enp5s0  e1419a5e-5e1d-3fff-a17c-b2fc6d2cef99  ethernet  enp5s0
lo  e71fd408-7b42-49a1-af17-072edc915266  loopback  lo
UPTOWN.guests   491fa5c8-68ef-4140-8679-dca422f5c262  wifi  --
root@mantic:/etc/NetworkManager/system-connections#

It's considering the .guests a bad extension as far as I can see. Only
removing the .guests makes it loadable. So we shouldn't load only
.nmconnection files.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2039503

Title:
  package network-manager 1.44.2-1ubuntu1 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 10

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Mantic:
  New

Bug description:
  lunar to mantic upgrade, exciting to see output from network-manager
  postinst migrating connections to /etc/netplan one by one.  But then:

  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  That UUID appears in a file /etc/NetworkManager/system-
  connections/UPTOWN.guests that hasn't been touched since 2015.

  Contents of the file were:

  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  
  I've removed it from disk and the migration continued to completion.

  Then I got another failure on:

  [connection]
  id=belkin.1e4.guests
  uuid=2c77e512-f3e3-4238-b401-c94559cc6db0
  type=802-11-wireless

  [802-11-wireless]
  ssid=belkin.1e4.guests
  mode=infrastructure
  mac-address=00:24:D7:1F:EA:20

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  Is it unhappy because of the . in the names?

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct 16 16:12:43 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-12-23 (1393 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: network-manager
  Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: 
installed network-manager package post-installation script subprocess returned 
error exit status 10
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039503/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status

[Danilo Egea Gondolfo]

Is the only problem the filename extension? Renaming it to
UPTOWN.guests.nmconnection makes it loadable.

Should we still try to load these files by renaming them first? Or,
should we iterate over the *.nmconnection files only instead of *?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2039503

Title:
  package network-manager 1.44.2-1ubuntu1 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 10

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Mantic:
  New

Bug description:
  lunar to mantic upgrade, exciting to see output from network-manager
  postinst migrating connections to /etc/netplan one by one.  But then:

  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  That UUID appears in a file /etc/NetworkManager/system-
  connections/UPTOWN.guests that hasn't been touched since 2015.

  Contents of the file were:

  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  
  I've removed it from disk and the migration continued to completion.

  Then I got another failure on:

  [connection]
  id=belkin.1e4.guests
  uuid=2c77e512-f3e3-4238-b401-c94559cc6db0
  type=802-11-wireless

  [802-11-wireless]
  ssid=belkin.1e4.guests
  mode=infrastructure
  mac-address=00:24:D7:1F:EA:20

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  Is it unhappy because of the . in the names?

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct 16 16:12:43 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-12-23 (1393 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: network-manager
  Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: 
installed network-manager package post-installation script subprocess returned 
error exit status 10
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039503/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2039371] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Term

[Danilo Egea Gondolfo]

Hello, thank you for reporting that.

May I ask you to attach the full NetworkManager journal so we can
understand better what is happening?

You can collect it with the command below:

journalctl -u NetworkManager > network-manager.log

It would be very helpful. Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2039371

Title:
  package network-manager 1.44.2-1ubuntu1 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  was killed by signal (Terminated)

Status in network-manager package in Ubuntu:
  New

Bug description:
  With do-release-upgrade -d, Setting up network-manager hanged
  indefinitely with

  [...]
  Setting up network-manager (1.44.2-1ubuntu1) ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  ^[[CSKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  [...]

  Killing it resulted in

  Terminated
  SKIP: NetworkManager is not ready ...
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess was 
killed by signal (Terminated)

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sun Oct 15 00:40:40 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2023-01-13 (274 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  IpRoute:
   default via 192.168.0.254 dev wlp2s0 proto dhcp src 192.168.0.29 metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.29 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: network-manager
  Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: 
installed network-manager package post-installation script subprocess was 
killed by signal (Terminated)
  UpgradeStatus: Upgraded to mantic on 2023-10-14 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  starting  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039371/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2038811] Re: /usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:_internal_write_connection:nms_keyfile_writer_connection:nms_keyfile_plugin_update_connecti

[Danilo Egea Gondolfo]

They might (likely to?) be related to libnetplan. I'm looking into it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2038811

Title:
  
/usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:_internal_write_connection:nms_keyfile_writer_connection:nms_keyfile_plugin_update_connection

Status in netplan.io package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
network-manager.  This problem was most recently seen with package version 
1.44.2-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/0185fff02c2976262de9f862e539829420f9c737 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2038811/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2033391] Re: Some Netplan-related autopkgtests are failing on armhf

[Danilo Egea Gondolfo]

** Changed in: netplan.io (Ubuntu Mantic)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2033391

Title:
  Some Netplan-related autopkgtests are failing on armhf

Status in netplan.io package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in netplan.io source package in Mantic:
  Fix Released
Status in network-manager source package in Mantic:
  Fix Released

Bug description:
  The root cause appears to be NM not being ready yet when the test
  starts.

  # /usr/bin/python3 
/tmp/autopkgtest.kW7u4i/build.K7E/src/debian/tests/nm_netplan.py
  test_nmcli_add_device_and_change_it 
(__main__.TestNetplan.test_nmcli_add_device_and_change_it)
  Uses the nmcli to add a connection and validates if the ... Warning: nmcli 
(1.44.0) and NetworkManager (Unknown) versions don't match. Restarting 
NetworkManager is advised.
  Error: NetworkManager is not running.
  FAIL

  We need to wait until Network Manager is ready before starting the
  test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2033391] Re: Some Netplan-related autopkgtests are failing on armhf

[Danilo Egea Gondolfo]

The patch helped with nm.py and nm_netplan.py tests but the ones that
require building kernel modules are still failing due to the gcc
version.

1749s autopkgtest [00:14:05]:  summary
1749s wpa-dhclient PASS
1749s nm.pyPASS
1749s killswitches-no-urfkill FAIL non-zero exit status 2
1749s urfkill-integration  FAIL non-zero exit status 2
1749s nm_netplan.pyPASS

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2033391

Title:
  Some Netplan-related autopkgtests are failing on armhf

Status in netplan.io package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in netplan.io source package in Mantic:
  New
Status in network-manager source package in Mantic:
  New

Bug description:
  The root cause appears to be NM not being ready yet when the test
  starts.

  # /usr/bin/python3 
/tmp/autopkgtest.kW7u4i/build.K7E/src/debian/tests/nm_netplan.py
  test_nmcli_add_device_and_change_it 
(__main__.TestNetplan.test_nmcli_add_device_and_change_it)
  Uses the nmcli to add a connection and validates if the ... Warning: nmcli 
(1.44.0) and NetworkManager (Unknown) versions don't match. Restarting 
NetworkManager is advised.
  Error: NetworkManager is not running.
  FAIL

  We need to wait until Network Manager is ready before starting the
  test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2033391] Re: Some Netplan-related autopkgtests are failing on armhf

[Danilo Egea Gondolfo]

Both tests that require building a kernel module are failing due to the
new default gcc

794s autopkgtest [10:41:29]: test killswitches-no-urfkill: 
[---
794s make -C /lib/modules/6.3.0-7-generic/build 
KBUILD_SRC=/lib/modules/6.3.0-7-generic/build 
M=/tmp/autopkgtest.6Iru72/build.A2V/src/debian/tests
794s make[1]: Entering directory '/usr/src/linux-headers-6.3.0-7-generic'
794s warning: the compiler differs from the one used to build the kernel
794s   The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 
12.3.0-1ubuntu1) 12.3.0
794s   You are using:   
794s   CC [M]  /tmp/autopkgtest.6Iru72/build.A2V/src/debian/tests/fake-rfkill.o
794s /bin/sh: 1: gcc-12: not found
794s make[2]: *** [scripts/Makefile.build:260: 
/tmp/autopkgtest.6Iru72/build.A2V/src/debian/tests/fake-rfkill.o] Error 127
794s make[1]: *** [Makefile:2030: 
/tmp/autopkgtest.6Iru72/build.A2V/src/debian/tests] Error 2
794s make[1]: Leaving directory '/usr/src/linux-headers-6.3.0-7-generic'
794s make: *** [debian/tests/Makefile:5: fake-rfkill] Error 2

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2033391

Title:
  Some Netplan-related autopkgtests are failing on armhf

Status in netplan.io package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in netplan.io source package in Mantic:
  New
Status in network-manager source package in Mantic:
  New

Bug description:
  The root cause appears to be NM not being ready yet when the test
  starts.

  # /usr/bin/python3 
/tmp/autopkgtest.kW7u4i/build.K7E/src/debian/tests/nm_netplan.py
  test_nmcli_add_device_and_change_it 
(__main__.TestNetplan.test_nmcli_add_device_and_change_it)
  Uses the nmcli to add a connection and validates if the ... Warning: nmcli 
(1.44.0) and NetworkManager (Unknown) versions don't match. Restarting 
NetworkManager is advised.
  Error: NetworkManager is not running.
  FAIL

  We need to wait until Network Manager is ready before starting the
  test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2033391] Re: Some Netplan-related autopkgtests are failing on armhf

[Danilo Egea Gondolfo]

I'm running some tests with the linked MP.

** Merge proposal linked:
   
https://code.launchpad.net/~danilogondolfo/network-manager/+git/network-manager/+merge/450220

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2033391

Title:
  Some Netplan-related autopkgtests are failing on armhf

Status in netplan.io package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in netplan.io source package in Mantic:
  New
Status in network-manager source package in Mantic:
  New

Bug description:
  The root cause appears to be NM not being ready yet when the test
  starts.

  # /usr/bin/python3 
/tmp/autopkgtest.kW7u4i/build.K7E/src/debian/tests/nm_netplan.py
  test_nmcli_add_device_and_change_it 
(__main__.TestNetplan.test_nmcli_add_device_and_change_it)
  Uses the nmcli to add a connection and validates if the ... Warning: nmcli 
(1.44.0) and NetworkManager (Unknown) versions don't match. Restarting 
NetworkManager is advised.
  Error: NetworkManager is not running.
  FAIL

  We need to wait until Network Manager is ready before starting the
  test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2033391] Re: Some Netplan-related autopkgtests are failing on armhf

[Danilo Egea Gondolfo]

Well, actually, there are tests from nm.py failing for the same
reason...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2033391

Title:
  Some Netplan-related autopkgtests are failing on armhf

Status in netplan.io package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in netplan.io source package in Mantic:
  New
Status in network-manager source package in Mantic:
  New

Bug description:
  The root cause appears to be NM not being ready yet when the test
  starts.

  # /usr/bin/python3 
/tmp/autopkgtest.kW7u4i/build.K7E/src/debian/tests/nm_netplan.py
  test_nmcli_add_device_and_change_it 
(__main__.TestNetplan.test_nmcli_add_device_and_change_it)
  Uses the nmcli to add a connection and validates if the ... Warning: nmcli 
(1.44.0) and NetworkManager (Unknown) versions don't match. Restarting 
NetworkManager is advised.
  Error: NetworkManager is not running.
  FAIL

  We need to wait until Network Manager is ready before starting the
  test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2033391] [NEW] Some Netplan-related autopkgtests are failing on armhf

[Danilo Egea Gondolfo]

Public bug reported:

The root cause appears to be NM not being ready yet when the test
starts.

# /usr/bin/python3 
/tmp/autopkgtest.kW7u4i/build.K7E/src/debian/tests/nm_netplan.py
test_nmcli_add_device_and_change_it 
(__main__.TestNetplan.test_nmcli_add_device_and_change_it)
Uses the nmcli to add a connection and validates if the ... Warning: nmcli 
(1.44.0) and NetworkManager (Unknown) versions don't match. Restarting 
NetworkManager is advised.
Error: NetworkManager is not running.
FAIL

We need to wait until Network Manager is ready before starting the test.

** Affects: netplan.io (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: netplan.io (Ubuntu Mantic)
 Importance: Undecided
 Status: New

** Affects: network-manager (Ubuntu Mantic)
 Importance: Undecided
 Status: New

** Also affects: network-manager (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2033391

Title:
  Some Netplan-related autopkgtests are failing on armhf

Status in netplan.io package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in netplan.io source package in Mantic:
  New
Status in network-manager source package in Mantic:
  New

Bug description:
  The root cause appears to be NM not being ready yet when the test
  starts.

  # /usr/bin/python3 
/tmp/autopkgtest.kW7u4i/build.K7E/src/debian/tests/nm_netplan.py
  test_nmcli_add_device_and_change_it 
(__main__.TestNetplan.test_nmcli_add_device_and_change_it)
  Uses the nmcli to add a connection and validates if the ... Warning: nmcli 
(1.44.0) and NetworkManager (Unknown) versions don't match. Restarting 
NetworkManager is advised.
  Error: NetworkManager is not running.
  FAIL

  We need to wait until Network Manager is ready before starting the
  test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build

[Danilo Egea Gondolfo]

Might be related to https://gitlab.gnome.org/GNOME/glib/-/issues/2927

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2927
   https://gitlab.gnome.org/GNOME/glib/-/issues/2927

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2026826

Title:
  glib2.0 (2.77.0 ) breaks Netplan build

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
  mantic-proposed.

  See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3

  When I downgrade glib in my sbuild environment, everything works as
  expected:

  $ apt install libglib2.0-0=2.76.3-1ubuntu1
  libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1
  libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1

  The build also works fine in Debian unstable, which is using glib2.0
  2.74.6-2.

  Netplan is using plenty of GLib's keyfile functions
  (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to
  producing a different output with this newer release (some strange
  line breaks injected in the middle of a keyfile).

  
  Example keyfile from the test_wifis.test_wifi_wowlan test, that should be 
generated by Netplan and the way it fails:

  Expected output:
  ```
  [connection]
  id=netplan-wl0-homenet
  type=wifi
  interface-name=wl0

  [wifi]
  wake-on-wlan=330
  ssid=homenet
  mode=infrastructure

  [ipv4]
  method=link-local

  [ipv6]
  method=ignore
  ```

  Failure:
  ```
  E   AssertionError: '[con[88 
chars]330\n\nssid=homenet\nmode=infrastructure\n[ipv[44 chars]re\n' != '[con[88 
chars]330\nssid=homenet\nmode=infrastructure\n\n[ipv[44 chars]re\n'
  E [connection]
  E id=netplan-wl0-homenet
  E type=wifi
  E interface-name=wl0
  E 
  E [wifi]
  E wake-on-wlan=330
  E   - 
  E ssid=homenet
  E mode=infrastructure
  E   + 
  E [ipv4]
  E method=link-local
  E 
  E [ipv6]
  E method=ignore
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2026826/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2026230] Re: error when setting up after upgrading

[Danilo Egea Gondolfo]

So,

the problem appears to be the value of "cloned-mac-address". Netplan
only accepts a MAC address, but Network Manager also supports some
special settings ("preserve", "permanent", "random" and "stable").

I prepared a fix for that https://github.com/canonical/netplan/pull/376

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: netplan.io (Ubuntu)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2026230

Title:
  error when setting up after upgrading

Status in netplan.io package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  I received an error from apport about a programme not working. I
  collected the data to submit. Hope this helps.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.42.6-2ubuntu1
  Uname: Linux 6.2.0-24-generic x86_64
  Architecture: amd64
  Date: Wed Jul  5 23:11:14 2023
  ExecutablePath: /usr/sbin/NetworkManager
  ExecutableTimestamp: 1687429583
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: network-manager
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2026230/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2026230] Re: error when setting up after upgrading

[Danilo Egea Gondolfo]

Thank for your bug report.

Based on the core dump you provided, the problem seems to be related to
libnetplan.

Can you collect the NetworkManager's systemd journal and attach to the
ticket, please?

journalctl -u NetworkManager > network-manager.log

Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2026230

Title:
  error when setting up after upgrading

Status in network-manager package in Ubuntu:
  New

Bug description:
  I received an error from apport about a programme not working. I
  collected the data to submit. Hope this helps.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.42.6-2ubuntu1
  Uname: Linux 6.2.0-24-generic x86_64
  Architecture: amd64
  Date: Wed Jul  5 23:11:14 2023
  ExecutablePath: /usr/sbin/NetworkManager
  ExecutableTimestamp: 1687429583
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: network-manager
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2026230/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2025027] Re: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Th

[Danilo Egea Gondolfo]

Based on the files attached to the bug report, the Wifi interface is not
present in the system.

I can see the system tried to initialize it:

jún 20 08:37:40 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi 
:02:00.0: retry init count 0
jún 20 08:37:40 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi 
:02:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
jún 20 08:37:40 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi 
:02:00.0: retry init count 1
jún 20 08:37:40 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi 
:02:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
jún 20 08:37:41 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi 
:02:00.0: retry init count 2


Run the command "rfkill list", does your wifi interface show up in the output?

Also check the output of "ip link".

If it's not showing up it might be a problem with the kernel driver or
the hardware itself.

You could try to install the kernel 5.19 to see if it fixes the problem.

But as far as I can see it's not a problem with Network Manager.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2025027

Title:
  When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise.
  The option to enable Wi-Fi is not available (does not pop up and it is
  hidden while on LAN). Therefore, I can't see any available WiFi
  networks. The issue gets resolved when I reboot the PC.

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  See my public question open here:
  
https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate

  I'd expect, to see the option "dis/enable wifi" at least when I disconnect 
from LAN, (if not regardless on LAN connection). 
  But I can not see that option to enable wifi, nor available wifi networks 
even when I disconnect the LAN cable..

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99
  Uname: Linux 5.15.0-75-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon Jun 26 09:48:33 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source /etc/network/interfaces.d/*
  InstallationDate: Installed on 2023-02-09 (136 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IpRoute:
   default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 
   169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 
   192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 
metric 100
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.36.6   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2025027/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface

[Danilo Egea Gondolfo]

After some more digging, turns out it's not a problem with Netplan.
Although, the problem will manifest depending on how Netplan generates
the configuration for Network Manager.

When selecting the option to store the private key in the KDE wallet
agent, the option "private-key-flags=1" will be added to the resulting
.nmconnection file and the private key will be omitted.

In this case, all the properties set in the group [wireguard] in the
keyfile are not supported by the netplan's keyfile parser and will be
left to be added to the keyfile *after* the wireguard peers, like this:

-
[connection]
id=wg0
type=wireguard
...

[wireguard-peer.M9nt4YujIOmNrRmpIRTmYSfMdrpvE7u6WkG8FY8WjG4=]
endpoint=10.20.30.40:51820
allowed-ips=0.0.0.0/0;

[wireguard]
#Netplan: passthrough setting
private-key-flags=1
#Netplan: passthrough setting
listen-port=51820
---

For some reason, Network Manager will load the connection but *will not*
load the wireguard-peer section.

Moving the [wireguard] section to above [wireguard-peer...] resolves the
issue.

I can't find a reference that says that [wireguard] is supposed to come
before [wireguard-peer].

A workaround you can use while we work on a fix is not use the option to
encrypt the private key and store it in the network manager
.nmconnection file.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2024661

Title:
  Unable to configure Wireguard connection at NetworkManager interface

Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Repro steps:

  1) Open NetworkManager GUI.
  2) Click "Add new Connection" and select "Wireguard" connection type.
  3) Then you have to configure new connection. Basic configuration looks like 
that:
  a) Write down connection name,
  b) Write down local private key,
  c) Create new peer and populate peer's parameters: public key of the 
peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port.
  4) Click "OK" and "Save".
  5) Open "Peers" again. Ensure that settings were not stored. All fields are 
empty.

  Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager 
interface.
  netplan.io 0.106.1-2
  network-manager 1.42.4-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2024661/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface

[Danilo Egea Gondolfo]

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2024661

Title:
  Unable to configure Wireguard connection at NetworkManager interface

Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Repro steps:

  1) Open NetworkManager GUI.
  2) Click "Add new Connection" and select "Wireguard" connection type.
  3) Then you have to configure new connection. Basic configuration looks like 
that:
  a) Write down connection name,
  b) Write down local private key,
  c) Create new peer and populate peer's parameters: public key of the 
peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port.
  4) Click "OK" and "Save".
  5) Open "Peers" again. Ensure that settings were not stored. All fields are 
empty.

  Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager 
interface.
  netplan.io 0.106.1-2
  network-manager 1.42.4-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2024661/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface

[Danilo Egea Gondolfo]

Ok, I think I see what the problem is.

The GUI tool will, by default, not add the private key to the
.nmconnection file. It will use some existing key chain agent to do
that.

We will need to take this into account when parsing the keyfile in
Netplan.

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => High

** Changed in: netplan.io (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2024661

Title:
  Unable to configure Wireguard connection at NetworkManager interface

Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  Repro steps:

  1) Open NetworkManager GUI.
  2) Click "Add new Connection" and select "Wireguard" connection type.
  3) Then you have to configure new connection. Basic configuration looks like 
that:
  a) Write down connection name,
  b) Write down local private key,
  c) Create new peer and populate peer's parameters: public key of the 
peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port.
  4) Click "OK" and "Save".
  5) Open "Peers" again. Ensure that settings were not stored. All fields are 
empty.

  Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager 
interface.
  netplan.io 0.106.1-2
  network-manager 1.42.4-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2024661/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface

[Danilo Egea Gondolfo]

Thanks for your bug report.

May I ask you to attach the NetworkManager's journal (journalctl -u
NetworkManager) to the ticket, please?

I can't reproduce it in Ubuntu Mantic using the NM GUI...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2024661

Title:
  Unable to configure Wireguard connection at NetworkManager interface

Status in netplan.io package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Repro steps:

  1) Open NetworkManager GUI.
  2) Click "Add new Connection" and select "Wireguard" connection type.
  3) Then you have to configure new connection. Basic configuration looks like 
that:
  a) Write down connection name,
  b) Write down local private key,
  c) Create new peer and populate peer's parameters: public key of the 
peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port.
  4) Click "OK" and "Save".
  5) Open "Peers" again. Ensure that settings were not stored. All fields are 
empty.

  Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager 
interface.
  netplan.io 0.106.1-2
  network-manager 1.42.4-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2024661/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2022023] Re: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status

[Danilo Egea Gondolfo]

Thanks for your bug report.

This problem seems to be caused by the netplan migration logic in the
postinst script. I'm looking into it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2022023

Title:
  package network-manager 1.42.4-1ubuntu4 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 8

Status in network-manager package in Ubuntu:
  New

Bug description:
  I am using netplan for my network config.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.42.4-1ubuntu4
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Thu Jun  1 12:05:16 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 8
  InstallationDate: Installed on 2020-04-25 (1131 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  IpRoute:
   default via 192.168.56.1 dev enp7s0 proto static 
   192.168.56.0/30 dev enp7s0 proto kernel scope link src 192.168.56.2
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.3, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.22ubuntu1
   apt  2.7.0
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: 
installed network-manager package post-installation script subprocess returned 
error exit status 8
  UpgradeStatus: Upgraded to mantic on 2023-06-01 (0 days ago)
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2022023/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2021937] Re: preinst writes to /root

[Danilo Egea Gondolfo]

Thanks, Julian.

This behavior was introduced by the netplan integration where we create
a backup of the existing network manager connections. I'll look for a
better place to store the backups.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2021937

Title:
  preinst writes to /root

Status in network-manager package in Ubuntu:
  New

Bug description:
  As part of my sandboxed APT I noticed that the package failed to
  install as it was trying to write to /root.

  /root is a user directory, not a system one, which may not even exist
  because the administrator changed it to like /home/root, for example,
  and we definitely should not be writing system files in user
  directories.

  Preparing to unpack .../16-network-manager_1.42.4-1ubuntu4_amd64.deb ...  
 
  mkdir: cannot create directory ‘/root/NetworkManager.bak’: Read-only file 
system
  cp: cannot create directory 
'/root/NetworkManager.bak/system-connections_1.42.4-1ubuntu2': No such file or 
directory
  dpkg: error processing archive 
/tmp/apt-dpkg-install-x9x0Qo/16-network-manager_1.42.4-1ubuntu4_amd64.deb 
(--unpack):
   new network-manager package pre-installation script subprocess returned 
error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2021937/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections

[Danilo Egea Gondolfo]

After taking another look at this I noticed that the function where we
create the Netplan YAML is called when the connection is created AND
when the connection is going down as though it was being updated.

The first time it's called the parameters is_volatile, is_nm_generated
and is_external are all set to true so we skip the libnetplan calls.
Although when it's called when the connection is going down they are all
false. And that's when the Netplan file is created and network-manager
gets to a point in the code it shouldn't reach, so it crashes and the
files are never removed.

Not sure if calling the plugin writer in this case is a bug or not as
the connection is volatile and is going to be deleted anyway. Maybe lost
tracking of the connection nature (volatile, nm_generated and external)
is the actual bug, not sure yet.

One way to work around this is generating Netplan YAMLs regardless if
the connection is volatile. If network-manager will create a file for it
we could create a file for Netplan too. In fact, after removing the
conditions to call libnetplan, the files are created and deleted when
the OpenVPN client and/or server is stopped.

Note that from network-manager 1.42.0 on, even the loopback interface
can be represented as a connection, so we will have a Netplan file for
it as well.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1998207

Title:
  netplan network-manager plugin tries to save temporary connections

Status in netplan:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  *** Note: This bug is mostly about comment #10, now ***

  When creating an OpenVPN connection, a temporal connection called tunN
  is created. For instance, after activating a connection called
  vpntest, I have:

  NAME  UUID  TYPE  DEVICE
  vpntest   458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn   ens3
  tun0  1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun   tun0

  tun0 is created/removed after activating/deactivating vpntest and
  should not really be saved, but I see netplan adding it in
  /etc/netplan. And while doing so the plugin also reports some errors
  (I see these when stopping the connection):

  Nov 28 16:16:57 ubuntu NetworkManager[11752]:  [1669652217.2920] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: 
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
  Nov 28 16:16:57 ubuntu NetworkManager[11752]:   [1669652217.2920] 
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) 
to 
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
 keyfile writer produces an invalid connection: cannot access file: No such 
file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2006744] [NEW] libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict

[Danilo Egea Gondolfo]

Public bug reported:

I enabled lunar-proposed today (with APT::Default-Release "lunar-
proposed";) and got the error below during update:

Preparing to unpack .../39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ...
Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-AkyzpG/39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also 
in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1
 
Then it will be broken:

root@deleteme-lunar:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libgl1-mesa-dri : Depends: libglapi-mesa (= 22.2.5-0ubuntu1) but 
22.3.4-1ubuntu1 is installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

root@deleteme-lunar:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libicu71 libpython3.10-minimal libpython3.10-stdlib python3.10 
python3.10-minimal
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  libgl1-mesa-dri
The following packages will be upgraded:
  libgl1-mesa-dri
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
62 not fully installed or removed.
Need to get 0 B/7806 kB of archives.
After this operation, 809 kB of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 81205 files and directories currently installed.)
Preparing to unpack .../libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ...
Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also 
in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1
Errors were encountered while processing:
 /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)


How to reproduce:

1. Spin up a Lunar VM
2. Enable -proposed
3. Install libgl1-mesa-dri and libgl1-amber-dri
4. Add APT::Default-Release "lunar-proposed"; to /etc/apt/apt.conf.d/somefile
5. Try to upgrade

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2006744

Title:
  libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1
  file conflict

Status in mesa package in Ubuntu:
  New

Bug description:
  I enabled lunar-proposed today (with APT::Default-Release "lunar-
  proposed";) and got the error below during update:

  Preparing to unpack .../39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ...
  Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-AkyzpG/39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is 
also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1
   
  Then it will be broken:

  root@deleteme-lunar:~# apt upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   libgl1-mesa-dri : Depends: libglapi-mesa (= 22.2.5-0ubuntu1) but 
22.3.4-1ubuntu1 is installed
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

  root@deleteme-lunar:~# apt --fix-broken install
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Correcting dependencies... Done
  The following packages were automatically installed and are no longer 
required:
libicu71 libpython3.10-minimal libpython3.10-stdlib python3.10 
python3.10-minimal
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
libgl1-mesa-dri
  The following packages will be upgraded:
libgl1-mesa-dri
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  62 not fully installed or removed.
  Need to get 0 B/7806 kB of archives.
  After this operation, 809 kB of additional disk space will be used.
  Do you want to continue? [Y/n]
  (Reading database ... 81205 files and directories currently installed.)
  Preparing to unpack .../libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ...
  Unpacking libgl1-mesa-dri:am

[Desktop-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections

[Danilo Egea Gondolfo]

The same problem happens if you spin up an OpenVPN server and kill it.
An yaml file will be created for the tun interface used by the server.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1998207

Title:
  netplan network-manager plugin tries to save temporary connections

Status in netplan:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  *** Note: This bug is mostly about comment #10, now ***

  When creating an OpenVPN connection, a temporal connection called tunN
  is created. For instance, after activating a connection called
  vpntest, I have:

  NAME  UUID  TYPE  DEVICE
  vpntest   458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn   ens3
  tun0  1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun   tun0

  tun0 is created/removed after activating/deactivating vpntest and
  should not really be saved, but I see netplan adding it in
  /etc/netplan. And while doing so the plugin also reports some errors
  (I see these when stopping the connection):

  Nov 28 16:16:57 ubuntu NetworkManager[11752]:  [1669652217.2920] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: 
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
  Nov 28 16:16:57 ubuntu NetworkManager[11752]:   [1669652217.2920] 
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) 
to 
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
 keyfile writer produces an invalid connection: cannot access file: No such 
file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken

[Danilo Egea Gondolfo]

Digging a bit more on that, the problem might be the font build system.
The most recent fonts-dejavu-extra package is shared across Jammy,
Kinetic and Lunar and it appears to be broken on all of them.

Rebuilding the package on Kinetic seems to be enough to fix the problem.
But that's not true for Jammy. So I suppose whatever was broken (maybe
it fontforge?) was fixed in the version we use in Kinetic.

A no-change build is probably enough to fix the issue on Kinetic and
Lunar.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-font-viewer in Ubuntu.
https://bugs.launchpad.net/bugs/1992369

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fontforge package in Ubuntu:
  New
Status in fonts-dejavu package in Ubuntu:
  Confirmed
Status in gnome-font-viewer package in Ubuntu:
  Invalid

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken

[Danilo Egea Gondolfo]

These fonts are working fine in Focal (fonts-dejavu-
extra_2.37-1_all.deb) and broken in Jammy, Kinetic and Lunar (fonts-
dejavu-extra_2.37-2build1_all.deb).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-font-viewer in Ubuntu.
https://bugs.launchpad.net/bugs/1992369

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fontforge package in Ubuntu:
  New
Status in fonts-dejavu package in Ubuntu:
  Confirmed
Status in gnome-font-viewer package in Ubuntu:
  Invalid

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken

[Danilo Egea Gondolfo]

It turns out the font files in our package are probably corrupt. I
tested with the files from the original source [0] and the problem
doesn't happen.

I also replaced the broken ones with the original ones, cleaned my font
cache and the problem appears to be gone.

Will try to find out when it happened.

[0] - https://github.com/dejavu-fonts/dejavu-fonts/releases

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-font-viewer in Ubuntu.
https://bugs.launchpad.net/bugs/1992369

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fontforge package in Ubuntu:
  New
Status in fonts-dejavu package in Ubuntu:
  Confirmed
Status in gnome-font-viewer package in Ubuntu:
  Invalid

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken

[Danilo Egea Gondolfo]

I just noticed that this font (and many others) are marked as
"experimental" even in the most recent version of the source [0] [1]. So
it might be broken in some scenarios.

I opened an issue to clarify if that might be the case [2].

Meanwhile, if you change your XFCE font settings like mentioned above,
does it help?

[0] - 
https://git.launchpad.net/ubuntu/+source/fonts-dejavu/tree/README.md?h=applied/ubuntu/kinetic
[1] - https://github.com/dejavu-fonts/dejavu-fonts/blob/master/README.md
[2] - https://gitlab.freedesktop.org/freetype/freetype/-/issues/1193


** Bug watch added: gitlab.freedesktop.org/freetype/freetype/-/issues #1193
   https://gitlab.freedesktop.org/freetype/freetype/-/issues/1193

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-font-viewer in Ubuntu.
https://bugs.launchpad.net/bugs/1992369

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fontforge package in Ubuntu:
  New
Status in fonts-dejavu package in Ubuntu:
  Confirmed
Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken

[Danilo Egea Gondolfo]

Not sure where the problem is exactly but it can be reproduced like Juha
suggested.

On Xubuntu 22.04 if you go to Settings -> Appearance -> Fonts and set
"Hinting" to "Medium" or "Full" and have
FREETYPE_PROPERTIES="truetype:interpreter-version=35", all the
DejaVuSerif...Italic fonts appear to break.

Either changing the interpreter version to 38 or 40 [0] or setting
"hinting" to "Slight" seems to be a workaround.


[0] - 
https://freetype.org/freetype2/docs/reference/ft2-properties.html#interpreter-version

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-font-viewer in Ubuntu.
https://bugs.launchpad.net/bugs/1992369

Title:
  DejaVu Serif Italic capital letters and digits broken

Status in fontforge package in Ubuntu:
  New
Status in fonts-dejavu package in Ubuntu:
  Confirmed
Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  After updating from Focal to Jammy, I noticed that DejaVu Serif Italic
  looks quite broken. At least the letters EFHKLMNT and the digits 1 and
  4 are affected

  Please see the attached screenshot. This was obtained from `gnome-
  font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf`

  As the font is the default for me in Firefox, it's quite noticeable.

  $ dpkg -l gnome-font-viewer fonts-dejavu-extra
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  
+++-==---==>
  ii  fonts-dejavu-extra 2.37-2build1 all  Vera font family derivate 
with>
  ii  gnome-font-viewer  41.0-2   amd64font viewer for GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp