zapping crashed with SIGSEGV

Bug #150861 reported by Lafa
6
Affects Status Importance Assigned to Milestone
zapping (Ubuntu)
Invalid
Medium
Basilio Kublik

Bug Description

Binary package hint: zapping

just trying to use the program with a pinnacel USB HD pro stick

ProblemType: Crash
Architecture: i386
Date: Tue Oct 9 01:22:01 2007
Disassembly: 0xb7c0d535:
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/zapping
NonfreeKernelModules: fglrx
Package: zapping 0.9.6-4ubuntu1
PackageArchitecture: i386
ProcCmdline: zapping
ProcCwd: /home/lafa
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/lafa/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/lafa/.local/bin
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: zapping
Stacktrace: #0 0xb7c0d535 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: zapping crashed with SIGSEGV
Uname: Linux shuttle 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Lafa (luis-alves) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Thanks in advance

Changed in zapping:
assignee: nobody → sourcercito
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) 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 zapping:
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.