June 2022 - wine-bugs

[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 52242] New: Mouse cursor disappears in GTA V when Social Club overlay is on
by WineHQ Bugzilla 28 Jul '23

28 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52242 Bug ID: 52242 Summary: Mouse cursor disappears in GTA V when Social Club overlay is on Product: Wine Version: 6.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vutov.martin97(a)gmail.com Distribution: --- Whenever you try to open the Social Club overlay, the cursor disappears. If you manage to press something with it, it works, it just can't be seen. Sometimes it works, but very rarely. Haven't figured why it works in said cases. To reproduce: Start GTA V Wait for it to load to home screen Press "Home" button for Social Club overlay to appear No mouse I am new when it comes to Linux so I've no idea where to get a log from. If someone tells me how I'll be more than glad to do so. I am launching the game via Lutris with the Rockstar Games Launcher installer. -- 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 3

[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 52065] New: Rockstar Games Launcher Installer is leaking memory
by WineHQ Bugzilla 27 Jul '23

27 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52065 Bug ID: 52065 Summary: Rockstar Games Launcher Installer is leaking memory Product: Wine Version: 6.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com Distribution: --- When installing Rockstar Games Launcher via its installer, the installer never quits and is shown to be stuck on the loading bar. During that, the app is leaking memory really fast, filling up my 32GBs of ram in approximately 1 minute. I can only track the issue down to 6.20 since that's the version the installer started working at, but it's present in 6.22 too. Strangely enough, after you kill its process, the installer actually succeeds at its jos and successfully installs the launcher. I don't know what I can provide to help with this, apart from the link to the installer, so let me know. -- 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 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 50631] New: Old programs on https://www.winehq.org/irc
by WineHQ Bugzilla 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=50631 Bug ID: 50631 Summary: Old programs on https://www.winehq.org/irc Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: jkfloris(a)dds.nl Distribution: --- On https://www.winehq.org/irc the following programs are mentioned. X-Chat last update 2010 Sidenet last update 2006 WineDoors last update 2013 Cedega IEs4Linux Do people really still use these programs? Perhaps the last four programs can be replaced by PlayOnLinux and PlayOnMac -- 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 50866] New: Accessing https://www.winehq.org/pipermail/ will make the whole website inaccessible
by WineHQ Bugzilla 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=50866 Bug ID: 50866 Summary: Accessing https://www.winehq.org/pipermail/ will make the whole website inaccessible Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: huupoke12(a)gmail.com Distribution: --- After accessing https://www.winehq.org/pipermail/ (the trailing slash is present), the user can't access any other www.winehq.org webpages. -- 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 7

[Bug 52439] New: apt-key is deprecated (bookworm/Debian)
by WineHQ Bugzilla 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52439 Bug ID: 52439 Summary: apt-key is deprecated (bookworm/Debian) Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: osamu(a)debian.org Distribution: --- apt-key(8) will last be available in Debian 11 and Ubuntu 22.04. For Debian/bookworm (12) (and probably for Ubuntu 22.10), apt-key usage as described. This affects following pages: * https://wiki.winehq.org/Debian * https://wiki.winehq.org/Ubuntu Specifically: ``` wget -nc https://dl.winehq.org/wine-builds/winehq.key sudo apt-key add winehq.key ``` The above should be changed to: * For Debian up to Buster(11): ``` wget -nc https://dl.winehq.org/wine-builds/winehq.key sudo apt-key add winehq.key ``` * For Debian from Bookworm (12): ``` wget -nc https://dl.winehq.org/wine-builds/winehq.key sudo cp winehq.key /etc/apt/trusted.gpg.d/winehq.gpg ``` I only tested this for Debian .... Osamu -- 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 53033] New: mirrors.ibiblio.org is no more
by WineHQ Bugzilla 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=53033 Bug ID: 53033 Summary: mirrors.ibiblio.org is no more Product: WineHQ.org Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: blocker Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com https://mirrors.ibiblio.org/wine/source/7.x/wine-7.9.tar.xz 404 Not Found https://mirrors.ibiblio.org/wine/source/7.x/wine-7.8.tar.xz 404 Not Found -- 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 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 52802] New: Dead/broken links / stale data
by WineHQ Bugzilla 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52802 Bug ID: 52802 Summary: Dead/broken links / stale data Product: WineHQ Bugzilla Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com CC: austinenglish(a)gmail.com Both: Add Bugzilla to Sidebar (requires a Mozilla browser like Mozilla Firefox) Install the Quick Search plugin (requires Firefox 2 or Internet Explorer 7) Are dead and could be removed. -- 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 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 52162] New: Ubuntu windows program has com1 the PIC micro programmer has usb device shows on /dev/ttyUSB0
by WineHQ Bugzilla 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52162 Bug ID: 52162 Summary: Ubuntu windows program has com1 the PIC micro programmer has usb device shows on /dev/ttyUSB0 Product: Wine Version: 6.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: usb Assignee: wine-bugs(a)winehq.org Reporter: mw0sbx(a)hotmail.com Distribution: --- marc@SPUPERMICRO-X9DRH-iF:~/.wine/drive_c/windows$ wine --version wine-5.0 (Ubuntu 5.0-3ubuntu1) Ubuntu - windows program has COM1 the PIC micro programmer has usb leed the device shows up using dmesg -w as /dev/ttyUSB0 program is called MicroPro.exe tried editing the wine registry as stated online by adding HKEY local machine >>> software >> wine >> ports string value COM1 >> DATA /dev/ttyUSB0 dmesg -w [ 2059.674461] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2059.674466] usb 2-1.2: Product: USB <-> Serial [ 2059.674469] usb 2-1.2: Manufacturer: FTDI [ 2059.675373] ftdi_sio 2-1.2:1.0: FTDI USB Serial Device converter detected [ 2059.675448] usb 2-1.2: Detected FT232BM [ 2059.675906] usb 2-1.2: FTDI USB Serial Device converter now attached to ttyUSB0 Still doesn't work no matter what i try program keeps reporting problem with coms port. -- 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 13

[Bug 52081] New: usbip: error: vhci driver is not loaded
by WineHQ Bugzilla 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52081 Bug ID: 52081 Summary: usbip: error: vhci driver is not loaded Product: Wine Version: 6.22 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 Distribution: --- When trying to install and use the usbip-win client https://github.com/cezanne/usbip-win/releases/download/v0.3.5/usbip-win-0.3… trying to attach a remote usb device fails with the usbip: error: vhci driver is not loaded This happens with the released version of usbip-win v0.3.5 as well as with a self-compiled version of usbip-win where the has_certificate function is disabled. Below are the steps to reproduce. In order to test this, are usbip server (in my case this is on "donglerasp") where "usbipd -D" is running and a usb device is exported with usbip bind --busid=1-1.2.3 $ wine usbip.exe install -w usbip: error: root driver already exist 0100:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000011FC20 $ wine usbip.exe list -r donglerasp Exportable USB devices ====================== - donglerasp 1-1.2.3: unknown vendor : unknown product (0529:0001) : /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2.3 : unknown class / unknown subclass / unknown protocol (ff/00/00) : 0 - unknown class / unknown subclass / unknown protocol (ff/00/00) 0100:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000011FC20 $ wine usbip.exe attach -r donglerasp -b "1-1.2.3" usbip: error: vhci driver is not loaded 0118:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000011FC20 -- 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 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 49972] New: Termie 1.0 crashes after selecting a serial port.
by WineHQ Bugzilla 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=49972 Bug ID: 49972 Summary: Termie 1.0 crashes after selecting a serial port. Product: Wine Version: 5.18 Hardware: x86-64 URL: http://termie.sourceforge.net/#downloads OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: ArchLinux Created attachment 68373 --> https://bugs.winehq.org/attachment.cgi?id=68373 Console messages Summary Termie 1.0 crashes after selecting a serial port. Download location http://termie.sourceforge.net/#downloads http://termie.sourceforge.net/Termie-1.0-Binary.zip $ sha256sum Termie-1.0-Binary.zip 53469ffdb38058b985482cbfac3f4c0575eeafa4e1b766b5f0c2af43acb7cba6 Termie-1.0-Binary.zip $ unzip Termie-1.0-Binary.zip Steps to reproduce: 1)Start the program: $ wine Termie.exe After a long time (+- 20 seconds) the program opens. 2) Select one of the comm port. Now the program crashes. 3) Press ctrl-c in the console to kill wine. 4) restart Termie. $ wine Termie.exe Now wine gives this error. "[ERROR] FATAL UNHANDLED EXCEPTION: System.IO.IOException: Broken pipe." Every time Termie is restarted via step 3, it crashes the same way. My versions $ wine --version wine-5.18 (Staging) $ pacman -Q wine wine-staging 5.18-1 uname -a Linux cedric-p4 5.8.14-arch1-1 #1 SMP PREEMPT Wed, 07 Oct 2020 23:59:46 +0000 x86_64 GNU/Linux -- 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 49974] New: termite-3.4 can't connect to com5 -> /dev/ttyACM0
by WineHQ Bugzilla 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=49974 Bug ID: 49974 Summary: termite-3.4 can't connect to com5 -> /dev/ttyACM0 Product: Wine Version: 5.18 Hardware: x86-64 URL: https://www.compuphase.com/software_termite.htm OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: ArchLinux Created attachment 68375 --> https://bugs.winehq.org/attachment.cgi?id=68375 console messages Summary termite-3.4 can't connect to com5 -> /dev/ttyACM0 Prepare wine: $ rm -rf ~/.wine/ $ wineserver -k $ wineboot Download location https://www.compuphase.com/software_termite.htm https://www.compuphase.com/software/termite-3.4.exe $ sha256sum termite-3.4.exe ca440b6c7f6eaa812ba5f8bf42aed86e02022ca50a1c72585168c9b671d0fe19 termite-3.4.exe Steps to reproduce: 1) Install the program: $ wine termite-3.4.exe Accept the defaults. Now termite starts. 2) Press settings. The dropdown box only shows COM1. Choose baud rate 9600 and press OK. Now termite reports "Failed to initialize the port. Please verify the COM port settings." 3) Press "Connect". Now that termite reports "Waiting for port" 4) Press close. Now termite closes. As a sanity test, I open moserial, choose /dev/ttyACM0 9600,8N1, press connect, and I see the messages my MCP2221 serial to USB converter is sending to me. /dev/ttyACM0 is detected by wine: $ ls -l ~/.wine/dosdevices/ total 0 lrwxrwxrwx 1 cedric cedric 10 Oct 10 19:25 c: -> ../drive_c lrwxrwxrwx 1 cedric cedric 10 Oct 10 19:35 com1 -> /dev/ttyS0 lrwxrwxrwx 1 cedric cedric 12 Oct 10 19:35 com5 -> /dev/ttyACM0 lrwxrwxrwx 1 cedric cedric 8 Oct 10 19:26 d:: -> /dev/sr0 lrwxrwxrwx 1 cedric cedric 1 Oct 10 19:25 z: -> / My versions $ wine --version wine-5.18 (Staging) $ pacman -Q wine wine-staging 5.18-1 uname -a Linux cedric-p4 5.8.14-arch1-1 #1 SMP PREEMPT Wed, 07 Oct 2020 23:59:46 +0000 x86_64 GNU/Linux -- 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 49752] New: Mikster MPC4 System: 'Selected serial port not exist'
by WineHQ Bugzilla 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=49752 Bug ID: 49752 Summary: Mikster MPC4 System: 'Selected serial port not exist' Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: amad4wine2020(a)gmail.com Distribution: --- Log in as 'Adm' user, go to the 'Controllers list', press the 'Add' button, select the appropriate 'Port COM' and 'Baud rate', press the 'Test' button, you will probably get an error message containing the phrase 'Selected serial port not exist'. I have tried the following registry keys: [System\\CurrentControlSet\\Enum\\SERIAL\\COM2\\COM2] 1598720497 #time=1d67e260ec36dbc "ClassGUID"="{4D36E978-E325-11CE-BFC1-08002BE10318}" "FriendlyName Value"="Serial Port (COM2)" [Software\\Wine\\Ports] 1598713705 #time=1d67e163e9541c4 "COM2"="/dev/ttyS1" Unfortunately, it makes no difference. Download links from the software's website: https://mikster.eu/en/download-center/ https://mikster.eu/wp-content/uploads/2019/03/installmpc482ENG.zip P.S. The installer will silently install FirebirdSQL 1.5 and enable Firebird Guardian, it does not work well with winehq-devel. Unpack the installmpc482ENG.exe and rename the included installmpc482ENG/firebird/FirebirdWin32.exe before continuing with the installation. Install the renamed FirebirdWin32.exe manually (uncheck the 'Use the Guardian to control the server?' option during the installation). -- 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 26

[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 52899] New: gdi32:font - test_fullname2() fails in non-English Windows 7 locales
by WineHQ Bugzilla 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52899 Bug ID: 52899 Summary: gdi32:font - test_fullname2() fails in non-English Windows 7 locales Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com test_fullname2() fails in non-English Windows 7 locales. For instance in German (I removed duplicate lines): font.c:5710: Test failed: Arial: style names don't match: returned Regular, expect Standard [...] font.c:5700: Test failed: Arial: font face names don't match: returned Arial Italic, expect Arial Kursiv font.c:5710: Test failed: Arial: style names don't match: returned Italic, expect Kursiv [...] font.c:5700: Test failed: Arial: font face names don't match: returned Arial Bold, expect Arial Fett font.c:5710: Test failed: Arial: style names don't match: returned Bold, expect Fett [...] font.c:5700: Test failed: Arial: font face names don't match: returned Arial Bold Italic, expect Arial Fett Kursiv font.c:5710: Test failed: Arial: style names don't match: returned Bold Italic, expect Fett Kursiv font.c:5710: Test failed: Tahoma: style names don't match: returned Regular, expect Standard [...] font.c:5700: Test failed: Tahoma: font face names don't match: returned Tahoma Bold, expect Tahoma Fett font.c:5710: Test failed: Tahoma: style names don't match: returned Bold, expect Fett [...] font.c:5710: Test failed: Webdings: style names don't match: returned Regular, expect Standard font.c:5710: Test failed: Wingdings: style names don't match: returned Regular, expect Standard https://test.winehq.org/data/patterns.html#gdi32:font Spanish and Portuguese (pt_PT) get the same set of errors but with their own localized names. Mark these tests as broken on Windows 7? win_skip() them? -- 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 3

[Bug 51391] New: On Windows 7 and 8.1 ntoskrnl.exe:ntoskrnl triggers a network firewall dialog, breaks user32:win
by WineHQ Bugzilla 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=51391 Bug ID: 51391 Summary: On Windows 7 and 8.1 ntoskrnl.exe:ntoskrnl triggers a network firewall dialog, breaks user32:win Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com On Windows 7 and 8.1 ntoskrnl.exe:ntoskrnl triggers a network firewall dialog (see the screenshots for the TestBot WineTest runs on w7u_2qxl and w8). Despite that ntoskrnl.exe:ntoskrnl succeeds. However it leaves that dialog open which then causes two failures in user32:win: https://test.winehq.org/data/patterns.html#user32:win win.c:3394: Test failed: GetActiveWindow() = 00000000 win.c:3394: Test failed: GetFocus() = 00000000 Notes: * These are the same failures as in bug 51390. If it is decided that user32:win is the test that needs fixing then this bug could be merged. * But if the decision is that ntoskrnl.exe:ntoskrnl should either not trigger such a dialog or close it, then this bug should remain separate. * Most of ntoskrnl.exe:ntoskrnl is skipped on Wow64 so this issue does not happen in newtb-w864-32. * The 64-bit ntoskrnl.exe:ntoskrnl test also does not trigger that dialog for some reason. -- 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 5

[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 47873] New: kernel32:comm fails randomly
by WineHQ Bugzilla 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=47873 Bug ID: 47873 Summary: kernel32:comm fails randomly Product: Wine Version: 4.17 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:comm fails randomly on multiple Windows versions: comm.c:708: Found Com port COM1. Connected devices may disturb results comm.c:859: Test failed: WaitCommEvent failed with a timeout comm.c:870: recovering after WAIT_TIMEOUT... comm.c:880: Test failed: WaitCommEvent error 0 comm.c:881: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:885: WaitCommEvent for EV_TXEMPTY took 1500 ms (timeout 1500) comm.c:886: Test failed: WaitCommEvent used 1500 ms for waiting https://test.winehq.org/data/tests/kernel32:comm.html These failures are random and have been seen on the following TestBot VM4 configurations: wxppro w2003std w7pro64-32 w1064v1507-32 w1064v1607-32 w1064v1607-64 w1064v1709-64 w1064v1607-64 w1064v1809-32 w1064v1809-32 w1064v1809-64 w1064v1809-2scr-32 w1064v1809-fr-64 w1064v1809-ja-32 w1064v1809-ja-64 So it does not depend on the Windows version, bitness of the test, or locale. However it only happens on QEmu VMs: it never happened on the fg-win7u64 VMware VMs or on the real hardware machines, cw-rx460 and cw2-gtx560. Yet the VMware VMs have two serial COM ports, and, according to dmesg | grep tty, the real hardware machines do have a serial port too. QEmu 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.

1 3

[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 50778] New: TortoiseMerge closes before showing a window
by WineHQ Bugzilla 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=50778 Bug ID: 50778 Summary: TortoiseMerge closes before showing a window Product: Wine Version: 6.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lexlexlex(a)gmail.com Distribution: --- Created attachment 69576 --> https://bugs.winehq.org/attachment.cgi?id=69576 Terminal log for TortoiseMerge startup and subsequent closing with wine Steps to reproduce: 1. Install TortoiseSVN in a 64-bit wine prefix. 2. Try to run TortoiseMerge.exe with the wine prefix mentioned in step 1. For example, run "wine TortoiseMerge.exe" from a terminal if the default wine prefix was used. Current behavior: TortoiseMerge closes before showing a window. No TortoiseMerge window appears. Expected behavior: TortoiseMerge is expected to start, allowing the user to compare and merge files in a windowed GUI. Additional information: A download for the current version of the TortoiseSVN installer as of this report is at https://osdn.net/projects/tortoisesvn/storage/1.14.1/Application/TortoiseSV… A log showing terminal output when trying to run "wine TortoiseMerge.exe" is attached. Opinion: This is one of 2 bugs preventing using TortoiseSVN fully in wine. The other is 50756. If these 2 bugs are fixed, TortoiseSVN could be used fully, easing the transition of users whose jobs rely on SVN to Linux. Currently some companies still use SVN and I've tried all the free SVN clients for Linux, and none of them come close to the level of convenience and intuitiveness that TortoiseSVN provides. I have nemo actions ready to enable full usage in of TortoiseSVN in Linux if these 2 bugs are fixed. This would help me personally tremendously, as digging through old revisions in alternate SVN branches is part of my job and extremely difficult with any SVN client other than TortoiseSVN using TortoiseMerge. Thanks for reading this. -- 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 7

[Bug 51212] New: i want to install itunes, it installed through wine but giving some error while to launch the program
by WineHQ Bugzilla 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=51212 Bug ID: 51212 Summary: i want to install itunes, it installed through wine but giving some error while to launch the program Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: robinssgraphics(a)gmail.com Distribution: --- Created attachment 70086 --> https://bugs.winehq.org/attachment.cgi?id=70086 i want to install itunes, it installed through wine but giving some error while to launch the program i want to install itunes, it installed through wine but giving some error while to launch the program -- 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 3

[Bug 53247] New: user32:sysparams - test_dpi_context() fails on Windows 10 1909+
by WineHQ Bugzilla 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=53247 Bug ID: 53247 Summary: user32:sysparams - test_dpi_context() fails on Windows 10 1909+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:sysparams - test_dpi_context() fails on Windows 10 1909+: sysparams.c:3813: Test failed: got 0 sysparams.c:3814: Test failed: wrong value -1 https://test.winehq.org/data/patterns.html#user32:sysparams These traces could include a bit more information rather than leaving most of it to the source line number. -- 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 52838] New: MachStudio Pro renders wrong
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52838 Bug ID: 52838 Summary: MachStudio Pro renders wrong Product: Wine Version: 7.6 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: svyatpro(a)gmail.com Any project is being rendered wrong in MachStudio Pro. The problem is in Wine's D2D1.DLL. When using native Vista's d2d1.dll (7.0.6002.18107 809kb) this issue does not appear. Steps to repro: 1. Run MachStudio Pro 2. Open a project for example by this path \Program Files\StudioGPU\MachStudio Pro\Data\assets\SGPU_MTL_BALL.mab Uploaded two screenshots: Wine's d2d1.dll and native d2d1.dll from Vista. Free GPU MachStudio Pro download link: https://download.cnet.com/MachStudio-Pro/3000-6677_4-75498419.html -- 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 6

[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 51669] New: EverQuest d3d:wined3d acquires unexpected context
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=51669 Bug ID: 51669 Summary: EverQuest d3d:wined3d acquires unexpected context Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: johnherschelfreeman2013(a)gmail.com Distribution: --- Created attachment 70543 --> https://bugs.winehq.org/attachment.cgi?id=70543 err wined3d_context_gl_reacquire In game launcher and game client -- 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 5

[Bug 53198] New: ws2_32:protocol - getaddrinfo() unexpectedly succeeds for IPv6 on Windows 10 1507
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=53198 Bug ID: 53198 Summary: ws2_32:protocol - getaddrinfo() unexpectedly succeeds for IPv6 on Windows 10 1507 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ws2_32:protocol - getaddrinfo() unexpectedly succeeds for IPv6 on Windows 10 1507: protocol.c:2459: Test failed: Test 0: Got unexpected ret 0 protocol.c:2459: Test failed: Test 1: Got unexpected ret 0 protocol.c:2459: Test failed: Test 2: Got unexpected ret 0 protocol.c:2459: Test failed: Test 3: Got unexpected ret 0 protocol.c:2459: Test failed: Test 4: Got unexpected ret 0 protocol.c:2459: Test failed: Test 5: Got unexpected ret 0 protocol.c:2459: Test failed: Test 12: Got unexpected ret 0 protocol.c:2459: Test failed: Test 13: Got unexpected ret 0 protocol.c:2459: Test failed: Test 14: Got unexpected ret 0 protocol.c:2459: Test failed: Test 15: Got unexpected ret 0 protocol.c:2459: Test failed: Test 16: Got unexpected ret 0 protocol.c:2459: Test failed: Test 28: Got unexpected ret 0 protocol.c:2459: Test failed: Test 29: Got unexpected ret 0 https://test.winehq.org/data/patterns.html#ws2_32:protocol This really looks like a Windows 10 1507 bug so it's tempting to add a broken((hinttests[i].family == AF_UNSPEC && hinttests[i].sock_type != 999) && ...). But it's strange that there is no failure on index 6 for instance since it's the same test after line 2455 (hint.ai_family = AF_INET6): 0: {AF_UNSPEC, SOCK_STREAM, IPPROTO_TCP, 0}, /* 0 */ 6: {AF_INET, SOCK_STREAM, IPPROTO_TCP, 0}, -- 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 52826] New: All windows are grayed out. text is unreadable
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52826 Bug ID: 52826 Summary: All windows are grayed out. text is unreadable Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mmikeinsantarosa(a)gmail.com Distribution: --- Created attachment 72213 --> https://bugs.winehq.org/attachment.cgi?id=72213 grayed out windows sample cardfile.exe windows are grayed out. No text is readable. Bug has been present since wine-6.6. link to cardfile.exe and its help file on my google drive https://drive.google.com/file/d/1uIJo1qtE1sQYQvgUsjiYHxBbU-ZhXehk/view?usp=… -- 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 9

[Bug 52117] New: All windows are blacked out when running 16 bit cardfile.exe
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52117 Bug ID: 52117 Summary: All windows are blacked out when running 16 bit cardfile.exe Product: Wine-staging Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mmikeinsantarosa(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 71147 --> https://bugs.winehq.org/attachment.cgi?id=71147 top window is unreadable due to being filled with black. All windows are blacked out when running 16 bit cardfile.exe. The program runs but text in any visible window is blacked out. The cardfile.exe and its help can be downloaded from this link https://drive.google.com/file/d/1uIJo1qtE1sQYQvgUsjiYHxBbU-ZhXehk/view?usp=… -- 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 12

[Bug 52576] New: Cardfile windows are grayed out
by WineHQ Bugzilla 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52576 Bug ID: 52576 Summary: Cardfile windows are grayed out Product: Wine-staging Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mmikeinsantarosa(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 71902 --> https://bugs.winehq.org/attachment.cgi?id=71902 selected window grayed out Program: cardfile.exe (16bit originally released in windows 3.1) Symptom: selected windows are grayed out making any text unreadable. History: this bug has been present in wine & wine-staging since release 6.6 The bug was not present in wine/wine-staging 6.5 -- 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 3

[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 51406] New: riched32:editor fails in Wine on right-to-left locales
by WineHQ Bugzilla 22 Jul '23

22 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=51406 Bug ID: 51406 Summary: riched32:editor fails in Wine on right-to-left locales Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: richedit Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- riched32:editor fails in Wine when run in the Arabic (EG and MA) and Hebrew (IL) locales: https://test.winehq.org/data/patterns.html#riched32:editor editor.c:122: Test failed: [2] EM_GETLINECOUNT returned 2, expected 2 editor.c:122: Test failed: [5] EM_GETLINECOUNT returned 3, expected 3 editor.c:122: Test failed: [6] EM_GETLINECOUNT returned 4, expected 4 editor.c:122: Test failed: [14] EM_GETLINECOUNT returned 3, expected 3 editor.c:122: Test failed: [15] EM_GETLINECOUNT returned 4, expected 4 editor.c:455: Test failed: 1: expected_bytes_written=2 editor.c:455: Test failed: 2: expected_bytes_written=4 editor.c:455: Test failed: 3: expected_bytes_written=5 editor.c:455: Test failed: 4: expected_bytes_written=3 editor.c:876: Test failed: EM_POSFROMCHAR reports x=1, expected 8 editor.c:902: Test failed: EM_POSFROMCHAR reports x=1, expected 8 In both cases the failure are the same. Also the test succeeds in the corresponding locales on Windows 2004. The test on line 122 fails because Wine returns the same values in RTL locales as in LTR ones. -- 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 49772] New: Memory safety issues in widl
by WineHQ Bugzilla 22 Jul '23

22 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=49772 Bug ID: 49772 Summary: Memory safety issues in widl Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: kolan_n(a)mail.ru Distribution: --- I have tried to compile some type libraries missing in MinGW-w64 and Wine and ReactOS SDKs too (more precisely, sapiddk.idl) into headers from the files in Windows SDK (used Windows 10 SDK). MinGW-w64 widl has crashed without producing any output, just left some files with garbled filenames (looks like a zero terminator got missing in a C string). So I have built wine widl. It has also crashed, but at least produced some meaningful output. -- 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 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 53092] New: Animated Puzzles crashes on start
by WineHQ Bugzilla 22 Jul '23

22 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=53092 Bug ID: 53092 Summary: Animated Puzzles crashes on start Product: Wine Version: 7.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user16 Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- 16bit application Animated Puzzles crashes on start. This bug report tracks commit https://github.com/otya128/winevdm/commit/9868db40f249595fcffc57050ce4a29ae… in otvdm. The same fix in Wine makes the application start and run correctly. -- 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 6

[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

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 June 2022