[apport] vbetool crashed with signal 5

Bug #83170 reported by jkuhnert
108
Affects Status Importance Assigned to Milestone
vbetool (Ubuntu)
Invalid
High
Unassigned

Bug Description

Binary package hint: vbetool

I had changed the power options to allow the "computer" to suspend into hibernation after 52 minutes. Assumedly that's what fu%$-ed things up.

ProblemType: Crash
Date: Sun Feb 4 00:01:56 2007
Dependencies:

ExecutablePath: /usr/sbin/vbetool
Package: vbetool 0.7-1.1
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:
 ?? ()
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 9744):
 #0 0x0804a235 in ?? ()
 #1 0x00000000 in ?? ()
UserGroups:

Revision history for this message
jkuhnert (jkuhnert) wrote :
Revision history for this message
Jyrki Pulliainen (jyrki-pulliainen) wrote :

Same behaviour found on my computer. Vbetool crashes on every login and returning from suspend

Changed in vbetool:
status: Unconfirmed → Confirmed
Revision history for this message
John Carr (johncarr) wrote :

Also having vbetool crash every time returning from suspend.

Revision history for this message
Andrew (adhenry) wrote :

me too...

HP Pavilion dv9297ea running Feisty Herd 5 amd64 with nvidia-glx driver. Suspend works, but upon resume, vbetool generates crash report. Other than that, resume works ok.

Changed in vbetool:
importance: Undecided → High
Revision history for this message
ChadScott (chad-scott) wrote :

Same here... Dell D620 on Feisty beta 1 i386 with the nvidia-glx driver.

Suspends fine, seems to resume fine except that vbetool crashes on resume.

Revision history for this message
Marcin Feder (marfed) wrote :

Same on my ASUS V6J (Intel T2400 + Nvidia 7400) Feisty with nvidia-glx. Supends witout any problem. After resume Wifi does not work. Than on reboot computer hang before restart. After next start I get this crash report .

Revision history for this message
Jeremy Visser (jeremy-visser) wrote :

Crash here, with a Compaq Evo N610c (ATI Radeon) laptop. Suspends fine, but does not resume. Hibernate works, but boots up normally - doesn't resume. On next boot, I get a crash dialog.

Revision history for this message
kurbacik (varlott1-deactivatedaccount) wrote :

Every time I log in to the root account I get this announcement of a vbetool crash. I use amd64 version of Edgy Eft on a HP ZV5000 laptop.

Revision history for this message
Amol Karmarkar (amol-karmarkar) wrote :

Me too. Dell 1505 feisty

Revision history for this message
Alec Wright (alecjw) wrote :

Confirmed in gutsy. My .crash is attached.

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

I believe my bug #131296 is a duplicate of this bug. Please assign it if this is correct.

Revision history for this message
Zed (scientist47-xyz) wrote : My messages

This is what my messages log looks like during suspend and resume.

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

it's been 1.5 years since this bug got any attention.
is this still an issue for you guys? could you please try with the latest versions of ubuntu?
thank you

Changed in vbetool (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jeremy Visser (jeremy-visser) wrote : Re: [Bug 83170] Re: [apport] vbetool crashed with signal 5

On Sun, Apr 19, 2009 at 12:59 AM, Dimitrios Symeonidis
<email address hidden> wrote:
> it's been 1.5 years since this bug got any attention.
> is this still an issue for you guys?

To be honest, I don't even remember participating in this bug in the
first place, and evidently haven't had any problems since. Bug is
probably too vague for further investigation anyway.

Buy Intel. It suspends reliably (in relative terms).

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

thank you jeremy. is this an issue for anyone else?

Revision history for this message
Vish (vish) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
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".

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.