search

yazgoo / umberwm

:ram: a minimalistic X window manager based on tinywm, inspired by qtile.
57 stars 3 forks source link

umbrewm v0.0.34 installed successfully, but failed to launch on Alpine Linux (v3.16) #54

Closed cryptixd closed 2 years ago

cryptixd commented 2 years ago

Installed umbrewm successfully on Alpine Linux 3.16 using cargo 1.60.0 as seen from output below...

$ cargo install umberwm

    Updating crates.io index
  Installing umberwm v0.0.34
   Compiling proc-macro2 v1.0.43
   Compiling unicode-ident v1.0.3
   Compiling quote v1.0.21
   Compiling syn v1.0.99
   Compiling libc v0.2.127
   Compiling ident_case v1.0.1
   Compiling fnv v1.0.7
   Compiling strsim v0.10.0
   Compiling serde_derive v1.0.142
   Compiling pkg-config v0.3.25
   Compiling serde v1.0.142
   Compiling log v0.4.17
   Compiling anyhow v1.0.59
   Compiling cfg-if v1.0.0
   Compiling xmodmap-pke-umberwm v0.0.1
   Compiling bitflags v1.3.2
   Compiling base64 v0.13.0
   Compiling x11 v2.19.1
   Compiling dirs-sys v0.3.7
   Compiling xcb v0.9.0
   Compiling dirs v3.0.2
   Compiling darling_core v0.13.4
   Compiling thiserror-impl v1.0.32
   Compiling darling_macro v0.13.4
   Compiling thiserror v1.0.32
   Compiling darling v0.13.4
   Compiling ron v0.6.6
   Compiling serde_with_macros v1.5.2
   Compiling serde_with v1.14.0
   Compiling umberwm v0.0.34
    Finished release [optimized] target(s) in 4m 14s
  Installing /home/teqnaz/.cargo/bin/umberwm
   Installed package `umberwm v0.0.34` (executable `umberwm`)

Full Rust Backtrace shown below... $ RUST_BACKTRACE=full umberwm

serializing conf... thread 'main' panicked at 'called Result::unwrap() on an Err value: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })', /home/teqnaz/.cargo/registry/src/github.com-1ecc6299db9ec823/umberwm-0.0.34/src/main.rs:161:29 stack backtrace: 0: 0x55f24959e00c - ::fmt::hd7af80eb76a6998a 1: 0x55f2495c40ac - core::fmt::write::h6939a8fd5b3a5e3a 2: 0x55f24959af01 - std::io::Write::write_fmt::hb5900ee4441529e9 3: 0x55f2495a0085 - std::panicking::default_hook::{{closure}}::h58a8be54ae947ef4 4: 0x55f24959fd44 - std::panicking::default_hook::h9fe353962e877b53 5: 0x55f2495a07b8 - std::panicking::rust_panic_with_hook::h0bc9d5d0acf73848 6: 0x55f2495a04c7 - std::panicking::begin_panic_handler::{{closure}}::h076ddf9c3777574c 7: 0x55f24959e4a4 - std::sys_common::backtrace::rust_end_short_backtrace::hdbbfbc78db18e8d2 8: 0x55f2495a01e9 - rust_begin_unwind 9: 0x55f249546d13 - core::panicking::panic_fmt::h6df85570a7d78752 10: 0x55f249546e03 - core::result::unwrap_failed::h7d332eb6dadc6c7c 11: 0x55f24954cf68 - umberwm::main::hcac728d811cdd674 12: 0x55f249549943 - std::sys_common::backtrace::rust_begin_short_backtrace::h014fa535c25ac036 13: 0x55f249549979 - std::rt::lang_start::{{closure}}::h00e782856a7b25dd 14: 0x55f24959d878 - std::rt::lang_start_internal::hddd786883f88af74 15: 0x55f24954d2d2 - main 16: 0x7f40d669aa22 -

cryptixd commented 2 years ago

There was no ~/.config dir, this did the trick:

$ mkdir ~/.config

The when I ran umberwm again I got this.... $ umberwm

serializing conf... generated configuration in /home/$user/.config/umberwm.ron