http://bugs.winehq.org/show_bug.cgi?id=24514
Summary: LVM_SUBITEMHITTEST fails on Chinese and Japanese
Versions of XP
Product: Wine
Version: 1.3.3
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austin.lund(a)gmail.com
In the test_hittest function for the listview test the following test fails for
the Chinese and Japanese versions on the test bot:
/* subitem returned with -1 item too */
x = pos.x + 150;
y = -10;
test_lvm_subitemhittest(hwnd, x, y, -1, 1, LVHT_NOWHERE, FALSE, FALSE, FALSE);
The failures read:
listview.c:3056: Test failed: Expected -1 retval, got -2
listview.c:3056: Test failed: Expected -1 item, got -2
listview.c:3056: Test failed: Expected flags 0x1, got 0x4
This basically says that the message returned -2 (undocumented ?) and set the
flags to LVHT_ONITEMLABEL.
Is y = -10 relative to the control client area or the parent window? How can
you be on the item label in either case? Should the above values be added as
successes to this test?
--
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=27117
Summary: Quake III Arena demo installer spawns Wine File when
setting up Start menu items
Product: Wine
Version: 1.3.19
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: tjwt(a)hush.ai
The demo is downloadable from
ftp://ftp.idsoftware.com/idstuff/quake3/win32/Q3ADemo.exe . During a default
installation in Wine, it creates ten files in C:\users\Public\Start Menu\ and
ten Wine File windows appear. No Windows Explorer windows open when installing
under Windows XP. I see the problem with Wine 1.3.18 and 1.3.19 (I did not try
earlier versions).
--
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=33092
Bug #: 33092
Summary: Melodyne Studio demo crashes on startup
Product: Wine
Version: 1.4.1
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jules.bernable(a)laposte.net
Classification: Unclassified
Created attachment 43757
--> http://bugs.winehq.org/attachment.cgi?id=43757
wine backtrace
Could the same issue as #16650, however this is happening with wine 1.4.1 on
debian wheezy.
--
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=58044
Bug ID: 58044
Summary: Realm Grinder freezes/crashes after a very long run
Product: Wine
Version: 10.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
Created attachment 78299
--> https://bugs.winehq.org/attachment.cgi?id=78299
output of two failed runs
This I strongly suspect is a regression, yet I can't really pin down the time
when this started happening. The problem happens with little to no human
interaction, yet the timeframes make it unreasonable to actively reproduce.
I suspect it started around 10.0 release, but with a -/+ 2 months margin (so
close to useless).
Anyway, what's the problem ?
If Realm Grinder is run for long enough (but 'long enough' here is measured in
*days*), it tends to eventually either freeze with a completely black window or
crash with an X server error.
The attachment has output of two such runs, second chunk is when it just froze,
the first when it crashed.
'fixme:d3d:swapchain_blit_gdi Using GDI present.' at the end of both seems to
be the moment the problem triggers.
It seems to be some kind of a resource leak, but it doesn't affect any other
apps running besides it, not even those run by wine.
No user action is really required to trigger this - I've seen it freeze after a
desktop switch, I've seen it crash when the window was just displayed, but not
really interacted with.
(Realm Grinder here is still at v4.2.27.0, though I'll likely update it shortly
for Easter event)
--
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=42898
Bug ID: 42898
Summary: Listbox keyboard input
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: janwinehq(a)gmail.com
Distribution: ---
A listbox widget in Wine does not react the same way to keyboard input as in
Windows.
In Windows, you can type the first characters of a word and the cursor will
jump to the first item matching *all* the characters you typed. This allows you
to drill down quickly to the item you want.
In Wine, when you start typing it only considers the *last* character you typed
when looking for a match. On listboxes where you have lots of items starting
with the same character, this can make it problematic to drill down to the
correct item.
This may be better explained with a simple example. Suppose you have a listbox
with the following items, sorted alphabetically:
* AMBER
* BLUE
* BROWN
* GREEN
* ORANGE
* RED
* YELLOW
Windows behavior:
* if you type "B", it will drill down to "BLUE"
* if you type "BR", it will drill down to "BROWN"
* if you type "BRO", it will drill down to "BROWN"
Wine behavior:
* if you type "B", it will drill down to "BLUE"
* if you type "BR", it will drill down to "RED"
* if you type "BRO", it will drill down to "ORANGE"
--
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=57943
Bug ID: 57943
Summary: Critical program error in CorelDraw 2024 Setup.exe
Product: Wine
Version: 10.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: d.astra(a)yopmail.com
Distribution: ---
Created attachment 78189
--> https://bugs.winehq.org/attachment.cgi?id=78189
The crash dump from CorelDraw 2024 Setup.exe
I manually downloaded the real CorelDraw Setup (not the CDGS2024.exe, which
gets a connection timeout while trying to download from the corel servers) to
install the program. Neither the Setup.exe in the root directory
(CorelDRAWGraphicsSuite2024Installer), nor the Setup_x64.msi work. They crash
nearly instantly with a critical error. I provide the crash dump from the main
Setup.exe, as both dumps are the same.
--
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=55176
Bug ID: 55176
Summary: Regression: Wing Commander Secret Ops/Prophecy unable
to launch.
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jcarthew(a)gmail.com
Distribution: ---
Game fails to load with a fatal error:
"file 'game\\cdlayout.iff' not found and not optional"
0024:err:vxd:MONODEBG_DeviceIoControl "Fatal: "
0024:err:vxd:MONODEBG_DeviceIoControl "Iff::Iff open file 'game\\cdlayout.iff'
not found and not optional"
0024:fixme:event:wait_for_withdrawn_state window 0x10070/a00001 wait timed out
0024:fixme:event:wait_for_withdrawn_state window 0x20070/a00004 wait timed out
Bug was introduced between WINE 7.8 and 7.9. Generating regression testing to
locate exact patch.
--
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=48795
Bug ID: 48795
Summary: Patches website mishandles HTML attachments
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Here is an example:
https://source.winehq.org/patches/data/181590
Created from:
https://www.winehq.org/pipermail/wine-devel/2020-March/162581.html
This typically happens with replies to patches:
* In the plain text version the diff is prefixed with "> " characters so it is
not recognized as a patch.
* But in the HTML version or the email the quoting is done through HTML tags
which typically leave "+++" at the start of the line. As a result the HTML part
can look like a patch.
But it could also happen if someone sends a patch in an HTML-only email (e.g.
due to a mail client misconfiguration).
The TestBot normally ignores HTML attachments (see NewPatch() in Patches.pm).
But when patches go through the patches website the TestBot does not have
access to the raw email. Instead it gets the files prepared by the patches
website as in the first link. Such files erase the distinction between the
plain text and HTML part and so mislead the TestBot into creating a job.
--
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=23978
Summary: keyboard seems to be dead after changing to another
field with TAB-key
Product: Wine
Version: 1.2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lorenz.giefing(a)utanet.at
Created an attachment (id=30111)
--> (http://bugs.winehq.org/attachment.cgi?id=30111)
WINDEBUG=+all
FileMaker Pro 5
If I change to another form-field using the TAB-key, the keyboard is dead, no
reaction at all. Mouse acts normal, I can use the menus and copy/paste text
anyway.
Clicking out of the window and into again (getting focus again) and the
keyboard is alive again.
There seems to be a pattern depending on the field, some trigger the problem
each time I leave them with TAB, some never do.
After reading a lot of bug reports, I tried "virtual desktop" on/off, "allow
window manager" on/off, no changes at all.
I tried [HKCU\software\Wine\X11 Driver] UseTakeFocus="yes" without changes.
Ubuntu 10.04
Keyboard and mouse via PS2
No SCIM installed.
--
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=50828
Bug ID: 50828
Summary: CompressonatorGUI 4.1 installer crashes (Advanced
Installer)
Product: Wine
Version: 6.4
Hardware: x86-64
URL: https://github.com/GPUOpen-Tools/Compressonator/releas
es/tag/V4.1.5083
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: the.ideals(a)gmail.com
Distribution: ---
After selecting or deselecting prerequisites during setup, the setup crashes.
[SEH_AV_READ_BADPTR] ACCESS_VIOLATION (0xc0000005) at address [0x00424f72]
Advanced Installer Enhanced UI 13.5 build 74683
*** Stack Trace (x86) ***
[0x00424f72] EntryPoint()
[0x00424ae6] EntryPoint()
[0x00400000] MODULE_BASE_ADDRESS
sha1sum CompressonatorGUI_x64_4.1.5083.exe
cb0c6f9bcaf7d2c93287ddeb90e72efa771b19fe CompressonatorGUI_x64_4.1.5083.exe
du -sh CompressonatorGUI_x64_4.1.5083.exe
33M CompressonatorGUI_x64_4.1.5083.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.