do-partial-upgrade crashed with SIGSEGV in pango_glyph_item_iter_next_cluster()

Bug #1044602 reported by Edward Donovan
This bug report is a duplicate of:  Edit Remove
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pango1.0 (Ubuntu)
ubuntu-release-upgrader (Ubuntu)

Bug Description

Updating Quantal today, I ran update-manager and picked 'Partial Upgrade'. It ran through its progress stages for a while, then crashed. Can't think of any other suspicious circumstances.

Apport crashed with bug 1017338 while reporting this. But the report went on to open Launchpad. I'm not totally sure what all the reported info should be, so I don't know if any was dropped. Thanks.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: ubuntu-release-upgrader-core 1:0.179
ProcVersionSignature: Ubuntu 3.5.0-13.11-lowlatency 3.5.3
Uname: Linux 3.5.0-13-lowlatency x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Fri Aug 31 20:21:56 2012
ExecutablePath: /usr/lib/ubuntu-release-upgrader/do-partial-upgrade
InterpreterPath: /usr/bin/python3.2mu
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/do-partial-upgrade --frontend=DistUpgradeViewGtk3
 PATH=(custom, no user)
 Segfault happened at: 0x7fd1cc536be9: movzbl (%rdi),%eax
 PC (0x7fd1cc536be9) ok
 source "(%rdi)" (0xaaaaaaaaaaaaab7b) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: ubuntu-release-upgrader
 ?? () from /usr/lib/x86_64-linux-gnu/
 pango_glyph_item_iter_next_cluster () from /usr/lib/x86_64-linux-gnu/
 pango_glyph_item_get_logical_widths () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
Title: do-partial-upgrade crashed with SIGSEGV in pango_glyph_item_iter_next_cluster()
UpgradeStatus: Upgraded to quantal on 2012-06-14 (78 days ago)


Revision history for this message
Edward Donovan (edward.donovan) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1026891, 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.

tags: removed: need-amd64-retrace
Revision history for this message
Edward Donovan (edward.donovan) wrote :

Ugh, I hate private master bugs.

(I like the retracer, though. :)

description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers