*** This bug is a duplicate of bug 927058 ***
    https://bugs.launchpad.net/bugs/927058

** This bug is no longer a duplicate of private bug 853476
** This bug has been marked a duplicate of bug 927058
   soffice.bin crashed with SIGABRT in raise()

-- 
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/938381

Title:
  soffice.bin crashed with SIGABRT in raise()

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  While trying to save a file to a very old (but still quite functional)
  USB flash drive (512MB, USB 1.0), Writer gave up the ghost.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-core 1:3.5.0~beta2-2ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.92-0ubuntu1
  Architecture: amd64
  Date: Wed Feb 22 10:00:51 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer --splash-pipe=6
  Signal: 6
  SourcePackage: libreoffice
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  Title: soffice.bin crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/938381/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to