Bug 38192 – Xemacs crashes regularly

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Richard Smith 2004-01-14 11:13:57 UTC]

About once per day Xemacs crashes with an error message like this:

xemacs: X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  25 (X_SendEvent)
  Resource id in failed request:  0x968fc3
  Serial number of failed request:  17368
  Current serial number in output stream:  17369
Xlib: unexpected async reply (sequence 0x43d9)!

xemacs: X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Resource id in failed request:  0x968fc3
  Serial number of failed request:  17367
  Current serial number in output stream:  17369


Reproducible: Sometimes
Steps to Reproduce:
1. Run Xemacs
2. Use it, or leave it running and don't use it.  Doesn't make any difference.
3. After a few hours it crashes.

Actual Results:  
Xemacs crashed with the above error message.

Expected Results:  
Not crashed.

[Comment 1 Brian O'Reilly 2004-07-29 08:45:47 UTC]

xemacs build fails on amd64 as well after gdbm update. configure fails without an error message:

...
checking for dbm_open in -lgdbm... no
Error: Required GNU DBM support cannot be provided.

!!! ERROR: app-editors/xemacs-21.4.15 failed.
!!! Function src_compile, Line 161, Exitcode 1
!!! (no error message)

suggestion for immediate workaround would be greatly appreciated.

[Comment 2 Richard Smith 2004-07-29 11:53:45 UTC]

Not the same bug.  File a new report.

(Regarding this bug, I can't say whether it has been fixed, because I don't run Xemacs any more.)

[Comment 3 Matthew Schulkind 2004-08-29 15:31:27 UTC]

Please post the output of "emerge info". Any other relevant info would be nice, maybe including a backtrace.

Post "cat /proc/cpuinfo" also, and are you running this remotely or su'ed into root or anything like that?

Does the problem go away if you run "xhost +" before running xemacs? Note, make sure this doesn't open you up security-wise before trying it.

Also, this doesn't seem to be related to the libgdbm, but that has been fixed.

[Comment 4 Timmy Douglas 2004-12-03 13:53:21 UTC]

i used to get the same error. like all the time, but with gnu emacs.
while my emacs is still unstable, i think i mostly got rid of that problem by doing (x-synchronize t)

[Comment 5 Jakub Moc (RETIRED) 2006-06-05 11:49:14 UTC]

Not enought information to do anything about this bug. See Comment #3 and reopen with the requested info if it's still an issue for you.