http://bugs.winehq.org/show_bug.cgi?id=2932
------- Additional Comments From Speeddymon(a)gmail.com 2005-07-05 07:05 -------
Ok, I have it narrowed down to 2 possible patches, but I will need you to test
them out yourself. It is more than likely the first one,
http://cvs.winehq.org/patch.py?id=15193
If not then it is http://cvs.winehq.org/patch.py?id=15363
I can walk you through a regression test that will take you directly before and
after each patch, but it will be easier to do it thru an Instant Messaging
client, than thru this bug :-) . SO.... Let me know what you want to do. I am
available all this weekend, and anytime after about 4pm Central Time (GMT-6)
monday thru wednesday. And anytime before 11:30am Central Time (GMT-6) thursday
and friday.
Of course, all of this is assuming that you know how to compile and build wine
from source. If not, I will just have to forward this bug and both patches to
the wine devs and hope that one of those 2 patches is the one that broke it. If
not, then it is a fix somewhere else in wine that broke the clipboard, and will
be very hard to track down without a proper regression test.
Let me know what you can/want to do.
--
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=2074
stephan(a)gsklan.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From stephan(a)gsklan.de 2005-07-05 03:35 -------
No, the issue has been fixed a long time ago.
--
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=1434
Bug 1434 depends on bug 2939, which changed state.
Bug 2939 Summary: X11DRV_ChangeDisplaySettingsExW No matching mode found! (NoRes)
http://bugs.winehq.org/show_bug.cgi?id=2939
What |Old Value |New Value
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--
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=2939
lionel.ulmer(a)free.fr changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From lionel.ulmer(a)free.fr 2005-07-05 02:42 -------
Rereading the bug, I found out that it affects Fallout (which I own). So I ran
it and fixed the bug (it was what I expected it to be) with the attached patch.
Setting the status to FIXED (as it works now for me), will have to RESOLVE it
once the patch has been committed.
--
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=2939
------- Additional Comments From lionel.ulmer(a)free.fr 2005-07-05 02:28 -------
Can any one with the issue attach a +ddraw,+x11settings trace ? I think I know
what patch caused the problem, I just want to confirm it before sending a patch
for it.
--
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=2398
------- Additional Comments From Speeddymon(a)gmail.com 2005-06-05 23:29 -------
Make sure you remove the extraneous characters windows inserts into text files
before trying to apply this patch, else it will either fail to apply, or
severely break your copy of wine.
--
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=2939
------- Additional Comments From inverseparadox(a)comcast.net 2005-06-05 23:26 -------
I'd like to do that, and in fact I tried, but for some reason (possibly just
some lack in my understanding of CVS) I haven't been able to reliably get any
granularity more precise than one day. I looked on the archives of the Wine
CVS-log mailing list, and there are only six commits which took place on
2005/04/24; I saw one - to wine/dlls/ddraw/ddraw/user.c (changing from revision
1.23 to 1.24) - which looked like it had a remote chance of being related, but
passing timestamps from immediately before and immediately after the timestamp
on that CVS commit to cvs update does not reliably produce any changes to my
local tree at all.
Specifically, if I run
cvs -z3 update -dPA -D "2005-04-24 12:23"
and then run
cvs -z3 update -dPA -D "2005-04-24 12:24"
the latter command does not report any changes (the timestamp on the revision in
question is 2005/04/24 12:23:39 - the minute-level precision wouldn't help, as
there are other commits in the intervening seconds).
If someone can figure out and explain to me what I'm doing wrong, I'd be glad to
do the rest of the refinement necessary to track down the offending commit
precisely. I'll note in passing, however, that the error message I'm getting is
not precisely the same as the one reported by Luiz (the string in the concluding
parentheses is different), and the game I am running is not the same; it is
faintly possible that these are two different bugs.
(As far as having a handle on CVS - I lurk, and occasionally contribute, on the
development mailing lists for a couple of other projects; one tends to pick up
good bug-reporting habits from observation rather quickly that way. I considered
joining some of the Wine mailing lists to report this, but the Bugzilla looks to
be a more streamlined way of handling things.)
--
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.