check-new-release-gtk crashed with SIGSEGV in g_callable_info_free_closure()

Bug #1943812 reported by Rachel Greenham
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
New
Medium
Unassigned

Bug Description

i don't even know why but guessing possibly related to #1943809 and #1943811. this thing's going nuts on me today! :-)

ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: ubuntu-release-upgrader-gtk 1:21.10.7
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu68
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 14 10:27:20 2021
ExecutablePath: /usr/lib/ubuntu-release-upgrader/check-new-release-gtk
InstallationDate: Installed on 2021-01-17 (241 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
InterpreterPath: /usr/bin/python3.9
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release-gtk
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 SHELL=/usr/bin/zsh
 XDG_RUNTIME_DIR=<set>
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1
PythonDetails: N/A
SegvAnalysis:
 Segfault happened at: 0x7f73b55edcec <g_callable_info_free_closure+12>: mov 0x8(%rax),%rdi
 PC (0x7f73b55edcec) ok
 source "0x8(%rax)" (0x441f0f66e307) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: ubuntu-release-upgrader
StacktraceTop:
 g_callable_info_free_closure () from /lib/x86_64-linux-gnu/libgirepository-1.0.so.1
 ?? () from /usr/lib/python3/dist-packages/gi/_gi.cpython-39-x86_64-linux-gnu.so
 ?? ()
Title: check-new-release-gtk crashed with SIGSEGV in g_callable_info_free_closure()
UpgradeStatus: Upgraded to impish on 2021-07-08 (69 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
VarLogDistupgradeTermlog:

separator:

Revision history for this message
Rachel Greenham (rachel-strangenoises) wrote :
Revision history for this message
Rachel Greenham (rachel-strangenoises) wrote :

it repeats, even though the 'relaunch' checkbox is unchecked.

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_callable_info_free_closure (callable_info=0x1f43720, closure=0x7f73b4c8dfc8) at ../girepository/girffi.c:428
 pygi_arg_garray_len_arg_setup (py_arg_index=<synthetic pointer>, arg_index=<optimized out>, direction=37023248, callable_cache=0x7f73b57903a0 <g_source_callback_funcs>, type_info=0x1d968e0, arg_cache=0x1f44230) at gi/pygi-array.c:891
 pygi_arg_cache_new (type_info=0x1d968e0, arg_info=<optimized out>, transfer=<optimized out>, direction=37023248, callable_cache=0x7f73b57903a0 <g_source_callback_funcs>, c_arg_index=<optimized out>, py_arg_index=0) at gi/pygi-cache.c:377
 ?? ()

tags: removed: need-amd64-retrace
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 ubuntu-release-upgrader (Ubuntu):
importance: Undecided → Medium
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.