Not a blocker. http://bugs.winehq.org/page.cgi?id=fields.html#importance

Your Wine version is obsolete. Please retest in the current development release.

Dup of bug 34982?

Hello folks,

resolving 'invalid', old releases are not valid for filing bugs.
As Bruno mentioned in comment #2 there is a bug 34982 containing a test with recent Wine 1.7.x version.

Regards

Duplicate, not invalid.

IMO, users who file bugs for old versions should be given a reasonable chance to retest in current Wine before the bug is closed. Just because the original reported version is old doesn't mean the bug isn't still present.

*** This bug has been marked as a duplicate of bug 34982 ***

Hello Rosanne,

--- quote ---
Duplicate, not invalid.
--- quote ---

'duplicate' means essentially "exactly the same problem".
If you dumb everything down to "oh, it's the same app and there is still a crash" then this might be true.

--- quote ---
IMO, users who file bugs for old versions should be given a reasonable chance to retest in current Wine before the bug is closed. 
--- quote ---

Sure... you know what usually happens?
People move on and forget about the bugs.
Some people are reporting back - most don't.
There are several hundreds (probably in the thousand) of bugs of this kind that could be closed and nothing of value would be lost.

-- quote ---
Just because the original reported version is old doesn't mean the bug isn't still present.
--- quote ---

Well you seem to have a better understanding/knowledge about this specific bug.
For me the backtrace indicated a different problem/insufficiency, no longer present because Wine evolved -> invalid.

Regards

I was going by your comment 3 in marking this duplicate; apparently I misread your intention in referring to the other bug.  

However, if the bug is no longer present "because Wine evolved," then shouldn't the resolution be "Fixed"? "Invalid" implies this was never a bug in the first place.

Hello Rosanne,

--- quote ---
However, if the bug is no longer present "because Wine evolved," then shouldn't the resolution be "Fixed"? "Invalid" implies this was never a bug in the first place.
--- quote ---

Well, that's indeed debatable ;-)
From my point of view:

* bug reported against a Wine version from current development branch 1.7.x after it has already been fixed in newer version -> 'dupe' or 'fixed'

* bug reported against last official stable Wine 1.6.x after it has already been fixed in newer version from 1.7.x development branch -> 'dupe' or 'fixed'

* bug reported against Wine from stone age, <= 1.4.x or older development branch <= 1.5.x, 1.3.x -> 'invalid'

Yes, there were rare exceptions like the infamous Steam bug 35030 which broke _all_ versions older than Wine 1.7.8
Even Wine 1.4 and 1.5 versions got resolved as 'dupe' in that case.

In general the idea is to provide support for the last stable branch and the current development branch.
Treating reports against ancient versions as 'invalid' is a way to indicate this.
But yes, it might be a matter of personal preference.

Regards

If it was a legitimate bug that is now fixed, and it was not reported before, it should definitely be marked as fixed.

Hello folks,

resolving fixed ... somewhere in between 1.4.1 and 1.7.7
Next installer bug is 34982

Regards

Closing bugs fixed in 1.7.10.