desktop-packages team mailing list archive

[anonymous mouse <785005@xxxxxxxxxxxxxxxxxx>]

I don't understand what is meant by either "Needs upstream bug reference
=> Incomplete" or "No reference URL.".

Regarding LibreOffice, I didn't open the bug for LibreOffice. I don't
have LibreOffice installed. I am not interested in LibreOffice at this
stage. I just want OOo, which is what comes with the current Ubuntu LTS
to work as it worked in 9.10. Which is to say, not crashing after
hibernate!

This bug report is one automatically submitted by Apport, If there is
further information needed, please explain to me what it is, and how to
get it. I'll note that others have had the same or similar problem (as
referenced in the bug report I linked to initially).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/785005

Title:
  soffice.bin crashed with SIGSEGV in __kernel_vsyscall() after
  hibernate

Status in The OpenOffice.org Suite:
  Invalid
Status in “libreoffice” package in Ubuntu:
  Invalid
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  Also see +bug/507061 <https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/507061>. 
  OOo seems to almost always (though not always) crash after hibernation. Maybe related to the Zotero plugin I just thought, I'll experiment a bit more. 

  System: Ubuntu 10.04.2 LTS
  Program version: 
  openoffice.org:
    Installed: 1:3.2.0-7ubuntu4.2
    Candidate: 1:3.2.0-7ubuntu4.2
    Version table:
   *** 1:3.2.0-7ubuntu4.2 0
          500 http://ftp.yz.yamagata-u.ac.jp/pub/linux/ubuntu/archives/ lucid-updates/universe Packages
          500 http://ftp.yz.yamagata-u.ac.jp/pub/linux/ubuntu/archives/ lucid-security/universe Packages
          100 /var/lib/dpkg/status
       1:3.2.0-7ubuntu4 0
          500 http://ftp.yz.yamagata-u.ac.jp/pub/linux/ubuntu/archives/ lucid/universe Packages
  What I expected to happen was it not to crash. What happened, it crashed. 

  Bug report generated by Apport.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: openoffice.org-core 1:3.2.0-7ubuntu4.2
  ProcVersionSignature: Ubuntu 2.6.32-31.61-generic 2.6.32.32+drm33.14
  Uname: Linux 2.6.32-31-generic i686
  Architecture: i386
  Date: Thu May 19 14:55:51 2011
  Disassembly: => 0x97b6f041:	Cannot access memory at address 0x97b6f041
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/openoffice/program/soffice.bin
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  ProcCmdline: /usr/lib/openoffice/program/soffice.bin -writer -splash-pipe=5
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x97b6f041:	Cannot access memory at address 0x97b6f041
   PC (0x97b6f041) not located in a known VMA region (needed executable region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: openoffice.org
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/tls/i686/cmov/libc.so.6
   abort () from /lib/tls/i686/cmov/libc.so.6
   os::die() ()
   VMError::report_and_die() ()
  Title: soffice.bin crashed with SIGSEGV in __kernel_vsyscall()
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/openoffice/+bug/785005/+subscriptions