Created attachment 59326 [details] There is a screenshot in attachment Problem description: After updating (in debian sid) from the version 3.4.6 into 3.5.2 I cant see the letters in menues and dialogs (empty spaces instead) Steps to reproduce: 1. sudo aptitude update && sudo aptitude upgrade 2. start libreoffice I tried to reinstall libreoffice (also with the full deinstallation and configuration directories removing) - the result was the same. Platform (if different from the browser): Debian sid x86_64 Browser: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.3) Gecko/20100101 Firefox/10.0.3 Iceweasel/10.0.3
Do you have desktop composition on?
NOT reproducible with "LibreOffice 3.5.2.2 German UI/Locale [Build-ID: 281b639-6baa1d3-ef66a77-d866f25-f36d45f] on German WIN7 Home Premium (64bit), seems to be Linux related. @Eric: If Urmas' hint does not lead to the roots, please add information - concerning your OS (Language) - concerning your LibO localization (UI language, Locale setting) -- Does a change to English UI help? - I doubt that there is a relation, but as act of desperation: does renaming of User Profile help?
When I switched compositing off, the problem disappeared. Thanks for idea! In compositing mode (either Compiz or Metacity) the problem exists.
> ...please add information > - concerning your OS (Language) Debian sid (russian locale) > - concerning your LibO localization (UI language, Locale setting) > -- Does a change to English UI help? I tried both in russian and english locales (also using LANG=en prefix) > - I doubt that there is a relation, but as act of desperation: does renaming > of User Profile help? I tried in several logons and also tried to remove LO configuration directory at all.
Here is the workaround: http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1006476.html
@Rene: Is there something to be done in LibO or is this NOTORUBUG (see Comment 5)?
I think there is nothing to do in LO, because the problem was gone.
(In reply to comment #7) > I think there is nothing to do in LO, because the problem was gone. Thanks for your feedback :-). Lets mark it as RESOLVED WORKSFORME then. Kind regards, Joren