September 2019 - Wine-Bugs - list.winehq.org

[Bug 47846] New: Age Of Empires III Crash after Intro

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47846 Bug ID: 47846 Summary: Age Of Empires III Crash after Intro Product: Wine Version: 4.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: piedra-igor(a)hotmail.com Distribution: --- Created attachment 65351 --> https://bugs.winehq.org/attachment.cgi?id=65351 Log after running from the console I have recently installed the Complete Edition of Age Of Empires III along with all of the demanded components. Every time I run the game I get a crash to desktop while I'm on the loading screen just after the intro. I have already tried all solutions related to the NewProfile file on the My Games/Age of Empires 3/Users directory without any success. -- 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.

Sept. 30, 2019

[Bug 47845] Bug to x86_64

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47845 Phaase <haasesaah(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |haasesaah(a)gmail.com --- Comment #1 from Phaase <haasesaah(a)gmail.com> --- Created attachment 65350 --> https://bugs.winehq.org/attachment.cgi?id=65350 Unhandled exception: page fault on read access to 0xc000700f8 in 64-bit code (0x000000007bc981dd). -- 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.

Sept. 30, 2019

[Bug 47845] New: Bug to x86_64

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47845 Bug ID: 47845 Summary: Bug to x86_64 Product: Wine Version: 4.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: haasesaah(a)gmail.com Distribution: --- My original architecture was x64 but as I like play some games in x86 I did convert with add-apt-repository ppa: architecture i386 to turn over x86_64 and after that I had trouble within ever runnig up the games at x86 architecture. Well, I thought the x86_64 architecture would support both. As x86 and x64. Sorry about my barely english typewriting. Thank you so very much. -- 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.

Sept. 30, 2019

[Bug 10130] Wine does not compile on x86_64

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=10130 Phaase <haasesaah(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |haasesaah(a)gmail.com -- 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.

Sept. 30, 2019

[Bug 47844] Add a dual-screen Wine VM

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47844 --- Comment #2 from François Gouget <fgouget(a)codeweavers.com> --- One positive point: multi-head does not seem to break screenshots for Linux guests. Maybe because they run vdagent. Even better, the screenshot contains both screen. I also tried Xinerama mode, i.e. configuring the VM with two QXL graphics cards, in an attempt to avoid the issues mentioned in the previous post. However I could not get it to work with fvwm. -- 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.

Sept. 30, 2019

[Bug 47844] Add a dual-screen Wine VM

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47844 --- Comment #1 from François Gouget <fgouget(a)codeweavers.com> --- Officially multi-head setups are very easy with Linux guests in a QEmu VM, much easier than with Windows guests. But that's all lies. Here's what's really needed to get multi-head going with Debian 10. 1. virsh edit wtbdebian10 (this cannot be done from virt-manager!) Set heads=2 and double the memory in the QXL device. So this line <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> becomes: <model type='qxl' ram='131072' vram='131072' vgamem='32768' heads='2' primary='yes'/> 2. In the guest install the spice-vdagent package. However note that in Debian the required daemons are only started by desktop environments which honor /etc/xdg/autostart (i.e. GNOME). We cannot run GNOME since its window manager is not up to the task of running Wine's windowing tests. And fvwm does not start the required spice-vdagent daemon. 3. So it's necessary to start spice-vdagent manually when the X session starts. I found the easiest way to be to add a /etc/X11/Xsession.d/90local-spice-vdagent file containing: /usr/bin/spice-vdagent & 4. Note that spice-vdagentd is not started on boot despite the presence of a spice-vdagentd.service file. That's ok. That service is configured to start the vdagentd daemon on demand when its socket is used. So starting spice-vdagent as described above will trigger the start of spice-vdagentd. 5. With this setup Lightdm will not be running spice-vdagent. This can be fixed by setting either display-setup-script or greeter-setup-script: display-setup-script=/usr/bin/spice-vdagent However that does not seem to make any noticeable difference (see below) so I did not add this line. 6. Then virt-manager does not support multi-head displays. So once the VM has booted one must connect to it with virt-viewer wtbdebian10 and go to View -> Displays -> Display 2 to 'connect' the second screen. But there are some gotchas. a. First spice-vdagent must be running. This means waiting for the winetest user autologin. b. Then the second screen remains stuck in the 'Waiting for display 2' state. The workaround is to log out and Lightdm fixes it. Then wait for the autologin again. c. If you power off the VM the second screen will not be present on the next boot. It can be added back going through steps 6a and 6b again. I don't know of an API to add it back (it obviously exists but it may be a Spice API, not a Libvirt one). That means the TestBot cannot auto-create live snapshots for multi-head Wine VMs. d. Starting spice-vdagent in Lightdm changes none of the above. 7. Having a tablet (e.g. Virtio Tablet) for absolute mouse positions is not necessary but it helps if one moves the virt-viewer windows around. 8. I thought at a point that using the Q35+BIOS virtual hardware instead of the i440FX+BIOS one was necessary. But now I doubt so although I did not test to confirm it. To be fair, if one uses an Ubuntu/GNOME guest then the spice-vdagent issues are automatically taken care of. However this does not solve points 1 and 6c. Also vdagent is meant to integrate the guest with the host environment to allow for features like resizing the guest desktop by resizing the viewer window on the host, allow copy/paste to/from the guest, etc. None of this is useful to Wine tests, particularly since no viewer will be connected anyway. Hopefully this also means vdagent will not interfere with the Wine tests. -- 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.

Sept. 30, 2019

[Bug 47844] New: Add a dual-screen Wine VM

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47844 Bug ID: 47844 Summary: Add a dual-screen Wine VM Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Wine has tests that deal with multi-head displays. These would need some matching multi-head test Wine VMs. -- 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.

Sept. 29, 2019

[Bug 47838] Add a dual-screen Windows VM

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47838 --- Comment #1 from François Gouget <fgouget(a)codeweavers.com> --- With Windows guests adding a multi-head configuration is pretty easy: just configure it with two QXL graphics video cards. Then tell Windows how you want those two screens set up. The VM can then be rebooted or powered off and the two screens will still be there. Of course the TestBot has been using the basic VGA graphics video card a lot to minimize the Direct3D errors so switching to QXL may have an impact on the test results. But it could be argued that it also makes sense to test the QXL driver as that's what's meant to be used in QEmu's Windows guests. Maybe it will help improve the QXL driver. A side-effect of a dual-screen configuration is that it breaks the TestBot screenshots: all we get is a black screen that says "Guest has not initialized the display (yet).". Even testing with virt-viewer, taking a screenshot only captures the screen displayed by that window. Some investigation is necessary to see if there's a fix for that (we currently ask to capture screen 0: screenshot($Stream, 0, 0)). Another option would be to do the screenshots on the client side where we may be better able to deal with multiple screen setups (see bug 44709). -- 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.

Sept. 29, 2019

[Bug 47817] Gameforge Client: Cannot launch TERA

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47817 --- Comment #8 from nkb <pdot(a)tutanota.com> --- (In reply to wineuser from comment #7) > Can you try 'winetricks wmi' and see if you get the same result after that? Yup, same result. Setting both wbemprox and wmiutils as disabled gives another error: > Failed to create IWbemLocator object. Error code = 0xffffffff80070005. -- 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.

Sept. 29, 2019

[Bug 47834] Borderlands 1 (version 1.5.0) doesn't capture mouse

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47834 kolAflash <kolAflash(a)kolahilft.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kolAflash(a)kolahilft.de --- Comment #5 from kolAflash <kolAflash(a)kolahilft.de> --- (In reply to Alistair Leslie-Hughes from comment #2) > I've just updated the raw-input patchset in staging. Does this help? No, at least not in StarCraft II :-/ https://github.com/wine-staging/wine-staging/commit/0c7512f5f53deb168d3508b… Everything was fine wine-staging-4.16. -- 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.

Sept. 29, 2019