Hi Brandon. Thanks very for reporting your issue. And thanks too for providing all the info I asked for your in "intro post".
Starting at the end, that failing 'apt' command was my bad. I meant to ask for 'apt list confconsole'. It was a "brain fart" as they say here in Australia! :) (Perhaps where you are too?)
For some context (in my common rambling style), please read on. If you're in a rush and/or you're not into ramble, please skip to below the next horizontal rule. :)
FWIW I mixed up a few different commands, and asked you for something that was never going to work. Apologies about that. Historically the package related apt commands were either 'apt-get SUB_COMMAND' or 'apt-cache SUB_COMMAND'. Modern apt still supports those commands and they are recommend for use in scripts (i.e. non interactive). However, the preferred interactive commands now are all 'apt SUB_COMMAND' these days.
When responding to your post, I initially asked for the succinct package version info provided by the "modern" 'apt list confconsole' command. Then I changed my mind, intending to ask you for the more detailed info displayed by the 'apt policy confconsole' command. But when editing my post, on auto pilot I mixed up the modern command with the "legacy" one, 'apt-cache policy confconsole'.
TLDR; I completely muffed my edit...!
Re the confconsole issue, that's clearly a bug; an oversight on our behalf. A situation we hadn't accounted for.
I've just double checked and unsurprisingly, I can reproduce it and have a few ideas on what behavior is preferable. At the very least it should fail gracefully; with a meaningful error message, rather than a stacktrace. Even better, it probably should either offer to fix it, or just fix it for you, probably with a message about what it's done. As such, I've opened an bug report.
I'd be interested in your thoughts on the best fix. And perhaps even the message you think it should show.
I'll aim to fix that ASAP. But in the meantime you can resolve the current error by editing the config file (/etc/confconsole/confconsole.conf) and change the default NIC to 'eth0'. I.e. so it looks like this:
default_nic eth0
Then restart Confconsole - with the command 'confconsole'. After that it should work as expected.
Thanks again for reporting and please don't hesitate to let me know if you have any further issues, ideas for improvements or any other feedback.
Hi Brandon, thanks for reporting your issue
Hi Brandon. Thanks very for reporting your issue. And thanks too for providing all the info I asked for your in "intro post".
Starting at the end, that failing 'apt' command was my bad. I meant to ask for 'apt list confconsole'. It was a "brain fart" as they say here in Australia! :) (Perhaps where you are too?)
For some context (in my common rambling style), please read on. If you're in a rush and/or you're not into ramble, please skip to below the next horizontal rule. :)
FWIW I mixed up a few different commands, and asked you for something that was never going to work. Apologies about that. Historically the package related apt commands were either 'apt-get SUB_COMMAND' or 'apt-cache SUB_COMMAND'. Modern apt still supports those commands and they are recommend for use in scripts (i.e. non interactive). However, the preferred interactive commands now are all 'apt SUB_COMMAND' these days.
When responding to your post, I initially asked for the succinct package version info provided by the "modern" 'apt list confconsole' command. Then I changed my mind, intending to ask you for the more detailed info displayed by the 'apt policy confconsole' command. But when editing my post, on auto pilot I mixed up the modern command with the "legacy" one, 'apt-cache policy confconsole'.
TLDR; I completely muffed my edit...!
Re the confconsole issue, that's clearly a bug; an oversight on our behalf. A situation we hadn't accounted for.
I've just double checked and unsurprisingly, I can reproduce it and have a few ideas on what behavior is preferable. At the very least it should fail gracefully; with a meaningful error message, rather than a stacktrace. Even better, it probably should either offer to fix it, or just fix it for you, probably with a message about what it's done. As such, I've opened an bug report.
I'd be interested in your thoughts on the best fix. And perhaps even the message you think it should show.
I'll aim to fix that ASAP. But in the meantime you can resolve the current error by editing the config file (/etc/confconsole/confconsole.conf) and change the default NIC to 'eth0'. I.e. so it looks like this:
Then restart Confconsole - with the command 'confconsole'. After that it should work as expected.
Thanks again for reporting and please don't hesitate to let me know if you have any further issues, ideas for improvements or any other feedback.