Created attachment 76664 [details] Screenshot showing an example After using LibO Impress and Writer, some words start to behave strange, and characters disrupt around the line. Up to now, I has happened only with headers (Writer) and title (Impress). The screenshot will clarify what I get. Sorry for not being able to select a better title for the bug, I can't explain what's happening better than what I see. I'm sorry also for not being able to give you how to reproduce the bug... it just happens some times after using LibreOffice 4 for a while. But since I got that error with 2 different programs I though it would be useful to fill this bug. For the record: I have found this just with "Open Sans Light", and "Charis SIL compact", both fonts installed by me.
Oops... OS: Kubuntu 12.04 64bits LibO packaged downloaded from official site.
Which official site? It is highly recommended that you stick with your distributions repository version so is this the official version you're running? Or did you download directly from LibreOffice's site?
Also, please provide more information. When this happens, if you save the document, close it and reopen it, are the fonts still messed up? Does it happen mostly with particular fonts? What locale are you using? Marking as NEEDINFO. Once you provide additional information please set status to UNCONFIRMED. Just this isn't enough to triage the bug so we need to track down the root of the issue.
Hi Joel > Which official site? LibreOffice site, I downloaded it directely > It is highly recommended that you stick with your distributions repository > version I use the version downloades from the official site for 2 reasons: 1º Ubuntu version is not dealing well with the menu bar in KDE, at least, in Kubuntu 12.04 with KDE 4.8.4 2º I use LibO 3.5 for production, and that's what I have installed by default because I want a lot of stability and reliability, some things I cannot get with LibO 4. So, I occasionally use LibO 4 for some production works > Also, please provide more information. When this happens, if you save the > document, close it and reopen it, are the fonts still messed up? Yes, sorry, I totally forgot to add that: I have to close ALL the running instances of LibO 4 to get them correctly working. Once done this, All fonts return to their place. > Does it happen mostly with particular fonts? Can't say. It has happened up to yesterday, with the fonts I've already mentiones (Open Sans Light and CHaris Sil compact). But it has happen in 2 different computers with 2 different versions of LibO 4: 4.0.0 and now with 4.0.1 > What locale are you using? spanish > Just this isn't enough to triage the bug so we need to track down the root > of the issue. I understand that, but I though it is conveniently to have it already filled
This bug happens for me if I install a font while having LibreOffice open (I use Ubuntu 13.04 & LibO 4.0.1). Francisco, do you remember if you installed the fonts having LibreOffice open? And what other program showed this issue?
@(In reply to comment #5) > This bug happens for me if I install a font while having LibreOffice open (I > use Ubuntu 13.04 & LibO 4.0.1). Francisco, do you remember if you installed > the fonts having LibreOffice open? And what other program showed this issue? Hi Fitoschido. No, that isn't my case, I have had these fonts already installed for some time.
> And what other program showed this issue? ...and I cannot remember other program showing this particular behavior except Impress and Writer.
So far: 1) Only happens with OpenSans Light (Open Sans in the same presentation look OK) 2) When a program is affected, other instances of LibO are affected too. For example: I hape Impress and Draw already opened. They were working 0K. After just inserting and image,texts in OpenSans Light in both programs are crazy.
Ooops, noup. Open Sans (Regular) is also not-good :-/
Well, I'll try to rename the OpenSans version inside the libreoffice folder "/LibreOffice4.0/share/fonts/truetype/" And see what happens...
(In reply to comment #10) > Well, I'll try to rename the OpenSans version inside the libreoffice folder > > "/LibreOffice4.0/share/fonts/truetype/" > > And see what happens... Noup, that didn't help. But this time, I opened Writer, typed some random words in OpenSans Light, and they looked 0K... :-/
Created attachment 76955 [details] Same behavior in Writer 4, using Linux Libertine G Today it has happened with Linux Libertine G, manually instaled.
For the record. It only has happened when I change the focus to another application, and then comeback to LibO 4
I'm confirming the bug. I see this on different fonts in Impress and Writer. Sometimes it hapens, sometimes it doesn't. If I close LO and then reopen the files everythig looks good. I use 4.0.2.1.
@ Cunio What system/platform are you using?
Is this bug a duplicate of bug 60565?
(In reply to comment #16) > Is this bug a duplicate of bug 60565? Not sure. The result is pretty similar, but this happens any time when changing the focus of the application, not while installing fonts. Although, it has happen with manually installed fonts if I remember correctly.
Created attachment 77233 [details] Calc affected This is getting more weird. Working with a Calc spreadsheet, I noticed some strange behavior on fonts: many of them appear as bold after changing focus of the application. But up to now, the typeface was always the same. Now, it shows a different typeface than the selected as the screenshot shows. It should be Ubuntu while it's showing Droid Serif. The strange part came when I change scale: after zooming in, the typeface shown came back to Ubuntu. When I did scale it to 100%, it came back to Droid. The most weird part was, after taking the screenshot attached (zoom 100%), I was going to take a screenshot of Calc at larger zoom... but now it shows correctly Ubuntu typeface.
This bug is happening with any installed font. Today, it has happen using Liberation Serif with LibO 4.0.2 downloaded from "www.libreoffice.org/download". One more interesting thing is that after characters appeared disrupted, I draw a line over disrupted text and then it turned back... or at least, it respected page margins, with characters forming understandable words, but the looked somehow "too hinted"
(In reply to comment #17) > (In reply to comment #16) > > Is this bug a duplicate of bug 60565? > > Not sure. The result is pretty similar, but this happens any time when > changing the focus of the application, not while installing fonts. Although, > it has happen with manually installed fonts if I remember correctly. In other words, if this bug is a dup of bug 60565, then the problem with the second one doesn't need to install/remove any font while having LibO open.
For now I am marking as NEW as several independent confirmations have happened. Also adding Michael to see if he has any advice on where to go from here. Michael - any ideas on this one? Seems quite serious and affecting multiple components - think it's a dupe of bug 60656?
This bug is still present in v 4.0.3.
Lubos - any quick thoughts / pointers on this font oddness ? :-) I wonder if your font embedding work improved this for 4.1 ? Francisco - it's a long shot (most of the font code is shared) - but it might be KDE related memory corruption; can you do (from a console): pkill -9 -f soffice.bin SAL_USE_VCLPLUGIN=gen soffice and see if you can reproduce it ? What are the steps to reproduce it even ? If you're moving fonts around in folders - that's rather like installing them I suspect, so yes, most prolly a dup of bug#60565
Hi Michael. > Francisco - it's a long shot (most of the font code is shared) - but it > might be KDE related memory corruption; can you do (from a console): > > pkill -9 -f soffice.bin > SAL_USE_VCLPLUGIN=gen soffice > > and see if you can reproduce it ? What are the steps to reproduce it even ? > If you're moving fonts around in folders - that's rather like installing > them I suspect, so yes, most prolly a dup of bug#60565 You mean, when this problem appears, right? (sorry, maybe a dumb question I need to know). But, if that's all you need, I will :-)
Two questions really: a) does it still appear without a gnome (or KDE) backend enabled ? that's what the kill / environment variable stuff does. b) what do you do in the suite: starting from a blank (or attached) document - to make it go this badly wrong? :-) - without being able to reproduce it it's really hard to fix your issue. Thanks !
(In reply to comment #25) > Two questions really: > a) does it still appear without a gnome (or KDE) backend enabled ? that's > what the kill / environment variable stuff does. I didn't try. I couldn't even imaging it. I'll see then. > b) what do you do in the suite: starting from a blank (or attached) > document - to make it go this badly wrong? :-) - without being able to > reproduce it it's really hard to fix your issue. Both, really. I mean, starting with a new/blank document and also, working with an already existing document. Yesterday at night, it took just some minutes to happen. Now, it's been arround one hour opened, and it hasn't. I'll continue trying.
Well, I have manage to reproduce it again, after 1 day. But the problem with this was when I executed "SAL_USE_VCLPLUGIN=gen soffice", LibreOffice 3.5 was the one to be opened, and not 4.0. Then, I could open LibreOffice 4.0, and of course, it looked like the old Windows theme... but nothing else. Of course, all the characters are again in their place, but that was the case when I closed LibO and opened it again. Should I wait with this "theme" after the problem appears again?
...and just now, I realized that I misunderstood what you ask me :-/ Sorry. Well, I'll try to reproduce it again
> Well, I have manage to reproduce it again, after 1 day. But the problem with > this was when I executed "SAL_USE_VCLPLUGIN=gen soffice", LibreOffice 3.5 was > the one to be opened, and not 4.0. Drat - of course, there could be any number of issues with 3.5 that are hard to track and fix, so ... we love testing of 4.0 :-) > Then, I could open LibreOffice 4.0, and of course, it looked like the old > Windows theme... but nothing else. Good - I wonder if you could make it go wrong like that ? if you cannot, but you can with the KDE backend, then I suspect some issue with that backend - but it's unlikely of course. > Should I wait with this "theme" after the problem appears again? Just waiting is not the best approach ;-) what is really needed is finding a way to trigger the problem that is quick - so with 10 steps from a blank (or attached) document the problem can be triggered. If it takes a long time to do - it's either memory corruption; or - you have some cron-job / rsync or something that touches your font configuration (I guess) which makes this a dup of bug#60565 :-) Thanks !
> Drat - of course, there could be any number of issues with 3.5 that are hard > to track and fix, so ... we love testing of 4.0 :-) Well, I know xD the point was that I have LibO 3.5 installed. But I said that because I misunderstood your previous message. > Just waiting is not the best approach ;-) what is really needed is finding a > way to trigger the problem that is quick - so with 10 steps from a blank (or > attached) document the problem can be triggered. > > If it takes a long time to do - it's either memory corruption; or - you have > some cron-job / rsync or something that touches your font configuration (I > guess) which makes this a dup of bug#60565 :-) > > Thanks ! Well, yes, that's the way it happens: changing the focus of the app, or waiting. In any case, it's gnome backend fault, not the KDE one.
@Francisco - apologies in advance if this is wrong but reading through comments I don't see independent confirmation so moving back to UNCONFIRMED. Someone other than you should move it to NEW (ie. a second person who can verify the problem)
(In reply to comment #31) > @Francisco - apologies in advance if this is wrong but reading through > comments I don't see independent confirmation so moving back to UNCONFIRMED. > Someone other than you should move it to NEW (ie. a second person who can > verify the problem) The confirmation was told on comment #14, by Cunio.
...But, since I'm not able to reproduce this bug without using the GNome backend, I'm also thinking it's a dup of bug 60565
Lets treat this as a duplicate, at least until the other bug is fixed then. Thanks ! :-) *** This bug has been marked as a duplicate of bug 60565 ***
I'm reopening this bug, since the problem still persist in LibO 4.0.5 and LibO 4.1.0, though the screenshot I'm uploading is only from 4.1 version. If this bug is still a duplicate if bug 60565, please close this and reopen that one.
Created attachment 84621 [details] screenshot with disrupted characters in Writer 4.1.0 Again, I've been able to reproduce this bug using the GNOME backend on KDE.
*** Bug 67640 has been marked as a duplicate of this bug. ***
I'm closing this bug since I have not been able to reproduce it since the launch of LibO 4.1, as was stated in bug 67640
(In reply to comment #38) > I'm closing this bug since I have not been able to reproduce it since the > launch of LibO 4.1, as was stated in bug 67640 Sorry, I mean 4.1.3