Fotconfig is depreciated

[steve7233]

I just issued the following command to fix this so I can hopfully run the Everquest Landmark closed beta:

mv .fonts.conf .config/fontconfig/fonts.conf

Its taking forever should it be taking over an hour?



The title is mispelled but I cant edit it.





;

[steve7233]

I went ahead an typed the escape code in the konsle and tried the program again. It still crashes with a fontconfig is depreciated warning.

[oshunluvr]

The "fontconfig is depreciated" warning is just that - a warning. That's not whats crashing the Everquest program. I can't comment on why moving that tiny file should take so long.

[steve7233]

Yes winehq claims that fixmes can always be ignored however in this case I think this one is causing a problem because the last part of the games crash log suggests that it crashed right after it got the fontconfig problem. I tried just renaming font.con to font-con and the game complained that it coudn't find the font config default file which was also a fixme error. I am going to try the program in my windows Vista vd via Virtualbox to make sure it is a software and not hardware problem. I am guesssing the FPS will be to low to ply, lol. EQII works sort of. To play EQII I have to goto the install directory and run launchpad.exe manualy. I try this with Landmark and I can log in and patch. When I click play it starts to initualize the game then crashes to the desktop. I saw on wine app database that alot of Linux users ran the alpha version of the game. When I researced the fontconfig problem I discovered that many distros have the problem mostly Ubutu and vareants! Obviously this is not a wine problem. This is a Linux problem mostly a Ubuntu problem! The ubuntu devs need to fix this ASAP please.

[oshunluvr]

https://bugs.launchpad.net/ubuntu/+s...g/+bug/1068549

Virtually every program that accesses fonts generates this message. Even winehq agrees with me, so I'm not changing my opinion on this: the font config warning is not the reason your program is crashing. If it is; the program is to poorly written to be used anyway. More likely, the error or source of the crash is not reporting itself. Try running the program from the command line with the debugging tool gdb and see if you get more meaningful output: