Hi guys. I'm the maintainer/developer of KPilot and I apologize for the problems you were having. This is an old bug, so I'm pretty sure you guys have just given up at this point, but this bug should be closed. The problem was with the version of pilot-link that you were using. If you'll notice from the first attachment (KDE crash information), what is listed is "/usr/lib/libpisock.so.8." This version came with pilot- link-0.11 or earlier and those versions cannot handle large database sizes, such as the newer ones like Blazer. So, the 2 solutions would have been to either tell KPilot to not back that database up in the configuration section, or to upgrade to a newer version of pilot-link.
Somewhere in the KDE 3.5 series, we made it a mandatory requirement for KPilot to have at least pilot-link/libpisock 12.0, so this problem doesn't exist anymore. -- kpilotDaemon crashes when "Backing up: Blazer" https://bugs.launchpad.net/bugs/26360 You received this bug notification because you are a member of Kubuntu Bugs, which is a direct subscriber. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
