Bug 92636

Unfortunately there's nothing we can do with this bug. We need clear reproducible steps. "Sometimes" just isn't information that is useable.

Please continue to test, see if you can get consistent steps, and then provide those steps.

Also - in the future please provide your OS in your description. Lastly, you might want to try to reset your user profile: https://wiki.documentfoundation.org/UserProfile

Closing as INVALID for now just because there isn't any actionable in the bug report - again, no offense to you and not saying you're not seeing an issue, just a bug report needs to be reproducible and they don't exist here. Apologies for any inconvenience. If you can get repro steps down set and see the issue with a fresh profile, set the bug to UNCONFIRMED and let us know what steps you're doing (along with your OS). Thanks!

I had to stop what I was working. I have no chance of finding a way to predict when this @#$% bug will crop up and when it won't.

I want to know how many other severe bugs have been "resolved" invalid in this way. I know another bug that made it impossible to use LibreOffice files after transferring from one computer to another was "resolved" invalid, because I was unable to submit an example file because (1) it was too big to submit (2) it would be impossible to compare "working on this machine" and "not working on this machine though it's the exact same file."

I can't answer that question - you can dig through INVALID bugs if you want to spend your time in that way. Our time is stretched incredibly thin, dedicated volunteers give tens of thousands of hours at no cost. As such, we require clear reproducible steps that we can follow and reproduce, else we're just wasting our time and devs time.

So - if you're interested, here is a list of INVALID bugs: https://bugs.documentfoundation.org/buglist.cgi?bug_status=RESOLVED&limit=0&list_id=548333&order=opendate%20DESC%2Cchangeddate%2Cbug_status%2Cpriority%2Cbug_severity&product=LibreOffice&query_format=advanced&resolution=INVALID


There are 4,073 of them - if you want to poke that list to get an answer to your question, feel free to do so.

I can't go through that list with my disabilities. It keeps changing the column width. I just think it would help to distinguish the different reasons bugs get declared "resolved" invalid:

For example,

1. the bug report system "reports" one the user hasn't finished typing.

2. The bug can't be documented, yet.

3. The bug was already resolved with another update. etc.

Seeing if the same ussues keep cropping up on #2 could help.

Thus sucking up even more time from our incredibly stretched volunteer team. We say in our comments why a bug is invalid - for instance this one is because instructions are not clear enough to actually reproduce the problem so we could spend hours trying to see "sometimes" bad behavior....we don't have that kind of time to spare thus why it is INVALID.

You saying you don't have the time or ability doesn't resolve the fact that our team is stretched thin and we can't dedicate infinite time to individual issues that are poorly reported. A good bug report does the following:

1) Says what OS is being used;
2) Says what version of LibreOffice is being used;
3) Says exact reproducible steps in a clear and concise way;
4) Provides simple test documents;
5) Provides screenshots where appropriate
6) The user is responsible for doing everything in their power to try to triage the issue to successfully get steps 1-5 done - it's not the QA volunteers job to mess around with files to see "sometimes" bad behavior.

Also - I suggested removing your user profile as this clears up a decent amount of issues: https://wiki.documentfoundation.org/UserProfile

If you want to insult people for posting bugs, and for talking about the limitations of the system, that's your problem.

Created attachment 117194 [details]
One affected document

I haven't clearly encountered the original bug today.

I have had trouble where I think I've selected one part of a group, but the computer has selected the whole group or another part of the group. In those cases, it sometimes loses the color indications because there are one.

I have also seem it claim the color "Sky Blue 10." Nothing in the file is Sky Blue 10.

This may be a bug involving the default color, and/or the absence of default colors.