https://bugs.winehq.org/show_bug.cgi?id=40715
Bug ID: 40715
Summary: American Girls Dress Designer crashes on clicking
Print or Quit
Product: Wine
Version: 1.9.11
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: peanuthead_069(a)yahoo.com
Created attachment 54613
--> https://bugs.winehq.org/attachment.cgi?id=54613
Crash log for Dress Designer
Title says all. I've been encountering this issue on Windows before, so I
thought of running the game on Wine to see if compatibility for this would be
better under it. At first I thought it was just Wineskin acting up so I ran it
on a clean, vanilla Wine to confirm things, but still no dice - Dress Designer
throws up an "An error occurred while opening a window" message and a Visual
C++ runtime error.
There's not much in the way of logs either, just a two EnumDisplayDevicesW
fixmes and what appears to be a ddraw error. On modern Windows versions, the
game's backgrounds are cut off to the right (http://i.imgur.com/BqGDfkF.png),
so that may have something to do with directdraw.
--
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=36994
Bug ID: 36994
Summary: War Thunder : Mouse aim unusable
Product: Wine
Version: 1.7.23
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: benoit(a)anbcorp.net
Created attachment 49143
--> http://bugs.winehq.org/attachment.cgi?id=49143
trace with +ddraw,+dinput,+cursor,+event
When using mouse aim in War Thunder (which is basically a FPS like control
mode), the cursor seems to be blocked by screen edges.
Normally, I should be able to go in a direction infinitely (much like in any
FPS).
Moreover, in dual screen, the auto-capture in fullscreen do not work, the
cursor go out in the second screen.
I tried MouseWrapOverride=Force with no success.
Forcing single screen doesn't help either. Neither does playing in windowed
mode or virtual desktop (fullscreen and windowed).
I suspected my window manager (awesome) and tried under xfce : no change.
I tried various versions of wine from 1.7.23 to 1.5.25 : no change either.
My configuration is :
Linux 3.14 on debian jessie,
Xorg server 1.15.1
Proprietary ati drivers 14.4
Wine 1.7.23
Attached is a trace with WINEDEBUG="+ddraw,+dinput,+cursor,+event" were I was
circling the mouse around. It seems the cursor is indeed blocked on the screen
edge.
Feel free to ask for more details.
--
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=37277
Bug ID: 37277
Summary: Minitab 17.10 fails with COM error
Product: Wine
Version: 1.7.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: graylion(a)sm-wg.net
After installation of minitab 17.10 starting it fails with "A necessary
component could not be created. Error code: 80040154
See http://support.microsoft.com/kb/175804
--
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=51629
Bug ID: 51629
Summary: rundll32.exe crash: unimplemented function
mscorwks.dll.DllRegisterServerInternal
Product: Wine
Version: 6.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: joseskvolpe(a)gmail.com
Distribution: ---
Created attachment 70485
--> https://bugs.winehq.org/attachment.cgi?id=70485
32-bit and 64-bit backtrace. They appear in the same (default) 64-bit
wineprefix
rundll32.exe crashes every wine update
This issue were happening with me since version 6.13
There's reported similar issues with this software, but they might have
different reasons (thus being classified as invalid), they didn't had backtrace
attachments and they were reported in much older versions of 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=51705
Bug ID: 51705
Summary: 16 bit apps don't run on versions > 6.5
Product: Wine-staging
Version: 6.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mmikeinsantarosa(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Beginning with wine-staging 6.6 my 16 bit applications will no longer run.
cardfile.exe ran on wine-staging up to version-6.5. from 6.6 on it will no
longer run.
I've posted in the winehq forum about this @
https://forum.winehq.org/viewtopic.php?f=8&t=35349 and have had > 700 views but
not one response.
This is what I see when executing cardfile.exe from a terminal
|0c8:err:plugplay:try_add_device Building report descriptor failed,
removing device 00c8:err:plugplay:try_add_device Building report
descriptor failed, removing device 014c:err:module:import_dll Loading
library krnl386.exe16 (which is needed by
L"C:\\windows\\system32\\winevdm.exe") failed (error c0000131).
014c:err:module:LdrInitializeThunk Importing dlls for
L"C:\\windows\\system32\\winevdm.exe" failed, status c0000135|
--
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=47858
Bug ID: 47858
Summary: x3daudio1_{0,1,2} need ABI corrections
Product: Wine
Version: 4.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: x3daudio
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
Created attachment 65361
--> https://bugs.winehq.org/attachment.cgi?id=65361
patch that attempts to fix the problem
Primary purpose of this bug is the problem addressed in recently sent
"x3daudio: fix lib exports" patch.
Patch attached should fix the problem...that is, if the problem is properly
diagnosed.
However, there's a secondary purpose.
App used to notice and diagnose the problem was Supreme Commander (RTS - see
the entry in appdb).
Without the patch, builtin fails early with a missing function error.
With the patch, game goes as far as the menu...
...but if (for example) you try to start a skirmish, it crashes.
I'm not sure whether it's a problem with wine or a problem with FAudio.
With native x3daudio, it works, so the problem is still in this or underlying
lib.
Going by the debug channel, game first calls X3DAudioInitialize a couple times
(seemingly successfully), then it calls X3DAudioCalculate with 0x61 flags and
goes into faultrep after that call. Shortly after that it terminates, often
with that annoying err:ntdll:RtlpWaitForCriticalSection hang.
--
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=51659
Bug ID: 51659
Summary: Thronebreaker:The Witcher Tales-- Mahakam act
beginning has broken cutscene ( MFP)
Product: Wine-staging
Version: 6.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yurnerolinux(a)yandex.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 70531
--> https://bugs.winehq.org/attachment.cgi?id=70531
Save files to quickly get into that act
Game had correctly working cutscenes until this act. Cutscene at the start of
this act looks like this.
https://i.imgur.com/BDkh0tq.png
Adding save files to make reproduction process easier. Otherwise person who
tries to repro would have to sink hours in it. With those save files in place
clicking to continue in main menu should grant the broken cutscene right away.
Combinations that problem is reproduced on:
- Wine 6.15 Staging- Reproduces the problem with both dxvk and wined3d
- Lutris 6.14 Fshack- Reproduces the problem with both dxvk and wined3d
- Screenshot above is taken on Wine 6.15 Staging+ Dxvk
--
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=34584
Bug #: 34584
Summary: thai2english not working at all may ole32 related
Product: Wine
Version: 1.7.2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ole32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: genrobgen5(a)gmail.com
Classification: Unclassified
Hi
linux distr debian wheezy (recently updated)
gcc version 4.6.3 (Debian 4.6.3-14)
thai2english-setup-2.3.4233.exe
http://www.thai2english.com/downloading/thai2english-setup-2.3.4233.exe
started with wine '/root/.wine/drive_c/Program
Files/Thai2English/thai2english.exe'
wine version 1.7.2 with wine.git-87c459ab2359784f238c30073b1adc0111876987.patch
I tried the patch mplementing VarDecRound
(wine.git-87c459ab2359784f238c30073b1adc0111876987.patch) in wine-1.7.2,
unfortunately it does not seem to have helped with [Bug 34463] thai2english.
I think there is going to be more than one bug. A visable bug at the moment is
CoGetContextToken apartment not initialised (see attached log log-initial in
attachment). I did a
WINEDEBUG=+ole,+relay wine '/root/.wine/drive_c/Program
Files/Thai2English/thai2english.exe' 2>log+ole,+relay
followed by
grep 'CoGetContextToken' log+ole,+relay
to give
002c:Call ole32.CoGetContextToken(030be730) ret=791f525b
trace:ole:CoGetContextToken (0x30be730)
err:ole:CoGetContextToken apartment not initialised
002c:Ret ole32.CoGetContextToken() retval=800401f0 ret=791f525b
002d:Call ole32.CoGetContextToken(045be790) ret=791f525b
trace:ole:CoGetContextToken (0x45be790)
002d:Ret ole32.CoGetContextToken() retval=00000000 ret=791f525b
0030:Call ole32.CoGetContextToken(046be710) ret=791f525b
trace:ole:CoGetContextToken (0x46be710)
trace:ole:CoGetContextToken apt->context_token=0x188750
0030:Ret ole32.CoGetContextToken() retval=00000000 ret=791f525b
(see log+ole+relay-greped in attachment)
retval=800401f0 refers to return CO_E_NOTINITIALIZED in CoGetContextToken in
wine-1.7.2/dlls/ole32/compobj.c so apartment_find_multi_threaded() fails.
I suspect the following bit of code fails
LIST_FOR_EACH( cursor, &apts )
{
struct apartment *apt = LIST_ENTRY( cursor, struct apartment, entry );
if (apt->multi_threaded)
{
result = apt;
apartment_addref(result);
break;
}
}
this piece of code looks for a struct apartment in &apts (or possibly it might
create one if none exists)
&apts created by
static struct list apts = LIST_INIT( apts ); /* protected by csApartment */
however there does not appear to be any struct apartment or an appropriate
pointer in struct list
I am not sure how the program is supposed to work but there is a problem here.
By the way thai2english does not work at all I am not just making it up or
something. If the bug is not worth dealing with then that is not a problem to
me as I can us virtualbox however wine is a neater solution.
Rob
--
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=51696
Bug ID: 51696
Summary: ntoskrnl.exe:ntoskrnl outputs too much traces (and
broke the Wine tests entirely)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ntoskrnl.exe:ntoskrnl outputs more than 200kB of traces:
$ ./wine dlls/ntoskrnl.exe/tests/ntoskrnl.exe_test.exe ntoskrnl
>ntoskrnl.report
$ tail -n3 ntoskrnl.report
0270:ntoskrnl: 96 tests executed (1 marked as todo, 0 failures), 0 skipped.
0020:ntoskrnl: Silenced 5475 todos, 0 skips and 0 traces.
0020:ntoskrnl: 21296 tests executed (1967 marked as todo, 0 failures), 0
skipped.
$ ls -l ntoskrnl.report
-rw-r--r-- 1 fgouget fgouget 208428 août 28 18:37 ntoskrnl.report
$ grep "Test marked todo:" ntoskrnl.report | wc -cl
1994 204531
This is not a problem of a runaway test or even that many trace() statements.
It's just that there are too many todos despite the vast majority being
silenced already.
The big issue is that adding so much data to a full Winetest run pushes it over
the 1.5MB limit (before and after debiant2 WineTest reports):
-rw-r--r-- 1 fgouget fgouget 1477298 août 28 20:27
/tmp/job96432_1_1_win32.report
-rw-r--r-- 1 fgouget fgouget 1689913 août 28 20:24
/tmp/job96543_1_1_win32.report
The commit that introduced the extra todos is:
commit 8d37962b43e5074bc0421611267dc41593114f85
Author: Zebediah Figura <zfigura(a)codeweavers.com>
AuthorDate: Thu Aug 26 20:54:10 2021 -0500
ntoskrnl/tests: Add more tests for IRP status handling.
Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
Also the TestBot warned about this issue when the patch was submitted, though
that did not carry over to sending an email to wine-devel or marking the patch
as failed on the patches website (bug 51695).
https://testbot.winehq.org/JobDetails.pl?Key=96439#k401
--
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.