January 2017 - Wine-Bugs - list.winehq.org

[Bug 4553] Future Cop doesn't start
by wine-bugs＠winehq.org Jan. 28, 2017

Jan. 28, 2017

https://bugs.winehq.org/show_bug.cgi?id=4553 Simon the Sorcerer <sur3(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #56956|0 |1 is obsolete| | --- Comment #37 from Simon the Sorcerer <sur3(a)gmx.de> --- Created attachment 57073 --> https://bugs.winehq.org/attachment.cgi?id=57073 Updated Error-Log for wine-2.0, trying to run FC. I updated the error log, now i really solved the i420 problem, by installing the appropriate codec. But game is still crashing on startup. When starting without mounted cd it asks for the cd to enter, that part is working fine, but after that i suppose its trying to show a video sequence where it crashes. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 36979] New: Cry of Fear defaults to 1280x1024 resolution
by wine-bugs＠winehq.org Jan. 28, 2017

Jan. 28, 2017

https://bugs.winehq.org/show_bug.cgi?id=36979 Bug ID: 36979 Summary: Cry of Fear defaults to 1280x1024 resolution Product: Wine Version: 1.7.23 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: schmatzler(a)googlemail.com Created attachment 49106 --> https://bugs.winehq.org/attachment.cgi?id=49106 Startup log Hello, I tried to run the game Cry of Fear, which is a free game available on Steam: http://store.steampowered.com/app/223710/ The game is bundled with a launcher where one can choose the resolution it should run with. Regardless of the resolution I choose, the game will only run in 1280x1024. The launcher starts up the cof.exe like this: wine cof.exe -basedir cryoffear -game cryoffear -hw -heapsize 1536000 -no3dmenu -fullscreen -widescreen -w 1280 -h 720 Even when I manually start it like this (without the launcher) it still won't use the specified resolution. A logfile is attached. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 27814] New: Die by the Sword: menus don't drawn unless mouse is moving
by wine-bugs＠winehq.org Jan. 27, 2017

Jan. 27, 2017

http://bugs.winehq.org/show_bug.cgi?id=27814 Summary: Die by the Sword: menus don't drawn unless mouse is moving Product: Wine Version: 1.3.24 Platform: x86 URL: http://www.fileplanet.com/11123/10000/fileinfo/Die-By- The-Sword-Demo OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Created an attachment (id=35574) --> (http://bugs.winehq.org/attachment.cgi?id=35574) plain terminal output This is a long-standing issue with the game under Wine (there are references on AppDB with Wine as old as 0.9.20). The problem: In the menus, when you click on an option the previous menu "rolls up" on the screen and the new menu drops down. In Wine the menu animation is broken: it is stuck (not redrawing) until you begin to move the mouse. A sound effect is intended to play when the menu comes down/up (a clashing sound of swords). The sound is looping while the menu is in stuck state. So you have to move the mouse constantly to use the menus. Die by the Sword is quite an oldie game (1998), using Directdraw/DirectX 5(?). The problem can be reproduced in the demo, too. Notes when testing with the demo: 1) Set Windows version to Win98 otherwise the game tries to use Glide3D (crashed for me). 2) You don't have to install the demo just unzip the contents of dbts.zip and launch the game by WINDIE.EXE -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 19

[Bug 41115] New: foldit-linux wine crashes puzzle 1269
by wine-bugs＠winehq.org Jan. 27, 2017

Jan. 27, 2017

https://bugs.winehq.org/show_bug.cgi?id=41115 Bug ID: 41115 Summary: foldit-linux wine crashes puzzle 1269 Product: Wine Version: 1.9.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: muns24072(a)mypacks.net Distribution: --- Created attachment 55323 --> https://bugs.winehq.org/attachment.cgi?id=55323 foldit-linux wine crashes puzzle 1269 backtrace foldit-linux wine crashes puzzle 1269 after a long play run -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 19815] New: FOnline has problem with textures, some are empty
by wine-bugs＠winehq.org Jan. 26, 2017

Jan. 26, 2017

http://bugs.winehq.org/show_bug.cgi?id=19815 Summary: FOnline has problem with textures, some are empty Product: Wine Version: 1.1.27 Platform: PC-x86-64 URL: http://fonline2238.blogspot.com/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: bafman(a)seznam.cz FOnline - The online remake of the Fallout world is currently in betatesting and in active development. The problem is, the game is functional, but on certain configurations there are outages in textures. The coders of FOnline expect the problem to be in the wine, escpecially, DX does not properly free unused texture from memory, preventing loading the new ones. Please, if you can give me some hints, how to debug the app in order to give you more indices, pls write me and I can liase with developers, who are primarily windows ones. Thanks, B. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 14

[Bug 13953] New: Spiceworks Hangs on launching app
by wine-bugs＠winehq.org Jan. 26, 2017

Jan. 26, 2017

http://bugs.winehq.org/show_bug.cgi?id=13953 Summary: Spiceworks Hangs on launching app Product: Wine Version: 1.0-rc5 Platform: PC OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: hytek3000(a)yahoo.com CC: hytek3000(a)yahoo.com Created an attachment (id=14106) --> (http://bugs.winehq.org/attachment.cgi?id=14106) Output from starting wine spicework_desktop.exe and trying to launch application Installer works okay for the most part (blank text on two of the install screens), and the taskbar icon works. When clicking launch, spiceworks loading screen hangs on "is starting..." The log contained has some messages about a missing registry entry for Ruby. AppDB entry: http://appdb.winehq.org/objectManager.php?sClass=version&iId=12579 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 23

[Bug 42282] New: Tales of Zestiria v1.2 (latest Steam provided runtime) crashes at launch
by wine-bugs＠winehq.org Jan. 25, 2017

Jan. 25, 2017

https://bugs.winehq.org/show_bug.cgi?id=42282 Bug ID: 42282 Summary: Tales of Zestiria v1.2 (latest Steam provided runtime) crashes at launch Product: Wine Version: 2.0-rc5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: temptempor(a)gmail.com Distribution: --- Created attachment 56991 --> https://bugs.winehq.org/attachment.cgi?id=56991 Crash report Tales of Zestiria (http://store.steampowered.com/app/351970/) Which previously worked on Wine 1.7.54 up to Wine 1.9.6 now crashes on launch. (report by: https://appdb.winehq.org/objectManager.php?sClass=version&iId=32845)/ Behaviour reproduced by me on Wine-staging 2.0.0-rc5 (I allowed myself to use Wine bugtracker as the report indicates it does not work on Wine-development either). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 39284] New: Keyboard entry problems in Turbocad 7.1
by wine-bugs＠winehq.org Jan. 25, 2017

Jan. 25, 2017

https://bugs.winehq.org/show_bug.cgi?id=39284 Bug ID: 39284 Summary: Keyboard entry problems in Turbocad 7.1 Product: Wine Version: 1.7.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tedhansen(a)sasktel.net Distribution: --- TurboCad 7.1 will not respond to keyboard entry when in drawing mode. Does respond to some keyboard entry when a pop-up dialog box is being used. Keyboard entry in drawing mode is usually key shortcuts to things like "snap to grid" so it may be the program is not accessing the key entry shortcut definitions (I have no ides how this works inside Turbocad though). This bug does not seem to be specific to any wine version, rather, it seems related to the linux version but it is getting worse. With Ubuntu 12.04 and wine 1.4, no bug. With Ubuntu 14.04 and wine 1.4, bug as described above. With Ubuntu 14.04 and wine 1.6, bug as described above. With Ubuntu 14.04 and wine 1.7, no keyboard response, unable to install. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 42189] New: Wildstar Stable: Launcher does not follow mouse movement when dragged
by wine-bugs＠winehq.org Jan. 25, 2017

Jan. 25, 2017

https://bugs.winehq.org/show_bug.cgi?id=42189 Bug ID: 42189 Summary: Wildstar Stable: Launcher does not follow mouse movement when dragged Product: Wine Version: 2.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jarl.gullberg(a)gmail.com Distribution: --- Created attachment 56820 --> https://bugs.winehq.org/attachment.cgi?id=56820 Run log from start to user closing the window When dragging the window of the Wildstar launcher, it does not follow the mouse as expected and instead jumps around in erratic fashion. This movement can be so severe that the window goes out of bounds of the visible displays and becomes unreachable. If the window is moved quickly, it will disappear, seemingly as if the program had crashed, but the process will remain running and prevent any further instances from opening until the process is forcibly stopped, the prefix configuration updated, and wineboot has been ran at least once. This issue occurs in both wine-development and wine-staging. On wine-staging, CSMT is enabled and GLSL is disabled. The following system information may be applicable: Linux Mint x64 18.1, Cinnamon Edition NVIDIA 660TI, binary drivers, version 375.26 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 42297] New: Gecko does not install itself in 2.0rc6
by wine-bugs＠winehq.org Jan. 25, 2017

Jan. 25, 2017

https://bugs.winehq.org/show_bug.cgi?id=42297 Bug ID: 42297 Summary: Gecko does not install itself in 2.0rc6 Product: Wine-gecko Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gecko-unknown Assignee: jacek(a)codeweavers.com Reporter: proveit(a)tutamail.com Distribution: --- I'm using the latest version of Wine in the development branch (2.0rc6). This bug occurs on Linux Mint Mate 32-bit. The bug is simple. In the past, when running any program in a development branch version of Wine, Wine always prompted me to install gecko and mono when I first run a program. The prompting is expected behavior: "WineHQ does not at present package wine-gecko or wine-mono. When creating a new wine prefix, you will be asked if you want to download those components. For best compatibility, it is recommended to click Yes here." (Source: https://wiki.winehq.org/Ubuntu) The instructions from the Gecko wiki page (https://wiki.winehq.org/Gecko) to manually install Gecko also does not work. The page says to download the .msi file manually (wine_gecko-2.47-x86.msi in my case) and copy it to /usr/share/wine/gecko. Not only does the directory wine not exist in /usr/share in a standard installation of the development branch from PPA (sudo apt-get install --install-recommends winehq-devel), but even when I create the wine/gecko directory under /usr/share, copying the .msi file there seems to do nothing when I run a program in a clean wine prefix. In other words, gecko can't be installed at all in the latest version of Wine development branch. The automatic install fails, and so does the manual install. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 11