vbetool crashed with SIGFPE

Bug #192317 reported by emk2203
104
This bug affects 8 people
Affects Status Importance Assigned to Milestone
vbetool (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: vbetool

Hardy Heron alpha 4, error was also in Gutsy Gibbon

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Feb 15 22:55:41 2008
Dependencies:
 libgcc1 1:4.2.3-1ubuntu2
 libx86-1 0.99-1.2ubuntu2
 gcc-4.2-base 4.2.3-1ubuntu2
 zlib1g 1:1.2.3.3.dfsg-7ubuntu1
 libc6 2.7-5ubuntu2
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/sbin/vbetool
NonfreeKernelModules: nvidia ath_hal
Package: vbetool 1.0-1.1
PackageArchitecture: i386
ProcCmdline: /usr/sbin/vbetool post
ProcCwd: /usr/lib/hal/scripts
ProcEnviron:
 PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/lib/pm-utils/bin
 LC_COLLATE=C
Signal: 8
SourcePackage: vbetool
StacktraceTop:
 ?? () from /lib/libx86.so.1
 ?? () from /lib/libx86.so.1
 ?? ()
 ?? () from /lib/ld-linux.so.2
 ?? () from /lib/libx86.so.1
Title: vbetool crashed with SIGFPE
Uname: Linux OptiGX260 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux
UserGroups:

Tags: apport-crash
Revision history for this message
emk2203 (emk2203) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:run_vm86 () at lrmi.c:526
LRMI_call (r=0xbf9656b0) at lrmi.c:797
do_real_post (pci_device=256) at vbetool.c:201
do_post () at vbetool.c:225
main (argc=0, argv=0xbf9657e4) at vbetool.c:115

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in vbetool:
importance: Undecided → Medium
Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

visibility: private → public
Changed in vbetool (Ubuntu):
status: New → Incomplete
Revision history for this message
Monkey (monkey-libre) 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 vbetool (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.