Hi! Today i tried to install OpenOffice 2.0. I use the apt (Synaptic). I got one warning about libs and i ignore. After installation i run KDE but there were no screen. I heard a sound, mouse works but i got just a gray screen. Anybody has a same problem? Is this official OpenOffice from SuSE? Thanks, Mitja
ajtiM wrote:
Hi!
Today i tried to install OpenOffice 2.0. I use the apt (Synaptic). I got one warning about libs and i ignore. After installation i run KDE but there were no screen. I heard a sound, mouse works but i got just a gray screen. Anybody has a same problem? Is this official OpenOffice from SuSE?
I had the same on 3 different machines - unrelated to OpenOffice though (I was already running the latest OOo long before this started happening). I rolled things back to the DVD versions, and the problem didn't go away until I reset all of KDE (including qt) back to 3.4.3, and fontconfig back to 2.3.2. If you drop to init 3, and then as user run startx, you'll see loads and loads of errors scrolling by. Problems with kded, and other core KDE components. My suggestion (based on my own experience) is to try rolling font config back to 2.3.2, and if that doesn't help, do the same for qt and KDE. Ummm second comment... if you're getting warnings about libs when you're installing applications, you shouldn't really just ignore. The warning is there for a reason... something is not right. You should try to solve the warnings BEFORE you continue... or you end up with broken packages, missing libs etc etc. C.
Am Dienstag, 25. Oktober 2005 07:49 schrieb Clayton:
ajtiM wrote:
Hi!
Today i tried to install OpenOffice 2.0. I use the apt (Synaptic). I got one warning about libs and i ignore. After installation i run KDE but there were no screen. I heard a sound, mouse works but i got just a gray screen. Anybody has a same problem? Is this official OpenOffice from SuSE?
I had the same on 3 different machines - unrelated to OpenOffice though (I was already running the latest OOo long before this started happening). I rolled things back to the DVD versions, and the problem didn't go away until I reset all of KDE (including qt) back to 3.4.3, and fontconfig back to 2.3.2.
If you drop to init 3, and then as user run startx, you'll see loads and loads of errors scrolling by. Problems with kded, and other core KDE components.
My suggestion (based on my own experience) is to try rolling font config back to 2.3.2, and if that doesn't help, do the same for qt and KDE.
Well, if you want to stay with fontconfig-2.3.91 you have to run fc-cache -f after installing fonts, as there is some bug in fontconfig. Its symptom is crashing every X application. As far as I know, OpenOffice 2.0 installs some fonts, therefore you should run fc-cache afterwords. Klaus
Well, if you want to stay with fontconfig-2.3.91 you have to run fc-cache -f after installing fonts, as there is some bug in fontconfig. Its symptom is crashing every X application. As far as I know, OpenOffice 2.0 installs some fonts, therefore you should run fc-cache afterwords.
Ahhh... that would explain why everyone is having problems with the latest fontconfig update from apt. Not knowing that you should run fc-cache is a HUGE handicap though. There will be a lot of people with broken GUIs in the next couple of days. :-( Can't this fc-cache -f be included as part of the RPM the same way config is done when you install a kernel RPM? Wonder if the maintainer of fontconfig could add that in? (I don't know enough about how RPMs work to know if this is possible... just asking) C.
On Tuesday 25 October 2005 09:46, Clayton wrote:
Well, if you want to stay with fontconfig-2.3.91 you have to run fc-cache -f after installing fonts, as there is some bug in fontconfig. Its symptom is crashing every X application. As far as I know, OpenOffice 2.0 installs some fonts, therefore you should run fc-cache afterwords.
Ahhh... that would explain why everyone is having problems with the latest fontconfig update from apt. Not knowing that you should run fc-cache is a HUGE handicap though. There will be a lot of people with broken GUIs in the next couple of days. :-(
Can't this fc-cache -f be included as part of the RPM the same way config is done when you install a kernel RPM? Wonder if the maintainer of fontconfig could add that in? (I don't know enough about how RPMs work to know if this is possible... just asking)
Adding workarounds usually leads to the fact that the bug never gets fixed, so we avoid this usually and better keep the bug visible. fc-cache -f would also increase the runtime of SuSEconfig.fonts heavily. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de
Adding workarounds usually leads to the fact that the bug never gets fixed, so we avoid this usually and better keep the bug visible.
fc-cache -f would also increase the runtime of SuSEconfig.fonts heavily.
Fair enough... that makes sense, but... then that makes me ask... why was the broken fontconfig released to the apt repositories then? Has it been pulled? If not it should be... and right away. I can deal with removing a buggy/broken fontconfig, or if I know I need to, manually running fc-cache, but... what about all the new users? On the SLE list a guy ran into this, and all of his X apps were crashing (like mine were) and he was so frustrated he is at the point where he is ready to throw in the proverbial towel and return to Windows. I've replied to his posting and pasted in Kaus' workaround solution... but... this is a pretty significant bug considering that it crashes all X applications. I can only wonder how many new users tried out apt, did an update, figured they trashed their install... and either have to reinstall (because they don't know to run fc-cache) or they return to Windows.... :-( C.
participants (4)
-
Adrian Schroeter -
ajtiM -
Clayton -
Klaus Hartmann