We do often include affiliate links to earn us some pennies. See more here.
Wine development team was able to produce a new experimental release today. 1.7.17 brining many new features and as many as 89 bugfixes.

A new issue of World Wine News is also available: #367

The few most interesting features introduced in this release:
  • More implementations for the Task Scheduler.
  • C runtime made more compatible by sharing source files.
  • Fixes in the Mac OS X joystick support.
  • 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.17.tar.bz2
    http://mirrors.ibiblio.org/wine/source/1.7/wine-1.7.17.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.
    Tags: Open Source, Wine
    0 Likes
    About the author -
    author picture
    Chicken chicken chicken chicken chicken chicken chicken chicken chicken chicken chicken chicken chicken*

    *Translation:
    If you do not get the reference, it is your fault not mine.
    See more from me
    The comments on this article are closed.
    13 comments
    Page: «2/2
      Go to:

    Jarkko Apr 20, 2014
    When someone opens bug in wine db, it gets unique id number. There are lot of bugs that has no activity for years and if someone tries the game and it works it becomes marked as fixed and will be added into new wine changelog as marked fixed even the work behind bugfix might be several versions earlier.
    Anonymous Apr 20, 2014
    If You want wine to go faster forward,

    report wine issues here
    http://bugs.winehq.org/enter_bug.cgi?product=Wine

    But you should have up to date wine (no crossover or playonlinux version) and debug. "wine program-name.exe >> debug.log 2>&1" creates basic debug file.

    But it would be more important to test bugs with recent wines and report with debugs.

    Take this list for an example

    http://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&limit=0&list_id=146298&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&query_format=advanced

    Even reporting games back wine database would help.

    Here is a link to search box your favorite games:

    http://appdb.winehq.org/objectManager.php?sClass=application&sTitle=Browse%20Applications&sOrderBy=appName&bAscending=true
    lordfragger Apr 20, 2014
    Quoting: AnonymousBut you should have up to date wine (no crossover or playonlinux version)
    You can have any wine version in playonlinux, even one you compile from source yourself (which I've had to do for a game once). When a new version is released, it's in the pol repo within a day.
    While you're here, please consider supporting GamingOnLinux on:

    Reward Tiers: Patreon. Plain Donations: PayPal.

    This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

    You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
    The comments on this article are closed.