gjs-console crashed with SIGSEGV in g_main_dispatch()

Bug #1966556 reported by Rafael Martines
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gjs (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

gjs-console crashed with SIGSEGV in g_main_context_dispatch()

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gjs 1.72.0-1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 26 13:33:01 2022
Disassembly: => 0x0: Não é possível acessar a memória no endereço 0x0
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2022-03-20 (6 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
ProcCmdline: /usr/bin/gjs /usr/share/gnome-maps/org.gnome.Maps --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x0: Não é possível acessar a memória no endereço 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
 source "0x0" (0x00000000) not located in a known VMA region (needed readable region)!
SegvReason:
 executing NULL VMA
 reading NULL VMA
Signal: 11
SourcePackage: gjs
StacktraceTop:
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libedataserver-1.2.so.26
Title: gjs-console crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
Rafael Martines (rafael-martines) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_main_dispatch (context=0x562cd8c07920) at ../../../glib/gmain.c:3417
 g_main_context_dispatch (context=0x562cd8c07920) at ../../../glib/gmain.c:4135
 g_main_context_iterate.constprop.0 (context=context@entry=0x562cd8c07920, block=block@entry=0, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4211
 g_main_context_iteration (context=0x562cd8c07920, may_block=may_block@entry=0) at ../../../glib/gmain.c:4276

tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_main_dispatch (context=0x562cd8c07920) at ../../../glib/gmain.c:3417
 g_main_context_dispatch (context=0x562cd8c07920) at ../../../glib/gmain.c:4135
 g_main_context_iterate.constprop.0 (context=context@entry=0x562cd8c07920, block=block@entry=0, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4183
 g_main_context_iteration (context=0x562cd8c07920, may_block=may_block@entry=0) at ../../../glib/gmain.c:4276

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gjs (Ubuntu):
importance: Undecided → Medium
summary: - gjs-console crashed with SIGSEGV in g_main_context_dispatch()
+ gjs-console crashed with SIGSEGV in g_main_dispatch()
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gjs (Ubuntu):
status: New → Confirmed
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.