Hey there,
I have a few students who are using Jamovi on a pc and they have an error that is something about a server error. When they open up jamovi the only thing there is a blank screen. They are using 2.7.17, the current version. Any ideas on what is going on?
PC users having a blank screen
Re: PC users having a blank screen
Hi,
when jamovi first starts up, it launches a python server process in the background. something on these PCs would seem to be interfering with that start-up process. it's possible that they have some anti-virus products that are interfering, or there may be something unusual about the way their systems load DLLs.
in this case, the easiest way forward is for them to use the cloud version instead:
https://cloud.jamovi.org
cheers
when jamovi first starts up, it launches a python server process in the background. something on these PCs would seem to be interfering with that start-up process. it's possible that they have some anti-virus products that are interfering, or there may be something unusual about the way their systems load DLLs.
in this case, the easiest way forward is for them to use the cloud version instead:
https://cloud.jamovi.org
cheers
Re: PC users having a blank screen
I may have a student with the same issue on Windows. When she installs and starts, she is greeted with this:
We have tried many things but cannot make any progress in *starting* jamovi. Is this the situation you were talking about, Jonathon?
I asked her to pause the antivirus software to see what happens; she does not have any.
Any tips?
P.
We have tried many things but cannot make any progress in *starting* jamovi. Is this the situation you were talking about, Jonathon?
I asked her to pause the antivirus software to see what happens; she does not have any.
Any tips?
P.
Re: PC users having a blank screen
hi pete,
i think this is a different one ... it starts up, but it's only the displaying of data that seems to be a problem
they could try starting jamovi at the terminal (jamovi debug should be available from the start menu), and provide any error messages that appear. alternatively, they could try the 28 series, and failing that, the cloud.
jonathon
i think this is a different one ... it starts up, but it's only the displaying of data that seems to be a problem
they could try starting jamovi at the terminal (jamovi debug should be available from the start menu), and provide any error messages that appear. alternatively, they could try the 28 series, and failing that, the cloud.
jonathon
Re: PC users having a blank screen
I'm getting a completely bank screen on my work laptop. I first installed using jamovi-2.7.38.0-win-x64.msix, then tried running jamovi-2.7.38.0-win-x64.exe as Administrator.
I got the startup splash and then nothing, just a white screen with jamovi in the task bar. Windows 11 Enterprise.
Edit -- a reboot did solve it, so perhaps it was due to something I'd done earlier in the day.
I got the startup splash and then nothing, just a white screen with jamovi in the task bar. Windows 11 Enterprise.
Edit -- a reboot did solve it, so perhaps it was due to something I'd done earlier in the day.
Re: PC users having a blank screen
always glad to know you still exist wake!
jonathon
jonathon
Re: PC users having a blank screen
Hello,
We are currently running jamovi in a university environment, using version 2.6.4. We are also planning to test version 2.7.38 to check whether the issue persists.
We are experiencing problems on some of the computers in our computer labs. Approximately 25% of the computers experience problems when launching the application.
Our environment is as follows:
Windows 11 25H2.
Computers managed through Microsoft Intune.
Computers joined to the university domain.
All computers have identical hardware.
All computers use the same Windows image and configuration.
All computers have the same version of jamovi installed.
The problem occurs when jamovi is launched. In some cases, the application does not finish starting and remains stuck displaying only a blank/white screen.
The behaviour is particularly interesting because, although approximately 25% of the computers experience the problem, it is not always the same computers. When we repeat the test, some computers that worked previously may experience the problem, while others that failed previously may start correctly. Nevertheless, the overall failure rate remains approximately 25%.
We would like to know whether this behaviour is known and whether it could be related to the environment in which we are running jamovi.
In particular, we would like to ask:
Is this a known issue with jamovi on Windows 11 25H2?
Are there any known compatibility issues or limitations when running jamovi in an environment managed through Microsoft Intune?
Are there any specific requirements regarding permissions, Windows policies, graphics configuration, or other system components that could cause jamovi to remain on a blank screen during startup?
Is there any specific configuration or recommended deployment method for running jamovi in university computer labs with centrally managed computers?
Is there any logging or diagnostic mechanism that we can enable or check to determine why the application does not finish starting?
Could there be an issue related to concurrency, application initialization, or a shared system resource that would explain why the problem appears to occur apparently at random?
This issue is particularly concerning because it occurs on computers that are, in principle, identical in terms of hardware, system image, and configuration, and because it affects approximately 25% of the launch attempts.
We would appreciate any information or recommendations you can provide to help us diagnose and resolve this issue.
Thank you very much for your help.
Best regards,
We are currently running jamovi in a university environment, using version 2.6.4. We are also planning to test version 2.7.38 to check whether the issue persists.
We are experiencing problems on some of the computers in our computer labs. Approximately 25% of the computers experience problems when launching the application.
Our environment is as follows:
Windows 11 25H2.
Computers managed through Microsoft Intune.
Computers joined to the university domain.
All computers have identical hardware.
All computers use the same Windows image and configuration.
All computers have the same version of jamovi installed.
The problem occurs when jamovi is launched. In some cases, the application does not finish starting and remains stuck displaying only a blank/white screen.
The behaviour is particularly interesting because, although approximately 25% of the computers experience the problem, it is not always the same computers. When we repeat the test, some computers that worked previously may experience the problem, while others that failed previously may start correctly. Nevertheless, the overall failure rate remains approximately 25%.
We would like to know whether this behaviour is known and whether it could be related to the environment in which we are running jamovi.
In particular, we would like to ask:
Is this a known issue with jamovi on Windows 11 25H2?
Are there any known compatibility issues or limitations when running jamovi in an environment managed through Microsoft Intune?
Are there any specific requirements regarding permissions, Windows policies, graphics configuration, or other system components that could cause jamovi to remain on a blank screen during startup?
Is there any specific configuration or recommended deployment method for running jamovi in university computer labs with centrally managed computers?
Is there any logging or diagnostic mechanism that we can enable or check to determine why the application does not finish starting?
Could there be an issue related to concurrency, application initialization, or a shared system resource that would explain why the problem appears to occur apparently at random?
This issue is particularly concerning because it occurs on computers that are, in principle, identical in terms of hardware, system image, and configuration, and because it affects approximately 25% of the launch attempts.
We would appreciate any information or recommendations you can provide to help us diagnose and resolve this issue.
Thank you very much for your help.
Best regards,