Package Details: wayfire 0.10.1-2

Git Clone URL: https://aur.archlinux.org/wayfire.git (read-only, click to copy)
Package Base: wayfire
Description: 3D wayland compositor
Upstream URL: https://wayfire.org
Keywords: compositor wayland
Licenses: MIT
Submitter: aperez
Maintainer: aperez
Last Packager: aperez
Votes: 65
Popularity: 0.52
First Submitted: 2019-02-14 08:43 (UTC)
Last Updated: 2025-12-16 00:01 (UTC)

Latest Comments

1 2 3 4 5 6 .. 11 Next › Last »

aperez commented on 2025-12-15 23:36 (UTC)

@dinkonin: the arch-meson script uses --buildtype plain, which in turn will pick the compiler options defined in /etc/makepkg.conf... I would expect that to work well (and it does here for me), because I do not see anything in the Meson build files included with Wayfire that would change drastically depending on the --buildtype value 🤔

octoamit commented on 2025-12-08 19:08 (UTC) (edited on 2025-12-09 20:38 (UTC) by octoamit)

Edit: Reinstalling wf-config (and opting for a clean build) fixed this issue for me. More details here: https://github.com/WayfireWM/wayfire/issues/2921

The build process fails with fatal error:

In file included from ../wayfire-0.10.1/src/core/output-layout.cpp:11:
../wayfire-0.10.1/src/core/../output/output-impl.hpp:11:10: fatal error: wayfire/nonstd/safe-list.hpp: No such file or directory
   11 | #include <wayfire/nonstd/safe-list.hpp>

dinkonin commented on 2025-09-08 16:45 (UTC) (edited on 2025-09-08 16:45 (UTC) by dinkonin)

I'm experiencing some high CPU usage in wayfire. Shouldn't this package be built with

-Dbuildtype=release build

as per Tips&Tricks page

kode54 commented on 2025-09-07 05:16 (UTC)

@devlvender The PKG_CONFIG_PATH is a leftover setting from two whole releases of wlroots ago, and should be removed.

devlavender commented on 2025-09-05 14:40 (UTC)

The depends array mentions wlroots0.19 as dependency. However, the build function explicitly uses PKG_CONFIG_PATH=/usr/lib/wlroots0.17/pkgconfig in the command.

What is actually expected to be my wlroots version?

kode54 commented on 2025-05-25 08:25 (UTC)

Just recompile and reinstall, and move on. The libxml2-legacy package is supposed to be for binary packages which you cannot recompile.

trames commented on 2025-05-23 15:09 (UTC) (edited on 2025-05-23 15:13 (UTC) by trames)

For libxml2 error, I installed the libxml2-legacy package and rebooted. Wayfire would then start.

Arzumify commented on 2025-05-07 23:15 (UTC)

Needs to be recompiled for new libxml2 Works if you simply symlink the new libxml to the library wayfire doesn't have, guessing it's not terribly XML reliant This is a hack though and certainly not ideal

je-vv commented on 2024-08-28 00:49 (UTC)

Well, to me the behavior I'm experiencing is new. This is my set of plugins (hide-cursor not enabled):

plugins = \
  session-lock \
  alpha \
  animate \
  autostart \
  command \
  decoration \
  fast-switcher \
  foreign-toplevel \
  gtk-shell \
  idle \
  move \
  oswitch \
  place \
  resize \
  shortcuts-inhibit \
  switcher \
  vswitch \
  wayfire-shell \
  window-rules \
  wm-actions \
  workspace-names

I have pending to remove the ones that are sort of bloat to me, but I need to investigate further. I only need transparency and opacity, plus closing/minimizing/starting applications animations. I do like the gtk-shell, if what it does is good integration for gtk applications, including CSDs. But I need to get rid of some of those. But except for session-lock, all the rest were there before 0.9.0. Perhaps it's the new way and I need to get used to it. But I feel like I really have to click several times to get the cursor back. Just moving the mouse for example doesn't bring it back, I really need to click on different places to get it back...

Greetings !

1 2 3 4 5 6 .. 11 Next › Last »