xjadeo crashed with SIGSEGV in FT_New_Memory()

Bug #436391 reported by Bordi
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xjadeo (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xjadeo

Description: Ubuntu karmic (development branch)
Release: 9.10

ProblemType: Crash
Architecture: amd64
Date: Wed Sep 23 05:39:39 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/xjadeo
Package: xjadeo 0.4.7-0ubuntu1
ProcCmdline: xjadeo -Q -q
ProcEnviron:
 LANG=de_CH.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.6-rt
Signal: 11
SourcePackage: xjadeo
StacktraceTop:
 ?? () from /lib64/ld-linux-x86-64.so.2
 ?? () from /lib64/ld-linux-x86-64.so.2
 FT_New_Memory () from /usr/lib/libfreetype.so.6
 FT_Init_FreeType () from /usr/lib/libfreetype.so.6
 ?? ()
Title: xjadeo crashed with SIGSEGV in FT_New_Memory()
Uname: Linux 2.6.31-5-rt x86_64
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0x7f5e6d5be209: mov %rax,0x0(%rbp,%rbx,1)
 PC (0x7f5e6d5be209) ok
 source "%rax" ok
 destination "0x0(%rbp,%rbx,1)" (0x7f5e6b910040) ok
 SP (0x7fff1ef7d5e0) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

Revision history for this message
Bordi (borderlinedancer) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Bordi (borderlinedancer)
visibility: private → public
Kees Cook (kees)
description: updated
Revision history for this message
Alessio Treglia (quadrispro) wrote :

Is this reproducible with the latest release available on Maverick?

Changed in xjadeo (Ubuntu):
status: New → Incomplete
Revision history for this message
Alessio Treglia (quadrispro) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Alessio Treglia (quadrispro) 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 xjadeo (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.