inline below: > This is curious, if you quit SFLphone normally (i.e. not by interrupting > it/killing it), it should save the config file in > .config/sflphone/sflphoned.yml
ah - you're probably right. i had multiple things going wrong, so the segfault was happening before the generation. i was stepping thru in gdb, but i can't remember the exact sequence anymore > > starting the client failed with a segmentation fault - appears that > > it was failing to get codecs > > may be related to 0.9.2 still being installed > > corrected this problem by starting the daemon explicitly first > > The 1.0.x series of SFLphone is not parallel installable with the 0.9.x > series. We will have to document this in the wiki and README. the 0.9.x is installed at the system level. i was installing 1.0.2 in a custom prefix ($HOME/install/apps/sflphone/install) and setting binpath and ldpath. the problem appears to be that you're using dbus to invoke the daemon, and there doesn't appear to be a (sane) way to set a custom search path for dbus dbus was picking the default org.sflphone.SFLphone.service in /usr/share instead of the one in the custom prefix. my gut is that any installation using "./configure --prefix=my/custom/path" is going to fail (even if there is no 0.9.x installed), but i haven't verified this this isn't a problem that's limited to sflphone ... i'm guessing that "configure --prefix" is effectively worthless for any package that provides dbus services. sad to see it's demise, --prefix was about the only thing that enabled some sort of divide and conquer strategy for package management (for a developer / hacker that wanted multiple versions installed) _______________________________________________ SFLphone mailing list [email protected] http://lists.savoirfairelinux.net/mailman/listinfo/sflphone
