Re: New Bug - libwnck Isn't The Problem

Abrolag <[email protected]> Mon, 25 Oct 2010 22:28:39 +0100
Newsgroups gmane.comp.desktop.rox.user
Message-ID <20101025222839.39871acf@debian>
On Sun, 19 Sep 2010 00:23:10 +0100
Tony Houghton <[email protected]> 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.

This problem seems to be finally cured with the latest updates for debian
squeeze.

-- 
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.

------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev