Am Sonntag, den 26.02.2012, 20:24 -0600 schrieb Ranjan Maitra:
On Mon, 27 Feb 2012 11:10:03 +0900 nomnex <nomnex(a)gmail.com>
wrote:
> > On Sun, 26 Feb 2012 18:07:16 +0100
> > Christoph Wickert <christoph.wickert(a)googlemail.com> wrote:
> >
> > will get an update to lxpanel 0.5.8 though (already in
> > updatest-testing for a while).
>
> Does it address the freeze issue?
Which bug are you referring to? There are so many... :(
Is it available on F-15? Else, can
> you backport it, once it is in in the stable F-16 repos.
It will be available for F15, too once it's in F16.
I don't know: I am also interested in lxpanel2 for this (among
other
reasons). I don't understand why it is a good idea not to move to
lxpanel2, since lxpanel has for all practical purposes, ceased
development. Of course, Christoph is more knowledgeable about these
issues than many others including me, so I am sure that he has very good
reasons to do so.
Idea/question: Is it possible to also package lxpanel2, for some of us
to try it, upon changing whatever else requires changing?
It is possible but I don't want to package a fork that vanishes later.
There are two different forks (lxpanel2 and lxpanel+), which one is the
right one? We only can make this decision if one of them becomes
upstream LXDE.
Switching to lxpanel2 means we need to modify the lxde-common package
and comps. I am not going to do this for a fork as long as the future is
unclear.
Kind regards,
Christoph