← Back to team overview

desktop-packages team mailing list archive

Re: [Bug 1454310] Re: LibreOffice 4.2 crashes vector::_M_range_check


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.



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

** Attachment added: "TerminalCaptureBug1454310.txt"

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.

  LibreOffice 4.2 crashes vector::_M_range_check

Status in libreoffice package in Ubuntu:

Bug description:
  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

To manage notifications about this bug go to: