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

Launching Insomnia Core with Ozone/Wayland causes a SIGSEGV #4131

Closed
1 task done
nermolov opened this issue Oct 19, 2021 · 3 comments · Fixed by #4708
Closed
1 task done

Launching Insomnia Core with Ozone/Wayland causes a SIGSEGV #4131

nermolov opened this issue Oct 19, 2021 · 3 comments · Fixed by #4708
Labels
B-bug Bug: general classification S-unverified Status: Unverified by maintainer

Comments

@nermolov
Copy link

nermolov commented Oct 19, 2021

Is there an existing issue for this?

  • I have searched the issue tracker for a bug that matches the one I want to file, without success.

Insomnia Version

2021.5.3

What operating system are you using?

Other Linux

Operating System Version

Fedora 35

Installation method

AppImage

Last Known Working Insomnia version

No response

Expected Behavior

Launching Insomnia with Ozone/Wayland enabled launches the application and it functions.

Actual Behavior

Launching Insomnia with Ozone/Wayland enabled opens the main window, then crashes with the following log:

./Insomnia.Core-2021.5.3.AppImage --enable-features=UseOzonePlatform --ozone-platform=wayland
14:26:23.339 › Running version 2021.5.3
14:26:23.359 › [electron client protocol] FAILED to set default protocol 'insomnia://'
14:26:23.374 › [electron client protocol] the current executable is not the default protocol for 'insomnia://'
14:26:23.486 › [electron client protocol] the default application set for 'insomnia://' was not found
14:26:23.673 › [fix] Running database repairs
14:26:23.730 › [db] Initialized DB at /home/nik/.config/Insomnia/insomnia.$TYPE.db
14:26:23.730 › [db] Init responses DB
14:26:23.732 › [localstorage] Initialized at /home/nik/.config/Insomnia/localStorage
14:26:23.871 › [main] Loading file:///tmp/.mount_InsomnaBrDek/resources/app.asar/renderer.html
14:26:23.886 › [ga] Non-interactive General, Updated, 2021.5.3
14:26:23.902 › [ga] Queued event [
  { name: 't', value: 'event' },
  { name: 'ec', value: 'General' },
  { name: 'ea', value: 'Updated' },
  { name: 'ni', value: '1' },
  { name: 'el', value: '2021.5.3' }
]
fish: Job 1, './Insomnia.Core-2021.5.3.AppIma…' terminated by signal SIGSEGV (Address boundary error)

Reproduction Steps

  1. Launch Insomnia with the following flags: --enable-features=UseOzonePlatform --ozone-platform=wayland

Additional Information

I'm running on a HiDPI display, so using XWayland as a rendering backend makes the UI really blurry, hence the draw towards using Wayland rendering. This works under other Electron applications I've used (Discord, Slack, Signal).

@nermolov nermolov added B-bug Bug: general classification S-unverified Status: Unverified by maintainer labels Oct 19, 2021
@frysztak
Copy link

frysztak commented Nov 3, 2021

Native Wayland support came with Electron 12, Insomnia is currently at Electron 11. Related PR: #4160

@filfreire
Copy link
Member

Hi folks! Sorry for long wait, and thank you for reporting this issue!

We upgraded Insomnia to Electron 17 on version 2022.2.0.

Recently we merged @matthew-jones-uk's PR that has a particular fix for this issue by upgrading to electron 17.3.1.

It should be included tomorrow in our upcoming beta release (2022.3.0-beta.4). Let us know if you still have issues with that release once it's out.

cc @nermolov @frysztak @matthew-jones-uk

@leonardehrenfried
Copy link

I've tried out this feature just now and now see Insomnia in all its HPDI glory - thanks!

However, the window doesn't have any window borders and I cannot move it.

I'm starting Insomnia like this:

 /opt/Insomnia/insomnia --enable-features=UseOzonePlatform --ozone-platform=wayland

Am I missing a flag? Is anyone else experiencing this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B-bug Bug: general classification S-unverified Status: Unverified by maintainer
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants