# Support Wayland

**URL:** <https://tagspaces.discourse.group/t/support-wayland/80>\
**Category:** Feature requests\
**Created:** [February 9, 2023, 11:11pm UTC](https://tagspaces.discourse.group/t/support-wayland/80 "2023-02-09T23:11:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rokejulianlockhart](https://yyz2.discourse-cdn.com/free1/user_avatar/tagspaces.discourse.group/rokejulianlockhart/32/20_2.png) [@rokejulianlockhart](https://tagspaces.discourse.group/u/rokejulianlockhart)\
**Post date:** [February 9, 2023, 11:11pm UTC](https://tagspaces.discourse.group/t/support-wayland/80/1 "2023-02-09T23:11:13Z")

</div>

XWayland isn’t an adequate shim for most.

---

<div class="post-metadata">

**Author:** ![ilian](https://yyz2.discourse-cdn.com/free1/user_avatar/tagspaces.discourse.group/ilian/32/6_2.png) [@ilian](https://tagspaces.discourse.group/u/ilian)\
**Post date:** [February 10, 2023, 7:19am UTC](https://tagspaces.discourse.group/t/support-wayland/80/2 "2023-02-10T07:19:01Z")

</div>

TagSpaces relays completely on Electron project for the desktop app, so if they support Wayland, TagSpaces will also support it.

---

<div class="post-metadata">

**Author:** ![rokejulianlockhart](https://yyz2.discourse-cdn.com/free1/user_avatar/tagspaces.discourse.group/rokejulianlockhart/32/20_2.png) [@rokejulianlockhart](https://tagspaces.discourse.group/u/rokejulianlockhart)\
**Post date:** [February 16, 2023, 3:06pm UTC](https://tagspaces.discourse.group/t/support-wayland/80/3 "2023-02-16T15:06:40Z")

</div>

@ilian, does TagSpaces activate the functionality, though? Per [http://reddit.com/r/linux/comments/lw7cvk](http://reddit.com/r/linux/comments/lw7cvk), `electron --enable-features=UseOzonePlatform --ozone-platform=wayland` is necessary to use the included Wayland support.

Invoking [https://github.com/tagspaces/tagspaces/releases/download/v5.2.5/tagspaces-linux-x86\_64-5.2.5.AppImage](https://github.com/tagspaces/tagspaces/releases/download/v5.2.5/tagspaces-linux-x86_64-5.2.5.AppImage) merely provides

 ![this,](https://global.discourse-cdn.com/free1/uploads/tagspaces/original/1X/99ef15e90768867d5835a4ee4750298e14bdc7a4.png) which appears to demonstrate that it isn’t even using XWayland, but rather X, since it doesn’t even attempt to scale at 200% like I have configured my window manager and compositor (KWin) to specify.

---

<div class="post-metadata">

**Author:** ![ilian](https://yyz2.discourse-cdn.com/free1/user_avatar/tagspaces.discourse.group/ilian/32/6_2.png) [@ilian](https://tagspaces.discourse.group/u/ilian)\
**Post date:** [February 16, 2023, 9:38pm UTC](https://tagspaces.discourse.group/t/support-wayland/80/4 "2023-02-16T21:38:39Z")

</div>

So what is your expectation, should we add the command line parameter to electron ? Or prefer to set them manually?

---

<div class="post-metadata">

**Author:** ![rokejulianlockhart](https://yyz2.discourse-cdn.com/free1/user_avatar/tagspaces.discourse.group/rokejulianlockhart/32/20_2.png) [@rokejulianlockhart](https://tagspaces.discourse.group/u/rokejulianlockhart)\
**Post date:** [February 16, 2023, 10:46pm UTC](https://tagspaces.discourse.group/t/support-wayland/80/5 "2023-02-16T22:46:13Z")

</div>

@ilian, what do you mean by set manually?

My suggestion is that you detect the compositor being used (X or Wayland) with the environment variable `$XDG_SESSION_TYPE` and, if Wayland, use the relevant flags when launching TagSpaces.

 ![image](https://global.discourse-cdn.com/free1/uploads/tagspaces/original/1X/0fd9aaf77be521dfdc81bfdb6d716bb7498555af.jpeg)