Bug 49816 - CONFIGURATION: Crash after clicking on any item under Language Settings in Options
Summary: CONFIGURATION: Crash after clicking on any item under Language Settings in Op...
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
Master old -3.6
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2012-05-11 13:02 UTC by Eric Bright
Modified: 2013-09-24 02:06 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Bright 2012-05-11 13:02:07 UTC
Problem description: 
LOdev crashes if you want to change any of the settings under Language Settings in Options. The Developers' nightly crashes while the official release works fine. 

Steps to reproduce:
1. Open LibreOffice (a new document or by clicking on the generic LOdev icon)
2. Open the Options dialogue box
3. Click to expand the Language Settings
4. Click on any item under Language Settings, such as Languages, Writing Aids, Complex Text Layout

Current behavior:
It crashes at this point!

Expected behavior:
It must open the setting without crashing.

Platform (if different from the browser): 
LOdev Version 3.6.0alpha0+ (Build ID: bdbd8d8)
Windows 7 Ultimate SP1              
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/15.0 Firefox/15.0a1
Comment 1 s-joyemusequna 2012-05-12 01:30:38 UTC
Works for me. Tested with LOdev 3.6 (2012-05-10) version 3.6.0alpha0+ (Build ID: 9980e69) from Win-x86@6-fast under Windows Vista 64.
Comment 2 Eric Bright 2012-05-12 09:44:52 UTC
Any idea how to narrow down the cause on my system? It happens consistently and no matter how I install the application.
Comment 3 manj_k 2012-05-12 15:41:38 UTC
Works for me (on WinXP 32b) w/ LibO-Dev_3.6.0alpha0
Win-x86@6-fast
pull time 2012-05-11 21:40:19
core:7327195602e7870e20a4eebb8ea26ae7294f065b.

@lucifer@ulmail.net
You might reset your user profile.
Comment 4 manj_k 2012-05-13 10:35:22 UTC
(In reply to comment #3)
> 
> @lucifer@ulmail.net
> You might reset your user profile.

Sorry, should be:
You might reset your LibreOffice user profile.
Comment 5 Roman Eisele 2012-05-14 08:42:43 UTC
Works for me with LOdev version 3.6.0alpha0+ (Build ID: e3bc45b; dated 2012-05-13) on MacOS X 10.6.8 German UI.

But I had the same problem some weeks ago on MacOS X, if I remember correctly with the Master build dated 2012-04-14. Using a newer Master build, 2012-04-20, the problem went away again. I could never figure out what caused these crashes (deleting the LibreOffice user profile did NOT help!); they seem to come and to go. Maybe using just a newer Master build helps you, too?
Comment 6 Eric Bright 2012-05-14 12:21:56 UTC
Roman Eisele, my problem is almost identical to what you described (though yours happened on a MacOS X). deleting the user profile did not help, nor did any other measure I took to have a clean/fresh install.
Comment 7 Roman Eisele 2012-05-15 02:37:42 UTC
(In reply to comment #6)
> Roman Eisele, my problem is almost identical to what you described (though
> yours happened on a MacOS X). deleting the user profile did not help, nor did
> any other measure I took to have a clean/fresh install.

I agree, but I'm sorry that this does not help you much: for me, the problem just went away again with another Master build ...
Comment 8 Caolán McNamara 2012-05-30 06:45:56 UTC
A crash like this on MacOSX is related to the installation of some version of Free Sans and appears to crash in MacOSXs own font code, This one though is on windows, so quite probably different. Nevertheless any fonts installed that didn't come pre-installed by Windows itself ?
Comment 9 Eric Bright 2012-05-30 13:47:43 UTC
Dear Caolán McNamara, thank you for your insights into the possible problem. I am going to check out my system to see what other fonts I have installed on it. Though, I can tell you that I am very careful with installing fonts on my system and I don't do it unless I's absolutely necessary (I regularly check my font folder and uninstall any font that is not installed by myself).

As for a free Serif font, I can tell you, off the top of my head, that I have Fontin installed (you can see it here: http://www.exljbris.com/fontin.html ). I don't recall having any other free Serif font on my system that did not already come with the OS. Nevertheless, I am going to check it out and will report back to you soon.

Again, thank you for following up with this issue.
Comment 10 Eric Bright 2012-05-30 14:31:55 UTC
My mistake! Fontin is a free, san serif, not a serif. I'll see what Serif fonts I have and will get back to you (I actually have a few Serif fonts installed by myself).

Regards.
Comment 11 Eric Bright 2012-05-30 15:39:25 UTC
Here is the list of the installed fonts on my computer:

https://docs.google.com/open?id=0B9jITfwK9rUnYWlFbE5HQXhCZjg

By the way, I reinstalled my Windows 7, and installed this version of LibO:

http://dev-builds.libreoffice.org/daily/Win-x86@6-fast/master/2012-05-25_07.27.31/

And it still crashed exactly the same as before.
Comment 12 Caolán McNamara 2012-06-06 03:16:57 UTC
fwiw, when I said "free serif" I meant http://en.wikipedia.org/wiki/Free_UCS_Outline_Fonts a font literally named "Free Serif". Clearly if it happens after a fresh install of OS, its hardly likely to be that after all.
Comment 13 Caolán McNamara 2012-07-12 13:24:02 UTC
There are some Microsoft Office fonts listed there. So, just in case, I installed those fonts as well on my windows instance, but (it was a long shot anyway) it persists in working fine for me without any crash. So I got nothing to make a stab at a guess for as to why it persists in working fine for me with the English UI.
Comment 14 bfoman (inactive) 2012-11-05 12:22:03 UTC
Is this still an issue in the latest 3.6 master?
Comment 15 Eric Bright 2012-11-06 06:55:44 UTC
I don't know, even if it is still an issue. I have no way to test the same issue since I changed my OS from Win 7 to Win 8.
Comment 16 QA Administrators 2013-07-18 06:16:08 UTC
Dear Bug Submitter,

Please read the entire message in its entirety before continuing - also please respond directly to FDO when replying - do not reply via email.

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 17 QA Administrators 2013-09-24 02:06:37 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