Arch Linux User Repository

Thank you for clarifying @dbermond

Fyi, setting PKG_CONFIG_PATH before installing (i'm using the FISH shell) fixed it for me, apparently pkg-config can't find the dbus library in the search path during the build...? Note that i have no clue what i'm doing:

set --export PKG_CONFIG_PATH "/usr/lib/pkgconfig:/usr/share/pkgconfig:$PKG_CONFIG_PATH"

@Obradinn I've just checked, and the package is building perfectly fine. You are not using Arch Linux, and this is not supported. Please seek help in your distribution support channels.

Hi there, fyi;

:: Resolving dependencies...
:: Calculating conflicts...
:: Calculating inner conflicts...

Aur (1)      Old Version  New Version    Make Only
aur/kdotool               0.2.3-1        No

:: Proceed to review? [Y/n]: y

:: Downloading PKGBUILDs...
 PKGBUILDs up to date
 nothing new to review
fetching devel info...
==> Making package: kdotool 0.2.3-1 (zo 10 mei 2026 07:21:43 CEST)

#...removed some lines...#

  Compiling phf_generator v0.13.1
error: failed to run custom build command for `libdbus-sys v0.2.7`

Caused by:
  process didn't exit successfully: `/home/obradinn/.cache/paru/clone/kdotool/src/target/release/build/libdbus-sys-bd989026b4c47bb1/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=build.rs
  cargo:rerun-if-changed=build_vendored.rs
  cargo:rerun-if-env-changed=DBUS_1_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=DBUS_1_STATIC
  cargo:rerun-if-env-changed=DBUS_1_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR

  --- stderr
  pkg_config failed: 
  pkg-config exited with status code 1
  > PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --libs --cflags dbus-1 'dbus-1 >= 1.6'

  The system library `dbus-1` required by crate `libdbus-sys` was not found.
  The file `dbus-1.pc` needs to be installed and the PKG_CONFIG_PATH environment variable must contain its parent directory.
  The PKG_CONFIG_PATH environment variable is not set.

  HINT: if you have installed the library, try setting PKG_CONFIG_PATH to the directory containing `dbus-1.pc`.

  One possible solution is to check whether packages
  'libdbus-1-dev' and 'pkg-config' are installed:
  On Ubuntu:
  sudo apt install libdbus-1-dev pkg-config
  On Fedora:
  sudo dnf install dbus-devel pkgconf-pkg-config


  thread 'main' (24969) panicked at /home/obradinn/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/libdbus-sys-0.2.7/build.rs:25:9:
  explicit panic
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'kdotool-0.2.3-1': 
error: packages failed to build: kdotool-0.2.3-1

EndeavourOS, Linux 7.0.3-arch1-2 KDE Plasma 6.6.4

@VorpalWay fixed.

This fails to build with rustc/cargo 1.92.0:

error: this function depends on never type fallback being `()`
   --> src/main.rs:390:1
    |
390 | fn main() -> anyhow::Result<()> {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions!
    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/never-type-fallback.html>
    = help: specify the types explicitly
note: in edition 2024, the requirement `!: ReadAll` will fail
   --> src/main.rs:466:20
    |
466 |         kwin_proxy.method_call("org.kde.kwin.Scripting", "unloadScript", (context.name,))?;
    |                    ^^^^^^^^^^^
    = note: `#[deny(dependency_on_unit_never_type_fallback)]` (part of `#[deny(rust_2024_compatibility)]`) on by default
help: use `()` annotations to avoid fallback changes
    |
466 ~         kwin_proxy.method_call::<(), _, _, _>("org.kde.kwin.Scripting", "unloadScript", (context.name,))?;
467 |         return Ok(());
...
518 |     // setup message receiver
519 ~     let _receiver_thread = std::thread::spawn::<_, ()>(move || {
520 |         let _receiver = receiver_conn.start_receive(
...
539 |     let start_time = chrono::Local::now();
540 ~     script_proxy.method_call::<(), _, _, _>("org.kde.kwin.Script", "run", ())?;
541 |     if context.shortcut.is_empty() {
542 ~         script_proxy.method_call::<(), _, _, _>("org.kde.kwin.Script", "stop", ())?;

Most recent upstream git revision builds though, so maybe it would be relatively easy to backport. (While I do know rust very well, it is late here, and I'm not going to make a patch in the next couple of days.)