Package Details: eww-x11 0.4.0-5

Git Clone URL: (read-only, click to copy)
Package Base: eww
Description: Standalone widget system made in Rust (X11 backend)
Upstream URL:
Licenses: MIT
Conflicts: eww
Provides: eww
Submitter: cog
Maintainer: eclairevoyant
Last Packager: eclairevoyant
Votes: 20
Popularity: 1.11
First Submitted: 2022-08-28 08:30 (UTC)
Last Updated: 2023-10-03 13:21 (UTC)

Required by (5)

Sources (1)

Pinned Comments

eclairevoyant commented on 2023-07-18 00:39 (UTC)

Make sure to fetch the signing keys from GitHub and import them before building:

curl -sS | gpg --import -i -
curl -sS | gpg --import -i -

Latest Comments

1 2 3 Next › Last »

umop3plsdn commented on 2023-11-03 03:33 (UTC)

not sure why i was having key errors trying to install this but have never had any other issues installing anything else but the pinned comment did work for me though. I would have never even seen this had I not came to the site and looked for the comments on the page

serxxx commented on 2023-10-31 16:27 (UTC)

The pinned imports do not fix the issue for me. gpg is throwing "no user ID" errors on the key.

gpg: key 4AEE18F83AFDEB23: no user ID
gpg: Total number processed: 1
 -> problem importing keys

This, after the imports, after pacman-key --refresh-keys.

MagnusVesper commented on 2023-10-16 21:37 (UTC)

For people getting a "failed to run gpg --recv-keys" error when updating, just run the 2 lines in the pinned comment. That fixed it for me.

grappas commented on 2023-10-06 19:58 (UTC)

It throws wrong gpg key. Cannot upgrade. Why though there's '' instead of ''?

gpg: error reading key: No public key
gpg: error reading key: No public key
gpg: error reading key: No public key

dbrl commented on 2023-10-05 13:06 (UTC)

i tried to install but it says that this key has expired: pub rsa3072 2021-05-03 [SC] [expired: 2023-05-03] B558974128820CB473BD9807E321AD71B1D1F27F uid [ expired] Leon Kowarschick

hcjl commented on 2023-10-03 13:58 (UTC)

@eclairevoyant Thanks a lot for the fix!

eclairevoyant commented on 2023-10-03 13:21 (UTC)

@GiftShower eww-git already includes wayland support.

Anyway, fixed.

hcjl commented on 2023-10-03 12:32 (UTC) (edited on 2023-10-03 12:32 (UTC) by hcjl)

Doing the changes GiftShower suggested and removing the --frozen option from cargo build let me build the package correctly. See the corresponding PKGBUILD below.

# Maintainer: éclairevoyant
# Contributor: Will Elliott <troutcobbler at gmail dot com>

pkgdesc="Standalone widget system made in Rust"
makedepends=(cargo-nightly git)
depends=(gtk3 gtk-layer-shell)
    'B558974128820CB473BD9807E321AD71B1D1F27F' # Leon Kowarschick <>
    '94E8F34BCE4F4BA8ED9B29BD50E76B4711E4C3E4' # Leon Kowarschick <>
    '5DE3E0509C47EA3CF04A42D34AEE18F83AFDEB23' # GitHub (web-flow commit signing) <>

prepare() {
    cd $pkgbase
    cargo update
    export RUSTUP_TOOLCHAIN=nightly

build() {
    cd $pkgbase

    export CARGO_TARGET_DIR=target_wayland
    cargo build --release --no-default-features --features=wayland

    export CARGO_TARGET_DIR=target_x11
    cargo build --release --no-default-features --features=x11

_pkg() {
    cd $pkgbase
    install -vDm644 LICENSE -t "$pkgdir/usr/share/licenses/$pkgname/"
    install -vd "$pkgdir/etc/xdg/$pkgbase/"
    cp -vr examples/eww-bar "$pkgdir/etc/xdg/$pkgbase/"

package_eww-wayland() {
    pkgdesc+=" (Wayland backend)"
    depends=(gtk3 gtk-layer-shell)
    install -vDm755 target_wayland/release/$pkgbase -t "$pkgdir/usr/bin/"

package_eww-x11() {
    pkgdesc+=" (X11 backend)"
    install -vDm755 target_x11/release/$pkgbase -t "$pkgdir/usr/bin/"

GiftShower commented on 2023-10-03 07:34 (UTC) (edited on 2023-10-03 10:58 (UTC) by GiftShower)

By adding this line of code at prepare() section of PKGBUILD:

export RUSTUP_TOOLCHAIN=nightly

and changing source to latest commit, package have been successfully built and installed. Looks like above code is required to use latest rust toolchain. Also, the source had to be updated to latest commit in order to solve this error:

error[E0557]: feature has been removed

Edit: Looks like what I did was same as eww-git, but instead building with wayland enabled. If it should be built on current commit in PKGBUILD, I think either package version needs to be specified or use latest rust toolchain and patch outdated code.

MaKaNu commented on 2023-10-02 20:04 (UTC) (edited on 2023-10-02 21:06 (UTC) by MaKaNu)

@ror5chach My last time building something with rust is some time ago and I am a bit rusty. I remember vaguely how the targeting works. How to determine the up-to-date Value?

Edit1: I looked into the variable $CARCH and it is saying x86_64 which looks kind of right for me. But please teach me wrong. Based on the PKGBUILD I think the variable is set in line 10.

Edit2: After looking through documentation of cargo fetch I removed the --target flag and tried without. Got me similar error than @Madeleaan, but for cfg-expr v0.15.5 asking for rustc 1.70.0. looked further into cargo.lock: I found cfg-expr aswell as toml_edit neither of them specifying the version of rustc necessary. Based on naive approach I think the rustc compiler itself know this dependecies?

Edit3: cloned the repo directly, builded twice. First time following build intruction from documentation, second building with --locked and --frozen as in PKGBUILD. Both worked. Package after paru -S eww-wayland -fm vim and deleting `--target "$CARCH-unknown-linux-gnu" not.