This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: problem with using xsetroot without window manager
- From: "Dawson, David W" <david dot w dot dawson at lmco dot com>
- To: Cygwin-Xfree <cygwin-xfree at sources dot redhat dot com>
- Date: Fri, 11 Jan 2002 09:20:14 -0500
- Subject: RE: problem with using xsetroot without window manager
As a matter of fact, that is how it works.
It is a design feature of XFree86 (and most other X-Servers) to perform a
reset when the number of client connections goes to zero. In your case (and
as discussed before) the xsetroot program is the only client connected, so
after it set's the root background, it disconnects and XWin resets. AFIK
this behavior is not optional. You need to re-order the sequence of client
starts, so that there is a "persistent" client (like an xterm or the window
manager, or...)
-D
---------------------
David Dawson
david.w.dawson@lmco.com
703-367-3885
> -----Original Message-----
> From: Ralf Habacker [SMTP:Ralf.Habacker@freenet.de]
> Sent: Friday, January 11, 2002 2:34 AM
> To: Cygwin-Xfree
> Subject: problem with using xsetroot without window manager
>
> Hi,
>
> I'm using the latest Xserver Test Release and have recognized a problem,
> when starting some
> apps without any window manager.
>
> For starting kde/kde2 I'm using setxroot to choose another background at
> the start of the
> launching process, which needs some time. At this time no window manager
> is running. With
> this configuration the color isn't set, but the xserver seems to be
> restarted. (The window
> seems to be closed for a little while and comes back)
> After startung twm, kwm or kwin color setting works.
> The same effect occurs, when I'm starting for example xdpyinfo without any
> window manager.
> When the end of the listing is reached the server "restarts".
>
> Any ideas ?
>
> Regards
> Ralf