https://bugs.winehq.org/show_bug.cgi?id=45627
Bug ID: 45627
Summary: mdac28 fails to install (SetupDefaultQueueCallbackW
copy error 32
L"C:\\users\\austin\\Temp\\IXP000.TMP\\msdaorar.dll")
Product: Wine-staging
Version: 3.13
Hardware: x86
URL: https://github.com/Winetricks/winetricks/issues/1061
OS: Linux
Status: NEW
Keywords: download, Installer
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: Gentoo
This was reported to winetricks upstream here:
https://github.com/Winetricks/winetricks/issues/1061
I was unable to reproduce it with plain wine. When I ran with
wine-staging-3.13, however, I see it:
austin@austin2:~$ wineserver -k ; rm -rf ~/.wine ; WINE=wine-staging-3.13
WINEARCH=win32 winetricks -q mdac28
Using winetricks 20180603-next - sha256sum:
b65cef4e1f530ecf7cbd067b6849222503fa994818ca154c2f52fdaf7d976a56 with wine-3.13
(Staging) and WINEARCH=win32
Executing w_do_call mdac28
Executing load_mdac28
Using native,builtin override for following DLLs: mtxdm odbc32 odbccp32 oledb32
Executing wine-staging-3.13 regedit /S C:\windows\Temp\_mdac28\override-dll.reg
Setting Windows version to nt40
Executing wine-staging-3.13 regedit /S C:\windows\Temp\_mdac28\set-winver.reg
Executing cd /home/austin/.cache/winetricks/mdac28
Executing wine-staging-3.13 mdac_typ.exe /q /C:setup /qnt
0066:err:richedit:ReadStyleSheet skipping optional destination
0066:err:richedit:ReadStyleSheet skipping optional destination
0066:err:richedit:ReadStyleSheet skipping optional destination
0066:err:richedit:ReadStyleSheet skipping optional destination
0066:err:richedit:ReadStyleSheet skipping optional destination
0066:fixme:setupapi:extract_cabinet_file awful hack: extracting cabinet
"C:\\users\\austin\\Temp\\IXP000.TMP\\msvcrt.CAB"
0066:fixme:setupapi:extract_cabinet_file awful hack: extracting cabinet
"C:\\users\\austin\\Temp\\IXP000.TMP\\mtxfiles.CAB"
0066:fixme:setupapi:extract_cabinet_file awful hack: extracting cabinet
"C:\\users\\austin\\Temp\\IXP000.TMP\\MDACxpak.CAB"
0066:fixme:setupapi:SetupDefaultQueueCallbackW notification 262144 params
32eebc,0
0066:fixme:setupapi:extract_cabinet_file awful hack: extracting cabinet
"C:\\users\\austin\\Temp\\IXP000.TMP\\MDACxpak.CAB"
0066:fixme:setupapi:extract_cabinet_file awful hack: extracting cabinet
"C:\\users\\austin\\Temp\\IXP000.TMP\\MDACxpak.CAB"
0066:err:setupapi:SetupDefaultQueueCallbackW copy error 32
L"C:\\users\\austin\\Temp\\IXP000.TMP\\msdaorar.dll" -> L"C:\\Program
Files\\Common Files\\System\\OLE DB\\msdaorar.dll"
------------------------------------------------------
Note: command wine-staging-3.13 mdac_typ.exe /q /C:setup /qnt returned status
5. Aborting.
--
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=28810
Bug #: 28810
Summary: d3dx9_36/tests/mesh.ok: D3DXLoadMeshTest fails under
valgrind
Product: Wine
Version: 1.3.30
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3dx9
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
CC: wine-bugs(a)winehq.org
Classification: Unclassified
Under Valgrind, "make mesh.ok" fails with
mesh.c:2333: Test failed: Vertex[7]: Expected diffuse b3ffffff, got b2ffffff
mesh.c:2333: Test failed: Vertex[11]: Expected diffuse b3ffffff, got b2ffffff
mesh.c:2333: Test failed: Vertex[18]: Expected diffuse b3ffffff, got b2ffffff
mesh.c:2406: Test failed: Vertex[7]: Expected diffuse b3ffffff, got b2ffffff
mesh.c:2406: Test failed: Vertex[11]: Expected diffuse b3ffffff, got b2ffffff
mesh.c:2406: Test failed: Vertex[18]: Expected diffuse b3ffffff, got b2ffffff
This is on my i5 laptop, nvidia GeForce GTS 360M, NVIDIA 280.13.
The test passes without valgrind.
--
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=46235
Bug ID: 46235
Summary: Opening ADODB.Connection results in: Method '~' of
object '~' failed
Product: Wine
Version: 3.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bugs(a)seeitmyway.org
Distribution: ---
Created attachment 62931
--> https://bugs.winehq.org/attachment.cgi?id=62931
VB6 example program
Hello
I've been battling with this for four days now and found no solution, yet it
worked a year ago.
Opening an ADODB.Connection in wine fails with this message:
Method '~' of object '~' failed
Yet it works fine in Windows (XP).
In essence, the program does only this:
Dim cn As ADODB.Connection
Set cn = New ADODB.Connection
cnStr = "DRIVER={MySQL ODBC 5.3 UNICODE Driver};" _
& "SERVER=localhost;" _
& "DATABASE=db;" _
& "UID=user;" _
& "PWD=password;" _
& "PORT=3306;" _
& "POOLING=false;" _
& "OPTION=3;"
cn.ConnectionString = cnStr
Call cn.Open ' <--- fail
Quick steps to reproduce:
1. Download:
-
https://downloads.mysql.com/archives/get/file/mysql-connector-odbc-5.3.6-wi…
- Attached sample VB6 program I compiled.
2. Run:
WINEARCH="win32" WINEPREFIX="$HOME/wine-ado" ./winetricks vb6run mdac28
WINEARCH="win32" WINEPREFIX="$HOME/wine-ado" wine msiexec /i
mysql-connector-odbc-5.3.6-win32.msi
WINEARCH="win32" WINEPREFIX="$HOME/wine-mca" wine adotest_early_53.exe
It will show a messagebox with the ODBC connection string and the error
description. I tried downloading the full binary I used in wine a year ago and
it too fails. This attached program is just the bare-bones needed to show the
problem, to remove all unknowns.
I tried wine-2.9, wine-3.0 and wine-3.18 staging, all failed. Tried with
POOLING=true, POOLING=false, and without the POOLING key at all. I tried all
the internet advice I could find to no avail.
Strangely enough, when I set the ODBC connection driver to something bogus,
like "carrots", it fails with the exact same reason. As if it doesn't see the
MySQL ODBC connector at all.
For more info and the source code, see:
http://www.vbforums.com/showthread.php?868713-Open-ADODB-connection-in-Linu…
--
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=40971
Bug ID: 40971
Summary: Zombie Army Trilogy crashes before the menu
Product: Wine
Version: 1.9.14
Hardware: x86
URL: http://store.steampowered.com/app/301640/
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
Distribution: ---
Created attachment 55121
--> https://bugs.winehq.org/attachment.cgi?id=55121
backtrace
This time I tried the game with Nvidia binary drivers 367.35.
The launcher (html-based) mostly works, I can modify settings and start the
game.
The game begins to load, displays the developer logo and the loading screen,
but crashes before the main menu should appear.
In the prefix I have corefonts, Xaudio2 and MSVC++2010 installed,
gameoverlayrenderer.dll is disabled.
wine-1.9.14-112-gfec0b69
Fedora 24
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 367.35
OpenGL core profile shading language version string: 4.50 NVIDIA
--
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=42582
Bug ID: 42582
Summary: Murdered: Soul Suspect has messed up rendering
Product: Wine
Version: 2.2
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 57492
--> https://bugs.winehq.org/attachment.cgi?id=57492
log
Most parts are black rendered. Also slow performance ~10-15 FPS.
err:d3d:wined3d_debug_callback 0x1ba07990: "GL_INVALID_OPERATION error
generated. <program> has not been linked, or is not a program object.".
err:d3d:wined3d_debug_callback 0x1ba07990: "GL_INVALID_OPERATION error
generated. <program> object is not successfully linked, or is not a program
object.".
err:d3d:wined3d_debug_callback 0x1ba07990: "GL_INVALID_OPERATION error
generated. No active compute shader.".
wine-2.2-276-ge6f8f13
--
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=43889
Bug ID: 43889
Summary: Gradient is inverted when using gdiplus
Product: Wine
Version: 2.19
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
Distribution: ---
Created attachment 59505
--> https://bugs.winehq.org/attachment.cgi?id=59505
Image using normal GDI
When viewing a checklist element in Enterprise Architect, the gradient is
inverted when using the Enhanced-2 renderer (GDIPlus)
--
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=40031
Bug ID: 40031
Summary: Singularity: In Steam the game is still running after
quit
Product: Wine
Version: 1.9.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: christoph.korn(a)posteo.de
Distribution: ---
After exiting singularity, steam still lists it as "running".
This makes steam unable to exit because it waits for singularity to quit.
$ /opt/wine-devel/bin/wine --version
wine-1.9.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=46093
Bug ID: 46093
Summary: GRLevel3 2.52 fails to start, hangs indefinitely
Product: Wine
Version: 3.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: mazecraze96(a)gmail.com
Distribution: Ubuntu
Created attachment 62720
--> https://bugs.winehq.org/attachment.cgi?id=62720
terminal log
GRLevel3 2.52 simply fails to start. Attached is a log of the terminal output
after trying to start it. The last message is repeated infinitely, every 60
seconds.
The activation window that pops up when the trial is over or almost over works
fine.
Bug occurs in both 32 and 64 bit Wine prefixes.
At least Wine stable to current Wine staging is affected. Probably earlier
versions too. It worked before with one of the 2.x versions to my memory,
granted it was an earlier version of GRLevel3 too.
http://www.grlevelx.com/downloads/grlevel3_2_setup.exe
I can provide more information if needed.
--
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=44015
Bug ID: 44015
Summary: Steam - fails to load UI since Wine 2.20 (due to
dwrite commit)
Product: Wine
Version: 2.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dwrite
Assignee: wine-bugs(a)winehq.org
Reporter: tgheretford(a)vivaldi.net
Distribution: ---
Created attachment 59677
--> https://bugs.winehq.org/attachment.cgi?id=59677
Steam terminal output
Since upgrading to Wine 2.20 on Arch Linux, the Steam user interface fails to
load on every single attempt. The bug is still present when testing using the
latest git version and a clean Wine directory.
Steam loads fine (with the usual bugs and caveats as per the appDB
instructions) in Wine 2.19 and earlier.
I have performed regression testing and it identified the first bad commit as
aa9fc635140cda1caccb0bc617f780ef8f842478 (dwrite: Reuse streams when
initializing font data and creating faces).
--
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.