Created attachment 158689 [details] Hardcopy Mailmerge with ODBC Connection to sqlite3. When sending by email, the crash (see attachment) occurs, even in safe mode.
The error is only triggered if the submenu "E-Mail Nachricht" is selected. However, the content of each e-mail is incorrect. ALL recipient e-mails are attached to each e-mail.
The problem only occurs when the email is persionalized. See 2 more attachments. Does anyone have an idea where I should start? Is debugging possible?
Created attachment 158694 [details] with email persionalization
Created attachment 158695 [details] without email personalization
@Tomi : is this particular to using SQLite as a backend data source, or does the same thing happen with any data source ? The reason I ask is because it would help us to triage this better. If it occurs with any data source when you select a personalized greeting, then it is a mailmerge problem (python code probably, or mishandling of UI input), whereas if it only occurs when accessing SQLite data source over ODBC, the problem probably lies with the database code.
A test with a table (ods) and with a very simple HSQLDB data source shows the same behaviour. Since I am a software engineer, I could also do deeper analysis. How should I approach debugging?
(In reply to Tomi from comment #6) > A test with a table (ods) and with a very simple HSQLDB data source shows > the same behaviour. > Since I am a software engineer, I could also do deeper analysis. How should > I approach debugging? Usually debugging is done with a symbols enabled build of LO, so either you would have to build LO yourself with symbols enabled, or alternatively, if you are on Linux, you might be able to find a symbols package provided for your distribution and specific version of LO that you could install. Not sure, how easy, or well, debugging a python script (for the mailmerge functionality is a python script) from within a running LO process would be, though, that's beyond my knowledge.
Would it be possible you attach the minimum files to reproduce this (ideally with hsqldb embedded) + minimal step by step process to reproduce this? Before this, you can give a try to 6.4.3 to be sure the pb is still there on 6.4 branch. About building LO, it's quite easy on Linux (see https://wiki.documentfoundation.org/Development/GetInvolved) but if you want debug build, you need space (at least 30GB) + good cpu and at least 8GB for RAM.
Dear Tomi, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Tomi, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp