On Sat, Jul 17, 1999 at 03:07:17PM -0500, fox_at_foxtaur.com wrote:
> I decided to change around some of my X startup stuff, and found a
> strange behavior of fvwm2.
>
> Previously I would start all my clients from my .xsession script, and
> then exec fvwm2 at the bottom. Now my script basically just exec's
> fvwm2, and I've moved my clients' startup to the InitFunction, like so:
>
> AddToFunc InitFunction
> + "I" Exec xload
> + "I" Exec oclock
> + "I" Exec xcb
> + "I" Exec netscape -iconic
> + "I" Function StandardXterms
> + "I" Exec ICQ
>
> Strangely, though, when I start up my X session now, I am treated to a
> completely blank X screen, and it will stay that way, indefinitely,
> until I touch the mouse, moving it slightly. Then the window manager
> "wakes up" and runs its InitFunction.
>
> Why does it do this?
That's hard to say unless you tell us the fvwm version you are using.
This should not happen.
Bye
Dominik ^_^
--
Dominik Vogt, Hewlett-Packard GmbH, Dept. BVS
Herrenberger Str.130, 71034 Boeblingen, Germany
phone: 07031/14-4596, fax: 07031/14-3883, dominik_vogt_at_hp.com
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sun Jul 18 1999 - 18:38:54 BST