I've installed www/otter-browser. I removed ~/.config/otter to begin with a clean environment. When I try to open 'gmail.com': $ otter-browser Bus error Exit 138 The google.com works. I searched 'freebsd' and the first hit (freebsd.org): $ otter-browser load glyph failed err=6 face=0x810d09600, glyph=2798 Bus error Exit 138
Can you recompile otter with debug flags and try to get a back trace? Also what FreeBSD version? Is everything up to date? Any "gentoo-magic" in make.conf, or non-default options? I'm afraid with the information given at the moment it's impossible to guess what's going wrong.
Yes, I gave too few information but I don't know which informations do you need. FreeBSD version: 10.3-RELEASE-p16 I'm using quarterly (not latest) from the official package repository. The 'otter-browser' version is 0.9.11_1. Some time later I will recompile it with debug flags, please patient :)
I hope it helps you: (gdb) run Starting program: /usr/local/bin/otter-browser [New LWP 100358] warning: Lowest section in /usr/local/lib/libicudata.so.58 is .hash at 0000000000000120 [New Thread 811006400 (LWP 100358/otter-browser)] [New Thread 8691ed800 (LWP 100913/otter-browser)] [New Thread 8691eb400 (LWP 100912/otter-browser)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 8691eb400 (LWP 100912/otter-browser)] 0x0000000858ca089f in OBJ_obj2nid () from /lib/libcrypto.so.7 - start otter-browser - open gmail.com
(gdb) backtrace #0 0x0000000858ca089f in OBJ_obj2nid () from /lib/libcrypto.so.7 #1 0x0000000858c8bf53 in X509_TRUST_get_trust () from /lib/libcrypto.so.7 #2 0x0000000858c8ba22 in X509_check_trust () from /lib/libcrypto.so.7 #3 0x0000000858c8784a in X509_verify_cert () from /lib/libcrypto.so.7 #4 0x0000000857c5bc8d in ssl_verify_cert_chain () from /usr/local/lib/libssl.so #5 0x0000000857c35c36 in ssl3_get_server_certificate () from /usr/local/lib/libssl.so #6 0x0000000857c34900 in ssl3_connect () from /usr/local/lib/libssl.so #7 0x0000000805bfe9c7 in QSslEllipticCurve::isTlsNamedCurve () from /usr/local/lib/libQt5Network.so.5 #8 0x0000000805bf82e4 in QSslEllipticCurve::isTlsNamedCurve () from /usr/local/lib/libQt5Network.so.5 #9 0x0000000805bf932f in QSslEllipticCurve::isTlsNamedCurve () from /usr/local/lib/libQt5Network.so.5 #10 0x0000000805bed33a in QSslSocket::encryptedBytesWritten () from /usr/local/lib/libQt5Network.so.5 #11 0x00000008062938d4 in QMetaObject::activate () from /usr/local/lib/libQt5Core.so.5 #12 0x0000000805bc9b8e in QAbstractSocket::socketType () from /usr/local/lib/libQt5Network.so.5 #13 0x0000000805bd646a in QLocalServer::qt_metacall () from /usr/local/lib/libQt5Network.so.5 #14 0x000000080216e0b6 in QApplicationPrivate::notify_helper () from /usr/local/lib/libQt5Widgets.so.5 #15 0x0000000802171c09 in QApplication::notify () from /usr/local/lib/libQt5Widgets.so.5 #16 0x0000000806260ed3 in QCoreApplication::notifyInternal2 () from /usr/local/lib/libQt5Core.so.5 #17 0x00000008062b5ac6 in QEventDispatcherGlib::QEventDispatcherGlib () from /usr/local/lib/libQt5Core.so.5 #18 0x000000080951a458 in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.0 #19 0x000000080951a794 in g_main_context_pending () from /usr/local/lib/libglib-2.0.so.0 #20 0x000000080951a824 in g_main_context_iteration () from /usr/local/lib/libglib-2.0.so.0 #21 0x00000008062b517b in QEventDispatcherGlib::processEvents () from /usr/local/lib/libQt5Core.so.5 #22 0x000000080625cfa2 in QEventLoop::exec () from /usr/local/lib/libQt5Core.so.5 #23 0x00000008060a7755 in QThread::exec () from /usr/local/lib/libQt5Core.so.5 #24 0x00000008060ab21a in QThreadStorageData::finish () from /usr/local/lib/libQt5Core.so.5 #25 0x00000008075d4855 in pthread_create () from /lib/libthr.so.3 #26 0x0000000000000000 in ?? ()
Now I tried with the latest, 0.9.12 version and it seems the bug disappeared. I close this report.