kpilotDaemon crashes when "Backing up: Blazer"

Bug #26360 reported by Matt Saunders
14
Affects Status Importance Assigned to Milestone
KDE PIM
Fix Released
High
kdepim (Ubuntu)
Fix Released
Medium
Jonathan Riddell

Bug Description

A segfault occurs when kpilotDaemon attempts to back up Web pages on my Palm
Tungsten E2.

This is at the stage when the Palm is displaying "Synchronizing Web" and kpilot
is "Backing up: Blazer".

This appears to be a similar bug to one found in pilot-link, specific to larger
storage devices such as the Tungsten E2. It's described at
http://www.pilot-link.org/pipermail/pilot-link-general/2005-June/002434.html

Revision history for this message
Matt Saunders (matts) wrote :

Created an attachment (id=5104)
KDE crash information

Revision history for this message
Matt Saunders (matts) wrote :

Created an attachment (id=5105)
strace output from the crash

Revision history for this message
Matt Saunders (matts) wrote :

Created an attachment (id=5112)
kpilot syslog information

Revision history for this message
Ben Challenor (ben-challenor) wrote :

I can confirm this bug in Ubuntu Dapper with another Tungsten E2. It crashes at Blazer and deletes all of my Calendar entries - luckily I have lots of backups.

I can provide any more information you need.

Thanks.
Ben

Revision history for this message
Carthik Sharma (carthik) wrote :

Confirmed by another user.

Changed in kdepim:
status: Unconfirmed → Confirmed
Changed in kdepim:
status: Unknown → New
Revision history for this message
Jason 'vanRijn' Kasper (vr-movingparts) wrote :

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.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Thanks a lot for the followup. :-)
Closing this now.

Changed in kdepim:
status: Confirmed → Fix Released
Changed in kdepim:
status: New → In Progress
Changed in kdepim:
status: In Progress → Fix Released
Changed in kdepim:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.