Apache OpenOffice (AOO) Bugzilla – Issue 16107
GNOME theme is not being used in latest builds.
Last modified: 2004-06-14 10:00:59 UTC
Seems that the getstyle-gnome program used to synchronise the GNOME theme with the theme used in SO is failing to work with the Crux theme in the Sun GNOME2.2 builds, it appears to be crashing.
sadly yes, it does
Created attachment 7220 [details] stack trace of crashing getstyle-gnome when switching to "crux" theme
it crashes somewhere deep inside gtk when loading the crux-engine; no OOo code is involved at all (stack attached). Do you know anyone who could be responsible for this ?
Off-hand, I'm afraid not. Though I'm surprised that it's GTK that's crashing since I'm using that theme all through my desktop and all applications work fine with it. I'll see if I can figure ou who to go to...
Darren, any news on that? Looking at the stack, it seems that gtk can not open the crux engine itself (/opt/gnome-2.2/lib/gtk-2.0/2.2.0/engines/libcrux-engine .so).
Updated my version of GNOME2.2 to the Accessibility build dated June 16 (previously I was using the build dated May 18). Now I don't see any crash and the theme colours are being reflected correctly in my SO install which is m8-1. I was speaking to OBR who saw the crash on June 16 build of GNOME2.2... I contact Erwann Chenede from the GNOME team here (who has experience in the operatin of GNOME's theming) and he hasn't been able to reproduce this either and he's using the build m8-1 also.
I've been in contact with OBR, who is still seeing the crash, and the understanding is that we're on the same versions of GNOME and SO, but different versions of RedHat, I'm on RH8 and OBR is on RH7.2, which AFAIK is the same as for PL. Erwann Chenede (a GNOME engineer here) thinks that there may be a mis-match between the gtk+ and the engine and that might be the cause. What worries me is that the crash is so far down the stack, in that it's in dlopen... This should not crash and there's no obvious sign of corruption in the stack trace. In this light it may be a Linux specific issue, but it's hard to be sure.
This seems to be reproducable only on a single machine. Philipp and me always logged in remotely, which might be one of the reasons why it shows up. Another reason could be that some libraries on this machine are corrupted.
I set this task to OOo 2.0. When this is only a problem of a single machine, we have to find out why. But this is not a showstopper for OOo 1.1. When we know the problem and we think it is important, we can fix it in the first product update for OOo 1.1.
After consulting with OBR and PL, we have agreed to close this bug because it's no longer relevant.
After agreement with OBR and PL it was agreed this bug is nolonger relevant for 2.0.
Closing