Re: [Opensync-users] Re: kdepim plugin crashing

[Armin B. <arm...@de...>]

Hi Guillaume,

one important note: you cannot sync with the KDE plugin using
Kitchensync. The reason is that both try to instance KApplication which
is not possible. So for reliable tests with the kde plugin you have to
use the cli.

About the backtrace: gdb msynctool should do the trick and give an
backtrace. So if you experience the crash again, i would be happy to
take a look at the backtrace.

Armin

Guillaume Pothier wrote:
> Some news: I no longer experiment the crash.
> Reason: unknown.
> The only thing I did was to compile kitchensync as described here
> (http://www.opensync.org/wiki/kitchensync), only changing KDE version
> from 3.4 to 3.5. Then I launched kitchensync, which listed my "g"
> group with its members. I tried to sync once - it crashed. Later I
> relaunched kitchensync and it didn't crash. It even actually did
> something with my phone, as the phone showed a synchronization
> progress bar. Exactly what it did I don't know, as no contact on the
> phone or in Kontact have changed...
> But the fact is that the CLI doesn't crash anymore. It fails with an
> OBEX error instead...
> I'll hack a bit more now...
> g
> 
> On 2/6/06, Guillaume Pothier <gpo...@gm...> wrote:
> 
>>Hi, I'm experiencing a systematic crash of the kdepim plugin with
>>v0.18 as well as with latest svn sources.
>>
>>I have a sync group called "g" with a kdepim member and a irmc member.
>>Below is the output of "msynctool --sync g". This is with latest svn
>>version of opensync and kdepim plugin, with debugging turned on.
>>My box has kde 3.5.1 from kubuntu breezy. KAdressBook is v3.5
>>Any idea how I could fix this? Is there a way I can get a stack trace?
>>g
>>
>>
>>
>>--------------------------
>>gpothier@tadzim:~/tmp/opensync/svn/opensync$ msynctool --sync g
>>[OSUSR] DEBUG: Detected User:
>>UID: 1000
>>GID: 1000
>>Home: /home/gpothier
>>OSyncDir: /home/gpothier/.opensync
>>[OSGRP] DEBUG: Trying to load group from directory
>>/home/gpothier/.opensync/group1
>>Synchronizing group "g"
>>[CLI] DEBUG: Creating new client 0x8052640
>>[CLI] DEBUG: Creating new client 0x8052ae0
>>[GRP] FULL DEBUG: locking file /home/gpothier/.opensync/group1/lock
>>[GRP] FULL DEBUG: locking group: file exists
>>[GRP] FULL DEBUG: Successfully locked
>>[ENG] WARNING: Detected stale lock file. Slow-syncing
>>The previous synchronization was unclean. Slow-syncing
>>[ENG] FULL DEBUG: Sending message 0x80530b0:"ENGINE_CHANGED"
>>[OSMEM] DEBUG: Instancing plugin kdepim-sync for member 1
>>[kde] DEBUG: kde_initialize
>>[kde] DEBUG: Loading implementation module
>>[kde] DEBUG: Getting initialization function
>>[kde] DEBUG: Initializing implementation module
>>[OSMEM] DEBUG: Instancing plugin irmc-sync for member 2
>>[ENG] DEBUG: Running the main loop
>>[OSDB] DEBUG: Preparing to load changes from file
>>/home/gpothier/.opensync/group1/change.db
>>[OSDB] INFORMATION: Unable create changes table! table tbl_changes
>>already exists
>>[OSDB] DEBUG: Unable step count! not an error
>>[ENG] DEBUG: Calling all client deciders (2)
>>[ENG] FULL DEBUG: Sending message 0x806cbf0:"CLIENT_CHANGED" for
>>client 0x8052640
>>[ENG] FULL DEBUG: Sending message 0x80893f8:"CLIENT_CHANGED" for
>>client 0x8052ae0
>>[CLI] DEBUG: Client message handler called for message "CONNECT"
>>[CLI] DEBUG: Client message handler called for message "CONNECT"
>>KCrash: Application 'libopensync-kdepim-plugin' crashing...
>>Segmentation fault
>>
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>