First thing I'd double check is that when you did your (dist-)upgrade, that you also updated the TurnKey repos (i.e. the files in /etc/apt/sources.list.d/) to also be jessie (and not just the Debian ones). You probably did, but just in case.
If not, then hopefully that's the issue and updating the TurnKey apt source files and installing the latest should (hopefully) fix it.
If it does match that, then I'm not really sure OTTOMH. Obviously your screenshot suggests that the init-script is failing (exit code 1). Although from your output, I'm not completely clear why. I note that it's whinging about $TERM not being set, which may be the issue, but I'm not sure if it is, nor why that would be occurring.
I suggest that you try launching it from the commandline as hopefully that will give us some more explicit output. If nothing else, that might help nudge my memory in the right direction! As you've probably guessed, it should be launchable like this:
confconsole
Actually, now that I think about it, it may have something to do with the new plugins system that confconsole now supports?! IIRC we added that in v14.2 and I don't think we ever tested it for a Debian (dist-)upgrade scenario (just upgrading from v14.0/14.1 to v14.2). Anyway, if it still whinges about $TERM, perhaps this is worth a try?:
export TERM=linux
confconsole
Regardless, please post back the stacktrace that manually launching confconsole will likely spit out.
Hmm weird?!
First thing I'd double check is that when you did your (dist-)upgrade, that you also updated the TurnKey repos (i.e. the files in
/etc/apt/sources.list.d/) to also bejessie(and not just the Debian ones). You probably did, but just in case.A really quick way to check is like this:
It should return, something like this:
confconsole: Installed: 1.0.1+g7e2bdbe Candidate: 1.0.1+g7e2bdbe Version table: *** 1.0.1+g7e2bdbe 999 999 http://archive.turnkeylinux.org/debian jessie/main amd64 Packages 100 /var/lib/dpkg/statusIf not, then hopefully that's the issue and updating the TurnKey apt source files and installing the latest should (hopefully) fix it.
If it does match that, then I'm not really sure OTTOMH. Obviously your screenshot suggests that the init-script is failing (exit code 1). Although from your output, I'm not completely clear why. I note that it's whinging about
$TERMnot being set, which may be the issue, but I'm not sure if it is, nor why that would be occurring.I suggest that you try launching it from the commandline as hopefully that will give us some more explicit output. If nothing else, that might help nudge my memory in the right direction! As you've probably guessed, it should be launchable like this:
Actually, now that I think about it, it may have something to do with the new plugins system that confconsole now supports?! IIRC we added that in v14.2 and I don't think we ever tested it for a Debian (dist-)upgrade scenario (just upgrading from v14.0/14.1 to v14.2). Anyway, if it still whinges about $TERM, perhaps this is worth a try?:
Regardless, please post back the stacktrace that manually launching confconsole will likely spit out.