audacity crashed with SIGSEGV, wxWindows-related?

[ExecutorElassus]

Binary package hint: audacity

This is an updated bug report (I thought it was as described in Bug#104879, but apparently not. This appears to be a wxWindows-related crash, but I can't say for sure.

Thanks for the help,

EE

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Feb 13 01:00:01 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/audacity
NonfreeKernelModules: ath_hal
Package: audacity 1.3.4-1.1ubuntu1
PackageArchitecture: amd64
ProcCmdline: audacity
ProcCwd: /home/elassus
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: audacity
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: audacity crashed with SIGSEGV
Uname: Linux choriac 2.6.24-7-generic #1 SMP Thu Feb 7 00:56:31 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
SegvAnalysis:
 Segfault happened at: 0x48f44d: callq *0x88(%rax)
 PC (0x0048f44d) ok
 source "*0x88(%rax)" (0x000000b8) not located in a known VMA region (needed readable region)!
SegvReason: reading NULL VMA

[Apport retracing service (apport)]

StacktraceTop:AudacityProject::GetUpdateFlags (this=0xd62720) at Menus.cpp:1032
AudacityProject::UpdateMenus (this=0xd62720) at Menus.cpp:1151
AudacityProject::FixScrollbars (this=0xd62720) at Project.cpp:1179
TrackPanel::DoDrawIndicator (this=0x12198d0, dc=@0x7ffff3904c40)
TrackPanel::OnPaint (this=0x12198d0) at TrackPanel.cpp:1134

[LimCore (limcore)]

Audacity seems to have a lot of small bugs related to GUI, as do other wxWidgets applications...

[Frank Cheung (fcuk112)]

can you please let us know if you are still experiencing issues with 1.3.9 (karmic latest)? if you are please set the status back to NEW. thanks.

[Benjamin Drung (bdrung)]

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!