Date: Thu, 15 Jan 2015 11:05:49 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 196754] www/chromium 39.0.2171.95_3 segfaults during login with security key Message-ID: <bug-196754-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196754 Bug ID: 196754 Summary: www/chromium 39.0.2171.95_3 segfaults during login with security key Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: chromium@FreeBSD.org Reporter: rod@lpho.de Assignee: chromium@FreeBSD.org Flags: maintainer-feedback?(chromium@FreeBSD.org) Hello, I have www/chromium 39.0.2171.95_3 installed from the binary package (tried compiling it myself, but the result was the same) and it segfaults when I try to login using an account which uses a security key (Yubico Nano). While I didn't expect support for the Yubico device to work right away, the segfault was a surprise. The problem occurs even when the security key is not inserted. Logging in with an account which does not use a security key works fine. I'm rebuilding chrome now with debug option, so the core file makes more sense. >From truss: stat("/usr/share/nls/en_US.UTF-8/libc.cat",0x7fffffffdf48) ERR#2 'No such file or directory' stat("/usr/share/nls/libc/en_US.UTF-8",0x7fffffffdf48) ERR#2 'No such file or directory' stat("/usr/local/share/nls/en_US.UTF-8/libc.cat",0x7fffffffdf48) ERR#2 'No such file or directory' stat("/usr/local/share/nls/libc/en_US.UTF-8",0x7fffffffdf48) ERR#2 'No such file or directory' Segmentation fault (core dumped) write(2,"Segmentation fault (core dumped)"...,33) = 33 (0x21) read(10,0x623330,1024) = 0 (0x0) process exit, rval = 139 (I've already manually build libc.cat and it's independent from this issue). >From chrome_debug.log: [14507:396322816:0115/114800:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114800:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114801:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114814:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114843:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114843:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue [14507:396322816:0115/114843:WARNING:message_in_transit_queue.cc(18)] Destroying nonempty message queue Thanks --- Comment #1 from Bugzilla Automation <bugzilla@FreeBSD.org> --- Auto-assigned to maintainer chromium@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196754-13>