> Perhaps the Launcher is not installed? #1555

[mav3ri3k]

          > Perhaps the Launcher is not installed? #1555

You are correct my friend... But now I am unable to install the launcher

error: failed to run custom build command for `smithay-client-toolkit v0.16.0 (https://github.com/Smithay/client-toolkit?rev=3776d4a#3776d4ae)`

Caused by:
  process didn't exit successfully: `/home/khushal/Downloads/launcher/target/release/build/smithay-client-toolkit-e14bbbc6212b3d3c/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=XKBCOMMON_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=XKBCOMMON_STATIC
  cargo:rerun-if-env-changed=XKBCOMMON_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
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: "`\"pkg-config\" \"--libs\" \"--cflags\" \"xkbcommon\"` did not exit successfully: exit status: 1\nerror: could not find system library 'xkbcommon' required by the 'smithay-client-toolkit' crate\n\n--- stderr\nPackage xkbcommon was not found in the pkg-config search path.\nPerhaps you should add the directory containing `xkbcommon.pc'\nto the PKG_CONFIG_PATH environment variable\nPackage 'xkbcommon', required by 'virtual:world', not found\n"', /root/.cargo/git/checkouts/client-toolkit-e56a3844de110279/3776d4a/build.rs:5:49
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: Recipe `build-debug` failed on line 40 with exit code 101

this is the result of command just build-release

Originally posted by @khushal-soni in https://github.com/pop-os/launcher/issues/171#issuecomment-1428394453

[mav3ri3k]

I am getting the same error on my system, however I have xkbcommon installed on my system. [apurva@apurva-fedora launcher]$ sudo dnf install libxkbcommon [sudo] password for apurva: Last metadata expiration check: 1:18:13 ago on Tue 02 May 2023 02:55:14 PM IST. Package libxkbcommon-1.5.0-2.fc38.x86_64 is already installed. Dependencies resolved. Nothing to do. Complete!

[mmstick]

You have to install the development packages for those build dependencies. libxkbcommon-dev and libegl-dev as seen in the debian/control file.

[mav3ri3k]

Fixed now and the launcher is working. I did not realise that libxkbcommon has several different packages and did not have -dev version installed. Can you please tell me what you meant by debian/control file, all I could figure out from the error was that xkbcommon was missing.

[mmstick]

This file lists build and runtime package dependencies for debian packaging tools