Bug 60159 - grip 3.2.0 always crashes with unexpected async reply from Xlib
Bug#: 60159 Product:  Gentoo Linux Version: unspecified Platform: x86
OS/Version: Linux Status: RESOLVED Severity: major Priority: P2
Resolution: UPSTREAM Assigned To: sound@gentoo.org Reported By: jgeisler@css.tayloru.edu
Component: Applications
URL: 
Summary: grip 3.2.0 always crashes with unexpected async reply from Xlib
Keywords:  
Status Whiteboard: 
Opened: 2004-08-12 11:20 0000
Description:   Opened: 2004-08-12 11:20 0000
Whenever I put a disk in my CDROM player, grip will error out with a line like:

Xlib: unexpected async reply (0x6df)

This is not an exact error message, since I've downgraded to grip 3.0.7 to confirm that the newer version was the problem.  The error is not immediate, but seems to be whenever I try pressing a button or when grip regains focus.

Reproducible: Always
Steps to Reproduce:
1. emerge -u grip-3.2.0
2. grip &
3. put a CD in the CDROM
4. move the mouse around or press a button

Actual Results:  
Grip segfaults, but Gtk seems to try catching the error and offers to restart
the program.  Unfortunately, that doesn't work either and so the window just
hangs doing nothing while the CD continues to play. kill(1)'ing the grip window
does work.

Expected Results:  
run withouout problems.  see grip 3.0.7 for an example

------- Comment #1 From Frank van de Pol (RETIRED) 2004-08-15 14:24:03 0000 -------
Could you include the emerge info output? Are there cases where you can operate
grip 3.2.0 without triggering this bug?

------- Comment #2 From Jonathan Geisler 2004-08-16 10:21:23 0000 -------
Created an attachment (id=37544) [details]
emerge info

------- Comment #3 From Jonathan Geisler 2004-08-16 10:22:23 0000 -------
I have not found a single positive case where grip 3.2.0 would run without
crashing.

------- Comment #4 From Jeremy Huddleston (RETIRED) 2004-09-15 11:07:31 0000 -------
works for me...  I think you're going to have to talk with the upstream devs
about this as we can't reproduce the problem.  Please reopen this bug when a
fix is found.