Menu
▾
▴
#92 Raki Crash with vdccm
Linux 2.6.16.13-4-default i686
SUSE LINUX 10.1 (i586)
KDE 3.5.1 Level "a"
Raki crashes when it looks to vdccm to connect thru to PDA. Can connect if Raki configured for dccm. Problem is can't do a synch between PDA and Kontact PIM with this configuration. The synchronization option is greyed out with left mouse button click of Raki Icon. When reset Raki to use vdccm, RAKI crashes with the following debug trace. At this point, only fall back is to use dccm and live without synch feature until problem is fixed.
DEBUG TRACE:
raki: in pda-init
raki: in PDE::init
raki: New Partnership
KCrash: Application 'raki' crashing...
[rapi_buffer_send:512] writev failed, returned -1 and not 12
[rapi_buffer_send:538] synce_socket_write failed
[rapi_context_call:181] rapi_buffer_send failed
[rapi_buffer_send:512] writev failed, returned -1 and not 12
[rapi_buffer_send:538] synce_socket_write failed
[rapi_context_call:181] rapi_buffer_send failed
raki: Fatal IO error: client killed
email is: griffri1@comcast.net
Logged In: YES
user_id=1676982
Originator: NO
same problem here, suse 10.1. Synce runs alright with rapip:/ in Konquerer but raki crashes upon connection.
Logged In: YES
user_id=1799071
Originator: NO
Is anyone still monitoring this bug ? Are you still encountering problems ?
By it's age this bug is probably defunct.
Logged In: YES
user_id=1799071
Originator: NO
Setting to pending, bug is old, no response, no other reports of problems with raki/vdccm.
Logged In: YES
user_id=1799071
Originator: NO
Setting to pending, bug is old, no response, no other reports of problems with raki/vdccm.
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).