Skip to content
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

impossible to start nvda_snapshot_threshold_py3_staging-17851,779ca15b.exe #9831

Closed
fernando-jose-silva opened this issue Jun 27, 2019 · 16 comments
Assignees
Milestone

Comments

@fernando-jose-silva
Copy link

Steps to reproduce:

I would like to apologize if the call does not apply.
I am not a programmer, I work with computers and I am interested in testing the software.
I saw that on the nvda snapshot page there was a new branch
threshold_py3_staging
and wanted to test.
I downloaded the file and tried to run, but I get an error.
only one error sound is played, nor is a message displayed.
below is the error log.
this verdict of nvda does not start.

Actual behavior:

pressing enter on the installation file causes an error sound to sound and not a message appears on the screen.
The temporary copy of nvda does not start and can not be installed or run as a temporary copy.

Expected behavior:

nvda is installed and can be tested.

System configuration

NVDA installed/portable/running from source:

installation file
nvda_snapshot_threshold_py3_staging-17851,779ca15b.exe

NVDA version:

installation file
nvda_snapshot_threshold_py3_staging-17851,779ca15b.exe

Windows version:

10 17763.557

Name and version of other software in use when reproducing the issue:

Other information about your system:

Other questions

Does the issue still occur after restarting your PC?

yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

no
log:
nvda.log

@LeonarddeR
Copy link
Collaborator

@josephsl: Would you be able to have a look?

@josephsl
Copy link
Collaborator

josephsl commented Jun 27, 2019 via email

@josephsl
Copy link
Collaborator

josephsl commented Jun 27, 2019 via email

@LeonarddeR
Copy link
Collaborator

LeonarddeR commented Jun 27, 2019 via email

@josephsl
Copy link
Collaborator

josephsl commented Jun 27, 2019 via email

@LeonarddeR
Copy link
Collaborator

web searches indicate that Python 3 (at least the one that ships with staging branch) insists on looking at somewhere when loading DLL’s.

Could you please provide the source of this information?

@LeonarddeR
Copy link
Collaborator

Looks like this needs a hook in py2exe. I will write a patch for it. cc @albertosottile

@josephsl
Copy link
Collaborator

josephsl commented Jun 27, 2019 via email

@nishimotz
Copy link
Contributor

I think AppVeyor VM is adding the location of _ssl.pyd to the PATH, so the CI doesn't fail.
The following batch file works for me.
Python 3.7.3 (32bit) should be installed.

set PATH=C:\Users\nishimotz\AppData\Local\Programs\Python\Python37-32\DLLs;%PATH%
nvda.exe

@albertosottile
Copy link

If the problem is just _ssl.pyd you can add _ssl in your 'includes' dictionary.

@LeonarddeR
Copy link
Collaborator

@albertosottile The problem is actually that _ssl relies on extra dll's that aren't copied by py2exe.

@Brian1Gaff
Copy link

Brian1Gaff commented Jun 27, 2019 via email

@dpy013
Copy link
Contributor

dpy013 commented Jun 28, 2019

I used nvda_snapshot_threshold_py3_staging-17866 in the Simplified Chinese windows10-1903, the same problem occurred during the 0b9f3ef.exe test.
thank

@LeonarddeR
Copy link
Collaborator

This can be fixed when py2exe/py2exe#12 and py2exe/py2exe#13 are merged, in which case we can update our py2exe binary copy.

@Adriani90
Copy link
Collaborator

@LeonarddeR I guess this issue can also be closed now. Right?

@LeonarddeR
Copy link
Collaborator

LeonarddeR commented Jul 3, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants