Bug 71384 - syncing new notes doubles on PDA + produces cruft
Summary: syncing new notes doubles on PDA + produces cruft
Status: RESOLVED FIXED
Alias: None
Product: kpilot
Classification: Applications
Component: Memofile Conduit (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: groot
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-28 20:10 UTC by Olaf Schulz
Modified: 2004-10-19 16:20 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olaf Schulz 2003-12-28 20:10:39 UTC
Version:           4.3.10 (BRANCH) (using KDE 3.1.4)
Installed from:     (testing/unstable)
Compiler:          gcc version 3.3.2 (Debian)
OS:          Linux (i686) release 2.4.23-xfs.noinitrd.acpi.athlon

using knotes, kpilot and Palm OS 3.5.2H5.7 (Memo V3.5)

syncing a new note (made with KNote) always produces two new memos on my PDA
One of them has one or some odd characters attached at the end. Editing at that odd character crashes my PDA with
"DataMgr.c,Line:70225, DmWrite:DmWriteCheck failed" and I have to soft reset it.

After the soft reset the PDA's memory seems to be reorganized and no further crashs will occur, but the doubled note remains.
Comment 1 groot 2004-03-19 00:50:43 UTC
Hi Olaf, sorry for the delay in responding to this bug. There's been a lot of work in the KNotes conduit in february, do you think you could try a more recent version? I'll provide a tarball and instructions if so.
Comment 2 Matthias Meßmer 2004-04-13 16:53:20 UTC
KPilot Version: 4.4.1 (using KDE 3.2.2)
KNotes Version: 3.0.1 (using KDE 3.2.2)
Installed from: Debian packages (unstable)
OS: Linux (i686) release 2.4.23-1-k7
PalmOS v3.5

Same odd characters at the end of memos on the PDA after syncing a new note created with KNotes. PDA crashes during deleting this chars.
Comment 3 Olaf Schulz 2004-04-15 00:46:05 UTC
KPilot Version: 4.3.10 (using KDE 3.1.5)
KNotes Version: 2.3
reproduced the bug with pose. (Palm OS 3.5.2H3.0, Memo Pad 3.5)
pose reported the following:
 
| Merkzettel (3.5) called SysFatalAlert with the message:
| "DataMgr.c, Line:7025, DmWrite: DmWriteCheck failed".
(Merkzettel is the german name for the Memo application on Palm OS.)
giving me the coice to reset, debug, or continue.
(no Idea what happened when I pressed debug)
after continuing: trying to cut the odd characters crashed pose
with a segfault.
Only with pose I also get doubled Memo entries.
I saved two sessions containing the error.
Trying to remove the odd characters with graffiti strokes is the safest
way to reproduce the error.

Adriaan, shall I send you all necessary pose files to further
investigate things?
Please, let me try the new version of kpilot if it is newer than the one
bmlmessmer has tried (provide me with instructions for compiling, please
list the "build-dependencies")

I tried an empty (hard-reset) 
Palm Zire 20 (Palm OS 4.1, Memo Version 4.0)
and there happened exactly the same crash, sometimes being persistent
over a (soft) reset. The odd characters at the end vanished when I
exported the MemoDB to my PC with pilot-xfer (both in the exported file
and on the Palm). So I can't send a damaged *.pdb file.
The Error Message on the Zire reads:
| Fatal Error
| DataMgr.c, Line:7386,
| DmWrite:DmWriteCheck failed
with the reset button on the screen not working

When I started kpilotDaemon from console I get the following messages
when hotsyncing (producing the crashing Memo entry)
| WARNING: [virtual void KPilotInstaller::daemonStatus(int)] : Unhandled status message 1
| WARNING: : Modified note unknown to Pilot

Olaf

Comment 4 groot 2004-04-16 23:19:20 UTC
On Thursday 15 April 2004 00:46, Olaf Schulz wrote:
> Only with pose I also get doubled Memo entries.
> I saved two sessions containing the error.
> Trying to remove the odd characters with graffiti strokes is the safest
> way to reproduce the error.

Hi Olaf, KPilot CVS HEAD is a pretty safe bet, actually, so you could run 
that. It requires KDE 3.2, but you should have that anyway. You can follow 
the instructions on the KDE Quality Team website for how to fetch CVS - or 
check the tarballs on the KPilot website, though I haven't updated them in a 
week or two.

Hmm, I think I see the problem, actually .. pilotMemo is using a wrong length 
for the string data to be written.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAgE22dqzuAf6io/4RAm29AKCCtKGCafDrvGI9FDIOVWwayjA7jQCfQfDq
CQEaVOJ4nkAI+ZzVLbTm0qY=
=PnU5
-----END PGP SIGNATURE-----

Comment 5 groot 2004-10-01 21:37:51 UTC
Was fixed in HEAD a while ago.
Comment 6 Olaf Schulz 2004-10-02 18:55:29 UTC
Hallo groot,
am Fri, 01.10.2004 um 19:37 h -0000 schriebst Du:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>         
> http://bugs.kde.org/show_bug.cgi?id=71384        
> groot kde org changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>          Resolution|                            |FIXED
> 
> 
> 
> ------- Additional Comments From groot kde org  2004-10-01 21:37 -------
> Was fixed in HEAD a while ago.

Could you tell me in which version of knotes or kde-pim
and give me a pointer to build instructions for that version?
Which version of KDE and qtlib does it require to run?

I would like to see the bugfix in effect.

regards
Olaf