宋文武 skribis:
> Ludovic Courtès writes:
>
>> Thinking more about it, the fix in 1d18d87 wasn’t quite right.
>>
>> I think the right thing would be to run the window manager as a child of
>> a ‘bash --login’ process, so the whole X session would get environment
>> variables like a login shell.
>>
Ludovic Courtès writes:
> Thinking more about it, the fix in 1d18d87 wasn’t quite right.
>
> I think the right thing would be to run the window manager as a child of
> a ‘bash --login’ process, so the whole X session would get environment
> variables like a login shell.
>
> WDYT, 宋文武?
Agree!
And
Thinking more about it, the fix in 1d18d87 wasn’t quite right.
I think the right thing would be to run the window manager as a child of
a ‘bash --login’ process, so the whole X session would get environment
variables like a login shell.
WDYT, 宋文武?
Thanks,
Ludo’.
I believe this is fixed by 1d18d87.
Let me know if there’s anything wrong.
Thanks!
Ludo’.
To reproduce, create an operating-system configuration that uses the
slim-service and do not add any additional packages to the base
system, such as xterm.
As an unpriveleged user, run 'guix packge -i xterm'. Then, try to
launch xterm via Window Maker's main menu. It will fail.
- Dave
