https://bugs.winehq.org/show_bug.cgi?id=38721
Bug ID: 38721
Summary: Steam problem - Wine uncompability or something
similar
Product: Wine
Version: 1.7.44
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adriansnetlis3(a)inbox.lv
Distribution: ---
Created attachment 51646
--> https://bugs.winehq.org/attachment.cgi?id=51646
The .log file with errors
Hi! I want to report that Steam installation has a problem here. I am posting
the log as attachment, but it is PlayOnlinux. Why PlayOnLinux - I am not gone
do very the same in console now as the installation was long for running
Resident Evil 5. But I am 100% sure this problem is releated to Wine and will
be the same also in non-POL installation. Actually, I am not 100% sure what the
problem is, but the log puts out one error that POL members which I reported a
problem with Resident Evil 5(here you can see my problem:
https://www.playonlinux.com/en/topic-13184-Resident_Evil_5_Gold_Edition_Ste…
). It may be reason why Resident Evil 5 not run, so I have to ask it here as
POL can't help with Wine errors. The POL log is in attachment. Please, don't
reject this - this may be important for multiple people!
--
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=34334
Bug #: 34334
Summary: MetaTester 5 never sends or receives data
Product: Wine
Version: 1.7.0
Platform: x86-64
URL: http://files.metaquotes.net/metaquotes.software.corp/m
t5/mt5tester.setup.exe
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kennybobs(a)o2.co.uk
Classification: Unclassified
Created attachment 45702
--> http://bugs.winehq.org/attachment.cgi?id=45702
wine-1.7.0-199-g52fb1cc console output (1st run)
The MetaTrader 5 Strategy Tester Agent (MetaTester 5) never sends or receives
any data.
It comes as part of MetaTrader 5 but is also available separately to create
your own server farm.
It installs itself as a system service on Windows (SYSTEM account) and runs in
the background once it has been initially set up from the main application.
Wine seems to have a problem running the services but that is a different
problem (bug not yet logged).
Wireshark confirms that no connection attempts are sent or received. Not
externally anyway.
The main application window shows statistics for data transfer and under
Windows XP this can be a few kB each day when quiet (when stock markets are
closed), but Wine never registers a single byte.
Netstat shows that the agents themselves are listening:
tcp 0 0 0.0.0.0:2001 0.0.0.0:* LISTEN
216313/wineserver
I can telnet to this port and it remains open for a few seconds before timing
out and closing. This does not register as data on the main application (same
in XP).
There are listeners on port 6010 and 6011 too but I think they're control
ports.
I am attaching the first run log as two agent services start successfully on
first run. You can start as many as you like but it makes sense to have one
agent per core.
Ran all day on Windows XP and Linux to compare.
In testing I enabled the agents to join the community (global) network. An
account is not required for this.
--
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=45917
Bug ID: 45917
Summary: battle.net launcher and mouse position on high DPI
monitor
Product: Wine
Version: 3.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kdt3rd(a)gmail.com
Distribution: ---
In both wine 3.16 and 3.17, and both vanilla and wine-staging wine, the cursor
/ mouse position is scaled inside the Battle.net launcher application. I
initially thought it was only temporary since it seemed there were a bunch of
changes for correctly passing the DPI in the change sets for 3.16, but it has
persisted, so thought to file a bug.
Basically, when running on a (single) UHD monitor (nvidia graphics card, asus
uhd monitor) where xdpyinfo returns 157 dpi (xdpyinfo|grep resolution gives
157x161 dots per inch), the Battle.net launcher application thinks the mouse is
in the wrong position, meaning to click on a particular button, I need to move
the window such that the button is in the upper left of the screen, or have the
mouse be ~1.5x of the distance from the upper left from where the button
actually is and have mouse still be inside the application (otherwise it
switches focus to the application under the mouse). And even then, the "play"
button is mouse-over highlighted wider than the actual button. When the button
is just in from the top left of the display, it doesn't become active
(mouse-over highlight or clickable) until the mouse is moved more than the
distance from the top left. Which is flat strange, because I haven't resized
the window, just moved, so the upper left of the toplevel app window is still
offset by the same amount from the button. Of course, I don't know if it is
computing position from the upper left of the top window or somehow querying
the global cursor position and comparing that to the perceived global position
of the widgets in the window. Basically, my attempt to naively find what is
being scaled by dpi and what has been missed in that step have failed.
Interestingly, if I do the above to move the window such that I can click the
Play button and then launch a game, the mouse position seems fine when the game
is running and in full screen - Of course, that's a different app, and as it is
fullscreen, I presume because it forces itself to be at 0,0, and probably uses
xrandr to reset the screen coordinates and figures itself out.
If there is any other information that would be helpful, or if someone can
point out code to look at / traces to turn on, I am happy to help.
--
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=32218
Bug #: 32218
Summary: LTSpice: Objects not resized when the window is
resized
Product: Wine
Version: 1.5.17
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: 00cpxxx(a)gmail.com
Classification: Unclassified
Steps to reproduce:
1) Download, install and run LTSpice -
http://ltspice.linear.com/software/LTspiceIV.exe
2) Create a new schematic (File -> New Schematic)
3) Press L, click somewhere (this will create a component in the screen)
4) Press ESC to go back to the select tool, hold CTRL and right-click the
component to open a properties window.
5) Resize the window.
The internal window listview will not get resized to match the new window size.
This is not a duplicate of bug 3037 and may or may not be a duplicate of bug
7007 it will take a while to check.
--
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=45719
Bug ID: 45719
Summary: comctl32:treeview test_right_click depends on mouse
pointer position
Product: Wine
Version: unspecified
Hardware: x86
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: mail(a)colinfinck.de
The result of the "test_right_click" part of the comctl32:treeview test highly
depends on the mouse pointer position.
Steps to reproduce under Windows:
1. Open a Command Prompt and type "comctl32_winetest treeview" without hitting
RETURN.
2. Move the mouse pointer, so that it will be inside the TreeView test window
that is spawned by the test. You probably need to run the test multiple times
to estimate that position.
3. Hit RETURN to run the test.
Result: "Test failed: parent right click sequence: ...", which doesn't happen
if the mouse pointer is outside the TreeView test window.
This bug has been uncovered during ReactOS Regression Testing, which is why a
similar report exists in the ReactOS bug tracker too:
https://jira.reactos.org/browse/CORE-14975
--
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=39959
Bug ID: 39959
Summary: Growtopia v2.11 fails to run with unhandled exception
(2.09 did run ok)
Product: Wine
Version: 1.9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wine.hq(a)jyge.net
Distribution: ---
Created attachment 53389
--> https://bugs.winehq.org/attachment.cgi?id=53389
backtrace.txt
See subject and attachment.
Application runs fine with Win8 but fails with Wine 1.9.0
Standard MythUbuntu 14.04 so tried wine 1.6.x (that comes with standard), and
now also the development version (1.9.0) using instructions from winehq.site
for Ubuntu to install. Same endresult (Unhandled exception) on both. Backtrace
is done with 1.9.0 -version.
Application download link: http://growtopiagame.com/GrowtopiaInstaller.exe
--
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=32221
Bug #: 32221
Summary: LTspice: component drawing issues when moving
Product: Wine
Version: 1.5.13
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: testelor(a)yahoo.com
Classification: Unclassified
Created attachment 42497
--> http://bugs.winehq.org/attachment.cgi?id=42497
Traces left behind when moving
Steps to reproduce:
1) Download and install LTspice -
http://ltspice.linear.com/software/LTspiceIV.exe
2) Run LTspice using:
$ wine scad3.exe -nowine
3) Create a new schematic, press 'R' (resistor), for example, and don't place
it by clicking, simply move it around.
The same happens for any component that is grabbed and moved. See the attached
screenshot.
--
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=45984
Bug ID: 45984
Summary: Skyrim Special Edition does not get past loading
screen on high core count or high memory systems
Product: Wine
Version: 3.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tom(a)r.je
Distribution: ---
Skyrim SE gets stuck at the loading screen on certain hardware configurations.
It doesn't freeze as keeps displaying different loading screen tips but does so
forever.
I posted on the Steam forums about this:
https://steamcommunity.com/app/221410/discussions/8/1734336452599497070/
With a blank wineprefix (no savegames, no mods, just a fresh install from
steam) click "New game". It sits at the loading screen forever.
Almost everyone affected has:
AMD Threadripper 1950x
>= 32gb RAM
### Software information
Skyrim Special Edition (Steam) (With or without DXVK)
### System information
- GPU: nvidia 980ti
- Driver: 410 (396.54 also affected)
- Wine version: 3.18
There are several systems listed in the steam thread:
/////
Arch Linux
AMD Threadripper 1950x
32gb RAM
nvidia 980ti with 396.54 driver
/////
Ubuntu 18.04
AMD Threadripper 1950x
64gb RAM
Nvidia Titan XP
///
Arch Linux
AMD Threadripper 1950x
32gb RAM
AMD Vega 64
////
Both AMD and nVidia GPUs are affected so it's unlikely to be a driver issue.
The common elements are:
32gb or more of RAM
AMD Threadripper 1950x
### What I've tried
Knowing that it only affects high CPU core systems or high RAM systems I have
tried the following:
- taskset -c 0-7 wine steam.exe I wasn't sure whether this would limit just
steam.exe, when steam.exe spawns SkyrimSE.exe does this have all 32 cores
enabled?
- Disabling SMT in the bios. This effectively disables half the cores so there
are only 16 available. This would be similar to someone playing on a Ryzen 7 (8
cores + smt) and I haven't seen any reports with 16 thread CPUs
- It seems like it might be a memory issue. I've tried enabling/disabling NUMA
in the bios to no effect
- With NUMA enabled I've tried using `numactl -m 0 -t wine Steam.exe` to force
WINE to only use one bank of memory (effectively limiting it to 16gb in the
process)
- Running off a SSD rather than NVME driver (It could be a scheduler issue??)
None of this made any difference. How else can I debug this?
Looking around, posts regarding similar issues on windows suggests it's a
memory problem. Perhaps it's something to do with having 32gb RAM in the
system?
Please let me know if you need any kind of trace/log. WINEDEBUG=all makes steam
take so long to start it eventually crashes, so I couldn't provide that, I can
try with requested debug options though.
--
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=33719
Bug #: 33719
Summary: comctl32:propsheet custom window proc test failure
Product: Wine
Version: 1.5.19
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fgouget(a)codeweavers.com
Classification: Unclassified
A number of VMs report one of these two related test failures:
Elevated privileges (or pre-Vista):
propsheet.c:746: Test failed: property sheet with custom window proc: the msg
0x001c was expected, but got msg 0x0047 instead
or not elevated privileges:
propsheet.c:746: Test failed: property sheet with custom window proc: the msg
0x0046 was expected, but got msg 0x0210 instead
They have been seen on the following systems:
comctl32 5.81.4968.2500 Windows 2000 Professional SP4 + IE55 (rare ~1/50)
comctl32 5.82.3790.3959 Windows 2003 Enterprise Server SP2 + IE8 (rare ~1/50)
comctl32 5.82.6002.18305 Windows Vista Home Premium SP2+IE9
comctl32 5.82.7601.17514 Windows 7 Ultimate SP1 64-bit (+IE8) (32-bit tests)
comctl32 5.82.7601.17514 Windows 7 Ultimate SP1 64-bit + IE9 (32-bit tests)
comctl32 5.82.7601.17514 Windows 7 SP1 (not one of mine)
comctl32 5.82.9200.16384 Windows 8
--
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=46352
Bug ID: 46352
Summary: TreePad X Enterprise 12GB (single user) v7.17.0
Generates Error on Startup
Product: Wine
Version: 4.0-rc2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winebugrpt18356(a)fastmail.jp
Distribution: ---
First, this issue actually started with 4.0-rc1 and is present in 4.0-rc2 as
well. The issue wasn't present in version 3.04-1. I'm using Debian Unstable.
Upon startup under WINE 4.0-rc2, TreePad X Enterprise 12GB (single user)
v7.17.0 generates the following error message in a popup window:
List index out of bounds (-2147483632)
Link to TreePad X Enterprie 12GB (single user) download (21-day evaluation):
http://www.treepad.com/download/tpxsu1.html
TreePad installation and run instructions:
01) Download one of the *.zip files from the above link
02) Navigate to ~/.wine/drive_c/Program Files (x86)
03) Create a folder called TreePadXSU
04) Extract the *.zip file to the TreePadXSU folder
05) From the command line, run one of the following to start TreePad
wine start 'C:\Program Files (x86)\TreePadXSU\TreePadXEnterprise.exe'
wine "C:\\Program Files (x86)\\TreePadXSU\\TreePadXEnterprise.exe"
The bug was initially reported to the Debian WINE Party team. They verified
the issue, but requested that I file a bug report upstream.
--
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.