February 2019 - wine-bugs

[Bug 34529] New: Game attempts to create and read from root Z:\ drive instead of C:\ (c_drive) directory.
by wine-bugs＠winehq.org 01 Aug '23

01 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=34529 Bug #: 34529 Summary: Game attempts to create and read from root Z:\ drive instead of C:\ (c_drive) directory. Product: Wine Version: 1.7.1 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: nemstar(a)zoho.com Classification: Unclassified When running the PC version of the game Shadowgun: Deadzone (http://www.madfingergames.com/deadzone/) which is free to download and play, I encounter a problem. The game is attempting to write to the root directory which is the Z:\ drive by default in wine. It attempts to create a directory named /users/<player name> with data files that pertain to the game. I know this because I set up a test bed and used root and the directory /users/<player name> and files within it were created successfully and the game ran as intended. If the Z:\ drive is removed using winecfg (as none root user) and the file is placed or created in ~/.wine/c_drive/users/<player name>, then the game will read the correct file on the C: drive and run as intended. If the Z:\ drive is re-enabled, then the game will try to read from the root file system on Z: and can not find /user/<player name> so it will not connect to a match or save settings. This is the case when ran as any user. Obviously the game should not be trying to create a new directory under C:\users in any circumstance, or as Z:\users if root is mounted as Z:\. -- 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.

2 3

[Bug 21448] New: RollerCoaster Tycoon 3 does not accept the original disc
by wine-bugs＠winehq.org 31 Jul '23

31 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=21448 Summary: RollerCoaster Tycoon 3 does not accept the original disc Product: Wine Version: 1.1.36 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: thomas.mertes(a)gmx.at Created an attachment (id=25828) --> (http://bugs.winehq.org/attachment.cgi?id=25828) Error log and content of message box when starting RollerCoaster Tycoon 3 When starting RollerCoaster Tycoon 3 it asks for the original disc although the original disk is in. There are some errors logged (see attachment) and then a message box appears: Please insert the original disc instead of a backup. See www.securom.com/copy for more details Greetings Thomas -- 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.

2 46

[Bug 38690] New: corrupted serial communications
by wine-bugs＠winehq.org 28 Jul '23

28 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=38690 Bug ID: 38690 Summary: corrupted serial communications Product: Wine Version: 1.7.38 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jpyle490(a)gmail.com Distribution: --- Serial communications are corrupted/laggy/ugly. Tested on a Dell Latitude D630 running Linux Mint 17.1 and Wine 1.7.38 from WineHQ PPA, as well as Wine 1.6.2 on the same hardware from the Ubuntu repo. The issue occurs whether it's the hardware 16550 serial port or a USB attached one. (In this Linux system case the USB adapter was Prolific-based.) I observed the same symptoms on Mac OS X Mavericks, compiling Wine 1.7.43 via Macports, using an FTDI-based USB adapter. The primary test scenario included Tera Term 4.87 talking to a Cisco router's console port at 9600 N,8,1 without flow control. Data back from the Cisco was incomplete, latent and just generally ugly. Using the same hardware and minicom running natively in either Linux or OS X there were no issues. Tera Term to a router provided the cleanest environment in which to observe what was happening. I can't get serial communications to work properly regardless of the Windows app or the serially-connected device. -- 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.

2 10

[Bug 38101] New: Devil May Cry 4 flickering/texture tearing to eventual white screen
by wine-bugs＠winehq.org 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=38101 Bug ID: 38101 Summary: Devil May Cry 4 flickering/texture tearing to eventual white screen Product: Wine Version: 1.7.34 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shomari.sharpe(a)gmail.com Distribution: --- on starting the game (Directx 9c version) there is lots of flicker present. Upon turning "ON" the VSYNC option in the game the flicker is reduced. The title screen will display until it eventually turns to a black and white alternating flickering. -- 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.

2 6

[Bug 39806] New: Devil May Cry 4 Frozen Screen Glitch
by wine-bugs＠winehq.org 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=39806 Bug ID: 39806 Summary: Devil May Cry 4 Frozen Screen Glitch Product: Wine Version: unspecified Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: dijscales(a)gmail.com Created attachment 53141 --> https://bugs.winehq.org/attachment.cgi?id=53141 Details of the Problem The screen will randomly freeze while I am playing the game. I can't even play for very long before it freezes. I tried to fix it by changing the config.ini, but that did nothing. -- 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.

2 19

[Bug 45711] New: Devil May Cry 4 DX10: Transparent sections of textures rendered as solid black or grey
by wine-bugs＠winehq.org 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=45711 Bug ID: 45711 Summary: Devil May Cry 4 DX10: Transparent sections of textures rendered as solid black or grey Product: Wine Version: 3.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx10 Assignee: wine-bugs(a)winehq.org Reporter: nenxvrr4.tgj(a)20mail.it Distribution: --- Created attachment 62142 --> https://bugs.winehq.org/attachment.cgi?id=62142 Forest level in Devil May Cry 4 illustrating problem. Transparent sections of textures are rendered as solid black or grey e.g a leaf appears as a leaf on a black rectangle. This also affects other assets such as paintings. -- 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.

2 3

[Bug 45712] New: Devil May Cry 4 DX10: Shadows are rendered as "lights", vice versa
by wine-bugs＠winehq.org 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=45712 Bug ID: 45712 Summary: Devil May Cry 4 DX10: Shadows are rendered as "lights", vice versa Product: Wine Version: 3.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx10 Assignee: wine-bugs(a)winehq.org Reporter: nenxvrr4.tgj(a)20mail.it Distribution: --- Created attachment 62143 --> https://bugs.winehq.org/attachment.cgi?id=62143 Game screenshot showing light and shadow being reversed. Shadows appear as "light" while light appears as shadows. This also causes levels to be unusually dark. -- 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.

2 3

[Bug 30186] New: Wine Bugzilla quick search return zero result for keywords
by wine-bugs＠winehq.org 26 Jul '23

26 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=30186 Bug #: 30186 Summary: Wine Bugzilla quick search return zero result for keywords Product: WineHQ Bugzilla Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bugzilla-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Classification: Unclassified If I remember correctly, it works yesterday. Today I try to search some short keywords in Wine Bugzilla quick search box, and found it doesn't work as before: For example, search for "win","mac","wow", "aj", "a", the result is empty. Here is a example URL: http://bugs.winehq.org/buglist.cgi?query_format=specific&order=relevance%20… Bug or feature? -- 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.

2 3

[Bug 21424] New: Cygwin 1.7.1 bash crashes
by wine-bugs＠winehq.org 26 Jul '23

26 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=21424 Summary: Cygwin 1.7.1 bash crashes Product: Wine Version: 1.1.36 Platform: x86 OS/Version: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com cygwin installs now, but one sees the following crash 10 [main] bash 9 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 1271 [main] bash 9 open_stackdumpfile: Dumping stack trace to bash.exe.stackdump err:ntdll:RtlpWaitForCriticalSection section 0x736d2784 "loader.c: loader_section" wait timed out in thread 0036, blocked by 003c, retrying (60 sec) during postinstall, and also when running bash interactively. -- 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.

2 16

[Bug 34497] New: ProAIS2 Serial Port enumeration requires Registry Local_Machine/=?UTF-8?Q?=E2=80=A6?=/Enum/SERIAL/COM1/COM1/*
by wine-bugs＠winehq.org 25 Jul '23

25 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=34497 Bug #: 34497 Summary: ProAIS2 Serial Port enumeration requires Registry Local_Machine/…/Enum/SERIAL/COM1/COM1/* Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: winehq(a)paul.sladen.org Classification: Unclassified ProAIS2 (Marine AIS software from SRT in the UK, and re-badged by large numbers of OEMs) performs Serial Port detection by enumerating the registry. The following keys need to be added: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\SERIAL\COM1\COM1] "ClassGUID"="{4D36E978-E325-11CE-BFC1-08002BE10318}" "FriendlyName"="Serial Port (COM1)" "PortName"="COM1" in addition to the matching ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com1 If only the ClassGUID/FriendlyName are set, then the port will be found, but immediately switched to in-case. PortName is being prefixed with "\\.\" ("\\\\.\\") to form "\\.\COM1". Kudos to Doug Brown for tracking down most of the issue: http://www.downtowndougbrown.com/2013/03/getting-x-ctu-in-wine-to-detect-yo… -- 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.

2 8

[Bug 39810] New: Office 2010 Pro Plus uninstallation fails
by wine-bugs＠winehq.org 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=39810 Bug ID: 39810 Summary: Office 2010 Pro Plus uninstallation fails Product: Wine Version: 1.7.55 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: isiraseneviratne(a)yahoo.com Distribution: --- After launching the uninstaller (through either the CD Setup or Wine Uninstaller), selecting the Remove option and then selecting Continue results in a message saying that setup was unable to finish successfully. -- 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.

2 12

[Bug 35904] New: USB connection not recognized by Axon MultiClamp Commander 700B.
by wine-bugs＠winehq.org 25 Jul '23

25 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=35904 Bug ID: 35904 Summary: USB connection not recognized by Axon MultiClamp Commander 700B. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com The "Axon MutiClamp Commander 700B" is a devices which connected with USB to the PC. The software for controlling the device installs and runs well, but it does not identify the USB device. For this reason, the application "MutiClamp Commander 700B" in Winehq's AppDB has currently status "Garbage". -- 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.

2 6

[Bug 19713] New: Some serial port communication functions behave differently in Wine and Windows.
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=19713 Summary: Some serial port communication functions behave differently in Wine and Windows. Product: Wine Version: 1.1.27 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: fenixk19(a)mail.ru Created an attachment (id=23025) --> (http://bugs.winehq.org/attachment.cgi?id=23025) Test program This makes test program to hang in Wine, but in MS it is ok. Test program attached. -- 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.

2 43

[Bug 37846] New: Communication broken using FTDI USB Serial Device converter (FT232RL) / Mostly send using CS-51PLUS
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=37846 Bug ID: 37846 Summary: Communication broken using FTDI USB Serial Device converter (FT232RL) / Mostly send using CS-51PLUS Product: Wine Version: 1.7.30 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lgeorgieff(a)gmail.com Distribution: --- Created attachment 50402 --> https://bugs.winehq.org/attachment.cgi?id=50402 WINEDEBUG="+comm" wine .wine/drive_c/Program\ Files\ $x86$/Icom/CS-51PLUS/CS51PLUS.exe log Hi, I am using FTDI USB Serial Device converter to program ham radio. Cable have FT232RL chip and software is CS-51PLUS. Reading from radio is OK but when I try to write (send) configuration to the radio communication is broken after while and I get error message. The same cable and software on the same machine runs without problems on QEMM's virtual windows. -- 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.

2 3

[Bug 13296] New: regression problem in upgrade to Ubuntu Hardy/1.0-rc1: Palm Hotsync over serial Segmentation Fault
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=13296 Summary: regression problem in upgrade to Ubuntu Hardy/1.0-rc1: Palm Hotsync over serial Segmentation Fault Product: Wine Version: 1.0-rc1 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jan-winehq(a)h-i-s.nl Created an attachment (id=13150) --> (http://bugs.winehq.org/attachment.cgi?id=13150) Logging output I upgraded to Ubuntu Hardy, and wine 1.0-rc1. Hotsync manager 1.0 for Palm Pilot worked fine before. http://appdb.winehq.org/objectManager.php?sClass=version&iId=10362 Now it crashes half-way synchronising over the serial port, sometimes after a few seconds, sometimes much later in the process. These crashes reproduce well, and yield a segmentation fault without further information $ wine hotsync.exe Segmentation fault $ I do not know if this means that a part of Wine crashes, or just the application. I added logging, where it seems that the problem lies within the call below: 0009:CallTo16(func=111f:072a,ds=1087,118f,7404,0000,0006) ss:sp=1087:ffd0 I am not sure if the problem lies with wine, or that other problems with Ubuntu Hardy may relate to this. It is disappointing that an application that used to work fine, and I came to depend on, is now broken. -- 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.

2 19

[Bug 25083] New: HyperTerminal unable to loop back on COM1 (RS-232)
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=25083 Summary: HyperTerminal unable to loop back on COM1 (RS-232) Product: Wine Version: 1.3.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: graham(a)nerve.org.za On a machine with an on-board RS-232 port at COM1, HyperTerminal (as shipped with Windows XP) is firstly unable to detect the port until changes are made in the WINE registry, thereafter, after attaching a simple loopback adapter (pins 2 and 3 of a DB9F shorted) no characters are echoed to the screen. Obtaining the software: >From a Windows XP installation, copy the files hypertrm.exe and htrn_jis.dll from 'C:\Program Files\Windows NT' and hticons.dll and hypertrm.dll from C:\Windows\System32' into a suitable directory below .wine/drive_c or Download a free 30 day trial of HyperTerminal Private Edition 7.0 from http://www.hilgraeve.com/hyperterminal/ Create a symbolic link for COM1, documented here: http://www.winehq.org/docs/wineusr-guide/misc-things-to-configure ln -s /dev/ttyS0 ~/.wine/dosdevices/com1 At this point, starting HyperTerminal will result in no serial ports being shown. Now, create a registry entry in WINE for the serial port, mentioned in this bug report: http://bugs.winehq.org/show_bug.cgi?id=4282 Add the following lines to .wine/system.reg [Hardware\\Devicemap\\SerialComm] "Serial0"="COM1" Now HyperTerminal can be started, COM1 can be selected and configured, but no characters are echoed to the screen. However, the free terminal program, simply named 'Terminal' and available here: https://sites.google.com/site/terminalbpp/ Does echo characters to the screen. -- 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.

2 23

[Bug 46676] New: Serial port enumeration (get device description) on Mac OS/X 10.9, 10.13
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=46676 Bug ID: 46676 Summary: Serial port enumeration (get device description) on Mac OS/X 10.9, 10.13 Product: Wine Version: 4.0 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: martin(a)hinner.info Created attachment 63628 --> https://bugs.winehq.org/attachment.cgi?id=63628 suspected problematic function Tested on: Mac OS/X 10.9, 10.13 WineBottler (Wine 1.8) works fine; Wine 4.0 (from .pkg) does not work Our application is trying to enumerate serial ports by using setupapi functions. I have not checked where exactly is the problem as debugging on OS/X is a bit difficult for me, however suspected function is attached (it's goal is to get device description). The affected apps are http://obdtester.com/ficom , http://obdtester.com/bimcom , http://obdtester.com/fcom ; I have tried to create symlink in dosdevices (required for WineBottler to get it working), one OS/X 10.13 my link got deleted everytime I ran the app; on OS/X 10.9 link persisted, but not possible to enumerate any serial port(s). I can provide login for download by personal e-mail (not to be disclosed). I have talked about this on wine mailing list a long time ago, it would be super easy if Wine-enabled application can have a way to load system native .so to talk directly to the host system, I have many examples of device drivers that would be super easy to implement. FYI I have already written "winegate.dll.so" which solves this real world problem, but it was rejected for submission to Wine because of "Wine must be 100% transparent" ideology. -- 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.

2 9

[Bug 23326] New: Cannot change printer settings, Family Tree 7
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=23326 Summary: Cannot change printer settings, Family Tree 7 Product: Wine Version: 1.2-rc4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jamesl(a)bestweb.net Created an attachment (id=29072) --> (http://bugs.winehq.org/attachment.cgi?id=29072) FTW7 print dialogue, compare Wine to XP Cannot select printer/change print settings with Family Tree Maker 7. Dialogue box comes up, drop-down boxes are working, but radio buttons for switching between "default printer" and an alternate printer are not selectable. Have compared the print dialogue between Wine vs a native install under Windows XP (SP3) and notice some text from the Windows install does not show up under Wine. Also tried the same thing with the "free" version of FTM2005se available at http://past.familytreemaker.com/download/starter.aspx and found it's behavior is the same. So I will describe steps from there, since it would be eaier for someone to get that to test against. STEPS TO RECREATE: 1: Set up wine profile with "WINEPREFIX=/home/jelabarre/wine-apps/ftw2005 winecfg"; set winver to "Windows XP", point the Documents directory under Desktop Integration to my own Documents directory 2: install FTW2005 by running "WINEPREFIX=/home/jelabaWINEPREFIX=/home/jelabarre/wine-apps/ftw2005 wine ./FamilyTreeMaker2005se.exe", accept all defaults. 3: open FTW 2005 from "Wine" menu entry on Gnome menu. Selected "Buy Later" from popup window (does not affect outcome, as same print problem occurrs in a regular retail version of FTM7) 4: create new file, or use existing file (same result either way) 5: select "File | Print Setup", then try to select radio button for either "Default Printer" or "Specific Printer". Neither can be selected 6: try selecting a "specific printer" from drop-down box. Printer can be selected, but radio buttons still not functional. 7: after selecting a printer other than the default (such as print-to-PDF) and then try printing. Output will still go to the Linux default printer, no edits of the print settings will take effect. The "Family Archive Viewer v6.0" at http://familytreemaker.genealogy.com/abtffiv.html and "Family Archive Viewer v11.0" at http://www.genealogy.com/abtffiv.html are other variants that exhibits this behavior. Have attached sample screenshots of Wine vs WinXP versions of the print dialogue. -- 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.

2 15

[Bug 30155] New: secdrv.sys from SafeDisc v2.05.030 does not work
by wine-bugs＠winehq.org 23 Jul '23

23 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=30155 Bug #: 30155 Summary: secdrv.sys from SafeDisc v2.05.030 does not work Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl AssignedTo: wine-bugs(a)winehq.org ReportedBy: stefan(a)codeweavers.com Classification: Unclassified Created attachment 39336 --> http://bugs.winehq.org/attachment.cgi?id=39336 service,relay,winedevice,ntoskrnl log SafeDisc 2.05.030 does not work out of the box. The user-visible symptom is that the application exits with exit code 0 without any output. This affects for example the Command and Conquer Red Alert 2 installer, which is safedisc protected for some reason. The problem seems to be related to the specific secdrv.sys version. If I take a secdrv.sys from a newer safedisc version(e.g. 2.40.010 from the RA2 Yuri's revenge expansion) and put it in C:\windows\system32\drivers, the installer works. ProtectId says: Scanning -> D:\Setup\Setup.exe File Type : 32-Bit Exe (Subsystem : Win GUI / 2), Size : 1308863 (013F8BFh) Byte(s) -> File has 733375 (0B30BFh) bytes of appended data starting at offset 08C800h [File Heuristics] -> Flag : 00000000000000000100000000100111 (0x00004027) [!] Safedisc v2.05.030 detected ! [i] Appended data contents.... [.] o: 0x0008C828 / t: <0x00000001> <0x00000000> <0x00000001> / s: 00194947 byte(s) -> ~de7bc4.tmp [.] o: 0x000BC1D2 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00030208 byte(s) -> clcd32.dll [.] o: 0x000C37F9 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00006784 byte(s) -> clcd16.dll [.] o: 0x000C529D / t: <0x00000001> <0x00000000> <0x0000044D> / s: 00067584 byte(s) -> mcp.dll [.] o: 0x000D5AC5 / t: <0x00000001> <0x00000000> <0x00000000> / s: 00327220 byte(s) -> ~df394b.tmp [.] o: 0x00125920 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00034304 byte(s) -> drvmgt.dll [.] o: 0x0012DF47 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00018768 byte(s) -> secdrv.sys [.] o: 0x001328BF / t: <0x00000001> <0x00000000> <0x00000000> / s: 00053248 byte(s) -> ~ef7194.tmp [CompilerDetect] -> Visual C++ 6.0 - Scan Took : 0.640 Second(s) The md5sum of the broken secdrv.sys is XXX. The md5sum of the working 2.40.010 driver is f376a1580204e47f37a721e1cbc5582a. I am attaching a +relay,+service,+winedevice+ntoskrnl log of a failed run of the setup tool. -- 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.

2 32

[Bug 44823] New: Steam doesn' t close on exit. Will continue running in background.
by wine-bugs＠winehq.org 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=44823 Bug ID: 44823 Summary: Steam doesn't close on exit. Will continue running in background. Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vblanton(a)gmail.com Distribution: --- Created attachment 60857 --> https://bugs.winehq.org/attachment.cgi?id=60857 Steam system information and version Running the latest Steam client, I find that Steam doesn't actually close entirely after I exit normally with Steam>Exit. I have to open System Monitor and kill all steam and wine related processes. I can't open steam again until I do so, and the Steam.exe and wineserver processes chew 17% of my CPU each in the background until I do so. -- 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.

2 14

[Bug 42360] New: Terragen 4 fails to start
by wine-bugs＠winehq.org 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=42360 Bug ID: 42360 Summary: Terragen 4 fails to start Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: eneeen(a)gmail.com Distribution: --- Created attachment 57137 --> https://bugs.winehq.org/attachment.cgi?id=57137 tgd4_backlog Using Kubuntu 16.10 I've attached backlog. -- 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.

2 12

[Bug 41693] New: The Forrest Steam crashes on startup
by wine-bugs＠winehq.org 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=41693 Bug ID: 41693 Summary: The Forrest Steam crashes on startup Product: Wine Version: 1.9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thomthomthom(a)ymail.com Distribution: --- When I click on the "Play" button, the window "TheForest Configuration" appears. I click on "Play!" and the game crashes. Terminal output: thomthomthom@thomthomthom:/usr/src/wine$ wine ~/.wine/drive_c/Program\ Files/Steam/Steam.exe fixme:ver:GetCurrentPackageId (0x32e460 (nil)): stub ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt". thomthomthom@thomthomthom:/usr/src/wine$ fixme:file:SetFileCompletionNotificationModes 0x29c 1 - stub wine: Unhandled exception 0x80000003 in thread 78 at address 0x100aa6d9 (thread 0078), starting debugger... fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS, hwnd=(nil)): stub fixme:appbar:SHAppBarMessage unknown msg: 4 fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=3): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=1): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=0): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=2): stub err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:mfplat:MFStartup (65648, 1): stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:gdi:GdiInitializeLanguagePack stub fixme:ntdll:EtwEventUnregister (deadbeef) stub. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, (nil) 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 (nil) 0x33f7a8) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, 0x179d48 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 0x179d48 0x33f7a8) returning a dummy value (current locale) fixme:winsock:WSALookupServiceBeginW (0x33f4b8 0x00000ff0 0x33f4f4) Stub! fixme:iphlpapi:NotifyAddrChange (Handle 0x33f638, overlapped 0x17af7c): stub fixme:win:RegisterDeviceNotificationW (hwnd=0x600e0, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterDeviceNotificationW (hwnd=0x600e0, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x33f114,0x00000000), stub! fixme:ver:GetCurrentPackageId (0x2f3dfa4 (nil)): stub fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS, hwnd=(nil)): stub fixme:appbar:SHAppBarMessage unknown msg: 4 fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=3): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=1): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=0): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=2): stub fixme:dwmapi:DwmExtendFrameIntoClientArea (0x6014a, 0x33e798) stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS, hwnd=(nil)): stub fixme:appbar:SHAppBarMessage unknown msg: 4 fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=3): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=1): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=0): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=2): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS, hwnd=(nil)): stub fixme:appbar:SHAppBarMessage unknown msg: 4 fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=3): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=1): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=0): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=2): stub fixme:file:SetFileCompletionNotificationModes 0x28c 1 - stub wine: Unhandled exception 0x80000003 in thread f6 at address 0x100aa6d9 (thread 00f6), starting debugger... err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:mfplat:MFStartup (65648, 1): stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:gdi:GdiInitializeLanguagePack stub fixme:ntdll:EtwEventUnregister (deadbeef) stub. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, (nil) 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 (nil) 0x33f7a8) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, 0x179d40 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 0x179d40 0x33f7a8) returning a dummy value (current locale) fixme:winsock:WSALookupServiceBeginW (0x33f4b8 0x00000ff0 0x33f4f4) Stub! fixme:iphlpapi:NotifyAddrChange (Handle 0x33f638, overlapped 0x17af74): stub fixme:win:RegisterDeviceNotificationW (hwnd=0x30126, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterDeviceNotificationW (hwnd=0x30126, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x33f114,0x00000000), stub! fixme:ver:GetCurrentPackageId (0x2f3dfa4 (nil)): stub fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:file:SetFileCompletionNotificationModes 0x28c 1 - stub wine: Unhandled exception 0x80000003 in thread 118 at address 0x100aa6d9 (thread 0118), starting debugger... err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:mfplat:MFStartup (65648, 1): stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:gdi:GdiInitializeLanguagePack stub fixme:ntdll:EtwEventUnregister (deadbeef) stub. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, (nil) 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 (nil) 0x33f7a8) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, 0x179d48 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 0x179d48 0x33f7a8) returning a dummy value (current locale) fixme:winsock:WSALookupServiceBeginW (0x33f4b8 0x00000ff0 0x33f4f4) Stub! fixme:iphlpapi:NotifyAddrChange (Handle 0x33f638, overlapped 0x17af7c): stub fixme:win:RegisterDeviceNotificationW (hwnd=0x4012a, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterDeviceNotificationW (hwnd=0x4012a, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x33f114,0x00000000), stub! fixme:ver:GetCurrentPackageId (0x303dfa4 (nil)): stub fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:file:SetFileCompletionNotificationModes 0x28c 1 - stub wine: Unhandled exception 0x80000003 in thread 13c at address 0x100aa6d9 (thread 013c), starting debugger... err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:mfplat:MFStartup (65648, 1): stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:gdi:GdiInitializeLanguagePack stub fixme:ntdll:EtwEventUnregister (deadbeef) stub. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, (nil) 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 (nil) 0x33f7a8) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, 0x179d50 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 0x179d50 0x33f7a8) returning a dummy value (current locale) fixme:winsock:WSALookupServiceBeginW (0x33f4b8 0x00000ff0 0x33f4f4) Stub! fixme:iphlpapi:NotifyAddrChange (Handle 0x33f638, overlapped 0x17af84): stub fixme:win:RegisterDeviceNotificationW (hwnd=0x80090, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterDeviceNotificationW (hwnd=0x80090, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x33f114,0x00000000), stub! fixme:ver:GetCurrentPackageId (0x2f3dfa4 (nil)): stub fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:dwmapi:DwmExtendFrameIntoClientArea (0x5010e, 0x33e69c) stub fixme:ntdll:EtwEventRegister ({47a9201e-73b0-42ce-9821-7e134361bc6f}, 0x100772c0, 0x100ed0e0, 0x100ed0d8) stub. fixme:ntdll:EtwEventRegister ({58a9201e-73b0-42ce-9821-7e134361bc70}, 0x100772c0, 0x100ed118, 0x100ed110) stub. fixme:ntdll:EtwEventRegister ({3fa9201e-73b0-43fe-9821-7e145359bc6f}, 0x100772c0, 0x100ed0a8, 0x100ed0a0) stub. fixme:ntdll:EtwEventRegister ({1432afee-73b0-42ce-9821-7e134361b433}, 0x100772c0, 0x100ed150, 0x100ed148) stub. fixme:ntdll:EtwEventRegister ({4372afee-73b0-42ce-9821-7e134361b519}, 0x100772c0, 0x100ed188, 0x100ed180) stub. fixme:imm:ImmGetOpenStatus (0x166778): semi-stub fixme:ver:GetCurrentPackageId (0x33f03c (nil)): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:system:SetProcessDPIAware stub! thomthomthom@thomthomthom:/usr/src/wine$ fixme:win:EnumDisplayDevicesW ((null),0,0x33f44c,0x00000000), stub! fixme:win:EnumDisplayDevicesW (L"\\\\.\\DISPLAY1",0,0x33f44c,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),1,0x33f44c,0x00000000), stub! fixme:imm:ImmReleaseContext (0x5012a, 0x206788): stub fixme:win:EnumDisplayDevicesW ((null),0,0x33f644,0x00000000), stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8A8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B10G10R10A2_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B5G6R5_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B5G5R5A1_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B5G5R5X1_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8A8_UNORM, dst_format WINED3DFMT_B5G6R5_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM, dst_format WINED3DFMT_B5G6R5_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B10G10R10A2_UNORM, dst_format WINED3DFMT_B5G6R5_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B5G6R5_UNORM, dst_format WINED3DFMT_B5G6R5_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B5G5R5A1_UNORM, dst_format WINED3DFMT_B5G6R5_UNORM stub! fixme:d3d:wined3d_check_device_format_conversion wined3d 0x20a180, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B5G5R5X1_UNORM, dst_format WINED3DFMT_B5G6R5_UNORM stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33ef94,0x00000000), stub! fixme:d3d9:wined3dformat_from_d3dformat Unhandled D3DFORMAT 0xffffffff. fixme:d3d9:wined3dformat_from_d3dformat Unhandled D3DFORMAT 0xffffffff. fixme:d3d9:wined3dformat_from_d3dformat Unhandled D3DFORMAT 0xffffffff. fixme:d3d9:wined3dformat_from_d3dformat Unhandled D3DFORMAT 0xffffffff. fixme:d3d9:wined3dformat_from_d3dformat Unhandled D3DFORMAT 0xffffffff. fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT! fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. fixme:win:RegisterDeviceNotificationW (hwnd=0xd00e0, filter=0x33eeb4,flags=0x00000004) returns a fake device notification handle! thomthomthom@thomthomthom:/usr/src/wine$ fixme:system:SystemParametersInfoW Unknown action: 116 fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB! fixme:win:RegisterDeviceNotificationW (hwnd=0x5012a, filter=0x33fb40,flags=0x00000004) returns a fake device notification handle! fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB! fixme:win:RegisterDeviceNotificationW (hwnd=0x5012a, filter=0x33fc18,flags=0x00000004) returns a fake device notification handle! fixme:win:RegisterTouchWindow (0x5012a 00000000): stub thomthomthom@thomthomthom:/usr/src/wine$ fixme:ver:GetCurrentPackageId (0x1c7eea08 (nil)): stub fixme:ver:GetCurrentPackageId (0x2061ea08 (nil)): stub fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x1c7ee994): stub fixme:win:RegisterDeviceNotificationW (hwnd=0x5012a, filter=0x31c3f098,flags=0x00000000) returns a fake device notification handle! fixme:ntdll:EtwRegisterTraceGuidsW (0x6f424d0, 0x6f4d708, {7c830ece-5fb3-417a-a1bd-508f45277356}, 1, 0x33e654, (null), (null), 0x6f4d710): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {7c830ece-5fb3-417a-a1bd-508f45277356} fixme:ntdll:EtwRegisterTraceGuidsW (0xba624d0, 0xba6d708, {7c830ece-5fb3-417a-a1bd-508f45277356}, 1, 0x33e654, (null), (null), 0xba6d710): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {7c830ece-5fb3-417a-a1bd-508f45277356} fixme:ntdll:EtwRegisterTraceGuidsW (0xbb024d0, 0xbb0d6e8, {7c830ece-5fb3-417a-a1bd-508f45277356}, 1, 0x33e654, (null), (null), 0xbb0d6f0): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {7c830ece-5fb3-417a-a1bd-508f45277356} fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block no range fixme:dbghelp:validate_addr64 Unsupported address fffffffff7550000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff72e0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff70f0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff5240000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff5210000 fixme:dbghelp:validate_addr64 Unsupported address ffffffffeba30000 fixme:dbghelp:validate_addr64 Unsupported address ffffffffe4410000 fixme:dbghelp:validate_addr64 Unsupported address ffffffffef420000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff40e0000 fixme:dbghelp:validate_addr64 Unsupported address ffffffffe9840000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff50d0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff4e30000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff50b0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff5090000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff5040000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff5030000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff44a0000 fixme:dbghelp:validate_addr64 Unsupported address fffffffff4430000 fixme:dbghelp:validate_addr64 Unsupported address ffffffffdd260000 err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x43b4ad thomthomthom@thomthomthom:/usr/src/wine$ fixme:file:SetFileCompletionNotificationModes 0x294 1 - stub wine: Unhandled exception 0x80000003 in thread 15d at address 0x100aa6d9 (thread 015d), starting debugger... err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:mfplat:MFStartup (65648, 1): stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:gdi:GdiInitializeLanguagePack stub fixme:ntdll:EtwEventUnregister (deadbeef) stub. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:heap:RtlSetHeapInformation 0x110000 0 0x33fcec 4 stub fixme:process:SetProcessDEPPolicy (3): stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x100de000, 0x12e0b680, 0x12f6acb0) stub. fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, (nil) 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 (nil) 0x33f7a8) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x33f7a4, 0x179d58 0x33f7a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x33f7a4 0x179d58 0x33f7a8) returning a dummy value (current locale) fixme:winsock:WSALookupServiceBeginW (0x33f4b8 0x00000ff0 0x33f4f4) Stub! fixme:iphlpapi:NotifyAddrChange (Handle 0x33f638, overlapped 0x17af8c): stub fixme:win:RegisterDeviceNotificationW (hwnd=0xa010e, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterDeviceNotificationW (hwnd=0xa010e, filter=0x33f60c,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x33f114,0x00000000), stub! fixme:ver:GetCurrentPackageId (0x2f3dfa4 (nil)): stub fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:ver:GetCurrentPackageId (0x33fb30 (nil)): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETTASKBARPOS, hwnd=(nil)): stub fixme:appbar:SHAppBarMessage unknown msg: 4 fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=3): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=1): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=0): stub fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=2): stub -- 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.

2 4

[Bug 9378] New: CM: Shock Force 'Could not initialize graphics display'
by wine-bugs＠winehq.org 22 Jul '23

22 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=9378 Summary: CM: Shock Force 'Could not initialize graphics display' Product: Wine Version: 0.9.43. Platform: PC URL: http://www.battlefront.com/products/cmsf/downloads.html OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-directx AssignedTo: wine-bugs(a)winehq.org ReportedBy: mailing_list(a)orange.nl After starting Combat Mission: Shock Force Demo it stops with the message: 'Could not initialize graphics display. REQUIRED 1024x768, 32-bit color'. The terminal output doesn't provide any clues: wine 'CM Shock Force DEMO.exe' ALSA lib conf.c:3939:(snd_config_expand) Unknown parameters 0 ALSA lib control.c:910:(snd_ctl_open_noupdate) Invalid CTL default:0 err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element fixme:wave:ALSA_AddCaptureDevice Add support for DSCapture ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 37

[Bug 18889] New: Live Messenger 2008 fails to load - possible actctx problem
by wine-bugs＠winehq.org 22 Jul '23

22 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=18889 Summary: Live Messenger 2008 fails to load - possible actctx problem Product: Wine Version: 1.1.16 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: andras(a)csevego.net Created an attachment (id=21730) --> (http://bugs.winehq.org/attachment.cgi?id=21730) +actctx,+relay log Starting of installed (on windows) Msn 2009 wil result: err:module:import_dll Library MSVCR80.dll (which is needed by L"Z:\\media\\disk\\Program Files\\Windows Live\\Messenger\\msnmsgr.exe") not found err:module:LdrInitializeThunk Main exe initialization for L"Z:\\media\\disk\\Program Files\\Windows Live\\Messenger\\msnmsgr.exe" failed, status c0000135 Same load failure, when I manually install with wine (from msi packages) MSVCRT 8.0 is installed, as shown attached +actctx,+relay log I suspect here an Activation Context failure. -- 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.

2 106

[Bug 35866] New: AvP 2000 game: some ingame text has red boxes around it
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=35866 Bug ID: 35866 Summary: AvP 2000 game: some ingame text has red boxes around it Product: Wine Version: 1.7.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bob.mt.wya(a)gmail.com Created attachment 47886 --> http://bugs.winehq.org/attachment.cgi?id=47886 In game HUD : red boxes Using the Steam version of Aliens Vs Predator Classic (2000). Some ingame text has red boxes around each individual character. Appears under both recent Nvidia (proprietary) and AMD radeon (kernel) drivers. I didn't even notice this glitch before. But having booted into Windows 7 to double check... The red boxes are not present when the game is run natively under Windows. I don't see anything of significance in the console log when I launch AvP manually (with Steam running in the same 64-bit Wineprefix). Any thoughts if this is low hanging fruit to fix? Thanks Robert -- 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.

2 15

[Bug 46221] New: League of Legends 8.23 crash after champion select
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=46221 Bug ID: 46221 Summary: League of Legends 8.23 crash after champion select Product: Wine Version: 3.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lollinos(a)hotmail.com Distribution: --- i think it's the same error about anti-cheat lol had last patches. After Champion select end, game crash with message: "A critical error has occurred and the process must be terminated. Would you liek to create a crash dump to aid the developers in troubleshooting this issue? This may take up to 5 minutes. NOYE: The process may appear unresponsive during this time. [YES] [NO]". Steps: - WINEPREFIX=~/.wine WINEARCH=win32 wine winecfg - WINEPREFIX=~/.wine WINEARCH=win32 wine winetricks --gui, set to true capture mouse, virtual Desktop and Windows version to XP (I've tried with 7-10 too) - wineboot -u, winetricks -q d3dx9 - cd .wine/drive_c/, ln -s ~/path/lol-installer.exe - wine start lol-installer.exe - wine reg add 'HKEY_CURRENT_USER\Software\Wine\DllOverrides' /v 'msvcp140' /t 'REG_SZ' /d 'native,builtin' /f - wine reg add 'HKEY_CURRENT_USER\Software\Wine\DllOverrides' /v 'wininet' /t 'REG_SZ' /d 'builtin,native' /f - wine start 'C:\Riot Games\League of Legends\LeagueClient.exe' I tried a lot of settings, but i cant make it works after champion select. Some way to fix this bug? ii wine-staging 3.21.0~stretch amd64 WINE Is Not An Emulator - runs MS Windows programs ii wine-staging-amd64 3.21.0~stretch amd64 WINE Is Not An Emulator - runs MS Windows programs ii wine-staging-i386:i386 3.21.0~stretch i386 WINE Is Not An Emulator - runs MS Windows programs ii winehq-staging 3.21.0~stretch amd64 WINE Is Not An Emulator - runs MS Windows programs ii winetricks 0.0+20170101-1 all package manager for Wine to install software easily -- 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.

2 8

[Bug 35690] New: Steam network hang ups.
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=35690 Bug ID: 35690 Summary: Steam network hang ups. Product: Wine Version: 1.7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hellsy22(a)gmail.com Created attachment 47657 --> http://bugs.winehq.org/attachment.cgi?id=47657 Installing and using steam Unpredictable hangups while establishing connection for downloading updates, loggining in, downloading games, etc. There are no problems with network for everything except wine/Steam. Win Steam works perfect, all other services - too. -- 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.

2 18

[Bug 45042] New: Steam doesn't uninstall applications, gets stuck saying " deleting %app" until next popup isn't very visible
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=45042 Bug ID: 45042 Summary: Steam doesn't uninstall applications, gets stuck saying "deleting %app" until next popup isn't very visible Product: Wine Version: 3.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: romulasry(a)gmail.com Distribution: --- Created attachment 61171 --> https://bugs.winehq.org/attachment.cgi?id=61171 wine log It is nearly impossible to delete steam applications when you right click then select uninstall. -- 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.

2 10

[Bug 41466] New: Steam: Tray icon menu sometimes flickers
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=41466 Bug ID: 41466 Summary: Steam: Tray icon menu sometimes flickers Product: Wine Version: 1.9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sworddragon2(a)aol.com Distribution: --- Created attachment 55847 --> https://bugs.winehq.org/attachment.cgi?id=55847 Terminal output On starting Steam, making a right click on the tray icon and clicking on "Setings" instead of vanishing most times the tray icon menu gets black and begins to flicker. This behavior disappears as soon as the mouse cursor is moved. In the attachments is the terminal output where this issues happened. -- 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.

2 5

[Bug 44529] New: [Steam] Process remaining after exiting
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=44529 Bug ID: 44529 Summary: [Steam] Process remaining after exiting Product: Wine Version: 3.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maxi.cass11(a)gmail.com Distribution: --- Created attachment 60483 --> https://bugs.winehq.org/attachment.cgi?id=60483 wine 3.1 terminal output When I close steam with the tray icon, a steam process is still her and use 14% of the CPU. I have attached the console output when I leave steam, I don't know how can I give more relevant information. -- 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.

2 9

[Bug 24614] New: Medieval Total War crashes on startup
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=24614 Summary: Medieval Total War crashes on startup Product: Wine Version: 1.2 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 AssignedTo: wine-bugs(a)winehq.org ReportedBy: th.seltsam(a)gmail.com CC: wine-bugs(a)winehq.org Running the game just shows a black window, no crash dialog, and an infinite console output err:d3dx:assemble-shader Asm reading failed err:d3dx:assemble-shader Asm reading failed err:d3dx:assemble-shader Asm reading failed err:d3dx:assemble-shader Asm reading failed Using d3dx9-36 did not solve the problem. -- 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.

2 27

[Bug 45564] New: Kolab E14 Client installation fails with "Copy failed"
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=45564 Bug ID: 45564 Summary: Kolab E14 Client installation fails with "Copy failed" Product: Wine Version: 3.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- Created attachment 61987 --> https://bugs.winehq.org/attachment.cgi?id=61987 Install log with WINEDEBUG=+ntdll,+commctl The installation of the Kolab E14 Client (Groupware based on KDE) fails with "Copy failed" and aborts. The install log including the generation of the Message "Copy failed" is attached. Wine is self-compiled with the patch from bug #45552 created by Fabian Maurer. -- 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.

2 4

[Bug 44223] New: FrameMaker 7.2: Console window minimized and not (re) drawn
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=44223 Bug ID: 44223 Summary: FrameMaker 7.2: Console window minimized and not (re)drawn Product: Wine Version: 3.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- When opening a file in FrameMaker 7.2 which has errors (i.e. missing font, missing cross references), a message window ("Framemaker console", text window with its own window manager decoration) is opened and a message box is created. When this happens the message window is drawn with the least possible size (to allow only the window manager icons to appear) and when enlarging it, its content is not drawn (the content pane shows the content of the underlying window). The message windows content is therefor not readable. Sometimes (not always) the dialog box and the message window are only shown in the panel and are not shown at all (which may be a window manager problem, cannot judge). Any hint to give more helpful details is welcome. -- 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.

2 6

[Bug 35701] New: League of Legends: Right click contextual menu on friends list is invisible
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=35701 Bug ID: 35701 Summary: League of Legends: Right click contextual menu on friends list is invisible Product: Wine Version: 1.7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: echo(a)cyphernaut.org When I open League of Legends, and I open the friends list, you can right click on a friend to do things such as remove, spectate, message, etc, however in Wine (as of 1.7.13) this contextual menu is invisible. Items in the menu are still clickable, if you know where to click them. No crash or anything occurs, just an invisible menu. This occurs both with and without compositing enabled, and I've seen it occurring on both Nvidia proprietary drivers as well as RadeonSI Mesa drivers. No output is given to the console when I right-click on the friends list. -- 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.

2 28

[Bug 42867] New: steam store doesnt work
by wine-bugs＠winehq.org 21 Jul '23

21 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=42867 Bug ID: 42867 Summary: steam store doesnt work Product: Wine Version: 2.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bronsonmathews(a)gmail.com Distribution: --- trying to access the steam store through steam itself doesnt work at all. -- 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.

2 7

[Bug 11436] New: Pepakura viewer: err:wgl: X11DRV_wglShareLists Could not share display lists, context already created !
by wine-bugs＠winehq.org 19 Jul '23

19 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=11436 Summary: Pepakura viewer: err:wgl:X11DRV_wglShareLists Could not share display lists, context already created ! Product: Wine Version: CVS/GIT Platform: PC URL: http://www.tamasoft.co.jp/pepakura- en/download/viewer.html OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: x11-driver AssignedTo: wine-bugs(a)winehq.org ReportedBy: fabio.capela(a)yahoo.com Created an attachment (id=10567) --> (http://bugs.winehq.org/attachment.cgi?id=10567) Trace until the error. I'm trying to run the Pepakura viewer, but it's giving an strange error on startup (error: no error) and is having some graphical glitches, as well as being extremely slow. The grafical glitches are a flickering 3D model and no textures on the 2D model. The bug seems to be the same one affecting Pepakura Designer 2. The console shows an error with X11DRV_wglShareLists (err:wgl:X11DRV_wglShareLists Could not share display lists, context already created !). I've attached a wgl trace up to the moment the error dialog appears. Seems like the workaround to handle the different way to share OpenGL contexts in Windows and Linux can't handle this specific software. The software is freeware and can be downloaded from http://www.tamasoft.co.jp/pepakura-en/download/viewer.html -- 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.

2 48

[Bug 42226] New: No ingame sfx audio when CD Audio playing with builtin dsound in Ignition
by wine-bugs＠winehq.org 19 Jul '23

19 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=42226 Bug ID: 42226 Summary: No ingame sfx audio when CD Audio playing with builtin dsound in Ignition Product: Wine Version: 1.9.23 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dsound Assignee: wine-bugs(a)winehq.org Reporter: mads(a)ab3.no Distribution: --- Wine 1.9.23 (Staging) If I play the original Ignition[1] (Ign_3dfx.exe with nGlide 1.05) with native *dsound driver (winetricks dsound), both CD Audio and ingame sfx works, but there's about a half-second latency to every ingame sfx. When I use the built-in dsound, I have to choose between listening to music, or listen to ingame sfx (if I enable CD Audio, there's no ingame sfx). But there's no latency to the ingame sfx when it's enabled. What kind of logs are interesting here? [1] https://en.wikipedia.org/wiki/Ignition_(video_game) -- 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.

2 4

[Bug 40427] New: PS4 Remote Play Installer does not work because it needs Windows Media Feature Pack
by wine-bugs＠winehq.org 19 Jul '23

19 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=40427 Bug ID: 40427 Summary: PS4 Remote Play Installer does not work because it needs Windows Media Feature Pack Product: Wine Version: 1.9.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: windowscodecs Assignee: wine-bugs(a)winehq.org Reporter: axfelix(a)gmail.com Distribution: --- Hi folks, Running wine-staging 1.9.5 and trying to install the new PS4 Remote Play app that was released this morning: https://www.thurrott.com/xbox/66088/ps4-remote-play-comes-pc Made a fresh wineprefix. First, I had to set the Windows version to 8.1 because anything less complained that it was unsupported by the installer. Then, I had to make another new 32bit wine prefix because on 64bits the installer complained that it had a resolution below 1024x768. Finally, I got an error about needing to install the Windows Media Feature Pack. This is an MSU installer (Windows8.1-KB2929699-x86.msu) so it isn't supported in upstream Wine; however, staging recently added support for some MSU installers. They haven't really documented how this is supposed to work beyond "it uses WUSA" and ".NET 4.5 will work out of the box after setting an override for mscoree in winecfg," so I set the override, and tried: $ env WINEPREFIX=~/.ps4test wine ~/.ps4test/drive_c/windows/system32/wusa.exe Windows8.1-KB2929699-x86.msu Which had this output: ... fixme:wusa:read_assembly Ignoring unexpected tag L"rescache" fixme:wusa:read_assembly Ignoring unexpected tag L"memberships" fixme:wusa:read_assembly Ignoring unexpected tag L"localization" fixme:wusa:read_assembly Ignoring unexpected tag L"rescache" fixme:wusa:read_assembly Ignoring unexpected tag L"languagePack" fixme:wusa:read_assembly Ignoring unexpected tag L"memberships" fixme:wusa:read_assembly Ignoring unexpected tag L"localization" fixme:wusa:read_assembly Ignoring unexpected tag L"rescache" fixme:wusa:install_assembly Assembly L"Microsoft-Windows-MFPlat" not found err:wusa:install_updates Failed to install update L"Microsoft-Windows-MediaFeaturePack-OOB-Package-TopLevel" err:wusa:install_msu Dryrun failed, aborting installation So, OK, maybe that one particular MSU doesn't work still, or maybe I'm doing it wrong. I then tried the middle answer from this AskUbuntu thread to add the relevant h264 functionality manually: http://askubuntu.com/questions/651099/how-to-install-windows-media-feature-… But unfortunately, after successfully registering the relevant DLLs and creating the registry keys, the PS4 Remote Play Installer still complains about wanting the Windows Media Feature Pack. So I'm stuck for now. But hopefully this is a start! -- 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.

2 16

[Bug 42668] New: RealMYST crashes with "Too many open files" error
by wine-bugs＠winehq.org 17 Jul '23

17 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=42668 Bug ID: 42668 Summary: RealMYST crashes with "Too many open files" error Product: Wine Version: 2.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: psychonaut(a)nothingisreal.com Distribution: --- Created attachment 57619 --> https://bugs.winehq.org/attachment.cgi?id=57619 Console output from Wine 2.3 realMYST (as distributed by GoG) crashes near the end of the introductory sequence, right before the book lands at the bottom of the screen. If I abort the introduction, I can start playing the game, which seems to work fine, except that it crashes after a few minutes (usually, but not always, when I try to save). The console output gives a message about too many files open: err:winediag:FILE_CreateFile Too many open files, ulimit -n probably needs to be increased I note that this is the same problem reported by Comment #10 of Bug 18975. I haven't tried increasing my maximum number of open file descriptors. It's currently set to 1024, though I think it would be bizarre for the game to require even that many. Unfortunately, it is not possible for me to get a backtrace. When I use winedbg, the game slows to a crawl and it's impossible to do anything. -- 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.

2 6

[Bug 21983] New: Buttons come on each other in Proteus
by wine-bugs＠winehq.org 16 Jul '23

16 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=21983 Summary: Buttons come on each other in Proteus Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ssserkkk(a)yahoo.com hi! The buttons in ISIS and ARES come on each other. The ones that create this problem are "subcircuit mode ile terminals mode", "virtual instruments mode and 2D graphics line mode" in ISIS program; "connectivity highlight mode and round through-hole pad mode", "padstack mode and 2D graphics line mode" in ARES. -- 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.

2 31

[Bug 31278] New: The Longest Journey: "eye-mouth-hand" dialog only appears sometimes (randomly?)
by wine-bugs＠winehq.org 14 Jul '23

14 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=31278 Bug #: 31278 Summary: The Longest Journey: "eye-mouth-hand" dialog only appears sometimes (randomly?) Product: Wine Version: 1.5.9 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: rmmartins(a)gmail.com Classification: Unclassified This bug has been described by Octavian Vocu on one of his comments in another bug report from the same game (http://bugs.winehq.org/show_bug.cgi?id=11819#c39). I'm pasting an excerpt of his comment below because it explains exactly what's happening: "There is still some issue related to doing actions on objects, with the mouse. Clicking an actionable object should display the eye-mouth-hand dialog. Mouse shows correct pointer, but simply clicking has no effect. I noticed that as you push the left mouse button, you need to move the mouse slightly for the action dialog to appear. Might be related to transparent windows, not sure yet." It's certainly a different bug and deserves a different report, that's why I'm creating this. I've tested this on Debian Sid (i386) with wine-1.5.9. The console output is small, so I just pasted it below; the messages look the same as every other bug report on the game. The last three fixme's repeat a million times. fixme:win:EnumDisplayDevicesW ((null),0,0x33eb04,0x00000000), stub! fixme:ddraw:ddraw7_Initialize Ignoring guid {00000000-0000-0000-0000-000000000000}. fixme:d3d_surface:wined3d_surface_flip Ignoring flags 0x1. fixme:d3d_surface:surface_load_location Unimplemented location SFLAG_INSYSMEM for depth/stencil buffers. fixme:d3d_surface:surface_unmap Depth / stencil buffer locking is not implemented. fixme:d3d:state_subpixel Render state WINED3D_RS_SUBPIXEL not implemented yet. fixme:d3d:state_flushbatch Render state WINED3D_RS_FLUSHBATCH not implemented yet. fixme:d3d_surface:surface_load_location Unimplemented location SFLAG_INSYSMEM for depth/stencil buffers. fixme:d3d_surface:surface_load_location Unimplemented location SFLAG_INSYSMEM for depth/stencil buffers. fixme:d3d_surface:surface_unmap Depth / stencil buffer locking is not implemented. It might be important to notice that Octavian was probably on the right track of fixing this with his previous patches. The game runs pretty well on 1.3.32 with three of his patches (http://bugs.winehq.org/show_bug.cgi?id=11819#c37); the issue reported here is the main thing keeping it from being almost perfect. Also, on a 1.5.9 with the same three patches (even though the characters are invisible again) the following three messages appear when you click an object (when the dialog should be displayed): fixme:x11drv:X11DRV_WindowPosChanged transparent window, fixing window rect fixme:x11drv:X11DRV_WindowPosChanged transparent window, fixing window rect fixme:x11drv:X11DRV_WindowPosChanged transparent window, fixing window rect -- 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.

2 24

[Bug 41976] New: Very high CPU usage while downloading stuff in Steam
by wine-bugs＠winehq.org 14 Jul '23

14 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=41976 Bug ID: 41976 Summary: Very high CPU usage while downloading stuff in Steam Product: Wine Version: 2.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: t.artem(a)mailcity.com Distribution: --- I'm now downloading Crysis in the latest Steam/Wine releases and CPU usage is extremely high: PID USER PR NI VIRT RES %CPU %MEM TIME+ nTH COMMAND 31543 birdie 20 0 2731.0m 227.1m 51.7 1.4 6:43.52 42 Steam.exe 31401 birdie 20 0 8.0m 5.6m 49.0 0.0 5:44.30 1 wineserver One extra note: I'm downloading to tmpfs so disk IO has zero effect on this process. The current download speed is around 3MB/sec (24Mb/sec). This is a bug. -- 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.

2 20

[Bug 36511] New: widl fails to build with clang -fsanitize=undefined
by wine-bugs＠winehq.org 14 Jul '23

14 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=36511 Bug ID: 36511 Summary: widl fails to build with clang -fsanitize=undefined Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com make[1]: Entering directory `/home/austin/src/wine-clang/tools/widl' clang -fsanitize=undefined -m32 -g -O2 -o widl client.o expr.o hash.o header.o proxy.o register.o server.o typegen.o typelib.o typetree.o utils.o widl.o write_msft.o parser.tab.o parser.yy.o ../../libs/wpp/libwpp.a ../../libs/port/libwine_port.a ../../libs/wpp/libwpp.a(ppy.tab.o): In function `ppy_parse': /home/austin/src/wine-clang/libs/wpp/ppy.y:397: undefined reference to `__mulodi4' /home/austin/src/wine-clang/libs/wpp/ppy.y:397: undefined reference to `__mulodi4' /home/austin/src/wine-clang/libs/wpp/ppy.y:397: undefined reference to `__mulodi4' clang: error: linker command failed with exit code 1 (use -v to see invocation) make[1]: *** [widl] Error 1 make[1]: Leaving directory `/home/austin/src/wine-clang/tools/widl' make: *** [tools/widl] Error 2 -- 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.

2 6

[Bug 42562] New: Act of War stuck at open (GOG and Steam Versions Affected )
by wine-bugs＠winehq.org 13 Jul '23

13 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=42562 Bug ID: 42562 Summary: Act of War stuck at open (GOG and Steam Versions Affected) Product: Wine Version: 2.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrdeathjr28(a)yahoo.es Distribution: --- Act of War direct action steam and gog versions stuck at try open, one cpu core go to 100% and actofwar.exe process cant be closed -- 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.

2 15

[Bug 39830] New: TomTom Home 2 TomTomHOMERuntime.exe failed with Error 87
by wine-bugs＠winehq.org 13 Jul '23

13 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=39830 Bug ID: 39830 Summary: TomTom Home 2 TomTomHOMERuntime.exe failed with Error 87 Product: Wine Version: 1.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: detlef.bieritz(a)gmx.de Distribution: --- Created attachment 53171 --> https://bugs.winehq.org/attachment.cgi?id=53171 Screenshot Ubuntu 15.10 Wine 1.8 TomTom Home 2 TomTomHOMERuntime.exe failed with Error 87: Ungültiger Parameter (siehe Screenshot) Installation: OK Start: NOK Run: NOK -- 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.

2 13

[Bug 45070] New: closing threads causes "wine client error" and kills process when run under winedbg --gdb
by wine-bugs＠winehq.org 13 Jul '23

13 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=45070 Bug ID: 45070 Summary: closing threads causes "wine client error" and kills process when run under winedbg --gdb Product: Wine Version: 3.6 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Created attachment 61208 --> https://bugs.winehq.org/attachment.cgi?id=61208 test program showing problem When run under winedbg in gdb mode, closing a thread consistently causes 'wine client error:30: write: Bad file descriptor', aborting the program. The basic problem seems to be that gdb will inject breakpoints into dlopen() to allow hooking that function if desired. Normally this works fine, but this can also be triggered during thread teardown, i.e. inside of pthread_exit(). In this case we catch the SIGTRAP, but abort when we try to pass it along to wineserver, since we've already closed our file handle to the server pipe. The obvious solution seems to be to block SIGTRAP during thread shutdown. Attempting this makes the 'bad file descriptor' message go away, but the process still gets killed prematurely. I haven't figured out why. -- 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.

2 6

[Bug 33257] New: Adobe Digital Editions does not recognize KOBO eReader.
by wine-bugs＠winehq.org 13 Jul '23

13 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=33257 Bug #: 33257 Summary: Adobe Digital Editions does not recognize KOBO eReader. Product: Wine Version: 1.4.1 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: peterharris20(a)sky.com Classification: Unclassified Adobe Digital Editions does not find the KOBO eReader when it is plugged in. Ubuntu 10.04 recognizes it and displays the folder and contents. -- 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.

2 11

[Bug 37466] New: Deadly Premonition: The Director's Cut 1.01b Steam crash after logos
by wine-bugs＠winehq.org 13 Jul '23

13 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=37466 Bug ID: 37466 Summary: Deadly Premonition: The Director's Cut 1.01b Steam crash after logos Product: Wine Version: 1.7.29 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: david.gamiz(a)gmail.com Distribution: --- Created attachment 49840 --> https://bugs.winehq.org/attachment.cgi?id=49840 log and trace crash wine Install, run launcher and run game. After logos the game crash. Overlay steam is OFF. WinXP config. 32bit wine 1.7.29 -- 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.

2 20

[Bug 45477] New: the forest - settings not saved
by wine-bugs＠winehq.org 11 Jul '23

11 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=45477 Bug ID: 45477 Summary: the forest - settings not saved Product: Wine Version: 3.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bronsonmathews(a)gmail.com Distribution: --- The settings for this game are stored in the registry. And when changing the settings in game they are not saved into the registry. Settings are located at the following location: HKEY_CURRENT_USER\Software\SKS\TheForest -- 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.

2 3

[Bug 41429] New: The Forest: Game crashes if started from Steam
by wine-bugs＠winehq.org 11 Jul '23

11 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=41429 Bug ID: 41429 Summary: The Forest: Game crashes if started from Steam Product: Wine Version: 1.9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sworddragon2(a)aol.com Distribution: --- Created attachment 55803 --> https://bugs.winehq.org/attachment.cgi?id=55803 Terminal output If The Forest gets started from Steam the game shows its configuration dialog and on clicking "Play!" the game crashes after a few seconds. But if the game gets directly started all is working fine no matter if Steam is already running or not (and if the multiplayer works too). -- 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.

2 7

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs February 2019