Skip to content

[Bug]: Segfault when calling screen.getCursorScreenPoint() under Wayland #35471

@weedz

Description

@weedz

Preflight Checklist

Electron Version

v20.0.3 and v22.0.0-nightly.20220824

What operating system are you using?

Other Linux, and Sway WM (1.7)

Operating System Version

ArchLinux, kernel 5.19.3

What arch are you using?

x64

Last Known Working Electron version

No response

Expected Behavior

Should provide a Point to the cursor position and not segfault.

Actual Behavior

Get a segmentation fault when calling screen.getCursorScreenPoint(); under Wayland (sway 1.7).

Testcase Gist URL

https://gist.github.com/weedz/b8002775cd1a23c46d38b5f10de957e4

Additional Information

Works fine under Xwayland. But will crash when launched with --ozone-platform-hint=wayland.

Tested every version down to electron@16 (with --enable-features=UseOzonePlatform --ozone-platform=wayland:

  • Electron@16: "interface 'wl_output' has no event 4" and no window or other errors.
  • Electron v17-v22.0.0-nightly.20220824: "electron exited with signal SIGSEGV"

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions