Fritzing crashed with SIGSEGV in QMetaObject::activate()

Bug #1077707 reported by Logan Rosen
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
fritzing (Ubuntu)
Fix Released
Medium
Georges Khaznadar

Bug Description

It is impossible to do anything in Fritzing after closing the update notification. It freezes and then eventually crashes after trying to click anything in the program. This same crash signature appears every time Fritzing crashes.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: fritzing 0.7.7b+dfsg-1
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.2-0ubuntu3
Architecture: amd64
Date: Sun Nov 11 15:23:44 2012
ExecutablePath: /usr/bin/Fritzing
InstallationDate: Installed on 2012-08-21 (82 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120821)
MarkForUpload: True
ProcCmdline: Fritzing
SegvAnalysis:
 Segfault happened at: 0x7f335d85bcb6 <_ZN11QMetaObject8activateEP7QObjectPKS_iPPv+22>: mov %rdi,0x40(%rsp)
 PC (0x7f335d85bcb6) ok
 source "%rdi" ok
 destination "0x40(%rsp)" (0x7fffd931ffd0) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: fritzing
StacktraceTop:
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 QStatusBar::messageChanged(QString const&) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 QStatusBar::hideOrShow() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 QStatusBar::messageChanged(QString const&) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
Title: Fritzing crashed with SIGSEGV in QMetaObject::activate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Logan Rosen (logan) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 QMetaObject::activate (sender=0x15c7640, m=0x7f335eb77e20, local_signal_index=0, argv=0x7fffd93200b0) at kernel/qobject.cpp:3449
 QStatusBar::messageChanged (this=<optimized out>, _t1=...) at .moc/release-shared/moc_qstatusbar.cpp:146
 QStatusBar::hideOrShow (this=0x15c7640) at widgets/qstatusbar.cpp:696
 QMetaObject::activate (sender=0x15c7640, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffd9320240) at kernel/qobject.cpp:3547
 QStatusBar::messageChanged (this=<optimized out>, _t1=...) at .moc/release-shared/moc_qstatusbar.cpp:146

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 fritzing (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Logan Rosen (logan)
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in fritzing (Ubuntu):
status: New → Confirmed
Revision history for this message
Logan Rosen (logan) wrote :

This crash is the same as the one reported here in the Fritzing forums: http://fritzing.org/forum/thread/1133/?page=all

It appears to be due to an incompatibility between the version of Fritzing in the Ubuntu/Debian repositories and Qt 4.8.3. An update of the Fritzing package to the latest version upstream will likely solve this issue.

Revision history for this message
Logan Rosen (logan) wrote :

Yep, the latest upstream version appears to eliminate this crash, after a quick test of the latest 0.7.10b binary. I have filed a request to update the packaging in Debian at [1], and I have imported that bug to Launchpad in Bug 1077716. After the packaging has been updated, this crash should go away.

Revision history for this message
Georges Khaznadar (georgesk) wrote :

The package has been updated (0.8.7b+dfsg-)

Changed in fritzing (Ubuntu):
assignee: nobody → Georges Khaznadar (georgesk)
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.