Package Details: wayfire 0.8.1-4

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: 57
Popularity: 2.20
First Submitted: 2019-02-14 08:43 (UTC)
Last Updated: 2024-04-08 07:15 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

szbergeron commented on 2022-03-11 17:53 (UTC)

I originally flagged this as out of date for not building with the current stable wlroots from extra. This could be solved by using -Duse_system_wlroots=false, but that isn't a great solution long term since then it conflicts with sway. I think the maintainer is currently busy with other work so there may not be an upstream resolution for some time

DN-debug commented on 2022-03-11 03:24 (UTC)

Hi,

I would repeat the last person's question -- why is this flagged out? The upstream version is matching with the aur pkg version. @aperez could you please check?

Many thanks!

ThePirate42 commented on 2022-03-05 14:54 (UTC)

Why is this package marked as outdated?

name commented on 2022-01-07 22:33 (UTC)

@aperez @IrvineHimself I still think polkit should be added to the dependencies or at least mentioned in the description, It's quite an annoying error you face when you don't have it installed and it does not point to polkit whatsoever.

IrvineHimself commented on 2021-12-06 17:27 (UTC) (edited on 2021-12-06 17:33 (UTC) by IrvineHimself)

@hynopanda: If you click on the doctest link, (above,) you will see that the only available package is in the Community-Testing repo, which you would need to enable. However, from the Wiki:

Warning:

Be careful when enabling the testing repositories. Your system may break after performing an update. Only experienced users who know how to deal with potential system breakage should use it. If you enable testing, you must also enable community-testing. If you enable any other testing repository listed in the following subsections, you must also enable both testing and community-testing.

See Here

There is not an AUR PKGBUILD, but you could download this one from the Community-Testing branch and downgrade it, (or not,) to the last known good package. :)

Irvine

zuki18 commented on 2021-12-06 16:26 (UTC)

for some reason i can't install "doctest" [zooki@zooki-arch-D ~]$ paru -S wayfire :: Resolving dependencies... :: There are 2 providers available for wayfire: :: Repository AUR: 1) wayfire 2) wayfire-git Enter a number (default=1): 1 error: could not find all required packages: doctest (wanted by: wayfire) [zooki@zooki-arch-D ~]$

IrvineHimself commented on 2021-10-25 06:37 (UTC) (edited on 2021-10-25 07:17 (UTC) by IrvineHimself)

@archorz: I do not disagree with what you are saying. Like most people, I already had polkit installed, so, (for me,) it wasn't a problem.

However, for reference only, I feel I should point out that it is not as simple as just making polkit a dependency. To get it to work you need to install a polkit authentication agent and add it to autostart in wayfire.ini

You should note:

  • Wayfire doesn't have it's own authentication-agent
  • The agent used by a DE, for example, gnome, is not the same as the authentication-agent required by Wayfire. In my example, this would be polkit-gnome. Which would be started with a1 = /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 in the autostart section of wayfire.ini.
  • Edit: You should also note that on all the wlroots compositors I have tested it on, whether they list is as an opt depend or not, most packages with elevated privileges will additionally require xorg-xhost for polkit to work.

Irvine

archorz commented on 2021-10-18 21:51 (UTC)

Like sway, on Arch wayfire requires polkit to run with default configuration.

kode54 commented on 2021-09-08 03:38 (UTC)

Might it be a good idea for the PKGBUILD to sed replace some paths in the shipped default config file that goes in docs? For instance, changing /usr/libexec/xdg-desktop-portal in the autostarts to /usr/lib/xdg-desktop-portal so that people like me don't get stupidly confused why it won't start it until I actually dig up where that command lives. It might have prevented me from stupidly adding the old hack for loading systemd's user environment into the process, thinking that was why it wasn't working. The current version already does that, I think.