https://bugs.winehq.org/show_bug.cgi?id=51167
Bug ID: 51167
Summary: 2CAudio Breeze2 window is blank
Product: Wine
Version: 6.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: schroedingerscat(a)disroot.org
Distribution: ---
Created attachment 70035
--> https://bugs.winehq.org/attachment.cgi?id=70035
2CAudio Breeze2 Wine Log
Opening the UI window of Breeze2 (or any other plugin released by 2CAudio after
2019) will just show a blank UI. The included log is from exactly the moment
the plugin is loaded and the window opened.
Steps to reproduce:
1. Install Win x64 version of a VST2 compatible host (like REAPER:
http://reaper.fm/download.php)
2. Install Breeze2 VST2 x64 version (demo:
https://www.2caudio.com/products/breeze#_Breeze2)
3. Open reaper with wine (wine ~/.wine/path/to/where/you/installed/reaper.exe)
4. Add the Breeze2 VST2 installation directory to the host (In REAPER:
Options->Preferences->Plugins->VST and hit "Re-scan")
5. Load the Breeze2 plugin (In REAPER: Insert->Virtual Instrument on new
track->All Plugins->VST: Breeze2 (2C-Audio) and hit "Add")
6. The UI opens and is blank (bug)
If you move the mouse cursor over the blank window or click into it, you'll see
the last line from the log repeatedly.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=51166
Bug ID: 51166
Summary: wine doesn't handle multiple monitors correctly
Product: Wine
Version: 6.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
Part of this might be new (because of odd circumstances), another likely not,
but I don't see a clear duplicate.
1. I have two monitors, but usually keep one of them turned off. Today I had to
disconnect the primary and use the other one for awhile.
xrandr kept the dimensions cached after disconnect, so I've only switched
primary.
For some reason, wine kept starting apps on the old primary and when I've tried
moving the windows by keyboard to the other screen, they became
mouse-insensitive. This happened even to as simple apps as winecfg and taskmgr
- note some basic keyboard input was still possible, that is Esc still closed
those two.
When the other monitor got reconnected, things began working again.
2. This one might be known, but I'm unsure which one would be an effective dupe
(same problem, not same app dupe).
I've noticed this during the above mentioned problem, but this is broken even
after reconnecting.
RPGVXAce games fail to redraw their windows if after starting such game on one
monitor the window is moved onto the second monitor. Once it's moved back,
redraws resume.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=20439
Summary: TroopMaster hangs on startup
Product: Wine
Version: 1.1.31
Platform: PC-x86-64
URL: http://www.troopmaster.com
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: al_turner(a)comcast.net
TroopMaster installs, but hangs on startup. Main window will not activate
(animation works, but no response to keyboard or mouse). Does not even get to
the DotNet download hangup as mentioned in bug 8997. More like 18801 but I
don't even get the popup window showing the attempt to connect to FTP.
As far as I can tell, the FTP attempt only happens if you activate the DOTNET
function (after installing the software). I have not been able to get to the
point of activating the DOTNET since I can't get it that far yet.
I followed the HOWTO from the AppDB that describes the install/kill/restart
process.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=8997
Tim Williams <tjandacw(a)yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|tjandacw(a)yahoo.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.
https://bugs.winehq.org/show_bug.cgi?id=51101
Bug ID: 51101
Summary: Regression in PGVDemo:
C:\\windows\\Microsoft.NET\\Framework64\\v2.0.50727\\m
scorwks.dll could not be loaded
Product: Wine
Version: 6.7
Hardware: x86-64
URL: https://master.dl.sourceforge.net/project/phpgedview/1
%20PhpGedView/PhpGedView%20v4.2.3/PGV-Demo-4.2.3.zip?v
iasf=1
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
Hi, found while trying to test https://bugs.winehq.org/show_bug.cgi?id=22327
Steps to reproduce: winetricks dotnet20
It starts fine when I run 'wine64 PGVDemo'
When I run 'wine PGVDemo' it errors out with messagbox: "
C:\\windows\\Microsoft.NET\\Framework64\\v2.0.50727\\mscorwks.dll could not be
loaded "
This is recent regression; In wine-staging-6.7 the last command works fine
--
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.
https://bugs.winehq.org/show_bug.cgi?id=47150
Bug ID: 47150
Summary: [Overwatch] Game freezes when new menu music starts
playing
Product: Wine
Version: 4.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: hewanci(a)gmail.com
Distribution: ---
Few days ago the new Lucio and Mercy League skins were introduced, and the menu
got a new music, and a showcase of aforementioned new skins.
Since then the game freezes as soon as the menu music starts playing. The music
(and later the regular menu ambient music) still plays, but the GUI is frozen
and unresponsive.
The only workaround I could find was to very quickly open one of the sub-pages
(eg. Play, Hero gallery, etc.) before the music starts. This way the music will
never play, and then I can go back to the menu and everything works fine,
including the showcase of the new skins playing in the background.
Arch Linux, fully updated
Wine Staging 4.7
--
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.
https://bugs.winehq.org/show_bug.cgi?id=51151
Bug ID: 51151
Summary: The 64-bit psapi:psapi_main fails in Wine
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: psapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The 64-bit psapi:psapi_main test fails in Wine:
https://test.winehq.org/data/patterns.html#psapi:psapi_main
psapi_main.c:154: Test failed: got 0, error 998
psapi_main.c:155: Test failed: expected non-NULL module
psapi_main.c:159: Test failed: got error 998
psapi_main.c:160: Test failed: got
psapi_main.c:163: Test failed: got error 998
psapi_main.c:168: Test failed: got error 998
psapi_main.c:170: Test failed: image size was 0
These failures happen on both the TestBot VM and various real hardware
machines.
These failures started with this commit:
commit 5864bc88de0e0a3b1094c2bb0c16ba9a5d39ce65
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Thu May 13 15:58:33 2021 +0200
ntdll: Always send the native PEB pointer to the server.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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.
https://bugs.winehq.org/show_bug.cgi?id=50844
Bug ID: 50844
Summary: infosoft:infosoft crashes on Windows 10 1607+
Product: Wine
Version: 6.3
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
infosoft:infosoft crashes on Windows 10 1607+, regardless of bitness or
privileges:
infosoft.c:75: Test failed: wrong data
infosoft.c:73: Test failed: wrong length
[...repeated thousands of times...]
infosoft:infosoft:084c done (-1073741819) in 0s
Test failed: crash (c0000005)
These failures are new because WineTest was incorrectly skipping the infosoft:*
tests before.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=48054
Bug ID: 48054
Summary: gdi32:bitmap fails on Windows XP and 2003
Product: Wine
Version: unspecified
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gdi32:bitmap started failing on Windows XP and 2003 right after the winehq.org
upgrade:
bitmap.c:1015: Test failed: StretchDIBits failed for 32/62/0/0
bitmap.c:1023: Test failed: GetDIBits failed for 32/62/0/0
bitmap.c:1052: Test failed: StretchDIBits failed for 32/62/0/0
(repeated 12 times)
See http://winetest.dolphin/data/tests/gdi32:bitmap.html
See also the attached screenshot showing the failures did start on Sept 09.
And this wine-devel thread:
https://www.winehq.org/pipermail/wine-devel/2019-October/152082.html
The failures are systematic and happen on all machines running one of these two
Windows versions. What's strange is that the TestBot's wxppro and w2003std VMs
have not been modified in this timeframe and neither has the gdi32:bitmap test.
In fact this appears related to the compiler which would explain why the
failure started when winehq.org (which builds the official WineTest binaries)
was upgraded to Debian 10.
Specifically, letting wtbbuild, which still runs Debian 9.9
(i686-w64-mingw32-gcc 6.3.0 20170516), compile the test binaries results in no
failure:
https://testbot.winehq.org/JobDetails.pl?Key=59354
But using a binary compiled with i686-w64-mingw32-gcc 8.3-win32 20190406 (in
this case on my development machine) produces the 36 failures:
https://testbot.winehq.org/JobDetails.pl?Key=59355
Either that or it's quite possibly a result of the new everything-as-PE vs. the
old cross-compilation approach still used by wtbbuild.
--
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.