** Visibility changed to: Public

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

  soffice.bin crashed with SIGSEGV in uno_type_sequence_construct()

Status in “libreoffice” package in Ubuntu:

Bug description:
  I'm using calc every day, and get ram eaten and 100 % cpu used after a while 
(> 15 minutes), then it freeze itself and sometimes give a crash like that one.
  This is happening on Quantal i386 logged as gnome-classic (unity fully 
purged, and no ppa)

  A possible related report is bug #1041354

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-core 1:3.6.0~rc4-0ubuntu3
  Uname: Linux 3.6.0-030600rc3-generic i686
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: i386
  Date: Sun Aug 26 16:05:20 2012
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
/home/username/Documents/Quinte-stats.ods --splash-pipe=6
   Segfault happened at: 0xb722c9e3 <uno_type_sequence_construct+76>:   cmpl   
   PC (0xb722c9e3) ok
   source "$0x0" ok
   destination "0x28(%edx)" (0x006f009b) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: libreoffice
   uno_type_sequence_construct () from 
   ?? () from 
   ?? () from 
 const&) () from 
   ?? () from 
  Title: soffice.bin crashed with SIGSEGV in uno_type_sequence_construct()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin avahi-autoipd cdrom couchdb dialout dip disk fax fuse 
haldaemon lpadmin netdev plugdev polkituser proxy root rtkit sambashare ssh 
tape tty users video whoopsie www-data

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to