ubuntu-hams-devel team mailing list archive

[Kamal Mostafa <kamal@xxxxxxxxxx>]

Thank you for taking the time to report this bug and helping to make Ubuntu better.  We would like to help resolve the problem, but we'll need some more information.  Please answer these questions:
1. Is this fldigi crash reproducible?  (Can you force it occur, or does it always happen when you use fldigi, or just under some circumstances?)
2. If so, what specific steps should we take to recreate the crash? Please be as detailed as possible.
Thanks again for reporting this.

** Changed in: fldigi (Ubuntu)
       Status: New => Incomplete

** Visibility changed to: Public

-- 
fldigi crashed with SIGSEGV in __kernel_vsyscall()
https://bugs.launchpad.net/bugs/434217
You received this bug notification because you are a member of Ubuntu
ham developers, which is subscribed to fldigi in ubuntu.

Status in “fldigi” package in Ubuntu: Incomplete

Bug description:
Binary package hint: fldigi

?

ProblemType: Crash
Architecture: i386
Date: Mon Sep 21 21:27:58 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/fldigi
Package: fldigi 3.11.4-1
ProcCmdline: fldigi
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SegvAnalysis:
 Segfault happened at: 0xcf2422 <__kernel_vsyscall+2>:	ret
 PC (0x00cf2422) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: fldigi
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 <signal handler called>
Title: fldigi crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare