From Newsgroup: comp.os.os2.misc
On 07/04/19 10:39 PM,
baden@baden.nu wrote:
El jueves, 4 de julio de 2019, 21:37:11 (UTC-5), Dave Yeo escribi||:
On 07/04/19 01:02 PM, baden@baden.nu wrote:
On Thursday, 4 July 2019 01:28:43 UTC-5, Dave Yeo wrote:
baden@baden.nu wrote:
Hi:(Dave?)
I really like the Cairo Clock, so I had Doodle Screen saver installed on my Franken OS/2, which is now almost pure ArcaOS 5.0, with my old ini files overlayed on top. To deal with the former (not in 'Properties'), I installed (ANPM) Doodle 2.1 from Hobbes, and it ran swell for a few weeks. However, a week ago, I noticed my mouse disappeared, and I traced that to Doodle. If I uninstall Doodle, the mouse cursor immediately reappears.
Are you aware of any similar symptoms?
Did you update Freetype from the netlabs exp repository? If so, upgrade >>> For the record, that URL is:
http://rpm.netlabs.org/experimental/00/zip/
it again as 2.10.0-1 broke the Cairo modules, fixed in 2.10.0-2.
That's all I'm aware of for bugs.
I concur that there are probably font issues. I
have the following identically named DLLs, the latest
from your suggestion:
This wasn't font issues, rather a missing mouse pointer or worse caused
by Bitwise enabling mmap in freetype, which broke the Cairo modules as
well as causing some other software to crash such as the 38ESR Mozilla apps. >> I take it that updating freetype fixed the screensaver?
Interestingly these are the exact symptoms.
However, the whole thing is currently a mess.
Note that the issue may be different. I _think_ what was happening was
the module was crashing after turning off the mouse pointer and leaving
it off. Crashes for other reasons may produce similar symptoms.
Did you look in popuplog.os2? I just reviewed mine and see sys3175's in SSMODWRP.EXE caused by FREETYP6.DLL from when I had the problem.
2019/06/18 02:28:00 418401 F:\Applications\freetype-2_10_0-2_oc00\@unixroot\usr\lib\freetyp6.dll
2017/03/01 07:41:20 389797 F:\usr\lib\freetyp6.dll
2016/02/26 08:56:18 380134 F:\OS2_Apps\DLL\freetyp6.dll
2015/07/29 20:59:18 356427 F:\Applications\seamonkey-2.42.9esr.en-US.os2\seamonkey\freetyp6.dll
You should only have one of the freetyp6.dll's installed and it should
match fontconfig. So if updating to the exp version of freetype, you
So, I renamed all the freetyp6.dll, except the new
one which I put in my libpath. No browsers worked. I
put the new freetyp6.dll in my SeaMonkey directory with
the other new dlls and the new freetype-config. I
still got an "xpcom" error. I then reverted to the
original freetyp6.dll in my SeaMonkey directory.
SeaMonkey started right up.
I found before that DSSaver would work without the
Cairo modules. Selecting a Cairo module would still
lose the mouse. PrettyClock will suffice for me.
After changing to the new freetyp6.dll, the Cairo
modules are not even listed on the notebook settings
page.
That's interesting that the Cairo modules vanished. But yes all the
other modules should work as only a couple are linked against the RPM
Cairo. More below.
should also update fontconfig.
I added freetype-config in my path. I am not sure I
am doing the correct thing.
Freetype-config is only for building, namely it configures where
freetype is installed, needed flags and such. You don't need it.
Fontconfig does need to find its configuration files. Possible you have
some in your home directory from years back.
Be aware that fontconfig has had changes to its configuration files that
it looks for in @UNIXROOT\etc\fonts and updating by unlocking fontconfig
as yum/rpm does, will crash SeaMonkey/Firefox until you reboot.
I also have problems running SeaMonkey(s) and
Firefox(s) since I updated to ArcaOS, so I may need to
allocate some time to figure this font stuff out.
What problems?
Dave
SeaMonkey 2.14 And Firefox xx will not start at all.
With the new DLL, I got "freetyp6" errors trying to
start the browsers from ArcaOS.
I take it you mean SeaMonkey 2.35 or 2.42 as 2.14 is old and used freetyp2.dll.
Understand that many of these DLLs depend on specific versions or newer
and it is quite complex. eg the new freetype will need the latest libcx
and libcn at least and as mentioned, fontconfig is dependent on
freetype. Things can go wonkey really quick as your finding.
Why not just install and use ANPM to take care of all these
dependencies? While I don't like the whole RPM/YUM/ANPM thing, it gets
to the point where letting it manage the dependencies is easier then
trying to do it yourself. It's hard to tell which freetyp6.dlls you have.
Also do you have SeaMonkey in the LIBPATH? That's not recommended, and
2.42.9 will actually set beginlibpath and libpathstrict so run! or cmd
files are unneeded and is also likely the reason that adding the DLLs to
the SeaMonkey program directory helps.
Anyways, good luck in straightening out the DLL mess. If not using ANPM,
you might want to just start over.
Dave
--- Synchronet 3.22a-Linux NewsLink 1.2