Menu

#16 segfault after creating a sync-pair

open
nobody
5
2004-04-22
2004-04-22
No

since my last upgrade of my debian sarge installation,
multisync crashes when saving a syncpair, or when there
exist already one in ~/.multisync it segfaults on startup.

The messag on stderr reads:
** (multisync:2837): CRITICAL **: file
bonobo-activation-activate.c: line 276
(bonobo_activation_query): assertion `ac != NULL' failed

$ rm -R ~/.multisync; rm /tmp/multisync-USER
enables me to start it again.

This happens with the version 0.81-7 and the current
cvs version
(from
http://packman.iu-bremen.de/debian/sid/multisync-cvs/\)

I have installed the following packages of bonobo:
bonobo/testing uptodate 1.0.22-2.2
bonobo-activation/testing uptodate 1:2.4.0-4
libbonobo-conf0/testing uptodate 0.16-1.2
libbonoboui2-common/testing uptodate 2.4.3-2
libbonobo2-common/testing uptodate 2.4.3-1
libbonobo2/testing uptodate 1.0.22-2.2
libbonoboui2-0/testing uptodate 2.4.3-2
libbonobo2-0/testing uptodate 2.4.3-1
libbonobo-activation4/testing uptodate 1:2.4.0-4
bonobo-conf/testing uptodate 0.16-1.2

Discussion

  • Thomas Uttenthaler

    Logged In: YES
    user_id=426516

    I started it with debug-flags on once:
    multisync --gtk-debug=all

    Now the error doesn't appear anymore, neither starting with
    debug flags nor without. Seems to have some funny side
    effects ...

     
  • Thomas Uttenthaler

    Logged In: YES
    user_id=426516

    Ok, it appeared again after a reboot.

    I deleted now all plugins I don't need (have only ldap,
    evolution and mobile plugin atm), multisync starts after
    $ rm -R ~/.multisync; rm /tmp/multisync-USER
    but after the next reboot the asseration is back again ...

     

Log in to post a comment.

MongoDB Logo MongoDB