*** This bug is a duplicate of bug 87947 ***
https://bugs.launchpad.net/bugs/87947
** This bug has been marked a duplicate of bug 87947
xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c-xlib.lock' failed.
--
c-xlib.lock
https://bugs.launchpad.net/bugs/87390
You received this bug notification
Using icedtea ist not an option, since there is currently no javaws
(webstart) binary...
--
c-xlib.lock
https://bugs.launchpad.net/bugs/87390
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
adam: java is broken. Either use icedtea or the workarounds mentioned in
/usr/share/doc/libx11-6/NEWS.Debian.gz.
--
c-xlib.lock
https://bugs.launchpad.net/bugs/87390
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I just updated my system to the latest Hardy packages and stumbled upon
this same issue. I am doing development with JOGL (Java OpenGL) and
java crashes every time I try to run the program. Here's the output:
--
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0
0) yes
1) open-vm-tools (vmware-user)
2) does not run, gets an assertion.
3)
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0xb7a75767]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_unlock+0x31) [0xb7a758b1]
#2 /usr/lib/libX11.so.6(_XReply+0xfd) [0xb7e0929d]
#3
Setting back to confirmed as this bug is back for hardy
** Changed in: libxcb (Ubuntu)
Status: Fix Released = Confirmed
--
c-xlib.lock
https://bugs.launchpad.net/bugs/87390
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
On 12/18/07, Che Guevara [EMAIL PROTECTED] wrote:
Setting back to confirmed as this bug is back for hardy
If you can confirm this bug, then you have an obligation to provide a
lot more information. Many quite different problems were reported in
this Launchpad bug, and many things have changed
Marking as fixed although libx11 in Gutsy doesn't use xcb so it cannot
be tested.
** Changed in: libx11 (Ubuntu)
Status: New = Fix Released
--
c-xlib.lock
https://bugs.launchpad.net/bugs/87390
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
We believe that current libX11 from upstream git fixes the problems when
GL-using apps exit on systems with the proprietary nVidia driver.
To the people who reported other bugs here: please ensure your X
libraries are up-to-date, and if you can still reproduce the problem
please supply a
After the update it works now. :)
Many thanks!
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
On the fglrx system the updated worked also.
Thank you
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Today's update fixed the issue for me, using the radeon-driver. Thanks!
libxcb and assosciated packages is now version 1.0-1.1ubuntu2, while
libx11 and assosciates is 1.1.1-1ubuntu1.
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
After the second update today the problem is also fixed for me! (nvidia
system) I'll try my fglrx system in just a sec
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
On 3/9/07, Jos Plompen [EMAIL PROTECTED] wrote:
This is fixed for me too.
But I now get another error:
$glxgears
3078 frames in 5.0 seconds = 613.898 FPS
4380 frames in 5.0 seconds = 875.375 FPS
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :
1.0
after
This is fixed for me too.
But I now get another error:
$glxgears
3078 frames in 5.0 seconds = 613.898 FPS
4380 frames in 5.0 seconds = 875.375 FPS
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :1.0
after 16469 requests (32 known processed) with 0 events remaining.
I installed all updates in Feisty, but still the same error occures:
$ glxgears
36 frames in 5.0 seconds = 7.183 FPS
13 frames in 5.2 seconds = 2.477 FPS
XIO: fatal IO error 22 (Invalid argument) on X server :0.0
after 29 requests (29 known processed) with 0 events remaining.
glxgears:
Does not work for me.
I posted the similar comment on launchpad:
$ glxgears
36 frames in 5.0 seconds = 7.183 FPS
13 frames in 5.2 seconds = 2.477 FPS
XIO: fatal IO error 22 (Invalid argument) on X server :0.0
after 29 requests (29 known processed) with 0 events remaining.
glxgears:
Same here, still broken:
`LIBXCB_ALLOW_SLOPPY_LOCK=true glxinfo`
name of display: :0.0
glxinfo: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c-xlib.lock' failed.
Aborted (core dumped)
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Same here, things still does not work. No Openoffice-applications work,
in addition to applications using OpenGL (at least including beryl,
ppracer, glxinfo, glxgears).
Setting the LIBXCB_ALLOW_SLOPPY_LOCK to true does not matter.
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs
Just updated everything again (including libxcb) + reboot.
Still get the same error on both of my systems.
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Just a mail to the desperate: It works if you install the nvidia drivers
from the nvidia web site.
Good luck
2007/3/8, Justin [EMAIL PROTECTED]:
Just updated everything again (including libxcb) + reboot.
Still get the same error on both of my systems.
--
c-xlib.lock
Why is this bug still unconfirmed? Is there any way we can speed up
the progress... Any output needed or commands to run so we can help the
maintainers of the package?
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
do you still get that bug? A libxcb update has been uploaded to
workaround the assertion for feisty and fix the problem then
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
this upload should fix this, if not please reopen:
libxcb (1.0-1.1ubuntu1) feisty; urgency=low
.
[ Timo Aaltonen ]
* debian/patches:
- 100_allow_sloppy_lock.diff from Novell, workaround to the various
'Assertion `c-xlib.lock' failed' -bugs by setting an environment
oops, sorry seb, I should refresh the bug before posting :)
anyway, reopen if the issue remains
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Same problem here with a dell d620 laptop and nvidia binary driver.
ooo fails to start, wine fails to start, 3d apps fail to start.
e.g.
#glxinfo
name of display: :0.0
glxinfo: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c-xlib.lock' failed.
Aborted (core dumped)
I'm more than happy to provide
I fully agree to Davim.
I've got a Radeon Xpress 200M too and i also have these Problems with starting
Beryl using fglrx+xgl
It would be lovely to see this fixed .
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I get the same problem when starting beryl-xgl, I have a Xpress 200m and
I'm using fglrx since I cant get 3d acceleration with the open drivers.
$ LD_PRELOAD=/usr/lib/fglrx/libGL.so.1.2.xlibmesa beryl-xgl --replace
[3] 31263
$ **
*
I've got the same problem, if I start some application e.g. Savage (game) there
is following Error:
xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c-xlib.lock' failed.
I've found some other people in different german speaking forums which
have the same problem e.g with OOo. If they install the the
I have the same problem with nvidia-glx-legacy 1.0.7184+2.6.20.2-9.8 on
feisty running beryl and glxgears:
~$ glxgears
6954 frames in 5.0 seconds = 1390.729 FPS
6749 frames in 5.0 seconds = 1349.751 FPS
XIO: fatal IO error 22 (Invalid argument) on X server :0.0
after 29 requests (29 known
I have the same problem but with the citrix ICA client. On both of my
machines. All fully updated Feisty Fawn machines. 1 has the binaire
nvidia driver from the repository: 1.0.9631+2
But on my laptop with the fglrx from ATI I got the some problem after
the update two days ago.
--
c-xlib.lock
I updated my xlibs this morning and the problem now exist with the nv
driver also. Things are just getting worst. :-(
2007/2/26, haaland [EMAIL PROTECTED]:
I've got the same bug, but I am using a radeon card, with the open
radeon-driver. libgl1-mesa-glx is version 6.5.2-3ubuntu1.
--
Comments like that one are of no use. You are using an unstable
distribution which is meant to get work done, problems happen and they
are often fixed. If you don't want any breakage you probably want to
consider sticking to a stable version of the distribution.
--
c-xlib.lock
What application is causing the problem with the nv driver? Could you
get a backtrace?
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Sorry if it seemed too negative. I did not want to complain. I just wanted
to comunicate. Anyway.. it was my fault this time. I did not test it well. I
thought I had the nv driver but it was not so. The problem is still
happening with the nvidia driver.
2007/2/27, Sebastien Bacher [EMAIL
** Changed in: libx11 (Ubuntu)
Sourcepackagename: libx11 = linux-restricted-modules-2.6.20
Status: Needs Info = Unconfirmed
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I've got the same bug, but I am using a radeon card, with the open
radeon-driver. libgl1-mesa-glx is version 6.5.2-3ubuntu1.
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Martin: try reinstalling nvidia-glx if that helps.
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Reinstalling nvidia-glx does not cure the proble. But if I use the nv
driver instead of the nvidia driver, it works. Well then I don't have 3D
anymore. :-(
2007/2/26, Timo Aaltonen [EMAIL PROTECTED]:
Martin: try reinstalling nvidia-glx if that helps.
--
c-xlib.lock
here is the backtrace when starting openoffice:
(no debugging symbols found)
Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no
I'm up to date on feisty. I use Crossover with wine. But my Openoffice has
nothing special.
2007/2/23, Sebastien Bacher [EMAIL PROTECTED]:
Thank you for your bug. Could you get a backtrace
(https://wiki.ubuntu.com/DebuggingProgramCrash) of the crash? The
problem is likely not to libx11, the
Looks like a problem with mesa. What version of the libgl1-mesa-glx
package is installed? What videocard do you have? Do you use any binary
driver that could divert the mesa libgl?
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
libgl1-mesa-glx is at version 6.5.2-3ubuntu1
I have a nvidia card with the binary driver that is in the feisty
repository: nvidia-glx version 1.0.9631+2.6.20.2-8.7
2007/2/24, Sebastien Bacher [EMAIL PROTECTED]:
Looks like a problem with mesa. What version of the libgl1-mesa-glx
package is
Thank you for your bug. Could you get a backtrace
(https://wiki.ubuntu.com/DebuggingProgramCrash) of the crash? The
problem is likely not to libx11, the new version of that package just
trigger lock problem to other libraries. Is you distribution uptodate?
wine, ooweb, oowriter works fine on my
Beryl (beryl-xgl) also has this lock / unlock problem.
That is the only app. I get that error with.
More info here for reference:
http://lwn.net/Articles/211808/
--
c-xlib.lock
https://launchpad.net/bugs/87390
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
45 matches
Mail list logo
