http://bugs.winehq.org/show_bug.cgi?id=31976
Bug #: 31976
Summary: sdl-mir2 crash at start with builtin wininet
Product: Wine
Version: 1.5.15
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wininet
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fracting(a)gmail.com
Classification: Unclassified
sdl-mir2 is a downloader for the Chuanqi game of SDO.
http://ou.sdo.com/download/gamesv2/sdl-mir2.exe
$ sha1sum sdl-mir2.exe
9e6c411aaf7ac268396d26a6be23882a1111506d sdl-mir2.exe
sdl-mir2.exe crash at start, with below backtrace:
Backtrace:
=>0 0x004057ba in sdl-mir2 (+0x57ba) (0x0077a9a8)
1 0x0040b1be in sdl-mir2 (+0xb1bd) (0x0077e948)
2 0x0040ae87 in sdl-mir2 (+0xae86) (0x0077e978)
3 0x00423f42 in sdl-mir2 (+0x23f41) (0x0077e9b4)
4 0x004240cf in sdl-mir2 (+0x240ce) (0x0077ea08)
5 0x0040613d in sdl-mir2 (+0x613c) (0x0077ea1c)
6 0x00406000 in sdl-mir2 (+0x5fff) (0x0077ea28)
7 0x7bc811a0 call_thread_func_wrapper+0xb() in ntdll (0x0077ea38)
8 0x7bc811e9 call_thread_func+0x3e(entry=0x405ff4, arg=0x4fe8e0,
frame=0x77eb38) [/home/fracting/wine-git/dlls/ntdll/signal_i386.c:2522] in
ntdll (0x0077eb18)
9 0x7bc8117e call_thread_entry_point+0x11() in ntdll (0x0077eb38)
+seh,+tid,+relay log shows:
0035:Call wininet.InternetReadFile(00000003,0077a9e4,00003f38,0077e92c)
ret=0040b18f
0035:Call KERNEL32.WriteFile(0000005c,0077a9e4,00003f38,0077a848,00000000)
ret=7e4729bc
0035:Ret KERNEL32.WriteFile() retval=00000001 ret=7e4729bc
0035:Ret wininet.InternetReadFile() retval=00000001 ret=0040b18f
0035:trace:seh:raise_exception code=c0000094 flags=0 addr=0x4057ba ip=004057ba
tid=0035
0035:trace:seh:raise_exception eax=09a57b80 ebx=00000000 ecx=00000000
edx=00000000 esi=7ffd0000 edi=003d0f00
0035:trace:seh:raise_exception ebp=0077a9a8 esp=0077a94c cs=0073 ds=007b
es=007b fs=0033 gs=003b flags=00010202
`winetricks -q wininet` works around
--
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=3864
Detlef Riekenberg <wine.dev(a)web.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wine.dev(a)web.de
--- Comment #26 from Detlef Riekenberg <wine.dev(a)web.de> ---
I send first patches for this bug, but it is not fixed yet.
The message in the Popup-Window should only contain:
"Installation successful."
This part "Procedure not found." is a different issue 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=41939
Bug ID: 41939
Summary: MS office pro 2007 data connections not possible
Product: Wine
Version: 1.9.23
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: juntjoo(a)gmail.com
Distribution: ---
Doesn't display current data connections(in data connection window) nor will it
allow you to create one. On the first step of selecting the file with which to
make the connection, when you locate then select the workbook it's file name
does not even appear in the "filename" box, so you can't select it.
--
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=41266
Bug ID: 41266
Summary: WKO4 crashes with thread errors if device is attached
on startup
Product: Wine
Version: 1.9.17
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jjmckenzie51(a)gmail.com
If a device is attached via USB (Garmin 510 in my case), the program crashes
with unable to create thread error.
--
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=3637
winetest(a)luukku.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |winetest(a)luukku.com
--- Comment #19 from winetest(a)luukku.com ---
Still valid wine 1.9.24 and staging 1.9.23.
--
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=41933
Bug ID: 41933
Summary: give better output for wine xcopy without arguments
Product: Wine
Version: 1.9.24
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winetest(a)luukku.com
Distribution: ---
wine xcopy
gives output of
fixme:xcopy:XCOPY_ProcessSourceParm Unexpected failure expanding source path
(203)
http://source.winehq.org/git/wine.git/blob/6d89f58ec2935b5e8bebef34e7fbe892…
Maybe wine xcopy without any flags should print the xcopy help that happens
when you use command wine xcopy /?
--
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=7961
Lauri Kenttä <lauri.kentta(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lauri.kentta(a)gmail.com
--- Comment #18 from Lauri Kenttä <lauri.kentta(a)gmail.com> ---
Created attachment 56304
--> https://bugs.winehq.org/attachment.cgi?id=56304
Tests for FindFirstFile
I hacked the FindFirstFile + FindNextFile from Wine into a stand-alone program
(attached) to see where the bug lies. This test shows that the Wine functions
work exactly the same on Wine and Windows, which means that the problem is in
the implementation of FindFirstFile (or FindNextFile) and not in any of the
other places.
My test output on Windows:
RtlGetFullPathName_U: '*.' -> 'Z:\7961\*'
RtlDosPathNameToNtPathName_U: '*.' -> '\??\Z:\7961\*'
RtlGetFullPathName_U: '*. ' -> 'Z:\7961\*'
RtlDosPathNameToNtPathName_U: '*. ' -> '\??\Z:\7961\*'
'*', wine copy: '.', '..', 'dot-end', '.dot-start', 'no-ext', 'full.ext',
'*', real deal: '.', '..', 'dot-end', '.dot-start', 'no-ext', 'full.ext',
'*.*', wine copy: '.', '..', 'dot-end', '.dot-start', 'no-ext', 'full.ext',
'*.*', real deal: '.', '..', 'dot-end', '.dot-start', 'no-ext', 'full.ext',
'.*', wine copy: '.', '..', '.dot-start',
'.*', real deal: '.', '..', '.dot-start',
'*.', wine copy: '.', '..', 'dot-end', '.dot-start', 'no-ext', 'full.ext',
'*.', real deal: '.', '..', 'dot-end', 'no-ext',
'*. ', wine copy: '.', '..', 'dot-end', '.dot-start', 'no-ext', 'full.ext',
'*. ', real deal: '.', '..', 'dot-end', '.dot-start', 'no-ext', 'full.ext',
On Wine, as you can guess, the "real deal" lines are identical to the "wine
copy" lines, so the only difference is with '*.', as this bug report states.
What's interesting is that adding a space after the dot makes Windows strip the
dot as well.
Apparently there should be some magic in FindFirstFile to detect and handle
paths ending with a dot.
--
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=29833
Bug #: 29833
Summary: XMLSpy 2012: Crashes when saving XML and XSD files.
Product: Wine
Version: 1.4-rc2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ashrader330(a)gmail.com
Classification: Unclassified
Created attachment 38746
--> http://bugs.winehq.org/attachment.cgi?id=38746
Crash backtrace.
XMLSpy 2012 crashes on me periodically when saving XML and XSD files. It does
not happen every time but frequently enough that it is more than an annoyance.
I have downloaded the debug release of 1.4-rc2 from the OpenSUSE 12.1
repository and attached the backtrace.
--
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=41923
Bug ID: 41923
Summary: Pool of Radiance: Ruins of Myth Drannor requires
DirectDraw Emulation Mode
Product: Wine
Version: 1.8.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Robert.Zenz(a)bonsaimind.org
Distribution: ---
Pool of Radiance: Ruins of Myth Drannor seems to be built/coded against a buggy
or old version of DirectDraw. On Windows XP+ it requires a so called
"DirectDraw Emulation Mode" to function properly. Without it characters will
become transparent when standing still.
There is a guide available which explains on how to enable it using the
Application Compatibility Toolkit from Microsoft:
http://www.sorcerers.net/community/index.php?threads/for-those-with-invisib…
Then there is a DirectDraw wrapper which enables it, too:
http://bitpatch.com/ddwrapper.html
However, I failed to get both to work under 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=4209
Lauri Kenttä <lauri.kentta(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lauri.kentta(a)gmail.com
--- Comment #12 from Lauri Kenttä <lauri.kentta(a)gmail.com> ---
Created attachment 56302
--> https://bugs.winehq.org/attachment.cgi?id=56302
Minimal test program
Since there's source code available, I isolated the problem and created a
minimal crashing example.
Steps to reproduce:
1) Compile hook.c to hook.exe (with MinGW or similar).
2) Start hook.exe in shell; optionally try also hook.exe {2|3|4}
3) Start Notepad.
4) Type a key in Notepad. It crashes right away.
5) Close hook.exe by inputting enter.
My sample program includes several versions of the hook callback. Looks like
the crash comes if the callback accesses memory at all, so practically anything
else than a simple return statement will cause a crash.
Someone with an undestanding about the Wine memory layout and/or process
boundaries should take a look at this.
--
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.