Package Details: walker 2.5.2-1

Git Clone URL: https://aur.archlinux.org/walker.git (read-only, click to copy)
Package Base: walker
Description: wayland application runner
Upstream URL: https://github.com/abenz1267/walker
Licenses: GPL
Conflicts: walker
Provides: walker
Submitter: benz
Maintainer: benz
Last Packager: benz
Votes: 14
Popularity: 2.10
First Submitted: 2024-03-12 14:36 (UTC)
Last Updated: 2025-10-18 09:35 (UTC)

Latest Comments

1 2 Next › Last »

benz commented on 2025-09-06 08:05 (UTC)

@max.bra i agree, will fix!

max.bra commented on 2025-09-06 07:55 (UTC)

Sorry, I didn't choose the best words. It's obvious that this is an unhandled exception at runtime. And yes, it was a problem with the configuration file, which has been slightly changed in the keybinding declaration in recent versions. But do you think it's appropriate to exit the runtime with such force just because a key name is incorrectly declared? (close = "esc" ==> close = "Escape"). If you're unable to continue anyway, it would be more appropriate to catch the exception, at least log the reason to the terminal, and then exit politely. My 2 cents.

I'm about to erase the unnecessary noise.

benz commented on 2025-09-05 20:07 (UTC)

@max.bra that's not a crash with the build but a runtime crash. Caused by an invalid keybind in your config.

zcdziura commented on 2025-08-28 19:57 (UTC)

Attempting to build walker results in the following error:

error: failed to run custom build command for `walker v1.0.0-beta-15 (/redacted/walker/src/walker-1.0.0-beta-15)`

Caused by:
  process didn't exit successfully: `/redacted/walker/src/walker-1.0.0-beta-15/target/release/build/walker-5f62b3d2ac6b749c/build-script-build` (exit status: 1)
  --- stderr
  /usr/bin/protoc: error while loading shared libraries: libabsl_log_initialize.so.2508.0.0: cannot open shared object file: No such file or directory
  codegen failed: parse and typecheck

  Caused by:
      0: using protoc parser
      1: protoc command "/usr/bin/protoc" "-Isrc/protos" "--descriptor_set_out=/tmp/protobuf-parset4tOPU/descriptor.pbbin" "--include_imports" "src/protos/query.proto" "src/protos/activate.proto" "src/protos/subscribe.proto" exited with non-zero code
warning: build failed, waiting for other jobs to finish...
==> ERROR: A failure occurred in build().
    Aborting...

s5e commented on 2025-08-25 12:48 (UTC)

Surely there's some way to make AUR dependencies work, if not via depends.

I tested it with paru -B and it worked.

benz commented on 2025-08-24 06:55 (UTC)

@markstos you can't add AUR dependencies into depends.

markstos commented on 2025-08-24 01:52 (UTC)

Panics and crashes on launch. It appears there is a missing dependency on elephant:

➤ walker

thread 'main' panicked at src/theme/mod.rs:83:10:
couldn't run 'elephant'. Make sure it is installed.: Os { code: 2, kind: NotFound, message: "No such file or directory" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'main' panicked at library/core/src/panicking.rs:225:5:
panic in a function that cannot unwind
stack backtrace:
   0:     0x55b0e727c252 - <unknown>
   1:     0x55b0e72a2893 - <unknown>
   2:     0x55b0e7279733 - <unknown>
   3:     0x55b0e727c0a2 - <unknown>
   4:     0x55b0e727d316 - <unknown>
   5:     0x55b0e727d119 - <unknown>
   6:     0x55b0e727dca2 - <unknown>
   7:     0x55b0e727da26 - <unknown>
   8:     0x55b0e727c759 - <unknown>
   9:     0x55b0e727d6ed - <unknown>
  10:     0x55b0e70eba6d - <unknown>
  11:     0x55b0e70ebb02 - <unknown>
  12:     0x55b0e70ebbc5 - <unknown>
  13:     0x55b0e71196ec - <unknown>
  14:     0x7f6a9c30783a - g_closure_invoke
  15:     0x7f6a9c32646b - <unknown>
  16:     0x7f6a9c3284cf - <unknown>
  17:     0x7f6a9c328749 - g_signal_emit_valist
  18:     0x7f6a9c328804 - g_signal_emit
  19:     0x7f6a9bf6bbb3 - g_application_register
  20:     0x7f6a9bf6c123 - <unknown>
  21:     0x7f6a9bf6c4b5 - g_application_run
  22:     0x55b0e714a4da - <unknown>
  23:     0x55b0e711ea95 - <unknown>
  24:     0x55b0e7134583 - <unknown>
  25:     0x55b0e7151c69 - <unknown>
  26:     0x55b0e7274150 - <unknown>
  27:     0x55b0e711eb05 - <unknown>
  28:     0x7f6a9b027675 - <unknown>
  29:     0x7f6a9b027729 - __libc_start_main
  30:     0x55b0e70ec235 - <unknown>
  31:                0x0 - <unknown>
thread caused non-unwinding panic. aborting.
fish: Job 1, 'walker' terminated by signal SIGABRT (Abort)

nezu commented on 2025-07-28 20:23 (UTC) (edited on 2025-07-30 22:55 (UTC) by nezu)

PKGBUILD claims arch=('any') but .SRCINFO claims arch = x86_64. Some tools get confused by this. You can generate an up-to-date .SRCINFO using makepkg --printsrcinfo. Furthermore, from the wiki: arch=(any) indicates the package can be built on any architecture, and once built, is architecture-independent in its compiled state (usually shell scripts, fonts, themes, many types of extensions, Java programs, etc.).. So any does not fit here, please specify supported architectures explicitly since packages built with any shouldn't contain architecture-specific code.

Edit: Thank you

benz commented on 2024-12-04 04:29 (UTC)

@8ightbits slightly confused, as in: i don't have it installed on my system and so far no one else has had this issue (at least reported). I added it to the makedepends array.