python3.8 crashed with signal 5 in g_object_new_with_properties()

Bug #1868244 reported by Maks on 2020-03-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python3.8 (Ubuntu)

Bug Description


ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: python3.8-minimal 3.8.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
Date: Fri Mar 20 09:41:47 2020
ExecutablePath: /usr/bin/python3.8
ProcCmdline: cinnamon-screensaver

Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
Signal: 5
SourcePackage: python3.8
 ?? () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
 g_object_new_with_properties () from /lib/x86_64-linux-gnu/
 ?? () from /usr/lib/python3/dist-packages/gi/
 ?? () from /usr/lib/python3/dist-packages/gi/
Title: python3.8 crashed with signal 5 in g_object_new_with_properties()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

Maks (makes3) wrote :

 g_settings_set_property (object=<optimized out>, prop_id=<optimized out>, value=<optimized out>, pspec=<optimized out>) at ../../../gio/gsettings.c:596
 g_object_new_internal () from /tmp/apport_sandbox_w4xv4r3z/usr/lib/x86_64-linux-gnu/
 g_object_new_with_properties () from /tmp/apport_sandbox_w4xv4r3z/usr/lib/x86_64-linux-gnu/
 pygobject_object_new_with_properties (values=0x19e66f0, names=0x19ff3b0, n_properties=1, object_type=<optimized out>) at gi/gimodule.c:1020
 pygobject_constructv (self=self@entry=0x7f5fbb106a00, n_properties=1, names=0x19ff3b0, values=values@entry=0x19e66f0) at gi/gimodule.c:1050

Changed in python3.8 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers