bug#19119: X cannot run programs in the current user's profile

bug#19119: X cannot run programs in the current user's profile

[Thompson, David]

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

bug#19119: X cannot run programs in the current user's profile

[Ludovic Courtès]

I believe this is fixed by 1d18d87.

Let me know if there’s anything wrong.

Thanks!

Ludo’.

bug#19119: closed (Re: bug#19119: X cannot run programs in the current user's profile)

[Ludovic Courtès]

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’.

bug#19119: closed (Re: bug#19119: X cannot run programs in the current user's profile)

[宋文武]

Ludovic Courtès <ludo@gnu.org> 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 currently ratposion and windowmaker are hardcoded,
how about make sessions configurable?
Like:
    (define %default-sessions
      `(("windowmaker" . #~(execl #$windowmaker "/bin/wmaker"))
        ("ratposion" . #~(execl #$ratposion "/bin/ratposion"))))

    (define* (slim-service #:key (sessions %default-sessions)
    ...
>
> Thanks,
> Ludo’.

bug#19119: closed (Re: bug#19119: X cannot run programs in the current user's profile)

[Ludovic Courtès]

宋文武 <iyzsong@gmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> 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!

Commit b2bd7c2 does that.  Let me know if you think of adjustments to make!

Ludo’.

PS: I’ll reply to the other topic on guix-devel.

SLiM session types

[Ludovic Courtès]

宋文武 <iyzsong@gmail.com> skribis:

> And currently ratposion and windowmaker are hardcoded,
> how about make sessions configurable?
> Like:
>     (define %default-sessions
>       `(("windowmaker" . #~(execl #$windowmaker "/bin/wmaker"))
>         ("ratposion" . #~(execl #$ratposion "/bin/ratposion"))))
>
>     (define* (slim-service #:key (sessions %default-sessions)
>     ...

I agree that something along these lines is needed.

However, these session types are currently unused.  SLiM is supposed to
support session choice from the log-in screen, but for that, a
‘session_dir’ key needs to be added to slim.cfg (in xorg.scm).

The ‘session_dir’ value should be the name of a directory containing
entries describing the various session types available, in a format that
SLiM understands.

Would you like to try adding that?

Thanks,
Ludo’.

Re: SLiM session types

[tcech]

[-- Attachment #1: Type: text/plain, Size: 1954 bytes --]

On Sat, Dec 13, 2014 at 04:28:50PM +0100, Ludovic Courtès wrote:
>宋文武 <iyzsong@gmail.com> skribis:
>
>> And currently ratposion and windowmaker are hardcoded,
>> how about make sessions configurable?
>> Like:
>>     (define %default-sessions
>>       `(("windowmaker" . #~(execl #$windowmaker "/bin/wmaker"))
>>         ("ratposion" . #~(execl #$ratposion "/bin/ratposion"))))
>>
>>     (define* (slim-service #:key (sessions %default-sessions)
>>     ...
>
>I agree that something along these lines is needed.
>
>However, these session types are currently unused.  SLiM is supposed to
>support session choice from the log-in screen, but for that, a
>‘session_dir’ key needs to be added to slim.cfg (in xorg.scm).
>
>The ‘session_dir’ value should be the name of a directory containing
>entries describing the various session types available, in a format that
>SLiM understands.

I'm not able to understand how the proposed solution should work and
it's a bit unclear to me what is needed to do to add new session -
enlightenment in my case.

Is there reason, why xsession files should not be stored within
profile? I can hardly imagine login manager with session selection to
be anything else than system wide service and in that case path like
/run/current-system/profile/share/xsessions sounds like proper place.

In any case, it would be helpful if packager could just ignore this
architectural decisions and could use some function which returns
desired target directory for xsession files (maybe defining as public
xsessions-directory from gnu/services/xorg.scm?) or even take xsession
file name as argument and do whatever is needed.

And one additional question - if xsession file can be part of multiple
profiles, I can't install or create symlink to target directory during
the build, but it needs to be done on adding to profile - is there any
hook for that?

TIA for answers,

S_W

[-- Attachment #2: Type: application/pgp-signature, Size: 181 bytes --]

Re: SLiM session types

[宋文武]

tcech@suse.cz writes:

> On Sat, Dec 13, 2014 at 04:28:50PM +0100, Ludovic Courtès wrote:
>>宋文武 <iyzsong@gmail.com> skribis:
>>
>>> And currently ratposion and windowmaker are hardcoded,
>>> how about make sessions configurable?
>>> Like:
>>>     (define %default-sessions
>>>       `(("windowmaker" . #~(execl #$windowmaker "/bin/wmaker"))
>>>         ("ratposion" . #~(execl #$ratposion "/bin/ratposion"))))
>>>
>>>     (define* (slim-service #:key (sessions %default-sessions)
>>>     ...
>>
>>I agree that something along these lines is needed.
>>
>>However, these session types are currently unused.  SLiM is supposed to
>>support session choice from the log-in screen, but for that, a
>>‘session_dir’ key needs to be added to slim.cfg (in xorg.scm).
>>
>>The ‘session_dir’ value should be the name of a directory containing
>>entries describing the various session types available, in a format that
>>SLiM understands.
>
> I'm not able to understand how the proposed solution should work and
> it's a bit unclear to me what is needed to do to add new session -
> enlightenment in my case.
>
> Is there reason, why xsession files should not be stored within
> profile? I can hardly imagine login manager with session selection to
> be anything else than system wide service and in that case path like
> /run/current-system/profile/share/xsessions sounds like proper place.
Hi, I just sent 2 patches to remove all the xsessions stuff in xorg.scm.
And use /run/current-system/profile/share/xsessions as sessiondir.

After this, one can get a xfce session by put 'xfce' in 'packages'.

While 'openbox' and 'sawfish' also provide xsession file, 'windowmaker'
and 'ratposion' not.  We can put 'exec ratposion' in ~/.xsession to
start it, or patch the package to install a xsession file to its
$out/share/xsessions if really needed.

>
> In any case, it would be helpful if packager could just ignore this
> architectural decisions and could use some function which returns
> desired target directory for xsession files (maybe defining as public
> xsessions-directory from gnu/services/xorg.scm?) or even take xsession
> file name as argument and do whatever is needed.
>
> And one additional question - if xsession file can be part of multiple
> profiles, I can't install or create symlink to target directory during
> the build, but it needs to be done on adding to profile - is there any
> hook for that?
>
> TIA for answers,
>
> S_W