Le 26 juillet 2015 15:17:06 GMT+02:00, Salvo Tomaselli a
écrit :
>I feel that this is going OT.
>
>Probably a new bugreport would be better to discuss the issue.
The bug is already filles: how to autostart something
-- eric
I feel that this is going OT.
Probably a new bugreport would be better to discuss the issue.
Am Sonntag, 26. Juli 2015, 13:15:43 schrieb Eric Valette:
> On 26/07/2015 13:02, Salvo Tomaselli wrote:
> > > Tried this setting only PATH, and it prevented me to log in...
> >
> > Probably a mistake in your script that causes sh to terminate.
>
> export PATH=$HOME/bin:/usr/local/bin:/bin:/usr/b
On Sunday 26 July 2015 13:15:43 Eric Valette wrote:
> export PATH=$HOME/bin:/usr/local/bin:/bin:/usr/bin:
>
> where is the error?
The $PATH at the end of you export statement:
export PATH=$HOME/bin:/usr/local/bin:/bin:/usr/bin:$PATH
signature.asc
Description: This is a digitally signed message
On 26/07/2015 13:02, Salvo Tomaselli wrote:
> Tried this setting only PATH, and it prevented me to log in...
Probably a mistake in your script that causes sh to terminate.
export PATH=$HOME/bin:/usr/local/bin:/bin:/usr/bin:
where is the error?
--eric
--
To UNSUBSCRIBE, email to debian-q
> Tried this setting only PATH, and it prevented me to log in...
Probably a mistake in your script that causes sh to terminate.
It is possible to mitigate the issue by placing shell scripts in
~/.config/plasma-workspace/env
However it must be noted that they will be sourced, not executed in separate
processes.
Tried this setting only PATH, and it prevented me to log in...
--eric
--
To UNSUBSCRIBE, email to debian-q
It is possible to mitigate the issue by placing shell scripts in
~/.config/plasma-workspace/env
However it must be noted that they will be sourced, not executed in separate
processes.
--
Salvo Tomaselli
"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione
8 matches
Mail list logo
