http://bugs.winehq.org/show_bug.cgi?id=6000
------- Additional Comments From infyquest(a)gmail.com 2006-22-08 11:25 -------
could you please send it to wine-patches(a)winehq.org
Where we can track your patch?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6000
------- Additional Comments From popej(a)friko.onet.pl 2006-22-08 11:18 -------
Ok, I have posted propsed patch on a mailing list.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5475
------- Additional Comments From infyquest(a)gmail.com 2006-22-08 11:04 -------
The Patch has not been accepted because of following reasons:
1. The patch is missing the filename header, and cannot be applied
to the sources by running 'patch'.
2. the patch was posted with the following legal notice:
"Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited."
That tells us "You may not use this patch."
You have to post patches without that.
3. the message did not contain any license information (e.g.
Author: Renu Rajput (Tata Inc.)
Copyright 2006 Tata Inc
License: LGPL.
Adding that would help.
4. The message essentially repeated much of the bug report in bugzilla.
That's not needed. Just refer to the bug report.
Any one of the above four might have been enough to cause the
patch to be ignored. Fix them all and you've got a good shot.
Two more tips:
5. The bug report in bugzilla does not link to your proposed fix.
Often after I post a proposed fix, I add a comment to bugzilla saying
something like
"Patch sent:
http://www.winehq.org/pipermail/wine-patches/2006-July/029145.html"
Not only does this give another way for people to stumble across and
review your patch, it also helps avoid duplication of effort.
I had no idea you had sent in a patch for this bug already!
6. Patches that do not get applied need to be resent after a few days.
Every time you resend it, you should try to improve it or the test case
a bit, and make sure it still applies against current cvs or git.
Use the same subject line as before, but append "(resend)" to the end.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4776
infyquest(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From infyquest(a)gmail.com 2006-22-08 10:57 -------
the patch has been commited to git.
please raise a new bug the new issue
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6029
------- Additional Comments From the3dfxdude(a)gmail.com 2006-22-08 10:29 -------
I wonder if you compiled wine yourself, that you need the 2.6 kernel headers.
The package is available in the testing series, and extra series in
slackware-current.
Here's a hint from the 10.2 changelog:
a/glibc-solibs-2.3.5-i486-5.tgz: Recompiled against header files from
linux 2.4.31 (linuxthreads version) and linux 2.6.13 (NPTL version).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6001
------- Additional Comments From the3dfxdude(a)gmail.com 2006-22-08 10:25 -------
Nope both logs are the same. Anyway turn on WINEDEBUG=+d3d_surface,+ddraw to see
the problem (overrun on surface).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5362
------- Additional Comments From dank(a)kegel.com 2006-22-08 10:11 -------
I tried installing the free trial from
http://store.sunburst.com/ProductInfo.aspx?itemid=176646
It installed fine until it started the import tool,
which showed a black window and more or less locked up
and could only be cleared with wineserver -k.
(Does that match the symptoms you saw?)
I didn't see a crash in the console output like you did, though.
I then reproduced the lockup with
$ cd ~/.wine/drive_c/TTL3/TTLIMPRT
$ wine TTLIMPRT.EXE
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6029
------- Additional Comments From mike(a)codeweavers.com 2006-22-08 10:09 -------
> The kernel is 2.6.17, and distro is mainly Slackware 10.2.
You need a libc (and kernel) that supports NPTL. If your libc isn't the same
version as slackware 10.2's then you'll need to upgrade it too.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6001
------- Additional Comments From lhouk(a)lesliehouk.com 2006-22-08 09:49 -------
Jan,
My apologies for not being more clear. The game hangs no matter what I do to
the sound settings, and I now think my two log files may be showing two
different problems. When MOO2 starts, it plays a small animated movie before
beginning the actual gameplay. When I checked only OSS sound and set the
hardware acceleration to emulation, the sound for the introductory movie was
much improved, but after the movie was over and actual gameplay began, the game
still hung when I moved the mouse. Based on what Jesse said, I am hopeful that
Wine 0.9.18 will fix the crashes, and as soon as this version is available from
the Fedora repository, I will try it out and report back.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.