On Thursday 26 of December 2019 23:30:36 ajh-valmer wrote:

On Thursday 26 December 2019 20:14:17 Slávek Banko wrote:

...

...

On Thursday 26 of December 2019 19:56:13 ajh-valmer wrote: # dpkg-reconfigure tdm-trinity "insserv: FATAL: service mountkernfs is missed in the runlevels 1 2 3 4 5 to use service networking insserv: exiting now !" What is the service "mountkernfs" ?

Hi André, please have you updated to the latest version? Insserv call failure for reasons not related to tdm-trinity has already been resolved by commit b89ef6e33b:

Hi Slavek,

I have upgraded and always : # dpkg-reconfigure tdm-trinity insserv: warning: script 'S19tdm' missing LSB tags insserv: warning: script 'tdm' missing LSB tags insserv: warning: script 'tdm' missing LSB tags insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script tdm. Maybe, this line not linked to Trinity : insserv: FATAL: service mountkernfs is missed in the runlevels 1 2 3 4 5 to use service networking insserv: exiting now !

Oh, there may be one thing: insserv reports a bug, because there really is something wrong with some packages other than tdm-trinity. However, the tdm-trinity package as such should now ignore this error from insserv and complete its work.

http://mirror.git.trinitydesktop.org/cgit/tde-packaging/commit/?h=r14.0. x&id=b89ef6e33b

tdebase/debian/tdm-trinity.postinst : Don't understand what to do... ?

You can check in tdm.postinst, if in the insserv call you really have added: " || true"

Regards,

André

Cheers