Developers introduced a new point release 1.7.15 of a development branch of Wine. While keeping with a two week release cycle, They were able to push out many new features and 53 bugfixes.
A new issue of World Wine News is also available: #365
The few most interesting features introduced in this release:
To learn more about this release pleas visit this announcement .
The source code for this release is available here:
http://prdownloads.sourceforge.net/wine/wine-1.7.15.tar.bz2
http://mirrors.ibiblio.org/wine/source/1.7/wine-1.7.15.tar.bz2
To get the most recent changes, a git repository is a good starting point.
Binary packages should be available for a download as soon as the build process is finished.
Check out Page 2 for the list of fixed bugs! Article taken from GamingOnLinux.com.
A new issue of World Wine News is also available: #365
The few most interesting features introduced in this release:
- New Task Scheduler service.
- Many regression test fixes.
- Support for exception unwinding in VBScript.
- Various bug fixes.
To learn more about this release pleas visit this announcement .
The source code for this release is available here:
http://prdownloads.sourceforge.net/wine/wine-1.7.15.tar.bz2
http://mirrors.ibiblio.org/wine/source/1.7/wine-1.7.15.tar.bz2
To get the most recent changes, a git repository is a good starting point.
Binary packages should be available for a download as soon as the build process is finished.
Check out Page 2 for the list of fixed bugs! Article taken from GamingOnLinux.com.
0 Likes
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Quoting: liamdaweWow some of the bugs on page two are ooooooold!Better fix them late than never.
Next vote:
How to display an age of the bug:
a) in days
b) properly break days into years and months
c) in seconds
d) discuss it on the forum
My vote:
b
a
d
c
0 Likes
Hello folks,
'fixed' also means someone bothered to revisit old bugs, checked it with recent wine version and found it working.
Many bugs that are probably fixed are just rotting for years in Bugzilla (users report them and never retest/revisit).
Also many bugs are invalid from start (use of outdated/broken wine versions, wineprefix/installation messed up...).
If you have severely limited resources it takes a long time to go through that many bugs and manually validate/investigate them.
The active part of Wine community which does bug triaging/fixing is pretty small compared to many other open/closed source projects.
And yet considerable success is achieved with each release, making many apps and games work better.
Regards,
Anastasius Focht
'fixed' also means someone bothered to revisit old bugs, checked it with recent wine version and found it working.
Many bugs that are probably fixed are just rotting for years in Bugzilla (users report them and never retest/revisit).
Also many bugs are invalid from start (use of outdated/broken wine versions, wineprefix/installation messed up...).
If you have severely limited resources it takes a long time to go through that many bugs and manually validate/investigate them.
The active part of Wine community which does bug triaging/fixing is pretty small compared to many other open/closed source projects.
And yet considerable success is achieved with each release, making many apps and games work better.
Regards,
Anastasius Focht
0 Likes
This video is assasins creed brotherhood with wine 1.7.15 without debugger (on console (on my case terminal on dolphin archive manager): WINEDEBUG=-all wine steam ), its recommended for more performance (but this depend game)
View video on youtube.com
:)
View video on youtube.com
:)
0 Likes
Quoting: fochtHello folks,
'fixed' also means someone bothered to revisit old bugs, checked it with recent wine version and found it working.
Many bugs that are probably fixed are just rotting for years in Bugzilla (users report them and never retest/revisit).
Also many bugs are invalid from start (use of outdated/broken wine versions, wineprefix/installation messed up...).
If you have severely limited resources it takes a long time to go through that many bugs and manually validate/investigate them.
The active part of Wine community which does bug triaging/fixing is pretty small compared to many other open/closed source projects.
And yet considerable success is achieved with each release, making many apps and games work better.
Regards,
Anastasius Focht
Well, personally I am waiting on http://bugs.winehq.org/show_bug.cgi?id=28268 to be fixed, reported on 2011-09-03 and with latest wine it still doesn't work.
Only just seen someone wanted feedback, so I tested and yup still an issue.
0 Likes
Quoting: sobkasQuoting: liamdaweWow some of the bugs on page two are ooooooold!Better fix them late than never.
Next vote:
How to display an age of the bug:
a) in days
b) properly break days into years and months
c) in seconds
d) discuss it on the forum
My vote:
b
a
d
c
Thank you for changing up the way the wine updates are done. This is much easier to read and the multi-page layout was really smart of you.
b
a
d
c
0 Likes
I have updated a script to make "b" option possible. Now waiting for votes.
0 Likes
Quote'fixed' also means someone bothered to revisit old bugs, checked it with recent wine version and found it working.
Many bugs that are probably fixed are just rotting for years in Bugzilla (users report them and never retest/revisit).
Also many bugs are invalid from start (use of outdated/broken wine versions, wineprefix/installation messed up...).
Hey mate, how would I go about helping retest/revisit the bugs? Would I need to be the one who issued the bug report? I've used Wine for a while now, but I only know how to post comments and test data on WineHQ's AppDB.
0 Likes
[code][/code]Hello Sabun,
volunteers are always welcome :-)
Wine Bugzilla itself: https://bugs.winehq.org/
This is the place where all the bug reports are stored and processed (of course appdb test reports are also welcome).
You could query Wine Bugzilla as described here: http://wiki.winehq.org/BugTriage (the "Useful Queries" part).
Before doing triaging work you need to make sure that your Wine environment is suitable for testing.
Recent Wine 1.7.x with all deps installed, graphics drivers up-to-date (to test games) ...
1) query all ''open'' bugs with a ''download'' keyword and no activity for xx days
2) select random bug, download the app/game or try to search for download (i often have to do this because the original download is no longer available)... if the app/game has no demo, try to find it by other "means" (people are still seeding stuff on public tracker which is very handy to get old software versions). also useful: "software archive" sites of internet: oldapps, filehippo ...
3) read the history to understand the problem ("app doesn't install", "app crashes on startup", "graphics artifacts", "no sound" ...)
4) always use a clean (new) WINEPREFIX (the virtual drive where to app gets installed to) for testing stuff. delete the prefix afterwards (default is "~/.wine", or WINEPREFIX=~/myinstalltest1 ...).
5) ensure that other prerequisites are properly installed before running the installer ("winetricks recipes"), if required or stated by bug report. Sometimes the prerequisites change when Wine has evolved ("got better") and they are no longer needed (if you figure this out, add a comment to bug report).
6) install app, check for errors ...
7) reproduce the problem
8) profit!
Add your findings as comment: "I tested the installer and it finished successfully without crash". This comment would be enough to have another triager with proper rights to resolve the bug (fixed and later closed).
or: "I can't reproduce the problem. the graphics are displayed fine." (another triager might join, try to reproduce and resolve).
or: "it still crashes the same way. tested with wine 1.7.x" (confirmation the bug is still present)
or: "the crash is gone but it fails in another way" (this is might be a sign the original problem is fixed -> bug fixed but another bug needs to be created for new (different) problem).
... many more possibilities.
Many bugs have evolved over time and people just kept adding comments with more issues, making the original bug essentially useless. This should be indicated ("multiple issues here: select one"). either the report will be closed (original issue fixed) or refined to tackle the last problem (until it's solved).
You can even help by doing other little tasks, outside of full triaging. Just correcting/adding links to downloads because in many cases the reporter provided little/no info. Also asking "what app (name) or version is this".
'pinging' bugs en masse by just asking "is this issue still present" should be avoided ... for some bugs it might be ok ... but in most cases one should try to test oneself.
Hope this helps a bit. Keep asking questions if something is unclear.
Regards
volunteers are always welcome :-)
Wine Bugzilla itself: https://bugs.winehq.org/
This is the place where all the bug reports are stored and processed (of course appdb test reports are also welcome).
You could query Wine Bugzilla as described here: http://wiki.winehq.org/BugTriage (the "Useful Queries" part).
Before doing triaging work you need to make sure that your Wine environment is suitable for testing.
Recent Wine 1.7.x with all deps installed, graphics drivers up-to-date (to test games) ...
1) query all ''open'' bugs with a ''download'' keyword and no activity for xx days
2) select random bug, download the app/game or try to search for download (i often have to do this because the original download is no longer available)... if the app/game has no demo, try to find it by other "means" (people are still seeding stuff on public tracker which is very handy to get old software versions). also useful: "software archive" sites of internet: oldapps, filehippo ...
3) read the history to understand the problem ("app doesn't install", "app crashes on startup", "graphics artifacts", "no sound" ...)
4) always use a clean (new) WINEPREFIX (the virtual drive where to app gets installed to) for testing stuff. delete the prefix afterwards (default is "~/.wine", or WINEPREFIX=~/myinstalltest1 ...).
5) ensure that other prerequisites are properly installed before running the installer ("winetricks recipes"), if required or stated by bug report. Sometimes the prerequisites change when Wine has evolved ("got better") and they are no longer needed (if you figure this out, add a comment to bug report).
6) install app, check for errors ...
7) reproduce the problem
8) profit!
Add your findings as comment: "I tested the installer and it finished successfully without crash". This comment would be enough to have another triager with proper rights to resolve the bug (fixed and later closed).
or: "I can't reproduce the problem. the graphics are displayed fine." (another triager might join, try to reproduce and resolve).
or: "it still crashes the same way. tested with wine 1.7.x" (confirmation the bug is still present)
or: "the crash is gone but it fails in another way" (this is might be a sign the original problem is fixed -> bug fixed but another bug needs to be created for new (different) problem).
... many more possibilities.
Many bugs have evolved over time and people just kept adding comments with more issues, making the original bug essentially useless. This should be indicated ("multiple issues here: select one"). either the report will be closed (original issue fixed) or refined to tackle the last problem (until it's solved).
You can even help by doing other little tasks, outside of full triaging. Just correcting/adding links to downloads because in many cases the reporter provided little/no info. Also asking "what app (name) or version is this".
'pinging' bugs en masse by just asking "is this issue still present" should be avoided ... for some bugs it might be ok ... but in most cases one should try to test oneself.
Hope this helps a bit. Keep asking questions if something is unclear.
Regards
0 Likes
Addendum: You can also learn how it's done by just reading/exploring the "wine-bugs" mailing list.
For example: https://www.winehq.org/pipermail/wine-bugs/2014-March/date.html
Just read the conversations or click the top link to the bug in bugzilla in the comment to get full history.
You will probably find many bugs where I put comments/analysis on ... ~2500 now ;-)
I daily skim the list for interesting bugs and just add my analysis/solutions so it gets resolved soon.
I also add many bugs on my own to document problems and resolve them.
Regards
For example: https://www.winehq.org/pipermail/wine-bugs/2014-March/date.html
Just read the conversations or click the top link to the bug in bugzilla in the comment to get full history.
You will probably find many bugs where I put comments/analysis on ... ~2500 now ;-)
I daily skim the list for interesting bugs and just add my analysis/solutions so it gets resolved soon.
I also add many bugs on my own to document problems and resolve them.
Regards
0 Likes
Patreon
PayPal
*Translation:
If you do not get the reference, it is your fault not mine.
See more from me