https://bugs.winehq.org/show_bug.cgi?id=55211
Bug ID: 55211
Summary: Print file not truncated when printing to file in
FrameMaker 8
Product: Wine
Version: 8.12
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: spooler
Assignee: wine-bugs(a)winehq.org
Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de
Distribution: ---
A existing print file ist not truncated when printing to the same
file again. So when printing a smaller document to the print file
which was generated for a larger file, the resultung file contains
garbage at its end.
This happens in Framemaker 8 and may happen in other apps too.
To reproduce
- Install Framemaker from the given URL
- Print the attached Document Large.fm to a file (select print to file
in the printer dialog). Check the size of the generated file.
- Print the attached Document Small.fm to the same file generated in
the previous step. Check again the size of the file - its the same.
Depending on the used Postscript interpreter reading the file fails
because of the garbage at the files end.
This is simple to see when using different documents as descibed above.
When printing existing documents again after (even small) changes the
resulting print file may be garbage without notice.
--
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=43185
Bug ID: 43185
Summary: "Battle Bugs" game in unresponsive once game starts
Product: Wine
Version: 2.9
Hardware: x86-64
OS: Linux
Status: NEW
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: matt(a)nightrealms.com
Distribution: ---
Created attachment 58457
--> https://bugs.winehq.org/attachment.cgi?id=58457
Wine output from before starting the game
When playing the free game "Battle Bugs"
(https://ldjam.com/events/ludum-dare/38/battle-bugs) on 64 bit Linux, the game
start screen loads just fine, and pressing an indicated key starts the game
just fine, but once the game starts nothing is moving and the game doesn't
respond to any keys. Got the same results with both versions of the
executable, and both WINEARCH unspecified or set to win32
--
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=55713
Bug ID: 55713
Summary: mspaint.exe crashes with: Unhandled exception:
unimplemented function
propsys.dll.PropVariantToUInt32WithDefault
Product: Wine
Version: 8.17
Hardware: x86-64
URL: https://win7games.com/download/ClassicPaint.zip
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: propsys
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
Follow-up of https://bugs.winehq.org/show_bug.cgi?id=43670#c11
Trying to start mspaint (after following steps from above link) it crashes
instantly:
Unhandled exception: unimplemented function
propsys.dll.PropVariantToUInt32WithDefault called in wow64 32-bit code
(0x7b012407).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:002b
EIP:7b012407 ESP:0012e8b4 EBP:0012e918 EFLAGS:00000246( - -- I Z- -P- )
EAX:0012e8c0 EBX:6bb4b000 ECX:00000004 EDX:0012e938
ESI:0012e938 EDI:684c90a0
--
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=55701
Bug ID: 55701
Summary: Sniper Elite 5 launcher opens Wine Internet Explorer
instead of Options window
Product: Wine
Version: 8.16
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: mshtml
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: gabrielopcode(a)gmail.com
Regression SHA1: ee80f1a07854479c443e6b409e9c759dcfae1410
Distribution: ---
Clicking on settings icon
06d8:fixme:ieframe:NewWindowManager_EvaluateNewWindow
(000000000081FE48)->(L"about:Settings" L"resource://icon_settings.png/"
L"about:blank" (null) 0 4 0)
trying to close the launcher
06d8:fixme:ieframe:NewWindowManager_EvaluateNewWindow
(000000000081FE48)->(L"about:blank" L"resource://close.png/" L"about:blank"
(null) 0 0 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=55656
Bug ID: 55656
Summary: user32:dialog - test_IsDialogMessage() fails in the
hi-u8 and mx-MX locales on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:dialog - test_IsDialogMessage() fails in the hi-u8 and mx-MX locales on
Windows:
w10pro64-hi-u8:
dialog.c:869: Test failed: Got unexpected wparam 0x97ade5.
dialog.c:580: Test failed: Got unexpected wparam 0xfffd.
w10pro64-mx-MX:
dialog.c:867: Test failed: Got unexpected wparam 0x3f.
dialog.c:578: Test failed: Got unexpected wparam 0x3f.
See https://test.winehq.org/data/patterns.html#user32:dialog
The 'mx-MX' locale is a mix of locales and may indicate the test only succeeds
when all the Windows locales match. For reference, mx-MX uses the following
settings:
SystemDefaultLCID 0411
UserDefaultLCID 040c
ThreadLocale 0411
SystemPreferredUILanguages 0412,0409
UserDefaultUILanguage 0412
ThreadUILanguage 0412
KeyboardLayout 00000000040A0C0A
Country 231
ACP 932
A bisect shows that both sets of failures started with the commit below:
commit fe594a83d4a87fccaced20372a83ecb2ef28de6c
Author: Zhiyi Zhang <zzhang(a)codeweavers.com>
Date: Fri Aug 18 11:39:19 2023 +0800
user32/tests: Test IsDialogMessageA() converting ASCII WM_CHAR messages.
--
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=55236
Bug ID: 55236
Summary: scrrun:dictionary - test_hash_value() gets bad hashes
on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: scrrun
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
scrrun:dictionary - test_hash_value() gets bad hashes on Windows:
dictionary.c:676: Test failed: got hash 0x2eb, expected 0x2ea
dictionary.c:686: Test failed: got hash 0x2eb, expected 0x2ea
dictionary.c:695: Test failed: got hash 0x2db, expected 0x2da
dictionary.c:721: Test failed: got hash 0x2eb, expected 0x2ea
dictionary.c:732: Test failed: got hash 0x2eb, expected 0x2ea
dictionary.c:742: Test failed: got hash 0x2db, expected 0x2da
See https://test.winehq.org/data/patterns.html#scrrun:dictionary
Note that the hash values change with every run causing false positives.
--
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=54791
Bug ID: 54791
Summary: explorerframe:nstc - test_events() sometimes gets
unexpected events on Windows 7
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: explorerframe
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
explorerframe:nstc - test_events() sometimes gets unexpected events on Windows
7. This can either be a single event but it can also happen multiple times for
multiple events:
nstc.c:2265: Test failed: Got event 4, count 1
or
nstc.c:1906: Test failed: Got event 7, count 0
nstc.c:1908: Test failed: Got event 4, count 0
nstc.c:1912: Test failed: Got event 4, count 1
nstc.c:1912: Test failed: Got event 7, count 1
nstc.c:1912: Test failed: Got event 12, count 8
See https://test.winehq.org/data/patterns.html#explorerframe:nstc
This first happened on 2022-12-07 and has been happening roughly once every
three week since. So it's probably caused by a commit in the fall of 2022.
--
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=54441
Bug ID: 54441
Summary: windows.media.speech:speech - test_Recognition()
sometimes gets unexpected recognizer state on Windows
10
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
windows.media.speech:speech - test_Recognition() sometimes gets unexpected
recognizer state on Windows 10:
speech.c:1775: Test failed: recog_state was 0.
See https://test.winehq.org/data/patterns.html#windows.media.speech:speech
This failure started on 2023-01-25.
--
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=54156
Bug ID: 54156
Summary: comctl32:edit & user32:edit - test_paste() sometimes
gets an empty string on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
comctl32:edit - test_paste() sometimes gets an empty string on Windows
edit.c:3238: Test failed: got 0
See https://test.winehq.org/data/patterns.html#comctl32:edit
This happens on Windows 10 1809 to 21H2 a bit less than 3 times per month.
Where 0 is the length of the string in the field we pasted to. So that field is
empty instead of having received the string we pasted.
We can also get this failure in user32:edit (2022-11-15 w10pro64v1809):
edit.c:3211: Test failed: got 0
See https://test.winehq.org/data/patterns.html#user32:edit
But the case above is for the single-line to single-line case and there is also
the same issue happening in the multi-line to multi-line case (2022-10-25
w11pro64-amd):
edit.c:3240: Test failed: got 0
So it's a pretty general, if rare (only 4 known instances in 6 months),
problem.
Note that while one could expect this to be caused by yet another
OpenClipboard() failure, like in bug 53276, there is no failure message
indicating this to be the case.
--
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.