During my tests for Bug 31585 my "LibreOffice 3.3.0Beta3 - WIN XP DE [OOO330m9 (build 220.127.116.11)]" lost ability for Mail Merge with Mail Merge Assistant. Even with an empty document LibO will stop responding without any processor load few moments after I I have started menu 'Tools - Mail Merge Wizard ...'.
I uploaded a standard Microsoft Crash report to a.m. URL, I will leave it there until end of December 2010.
Mail merge via print dialog still works without problems
I already tried to uninstall LibO, delete my user profile and reinstall - that did not help.
My 3.1.1 still creates Mail merge documents without problem.
Not reproducible on LibO 3.3 Beta3 Linux, I'll see ths when got my Windows build ready.
Hi Tor, I didn't see the problem on beta3 Windows either. Would you help to look at the log if there's something wrong there in LibO?
Sorry, that kind of crash report is useless to us, as far as I know. (At least I have no idea what to do with it.)
So is it a crash or a hang? The summary and initial description says hang, but then mentions a Microsoft crash report which presumably is generated when a process crashes.
LibO hangs without any CPU load, stops responding.
The MS crash report has been created because I have to terminate LibO using task manager (no other possibility), my hope was that the report might show in what situation LibO was when it was terminated with Task Manager.
No Progress with RC1 (as I feared).
I tried with LibreOffice 3.3.0 OOO330m17 (Build:3) libreoffice-build 18.104.22.168 (aka RC1) on WinXP DE (clean installation of LO w/o any existing profile for different reason)
The mail merge assistant worked for me
The mail merge assistant worked for me
LibO 3.3rc1 Win XP IT
(In reply to comment #6)
> No Progress with RC1 (as I feared).
Can you post a FileMonitor (http://technet.microsoft.com/en-us/sysinternals/bb896645) log?
Good Idea, I will try soon.
Strange thing, yesterday I was able to start mail merge E-Mail several times (and so I found [Bug 32329]), but Today the hang problem is back, so today I will do the FileMonitor test.
Same problem on my new PC: I ran through all steps of Mail Merge Wizard during my first mail merge on this PC, failed because of Bug 32329, and with my second attempt the hang is back.
Slightly loosing hope ...
I wonder if this is caolan's python magic: scripting/source/pyprov/mailmerge.py at least on Unix this goes through that (for me). Caolan - any thoughts ?
For me (having entered invalid server details), I get rather a nice delay - 10 seconds or so of hang, before it returns; how patient are you Rainer ? :-)
My only thoughts are that I wish I never implemented the mailmerge backend because of the constant moaning about it. If there's a problem in the backend itself, then its such a trivial little .py that anyone can debug it. So if someone has a problem with it then just find the mailmerge.py and add a few prints in it to log to a file.
If LibO does not hang, MM wizard appears within few seconds after Menu 'Tools -> MM-wizard'. If LibO wants to hang, it does not help to wait several minutes (It tried that).
Just I tried with an empty document, and LibO did not hang. I tried with a document with address fields, really tried to send, failed because of Bug 32329. After that UI is somehow broken, cant use scroll slider with mouse.
After termination of LibO and new start also no hang, today it works (but I also saw that with earlier LibO versions).
Currently I can't tell whether this particular problem has been solved or only been shifted, E-Mail Mailmerge still crashes on and on and will not send E-Mails
Hi Rainer; Caolan's comment is that you need to tweak the python to add some debugging information (popup dialogs or whatever) for when it fails. I've no idea how to do that, but with a few minutes of hunting it should be possible surely ?
Until we work out exactly where it is failing, not much can be done; and we simply cannot do that from here - we don't have your mail setup;
I will try that hoping to get a hint concerning crashes in
Bug 34187 - MAILMEGE E-Mail does not send mails
Any Ideas concerning alternative concepts to get something like a crash report?
I set "dbg = True" in "mailmerge.py", where can I find something like a report?
I think that oosplash.bin actually hides messages printed by the soffice.bin binary. Please try to run the application in a terminal using:
/opt/libreoffice/program/soffice -no-oosplash 2>&1 | tee mailmerge-debug.log
(In reply to comment #20)
> I think that oosplash.bin actually hides messages printed by the soffice.bin
> binary. Please try to run the application in a terminal using:
> /opt/libreoffice/program/soffice -no-oosplash 2>&1 | tee mailmerge-debug.log
Please forget about this. The problem is not Windows and it does not help there.
We need help from Tor.
(In reply to comment #19)
> I set "dbg = True" in "mailmerge.py", where can I find something like a report?
Caolan was so kind to help me some time ago:
I think the python emailmerge backend here is something of a red herring.
This bug talks about LibreOffice hanging on doing a emailmerge, but without an exact route to reproduce it. bug 32553 is also a hang on doing emailmerge, but with an exact route to reproduce it which I can fix, so I'm going to assume they're both the same thing.
*** This bug has been marked as a duplicate of bug 32553 ***
Rainer, please close if it is fixed.
I will not handle this bug any longer because we have several more detailed ones.