vbetool crashed with signal 5 in LRMI_int()

Bug #127802 reported by Jeroen Maris
6
Affects Status Importance Assigned to Milestone
vbetool (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: vbetool

I started Ubuntu and Apport reported that a problem was detected. In fact, nothing malfunctioned, I hadn't started any application yet.

ProblemType: Crash
Architecture: i386
Date: Mon Jul 23 17:01:05 2007
Dependencies:
 libgcc1 1:4.2.1-0ubuntu1
 libx86-1 0.99-1.2
 gcc-4.2-base 4.2.1-0ubuntu1
 zlib1g 1:1.2.3.3.dfsg-5ubuntu1
 libc6 2.6-2ubuntu2
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/sbin/vbetool
NonfreeKernelModules: nvidia
Package: vbetool 1.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: vbetool vgamode set 3
ProcCwd: /usr/lib/hal/scripts
ProcEnviron: PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/lib/hal:/usr/lib/hal/scripts:/usr/bin:/usr/bin/X11
Signal: 5
SourcePackage: vbetool
StacktraceTop:
 ?? () from /lib/libx86.so.1
 ?? () from /lib/libx86.so.1
 ?? ()
 ?? () from /lib/ld-linux.so.2
 LRMI_int () from /lib/libx86.so.1
Title: vbetool crashed with signal 5 in LRMI_int()
Uname: Linux Nemo 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux
UserGroups:

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

StacktraceTop:run_vm86 () at lrmi.c:526
LRMI_int (i=16, r=0xbfb5ecec) at lrmi.c:844
do_vbe_service (AX=3, BX=0, regs=0xbfb5ecec) at vbetool.c:158
do_set_mode (mode=3, vga=1) at vbetool.c:373
main (argc=65535, argv=0xbfb5ee04) at vbetool.c:104

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Данило Шеган (danilo) wrote :

Is this not the duplicate of bug 132353 (or vice versa)?

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.