Re: New Bug - libwnck Isn't The Problem

Tony Houghton wrote:
> On Sat, 18 Sep 2010 22:21:54 +0100
> Mark Williams<[email protected]>  wrote:
>
>> It's definitely python-wnck. Tasklist depends on lib-wnck and that runs
>> fine. Tasktray depends on python-wnck and that generates the windows
>> state error message.
>
> The problem was that the GObject type used for some constants didn't
> match the type the python bindings thought they should be. The bug was
> in libwnck, not in python-wnck, because the python bindings were right
> about what the type should be and libwnck had it wrong, but to C
> programs it didn't matter which type was used.
>
> If you patched python-wnck and started using a newer, fixed libwnck,
> that would create the problem in reverse but with identical symptoms. I
> think libwnck 2.30.0 was the release that fixed it, so if you're using
> that or newer make sure your python bindings are up to date and *not*
> patched.
>
It doesn't matter what I do the bug remains. I've tried everything from 
getting rid of all instances of libwnck and then reinstalling it from 
the Synaptic to reinstalling the entire OS. But still that bug pops up.

I really have no idea what could be causing it. It's very frustrating.


------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev