http://bugs.winehq.org/show_bug.cgi?id=11887
Summary: WinPMail v4.50 closes on sending mail Product: Wine Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: admin@ubunto-tstephenson.com CC: admin@ubunto-tstephenson.com
I am testing a new release of Pegasus Mail, closed beta v14, v4.50. This version of the program is using the Visual C++ complier instead of the Borland C complier. Pretty much everything works except the sending process. When you send a message using either the built-in mailer or the Mercury queue the program just goes away without error. This is pretty much the same error as has been seen with previous versions of the program. When you hit send, the message is sent (or queued) but the program is closed by the OS. There is no error message in Pegasus Mail as you would expect if there was a crash by the program. Obviously this does not happen when running on MS Windows Win98, WinXP or Vista. The latest version of Wine allows a "Reply" to work properly but a "New" message", or "Forward" (with or without editing), causes the program to close.
Regression testing will not work since all versions of Wine I've tested over the years cause the same problem.
When working with MS Windows there is a program called WinDBG provided by MS that allows you to see exactly what happens when the program fails. Is there a similar program that we can use with Linux and Wine that will allow us to trap the program calls at the time of failure?
I am currently testing with Ubuntu v7.10 and Wine 0.9.56
http://bugs.winehq.org/show_bug.cgi?id=11887
Timo-Heikki Mäkelä imaxfun@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|admin@ubunto-tstephenson.com|
--- Comment #1 from Timo-Heikki Mäkelä imaxfun@gmail.com 2008-03-07 16:23:26 --- Welcome to debug Wine! :)
This is not critical for Wine to work in general, just another normal bug. Please, change the tag.
Yes, there'z an built-in debugger in Wine, winedbg. Check more here: http://www.winehq.org/site/docs/winedev-guide/index
I remove you from the CC, because you'll get the messages as Author of the bug already.
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #2 from Thomas Stephenson admin@ubunto-tstephenson.com 2008-03-07 17:38:52 --- (In reply to comment #1)
Welcome to debug Wine! :)
This is not critical for Wine to work in general, just another normal bug. Please, change the tag.
Yes, there'z an built-in debugger in Wine, winedbg. Check more here: http://www.winehq.org/site/docs/winedev-guide/index
I remove you from the CC, because you'll get the messages as Author of the bug already.
Thanks for the information. I've gone through WineDBG and I'm not all that sure that this is going to help. There is no program faults shown, no windows crash error at all. The program is simply closed when the message is sent. This would normally be a failure of a another program and Windows closes the program to do the system recover.
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #3 from Thomas Stephenson admin@ubunto-tstephenson.com 2008-03-07 17:44:24 --- (In reply to comment #1)
Welcome to debug Wine! :)
This is not critical for Wine to work in general, just another normal bug. Please, change the tag.
Not sure what this means. Wine is failing, there is nothing wrong with the program, it works with all of the various flavors of 32 bit MS Windows. What level of severity should this be?
http://bugs.winehq.org/show_bug.cgi?id=11887
Timo-Heikki Mäkelä imaxfun@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |imaxfun@gmail.com
--- Comment #4 from Timo-Heikki Mäkelä imaxfun@gmail.com 2008-03-07 18:04:51 --- For a bug to be 'critical' it would make Wine fail in general, not just on a single application or even several. Wine failing on a single application makes it a 'normal' bug. Please, see 'Severity' above for definitions.
http://bugs.winehq.org/show_bug.cgi?id=11887
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal Version|unspecified |0.9.56.
http://bugs.winehq.org/show_bug.cgi?id=11887
Jaroslav Fojtik fojtik@penguin.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fojtik@penguin.cz
--- Comment #5 from Jaroslav Fojtik fojtik@penguin.cz 2008-05-10 06:59:31 --- I confirm this bug on my computer and wine 1.0rc1.
It is strange that Email is coorrectly sent ant Wine crashes then. It is also interesting that Pegasus Mail popups something about not having space on a drive (I have 1GB free).
May be that tons of these messages on a console might lead to fixing this bug. fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
http://bugs.winehq.org/show_bug.cgi?id=11887
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #6 from Lei Zhang thestig@google.com 2008-05-10 10:04:12 --- confirming
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #7 from Lei Zhang thestig@google.com 2008-06-02 17:50:08 --- duplicate of bug 10213?
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #8 from Thomas Stephenson admin@ubunto-tstephenson.com 2008-06-03 00:36:56 --- (In reply to comment #7)
duplicate of bug 10213?
Different version of Pegasus Mail but the problem is essentially identical. Wine shuts the program down when a message is sent or the editor window is closed. This seems to be a normal shutdown in but cases since the lock file is removed as in done with a normal close. If the program crashed the lock file would remain.
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #9 from Lei Zhang thestig@google.com 2008-06-03 02:26:57 --- You can try reverting the patch that caused the regression in bug 10213. If that fixes it, then it's the same bug.
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #10 from Thomas Stephenson admin@ubunto-tstephenson.com 2008-06-10 10:29:08 --- (In reply to comment #9)
You can try reverting the patch that caused the regression in bug 10213. If that fixes it, then it's the same bug.
Could you please point me to some place that describes how I would "revert the patch". I've been searching all over and have had no luck at all.
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #11 from Austin English austinenglish@gmail.com 2008-06-10 15:56:36 --- (In reply to comment #10)
(In reply to comment #9)
You can try reverting the patch that caused the regression in bug 10213. If that fixes it, then it's the same bug.
Could you please point me to some place that describes how I would "revert the patch". I've been searching all over and have had no luck at all.
$ git show 29b5c987d53baced430abc6cabdd55115107d688 | patch -p1 -R
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #12 from Thomas Stephenson admin@ubunto-tstephenson.com 2008-06-10 23:14:05 --- (In reply to comment #11)
(In reply to comment #10)
(In reply to comment #9)
You can try reverting the patch that caused the regression in bug 10213. If that fixes it, then it's the same bug.
Could you please point me to some place that describes how I would "revert the patch". I've been searching all over and have had no luck at all.
$ git show 29b5c987d53baced430abc6cabdd55115107d688 | patch -p1 -R
I must be thick. I assume this needs to be run in a terminal session but when I try this it errors out. It can't find the "get" command.
bash: $: command not found The program 'patch' is currently not installed. You can install it by typing: apt-get install patch bash: patch: command not found
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #13 from Austin English austinenglish@gmail.com 2008-06-11 01:21:00 --- (In reply to comment #12)
I must be thick. I assume this needs to be run in a terminal session but when I try this it errors out. It can't find the "get" command.
bash: $: command not found The program 'patch' is currently not installed. You can install it by typing: apt-get install patch bash: patch: command not found
sudo apt-get install patch git-core
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #14 from Thomas Stephenson admin@ubunto-tstephenson.com 2008-06-11 11:59:51 --- (In reply to comment #13)
(In reply to comment #12)
I must be thick. I assume this needs to be run in a terminal session but when I try this it errors out. It can't find the "get" command.
bash: $: command not found The program 'patch' is currently not installed. You can install it by typing: apt-get install patch bash: patch: command not found
sudo apt-get install patch git-core
Ok, now I get
git show 29b5c987d53baced430abc6cabdd55115107d688 | patch -p1 -R fatal: Not a git repository
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #15 from Austin English austinenglish@gmail.com 2008-06-11 13:08:11 --- (In reply to comment #14)
Ok, now I get
git show 29b5c987d53baced430abc6cabdd55115107d688 | patch -p1 -R fatal: Not a git repository
Do you have the git repository downloaded? You need to cd to that directory.
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #16 from Thomas Stephenson admin@ubunto-tstephenson.com 2008-06-11 13:37:47 --- (In reply to comment #15)
(In reply to comment #14)
Ok, now I get
git show 29b5c987d53baced430abc6cabdd55115107d688 | patch -p1 -R fatal: Not a git repository
Do you have the git repository downloaded? You need to cd to that directory.
Not that I know of, where is the repository located on the web?
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #17 from Austin English austinenglish@gmail.com 2008-06-11 14:15:44 --- (In reply to comment #16)
(In reply to comment #15)
(In reply to comment #14)
Ok, now I get
git show 29b5c987d53baced430abc6cabdd55115107d688 | patch -p1 -R fatal: Not a git repository
Do you have the git repository downloaded? You need to cd to that directory.
Not that I know of, where is the repository located on the web?
http://wiki.winehq.org/GitWine
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #18 from Thomas Stephenson admin@ubunto-tstephenson.com 2008-06-11 15:17:58 --- (In reply to comment #17)
(In reply to comment #16)
(In reply to comment #15)
(In reply to comment #14)
Ok, now I get
git show 29b5c987d53baced430abc6cabdd55115107d688 | patch -p1 -R fatal: Not a git repository
Do you have the git repository downloaded? You need to cd to that directory.
Not that I know of, where is the repository located on the web?
Yep, found it and looks like I'm getting closer. Here's the error this time;
root@ubuntu:~/wine# root@ubuntu:~/wine# git show 29b5c987d53baced430abc6cabdd55115107d688 | patch -p1 -R can't find file to patch at input line 13 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |commit 29b5c987d53baced430abc6cabdd55115107d688 |Author: Francois Gouget fgouget@codeweavers.com |Date: Fri Feb 24 15:34:09 2006 +0100 | | user32: Handle WM_ENDSESSION in DefWinProc(). | DefWinProc() should call PostQuitMessage() on WM_ENDSESSION if the | shutdown is proceeding. | |diff --git a/dlls/user/defwnd.c b/dlls/user/defwnd.c |index 27d0683..5ea3ee4 100644 |--- a/dlls/user/defwnd.c |+++ b/dlls/user/defwnd.c -------------------------- File to patch:
FWIW, if this actually fixes the closing problem with WinPMail should this not be removed as a patch to the basic Wine package?
http://bugs.winehq.org/show_bug.cgi?id=11887
Thomas Stephenson admin@ubunto-tstephenson.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fgouget@codeweavers.com
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #19 from Austin English austinenglish@gmail.com 2008-06-11 16:36:14 --- (In reply to comment #18)
Yep, found it and looks like I'm getting closer. Here's the error this time;
root@ubuntu:~/wine#
Don't run/build as root. Root permission is only needed to run make install, and you don't have to install it to test (optional, but not needed, as you can run wine from the build directory).
root@ubuntu:~/wine# git show 29b5c987d53baced430abc6cabdd55115107d688 | patch -p1 -R can't find file to patch at input line 13 Perhaps you used the wrong -p or --strip option? The text leading up to this was:
File to patch:
That one wasn't your fault ;-). Seems dlls/user was renamed to dlls/user32. I'll attach a patch in a moment, you can either tell it manually to patch the correct file, or use the patch I'll attach shortly.
FWIW, if this actually fixes the closing problem with WinPMail should this not be removed as a patch to the basic Wine package?
The patch fixed behavior for some apps, but not others. Win32 API is a disastrous mess, and fixing some bugs often causes others. However, in this case, the patch has seemed to cause more problems than it solved, and probably should be reverted.(In reply to comment #18)(In reply to comment #18)
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #20 from Austin English austinenglish@gmail.com 2008-06-11 16:37:29 --- Created an attachment (id=13931) --> (http://bugs.winehq.org/attachment.cgi?id=13931) Revert patch
Download this patch, and apply this with:
$ patch -p1 < test.txt
Then rebuild wine and test your app.
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #21 from Thomas Stephenson admin@ubunto-tstephenson.com 2008-06-12 12:17:46 --- (In reply to comment #20)
Created an attachment (id=13931)
--> (http://bugs.winehq.org/attachment.cgi?id=13931) [details]
Revert patch
Download this patch, and apply this with:
$ patch -p1 < test.txt
Then rebuild wine and test your app.
Done the patch but the rebuild wine means I again have no real idea how to do something. ;-( Could you give me a couple of pointers?
Thanks,
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #22 from Austin English austinenglish@gmail.com 2008-06-12 13:22:53 --- (In reply to comment #21)
(In reply to comment #20)
Created an attachment (id=13931)
--> (http://bugs.winehq.org/attachment.cgi?id=13931) [details] [details]
Revert patch
Download this patch, and apply this with:
$ patch -p1 < test.txt
Then rebuild wine and test your app.
Done the patch but the rebuild wine means I again have no real idea how to do something. ;-( Could you give me a couple of pointers?
Thanks,
The regression testing guide also sortof serves as a build guide: http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #23 from Thomas Stephenson admin@ubunto-tstephenson.com 2008-06-12 15:29:09 --- (In reply to comment #22)
(In reply to comment #21)
(In reply to comment #20)
Created an attachment (id=13931)
--> (http://bugs.winehq.org/attachment.cgi?id=13931) [details] [details] [details]
Revert patch
Download this patch, and apply this with:
$ patch -p1 < test.txt
Then rebuild wine and test your app.
Done the patch but the rebuild wine means I again have no real idea how to do something. ;-( Could you give me a couple of pointers?
Thanks,
The regression testing guide also sortof serves as a build guide: http://wiki.winehq.org/RegressionTesting
This is not much help to me. I tried doing regression testing for days and never was sure I got it right since there was never any change to the way Wine worked with Pegasus Mail. That's the primary reason no one had done regression testing since we were not at all clear as to how to do this.
My Wine is now in two different directories. ~.wine and ~\wine I was hoping there would be some simple way to build the wine package by running something like wineinstall that is in the ~\wine\tools directory.
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #24 from Austin English austinenglish@gmail.com 2008-06-12 15:34:37 --- (In reply to comment #23)
This is not much help to me. I tried doing regression testing for days and never was sure I got it right since there was never any change to the way Wine worked with Pegasus Mail. That's the primary reason no one had done regression testing since we were not at all clear as to how to do this.
My Wine is now in two different directories. ~.wine and ~\wine I was hoping there would be some simple way to build the wine package by running something like wineinstall that is in the ~\wine\tools directory.
E-mail me privately, and I'll try to help. This sort of thing doesn't belong on bugzilla.
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #25 from Thomas Stephenson admin@ubunto-tstephenson.com 2008-06-12 15:57:24 --- (In reply to comment #24)
(In reply to comment #23)
This is not much help to me. I tried doing regression testing for days and never was sure I got it right since there was never any change to the way Wine worked with Pegasus Mail. That's the primary reason no one had done regression testing since we were not at all clear as to how to do this.
My Wine is now in two different directories. ~.wine and ~\wine I was hoping there would be some simple way to build the wine package by running something like wineinstall that is in the ~\wine\tools directory.
E-mail me privately, and I'll try to help. This sort of thing doesn't belong on bugzilla.
Agreed, it should not be in bugzilla but it's also obvious that this is way beyond my skill set. I've worked with Windows, VM, VMS, Netware and a bit of UNIX but it's not at all clear to me as to how to get rid of the patch. I'm too much of a Linux/Wine nubie.
It appears that you have found the reason through regression testing of why the Wine closes Pegasus Mail when it sends a close to the editor. I really want to thank you for your effort. I would have expected some sort of response from the developer of the patch that broke this in the first place but that does not appear to be the case.
I hope one of these days this fix will show up in a released version.
http://bugs.winehq.org/show_bug.cgi?id=11887
David Harrington x3jia@tesco.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |x3jia@tesco.net
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #26 from David Harrington x3jia@tesco.net 2008-07-08 16:46:15 --- Still not fixed in 1.1.0.
http://bugs.winehq.org/show_bug.cgi?id=11887
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE
--- Comment #27 from Lei Zhang thestig@google.com 2008-07-08 18:06:25 --- I have a strong feeling this is a duplicate of Bug 10213.
*** This bug has been marked as a duplicate of bug 10213 ***
http://bugs.winehq.org/show_bug.cgi?id=11887
--- Comment #28 from David Harrington x3jia@tesco.net 2008-07-08 18:46:53 --- (In reply to comment #27)
I have a strong feeling this is a duplicate of Bug 10213.
*** This bug has been marked as a duplicate of bug 10213 ***
I'm sure you are right, Lei Zhang - thanks.
http://bugs.winehq.org/show_bug.cgi?id=11887
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #29 from Lei Zhang thestig@google.com 2008-07-08 20:02:12 --- closing dup.