http://bugs.winehq.org/show_bug.cgi?id=16265
Summary: ActiveX Control Pad installer hangs sometimes on exit;
deadlock between LdrShutdownThread and TASK_ExitTask?
Product: Wine
Version: 1.1.9
Platform: Other
URL: http://msdn.microsoft.com/en-us/library/ms968493.aspx
OS/Version: other
Status: NEW
Keywords: download, Installer
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
A user said that ConvWPT ran in Wine, but gave a very complicated recipe,
so I tried simplifying it. Along the way, I noticed that Microsoft's
ActiveX Control Pad installer hangs sometimes on exit. Here's how to
reproduce:
1) Do "winetricks wsh56", else "winetricks fm20" will fail with dialog
"Setup has determined that Microsoft Internet Explorer 3.0 was not detected."
2) Do "winetricks fm20". This will complain "Setup was unable to start DDE
communication with the desktop". Click Ignore.
(This is probably bug 9159.)
When the installer is done, it sometimes hangs with
err:ntdll:RtlpWaitForCriticalSection section 0x7ef2b3c0 "syslevel.c:
Win16Mutex" wait timed out in thread 002f, blocked by 002e, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7efec5e4 "loader.c:
loader_section" wait timed out in thread 002e, blocked by 002f, retrying (60
sec)
Using winedbg, I was able to get a backtrace of those threads by pressing ^C
and then using the bt command:
Wine-dbg>bt 0x2e
Backtrace:
=>1 RtlpWaitForCriticalSection+0x2fd(crit=0x7efec5e4)
[dlls/ntdll/critsection.c:64] in ntdll
2 RtlEnterCriticalSection+0x4a(crit=<?>) [dlls/ntdll/critsection.c:553] in
ntdll
3 LdrShutdownThread+0x49() [dlls/ntdll/loader.c:2160] in ntdll
4 RtlExitUserThread+0x67(status=<?>) [dlls/ntdll/thread.c:628] in ntdll
5 in kernel32 (+0x74ca6)
6 DOSVM_Int21Handler+0x9a17(context=0x7e56638c) [dlls/winedos/int21.c:3192]
in winedos
7 DOSVM_CallBuiltinHandler+0x17(context=0x7e56638c, intnum=<?>)
[dlls/winedos/interrupts.c:712] in winedos
8 INSTR_CallBuiltinHandler+0x3c(context=0x7e56638c, intnum=<?>)
[dlls/kernel32/instr.c:901] in kernel32
9 DOS3Call+0x25(context=0x7e56638c) [dlls/kernel32/instr.c:911] in kernel32
...
Wine-dbg>bt 0x2f
Backtrace:
=>1 RtlpWaitForCriticalSection+0x2fd(crit=0x7ef2b3c0)
[dlls/ntdll/critsection.c:64] in ntdll
2 RtlEnterCriticalSection+0x4a(crit=<?>) [dlls/ntdll/critsection.c:553] in
ntdll
3 _EnterSysLevel+0x7b(lock=0x7ef2b3c0) [dlls/kernel32/syslevel.c:106] in
kernel32
4 _EnterWin16Lock+0x20() [dlls/kernel32/syslevel.c:187] in kernel32
5 TASK_ExitTask+0x19() [dlls/kernel32/task.c:564] in kernel32
6 DllMain+0x75(hinst=0x7ee10000, reason=3, reserved=(nil))
[dlls/kernel32/kernel_main.c:212] in kernel32
7 __wine_spec_dll_entry+0x3e(inst=0x7ee10000, reason=<?>, reserved=<?>)
[dlls/winecrt0/dll_entry.c:40] in kernel32
8 call_dll_entry_point+0x15() in ntdll
9 MODULE_InitDLL+0xe3(wm=<?>, reason=3, lpReserved=(nil))
[dlls/ntdll/loader.c:912] in ntdll
10 LdrShutdownThread+0x96() [dlls/ntdll/loader.c:2163] in ntdll
11 RtlExitUserThread+0x67(status=<?>) [dlls/ntdll/thread.c:628] in ntdll
12 in kernel32 (+0x74ca6)
13 WINOLDAP_EntryPoint+0x1a2(context=0x7d7b138c)
[dlls/kernel32/kernel16.c:207] in kernel32
...
--
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=39249
Bug ID: 39249
Summary: AMD and Intel problem O2Jam Black Screen problem
Product: Wine
Version: 1.7.51
Hardware: x86-64
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: onte_jc(a)yahoo.com
AMD and Intel problem O2Jam Black Screen problem
http://o2jam.intgamerz.net
Running O2Jam in AMD or Intel Graphics will stuck the game, black screen, not
runnable anymore
Nvidia is working fine w/o any problems at all
--
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=41269
Bug ID: 41269
Summary: MSI uninstaller does not clean up Registry's
UpgradeCode, ProductCode
Product: Wine
Version: 1.9.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: reinhold.hoffmann(a)hotmail.com
Distribution: ---
Created attachment 55569
--> https://bugs.winehq.org/attachment.cgi?id=55569
What needs to be deleted in the Registry when de-installing
When uninstalling an installed Wine app the uninstaller de-installs the app
accurately but it does not clean up the UgradeCode and ProductCode in the
Registry. In an subsequent installation when the same app (same UpgradeCode,
different ProductCode, higher version number) is installed, the MSI option
"RemoveExistingProducts" fails. "RemoveExistingProducts" should automatically
de-install a former version before the new version is installed. As a
consequence always the former version needs to be manually de-install BEFORE
the new version otherwise the next installation fails.
In addition the Windows call "MsiEnumRelatedProducts" finds a product which
does not exist anymore. De-installing with "MsiConfigureProduct
(parameter=ProductCode, INSTALLLEVEL_DEFAULT, INSTALLSTATE_ABSENT)" does not
work either.
Because the MSI uninstaller leaves all ProductCodes of former installations in
place forever, the Registry get screwed and is not in sync to what really is
installed.
This is a big issue for almost every our customer when installing updates or
upgrade. Always, the former installation has to be manually de-installed
because "RemoveExistingProducts" always fails. We have detected this issue in a
deep dive and see this bug to be the biggest issue for our customers for a
broader use of our software on Wine. Therefore set this bug to be critical.
Please find attached what needs to be deleted in the Registry when the
uninstaller de-installs a software.
The bug happens for Ubuntu, openSuSE, Mac OS X
Reinhold
--
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=45828
Bug ID: 45828
Summary: Unimplemented function ntdll.dll.WinSqmIncrementDWORD
called in several Win 7 games upon exiting
Product: Wine
Version: 3.15
Hardware: x86
URL: http://www.4forum.us/purble-place-the-greatest-game/
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: ---
Hi,
A user reported these crashes on forum:
https://forum.winehq.org/viewtopic.php?f=2&t=29535#p118004
Easiest to reproduce is run Solitaire.exe if you have a Win7 partition by hand;
Upon exiting the game it crashes.
--
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=42550
Bug ID: 42550
Summary: Photoshop CC 2017: Installation Error
Product: Wine
Version: 2.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jf(a)grafik-service.info
Distribution: ---
Created attachment 57454
--> https://bugs.winehq.org/attachment.cgi?id=57454
Install Log
Using this Installer:
https://download-esd.adobeoobe.com/AdobeProducts/eca60e6c-1f05-41de-bf6b-ae…
sha1: 329402f2358b8db7c01c405993a1e5d75ea6a468
it gets to about 30 %, then throws an 'unknown error' with code 1.
--
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=44620
Bug ID: 44620
Summary: `Nt{WaitFor,Release}KeyedEvent()` don't accept null
handles, while Windows 7 does.
Product: Wine
Version: 3.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: lh_mouse(a)126.com
Distribution: ---
Created attachment 60609
--> https://bugs.winehq.org/attachment.cgi?id=60609
testcase
Testcase (also attached as 'ntwaitforkeyedevent.c'):
------
#include <winternl.h>
#include <winnt.h>
#include <stdio.h>
__attribute__((__dllimport__, __stdcall__))
extern NTSTATUS NtWaitForKeyedEvent(HANDLE hKeyedEvent, void *pKey, BOOLEAN
bAlertable, const LARGE_INTEGER *pliTimeout);
int main(void){
LARGE_INTEGER liTimeout;
NTSTATUS lStatus;
liTimeout.QuadPart = -10000000;
printf("Waiting...\n");
lStatus = NtWaitForKeyedEvent(NULL, &lStatus, FALSE, &liTimeout);
printf("NtWaitForKeyedEvent() returned %08lx\n", lStatus);
return 0;
}
------
Compiling and running this program on Linux Mint 18.3 results in the following
output:
------
lh_mouse@lhmouse-ideapad-720S ~/桌面 $ x86_64-w64-mingw32-gcc
ntwaitforkeyedevent.c -Wall -Wextra -Wpedantic -lntdll && ./a.exe
Waiting...
NtWaitForKeyedEvent() returned c0000008
lh_mouse@lhmouse-ideapad-720S ~/桌面 $ wine --version
wine-3.0
lh_mouse@lhmouse-ideapad-720S ~/桌面 $
------
On Windows 7 `NtWaitForKeyedEvent()` returns `STATUS_TIMEOUT` i.e. it
succeeds:
------
E:\Desktop>x86_64-w64-mingw32-gcc ntwaitforkeyedevent.c -Wall -Wextra
-Wpedantic -lntdll && a.exe
Waiting...
NtWaitForKeyedEvent() returned 00000102
------
Passing null handles to `Nt{WaitFor,Release}KeyedEvent()` is how SRW locks and
condition variables are implemented on Windows 7. I presume that a handle to
the preallocated global keyed event with the name
'\KernelObjects\CritSecOutOfMemoryEvent' is used in this case.
At the moment <https://github.com/lhmouse/mcfgthread> expects the Windows
behavior and fails in 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=45966
Bug ID: 45966
Summary: Regression from TraCFoil ribs plotting program
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: tracfoil(a)free.fr
Distribution: ---
Created attachment 62520
--> https://bugs.winehq.org/attachment.cgi?id=62520
Regression from TraCFoil ribs plotting program
I use TraCFoil (https://tracfoil.com/tracfoil/en/telechargementE.html)
But somme problems with scrollbars with the last devel version
This program is written in Visual Basic 5.0 Microsoft
Libraries and controls needed to run this program
-* Vb5fr.dll
-* cmctlfr.dll
-* Cmdlgfr.dll
-* Msvbvm50.dll
-* Comctl32.ocx
-* Comdlg32.ocx
On Wine devel 3.17
horizontal and vertical scrollbars are no displayed
see tf412_wine-devel317.png
If i use on full screen the scrollbars are a black band
see tf412_wine-devel317_full screen_hscrollbar.png
On Wine devel 3.14
horizontal and vertical scrollbars are displayed and OK
see tf412_wine-devel314.png
If test on wine stable 3.0.
horizontal and vertical scrollbars are displayed and OK
see tf412_wine-stable303.png
--
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=45970
Bug ID: 45970
Summary: Add support for browseui IProgressDialog
PROGDLG_AUTOTIME flag
Product: Wine
Version: 3.17
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
to track:
https://www.winehq.org/pipermail/wine-devel/2018-October/thread.html#133363
Wine-Staging patch:
https://github.com/wine-staging/wine-staging/tree/master/patches/browseui-P…
Also seen in console output for various installers:
--- snip ---
fixme:browseui:ProgressDialog_StartProgressDialog Flags PROGDLG_AUTOTIME not
supported
--- snip ---
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=44759
Bug ID: 44759
Summary: Steam show all text with italic font when dwrite is
enabled
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: dwrite
Assignee: wine-bugs(a)winehq.org
Reporter: andy86(a)fastwebnet.it
Distribution: ---
When dwrite is enabled steam show all text as italic.
If dwrite is disabled text is poor quality.
Present in wine 3.4
Problem do not occurs if use 64bit wine profile. :-/
--
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.