A user can make LibreOffice unusable by mistyping 1. Open any LibreOffice application 2. Select Tools -> Options -> LibreOffice -> View 3. Write 100?0 to scaling field (You can use any incorrect character instead of “?”, for example, wrong decimal separator) 4. Press OK Scaling is set to 400%. LibreOffice interface become unusable (at least for 1280x1024 screen resolution). I think it would be great to show a warning if a user tried to input not a number into the field. In LibreOffict 3.5 it was not a problem, because it has much less scale range, hence, the scale become 130% and a user can open the dialogue and fix his mistake. In LibreOffice 4.3 - 5.0 it is frustrating. Workaround: Open a file with the configuration in a text editor (in my case (Debian Jessie) the file is ~/.config/libreoffice/4/user/registrymodifications.xcu). Find and delete the string <item oor:path="/org.openoffice.Office.Common/View"><prop oor:name="FontScaling" oor:op="fuse"><value>400</value></prop></item>
On pc Debian x86-64 with master sources updated 2 days ago, I could reproduce this. Here are some code pointers: http://opengrok.libreoffice.org/xref/core/svtools/source/config/apearcfg.cxx#125 http://opengrok.libreoffice.org/xref/core/cui/source/options/optgdlg.cxx#807 but I'm recognize I'm a bit stuck: (gdb) p *m_pBody $10 = {... mpIMEInfos = 0x0, maText = "400 %", maPlaceholderText = "", maSaveValue = "", ...0x68006f8} (gdb) bt #0 0x00002aaab196db54 in rtl::Reference<Edit>::get() const (this=0x67fde78) at /home/julien/compile-libreoffice/libreoffice/include/rtl/ref.hxx:142 #1 0x00002aaab1b52672 in VclPtr<Edit>::operator bool() const (this=0x67fde78) at /home/julien/compile-libreoffice/libreoffice/include/vcl/vclptr.hxx:187 #2 0x00002aaab1b82344 in Edit::GetText() const (this=0x67fdc10) at /home/julien/compile-libreoffice/libreoffice/vcl/source/control/edit.cxx:2700 #3 0x00002aaab1bafcf3 in MetricFormatter::GetValue(FieldUnit) const (this=0x67fe018, eOutUnit=FUNIT_NONE) at /home/julien/compile-libreoffice/libreoffice/vcl/source/control/field.cxx:1517 #4 0x00002aaab1bafe86 in MetricFormatter::GetValue() const (this=0x67fe018) at /home/julien/compile-libreoffice/libreoffice/vcl/source/control/field.cxx:1539 #5 0x00002aaadfa4e042 in OfaViewTabPage::FillItemSet(SfxItemSet*) (this=0x67d7460) at /home/julien/compile-libreoffice/libreoffice/cui/source/options/optgdlg.cxx:809 I don't know where this "400 %" comes from.
As far as I understand, LibreOffice just ignores incorrect characters in the field. Hence, if a user types wrong decimal separator, it gets 1000 instead of 100.0 and uses max possible value 400%. Anyway, the behaviour has not appeared in 5.1. Even LibreOffice 3.5 interprets wrong characters this way. So, I change version to older one.
Alexandr: just for curiosity, where do you see "1000"?
Julien, it is my guess. If I type 1?23 I get 123%. If I type something more than 400, I get 400%. So if I type 100?0 (where "?" can be a wrong decimal separator), it would be interpreted as 1000.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
close as WONTFIX because scale options were delete from GUI