Quick fix/workaround is the following patch, simply overwriting the
wrapped trezor_agent.py with the real thing.
live well,
vagrant
commit ef39a4dc42dcd2daaa7a626c923f1115f8540091
Author: Vagrant Cascadian
Date: Fri Feb 8 03:23:14 2019 +
trezor-agent: Overwrite trezor_agent.py
When running trezor-agent (or any of the others), I get a bizarre python
traceback with a bunch of code that looks to be shell code.
$ trezor-agent
Traceback (most recent call last):
File
"/gnu/store/77i5pm165ljn8fx030z41yqaja77lb99-trezor-agent-0.10.0/bin/.trezor-agent-real",
line 11, in
Hi!
Ricardo Wurmus skribis:
> Christopher Baines writes:
>
>> I've tried out the change you pushed here [1], and it looks good to me
>> :) I can't see anything odd in the output now.
>>
>> 1:
>> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=7473bce207af846312d5167a398f5f20bbf3e896
>
>
Arun Isaac writes:
>> + ;; TODO: Something like this:
>> + ;; (disallowed-references native-inputs)
>
> What is this part for?
This is to ensure that no references to any native input are retained in
the output. (Think of it as an assertion that is
Ricardo Wurmus writes:
> [snip]
>
> I think it’s fine to leave it as it is, then. “--install” and
> “--remove” are stateful and should be expected to have quirks like this.
> (E.g. upgrading Guix in between two “--install”s can lead to
> a mosaic of a profile that could not be produced any
I first noticed this when setting sddm as my login session manager, however
this bug can be reproduced without setting it as login session manager - Run
`guix environment --ad-hoc sddm -- sddm` and one of the output lines is:
[11:05:41.156] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth
