Thanks for the rapid response.
[AS]
> > Summary: it seems that either replacing 64 bit LO with 32 bit LO, or
> > installing a later version of LO, or both, allowed, me to get LO
> > working in my 32 bit ctwm, including colour menus. So I don't need
> > to switch to OpenBox!
[MF]
> I'm pretty durn sure bittiness of apps vs window managers can't have
> any effect on anything. The two don't call or link to each other at
> all, they only communicate via properties set in the X server. So, I
> wouldn't waste any skull-sweat on angling for that herring.
>
> I'd tend to doubt that the bittiness of LO has any real effect either.
> The toolchain issues you're having do point at _something_ being
> marfed up on 64 that isn't on 32, but it strains the crap out of
> credibility to imagine a way it could be messed up that would work
> fine, except for pulling up those dialogs.
Well, it seems I was misled by these error messages
> > (soffice:30121): Gdk-WARNING **: GdkWindow 0x480187f unexpectedly destroyed
> >
> > (soffice:30121): GLib-GObject-WARNING **: invalid unclassed pointer in cast
> > to 'GtkWidget'
which vaguely reminded me of past errors associated with 32bit vs 64bit code.
People who invoke things like LO from menus would not see those, which may be
why google search did not take me to helpful information. Being a mouse-hater I
do almost everything at the command line in xterm windows (using keyboard to
start up and switch between xterm windows, or desktops) which is why I like
ctwm so much.
Anyhow, it was simple to test your theory. I installed LO v5 on my laptop, also
running F22, but 64 bit rather than 32 bit version as done last night on the
desktop PC.
You'll be delighted to hear that on the laptop the colour menus in 64 bit LO v5
work perfectly. Moreover, I don't get this on the laptop:
javaldx: Could not find a Java Runtime Environment!
Warning: failed to read path from javaldx
> So, I'd guess it's just the version that's the determinant.
It seems you are right.
So I'll now get rid of the 32 bit stuff I installed on the desktop machine and
just use 64bit LO on both.
> You might look at flipping around the various *Transient options of
> ctwm, on the off chance that something in them ties in with the issue
> (since I'd assume those are transient windows it's trying to pop up).
I think I had tried things like that previously without success. But the
LO developers have solved the problem.
Thanks!
Aaron
