On Mon, 12 Jul 1999 srosa_at_neu.sgi.com wrote:
> Hi,
>
> I got a few programs that were running on the default WM
> for Irix (4DWm), but are crashing under Fvwm2. One example
> is colorview, which shows colors from rgb.txt. I get the
> following error :
>
> [afterburner] ~ (609) % colorview
> X Error of failed request: BadAccess (attempt to access private resource denied)
> Major opcode of failed request: 89 (X_StoreColors)
> Serial number of failed request: 176
> Current serial number in output stream: 183
This is the kind of error that results from fvwm2 having a key binding
overriding that expected by the application. I had this problem with a
Raise/Lower binding to a Ctrl-<something> from a default fvwmrc setup
(from fvwm version 1 days). When the app tries to start up, it apparently
tries to register with the X server for its expected special keys. It
dies when it cannot get direct access to the key it wants. Check out all
of the hotkeys your app uses and find out which is already in use by
fvwm2. Alternately (what I really did), delete all key bindings other
than root window bindings and successively add them back to find which
causes the problem. The app will have to be restarted after eacy key
assignment, or at least have a new window popped up which expects the key
to be available.
There should be appropriate key assignment references to this problem in
the mailing list archive. I don't recall seeing anyone else suffer this
problem (or complain publicly about it), so it is possible you could find
them all by searching on my name in the archive.
Michael Tiefenback
--
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 Mon Jul 19 1999 - 09:54:40 BST