104863 – Crash in: com::sun::star::uno::Sequence<com::sun::star::datatransfer::DataFlavor>::Sequence<com::sun::star::datatransfer::DataFlavor>(long)

Bug 104863 - Crash in: com::sun::star::uno::Sequence<com::sun::star::datatransfer::DataFlavor>::Sequence<com::sun::star::datatransfer::DataFlavor>(long)

Summary: Crash in: com::sun::star::uno::Sequence<com::sun::star::datatransfer::DataFla...

Status:	RESOLVED INSUFFICIENTDATA

Alias:	None

Product:	LibreOffice
Classification:	Unclassified
Component:	Writer (show other bugs)
Version: (earliest affected)	5.2.3.3 release
Hardware:	x86-64 (AMD64) Windows (All)

Importance:	medium minor
Assignee:	Not Assigned

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2016-12-22 14:55 UTC by chiropterist+bugzilla
Modified:	2017-07-27 12:02 UTC (History)
CC List:	2 users (show)

See Also:
Crash report or crash signature:	["com::sun::star::uno::Sequence<com::sun::star::datatransfer::DataFlavor>::Sequence<com::sun::star::datatransfer::DataFlavor>(long)"]

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description chiropterist+bugzilla 2016-12-22 14:55:28 UTC

This bug was filed from the crash reporting server and is br-b6547baf-6dd8-410a-b4e8-15e0cfc3b868.
=========================================
Steps to reproduce:
- Open .odt document
- Select Keep Old Styles (in template)
- Cut and paste text (immediately after opening doc)

Result:
- Nothing happens (text doesn't move to new location)

(When I reopened Writer, everything worked normally.)

Comment 1 Xisco Faulí 2016-12-22 17:25:56 UTC Comment hidden (obsolete)

Hello

Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)

Comment 2 Julien Nabet 2016-12-23 09:44:37 UTC

I don't understand how to reproduce this since an odt isn't a template.
So I can't see "Keep Old Styles".
However, I must recognize I don't use templates so it's certainly because I know too few about this.

Comment 3 QA Administrators 2017-06-28 12:36:50 UTC Comment hidden (obsolete)

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 INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

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

MassPing-NeedInfo-Ping-20170628

Comment 4 QA Administrators 2017-07-27 12:02:22 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-20170727