update today and got the new ophonekitd as well.
still, as normal user, ophonekitd crashes heavily:


** (process:16431): DEBUG: Initiated etk
** (process:16431): DEBUG: resource GSM is now enabled
** (process:16431): DEBUG: GSM is ready now
** (process:16431): DEBUG: call ogsmd_device_set_antenna_power()
** (process:16431): DEBUG: resource GSM is now enabled
** (process:16431): DEBUG: request_resource_callback()
Failed to handle dbus error: Resource Device is not enabled, current status is 'enabling', 81 (dbus-glib-error-quark), code 32
** (process:16431): DEBUG: power_up_antenna_callback()
Failed to handle dbus error: Resource Device is not enabled, current status is 'enabling', 81 (dbus-glib-error-quark), code 32
** (process:16431): DEBUG: sim_ready_status_callback(status=1074499584)
** (process:16431): DEBUG: sim ready
Failed to handle dbus error: Resource Device is not enabled, current status is 'enabling', 81 (dbus-glib-error-quark), code 32
** (process:16431): DEBUG: get_messagebook_info_callback()
Segmentation fault


starting as root, however, (with DISPLAY=:0) makes the pin dialog poccure almost immediately. when starting fso-abyss manually as root and ophonekitd as normal user after a few moments, it doesn't crash neither.

and the time after (now without starting fso-abyss manually), ophonekitd does not crash, but does not get to the pin dialog either (fso-abyss did not start automatically, for what reason ever):

** (process:16453): DEBUG: Initiated etk
** (process:16453): DEBUG: resource GSM is now enabled
** (process:16453): DEBUG: GSM is ready now
** (process:16453): DEBUG: call ogsmd_device_set_antenna_power()
** (process:16453): DEBUG: resource GSM is now enabled
** (process:16453): DEBUG: request_resource_callback()
** (process:16453): DEBUG: power_up_antenna_callback()
** (process:16453): DEBUG: dbus not available, try again in 5s
** (process:16453): DEBUG: sim_ready_status_callback(status=1074499584)
** (process:16453): DEBUG: sim ready
** (process:16453): DEBUG: call ogsmd_device_set_antenna_power()
** (process:16453): DEBUG: get_messagebook_info_callback()
** (process:16453): DEBUG: MessageBookInfo failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. dbus -2
** (process:16453): DEBUG: ogsmd_sim_retrieve_phonebook_callback()
** (process:16453): DEBUG: cache_phonebook_callback called
** (process:16453): DEBUG: caching phonebook failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. dbus -2
** (process:16453): DEBUG: power_up_antenna_callback()
** (process:16453): DEBUG: dbus not available, try again in 5s
** (process:16453): DEBUG: call ogsmd_device_set_antenna_power()
** (process:16453): DEBUG: power_up_antenna_callback()
** (process:16453): DEBUG: dbus not available, try again in 5s
** (process:16453): DEBUG: call ogsmd_device_set_antenna_power()
** (process:16453): DEBUG: power_up_antenna_callback()
** (process:16453): DEBUG: dbus not available, try again in 5s
** (process:16453): DEBUG: call ogsmd_device_set_antenna_power()
** (process:16453): DEBUG: power_up_antenna_callback()
** (process:16453): DEBUG: dbus not available, try again in 5s
** (process:16453): DEBUG: call ogsmd_device_set_antenna_power()
** (process:16453): DEBUG: power_up_antenna_callback()
** (process:16453): DEBUG: dbus not available, try again in 5s
** (process:16453): DEBUG: call ogsmd_device_set_antenna_power()
** (process:16453): DEBUG: power_up_antenna_callback()
** (process:16453): DEBUG: dbus not available, try again in 5s
** (process:16453): DEBUG: call ogsmd_device_set_antenna_power()
** (process:16453): DEBUG: power_up_antenna_callback()
** (process:16453): DEBUG: dbus not available, try again in 5s
** (process:16453): DEBUG: call ogsmd_device_set_antenna_power()



_______________________________________________
Smartphones-userland mailing list
Smartphones-userland@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland

Reply via email to