http://bugs.winehq.org/show_bug.cgi?id=13296
--- Comment #4 from Jan Hoogenraad jan-winehq@h-i-s.nl 2008-05-28 16:51:55 --- Created an attachment (id=13443) --> (http://bugs.winehq.org/attachment.cgi?id=13443) Logging from Wine
Filed bug at Ubuntu under: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/235613
I just got the kernel upgrade from vmlinuz-2.6.24-16 to vmlinuz-2.6.24-17 (patch for Ubuntu Hardy). Now, the problem is less frequent. It seems that I can introduce the failure by either 1) switching electrical equipment nearby. 2) switching on the logging (as for attached file) Therefore, I think that the crash occurs after a communications / timing failure. Apparently, Hardy generates them, even with no ambient influences, where Feisty didn't.
Probably unrelated: at end of a succesful synchronisation, I now get : fixme:comm:io_control Unsupported fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for 000000c0