eboard and other chess clients freeze my machine

Bug #225420 reported by Smeagal
4
Affects Status Importance Assigned to Milestone
eboard (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: eboard

This behavior is so weird and so nasty at the same time, but i have no way to figure it out yet.

If i play some real fast chess games ("blitzen") over the Internet at fics with eboard (or knights, winboard)
potentially my machine freezes, like a hard crash. But it is unpredictable.
Reset button then is the only option i have, no Ctrl+Alt+F1, nothing works.
I have this since Feisty (x86-32), did a clean install of Gutsy (x86-32) and updated to Hardy (x86-32) recently,
sadly the problem is still there.
There is nothing (!) under /var/log nor in .xsession_error, it is like the crash didnot happen.
Other things i tried:
- turning of Cool&Quiet - could have been related to powernow
- changeing my network card (perhaps IRQ poblems?)
- interference of other programms - so pure kde and eboard
- eboard with/without timeseal
- other clients like winboard, knights
- using a ps2 mouse instead of my usb-mouse

Sadly, it had no effect on the freezes. Is fics sending strange ip-packets, that could kill my pc?
If this crash happens, like it happened a few minutes ago, and i am listening to music with amarok,
it stutters for about 3 times in a loop and then dies completly.

Any hint what is causing the freezes or how to prevent them, is greatly appreciated.

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Are you still affected from this bug? Can't reproduce this bug on the latest Ubuntu version. Thank you for telling me!

Changed in eboard (Ubuntu):
status: New → Incomplete
Revision history for this message
Smeagal (smeagal) wrote :

No, this bug doesn't affect me anymore. Everything works fine here now.

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Thank you for your response. I'll mark the bug as fixed.

Changed in eboard (Ubuntu):
status: Incomplete → Fix Released
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.