https://bugs.winehq.org/show_bug.cgi?id=44092
Bug ID: 44092
Summary: user32:sysparams test in Windows permanently
vertically shortens the test shell window
Product: Wine
Version: 2.22
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: parkerjbarker(a)yahoo.com
When I run the 64 bit winetest under Vista Ultimate 64-bit, I find that it's
the user32:sysparams test that shortens the test shell window vertically, so
that the status bar (showing how many tests have failed) is now half-showing.
The wine test shell window is not being properly restored.
--
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=47471
Bug ID: 47471
Summary: World of Warcraft, 8.2.0 New zone Nazjatar
Product: vkd3d
Version: 1.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: eaglecomputers.ok(a)gmail.com
Distribution: ---
Game freezes completely when loading into the new zone, if DX12 is being used,
but works fine if you use DX11 with DXVK.
--
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=30993
Bug #: 30993
Summary: diablo 3 d3d device error
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cleverca22(a)gmail.com
Classification: Unclassified
Created attachment 40680
--> http://bugs.winehq.org/attachment.cgi?id=40680
WINEDEBUG=trace+d3d output
when running diablo 3 on wine version d35cb8164a7635201c2ccdf73de2a78cebf6cb94
the game comes up with a fullscreen grey window (same as windows just before 3d
loads)
and gives an alert box with this message:
"graphics error
click to retry creating d3d device
click ok to retry"
clicking OK a few times changes the message slightly, to have retry/cancel,
retry just keeps retrying, cancel gives up as expected
--
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.
http://bugs.winehq.org/show_bug.cgi?id=32533
Bug #: 32533
Summary: QQDict: a button can't be displayed normally
Product: Wine
Version: 1.5.20
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jactry92(a)gmail.com
Classification: Unclassified
Created attachment 42928
--> http://bugs.winehq.org/attachment.cgi?id=42928
The Log
I installed QQDict in wine 1.5.20 and found that a botton in it can't be
displayed normally(as picture 1 in attachments).
I found that 'winetricks -q ie7' help a lot, just as the picture 2 in
attachments.
--
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=46592
Bug ID: 46592
Summary: Heroes III Horn of the Abyss TCP/IP issue
Product: Wine
Version: 3.0.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dplay
Assignee: wine-bugs(a)winehq.org
Reporter: kudraigor29(a)gmail.com
Distribution: ---
Created attachment 63485
--> https://bugs.winehq.org/attachment.cgi?id=63485
Debug log
TCP/IP window closes on create a host multiplayer game
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=24501
Summary: Games For Windows - Live: client doesn't start with
mono
Product: Wine
Version: 1.3.3
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download
Severity: enhancement
Priority: P2
Component: mscoree
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
It wants .Net 3.5, but that doesn't work in wine. In mono, fails with:
** (GFWLClient.exe:8): WARNING **: The following assembly referenced from
C:\Program Files\Microsoft Games for Windows - LIVE\Client\GFWLClient.exe could
not be loaded:
Assembly: PresentationFramework (assemblyref_index=2)
Version: 3.0.0.0
Public Key: 31bf3856ad364e35
The assembly was not found in the Global Assembly Cache, a path listed in the
MONO_PATH environment variable, or in the location of the executing assembly
(C:\Program Files\Microsoft Games for Windows - LIVE\Client\).
which is WPF, and according to Mono, http://mono-project.com/WPF, they have no
plans to implement (big project, not much reward).
I'm filing a bug here mostly to collect duplicates. If a lot of duplicates show
up, perhaps Novell/Mono will change their mind...
To reproduce:
$ winetricks -q gfw mono26
$ cd .wine/drive_c/Program\ Files/Microsoft\ Games\ for\ Windows\ -\
LIVE\Client
$ wine GFWLClient.exe
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46595
Bug ID: 46595
Summary: Rainbow Six Siege hangs on Uplay splash screen
Product: Wine
Version: 4.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: riesi(a)opentrash.com
Distribution: ---
Created attachment 63492
--> https://bugs.winehq.org/attachment.cgi?id=63492
Log without specific debug channels
To make this clear the game is Battleye protected, but it does not even get far
enough to load Battleye. At least I could not see any traces of a Battleye dll
when looking at the logs with +loaddll.
So the problem is that the game hangs on the Uplay splash screen and doesn't do
anything else after that. There is no continuous log output or anything. It
just sits there.
The part of the log that's interesting for this issue is at the bottom of the
file after:
0034:fixme:secur32:schannel_get_mac_algid unknown algorithm 200, cipher 23
This is all the output that is generated when the game tries to start and after
its killed.
If you need any additional logging with specific WINEDEBUG channels, I am happy
to assist.
Thanks in advance,
Riesi
--
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=34643
Bug #: 34643
Summary: The Bureau XCOM Declassified crashes immediately
Product: Wine
Version: 1.7.3
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: arathorn2nd(a)gmail.com
Classification: Unclassified
Created attachment 46171
--> http://bugs.winehq.org/attachment.cgi?id=46171
crash backtrace
When starting the game, wine crashes imediately. Installed correctly, thou,
using a clean wineprefix created with WINEARCH="win32"
Seems related to wxWidgets.
$ env WINEPREFIX="$(pwd)/wine" wine TheBureau.exe
wine: Unhandled page fault on read access to 0xfffffff8 at address 0x3ba5a1a
(thread 0009), starting debugger...
...
Backtrace:
=>0 0x03ba5a1a in wxmsw28u_vc_custom (+0x5a1a) (0x0386f688)
...
--
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=46960
Bug ID: 46960
Summary: Mono's interactive C# shell crashes when typing a
character
Product: Wine
Version: 4.5
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Distribution: ---
Mono ships with an interactive C# interpreter, located at
lib/mono/4.5/csharp.exe. This can be run directly from inside a Wine Mono
install.
It crashes with an ArgumentOutOfRangeException the first time a character is
typed.
System.ArgumentOutOfRangeException: Console key values must be between 0 and
255 inclusive.
Parameter name: key
at System.ConsoleKeyInfo..ctor (System.Char keyChar, System.ConsoleKey key,
System.Boolean shift, System.Boolean alt, System.Boolean control) [0x0000c] in
<72b294be54bc4854bce603b664bafd63>:0
at System.WindowsConsoleDriver.ReadKey (System.Boolean intercept) [0x00079]
in <72b294be54bc4854bce603b664bafd63>: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.
http://bugs.winehq.org/show_bug.cgi?id=28393
Summary: WiX light can't find files in deeply-nested
directories
Product: Wine
Version: 1.3.28
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sam(a)robots.org.uk
Created an attachment (id=36407)
--> (http://bugs.winehq.org/attachment.cgi?id=36407)
depth.tar
The attached test case fails to run under Wine with the following error:
Z:\home\sam\src\wix-test\depth\A.wxs(8) : error LGHT0103 : The system cannot
find the file
'Z:\home\sam\src\wix-test\depth\A\AOL\Aachen\Aaliyah\Aaron\Abbas\Abbasid\Abbott\Abby\Abdul\Abe\Abel\Abelard\Abelson\Aberdeen\Abernathy\Abidjan\Abigail\Abilene\Abner\Abraham\Abram\Abrams\Absalom\Abuja\Abyssinia\readme.txt'.
This happens with both Mono 2.10.5 and Microsoft .NET 2.0. Unpack the test case
and run 'make' and it should create a fresh WINEPREFIX in which it will install
the test pre-requisites before running the test itself.
On a Windows 7 machine, light is able to correctly build B.msi.
--
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.