trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: June 2018

Re: [trinity-devel] "could not find module 'kde-fonts'"

From: Luke Kenneth Casson Leighton <lkcl@...>
Date: Sun, 3 Jun 2018 21:19:16 +0100
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68


On Sun, Jun 3, 2018 at 1:31 PM, Felix Miata <mrmazda@...> wrote:
> Luke Kenneth Casson Leighton composed on 2018-06-03 11:22 (UTC+0100):
>
>> 9th major difference: there are signs that the directory
>> /usr/share/locale-langpack does not exist:
>
>> +access("/usr/share/locale-langpack", F_OK) = -1 ENOENT (No such file
>> or directory)
>
>> also, one of the systems appears to have been set to plastik style,
>> the other to keramik
>
>> at that point the differences becomes significant (line 2603) because
>> the styles do radically different things.  one is looking for
>> /etc/tqt3/qtrc and finds it, the other doesn't look for it.
>
> I recognized all those fontconfig/installed fonts/not installed fonts to be
> irrelevant. The fonts unit worked find via kcontrol.
>
> I've updated
> https://bugs.pearsoncomputing.net/show_bug.cgi?id=2821
> with the cause: having yast2-fonts installed breaks the finding of module fonts.

 interesting.  is that reproducible on both systems (add yast2-fonts
on each, remove yast2-fonts on each).  it would be worthwhile adding
strace logs for both systems, before and after yast2-fonts installed.

l.