[Bug]: My JASP homepage's screen keeps flashing between the homepage and the datacell page. I cannot click on the hamburger icon or any other icon whilst it does this.

[TheMegaPEKKA]

JASP Version

0.19.3

Commit ID

No response

JASP Module

Other

What analysis are you seeing the problem on?

None in particular- trying to do an ANCOVA + ANOVA but unable to even reach the page where I can open the files

What OS are you seeing the problem on?

ChromeOS

Bug Description

Whenever I load JASP on my (up to date) chromebook, the JASP home screen is unusable. It remains stuck there, flashing between the homepage and the data cells repeatedly and violently. I cannot click any of the options, so accessing the safe graphics setting is out of the question, and nothing I have tried (including deleting + reinstalling JASP, ensuring my chromebook is up to date, etc) seems to fix it. I can't paste the video here but just imagine the screen flashing multiple times a second between the home + datacell page, whilst I am unable to click any of the icons across the top.

Expected Behaviour

Well, I should just be able to actually use JASP

Steps to Reproduce

I'm not sure what this means, its pre-existing every time i open JASP

Log (if any)

No response

More Debug Information

No response

Final Checklist

• I have included a screenshot showcasing the issue, if possible.
• I have included a JASP file (zipped) or data file that causes the crash/bug, if applicable.
• I have accurately described the bug, and steps to reproduce it.

[github-actions]

@TheMegaPEKKA, thanks for taking the time to create this issue. If possible (and applicable), please upload to the issue website (#3429, attaching to an email does not work) a screenshot showcasing the problem, and/or a compressed (zipped) .jasp file or the data file that causes the issue. If you would prefer not to make your data publicly available, you can send your file(s) directly to us, [email protected]

[tomtomme]

@TheMegaPEKKA
thx for the report. We had some similar in the past months, see https://github.com/jasp-stats/jasp-issues/issues?q=is%3Aissue%20label%3A%22OS%3A%20ChromeOS%22%20(flash%20OR%20glitch%20OR%20shaky)%20

Can you try in a terminal / command line window: sudo apt-get update && sudo apt-get dist-upgrade
and then reboot?
another user at #3204 reported this as a fix

If this does not help, please report back. Not everybody had success with this.
You can also start jasp from the linux terminal by running
flatpak run org.jaspstats.JASP or
flatpak run org.jaspstats.JASP --safeGraphics

and then paste the output log here. It might tell us more of what is going on.

[TheMegaPEKKA]

Hello Tom, I tried the 3 commands provided, first attempting the update + dist-upgrade commands, before closing and restarting JASP, and the problem persisted. I then tried to start JASP using the command provided, wherein the output log is attached (the highlighted text in screenshot #2 is where screenshot #1 left off)

…

On Mon, 5 May 2025 at 21:40, Thomas Langkamp ***@***.***> wrote: *tomtomme* left a comment (jasp-stats/jasp-issues#3429) <#3429 (comment)> @TheMegaPEKKA <https://github.com/TheMegaPEKKA> thx for the report. We had some similar in the past months, see https://github.com/jasp-stats/jasp-issues/issues?q=is%3Aissue%20label%3A%22OS%3A%20ChromeOS%22%20(flash%20OR%20glitch%20OR%20shaky)%20 Can you try in a terminal / command line window: sudo apt-get update && sudo apt-get dist-upgrade and then reboot? another user at #3204 <#3204> reported this as a fix If this does not help, please report back. Not everybody had success with this. You can also start jasp from the linux terminal by running flatpak run org.jaspstats.JASP or flatpak run org.jaspstats.JASP --safeGraphics and then paste the output log here. It might tell us more of what is going on. — Reply to this email directly, view it on GitHub <#3429 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BSFI5ZWTO7IMME3WIHECBD3247EE7AVCNFSM6AAAAAB4PDEAWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJSGI4DCOBSHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[tomtomme]

@TheMegaPEKKA
thx for the info. However if you attach the screenshots via mail, they do not come through. Please drag and drop them directly here on github

[TheMegaPEKKA]

I believe these are the two correct images

[TheMegaPEKKA]

My apologies, this is the first one- ignore the fact I posted two of the same haha

[JorisGoosen]

@TheMegaPEKKA somethings you could try is:

Run in the terminal: export QT_QPA_PLATFORM=xcb
then start jasp from there again as flatpak run org.jaspstats.JASP

Does this work better?

If not please paste the output here, but next time, instead of two or three screenshots it is a bit more pleasant for me to read if you select the actual contents of the terminal window and paste that here instead.

The practical upside for you is that that will be easier to do through an email to github ;)

[shun2wang]

Also you can try

flatpak run --nosocket=fallback-x11 --socket=x11 --nosocket=wayland org.jaspstats.JASP

see if it help.

[TheMegaPEKKA]

This command works! I can't run JASP automatically thru my chromebook, but as long as I access it thru the terminal it seems to fix itself. Thank you so much, ur a lifesaver

[shun2wang]

This command works! I can't run JASP automatically thru my chromebook, but as long as I access it thru the terminal it seems to fix itself. Thank you so much, ur a lifesaver

Great! Then you can run bellow only once to let flatpak settings works for the App, and then can start from icons:

flatpak override --user --nosocket=fallback-x11 --socket=x11 --nosocket=wayland org.jaspstats.JASP

[tomtomme]

Can we make this default for chromeOS installs?

[shun2wang]

Can we make this default for chromeOS installs?

I think just update the guidance on the website.