** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

At present, OSX users who require Java functionality, including any that https://www.anchoragekitchenremodeling.com/ created embedded databases which worked previously, no longer have access to that functionality in current builds.

sing 64-bit Linux Mint Cinnamon 17.1 with 4.0.4-040004-generic kernel
LibreOffice version: 5.0.0.0.beta1
Build ID: 0a16c3dda4150008d9be6f24cbd15ac198d116d3 http://www.iu-bloomington.com/ 
Locale: et-EE (et_EE.UTF-8)


Writing long comments will scroll automatically the comment first row to screen and writing place at the end remains unvisible from screen.

Same situation - activating comment window to improve already written comment firstly will mark bunch of text because it tries to scroll long comment https://www.webb-dev.co.uk/  first row to screen and therefore will automatically mark a lot of text. It means that if the long comment was scrolled to the end and then tries to edit that comment - it means to write something to the end of long comment then it will automatically scroll the first row at the same time when activating comment editing and therefore will mark all text because mouse left cursor is pressed down and this means also text marking due to automatic scrolling.
 https://waytowhatsnext.com/ 
Here is one exception - when inserting long comment in case there is one comment before (upwards) then there will be scroll bar until there will be finished first editing session. But when once click outside the comment and then again back to improve it - then this error starts again - first row will be scrolled to the screen and downside of comment goes out of the screen and is not viewable and thus http://www.acpirateradio.co.uk/  hard to edit. Workaround is to write comment in some external text editor and just copy to the appropriate place, usually in the end of long comment.

sing 64-bit Linux Mint Cinnamon 17.1 with 4.0.4-040004-generic kernel
LibreOffice version: 5.0.0.0.beta1
Build ID: 0a16c3dda4150008d9be6f24cbd15ac198d116d3
Locale: et-EE (et_EE.UTF-8)
 http://www.logoarts.co.uk/ 

Writing long comments will scroll automatically the comment first row to screen and writing place at the end remains unvisible from screen.

Same situation - activating comment window to improve already written comment firstly will mark bunch of text because it tries to scroll long comment first row to screen and therefore will automatically mark a lot of text. It means that if the long comment was scrolled to the end and then tries to edit that comment - it means http://www.slipstone.co.uk/  to write something to the end of long comment then it will automatically scroll the first row at the same time when activating comment editing and therefore will mark all text because mouse left cursor is pressed down and this means also text marking due to automatic scrolling.
 http://embermanchester.uk/ 
Here is one exception - when inserting long comment in case there is one comment before (upwards) then there will be scroll bar until there will be finished first editing session. But when once click outside the comment and then again back to improve it - then this error starts again - first row will be scrolled to the screen and downside http://connstr.net/  of comment goes out of the screen and is not viewable and thus hard to edit. Workaround is to write comment in some external text editor and just copy to the appropriate place, usually in the end of long comment.

sing 64-bit Linux Mint Cinnamon 17.1 with 4.0.4-040004-generic kernel
LibreOffice version: 5.0.0.0.beta1
Build ID: 0a16c3dda4150008d9be6f24cbd15ac198d116d3
Locale: et-EE (et_EE.UTF-8) http://joerg.li/ 


Writing long comments will scroll automatically the comment first row to screen and writing place at the end remains unvisible from screen.

Same situation - activating comment window to improve already written comment firstly will mark bunch of text because it tries to scroll long comment http://www.jopspeech.com/  first row to screen and therefore will automatically mark a lot of text. It means that if the long comment was scrolled to the end and then tries to edit that comment - it means to write something to the end of long comment then it will automatically scroll the first row at the same time when activating comment editing and therefore will mark all text because mouse left http://www.wearelondonmade.com/  cursor is pressed down and this means also text marking due to automatic scrolling.

Here is one exception - when inserting long comment in case there is one comment before (upwards) then there will be scroll bar until there will be finished first editing session. But when once http://www.compilatori.com/  click outside the comment and then again back to improve it - then this error starts again - first row will be scrolled to the screen and downside of comment goes out of the screen and is not viewable and thus hard to edit. Workaround is to write comment in some external http://www-look-4.com/  text editor and just copy to the appropriate place, usually in the end of long comment.

No Repro using VCL: gtk2 tested in current master back to version 5.4 for https://www.drywallaugusta.com/ This is also true for gradients perhaps.