https://bugzilla.suse.com/show_bug.cgi?id=1212970 https://bugzilla.suse.com/show_bug.cgi?id=1212970#c5 Franck Bui <fbui@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|systemd-maintainers@suse.de |antonio.teixeira@suse.com --- Comment #5 from Franck Bui <fbui@suse.com> --- (In reply to Franck Bui from comment #4)

...

It would also be fine to ignore this particular error.

It's already ignored by systemd-vconsole-setup and the service doesn't fail.

After looking at this again I wasn't 100% correct here. I copied the logs found in the journal (from commit #0) and added the emitter as well as the log priority for each message:

s-v-c: [LOG_ERR] systemd-vconsole-setup[165]: /usr/bin/setfont failed with exit status 71. setfont: [LOG_ERR] systemd-vconsole-setup[169]: setfont: ERROR kdfontop.c:183 put_font_kdfontop: Unable to load such font with such kernel version s-v-c: [LOG_NOTICE] systemd-vconsole-setup[165]: Setting fonts failed with a "system error", ignoring.

There is/was an inconsistency in the priority used by s-v-c: while setfont failing with exit status 71 is supposed to be ignored by s-v-c, the first message was still emitted as an error. I fixed it (commit 2f26c211718d29c322b2732d99617fce4d837ae1) so both messages are now emitted at LOG_NOTICE. Now only the second message sent by setfont remains at LOG_ERR. I'm not sure whether the real intention of https://github.com/legionus/kbd/commit/1e15af4d8b272ca50e9ee1d0c584c5859102c... was to change the previous behavior... IOW should it really consider a driver without font support as an error ? Antonio, I'm reassigning this bug to you so you can figure out if the previous behavior of kbd needs to be restored. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.