Walter Garcia-Fontes, after you clicked Ok in step 4, did it immediately
crash, or would you have to wait a few seconds, while still being able
to click around the spreadsheet?

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

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

Title:
  [Upstream] soffice.bin crashed with SIGSEGV in
  Timer::ImplTimerCallbackProc()

Status in LibreOffice Productivity Suite:
  New
Status in “libreoffice” package in Ubuntu:
  Incomplete

Bug description:
  I have a package composed by a collection of spreadsheets with macros.
  Since a couple of LibreOffice versions I get this crash. I attach a
  spreadsheet with macros where I can reproduce this crash 100% of the
  times. I will try to create a simpler test case since this spreadsheet
  is unnecessarily complex (a part of my package).

  To reproduce the crash, enable macros, and

  1) Open 1num1cat.ods (attached file). Press OK to the dialog that appears.
  2) Go to the "Data entry" worksheet
  3) Copy the range A2:B50 (any range here would do)
  4) Double click on A1 or B1, a dialog opens, click OK.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: libreoffice-core 1:4.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Jan 16 10:35:35 2014
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2010-10-25 (1178 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc --splash-pipe=5
  SegvAnalysis:
   Segfault happened at: 0x7f6821e4b52a:        testb  $0x2,0x38(%rdi)
   PC (0x7f6821e4b52a) ok
   source "$0x2" ok
   destination "0x38(%rdi)" (0x00000038) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/../program/libsclo.so
   ?? () from /usr/lib/libreoffice/program/../program/libsclo.so
   Timer::ImplTimerCallbackProc() () from 
/usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /usr/lib/libreoffice/program/libvclplug_gtklo.so
   g_main_dispatch (context=0xf5fc50) at 
/build/buildd/glib2.0-2.38.1/./glib/gmain.c:3065
  Title: soffice.bin crashed with SIGSEGV in Timer::ImplTimerCallbackProc()
  UpgradeStatus: Upgraded to saucy on 2013-09-12 (125 days ago)
  UserGroups: adm admin audio cdrom dialout lp lpadmin plugdev sambashare video 
www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1269734/+subscriptions

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