http://bugs.winehq.org/show_bug.cgi?id=28485
Summary: Pegasus Mail version 4.62 crashes on startup Product: Wine Version: 1.3.28 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: turbolad995@hotmail.co.uk
Created attachment 36535 --> http://bugs.winehq.org/attachment.cgi?id=36535 Error when starting Pegasus Mail 4.62. This was created the second time I tried opening Pegasus Mail with Wine.
When you install Pegasus Mail for the first time and complete the Internet Setup wizard, Pegasus Mail then crashes. It does this every time you try running Pegasus Mail version 4.26 with Wine.
http://bugs.winehq.org/show_bug.cgi?id=28485
--- Comment #1 from David turbolad995@hotmail.co.uk 2011-09-24 16:45:41 CDT --- Created attachment 36536 --> http://bugs.winehq.org/attachment.cgi?id=36536 More lines of information when I managed to kill the process.
This is the output I managed to get when I killed WINPM-32.EXE - using the "System Monitor" in Ubuntu - after Pegasus Mail crashed in Wine.
I'm not an expert at creating bug reports for Wine, sorry. :(
http://bugs.winehq.org/show_bug.cgi?id=28485
David turbolad995@hotmail.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://www.pmail.com/downlo | |ads_s3_t.htm
http://bugs.winehq.org/show_bug.cgi?id=28485
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Severity|major |normal
http://bugs.winehq.org/show_bug.cgi?id=28485
--- Comment #2 from David turbolad995@hotmail.co.uk 2011-10-01 15:11:51 CDT --- This problem does not happen in version 4.52 of Pegasus Mail in Wine.
http://bugs.winehq.org/show_bug.cgi?id=28485
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com
--- Comment #3 from Bruno Jesus 00cpxxx@gmail.com 2011-10-01 15:43:01 CDT --- Please, try installing the wine debugging symbols in your distribution and then run the program again. Follow the guidelines from http://wiki.winehq.org/FAQ#get_log to get the output log and remember to close the crash window so the backtrace is printed in the log too. In ubuntu the debug package is probably something like wine1.3-dbg.
http://bugs.winehq.org/show_bug.cgi?id=28485
--- Comment #4 from David turbolad995@hotmail.co.uk 2011-10-05 07:03:46 CDT --- (In reply to comment #3)
Please, try installing the wine debugging symbols in your distribution and then run the program again. Follow the guidelines from http://wiki.winehq.org/FAQ#get_log to get the output log and remember to close the crash window so the backtrace is printed in the log too. In ubuntu the debug package is probably something like wine1.3-dbg.
I've tried doing that, but don't know how to get this working. The only method I know, which I've done already, is to open the Terminal in Ubuntu, type wine, add a space and then drag and drop the Pegasus Mail .exe file in front of the word wine, then press Enter.
The 2 attachments I added to this bug report were created by following that method.
It's hard for end users, such as myself, to provide technical information in these bug reports. I do my best and write these bug reports when Windows programs don't work properly in Wine and I hope that helps.
http://bugs.winehq.org/show_bug.cgi?id=28485
--- Comment #5 from Bruno Jesus 00cpxxx@gmail.com 2011-10-05 07:18:24 CDT --- After drag & drop the exe you will have something like: wine /home/...../pegasus.exe
Then, simply type the rest of the command from the get log URL: wine /home/...../pegasus.exe &> log.txt
Then attach the generated log.txt here. It will be created in the folder where your terminal is currently. Use the command pwd to see what directory the terminal is.
I'll test it today later too.
http://bugs.winehq.org/show_bug.cgi?id=28485
--- Comment #6 from David turbolad995@hotmail.co.uk 2011-10-05 14:03:08 CDT --- I had to un-install the previous working version of Pegasus Mail - version 4.52 - in order to install the non-working version i.e. version 4.62 which is affected by this bug.
The problem happens with Pegasus Mail 4.62 AFTER it's been installed in Wine. I closed Wine's crash window, but nothing happens after that. The log file gets stuck on this:
"wine: Unhandled page fault on read access to 0x01989258 at address 0x32f1b3:0x016c4e7e (thread 0009), starting debugger..."
The only way to kill Pegasus Mail once it crashes and stays "dead" on the screen forever is to use the "System Monitor" in Ubuntu and kill "winpm-32.exe". After killing Pegasus Mail in the "System Monitor", the lines of information in the log file are exactly the same as those in the file I attached here called "More lines of information when I managed to kill the process.".
http://bugs.winehq.org/show_bug.cgi?id=28485
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #7 from Bruno Jesus 00cpxxx@gmail.com 2011-10-09 13:25:02 CDT --- I can confirm this issue in 1.3.29. The app crashes and there is no backtrace printed.
http://bugs.winehq.org/show_bug.cgi?id=28485
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net Component|-unknown |kernel32 Summary|Pegasus Mail version 4.62 |Pegasus Mail version 4.62 |crashes on startup |crashes on startup (needs | |GetProcessDEPPolicy stub)
--- Comment #8 from Anastasius Focht focht@gmx.net 2011-10-19 16:44:04 CDT --- Hello,
the problem is the missing GetProcessDEPPolicy() API.
Some app code in "IERenderer.dll" dll entry manually resolves various API using GetProcAddress() and stores the API entry addresses in a table (IAT style).
--- snip --- ... 0024:Call KERNEL32.GetProcAddress(7b810000,019891c4 "GetProcessDEPPolicy") ret=016cc21b 0024:Ret KERNEL32.GetProcAddress() retval=00000000 ret=016cc21b ... 0024:Call KERNEL32.GetProcAddress(7b810000,019891c4 "SetProcessDEPPolicy") ret=016cc21b 0024:Ret KERNEL32.GetProcAddress() retval=7b824a38 ret=016cc21b ... --- snip ---
Later the app calls most of the API directly - without validation. Using GetVersionEx() it determined the Windows version and relied on this information - assuming specific APIs are present. Wine implements API on demand and does not provide a stub for every API leading to failure.
--- snip --- 0024:trace:seh:raise_exception code=c0000005 flags=0 addr=0x7bc7d333 ip=7bc7d333 tid=0024 0024:trace:seh:raise_exception info[0]=00000000 0024:trace:seh:raise_exception info[1]=00000000 0024:trace:seh:raise_exception eax=00000000 ebx=7bcc7ff4 ecx=67c24165 edx=00000000 esi=01801f5c edi=0000008f 0024:trace:seh:raise_exception ebp=0032eb64 esp=0032ea6c cs=0073 ds=007b es=007b fs=0033 gs=003b flags=00210246 0024:trace:seh:call_vectored_handlers calling handler at 0x7e00f3cd code=c0000005 flags=0 0024:trace:seh:call_vectored_handlers handler at 0x7e00f3cd returned 0 0024:trace:seh:call_stack_handlers calling handler at 0x7bc980b5 code=c0000005 flags=0 0024:trace:seh:__regs_RtlUnwind code=c0000005 flags=2 0024:trace:seh:__regs_RtlUnwind calling handler at 0x7bc7ae27 code=c0000005 flags=2 0024:trace:seh:__regs_RtlUnwind handler at 0x7bc7ae27 returned 1 0024:trace:seh:raise_exception code=c0000005 flags=0 addr=(nil) ip=00000000 tid=0024 0024:trace:seh:raise_exception info[0]=00000000 0024:trace:seh:raise_exception info[1]=00000000 0024:trace:seh:raise_exception eax=00000000 ebx=0000008e ecx=00000000 edx=00000000 esi=01801f5c edi=0000008f 0024:trace:seh:raise_exception ebp=0032ef00 esp=0032eed8 cs=0073 ds=007b es=007b fs=0033 gs=003b flags=00210206 0024:trace:seh:call_vectored_handlers calling handler at 0x7e00f3cd code=c0000005 flags=0 0024:trace:seh:call_vectored_handlers handler at 0x7e00f3cd returned 0 0024:trace:seh:call_stack_handlers calling handler at 0x1801ff9 code=c0000005 flags=0 0024:trace:seh:call_stack_handlers handler at 0x1801ff9 returned 1 0024:trace:seh:call_stack_handlers calling handler at 0x16c5c9e code=c0000005 flags=0 0024:Call user32.LoadStringW(016c0000,0000ffec,0032c700,00001000) ret=016ca6c6 0024:Ret user32.LoadStringW() retval=00000004 ret=016ca6c6 0024:Call KERNEL32.VirtualQuery(00000000,0032e974,0000001c) ret=016d99a0 0024:Ret KERNEL32.VirtualQuery() retval=0000001c ret=016d99a0 0024:Call user32.LoadStringW(016c0000,0000ffe2,0032c6f8,00001000) ret=016ca6c6 0024:Ret user32.LoadStringW() retval=00000030 ret=016ca6c6 0024:Call ntdll.RtlUnwind(0032ef08,016c5694,0032ee80,00000000) ret=016c5694 --- snip ---
The first exception is actually Wine itself, trying to figure out if this is an ATL thunk to be emulated.
http://source.winehq.org/git/wine.git/blob/62b7069fa941c6ac1c923f0a7986261e2...
Small nitpick ;-) One could check for NULL pc before trying this (line 1543), avoiding one extra exception ("call <null ptr>" is common for missing API/unimpl stubs bugs).
The second exception is the real one passed to app. Unfortunately this all happens in dll entry point with loader lock, hence the hang/winedbg behaviour.
Add GetProcessDEPPolicy() stub and the app happily starts, showing main GUI. Though it will complain later about other Wine insufficiencies, deserving own bugs.
Regards
http://bugs.winehq.org/show_bug.cgi?id=28485
--- Comment #9 from Austin English austinenglish@gmail.com 2011-10-19 18:09:57 CDT --- http://source.winehq.org/patches/data/80163
http://bugs.winehq.org/show_bug.cgi?id=28485
Saulius K. saulius2@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |saulius2@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=28485
--- Comment #10 from Saulius K. saulius2@gmail.com 2011-10-20 02:51:19 CDT --- Does this affect PM v4.61 also? http://www.filehippo.com/download_pegasus_mail/9330/
http://bugs.winehq.org/show_bug.cgi?id=28485
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |d4ec0a19c05c468532c47312bea | |f69e67cc4a7a4 Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #11 from Anastasius Focht focht@gmx.net 2011-10-20 16:19:11 CDT --- Hello,
fixed by http://source.winehq.org/git/wine.git/commitdiff/d4ec0a19c05c468532c47312bea... Thanks Austin.
--- quote --- Does this affect PM v4.61 also? http://www.filehippo.com/download_pegasus_mail/9330/ --- quote ---
No, only 4.62. They did some IE9 related overhaul between these versions, see their changelog.
Regards
http://bugs.winehq.org/show_bug.cgi?id=28485
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Alexandre Julliard julliard@winehq.org 2011-10-21 13:49:02 CDT --- Closing bugs fixed in 1.3.31.
http://bugs.winehq.org/show_bug.cgi?id=28485
--- Comment #13 from Saulius K. saulius2@gmail.com 2011-10-21 14:12:25 CDT --- (In reply to comment #11)
--- quote --- Does this affect PM v4.61 also? http://www.filehippo.com/download_pegasus_mail/9330/ --- quote ---
No, only 4.62. They did some IE9 related overhaul between these versions, see their changelog.
Thank you, Anastasius:). It seems it's time for new PM version entry in AppDB
(In reply to comment #8)
The first exception is actually Wine itself, trying to figure out if this is an ATL thunk to be emulated.
http://source.winehq.org/git/wine.git/blob/62b7069fa941c6ac1c923f0a7986261e2...
Small nitpick ;-) One could check for NULL pc before trying this (line 1543), avoiding one extra exception ("call <null ptr>" is common for missing API/unimpl stubs bugs).
So this could be filled like a separate bug set to ENHANCEMENT, no? This is probably for Alexandre to answer.
-
wine-bugs＠winehq.org