Version-Release number of selected component: glib-networking-2.54.1-1.fc27 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/glib-pacrunner crash_function: JS_AbortIfWrongThread executable: /usr/libexec/glib-pacrunner journald_cursor: s=4412bf6ede71490d8fbc5d1d8188d207;i=508b5;b=33e61acea4f941fc86376b179ec8aa58;m=14391e7d8;t=55e67a4a40dad;x=726d43030e9a28aa kernel: 4.13.12-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 JS_AbortIfWrongThread at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/jsapi.cpp:5405 #1 js::DestroyContext at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/jscntxt.cpp:154 #2 JS_DestroyContext at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/jsapi.cpp:576 #3 mozjs_pacrunner::~mozjs_pacrunner at /usr/src/debug/libproxy-0.4.15-4.fc27.x86_64/libproxy/modules/pacrunner_mozjs.cpp:158 #5 libproxy::pacrunner_extension::get at /usr/src/debug/libproxy-0.4.15-4.fc27.x86_64/libproxy/extension_pacrunner.cpp:37 #6 libproxy::proxy_factory::run_pac at /usr/src/debug/libproxy-0.4.15-4.fc27.x86_64/libproxy/proxy.cpp:419 #7 libproxy::proxy_factory::get_proxies at /usr/src/debug/libproxy-0.4.15-4.fc27.x86_64/libproxy/proxy.cpp:216 #8 px_proxy_factory_get_proxies at /usr/src/debug/libproxy-0.4.15-4.fc27.x86_64/libproxy/proxy.cpp:463 #9 get_libproxy_proxies at glibproxyresolver.c:145 #10 g_task_thread_pool_thread at gtask.c:1328 Potential duplicate: bug 1506044
Created attachment 1355648 [details] File: backtrace
Created attachment 1355649 [details] File: cgroup
Created attachment 1355650 [details] File: core_backtrace
Created attachment 1355651 [details] File: cpuinfo
Created attachment 1355652 [details] File: dso_list
Created attachment 1355653 [details] File: environ
Created attachment 1355654 [details] File: exploitable
Created attachment 1355655 [details] File: limits
Created attachment 1355656 [details] File: maps
Created attachment 1355657 [details] File: mountinfo
Created attachment 1355658 [details] File: open_fds
Created attachment 1355659 [details] File: proc_pid_status
Similar problem has been detected: I attempted to synchronize my GNOME Calendar. It appears to have crashed in libproxy. The crash does not appear if I disable my proxy configuration in GNOME settings. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/glib-pacrunner crash_function: JS_AbortIfWrongThread executable: /usr/libexec/glib-pacrunner journald_cursor: s=a23e45c356d2400e87124670148938f1;i=78aac;b=d1a3deec1a7441e08d0cdc7a5eb24b38;m=45f583429;t=560510a21ed01;x=f2475bc1a4374d51 kernel: 4.13.16-302.fc27.x86_64 package: glib-networking-2.54.1-1.fc27 reason: glib-pacrunner killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 13041
*** Bug 1526936 has been marked as a duplicate of this bug. ***
*** Bug 1538012 has been marked as a duplicate of this bug. ***
*** Bug 1541804 has been marked as a duplicate of this bug. ***
*** Bug 1545530 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I upgrade my OS two days ago and it problem appear. I usally use port to deploy web services right now Im using glassfish5, before the cras it was working well but now I cannot start the server running "asadmin start-domain" I get this error "There is a process already using the admin port 4848 -- it probably is another instance of a GlassFish server. Command start-domain failed" but there is any aplication using that port. Also. I was seen and the network service is not running, it status is ● network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network; generated; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2018-03-06 14:03:41 EST; 1min 37s ago Docs: man:systemd-sysv-generator(8) Process: 1057 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE) CPU: 1.484s Mar 06 14:03:41 Juancho systemd[1]: network.service: Control process exited, code=exited status=1 Mar 06 14:03:41 Juancho systemd[1]: Failed to start LSB: Bring up/down networking. Mar 06 14:03:41 Juancho systemd[1]: network.service: Unit entered failed state. Mar 06 14:03:41 Juancho systemd[1]: network.service: Failed with result 'exit-code'. I have tried to use old linux core but the problem persist reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/glib-pacrunner crash_function: JS_AbortIfWrongThread executable: /usr/libexec/glib-pacrunner journald_cursor: s=ab025f867f3641cb8e64c6c6a42f9319;i=3018;b=1019b8e0fd0b412189e52b7b75518357;m=40265da4;t=566c0f17e7a27;x=218e29cb649e7856 kernel: 4.15.6-300.fc27.x86_64 package: glib-networking-2.54.1-1.fc27 reason: glib-pacrunner killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Lunch gnome-tweak-tool reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/glib-pacrunner crash_function: JS_AbortIfWrongThread executable: /usr/libexec/glib-pacrunner journald_cursor: s=7f5f62cf60e542f28f531d8704cae651;i=306373;b=8076ef5139774c6096788461089a4009;m=2b79ff9887;t=567724575cd68;x=d9be2572d6b20c9b kernel: 4.15.7-300.fc27.x86_64 package: glib-networking-2.54.1-1.fc27 reason: glib-pacrunner killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** This bug has been marked as a duplicate of bug 1538698 ***
*** This bug has been marked as a duplicate of bug 1459779 ***
*** Bug 1598827 has been marked as a duplicate of this bug. ***