Appimagekit: What is the problem with QQ now?

Created on 27 Nov 2017  路  27Comments  路  Source: AppImage/AppImageKit

I am Kevin from deepin, What is the problem with QQ now?

Can you provide wrong information or screenshots?

Most helpful comment

AppImage is running now. But it still needs to be optimized.

All 27 comments

QQ is a 32-bit Windows executable. This is difficult because:

  • [x] I need to figure out how to bundle WINE in an AppImage
  • [x] I need to figure out how to bundle 32-bit binaries for use on 64-bit machines in an AppImage
  • [x] I need to figure out how to make WINE use a read-only $WINEPREFIX contained in an AppImage without copying everything to $HOME first
  • [x] I need to make it free of crashes
  • [x] I need to test it
  • [x] I need keep the mountpoint even though the launched WINE exits after logging in
  • [x] I need to find a way to make the first launch faster
  • [x] I need to find a way to reduce udiskd activity
  • [ ] I need to fix Unable to update the static FcBlanks
  • [ ] I need to fix Cannot run due to existing symlinks in /tmp (FIXME)
  • [ ] I need to minimize it to reduce the AppImage size
  • [ ] I need to install Chinese fonts into the WINEPREFIX and set the registry to use them
  • [ ] I need to get rid of /tmp/ld-linux.sh https://github.com/Hackerl/Wine_Appimage/issues/11#issuecomment-445545841
  • [ ] I need to document everything

1 zr2knzzzzbbh1nc1bbxkzw

I've forwarded the question to the developer.

AppImage is running now. But it still needs to be optimized.

@probonopd by the way, what does "Gamux" stand for?

Chinese instant messenger meets German distribution:

@probonopd What's the same problem with the screenshot under the deepin?

  1. Open the registry , the command WINEPREFIX=$bottle wine regedit
  2. Import the registry file according to the content of the screenshot.

_ _20171129093250

QQ_fonts.reg.zip

@TheAssassin "Gamux" = Game + Linux, a community about Linux games. they hope spread linux and opensource in china through offerting more games. and they have explored more than 4 years for offering same experiences in different distributions. the AppImage is very well in line with their goals. so they embrace AppImage.
AppImage for Gamux = appImage for chinese linux user.

deepin@deepin:~/Desktop$ ./QQ-20171129-x86_64.AppImage wine: cannot find L"C:\\windows\\system32\\wineboot.exe" Wine cannot find the ncurses library (libncurses.so.5). Unable to update the static FcBlanks: 0x0600 Unable to update the static FcBlanks: 0x0601 Unable to update the static FcBlanks: 0x0602 Unable to update the static FcBlanks: 0x0603 Unable to update the static FcBlanks: 0x06dd Unable to update the static FcBlanks: 0x070f Unable to update the static FcBlanks: 0x2028 Unable to update the static FcBlanks: 0x2029 Unable to update the static FcBlanks: 0xfff9 Unable to update the static FcBlanks: 0xfffa Unable to update the static FcBlanks: 0xfffb

@jingle0927 which distribution and version are you using? How can this be reproduced?
/etc/fonts/fonts.conf on your system may be causing your issue. Can you please attach it (zip) to this ticket? Please see https://bbs.archlinux.org/viewtopic.php?id=195198

@probonopd deepin distribution QQ_fonts.reg.zip ?

fc-cache -f

then is ok

_deepin-terminal_20171130145829

I find some problem in QQ AppImage. After I close it and reopen it many times, I can't open QQ again. The message in the terminal:
Cannot run due to existing symlinks in /tmp (FIXME)

Do I need learn to read and write Chinese (and type it on my keyboard) in order to use this? :-)
(I'm WILLING, but my brain may be too old by now...)

@KurtPfeifle there is also an (older?) International version which can do English, will probably be next on the list...

The fc-cache -f command takes way too long for it to be executed upon every start of the AppImage. Does this problem occur on __every__ installation of Deepin and on the Live ISO? Otherwise we may just give users the instruction to run the command (once).

Cannot run due to existing symlinks in /tmp (FIXME)

Need to

rm /tmp/ld-linux.so.2

Needs to be fixed in the AppImage AppRun script.

About the fonts:
The registry entry just sets some Windows fonts to be replaced by some Linux fonts. But if the fonts are not installed in Linux, then it will not work. But I think it is OK because people who use Chinese will probably have Chinese fonts installed in their Linux OS.

we can put windows fonts needed in the driver_c/windows/Fonts as well as Import the registry file
and then the problem can be solved .

Very good @askme765cs we should do that. Which Chinese fonts (under a permissive license) do you recommend?

Since windows fonts are not allowed to be used or distributed out of the Windows ,use opensource fonts may be a good ideal as a substitute.Place the fonts needed in driver_c/windows/Fonts,so that it no longer needs there fonts exists in targeted system.
I suggest the wenquanyi project (https://sourceforge.net/projects/wqy/files/) .This project supplies various of chinese opensource fonts.Fonts from this projects are uesd as the default chinese fonts in many linux distributions.
How to:
Step1
place the fonts you want to use in driver_c/windows/Fonts
Step 2 modify and import the .reg file

an example for chn_font.reg

'''
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersionFontLink\SystemLink]
"Lucida Sans Unicode"="wqy-microhei.ttc"
"Microsoft Sans Serif"="wqy-microhei.ttc"
"MS Sans Serif"="wqy-microhei.ttc"
"Tahoma"="wqy-microhei.ttc"
"Tahoma Bold"="wqy-microhei.ttc"
"SimSun"="wqy-microhei.ttc"
"Arial"="wqy-microhei.ttc"
"Arial Black"="wqy-microhei.ttc"
'''
replace fonts back following the "=" to fonts you prefer
use WINEPREFIX=$bottle wine regedit command to open the regedit and import it

@jingle0927 do you know [email protected]? He has sent patches to WINE before, so maybe he could help us on solving this:

https://www.winehq.org/pipermail/wine-devel/2017-November/119944.html

It's not possible in standard Wine, but you could probably hack
wine_exec_wine_binary() in libs/wine/config.c to add your special magic.

Here is the description of the problem:
https://www.winehq.org/pipermail/wine-devel/2017-November/119906.html

If we could patch WINE in the way suggested above, then we would not need these weird symlinks in /tmp anymore that I had to use as a quick-and-dirty workaround.

Thanks for your help.

Any update on this topic? Is it still required to keep the issue open?

Yes, shall be kept open until someone implements https://github.com/AppImage/AppImageKit/issues/551#issuecomment-350465625 in/for WINE, as that is the "proper" course of action. Thanks.

@probonopd That's good!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

emanresusername picture emanresusername  路  3Comments

probonopd picture probonopd  路  8Comments

niess picture niess  路  6Comments

jakub-bochenski picture jakub-bochenski  路  8Comments

TheAssassin picture TheAssassin  路  9Comments