Perhaps you may be on to something - my SSID has caused some issues on systems that cannot handle some characters. Strange that it ended up in the network configuration regardless.
I would agree, it is not a "BIG" issue from my perspective. More of a nuisance I suppose. I would have to test with my other "normal" SSID to see if it works as expected but again, don't believe it's a big issue, so I'm not sure that's really necessary. -Austin On Wed, Jun 28, 2023, at 2:47 PM, Cyril Brulebois wrote: > Austin Moss <aus...@themosses.org> (2023-06-28): > > Thank you for taking a look at this. Attached an archive with > > /var/log/installer/syslog for you. > > The relevant parts of the log are likely the following: > > Jun 27 22:03:08 netcfg[4939]: DEBUG: Network config complete > Jun 27 22:03:08 netcfg[4939]: DEBUG: No interface given; clearing > /etc/network/interfaces > Jun 27 22:03:08 netcfg[4939]: DEBUG: Writing informative header > Jun 27 22:03:08 netcfg[4939]: DEBUG: Success! > Jun 27 22:03:08 netcfg[4939]: DEBUG: Writing loopback interface > Jun 27 22:03:08 netcfg[4939]: DEBUG: Success! > Jun 27 22:03:08 netcfg[4939]: DEBUG: Writing DHCP stanza for wlp4s0 > Jun 27 22:03:08 netcfg[4939]: INFO: Detected wlp4s0 as a hotpluggable > device > Jun 27 22:03:08 netcfg[4939]: DEBUG: Writing wireless options for wlp4s0 > Jun 27 22:03:08 netcfg[4939]: DEBUG: Success! > Jun 27 22:03:09 netcfg[4939]: INFO: Unable to open file for writing > network-manager configuration. The connection id (¯\_(ツ)_/¯) might not be set > to a proper value. > > And later: > > Jun 28 03:20:31 finish-install: info: Running > /usr/lib/finish-install.d/55netcfg-copy-config > Jun 28 03:20:31 netcfg: DEBUG: copy-config: /tmp/connection_type not > found: netcfg did not complete or was compiled without network-manager > support; exiting. > > While I'm not familiar with all the details, it looks to me the funky > connection ID prevented some initial configuration, which led to a > missing file expected at the end of the installation, which in turn led > to a fallback /e/n/i configuration instead of the detected/desired NM > configuration. But seeing how the last DEBUG message leads to an early > exit in the finish-install script (responsible for copying things > around), I'm not sure why/how /e/n/i got copied from the installer's > context to the installed system… > > > In any case, this might not be a “big issue” as I feared, just > particular circumstances? > > > Cheers, > -- > Cyril Brulebois (k...@debian.org) <https://debamax.com/> > D-I release manager -- Release team member -- Freelance Consultant > > > *Attachments:* > • signature.asc
