Bug 86806 - paintbrush paintbucket format painter cursor does not always appear when it should
Summary: paintbrush paintbucket format painter cursor does not always appear when it s...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2014-11-27 23:47 UTC by pb
Modified: 2015-07-18 17:27 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Note You need to log in before you can comment on or make changes to this bug.
Description pb 2014-11-27 23:47:21 UTC
Sometimes, when a column is selected, clicking the paintbrush icon does not result in paintbucket cursor.  This also seems to be associated with strange behavior when trying to create a new column, sometimes crashing Calc.  (And unavoidable recovery process then trashes the document.)

This is new behavior for me, and it is not consistent, so I suspect it is related to the content of my xls file (or hardware! [but I doubt it]).

It seems to happen the first time a sheet or document has been opened, but not every time.

Obviously, this is not enough info to debug.  I will add more if I can find out more.
Comment 1 raal 2014-11-29 11:15:28 UTC
Hello pb,

Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document.
(Please note that the attachment will be public, remove any sensitive information before attaching it.)
How can I eliminate confidential data from a sample document?
Thank you
Comment 2 pb 2014-11-29 20:28:48 UTC
Sorry, I should have set it as needinfo in the first place.

The document that I have been seeing this on is a financial spreadsheet.  Sanitizing it would involve removing everything except dates.  Since I suspect the bug is data-dependent, it would be sort of pointless to submit a sanitized document for a possibly data-dependent bug that happens only sporadically.

I just wanted to put down a marker that it happens -- it might click with someone who is working on another seemingly different bug.  At some point, I may be able to determine more.
Comment 3 QA Administrators 2015-06-08 14:28:41 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:

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!

This NEEDINFO Message was generated on: 2015-06-08

Warm Regards,
QA Team
Comment 4 QA Administrators 2015-07-18 17:27:19 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-07-18