[debian/fso] openmoko-panel-plugin should be more patient?

Sebastian Krzyszkowiak seba.dos1 at gmail.com
Sat Jul 18 17:58:58 CEST 2009

On 7/18/09, Christian Adams <morlac at morlac.de> wrote:
> Hash: SHA1
> moinmoin,
> Am 18.07.2009 um 00:19 schrieb arne anka:
>> hi,
>> just upgraded to fso 5.5 and opp seemed to work as usual.
>> in a second step i installed fsousaged and disabled ousaged.
>> after that opp wasn't able to start up properly at boot (confusing
>> lxpanel
>> heavily).
>> killing opp and starting it manually after i registered to my provider
>> went through w/o hassle.
>> seeing that fsousaged comes up considerably later than frameworkd, i
>> guess, opp is too fast -- it should probably have more patience and at
>> least start with all icons in a disabled state, enabling them when
>> fsousaged becomes available.
> arne,
> could you take a look at xsession-errors and send me opp-regarding
> lines?
> would help to see what happend there and do something for robustness
> of opp
> cheers,
> 	christian (morlac) adams
Just fsousaged was started when openmoko-panel-plugin requested it.
opp should just try again, instead of failing.

More information about the community mailing list