http://bugzilla.suse.com/show_bug.cgi?id=965738
http://bugzilla.suse.com/show_bug.cgi?id=965738#c18
--- Comment #18 from Raymond Wooninck ---
Thanks for the feedback as this confirms my suspicion.
Based on feedback and requests in the past we enabled for Chromium to build
against certain system libraries instead of the in-source versions. I never
actually enabled this for the Beta and Dev builds and therefore I couldn't
initially reproduce your issue.
As that it worked in the past, I assume that a recent update of ones of these
libraries is causing the issue to appear. In order to prevent this issue from
happening again, I will build chromium purely against the in-source libraries.
I will leave it up to you if you want to revert back to using the chromium
builds from the Leap Update repo or that you want to keep this network:chromium
repo active. Both will provide the same, except that the network:chromium
repository is always a couple of days ahead of the update repo.
Thanks for testing.
--
You are receiving this mail because:
You are on the CC list for the bug.