gimp-2.8 crashed with SIGSEGV in pango_ot_info_list_scripts()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gimp (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
C'est en faisant une image (en ayant importé un calque) que GIMP a planté, je n'ai pas compris pourquoi
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gimp 2.8.20-1
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Oct 26 13:40:43 2017
ExecutablePath: /usr/bin/gimp-2.8
InstallationDate: Installed on 2017-09-01 (54 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: gimp
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fa46799f34f <pango_
PC (0x7fa46799f34f) ok
source "0x20(%r12)" (0x00000020) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gimp
StacktraceTop:
pango_
?? ()
gimp_viewable_
?? ()
gimp_viewable_
Title: gimp-2.8 crashed with SIGSEGV in pango_ot_
UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1694977, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.