https://bugs.winehq.org/show_bug.cgi?id=44987
Bug ID: 44987
Summary: Civilization V crashes on startup
Product: Wine
Version: 3.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: christophercormier(a)protonmail.com
Distribution: ---
Created attachment 61121
--> https://bugs.winehq.org/attachment.cgi?id=61121
Backtrace from running the game in DirectX 9 mode
When launching Civilization V in DirectX 9 mode on a clean 32-bit Wine prefix,
it immediately crashes with a program error of "The program CivilizationV.exe
has encountered a serious problem and needs to close."
The launcher does work, as it allows me to choose between DirectX 9 and DirectX
11. Neither DX9 or DX11 launch and both cause the same error. This is a
regression since, if I roll back the Wine version to 2.19, it works without any
issues in DX9 mode. It also previously would open a window for DX11 before
crashing, but now it does not even get that far.
I'm testing this on Kubuntu 17.10, with a GTX 960 graphics card using the
binary NVIDIA driver. This issue persists in both regular Wine 3.6 and Wine
3.6-staging, and with the multi-threaded command stream both enabled and
disabled. The backtrace for both the DX9 and DX11 versions have been attached
--
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=44992
Bug ID: 44992
Summary: Setting dpi in winecfg has no effect on application
Product: Wine
Version: 3.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gordon1drake(a)yahoo.com
Distribution: ---
I am using a "low" resolution monitor set at 1280x1024 and I have been setting
the dpi in winecfg to 128 otherwise the fonts are too small. With version 3.6,
however, the application still looks like it is set at 96 and changing the
value in winecfg has no effect.
The application is called Scrivener and it does have the ability to set the
font and size of the menu and other panes. It also has the ability to zoom on
the editor pane. Unfortunately, it now has to be set much higher than usual.
It should be noted that winecfg, task manager, etc do change. There was an
instance when the font did not change in these but I can't reproduce. It may
have happened when trying to upgrade an existing wineprefix.
--
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=44996
Bug ID: 44996
Summary: Enhancement requests related to Winetricks and Wine
Product: Wine
Version: 3.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ricky.tigg(a)gmail.com
Distribution: ---
Created attachment 61128
--> https://bugs.winehq.org/attachment.cgi?id=61128
Snaphots related to designs and fonts sizes
1. As noticeable GUI messages associated to the launch of Winetricks are not
displayed properly as expected in any user-friendly designs
(winetricks_error.png, winetricks_One-time question about helping Winetricks
development.png, winetricks_Information.png).
2. With no exception in all windows associated to Wine, fonts' sizes are not
applied according to the size currently in use on Linux system, especially the
one which applies to interfaces (here set to Cantarell Regular 11). Window
title is Cantarell Bold 11. Wine persists to apply its own size set to
interfaces (probably size 7–8) regardless system set font sizes (Wine
configuration.png).
For comparison system fonts apply normally to windows related Wineprefix itself
(Winetricks - current prefix is "-home-yk-.wine"_006.png).
For convenience I opened the Wine windows from Winetricks | Select the default
Wineprefix.
Tested on Fedora desktop using components:
winetricks.noarch 20180217-1.fc28 @updates-testing
wine.x86_64 3.5-1.fc28 @updates-testing
--
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.
The address p54936861.dip0.t-ipconnect.de (84.147.104.97) failed too many login attempts (5) for
the account shadow(a)umbrox.de.
The login attempts occurred at these times:
2018-04-16 20:52:11 CDT
2018-04-16 20:52:27 CDT
2018-04-16 20:52:34 CDT
2018-04-16 20:52:53 CDT
2018-04-16 20:53:07 CDT
This IP will be able to log in again using this account at
2018-04-16 21:22 CDT.
https://bugs.winehq.org/show_bug.cgi?id=41265
Bug ID: 41265
Summary: Far Cry 1: game crashes when using mouse wheel
Product: Wine
Version: 1.9.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: DanBrake0819(a)freenet.de
Distribution: ---
Created attachment 55565
--> https://bugs.winehq.org/attachment.cgi?id=55565
logfile
Far Cry 1.4 (and unofficial 1.5 patch) crashes when using the mouse wheel. It
happens in the latest Wine version (1.9.18). I also tested the latest stable
version (1.8.4) and an older stable version (1.6.2)... the same thing: crash
when using the mouse wheel.
--
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=44929
Bug ID: 44929
Summary: Anno 2205 crash at startup
Product: Wine
Version: 3.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mo78(a)abv.bg
Distribution: ---
Created attachment 61016
--> https://bugs.winehq.org/attachment.cgi?id=61016
Anno 2205 crash log
Anno 2205 crashes at startup with the following error:
Fatal Python error: Py_Initialize: can't initialize sys standard streams
LookupError: unknown encoding: cp437
002b:fixme:imm:NotifyIME NI_CLOSECANDIDATE
I installed different components one by one but the error is always the same.
First I tried clean prefix and than I add one by one DX9, after that DX 10,
DX11 and vcredist 2015. The error and the log is alwaus the same after
installing every component.
--
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=42378
Bug ID: 42378
Summary: Diablo 3 2.4.3 - incorrect and slow rendering on x64
client
Product: Wine
Version: 2.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx11
Assignee: wine-bugs(a)winehq.org
Reporter: f.volejnik(a)gmail.com
Distribution: ---
Created attachment 57164
--> https://bugs.winehq.org/attachment.cgi?id=57164
Wine-staging 2.0 log of diablo3 running the d3d11 x64 client.
Since the release wine-staging 2.0, diablo 3 is able to start in the 64bit
mode, which utilizes d3d11 for rendering (Thanks!).
It is not without issues, yet, though.
Namely, the performance is really bad, on my machine (core i5, GTX 770) it
renders about 3 frames per second (whereas the 32bit version runs with >60
FPS). The rendering is not without issues, too. Characters look matte and dark,
very different look from the one one sees in the 32bit client.
I am attaching a log from my machine (Arch linux, 64bit, nvidia blob 375.26,
wine-staging 2.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.
https://bugs.winehq.org/show_bug.cgi?id=44783
Bug ID: 44783
Summary: Jedi Knight Dark Forces II/Mysteries of the Sith,
choppy audio causing very poor performance
Product: Wine
Version: 3.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: libsanorec(a)hotmail.com
Distribution: ---
After a somewhat recent upgrade in Wine (don't remember from what version
though, but it was a very old one), I've been having problems with audio in
both JK and MotS, where sounds playing in-game will lower fps significantly and
sound very choppy.
In Jedi Knight, causing sounds to play continuously (say, by firing a very fast
gun right into a wall) will cause the framerate to drop drastically, from the
usual already very low average of 30fps to around 10fps. Needless to say, the
sound will become increasingly choppy the lower the framerate is. The problem
is less present but still there when playing the game without 3d Acceleration,
and the average FPS is a lot higher as well.
I normally use JACK audio with a Pulse Audio module, but having JACK on or off
doesn't seem to make any difference in game performance. Changing the Wine
audio driver to winealsa or winepulse also didn't have any noticeable
difference. I however did not experience any such performance drops when
running the game with Wine audio disabled.
Running from console won't cause any error or "fixme" messages to print when
choppiness happens.
In MotS the problem is even worse: audio choppiness happens in almost every
frame, leading to short freezes and overall complete unplayability. I believe
this might have something to do with the sample rate for the sounds in these
games: JK uses 22050Hz and MotS uses 11025Hz.
After resetting the ".wine" directory, overall performance seems much better
(still around 30fps, but far more stable), but the audio is still very choppy.
--
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.