Skip to content

/ org.chromium.Chromium

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

Jump to bottom

Not opening in a native Wayland window #26

Closed
TheEvilSkeleton opened this issue Nov 20, 2020 · 2 comments
Closed

Not opening in a native Wayland window #26

TheEvilSkeleton opened this issue Nov 20, 2020 · 2 comments

Comments

@TheEvilSkeleton
Copy link

@TheEvilSkeleton TheEvilSkeleton commented Nov 20, 2020

Wayland is enabled since 818d57b. I'm using stock permissions of the flatpak (only with X11 disabled), but it doesn't seem to be working:

    ~ 
flatpak override --user --show org.chromium.Chromium
[Context]
sockets=!x11
    ~ 
flatpak run org.chromium.Chromium
[2:2:1120/084729.791197:ERROR:browser_main_loop.cc(1434)] Unable to open X display.
@GeorgesStavracas
Copy link
Collaborator

@GeorgesStavracas GeorgesStavracas commented Nov 20, 2020

You need to pass --enable-features=UseOzonePlatform --ozone-platform=wayland. This is a conscious decision made by upstream, because not everything is implemented on Wayland yet. I don't think this is an issue.
@TheEvilSkeleton
Copy link
Author

@TheEvilSkeleton TheEvilSkeleton commented Nov 20, 2020

I see, thank you. It worked.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@GeorgesStavracas @TheEvilSkeleton