On Thu, May 16, 2013 at 01:11:28PM -0400, Chris Siebenmann wrote:
>  There was a recent change (April 14th) to FvwmIconMan's source code
> to, to quote the changelog:
>         * FvwmIconMan/x.c (change_colorset, recreate_background)
>         (create_manager_window):
>         fix bad hilight colour on some systems (64 bit issue?)
> 
>  Unfortunately on my machine[*] the effect is exactly the opposite: this
> change destroys the correct colours in my FvwmIconMan setup. In fact it
> appears to do very odd things. I've produced two PNGs to illustrate:
>       http://www.cs.toronto.edu/~cks/fvwm-test/fvwmiconman-good.png
>       http://www.cs.toronto.edu/~cks/fvwm-test/fvwmiconman-bad.png

Yes, that's very similar to what I had.  My problem is that I
don't understand at all why my patches work on that X86-64
machine, I just fiddled with the code until it worked, hoping not
to break something.  Actually, both version of the code should
work everywhere, but obviously they don't.

> I don't set a general FvwmIconMan foreground or background colour.
> Setting them explicitly doesn't fundamentally change the results; the
> only net effect is that the iconified 'xterm1' FvwmIconMan button
> doesn't have the grey cast it does in the -bad PNG here.

That's the same observation I made on that bad machine.  Setting
the background colour of the focused button had no effect
whatsoever.  I moved the code that sets the colour around in the
source files, and at _some_ location it worked, but not in others,
although the background colour was not overwritten anywhere.

>  I can easily test patches/changes if people would like.

That will help a lot.  Pinnig the problem down is probably going
to be difficult.

> [*: my machine is 64-bit Fedora 18 with an ATI graphics card and the
>     normal Fedora 18 open source drivers. These particular screenshots
>     are from an Xephyr session, but I first saw the effect on the real
>     display.]

So, you have a 64-bit CPU with a 64-bit version of the OS?  What X
server do you have (version?).  

Can you please post the output of

  $ ldd /path/to/fvwm2

and a minimal fvwm configuration file that shows your problem?

P.S.:  Do you read the list, or should I cc you on replies?
P.P.S.:  Please do _not_ cc me unless I specifically ask for it.

Ciao

Dominik ^_^  ^_^

-- 

Dominik Vogt

Reply via email to