Bug 86112 - calc crashes when launched from writer
Summary: calc crashes when launched from writer
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected)
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Not Assigned
Depends on:
Reported: 2014-11-10 14:32 UTC by sophie
Modified: 2015-12-05 14:48 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description sophie 2014-11-10 14:32:04 UTC
Hi, to reproduce:
- open a new writer doc
- fill some text (dt+F3)
- try to open Calc from the toolbar
==> it crashes immediately.
The terminal says:
** (soffice:8514): WARNING **: Unknown event notification 36
pure virtual method called
terminate called without an active exception
version: Version:
Build ID: 3d16e8593ac1e9d90f0a033732766907476822f9
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-11-09_23:54:19 Ubuntu 14.10 x64
Comment 1 Julien Nabet 2014-11-10 14:38:49 UTC
On pc Debian x86-64 with master sources updated today, I don't reproduce this.
I opened Writer, typed "text", then in toolbar (first icon at left), "Worksheet", Calc opened.

- What does "dt+F3" mean?
- Could you confirm I did the same thing as you?
 if yes, could you try to retrieve a backtrace (by following this link https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)?
Comment 2 sophie 2014-11-10 14:44:11 UTC
Hi Julien, 
dt is an autotext (dummy text) that allow you to fill quickly some text. To use it, just write dt and then hit f3.
Could you try to fill more text (about 6 or 8 lines). It does not crash with one line but with more than 6. 
I can't get a backtrace on Ubuntu, I need to build LibreOffice and I can't do it now, really sorry I can't help here. Sophie
Comment 3 Julien Nabet 2014-11-10 14:48:16 UTC
No problem for bt.
Thank you for "dt" explanation :-)

I put 5 Lorem Ipsum paragraphs, no crash :-(
Just to be sure, did you reset your LO directory profile?
Do you enable accessibility part?
Comment 4 sophie 2014-11-10 14:52:25 UTC
It's a parallel install completely new, so the profile is just created. All my accessibility settings are disabled. I get the same crash if I use the menu. I'll try under my debian install. Sophie
Comment 5 sophie 2014-11-10 15:10:08 UTC
More testing: If I add two autotext using dt+f3, it doesn't crash. But with only one, it crashes. There is no alpha2 for deb x86 other than 64 so I can't test under Debian.
Comment 6 Julien Nabet 2014-11-10 15:27:36 UTC
Still fail to reproduce :-(
Hope someone will be luckier than me.
Comment 7 sophie 2014-11-10 16:53:52 UTC
Testing with Version:
Build ID: 24f0a5815f581dd9a7f09d30213a379edee6e9ac (pre release) Ubuntu 14.10 crashing. I don't get any crash with the alpha2 under Debian 6.0 Sophie
Comment 8 Buovjaga 2014-11-27 12:16:06 UTC
No need for this to be NEEDINFO anymore.
Couldn't repro.

Ubuntu 14.10 64-bit Version:
Build ID: 6b219f012edbe069c461f4e0746898e33fa1dd49
TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2014-11-25_21:56:46
Comment 9 raal 2014-11-27 18:21:41 UTC
I can not confirm with Version:
Build ID: d273a60bfdbf9bb7623bed38667ec0647753157c
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-11-20_03:05:21
Comment 10 Maxim Monastirsky 2014-11-27 18:59:51 UTC
Hi sophie,

(In reply to sophie from comment #0)
> The terminal says:
> ** (soffice:8514): WARNING **: Unknown event notification 36
This warning comes from the accessibility code, and that proves what I suggested in Bug 86117 that you have accessibility features turned on _in some way_ on your system. It could be even some env. variable. (Actually it seems from Bug 79913 comment 7, that some package on Ubuntu triggers accessibility without user knowledge.) Is it possible to test it on a Ubuntu livecd, or on a _clean_ vm installation?

So for anyone trying to confirm this bug - you should do it e.g. with Orca running. (Although I couldn't reproduce it even in this case.)
Comment 11 raal 2014-11-27 20:09:08 UTC
> So for anyone trying to confirm this bug - you should do it e.g. with Orca
> running. (Although I couldn't reproduce it even in this case.)

Still unable to reproduce with Orca running, ubuntu 14.10
Comment 12 tommy27 2015-01-04 15:05:07 UTC
please retest with a recent 4.4.x build and tell if the issue you saw in november 2014 is still present
Comment 13 QA Administrators 2015-07-18 17:36:40 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-07-18
Comment 14 QA Administrators 2015-09-04 03:01:53 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-09-03
Comment 15 Julien Nabet 2015-12-05 14:48:18 UTC
cleanup keywords