Christopher M. Penalver, thank you for your response and instructions. I have executed the commands in the first paragraph, and everything went through without a problem. One minor thing, the very first command (cd /var/crash) complained that there is no such directory. Nevertheless, after executing all commands now I do have such directory.
The problem is, that it is empty, i.e. no crash report is generated by LibreOffice. I did reproduce the crash, but var/crash directory is empty. Apparently, this is a crash within LibreOffice. In fact, when I open LibvreOffice the next time it remembers that there was a crash and recovers successfully the active file prior to the crash. By the way, I suspect the crash is due to the parser module that builds the "Design View" (sorry, I used the wrong terminology in my original bug report), because editing in SQL View or running the query itself does not produce a crash. I chose to file the bug report with Ubuntu and not with LibreOffice because my LibreOffice is from Ubuntu distribution, and as I mentioned, it does not have the standard "update" option. Evidently, Ubuntu has modified or customized the generic LibreOffice package to better suit Ubuntu's architecture. Thanks again, Janos On 05/13/2015 11:48 PM, Christopher M. Penalver wrote: > Janos G. Komaromi, thank you for reporting this and helping make Ubuntu > better. However, your crash report is missing. Please follow these > instructions to have apport report a new bug about your crash that can be > dealt with by the automatic retracer. First, execute at a terminal: > cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade > && sudo service apport start force_start=1 > > If you are running the Ubuntu Stable Release you might need to enable > apport in /etc/default/apport and restart. > > Now reproduce the crash, then open your file manager, navigate to your > /var/crash directory and open the crash report you wish to submit. > If this fails you will have to open a terminal and file your report with > 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash > is the crash you would like to report. If you get an error that you aren't > allowed to access this report you will have to file it with 'sudo ubuntu-bug > /var/crash/_my_crash_report.crash'. If you run the command against the crash > report and a window pops up asking you to report this, but then never opens a > new report, you would be affected by > https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to > WORKAROUND this, one would need to open the following file via a command line: > sudo nano /etc/apport/crashdb.conf > > and comment out the line: > 'problem_types': ['Bug', 'Package'], > > by changing it to: > # 'problem_types': ['Bug', 'Package'], > > Save, close, and try to file the crash report again via: > ubuntu-bug /var/crash/_my_crash_report.crash > > I'm closing this bug report since the process outlined above will > automatically open a new bug report which can then dealt with more > efficiently. > > Please feel free to subscribe me to this new report. > > Also, please do not attach your crash report manually to this report and > reopen it. > > Thank you for your understanding. > > Helpful bug reporting tips: > https://wiki.ubuntu.com/ReportingBugs > > ** Changed in: libreoffice (Ubuntu) > Status: New => Invalid > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454310 Title: LibreOffice 4.2 crashes vector::_M_range_check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1454310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
