This Crash happened in LibreOfficeWriter Version: 6.4.0.0.alpha0+ Build ID: 4248d759744f83a68d334a8b347124719a2886a8 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-07-09_15:00:58 Locale: de-DE (de_DE.UTF-8); UI-Language: en-US Calc: threaded I had a document consisting of 196 paragraphs (ca 30 pages). Then I used Table>Convert>Text to table to make a table with one paragraph per cell (1 column), for this purpose I selected the paragraph marker for Separate Text At. Then I added a column left to the one column table. The purpose of this column is to number the paragraphs consecutively in this leftmost column. Then I added another column to the right in order to provide space to comment each cell in the middle. Then I adjusted the column width to meet my objectives. I tried to apply consecutive numbering to the first column. For this purpose I entered the numbers 1, 2, 3, 4, to the first four cells. Then I selected these cells and wanted to extend the numbering as one does in a spreadsheet application. Sometimes this is possible in tables which are part of a LO Writer document: Then the usual controls around the table show up like in a spreadsheet application like LibreOfficeCalc. However it did not do that. My next idea to apply consecutive ordering was to copy all cells to LibreOfficeCalc by selecting them all and using the clipboard. I added the numbers 1, 2, 3, 4 to the cells A1, …, A4. Then I selected these cells and extended the numbering downward to the end of the table (i.e. to A196 in my case). Then I did Ctl-C to copy this column to the clipboard. Formatting the whole LO Writer document had cost me quite some effort and I did not want to loose that. Therefore I tried to paste the clipboard to the table in the LO Writer document to the first column. For this purpose I first marked the first column. There was an empty paragraph in each of them. For some strange reason the cells had inherited the paragraph style from the (original) column right to it. But I did not want paragraphs with indentation or bullets there, therefore I first set them all to Default Style and also I specifically switched off any bullets for all the paragraphs in the first column. Then LO Writer crashed and showed me this message: Due to an error.LibreOgfficeDev crashed. All the files you were working on will now be saved. The next time LibreOfficeDev is launched, your files will be recovered automatically. The following files will be recovered (and it showed me the three files which were open in LibreOfficeDev at that moment). The next message was: Unfortunately it seems that LibreOfficeDev crashed when it was last run. You can help us to fix this issue by sending an anonymous report to the LibreOfficeDev crash reporting server. Then an option to restart LibreOfficeDev in safe mode (which I did not check). I selected “Send Crash Report”. The next thing was a crash report dialogue. I already complained about this type of dialogue earlier in https://bugs.documentfoundation.org/show_bug.cgi?id=126488 and showed a picture of it there. I hope the crash reporting server got the crash report and hopefully you can associate it with my bug report now. Unfortunately until now, nobody could tell me where to really find the crash dump file on my Xubuntu 16.04.4 computer. In fact, I was told there is no crash report on the type of version which I was using. However, there was this message! If I knew where the crash dump is, I would like to add it. Unfortunately the dialogue above did not even tell which kind of bug it was nor in which module it happened! So if anyone could please tell me which additional file is necessary to pin down this bug, I would like to provide it. But I can not provide the file with which the bug happened.
Adalbert, can you attach your file here?
(In reply to Roman Kuznetsov from comment #1) > Adalbert, can you attach your file here? As I wrote just in the last line of my post, I can not provide the file for confidentiality reasons. Meanwhile I tried to make a smaller one (with only 10 lines) but on that one the method of pasting the column with the numbers from the spreadsheet to the table in LO Writer worked. Today and tomorrow I don't have the time to look deeper into this bug. But do you know, where I might grasp the crash logfile telling about the call stack and type of error, which was made during the crash and perhaps was automatically uploaded to your servers? Unfortunately in the crash-process, there is no place to note what I have done immediately before the crash happened. Perhaps the automatic crash report is just there among hopefully only a few others, but according to my own debugging experience, knowing the line of code where a crash happened often is less than half of the information necessary to really fix it.
Surprisingly, from the spreadsheet version of my LO Writer table I could copy the first column to the clipboard after it has been made to contain consecutive numbers. Just for analysis I pasted this clipboard content to mousepad, a pure ASCII editor. Mousepad then showed me the numbers 1 to 196, each number on a separate line. My next idea was to introduce one additional step: I marked the complete content of the file in the mousepad editor: Ctl-A and then Ctl-C to copy it to the clipboard. Then I went to my LO Writer window and pasted the numbers 1 to 196 (each on a separate line) to the first column of the table in the Writer document. Before I did Ctl-V, I marked the complete first column, which I had prepared initially to provide space for the line numbering. And to my great surprise (after the disappointment that pasting from LO Calc caused a crash) pasting the apparently same content from mousepad worked! So at least there is a workaround to apply consecutive numbering to a table in a LO Writer document, but it is a bit awkward. Of course the error itself should be eradicated after its exact faultiness has been understood.
[Automated Action] NeedInfo-To-Unconfirmed
Hello Adalbert, Would it be possible to send the document to me ( to my email ) ? I promise I won't share it with someone else and I can also investigate the crash, otherwise it's impossible to know what's going on
(In reply to Xisco Faulí from comment #5) > Hello Adalbert, > Would it be possible to send the document to me ( to my email ) ? I promise > I won't share it with someone else and I can also investigate the crash, > otherwise it's impossible to know what's going on setting to NEEDINFO
Today I could download the most recent development version from https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@86-TDF/current/. I installed version Version: 6.4.0.0.alpha0+ Build-ID: 9ee5ad5a0b84bfa652da34694ba4f75668f06087 CPU-Threads: 4; BS: Linux 4.4; UI-Render: Standard; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-07-30_13:21:44 Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE Calc: threaded in parallel to Version: 5.1.6.2 Build-ID: 1:5.1.6~rc2-0ubuntu1~xenial8 CPU-Threads: 4; BS-Version: Linux 4.4; UI-Render: Standard; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group which I normally use when I can not afford loosing work. I tried the bug with the same data with which I had incurred the crash using the Build ID: 4248d759744f83a68d334a8b347124719a2886a8 (2019-07-09). I could not reproduce the crash with this one. I also tried it with all steps from the beginning. Same result. So I would suggest to close this thread now. I hope setting it to "unconfirmed" is the right action for that purpose.
(In reply to Adalbert Hanßen from comment #7) > Today I could download the most recent development version from > https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@86-TDF/ > current/. > > I installed version > > Version: 6.4.0.0.alpha0+ > Build-ID: 9ee5ad5a0b84bfa652da34694ba4f75668f06087 > CPU-Threads: 4; BS: Linux 4.4; UI-Render: Standard; VCL: gtk3; > TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: > 2019-07-30_13:21:44 > Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE > Calc: threaded > > > So I would suggest to close this thread now. I hope setting it to > "unconfirmed" is the right action for that purpose. Adalbert, thank you for testing. Let's close it as WFM now