From owner-freebsd-ports  Fri Jun  2 13:50:12 2000
Delivered-To: freebsd-ports@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 5011237B78C
	for <freebsd-ports@FreeBSD.org>; Fri,  2 Jun 2000 13:50:01 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id NAA08796;
	Fri, 2 Jun 2000 13:50:01 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from snapple.webct.com (snapple.webct.com [209.87.17.45])
	by hub.freebsd.org (Postfix) with ESMTP id 142A937B78C
	for <FreeBSD-gnats-submit@freebsd.org>; Fri,  2 Jun 2000 13:48:42 -0700 (PDT)
	(envelope-from varju@snapple.webct.com)
Received: (from root@localhost)
	by snapple.webct.com (8.9.3/8.9.3) id NAA00583;
	Fri, 2 Jun 2000 13:48:41 -0700 (PDT)
	(envelope-from varju)
Message-Id: <200006022048.NAA00583@snapple.webct.com>
Date: Fri, 2 Jun 2000 13:48:41 -0700 (PDT)
From: Alex Varju <varju@ca.webct.com>
Reply-To: varju@ca.webct.com
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: ports/18971: bug fix for ports/palm/jpilot
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         18971
>Category:       ports
>Synopsis:       bug fix for ports/palm/jpilot
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 02 13:50:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Alex Varju
>Release:        FreeBSD 5.0-CURRENT i386
>Organization:
WebCT
>Environment:
>Description:
There is a problem with the synchronization routines in jpilot, which
cause the process to hang sometimes.  Thomas Runge
<runge@rostock.zgdv.de> sent me a patch the other day which should
solve the problem.  Here is his summary:

|As you probably found out, jpilot has a big problem with
|synchronizing. Almost everytime it freezes after that, all you can do
|is killing the process.  Thats very annoying and I had a look into the
|sources. The problem was, that the author makes a lot of X-calls
|inside a signal handler and a debugging sessions shows, that the
|problem lies in XSync. I guess, it works on Linux, because they have
|thread-save X-libs, which we do not have by default, yet.  Please find
|my patches attached, they work for me and will most probably work on
|every unix.

I've emailed the author, and he has said that this patch will be in
the next release of jpilot.

>How-To-Repeat:
This bug is intermittent, but it usually occurs after synchronization
with the pilot.
>Fix:
The following patch should be created as
ports/palm/jpilot/patches/patch-bd


--- jpilot.c      Sat Feb 12 21:33:21 2000
+++ jpilot.c.orig Fri May 19 19:49:10 2000
@@ -609,6 +609,11 @@
            bad_sync_exit_status(exit_status);
         }
       }
+      /*Look for finish message */
+      Pstr1 = strstr(buf, "Finished");
+      if (Pstr1) {
+        cb_app_button(NULL, GINT_TO_POINTER(REDRAW));
+      }
    }
 }

--- sync.c        Thu Feb 24 03:20:33 2000
+++ sync.c.orig   Fri May 19 19:48:43 2000
@@ -107,7 +107,7 @@
    waitpid(-1, NULL, WNOHANG);
 
    /*refresh the screen after a sync */
-   cb_app_button(NULL, GINT_TO_POINTER(REDRAW));
+   /*cb_app_button(NULL, GINT_TO_POINTER(REDRAW));*/
 
    return;
 }


>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message