On 2017-02-20 10:15:16 -0500, Greg Wooledge wrote:
> On Mon, Feb 20, 2017 at 04:02:50PM +0100, Vincent Lefevre wrote:
> > Note: since window managers can also start X clients on start up,
> > a .xsession file may not be useful for everyone.
>
> It's a crazy mixed-up world.
I'd say that it's
On 2017-02-20 10:15:16 -0500, Greg Wooledge wrote:
> On Mon, Feb 20, 2017 at 04:02:50PM +0100, Vincent Lefevre wrote:
> > More precisely, if I understand correctly,
> >
> > 1. The DM can request some window manager (for instance, the user has
> >the choice between several ones, and he may
On 2017-02-20 08:34:23 -0500, Greg Wooledge wrote:
> If you need a home directory that will work consistently across different
> operating systems, then I *strongly* suggest you stick with startx and
> make .xinitrc a symlink to .xsession for backwards compatibility.
This what I did in the past,
On Mon, Feb 20, 2017 at 04:02:50PM +0100, Vincent Lefevre wrote:
> More precisely, if I understand correctly,
>
> 1. The DM can request some window manager (for instance, the user has
>the choice between several ones, and he may also choose the default
>session file, or whatever has been
On 2017-02-20 08:19:28 -0500, Greg Wooledge wrote:
> OK, short version: forget .xinitrc ever existed.
*And* make sure that you do not have a .xinitrc file, otherwise it
can break things (at least when logging in on a text console).
> Use ~/.xsession unless that doesn't work. See
>
Greg Wooledge wrote:
> Debian's Xsession is not the same as Red Hat's.
>
> If you need a home directory that will work consistently across different
> operating systems, then I *strongly* suggest you stick with startx and
> make .xinitrc a symlink to .xsession for backwards compatibility. Any
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 20, 2017 at 01:13:09PM +, Rob Brewer wrote:
> to...@tuxteam.de wrote:
>
> >
> > On Mon, Feb 20, 2017 at 01:32:37PM +0100, Vincent Lefevre wrote:
> >> On 2017-02-20 12:49:34 +0100, to...@tuxteam.de wrote:
> >
> > [...blah...]
> >
>
On Mon, Feb 20, 2017 at 01:13:09PM +, Rob Brewer wrote:
> Thank you for your explanations, I must admit that I didn't expect it to be
> so involved. I seem to remember mapping out the X startup processes a number
> of years ago but I was running RedHat then, so I suppose it has changed a
>
to...@tuxteam.de wrote:
>
> On Mon, Feb 20, 2017 at 01:32:37PM +0100, Vincent Lefevre wrote:
>> On 2017-02-20 12:49:34 +0100, to...@tuxteam.de wrote:
>
> [...blah...]
>
>> > See man (5) Xsession and poke a bit through the scripts in
>> > /etc/X11/Xsession.d/, then have a look at
On Mon, Feb 20, 2017 at 01:32:37PM +0100, Vincent Lefevre wrote:
> I don't see any contradiction to what I've said. Note that I haven't
> mentioned .xsessionrc at all, only .xinitrc, which is a different
> thing.
OK, short version: forget .xinitrc ever existed. Use ~/.xsession unless
that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 20, 2017 at 01:32:37PM +0100, Vincent Lefevre wrote:
> On 2017-02-20 12:49:34 +0100, to...@tuxteam.de wrote:
[...blah...]
> > See man (5) Xsession and poke a bit through the scripts in
> > /etc/X11/Xsession.d/, then have a look at
On 2017-02-20 12:49:34 +0100, to...@tuxteam.de wrote:
> On Mon, Feb 20, 2017 at 12:08:00PM +0100, Vincent Lefevre wrote:
> > On 2017-02-19 19:52:24 +, Brian wrote:
> > > On Sun 19 Feb 2017 at 11:00:25 +0100, Vincent Lefevre wrote:
> > >
> > > > On 2017-02-18 20:59:44 +, Brian wrote:
> > >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 20, 2017 at 12:08:00PM +0100, Vincent Lefevre wrote:
> On 2017-02-19 19:52:24 +, Brian wrote:
> > On Sun 19 Feb 2017 at 11:00:25 +0100, Vincent Lefevre wrote:
> >
> > > On 2017-02-18 20:59:44 +, Brian wrote:
> > > > The advice in
On 2017-02-19 19:52:24 +, Brian wrote:
> On Sun 19 Feb 2017 at 11:00:25 +0100, Vincent Lefevre wrote:
>
> > On 2017-02-18 20:59:44 +, Brian wrote:
> > > The advice in startx(1) is sound but nothing stops you using a ,xinitrc.
> > > The command doesn't work in a ,xinitrc? Perhaps it is
On Sun 19 Feb 2017 at 11:00:25 +0100, Vincent Lefevre wrote:
> On 2017-02-18 20:59:44 +, Brian wrote:
> > The advice in startx(1) is sound but nothing stops you using a ,xinitrc.
> > The command doesn't work in a ,xinitrc? Perhaps it is incorrect or the
> > DM ignores it.
>
> AFAIK, .xinitrc
On Sun 19 Feb 2017 at 09:53:41 +, Rob Brewer wrote:
> >> I am running up to date KDE Sid with SDDM but I need to start the gnome
> >> keyring at x startup to satisfy Midori dependencies.
> >>
> >> The Midori FAQ suggests adding “export `gnome-keyring-daemon –start`” to
> >> the historical
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Feb 19, 2017 at 09:53:41AM +, Rob Brewer wrote:
[...]
> Thank you for your help, I was wrong footed by the man page which suggested
> using .xsession not .xsessionrc so I guess the man page needs an update.
> Looks
> like it is now OK
On 2017-02-18 20:59:44 +, Brian wrote:
> The advice in startx(1) is sound but nothing stops you using a ,xinitrc.
> The command doesn't work in a ,xinitrc? Perhaps it is incorrect or the
> DM ignores it.
AFAIK, .xinitrc is not used by DM's, in particular because X has
already been started.
>> I am running up to date KDE Sid with SDDM but I need to start the gnome
>> keyring at x startup to satisfy Midori dependencies.
>>
>> The Midori FAQ suggests adding “export `gnome-keyring-daemon –start`” to
>> the historical .xinitrc but this seems to be ignored as does .xsession as
>>
I am running up to date KDE Sid with SDDM but I need to start the gnome
keyring at x startup to satisfy Midori dependencies.
The Midori FAQ suggests adding “export `gnome-keyring-daemon –start`” to
the historical .xinitrc but this seems to be ignored as does .xsession as
suggested by the
On Sat 18 Feb 2017 at 12:56:54 +, Bob Brewer wrote:
> I am running up to date KDE Sid with SDDM but I need to start the gnome
> keyring at x startup to satisfy Midori dependencies.
>
> The Midori FAQ suggests adding “export `gnome-keyring-daemon –start`” to
> the historical .xinitrc but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Feb 18, 2017 at 12:56:54PM +, Bob Brewer wrote:
> I am running up to date KDE Sid with SDDM but I need to start the gnome
> keyring at x startup to satisfy Midori dependencies.
>
> The Midori FAQ suggests adding “export
I am running up to date KDE Sid with SDDM but I need to start the gnome
keyring at x startup to satisfy Midori dependencies.
The Midori FAQ suggests adding “export `gnome-keyring-daemon –start`” to
the historical .xinitrc but this seems to be ignored as does .xsession as
suggested by the
23 matches
Mail list logo
