FVWM: Oddities in 2.4.16

From: Dameron, Gregg <gregg.dameron_at_lmco.com>
Date: Wed, 13 Aug 2003 14:19:16 -0600

Setup: fvwm 2.4.16, fvwm-themes 0.6.2 on Solaris 8, dual-head non-Xinerama.

Since upgrading from 2.4.7, and with no substantial changes to my config (other than converting deprecated single-letter variables to their longer counterparts), I am seeing two intermittent startup problems.

1) Error messages of the form:
    [FVWM.0][FvwmErrorHandler]: <<ERROR>> *** internal error ***
    [FVWM.0][FvwmErrorHandler]: <<ERROR>> Request 7, Error 8, EventType: 20
or
    [FVWM.0][FvwmErrorHandler]: <<ERROR>> *** internal error ***
    [FVWM.0][FvwmErrorHandler]: <<ERROR>> Request 7, Error 8, EventType: 12
or
    [FVWM.0][FvwmErrorHandler]: <<ERROR>> *** internal error ***
    [FVWM.0][FvwmErrorHandler]: <<ERROR>> Request 56, Error 7, EventType: 12
or
    [FVWM.1][FvwmErrorHandler]: <<ERROR>> *** internal error ***
    [FVWM.1][FvwmErrorHandler]: <<ERROR>> Request 56, Error 7, EventType: 2

Whatever causes these errors appears to be self-healing: when I get one of these, the desktop usually comes up normally anyway. What do these errors signify?

2) Failure to execute the StartFunction and InitFunction on *one* of the displays. Fvwm2 and FvwmTheme are running, my Key and Mouse bindings are all fine, but none of the Modules started in StartFunction are running, nor is the process I "Exec" in InitFunction. Happens on about one-in-ten logins. Ctrl-Alt-Escape doesn't help; restarting is required. (On the opposite display, everything is fine.) Any help is appreciated.

Gregg Dameron

--
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 Wed Aug 13 2003 - 15:21:43 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:55 BST