Re: error starting ion3

"Stéphane Mourey" <[email protected]>
Newsgroups gmane.comp.window-managers.ion.general
Message-ID <[email protected]>
By the way, it seems that you have to use .xinitrc instead of .xsession with
Gentoo...

2008/7/2 Stéphane Mourey <[email protected]>:

> Hi,
>
> You're right. I was running another wm (twm). So I just killed it, and ion3
> started as expected.
> I've read the README, but the fact is that I wasn't aware of running
> another wm, and I tried to run nearly like what I did during previous tests
> on Fedora (xinit, then ion3 in xterm). The difference was that I ran startx
> instead of xinit...
> Note that, since my previous mail, I've launch wmii, and its error message
> was far more explicit, and I succeeded to start it after killing twm. At the
> time, I did not realize that the problem should have been the same with ion.
> wmii did not suit me at all, so I so happy now back with ion.
>
> Best regards,
>
> BrokenClock
>
> 2008/7/2 Tuomo Valkonen <[email protected]>:
>
> On 2008-07-02, Stéphane Mourey <[email protected]> wrote:
>> > I'm currently tring to run Ion3 on a freshly installed Gentoo Linux
>> distro.
>> > The installation seems to have been successful, but, when I type "ion3"
>> in
>> > an xterm, I get an error:
>> > "Unable to redirect root window event for screen 0.
>> > Refusing to start due to encountered errors."
>>
>> RTFREADME installation notes. You're likely running another WM
>> already. You should set up your X startup files to launch Ion
>> instead of that. E.g. create .xsession containing
>>
>>    #!/bin/sh
>>    ion3
>>
>> and startx should automatically use it on most systems.
>> If you use a fucked up display manager, you may these days
>>  need to somehow force it to use .xsession. Traditionally
>> it was _exactly the display manager_ that .xsession was
>> for, while startx/xinit didn't use it. But the desktop
>> herd don't want things to work so simple.
>>
>> --
>> Tuomo
>>
>>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.