docker-wechat
docker-wechat copied to clipboard
The text in the input box is invisible
你好~盒装微信非常好用,很棒很厉害。 在使用的时候我遇到了这样子的问题: 输入框内输入的文字并没有显示,无论是中文或英文。 虽然文字在输入框中不可见,但当我点击发送时,我的输入文字是被发送的,在聊天记录中可见。(即我的输入实际上输入到了我的输入框,但我无法看到它,除非我将它发送出去) 请问这个有什么好的解决方法吗? 谢谢!
os:
./+o+- yul@yul-F117-V
yyyyy- -yyyyyy+ OS: Ubuntu 18.04 bionic
://+//////-yyyyyyo Kernel: x86_64 Linux 5.3.0-42-generic
.++ .:/++++++/-.+sss/` Uptime: 5h 45m
.:++o: /++++++++/:--:/- Packages: 3507
o:+o+:++.`..```.-/oo+++++/ Shell: bash 4.4.20
.:+o:+o/. `+sssoo+/ Resolution: 3840x1080
.++/+:+oo+o:` /sssooo. DE: GNOME
/+++//+:`oo+o /::--:. WM: GNOME Shell
\+/+o+++`o++o ++////. WM Theme:
.++.o+++oo+:` /dddhhh. GTK Theme: Ambiance [GTK2/3]
.+.o+oo:. `oddhhhh+ Icon Theme: ubuntu-mono-dark
\+.++o+o``-````.:ohdhhhhh+ Font: Ubuntu 11
`:o+++ `ohhhhhhhhyo++os: CPU: Intel Core i7-9750H @ 12x 4.5GHz
.o:`.syhhhhhhh/.oo++o` GPU: GeForce RTX 2060
/osyyyyyyo++ooo+++/ RAM: 4960MiB / 15937MiB
````` +oo+++o\:
`oo++.
原因出在riched20 和 riched32 两个配置上,但目前我只能通过
docker start
的方法启动已经配置好的容器,没办法使用你的新建容器脚本来启动。
I believe we have already pre installed the richard
winetricks in the docker container, and I'm using it under Ubuntu without this problem.
If you can figure out how to solve your problem, please send a pull request and I will check it.
I am geting the same issue on openSUSE, for the VERSION=2.8.0.121 .
VERSION=2.8.0.112 is working fine for me.
I just update the DoChat in version 0.7into the lastest , and I appear to find this problem , my system is ubuntu18.04 , Docker version 19.03.6;
How can I solve this problem? Thanks
ubuntu 20.04 with ibus is same.
ubuntu 20.04 is same.
同样的问题 Archlinux, FCITX
Same issue here in Ubuntu 20.04 LTS.
不知道是什么问题, 我同一个镜像,昨天更新了系统,重启后,同一镜像,更新前是可以输入回显的,更新后就不行了 另一个同样的问题是,权限问题,更新前是没事的,更新后要手工chown改数据目录为当前用户的权限
感觉和字体有点关系。2.9目前是好的,但是引用文字点开的显示是空白。
Ubuntu 20.04 same issue
@huan 你还有三个月前的2.7.1.85版本吗? 这版本几乎完美,不会出现输入框不见的问题,也可以发图片
We have 2.7.1.85
tag and you can use it by running docker pull zixia/wechat:2.7.1.85
.
Or for your convenience, run DoChat with the following command:
curl -sL https://raw.githubusercontent.com/huan/docker-wechat/master/dochat.sh \
| DOCHAT_WECHAT_VERSION=2.7.1.85 bash
Does that work for you?
We have
2.7.1.85
tag and you can use it by runningdocker pull zixia/wechat:2.7.1.85
.Or for your convenience, run DoChat with the following command:
curl -sL https://raw.githubusercontent.com/huan/docker-wechat/master/dochat.sh \ | DOCHAT_WECHAT_VERSION=2.7.1.85 bash
Does that work for you?
不行,至从一次升级系统重启后,现在docker hub上的所有tag都会出现输入框显示不了, 输入框不显示会导致无法粘贴图片,虽然可以发文字 (看我docker images的截图,所有版本都用过了,就只有三个月前那个是完好的,当时的tag名也叫2.7.1.85)
Can you share your image with us? I can use that hash to overwrite the Docker Hub version and keep it not to be overwritten in the future.
I uploaded it to ystyle/wechat
tag: 2.7.1.85
https://hub.docker.com/r/ystyle/wechat
docker pull ystyle/wechat:2.7.1.85
@ystyle Brilliant!
I have sync that version with yours at https://hub.docker.com/layers/zixia/wechat/2.7.1.85/images/sha256-e6e9d21c7cd1dfae0484e697f12f5f3c401de2f02e771d061868740e0d26549d?context=repo
And please let me know if it works for you.
Also, we should investigate in it to see what's the key difference between this version and the later work, so that we can try to fix it.
Thank you very much for your contribution, appreciate it!
@ystyle Brilliant!
I have sync that version with yours at https://hub.docker.com/layers/zixia/wechat/2.7.1.85/images/sha256-e6e9d21c7cd1dfae0484e697f12f5f3c401de2f02e771d061868740e0d26549d?context=repo
这个版本完全打不开,Wechat.exe 占 100% 的 CPU。2.8.0.112 是可以打开的,只是有输入框的问题
@ystyle Brilliant! I have sync that version with yours at https://hub.docker.com/layers/zixia/wechat/2.7.1.85/images/sha256-e6e9d21c7cd1dfae0484e697f12f5f3c401de2f02e771d061868740e0d26549d?context=repo
这个版本完全打不开,Wechat.exe 占 100% 的 CPU。2.8.0.112 是可以打开的,只是有输入框的问题
你这是因为用了2.8的,导致本地数据库更新了,切回旧版本会出问题。你换个数据目录就好了
I uploaded it to
ystyle/wechat
tag: 2.7.1.85 https://hub.docker.com/r/ystyle/wechat
docker pull ystyle/wechat:2.7.1.85
我在这个版本下也输入框汉字是方框,感觉是不是镜像里面缺字体?
有什么好的解决办法吗。我已经盲打几个星期了。
@DogLooksGood 我这边也是,Arch Linux. 但是在另一个ubuntu上又没有这个问题。
@vc60er 等会,请问下,你是不是已经盲打了几个月了,还是解决了