Bug 51967 - EDITING: Copy-Paste Problem
Summary: EDITING: Copy-Paste Problem
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-10 22:11 UTC by andreas_paravan
Modified: 2013-10-25 15:08 UTC (History)
0 users

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 andreas_paravan 2012-07-10 22:11:05 UTC
Some often times, when operating with copy-paste to transfer text from one part to another the complete Writer freeze closes!!!


Current behavior:

Expected behavior:

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0.1
Comment 1 ydutrieux 2012-12-18 09:21:40 UTC
Hi andreas,

could you attach a doc where these copy/paste are more recurrent ?
Do you have the problem if you upgrade your version of libo to latest (3.5.7) ?
Comment 2 andreas_paravan 2012-12-21 10:52:44 UTC
Hello!
The problem occured in every textdocument, 1 of 100 copy/paste-procedures.
I have updated recently, and yesterday the problem occured once more!
I couldn`t attach a document because the problem collapse after the problem.
Andreas

Am 18.12.2012 10:21, schrieb bugzilla-daemon@freedesktop.org:
> ydutrieux@gmail.com <mailto:ydutrieux@gmail.com> changed bug 51967 
> <https://bugs.freedesktop.org/show_bug.cgi?id=51967>
> What 	Removed 	Added
> Status 	UNCONFIRMED 	NEEDINFO
> Ever confirmed 		1
>
> *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=51967#c1> 
> on bug 51967 <https://bugs.freedesktop.org/show_bug.cgi?id=51967> from 
> ydutrieux@gmail.com <mailto:ydutrieux@gmail.com> *
> Hi andreas,
>
> could you attach a doc where these copy/paste are more recurrent ?
> Do you have the problem if you upgrade your version of libo to latest (3.5.7) ?
> ------------------------------------------------------------------------
> You are receiving this mail because:
>
>   * You reported the bug.
>
Comment 3 QA Administrators 2013-09-24 01:47:47 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: 
https://wiki.documentfoundation.org/QA/FDO/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
Comment 4 QA Administrators 2013-10-25 15:08:59 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