Bug 73170

Summary: Screen blanks during selection
Product: LibreOffice Reporter: Frann Leach <frann.leach>
Component: LibreOfficeAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: serval2412
Priority: medium    
Version: 3.5.7.2 release   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Frann Leach 2013-12-30 21:49:35 UTC
This bug has been around for some time. I first noticed it 2 computers ago, but as it died shortly afterwards, I assumed it was related to that. It also occurred on a laptop (also on the way out). But I have finally noticed that it only occurs when selecting text in LibreOffice.

You put your cursor at the beginning of the bit you want to select, and whether you click and drag or double click and drag, almost always the screen will go black until you let go the mouse button. Of course, you can't see where you got to, so you generally have to repeat the selection. Oddly, when you do, the screen blanking does not recur for that particular selection, but it will do it again when you go to select something else.

So far as I can tell, it only happens in LibreOffice, both in Writer and Spreadsheet to my knowledge, which are the components I use most often.

I'm using the default version for my distro of Ubuntu (12.04).
Comment 1 Julien Nabet 2013-12-31 10:38:07 UTC
Frann:
Did you install any LO specific extensions?
Do you reproduce this with a brand new file?
Do you have accessibility components enabled?
Do you reproduce this after having renamed your LO directory profile? (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux)
Could you give a try to a newer LO version by using ppa repo? (see https://launchpad.net/~libreoffice/+archive/ppa)
Comment 2 Frann Leach 2013-12-31 14:42:22 UTC
Did you install any LO specific extensions? No

Do you reproduce this with a brand new file? Yes

Do you have accessibility components enabled? Don't think so, how would I check?

Do you reproduce this after having renamed your LO directory profile? (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux) After a quick try, it seems to work, will let you know if it recurs over the next few days, as I'm in the process of writing something that will necessitate quite a bit of use. However, even if it does fix the problem, since it seems to be a frequent event (judging by the number of times it's happened to me), surely there must be a permanent fix that doesn't require regular renaming of the user folder. I'm not a naive user, but it must be a major problem for those that are, given that I've noted this on 3 separate computers (all running Ubuntu, but probably not all using 12.04, as I resisted for some time, lol).

Could you give a try to a newer LO version by using ppa repo? (see https://launchpad.net/~libreoffice/+archive/ppa) I'll leave this until I am sure the previous fix didn't work.
Comment 3 QA Administrators 2014-07-08 17:28:43 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 Frann Leach 2014-07-08 20:53:44 UTC
It doesn't recognise my signin details, but the bug hasn't appeared for
some time (otoh I don't often use OO any more)


On 8 July 2014 18:28, <bugzilla-daemon@freedesktop.org> wrote:

>   *Comment # 3 <https://bugs.freedesktop.org/show_bug.cgi?id=73170#c3> on
> bug 73170 <https://bugs.freedesktop.org/show_bug.cgi?id=73170> from QA
> Administrators <qa-admin@libreoffice.org> *
>
> 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
>
>  ------------------------------
> You are receiving this mail because:
>
>    - You reported the bug.
>
>
Comment 5 QA Administrators 2014-08-04 16:14:52 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