Briefly: Because Debian is using kernel 3.1.x and has CONFIG_SECCOMP turned on, all attempts to call time() with the seccomp sandbox active and using a glibc old enough that it uses the vsyscall page for such calls will 'Aw, snap!' the renderer:
<http://code.google.com/p/chromium/issues/detail?id=104084> <http://code.google.com/p/seccompsandbox/issues/detail?id=17> This is fixed, but very recently... but this is likely moot since Debian doesn't turn on the seccomp sandbox. When you do, take note... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
