I've gone ahead and forwarded this upstream as an X bug, however really
some additional analysis ought to be done. I don't think there's enough
info on the upstream bug for us to be able to expect a response, but who
knows, worth a shot I guess.
It would be helpful to narrow this to a test code that reproduces the
problem. *Maybe* since firefox is so widely available they'll look at
it, but most typically with these kinds of bugs upstream wants to see a
concise test case.
It is also almost always a good idea to run the client app using xtrace
in order to study the client-server interaction and see exactly what
sequence of commands the client is sending to the server. Especially in
this case I think it's extraordinarily likely upstream is going to ask
for this to be done.
** Also affects: libx11 (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: freedesktop.org Bugzilla #23416
https://bugs.freedesktop.org/show_bug.cgi?id=23416
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=23416
Importance: Unknown
Status: Unknown
** Changed in: libx11 (Ubuntu)
Importance: Undecided => High
** Changed in: libx11 (Ubuntu)
Status: New => Incomplete
--
[MASTER] Gdk-ERROR **: The program 'firefox-3.5' received an X Window System
error (BadWindow)
https://bugs.launchpad.net/bugs/401055
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
