Summary: | Consistent crash with Linux Libertine G font and Spanish locale | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | RGB <rgbl> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | critical | ||
Priority: | medium | CC: | gleppert |
Version: | 3.4.0 Beta2 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 34420, 35673 |
Description
RGB
2011-04-22 13:51:57 UTC
. addded myself to cc. Testing this issue on my system. Admittedly in a completely different test environment: LibreOffice PPA 3.3.2 on Ubuntu 10.4 Intel 32bit. German Language environment. Here, I cannot confirm this issue. Problem still present on beta 3. This time tested on openSUSE 11.4 64 bits. English UI → OK Spanish UI → Crash. I can reproduce it on Windows XP with LibO 3.4 beta 3. More info soon. It seems, it's the same problem, as in the Bug 36703. Replacements of the "Qu" and some other ligatures halt LibreOffice with the new Graphite 2 (Issue 34420). (In reply to comment #5) > It seems, it's the same problem, as in the Bug 36703. Replacements of the "Qu" > and some other ligatures halt LibreOffice with the new Graphite 2 (Issue > 34420). They seem related... but on this issue there is also a correlation with the language UI: with English UI, no crash, same procedure with Spanish UI, crash. It is quite complex scenario, so it will not affect all users => should not block 3.4.0 release. Anyway, it might affect quite some users => adding to the list of most annoying bugs. OK (silly me!): the reason because the autotext makes Writer crash only with Spanish UI is that the Spanish version of the autotext contains the Qu ligature while the English version do not. László Németh is right: this issue is a duplicate of the other issues related with Libertine G problems. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.