http://bugs.winehq.org/show_bug.cgi?id=12653
--- Comment #27 from Robert Wm Ruedisueli esd45@earthlink.net 2008-10-17 23:44:07 --- (In reply to comment #26)
(In reply to comment #24)
Created an attachment (id=16632)
--> (http://bugs.winehq.org/attachment.cgi?id=16632) [details] [details]
Trace on NTOSKRNL channel w/ Wine GIT~2008.10.12 on Ubuntu Linux 8.04
I obsoleted the NTDLL which includes the problem call to the kernel to the kernel traces themselves.
PLEASE READ what I said already before!!! Stop posting the same stuff over and over again. The bug I pointed to is not fixed.
Those were both the same log.
Or can you not read.
Anyways, it's still a blocker when a new bug prevents us from fixing this bug. Anyways, There was a lot of regression in 1.1.6, and I'll wait for 1.1.7 to work further.
I need to give 1.0.1 a try soon(In reply to comment #26)
(In reply to comment #24)
Created an attachment (id=16632)
--> (http://bugs.winehq.org/attachment.cgi?id=16632) [details] [details]
Trace on NTOSKRNL channel w/ Wine GIT~2008.10.12 on Ubuntu Linux 8.04
I obsoleted the NTDLL which includes the problem call to the kernel to the kernel traces themselves.
PLEASE READ what I said already before!!! Stop posting the same stuff over and over again. The bug I pointed to is not fixed.
Well, that is the current crash most people are getting, so until that bug is resolved, then that is the current "crash on startup." Could you be a little easier going and take a look from my perspective. I do not see this issue as one problem. It seems this program is hitting bug after bug. I have seen no fewer than 3 different crash causes now, all in the startup sequence. I don't think that it is unlikely that we are hitting multiple bugs.
Just because we that bug is causing the crash on 1.1.6 doesn't mean it's causing the crash on 1.1.5 ior 1.0.1. So be a little more respectful, and don't insult people's intelligence by claiming this bug has only one cause.