testdrive-gtk crashed with SIGSEGV in pango_context_get_base_dir()

Bug #1028956 reported by Nicholas Skaggs
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
TestDrive
Confirmed
Medium
Unassigned
testdrive (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

One time launching testdrive gave this random error upon startup.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: testdrive-gtk 3.16-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-5.5-generic 3.5.0-rc7
Uname: Linux 3.5.0-5-generic x86_64
ApportVersion: 2.4-0ubuntu5
Architecture: amd64
Date: Wed Jul 25 11:04:42 2012
ExecutablePath: /usr/bin/testdrive-gtk
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/testdrive-gtk
SegvAnalysis:
 Segfault happened at: 0x7f894951f475 <pango_context_get_base_dir+5>: mov 0x28(%rdi),%eax
 PC (0x7f894951f475) ok
 source "0x28(%rdi)" (0xaaaaaaaaaaaaaad2) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: testdrive
StacktraceTop:
 pango_context_get_base_dir () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
 pango_layout_get_pixel_extents () from /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
Title: testdrive-gtk crashed with SIGSEGV in pango_context_get_base_dir()
UpgradeStatus: Upgraded to quantal on 2012-07-20 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Nicholas Skaggs (nskaggs) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 pango_context_get_base_dir (context=0xaaaaaaaaaaaaaaaa) at /build/buildd/pango1.0-1.30.1/./pango/pango-context.c:428
 pango_layout_check_lines (layout=0x16eb6f0) at /build/buildd/pango1.0-1.30.1/./pango/pango-layout.c:3827
 pango_layout_check_lines (layout=0x16eb6f0) at /build/buildd/pango1.0-1.30.1/./pango/pango-layout.c:3788
 pango_layout_get_extents_internal (layout=0x16eb6f0, ink_rect=0x0, logical_rect=<optimized out>, line_extents=0x0) at /build/buildd/pango1.0-1.30.1/./pango/pango-layout.c:2490
 pango_layout_get_pixel_extents (layout=0x16eb6f0, ink_rect=0x0, logical_rect=0x7fff323d1500) at /build/buildd/pango1.0-1.30.1/./pango/pango-layout.c:2698

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in testdrive (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in testdrive (Ubuntu):
status: New → Confirmed
Revision history for this message
Jackson Doak (noskcaj) wrote :

I got the error after xfce4-session auto-opened the app.

Changed in testdrive:
status: New → Confirmed
importance: Undecided → Medium
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.