Arch Linux User Repository

Unfortunately, I cannot install “espanso-wayland” on my current CachyOS.

I get the following message.

warning: espanso-info@0.1.0: src/x11/native.cpp:21:10: fatal error: X11/Xlibint.h: No such file or directory
warning: espanso-info@0.1.0:    21 | #include <X11/Xlibint.h>
warning: espanso-info@0.1.0:       |          ^~~~~~~~~~~~~~~
warning: espanso-info@0.1.0: compilation terminated.
error: failed to run custom build command for `espanso-info v0.1.0 (/home/ckagerer/.cache/paru/clone/espanso/src/espanso-2.2.3/espanso-info)`

Does anyone have an idea how I can get it installed? libx11 is in the dependencies and also installed.

If you see the following error when trying to build espanso from the AUR:

error: failed to parse lock file at: .../Cargo.lock
Caused by: lock file version 4 was found, but this version of Cargo does not understand this lock file, perhaps Cargo needs to be updated?

It means your version of Rust and Cargo is too old to understand the lock file format used by espanso. To fix this, update Rust and Cargo to the latest stable version using rustup:

sudo pacman -S rustup
rustup update stable

After updating, try building espanso again. This should resolve the issue.

Alternatively, if you are building from source, you can delete the existing Cargo.lock file in the espanso source directory and let Cargo regenerate it:

rm path/to/espanso/Cargo.lock

Then rebuild the project.

Newer version was released. v2.2.3 is latest version.

@carsme Thanks for your continued work. I just switched back to this package from espanso-wayland-git, which is currently broken.

However, I ran into a different problem with this package. As I had previously, I'm seeing persistent artifacts on screen. I assume it's to do with what would otherwise be the rainbow-colored square that displays briefly when espanso starts up. This is what it looks like for me.

https://imgur.com/a/zA97u9f

I'm running into a problem on both my Intel (ThinkPad X1 Carbon) and AMD (Framework 13) machines. Both produce the below warnings during compilation, which would seem to be the cause of the behaviors I'm experiencing. espanso service register && espanso service start produces a generic gear logo icon in the dock (see screenshot), as well as a square (failed dialog rendering?) and pixel artifacts on screen (see screenshot)

https://paste.pics/e36f3f390735788f3f1fdc2657f202c7

https://paste.pics/5ca6f0e346329d533cd2b592bf2f35bc

Partial output of yay -S espanso-wayland:

   Compiling espanso v2.2.1 (/home/shawn/.cache/yay/espanso/src/espanso-2.2.1/espanso)
warning: field `show_in_dock` is never read
  --> espanso/src/cli/mod.rs:49:7
   |
42 | pub struct CliModule {
   |            --------- field in this struct
...
49 |   pub show_in_dock: bool,
   |       ^^^^^^^^^^^^
   |
   = note: `#[warn(dead_code)]` on by default

warning: method `get_default_config` is never used
  --> espanso/src/cli/worker/context/mod.rs:31:6
   |
30 | pub trait ConfigContext {
   |           ------------- method in this trait
31 |   fn get_default_config(&self) -> Arc<dyn Config>;
   |      ^^^^^^^^^^^^^^^^^^

warning: field `search_icon` is never read
  --> espanso/src/icon.rs:52:7
   |
50 | pub struct IconPaths {
   |            --------- field in this struct
51 |   pub form_icon: Option<PathBuf>,
52 |   pub search_icon: Option<PathBuf>,
   |       ^^^^^^^^^^^
   |
   = note: `IconPaths` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis

warning: `espanso` (bin "espanso") generated 3 warnings
    Finished `release` profile [optimized] target(s) in 2m 11s
warning: the following packages contain code that will be rejected by a future version of Rust: fs_extra v1.2.0, html5ever v0.25.1, xml5ever v0.16.1
note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1`

Can you replace the dependencies wxwidgets-common and wxwidgets-gtk3 with wxwidgets only?

This would allow to either select wxwidgets-gtk3 or wxwidgets-qt5 depending on which desktop environment is used.

I tested it locally with makepkg and it seems to work.

Edit: I just realized that I manually had to create a symlink from /usr/bin/wx-config to /usr/bin/wx-config-qt to make the build work. Not sure how to solve this :(

Edit2: I created a pull request to fix this: https://github.com/espanso/espanso/pull/1918

@psto the linked issue should now be resolved on dev.

@NathanU unfortunately I cannot reproduce this build failure, can you try building in a clean chroot?

espanso-wayland build fails:

error[E0658]: use of unstable library feature 'is_some_with'
   --> espanso-engine/src/process/middleware/disable.rs:131:6
    |
131 |     .is_some_and(|key| key == &event.key)
    |      ^^^^^^^^^^^
    |
    = note: see issue #93050 <https://github.com/rust-lang/rust/issues/93050> for more information

error[E0277]: can't compare `&Key` with `Key`
   --> espanso-engine/src/process/middleware/disable.rs:131:28
    |
131 |     .is_some_and(|key| key == &event.key)
    |                            ^^ no implementation for `&Key == Key`
    |
    = help: the trait `PartialEq<Key>` is not implemented for `&Key`
    = help: the trait `PartialEq` is implemented for `Key`
    = note: required for `&&Key` to implement `PartialEq<&Key>`

Some errors have detailed explanations: E0277, E0658.
For more information about an error, try `rustc --explain E0277`.
error: could not compile `espanso-engine` due to 2 previous errors
warning: build failed, waiting for other jobs to finish...
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: espanso-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
espanso-wayland - exit status 4

EDIT: I just needed to update rust and the build was successful.

NOTICE: The standalone espanso-wayland package has been merged into this pkgbase, which now builds two distinct packages:

• espanso-x11: Espanso built for X11, replaces the former espanso package.
• espanso-wayland: Espanso built for Wayland, identical to the former standalone espanso-wayland package.

This change simplifies maintenance and ensures the packages are kept in sync. It does however incur slightly longer build times, as Espanso is compiled twice during the build process.

Your AUR helper will hopefully handle the upgrade/migration automatically.

Let me know if you encounter any issues.