tora crashed with SIGSEGV in QColor::operator=()

Bug #399903 reported by Prohto
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tora (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: tora

Hi I'm running Ubuntu Karmic. After I start tora, it crash when I try to connect to a mysql database

ProblemType: Crash
Architecture: i386
Date: Wed Jul 15 15:05:22 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/tora
NonfreeKernelModules: nvidia
Package: tora 2.0.0-4build1
ProcCmdline: tora
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SegvAnalysis:
 Segfault happened at: 0x3ef1b9 <_ZN6QColoraSERKS_+9>: mov (%edx),%ecx
 PC (0x003ef1b9) ok
 source "(%edx)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tora
StacktraceTop:
 QColor::operator=(QColor const&) ()
 QsciLexer::setPaper(QColor const&, int) ()
 toHighlightedText::toHighlightedText(QWidget*, char const*)
 toWorksheetText::toWorksheetText(toWorksheet*, QWidget*, char const*) ()
 toWorksheet::setup(bool) ()
Title: tora crashed with SIGSEGV in QColor::operator=()
Uname: Linux 2.6.31-3-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev pulse scanner uucp video

Related branches

Revision history for this message
Prohto (carlos-fangmeier) 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-i386-retrace
visibility: private → public
Revision history for this message
xtknight (xt-knight) wrote :

I can reproduce it. I'll see what I can do to debug it further.

Changed in tora (Ubuntu):
assignee: nobody → xtknight (xt-knight)
status: New → In Progress
Revision history for this message
xtknight (xt-knight) wrote :

Simply rebuilding the package fixes it for me. Perhaps the one in the repositories got linked against the wrong library version?

Can you try the package in my PPA and see if it fixes your problem?

https://launchpad.net/~xt-knight/+archive/ppa/

Changed in tora (Ubuntu):
assignee: xtknight (xt-knight) → nobody
status: In Progress → Confirmed
Revision history for this message
Prohto (carlos-fangmeier) wrote :

Hi, I tested the package you said. I verified that the problem was solved.
One las question, by default tora has mysql support only?

Revision history for this message
xtknight (xt-knight) wrote :

Tora is by default built without Oracle OCI or sqlplus support, but with PostgreSQL support. Does that answer your question?

The debdiff consists of only a modification to the changelog, so this package just needs to be rebuilt.

Revision history for this message
xtknight (xt-knight) wrote :

I subscribed ubuntu-universe-sponsors so they can deal with it appropriately before Karmic's release.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package tora - 2.0.0-4build2

---------------
tora (2.0.0-4build2) karmic; urgency=low

  * No-change-rebuild to fix crash in QColor::operator (LP: #399903)
    Thanks xtknight for the hint.

 -- Andreas Moog <email address hidden> Tue, 11 Aug 2009 00:29:54 +0200

Changed in tora (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.