Created attachment 326212 [details, diff] libxcb-1.8.1-multithread-deadlock.patch Hi! app-emulation/emul-linux-x86-xlibs should be fixed because it have unpatched 32-bit libxcb that break latest wine as described in https://bugs.gentoo.org/show_bug.cgi?id=436780#c14 x11-libs/libxcb-1.8.1-r1 already have libxcb-1.8.1-multithread-deadlock.patch which I attach below.
As in http://www.gentoo.org/proj/en/base/amd64/emul/emul-linux-x86-20120520.xml#doc_chap14 emul-linux-x86-xlibs contain non-fixed libxcb-1.7. I hope for your decision.
This bug also affects many applications using wine. http://bugs.winehq.org/show_bug.cgi?id=31882
It seems gentoo-devs are not interested to fix this bug =(. But it's not bad for me, because I already have a fixed version app-emulation/emul-linux-x86-xlibs which I created myself.
(In reply to comment #3) > It seems gentoo-devs are not interested to fix this bug =(. But it's not bad > for me, because I already have a fixed version > app-emulation/emul-linux-x86-xlibs which I created myself. Could you share your ebuild?
(In reply to comment #4) > (In reply to comment #3) > > It seems gentoo-devs are not interested to fix this bug =(. But it's not bad > > for me, because I already have a fixed version > > app-emulation/emul-linux-x86-xlibs which I created myself. > > Could you share your ebuild? Ebuild is not custom. Tarball is custom. Here it is http://dl.dropbox.com/u/32559648/emul-linux-x86-xlibs-20120520.tar.xz
Check content of that tarball if you don't trust me.
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > It seems gentoo-devs are not interested to fix this bug =(. But it's not bad > > > for me, because I already have a fixed version > > > app-emulation/emul-linux-x86-xlibs which I created myself. > > > > Could you share your ebuild? > > Ebuild is not custom. Tarball is custom. > > Here it is > > http://dl.dropbox.com/u/32559648/emul-linux-x86-xlibs-20120520.tar.xz How did you do that? Compile libxcb-1.8.1-r1 (with deadlock patch) and put into tarball? I just want do the same for me.
(In reply to comment #3) > It seems gentoo-devs are not interested to fix this bug =(. But it's not bad > for me, because I already have a fixed version > app-emulation/emul-linux-x86-xlibs which I created myself. Yes you are right. good for you
Pacho, any chance to bump this anytime soon?
Not for now :| (I read the bug in amd64 alias... but I don't have time yet :S)
(In reply to comment #3) > It seems gentoo-devs are not interested to fix this bug =(. But it's not bad > for me, because I already have a fixed version > app-emulation/emul-linux-x86-xlibs which I created myself. I am interested and really appreciate the effort... but I am all the day at work and also some important personal problems raised past weekend and, then, I am not able to work on this yet at least until weekend (and I can't promise this weekend will be able to work on this :S)
(In reply to comment #7) > (In reply to comment #5) > > (In reply to comment #4) > > > (In reply to comment #3) > > > > It seems gentoo-devs are not interested to fix this bug =(. But it's not bad > > > > for me, because I already have a fixed version > > > > app-emulation/emul-linux-x86-xlibs which I created myself. > > > > > > Could you share your ebuild? > > > > Ebuild is not custom. Tarball is custom. > > > > Here it is > > > > http://dl.dropbox.com/u/32559648/emul-linux-x86-xlibs-20120520.tar.xz > > How did you do that? Compile libxcb-1.8.1-r1 (with deadlock patch) and put > into tarball? > I just want do the same for me. I compiled libxcb-1.8.1-r1 (which already have that patch) in Gentoo's i686 chroot by emerge -b =x11-libs/libxcb-1.8.1-r1. Then I unpack old emul-linux-x86-xlibs-20120520.tar.xz and 'replaced' libxcb*.so files with new libxcb*.so from fixed libxcb-1.8.1-r1.tbz2 (I just removed old libraries and copied new). Then packed it as same emul-linux-x86-xlibs-20120520.tar.xz. I add forcing key to generate ebuild's manifest, because it is modified tarball.
Also I replaced /var/db/pkg/x11-libs/libxcb-1.7 to /var/db/pkg/x11-libs/libxcb-1.8.1-r1 in emul-linux-x86-xlibs-20120520.tar.xz.
Created attachment 326718 [details, diff] libxcb-1.8.1-multithread-deadlock.patch Old version of attached patch is wrong and obsolete. Strange html tags, Oo. Maybe I mistakes. Added proper patch, I hope, it will not be broken after attaching.
(In reply to comment #11) > (In reply to comment #3) > > It seems gentoo-devs are not interested to fix this bug =(. But it's not bad > > for me, because I already have a fixed version > > app-emulation/emul-linux-x86-xlibs which I created myself. > > I am interested and really appreciate the effort... but I am all the day at > work and also some important personal problems raised past weekend and, > then, I am not able to work on this yet at least until weekend (and I can't > promise this weekend will be able to work on this :S) I'm understand you, you have your main work and you not obliged to fix bugs quickly. I'm just student. I don't have work because I person with disabilities. (I'm no sure how it writes properly) I have Gentoo at home as desktop Linux, it seems easier and much fits (than other binary distro like Debian/Ubuntu) for me and my demands :) So, I reports any bugs already after as I will found them.
> Ebuild is not custom. Tarball is custom. > > Here it is > > http://dl.dropbox.com/u/32559648/emul-linux-x86-xlibs-20120520.tar.xz Thank you :)
How is the correct way to install the package is there an ebuild command or a manual emerge command? I'm asking because i tried to just unpack it in the root folder and ran into an issue.
(In reply to comment #17) > How is the correct way to install the package is there an ebuild command or > a manual emerge command? I'm asking because i tried to just unpack it in the > root folder and ran into an issue. Put tarball to distfiles directory and add RESTRICT="fetch" into ebuild. Then, you should run # ebuild --force $local_overlay/app-emulation/emul-linux-x86-xlibs/emul-linux-x86-xlibs-20120520-r1.ebuild manifest
(In reply to comment #17) > How is the correct way to install the package is there an ebuild command or > a manual emerge command? I'm asking because i tried to just unpack it in the > root folder and ran into an issue. this will definitely break your system in no time
This fixed emul-linux-x86-xlibs does not fix it for me. It actually adds additional problems. Several lockups with wargamesEE and steam.
(In reply to comment #20) > This fixed emul-linux-x86-xlibs does not fix it for me. It actually adds > additional problems. Several lockups with wargamesEE and steam. I think you did something wrong, because I have not any lockup with wine-1.5.10 (and higher) with Mass Effect 3, Skyrim and other. All they runs fine. Downgrade it and wait official fixed emul-linux-x86-xlibs in portage, sorry.
(In reply to comment #16) > > Ebuild is not custom. Tarball is custom. > > > > Here it is > > > > http://dl.dropbox.com/u/32559648/emul-linux-x86-xlibs-20120520.tar.xz > > Thank you :) If you fall to some troubles too, see the comments #18 or #21. ...And remember: Binary distro like a wall of bricks to fall one and all fall off. Source distro like a wall of clay. There are no any restricts, easy to break, alter or lift back :)
As a workaround you can all use the FireBurn overlay until there is a proper solution. https://forums.gentoo.org/viewtopic-t-886398.html I've been using it for almost a year without too much trouble. That way I got my bug 405473 fixed instantly when it was (finally) committed to mesa master.
*** Bug 439890 has been marked as a duplicate of this bug. ***
New set added
