Created
October 15, 2015 15:25
-
-
Save ileonte/63b3bd0d7d9d58948d2e to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| [9322:1015/181708:ERROR:browser_main_loop.cc(189)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on. | |
| [9351:1015/181708:INFO:renderer_main.cc(200)] Renderer process started | |
| [9355:1015/181708:INFO:renderer_main.cc(200)] Renderer process started | |
| [9322:1015/181708:ERROR:nss_ocsp.cc(613)] No URLRequestContext for NSS HTTP handler. host: g2.symcb.com | |
| [9322:1015/181708:ERROR:nss_ocsp.cc(613)] No URLRequestContext for NSS HTTP handler. host: g2.symcb.com | |
| [9322:1015/181708:ERROR:nss_ocsp.cc(613)] No URLRequestContext for NSS HTTP handler. host: g1.symcb.com | |
| [9322:1015/181708:ERROR:nss_ocsp.cc(613)] No URLRequestContext for NSS HTTP handler. host: g2.symcb.com | |
| [9322:1015/181708:ERROR:nss_ocsp.cc(613)] No URLRequestContext for NSS HTTP handler. host: g2.symcb.com | |
| [9322:1015/181708:ERROR:nss_ocsp.cc(613)] No URLRequestContext for NSS HTTP handler. host: g1.symcb.com | |
| [9322:1015/181708:ERROR:nss_ocsp.cc(613)] No URLRequestContext for NSS HTTP handler. host: crl.geotrust.com | |
| [9322:1015/181710:INFO:CONSOLE(8)] "%c[GatewaySocket]", source: https://discordapp.com/assets/b6012e8d9256c489c371.js (8) | |
| The program 'discord' received an X Window System error. | |
| This probably reflects a bug in the program. | |
| The error was 'BadAtom (invalid Atom parameter)'. | |
| (Details: serial 6930 error_code 5 request_code 20 minor_code 0) | |
| (Note to programmers: normally, X errors are reported asynchronously; | |
| that is, you will receive the error a while after causing it. | |
| To debug your program, run it with the --sync command line | |
| option to change this behavior. You can then get a meaningful | |
| backtrace from your debugger if you break on the gdk_x_error() function.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment