Office365 - Segmentation error about jak

[codesardine]

I can't replicate this, What branch are you on?

[ilteoood]

I've installed everything from Pacman

[codesardine]

I mean are you on Stable, Testing or Unstable?

[codesardine]

Seems there are some missing dependency's, that should not cause a core dump. Remove and reinstall the package including python-jade-application-kit,
Delete the contents on /home/username/.jak make sure you have pyqt5 and python-pyqtwebengine installed, let me know if that works for you.

[ilteoood]

The problem persist.
This time I've tried to clean everything, installing the dependencies from the requirements file and the setup from the master branch.

[codesardine]

Did you try with pyside2 bindings?

export JAK_PREFERRED_BINDING=PySide2

[ilteoood]

Yes, this is the output:

[teo@teo-pc ~]$ export JAK_PREFERRED_BINDING=PySide2
[teo@teo-pc ~]$ jak-cli --url https://www.office.com/launch/word?auth=2 --title Word
JAK v2.1.3
PySide2 Bindings, JAK_PREFERRED_BINDING environment variable not set.
Production Mode On, use (--dev) for debugging
NVIDIA detected:Known bug - kernel rejected pushbuf
Falling back to Software Rendering
Engine interprocess communication (IPC) up and running:
Use of deprecated not thread-safe setter, use setUrlRequestInterceptor instead.
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/5.14.0 Chrome/77.0.3865.129 Safari/537.36
Loading URL:https://www.office.com/launch/word?auth=2
Registering ['view'] Instance
Registering and Retrieving ['win'] Instance
Segmentation error (core dump created)

[codesardine]

You have deleted the cache? on
/home/username/.jak

[ilteoood]

Yes, before the new installation from master branch

[teo@teo-pc ~]$ ~
bash: /home/teo: Is a directory
[teo@teo-pc ~]$ ls -la | grep '.jak'
[teo@teo-pc ~]$ 

[codesardine]

I going to need some help debugging this since I can't reproduce on my end, could you install gdb

pacman -S gdb

run gdb

gdb

Then type

(gdb) file python
(gdb) run /usr/bin/ms-office-online

And paste the output here, Thanks

[ilteoood]

I did a clean installation of manjaro and I can't recreate this problem.
Thank you for your time.