Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#8575 - libxcb and libxcb-no-assert-on-lock.patch
Attached to Project:
Arch Linux
Opened by Sébastien (sebcactus) - Thursday, 08 November 2007, 17:19 GMT
Last edited by Alexander Baldeck (kth5) - Friday, 09 November 2007, 12:52 GMT
Opened by Sébastien (sebcactus) - Thursday, 08 November 2007, 17:19 GMT
Last edited by Alexander Baldeck (kth5) - Friday, 09 November 2007, 12:52 GMT
|
DetailsDescription:
The new libxcb is not using the libxcb-no-assert-on-lock.patch anymore. This patch is useful for certain softwares (e.g. MATLAB) on x86_64 Even if the problem comes from the later, it would be good to use it. However I don't experience the problem on my desktop (i686) Additional info: * libxcb 1.1-1 Steps to reproduce: Run Matlab 7.3.0.298 (R2006b) on a x86_64 machine with the new libxcb 1.1-1. |
This task depends upon
Closed by Alexander Baldeck (kth5)
Friday, 09 November 2007, 12:52 GMT
Reason for closing: Won't fix
Additional comments about closing: dublicate of FS#8521
Friday, 09 November 2007, 12:52 GMT
Reason for closing: Won't fix
Additional comments about closing: dublicate of
* http://suseforums.net/index.php?showtopic=39734
Or
* recompile libxcb by applying the libxcb-no-assert-on-lock.patch (have to modify it a bit though, but very easy)