software-center crashed with SIGSEGV in FcFontRenderPrepare()

Bug #676834 reported by Praveen B
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: software-center

I tried to search for openoffice in Xubuntu software center and that application crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: software-center 3.0.4
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Thu Nov 18 17:27:03 2010
ExecutablePath: /usr/share/software-center/software-center
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Xubuntu 10.10 "Maverick Meerkat" - Release i386 (20101008.1)
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x5ad7d8: mov (%edx),%ecx
 PC (0x005ad7d8) ok
 source "(%edx)" (0x0d000004) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: software-center
StacktraceTop:
 ?? () from /usr/lib/libfontconfig.so.1
 FcFontRenderPrepare () from /usr/lib/libfontconfig.so.1
 FcFontMatch () from /usr/lib/libfontconfig.so.1
 ?? () from /usr/lib/libpangoft2-1.0.so.0
 ?? () from /usr/lib/libpangoft2-1.0.so.0
Title: software-center crashed with SIGSEGV in FcFontRenderPrepare()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Praveen B (bhamidipati-praveen) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 FcValueCanonicalize (v=0xd000004) at fcpat.c:75
 IA__FcFontRenderPrepare (config=0x8fc87f0, pat=0x972b920,
 IA__FcFontMatch (config=0x8fc87f0, p=0x972b920,
 pango_fc_fontset_get_font_at (fontset=0x98c39b8,
 pango_fc_fontset_foreach (fontset=0x98c39b8,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in software-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* what specific steps should we take to recreate this bug?
* Could you please provide the output from running "software-center --debug"

This will help us to find and resolve the problem.

Changed in software-center (Ubuntu):
status: New → Incomplete
Revision history for this message
Praveen B (bhamidipati-praveen) wrote :

I was running Xubuntu 10.10 on a usb-stick (with persistence-enabled).

Here is what I remember to have done.

* what specific steps should we take to recreate this bug?
I have opened Software Center (via the Xfce Menu) and searched for openoffice. Then the crash occurred.

* Could you please provide the output from running "software-center --debug"
I have attached the output (but given that there was no crash this time, I am not sure if the output would really help)

I was (and am) unable to reproduce the defect after the first time it happened.

Let's close this defect. If I see the crash again, I will re-open it with additional information (such as running software-center --debug and attaching the output).

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in software-center (Ubuntu):
status: Incomplete → Invalid
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.