ubiquity-dm crashed with SIGSEGV in PyObject_Vectorcall()

Bug #2009607 reported by Bernard Stafford
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Edubuntu 23.04 Daily Build 20230307 Ubiquity crashed during QA Testing.
Firefox crashed during this bug report, then reloaded info sent to Firefox.
Installed in Virtual Box.

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: ubiquity 23.04.4
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.480
Date: Tue Mar 7 14:23:08 2023
ExecutablePath: /usr/bin/ubiquity-dm
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/edubuntu.seed maybe-ubiquity quiet splash ---
InterpreterPath: /usr/bin/python3.11
LiveMediaBuild: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 (20230307)
ProcCmdline: /usr/bin/python3 /usr/bin/ubiquity-dm vt1 :0 ubuntu /usr/bin/ubiquity --greeter --only
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
PythonDetails: N/A
SegvAnalysis:
 Segfault happened at: 0x4f754a: mov 0x8(%rax),%rdx
 PC (0x004f754a) ok
 source "0x8(%rax)" (0x4678280d813b9af4) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: ubiquity
StacktraceTop:
 ?? ()
 PyObject_Vectorcall ()
 _PyEval_EvalFrameDefault ()
 ?? ()
 PySequence_Tuple ()
Title: ubiquity-dm crashed with SIGSEGV in PyObject_Vectorcall()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:

Revision history for this message
Bernard Stafford (bernard010) wrote :
information type: Private → Public
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 Py_TYPE (ob=0x4678280d813b9aec) at ../Include/object.h:133
 Py_IS_TYPE (type=0x95fb20 <PyBytes_Type>, ob=0x4678280d813b9aec) at ../Include/object.h:150
 PyObject_TypeCheck (type=0x95fb20 <PyBytes_Type>, ob=0x4678280d813b9aec) at ../Include/object.h:263
 descr_check (obj=0x4678280d813b9aec, descr=0x7fa78d697fb0) at ../Objects/descrobject.c:94
 method_check_args (kwnames=0x0, nargs=2, args=0x7fa78db22a30, func=0x7fa78d697fb0) at ../Objects/descrobject.c:285

tags: removed: need-amd64-retrace
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2009607

tags: added: iso-testing
Revision history for this message
Bernard Stafford (bernard010) wrote (last edit ):

2nd install Edubuntu passed.
3rd install Edubuntu bootloader failed.
Daily Build 20230307 QA Testing.
Including screenshot of bootloader failure.
Used automatic install entire disk method.
All testing using same download.

Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!

Changed in ubiquity (Ubuntu):
status: New → Invalid
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.