Kernel 2.6.39-bpo breaks tint2

[dbb <dbb008@gmail.com>]

Using the backported kernel 2.6.39-bpo.2 will break tint2:

==========
% uname -r
2.6.39-bpo.2-amd64

% apt-cache policy tint2
tint2:
  Installed: 0.9-2
  Candidate: 0.9-2
  Version table:
 *** 0.9-2 0
        500 http://ftp.us.debian.org/debian/ squeeze/main amd64 Packages
        100 /var/lib/dpkg/status

% tint2
real transparency off.... depth: 24
tint2 : another systray is running
ERROR: battery applet can't open energy_now
zsh: segmentation fault  tint2
==========

See this bug report: http://code.google.com/p/tint2/issues/detail?id=302

The only work-arounds are either to 1) use the stock 2.6.32 squeeze
kernel, or 2) disable the battery applet, which I think is one of the
more useful features of tint2.

The developers have suggested using a newer version. I attempted to
build it from source, but `apt-get build-dep tint2` failed:

==========
The following packages have unmet dependencies:
 libcairo2-dev : Depends: libfontconfig1-dev but it is not going to be installed
                 Depends: libfreetype6-dev (>= 2.1.10) but it is not
going to be installed
 libimlib2-dev : Depends: libfreetype6-dev but it is not going to be installed
 libpango1.0-dev : Depends: libfreetype6-dev (>= 2.1.3) but it is not
going to be installed
                   Depends: libxft-dev but it is not going to be installed
                   Depends: libfontconfig1-dev (>= 2.1.91) but it is
not going to be installed
E: Build-dependencies for tint2 could not be satisfied.
==========

So it seems this is a bit of a pickle. I'm not sure whether a backport
is warranted, but I can say that when I used the version of tint2 from
wheezy with 2.6.39 and 3.0.0 kernels I did not see this issue. It
seems like building this from source would be quite difficult and
possibly result in dependency hell.

--Daniel