Re: [debian/fso] openmoko-panel-plugin should be more patient?
-BEGIN PGP SIGNED MESSAGE- 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. will have to investigate. set in on my opp todo-list. cheers christian (morlac) adams - -- - -BEGIN CONTACT BLOCK- eMail: mor...@morlac.de Jabber: mor...@skavaer.homelinux.org - --END CONTACT BLOCK-- - -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS$/IT;d-;s:;a?;C++(+++);UL;P++(+++); L++(+++);E---;W++;N(+);o?;K?;!w;!O;!M+;!V;PS(+);PE; Y+;PGP++;t+(++);5(+)++;X(+);R*;tv-+;b++(+++);DI++; D++(+++);G(+)++;e;h-()++;r++;y++; - --END GEEK CODE BLOCK-- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFKYa8tr81gVylJyzERAmHQAKCredntPY+SubbyLbJf2HJXk05RigCeJgvn lTdATU1SaQ48lH7qKFPG1kk= =d+XM -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian/fso] openmoko-panel-plugin should be more patient?
On Saturday 18 July 2009 00:19:32 arne anka wrote: 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. I agree. When moving applications to using interprocesscommunication (such as DBus), applications need to cope with all kinds of startup and shutdown orders, as well as servers that are restarted during the lifetime. This will make apps more solid and reliable. Cheers, :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian/fso] openmoko-panel-plugin should be more patient?
-BEGIN PGP SIGNED MESSAGE- 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 - -- - -BEGIN CONTACT BLOCK- eMail: mor...@morlac.de Jabber: mor...@skavaer.homelinux.org - --END CONTACT BLOCK-- - -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS$/IT;d-;s:;a?;C++(+++);UL;P++(+++); L++(+++);E---;W++;N(+);o?;K?;!w;!O;!M+;!V;PS(+);PE; Y+;PGP++;t+(++);5(+)++;X(+);R*;tv-+;b++(+++);DI++; D++(+++);G(+)++;e;h-()++;r++;y++; - --END GEEK CODE BLOCK-- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFKYdp2r81gVylJyzERApNMAJ9eDhLmpX2+MALnKma//KUqMhWSxgCdGBBI XAFzSCZJ2Cbzfh+t+KPOO+c= =e0u1 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian/fso] openmoko-panel-plugin should be more patient?
On 7/18/09, Christian Adams mor...@morlac.de wrote: -BEGIN PGP SIGNED MESSAGE- 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. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian/fso] openmoko-panel-plugin should be more patient?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 moinmoin, Am 18.07.2009 um 17:58 schrieb Sebastian Krzyszkowiak: Just fsousaged was started when openmoko-panel-plugin requested it. opp should just try again, instead of failing. thats what it actually is supposed to do .. to know what happend there and to be able to change opp's behaviour i need logfiles (xsession-errors) .. cheers, christian (morlac) adams - -- - -BEGIN CONTACT BLOCK- eMail: mor...@morlac.de Jabber: mor...@skavaer.homelinux.org - --END CONTACT BLOCK-- - -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS$/IT;d-;s:;a?;C++(+++);UL;P++(+++); L++(+++);E---;W++;N(+);o?;K?;!w;!O;!M+;!V;PS(+);PE; Y+;PGP++;t+(++);5(+)++;X(+);R*;tv-+;b++(+++);DI++; D++(+++);G(+)++;e;h-()++;r++;y++; - --END GEEK CODE BLOCK-- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFKYgq2r81gVylJyzERAjWkAJ44nqvD59a7s1jvLZ5rV5MqhaBemgCgkKrO m/BlbFTTU8iLmlKLimRYKz4= =6dCW -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian/fso] openmoko-panel-plugin should be more patient?
Xsession: X session started for arne at Sat Jul 18 19:57:49 CEST 2009 libnotify-Message: GetServerInformation call failed: The name org.freedesktop.Notifications was not provided by any .service files INFO:root:entering dbusReInit of keyboard INFO:root:entering dbusReInit of gps INFO:root:entering dbusReInit of battery INFO:root:entering dbusReInit of bluetooth INFO:root:entering dbusReInit of buttons INFO:root:entering init for UsageInterface for gps INFO:root:resourceChanged: name: GPS state: 0 attributes: None INFO:root:entering postDisable of gps INFO:root:entering init for battery INFO:root:entering init for UsageInterface for bluetooth INFO:root:resourceChanged: name: Bluetooth state: 0 attributes: None INFO:root:entering postDisable of bluetooth INFO:root:entering init for UsageInterface for wifi INFO:root:resourceChanged: name: WiFi state: 0 attributes: None INFO:root:entering postDisable of wifi INFO:root:entering init for buttons ERROR:dbus.connection:Exception in handler for D-Bus signal: Traceback (most recent call last): File /usr/lib/pymodules/python2.5/dbus/connection.py, line 214, in maybe_handle_message self._handler(*args, **kwargs) File /usr/lib/pymodules/python2.5/panelplugin/UsageIcon.py, line 297, in resourceAvailable logging.info(resourceAvailable: name: %s available: %s % (name, available1)) NameError: global name 'available1' is not defined ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian/fso] openmoko-panel-plugin should be more patient?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 moinmoin, Am 18.07.2009 um 20:04 schrieb arne anka: Xsession: X session started for arne at Sat Jul 18 19:57:49 CEST 2009 libnotify-Message: GetServerInformation call failed: The name org.freedesktop.Notifications was not provided by any .service files INFO:root:entering dbusReInit of keyboard INFO:root:entering dbusReInit of gps INFO:root:entering dbusReInit of battery INFO:root:entering dbusReInit of bluetooth INFO:root:entering dbusReInit of buttons INFO:root:entering init for UsageInterface for gps INFO:root:resourceChanged: name: GPS state: 0 attributes: None INFO:root:entering postDisable of gps INFO:root:entering init for battery INFO:root:entering init for UsageInterface for bluetooth INFO:root:resourceChanged: name: Bluetooth state: 0 attributes: None INFO:root:entering postDisable of bluetooth INFO:root:entering init for UsageInterface for wifi INFO:root:resourceChanged: name: WiFi state: 0 attributes: None INFO:root:entering postDisable of wifi INFO:root:entering init for buttons ERROR:dbus.connection:Exception in handler for D-Bus signal: Traceback (most recent call last): File /usr/lib/pymodules/python2.5/dbus/connection.py, line 214, in maybe_handle_message self._handler(*args, **kwargs) File /usr/lib/pymodules/python2.5/panelplugin/UsageIcon.py, line 297, in resourceAvailable logging.info(resourceAvailable: name: %s available: %s % (name, available1)) NameError: global name 'available1' is not defined i just uploaded a current version of opp where i fixed this typo to http://projects.openmoko.org/projects/panel-plugin/ cheers, christian (morlac) adams - -- - -BEGIN CONTACT BLOCK- eMail: mor...@morlac.de Jabber: mor...@skavaer.homelinux.org - --END CONTACT BLOCK-- - -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS$/IT;d-;s:;a?;C++(+++);UL;P++(+++); L++(+++);E---;W++;N(+);o?;K?;!w;!O;!M+;!V;PS(+);PE; Y+;PGP++;t+(++);5(+)++;X(+);R*;tv-+;b++(+++);DI++; D++(+++);G(+)++;e;h-()++;r++;y++; - --END GEEK CODE BLOCK-- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFKYiVzr81gVylJyzERAnbRAKDIYXWdkl1kcEkR1qXaKNeiALpRBgCgkz5y Uczbbp3ZqmtOjMNLyrmfD78= =M31I -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[debian/fso] openmoko-panel-plugin should be more patient?
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. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
