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=51321
Bug ID: 51321
Summary: Some Chinese characters aren't rendered correctly in
Foxmail.
Product: Wine
Version: 6.11
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jactry92(a)gmail.com
Distribution: ---
Created attachment 70181
--> https://bugs.winehq.org/attachment.cgi?id=70181
Chinese characters were rendered correctly.
Steps to reproduce:
1. `winetricks -q arial` to work around a crash of CEF.
2. `wine FoxmailSetup_7.2.21.453.exe` for installing Foxmail.
3. `export LANG=zh_CN.UTF-8 LANGUAGE=zh_CN.UTF-8 LC_ALL=zh_CN.UTF-8` to switch
to a Simplified Chinese locale.
4. `cd ~/.wine/drive_c/Foxmail\ 7.2/` and `wine Foxmail.exe`, then select the
first(腾讯邮箱) or the second(mail.qq.com) icon in the dialog.
Expected: All characters are rendered correctly.
Actually: Chinese characters are rendered as some boxes.
Wine version: wine-6.11-58-gfd7954974b9
--
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=51225
Bug ID: 51225
Summary: regression - Warframe colors messed up - wine staging
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pmargeti34(a)gmail.com
Distribution: ---
Created attachment 70092
--> https://bugs.winehq.org/attachment.cgi?id=70092
Rainbow colors
See attached screenshot please.
--
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=51052
Bug ID: 51052
Summary: 6.4 regression: 32-bit Cheat Engine attaching its
debugger leads to the target process crashing
Product: Wine
Version: 6.4
Hardware: x86-64
URL: https://cheatengine.org/downloads.php
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: subgraph93(a)gmail.com
Regression SHA1: af74bd31229e0f065448253b248ec0cb3b51af26
Distribution: Ubuntu
Steps to reproduce:
1) Install Cheat Engine (version 7.2 is affected, so is 7.1).
2) Start up cheatengine-i386.exe.
3) In the same prefix, start up the target process. No other software is
needed, because the issue can be reproduced with CE tutorials. To start up the
tutorial, open the "Help" dropdown menu and click the "Cheat Engine Tutorial"
entry.
4) Open the process selection window: File > Open Process; or just click the
flashing icon that shows the computer display with a magnifying glass.
5) In the "Applications" view (it is probably default), there should be an
entry for Cheat Engine itself, and one for "Tutorial-i386". Select the latter
entry, then click "Attach debugger to process", then click "Yes" in the
confirmation modal.
6) When the debugger attaches (should be near-instant for release builds, but
unoptimized builds can take about a minute), the process selection window will
close. At this point, the target process may crash already, but in some cases
it may still work. If the tutorial window still displays, switching focus to it
should cause the crash. In some cases, the target process crashes before this
happens, and Cheat Engine gives a "failed to attach debugger" error instead.
Logs almost always have the following entry (thread ID and the address may
vary):
013c:err:seh:NtRaiseException Unhandled exception code c000008f flags 0 addr
0xf7b80644
In one case (on a dirty prefix, which may or may not matter; the issue
otherwise still happens on a clean prefix), the error code was not c000008f,
but c00002b5. In some cases as well, in addition to the above error and
immediately before it, the following is output:
01d0:fixme:seh:fpe_handler untested SIMD exception: 0x6. Might not work
correctly
I didn't notice other major differences in console logs compared to working
Wine versions, so I didn't attach complete terminal outputs.
Regression testing (which I hope I did correctly) points to:
commit af74bd31229e0f065448253b248ec0cb3b51af26
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Tue Mar 2 18:52:44 2021 +0100
ntdll: Use syscall dispatcher to restore context in NtSetContextThread.
Signed-off-by: Jacek Caban <jacek(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
Other notes:
1) Ubuntu 20.10
2) Wine 6.7 (devel and staging) are still affected.
3) 64-bit Cheat Engine crashed neither 64-bit nor 32-bit target processes,
though it has issues working with 32-bit target processes.
4) This can be reproduced with most, but not all target processes. I think
targeting a 64-bit process doesn't cause the issue, though I wouldn't expect
debugging to work anyway with 32-bit CE. For example of a process that didn't
crash, I couldn't crash winecfg. My testing seems to indicate that the behavior
of a process is consistent in terms of whether or not it crashes, how it
crashes, and what terminal messages are output; however, different processes
may have slightly different behavior.
--
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=49935
Bug ID: 49935
Summary: mismatch behavior in API function GetOpenFileName
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comdlg32
Assignee: wine-bugs(a)winehq.org
Reporter: ch.panel(a)free.fr
Distribution: ---
GetOpenFileName with filter show all files instead of filtering files : ex:
("PDF files|*.PDF" as filter show not only PDF files. We have to validate the
dialog for the filter to oper.
--
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.