** Changed in: xorg-server
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in ubuntu.
https://bugs.launchpad.net/bugs/185311
Title:
hardy, locking assertion failure, xorg/libsdl
--
** Changed in: xorg-server
Importance: Medium = Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in ubuntu.
https://bugs.launchpad.net/bugs/185311
Title:
hardy, locking assertion failure, xorg/libsdl
--
I just started having this problem in hardy (manifested by Java) after
an update today (2009-07-14). The sed/XINERAMA workaround suggested by
others earlier worked for now.
Here are the packages I upgraded, it began immediately afterward:
2009-07-14 09:12:52 upgrade libdbus-1-3
** Changed in: xorg-server
Status: Confirmed = Fix Released
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in ubuntu.
--
desktop-bugs
Thanks, sounds like it's resolved and can be closed for karmic.
** Changed in: libxcb (Ubuntu)
Status: Triaged = Fix Released
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Hi Bryce,
ok. I've upgraded to jaunty now (from 8.10 with update-manager -d).
Now in ProE the refresh of windows is more fast that in previous
version. There's only a slight hiccups initially when i open menu or
parameter window, but for the rest it's perfect! Now it's possible to
working again
I've pinged upstream. Has anyone had a chance to test if this still
occurs on Jaunty yet?
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in
I want to change the latest edition of libx11-6 with the non xcb
version (I've the problem of jhyder79 in Pro/Engineer with very slowy
slid-up windows). I've downloaded libx11-6_1.1.3-1ubuntu2~noxcb_i386.deb
but I don't understand how to make the change with my actual libx11-6
(error: a later
My actual installed version of libx11-6 is: 2.1.1.5-2ubuntu1.1
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in ubuntu.
--
desktop-bugs
The Marble Blast game demo also exhibits this bug. I've only checked
this under hardy, however.
The demo can be downloaded from http://www.garagegames.com/products/15/
(you can enter empty strings for the contact info).
Backtrace:
Locking assertion failure. Backtrace:
#0
charly4711, I'm just using libX11 I have from a Fedora 3/64-bit install
I have on another machine (a machine I'm trying to replace with an
Ubuntu one). I've also had success with Bryce's non-x11 .deb files (see
my first posts on this bug, and his posts after that).
--
hardy, locking assertion
Alex,
can you make an intrepid non-xcb libX11 available somewhere?
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in ubuntu.
--
desktop-bugs
Ok, it seems the Intrepid upgrade didn't do anything to fix this issue
for me.
If I ssh from an Intrepid (32-bit) desktop to an Intrepid server
(64-bit) and run Matlab (which utilizes Java), it still runs slow
(screen drawing is unnaturally sluggish). If I LD_LIBRARY_PATH in the
non-xcb libX11
Bryce,
as far as fixing the applications are concerned, I don't quite follow
why applications that used to work need to be fixed because libxcb
apparently one way or another changes an API contract that it has no
business of changing.
That being said, if somebody claims its the application's
xvidcap deadlock backtrace 2
** Attachment added: lock2.txt
http://launchpadlibrarian.net/19121081/lock2.txt
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
xvidcap deadlock backtrace 3
** Attachment added: lock3.txt
http://launchpadlibrarian.net/19121100/lock3.txt
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
We had been anticipating a fix for this issue in time for intrepid from
libxcb upstream, but none was forthcoming. We did not have time during
intrepid to explore the option of de-enabling xcb in libx11 (it would
require changes to compiz and other things that now require it).
This bug has
Closing out the pygtk tasks; there was never evidence presented that it
has any relation to this bug. If you feel there's an xcb issue in
pygtk, please file a new bug.
** Changed in: pygtk (Ubuntu Hardy)
Status: New = Invalid
--
hardy, locking assertion failure, xorg/libsdl
how is this issue a pygtk one?
** Changed in: pygtk (Ubuntu Intrepid)
Importance: Undecided = Low
Status: New = Incomplete
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Hiya -
Just to confirm, the noxcb deb files above allowed python-pyxine to work
properly on hardy, where previously it had suffered a hard lockup just
after creating the display visual object and spawning the X event thread
on roughly 95% of attempts. This was tested on machines with Intel and
Hello,
this setting had no visible influence in my case.
(Hardy, 64 Bit)
Christian
Colin Watson wrote:
Could those people reporting problems over the last half-dozen comments
or so please confirm whether the workaround Bryce posted works? Many
people have not mentioned this at all.
Sorry to add to the confusion Yes I have a /usr/share/icons/ folder but I do
not have a /usr/share/icons/customicons folder. I am running Hardy, AMD64.
Setting the export LIBXCB_ALLOW_SLOPPY_LOCK=1
produces:
Unable to load image-loading module:
OK that l3232 is a typo. A result of you running the sed fix for
64bit. I did not have to run that fix on hardy 64bit fresh install.
that l3232 is supposed to be l32 in the sed fix so it should be
/usr/l32/gtk.
--
hardy, locking assertion failure, xorg/libsdl
Could those people reporting problems over the last half-dozen comments
or so please confirm whether the workaround Bryce posted works? Many
people have not mentioned this at all.
export LIBXCB_ALLOW_SLOPPY_LOCK=1
(Note that of course this has to be run in a terminal before starting
the
I tried the export LIBXCB_ALLOW_SLOPPY_LOCK=[1|true] thing to no avail,
just as some others have reported previously.
As for the -noxcb packages, I got a violation fault with them.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug
the hardy package already uses sloppy locking by default, so the
environment value does nothing.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Colin, for me, only the non-xcb libx11 packages seemed to help.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in ubuntu.
--
desktop-bugs
I would like to fix vmware in /usr/lib/vmware/lib/wrapper-gtk24.sh so
could Adam Fonseca say what the changes are?
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Here is what I found out that was causing VMWARE console to crash with
this bug in Hardy. I had a broken icon set. The default folder icons
in gnome had broken links. After fixing the links this bug
disappeared. If you run into this bug while starting the VMWARE
Console then switch to the
No this is not my problem. I switched to Human with no difference. Also,
I do not have custom icons and no directory /usr/share/icons like
Andy's.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member
I used this to install VMware on a fresh install
http://www.howtoforge.com/installing-vmware-server-on-ubuntu-8.04
When I installed the custom icon set I got the bug starting vmware both on
64bit and 32bit systems. On all the systems when I switch back to human
VMware Console starts up fine.
the problem and verify a solution.
Let me know if you haven't received the test program and I will send you
a copy.
Regards
Tom
--- On Thu, 11/9/08, Colin Watson [EMAIL PROTECTED] wrote:
From: Colin Watson [EMAIL PROTECTED]
Subject: [Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl
The libx11-noxcb library does fix this problem for vmware. The vmware
startup scripts destroy any changes to LD_LIBRARY_PATH though, so it is
not sufficient to add the LD_LIBRARY_PATH override to libx11-noxcb. You
have to add the path later in the vmware startup scripts. I do it in
Dear Bryce,
Thanks for your hard work and the temporary workaround with the non-xcb
libx11.
Unfortunately the problem is real and hurting and needs a proper fix for
Hardy. I have come across a number of trusted old applications which
fail in a similar way when running with the xcb based libx11
Hello Bryce,
this is (again) the transcript from the proprietary CAD Application I
can not use anymore:
ic: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int)
((xcb_req) - (dpy-request)) = 0)' failed.
Aborted
Attached is the complete strace -f transcript.
Hope this helps.
Let me
@Bryce: Of course you're right, the xcd/xcb thing was an unfortunate
mental glitch on my part.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk
The last several comments is doing nothing at all to help the case of
those wishing to revert libx11. Still no data about *specific* apps
with *specific* problems (backtraces or at least stderr msgs) are NOT
being posted to this bug report. If problems are so pervasive, then I
would expect it to
I hit this bug recently using the player/stage robot simulator [1].
Although the main GUI works okay, the amcl driver debug GUI will cause
player to crash with the familiar locking assertions. I think that
player/stage uses XCD through the C binding.
I know the above description is not totally
Btw, this bug is about XCB not XCD.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in ubuntu.
--
desktop-bugs mailing list
I'm having this bug while trying to run a small pyqt application that
uses threads.
python: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assert `((int)
((xcb_req) - (dpy-request)) = 0)' failed.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this
Bryce, thanks for the update.
I'm glad that some fixes are being deployed in Intrepid, but I just wish
some of them would be backported to this LTS release. There doesn't seem
to be to much confidence about these Java fixes, never mind not even
knowing (ETA) about when the real fixes could be
Is this bug Fixed yet.It like most other high visibilty bugs in
Hardy have been going on for way too long. This is pathetic. One
cannot run vmware console on HARDY..What gives? Does no one at
Canonical CARE? This bug along with the DVD read bug and the pulse
audio bugs have been since
I tried the solution knarf posted
here is the command i type.
LD_LIBRARY_PATH=/opt/LIBx11-noxcb/lib:$LD_LIBRARY_PATH vmware
I still get this
LD_LIBRARY_PATH=/opt/LIBx11-noxcb/lib:$LD_LIBRARY_PATH vmware
Locking assertion failure. Backtrace:
#0 /usr/lib32/libxcb-xlib.so.0 [0xf6f73767]
#1
I spoke with Bart Massey about this the other day, and unfortunately he
says the re-architecture work to eliminate the locking issues is delayed
and doesn't have an ETA.
However, I've word that the recent java fixes in Intrepid pretty much
resolve this issue now. I'd love hearing any
OK, tested and work perfect.
This solves all my problems with Cinelerra CV. (and I can enable Compiz)
:-)
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
A good temporary solution to these problems is to copy Bryce's noxcb
version of libx11 to a separate directory which you then prepend to
LD_LIBRARY_PATH before starting problematic apps. A simple if somewhat
hackish way to do that goes like this:
# go to your home directory, get the package,
Bryce, thanks for the update and your good work on the issue. Keeping
the community in the loop is one reason why I'm glad I switched over to
Ubuntu back when I did, even if it means tripping over an odd bug or
two.
I really hope Canonical decides to unroll the xcb stuff in libX11 (and
perhaps
i was with jre 1.5, and i tried to do those things... and nothing worked for
me, after i removed 1.5 and installed 1.6 everything is working fine.
anyway thanks for the advices.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug
PS re WONT FIX - this must be a severity 1/2 problem since it breaks
some many applications.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in
I am getting the problem in eclipse ide. with jdk5 and 6, I knocked up
this quick script to zap all ...
#!/bin/bash
sos=`locate libmawt.so`
for SO in $sos ; do
dir=`dirname $SO`
# make copy of original
if [ ! -f $dir/libmawt.so.old ]; then
cp $SO $dir/libmawt.so.old
fi
Hi folks,
I tried to install the libraries from
http://people.ubuntu.com/~bryce/Testing/libx11/
... so far everything is working again !!! Great !
My OS is Ubuntu 8.04 (Hardy Heron) x86_64. All packages are up to date.
What does it need to verify this as a fix ?
Actually I did not have
To follow up to the above comments, as I mentioned, the specific issue
characterized on this bug - OpenOffice crashing - was resolved (it
turned out to be a xrandr heap corruption rather than a libxcb issue).
However, regarding the libxcb locking issue, I checked with upstream
about it the other
** Changed in: libxcb (Ubuntu Intrepid)
Assignee: (unassigned) = Bryce Harrington (bryceharrington)
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Please note that the problem is triggered in stable applications which
have been running correctly for many years on many platforms including
*BSD, Solaris and Linux. The problem is clearly not in the application,
but in XCB. One example of a non-fatal fault in Desktop CYBER is below:
Locking
This bug affects a large number of programs written using xlib. Why is
the status won't fix?
Thanks
Tom
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I totally agree. I can not run my main Application to create IC-Layouts
and Schematics...
LTS Hardy is therefor not a platform for such professional
applications.. :-( ... what a pitty...
Chris
Alex Demko wrote:
Dang, is compiz the only major application that needs both X11 and xcb?
I'm marking the libxcb bug won't fix for hardy because a) the only
libxcb fix we can deploy at this point would be to disable libxcb
entirely - with the side effect of disabling compiz for everyone (c.f.
comment #137), and b) a viable workaround exists (c.f. comment #144).
See bug #236676 for
Hello,
this is really bad because it means the LTS Ubuntu Hardy is not usable
for serious applications.
Is there any summary about this problem? Anything one could pass to the
programmers of broken applications to fix it on the application side ?
(BTW, the subject refers libsdl. My
Dang, is compiz the only major application that needs both X11 and xcb? Because
if it is, wouldn't it make more sense to link compiz against libX11-xcb.so
and leave libX11.so be the non-xcb, stock/old/stable/working libX11?
I suggest this, as I hope you guys rethink the magnatude of the
I tried downloading and running Savage again, and it no longers produces
the original output/error. It now tells me that I need GLSL-support
instead.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a
having the same problem with openoffice
also running hardy amd64 2.6.24-19-generic
when i boot into a secondary test account that i made since OO.o went bad,
everything's fine
from my primary account i can sudo soffice and it works, but if i sudo
soffice -write i get the same locking assertion
After testing it appears I have a fix for the openoffice.org problem and
hopefully will be uploading a new version tomorrow to hardy-proposed. I
have a few other bugs to fix at the same time which I am still working
on.
Chris
--
hardy, locking assertion failure, xorg/libsdl
I marked the openoffice.org part of this bug as invalid since it is an
openoffice.org specific issue and I split out the duplicate OOo related
bugs into their own separate bug 236676.
Chris
** Changed in: openoffice.org (Ubuntu Hardy)
Status: Confirmed = Invalid
** Changed in:
Oops, scratch that. The double dashes don't do anything, except open
writer.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in ubuntu.
--
Confirmed working when following Abinoam Jr post, by commenting out the
indicated lines in /usr/lib/openoffice/program/soffice
Now, the following (in terminal) work:
openoffice
ooffice
ooffice --writer
ooffice --calc
ooffice --impress
The followng does not work:
ooffice -writer
ooffice -calc
Bryce,
the noxcb libx11 works fine but Compiz does not work anymore. Compiz
depends on libx11-xcb1. The noxcb libx11-xcb1 package contains nothing
(except the normal doc files). So compiz.real complains that it cannot
find libX11-xcb.so.1. I have tried to recompile compiz. But it complains
about
This is getting ridiculous... Why don't we simply revert this update and
try to find a solution in testing or proposed repository. This bug
affects too many people who are supposed to use a production version of
Ubuntu. I have at least twelve of my users that are complaining because
of this bug.
For the openoffice.org part of this bug I am currently building a set of
test openoffice.org debs with some new patches and will be checking to
see if it fixes the bug. Hopefully we will know by tomorrow and can get
it into hardy-updates as well.
Chris
--
hardy, locking assertion failure,
(Woops, missed that the other bug was closed and this one is the tracker
of this issue now)
It seems it has something to do with locale settings. With locale set to
en_US.UTF-8 it works, with locale setting to nl_NL.UTF-8 (I also tried
pl_PL, but also doesn't work)
openoffice.org
Just wanted to add that Bryce's libx11 files completely fixed my
problems with Pro/Engineer Wildfire 3.0. I no longer have the issues
with the menus reacting slowly and everything is extremely responsive.
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You
** Also affects: pygtk (Ubuntu)
Importance: Undecided
Status: New
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in ubuntu.
--
Installed the noxcb package. No luck, I now get a sequence lost error when i
run glx or fglrxinfo.
But some program like ume-launcher are running with the patch.
Does anyone know how to fix these sequence errors or is that just because there
is a new version of glxinfo which uses xcb?
--
Lars,
To find out what JRE openoffice.org is attempting to use look in this
file, it will be named slightly differently depending on arch.
~/.openoffice.org2/user/config/javasettings_Linux_x86.xml
Chris
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
Thanks osteenbeergen for testing that, although your comments are
ambiguous - does it function better, worse, the same as, or just
differently than before?
Since we're seeing a few issues with traces involving libxcb, I've
prepared a non-xcb-enabled libx11 here:
I'm using 8.04 amd64 with backports enabled.
openoffice from another user's account -- worked for me!
/usr/lib/openoffice/program/soffice.bin -- worked for me!
/usr/lib/openoffice/program/soffice.bin -writer -- didn't work for me!
/usr/lib/openoffice/program/soffice.bin --anything -- opens the
I mean... COMMENTING the lines in /usr/lib/openoffice/program/soffice,
like bellow:
# test for availability of the fast external splash
# if [ $sd_binary = soffice.bin -a -x $sd_prog/oosplash.bin ] ; then
# sd_binary=oosplash.bin
# fi
--
hardy, locking assertion failure, xorg/libsdl
76 matches
Mail list logo
