Re: FVWM: Program crash with "BadAcess"

From: Charles Hines <chuck_hines_at_VNET.IBM.COM>
Date: Fri, 20 Sep 1996 09:28:31 -0400

>>>>> "Jerome" == Jerome Audu <ja_at_itmi.cgs.fr> writes:

Jerome> Hello,
Jerome> I've been using Fvwm2.4+ for a few days

When referring to fvwm version numbers, please use the correct full
version number if you know it (see the man page for how to figure that
out). It is a number like 2.0.43 (not 2.4), and the distinction is
rather important in case one is referring to a bug that was fixed in a
specific patchlevel. This is not the case for this problem, but
enough people do this so I figured I should say something (I'm putting
a note about that in the FAQ too).

Jerome> on SunOS 4.1.3 I compiled it with gcc 2.7.2, xpm 3.4h, etc..

Jerome> It works fine with all my programs but one of
Jerome> them (ProcTool) tells this:

>> brutus# ./proctool
>> Assertion failure, datatype != KSTAT_DATA_ULONG
>> Warning: Cannot convert string "times-bold-14" to type FontStruct
>> ProCtool, reading init file "/usr/local/proctool/.proc.init" ...
>> X Error of failed request: BadAccess (attempt to access private
>> resource denied)
>> Major opcode of failed request: 28 (X_GrabButton)
>> Serial number of failed request: 1595
>> Current serial number in output stream: 1596

Jerome> But this program works fine with the old "mwm" !

Jerome> So, what can I do to solve the problem ?? Any idea ??

You just reminded me of another thing I wanted to put in the FAQ, but
had forgotten about. Coincidentally it answers your question:

----------------------------------------------------------------------

31) I try to run some program under FVWM, but it dies with an X11
    error like BadAccess. The same program works just fine under MWM
    or OLWM. What's going on?

A: The error message usually looks something like this:

        X Error of failed request: BadAccess (attempt to access private
        resource denied)
         Major opcode of failed request: 28 (X_GrabButton)
         Serial number of failed request: 1595
         Current serial number in output stream: 1596

   Well, this is generally telling you that there is a conflict in
   key/button assignments. In your .fvwm2rc you have bound some
   key/button that this program really wants to bind to an action, but
   it can't since FVWM has already done so (but you weren't doing it
   in the rc file for your previous window manager). Figure out what
   the offending key binding is and remove it from your .fvwm2rc, or
   temporarily via FvwmTalk by removing the FVWM binding (see the man
   page for the Key & Mouse commands).

----------------------------------------------------------------------

Hope that helps,
Chuck
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Sep 20 1996 - 08:47:35 BST

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