After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 274032 - crashe on sync
crashe on sync
Status: RESOLVED FIXED
Product: gnome-pilot
Classification: Other
Component: gpilotd
2.0.x
Other All
: High major
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
: 300842 301256 302597 303441 303752 305002 307104 307305 307311 307681 307730 307857 308240 308284 308380 308385 308707 308733 308986 309098 312456 312617 313371 315475 315958 316953 317094 318033 318341 319478 320240 320882 323216 323538 327774 328467 330536 331318 332363 333410 333742 336698 338740 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-03-23 21:30 UTC by sklar
Modified: 2006-10-05 13:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Crash on sync with an Palm m500 (4.09 KB, application/octet-stream)
2005-06-18 10:10 UTC, Patrick DOURET
  Details
Fix return code checks (992 bytes, patch)
2005-06-25 15:21 UTC, Mark Adams
none Details | Review
Don't call pi_close on listen_sd after establishing connection (1.45 KB, patch)
2005-06-25 15:22 UTC, Mark Adams
none Details | Review
Fix database-reading loop (1.22 KB, patch)
2005-06-25 15:24 UTC, Mark Adams
none Details | Review

Description sklar 2005-03-23 21:30:52 UTC
Distribution: Fedora Core release Rawhide (Rawhide)
Package: Evolution
Priority: Normal
Version: GNOME2.10.0 2.2.1
Gnome-Distributor: Red Hat, Inc
Synopsis: gpilotd crashes on setup
Bugzilla-Product: Evolution
Bugzilla-Component: Gnome-pilot & pilot-link
Bugzilla-Version: 2.2.1
BugBuddy-GnomeVersion: 2.0 (2.9.1)
Description:
Description of the crash:
I tried to set up my Tungsten C to work with Evolution and gpilotd
crashed

Steps to reproduce the crash:
1. Pick Tools->Pilot settings from the Evolution menu
2. Follow the prompts (Cradle is plugged in via USB)
3. Press sync button on cradle when instructed ("About to retrieve
UserName and ID from the pilot")

Expected Results:

Communication with the pilot		

How often does this happen?

Whenever I try it.

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/libexec/gpilotd'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208457536 (LWP 27421)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x003a47e2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

Thread 1 (Thread -1208457536 (LWP 27421))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 pi_listen
    from /usr/lib/libpisock.so.9
  • #5 device_equal_by_io
  • #6 network_device_err
  • #7 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_iteration
    from /usr/lib/libglib-2.0.so.0
  • #11 main



Unknown reporter: sklar@sklar.com, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Christian Kirbach 2005-04-16 09:36:30 UTC
*** Bug 300842 has been marked as a duplicate of this bug. ***
Comment 2 Christian Kirbach 2005-04-16 09:39:20 UTC
reassigning to gnome-pilot
Comment 3 Elijah Newren 2005-04-20 05:48:26 UTC
*** Bug 301256 has been marked as a duplicate of this bug. ***
Comment 4 Elijah Newren 2005-05-01 05:23:20 UTC
*** Bug 302597 has been marked as a duplicate of this bug. ***
Comment 5 Olav Vitters 2005-05-08 09:30:37 UTC
*** Bug 303441 has been marked as a duplicate of this bug. ***
Comment 6 Elijah Newren 2005-05-12 02:11:59 UTC
*** Bug 303752 has been marked as a duplicate of this bug. ***
Comment 7 Elijah Newren 2005-05-29 00:00:13 UTC
*** Bug 305002 has been marked as a duplicate of this bug. ***
Comment 8 Maxwell Bottiger 2005-06-03 00:02:22 UTC
I fixed the crash problem on my system.  All I had to do was change my
/etc/udev/rules.d/10-visor.rules file.  I added MODE="0666" to the rule and now
my pilot syncs.  For reference, the contents of the file is:

BUS="usb", SYSFS{product}="Palm Tungsten T / Zire 71", KERNEL="ttyUSB*",
SYMLINK="pilot" MODE="0666"

Right now gpilotd and hotsync have stopped crashing, however, none of the
conduits seem to work.  That is probably an unrelated issue.

Best of luck.
Comment 9 Sebastien Bacher 2005-06-11 13:15:45 UTC
*** Bug 307104 has been marked as a duplicate of this bug. ***
Comment 10 Sebastien Bacher 2005-06-11 20:37:01 UTC
*** Bug 307311 has been marked as a duplicate of this bug. ***
Comment 11 Sebastien Bacher 2005-06-11 20:37:21 UTC
*** Bug 307305 has been marked as a duplicate of this bug. ***
Comment 12 dvilla 2005-06-14 20:25:13 UTC
This happens also with Tungsten T5. Specially with conduits EAddress, ECalendar
and EToDo.
Comment 13 Mark Adams 2005-06-15 06:00:50 UTC
Also hit with my Tungsten T3 on a brand new FC4 x86-64 install. This worked fine
on FC3 x86-64. I'm happy to test any workarounds or patches.
Comment 14 Patrick Steiner 2005-06-15 16:50:44 UTC
Also with my Palm Tungsten T3 on FC4 x86. With FC3 all works fine  
Comment 15 Patrick DOURET 2005-06-18 10:10:02 UTC
Created attachment 47951 [details]
Crash on sync with an Palm m500
Comment 16 Patrick DOURET 2005-06-18 10:32:51 UTC
To complete my report, gpilot hangs when i have to synchronise appointement on
several days.
Comment 17 joel 2005-06-20 17:53:19 UTC
I just added an appointment spanning multiple days and a crash occoured by
gpilotd. I got the following backtrace (unfortunately debuggign symbols are
disabled in the build I used):

Backtrace was generated from '/usr/libexec/gpilotd'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...[Thread debugging using libthread_db enabled]
[New Thread -1208084800 (LWP 4794)]
[New Thread -1223308368 (LWP 14649)]
[Thread debugging using libthread_db enabled]
[New Thread -1208084800 (LWP 4794)]
[New Thread -1223308368 (LWP 14649)]
[Thread debugging using libthread_db enabled]
[New Thread -1208084800 (LWP 4794)]
[New Thread -1223308368 (LWP 14649)]
[New Thread -1212818512 (LWP 14648)]
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...0x001857a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 giop_send_buffer_append_string
    from /usr/lib/libORBit-2.so.0
  • #5 ??
  • #6 ??
  • #7 ??
    from /usr/lib/libORBit-2.so.0
  • #8 ??
  • #9 ??
  • #10 giop_send_buffer_append_string
    from /usr/lib/libORBit-2.so.0
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ORBit_marshal_value
    from /usr/lib/libORBit-2.so.0

I'm using FC3.
Comment 18 Jyrki Pajunen 2005-06-24 10:07:04 UTC
This is visible on FC4 not on my FC3.
Comment 19 Sebastien Bacher 2005-06-24 16:32:11 UTC
*** Bug 307681 has been marked as a duplicate of this bug. ***
Comment 20 Sebastien Bacher 2005-06-24 16:32:39 UTC
*** Bug 307730 has been marked as a duplicate of this bug. ***
Comment 21 Sebastien Bacher 2005-06-24 16:33:09 UTC
*** Bug 307857 has been marked as a duplicate of this bug. ***
Comment 22 Sebastien Bacher 2005-06-24 16:33:50 UTC
*** Bug 308284 has been marked as a duplicate of this bug. ***
Comment 23 Sebastien Bacher 2005-06-24 16:34:10 UTC
*** Bug 308240 has been marked as a duplicate of this bug. ***
Comment 24 Mark Adams 2005-06-25 15:18:30 UTC
I've been digging into this problem as it's a major blocker for me to run FC4 as
my main OS. I've made some progress, but am now running into a conduit problem.

The first problem is the crash - that is caused by udev taking a moment before
it creates /dev/ttyUSB[01]; gnome-pilot is supposed to loop trying to connect
until the specified devices are created. However, the checks for error codes
(particularly on pi_bind) are incorrect. They check for ret == -1, but that
function can and does return other negative values on error. Thus, we blithly
keep on going an call pi_listen, but the connection doesn't exist. Fixed in the
attached gpilotd.diff

BTW, the reason some people haven't run into it is that on their machine, either
the relevant device files always exist (using serial connection probably) or
happen to be created in time.

The next problem encountered is that we disconnect from the device as soon as
we've connected, before doing anything. The problem here is that the usage of
the pilot-link API in gpilotd.c doesn't match what it should. In particular, the
'socket' fd we pass around is just a lookup handle, so we _must not_ call
pi_close() on the listener handle after getting a handle from accept; that has
the effect of closing the connection. Yes, I agree this is unexpected behaviour
which doesn't match any other socket API; talk with the pilot-link developers,
not me. :> Fixed in the attached gpilotd2.diff patch.

This then finally permits me to get the user name and id from my Tungsten.

Next, when I try to sync, no conduits are invoked. When somebody put together
the patch to port gnome-pilot to 0.12.0-pre*, they changed the usage of
dlp_ReadDBList from something that worked to something that's not even close to
working, which resulted in finding the first database and then several hundred
thousand chunks of random memory. The attached manager.diff patch reverts those
changes as well as adds better error handling in that loop.

This results in the databases being found and the conduits are attempted to be
run, but they run into other errors. I'll keep pushing ahead unless somebody
beats me to it.

All patches are on top of the patches included in the FC4 gnome-pilot RPM. Also,
FWIW, I updated my version of pilot-link to pilot-link-0.12.0-pre4 in case there
were relevant bug-fixes.

I must say, gnome-pilot as shipped in FC4 didn't have a hope of working. While I
understand the desire to ship with newer software upstream whenever possible, a)
pilot-link-0.12 is still in beta, and b) the changes to gnome-pilot to support
the new pilot-link obviously weren't tested. "working" is more important than
"brand-spanking-new".
Comment 25 Mark Adams 2005-06-25 15:21:13 UTC
Created attachment 48322 [details] [review]
Fix return code checks
Comment 26 Mark Adams 2005-06-25 15:22:40 UTC
Created attachment 48323 [details] [review]
Don't call pi_close on listen_sd after establishing connection
Comment 27 Mark Adams 2005-06-25 15:24:18 UTC
Created attachment 48324 [details] [review]
Fix database-reading loop
Comment 28 Sebastien Bacher 2005-06-25 23:57:09 UTC
*** Bug 308986 has been marked as a duplicate of this bug. ***
Comment 29 Teppo Turtiainen 2005-06-26 11:25:11 UTC
*** Bug 308380 has been marked as a duplicate of this bug. ***
Comment 30 Teppo Turtiainen 2005-06-26 11:25:34 UTC
*** Bug 308385 has been marked as a duplicate of this bug. ***
Comment 31 Teppo Turtiainen 2005-06-26 11:25:56 UTC
*** Bug 308707 has been marked as a duplicate of this bug. ***
Comment 32 Teppo Turtiainen 2005-06-26 11:26:47 UTC
*** Bug 308733 has been marked as a duplicate of this bug. ***
Comment 33 Mark Adams 2005-06-26 19:55:02 UTC
Ok, I've had success getting the three evolution conduits to work. I'm going to
treat this bug report as a meta-bug pointing out the required patches to the
other involved components, so there's a record in one place for whoever at
RedHat puts together FC4 updates for pilot-link, gnome-pilot, evolution and
evolution-data-server (lucky guy) :P

To get everything working:

1) pilot-link needs to be updated to pilot-link-0.12.0-pre4 (note that that
obsoletes many of the patches included in the pilot-link RPM shipped with FC4).
Then the following three patches which I've reported in their bug database need
to be applied:
http://bugs.pilot-link.org/1507
http://bugs.pilot-link.org/1508
http://bugs.pilot-link.org/1509

2) gnome-pilot needs to be updated with the three patches attached to this bug,
as well as the memory leak patch in bug #309077

3) evolution needs to be updated with the patches attached to bug #309078

4) evolution-data-server needs to be updated with the patches attached to bug
#309079

Once all patches have been applied and the components rebuilt in order, then I
am able to successfully sync the calendar, addressbook and todo list with
evolution. Basic operations seem to work fine and are now clean in valgrind.

The worst memory leaks are fixed by the above referenced patches, although there
are still a couple which I haven't tracked down yet.

Note that gnome-pilot still isn't backing up the PDA databases as it did in FC3;
I'll look into that next, as backups are A Good Thing.
Comment 34 Mark Adams 2005-06-26 22:53:40 UTC
5) Backup conduit has been updated for new pilot-link API etc and is now
functional. See bug #309092 for details.

I believe that satisfies my requirements functionality-wise. With the full set
of patches, sync is working for me as anticipated.
Comment 35 Mark Adams 2005-06-27 14:30:47 UTC
Since some of the problems are upstream issues and some are problems with the
RedHat patches, I'm starting to divvy up the patches accordingly.

To begin with, bug #309092 which is the backup conduit issue has been divided
into bug #309130 and https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161799

I will work back through all my above patches in a similar fashion.

As a side note, this is perhaps a good example why it's not a good idea for the
default bugzilla for FC4 problems in gnome to be bugzilla.gnome.org; the Gnome
folks here are getting inundated by reports of this bug, and the problems are
largely due to RedHat patches.
Comment 36 Mark Adams 2005-06-27 15:52:46 UTC
I've now split the evolution patches into two sets. The first is now bug #309138
which is the upstream memory leaks. The second is
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161817 which is the fix to
port to the new pilot-link API.
Comment 37 Mark Adams 2005-06-27 16:12:28 UTC
Finally, I've redone the patches attached to this bug and placed them at
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161824 as they have to do
with RedHat's porting of gnome-pilot to the new pilot-link API. That then
obsoletes the patches attached to this bug.

I believe that completes the splitting of the patches to appropriate locations.
Comment 38 Mark Adams 2005-06-27 16:13:43 UTC
Comment on attachment 48322 [details] [review]
Fix return code checks

Obseleted as described in the bug above.
Comment 39 Mark Adams 2005-06-27 16:14:13 UTC
Comment on attachment 48323 [details] [review]
Don't call pi_close on listen_sd after establishing connection

Obsoleted as described above in the bug.
Comment 40 Mark Adams 2005-06-27 16:14:36 UTC
Comment on attachment 48324 [details] [review]
Fix database-reading loop

Obsoleted as described in the bug above.
Comment 41 Veerapuram Varadhan 2005-07-01 10:39:20 UTC
The memory leaks patch looks good.

The other patch related to compatibility with pilot-link 0.12.prexxxx version. 
The patch has ported the code to use the pilot-link 0.12.prexxx APIs, however,
doesn't enforce it in configure, because of which, the gnome-pilot fails to
compile.  If pilot-link 0.12.prexxx APIs are stable enough, I would suggest move
the dependency from 0.11.x to 0.12.prexxx.
Comment 42 Veerapuram Varadhan 2005-07-01 12:14:38 UTC
Mark: I am committing your mem-leak patch. Thanks for the patch, however, in
future generate patches with "-p" option. For more details check the HACKING file.
Comment 43 Dr. Tilmann Bubeck 2005-07-14 21:39:53 UTC
Could you please offer all the changed RPM files for download? It's quite
complicated to do all these things....
Comment 44 Mark Adams 2005-07-18 23:10:31 UTC
Ok, I've put together updated SRPMS and RPMS for i386 with my fixes; however, I
need a place to host them (comes to 29M total). If somebody can either host them
or point me to a place that can host them, I can make them available for people
to try.

I don't know what the holdup at RedHat is; they may be trying to track down the
separate problem of udev taking forever to create the ttyUSB* devices on sync.
There was also a report of the newer versions in rawhide deleting todo lists,
but I've been unable to reproduce that with my patched versions.
Comment 45 nigel.metheringham 2005-07-20 08:00:06 UTC
Now available at:-
  http://zeniv.linux.org.uk/pub/people/mark_adams/
  ftp://zeniv.linux.org.uk/pub/people/mark_adams/

yum metadata is in place so you could point yum at either of those URLs
Comment 46 Patrick Steiner 2005-07-20 08:52:05 UTC
thanks nigel,

with this rpms palm sync works fine with my t3.

there is only one litte problem, after every sync i get 2 warnings from gpilotd

warning Unknown conduit""

does anyone know what i can do?
Comment 47 Patrick Steiner 2005-07-20 11:01:51 UTC
i found another problem. memo-file sync doesnt work.

any ideas?
Comment 48 Mark Adams 2005-07-20 12:59:24 UTC
Could be that the stuff in gnome-pilot-conduits also needs some fixes; I've not
taken a look at that package. I'll see if I can get some time to do so in the
next day or two.
Comment 49 Ralf Spenneberg 2005-07-20 15:08:23 UTC
RPMs also available at
http://www.spenneberg.org/Evolution

Ralf
Comment 50 Mark Adams 2005-07-21 03:03:14 UTC
Ok, gnome-pilot-conduits did indeed need a bit of work. I identified the
following issues:

1) there was another bug in the gnome-pilot port to pilot-link-0.12pre which
gets tickled by these conduits; I've updated the patch at
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161824

2) there were to crashers in the expense conduit; report and patch is in bug #311072

3) I encountered three memory leaks in the memo conduit; report and patch is in
bug #311074

In addition, the location of the conduits had to be updated to match what
gnome-pilot expected. With these changes, the conduits at least nominally seem
to work, and valgrind is much happier; I've not tested extensively.

It was also pointed out that a line I'd added to the pilot-link and gnome-pilot
specfiles while trying to do 64->32 cross compile a while ago and then forgot
about broke building on x86_64. I've fixed those specfiles and re-spun those
packages with newer release numbers.

I've sent updated SRPMS and RPMS to both Ralf and Nigel so that they can make
them available when they get an opportunity. I've also built and sent x86_64
versions of the RPMS.

David, these SRPMS should form a pretty good basis for a FC4 update. I've put a
bit of effort into cleaning things up and updating specfiles and lib64 patches,
so they should be in good shape. I've also moved the conduits to
/usr/lib{64}/gnome-pilot/conduits/ instead of /usr/share/gnome-pilot/conduits/
as requested.

To ensure you're getting the latest packages, here are the new versions:
pilot-link-0.12.0-0.pre4.0.fc4.2
gnome-pilot-2.0.13-4
gnome-pilot-conduits-2.0.13-2
evolution-2.2.2-6
evolution-data-server-1.2.2-4
Comment 51 Mark Adams 2005-07-22 19:25:17 UTC
The updated RPMS are now available at both sites listed above. Patrick, can you
verify that syncing memo files now works for you?
Comment 52 Patrick Steiner 2005-07-23 17:07:57 UTC
With the latest RPMS syncing memofiles work again. Many thanks.
Comment 53 Teppo Turtiainen 2005-08-03 19:39:10 UTC
*** Bug 309098 has been marked as a duplicate of this bug. ***
Comment 54 Teppo Turtiainen 2005-08-03 19:39:33 UTC
*** Bug 312456 has been marked as a duplicate of this bug. ***
Comment 55 Teppo Turtiainen 2005-08-05 08:00:29 UTC
*** Bug 312617 has been marked as a duplicate of this bug. ***
Comment 56 Christian Kirbach 2005-09-11 09:43:51 UTC
*** Bug 315958 has been marked as a duplicate of this bug. ***
Comment 57 Christian Kirbach 2005-09-11 09:47:25 UTC
*** Bug 315475 has been marked as a duplicate of this bug. ***
Comment 58 Christian Kirbach 2005-09-11 09:47:37 UTC
*** Bug 313371 has been marked as a duplicate of this bug. ***
Comment 59 Christian Kirbach 2005-09-11 09:54:11 UTC
the last dups are all FC4.

given the vast number of duplicates this needs to be fixed.

raising priority.
Comment 60 JP Rosevear 2005-09-14 22:55:48 UTC
Fedora does patch to use p-l 0.12 which changed the memory handling.
Comment 61 Gilboa Davara 2005-09-23 13:47:18 UTC
Mark,

Your fix seems to work just fine on my FC4/x86-64. Thanks!
However, current Fedora RPM versions are closing in, which may cause them to
upgrade your RPMs, breaking the Palm sync (again).
Can you bump your RPM versions, maybe syncing the fixes with Fedora. (I believe
we spoke about it in Fedora's -devel list)

Thanks again!
Comment 62 David Cafaro 2005-10-11 19:51:18 UTC
Well, using only the gnome-pilot and gnome-pilot-conduits packages on a fully
updated Fedora Core 4 x86 (As of 10-11-2005), syncing now works.  Hope they get
FC4 updated in the maintstream soon.

Thank you much for your work!!!
Comment 63 Sebastien Bacher 2005-11-20 16:45:13 UTC
*** Bug 316953 has been marked as a duplicate of this bug. ***
Comment 64 Sebastien Bacher 2005-11-20 16:45:17 UTC
*** Bug 317094 has been marked as a duplicate of this bug. ***
Comment 65 Sebastien Bacher 2005-11-20 16:45:31 UTC
*** Bug 318033 has been marked as a duplicate of this bug. ***
Comment 66 Sebastien Bacher 2005-11-20 16:45:36 UTC
*** Bug 318341 has been marked as a duplicate of this bug. ***
Comment 67 Sebastien Bacher 2005-11-20 16:45:42 UTC
*** Bug 319478 has been marked as a duplicate of this bug. ***
Comment 68 Sebastien Bacher 2005-11-20 16:45:50 UTC
*** Bug 320240 has been marked as a duplicate of this bug. ***
Comment 69 Sebastien Bacher 2005-11-20 16:45:55 UTC
*** Bug 320882 has been marked as a duplicate of this bug. ***
Comment 70 Teppo Turtiainen 2005-12-05 17:34:22 UTC
*** Bug 323216 has been marked as a duplicate of this bug. ***
Comment 71 Teppo Turtiainen 2005-12-09 20:29:59 UTC
*** Bug 323538 has been marked as a duplicate of this bug. ***
Comment 72 Karsten Bräckelmann 2006-01-28 23:38:57 UTC
*** Bug 327774 has been marked as a duplicate of this bug. ***
Comment 73 Karsten Bräckelmann 2006-01-28 23:39:03 UTC
*** Bug 328467 has been marked as a duplicate of this bug. ***
Comment 74 Matt Davey 2006-02-07 14:13:56 UTC
The current gnome-pilot CVS has been updated, and should fix this issue when compiled against current pilot-link CVS.
Comment 75 Olav Vitters 2006-02-09 17:25:09 UTC
*** Bug 330536 has been marked as a duplicate of this bug. ***
Comment 76 Karsten Bräckelmann 2006-02-15 20:37:42 UTC
*** Bug 331318 has been marked as a duplicate of this bug. ***
Comment 77 Karsten Bräckelmann 2006-02-23 20:17:55 UTC
*** Bug 332363 has been marked as a duplicate of this bug. ***
Comment 78 Karsten Bräckelmann 2006-03-05 00:27:44 UTC
*** Bug 333410 has been marked as a duplicate of this bug. ***
Comment 79 Matt Davey 2006-03-08 17:39:14 UTC
*** Bug 333742 has been marked as a duplicate of this bug. ***
Comment 80 Matt Davey 2006-03-31 11:40:44 UTC
*** Bug 336698 has been marked as a duplicate of this bug. ***
Comment 81 Matt Davey 2006-04-17 08:27:02 UTC
*** Bug 338740 has been marked as a duplicate of this bug. ***
Comment 82 André Klapper 2006-10-05 13:32:05 UTC
according to comment #74, this issue should be fixed in gnome-pilot 2.0.13 or later. can anyone please re-test this? thanks a lot in advance for helping!
(no duplicates for half a year now, setting status to NEEDINFO.)
Comment 83 Matt Davey 2006-10-05 13:45:50 UTC
Previous comment should read *fixed in gnome-pilot 2.0.14 or later*.  gnome-pilot 2.0.13 won't build against pilot-link 0.12.x, but gnome-pilot 2.0.14 will.  This bug was caused by a buggy redhat patch to port gp 2.0.13 to pl 0.12.x.

The lack of duplicates would correspond to when redhat downgraded fc5 to pilot-link 0.11.8.

Closing this bug.