https://bugzilla.novell.com/show_bug.cgi?id=741021
https://bugzilla.novell.com/show_bug.cgi?id=741021#c8
--- Comment #8 from Raymond Wooninck 2012-01-13 13:35:38 UTC ---
The troubles started this Monday while I was preparing a new snapshot of
Chromium. Updating from cartman's nightly build repo didn't resolve the issue
and then we started the whole debugging session on Wednesday.
In total this has a very strange behavior. If I update Chromium, then it is
working, but after a reboot Chromium causes the segfaults. However this is also
not a consistent behavior as that 1 out of 10 times, Chromium is starting
normally. Running Chromium under gdb works fine and no sign of any segmentation
fault. Running under Valgrind I see the same behavior, however I managed once
or twice to get the segmentation fault, which lead to the attached logfile. I
even tried the latest glibc from Base:Systems (as indicated by cartman), but
that didn't help. Only after switching to nscd from glibc, I managed to get a
consistent situation again where Chromium starts up normally. The same as I see
now with the reverted patch from Andreas's home project.
I don't know if there is anything related with regards to running either KDE or
Gnome. However I have heard also in the #opensuse-kde IRC channel that another
user has to remove a certain LD_ environment variable from /usr/bin/startkde,
otherwise he is getting also a couple of segfaults during startup of KDE.
All in all, it seems that the new glibc 2.15 version is causing for some
inconsistent behavior which seems to depend on hardware, setup, etc.
Let me know whatever information you require as that you cannot reproduce the
issue.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.