Florian Warzecha

Repoman QA tests fail without any modification of source tree

2

I wanted to bump the version of app-shells/elvish to the latest version. When I ran the repoman commands pointed out in the readme to check if I did everything correct,...

Template for GUIs with seed+gotham - potential use case/example

2

Hey there, after posting my project on reddit, someone proposed to inform the seed contributors about it. Because you also have a section with examples/use case, I thought you could...

Docker support?

1

First: Thank you for your amazing work bringing gentoo (or a 64bit OS in general) on the raspberry pi 3/4. Now to my problem/question: The docker daemon crashes on my...

[windows/wsl] binfmt does not work in default machine

7

### Issue Description The default machine (WSL 2, Fedora) created during installation of podman for windows has broken binfmt support. ### Steps to reproduce the issue ```shell $ podman.exe run...

This is my first draft for implementing the sysfs abstraction for the charging profiles discussed in #80. The TODO notes in the diff mark stuff where I'm unsure which model...

[Feature Request] Charging Profiles

3

First of all: This project is simply amazing! Now, onto my feature request itself: more recent tuxedo control center versions allow to set so called 'charging profiles', which limit battery...

[Feature Request] Extended CPU settings (governor, min/max frequency, boosting, enabled cores, energy performance profile)

1

The Tuxedo Control Center allows profiles to configure additional settings regarding CPU performance. I.e. both Tuxedo Control Center and tuxedo-rs support a so called 'performance' or 'odm' profile, while only...

apply ld-wrapper to `rust-lld`

2

Since the `2024-05-18` nightly, [rust defaults to its own `rust-lld` linker](https://blog.rust-lang.org/2024/05/17/enabling-rust-lld-on-linux.html), which doesn't work by default on NixOs (rust-lang/rust#125321). The problem has been fixed in: - oxalica/rust-overlay#171 - NixOs/nixpkgs#314268 for...

[docs] suggestion: explicity remark that signals cannot be used from other threads

1

Using signals from another thread (e.g. `set()`) leads to the following error at runtime: ``` thread '' panicked at /home/florian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/floem_reactive-0.1.0/src/signal.rs:274:39: called `Option::unwrap()` on a `None` value note: run with `RUST_BACKTRACE=1`...