Fails to open on Ubuntu 22.04 with Wayland

[eikooc]

Search first

• I searched and no similar issues were found

What Happened?

After downloading either the AppImage or the Zip file and trying to run the program it errors with this message:

(rsapi) init loggers
[979315:0710/130647.350381:ERROR:ozone_platform_x11.cc(247)] Missing X server or $DISPLAY
[979315:0710/130647.350402:ERROR:env.cc(226)] The platform failed to initialize.  Exiting.
The futex facility returned an unexpected error code.
fish: Job 1, './Logseq' terminated by signal SIGABRT (Abort)

Reproduce the Bug

1. Download release
2. make executable with chmod u+x ./Logseq
3. Try to run with ./Logseq
4. Experience error

Expected Behavior

That the application opens

Screenshots

No response

Desktop or Mobile Platform Information

Desktop Linux Ubuntu 22.04

Additional Context

Tried with both 0.9.10 and 0.9.9

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)

[sprocketc]

@eikooc Hello! What's the output of set | grep DISPLAY ?

[eikooc]

Hello @sprocketc. Here's the output:

DISPLAY :0
GNOME_SETUP_DISPLAY :1
WAYLAND_DISPLAY wayland-0

[sprocketc]

Does executing ./Logseq --enable-features=UseOzonePlatform --ozone-platform=wayland work?

[eikooc]

@sprocketc it sure does. Thanks for the assistance, is this documented anywhere? If so I have totally overlooked it

[sprocketc]

@eikooc You are right, this isn't documented yet. I looked into it and we might be able to help Wayland users by adding --ozone-platform-hint=auto to our desktop file electron/electron#34937.

[github-actions]

Hi There! 👋

We haven't seen any activity on this issue in a while 😴, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!

If the issue has been resolved or is no longer relevant, that's great news! 🎉
We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.

Access additional Logseq 🚀 resources:

• Forum: https://discuss.logseq.com
• Blog: https://blog.logseq.com
• Docs: https://docs.logseq.com

Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!