-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Failure to save file in the default path will affect your experience on Wechat. Try other path. #22
Comments
I am not sure why wechat has a problem here. Two notes:
|
See following:
How exactly should I use this option?
Just for debug purpose and convenience. |
Just rather share other folders. |
Based on my tries, only using the --share folder located directly under the $HOME won't trigger the problem, i.e., as below:
I really can't figure out the reason. It maybe a bug of x11docker. |
I have tried some of your suggested failing setups. I cannot reproduce the issue here. |
I don't have this folder at all:
|
Ok, than it is |
|
If you ran the image with option |
Maybe we are discussing different problems. Could you please give the concrete example using the arguments combinations? Let us focus on each specific issue for discussion corresponding to all the situations I described above and take it one step at a time. |
My idea is that wechat might have stored a bad configuration. |
It seems the problem is not that simple. I've already deleted all the possible configuration folders before the testings:
|
Can you give me an example how I could reproduce the issue? |
Could you please first build the deepin and deepin-wine images with the same Dockerfiles used by me with the following commands:
Then do the tests I mentioned above. |
Sorry, I won't build them. I have very low internet speed and the build would take at least about 12 hours. I want to use the internet for other tasks meanwhile. Running with your first example but my wechat image and a similar shared folder does not trigger the issue:
Tests with |
Today, we all in the 21st century, and I am very surprised that Germany, as a world-famous developed country, should have mature internet technology infrastructure deployed everywhere in the country. How can you have such a low-speed Internet connection? BTW, what's internet bandwidth promised by ISP for you? Anyway, I'll try to build the exactly same docker image as yours to further pinpoint and check the problem. |
Yes, it's a shame. Major cities normally have a good high-speed internet, but in rural areas there is often close to no internet at all. Some still use 56K-Modems, others can be happy to receive an UMTS signal.
I am living about 3 miles away from a small city in a forest. I have a DSL connection that serves about 50 kilobyte per second, sometimes less. I am happy to get this at all. I am paying for more than this, but the ISP directly said it will be much less and asked me if I really want this. I've tried LTE, too, but depending on the weather conditions the connection broke entirely. |
I created the exactly same docker image as you mentioned here with the following method:
Then I perform the following 4 tests in sequence respectively:
Once the deepin desktop has been started successfully, I then run the following command under the deepin-terminal to start WeChat for checking whether the problem reported here will be triggered:
Between each of the above two tests, I run the following commands to clear the possible configuration cache:
Below is the results obtained based on the above testings. Here , Yes/No means the problem will/won't be triggered.
To summarize: only using the --share folder located directly under the $HOME won't trigger the problem, i.e., as below:
Regards, |
Thank you for the detailed analysis! Now I can reproduce the issue. I've yet created On host, It seems wechat tries to access Well, I could have detected this with your earlier informations, too. But I did not thought of the possibility that the folder name itself makes a difference. I am not sure how to handle this in future. Although Another solution for the special wechat case could be to provide a However, if a |
As a rule of thumb, it's sensible and reasonable to only use the English ((path|file) name | input method), and so on, for code debugging and bug analysis.
Do you mean the German names used by your previous tests? |
Yes. |
I'd say this ticket can finally be closed. |
Based on my tries, this problem doesn't appear for the wechat running on deepin apricot. |
I start the self-build docker image deepin-wine as shown below:
$ x11docker --share ~/Documents/x11docker --sudouser -c --desktop --init=systemd -- --cap-add=ALL --security-opt seccomp=unconfined -- hongyi-zhao/deepin-wine startdde
This will cause the following problem, which won't appear if I use the --share option like this: "--share ~/x11docker", when starting wechat:
Failure to save file in the default path will affect your experience on Wechat. Try other path.
See the screenshot for more detailed info:
Any hints for this problem?
Regards,
HY
The text was updated successfully, but these errors were encountered: