Resolving fixed as this problem doesn't occur in Hardy either.
** Changed in: xcb (Ubuntu)
Status: Confirmed = Fix Released
--
Closing glxgears window causes xcb_xlib_lock assertion and sound interruption
https://bugs.launchpad.net/bugs/91077
You received this bug notification because
This problem no longer happens in Gutsy. Resolve fixed?
--
Closing glxgears window causes xcb_xlib_lock assertion and sound interruption
https://bugs.launchpad.net/bugs/91077
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
We believe this bug is fixed in current upstream libX11 git.
--
Closing glxgears window causes xcb_xlib_lock assertion and sound interruption
https://bugs.launchpad.net/bugs/91077
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
From aaronp:
I believe that this is not a bug in libGL. The library needs to unregister
its extension in its teardown path in case it is unloaded with dlclose(3).
The fact that this can happen from inside libX11 while the lock is held is an
issue that libX11 needs to be able to handle.
--
The consensus among Nvidia engineers is that this is a bug in xcb :)
** Changed in: xcb (Ubuntu)
Sourcepackagename: linux-restricted-modules-2.6.20 = xcb
--
Closing glxgears window causes xcb_xlib_lock assertion and sound interruption
https://bugs.launchpad.net/bugs/91077
You received this bug
I'm going to assume that 302927 in the NVIDIA bugzilla.
Timo:
Thanks for sending this upstream. I did send an email to nvidia about this on
the 11th but never received a reply. It seems your contact was far more
effective...
--
Closing glxgears window causes xcb_xlib_lock assertion and sound
this is confirmed by upstream :
02:19 aaronp tepsipakki: I reproduced the problem and filed bug 302927.
02:32 aaronp tepsipakki: It looks like what's happening is that XPending is
calling
XLockDisplay and then encounters an IO error, which calls exit,
and libGL
: )
--
Closing glxgears window causes xcb_xlib_lock assertion and sound interruption
https://bugs.launchpad.net/bugs/91077
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Sourcepackagename: mesa = linux-restricted-modules-2.6.20
--
Closing glxgears window causes xcb_xlib_lock assertion and sound interruption
https://launchpad.net/bugs/91077
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
OK, it looks like assertion is being caused by the legacy NVIDIA GL
library:
(gdb) thread apply all bt
Thread 1 (process 5358):
#0 0xb7f30410 in __kernel_vsyscall ()
#1 0xb7d92df0 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7d94641 in abort () from /lib/tls/i686/cmov/libc.so.6
#3
Version information:
nvidia-glx-legacy 1.0.7184+2.6.20.2-9.8
--
Closing glxgears window causes xcb_xlib_lock assertion and sound interruption
https://launchpad.net/bugs/91077
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
which version of libxcb do you have installed? The latest version
(1.0-1.1ubuntu2) has a patch which should fix those assertion bugs (in
fact, it only skips the locking test).
** Changed in: mesa (Ubuntu)
Status: Unconfirmed = Needs Info
--
Closing glxgears window causes xcb_xlib_lock
libxcb1 1.0-1.1ubuntu1 .
I'm aware of the patch that went in to stop the notification of these
types of problem (Bug #90757 ?). However after Feisty is released this
lock checking will be re-enabled so I might as well report the problem
in core packages now. I don't object to seeing legit
13 matches
Mail list logo
