[Bug 1816415] [NEW] gjs-console crashed with SIGSEGV in g_socket_receive_message_with_timeout()

Launchpad Bug Tracker 1816415 at bugs.launchpad.net
Wed Mar 6 22:26:54 UTC 2019


You have been subscribed to a public bug:

https://errors.ubuntu.com/problem/434b8b4abd971c7f84ca824ef5878a00d547753a
https://gitlab.gnome.org/GNOME/gjs/issues/227

---

I have performance problems, after updating.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gjs 1.54.3-1build1
Uname: Linux 5.0.0-050000rc6-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 18 07:39:11 2019
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2018-12-02 (77 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: gjs /home/username/.local/share/gnome-shell/extensions/gsconnect at andyholmes.github.io/service/daemon.js
SegvAnalysis:
 Segfault happened at: 0x7f224b1fafd8:	mov    (%r15),%edx
 PC (0x7f224b1fafd8) ok
 source "(%r15)" (0xfff9800000000002) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gjs
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_socket_receive_message () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ?? () from /usr/lib/libgjs.so.0
Title: gjs-console crashed with SIGSEGV in g_socket_receive_message()
UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

** Affects: glib2.0 (Ubuntu)
     Importance: High
     Assignee: Andrea Azzarone (azzar1)
         Status: In Progress


** Tags: amd64 apport-crash disco third-party-packages
-- 
gjs-console crashed with SIGSEGV in g_socket_receive_message_with_timeout()
https://bugs.launchpad.net/bugs/1816415
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to glib2.0 in Ubuntu.



More information about the foundations-bugs mailing list