designer-qt4 crashed with SIGSEGV in QMetaObject::activate()

Bug #354063 reported by Niels Egberts
6
Affects Status Importance Assigned to Milestone
qt4-x11 (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: qt4-designer

I was just using designer-qt4 for a few minutes when this crash popped up. I'm using the latest beta version of Jaunty.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/designer-qt4
NonfreeKernelModules: nvidia
Package: qt4-designer 4.5.0-0ubuntu3
ProcCmdline: /usr/bin/designer-qt4
ProcEnviron:
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: qt4-x11
StacktraceTop:
 ?? () from /usr/lib/libQtDesignerComponents.so.4
 ?? () from /usr/lib/libQtDesignerComponents.so.4
 ?? () from /usr/lib/libQtDesignerComponents.so.4
 ?? () from /usr/lib/libQtDesignerComponents.so.4
 QMetaObject::activate ()
Title: designer-qt4 crashed with SIGSEGV in QMetaObject::activate()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare vboxusers

Revision history for this message
Niels Egberts (nielsegberts) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:QtVariantProperty::value (this=0x0)
qdesigner_internal::FontPropertyManager::resetFontSubProperty (this=0x2b6ac20, vm=0x2b6aab0, property=0x38ebaa0)
qdesigner_internal::PropertyEditor::slotResetProperty (this=0x2b6a070, property=0x38ebaa0)
qdesigner_internal::PropertyEditor::qt_metacall (
QMetaObject::activate (sender=0x2abc450,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in qt4-x11 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Changed in qt4-x11 (Ubuntu):
importance: Medium → Low
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version has died long ago; no more supported

Changed in qt4-x11 (Ubuntu):
status: Confirmed → 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.