vbetool crashed with signal 5

[Tommy]

Binary package hint: vbetool

when i start up from suspend on compact evo n610c

ProblemType: Crash
Architecture: i386
Date: Fri Feb 15 12:56:36 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: cdrom
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: 5
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 signal 5
Uname: Linux liselotte-laptop 2.6.24-7-generic #1 SMP Thu Feb 7 01:29:58 UTC 2008 i686 GNU/Linux
UserGroups:

[Apport retracing service (apport)]

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

[Dimitrios Symeonidis (azimout)]

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.

[Shabakthanai (stevenvollom)]

On Sunday 19 April 2009 12:54:00 pm Dimitrios Symeonidis 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 changed to: Public
>
> ** Changed in: vbetool (Ubuntu)
> Status: New => Incomplete
I don't have any negative to report. I am not as experienced as I should be
using a beta, but I am, because of the components in my computer. It is quite
an advanced MB and a AMD Quad, which is not that remarkable anymore. I
couldn't even get a screen with Intrepid and changed to Jaunty as a result.

I report all bugs with the information my computer compiles. I do not always
understand what has happened and cannot comment. But in case I did not give
enough system information with the report I made, I am currently using KDE
4.2.2, Jaunty Beta, 9600 AMD Quad Core, 8gb SDRAM ECC, 9600 nvidia Gforce
w/512mb DDR3, 800W BFG Power Supply, ASUS M3N-HT Mempipe Motherboard with
nvidia 780a chip. I use the on-board 8.1 sound. I don't even know if any of
this information is important, however, on the Kubuntu Users List, I recently
read a post indicating lacking information on a bug report. Is it better if I
include all this information, or what is preferred. Also, since I am so
inexperienced, would you rather I not make reports, or are they helpful?

I really want to help and will contribute more as I learn.

Steven

[Dimitrios Symeonidis (azimout)]

Thank you Steven. Reporting any problems you face is very useful, and I encourage you to continue to do so.

Any information you include is useful. As you become more experienced, you'll learn to identify the information that is useful in resolving a bug...

Since you reported this 2 days ago, I'm switching this report back to confirmed.

Thank you, and good luck

[dino99 (9d9)]

That version has died long ago; no more supported