Arch Linux

djg1971

Member

Registered: 2008-09-11

Posts: 185

Xlib: extension "Generic Event Extension" missing on display ":0.0".

I have been updating my arch system more than once per week via "pacman -Sy; pacman -Su."

After this morning's update, the following error is echoed to the screen whenever I launch an application such as gv, acroread, etc.:

Xlib:  extension "Generic Event Extension" missing on display ":0.0".

Often it is repeated many times.  The programs run without crashing though.

Does anyone else observe this?

Mogger

Member

From: Sweden

Registered: 2008-12-07

Posts: 153

Website

Re: Xlib: extension "Generic Event Extension" missing on display ":0.0".

Yep, I get this. And well, other people too.

djgera

Developer

From: Buenos Aires - Argentina

Registered: 2008-12-24

Posts: 723

Website

Re: Xlib: extension "Generic Event Extension" missing on display ":0.0".

Yes, read http://bugs.archlinux.org/task/13295 please.

bernarcher

Forum Fellow

From: Germany

Registered: 2009-02-17

Posts: 2,281

Re: Xlib: extension "Generic Event Extension" missing on display ":0.0".

Is there any way to at least block this error message?

I make extensive use of Xdialog scripts which often return values via the error channel. While this mostly can be worked around using tail commands for the moment, a less awkward solution would be preferable.

---

To know or not to know ...
... the questions remain forever.

djg1971

Member

Registered: 2008-09-11

Posts: 185

Re: Xlib: extension "Generic Event Extension" missing on display ":0.0".

Sorry for not checking for other posts.

If it is of any use to people involved, I just noticed that using some menus within
xemacs now causes it to crash.  The same action did not cause any crashes right
before the latest update.

Here is what is echoed to the screen:

Fatal error: assertion failed, file signal.c, line 730, QUIT called from within redisplay without being properly wrapped

Fatal error (6).

Lisp backtrace follows:

  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque, size=0) 0x841fbc8> ...)
  # (unwind-protect ...)
  # bind (inhibit-quit)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # bind (inhibit-quit)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  ("(in redisplay)" "[internal]")
  # (unwind-protect ...)
  # bind (inhibit-quit)
  (next-event "[internal]")
  # (condition-case ... . error)
  # (catch top-level ...)

[1]+  Aborted

.:B:.

Forum Fellow

Registered: 2006-11-26

Posts: 5,819

Website

Re: Xlib: extension "Generic Event Extension" missing on display ":0.0".

1. It's not an error, it's a warning. Warnings don't make things go haywire.

2. It's not a pacman issue.

Open a topic for your emacs problem, but this is not related. Check if any packages related to emacs got updated (or emacs itself).

---

Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy