Bug 57001 - EDITING: Characters get overwritten - no text entry possible
Summary: EDITING: Characters get overwritten - no text entry possible
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
3.5.7.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-12 04:43 UTC by bugquestcontri
Modified: 2015-03-01 07:25 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
screenshot showing the position of the bug (234.84 KB, image/png)
2013-11-24 14:14 UTC, bugquestcontri
Details
bug mentioned in comment 12 (96.90 KB, image/png)
2014-12-26 15:09 UTC, bugquestcontri
Details
observed the same bug (47.86 KB, image/png)
2015-02-17 13:42 UTC, bugquestcontri
Details
screen shote of the bug and explanations in the screenshot (158.89 KB, image/png)
2015-03-01 07:25 UTC, bugquestcontri
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bugquestcontri 2012-11-12 04:43:05 UTC
Problem description: 
Suddenly characters get overwritten in Impress content field (bulleted list). Continuing of typing is not possible. Moving of ther cursor makes automatically a text selection although no mouse button is clicked.

I observed this problem already several times. Until now only on my old PC ( XP SP2)
Today for the first time on my new PC (XP SP3)

Today I had only LIbO Writer, Impress and Firefox running the same time. 

Steps to reproduce:
I cannnot reproduce the problem but could document it with a camera. Explanations are recorded

Current behavior:
Suddenly characters get overwritten until I get out of the content element. 


Expected behavior:
Non sudden overwriting of characters

Platform (if different from the browser):  XP SP3
              
Browser: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0

I can be contacted.
Comment 1 bugquestcontri 2012-11-12 04:59:41 UTC
here is the link to the movie

https://dl.dropbox.com/u/47733131/MOV09974.MPG
Comment 2 bugquestcontri 2013-03-05 01:35:53 UTC
I observe the same bug in Version 3.6.5.2 (Build ID: 5b93205), machine and OS is the same as in previous report
Comment 3 A (Andy) 2013-03-24 08:45:05 UTC
This seems to be really strange.  But, I have currently no idea to reproduce it.
Does this issue only occur with this specific presentation file or also with any other new presentation file?

Does this issue still persist for you with the latest release of LO?

Could you ask a friend to reproduce this on his/her computer or attach a sample file to reproduce it?
Comment 4 bugquestcontri 2013-03-24 09:27:55 UTC
@A thanks for working on this topic. I understand that you need to reproduce it. Just in the last days it happened again and I have no clue on what was the trigger.

I could possibly observe and note
- which applications are running
- what template was used
- was the file once save in a format different than odp and opened from there

Please comment on above and feel free to add more parameters. I will try to collect information as much as possible.

Please understand that I have periods where I work every day with Impress and then there are periods without Impress work.

Let's get this bug!!!!
Comment 5 QA Administrators 2013-09-24 01:44:07 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 6 QA Administrators 2013-10-25 15:09:28 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
Comment 7 bugquestcontri 2013-11-24 14:12:28 UTC
Sorry for not replying earlier.

Last week I still observed the bug in 4.0.5.2 several times. and today, in 4.1.3.2 I could create the bug several time.

I observed that it has to do with the location of the cursor position and the horizontal guidelines/snap lines. In the vertical position shown in the screenshot "BugPosition" I could create the bug several times but never with a 100% success rate. Success rate to create the bug is estimated to be less then 10%. Therefore I assume that still another parameter is needed.

I one case I remember that the cursor was already in the text box but a different position

I created it by having text lines just below the horizontal snap line and tried to insert the cursor in this existing text. When the bug appears, the cursor is not a thin vertical line but selects an entire character. Using the insert button does not have any influence to the bug. 

Last week in version 4.0.5.2 I needed to save and close Impress to get rid of the bug. Today in 4.1.3.2

I continue to observe the bug to understand and report the cause.
Comment 8 bugquestcontri 2013-11-24 14:14:03 UTC
Created attachment 89713 [details]
screenshot showing the position of the bug
Comment 9 Joel Madero 2014-11-06 17:38:01 UTC
Never confirmed - moving to UNCONFIRMED so QA looks at it. Thanks
Comment 10 tommy27 2014-12-14 14:08:10 UTC
please tell if bug is still present in LibO 4.3.4.1
if YES, revert status to UNCONFIRMED
if NO, change it to RESOLVED WORKSFORME
Comment 11 bugquestcontri 2014-12-26 14:48:49 UTC
It is a bit tricky to create the bug but I will try to test it during a presentation I have to make in the next weeks and will get back to you.

I am using 4.3.5.2 in the meantime. 

Please give me some time.
Comment 12 bugquestcontri 2014-12-26 15:07:49 UTC
Despite having written my above comment I tried for a while to create the bug but could not. During the upcoming presentation I will try to provoke the bug by using several horizontal guide line. 

However I could create a similar bug. Please see attachment  "Impress bug 141226".
Comment 13 bugquestcontri 2014-12-26 15:09:37 UTC
Created attachment 111375 [details]
bug mentioned in comment 12
Comment 14 QA Administrators 2015-02-11 20:03:46 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-02-11
Comment 15 bugquestcontri 2015-02-17 13:42:22 UTC
Created attachment 113460 [details]
observed the same bug

I again found the same bug in v 4.3.5.2 running XP/SP3.
Comment 16 Buovjaga 2015-02-19 12:27:43 UTC
(In reply to bugquestcontri from comment #15)
> Created attachment 113460 [details]
> observed the same bug
> 
> I again found the same bug in v 4.3.5.2 running XP/SP3.

Hey, please create a new bug report for your new bug. Try to reproduce it with 4.4 before creating the report. Thanks.
Comment 17 bugquestcontri 2015-02-19 13:59:46 UTC
About reporoduction I explained already that I cannot really reproduce it but observe it often. 

Should I observe it again in 4.4 I will open a new report. I will usual switch to the next version at x.y.4.
Comment 18 bugquestcontri 2015-03-01 07:25:52 UTC
Created attachment 113790 [details]
screen shote of the bug and explanations in the screenshot

I could create the bug again. Please see attachment. There is also the description of the bug. 

I wanted to save the file, remove all confidential staff and attach it here but saving and reopening the file removed the bug. Thus there is only a screen shot with additional explanations

What is clearly to be seen the bug occurs when the text, written at the moment of the bug. is located closely to the guide line.

Version used was either 4.3.5 or 4.3.6 on XP/.SP3