https://bugs.winehq.org/show_bug.cgi?id=41235
Bug ID: 41235
Summary: msiexec fails to show installer window
Product: Wine
Version: 1.7.51
Hardware: x86-64
URL: https://dl.bintray.com/supertux/SuperTux-Nightly/:Supe
rTux-v0.5.0-rc.3-23-g470349f-win32.msi
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: tobbi.bugs(a)googlemail.com
When I try to install an MSI file, it doesn't open. I am only getting the
following error messages on the console:
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
err:winediag:nulldrv_CreateWindow Application tried to create a window, but no
driver could be loaded.
err:winediag:nulldrv_CreateWindow The explorer process failed to start.
err:msi:dialog_run_message_loop Failed to create dialog L"PrepareDlg"
err:msi:dialog_run_message_loop Failed to create dialog
L"MaintenanceWelcomeDlg"
err:msi:dialog_run_message_loop Failed to create dialog L"ProgressDlg"
err:msi:dialog_run_message_loop Failed to create dialog L"ExitDialog"
This has also been reported on the forums:
https://forum.winehq.org/viewtopic.php?f=9&t=27223
I tried with the following msi file:
https://dl.bintray.com/supertux/SuperTux-Nightly/:SuperTux-v0.5.0-rc.3-23-g…
SHA1(SuperTux-v0.5.0-rc.3-23-g470349f-win32.msi)=
4343922f3f0342d86088ac286fb8d3a32e039330
--
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=41550
Bug ID: 41550
Summary: The native implementation of OLEAUT32.DLL cannot be
used with Wine's RPCt4.DLL. Remove OLEAUT32.DLL and
try again.
Product: Wine
Version: 1.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: oleaut32
Assignee: wine-bugs(a)winehq.org
Reporter: lokesh.bhandari(a)enjayworld.com
Distribution: ---
The native implementation of OLEAUT32.DLL cannot be used with Wine's RPCt4.DLL.
Remove OLEAUT32.DLL and try again.
I am trying to run my custom application in wine
-- In which if I do not make oleaut32.dll to native then it show message "run
time error 91 object variable or with block variable not set"
After that I have make oleaut32.dll to native from winetricks
-- when I am trying to export to excel then it show message "The native
implementation of OLEAUT32.DLL cannot be used with Wine's RPCt4.DLL. Remove
OLEAUT32.DLL and try again."
I have read too many post but not found correct solution for that.
I am using wine 1.8.
--
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=39986
Bug ID: 39986
Summary: Smartflix (to access Netflix) gives an error - setup
does not start
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: thierry.salmon(a)gmail.com
Distribution: ---
Created attachment 53425
--> https://bugs.winehq.org/attachment.cgi?id=53425
file created after Smartlix crashed
When starting Smartflix (to access Netflix), I get this error. See attachment.
wine SmartflixSetup.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.
https://bugs.winehq.org/show_bug.cgi?id=39749
Bug ID: 39749
Summary: Battle Realms: black screen after starting a new game
(only with nouveau?)
Product: Wine
Version: 1.7.53
Hardware: x86
URL: http://www.fileplanet.com/82509/80000/fileinfo/Battle-
Realms-Demo
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: stefan(a)codeweavers.com
Regression SHA1: 973de3f59c7d47602fe68c8cecf8fc3dbc59bcff
Distribution: ---
The game loads to the main menu, but when I start a new game (or the tutorial
in the demo version) I'm getting only a black screen although the game seems to
be running because I can hear audio from the game.
Alt-tabbing back and forth doesn't resolve the problem, but if I switch to
another workspace in XFCE and switch back to the game, then the screen is
displayed correctly.
Actually, I have this problem with some other games as well: Planescape:Torment
shows the same behaviour when I try to save the game, the screen is not
refreshing in the save game dialogue.
Atlantis III also has a similar problem: after playing the intro video, the
screen remains frozen (until I switch workspaces back and forth).
According to my testing, the problem in those games was introduced by
commit 973de3f59c7d47602fe68c8cecf8fc3dbc59bcff
Author: Stefan Dösinger <stefan(a)codeweavers.com>
Date: Thu Oct 15 22:41:12 2015 +0200
wined3d: Pass a context to surface_load_location.
The commit can't be reverted, but the games work properly with the previous
commit.
I can't reproduce the problem with Nvidia binary driver 340.96.
Stefan, could you please check whether it is present with other gpus/drivers?
To reproduce the problem in Battle Realms demo:
1. Install and start the demo. You can skip the intros by pressing <Space>. In
the main menu select <New Game>, choose <Tutorials> and select one of the
available missions. When the map is loaded (sound begins to play) the screen
remains black here.
Wine 1.8-rc3
Fedora 23
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NV92
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.2.0-devel
OpenGL core profile shading language version string: 3.30
X Server 1.18
XFCE 4.12 (also present in Gnome 3 and Openbox window managers)
BattleRealmsDemo.zip
sha1: fd5f8e5bc30df10abc0b9d4890f8dd3c8953ba90
Terminal output:
fixme:ddraw:DirectDrawEnumerateExA flags 0x00000006 not handled
fixme:win:EnumDisplayDevicesW ((null),0,0x33f258,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x33ba98,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x33ba98,0x00000000), stub!
fixme:ddraw:ddraw7_Initialize Ignoring guid
{aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:win:EnumDisplayDevicesW ((null),0,0x33f598,0x00000000), stub!
fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to
16
fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to
16
fixme:ddraw:ddraw_surface7_Flip Ignoring flags 0x1.
fixme:ddraw:ddraw7_FlipToGDISurface iface 0x12aeb0 stub!
--
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=41144
Bug ID: 41144
Summary: GOG Galaxy fails to start in every version of Windows
after Windows XP
Product: Wine
Version: 1.9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fjfrackiewicz(a)gmail.com
Distribution: ---
Created attachment 55350
--> https://bugs.winehq.org/attachment.cgi?id=55350
Sample terminal output from a prefix set to Windows 7 mode
I am not sure if this will be considered a valid bug report but GOG Galaxy has
issues when attempting to start it on any version of Windows besides XP.
The issue here is manifold:
1. Windows-only games that are 64-bit only with no 32-bit version are becoming
more and more common. This makes it impossible for users to use certain online
features within the game such as uploading discoveries because the online
portion requires GOG Galaxy to be present and running.
2. The 64-bit version of Windows XP has never received Service Pack 3 and GOG
Galaxy requires, at minimum, Windows XP SP3.
Here's one scenario I have tried to make Galaxy run in a 64-bit Windows 7
install:
1. Run winetricks vcrun2010 vcrun2012 vcrun2013 in Windows 7 mode.
2. Switch the prefix to Windows XP mode then run winetricks vcrun2015 to get
around the issue with Windows 7 mode and the lack of a working Windows Upgrade
Service in the non-Staging version of Wine.
3. Install GOG Galaxy afterwards in Windows 7 mode.
4. Attempt to run "wine GalaxyClient.exe"
I am not sure if this issue is caused by running "winetricks vcrun2015" in
Windows XP mode and then switching to Windows 7 mode as I've used this
workaround to work around VC2015 issues with UE4 games that require Windows 7
and above in order to run.
I have tried starting GOG Galaxy with and without "winetricks vcrun2010
vcrun2012 vcrun2013" ("winetricks vcrun2015" is always needed for now so very
attempt at me running GOG Galaxy will have this winetrick performed). I have
also attempted to run Galaxy in Vista, 8, 8.1 modes and nothing works.
Is there anything I am missing and is there anything I can do to help get it
running in a 64-bot prefix?
--
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=39790
Bug ID: 39790
Summary: brainexplorer2 crashes when run w/o
WINEDEBUG=warn+heap
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
Created attachment 53085
--> https://bugs.winehq.org/attachment.cgi?id=53085
backtrace when WineExplorer crashes.
BrainExplorer2 can be installed, and can be started.
The first thing it will ask you is to download up to for atlases of size 30-110
MB. For testing, it is sufficient to download the smallest.
When the atlas is downloaded, and should be loaded, the BrainExplorer2 crashes
(see attached backtrace). The crash can be avoided when starting BrainExplorer2
is prefixed with
WINEDEBUG=warn+heap
This is reproducible and happens when any of the 4 atlases is selected. It
happens also on different wine versions (1.6.2, 1.8-rc3) and also when
WINEARCH="win32" is set.
I'm surprised by this "hack", because I thought WINEDEBUG would only affect the
debugging, and not the memory management itself.
--
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=38433
Bug ID: 38433
Summary: [regression] Exile - Escape from the Pit: some dialog
windows are not drawn
Product: Wine
Version: 1.7.41
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: debuser1(a)mt2014.com
Distribution: ---
Created attachment 51293
--> https://bugs.winehq.org/attachment.cgi?id=51293
Screenshot of bad Exile look in wine-1.7.40
http://www.spiderwebsoftware.com/exile/winexile.htmlhttp://www.spiderwebsoftware.com/ftp/installers/win/EXILINST.EXE
Steps to reproduce:
0. Download the game, it's small, install, run EXILE.EXE
1. File / New Game, select "PreFab" button, press OK to introductions
2. Press "P" to display spells dialog
3. Press "Spell Library" button
4. See almost empty dialog window (screenshot attached)
I did a brief check of different wine builds from PoL:
wine-1.1.40 worked without noticeable issues
wine-1.1.43 changed something, and dialogs are not drawn, rarely
wine-1.5.16 introduced Bug 35977: Exile crashes on startup
wine-1.7.17 the bug fixed, but dialogs are not drawn any more
Summary:
1.1.40...1.1.42 = good
1.1.43...1.5.15 = rare issues with dialogs
1.5.16...1.7.16 = crashes on startup, unusable
1.7.17...1.7.41 = issues with dialogs
I have not tested wine versions before 1.1.40.
--
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=40545
Bug ID: 40545
Summary: Make Wine to automatically recognize desktop DPI
Product: Wine
Version: 1.6.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: es20490446e(a)gmail.com
Distribution: ---
Please make Wine to automatically recognize the desktop DPI and set a good
default for its config.
--
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=33729
Bug #: 33729
Summary: Soldier of Fortune II - Double Helix crashes at
startup
Product: Wine
Version: 1.5.31
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: tiar85(a)luukku.com
Classification: Unclassified
Created attachment 44667
--> http://bugs.winehq.org/attachment.cgi?id=44667
Details for crash (single player).
Soldier of Fortune II - Double Helix crashes at startup. It happens for both,
single player and multiplayer executables. NoCD-patch did not help. Same with
compatibility modes.
In AppDB, one of the users had found a workaround for SoF II multiplayer.
Details:
http://appdb.winehq.org/objectManager.php?sClass=version&iId=1116
I can not get the game work with the guide. With it, on my PC, Wine only tries
to run the multiplayer, but will never reach the main menu.
Closed bugs do not show a similar issue reported before. The game is also
broken with Wine. 1.4.
--
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=38920
Bug ID: 38920
Summary: Aura Kingdom does not start up.
Product: Wine
Version: 1.7.37
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Findanother1X3(a)gmail.com
Created attachment 51851
--> https://bugs.winehq.org/attachment.cgi?id=51851
What I was able to obtain when the application wasn't starting.
I installed a game called Aura Kingdom which is originally on the PC.
Unfortunately, I am not able to start up the game, instead it gives me "The
program _Launcher.exe has encountered a serious problem and needs to be
closed." along with the details. I do not know what I have done wrong. All I
know is that I cannot start up the game.
--
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.