Bug 80624 - BUG related to UniversalAccess Setting: Large Font in Libreoffice Calc
Summary: BUG related to UniversalAccess Setting: Large Font in Libreoffice Calc
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2014-06-28 09:23 UTC by nicolay bohn
Modified: 2015-09-04 03:01 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

spreadsheet with full description (20.62 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-06-28 09:23 UTC, nicolay bohn

Note You need to log in before you can comment on or make changes to this bug.
Description nicolay bohn 2014-06-28 09:23:37 UTC
Created attachment 101910 [details]
spreadsheet with full description

When the Universal Access setting Large Text is turned on
(in Fedora 19) cells may cease to display their content,
and act as if they were empty.
A full description is shown in the spreadsheet adjoined.

Also a bug in the customize keyboard dialog where everything
is a MESS and nothing works!
Comment 1 Robinson Tryon (qubit) 2014-12-24 03:58:41 UTC
Comment on attachment 101910 [details]
spreadsheet with full description

Fix mimetype
Comment 2 raal 2014-12-28 16:11:13 UTC
please 1 bugreport = 1 bug. Please provide test document and screenshots for "BUG related to UniversalAccess Setting: Large Font in Libreoffice Calc"

In your file is written:
Note: I use Fedora rel 19 and also use Large Text on the Universal Access Settings;
which in some cases may cause malfunction in combo-boxes and lists because the
size of the font is not correctly calculated.
(when I turned off Large Text, the behaviour returned (it seemed) to normal.)

I tested UniversalAccess Setting:Large text on Ubuntu 14.10 with LO Version:
Build ID: 7f476fea47f06a7f8cc961dd4f6595a524346fa5
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-12-27_23:36:28 and I doesn't see any problems with combo box.

Also please retest with actual version of LO 4.3.5

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 3 QA Administrators 2015-07-18 17:36:27 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!

Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-07-18
Comment 4 QA Administrators 2015-09-04 03:01:44 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-09-03