https://bugs.winehq.org/show_bug.cgi?id=49420
Bug ID: 49420
Summary: Ableton 10: file dialogs not DPI scaled
Product: Wine
Version: 5.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: io(a)mikelpr.com
Distribution: ---
the file open/save dialogs are not scaled when running with a different DPI,
yet the mouse input is - like if the window were actually scaled. therefore, I
can only click the top left halves (width and height) of the file dialogs
--
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=56900
Bug ID: 56900
Summary: Error related to download
Product: Wine
Version: 6.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: thatlocalbozo(a)gmail.com
Distribution: ---
Created attachment 76722
--> https://bugs.winehq.org/attachment.cgi?id=76722
cef_window_renderer.exe is non-functional, non-windows error
I was downloading GameLoop Android Emulator and it malfunctioned as so.
--
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=25961
Summary: Visual C++ 2008 runtime not marked as installed by
default
Product: Wine
Version: 1.3.12
Platform: x86
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: msvcrt
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
The installer for the app I'm looking at now
checks for the visual c++ 2008 runtime, and runs
D:\\Redistributable\\vcredist_x86_en.exe if it wasn't found.
Now, one of these days, Wine's builtin msvcr / msvcp is going to suffice
for this and most other apps, at which point Wine might want to set
the registry to indicate that vcrun2008 is already installed.
This might be in the distant future, depending on how many apps need
the other things that come with the runtime package, like mfc and a full
msvcp, that wine does not yet provide. So this bug will likely remain
open for a long time (if it's not closed for being too far ahead of its time).
For the record, this seems to be how the app is checking whether vcrun2008
is installed:
0024:Call msi.MsiQueryProductStateW(0033e2de
L"{9A25302D-30C0-39D9-BD6F-21E6EC160475}") ret=0040b9ad
0024:Call advapi32.RegOpenKeyW(80000002,0033d6c2
L"Software\\Microsoft\\Windows\\CurrentVersion\\Installer\\Managed\\S-1-5-4\\Installer\\Products\\D20352A90C039D93DBF6126ECE614057",0033d968)
ret=7ef2cd5c
0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=7ef2cd5c
0024:Call advapi32.RegOpenKeyW(80000001,0033d6c2
L"Software\\Microsoft\\Installer\\Products\\D20352A90C039D93DBF6126ECE614057",0033d968)
ret=7ef2cd5c
0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=7ef2cd5c
0024:Call advapi32.RegOpenKeyW(80000002,0033d6c2
L"Software\\Classes\\Installer\\Products\\D20352A90C039D93DBF6126ECE614057",0033d968)
ret=7ef2cd5c
0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=7ef2cd5c
0024:Call advapi32.RegOpenKeyW(80000002,0033d4ca
L"Software\\Microsoft\\Windows\\CurrentVersion\\Installer\\UserData\\S-1-5-4\\Products\\D20352A90C039D93DBF6126ECE614057\\InstallProperties",0033d964)
ret=7ef2b600
0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=7ef2b600
0024:Ret msi.MsiQueryProductStateW() retval=ffffffff ret=0040b9ad
--
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=55868
Bug ID: 55868
Summary: Horizontal tab character (ASCII 0x09) not rendered in
text fields
Product: Wine
Version: 5.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vojtech.turek(a)hotmail.cz
Distribution: ---
Created attachment 75394
--> https://bugs.winehq.org/attachment.cgi?id=75394
Wine vs. Windows: the text field contains two horizontal tab characters, none
of which are rendered by Wine
If a text field contains horizontal tab (ASCII 0x09) characters, these are not
rendered.
See the attached screenshot from Wine 5.0.3 (left) and the same application
running under Windows 10 x64 (right). The field value is
"<HT>www.test.org<HT>x" ("<HT>" denotes a single horizontal tab character), yet
Wine shows just "www.test.orgx" in the field. However, Wine clearly knows the
horizontal tab characters are present, because it shows them in the text field
tooltip stating (in English) "Website address<NEW LINE>[<TEXT FIELD VALUE>]".
Installing corefonts via winetricks (as recommended in bug #45316) does not
lead to any improvement.
--
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=56986
Bug ID: 56986
Summary: Cursor flickering in Infinity Engine games
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: accounts.winehq.org(a)vv221.fr
Distribution: ---
I get cursor flickering with some of the Infinity Engine games, maybe in all of
them.
csmt is disabled, to prevent performance problems. The games are run in a WINE
virtual desktop.
The flickering disappear if the games are run in windowed mode, it only happens
when in full screen mode.
I plan to run extra tests, first to ensure it actually affects all Infinity
Engine games, then to check if the flicker still happens with the current
development build of WINE, finally to find out when this problem was
introduced.
I am quite sure this is a regression, as I do not remember this flickering from
the last time I played these games (that was probably prior to WINE 9.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=56987
Bug ID: 56987
Summary: PiTool (pi_server.exe) can't detect Pimax HMD hid/usb
devices
Product: Wine
Version: 9.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: hid
Assignee: wine-bugs(a)winehq.org
Reporter: ivarbug(a)gmail.com
Distribution: ---
Created attachment 76817
--> https://bugs.winehq.org/attachment.cgi?id=76817
using app's hidapi.dll
https://appdb.winehq.org/objectManager.php?sClass=application&iId=19830
The windows application is able to enumerate hid devices but doesn't identify
or start talking to it's devices. The app comes with and uses a build of
hidapi.dll (version <= 0.9.0 based on it's exports).
I followed https://wiki.winehq.org/Winelib_User%27s_Guide#Building_Winelib_DLLs
and tried building my own hidapi.dll that uses Linux native hidapi-hidraw.
Using this the app does pick up the device, but crashes (probably unrelated to
hid) after ~5s in an ungetc call.
--
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=31990
Bug #: 31990
Summary: Add ability to upload extra files along with test ext
Product: Wine-Testbot
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: titan.costa(a)gmail.com
Classification: Unclassified
That would be good to have the ability to upload extra files (avi files, dlls,
.drv, ...) to perform individual test (not part of the test suite).
Otherwise it requires to embed the file or use a self extracting exe which are
not very convenient.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=33126
Bug #: 33126
Summary: divided SysEx and coalesced midiOutLongMsg
Product: Wine
Version: 1.5.25
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winealsa.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hoehle(a)users.sourceforge.net
Classification: Unclassified
Johannes Kroll reported in wine-patches that the KORG Kontrol Editor software
hung after sending an ill-formed SysEx via winealsa's midiOutLongMsg.
http://www.winehq.org/pipermail/wine-patches/2013-January/121335.html
The MIDIHDR data is F0 ... F7 00 00 00 (125 bytes).
http://www.winehq.org/pipermail/wine-devel/2013-February/098852.html
He observed that no hang occurs when skipping the trailing 3 zero bytes. F7 is
the "End Of SysEx" (EOX) marker.
It is still unclear what happens. MIDI HW is expected to skip over bogus
bytes, thus the zero bytes should cause no harm. OTOH, ALSA might be getting
into trouble processing ill-formed messages, and we don't know if or how many
bytes ALSA actually sent out through the serial port.
In any case, midiOutLongMsg handling in Wine needs fixes.
- winealsa should extract the F0...F7 part and send that as a SysEx.
- More generally, midiOutLong is known to accept not only SysEx packets, but
also coalesced status messages. Some MIDI authors prefer to send e.g. chords
via one LongMsg rather than successive calls to midiOutShortMsg, arguing that
it's faster. Hence all Wine MIDI drivers need to decompose midiOutLongMsg into
packets consisting of status message, regular SysEx ... and possibly junk.
- All APIs (MS, ALSA, OSS, CA) acknowledge the existence of divided SysEx. As
a result, framing SysEx with F0 ... F7 is entirely under application control.
The current winealsa framing code is simply wrong.
- winecoreaudio always declared 3 bytes for short messages, even program
change.
I have written a sequence of patches to fix all of this. The only thing that
is unclear is how to encapsulate garbage data like the above 3 zero bytes or
real time messages with ALSA. What ALSA API function and what ALSA message
type to use? Heck, I'm not even sure winealsa.drv/midi.c:modData is ok to send
a 2-byte MTC quarter frame via snd_seq_ev_set_sysex instead of using a
primitive that sets the type SND_SEQ_EVENT_CLOCK/TICK.
--
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=56962
Bug ID: 56962
Summary: Moto Racer 4 intro movie has broken aspect
Product: Wine
Version: 8.6
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: winegstreamer
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: ef354da59097b206122ec9101ee1f44201cca466
Distribution: ---
Created attachment 76780
--> https://bugs.winehq.org/attachment.cgi?id=76780
comparison
Good and bad versions.
--
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=56981
Bug ID: 56981
Summary: Mouse movement causes huge CPU spikes when using
WINEESYNC.
Product: Wine-staging
Version: 9.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: logos128(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Regression SHA1: e479cad86f1f7de5d2a0a0d1398e7733c0aaef3e
Distribution: ArchLinux
The problem occurs every time when Wine is launched with WINEESYNC=1 - doesn't
matter the application or the type of desktop used (virtual/non-virtual). It
also happens when wine apps are in background, i.e. the topmost window is from
a Linux app, etc. (As a side note Proton's fsync patchset is also affected.)
The process with highest CPU usage is c:\windows\system32\explorer.exe (~70%)
followed by /usr/bin/wineserver (~40%) - on a 6 core Intel CPU (12 virtual
cores).
Normally these processes have very low CPU usage (<1%) on mouse movement.
I did manual bisect on the wine-development tree and found that commit
90dcd2eaa6b6a2afaf298f1e457938350b0becfc "win32u: Use the thread message queue
shared memory in peek_message." was causing the problem with the
eventfd_synchronization patchset.
After reverting this commit + the other two related win32u commits, CPU usage
is back to normal when using esync.
Steps to reproduce:
1. Launch any Wine app - for example "winecfg".
2. Move the mouse pointer intensively.
3. See the CPU usage.
--
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.