LibreOffice 4.2 crashes vector::_M_range_check

[Janos G. Komaromi]

LibreOffice Base, Query: The specific query works, but can only edit in SQL view. If I try to edit in Base view mode it crashes. Only one of the many queries have this problem. Also, as I was researching this I could not find the Check for update option in the Tools menu. Is it not available in the Ubuntu packaged version? - thanks, Janos
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: XFCE
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2013-10-31 (819 days ago)
InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820)
Package: libreoffice 1:4.2.8-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
Tags: third-party-packages trusty
Uname: Linux 3.13.0-77-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-08-31 (515 days ago)
UserGroups: adm apu audio cdrom dip lpadmin plugdev sambashare sudo x2gouser
_MarkForUpload: True

[Janos G. Komaromi (jankom)]

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
...

[penalvch (penalvch)]

Janos G. Komaromi, to advise, please don't manually create new reports about this issue as noticed in:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1538730

as it doesn't accomplish anything but creating unnecessary reports to duplicate to this one.

Despite this, I've recently encountered a situation where a crash bug for a different problem with LibreOffice aren't "caught" by apport, substantiating what you have experienced. So, while the reporting work flow is valid (closing this report), the infrastructure to execute on the work flow isn't.

Hence, please perform the following to further debug this issue:
1) Execute at a terminal:
sudo apt-get -y install libreoffice

2) Execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1454310

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

3) Execute at a terminal and post the results here untarred/uncompressed:
apt-show-versions -r libreoffice*

4) Advise to any 3rd party add-ons, plugins, etc. that you downloaded not expressed in 3). This wouldn't invalidate the report, but it helps to fully understand the environment one is in.

Thank you for your understanding.

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

apport information

[Janos G. Komaromi (jankom)]

Dear Christopher M. Penalver,

Thank you for the quick reply. The attached text file is the copy of my
terminal output according to your instructions. I recreated the bug
before executing step #2. It looks like my computer (acerlinux) was
communicating with launchpad.

As far as creating unnecessary reports - I did not mean to cause any
trouble, and will report eventual future bugs according to your email.

Btw: the ^C at the end of the terminal output is due to the fact that
the normal "paint text with cursor" then "right click" will copy and
paste the painted (marked) text Unix/Linux method did not work. So I
tried the Ctr-C / Ctr-V method. That did not work either. Finally the
GUI right click in terminal gave me the opportunity to copy the terminal
output into the clipboard. Why is this? Why do we have to emulate
Vindooz? - just a little annoyance. It seems to me this change is
recent. The "paint text" method used to work B4.

regards,

Janos

On 01/27/2016 05:00 PM, Christopher M. Penalver wrote:
> Janos G. Komaromi, to advise, please don't manually create new reports about this issue as noticed in:
> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1538730
>
> as it doesn't accomplish anything but creating unnecessary reports to
> duplicate to this one.
>
> Despite this, I've recently encountered a situation where a crash bug
> for a different problem with LibreOffice aren't "caught" by apport,
> substantiating what you have experienced. So, while the reporting work
> flow is valid (closing this report), the infrastructure to execute on
> the work flow isn't.
>
> Hence, please perform the following to further debug this issue:
> 1) Execute at a terminal:
> sudo apt-get -y install libreoffice
>
> 2) Execute the following command only once, as it will automatically gather debugging information, in a terminal:
> apport-collect 1454310
>
> When reporting bugs in the future please use apport by using 'ubuntu-
> bug' and the name of the package affected. You can learn more about this
> functionality at https://wiki.ubuntu.com/ReportingBugs.
>
> 3) Execute at a terminal and post the results here untarred/uncompressed:
> apt-show-versions -r libreoffice*
>
> 4) Advise to any 3rd party add-ons, plugins, etc. that you downloaded
> not expressed in 3). This wouldn't invalidate the report, but it helps
> to fully understand the environment one is in.
>
> Thank you for your understanding.
>
> ** Changed in: libreoffice (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: libreoffice (Ubuntu)
> Status: Invalid => Incomplete
>

[penalvch (penalvch)]

Posting relevant requested information:
apt-show-versions -r libreoffice
libreoffice:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-avmedia-backend-gstreamer:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-base:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-base-core:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-base-drivers:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-calc:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-common:all/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-core:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-draw:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-gnome:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-gtk:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-impress:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-java-common:all/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-math:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-pdfimport:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-report-builder-bin:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-sdbc-firebird:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-sdbc-hsqldb:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-style-human:all/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-style-tango:all/trusty-security 1:4.2.8-0ubuntu3 uptodate
libreoffice-writer:amd64/trusty-security 1:4.2.8-0ubuntu3 uptodate
openclipart-libreoffice:all/trusty 1:0.18+dfsg-14 uptodate

[penalvch (penalvch)]

Janos G. Komaromi, to see if this is already resolved, could you please use one of the 5.x PPAs via https://launchpad.net/~libreoffice and advise to the results?

[Janos G. Komaromi (jankom)]

Christopher M. Penalver, sorry, I did my best to study the web site and
try to fetch the ppa but failed. Must have missed something. Here is the
terminal output:

*janos@acerlinux:~$ sudo add-apt-repository 1:5.0.4-rc2-Oubuntu1-trusty1
[sudo] password for janos:
Error: '1:5.0.4-rc2-Oubuntu1-trusty1' invalid
janos@acerlinux:~$ sudo add-apt-repository 1:5.0.4-rc2-0ubuntu1-trusty1
Error: '1:5.0.4-rc2-0ubuntu1-trusty1' invalid
janos@acerlinux:~$

*As you see, I tried with both "Oh"ubuntu and "zero"ubuntu.

Please, help steer me in the right direction.

**

On 01/29/2016 12:43 PM, Christopher M. Penalver wrote:
> Janos G. Komaromi, to see if this is already resolved, could you please
> use one of the 5.x PPAs via https://launchpad.net/~libreoffice and
> advise to the results?
>

[Janos G. Komaromi (jankom)]

Christopher M. Penalver,

Thanks again, and THE BUG IS FIXED in LibreOffice 5!

1) sudo add-apt-repository ppa:libreoffice-5.0 - executed OK
2) sudo apt-get update - executed OK
3) "Software updater" notification appeared - ran it OK
4) Another "Software updater notification appeared, this time for
LibreOffice - ran it OK
5) Opened the file where the query edit crash happened before - this
time NO CRASH, works as expected.

Please, close the bug as completed and fixed.

Janos

On 01/29/2016 09:59 PM, Christopher M. Penalver wrote:
> sudo add-apt-repository ppa:libreoffice/libreoffice-5-0
>

[penalvch (penalvch)]

Janos G. Komaromi, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1454310/comments/11 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.