https://bugs.winehq.org/show_bug.cgi?id=48855
Bug ID: 48855
Summary: Borderlands 3: Unable to save
Product: Wine
Version: 5.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mrs11teen(a)gmail.com
Distribution: ArchLinux
Created attachment 66779
--> https://bugs.winehq.org/attachment.cgi?id=66779
Terminal output
When I load into a save file in Borderlands 3 with wine 5.4 or 5.5, an in-game
message is displayed warning me that my "settings have failed to save." Any
progress fails to save, and next time I load the game I am back where I
started.
This issue seems to be a regression that occurred with wine version 5.4 and
that persists with version 5.5. I've tested 5.3 and 5.2 and have not
encountered this issue.
The current line is repeated a number of times in the terminal while the game
attempts to save, I'm not sure if it's relevant to the error.
0104:fixme:file:ReplaceFileW Ignoring flags 6
The full terminal output (which includes output from the Epic Games launcher as
well) is attached.w
--
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.
https://bugs.winehq.org/show_bug.cgi?id=51218
Bug ID: 51218
Summary: Can not set zero disk volume serial number
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: ravenexp(a)gmail.com
Distribution: ---
When .wine/drive_c/.windows-serial file does not exist or contains 00000000
the following volume serial number is reported:
c:\>vol
Volume in drive c has no label.
Volume Serial Number is 4300-0000
In the previous Wine versions the default volume serial number was 00000000
and the zero serial number could be set via .windows-serial.
This regression broke the registration of a Windows program
I can't get a new registration key for.
--
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=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.