site  contact  subhomenews

First bootup EasyOS Dunfell-series

September 24, 2020 — BarryK

So far, have built 736 packages in OE. That's whole packages, not split up ones. Previous post about this project to compile everything from source in the latest release of OpenEmbedded/Yocto:

...actually, that "horrible hack" did solve the compile fail, but glibc has probably removed the infrastructure to actually make that code work at runtime. I probably should take a look at the latest version of xlockmore (says he, writing yet another reminder on all the bits of paper scattered around on his desk).

So, I did a complete build, and also imported the compiled packages into woofQ, and then built EasyOS ...and hey, it worked, got a desktop!

It seemed perfect, but then started to notice few things wrong...

Opened a text file in Geany text editor, and all characters in the file displayed as rectangular boxes only. Clicked on the "console" icon on the desktop to start the Sakura terminal emulator, same problem.

After considerable bafflement, I realised that what is failing is the monospace Type1 font (Nimbus Mono L). It does display OK in the urxvt terminal emulator, which is an X11 app. It is GTK apps that are the problem, both gtk2 and gtk3.

A very brief online search has suggested that the harfbuzz package is the cause of this problem. I won't try to track the cause down any further, rather, will remove the Type1 font.

Why am I still using a Type1 font anyway? This is an early Postscript font format, and, I don't know the precise details, but it is a very restrictive format compared with TrueType. That to-do has been added on one of those bits of paper.

The build has the Epiphany web browser. Seems OK. As that is the one officially supported by OE, might stay with that, and provide SeaMonkey as an SFS. Chromium as an SFS also. The OE build does not have LibreOffice, so might just have that as an SFS also.

Gotta say, this is an enjoyable exercise! 

Tags: easy