8000 Hangs on openSUSE Tumbleweed · Issue #27 · huan/docker-wechat · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Hangs on openSUSE Tumbleweed #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
8000
leodream opened this issue Mar 2, 2020 · 4 comments
Closed

Hangs on openSUSE Tumbleweed #27

leodream opened this issue Mar 2, 2020 · 4 comments
Labels
question Further information is requested

Comments

@leodream
Copy link
leodream commented Mar 2, 2020

Ran the following commands on openSUSE Tumbleweed and got the wechat window.

xhost +
curl -sL https://raw.githubusercontent.com/huan/docker-wechat/master/dochat.sh | DOCHAT_DEBUG=true  bash

image

But after clicking the button, the window disappeared and the container hanged after logging the following messages.

0043:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
[0302/071923:INFO:exception_record.cc(518)] [QB]Process ID: 49 Type: 1
[0302/071923:ERROR:network_change_notifier_win.cc(156)] WSALookupServiceBegin failed with: 8

Re-runing the command generates the same messages and the window does not show up anymore.

@leodream leodream changed the title Hangs on openSUSE Tumble\weed Hangs on openSUSE Tumbleweed Mar 2, 2020
@jackielii
Copy link
Contributor

@leodream @gaoyanami
This happens on my machine too. Attempted to fix it with:

docker build -t wechat - <<EOF
from zixia/wechat
run apt-get -y remove winbind && apt-get -y install winbind
EOF

now it fails with:

[0302/112933:INFO:exception_record.cc(518)] [QB]Process ID: 49 Type: 1
[0302/112933:ERROR:network_change_notifier_win.cc(156)] WSALookupServiceBegin failed with: 8

my system:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.4 LTS
Release:        18.04
Codename:       bionic

@huan huan added the question Further information is requested label Mar 2, 2020
@huan
Copy link
Owner
huan commented Mar 2, 2020

You can use the 100% scale DPI (96) to start your DoChat and see if there are any other messages by using this command:

curl -sL https://raw.githubusercontent.com/huan/docker-wechat/master/dochat.sh | DOCHAT_DEBUG=true  DOCHAT_DPI=96 bash

DOCHAT_DPI=96 was set in the above command

@jackielii
Copy link
Contributor

same error, here is the full log:

curl -sL https://raw.githubusercontent.com/huan/docker-wechat/master/dochat.sh | DOCHAT_DEBUG=true  DOCHAT_DPI=96 bash


       ____         ____ _           _
      |  _ \  ___  / ___| |__   __ _| |_
      | | | |/ _ \| |   | '_ \ / _` | __|
      | |_| | (_) | |___| | | | (_| | |_
      |____/ \___/ \____|_| |_|\__,_|\__|

      https://github.com/huan/docker-wechat

                +--------------+
               /|             /|
              / |            / |
             *--+-----------*  |
             |  |           |  |
             |  |   盒装    |  |
             |  |   微信    |  |
             |  +-----------+--+
             | /            | /
             |/             |/
             *--------------*

      DoChat /dɑɑˈtʃæt/ (Docker-weChat) is:

      📦 a Docker image
      🤐 for running PC Windows WeChat
      💻 on your Linux desktop
      💖 by one-line of command

🚀 Pulling the latest docker image...

Using default tag: latest
latest: Pulling from zixia/wechat
Digest: sha256:686ddc1d8df276e69b66fed28f09e9b4f01d7874e3fdcf171e504fb2e134e429
Status: Image is up to date for zixia/wechat:latest
docker.io/zixia/wechat:latest

🚀 Pulling the latest docker image done.
🚀 Starting DoChat /dɑɑˈtʃæt/ ...

+ main
++ id -u
+ '[' 0 -ne 0 ']'
+ setupUserGroup
+ '[' -n 29 ']'
+ groupmod -o -g 29 audio
+ '[' -n 44 ']'
+ groupmod -o -g 44 video
++ id -g user
+ '[' 1000 '!=' 1000 ']'
++ id -u user
+ '[' 1000 '!=' 1000 ']'
+ chown user:group '/home/user/.wine/drive_c/users/user/Application Data' '/home/user/WeChat Files'
+ setupHostname
+ export HOSTNAME=DoChat
+ HOSTNAME=DoChat
+ echo DoChat
+ hostname DoChat
+ exec gosu user /entrypoint.sh
+ main
++ id -u
+ '[' 1000 -ne 0 ']'
+ startWechat
+ hello
++ cat /VERSION
[DoChat] 盒装微信 v0.7.0
+ VERSION=0.7.0
+ echo '[DoChat] 盒装微信 v0.7.0'
+ disableUpgrade
+ wine REG ADD 'HKEY_CURRENT_USER\Software\Tencent\WeChat' /v NeedUpdateType /t REG_DWORD /d 0 /f
+ CONFIG_EX_INI_FILE='/home/user/.wine/drive_c/users/user/Application Data/Tencent/WeChat/All Users/config/configEx.ini'
+ '[' -e '/home/user/.wine/drive_c/users/user/Application Data/Tencent/WeChat/All Users/config/configEx.ini' ']'
+ setupFontDpi
+ DELETE_KEYS=('HKEY_CURRENT_USER\Control Panel\Desktop' 'HKEY_CURRENT_USER\Software\Wine\Fonts')
+ for key in "${DELETE_KEYS[@]}"
+ wine reg DELETE 'HKEY_CURRENT_USER\Control Panel\Desktop' /v LogPixels /f
+ true
+ for key in "${DELETE_KEYS[@]}"
+ wine reg DELETE 'HKEY_CURRENT_USER\Software\Wine\Fonts' /v LogPixels /f
+ wine reg ADD 'HKEY_LOCAL_MACHINE\System\CurrentControlSet\Hardware Profiles\Current\Software\Fonts' /v LogPixels /t REG_DWORD /d 96 /f
+ '[' -n true ']'
+ unset WINEDEBUG
+ wine reg query 'HKEY_CURRENT_USER\Software\Tencent\WeChat'

HKEY_CURRENT_USER\Software\Tencent\WeChat
    NeedUpdateType    REG_DWORD    0x0

[DoChat] DISPLAY=:0.0
[DoChat] Starting...
+ echo '[DoChat] DISPLAY=:0.0'
+ true
+ echo '[DoChat] Starting...'
+ '[' -n true ']'
+ wine 'C:\Program Files\Tencent\WeChat\WeChat.exe'
003f:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
[0302/145214:INFO:exception_record.cc(518)] [QB]Process ID: 49 Type: 1
[0302/145214:ERROR:network_change_notifier_win.cc(156)] WSALookupServiceBegin failed with: 8

@leodream
Copy link
Author

Tried on a different computer and followed #150, the issue had gone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants
0