Bug 102269 - crashes after Interactive Calendar is used
Summary: crashes after Interactive Calendar is used
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-19 00:51 UTC by Tom O
Modified: 2017-05-02 11:34 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom O 2016-09-19 00:51:04 UTC
I use a freeware called Interactive Calendar.  It has a transparent calendar on the screen, and allows editing "calendar events."  I use it pretty much as a daily diary, if you will, but also for posting appointments.

When I attempt to load a calc spreadsheet after working with the calendar, the spreadsheet loads without the icon bar, and generally crashes if you try to close it.  When you reload, it reloads okay, and is completely functional.  After calc has been used, however, the calendar program has a crash, but loads immediately, and when calc is used again, it will crash on loading.  I suspect they are trying to write to the same dll in windows, since these are both windows programs.  Frustrating, but thought I would bring it to someone's attention since it may also happen with other programs if they are writing to a shared dll, or whatever.  I was always a fan of programs that kept all their parts in their own directory, and this was why - shared files that can be written to in Windows tend to be used by more than one program.  It is possible that the calendar is keeping a file open since it is up all the time, and office is only loaded as needed.
Comment 1 Buovjaga 2016-09-19 07:47:21 UTC
Just to clarify:
Which LibreOffice version are you using?
Which Windows version are you using?

LibreOffice 5.2 has a crash reporter, that might be able to catch the crash and then you could submit the crash data to a server with the click of a button. It might not catch every sort of crash, though.

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.
Comment 2 QA Administrators 2017-03-28 08:18:27 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2017-05-02 11:34:44 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20170502