http://bugs.winehq.org/show_bug.cgi?id=33542
Bug #: 33542
Summary: EnableWindow calls ReleaseCapture when mouse captured
on child window
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: orzhvs(a)gmail.com
Classification: Unclassified
Created attachment 44392
--> http://bugs.winehq.org/attachment.cgi?id=44392
WINEDEBUG=+relay,+message wine /usr/local/vboxvm/vmshare/Spy.exe 2>&1 | grep -E
SetCapture\|ReleaseCapture\|LBUTTONDOWN\|LBUTTONUP\|EnableWindow > out.txt
When EnableWindow disabling a window in Wine, mouse capture in its child window
gets lost. As far as I tested in windows, capture is released only when
disabling the exact captured window, rather than its parent window.
There's a tool named 'Spy32' ( download at
http://www.woodmann.com/RCE-CD-SITES/Protools/files/utilities/spy.zip ), please
try picking window by dragging the 'target' icon to target window, it will
misbehave like the mouse button never released. In further debug info (
attached ) I saw it disable its main window to avoid picking itself, it indeed
plans to re-enable the window when mouse button is up but it dose not as
capture has been released and no WM_LBUTTONUP is received.
--
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=43661
Bug ID: 43661
Summary: DraftSight 2017 - Font corrupted with version set to
win7
Product: Wine
Version: 2.15
Hardware: x86
URL: https://www.3ds.com/products-services/draftsight-cad-s
oftware/free-download/
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Created attachment 59106
--> https://bugs.winehq.org/attachment.cgi?id=59106
Version set to Win7
Program is free for testing, but unfortunately requires registration.
In win7 mode it displays fonts very broken, with version set to XP it works
fine.
--
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=42064
Bug ID: 42064
Summary: Race Driver: Grid - Races throw errors within a few
corners
Product: Wine
Version: 1.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: thecreator224(a)gmail.com
Distribution: ---
Created attachment 56556
--> https://bugs.winehq.org/attachment.cgi?id=56556
Backtrace of Campaign Crash
Installs and runs fine and until it crashes the game performs up to
expectations. Since my laptop is fairly poor I run minimum graphics settings
with no multi-sampling to reach 60fps.
The game crashes during custom races with "Invalid Parameters" Message, whilst
during the campaign races it throws an write access error. Backtrace is for the
campaign race crash.
--
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=45327
Bug ID: 45327
Summary: I have been playing League of Legends fine until I
tried to open it tonight and it keeps giving me fatal
and critical errors. League of legends 8.12
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: brandon_bunning1(a)mymail.eku.edu
Distribution: ---
Created attachment 61615
--> https://bugs.winehq.org/attachment.cgi?id=61615
Error report?
I have been playing League of Legends fine until I tried to open it tonight and
it keeps giving me fatal and critical errors. I have tried different wine
versions, i have tried uninstalling and reinstalling EVERYTHING:playonlinux,
league, wine.
--
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=38875
Bug ID: 38875
Summary: DirectDraw: blitting from Offscreen Plain surface to
Primary Surface displays black instead
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: danweiss(a)gmail.com
Distribution: ---
I made a simple DirectDraw test program that draws a bitmap to an Offscreen
Plain surface, then draws that surface to the primary surface with resizing.
It works fine on Windows. But whenever I run it on Wine, it draws a black
rectangle instead of the bitmap.
If I create a System Memory Surface instead of an Offscreen Plain Surface, it
draws correctly.
Link to the test program EXE: http://www.dwedit.org/files/TestWin32_2.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.
https://bugs.winehq.org/show_bug.cgi?id=45486
Bug ID: 45486
Summary: Byond 512.x dreamseeker will crash on loading into a
ss13 station that uses shaders if run on wine 3.9 or
later, but will run fine if you use 3.8
Product: Wine
Version: 3.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: midicow(a)gmail.com
Distribution: ---
As in the title, in order to get dream-seeker to successfully launch into a
station you have to use wine 3.8 or earlier.
Steps;
Installed wine 3.9
export WINEARCH=win32
set version to windows 7
winetricks allfonts mfc42 gdiplus vcrun2013 wsh57 windowscodecs ogg ole32
riched30 msls31 ie8
got the windows beta exe for byond from http://www.byond.com/download/
Login and launch any of the populated ss13 servers listed (Most of them use
d3d9 shaders for lighting and ao now)
Dreamseeker attempts to connect, might even download stuff and go to launch,
then closes.
009a:err:d3d:wined3d_debug_callback 0x42a1848: "GL_INVALID_OPERATION in
glVertexAttribPointer(non-VBO array)".
009a:err:d3d:wined3d_debug_callback 0x42a1848: "GL_INVALID_OPERATION in
glVertexAttribPointer(non-VBO array)".
--
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=43665
Bug ID: 43665
Summary: The Quantum Break crashes at certain place.
Product: Wine
Version: 2.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: mail.aermakov(a)gmail.com
Distribution: ---
Created attachment 59110
--> https://bugs.winehq.org/attachment.cgi?id=59110
Screenshot, wine log and backtrace.
Hello.
The game "Quantum Break" crashes at certain place during an animated intro. I
have launched it several times on wine-staging.2.15 and result was the same.
Best Regards.
--
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=46007
Bug ID: 46007
Summary: Binary Domain crashes with builtin d3dx9_43 or
d3dcompiler_43
Product: Wine
Version: 3.18
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 62578
--> https://bugs.winehq.org/attachment.cgi?id=62578
backtrace
If one of these files set to 'native,builtin' all works fine.
wine-3.18-75-ge55aca8f49
--
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=29181
Bug #: 29181
Summary: Combo box doesn't get a background in dialog editor
Product: Wine
Version: 1.3.33
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: toni.spets(a)iki.fi
Classification: Unclassified
Created attachment 37647
--> http://bugs.winehq.org/attachment.cgi?id=37647
Hack for background drawing
When using a resource editor like ResEdit to create dialogs, combo boxes have
CBF_EDIT set and the white background is not drawn and the dialog background is
seen instead.
Attached a patch that workarounds the problem for this case. It is probably not
the correct fix as there must be a reason why CBF_EDIT state control background
is not drawn. Of course on Windows the combo box background is drawn with this
program.
--
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=46067
Bug ID: 46067
Summary: Crysis has lighting issues
Product: Wine
Version: 3.10
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: joseph.kucia(a)gmail.com
Regression SHA1: 5836b957e55c6ec3f720e995bb8a01ec295d7d38
Distribution: ---
Created attachment 62670
--> https://bugs.winehq.org/attachment.cgi?id=62670
before and after
comparison
--
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=46059
Bug ID: 46059
Summary: Final Fantasy XI Online: Mouse Movement Heavily
Affects FPS
Product: Wine
Version: 3.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: escomk3(a)hotmail.com
Distribution: ---
This isn't exactly a new issue, and it hasn't been a bother before, especially
if one doesn't tend to use the mouse in the game, but it has become so bad that
moving the mouse around steadily makes the game a slide-show. Bisect actually
took me a lot farther back in history than I would have guessed.
It seems commit c2e0ae5b [1] is responsible, and reverting it restores
abnormality (there's still a clear effect on the FPS, but it's very different,
and definitely not as drastic).
A quick 'operf' test, though I'm not sure how accurate or helpful it might
be...
Top 5 with the commit, without moving the mouse, and spinning the camera
steadily around using the keyboard during a period of about 10 seconds:
samples| %|
------------------
377648 69.8603 wined3d.dll.so
67991 12.5775 vmlinux
41998 7.7691 libnvidia-glcore.so.410.66
13403 2.4794 anon (tgid:18170 range:0x2681000-0x299dfff)
9164 1.6952 dsound.dll.so
Now with additionally moving the mouse around (if in windowed mode, the cursor
needs to go over the game window, whether it's the active window or not):
samples| %|
------------------
201289 38.5848 wined3d.dll.so
163583 31.3570 libwine.so.1.0
51344 9.8420 vmlinux
41387 7.9334 gdi32.dll.so
12685 2.4316 libnvidia-glcore.so.410.66
Now without the commit, while moving the mouse (without moving the mouse,
there's not much of a difference as one might expect):
samples| %|
------------------
452427 67.5044 wined3d.dll.so
85858 12.8104 vmlinux
40397 6.0274 libnvidia-glcore.so.410.73
22614 3.3741 libwine.so.1.0
14258 2.1274 anon (tgid:3579 range:0x2681000-0x299dfff)
To get a bit more in-depth, I gave 'opannotate' a go, though it may be
inaccurate even according to its docs.
The highest spikes would seem to come from a 'switch(index)' [2], with 35667
samples, and 'if (index >= nb_dll_paths) return NULL;' [3] with 44687 samples.
Without the commit, these lines get hit with only 4811 and 6023 samples
respectively.
1.
https://source.winehq.org/git/wine.git/commit/c2e0ae5bfd084d9b34c46517507e5…
2.
https://source.winehq.org/git/wine.git/blob/c2e0ae5bfd084d9b34c46517507e5d3…
3.
https://source.winehq.org/git/wine.git/blob/c2e0ae5bfd084d9b34c46517507e5d3…
--
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=43506
Bug ID: 43506
Summary: Adobe Air installer does not make any progress unless
winetricks ie8 is installed (or quiet mode is used)
Product: Wine
Version: 2.12
Hardware: x86
URL: https://github.com/Winetricks/winetricks/issues/821
OS: Linux
Status: NEW
Keywords: download, Installer
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: ---
This was pointed out to me in
https://github.com/Winetricks/winetricks/issues/821. I can confirm that. Doing:
$ winetricks -q adobeair
works fine. However,
$ winetricks adobeair
hangs on initializing. If `winetricks -q ie8` is run beforehand, then
`winetricks adobeair` will work.
--
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=46023
Bug ID: 46023
Summary: Cisco Packet Tracer 7.2 (kind of) crashes on startup
and when reading saved files from disk
Product: Wine
Version: 3.14
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tjt263(a)gmail.com
Created attachment 62600
--> https://bugs.winehq.org/attachment.cgi?id=62600
app crashed. wineloader64 box popped up. gave me this crashlog/traceback. tell
me to save it and submit it to this page. so that's what i'm doing; following
the instructions it gave me. hope it helps.
Relevant to Wine and/or CrossOver.
trying to get cisco packet tracer working reliably on macos. but there's an
annoying error/dialog box at startup: "packet tracer has stopped working
unexpectedly blah blah". Here is a screenshot: https://i.imgur.com/HsyEKFq.png
but it has't actually stopped working.
it works.
for the most part, at least.
although actually interacting with the erroneous error/dialog box will in turn
terminate the application.
i'm guessing it's expecting something from the windows environment, and when
it's not there, it throws an exception because some condition is not met.
i can just move the dialog box out of the way and carry on in the meantime, but
it's still annoying.
i think it's to do with the login screen.
on windows it bullies you into signing up and logging in. or you can enter as a
guest with a reduced feature set or something. but that isn't displayed in
Wine. it just goes straight into the main application.
i just move the error/dialog box to another desktop, or stash it in the corner,
or behind the main window.
it was going fine for hours, then out of nowhere it crashed for real. but it
allowed me to save progress. i saved to the macOS desktop. I can execute the
application again and load the saved file, but after that, it will crash any
time i try to move objects around. so i got so far, but now i'm stuck.
--
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=45361
Bug ID: 45361
Summary: Graphical issues in The Sims 3 (regression)
Product: Wine
Version: 3.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
Distribution: Ubuntu
Created attachment 61662
--> https://bugs.winehq.org/attachment.cgi?id=61662
terminal output (no +d3d_shader)
Setting High Detail Lots to any level above 1 results in very annoying
graphical issues on non-household lots and when moving through buildings. It is
also present with all options turned down to minimum but it's just easier to
reproduce with High Detail Lots set to level 4 and moving through buildings.
I can reproduce this bug in version 2.10 and higher but can't in 2.6 and 2.0.2,
so it must be a regression. Not sure about versions between 2.6 and 2.10 as I
get an error when compiling those, but I suspect the regression happened in 2.9
due to introduced tessellation.
Attaching terminal output (without WINEDEBUG argument) from 3.10 (devel),
screenshot of the problem and terminal output with WINEDEBUG=+d3d_shader (raw
file is almost 1GB so i compressed it into tar.xz).
I am using Ubuntu 18.04 (64 bit) with NVidia GTX 1070 using proprietary version
396.24.02 driver.
--
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=45199
Bug ID: 45199
Summary: MS Excel 2010 fails on start upgrading to wine 3.8
Product: Wine
Version: 3.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lviggiani(a)gmail.com
Distribution: ---
Created attachment 61414
--> https://bugs.winehq.org/attachment.cgi?id=61414
backtrace
After upgrading to wine 3.8 (on Arch x64) MS Excel 2010 fails on start. The
splash screen appear for a few second and then a message error is displayed
saying that an error occurred and offering to report the error to microsoft and
to re-open excel.
Even afer restarting the error persists.
Downgrading to 3.7 works.
Please see the attached backtrace
--
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=44128
Bug ID: 44128
Summary: HebRech Invoicing throws error message
Product: Wine
Version: 2.22
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 59867
--> https://bugs.winehq.org/attachment.cgi?id=59867
Console Output (wine 2.22)
Hello everyone,
after testing HebRech which got its own entry in the AppDB I noticed that the
button "Rechnung" in the main programm throws an error message.
Ein unerwarteter Fehler ist aufgetreten: LOMAIN ist kein Objekt. (1)
Klasse Commain_optionsdialogsservice (Zeile: 0)
Translation: An unexpected error has occured: LOMAIN is not an object. (1)
Class Commain_optionsdialogsservice (Line: 0)
Console output is attached.
Please note that this program requires a "winetricks dotnet46" to install.
--
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=33835
Bug #: 33835
Summary: Touhou 13.5 black screen
Product: Wine
Version: unspecified
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: directx-d3dx9
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: murela_alba(a)abv.bg
CC: wine-bugs(a)winehq.org
Classification: Unclassified
Created attachment 44861
--> http://bugs.winehq.org/attachment.cgi?id=44861
Title screen
When running Hopeless Masquerade after the loading screen the only thing
rendered is the main menu and game logo, with no background and when trying to
go into story mode, the entire screen turns black. Music and sound effects are
running properly at the same time. Game version is 1.03b, but 1.0 does the
same. Tested with wine 1.6-rc2 on Ubuntu 13.04 (64-bit).
--
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=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.