Dear Maintainer,

   * What led up to the situation?
   In Network settings in GUI clicking the cog icon of the Wired
   connection and trying to setup 802.1x authentication on a wired connection with TLS
   mode.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   Selecting Certificate authority or User certificate yields in cannot
   display file contents error but in GUI it seems like it is selected.
   Then selecting user password closes the whole settings window.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     Not solved yet. Will try to setup it up over commandline

   * What was the outcome of this action?
   Window crash

   * What outcome did you expect instead?
   Successfully setup and saved connection

Am 09.01.25 um 10:34 schrieb Lukas Sismis:

Can you make a screenshot of your UI.
Maybe also start the settings program from the command line and paste
the output.

Michael

Hi Michael,

just to make sure I'll do it correctly, am I supposed to just add the
screenshots as an attachments to the follow-up emails?

I can do so, the same with the terminal output.

Lukas

Am 14.01.25 um 21:54 schrieb Lukáš Šišmiš:

Sure, just attach them to the email.

Hi Michael,


Here is the screenshot.

Just for the record, the certificates are valid and after fighting with
it I was able to kind of connect to the network but it requires some
luck. The issue is present with whatever USB-C Ethernet adapter.

The whole GUI window contains multiple errors so:

1) Upon opening the window what surprised me that it requires User
certificate - when it should not - or at least it should present an
option to skip it. In e.g. new Ubuntu 22.04+ this option is not present.

2) With the settings open in terminal on verbose, each character typed
in the "Identity" produces "Invalid setting Security: invalid EAP-TLS CA
certificate: no certificate specified" OR "Invalid setting Security:
invalid EAP-TLS private-key: no file selected" warning - I guess it
checks all the conditions but the print outs make it a bit to convoluted
- it is a debug message only but still.

3) User certificate file picker window let's you pick the file but it
will complain with a popup saying "The folder contents could not be
displayed. The operation was cancelled". The same for CA certificate and
Private key (if you are lucky). Additionally, in the terminal it shows:

4) After the pop-up, the picked file can be seen but is in red. I would
expect it to be gray.

5) Here is the main challenge - picking the private key leads to
segfault as seen from the logs. That's when the window closes.

6) I have found some way around it - sometimes if I select "Always stay
on the top" - it doesn't segfault and it continues. But still all file
pickers are red and even with all the fields entered, I cannot click the
"Apply" button. But in some rare occasions I was able to. And then it
sometimes worked and sometimes it did not.


Here is the output from the terminal:

$ gnome-control-center -v
07:49:26.0371          network-cc-panel:    DEBUG: coldplugging devices
07:49:26.0371          network-cc-panel:    DEBUG: New device added
07:49:26.0371          network-cc-panel:    DEBUG: device
/sys/devices/virtual/net/lo type 32 path
/org/freedesktop/NetworkManager/Devices/1
07:49:26.0371          network-cc-panel:    DEBUG: New device added
07:49:26.0371          network-cc-panel:    DEBUG: device
/sys/devices/pci0000:00/0000:00:14.3/net/wlp0s20f3 type 2 path
/org/freedesktop/NetworkManager/Devices/2
07:49:26.0371          network-cc-panel:    DEBUG: New device added
07:49:26.0371          network-cc-panel:    DEBUG: device
/sys/devices/virtual/net/wg0 type 29 path
/org/freedesktop/NetworkManager/Devices/9
07:49:26.0371          network-cc-panel:    DEBUG: New device added
07:49:26.0371          network-cc-panel:    DEBUG: device
/sys/devices/virtual/net/tailscale0 type 16 path
/org/freedesktop/NetworkManager/Devices/10
07:49:26.0371          network-cc-panel:    DEBUG: New device added
07:49:26.0371          network-cc-panel:    DEBUG: device
/virtual/device/placeholder/24 type 30 path
/org/freedesktop/NetworkManager/Devices/26
07:49:26.0371          network-cc-panel:    DEBUG: New device added
07:49:26.0371          network-cc-panel:    DEBUG: device
/sys/devices/pci0000:00/0000:00:0d.0/usb2/2-2/2-2.3/2-2.3:1.0/net/enxac1a3def7fa3
type 1 path /org/freedesktop/NetworkManager/Devices/27
07:49:26.0372          network-cc-panel:    DEBUG: Calling handle_argv()
after cold-plugging devices
07:49:26.0392      diagnostics-cc-panel:    DEBUG: ABRT vanished
07:49:31.0387          network-cc-panel:    DEBUG: Invalid setting
Security: missing EAP username
07:49:32.0987          network-cc-panel:    DEBUG: Invalid setting
Security: missing EAP-TLS identity
07:49:34.0098          network-cc-panel:    DEBUG: Invalid setting
Security: invalid EAP-TLS CA certificate: no certificate specified
07:49:34.0345          network-cc-panel:    DEBUG: Invalid setting
Security: invalid EAP-TLS CA certificate: no certificate specified
07:49:34.0440          network-cc-panel:    DEBUG: Invalid setting
Security: invalid EAP-TLS CA certificate: no certificate specified
(gnome-control-center:640436): dconf-DEBUG: 07:49:35.021: watch_fast:
"/org/gtk/gtk4/settings/file-chooser/" (establishing: 0, active: 0)
(gnome-control-center:640436): dconf-DEBUG: 07:49:35.021:
watch_established: "/org/gtk/gtk4/settings/file-chooser/" (establishing: 1)
07:49:36.0553          network-cc-panel:    DEBUG: Invalid setting
Security: invalid EAP-TLS CA certificate: no certificate specified
(gnome-control-center:640436): dconf-DEBUG: 07:49:36.553: change_fast
07:49:42.0982          network-cc-panel:    DEBUG: Invalid setting
Security: invalid EAP-TLS private-key: no file selected
(gnome-control-center:640436): dconf-DEBUG: 07:49:42.983: change_fast
Segmentation fault



Lukas

Hi Lukáš,

what you describe so far looks like a crash in gnome-control-center.
Thank you for the additional information.
I'm thus reassigning the issue accordingly (with a CC of the mantainer)

To further investigate the issue, I would advise you to follow [1] and
get a proper backtrace of the crash including having all the dbg-sym
packages installed.

Regards,
Michael


[1] https://wiki.debian.org/HowToGetABacktrace

Am 16.01.25 um 08:09 schrieb Lukáš Šišmiš: