On Aug 8, 4:03pm, Benoit Champagne wrote:
> Subject: FVWM: X protocol problems
> ===>Scott Lampert writes:
>
> Scott> I was wondering if anyone has seen a problem with getting tons
> Scott> of X-protocol error messages while running fvwm2.0.xx under Linux?
> Scott> I've determined the problem is definately fvwm on my end; none of
my
> Scott> other window managers exhibit this behavior. It seems to happen
> Scott> randomly, but it happens a lot. This has been happening here
since
> Scott> version 2.0.42 (which is the first version I installed after 1.24)
> Scott> and I haven't been able figure out where the problem is coming
from.
> Scott> If anyone would have any suggestions on where to start looking I'd
> Scott> appreciate a tip or two.
>
> Scott> I'm currently running the XFree S3 server with 3.1.2E on Linux
> Scott> kernel 2.0.11 (but the version of the kernel never seemed to
> Scott> matter). I recently switched to an S3 Trio64V+ card from a Tseng
> Scott> W32 but I had the problems with the W32 also. Thanks,
>
> Scott> -Scott
>
> Scott> -- Scott Lampert fortunato_at_ioa.com
http://www.ioa.com/home/fortunato
> Scott> "Sing the Hare Hare, Dance the Hoochie Koo" -- Visit the official
> Scott> FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>. To
unsubscribe
> Scott> from the list, send "unsubscribe fvwm" in the body of a message to
> Scott> majordomo_at_hpc.uh.edu. To report problems, send mail to
> Scott> fvwm-owner_at_hpc.uh.edu.
>
> I do encounter X errors when restarting fvwm with the FvwmButton Module.
>
> Here's an example:
> FvwmButtons: Cause of next X Error.
> X Error of failed request: BadWindow (invalid Window parameter)
> Major opcode of failed request: 12 (X_ConfigureWindow)
> Resource id in failed request: 0x2800003
> Serial number of failed request: 460
> Current serial number in output stream: 479
>
> Don't know the cause of it though...
I thought that this would be in the mailing list archive. Does this not happen
when you have something like the pager swallowed in the button bar?
I was hoping that this would be fixed in version 2.0.43. Is it not?
I have another problem that I think might be related to this. I use
xscreensaver as my locking program. After unlocking my workstation first thing
in the morning, my FvwmButtons module is always dead and I have to restart it.
Does anyone else have this problem.
--
_/_/_/ _/ _/ _/_/_/_/ _/_/_/_/_/_/ Robert H. Ford II
_/ _/ _/ _/ _/ _/ _/ Luncet Technologies
_/_/_/ _/_/_/ _/_/_/ _/ _/ Bell Labs Innovations
_/ _/ _/ _/ _/ _/ _/ Naperville IL, 60566-7045
_/ _/ _/ _/ _/ _/_/_/_/_/_/ Email: RHFORD2_at_LUCENT.COM
Voice: (708) 713-4957
__________________________________________________
| M R spiders! | | | |
| M N O spiders! | | | |
| O S A R - C D E D B D I's? | | | |
| Y I B, M R spiders... | | * |
| * | |
| * |
--------------------------------------------------
--
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 Thu Aug 08 1996 - 15:59:59 BST