<?xml version="1.0" encoding="iso-8859-1"?><!-- generator="b2evolution/2.4.5" -->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>Petteri R&#228;ty - Latest comments on Do not turn on the xcb use flag if you plan on using =sun-jre-1.5*</title>
		<link>http://blogs.gentoo.org/betelgeuse?disp=comments</link>
		<description></description>
		<language>en-US</language>
		<docs>http://backend.userland.com/rss</docs>
		<admin:generatorAgent rdf:resource="http://b2evolution.net/?v=2.4.5"/>
		<ttl>60</ttl>
				<item>
			<title>In response to: Do not turn on the xcb use flag if you plan on using =sun-jre-1.5*</title>
			<pubDate>Wed, 16 Apr 2008 23:49:27 +0000</pubDate>
			<dc:creator>Hedley Robertson [Visitor]</dc:creator>
			<guid isPermaLink="false">c19805@http://blogs.gentoo.org/</guid>
			<description>Running Java on Linux has been the most frustrating experience I have had since I switched over from using Windows full time.  &lt;br /&gt;
&lt;br /&gt;
Thanks for this workaround, this solved a ton of issues for me.&lt;br /&gt;
&lt;br /&gt;
This thread: http://forums.gentoo.org/viewtopic-p-4547777.html?sid=5877773e911fcf3de235b3c31414ad26&lt;br /&gt;
&lt;br /&gt;
Has a handy little java program you can compile and run in order to test the bugfix.</description>
			<content:encoded><![CDATA[Running Java on Linux has been the most frustrating experience I have had since I switched over from using Windows full time.  <br />
<br />
Thanks for this workaround, this solved a ton of issues for me.<br />
<br />
This thread: http://forums.gentoo.org/viewtopic-p-4547777.html?sid=5877773e911fcf3de235b3c31414ad26<br />
<br />
Has a handy little java program you can compile and run in order to test the bugfix.]]></content:encoded>
			<link>http://blogs.gentoo.org/betelgeuse/2006/11/26/do_not_turn_on_the_xcb_use_flag_if_you_p_5#c19805</link>
		</item>
				<item>
			<title>In response to: Do not turn on the xcb use flag if you plan on using =sun-jre-1.5*</title>
			<pubDate>Tue, 30 Oct 2007 10:13:31 +0000</pubDate>
			<dc:creator>David [Visitor]</dc:creator>
			<guid isPermaLink="false">c19255@http://blogs.gentoo.org/</guid>
			<description>WOW! Gotta say that fixed my java problems, Thanks!!!!!!</description>
			<content:encoded><![CDATA[WOW! Gotta say that fixed my java problems, Thanks!!!!!!]]></content:encoded>
			<link>http://blogs.gentoo.org/betelgeuse/2006/11/26/do_not_turn_on_the_xcb_use_flag_if_you_p_5#c19255</link>
		</item>
				<item>
			<title>In response to: Do not turn on the xcb use flag if you plan on using =sun-jre-1.5*</title>
			<pubDate>Wed, 05 Sep 2007 14:25:39 +0000</pubDate>
			<dc:creator>Rob [Visitor]</dc:creator>
			<guid isPermaLink="false">c19044@http://blogs.gentoo.org/</guid>
			<description>You're genius my friend. This solution solved my problem with some java apps.</description>
			<content:encoded><![CDATA[You're genius my friend. This solution solved my problem with some java apps.]]></content:encoded>
			<link>http://blogs.gentoo.org/betelgeuse/2006/11/26/do_not_turn_on_the_xcb_use_flag_if_you_p_5#c19044</link>
		</item>
				<item>
			<title>In response to: Do not turn on the xcb use flag if you plan on using =sun-jre-1.5*</title>
			<pubDate>Sun, 19 Aug 2007 22:02:44 +0000</pubDate>
			<dc:creator>Stephan Sokolow [Visitor]</dc:creator>
			<guid isPermaLink="false">c19024@http://blogs.gentoo.org/</guid>
			<description>Actually, it is a Java bug. That patch just disables XCB's equivalent to segfaulting on a double-free.&lt;br /&gt;
&lt;br /&gt;
See http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373&lt;br /&gt;
&lt;br /&gt;
The gist of it is:&lt;br /&gt;
1. Java (including 1.6) is statically linked against a VERY old libXext compiled with threading off.&lt;br /&gt;
2. Java dynamically links against the modern libX11 with threading enabled and, when using the XCB version, XML-parser-like strictness.&lt;br /&gt;
3. If Java detects the Xinerama X extension, it does some calls to figure out how the Xinerama desktop is put together... which causees the problem.&lt;br /&gt;
4. The problem exists because the un-threaded libXext doesn't bother to acquire the lock but the XCB-backed threaded Xlib is then asked to release the lock and cries foul over it's equivalent of a double-free.&lt;br /&gt;
&lt;br /&gt;
To patch away XCB's strictness is like patching away XML's strictness or telling the Linux kernel to not throw segfaults if one program messes with another program's memory. You're just asking for trouble in the long run.&lt;br /&gt;
&lt;br /&gt;
According to that bug page, one of the Java people is working on solving the problem but, until they do, I'd suggest the following solution which someone on the bug page suggested instead:&lt;br /&gt;
&lt;br /&gt;
Run this sed line (adapt the path, obviously) so that Java doesn't detect Xinerama and doesn't call the problem code:&lt;br /&gt;
sed -i 's/XINERAMA/FAKEEXTN/g' /opt/sun-jdk-1.6.0.02/jre/lib/amd64/xawt/libmawt.so&lt;br /&gt;
</description>
			<content:encoded><![CDATA[Actually, it is a Java bug. That patch just disables XCB's equivalent to segfaulting on a double-free.<br />
<br />
See http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373<br />
<br />
The gist of it is:<br />
1. Java (including 1.6) is statically linked against a VERY old libXext compiled with threading off.<br />
2. Java dynamically links against the modern libX11 with threading enabled and, when using the XCB version, XML-parser-like strictness.<br />
3. If Java detects the Xinerama X extension, it does some calls to figure out how the Xinerama desktop is put together... which causees the problem.<br />
4. The problem exists because the un-threaded libXext doesn't bother to acquire the lock but the XCB-backed threaded Xlib is then asked to release the lock and cries foul over it's equivalent of a double-free.<br />
<br />
To patch away XCB's strictness is like patching away XML's strictness or telling the Linux kernel to not throw segfaults if one program messes with another program's memory. You're just asking for trouble in the long run.<br />
<br />
According to that bug page, one of the Java people is working on solving the problem but, until they do, I'd suggest the following solution which someone on the bug page suggested instead:<br />
<br />
Run this sed line (adapt the path, obviously) so that Java doesn't detect Xinerama and doesn't call the problem code:<br />
sed -i 's/XINERAMA/FAKEEXTN/g' /opt/sun-jdk-1.6.0.02/jre/lib/amd64/xawt/libmawt.so<br />
]]></content:encoded>
			<link>http://blogs.gentoo.org/betelgeuse/2006/11/26/do_not_turn_on_the_xcb_use_flag_if_you_p_5#c19024</link>
		</item>
				<item>
			<title>In response to: Do not turn on the xcb use flag if you plan on using =sun-jre-1.5*</title>
			<pubDate>Wed, 15 Aug 2007 15:55:01 +0000</pubDate>
			<dc:creator>Todd Partridge [Visitor]</dc:creator>
			<guid isPermaLink="false">c19009@http://blogs.gentoo.org/</guid>
			<description>What does the xcb USE flag do?  I see it mentioned now with the use of compiz-fusion.</description>
			<content:encoded><![CDATA[What does the xcb USE flag do?  I see it mentioned now with the use of compiz-fusion.]]></content:encoded>
			<link>http://blogs.gentoo.org/betelgeuse/2006/11/26/do_not_turn_on_the_xcb_use_flag_if_you_p_5#c19009</link>
		</item>
				<item>
			<title>In response to: Do not turn on the xcb use flag if you plan on using =sun-jre-1.5*</title>
			<pubDate>Tue, 28 Nov 2006 07:00:58 +0000</pubDate>
			<dc:creator>betelgeuse [Member]</dc:creator>
			<guid isPermaLink="false">c18473@http://blogs.gentoo.org/</guid>
			<description>I have tried 1.6 and it did not work either.</description>
			<content:encoded><![CDATA[I have tried 1.6 and it did not work either.]]></content:encoded>
			<link>http://blogs.gentoo.org/betelgeuse/2006/11/26/do_not_turn_on_the_xcb_use_flag_if_you_p_5#c18473</link>
		</item>
				<item>
			<title>In response to: Do not turn on the xcb use flag if you plan on using =sun-jre-1.5*</title>
			<pubDate>Tue, 28 Nov 2006 03:59:28 +0000</pubDate>
			<dc:creator>Brian [Visitor]</dc:creator>
			<guid isPermaLink="false">c18471@http://blogs.gentoo.org/</guid>
			<description>Apparently this patch 'solves' that problem:&lt;br /&gt;
http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/x11-libs/libxcb/xcb_xlib-no-assert-on-lock.patch&lt;br /&gt;
&lt;br /&gt;
I'm not sure how safe or correct it is, but it allows broken apps to run.</description>
			<content:encoded><![CDATA[Apparently this patch 'solves' that problem:<br />
http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/x11-libs/libxcb/xcb_xlib-no-assert-on-lock.patch<br />
<br />
I'm not sure how safe or correct it is, but it allows broken apps to run.]]></content:encoded>
			<link>http://blogs.gentoo.org/betelgeuse/2006/11/26/do_not_turn_on_the_xcb_use_flag_if_you_p_5#c18471</link>
		</item>
				<item>
			<title>In response to: Do not turn on the xcb use flag if you plan on using =sun-jre-1.5*</title>
			<pubDate>Mon, 27 Nov 2006 07:16:46 +0000</pubDate>
			<dc:creator>Jamey Sharp [Visitor]</dc:creator>
			<guid isPermaLink="false">c18469@http://blogs.gentoo.org/</guid>
			<description>&lt;p&gt;This was a bug in the open-source libXi library, which has been fixed upstream.&lt;/p&gt;

&lt;p&gt;Proprietary software considered harmful, certainly, but not actually the source of the problem this time. :-)&lt;/p&gt;</description>
			<content:encoded><![CDATA[<p>This was a bug in the open-source libXi library, which has been fixed upstream.</p>

<p>Proprietary software considered harmful, certainly, but not actually the source of the problem this time. :-)</p>]]></content:encoded>
			<link>http://blogs.gentoo.org/betelgeuse/2006/11/26/do_not_turn_on_the_xcb_use_flag_if_you_p_5#c18469</link>
		</item>
			</channel>
</rss>
