@xatt11 Please don't change the bug status if you don't understand what it means. As per the numerous comments, this is not actually a bug in chromium, but in eglibc, which is why the correct status for the chromium package for this bug is "Invalid".
@xatt11 Please don't change the bug status if you don't understand what it means. As per the numerous comments, this is not actually a bug in chromium, but in eglibc, which is why the correct status for the chromium package for this bug is "Invalid".