ubuntu16.04: tcsd
I have a TPM in my machine,but trousers.service failed: It report: Failed to start LSB:starts tcsd So how to deal with it ? Regards, Kun Yan -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
ubuntu16.04: tcsd
I have a TPM in my machine,but trousers.service failed: It report: Failed to start LSB:starts tcsd So how to deal with it ? Regards, Kun Yan -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: dosbox 0.74-4.2build1 amd64 produces runtime-errors (now)
On 06.03.2017 [10:34:06 +], Nico Schumann wrote: > Hello dear package maintainers, after a new installation from lubuntu > 16.4LTS to lubuntu 16.10, dosbox doesn't work anymore correctly. Now I > get this runtime error when I'm runing some games: > Exit to error: DRC64:Unhandled memory reference > On lubuntu 16.4 LTS, dosbox works fine at them. I looked for the 16.4 > LTS package version here, and it seems that's the same version like in > 16.10. Hence I think, the failure could be due building with a > different compiler/-version then it was been build at 16.4 LTS. It is best to search for existing bug reports first, I think: https://bugs.launchpad.net/ubuntu/+source/dosbox And there is: https://bugs.launchpad.net/ubuntu/+source/dosbox/+bug/1569438 Thanks, Nish -- Nishanth Aravamudan Ubuntu Server Canonical Ltd -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
dosbox 0.74-4.2build1 amd64 produces runtime-errors (now)
Hello dear package maintainers, after a new installation from lubuntu 16.4LTS to lubuntu 16.10, dosbox doesn't work anymore correctly. Now I get this runtime error when I'm runing some games: Exit to error: DRC64:Unhandled memory reference On lubuntu 16.4 LTS, dosbox works fine at them. I looked for the 16.4 LTS package version here, and it seems that's the same version like in 16.10. Hence I think, the failure could be due building with a different compiler/-version then it was been build at 16.4 LTS. Regards, Nico -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
