Package Details: xidlehook 0.10.0-1

Git Clone URL: https://aur.archlinux.org/xidlehook.git (read-only, click to copy)
Package Base: xidlehook
Description: xautolock rewrite in Rust, with a few extra features
Upstream URL: https://gitlab.com/jD91mZM2/xidlehook
Keywords: activity lock screen xautolock
Licenses: MIT
Submitter: jD91mZM2
Maintainer: lxmnk
Last Packager: lxmnk
Votes: 32
Popularity: 0.82
First Submitted: 2018-02-02 14:49 (UTC)
Last Updated: 2021-03-05 09:07 (UTC)

Latest Comments

1 2 Next › Last »

stef204 commented on 2022-05-12 20:08 (UTC) (edited on 2022-05-13 01:01 (UTC) by stef204)

Just looked at it again: it's i3lock which needed libasan.so.6 and then produced this error: i3lock: error while loading shared libraries: libasan.so.6: cannot open shared object file: No such file or directory, not xidlehook. My bad! I use xidlehook in combination with i3lock and needed to recompile i3lock-git. Problem fixed.

desbma commented on 2022-05-12 18:24 (UTC)

@stef204 this package builds and runs fine even after the gcc-libs update. Neither xidlehook or xidlehook-client depends on libasan.so. Maybe you are building with an outdated toolchain?

stef204 commented on 2022-05-11 21:33 (UTC) (edited on 2022-05-13 01:02 (UTC) by stef204)

Has anyone taken over maintenance of this project upstream?
At the moment, this compiles but fails at runtime due to the update to gcc-libs. It needs libasan.so.6 when we are now officially at libasan.so.8. Symlinking libasan.so.6 to 8 works but that's an ugly hack and who knows how long this will hold.

skug commented on 2020-11-29 10:29 (UTC)

@heyarne, you need to have the same rust toolchain version active via rustup as is provided by the rust package, at the time of writing this is 1.48.0. The Archlinux rust package seems to be following the stable version of rust.

lxmnk commented on 2020-08-07 19:58 (UTC)

@heyarne, I can confirm that build fails via rustup. But via rust (package from official repositories) build passes successfully. Unfortunately, I don't know how to build xidlehook with your rustup.

heyarne commented on 2020-08-06 14:01 (UTC)

I'm trying to build the most recent version of xidlehook (0.9.1-1) from the AUR. I'm using the latest rust nightly via rustup (rustc 1.47.0-nightly (f9d422ea7 2020-08-04) -- not sure if the global rustc gets used when compiling though). The build fails with the following message:

…
   Compiling xidlehook-core v0.2.0 (/home/arne/.cache/yay/xidlehook/src/xidlehook-0.9.1/xidlehook-core)
error: attributes are not yet allowed on `if` expressions
   --> xidlehook-core/src/lib.rs:474:21
    |
474 |                     #[cfg(feature = "tokio")]
    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^

error: attributes are not yet allowed on `if` expressions
   --> xidlehook-core/src/lib.rs:484:21
    |
484 |                     #[cfg(feature = "tokio")]
    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to 2 previous errors

error: could not compile `xidlehook-core`.
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERROR: A failure occurred in build().
    Aborting...
error making: %!s(func() string=0x563fe520aa60)

It seems like the rust version used is not up to date. Is the one I configure in rustup even relevant in the build process or can I make it be?

lxmnk commented on 2020-05-19 12:50 (UTC)

Done. Thank you, @mipi.

mipi commented on 2020-05-19 09:43 (UTC)

Hi lxmnk, I successfully built and ran xidlehook on Aarch4 (on a RPi4 with aarch64 kernel). Could you therefore list aarch64 as supported architecture in the PKGBUILD? Thanks, mipi

etrigan63 commented on 2020-03-15 23:35 (UTC) (edited on 2020-03-15 23:38 (UTC) by etrigan63)

There appears to be some sort of protocol issue with crates.io. I am getting th following errors during my attempts to update:

warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of broadcaster v1.0.0 failed to transfer more than 10 bytes in 30s)

warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for async-task v1.3.1 within 30s)

warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of crossbeam-deque v0.7.3 failed to transfer more than 10 bytes in 30s)

warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for crossbeam-channel v0.4.2 within 30s)

warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of futures-io v0.3.4 failed to transfer more than 10 bytes in 30s)

warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for crossbeam-utils v0.7.2 within 30s)

warning: spurious network error (1 tries remaining): [28] Timeout was reached (failed to download any data for crossbeam-utils v0.7.2 within 30s)

warning: spurious network error (1 tries remaining): [28] Timeout was reached (download of futures-io v0.3.4 failed to transfer more than 10 bytes in 30s)

warning: spurious network error (1 tries remaining): [28] Timeout was reached (failed to download any data for crossbeam-channel v0.4.2 within 30s)

warning: spurious network error (1 tries remaining): [28] Timeout was reached (download of async-task v1.3.1 failed to transfer more than 10 bytes in 30s)

warning: spurious network error (1 tries remaining): [28] Timeout was reached (failed to download any data for broadcaster v1.0.0 within 30s)

warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of once_cell v1.3.1 failed to transfer more than 10 bytes in 30s)

warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for num_cpus v1.12.0 within 30s)

error: failed to download from https://crates.io/api/v1/crates/crossbeam-channel/0.4.2/download

Caused by: [1] Unsupported protocol (Received HTTP/0.9 when not allowed ) ==> ERROR: A failure occurred in build(). Aborting... Error making: xidlehook

jhenson commented on 2019-12-07 22:27 (UTC) (edited on 2019-12-07 22:27 (UTC) by jhenson)

Please add 'python' to the makedepends array. The rust dependency xcb needs it to build properly in a clean chroot.

error: failed to run custom build command for `xcb v0.9.0`

Caused by:
  process didn't exit successfully: `/build/xidlehook/src/xidlehook-0.8.1/target/release/build/xcb-ee122d4813a798c7/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'Unable to find build dependency python3: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/libcore/result.rs:1165:5 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.