'Re: [kdepim-users] KPilot has been reported to cause data loss'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdepim-users
Subject:    Re: [kdepim-users] KPilot has been reported to cause data loss
From:       Adriaan de Groot <adridg () sci ! kun ! nl>
Date:       2004-04-22 13:10:38
Message-ID: Pine.GSO.4.44.0404221449110.11647-100000 () wn4 ! sci ! kun ! nl
[Download RAW message or body]

Hi Imanol,

I can't really tell what the question or comment is here; since this
message ends with a backtrace, I suppose that's because KPilot crashed on
you.

On Wed, 21 Apr 2004, imanol aranaga wrote:
> 23:08:51  Haciendo copia de seguridad del Pilot. Por favor pulse el botón de
> sincronización en caliente.

Someone should check if that's the translation for HotSync that is also
used in the spanish users documentation for the pilot.

> 23:09:01  Running with flags: --backup  --full
> 23:09:01  KNotes is not running. The conduit must be able to make a DCOP
> connection to KNotes for synchronization to take place. Please start KNotes
> and try again.

Looks like you've got everything enabled - and the daemon isn't
translated. This has been fixed in more recent versions (eh, CVS HEAD).

> 23:09:01  [Conduit vcal-conduit]
> 23:09:01  Running with flags: --backup  --full
> 23:09:02  Syncing with file "empty"

Not good, I don't think. Configure KPilot first.

> 23:09:07  [Conduit todo-conduit]
> 23:09:07  Running with flags: --backup  --full
> 23:09:08  Syncing with file "empty"

And I take it it crashed here?
> #3  <signal handler called>
> #4  0x414207db in __dynamic_cast () from /usr/lib/libstdc++.so.5
> #5  0x41af7486 in TodoConduit::recordFromIncidence(PilotAppCategory*,
> KCal::Incidence const*) () from /opt/kde3/lib/kde3/conduit_todo.so
> #6  0x41afd083 in VCalConduitBase::updateIncidenceOnPalm(KCal::Incidence*,
> PilotAppCategory*) () from /opt/kde3/lib/kde3/conduit_todo.so

Well that's sufficiently weird .. I didn't think dynamic_cast _could_
crash, unless maybe the Incidence pointer is bad already. I know some odd
pointer crashes were fixed in the past month or so in HEAD, so I'm going
to suggest upgrading.

-- 
 Adriaan de Groot    adridg@cs.kun.nl     Kamer A6020     024-3652272
GPG Key Fingerprint 934E 31AA 80A7 723F 54F9  50ED 76AC EE01 FEA2 A3FE
               http://www.cs.kun.nl/~adridg/research/

_______________________________________________
KDE PIM users mailing list
kdepim-users@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users

[prev in list] [next in list] [prev in thread] [next in thread] 