Attempt to use CJK fonts crashes container

[markalex2209]

I had a problem with Korean symbols not being rendered and ▯▯▯ being shown instead (both in Picard's main menu and dialog for folder/file selection). As I understood, the problem stemmed from the lack of the Korean font in the system.

After investigation, I found that environment variable ENABLE_CJK_FONT is supposed to fix this.

But the addition of that variable causes the container to crash with the following error log:

[cont-init   ] 15-cjk-font.sh: dpkg: unrecoverable fatal error, aborting:
[cont-init   ] 15-cjk-font.sh:  unknown system group 'messagebus' in statoverride file; the system group got removed
[cont-init   ] 15-cjk-font.sh: before the override, which is most probably a packaging bug, to recover you
[cont-init   ] 15-cjk-font.sh: can remove the override manually with dpkg-statoverride
[cont-init   ] 15-cjk-font.sh: E: Sub-process /usr/bin/dpkg returned an error code (2)
[cont-init   ] 15-cjk-font.sh: terminated with error 100.

How to reproduce: add option -e ENABLE_CJK_FONT=1 to docker run command.

Affected versions: 2.11, 2.10.

Version 2.8.5 seems to install CJK fonts successfully, but they don't work in Picard.

---

The problem here seems to be from unexpected content of the file /var/lib/dpkg/statoverride. Maybe there was something wrong with the clean-up after installation on the last image creation?

As a quick and dirty workaround, it's possible to create an image based on the current one, and clean statoverride file:

FROM mikenye/picard

RUN truncate -s 0 /var/lib/dpkg/statoverride

Or as even more dirtier workaround, it's possible to install package for Korean font (fonts-baemuk for example) during container creation. Since container already has fonts for Japanese and Chinese, I guess this will render ENABLE_CJK_FONT redundant for this container.

[louhisuo]

+1. I am facing same issue. Setting ENABLE_CJK_FONT=1 in mikenye/picard:2.11 causes reboot loop in the container.