Community Packages

Please read this before reporting a bug:

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#39597 - [TeamViewer9] lib32-glibc problem with Intel haswell processors

Attached to Project: Community Packages
Opened by Prabu (prabuselva) - Sunday, 23 March 2014, 07:30 GMT
Last edited by Jan Alexander Steffens (heftig) - Sunday, 04 May 2014, 15:06 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Florian Pritz (bluewind)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


It seems that the lib32-glibc is compiled with --enable-lock-ellision flag in PKGBUILD. This flag has problems with Intel 4th Gen Haswell processors. Because of this, I was unable to use the latest Teamviewer9 in my system. Also the Anjuta crashes often with pthread_mutex lock problem.

If --enable-lock-ellision is not much significant, then I suggest it to be removed from the configure cmd in the PKGBUILD.
Compiling the glibc library without that flag resolved all the startup issues with Teamviewer9 and Anjuta.

This Problem has been experienced by few people as discussed in the forum

Additional info:
* package version(s) - lib32-glibc-2.19-3.tar.gz
* config and/or log files etc.

Steps to reproduce:
1) All the below steps need to be performed only in Intel 4th Generation Processor(Haswell Architecture)**.
2) Use the package in the Arch community repository. Try to Start Teamviewer 9. It will never show up.
3) Also start Anjuta and try to build a hello world autotools project. It will crash when the autogen package tries to configure the package

1) As Holoduke mentioned in the above forum, I recompiled the lib32-glibc without the enable-lock-ellision flags. Now all the problems seems to be resolved.
2) My recompiled version of lib32-glibc can be downloaded from
3) I compiled using the same PKGBUILD from community repo but removed the enable-lock-ellision flag from the build configuration.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Sunday, 04 May 2014, 15:06 GMT
Reason for closing:  Upstream
Additional comments about closing:  Not our bug
Comment by Allan McRae (Allan) - Sunday, 23 March 2014, 10:36 GMT
File bug reports about the broken packages with details of how to replicate the crash and a backtrace. This is probably not a glibc issue.
Comment by Prabu (prabuselva) - Sunday, 23 March 2014, 10:55 GMT
Hi Allan,
yeah I know it is not glibc issue. This is my first bug post in Archlinux bug tracking system. Can you guide me on how to report this issue to the package maintainer of lib32-glibc. So that future updates of this package may not break my system again. I have provided the steps for reproducing the crash. Should I need to provide more details about the crash?
Comment by Allan McRae (Allan) - Sunday, 23 March 2014, 11:02 GMT
The maintainer of lib32-glibc does not need to know about this bug as it is not a lib32-glibc issue. The developers of TeamViewer9 do.
Comment by Alexander F. Rødseth (xyproto) - Saturday, 12 April 2014, 18:13 GMT
Prabu, please report this to the TeamViewer9 developers and, if desired/possible, add a link here to the upstream bug report.
Comment by Alexander F. Rødseth (xyproto) - Sunday, 04 May 2014, 12:10 GMT
Maintainers of lib32-glibc:
If --enable-lock-ellision should not be removed from the lib32-glibc PKGBUILD, please close this as ie. "upstream".