[debian] frameworkd bug?
since the update today, frameworkd soon after starting zhone simply disappears (no error, no log entry, it's just gone). while trying to figure out what happens, i saw the error below. i have no idea, if it is related: _processElement() got an element from the queue Traceback (most recent call last): File /usr/lib/pymodules/python2.5/dbus/connection.py, line 581, in msg_reply_handler *message.get_args_list())) File /usr/lib/pymodules/python2.5/framework/subsystems/oeventsd/fso_actions.py, line 233, in lambda error_handler = lambda cls=cls,name=name, e=None: cls.onResourceRequestError( name, e ) ) AttributeError: 'DBusException' object has no attribute 'onResourceRequestError' no elements in queue: starting idle task. _processElement() ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] frameworkd bug?
well, here's the real mccoy:
Traceback (most recent call last):
File /usr/lib/pymodules/python2.5/framework/patterns/tasklet.py, line
178, in send
value = self.generator.send(value)
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimb_sim_messages_fso.py,
line 287, in load_entries
self.process_all_entries(entries)
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimb_sim_messages_fso.py,
line 247, in process_all_entries
self.process_single_entry([[message[0][0]],message[0][1],message[0][2],message[0][3],message[0][4]])
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimb_sim_messages_fso.py,
line 139, in process_single_entry
entry_id = self._domain_handlers['Messages'].register_entry(self,
entry)
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimd_messages.py,
line 324, in register_entry
message_id = GenericDomain.register_entry(self, backend, message_data)
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimd_generic.py,
line 647, in register_entry
entry.import_fields(entry_data, backend.name)
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimd_generic.py,
line 171, in import_fields
compare_value = self.make_comp_value(field_value)
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimd_generic.py,
line 140, in make_comp_value
if str(field_value).startswith('tel:'):
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in
position 25: ordinal not in range(128)
looks, like utf8 is till not used as default or at least exception
handling could use some improvement.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] frameworkd bug?
well, here's the real mccoy: Traceback (most recent call last): ... Thanks for your report. But please post such things either to pkg-fso-ma...@lists.alioth.debian.org list, or directly into debian BTS (http://bugs.debian.org/). If posted to community@lists.openmoko.org, information may be not seen by relevant people. Nikita signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] frameworkd bug?
If posted to community@lists.openmoko.org, information may be not seen by relevant people. well, imo community has the biggest chance to be read by the relevant people. frinst i am not sure, if the issue at hand is confined to debian (fixed in most recent fso git or whatever) and if other people did experience/worked around it. i considered, sending to smartphone-... _too_ but dismissed the idea, because of my conviction, that everybody concerned reads community as well. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] frameworkd bug?
If posted to community@lists.openmoko.org, information may be not seen by relevant people. well, imo community has the biggest chance to be read by the relevant people. frinst i am not sure, if the issue at hand is confined to debian (fixed in most recent fso git or whatever) and if other people did experience/worked around it. i considered, sending to smartphone-... _too_ but dismissed the idea, because of my conviction, that everybody concerned reads community as well. community@ is a bit high-traffic, don't you find so ;-) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] frameworkd bug?
community@ is a bit high-traffic, don't you find so ;-) no doubt about that -- but then again: you catched, didn't you ;-) a matter like incomplete unicode handling is no doubt relevant for upstream too, so what would be the best course of action? - simply doing reportbug? - posting only pkg-fso and expecting the package maintainer to transport further upstream? - double posting at least pkg-fso and smartphones-userland (or -standard?)? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] frameworkd bug?
community@ is a bit high-traffic, don't you find so ;-) no doubt about that -- but then again: you catched, didn't you ;-) I've only sent a link to your post to pkg-fso-maint - I won't work on the fix myself, at least not in ongoing days :( a matter like incomplete unicode handling is no doubt relevant for upstream too, so what would be the best course of action? - simply doing reportbug? - posting only pkg-fso and expecting the package maintainer to transport further upstream? - double posting at least pkg-fso and smartphones-userland (or -standard?)? Not -standard - it's about standards and not implementation. Since Debian carries something that differs from upstream head, it is more correct to send bugs to debian packages maintainers first. Pkg-fso-maint is the correct list for that. Nikita signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] frameworkd bug?
On 9/22/09, arne anka openm...@ginguppin.de wrote:
well, here's the real mccoy:
Traceback (most recent call last):
File /usr/lib/pymodules/python2.5/framework/patterns/tasklet.py, line
178, in send
value = self.generator.send(value)
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimb_sim_messages_fso.py,
line 287, in load_entries
self.process_all_entries(entries)
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimb_sim_messages_fso.py,
line 247, in process_all_entries
self.process_single_entry([[message[0][0]],message[0][1],message[0][2],message[0][3],message[0][4]])
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimb_sim_messages_fso.py,
line 139, in process_single_entry
entry_id = self._domain_handlers['Messages'].register_entry(self,
entry)
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimd_messages.py,
line 324, in register_entry
message_id = GenericDomain.register_entry(self, backend, message_data)
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimd_generic.py,
line 647, in register_entry
entry.import_fields(entry_data, backend.name)
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimd_generic.py,
line 171, in import_fields
compare_value = self.make_comp_value(field_value)
File
/usr/lib/pymodules/python2.5/framework/subsystems/opimd/pimd_generic.py,
line 140, in make_comp_value
if str(field_value).startswith('tel:'):
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in
position 25: ordinal not in range(128)
looks, like utf8 is till not used as default or at least exception
handling could use some improvement.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
That's me who should get this mail. Mail starred, expect fix soon ;)
--
Sebastian Krzyszkowiak
dos
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
