https://bugs.winehq.org/show_bug.cgi?id=44228
Bug ID: 44228
Summary: prince of persia 3D crashes at play (installes ok)
Product: Wine
Version: 3.0-rc3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cedric.dewijs(a)telfort.nl
Distribution: ---
Created attachment 60024
--> https://bugs.winehq.org/attachment.cgi?id=60024
backtrace created by wine itself
After installing, Prince of persia 3D crashes with an unhandled exception
uname -a
Linux archlinux 4.14.8-1-ARCH #1 SMP PREEMPT Wed Dec 20 21:27:44 UTC
2017 x86_64 GNU/Linux
--
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=44249
Bug ID: 44249
Summary: Can't play Diablo 2 (Battle.net) when Virtualization
in BIOS is disabled.
Product: Wine
Version: 2.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: asriroc(a)gmail.com
Distribution: ---
1. I have "Virtualization" as "Enable" in my BIOS (Compaq Presario F763NR
Notebook with the most recent BIOS version).
2. I installed a fresh Fedora 27 Cinnamon Spin with Linux
4.14.8-300.fc27.x86_64 kernel.
3. I installed NVIDIA 304.137
4. I installed Diablo 2 using WINE 2.22
At this point, I would be able to play Diablo 2 using Battle.net
5. I rebooted the notebook, and set "Disable" on the "Virtualization" in my
BIOS.
6. I tried to play Diablo 2, using WINE 2.22, but I won't be able to use
Battle.net
Now, if I rebooted and enabled my virtualization in my BIOS, Diablo 2 would
work again.
Thank you so much.
--
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=42223
Bug ID: 42223
Summary: I cant install AB Bulkmailer .. Please HELP me ...
Product: Wine
Version: 2.0-rc4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bluebird456(a)vfemail.net
Distribution: ---
Created attachment 56863
--> https://bugs.winehq.org/attachment.cgi?id=56863
AB BulkMailer install BUG
I want to install AB BulkMailer .
Which is a Windows app .
I tried to install the app , But error appears ...
I attached the detail in attached TEXT FILE ...
Please CHECK and PLEASE HELP ME ..
Please Fix the error BUG as soon as possible ...
I JUST want to use the app ...
--
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=39787
Bug ID: 39787
Summary: Lilos Lesewelt 2 crashes
Product: Wine
Version: 1.8-rc3
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 53081
--> https://bugs.winehq.org/attachment.cgi?id=53081
backtrack file, run with WINEDEBUG=+all
"Lilos Lesewelt 2" can be installed, but when trying to start it, it crashes.
The full debug log with
WINEDEBUG=+all
is available from (11MB !)
http://pub.ist.ac.at/~schloegl/wine-reports/lilo2.debug.all.log.gz
A short version for
WINEDEBUG=+cdrom
in
http://pub.ist.ac.at/~schloegl/wine-reports/lilo2.debug.cdrom.log
--
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=35883
Bug ID: 35883
Summary: Horizon crashes with page fault
Product: Wine
Version: 1.7.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jmelton116(a)gmail.com
Created attachment 47912
--> http://bugs.winehq.org/attachment.cgi?id=47912
Backtrace generated by crash
Horizon seems to crash at random times with a page fault. There seems to be no
sort of consistency between what is occuring in game and when these occur, but
I could be wrong. These were encountered on the latest git version. Page
fault's backtrace is attached.
--
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=44146
Bug ID: 44146
Summary: Crysis 2: DX11 is a slideshow
Product: Wine
Version: 3.0-rc1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: christian.frank(a)gmx.de
Distribution: ---
Hi,
trying to play Crysis 2 with DX11 is actually impossible, it is a complete
slideshow. Switching from DX9 to DX11 the FPS drop from ~ 40 to ~ 8 fps.
Tons of fixmes are spit out:
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[31]" might be used before being initialized
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 4.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 5.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 6.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 7.
0048:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader
#24:
0048:fixme:d3d_shader:print_glsl_info_log Vertex info
0048:fixme:d3d_shader:print_glsl_info_log -----------
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[1]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[2]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[3]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[4]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[5]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[6]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[7]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[8]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[9]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[10]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[11]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[12]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[13]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[14]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[15]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[16]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[17]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[18]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[19]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[20]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[21]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[22]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[23]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[24]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[25]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[26]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[27]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[28]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[29]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[30]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[31]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log
0048:fixme:d3d_shader:print_glsl_info_log Fragment info
0048:fixme:d3d_shader:print_glsl_info_log -------------
0048:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "R0.yzw"
might be used before being initialized
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 4.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 5.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 6.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 7.
0048:fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier
0x800000c2.
0048:fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier
0x00155543.
0048:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader
#27:
0048:fixme:d3d_shader:print_glsl_info_log Vertex info
0048:fixme:d3d_shader:print_glsl_info_log -----------
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[1].zw" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[2]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[3]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[4]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[5]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[6]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[7]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[8]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[9]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[10]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[11]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[12]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[13]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[14]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[15]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[16]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[17]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[18]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[19]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[20]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[21]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[22]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[23]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[24]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[25]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[26]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[27]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[28]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[29]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[30]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[31]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log
0048:fixme:d3d_shader:print_glsl_info_log Fragment info
0048:fixme:d3d_shader:print_glsl_info_log -------------
0048:fixme:d3d_shader:print_glsl_info_log 0(26) : warning C7050: "R0.yzw"
might be used before being initialized
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 4.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 5.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 6.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 7.
My GPU: Nvidia GTX 970 (384.98)
Memory: 16GB
CPU: Core i5 3570k
Opensuse Tumbleweed, latest Snapshot
Many thanks !
Christian
--
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=22755
Summary: Regression : win16 installer program of "de rouck"
freeze
Product: Wine
Version: 0.9.31.
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: vincent.hardy.be(a)gmail.com
Created an attachment (id=28058)
--> (http://bugs.winehq.org/attachment.cgi?id=28058)
wine-1.1.31 screenshot
It works with wine-1.1.30.
With wine-1.1.31, see screenshot
Regression test says :
3b1186de5aeabd261e70dab8b78a730030075ca1 is the first bad commit
commit 3b1186de5aeabd261e70dab8b78a730030075ca1
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Wed Oct 7 17:14:10 2009 +0200
kernel32: Move the 16-bit string functions to kernel16.c.
:040000 040000 3412021b8c21c250ee3ccc60ce31c3f3f9365c50
3c5be0f4e2330e28e86e4b839447d40d88bf42f3 M dlls
--
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=47189
Bug ID: 47189
Summary: Vortex doesn't start
Product: Wine
Version: 4.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: logicalman101(a)gmail.com
Distribution: ---
Vortex doesn't run past installation phase no matter what version of dotnet I
have installed.
--
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=44822
Bug ID: 44822
Summary: Warframe can't update / game can't run
Product: Wine
Version: 3.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vblanton(a)gmail.com
Distribution: ---
Warframe can't get past updating process, hence game won't start. This is a
fresh install.
Installs fine via steam. Starts with workarounds:
winetricks: d3dx9 wininet winhttp xact hosts corefonts fontfix vcrun2015
Updating fails with the message "Update Failed! The content servers are
temporarily"
No workarounds have fixed this so far. Attempts to install other Visual C++
packages haven't helped. Various DLL overrides haven't helped.
--
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=33131
Bug #: 33131
Summary: taskkill doesn't support /fi (filtering) option
Product: Wine
Version: 1.5.25
Platform: x86-64
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Blocks: 33130
Classification: Unclassified
Noticed while looking at bug 33130
0067:Call KERNEL32.CreateProcessW(00000000,008fcb00
L"C:\\windows\\system32\\taskkill.exe /F /Fi \"MODULES eq
AutoupdatePlugin.cpl\"
/T",00000000,00000000,00000000,00000400,00000000,00000000,008fb1fc,008fb240)
ret=7e4d517f
--
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.
http://bugs.winehq.org/show_bug.cgi?id=24169
Summary: QuarkXPress version 8.x hangs on start (missing double
quoting of browser path in
HKCR\htmlfile\shell\open\command)
Product: Wine
Version: 1.3.1
Platform: x86
URL: http://downloads.quark.com/Details.aspx?fid=163&&mid=2
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Hello,
someone in appdb reported QuarkXPress version 8.x (2010 version) hangs on
start.
Downloaded a 60-day trial ... it does indeed - due to a Wine shortcoming and an
application bug. ;-)
Basically the app retrieves default browser setting from registry and does some
parsing to extract browser (unquoting and splitting '\' '/' path delimiter).
Their parsing is broken in a way that it can't cope with missing double quotes
around browser path leading to endless looping.
HKEY_CLASSES_ROOT\htmlfile\shell\open\command ->
C:\windows\system32\winebrowser.exe -nohome
With the browser path in double quotes, QuarkXPress 8 starts fine.
"C:\windows\system32\winebrowser.exe" -nohome
The quoting is most likely present in Windows as the app would loop there too
without.
Regards
--
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=47584
Bug ID: 47584
Summary: Ryzen APU Device ID
Product: Wine
Version: 4.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: vasthusya(a)gmail.com
Distribution: ---
Created attachment 64991
--> https://bugs.winehq.org/attachment.cgi?id=64991
Add Ryzen APU device IDs.
The GPU description table is missing Ryzen APU device IDs.
0x15dd : Raven Ridge
0x15d8 : Picasso
--
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=31033
Bug #: 31033
Summary: Multiple apps need IWbemServices::GetObject to
retrieve WMI class instances
Product: Wine
Version: 1.5.7
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wmi&wbemprox
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Classification: Unclassified
Hello,
continuation of bug 20651
Multiple apps still fail to query for WMI classes/properties because
IWbemServices::GetObject method is not implemented (they use a different
method).
One app is bug 28682 (Ragnarok downloader)
Example .NET code:
--- snip ---
ManagementClass class2 = new ManagementClass("Win32_Processor");
foreach (ManagementObject obj2 in class2.GetInstances())
{
if (str == string.Empty)
{
str = obj2.Properties["ProcessorId"].Value.ToString();
}
}
--- snip ---
MSDN:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa392109%28v=vs.85%…
Regards
--
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.
http://bugs.winehq.org/show_bug.cgi?id=24225
Summary: provide "taskkill" command line tool to aid installers
(Impulse installer and more)
Product: Wine
Version: 1.3.1
Platform: x86
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Hello,
various installers use "taskkill" command line tool to terminate running
processes, preventing possible sharing/update problems with components to be
installed.
--- snip ---
wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe"
--- snip ---
Trace logs for "Impulse" installer as example:
--- snip ---
0034:Call KERNEL32.CreateProcessA(00000000,0092fab0
"\"C:\\windows\\system32\\TASKKILL.exe\" /f /im
impulse.exe",00000000,00000000,00000000,00000010,00000000,00000000,0108e980,0108e970)
ret=004e5657
...
wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe"
0034:Ret KERNEL32.CreateProcessA() retval=00000000 ret=004e5657
...
0037:Call KERNEL32.CreateProcessA(00000000,0092fab0
"\"C:\\windows\\system32\\TASKKILL.exe\" /f /im
impulsedock.exe",00000000,00000000,00000000,00000010,00000000,00000000,0118e980,0118e970)
ret=004e5657
...
wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe"
0037:Ret KERNEL32.CreateProcessA() retval=00000000 ret=004e5657
...
003a:Call KERNEL32.CreateProcessA(00000000,0092fab0
"\"C:\\windows\\system32\\TASKKILL.exe\" /f /im
impulsemini.exe",00000000,00000000,00000000,00000010,00000000,00000000,00e5e980,00e5e970)
ret=004e5657
...
wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe"
003a:Ret KERNEL32.CreateProcessA() retval=00000000 ret=004e5657
...
003d:Call KERNEL32.CreateProcessA(00000000,0092fab0
"\"C:\\windows\\system32\\TASKKILL.exe\" /f /im
impulsenow.exe",00000000,00000000,00000000,00000010,00000000,00000000,0108e980,0108e970)
ret=004e5657
...
wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe"
003d:Ret KERNEL32.CreateProcessA() retval=00000000 ret=004e5657
...
--- snip ---
Wine should provide such a tool to aid installers.
Reference: http://technet.microsoft.com/en-us/library/bb491009.aspx
Regards
--
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.
http://bugs.winehq.org/show_bug.cgi?id=32758
Bug #: 32758
Summary: TurboTax 2012 fails to run update service
Product: Wine
Version: 1.5.22
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: dotnet, download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
CC: focht(a)gmx.net
Depends on: 27991
Classification: Unclassified
Using wine-1.5.22, you'll need to workaround bug 27991, and install dotnet40
with winetricks. The installer will then work fine.
Try to start it, and you'll get 3 errors on start about the update service not
working. The relevant turbotax help links:
http://turbotax.intuit.com/support/iq/Update-Product/Error-5639--Can-t-Conf…http://turbotax.intuit.com/support/iq/Connectivity-Errors/Error-5640--Can-t…
stdout shows:
Operation is not supported on this platform.
3 times, which is probably related.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=16905
Summary: CommitMonitor: Application could not connect to
repository
Product: Wine
Version: 1.1.12
Platform: PC-x86-64
URL: http://code.google.com/p/commitmonitor/downloads/list
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: alex(a)stanev.org
When trying to connect to repository to check for activity, the tool gives
following error message:
"An error occured the last time CommitMonitor tried to access the url:
http://example.com/svn/example
Couldn't perform atomic initialization"
The application uses libsvn, the error is likely to come from here:
http://svn.collab.net/repos/svn/trunk/subversion/libsvn_subr/atomic.c
--
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.
http://bugs.winehq.org/show_bug.cgi?id=25749
Summary: TortoiseSVN fails after successful commit
Product: Wine
Version: 1.3.11
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andrey(a)niakhaichyk.org
Created an attachment (id=32800)
--> (http://bugs.winehq.org/attachment.cgi?id=32800)
TortoiseSVN log for commit operation
TortoiseSVN fails after successful commit for wine 1.3.*. In wine 1.2.* all
works perfectly.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=22992
Summary: SVN-Monitor needs gdiplus.dll.GdipGetRenderingOrigin
Product: Wine
Version: 1.2-rc2
Platform: x86
URL: http://www.svnmonitor.com/
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdiplus
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Hello,
SVN Monitor doesn't run well with builtin gdiplus.
Although it doesn't crash, a nasty error dialog is displayed each time the
exception is thrown (can be dismissed).
--- snip ---
...
fixme:gdiplus:GdipDrawImagePointsRect Image wrap mode not implemented
fixme:gdiplus:GdipGetRegionScansCount not implemented
...
fixme:shell:URL_ParseUrl failed to parse L"SVNMonitor.resources"
wine: Call from 0x7b836c0f to unimplemented function
gdiplus.dll.GdipGetRenderingOrigin, aborting
--- snip ---
Install recipe (see also appdb entry):
--- snip ---
$ sh winetricks -q dotnet20
TortoiseSVN is also needed (http://tortoisesvn.net/downloads/) Install the MSI
package:
$ wine start TortoiseSVN-xxx-win32-svn-xxx.msi
Now run the SVN Monitor application installer.
$ wine SVNMonitor-xxx-Setup.exe
--- snip ---
Regards
--
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=45896
Bug ID: 45896
Summary: Dungeon Keeper 2 - Patch'ed v1.8 - doesn't start
Product: Wine
Version: 3.0.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: thomas000bauer(a)gmail.com
Distribution: ---
Hi,
i have tried to launch Dungeon Keeper 2 with the "unofficial" Patch to Version
v1.8 so the necessity of a noCD Crack is obsolete.
When i try to execute the "wine" command it takes about 4-5seconds with/and
without attached debug-log export to get me a new command line. But nothing
else happens, no Output in the Terminal no nothing.
I do as followed to launch Dungeon Keeper 2:
[code]
export WINEPREFIX="/media/daten350/games-software/wine/dungeon.keeper.2"
export
WINEDEBUG=+timestamp,+tid,+loaddll,+winediag,+synchronous,+seh,+x11drv,+xrandr
cd /media/daten350/games-software/wine/dungeon.keeper.2/drive_c/Program\ Files\
\(x86\)/Bullfrog/Dungeon\ Keeper\ 2/
wine Dkii.exe &>~/wine-vanilla-3.0.2_loaddl_wgl_log.txt
[/code]
here the Log is on Git
[url]https://gist.github.com/Phenicien/16b7fb1230df0e1becc0845351e80cdb[/url]
as well as i have attached it as a .zip file.
I already created a Form Thread
[url]https://forum.winehq.org/viewtopic.php?f=2&t=31165&sid=b68c344b875b8472…]
I'm grateful for every help or solution. Thanks
--
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=27269
Summary: Bitcoin display ugly
Product: Wine
Version: 1.3.20
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
Created an attachment (id=34876)
--> (http://bugs.winehq.org/attachment.cgi?id=34876)
Screenshot : bitcoin
1. download bitcoin
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.21/bitcoi…
$ sha1sum bitcoin-0.3.21-win32-setup.exe
3f94d6a8b08c455a7886561089270247eaada7b4 bitcoin-0.3.21-win32-setup.exe
2. install with wine
3. start bitcoin
$ wine bitcoin.exe
fixme:msvcrt:_setmbcp trail bytes data not available for DBCS codepage 0 -
assuming all bytes
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub
fixme:system:SetProcessDPIAware stub!
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub
some part of bitcoin became transparent, see screenshot for details
--
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=40733
Bug ID: 40733
Summary: page fault on read access to 0x00000004 in 32-bit code
(0x007091ad).
Product: Wine
Version: 1.6.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: martin.suc(a)googlemail.com
Distribution: ---
Created attachment 54639
--> https://bugs.winehq.org/attachment.cgi?id=54639
backtrace of the inkscape
Crash of the inkscape application:
Unhandled exception: page fault on read access to 0x00000004 in 32-bit code
(0x007091ad).
System information:
Wine build: wine-1.6.2
Platform: i386 (WOW64)
Host system: Linux
Host version: 4.4.0-23-generic
--
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=23782
Summary: Spaceforce Rogue Universe crashes in game videos
(iccvid.dll)
Product: Wine
Version: 1.2
Platform: x86
URL: http://www.gamershell.com/download_19328.shtml
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
Created an attachment (id=29821)
--> (http://bugs.winehq.org/attachment.cgi?id=29821)
traces log using only built-in dlls
Spaceforce: RU always crashes when trying to play the game videos. Both the
demo and the patched retail version is affected.
How to reproduce the issue in the demo:
1. Install the demo then launch it from the game's /System directory, either by
Start.exe (the launcher), or directly the game by SpaceForce.exe. Wine will
crash when trying to play the intro video/company logos.
The crash is always reproducible, when using Wine's built-in dlls.
output of the 'file' command on one of the game's video files:
Intro001.mff: RIFF (little-endian) data, AVI, 640 x 480, 25.00 fps, video:
uncompressed Cinepak, audio: uncompressed PCM (stereo, 44100 Hz)
If I replace the built-in iccvid.dll with the free version of the cinepak codec
(available: http://www.probo.com/cinepak.htm) the issue changes into: Wine
doesn't crash anymore, but plays the videos in a strange way: almost the whole
screen is black, only a small chunk of the video can be seen at the left side
of the screen. No music during the videos and in the whole game, though.
Fedora 13
Nvidia 7600 series card / driver 195.36.31
The attached log shows traces, using
winedebug=+ole,+msvideo,+iccvid,+avifile,+amstream,+quartz (all dlls are the
built-in ones)
--
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=46841
Bug ID: 46841
Summary: JASC Paint Shop Pro 8 Crash
Product: Wine
Version: 4.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: robcashwalker(a)gmail.com
Distribution: ---
Created attachment 63879
--> https://bugs.winehq.org/attachment.cgi?id=63879
back trace of fault for Paint Shop Pro 8
Used to work great with earlier version of Wine on Linux Mint 17. I don't
recall which version of Wine, but I remember installing it from the ubuntu
repository, not from WineHQ.
Never really gets into the program. Crashes after splash screen, but has built
the main window. Guessing right about the time it would destroy the splash
screen.
Happens in both stable release and development.
Had the same issue with PSP v9, gave up, and then I just came across the
install media for v8 and decided to try it, as I had been using v8 previously.
--
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.