> Is it?
> Let's look at /etc/X11/Xsession
> $ grep HOME /etc/X11/Xsession
> USRRESOURCES=$HOME/.Xresources
> USERXSESSION=$HOME/.xsession
> USERXSESSIONRC=$HOME/.xsessionrc
> ALTUSERXSESSION=$HOME/.Xsession
> ERRFILE=$HOME/.xsession-errors
> $ grep USERXSESSION /etc/X11/Xsession /etc/X11/Xsession.
> On Friday 16 October 2009 13:42:25 Tim Clewlow wrote:
>> Ok, I found out that there is an error in the .xsession file, the
>> correct version is below, note the line 'icewm &' has now become
>> 'icewm-session &' - this should bring back the correct background
>> and hopefully the mouse will beha
On Fri, Oct 16, 2009 at 11:33:17AM +1100, Tim Clewlow wrote:
> > On Wednesday 14 October 2009 00:34:57 Tim Clewlow wrote:
> >> > On Tuesday 13 October 2009 10:43:21 Tim Clewlow wrote:
> >> >> You can rearrange the order in which things are started in
> your
> >> >> .xsession file, ie you dont have
On Friday 16 October 2009 13:42:25 Tim Clewlow wrote:
> Ok, I found out that there is an error in the .xsession file, the
> correct version is below, note the line 'icewm &' has now become
> 'icewm-session &' - this should bring back the correct background
> and hopefully the mouse will behave nore
On Friday 16 October 2009 13:06:42 Tim Clewlow wrote:
> > But there is still this grey greying out grid over everything
> > instead of a
> > desktop with icons that are not covered by a grid of any kind!
> And
> > if I
> > use .bash_profile to start X and then start idesk from a terminal
> I
> > ge
Ok, I found out that there is an error in the .xsession file, the
correct version is below, note the line 'icewm &' has now become
'icewm-session &' - this should bring back the correct background
and hopefully the mouse will behave noremally again :-)
#!/bin/sh
xrdb -merge ~/.Xdefaults &
icewm-se
> On Friday 16 October 2009 11:10:04 Tim Clewlow wrote:
>> lol - that error makes quite a difference. It means pretty much what
>> it says, ie X is already running, or, the combination of config
files means the system ends up trying to start X twice.
> Yes, I am very sorry. I know that it is essen
On Friday 16 October 2009 11:10:04 Tim Clewlow wrote:
> lol - that error makes quite a difference. It means pretty much what
> it says, ie X is already running, or, the combination of config
> files means the system ends up trying to start X twice.
Yes, I am very sorry. I know that it is essentia
> On Friday 16 October 2009 01:33:17 Tim Clewlow wrote:
>> It sounds like your system is not using the xsession method of
>> managing an X session, which means it is using the native xinit
method. That's ok, and just as easy to work with. First check if
you
>> have a file called .xinitrc in your ho
On Friday 16 October 2009 01:33:17 Tim Clewlow wrote:
> It sounds like your system is not using the xsession method of
> managing an X session, which means it is using the native xinit
> method. That's ok, and just as easy to work with. First check if you
> have a file called .xinitrc in your home
> On Wednesday 14 October 2009 00:34:57 Tim Clewlow wrote:
>> > On Tuesday 13 October 2009 10:43:21 Tim Clewlow wrote:
>> >> You can rearrange the order in which things are started in
your
>> >> .xsession file, ie you dont have to start the window manager
>> last.
>> > [snip]
>> >> Basically, when
On Wednesday 14 October 2009 00:34:57 Tim Clewlow wrote:
> > On Tuesday 13 October 2009 10:43:21 Tim Clewlow wrote:
> >> You can rearrange the order in which things are started in your
> >> .xsession file, ie you dont have to start the window manager last.
> >
> > [snip]
> >
> >> Basically, when th
> On Tuesday 13 October 2009 10:43:21 Tim Clewlow wrote:
>> You can rearrange the order in which things are started in your
>> .xsession file, ie you dont have to start the window manager last.
> [snip]
>> Basically, when the script finishes, X will close - so dont let
>> the
>> script finish - tha
On Tuesday 13 October 2009 10:43:21 Tim Clewlow wrote:
> You can rearrange the order in which things are started in your
> .xsession file, ie you dont have to start the window manager last.
[snip]
> Basically, when the script finishes, X will close - so dont let the
> script finish - thats what the
On Monday 12 October 2009 23:02:19 Nuno Magalhães wrote:
> On Mon, Oct 12, 2009 at 22:52, Lisi wrote:
> [...]
>
> > Yes. But I omitted to mention that because I forgot, that putting an &
> > after both startx and Idesk results in Idesk running correctly - but only
> > if and when I open a termina
> I don't run the xserver by entering startx in the console. I have
it starting
> and running automatically via an entry in ~/.bash_profile.
>> All entries in your .Xsession or similar must end with &, so
>> they'll
>> run in the background, except the last one. This last one should be
>> your win
On Monday 12 October 2009 22:56:28 Andrew Sackville-West wrote:
> On Mon, Oct 12, 2009 at 09:32:55PM +0100, Lisi wrote:
> > The box boots automatically into IceWM in 32 seconds from a standing
> > start.
> >
> > I have Idesk configured to my satisfaction, and it runs beautifully if I
> > start it m
Lisi ha scritto:
The box boots automatically into IceWM in 32 seconds from a standing start.
I have Idesk configured to my satisfaction, and it runs beautifully if I start
it manually after I have booted up and IceWM is running.
Any attempt, however, to make Idesk also start automatically, r
On Mon, Oct 12, 2009 at 22:52, Lisi wrote:
[...]
> Yes. But I omitted to mention that because I forgot, that putting an & after
> both startx and Idesk results in Idesk running correctly - but only if and
> when I open a terminal: and Idesk then closes when I shut the terminal down.
Why are you
On Mon, Oct 12, 2009 at 09:32:55PM +0100, Lisi wrote:
> The box boots automatically into IceWM in 32 seconds from a standing start.
>
> I have Idesk configured to my satisfaction, and it runs beautifully if I
> start
> it manually after I have booted up and IceWM is running.
>
> Any attempt,
On Monday 12 October 2009 22:25:03 Nuno Magalhães wrote:
> On Mon, Oct 12, 2009 at 21:32, Lisi wrote:
> [...]
>
> > Any attempt, however, to make Idesk also start automatically, results in
> > Idesk running fine - but not X and IceWM. The desktop looks odd (as if
> > it hasn't finished loading),
On Mon, Oct 12, 2009 at 21:32, Lisi wrote:
[...]
> Any attempt, however, to make Idesk also start automatically, results in Idesk
> running fine - but not X and IceWM. The desktop looks odd (as if it hasn't
> finished loading), and although all the icons work and the applications start
> up and f
22 matches
Mail list logo
