Created attachment 55763 [details] Test kit Steps to reporoduce with Parallel Dev-Installation of "LibreOffice 3.5.0 Beta3- WIN7 Home Premium (64bit) German UI [Build-ID: e40af8c-10029e3-615e522-88673a2-727f724] : 1. Download / unzip attached test kit 2. replace my e-mail address by yours in spreadsheet "adhoc.ods" 3. Create and connect a database "adhoc.odb" 4. open sampledrawing.odt 5. Start Mail merge wizard and try to send all 158 mails as PDF > Starts promising, but when send process starts LibO will hang Kill LibO, start again 11. open samplegdi.odt (more or less the same, but heading picture created by cutting DRAWing and inserting as GDI 12. Start Mail merge wizard and try to send all 158 mails as PDF > Much faster creation of 158 documents to be sent, send process is heavy work for LibO, but all few seconds a document will be sent I also checked older Master versions and OOo 3.1.1., all the same. Seems inherited from OOo.
Okay ... this bus is almost 1 year old, has good 'how to reproduce'-steps, and yet never tried to confirm? Ok, lets change that :-). I can CONFIRM a crash after step '5' using Mac OSX 10.8.2; I'll upload crashlog. But when continuing with step 12: no crash, but still no document will be send (I don't receive any mail). Kind regards, Joren
(In reply to comment #1) > Okay ... this bus is almost 1 year old, has good 'how to reproduce'-steps, > and yet never tried to confirm? Ok, lets change that :-). > > I can CONFIRM a crash after step '5' using Mac OSX 10.8.2; I'll upload > crashlog. But when continuing with step 12: no crash, but still no document > will be send (I don't receive any mail). > > Kind regards, > Joren Addition information: LibreOffice 4.1.0.0.alpha0+ (Build ID: 73731b01cd65defdf9b42a9754bede3ba84221d) TinderBox: MacOSX-Intel@1-built_no-moz_on_10.6.8, Branch:master, Time: 2013-01-02_08:47:51
Created attachment 72401 [details] Crash log Mac osx
Adding self to CC if not already on
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT: - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
Dear Rainer Bielefeld Retired, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Rainer Bielefeld Retired, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This is a bit difficult to test as the volume of emails is so high. I first tried with 9 emails, it went fine, no hang. Then I tried with 40 and I got this: <class 'smtplib.SMTPSenderRefused'>: (421, b'Service not available, closing transmission channel', 'my@email.com'), traceback follows File "/home/user/libreofficetwo/instdir/program/mailmerge.py", line 262, in sendMailMessage self.server.sendmail(sendermail, truerecipients, msg.as_string()) File "/usr/lib/python3.10/smtplib.py", line 887, in sendmail raise SMTPSenderRefused(code, resp, from_addr) So I think my email provider refused to send so much email in such a short period of time. In any case, the hang does not seem to be present anymore. Rainer: if you still reproduce, feel free to change back to NEW. You should test with a fresh master build as there were fixes to mail merge code recently. Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: ff2f433cdfda74dbf69a11342a98ccbfb5bc6a72 CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded