status bar error

[mouad-all]

Hello,

I installed oasislinux on bare metal and after launching velox, switching to another tty and returning to velox, I am getting this error:

status bar: Initializing...Fontconfig error: Cannot load default config file

It seems like there is a font problem, how do I configure that please.

[danielboston38]

did you install any fonts?

[michaelforney]

Could you also clarify whether you are actually seeing problems with fonts, or are you just concerned about the error message?

[danielboston38]

do fonts get installed automatically when you install wayland?

[mouad-all]

Thank you very much for your reply.

I finally figure it out. You need to create a directory fontconfig in .config containing an xml file named fonts.conf. It contains the directories where to find the fonts.

@danielboston38 I installed what is added by default in the sets.lua file (terminus-fonts and adobe-source-fonts) and then added Cascadia Code fonts manually.

@michaelforney Regarding fonts, I tried SourceCodePro fonts with velox. They are ugly. So I added Cascadia Code otf fonts, but they are ugly too. Terminus fonts are acceptable. The default fonts of netsurf are unreadable. Please, how do I set the fonts for netsurf to look like your screenshot in the wiki?

[michaelforney]

I finally figure it out. You need to create a directory fontconfig in .config containing an xml file named fonts.conf. It contains the directories where to find the fonts.

You don't need to do this. fontconfig still works without a config file. It will search in the default directory, /share/fonts. You can ignore the error.

@michaelforney Regarding fonts, I tried SourceCodePro fonts with velox. They are ugly. So I added Cascadia Code otf fonts, but they are ugly too. Terminus fonts are acceptable. The default fonts of netsurf are unreadable. Please, how do I set the fonts for netsurf to look like your screenshot in the wiki?

The screenshot is the default. The fonts for netsurf are hardcoded in pkg/netsurf/config.h, and use adobe-source-fonts (SourceSans3, SourceSerif4, and SourceCodePro). I'm not sure why your netsurf might look different, since it doesn't even use fontconfig, but loads the fonts directly.

velox and st use Terminus. They use wld for rendering, which only supports bitmap fonts. Terminus is the only bitmap font included in oasis, and it's also hardcoded in pkg/st/config.h and pkg/velox/src/clients/status_bar.c. If you try to use a truetype font, it will be rendered as bitmap, which doesn't look good. Maybe that's what you're seeing? Use a bitmap font for best results.

[mouad-all]

@michaelforney It turned out that velox colors are rendered as green. At first, I thought that's the default setup, but when I changed the colors in the config file, they were still rendered as green or white. PDFs are not displayed correctly with mupdf (like in netsurf, that's why I thought it was a fonts problem), same with videos.

I compiled oasislinux with GPU driver enabled in config.lua (video_drivers={intel=true}) but the colors and fonts are still messed up.

[danielboston38]

what driver are you using? don't use the old intel driver just use the built in driver from linux.

wayland does still have some weirdness i noticed even though its been implemented by most distros. it would be interesting to see if you installed a x server if you had the same issues.

[mouad-all]

@danielboston38 I used the built-in drivers of the linux kernel, still I could not for the life of me fix the colors problem!

[michaelforney]

I'm not sure what you mean by the "built in driver from linux". Both the generic pixman renderer and and the intel BLT renderer both use the intel drm driver in linux.

@PapillonAll try running velox with WLD_DRM_DUMB=1, which will force wld to use dumb buffers and software rendering.

[mouad-all]

@michaelforney Running velox with WLD_DRM_DUMB=1 did not work!

My hardware:

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)

I built oasislinux without video_drivers={intel=true} in config.lua.

[danielboston38]

yes the drm driver. there is a driver provided by intel but its horribly out of date.

i haven't really messed with wayland with a intel only setup. is this integrated graphics? you might check the arch wiki and see if there are any mentions of issues? i'd check both the wayland article and the intel one.

also would still be a interesting bit of debugging if you built a x server and see if the issue is the same.

[danielboston38]

@michaelforney Running velox with WLD_DRM_DUMB=1 did not work!

My hardware:

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)

I built oasislinux without video_drivers={intel=true} in config.lua.

uhhh your aware this chip is almost 20 years old?

[michaelforney]

yes the drm driver. there is a driver provided by intel but its horribly out of date.

I'm still confused. Which driver are you talking about?

i haven't really messed with wayland with a intel only setup. is this integrated graphics? you might check the arch wiki and see if there are any mentions of issues? i'd check both the wayland article and the intel one.

I doubt the arch wiki page would be very relevant to oasis.

uhhh your aware this chip is almost 20 years old?

Who cares? If it has a linux drm driver, it should work.