Description of problem: The NetworkManager failed to load the old ifcfg config files after upgrading from Fedora 35 to Fedora 36. The expected behavior would be for it to either migrate the ifcfg files to keyfiles and start OR to ignore those deprecated ifcfg config files and start nonetheless, but definitely not crash. Migrating the configs works and makes it run successfully, so this should be done automatically as part of the upgrading process for the user. For more information, check here: https://forums.fedoraforum.org/showthread.php?328599-Network-Manager-no-longer-runs-after-upgrading-from-Fedora-35-to-Fedora-36 Version-Release number of selected component: NetworkManager-1:1.38.0-2.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/system.slice/NetworkManager.service cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: nm_supplicant_interface_get_capability executable: /usr/sbin/NetworkManager journald_cursor: s=71cd9bea53c74231afed1bf8754eecea;i=45a29e;b=16c7e954008f4af1ab788a133c485512;m=da65519;t=5e0606e2bf3a3;x=57a22db9f2ae2c00 kernel: 5.17.12-300.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 nm_supplicant_interface_get_capability at src/core/supplicant/nm-supplicant-interface.c:1400 #1 check_connection_compatible at src/core/devices/wifi/nm-device-wifi.c:1079 #2 find_parent_device_for_connection at src/core/nm-manager.c:1872 #3 retry_connections_for_parent_device at src/core/nm-manager.c:2171 #4 manager_device_state_changed at src/core/nm-manager.c:1570 #5 ffi_call_unix64 at ../src/x86/unix64.S:105 #6 ffi_call_int at ../src/x86/ffi64.c:672 #7 g_cclosure_marshal_generic at ../gobject/gclosure.c:1534 #9 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3743 #12 _set_state_full at src/core/devices/nm-device.c:15550
Created attachment 1885968 [details] File: backtrace
Created attachment 1885969 [details] File: core_backtrace
Created attachment 1885970 [details] File: cpuinfo
Created attachment 1885971 [details] File: dso_list
Created attachment 1885972 [details] File: environ
Created attachment 1885973 [details] File: exploitable
Created attachment 1885974 [details] File: limits
Created attachment 1885975 [details] File: maps
Created attachment 1885976 [details] File: mountinfo
Created attachment 1885977 [details] File: open_fds
Created attachment 1885978 [details] File: proc_pid_status
Created attachment 1885979 [details] File: var_log_messages
fixed upstream by https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/fe7bdaa7e496842ce868e40dee032dc42fe2b3e4 thanks for the report!!!
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.