[Bug]: JASP not clickabel on ChromeOS

[ics50]

JASP Version

0.19.3

Commit ID

No response

JASP Module

Other

What analysis are you seeing the problem on?

No response

What OS are you seeing the problem on?

Linux

Bug Description

I have downloaded JASP on my Chromebook via Linux. I can open the application, but onceit is opened I cannot select any buttons or click on anything. Sometimes the screen even glitches (the words on the screen glitch specifically, and I still cannot select anything). I cannot use JASP right now, and would like help on how to resolve the bug.

Expected Behaviour

I would like to be able to use JASP without any issues, so without any screen glitches.

Steps to Reproduce

No

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]

@ics50, thanks for taking the time to create this issue. If possible (and applicable), please upload to the issue website (#3162, 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]

@ics50
thx for the report. Can you provide the following info?

sidenote:
this seems to be a duplicate of #3118

[ics50]

@tomtomme Thank you for the reply! Unfortunately I cannot click on anything, including the sidebar. I can only click on the button that closes the application, to which JASP does ask if I want to save my files.

[tomtomme]

@ics50
understood.

Since this is the second bug report about this problem on ChromeOS, we should really try to fix it. It would be very helpful if you could provide log-files, so that we can diagnose the problem better.

How to get log files:

Linux / Chromebook

On Linux one should open a terminal and run jasp as flatpak run org.jaspstats.JASP --logToFile.

You will also see some lines of output there in the terminal, these might be useful to a developer in case JASP doesn't even reach a state in which it can start logging.

Presumably you still do not see a JASP window opening now, so you'll have to navigate manually to the logfiles.

The logfiles can then be found under ~/.var/app/org.jaspstats.JASP/data/JASP/JASP/Logs.

[ics50]

@tomtomme I have run flatpak run org.jaspstats.JASP --logToFile in Linux. Do I have to copy and paste the output here? I'm sorry, I do not fully understand what I should do now

[tomtomme]

Yes, copy pasting the output of what is shown in the terminal would be a great start!!

And then - in addition - you could look for the files located here
~/.var/app/org.jaspstats.JASP/data/JASP/JASP/Logs.

But this folder is probably hidden. Any chromebook expert here? @shun2wang or @RensDofferhoff maybe?

[ics50]

@tomtomme This is the output from Linux after I ran the code you gave me:

: QML cache directory: /home/username/.var/app/org.jaspstats.JASP/cache/JASP/JASP/qmlcache_c8710df5442149527b0692cc1367ea5b3c982d04
Making new argument list for Application startup: JASP --logToFile
Starting JASP 0.19.3 from commit c8710df5442149527b0692cc1367ea5b3c982d04 and branch HEAD
QtWebEngineQuick initialized
Application initialized
Application init entered
MainWindow constructor started
TempFiles::createSessionDir(): '/home/username/.JASP/temp/3' about to be (removed and re)created.
Going to construct the necessary models for JASP to function.
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-de.qm
Desktop: Language (German) not registered in LanguageModel, adding it now
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-eo.qm
Desktop: Invalid translation file found with name: jaspDesktop-eo.qm
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-es.qm
Desktop: Language (Spanish) not registered in LanguageModel, adding it now
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-fr.qm
Desktop: Language (French) not registered in LanguageModel, adding it now
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-gl.qm
Desktop: Language (Galician) not registered in LanguageModel, adding it now
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-id.qm
Desktop: Language (Indonesian) not registered in LanguageModel, adding it now
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-it.qm
Desktop: Language (Italian) not registered in LanguageModel, adding it now
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-ja.qm
Desktop: Language (Japanese) not registered in LanguageModel, adding it now
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-nl.qm
Desktop: Language (Dutch) not registered in LanguageModel, adding it now
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-pl.qm
Desktop: Language (Polish) not registered in LanguageModel, adding it now
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-pt.qm
Desktop: Language (Portuguese) not registered in LanguageModel, adding it now
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-pt_BR.qm
Desktop: Invalid translation file found with name: jaspDesktop-pt_BR.qm
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-ru.qm
Desktop: Language (Russian) not registered in LanguageModel, adding it now
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-tr.qm
Desktop: Invalid translation file found with name: jaspDesktop-tr.qm
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-zh_Hans.qm
Desktop: Language (Chinese) not registered in LanguageModel, adding it now
Desktop: Checking qm file: /app/Resources/Translations/jaspDesktop-zh_Hant.qm
Desktop: Language (Chinese) not registered in LanguageModel, adding it now
Desktop: Opened internal sqlite database for creation at '/home/junaxpumpkin/.JASP/temp/3/internal.sqlite'.
Desktop: DataSet::DataSet(index=-1)
Desktop: DataSetPackage::reset()
Desktop: DataSet::DataSet(index=-1)
Desktop: DataSetPackage::endLoadingData
Entering eventloop
Error in loadNamespace(x) : there is no package called ‘jaspBase’
Error in loadNamespace(x) : there is no package called ‘jaspBase’
qt.qpa.wayland: Ignoring unexpected wl_surface.enter received for output with id: 7 screen name: "Screen5" screen model: "unknown" This is most likely a bug in the compositor.
[57:16:0128/165017.373657:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
qt.qpa.wayland: Ignoring unexpected wl_surface.enter received for output with id: 7 screen name: "Screen5" screen model: "unknown" This is most likely a bug in the compositor.
QProcess: Destroyed while process ("/app/bin/JASPEngine") is still running.
Failed to write to the pipe: Bad file descriptor.

[boutinb]

If I google the this error "This is most likely a bug in the compositor.", I get this https://avidemux.org/smif/index.php?topic=20527.0.
Can you start JASP with the platform argument JASP -platform xcb ?
I'm not sure if the xcb platform is delivered with JASP on linux, but if it is, it is worth trying it.