audacity crashed with SIGSEGV in wxAppConsole::HandleEvent()

Bug #307840 reported by Tomas Cassidy
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
audacity (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: audacity

Can't remember what I was doing when Audacity crashed. I think it happened just after I closed the dialog for exporting multiple tracks, before actually doing any exporting.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/audacity
NonfreeKernelModules: nvidia
Package: audacity 1.3.5-2
ProcAttrCurrent: unconfined
ProcCmdline: audacity
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: audacity
StacktraceTop:
 ?? ()
 ?? ()
 wxAppConsole::HandleEvent ()
 wxEvtHandler::ProcessEventIfMatches ()
 wxEventHashTable::HandleEvent ()
Title: audacity crashed with SIGSEGV in wxAppConsole::HandleEvent()
Uname: Linux 2.6.27-9-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Tomas Cassidy (tomas-cassidy) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:AudacityProject::GetUpdateFlags (this=0xa0c6240)
AudacityProject::UpdateMenus (this=0xa0c6240)
wxAppConsole::HandleEvent (this=0x9eb6198,
wxEvtHandler::ProcessEventIfMatches (entry=@0x84c5a40,
wxEventHashTable::HandleEvent (this=0x84c5660,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in audacity:
importance: Undecided → Medium
Revision history for this message
Frank Cheung (fcuk112) wrote :

Tomas, can you please let us know if you are able to reproduce this bug in 1.3.9 (karmic latest)? if yes, please set the status back to NEW. thanks.

Changed in audacity (Ubuntu):
status: New → Incomplete
Revision history for this message
Benjamin Drung (bdrung) 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 audacity (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.