mypaint

Bug #2055220 reported by Mahir
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mypaint (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

As soon as I start drawing a line, it always crashes

ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: mypaint 2.0.1-10
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 27 22:38:46 2024
ExecutablePath: /usr/bin/mypaint
InstallationDate: Installed on 2024-01-07 (52 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
InterpreterPath: /usr/bin/python3.12
ProcCmdline: /usr/bin/python3 /usr/bin/mypaint
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu1
PythonDetails: N/A
SegvAnalysis:
 Segfault happened at: 0x4df4fe: mov 0x10(%rcx),%rcx
 PC (0x004df4fe) ok
 source "0x10(%rcx)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SignalName: SIGSEGV
SourcePackage: mypaint
StacktraceTop:
 ?? ()
 PyObject_GetAttrString ()
 _PyObject_CallMethod_SizeT ()
 ?? () from /usr/lib/mypaint/lib/_mypaintlib.cpython-312-x86_64-linux-gnu.so
 process_tile_internal () from /lib/x86_64-linux-gnu/libmypaint-1.5.so.1
Title: mypaint crashed with SIGSEGV in PyObject_GetAttrString()
UpgradeStatus: Upgraded to noble on 2024-01-12 (47 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sudo users vboxusers
separator:

Revision history for this message
Mahir (mah01) wrote :
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 mypaint (Ubuntu):
status: New → Invalid
tags: removed: need-amd64-retrace
Revision history for this message
Seth Arnold (seth-arnold) wrote : Bug is not a security issue

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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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