← Back to team overview

desktop-packages team mailing list archive

[Bug 1058977] Re: soffice.bin crashed with SIGSEGV in UpdateNativeMenu()


Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner.

So far all reports show it was on Ubuntu 12.10.  Can anyone reproduce on

** Changed in: libreoffice (Ubuntu)
       Status: Confirmed => Incomplete

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 UpdateNativeMenu()

Status in “libreoffice” package in Ubuntu:

Bug description:
  libreoffice crashes after closing in ubuntu 12.10

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.5.3-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  Date: Sun Sep 30 12:10:02 2012
  Disassembly: => 0x58:	Cannot access memory at address 0x58
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --impress --splash-pipe=6
   Segfault happened at: 0x58:	Cannot access memory at address 0x58
   PC (0x00000058) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: libreoffice
   ?? ()
   ?? () from /usr/lib/libreoffice/program/libvclplug_gtklo.so
   ?? () from /usr/lib/libreoffice/program/libvclplug_gtklo.so
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: soffice.bin crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to quantal on 2012-08-11 (49 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare www-data

To manage notifications about this bug go to: