Bug Hunting Session
Bug 58321 - About the menu in Mandriva Linux
Summary: About the menu in Mandriva Linux
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
3.6.4.3 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-15 06:18 UTC by Chiyaruka
Modified: 2014-10-05 22:59 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Image of a check mark (85.34 KB, image/png)
2012-12-15 06:18 UTC, Chiyaruka
Details
Image of a Checkmark (85.34 KB, image/png)
2012-12-26 09:54 UTC, Rob Snelders
Details
Apache OpenOffice (87.48 KB, image/png)
2013-01-31 12:51 UTC, Chiyaruka
Details
OpenOffice.org (87.39 KB, image/png)
2013-01-31 12:52 UTC, Chiyaruka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chiyaruka 2012-12-15 06:18:58 UTC
Created attachment 71533 [details]
Image of a check mark

Hello, I'm Japanese. I'm sorry English is weird.
I'm using LibreOffice on Mandriva Linux 2010.2.
The color of a check mark in the menu is not inverted.
A check mark will work, but I am hard to see.
Thanks in advance.
Comment 1 Rob Snelders 2012-12-26 09:54:38 UTC
Created attachment 72128 [details]
Image of a Checkmark

Setting the attachment to a picture
Comment 2 Rob Snelders 2012-12-26 09:55:48 UTC
Thank you for reporting this problem.

I can't reproduce the problem with Ubuntu 12.04 x86_64 and LO4.0-beta2.

Maybe somebody else can try.
Comment 3 Adolfo Jayme 2013-01-31 04:49:00 UTC
Seems like the problem is in the GTK theme used, and not in LibreOffice itself. Chiyaruka, can you confirm this? Do you have this problem with other applications?
Comment 4 Chiyaruka 2013-01-31 12:51:24 UTC
Created attachment 73990 [details]
Apache OpenOffice
Comment 5 Chiyaruka 2013-01-31 12:52:03 UTC
Created attachment 73991 [details]
OpenOffice.org
Comment 6 Chiyaruka 2013-01-31 12:55:12 UTC
Hello, Thank you for your comment.
I was inverted in the Apache OpenOffice and OpenOffice.org.
There is no problem in other applications.
Comment 7 tommy27 2013-12-28 22:34:53 UTC
are you still seeing this issue with current LibO 4.1.4.2?
Comment 8 Robinson Tryon (qubit) 2014-02-04 14:55:38 UTC
(In reply to comment #7)
> are you still seeing this issue with current LibO 4.1.4.2?

Status -> NEEDINFO
Comment 9 QA Administrators 2014-09-03 21:32: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: 
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 10 QA Administrators 2014-10-05 22:59:49 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